Search Results check_ap_invoices

Overview

PA_INTEGRATION is a public PL/SQL package in the APPS schema that mediates the integration between Oracle Projects (PA) and adjacent EBS modules — most notably Oracle Payables (AP) and Oracle General Ledger (GL). Its primary business purpose is to answer cross-module questions about cost distribution and accounting period context without forcing the calling process to re-query the base transaction tables repeatedly. The package implementation (PAXPINTS.pls, version 120.1) shows a deliberate caching architecture: package-level global variables hold the earliest start date, end date, and period name for a provider organization and a receiver organization, taken from PA_COST_DISTRIBUTION_LINES_ALL columns such as PA_DATE, RECVR_PA_DATE, PA_PERIOD_NAME, and RECVR_PA_PERIOD_NAME. Because those globals persist for the life of a database session, PA_INTEGRATION exposes a refresh routine so that callers can invalidate the cached values when underlying data changes — this is the purpose of REFRESH_PA_CACHE, the procedure most often sought when users search for "refresh_pa_cache".

Key Procedures and Functions

• REFRESH_PA_CACHE — Resets the session-level global cache variables used by the date and period retrieval functions, ensuring that subsequent calls obtain current values from the cost distribution tables rather than stale session state. Typically invoked after processing that alters provider or receiver PA dates.
• GET_RAW_CDL_PA_DATE — Returns the raw PA date for the provider organization from PA_COST_DISTRIBUTION_LINES_ALL, using the cached globals where valid.
• GET_RAW_CDL_RECVR_PA_DATE — Companion function returning the receiver-side PA date from the RECVR_PA_DATE column.
• GET_BURDEN_CDL_PA_DATE — Returns the burdened cost distribution line PA date used for accounting date derivation.
• GET_PERIOD_NAME — Returns the PA period name associated with the cached cost distribution context (referenced internally by note 2835063).
• GET_PERIOD_INFORMATION — Supplies consolidated period attributes for the provider or receiver organization.
• GET_GL_PERIOD_NAME — Maps the Projects period context to the corresponding GL period name, supporting accounting event generation.
• CHECK_AP_INVOICES — Determines whether Payables invoice data exists for the transaction under consideration, gating downstream interface logic.
• INIT_AP_INVOICES — Initializes the AP invoice working structures prior to validation.
• AP_INVOICE_STATUS — Returns the status of the associated AP invoice, enabling Projects to detect whether related Payables activity has posted or is pending.

Tables Accessed

The package reads cost and expenditure data through APPS synonyms: PA_COST_DISTRIBUTION_LINES_ALL and PA_COST_DISTRIBUTION_LINES (raw and burdened PA dates, period names, receiver dates), PA_EXPENDITURE_ITEMS_ALL and PA_EXPENDITURE_ITEMS (provider and receiver organization identifiers), PA_PERIODS and PA_PERIODS_ALL (period definitions), PA_IMPLEMENTATIONS_ALL (operating unit configuration), GL_PERIODS and GL_PERIOD_STATUSES (GL calendar and open/closed status), and AP_INVOICES_ALL (invoice existence and status). These accesses explain the package's name: it joins Projects costing facts to Payables invoices and GL periods.

Usage Notes

PA_INTEGRATION is a public API (classification OTHER) referenced by four other packages, which indicates that Oracle's own Projects cost and accounting flows call it rather than end users invoking it directly. In practice it is invoked from concurrent programs, Oracle Forms-based Projects windows, and custom extensions that need consistent PA date or period derivation. Because the caching globals are session-scoped, custom code that changes cost distribution lines within the same session must call REFRESH_PA_CACHE before re-reading dates; otherwise stale provider and receiver dates may be returned, producing incorrect accounting dates or period assignments.