Search Results fnd_conc_global




Overview
Explore in AI Chat

Overview

The APPS.FND_CONC_GLOBAL package body is a core Oracle E-Business Suite utility that manages global (session-level) concurrent processing settings within the Concurrent Manager runtime environment. Its primary role is to isolate and expose the global variables that govern request behavior — such things as the number of output copies, hold and priority flags, print options, and the operating system instance number of the node executing a concurrent request. The package provides a controlled, programmatic interface for reading and writing these globals so that concurrent programs, the Concurrent Manager, and reporting logic can share consistent request state without directly manipulating low-level session variables.

The package body is owned by the APPS schema and is documented as VALID in the ETRM repository for both 12.1.1 and 12.2.2. Its API classification is listed as OTHER, reflecting its role as an internal support package rather than a business-facing public API.

Key Procedures and Functions

The package exposes fifteen documented procedures and functions that fall into three broad categories.

No parameter lists are documented in the ETRM metadata, so each routine is described here by purpose only.

Tables Accessed

The only documented table referenced by this package (through an APPS synonym) is V$INSTANCE. The package reads V$INSTANCE to determine the current database instance identity, which it uses to derive and populate the global operating-system instance number exposed by OPS_INST_NUM and related routines. No other base tables are recorded, consistent with the package's role as an in-memory global state holder rather than a persistent data manipulator.

Usage Notes

FND_CONC_GLOBAL is heavily integrated into the concurrent processing stack: the ETRM metadata records that it is referenced by 111 other database objects, while it does not itself reference any application-level database object other than V$INSTANCE. Internally it depends on FND_PROFILE, FND_MESSAGE, FND_LOG, and APP_EXCEPTION, which indicates it participates in profile lookups, message resolution, diagnostics logging, and standardized error raising.

In practice the package is invoked implicitly during concurrent request initialization and execution. The Concurrent Manager and related runtime code call its INITIALIZE, GET_REQ_GLOBALS, and SET_REQ_GLOBALS routines to prime and persist the global request state, while report and printing logic consult the option accessors (CONC_COPIES, PRINTER, CONC_PRINT_OUTPUT, and similar). Custom concurrent programs written against the EBS concurrent framework may also reference these routines to interrogate or set print and hold behavior. Because the metadata documents no formal parameter signatures, developers should treat the procedures as internal runtime hooks and verify current definitions against the deployed package before calling them directly.