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 current record in a unique way.

    • Description (field ZINTIT)

     

    • Abbreviation (field ABR)

     

    Characteristics

    An activity code is used to:

    • Make an element optional 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

    If the activity code is disabled:

    • The marked element will not be useable
    • The associated code will not be generated nor activated
    • Module (field MODULE)

    Select a module for the setup.

    Use this field to specify if the screen has to be created in the folder database. This is the case when the module linked to the screen is active on 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)

    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.

    • field WD

     

    • 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

    • field WE

     

    • 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 an element optional 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

    If the activity code is disabled:

    • The marked element will not be useable
    • The associated code will not be generated nor 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)

    Use this field to define the folder from which the record will be copied. The possible syntaxes are described in the Dedicated appendix.

    • All folders (field TOUDOS)

    Use this option to copy the record to all the folders defined in the dictionary (ADOSSIER table of the current solution).

    • To folder (field DOSDES)

    Use this field to define the folder to which the record will 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 menu item allows access to the documentation management on the first paragraph of the documentation (if there is one) associated with the current record.

    Documentation / Links

    This menu item allows access to link management. It is used to define the links between the current record and other records (for example, the links between functions and parameters). These links are specific to the documentation and are used to load the generation of documentation structures.

    Documentation / Generation

    This menu item launches a documentation generation. You can also launch it from the Generation button at the bottom of the screen.

    You can launch three types of generation one by one or simultaneously

    • The generation of the documentation structure from the dictionary (ADOCUMENT, ADOCBLB, and ADOCCLB tables)
    • 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 you can modify it at launch time.

    Error messages

    The only error messages are the generic ones.

    Tables used

    SEEREFERTTO Refer to documentation Implementation