Translate

Tuesday, 17 June 2014

OBIA 11.1.1.7.1 (ODI) Externalize RPD Presentation Layer


OBIA 11.1.1.7.1 (ODI) Externalize RPD Presentation Layer


How to Add String Localizations for Oracle BI Repository Metadata



OBIEE RPD – Init Block : RPD Msgs
If you added a new Column or Subject Area, follow this procedure to add string localizations in the Oracle BI Repository metadata.

To add string localizations for Oracle BI repository metadata:
1. Stop the OPMN services.
Use the command:
opmnctl stopall.
2. Open a database administration tool, and connect to the Oracle Business Analytics Warehouse schema.
3. Identify the strings for the following presentation objects:
- Subject area
- Presentation table
- Presentation hierarchy
- Presentation level
- Presentation column
For example, for the subject area Payables Invoices - Prepayment Invoice Distributions Real Time, you would enter the following strings:
Table 4-1 Example of Localization Strings

String
Presentation Object
Payables Invoices - Prepayment Invoice Distributions Real Time Subject area
Time Presentation table
Date – Year Presentation hierarchy
Total Presentation level
Year Presentation level
Calendar Year Presentation column



 
4. For each subject area, externalize the strings for localization and generate custom names for the presentation objects:
a. In the Oracle BI Administration Tool, right-click the subject area and select Externalize Display Names, and then select Generate Custom Names.
b. Save your work.
For more information about localizing strings, see "Localizing Metadata Names in the Repository," in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
5. Check the consistency of the repository, and remove any inconsistencies.
For instructions, see "Checking the Consistency of a Repository or Business Model," in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition (Oracle Fusion Applications Edition).
6. Enter the custom name of one of the presentation objects into the table C_RPD_MSGS:
7. INSERT INTO C_RPD_MSGS(MSG_ID, CREATED_BY, CREATION_DATE)
8. VALUES('<CUSTOM NAME OF PRESENTATION OBJECT>', 'CUSTOM', SYSTIMESTAMP);
9. COMMIT;
Note: To view the values for custom names and logical columns in the Administration Tool, right-click the presentation object and select Properties. The data in the "Custom display name" field appears in the format VALUEOF(NQ_SESSION.VALUE, where VALUE is the custom name for a presentation object, or the logical value for a presentation column. This value is the value that you need to enter in the VALUES section of the SQL statement above.
10. Enter the localized string for the presentation object in the previous step into the table C_RPD_MSGS_TL:
11. INSERT INTO C_RPD_MSGS_TL(MSG_ID, MSG_TEXT, LANGUAGE_CODE, CREATED_BY, CREATION_DATE)
12. VALUES('<CUSTOM NAME OF PRESENTATION OBJECT>', '<LOCALIZATION OF THE STRING'>, '<LANGUAGE CODE FOR TRANSLATED LANGUAGE>', 'CUSTOM', SYSTIMESTAMP);
13. COMMIT;
To identify the language code for a particular language, use the following SQL:
SELECT LANGUAGE_CODE, NLS_LANGUAGE, NLS_TERRITORY
FROM FND_LANGUAGES_B
WHERE INSTALLED_FLAG IN ('B', 'I');
14. Enter additional details about the presentation object into the table C_RPD_MSGS_REL as indicated by the following SQL:
15. INSERT INTO C_RPD_MSGS_REL(MSG_ID, MSG_NUM, MESSAGE_TYPE, CREATED_BY, CREATION_DATE)
16. VALUES('<CUSTOM NAME OF PRESENTATION OBJECT>', '<TRANSLATION OF THE STRING'>, '<LANGUAGE CODE FOR TRANSLATED LANGUAGE>', 'METADATA','CUSTOM', SYSTIMESTAMP);
17. COMMIT;
18. Repeat steps 6 through 8 for each presentation object requiring localization.
19. Validate that the physical connection of the session initialization block INIT_USER_LANGUAGE_CODE is operable:
a. In the Oracle BI Administration Tool, select Manage, Variables, Session Initialization Block.
b. Right-click INIT_USER_LANGUAGE_CODE.
c. In the Properties dialog, click Edit Data Source.
d. Click Test, and input the value for the language code. Then, click OK.
For example, for Arabic enter 'AR'.
The value
USER_LANGUAGE_CODE = '<language code>' should be returned.
If this value is not returned, the TNS entry for the data source is not properly configured.
20. Restart the OPMN services.
21. Verify the localized strings in Oracle BI Answers. On the login page, specify the appropriate language.
 

No comments:

Post a Comment

Google Big Query Clone / Copy DataSets / Tables - PROD --> TEST --> DEV Projects

Google Big Query Cloning of Datasets & Tables across GCS Projects. We searched the internet and could not find a simple cloning / ...