MLS Table Configuration

Consider a Hierarchy “Income” defined on a dimension table “DIM_INCOME”. The table structure is as indicated in the following table:

Table 6-1 Column Name, Primary Key, and Datatype information for MLS Table Configuration

Column Name Primary Key Datatype
N_CUST_INCOME_BAND_CODE PK Number(5,0)
FIC_MIS_DATE Date
V_CUST_INCOME_SHORT_DESC Varchar2(80)
V_INCOME_DESC Varchar2(80)
N_D_INCOME_UPPER_VALUE Number(22,3)
N_D_INCOME_LOWER_VALUE Number(22,3)

The primary key of DIM_INCOME table is PK_DIM_INCOME and is enforced on the column N_CUST_INCOME_BAND_CODE.

An MLS table with name, say “DIM_INCOME_LANG” can be created in the Atomic Schema to provide MLS support for DIM_INCOME. The structure of this table can be as indicated in the following table:

Table 6-2 Column Name, Primary Key, and Datatype information for MLS Table Configuration

Column Name Primary Key Datatype
N_INCOME_BAND_CODE PK Number(5,0)
LOCALE_CD Varchar2(10)
V_CUST_INCOME_SHORT_DESC Varchar2(80)
The MLS table corresponding to the Dimension DIM_INCOME can be created as follows:
  • Create a table to provide MLS support for the Dimension DIM_INCOME. For example, assume the name of the table is DIM_INCOME_LANG. This table which is to provide MLS related information for DIM_INCOME ,needs to be configured:
    • AAI_OBJECT_B
      • This table registers information about an AAI object. Since Dimension is considered as an AAI object, the data corresponding to the Dimension DIM_INCOME needs to be maintained in this table.
    • AAI_OBJECT_TL
      • This table holds locale specific information about an object in AAI. So locale specific information pertaining to the Dimension, DIM_INCOME, needs to be maintained in this table.
    • AAI_DIMENSION
      • This table will provide further information about the DIMENSION table. Information such as whether the data in dimension table is in PC structure, whether the members are acquired in the dimension, and so on are maintained in this table.
    • AAI_DIM_META_TABLE
      • This is the metadata table for a DIMESNION. Information about the table such as the MLS table meant for the Dimension, the hierarchy table, the attribute table, and so on will be maintained in this table.
    • AAI_DIM_META_COLUMN
      • This table provides information about various columns that will be used for a Dimension table. From Hierarchy Node Localization perspective, the name of the locale column which will hold locale information needs to be maintained here.
    • AAI_DIM_META_JOIN
      • This table holds information about the columns that will be used for joining the Dimension table with other tables such as the MLS table, Hierarchy table, Attribute table, and so on. Here multiple join conditions can be specified as well. Refer to HNL_Data excel for further information on providing joining columns information with respect to Hierarchy Node Localization.

The following table displays sample data which can be populated in DIM_INCOME_MLS table in a setup where there are 2 locales installed say, English (en_US) and Chinese (zh_CN).

Table 6-3 Sample data that is populated in the MLS table

N_CUST_BAND_CODE V_INCOME_DESC LOCALE_CD
1 AAA en_US
2 BBB en_US
1 CCC zh_CN
2 DDD zh_CN

Note the following:

  • In Regular BI enabled and PC Hierarchies, the Level Description expression should not contain columns with Number or Date data types. The inclusion of such a column in the Level Description expression would prevent the Business Hierarchy from generating nodes.
  • There is no concept of default locale. Whenever a Hierarchy is saved, the translated node descriptions present in MLS table are saved in the corresponding columns of the REV_LOCALE_HIER table depending on the availability of translated values in the MLS table.
  • The inclusion or exclusion of nodes from a Hierarchy will be reflected in Forms once the Hierarchy is resaved.