Search Results gl_top

Overview

PSA_FUNDS_CHECKER_PKG is the core budgetary funds-checking engine within the Oracle E-Business Suite Public Sector / Grants (PSA) application. It evaluates whether sufficient funds and budget authority exist before an expenditure, encumbrance, or reservation is committed against a ledger. The package supports multiple operating modes, driven by the g_fcmode global: Funds Check (partial and full), Funds Reservation, Funds Adjustment, Force Pass, Unreservation, and Partial Reservation. It returns a packet-level return code (g_return_code) of Success, Advisory, Failure, Partial, Force Pass, or Fatal, allowing callers to act on the outcome. The package also integrates with Grants Management (GMS) and Project Accounting (PA) when those flags are enabled, and supports the USSGL and budgetary encumbrance options. In EBS 12.1.1 and 12.2.2 the body is shipped under the APPS schema, consistent with the 12.2 online patching model where APPS-owned PL/SQL is editioned.

Key Procedures and Functions

• GLXFCK — the primary funds check routine; evaluates a packet and produces the funds-check result.
• GLXFMA — funds adjustment processing, structurally similar to reservation but emitting adjustment-specific messages.
• GLXFPP — force-pass processing, used to bypass a check and record a force-pass outcome.
• GL_CONFIRM_OVERRIDE — records/confirms an override of a funds-check failure, enabling the caller to proceed under authority.
• GLSIBC — budgetary control interface/setup routine that initialises budgetary control context and options.
• GLSFBC — the budgetary control execution routine underpinning GLXFCK-style processing.
• BUDGETARY_CONTROL — the entry point that coordinates budgetary control logic across the packet lifecycle.
• GET_DEBUG — returns the diagnostic/debug information string assembled from the segment, token, and value arrays (SegNamArray, TokNameArray, TokValArray).
• BC_OPTIMIZER — housekeeping routine to optimise budgetary control data.
• BC_PURGE_HIST — purges historical budgetary control records to control data growth.
• POPULATE_GROUP_ID — populates the group identifier used to correlate a batch of packets.
• SYNC_XLA_ERRORS — synchronises Subledger Accounting (XLA) error information associated with the packets.

Note: the ETRM metadata lists GLXFPP, GL_CONFIRM_OVERRIDE and related entries among thirteen documented routines; GET_DEBUG, BC_OPTIMIZER, BC_PURGE_HIST, POPULATE_GROUP_ID and SYNC_XLA_ERRORS are utility/support routines. The gl_top search term relates to the transaction origin classification used when packets originate from General Ledger.

Tables Accessed

• GL_BC_PACKETS — the budgetary control packet being checked, reserved, adjusted, or unreserved; the central persistent table.
• PSA_XLA_AE_HEADERS_LOGS / PSA_XLA_AE_LINES_LOGS — staging logs of XLA accounting entry headers and lines produced during processing.
• PSA_XLA_DIST_LINKS_LOGS / PSA_XLA_EVENTS_LOGS / PSA_XLA_VALIDATION_LINES_LOGS — supporting XLA event, distribution-link and validation logs.
• XLA_AE_LINES_GT / XLA_VALIDATION_LINES_GT — global temporary tables used as transient working sets for accounting lines and validation lines.
• FND_APPLICATION, FND_CURRENCIES, FND_DESCRIPTIVE_FLEXS, FND_ID_FLEX_SEGMENTS — Flexfield and application metadata used to identify active accounting segments and their definitions.
• FND_ORACLE_USERID, FND_PRODUCT_INSTALLATIONS — user identity and product registration checks (including GMS/PA enablement).
• FND_PROFILE_OPTION_VALUES — profile option lookups that drive funds-check behaviour and options such as USSGL and budgetary encumbrance defaults.

Usage Notes

PSA_FUNDS_CHECKER_PKG is invoked indirectly rather than directly by end users. It is called from Funds Check and Funds Reservation concurrent programs, from the budgetary control forms flows, and from other PL/SQL packages (the metadata records it as referenced by fourteen packages). Typical invocation occurs during expenditure/commitment processing, when a packet is submitted for checking. Callers should rely on the returned return code rather than the internals, and developers integrating custom code should call the documented entry points (for example GLXFCK or BUDGETARY_CONTROL) rather than manipulating GL_BC_PACKETS directly. Debug output is available via GET_DEBUG, and periodic maintenance should schedule BC_PURGE_HIST and BC_OPTIMIZER to manage historical data. Because the body is editioned in 12.2, customisations must be applied through supported extension mechanisms rather than direct modification.