Hello,
Last friday, my colegues came with a problem. They got a new Noetix build 6.0 but when they try to install Global Views, only Inventory Global views are getting installed. They were trying to install 6.0 in an existing Noetix_sys, where 5.7 version views are installed. We cannot upgrade to 6.0. It is totally a new platform, so we created a new schema but still only Inventory Global views got installed. When we checked the datfiles.ini, we found out that only Inventory global views were enabled (in my previous post, i have mentioned how to validate, what we have purchased)
Define dat_global_modules = 'INV'
What if you dont have access to datfiles.ini? This information is also stored in a table in Noetix_Sys schema.
Select application_label, global_instance_enabled from n_application_owner_templates where base_application = 'Y'
If the application has global_instance_enabled as 'Y' then atleast your noetix package has global views.
Showing posts with label variable. Show all posts
Showing posts with label variable. Show all posts
Sunday, January 30, 2011
Sunday, December 19, 2010
Configure Language settings of choice for NoetixViews to return data in OBIEE.
Oracle EBS multi-lingual capability for the data stored, by storing the translations in special _TL tables. For example, Part description in multiple language is stored in MTL_SYSTEM_ITEMS_B_TL one row for each translation. Noetix views invlude these tables in there definition to provide multi-lingual translations for the reporting. All noetix views (where translation tables are used), use "language" environment variable to identify the language in which the data is requested. When querying through OBIEE, you can choose the language in which noetix views should return data. Under "My Accounts" in OBIEE, users have capability to select there locale language and this language value is stores in a predefined OBIEE session variable VALUEOF(NQ_SESSION.WEBLANGUAGE). Following are the changed need to be done, to map obiee session value to database language. So that Noetix views return the data in the appropriate language. Following are the steps to be performed
a. Open the RPD of your choice.
b. In the physical layer, open the connection pool properties for the noetix views
c. In the Execute Before Query Tab, place the following code
Declare
lang_name = varchar2(30);
BEGIN
Select DECODE('VALUEOF(NQ_SESSION.WEBLANGUAGE)','no','NORWEGIAN','es','SPANISH','ENGLISH') INTO LANG_NAME FROM DUAL;
EXECUTE IMMEDIATE 'alter session set NLS_LANGUAGE = ' lang_name;
END;
d. Save the rpd.
Now when the user changes its locale to Spain, the weblanguage session variable will be populated with es code and an alter session command will be executed before each query execution. This way, correct language filter will be applied to the noetix views and the data will be displayed as per the user's preffered language.
a. Open the RPD of your choice.
b. In the physical layer, open the connection pool properties for the noetix views
c. In the Execute Before Query Tab, place the following code
Declare
lang_name = varchar2(30);
BEGIN
Select DECODE('VALUEOF(NQ_SESSION.WEBLANGUAGE)','no','NORWEGIAN','es','SPANISH','ENGLISH') INTO LANG_NAME FROM DUAL;
EXECUTE IMMEDIATE 'alter session set NLS_LANGUAGE = ' lang_name;
END;
d. Save the rpd.
Now when the user changes its locale to Spain, the weblanguage session variable will be populated with es code and an alter session command will be executed before each query execution. This way, correct language filter will be applied to the noetix views and the data will be displayed as per the user's preffered language.
Subscribe to:
Posts (Atom)