Search Results is_award_closed

Overview

GMS_PA_API2 is a lightweight Oracle E-Business Suite PL/SQL package body owned by the APPS schema that serves as a Grants Management System (GMS) integration shim for Oracle Projects (PA). Its principal business purpose is to provide Grants-aware wrappers around Projects APIs and to expose Grants enablement status to other Projects components, most notably views and packages that must behave differently when Oracle Grants Accounting is installed and enabled. Rather than re-implementing business logic, GMS_PA_API2 delegates to sister packages such as GMS_PA_API and to the installation-status utility GMS_INSTALL. The header comment identifies the file as $Header: gmspax2b.pls 120.2 2007/02/06, indicating a mature, low-churn artifact within the Grants product family. Because the package is classified as OTHER in the ETRM metadata and contains only two documented program units, it functions as a thin, defensive façade intended to isolate callers in Oracle Projects from direct dependencies on Grants-specific code.

Key Procedures and Functions

• IS_AWARD_CLOSED — A function that determines whether an award associated with a given context is closed. It exists to let Projects and Grants-aware callers short-circuit processing (for example, blocking new expenditures or burdens) when the funding award is no longer open. Per the source header, the function first checks gms_install.enabled; if Grants is not installed and enabled, it returns a default value of 'N' rather than raising an error or querying Grants tables. When Grants is enabled, it delegates to gms_pa_api.is_award_closed, forwarding its inputs unchanged. The default return value of 'N' is a deliberate safe fallback, ensuring non-Grants installations are unaffected. The embedded reference to Bug 5726575 indicates the signature was extended, adding a document-type discriminator with a default of 'EXP' (expenditure), allowing the same function to be reused across expenditure and other document contexts.
• IS_GRANTS_ENABLED — A function returning a single-character status flag: 'Y' when gms_install.enabled evaluates true, and 'N' otherwise. Introduced under Bug 2733355, its stated purpose is to support the definition of the pa_cdl_burden_detail_v view, where the presence or absence of Grants changes the required query shape. By centralizing this check in a packaged function, Oracle avoids duplicating installation logic across view definitions and callers.

Tables Accessed

No tables are referenced directly through APPS synonyms in the documented metadata. All data access is indirect: gms_pa_api.is_award_closed performs the actual award and task lookups on behalf of this wrapper, and gms_install.enabled supplies the installation flag. This absence of direct SQL is consistent with the package's role as a delegation layer and reduces the risk of invalidation when underlying Grants tables change.

Usage Notes

GMS_PA_API2 is typically invoked indirectly rather than from user-facing forms. Its documented consumers are other PL/SQL packages—three packages are noted as referencing it—and the pa_cdl_burden_detail_v view, which relies on IS_GRANTS_ENABLED at query-parse time. Custom code that must behave conditionally on Grants availability, or that needs to test award closure before processing expenditures, should call these wrappers rather than querying gms_install or Grants tables directly, thereby preserving the supported delegation path. Because IS_AWARD_CLOSED defaults to 'N', callers in non-Grants environments receive a consistent, non-exceptional answer, and the same call site remains valid across 12.1.1 and 12.2.2 regardless of whether Grants Accounting is licensed or enabled.