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.

    • Description (field ZINTIT)

    [object Object]

    • 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)

    [object Object]

    Setup

    • Authorization site (field AUZFCY)

     

     

    Block number 5

    • Limit size of result (field RESULT)

     

    • field WA

     

    • Limit execution to (field DUREE)

     

    • field WB

     

    Block number 6

    • ANSI standard (field ANSI)

    The designer manages the ANSI 92 syntax for the joins. ANSI 92 is not managed by default. The management has to be activated by setting this universe parameter SQL ANSI92 asYes.

    • Flag class (field MESURE)

    This parameter is used to group all the indicator fields of the fact table in a specific class.

    • Null date management (field DATNUL)

    This datamart parameter is used to manage X3 'null' dates in the universe.

    Depending on the database type, the date 12-31-1599 will be replaced by null.

    The date object select will display: a field that corresponds to the date field of the current table

      • For Oracle:

    "CASE WHEN " & Champ & " = '31-12-1599' THEN null Else " & Champ & " END COLCASE"

      • For SQL-SERVER

    "CASE {fn year(" & Champ & ")} WHEN 1753 THEN null ELSE " & Champ & "  END"

    • Additional info. (field COMPL)

    Addition used if there are two objects with the same name in a class

    • Sub-class (field SCLASS)

    This parameter determines whether subclasses are created or not during the universe generation.

    • Prefix (field PREFIX)

    This parameter is used to define the universe's object or not.

    Grid Fact tables

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

    • Description (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 included on the window opened through this button :

    Block number 1

    • field OBJET

     

    • field CLES

     

    Block number 2

    • From folder (field DOSORG)

    Indicate 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)

    Indicate 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 choice of menu allows to zoom to the documentation management, on the first documentation paragraph (if it exists) related to the current record.

    Documentation / Links

    This choice of menu allows to zoom on the dictionary link management function. This function allows to establish links between the current record and other records (for example links between functions and parameters). These links, dedicated for documentation purpose, allows the generation of documentation structure.

    Documentation / Generation

    This choice of menu allows to generate the documentation. Three types of generation can be separately or simultaneously started :

    • the generation of the structure of documentation from dictionary (tables ADOCUMENT, ADOCBLB, ADOCCLB).
    • the generation of the documentation itself from the previous table (they have been normally completed after the first generation).
    • the field help documentation generation.

    The ranges and parameter proposed by default are defaulted according ti the current record, but they can be changed during the execution.

    Error messages

    The only error messages are the generic ones.

    Tables used

    SEEREFERTTO Refer to documentation Implementation