Search Results verify_create_adls

Overview

GMS_AP_API2 is a public PL/SQL package in the APPS schema that supports Oracle Grants Management (GMS) integration with Oracle Payables. Its principal business function is the creation and validation of award distribution lines (ADLs) for sponsored projects when Payables invoice distributions are generated. The package is the bridge that ensures invoice activity originating in Payables — including activity produced by the recurring invoice feature — is reflected correctly against the relevant award in Grants Management.

The package is classified as a non-interface (OTHER) API. It is invoked internally by Payables processing rather than being called directly by end users. Specifically, it interfaces with the AP recurring invoice feature and the invoice approval process, identifying newly created invoice distribution lines and deriving the corresponding award distribution lines for sponsored projects. A second role is validation: it verifies award-related information on manually entered invoice distributions whose award attributes were copied from a distribution set.

Key Procedures and Functions

• VERIFY_CREATE_ADLS — A public procedure that creates award distribution lines using bulk processing. It is designed to be called after Payables has created recurring invoices, so that distribution lines associated with an award are detected and mirrored as award distribution lines in Grants Management. The procedure accepts the invoice identifier and a calling sequence string used for debugging and traceability. Documented calling APIs include AP_RECURRING_INVOICES_PKG.ap_create_recurring_invoices and ap_approval_pkg.
• VALIDATE_TRANSACTION — A public function that validates award-related information on invoice distributions. It is called from AP_INVOICE_DISTRIBUTIONS_PKG.insert_from_dist_set, the exact entry point associated with the search term insert_from_dist_set. The routine determines the award referenced by the distribution and delegates to the standard Grants Management validation routine. It exists to address defect 2755183, in which invoice entry did not validate the expenditure item date against an award copied from a distribution set. Parameters include project, task, award, expenditure type, expenditure item date, calling sequence, and the message application identifier.

Tables Accessed

The package reads from and writes to the following documented tables, referenced through APPS synonyms:

• AP_INVOICES_ALL and AP_INVOICE_DISTRIBUTIONS_ALL — the Payables invoice and distribution entities from which newly created distribution lines are identified.
• AP_SELF_ASSESSED_TAX_DIST_ALL — self-assessed tax distribution data considered during processing.
• GMS_AWARD_DISTRIBUTIONS — the award distribution lines created by VERIFY_CREATE_ADLS.
• GMS_INSTALLMENTS — award installment information used in validating and deriving award data.
• GMS_PROJECT_TYPES_ALL — project type definitions used to determine sponsored-project eligibility.
• GMS_SUMMARY_PROJECT_FUNDINGS — award funding summaries consulted during validation.
• PA_PROJECTS_ALL — project definitions for the project and task referenced on the distribution.
• PLITBLM — the standard EBS message/log table used to return validation messages.

Usage Notes

GMS_AP_API2 is not invoked from a form or concurrent program directly. It is called programmatically from within the Payables code base. VERIFY_CREATE_ADLS executes as part of recurring invoice creation and approval, so award distribution lines are generated automatically whenever qualifying invoice distributions are produced. VALIDATE_TRANSACTION executes during invoice entry, specifically from the AP_INVOICE_DISTRIBUTIONS_PKG.insert_from_dist_set path, validating the award, project, task, expenditure type, and expenditure item date combination before the distribution is accepted.

Customizations and extensions that bypass these standard Payables routines — for example, direct inserts into AP_INVOICE_DISTRIBUTIONS_ALL — will not trigger the award validation or ADL creation logic, and may result in missing award distribution lines or unvalidated expenditure item dates. Because the package is referenced by one other package and is itself dependent on AP and GMS tables, implementations should treat it as internal infrastructure rather than as a supported public integration point.