Search Results pa_po_integration

Overview

PA_PO_INTEGRATION is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its name reflects its role as a control and validation layer within the integration between Oracle Projects (PA) and Oracle Purchasing (PO). In EBS, commitments and encumbrances originating from purchase orders can be associated with projects and tasks, and Project Manufacturing, Project Costing, and cross-charge workflows depend on consistent behavior between the two modules. Rather than performing the full integration transaction itself, PA_PO_INTEGRATION exposes a small set of boolean-valued check functions that report whether specific integration features are enabled in the current environment. Consumer packages use these functions to decide whether to execute project-related logic during purchasing events such as document creation, price adjustment, or retroactive pricing.

Key Procedures and Functions

The ETRM documentation for APPS.PA_PO_INTEGRATION classifies the package as OTHER and records three documented functions. Because each is a boolean check, no parameter list is published in the metadata; only purpose is described below.

• IS_PJR_PO_INTEG_ENABLED — Determines whether the Project Manufacturing (PJR) purchasing integration is active. Callers use the result to gate logic that ties purchase order distributions to project and task references.
• IS_PJC_PO_CWK_INTG_ENAB — Reports whether the Project Costing (PJC) purchasing and costing/work-plan integration is enabled. This governs whether purchasing activity should feed project cost collection or work-plan related structures.
• IS_PJC_11I10_ENABLED — Indicates whether the environment is operating with the legacy 11.5.10 Project Costing behavior. This supports conditional handling where newer R12 functionality must fall back to older processing paths.

Tables Accessed

The provided metadata does not document any tables referenced by PA_PO_INTEGRATION through APPS synonyms. The absence of a table dependency list is consistent with the package's nature: each documented function is a feature or profile-option switch, and such checks are typically resolved by reading system profile option values rather than by querying project or purchasing transaction tables directly. The package therefore does not read or write project commitments, purchase order distributions, or expenditure records itself. Any data persistence occurs in the calling packages after they evaluate these boolean results.

Usage Notes

PA_PO_INTEGRATION is designed for internal consumption by other Oracle Projects and Purchasing packages rather than for direct invocation by end users. The ETRM dependency information confirms that it is referenced by AP_WEB_PROJECT_PKG, PO_PDOI_PVT, and PO_RETROACTIVE_PRICING_PVT, along with a recursive reference from PA_PO_INTEGRATION itself. This dependency pattern places the package in the purchasing document open interface (PDOI) and retroactive pricing flows, where it is called early to determine whether project integration rules should apply to the document being processed. The AP_WEB_PROJECT_PKG dependency extends the same control to expense-related project processing.

Because the exposed functions are simple enablement checks, they are typically invoked as conditions inside larger PL/SQL blocks rather than scheduled through concurrent programs or Oracle Forms. No standard profile-driven form or concurrent program is documented as calling the package directly. Developers extending purchasing or project integration logic in a custom environment may call these functions for consistency, but should be aware that the behavior of the flags depends on system configuration and release level, and that the functions remain subject to change between 12.1.1 and 12.2.2 unless the ETRM metadata explicitly confirms their availability.