Search Results gms_message

Overview

PA_AP_INTEGRATION is a PL/SQL package body owned by APPS that mediates the transfer of supplier, invoice, and cost data between Oracle Payables and Oracle Projects. Its principal business role is to keep Projects-side records consistent when Payables-side supplier data changes, and to supply Projects with the derived values it needs when generating or validating supplier invoices and expenditure items. The package is central to the supported "supplier merge" operation across the two modules and to the interface that creates project-related distributions from Payables documents.

The metadata notes that the object is referenced by eight other packages in the E-Business Suite, indicating it is an internal dependency rather than an end-user feature. The user search term "gms_message" aligns with the package's inclusion of Oracle Grants Management tables (GMS_AWARDS_ALL and GMS_AWARD_DISTRIBUTIONS), which the integration reads when project and award context must be resolved alongside supplier invoice activity.

Key Procedures and Functions

• UPD_PA_DETAILS_SUPPLIER_MERGE — Propagates a supplier merge from the old vendor to the new vendor across Projects tables. The documented excerpt shows it updating PA_IMPLEMENTATIONS_ALL and PA_EXPENDITURES_ALL, and applying the last-updated audit columns. A v2.0-style optional invoice scope (INVOICE_ID) restricts the update to expenditures tied to a specific AP invoice, using ORIG_EXP_TXN_REFERENCE1 as the link.
• ALLOW_SUPPLIER_MERGE — Determines whether a supplier merge is permissible for the Project Accounting context, providing the guard condition invoked by the merge process before UPD_PA_DETAILS_SUPPLIER_MERGE performs its updates.
• GET_ASSET_ADDITION_FLAG — Returns the flag indicating whether a project or expenditure qualifies as an asset addition, used to decide capitalization treatment.
• GET_PROJECT_TYPE — Returns the project type classification for a given project, used to drive downstream logic such as costing and billing behavior.
• GET_SI_COST_EXP_ITEM_DATE — Derives the supplier invoice cost expenditure item date, aligning the Projects expenditure item date with the Payables invoice activity.
• GET_SI_DEFAULT_EXP_ORG — Returns the default expenditure organization for supplier-invoice-generated expenditure items, based on project and organization setup.
• GET_PO_MATCH_SI_EXP_ITEM_DATE — Derives the expenditure item date for supplier invoices matched to purchase orders, using the PO match date rather than the invoice date.
• VALIDATE_EI_DATE — Validates a supplied expenditure item date against project, period, and purchase-order match constraints before the item is created.

Tables Accessed

The package reads and writes AP_INVOICES_ALL and AP_INVOICE_DISTRIBUTIONS_ALL, the Payables source of invoice and distribution data used for validation and for scoping supplier-merge updates. On the Projects side it touches PA_IMPLEMENTATIONS_ALL, PA_EXPENDITURES_ALL, PA_EXPENDITURE_ITEMS_ALL, PA_COST_DISTRIBUTION_LINES_ALL, PA_PROJECTS_ALL, PA_BUDGET_LINES, PA_BC_COMMITMENTS_ALL, PA_BC_PACKETS, and PA_CI_SUPPLIER_DETAILS, covering project definition, expenditure, cost distribution, budgeting, and supplier detail. PO_DISTRIBUTIONS_ALL provides purchase-order match context, while GMS_AWARDS_ALL and GMS_AWARD_DISTRIBUTIONS supply grants/award context for funded projects. HR_ALL_ORGANIZATION_UNITS_TL supplies organization-name lookups for expenditure organization defaults.

Usage Notes

PA_AP_INTEGRATION is normally invoked indirectly. The supplier merge path is reached from the Oracle Payables Supplier Merge process and the Oracle Projects supplier merge concurrent program, which first call ALLOW_SUPPLIER_MERGE and then UPD_PA_DETAILS_SUPPLIER_MERGE. The date and flag functions are consumed by the Payables-to-Projects interface that creates supplier invoice expenditure items, and by project costing and billing programs that need project type, asset addition, or organization defaults. Because these are internal APIs, direct calls should be limited to supported extension points; the eight dependent packages indicate that modifications here carry broad downstream risk. Run supplier merges during a period when Payables and Projects are reconciled, since the updates span both modules' tables.