Search Results open_specific_headers




Overview
Explore in AI Chat

Overview

APPS.PO_PDOI_HEADER_PROCESS_PVT is a private PL/SQL package within the Oracle E-Business Suite Purchasing module that supports the Processing Document Interface (PDOI) engine. PDOI is the internal framework used by Oracle Purchasing to process large volumes of transactional data through the open interface tables, most notably PO_HEADERS_INTERFACE and its line and distribution counterparts. The header process package is responsible for the header-level slice of that pipeline: it opens the interface data, derives and defaults header attributes, validates the resulting records, and stages them for downstream processing.

Classified as a PVT (private) package in the APPS schema, it is not intended as a public API for external or customer use. Its status is VALID over both the 12.1.1 and 12.2.2 releases, and it is tightly bound to the PDOI family — PO_PDOI_MAINPROC_PVT, PO_PDOI_PREPROC_PVT, PO_PDOI_POSTPROC_PVT, and PO_PDOI_LINE_LOC_PROCESS_PVT — which invoke or are referenced alongside it. This layered design allows the framework to process headers independently of lines, locations, and distributions while keeping the PL/SQL interface consistent.

Key Procedures and Functions

The package exposes eleven documented procedures and functions, grouped functionally:

  • OPEN_HEADERS and OPEN_SPECIFIC_HEADERS — Open header-level cursors for processing. OPEN_HEADERS typically processes the full set of eligible interface rows, while OPEN_SPECIFIC_HEADERS allows a targeted subset, such as a specific interface header or batch, to be opened.
  • FETCH_HEADERS — Retrieves records from the opened header cursor so that subsequent derive and validate routines can operate on them.
  • DERIVE_HEADERS — Computes derived header attributes that are not directly supplied by the interface data.
  • DEFAULT_HEADERS — Applies defaulting rules to header fields, drawing on sourcing rules, document style configuration, and profile options.
  • VALIDATE_HEADERS — Applies validation logic to header records and returns or records any errors before the records proceed downstream.
  • DERIVE_LOCATION_ID, DERIVE_TERMS_ID, DERIVE_VENDOR_ID, DERIVE_CLM_SOURCE_DOCUMENT_ID, and DERIVE_VENDOR_ID_FROM_IDV — Specialized derivation helpers for key header foreign keys. These resolve the location, payment terms, vendor, and contract source document identifiers, including the path that identifies a vendor from an internally defined vendor (IDV) when the interface supplies an indirect reference.

Tables Accessed

The package reads and writes through APPS synonyms. Header data is stored in PO_HEADERS_INTERFACE and is eventually written to PO_HEADERS and PO_HEADERS_ALL. Derived attributes reference AP_TERMS for payment terms, GL_DAILY_CONVERSION_TYPES for currency conversion, PO_DOC_STYLE_HEADERS and PO_DOC_STYLE_LINES_TL for document style configuration, and PO_PRINT_FORM_FORMATS for layout metadata. PO_SESSION_GT acts as a global temporary session table holding per-session processing state, while PO_PDOI_TYPES and the PO_TBL_NUMBER, PO_TBL_VARCHAR30, PO_TBL_VARCHAR100, PO_TBL_VARCHAR240, PO_TBL_VARCHAR2000 collections are used internally. DBMS_SQL supports dynamic SQL construction, and PLITBLM is a standard supporting table.

Usage Notes

PO_PDOI_HEADER_PROCESS_PVT is invoked internally by the PDOI concurrent programs, principally the Purchasing Documents Open Interface, and by the coordinating packages PO_PDOI_MAINPROC_PVT, PO_PDOI_PREPROC_PVT, and PO_PDOI_POSTPROC_PVT. It should not be called directly from custom code; customer extensions should use the supported open interface tables and concurrent programs instead. Because PDOI runs in a batch context, the session global temporary table must be populated before derivation and validation execute, and the package assumes interface records have already been loaded by upstream stages. When troubleshooting import failures, checking the outcome of VALIDATE_HEADERS and the interface error tables is the normal diagnostic path.