FND_GLOBAL and FND_PROFILE: Import List of System Global values

By | December 24, 2014

We can find values of System global values using FND_PROFILE and FND_GLOBAL

FND_PROFILE

To manipulate values stored in client and server user profile caches.Any changes you make to profile option values using these routines affect only the run-time environment. The effect of these settings end when the program ends, because the database session (which holds the profile cache) is terminated.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
fnd_profile.VALUE('PROFILEOPTION')
fnd_profile.VALUE('MFG_ORGANIZATION_ID')
fnd_profile.VALUE('ORG_ID')
fnd_profile.VALUE('LOGIN_ID')
fnd_profile.VALUE('USER_ID')
fnd_profile.VALUE('USERNAME')
fnd_profile.VALUE('CONCURRENT_REQUEST_ID')
fnd_profile.VALUE('GL_SET_OF_BKS_ID')
fnd_profile.VALUE('SO_ORGANIZATION_ID')
fnd_profile.VALUE('APPL_SHRT_NAME')
fnd_profile.VALUE('RESP_NAME')
fnd_profile.VALUE('RESP_ID')
fnd_profile.VALUE('PER_BUSINESS_GROUP_ID')
fnd_profile.VALUE('GL_SET_OF_BKS_ID')
fnd_profile.VALUE('CURRENT_ORG_CONTEXT')

FND_GLOBAL

The server-side package FND_GLOBAL returns the values of system globals, such as the login/signon or “session” type of values. You should not use FND_GLOBAL routines in your forms (that is on the client side). On the client side, most of the procedures in the FND_GLOBAL package are replaced by a user profile option with the same (or a similar) name. You should use FND_PROFILE routines in your forms instead.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
fnd_global.USER_ID 
fnd_global.USER_NAME 
fnd_global.RESP_ID 
fnd_global.RESP_NAME 
fnd_global.APPLICATION_NAME 
fnd_global.APPLICATION_SHORT_NAME 
fnd_global.RESP_APPL_ID 
fnd_global.BASE_LANGUAGE 
fnd_global.CONC_LOGIN_ID 
fnd_global.CONC_PRIORITY_REQUEST 
fnd_global.CONC_PROCESS_ID 
fnd_global.CONC_PROGRAM_ID 
fnd_global.CONC_QUEUE_ID 
fnd_global.CONC_REQUEST_ID 
fnd_global.CURRENT_LANGUAGE 
fnd_global.CUSTOMER_ID 
fnd_global.EMPLOYEE_ID 
fnd_global.FORM_APPL_ID 
fnd_global.FORM_ID 
fnd_global.GET_SESSION_CONTEXT 
fnd_global.LANGUAGE_COUNT 
fnd_global.LOGIN_ID 
fnd_global.NEWLINE 
fnd_global.NLS_DATE_FORMAT 
fnd_global.NLS_DATE_LANGUAGE 
fnd_global.NLS_LANGUAGE 
fnd_global.NLS_NUMERIC_CHARACTERS 
fnd_global.NLS_SORT 
fnd_global.NLS_TERRITORY 
fnd_global.ORG_ID 
fnd_global.ORG_NAME 
fnd_global.PARTY_ID 
fnd_global.PER_BUSINESS_GROUP_ID 
fnd_global.PER_SECURITY_PROFILE_ID 
fnd_global.PROG_APPL_ID 
fnd_global.QUEUE_APPL_ID 
fnd_global.RT_TEST_ID 
fnd_global.SECURITY_GROUP_ID 
fnd_global.SERVER_ID 
fnd_global.SESSION_ID 
fnd_global.SUPPLIER_ID 
fnd_global.TAB

Where do we use FND_GLOBAL and FND_PROFILE?

We can use them any where in PL/SQL to get values dynamically as per the session. In Forms we can use only FND_GLOBAL not FND_PROFILE.

Initializing the Environment

   l_user_id       := fnd_global.user_id;
   l_resp_id       := fnd_global.resp_id;  
   l_resp_appl_id  := fnd_global.resp_appl_id;   
 
   fnd_global.APPS_INITIALIZE(l_user_id,l_resp_id, l_resp_appl_id);

Also read, What is the difference between FND_GLOBAL and FND_PROFILE??

WOW! Did you like this post? We'll send more interesting posts like FND_GLOBAL and FND_PROFILE: Import List of System Global values to you!
Enter your Email Address:
  • Pavan

    Hello Shailendar,

    Thanks for this post.

    Can you please clarify the above sentence once.?

    In the FND_GLOBAL description, it was mentioned that
    “You should not use FND_GLOBAL routines in your forms (that is on the client side). On the client side, most of the procedures in the FND_GLOBAL package are replaced by a user profile option with the same (or a similar) name. You should use FND_PROFILE routines in your forms instead”

    Where as in the
    Where do we use FND_GLOBAL and FND_PROFILE?, description its mentioned that
    “We can use them any where in PL/SQL to get values dynamically as per the session. In Forms we can use only FND_GLOBAL not FND_PROFILE.”

    • Hello Pavan,

      Yes! we can use only FND_GLOBAL in Forms because FND_GLOBAL access its values in server side where as FND_PROFILE access its values in client side profile cache. Even if it is same login, different profile caches are maintained for each form. Changes made to profile caches(means any profile option) from one form will not reflect in another form, that is the reason we are asked to logout and re-login for the profile option values to get reflected.

      Read this article for detailed explanation: – http://oracleappsdna.com/question/what-is-the-difference-between-fnd_global-and-fnd_profile/

      Thanks,
      Shailender