Results for “application_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_GLOBAL is the foundational PL/SQL package body in Oracle E-Business Suite that maintains and exposes the runtime session context for every connected user, concurrent program, and Forms session. Its principal business function is to record, cache, and serve the set of global variables that identify who is running, under which responsibility, application, and organization, so that security rules, profile option values, and multi-org (MOAC) filtering behave correctly throughout a session. The body maintains an internal context hash (z_context) together with parallel name and value arrays, a backup context used by restore operations, an initialization hash populated from caller-supplied name/value pairs, and a separate set of flags (z_syscontext) controlling which entries are propagated into the DBMS_SESSION application context via SYS_CONTEXT. It further tracks whether profile initialization has completed through the z_allow_profile_puts guard, whether security groups are enabled, and whether the security context or site context has changed. References to V$NLS_PARAMETERS and V$SESSION support language, territory, and session-identity resolution required by the set_nls and related NLS handling logic that users frequently search for. With over 11,000 dependent packages, FND_GLOBAL is among the most widely referenced objects in the EBS data dictionary.

Key Procedures and Functions

The package exposes sixty-one documented routines. The numeric and identity accessors return the current session's USER_ID, RESP_ID, RESP_APPL_ID, and SECURITY_GROUP_ID. Descriptive accessors return USER_NAME, RESP_NAME, APPLICATION_NAME, and APPLICATION_SHORT_NAME. Concurrent processing context is provided by LOGIN_ID, CONC_LOGIN_ID, PROG_APPL_ID, CONC_PROGRAM_ID, CONC_REQUEST_ID, and CONC_PRIORITY_REQUEST. Multi-organization context is exposed through PER_BUSINESS_GROUP_ID and PER_SECURITY_PROFILE_ID. LANGUAGE_COUNT reports the number of installed languages. Formatting helpers LOCAL_CHR, NEWLINE, and TAB supply platform-appropriate character sequences for dynamically built SQL and output. These routines are the canonical way application code discovers session identity without querying FND tables directly.

Tables Accessed

The body reads FND_USER for identity data, FND_APPLICATION for application names and short names, and FND_LANGUAGES for language and NLS information. Profile option behavior depends on FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES, consistent with the profile reset flags maintained internally. FND_LOOKUP_TYPES supports lookup-driven context attributes. V$NLS_PARAMETERS and V$SESSION supply database-level NLS and session facts, while ALL_TAB_COLUMNS supports metadata verification. DBMS_APPLICATION_INFO, DBMS_OUTPUT, DBMS_SESSION, DBMS_SQL, DBMS_UTILITY, and PLITBLM are invoked for context registration, output, dynamic SQL, and internal utility work.

Usage Notes

FND_GLOBAL is invoked implicitly by the EBS framework at login, when a responsibility is selected, and during concurrent request startup, and explicitly by forms, concurrent programs, and custom PL/SQL that needs session identity or NLS settings. Custom code should call the accessor functions rather than querying context tables, because the package caches values and synchronizes them with the SYS_CONTEXT application context used by row-level security. Because profile values are not flushed until initialization completes, code executed early in an initialization sequence should account for the z_allow_profile_puts gating.