Search Results gms_util_pc_fck




Overview
Explore in AI Chat

Overview

GMS_UTILITY is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as an "OTHER" API within the Grants Management (GMS) module. It provides shared utility logic that supports award identification and the Funds Checking (FCK) process for Grants Management transactions. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer, which aligns it with the standard Oracle EBS convention for public utility APIs invoked from multiple contexts. The header source indicates a 2012 revision (120.0.12020000.2), consistent with the 12.1.1 and 12.2.2 release lineages. Its principal responsibilities are twofold: returning the human-readable award number for a given internal award identifier, and orchestrating the interaction between GMS funds checking and General Ledger budgetary control packets.

Key Procedures and Functions

The package exposes four documented program units:

  • GET_AWARD_NUMBER — A function that accepts an award identifier and returns the corresponding award number as a VARCHAR2. This is the object most frequently referenced by developers searching for award number resolution, since it abstracts the join between the internal numeric award key and the user-facing award number.
  • GMS_UTIL_FCK — The primary funds checking driver, invoked with a set of identifiers and mode flags (set of books, packet, FC mode, override, partial, user and responsibility context, execute flag) and returning both a GMS return code and a GL return code. It coordinates the overall funds check for a packet and passes status back to the caller.
  • GMS_UTIL_PC_FCK — A variant of the funds check that operates on a packet control context and returns only a GMS return code. Its parameter profile closely mirrors GMS_UTIL_FCK but omits the paired GL return code, reflecting a narrower or secondary checking path.
  • GMS_UTIL_GL_RETURN_CODE — A helper that resolves the GL return code for a packet given the mode, an incoming GL return code, the GMS return code, and a partial reservation flag. It is typically invoked after the funds check primitives to interpret or normalize the GL-side outcome.

Tables Accessed

The package operates against budgetary control and award structures through APPS synonyms:

  • GL_BC_PACKETS — The General Ledger budgetary control packet table, used to read and update packet-level funds checking state.
  • GMS_BC_PACKETS — The Grants Management budgetary control packet table, holding the GMS-side packet definition that is processed during a funds check.
  • GMS_BC_PACKET_ARRIVAL_ORDER — Defines the order in which packets are processed, ensuring deterministic sequencing of funds checks across related packets.
  • DUAL — Used for simple single-row selection expressions, typically in the award number lookup utility.
  • DBMS_SQL — Oracle's dynamic SQL package, indicating that portions of the logic build and execute SQL dynamically at runtime.

Usage Notes

GMS_UTILITY is an internal utility rather than an end-user interface. GET_AWARD_NUMBER is commonly called from custom code, reports, and forms personalizations that need to translate an internal award id into its displayed award number without re-implementing the lookup. The funds checking procedures are invoked during transaction processing and concurrent funds check runs, where a calling program constructs the set of books, packet, and mode parameters and evaluates the returned GMS and GL return codes to determine whether a transaction is funded. Custom integrators should treat the return codes as authoritative status holders and must declare them as IN OUT NOCOPY variables, matching the documented signatures. Because the package uses AUTHID CURRENT_USER and DBMS_SQL, effective privileges and any dynamic SQL context are resolved at runtime; callers should ensure appropriate grants on the underlying GMS and GL tables. No other packages are documented as referencing GMS_UTILITY, so it is best regarded as a leaf-level utility available to forms, concurrent programs, and bespoke extensions rather than a shared dependency of the standard API stack.