Development > Business intelligence > Setup > Datamart 

This function is used to define a datamart that can be used in the company managing functions. A datamart corresponds to a set of facts tables that cab be used for the decision support reports.

    Prerequisites

    SEEREFERTTO Refer to documentation Implementation

    Screen management

    Entry screen

    Presentation

    The entry screen is used to define in a grid the set of facts tables used by the datamart.

    Close

     

    Fields

    The following fields are present on this tab :

    Block number 1

    This code identifies the created records in a unique manner.

    • Title (field ZINTIT)

    It used to define a name associated with each record.

    • Abbreviation (field ABR)

     

    Characteristics

    An activity code is used to:

    • make optional an element in the dictionary if the value associated with the activity code is null.
    • identify the specific/custom elements if they are marked with a code starting with X, Y or Z.
    • size a maximum number of lines when the activity code marks elements from a grid.

    In this way, if the activity code is disabled, the marked element will not be useable, and the associated code (if any) will neither be generated nor can be activated.

    • Module (field MODULE)

    Module belonging to the setup. This field is used to specify whether the screen has to be created in the folder database. It is specified when the module linked to the screen is active in the folder.

    Setup

    • Authorization site (field AUZFCY)

     

     

    • Limit size of result (field RESULT)

     

    • field WA

     

    • Limit execution to (field DUREE)

     

    • field WB

     

    • field WC

     

    • ANSI standard (field ANSI)
    • Flag class (field MESURE)
    • field WD

     

    • Null date management (field DATNUL)
    • Add. info. (field COMPL)
    • field WE

     

    • Sub-class (field SCLASS)
    • Prefix (field PREFIX)

    Table Fact tables

    Define the code of a facts table associated with the datamart.

    • Title (field INTABF)

     

    An activity code is used to:

    • make optional an element in the dictionary if the value associated with the activity code is null.
    • identify the specific/custom elements if they are marked with a code starting with X, Y or Z.
    • size a maximum number of lines when the activity code marks elements from a grid.

    In this way, if the activity code is disabled, the marked element will not be useable, and the associated code (if any) will neither be generated nor can be activated.

    Close

     

    Specific Buttons

    Once all the structures (datamart, facts tables, dimensions, etc.) are defined, a generation operation creates the dictionary structures used by the business intelligence module. Here this is a BO environment (TM).

    The generation logic is as follows:

    • a class is created for each facts table defined in the datamart. In this class there is an object for each field of type Information or Measure present in the facts table.
    • a class is created for each crossing facts table/datamart dimension. In this class there is an object for each field of type Dimensionor Informationpresent in the dimension and in the parent dimensions gone through one after the other.

    This button is used to list the classes and object to be generated and displays as an error the duplicates (fields that have the same name). These are non-blocking errors: indeed, in this case, aliases are automatically created and the second field found gets the characters _2 at the end of the name, the following gets _3, and so on. But these errors are still displayed because the universe is harder to understand due to these duplicates.

    The following fields are present on the window opened through this button :

    Block number 1

    • field OBJET

     

    • field CLES

     

    Block number 2

    • From folder (field DOSORG)

    This field is used to define the folder from which the record is going be copied. The possible syntaxes are described in the dedicated appendix.

    • All folders (field TOUDOS)

    This option is used to copy the record to all the folders defined in the dictionary (ADOSSIER table from the current solution).

    • To folder (field DOSDES)

    This field used to define the folder in which the record is going be copied. The possible syntaxes are described in the dedicated appendix.

    Close

    This button is used to copy the record definition from or to another folder.

    Menu Bar

    Copy

    Documentation / Paragraphs

    This function is used to access the documentation management on the first paragraph of the documentation (if there is one) associated to the current record.

    Documentation / Links

    This function is used to access the links management. It is used to define the links between the current and other records (for example the links between functions and setups). These links are specific to the documentation and are used to load the generation of documentation structures.

    Documentation / Generation

    This menu is used to launch a documentation generation. The generation can also be launched from the [Generation] button at the bottom of the window.

    Three types of generation can be launched one by one or simultaneously:

    • the generation of the documentation structure from the dictionary (tables ADOCUMENT, ADOCBLB, ADOCCLB).
    • the generation of the documentation from the previous tables.
    • the generation of the field documentation.

    The range suggested by default takes into account the current record but it can be modified upon launch.

    Error messages

    The only error messages are the generic ones.

    Tables used

    SEEREFERTTO Refer to documentation Implementation