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.
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.
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??
MOAC – Oracle Apps ORG_ID, Multi Org Concept