15BR_LocalizingOracleBiData.pdf

download 15BR_LocalizingOracleBiData.pdf

of 19

Transcript of 15BR_LocalizingOracleBiData.pdf

  • Copyright 2008, Oracle. All rights reserved.

    Localizing Oracle BI Data

  • Copyright 2008, Oracle. All rights reserved.15 - 2

    Objective

    After completing this lesson, you should be able to localize

    Oracle BI data to support multilingual environments.

  • Copyright 2008, Oracle. All rights reserved.15 - 3

    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 support to Oracle BI.

  • Copyright 2008, Oracle. All rights reserved.15 - 4

    Oracle BI Multilingual Support

    Requires three types of configurations:

    Repository metadata, such as presentation folders

    Database data, such as product names

    Report and dashboard metadata, such as chart labels

    Focus of last lesson

    Focus of this lesson

    Covered in a separate course

  • Copyright 2008, Oracle. All rights reserved.15 - 5

    Required Translation Tables

    Data translation requires two tables:

    List of values (LOV) language translation table

    Provides functionality similar to metadata translation table

    Available language table

    Provides list of available user data languages

  • Copyright 2008, Oracle. All rights reserved.15 - 6

    ABC Example

    Translate ABC product-type data from English to French.

  • Copyright 2008, Oracle. All rights reserved.15 - 7

    Steps for Localizing Data

    1. Create a language translation table.

    2. Create an available language table.

    3. Import tables to the Physical layer.

    4. Create a session variable initialization block.

    5. Create a language translation table alias.

    6. Create physical joins.

    7. Map the logical table source.

    8. Create column mapping.

    9. Apply a WHERE filter.

    10.Verify the results.

  • Copyright 2008, Oracle. All rights reserved.15 - 8

    1. Create a Language Translation Table

    This table contains required columns and the language value

    translations.

    Language-

    independent code (LIC): Identifies

    which record is being

    translated

    VAL: Translated data

    that is displayed to

    the user

    LANG_ID: Code

    that identifies the

    language of the row

    TYPE: A categorization for

    a set of values

  • Copyright 2008, Oracle. All rights reserved.15 - 9

    2. Create an Available Language Table

    This table stores a list of languages available for querying

    against the data.

    LANGUAGE_EXTENSION:

    identifies language variations

    based on country or region

    LANG_ID: identifies the

    language of the row

    LANGUAGE: identifies the

    language name

  • Copyright 2008, Oracle. All rights reserved.15 - 10

    3. Import Tables to the Physical Layer

    Use known techniques to import language tables to the

    Physical layer of the repository.

    Language translation table

    Available language table

  • Copyright 2008, Oracle. All rights reserved.15 - 11

    4. Create a Session Variable Initialization Block

    Create a session variable initialization block to check whether

    the language selected by the user is in the language table.

    Checks whether the user

    language preference stored in WEBLANGUAGE is in the

    D1_LANG table

    Language default if the preferred language is not found in the D1_LANG table

    Session variable

  • Copyright 2008, Oracle. All rights reserved.15 - 12

    5. Create a Language Translation Table Alias

    Create an alias of the LOV table for each column that needs to

    be translated.

    Set the alias name to the

    name of the column to be

    translated.

  • Copyright 2008, Oracle. All rights reserved.15 - 13

    6. Create Physical Joins

    Create a join between the product dimension and the alias for

    the column translation.

    Dimension table

    column to be

    translated joins to LIC in alias table.

    Join finds all

    translations in

    alias table for a

    given item type.

  • Copyright 2008, Oracle. All rights reserved.15 - 14

    7. Map the Logical Table Source

    Map an existing logical table source to the alias.

    Alias table

  • Copyright 2008, Oracle. All rights reserved.15 - 15

    8. Create Column Mapping

    Modify the Type field to map to the VAL column in the ItemType

    (D1_LOV_D) alias.

  • Copyright 2008, Oracle. All rights reserved.15 - 16

    9. Apply a WHERE Filter

    To the logical table source, apply a WHERE filter that:

    Searches in the alias table for records that have the

    same language ID as

    specified in the language

    initialization block

    Identifies the set of records in the alias table that are of

    the ABC Product Type

    category

  • Copyright 2008, Oracle. All rights reserved.15 - 17

    10. Verify the Results

    Run a query in Answers and verify that the expected results are returned.

    Check the log file and verify that the VAL column is accessed with the expected WHERE clause.

  • Copyright 2008, Oracle. All rights reserved.15 - 18

    Summary

    In this lesson, you should have learned how to localize Oracle

    BI data to support multilingual environments.

  • Copyright 2008, Oracle. All rights reserved.15 - 19

    Practice 15-1 Overview:

    Localizing Oracle BI Data

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

    French.