Search Results po_headers_interface_s




Overview
Explore in AI Chat

Overview

PO_AUTO_IMPLEMENT_PVT is an internal (private) PL/SQL package body owned by the APPS schema in Oracle E-Business Procurement. It participates in the AutoCreate process, which automates the conversion of approved requisitions and other demand documents into blanket agreement, standard, or planned purchase orders. The AutoCreate flow is executed through the PO AutoCreate concurrent program and its associated parameter framework; the PO_AUTO_IMPLEMENT_PVT package provides the implementation-phase logic that takes data staged from AutoCreate processing and applies it to the purchasing tables, ultimately creating the resulting documents.

The package is classified as PVT, meaning it is not a public API and is intended strictly for internal invocation by other AutoCreate processes rather than by customer extension code. It is documented with a single entry point, PROCESS, and is referenced by one other package within the Oracle Purchasing module. Because the object status is VALID, the compiled body is consistent with its specification and dependent objects in both Oracle EBS 12.1.1 and 12.2.2 codelines.

Key Procedures and Functions

The documented interface exposes one procedure:

  • PROCESS — The primary control routine that drives the implementation stage of AutoCreate. It is responsible for orchestrating the reading of interfaced records and the creation or update of the resulting purchasing entities. Based on its name and dependencies, it consumes AutoCreate parameters and staged interface rows, then commits the generated purchase orders and their associated lines and schedules. No public parameter list is documented in the ETRM metadata, so the exact signature should be confirmed against the package specification in a given environment.

The package body also depends on PO_AUTOCREATE_PVT and PO_AUTOCREATE_PARAMS, reflecting a layered design in which parameter handling and AutoCreate orchestration are separated from the implementation logic compiled into this body. PO_DEBUG is referenced for diagnostic trace output, and PO_MESSAGE_S is referenced for message-handling during processing errors or warnings.

Tables Accessed

The documented table dependencies map directly to the AutoCreate document-creation flow:

  • PO_HEADERS_INTERFACE, PO_HEADERS_INTERFACE_S — The inbound header-level staging tables from which AutoCreate extracts requisition grouping and supplier/document attributes. PO_HEADERS_INTERFACE_S is the corresponding sequence used to generate unique interface identifiers.
  • PO_HEADERS_ALL — The destination table for created or updated purchase order headers.
  • PO_LINES_INTERFACE, PO_LINES_INTERFACE_S — Staged line-level data sourced from requisition lines; the sequence supports surrogate key population.
  • PO_LINES_ALL — Stores the resulting purchase order lines derived from the interface records.
  • PO_LINE_LOCATIONS_ALL — Holds shipment or schedule distribution rows generated for the created lines.
  • PO_REQUISITION_LINES_ALL — The source requisition lines that are consumed and subsequently referenced as the origin of the created purchase order lines.
  • DUAL — Used for single-row lookups and scalar evaluations within the PL/SQL logic.

Usage Notes

PO_AUTO_IMPLEMENT_PVT is not intended for direct invocation by end users or by custom code. It is invoked indirectly when an AutoCreate run is executed, either interactively through the AutoCreate form or through the PO AutoCreate concurrent program, and it operates on data previously staged by the AutoCreate extraction and validation phases. Because the object is documented as not referenced by any business-facing database object but referencing PO_AUTOCREATE_PVT and related internals, it should be treated as part of the sealed AutoCreate implementation stack.

Customizations that require modification of AutoCreate behavior should be implemented through supported extension mechanisms, such as AutoCreate document style or sourcing rule configuration, rather than by altering this private package. When diagnosing AutoCreate issues, the tables PO_HEADERS_INTERFACE, PO_LINES_INTERFACE, and the _S sequence objects, together with PO_MESSAGE_S output, are the most useful checkpoints for confirming that PROCESS-completed rows were successfully migrated into PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL. Debug tracing can be enabled through the PO_DEBUG dependency when supported by the environment's profile settings.