Search Results po_pdoi_params




Overview
Explore in AI Chat

Overview

The APPS.PO_PDOI_POSTPROC_PVT package is an internal Oracle Purchasing private API that forms part of the Purchasing Documents Open Interface (PDOI) processing architecture within Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to perform post-processing validation and reconciliation activities after a purchasing document has been processed through the PDOI import pipeline. During the PDOI workflow, supplier-facing and internally managed purchasing documents such as purchase orders, quotations, and agreements are staged in interface tables and subsequently loaded into the base Purchasing tables. The post-processing phase handled by this package is responsible for evaluating the imported records, resolving vendor and agent references, and preparing the document for downstream approval routing and distribution. By isolating these activities into a private package, Oracle separates the core import logic in PO_PDOI_PVT from the follow-on processing performed by PO_PDOI_POSTPROC_PVT, providing a modular and maintainable pipeline. The package is classified as PVT, indicating that it is intended for internal use by Oracle's own code and is not part of the supported public API surface. Its companion objects include the interface tables and several draft and attribute tables that hold intermediate data during import.

Key Procedures and Functions

The documented ETRM metadata lists a single program unit exposed by this package: the PROCESS procedure. This procedure serves as the entry point for the post-processing stage of the PDOI pipeline. In practice, it is invoked after the primary import steps have completed and is responsible for validating and finalizing imported document records before they become available for approval and use. PROCESS coordinates the evaluation of imported header data, the reconciliation of associated draft records, and the resolution of related entities such as vendors and buyers. The precise parameter signature is intentionally not reproduced here; the procedure is an internal component and callers should rely on Oracle's own PDOI orchestration rather than invoke it directly.

Tables Accessed

The package operates across the core Purchasing data model and its interface staging area. PO_HEADERS_INTERFACE holds the incoming document data that is being imported, and it is read during post-processing to determine the state and content of each imported record. PO_HEADERS_ALL represents the base purchasing header table into which finalized documents are stored, while PO_HEADERS_DRAFT_ALL and PO_DRAFTS support the draft and change-management constructs used when documents are created or modified. PO_VENDORS supplies supplier information required to validate and complete the document, and PO_PDOI_PARAMS provides the runtime parameters that govern how PDOI processing behaves, including options affecting post-processing. The package also relies on the collection types PO_TBL_DATE, PO_TBL_NUMBER, and PO_TBL_VARCHAR60 to carry arrays of values during its internal processing. Additional tables documented for the 12.2.2 release, such as PO_AGENTS, PO_DISTRIBUTIONS_ALL, PO_DOCUMENT_TYPES, PO_DOC_STYLE_HEADERS, and AME-related approval tables, reflect the broader reconciliation performed during post-processing, including buyer resolution, distribution handling, and document style determination.

Usage Notes

PO_PDOI_POSTPROC_PVT is not a public API and should not be called directly from custom code. It is invoked internally by PO_PDOI_PVT, which references it as part of the PDOI import orchestration, and it is also self-referenced within the package. The typical invocation path is through the Purchasing Documents Open Interface concurrent program, which drives the import of staged documents and manages the transition from interface tables to base tables. Forms-based Processing options for PDOI ultimately trigger this processing on the server. Because the package touches core header, draft, distribution, and approval tables, any customizations that bypass Oracle's supported import flow risk data integrity issues and are unsupported. Developers troubleshooting PDOI import problems may examine this package to understand validation and reconciliation behavior, but should rely on the documented public interfaces for extensions.