Search Results g_program

Overview

XLA_ENVIRONMENT_PKG is an Oracle E-Business Suite subledger accounting (XLA) infrastructure package owned by the APPS schema. It provides a central repository for runtime environment and session context information that other XLA components rely upon during subledger accounting processing. The package exposes a set of public package-level variables that capture the release identifier, Multi-Org (MApps) status, platform-specific character handling, WHO audit columns, and session tracing identifiers. It further provides a public procedure, REFRESH, that repopulates this shared context so that callers always operate against current runtime values.

The package is classified as OTHER within the ETRM (E-Business Suite Technical Reference Manual) metadata, reflecting its role as a foundational utility rather than a business-facing API. It is referenced by 123 other packages, which confirms its position as a widely consumed dependency across the subledger accounting module and adjacent components.

Key Procedures and Functions

The documented public interface consists of a single procedure:

• REFRESH — Re-establishes the package-level environment and session state held in the public global variables. Typical callers invoke REFRESH when the runtime context may have changed, such as at the start of processing, after a reconnection, or following a change in the active responsibility or session, so that the cached global values reflect the current environment.

The package also declares several public global variables that form part of its contract with callers. These include g_release_name (the release identifier), g_mapps_flag (Multi-Org installation indicator), g_chr_newline (platform-specific newline character), the WHO variables g_Login_Id, g_Prog_Appl_Id, g_Resp_Appl_Id, g_Prog_Id, g_Req_Id, and g_Usr_Id, and the session variables g_program, g_module, g_process_id, g_session_id, and g_session_name. The variable g_program, which is the term the user searched for, is a VARCHAR2(255) global holding the name of the currently executing program for the session. It is populated and maintained alongside the other session globals so that downstream XLA routines can record or report the executing program without repeatedly querying session metadata.

Tables Accessed

The documented data sources are accessed through APPS synonyms and Oracle fixed views:

• FND_DATA_GROUPS — queried to resolve data group and Multi-Org related configuration.
• FND_PRODUCT_GROUPS — queried to determine product group and installation-level information, including release details used to populate g_release_name.
• DBMS_PIPE — used for inter-session communication and signalling within the EBS runtime environment.
• V$MYSTAT — provides session-level statistics used during environment refresh.
• V$PROCESS — supplies operating system process information, supporting population of process-related globals.
• V$SESSION — supplies session identity, program, module, and related attributes, supporting population of g_program, g_module, g_session_id, and g_session_name.

Usage Notes

XLA_ENVIRONMENT_PKG is internal infrastructure and is not typically invoked directly by end users. It is called from XLA subledger accounting programs, concurrent programs, and other PL/SQL packages that need consistent access to environment and session context. Custom code that extends subledger accounting should reference the public globals (for example, g_program) when stamping or logging program and session information, rather than re-deriving these values independently. Because the globals are cached, any code that depends on them across a session lifetime should invoke REFRESH when context changes. Direct modification of the public variables by external code should be avoided, as this can desynchronize the shared environment state on which the many dependent XLA packages rely. The behaviour is consistent across Oracle EBS 12.1.1 and 12.2.2, with the header revision indicating the package has remained stable since its early release.