Search Results gms_ld_pkg




Overview
Explore in AI Chat

Overview

GMS_LD_PKG is a PL/SQL package in the APPS schema that supports Oracle Grants Management (GMS) encumbrance processing and award-related load/validation logic. It is classified as an OTHER API, meaning it is an internal utility package rather than a formally published public API, and it is intended primarily for use by other GMS packages and concurrent processing routines. The package operates against the Grants Management encumbrance data model, which links sponsored award distribution to encumbrance items and to Oracle Projects transaction interface records. It is referenced by GMS_ENC_IMPORT_PKG, indicating that its primary role is to validate and prepare data during the encumbrance import cycle, particularly around award dates, project/task references, and transaction interface staging.

Key Procedures and Functions

PRE_PROCESS — Performs preparatory processing on records before the main encumbrance import logic executes. This typically includes validating award, project, and task context, and staging or normalizing data in the transaction interface tables so that downstream import steps can consume clean input.

VALIDATE_DATES_YN — A date validation routine that returns a yes/no style result, used to confirm whether award or transaction dates (for example award start/end dates versus encumbrance item dates) fall within acceptable ranges for processing.

Tables Accessed

Usage Notes

GMS_LD_PKG is not typically invoked directly from an Oracle Forms user interface. It is called internally by GMS_ENC_IMPORT_PKG during the encumbrance import concurrent program, which is the standard vehicle for loading grants encumbrance transactions into Oracle EBS. Customers extending Grants Management may call the package from custom PL/SQL or concurrent programs, but because it is an OTHER-classified object, its signature is not guaranteed across patch levels and direct calls should be avoided unless no documented public API exists. Its validity in both 12.1.1 and 12.2.2 reflects the object's stability across the two release streams.