BI Publisher Scheduler does not provide Multi Language Support for data translation

Valeriy Gorbunov-80491

Organization Name

Chartwell Master Care LP

Description

When a multi-language BI Publisher (BIP) report is being RUN ONLINE, both, static template content and dynamic data, are translated using User profile's currently selected language, and it works fine.

Problem appears when the report is SCHEDULED using BIP Scheduler. Scheduled Request submission parameters include 'Locale' that is responsible for the scheduled report's language and it does only a half of job - supporting translation of static template content only.

Imagine, the User has the current language set as 'English' and is submitting a request choosing the report's 'Locale' = "French". Next, the job will translate the static template content to 'French' (from XLIFF file) but all dynamic data will be in the User's "English" because the report's SQL has no way to know what the 'Locale' was used to submit the BIP Scheduled request. At the end, the report will have all headings and other static data in French and tabular (dynamic) data in English, not nice.

Use Case and Business Need

One would say, let the User change their current language equal to 'Locale' being set for Scheduling and that's it, not a big deal. However, here is coming a report in multi-language company bursting output to many hundreds subsidiaries in different languages and the 'Locale' is being set automatically to according to each subsidiary preferred language, and dynamic data must be translated to the same language. And BIP Scheduler doesn't provide at report's SQL run time any information what the current 'Locale' parameter value is, really not nice.

More details

Oracle BI Publisher Scheduler should provide a way for the Data Model's SQL to read current 'Locale' value to support it's (Oracle) own "Multi Language Support" and allow proper dynamic data translation.

Anything that can be accessed as public from, say, FUSION schema for HCM, global variable, function returning 'Locale' value, etc, would work. Probably the best solution is to change the DB session user environment variable 'LANG' to 'Locale' value.

Initial Oracle Support SR for the subject: 3-20946204011

Original Idea Number: 251fd5299f

Valeriy Gorbunov-80491

Actually, Oracle provides a number of system variables in BI Publisher available to SQL during run-time. There is a variable XDO_USER_REPORT_LOCALE that fits the purpose and it works in online report run, but (oops...) it is not populated during scheduled report execution.

Re-opened Oracle SR...