Search Results vert_reject_txn

Overview

GMS_PA_API is a PL/SQL API package in the APPS schema that provides the programmatic bridge between Oracle Grants Management (GMS) and Oracle Projects (PA). Its central business function is to enforce award-level control over project transactions in Oracle E-Business Suite. When expenditure items are generated, adjusted, transferred, or interfaced in Oracle Projects, this package evaluates those transactions against the governing award and determines whether they are allowable, whether they must be split, and whether they should be rejected or adjusted. In effect, it is the mechanism that prevents grant funds from being applied to unallowable costs and that keeps Projects transactions synchronised with the award structure.

The package is classified as an API in the ETRM repository and holds VALID status in the APPS schema. It is a heavily depended-upon object within the Grants costing chain, and its procedures are consumed both by standard GMS packages and by Oracle Projects through the PA_GMS_API integration.

Key Procedures and Functions

The ETRM metadata documents 24 procedures and functions. The most significant are described below.

• GMS_SET_AWARD / GMS_SET_PROJECT_ID / VERT_GET_AWARD_ID — Resolve and attach the correct award and project context to the transaction being processed, forming the prerequisite step for all downstream validation.
• GMS_SPLIT / VERT_TRANSFER / VERT_ADJUST_ITEMS — Perform the distributive work on expenditure items, splitting or transferring amounts so that sponsored and non-sponsored portions are recorded against the correct award and distribution lines.
• VERT_ALLOW_ACTION / VERT_ALLOW_ADJUSTMENTS / SET_ADJUST_ACTION — Return the allowability decision for a proposed action. These functions gate whether a user or concurrent process may proceed with a transfer or an adjustment against a sponsored project.
• VERT_APP_VALIDATE / VERT_TRX_INTERFACE / VERT_REJECT_TXN — Validate incoming transaction interface rows, and reject those that fail award-based validation rules.
• VERT_PAAP_SI_ADJUSTMENTS / VERT_SI_ADJ / VERT_INSTALL — Handle adjustments related to supplier invoice (PAAP) processing and installation setup for the vertical.
• IS_SPONSORED_PROJECT / IS_AWARD_CLOSED — Boolean-style checks used throughout GMS and PA to determine whether a project is award-bearing and whether the associated award remains open for charging.
• OVERRIDE_RATE_REV_ID — Supports override of the rate revision identifier used in burden and cost calculations.
• CLIENT_GROUPING — Groups client-related data during award and expenditure processing.
• RETURN_ERROR — Standard error-raising utility that surfaces coded messages to the calling program.

Tables Accessed

GMS_PA_API reads and writes against a defined set of GMS and PA tables through APPS synonyms. GMS_AWARDS_ALL and GMS_AWARDS supply the award header and terms; GMS_ALLOWABLE_EXPENDITURES and GMS_AWARD_EXP_TYPE_ACT_COST carry the allowability rules applied by the VERT_* validation procedures. GMS_AWARD_DISTRIBUTIONS and GMS_BUDGET_VERSIONS define how award funds are distributed and budgeted. GMS_TRANSACTION_INTERFACE_ALL, GMS_BC_PACKETS and GMS_BC_PACKETS_S support the transaction interface and burden-cost packet processing. GMS_IMPLEMENTATIONS holds installation-level controls.

On the Projects side, the package references PA_EXPENDITURE_ITEMS_ALL and PA_EXPENDITURE_TYPES for the expenditure records being validated and adjusted, and PA_COMPILED_MULTIPLIERS for rate information. AP_INVOICE_DISTRIBUTIONS_ALL and AP_SELF_ASSESSED_TAX_DIST_ALL are accessed for supplier invoice and tax distribution handling.

Usage Notes

GMS_PA_API is not typically called directly by end users. It is invoked from GMS and PA concurrent programs, from the Grants expenditure and adjustment forms, and from the transaction interface workflow. The metadata shows it is referenced by GMS_AP_API, GMS_EXP_ADJUSTMENT_PKG, GMS_LD_PKG, GMS_PA_API2, GMS_PA_API3, GMS_PA_COSTING_PKG and PA_GMS_API, which confirms its role as a shared internal service. Custom extensions that generate or adjust project expenditures on sponsored projects should call these APIs rather than manipulating the underlying tables directly, so that allowability, splitting, and award-closure rules continue to be enforced. In 12.1.1 and 12.2.2 the package behaves consistently, but implementations should confirm the file version, since ETRM documentation reflects the current certified body.