Search Results is_sponsored_project

Overview

GMS_INSTALL is an installation and enablement utility package in the Oracle Grants Management (GMS) module of Oracle E-Business Suite. Its primary responsibility is to determine whether Grants Management has been implemented and enabled for a given operating unit or organization, and to expose that state to the rest of the GMS application stack. Because Grants Management is an optional module that can be enabled selectively across organizations, the application requires a reliable, centrally maintained mechanism to answer the question "is Grants Management active here?" GMS_INSTALL provides that mechanism through a small set of Boolean functions and supporting procedures.

The package body is classified as OTHER in the ETRM metadata for release 12.2.2, indicating that it is an internal utility rather than a public API. It implements multi-organization access control (MOAC) awareness, allowing enablement to be evaluated either against the currently selected organization or against an explicitly supplied organization identifier. Its source header carries a revision date of 2006, reflecting its long-standing stability within the GMS codebase.

Key Procedures and Functions

The package exposes eight documented program units. The central function, ENABLED, returns a Boolean indicating whether Grants Management is active. The no-argument form resolves the current organization through PA_MOAC_UTILS.get_current_org_id and delegates to the overloaded form, which accepts an explicit organization identifier. When that identifier is null, the function tests for the existence of any enabled implementation row; otherwise it tests for an enabled row specific to the supplied organization. A NO_DATA_FOUND exception handler causes the function to return FALSE, which makes it safe to call in conditional logic.

• ENABLED — Determines whether Grants Management is enabled, using the current MOAC organization or a supplied organization identifier.
• FAB_ENABLED — Evaluates enablement in the context of the FAB (Federal Advisory Board) installation, distinguishing that configuration from other GMS deployments.
• SITE_ENABLED — Reports whether Grants Management is enabled at the site level, independent of a specific operating unit.
• IS_SPONSORED_PROJECT — The function most relevant to the user's search; it identifies whether a given project is a sponsored project. This classification drives GMS-specific processing such as award linkage, sponsored reporting, and grant-related validation.
• SET_ORG_ARRAY — Populates a PL/SQL table (t_org_id) by bulk collecting organization identifiers from GMS_IMPLEMENTATIONS, building an in-memory list of organizations where Grants Management is implemented.
• GMS_ENABLED_MOAC — Provides MOAC-aware enablement checking, integrating with the current organization context established by the EBS multi-org framework.

Tables Accessed

GMS_INSTALL reads from a compact set of tables, accessed through APPS synonyms.

• GMS_IMPLEMENTATIONS and GMS_IMPLEMENTATIONS_ALL — The authoritative source for enablement status. Queries filter on the ENABLED flag and, where applicable, on ORG_ID, forming the basis of the ENABLED functions and the SET_ORG_ARRAY bulk collection.
• PA_PROJECTS_ALL — Consulted to resolve project information, supporting the IS_SPONSORED_PROJECT determination.
• PA_PROJECT_TYPES_ALL — Used in conjunction with PA_PROJECTS_ALL to classify projects by type, distinguishing sponsored projects from capital or other project classifications.
• DUAL — Used as the driver for the existence-check queries in the ENABLED functions.
• PLITBLM — The PL/SQL table type definition underlying the t_org_id collection populated by SET_ORG_ARRAY.

Usage Notes

GMS_INSTALL is invoked throughout the GMS codebase as a gating check. It is referenced by 26 other packages, and the source comments note that SET_ORG_ARRAY is called from GMS.pld and from gms.style and gms.event for Payables and Purchasing integrations. In practice, this package is called from Grants Management forms, from concurrent programs that must confirm module enablement before processing sponsored data, and from custom extensions that need a supported way to test whether Grants Management is active for an organization. Because it is not a public API, custom code should prefer existing packaged entry points over direct modification, and any caller must account for the Boolean return convention and the possibility that IS_SPONSORED_PROJECT classifies a project as non-sponsored.