MLS Table Structure

Following points must be taken care during MLS table creation:

  • Description columns on which the Hierarchy definition is based should also be present in the MLS table.
  • A column of data type Varchar / Varchar2 should be present in the MLS table. This column should contain the information about the locale (such as fr_FR, ko_KR). Refer to the MLS Table Configuration section for more details.
  • Going forward Dimension related information will be maintained in OFSAAI tables. Before proceeding with the configuration of Dimension and its MLS table, the following master tables need to have data.
    • CSSMS_SEGMENT_MAST
      • This table holds information about the segments present in OFSAAI and an entry needs to be present in this table for mapping a dimension to a segment/ folder. The Dimension data to be seeded into AAI tables can be mapped to the folder/segment ‘DEFAULT’. So the entry for ‘DEFAULT’ folder needs to be included in this table.
    • AAI_OBJ_TYPE_B
      • This table holds information about various object types supported in OFSAAI such as Dataset, Business Measure, and so on. For Dimension management, the object type will be DIMENSION.
    • AAI_OBJ_TYPE_TL
      • This table holds locale specific information about various object types present in OFSAAI. Locale specific information about the object type ‘DIMESNION’ needs to be added here.
    • AAI_OBJ_SUBTYPE_B
      • This table holds information about different objects’ sub types supported in OFSAAI. The different sub types associated with a ‘DIMENSION’ object will be mentioned in this table.
    • AAI_OBJ_SUBTYPE_TL
      • This tables hold locale specific information about various object sub types present in OFSAAI and information on the subtypes of ‘DIMESNION’ are maintained in this table.

Note:

Refer to the HNL_Data for more information on the sample data. The data provided in each of these tables is not exhaustive and has been provided as per requirements of Hierarchy Node Localization only.