Enable multi-language support for the Oracle BIEE data source in BI Publisher

Marcus M. Thompson

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

Sage Intacct

Description (Required):

In our OAS environment, we have used the Externalize Strings functionality in the RPD to create session variables for displaying the names of presentation layer tables and columns in different languages. This works great in Analytics. For example, users in the U.S. might select the Month column, while our French-speaking users could select Mois, and our Germans would see Monat. Cool functionality.

But when building a BI Publisher data model, and selecting Oracle BIEE as the data source, that multi-language functionality is not present. Instead, everyone sees the native, untranslated column names, such as Month.

When building a BI Publisher data model using the Oracle BIEE data source, we need the interface to reflect the same multi-language capabilities that we see in Analytics.

Use Case and Business Need (Required):

We need to create BI Publisher data models that include data from OBIEE and data from database tables. The data from OBIEE needs to be presented in the user's language, just as it is in Analytics.

Our first thought was to just create an analysis (which presents the user's language correctly) and use that as the source of our OBIEE data in the BI Publisher data model. But that won't work, because a dataset sourced from an OBIEE Analysis can't join with another dataset. The Create Link option is grayed out for datasets sourced from an OBIEE Analysis.

The other option for using OBIEE as a data source is to select the Oracle BIEE option as the source for the dataset, which as mentioned above presents the tables and columns only in their native form as seen in the RPD, not in the user's language as seen in Analytics. We believe this is because the Oracle BIEE option connects directly to the RPD, and does not launch a session of Oracle BI, therefore the initialization blocks are not executed, and the session variables that drive the externalized strings for multi-language support are not populated.

Enhancement Request / Service Request: SR 3-30566997691