Search Results fundscheck_supplier_cost

Overview

GMS_PA_COSTING_PKG is an Oracle Grants Management (GMS) package owned by the APPS schema that orchestrates the costing and interface of award-related transactions into Oracle Payables (AP) and Oracle Project Accounting (PA). Its central business function is to bridge Grants award data with the subledger costing engines, ensuring that supplier invoices and transaction interface records are validated, tied back to awards, and posted correctly. The package sits at the intersection of GMS_BC_PACKETS (the Grants business-class packets used to stage accounting events), PA_TRANSACTION_INTERFACE (the staging table for project expenditures), and the AP invoice tables. It supports the funding-check and tie-back logic that confirms costs charged against an award are legitimate and fully accounted for before they are imported as project costs. In both EBS 12.1.1 and 12.2.2, the package is registered as VALID in the APPS schema, and its dependency footprint confirms that it is a long-standing component of the Grants-to-Projects costing flow rather than a version-specific addition.

Key Procedures and Functions

The documented API surface contains six procedures and functions:

• FUNDSCHECK_CDL — Performs funding validation in the context of cost distribution lines (CDL), verifying that the amounts being costed on an award have sufficient available funding before the transaction proceeds.
• FUNDSCHECK_TIEBACK — Executes funding verification during tie-back processing, reconciling the cost transaction being processed against the original award funding position.
• NET_ZERO_ADLS — Handles award distribution lines (ADLs) whose net value is zero, processing or suppressing them so that no unnecessary accounting is generated.
• FUNDSCHECK_SUPPLIER_COST — Applies funding-check logic specifically to supplier costs, i.e. costs originating from AP invoices, before they are converted into project expenditures.
• TIEBACK_INTERFACE — Drives the tie-back routine that links an incoming interface transaction back to its originating award, invoice, or packet, populating the relevant identifiers to complete the costing chain.
• GRANTS_IMPLEMENTED — A utility check that determines whether Oracle Grants Management is implemented or active in the current operating unit, allowing the package to short-circuit Grants-specific logic when Grants is not in use.

No parameter signatures are published in the dependency metadata; callers should treat these as internal Grants APIs and not assume a stable public interface across releases.

Tables Accessed

The package reads and writes across three functional domains. In Oracle Payables it references AP_INVOICES, AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS, AP_INVOICE_DISTRIBUTIONS_ALL, AP_INVOICE_PAYMENTS, AP_PAYMENT_HIST_DISTS, AP_SELF_ASSESSED_TAX_DIST, and AP_SELF_ASSESSED_TAX_DIST_ALL — the sources of supplier cost data that require funding validation and tie-back. In Oracle Projects it uses PA_EXPENDITURE_TYPES, PA_TRANSACTION_INTERFACE, and PA_TRANSACTION_INTERFACE_ALL to derive expenditure attributes and to stage or interrogate transactions awaiting import. In Grants it works with GMS_AWARD_DISTRIBUTIONS, GMS_BC_PACKETS, GL_BC_PACKETS_S, and GMS_ADLS_AWARD_SET_ID_S, which supply award distribution, accounting packet, and award set identifiers essential to the tie-back and net-zero logic. All access is made through APPS synonyms, so the package must be run with APPS-level privileges.

Usage Notes

GMS_PA_COSTING_PKG is an internal dependency of the Grants costing infrastructure rather than a standalone API. The ETRM metadata shows it is referenced by PA_TRANSACTIONS, PA_TRX_IMPORT, and by GMS_PA_COSTING_PKG itself, and it in turn references four other packages. In practice it is invoked indirectly when supplier invoices and staged interface transactions are costed against awards — typically through the Grants concurrent programs that import project transactions and through the transaction import and costing paths in Oracle Projects. Because Grants funding checks are conditional on implementation status, the GRANTS_IMPLEMENTED function governs whether the remaining procedures execute. Customizations should avoid calling these procedures directly; instead, extend the supported import and costing flows so that upgrades across 12.1.1 and 12.2.2 do not break dependent logic.