FND_PROFILE.VALUE('ORG_ID') returns -1 When Changing Responsibility And Organization Context (Doc ID 1235274.1)

Last updated on JANUARY 19, 2017

Applies to:

Oracle Application Object Library - Version 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
Checked for relevance on 19-Jan-2017

Symptoms

In E-Business suite 11i or R12, a Responsibility context change initiates an Organization context change depending on the value of the profile 'MO: Operating Unit'. Once a Responsibility context change occurs in alternate times, i.e.

- 1st resp context sets org context correctly
- 2nd resp context resets org context incorrectly
- 3rd resp context sets org context correctly
- 4th resp context resets org context incorrectly

the organization context is reset to -1.

The organization context should always be set to the proper value given a valid responsibility context change that is associated to a valid operating unit.

Steps to Reproduce:
1. Set valid profile values for MO: Operating Unit for the System Administrator Responsibility and Application Developer Responsibility.
2. Execute the following query:
set serverout on
begin
fnd_global.apps_initialize(0,20420,1);
dbms_output.PUT_LINE (FND_PROFILE.VALUE('FND_INIT_SQL'));
dbms_output.PUT_LINE (FND_PROFILE.VALUE('ORG_ID'));
dbms_output.PUT_LINE (FND_GLOBAL.ORG_ID);
fnd_global.apps_initialize(0,20419,0);
dbms_output.PUT_LINE (FND_PROFILE.VALUE('ORG_ID'));
dbms_output.PUT_LINE (FND_GLOBAL.ORG_ID);
end;

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms