A Lookup Table for Each Translated Field

Localizing Oracle Business Intelligence 15-25 the current language. The column is not derived from any other logical column unlike logical lookup columns. The following procedure explains how to configure a physical lookup translation column using the previous example. To configure a translation column that is derived from a physical lookup table: 1. Open the repository in the Administration Tool. 2. In the Business Model and Mapping layer, create a new logical column by right-clicking the appropriate logical table for example, Categories and selecting New Object , then Logical Column. 3. Provide a name for the logical column for example, categoryname_p. 4. Select the Column Source tab.

5. In the Logical Table Source box under Derived from physical mappings,

double-click the logical table source object that contains the base table column. The Column Mapping tab of the Logical Table Source dialog is displayed.

6. Ensure that Show unmapped columns is selected.

7. In the Expression column for the new logical column for example, categoryname_

p, enter an expression such as the following: INDEXCOLVALUEOFNQ_SESSION.LAN_INT, DB_Name.My_Category.My_Schema.Categories.CategoryName, LOOKUPSPARSE DB_Name.My_Category.My_Schema.CATEGORIES_TRANS.CATEGORYNAME, DB_Name.My_Category.My_Schema.Categories.CategoryName, DB_Name.My_Category.My_Schema.Categories.CategoryID, VALUEOFNQ_SESSION.LANGUAGE You can also use Expression Builder to create the expression.

8. Click OK in the Logical Table Source dialog.

9. Click OK in the Logical Column dialog.

10. Save your changes. The Categories_trans physical translation table does not need to be incorporated into the logical table source. The INDEXCOL function checks that if the LAN_INT session variable is 0, then the categoryname column is fetched from the base table. Note the following about the LOOKUP function: ■ The physical LOOKUP function works the same as a logical LOOKUP function. The only difference is that all the references to logical tables and columns are replaced by physical tables and columns. ■ The first column of the LOOKUP function is a value column, which is a translation value column from a translation table. The second column is the base value column, if a sparse lookup exists. The remaining columns are columns or values to be joined to the physical translation table, which is the table that is implied by the value column of the LOOKUP function. Because you cannot use a dialog to configure a physical lookup table, you must ensure that the order of the join columns and values is compatible with the column sequence that is displayed in the Physical Table dialog for the physical translation table. For example, on the Keys tab of the Physical Table dialog for the Categories_trans table, the primary key is composed of the CategoryID and Language_Key columns. The columns that are specified in the LOOKUP function correspond to these columns: