Localizing Oracle BI Data

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Objective
After completing this lesson, you should be able to localize Oracle BI data to support multilingual environments.

16 - 2

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Business Challenges and Solution

Challenges: Companies require multilingual support for global deployments of Oracle BI. Users need to make decisions based on applications and data presented in their own language. Solution: Add multilingual data support to Oracle BI.

16 - 3

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Oracle BI Multilingual Data Support

Requires three types of configurations: Repository metadata, such as presentation folders
Focus of last lesson

Database data, such as product names

Focus of this lesson

Analysis and dashboard metadata, such as chart labels

Covered in a separate course

16 - 4

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

What Is Multilingual Data Support?

Multilingual data support is the ability to display data from database schemas in multiple languages.
Product data in English Data translated to French

16 - 5

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Required Translation Tables

Available language table
Provides list of available languages

Lookup translation table

Contains translations

16 - 6

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Available Language Table

Defines the language for users when they log in to Oracle BI Server.

16 - 7

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Lookup Tables
Multilingual schemas typically store translated fields in separate tables called lookup tables.
Base table contains data in base language. Lookup tables contain translations for descriptor columns in several languages.

16 - 8

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Designing Translation Lookup Tables

There are two common techniques for designing translation lookup tables in a multilingual schema: Lookup table for each base table Lookup table for each translated field
Base table contains data in base language.

Lookup table for each base table

Lookup table for each translated field

16 - 9

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

ABC Example
Translate ABC product data from English to French.

16 - 10

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Steps for Localizing Data

1. 2. 3. 4. 5. 6. 7. 8. 9. Create a physical lookup table. Create an available language table. Import tables to the Physical layer. Create a session variable initialization block. Create a logical lookup table. Set keys for the logical lookup table. Create a logical lookup column. Add the logical lookup column to the Presentation layer. Test your work.

16 - 11

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

1. Create a Physical Lookup Table

Create a lookup table with translated fields in your physical data source.
Product Type base table Separate lookup table for Product Type base table

16 - 12

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

2. Create an Available Language Table

In your physical data source, create an available language table that defines the language for users when they log in to Oracle BI Server.

16 - 13

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

3. Import Tables into the Physical Layer

Import the lookup table and available language table into the Physical layer of the repository.

Available language table

Lookup table

16 - 14

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

4. Create a Session Variable Initialization Block

Create an initialization block that populates a variable with a language code based on user login.

LAN_INT session variable is populated with value from LAN_INT column in D1_LANG table based on user name supplied by the :USER system variable.

16 - 15

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

5. Create a Logical Lookup Table

Create a logical lookup table object in the business model to define the necessary metadata for a translation lookup table.

Select to designate as a lookup table.

16 - 16

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

6. Set Keys for the Logical Lookup Table

Specify the key column order to match the order of corresponding arguments in the LOOKUP function.

Lookup key Use arrows to set key column order. Lookup key

identifies value column.

16 - 17

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

7. Create a Logical Lookup Column

Create a logical column that includes the LOOKUP function.

Logical column uses the INDEXCOL and LOOKUP functions.

16 - 18

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

8. Add the Logical Lookup Column to the Presentation Layer

16 - 19

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

9. Test Your Work

Log in as local user. Create an analysis using the logical lookup column.

Verify that results are returned with the expected translation.

16 - 20

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Summary
In this lesson, you should have learned how to localize Oracle BI data to support multilingual environments.

16 - 21

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practice 16-1 Overview: Localizing Oracle BI Data

In this practice, you localize product type data from English to French.

16 - 22

Copyright 2010, Oracle and/or its affiliates. All rights reserved.