Search Results po_pdoi_pvt




Overview

APPS.PO_PDOI_PVT is the core private (PVT) PL/SQL package that implements the Purchasing Documents Open Interface (PDOI) processing engine in Oracle E-Business Suite Release 12.1.1 and 12.2.2. PDOI is the standard integration point through which external systems, legacy applications, and batch loaders feed requisition, quotation, purchasing document, and sourcing data into Oracle Purchasing. The package name PO_PDOI_PVT reflects its role as the internal worker program: it is not a public, supported API surface but the procedural backbone invoked by the PDOI concurrent programs to validate, default, transform, and ultimately create purchasing documents from staging rows in the open interface tables.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the owner, a design consistent with packages that are called from within concurrent program request flows or from wrapper APIs running under APPS. The header carries a version marker dated 2013, consistent with the 12.2.x code line.

Key Procedures and Functions

The ETRM metadata documents exactly one program unit in this package: START_PROCESS.

  • START_PROCESS — The single entry point for the interface run. It accepts a standard API-style set of control arguments (API version, initialization of the message list, validation level, and commit flag) together with a large body of PDOI-specific configuration parameters. These parameters govern the selected batch to process, batch size, buyer context, document type and subtype, item and sourcing-rule creation flags, release generation method, sourcing level and inventory organization, approval status, processing code, interface header selection, operating unit, goods-received flag, draft submission flag, role, catalog expiration, and error-line tolerance behavior. The CLM (Contract Lifecycle Management) flag is an extension added for the PDOI project. On completion it returns the standard return status plus counters for processed lines, rejected lines, and whether the error tolerance threshold was exceeded.

This single-procedure design indicates that START_PROCESS orchestrates the entire run internally, delegating detailed work to sibling private packages rather than exposing granular operations to callers.

Tables Accessed

The documented table references show both configuration lookups and transactional writes:

Usage Notes

PO_PDOI_PVT is invoked indirectly. In standard deployments it is called by the Purchasing Documents Open Interface concurrent program (and its related submission flows) after staging records have been loaded into PO_HEADERS_INTERFACE and its interface lines. The documented metadata notes that it is referenced by one other package, consistent with a wrapper API such as PO_PDOI that exposes a narrower public signature and delegates to START_PROCESS.

Customizations should treat this package as private and unsupported for direct calls. Extensions of PDOI behavior are normally delivered through approved interface-table hooks, document type configuration, or wrapper APIs, not by altering or invoking PO_PDOI_PVT directly.