Creating Logical Lookup Tables

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: 15-26 System Administrators Guide for Oracle Business Intelligence Enterprise Edition ■ The following line: DB_Name.My_Category.My_Schema.Categories.CategoryID corresponds to the Categories_trans.CategoryID column. ■ The following line: valueofNQ_SESSION.LANGUAGE corresponds to the Categories_trans.Language_key column. See Section 15.6.5, Creating Logical Lookup Tables and Logical Lookup Columns for information about lookup concepts like the LAN_INT and LANGUAGE session variables and full syntax information for the LOOKUP function.

15.6.7 Supporting Multilingual Data in Essbase Through Alias Tables

Often, members in Essbase cubes have separate aliases for each user language to enable users to view member names in their own language. Typically, you define a session variable to dynamically select the appropriate alias upon user login. See Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for information about Essbase alias tables and how to use them with session variables.

15.6.8 Enabling Lexicographical Sorting

Lexicographical sorting is the ability to sort data in alphabetical order. Most data sources support lexicographical sorting. However, if you notice that lexicographical sorting is not working properly for a particular data source, then you can configure the Oracle BI Server to perform the sort rather than the back-end data source. To perform this configuration, ensure that ORDERBY_SUPPORTED is not selected in the Features tab of the Database dialog in the Administration Tool. See Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for information about specifying database features. Note that disabling ORDERBY_SUPPORTED in the data source can have a very large performance impact, because consequently, many joins are not pushed down to the data source. In many cases, the performance impact is significant enough that ORDERBY_SUPPORTED should still be enabled in the data source, regardless of the impact on the lexicographical sorting functionality. 16 Configuring Currency Options 16-1 16 Configuring Currency Options When content designers create analyses, they often include data that shows currency, such as American dollars. As the administrator, you can perform various tasks that affect currency options that are available to users. This chapter includes the following topics: ■ Section 16.1, Changing the Default Currency for Analyses ■ Section 16.2, Defining User-Preferred Currency Options

16.1 Changing the Default Currency for Analyses

You can change the default currency that is displayed, for example, from French Francs to Euros. For information about using formatting functions in Answers, see Oracle Fusion Middleware Users Guide for Oracle Business Intelligence Enterprise Edition. To set the default currency: 1. Open the currencies.xml file in the directory ORACLE_HOME\bifoundation\web\display. 2. Search for the currency to make the default, for example, USD, CAD, PEN, or MAD. 3. Copy the entire currency element. For example, copy the currency tag for the Euro: - Currency tag=int:euro-l type=international symbol=_ displayMessage=kmsgCurrencyEuroLeft digits=2 format= negative tag=minus format=- Currency 4. Search for the text string int:wrhs, located near the top of the file. 5. Select the entire element and replace it by pasting the copied element over it. 6. Replace the tag attribute so it reads int:wrhs. For example, replace tag=int:euro-l with tag=int:wrhs. 7. Restart the service for Oracle BI Presentation Services. To specify the currency for a column in a customized subject area: 1. In Answers, modify the analysis that uses the subject area.

2. In the Analysis editor: Criteria tab, click the Options button for the currency

column and select Column Properties to display the Column Properties dialog. 3. Click the Data Format tab and select the Override Default Data Format box.