FND_GLOBAL: WHO Column Maintenance and Database Initialization
This section describes Global APIs you can use in your server-side PL/SQL procedures. The server-side package FND_GLOBAL returns the values of system globals, such as the login/signon or "session" type of values. You need to set Who columns for inserts and updates from stored procedures. Although you can use the FND_GLOBAL package for various purposes, setting Who columns is the package's primary use.
You should not use FND_GLOBAL routines in your forms (that is on the client side), as FND_GLOBAL routines are stored procedures in the database and would cause extra roundtrips to the database. 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.
See: Tracking Data Changes with record History (WHO)
FND_PROFILE: User Profile APIs
FND_GLOBAL.USER_ID (Server)
| Summary
| function FND_GLOBAL.USER_ID
return number;
|
| Description
| Returns the user ID.
|
FND_GLOBAL.APPS_INITIALIZE (Server)
| Summary
| procedure APPS_INITIALIZE(user_id in number,
resp_id in number,
resp_appl_id in number);
|
| Description
| This procedure sets up global variables and profile values in a database session. Call this procedure to initialize the global security context for a database session. You can use it for routines such as Java, PL/SQL, or other programs that are not integrated with either the Oracle E-Business Suite concurrent processing facility or Oracle Forms (both of which already do a similar initialization for a database session). The typical use for this routine would be as part of the logic for launching a separate non-Forms session (such as a Java program) from an established Oracle E-Business Suite form session. You can also use this procedure to set up a database session for manually testing application code using SQL*Plus. This routine should only be used when the session must be established outside of a normal form or concurrent program connection You can obtain valid values to use with this procedure by using profile option routines to retrieve these values in an existing Oracle E-Business Suite form session. For manual testing purposes, you can use Examine during an Oracle E-Business Suite form session to retrieve the profile option values.
|
Arguments (input)
| USER_ID
| The USER_ID number
|
| RESP_ID
| The ID number of the responsibility
|
| RESP_APPL_ID
| The ID number of the application to which the responsibility belongs
|
Example fnd_global.APPS_INITIALIZE (1010, 20417, 201);
FND_GLOBAL.LOGIN_ID (Server)
| Summary
| function FND_GLOBAL.LOGIN_ID
return number;
|
| Description
| Returns the login ID (unique per signon).
|
FND_GLOBAL.CONC_LOGIN_ID (Server)
| Summary
| function FND_GLOBAL.CONC_LOGIN_ID
return number;
|
| Description
| Returns the concurrent program login ID.
|
FND_GLOBAL.PROG_APPL_ID (Server)
| Summary
| function FND_GLOBAL.PROG_APPL_ID
return number;
|
| Description
| Returns the concurrent program application ID.
|
FND_GLOBAL.CONC_PROGRAM_ID (Server)
| Summary
| function FND_GLOBAL.CONC_PROGRAM_ID
return number;
|
| Description
| Returns the concurrent program ID.
|
FND_GLOBAL.CONC_REQUEST_ID (Server)
| Summary
| function FND_GLOBAL.CONC_REQUEST_ID
return number;
|
| Description
| Returns the concurrent request ID.
|