Search Results pa_integration




Overview
Explore in AI Chat

Overview

PA_INTEGRATION is an Oracle Projects (PA) package body owned by the APPS schema that supports the integration between Oracle Projects and Oracle Payables, with additional touchpoints to the General Ledger period model. Its primary business purpose is to resolve and validate the accounting period context in which project cost distribution and expenditure activity is recognized, and to reconcile that context with related Payables invoice data. Because project expenditures are eventually interfaced into Payables, Suppliers, and the General Ledger, the package exists to ensure that the period attributes recorded on Projects cost transactions remain consistent with the open and active periods defined in the financials applications. Documented package metadata classifies it as an OTHER API, indicating it is an internal utility package rather than a public, externally documented interface. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2, and it is referenced by four other packages but references no other database object externally on the Projects side beyond its own body.

Key Procedures and Functions

The ETRM metadata documents ten procedures and functions, all oriented toward period derivation and Payables validation:

  • GET_PERIOD_NAME — Returns the period name applicable to a given transaction or date context, using the Projects period calendar.
  • GET_GL_PERIOD_NAME — Returns the corresponding General Ledger period name, drawing on the GL period and period-status definitions.
  • GET_PERIOD_INFORMATION — Retrieves consolidated period attributes, including the Projects and GL period pair used for validation.
  • CHECK_AP_INVOICES — Verifies the presence or status of related Payables invoices for the project expenditure context.
  • INIT_AP_INVOICES — Initializes the Payables invoice data set used by the subsequent check and status calls.
  • AP_INVOICE_STATUS — Determines the status of the associated Payables invoice record.
  • REFRESH_PA_CACHE — Clears and reloads cached Projects data used by the package, such as implementation and period information.
  • GET_RAW_CDL_PA_DATE — Derives the Projects accounting date for raw cost distribution lines.
  • GET_RAW_CDL_RECVR_PA_DATE — Derives the Projects accounting date for raw cost distribution lines originating from receipt-based transactions.
  • GET_BURDEN_CDL_PA_DATE — Derives the Projects accounting date for burdened cost distribution lines.

Tables Accessed

The package reads and writes the following tables via APPS synonyms: PA_COST_DISTRIBUTION_LINES_ALL and PA_COST_DISTRIBUTION_LINES (cost distribution lines whose projects accounting dates are derived); PA_EXPENDITURE_ITEMS_ALL and PA_EXPENDITURE_ITEMS (expenditure records validated against period information); PA_IMPLEMENTATIONS_ALL (implementation and operating configuration used to drive caching and period behavior); AP_INVOICES_ALL (Payables invoices checked for existence and status); GL_PERIODS and GL_PERIOD_STATUSES (GL period definitions and their open/closed status); and PA_PERIODS and PA_PERIODS_ALL (Projects period calendar definitions). It also depends on shared utilities FND_API, FND_PROFILE, PA_DEBUG, PA_PERIOD_PROCESS_PKG, and PA_UTILS2.

Usage Notes

PA_INTEGRATION is invoked internally by the Projects cost processing stack rather than being called directly by end users. It is typically executed during cost distribution and expenditure processing, and its period-lookup routines are used to determine the correct PA and GL accounting period for raw, receipt-generated, and burdened cost distribution lines. The Payables-related procedures are invoked when the application must confirm that a corresponding AP invoice exists and is in an appropriate status before integration completes. Because the package is referenced by four other packages, customizations should not call it as a supported public API; if required, callers should account for its reliance on cached Projects implementation and period data and invoke REFRESH_PA_CACHE when underlying configuration changes.