What is Double Column Support?

15-24 System Administrators Guide for Oracle Business Intelligence Enterprise Edition Handling Non-ISO Type Language Codes If the data has non-ISO type language codes in the tables, then there should be a table that maps ISO language codes to non-ISO language codes. You can use the preexisting WEBLANGUAGE variable that sets the ISO language code when a user logs in. You define a separate LANGUAGE variable whose initialization block runs a query against a mapping table to fetch the non-ISO language code filtered by the value from the WEBLANGUAGE variable. Table 15–3 provides a mapping table for non-ISO language codes. LANGUAGE is a non-ISO language code.

15.6.6 Creating Physical Lookup Tables and Physical Lookup Columns

You can create physical lookup table objects in the business model to define the necessary metadata for translation lookup tables. Physical lookup tables are similar to logical lookup tables in both semantics and usage. Physical lookup tables address the following scenarios that logical lookup tables cannot handle: ■ The lookup table source is fragmented. In this case, use multiple physical lookup tables to hold the values. For example, translation values for fragmented product name data can be distributed in two physical lookup tables called productname_ trans_AtoM and productname_trans_NtoZ. ■ Different levels of translation tables are available. For example, translations are available in both an Essbase data source and a relational data source. It is preferable to use the same source as the base query. Unlike logical lookup tables, which you designate by selecting an option in the Logical Table dialog, you configure physical lookup tables by constructing lookup functions in the logical table source mapping. For example, suppose that you have the following physical tables: ■ A base table called Categories, with columns such as categoryid and categoryname. ■ A translation table called Categories_Trans, with columns such as categoryid, language_key, and categoryname. The translated value of categoryname is determined through a combination of the categoryid and language_key columns. Suppose that you have a logical table called Categories. In that table, you add a new logical column called categoryname_p, which is a translation column that depends on Note: You cannot use a derived logical column that is the result of a LOOKUP function as part of a primary logical level key. This limitation exists because the LOOKUP operation is applied after aggregates are computed, but level key columns must be available before the aggregates are computed because they define the granularity at which the aggregates are calculated. You can use a derived logical column that is the result of a LOOKUP function as a secondary logical level key. Table 15–3 Mapping Table for Non-ISO Language Codes WEBLANGUAGE LANGUAGE LAN_INT en ENG cn CHI 1 fr FRA 1