Search Results po_headers_interface_u1

Overview

PO_HEADERS_INTERFACE is the public interface table in the PO schema that serves as the staging area for the Purchasing Documents Open Interface (PDOI) program. It holds header-level information used by PDOI to create standard purchase orders, blanket purchase orders, contract purchase agreements, global agreements, and catalog quotations in Oracle E-Business Suite 12.1.1 and 12.2.2. Records inserted into this table by external systems, batch loaders, or custom concurrent programs are validated and processed by PDOI, which derives or defaults additional attribute values and writes a row into PO_INTERFACE_ERRORS for every validation that fails.

The table is classified under multiple BUSINESS_ENTITY categories, including PO_STANDARD_PURCHASE_ORDER, PO_BLANKET_PURCHASE_AGREEMENT, PO_CONTRACT_PURCHASE_AGREEMENT, PO_GLOBAL_BLANKET_AGREEMENT, PO_GLOBAL_CONTRACT_AGREEMENT, and PO_PRICE_BREAKS. From a Data Vault modeling perspective, the mined metadata classifies this object as standalone; it is best treated as a staging or link-style structure rather than a true hub or satellite, since it brokers header data from external sources into the transactional PO_HEADERS_ALL and related entities.

Key Information Stored

The table contains 172 documented columns and resides in the APPS_TS_INTERFACE tablespace. The surrogate primary key is INTERFACE_HEADER_ID, enforced by the unique index PO_HEADERS_INTERFACE_U1; this column is the documented business-key candidate and the primary join key back to PO_INTERFACE_ERRORS. The most operationally significant columns include:

• INTERFACE_HEADER_ID — unique interface header identifier and the key used for error tracking.
• BATCH_ID — groups records loaded together for controlled processing; indexed by PO_HEADERS_INTERFACE_N2.
• PROCESSING_ID / PROCESSING_ROUND_NUM — control the PDOI run and re-validation rounds; indexed by PO_HEADERS_INTERFACE_N1.
• ACTION — the interface action (for example, ADD or NEW) to be applied by PDOI.
• INTERFACE_SOURCE_CODE — identifies the originating source system.
• ORG_ID — the operating unit that will own the created document.
• DOCUMENT_TYPE_CODE / DOCUMENT_SUBTYPE — determine whether a PO, RFQ, blanket, or contract is created.
• DOCUMENT_NUM — the supplier-facing document number.
• VENDOR_ID, VENDOR_SITE_ID, SHIP_TO_LOCATION_ID, BILL_TO_LOCATION_ID — key trading-partner and location references.
• PO_HEADER_ID — populated after successful import with the identifier of the created document; indexed by PO_HEADERS_INTERFACE_N4.
• CURRENCY_CODE, RATE_TYPE, RATE_DATE, RATE — currency and exchange-rate inputs.
• VENDOR_DOC_NUM — the supplier reference number; indexed by PO_HEADERS_INTERFACE_N3.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID — audit trail of the concurrent program that touched the row.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — descriptive flexfield context and segments.

Common Use Cases and Queries

Typical scenarios include bulk-loading supplier contracts from legacy systems, importing negotiated blanket agreements, and populating catalog quotations. A monitoring query identifies failed rows before or after PDOI execution:

• SELECT interface_header_id, batch_id, processing_id, processing_round_num, document_num, vendor_id FROM po.po_headers_interface WHERE action = 'ADD' AND processing_id IS NULL;
• SELECT hi.interface_header_id, hi.document_num, ie.error_message FROM po.po_headers_interface hi, po.po_interface_errors ie WHERE hi.interface_header_id = ie.interface_header_id AND ie.interface_header_id IS NOT NULL;
• SELECT batch_id, COUNT(*) FROM po.po_headers_interface GROUP BY batch_id ORDER BY batch_id;

Reporting frequently correlates the interface row with the resulting document using PO_HEADER_ID to confirm successful conversion and to reconcile counts per batch.

Related Objects

PO_HEADERS_INTERFACE references several parent objects directly and is itself referenced by validation and line-level companions:

• PO.PO_RELEASES_ALL — joined via PO_RELEASE_ID for release-level headers.
• PO.PO_VENDOR_LIST_HEADERS — joined via VENDOR_LIST_HEADER_ID for vendor-list sourcing rules.
• HR.HR_ADE_STYLES — joined via STYLE_ID for contract styles in procurement contracts.
• PO.PO_INTERFACE_ERRORS — receives validation failures keyed by INTERFACE_HEADER_ID.
• PO.PO_LINES_INTERFACE — the line-level companion table processed in the same PDOI run.
• PO.PO_HEADERS_ALL — the target transactional table populated with PO_HEADER_ID on success.
• PO.PO_DISTRIBUTIONS_INTERFACE and PO.PO_ATTRIBUTES_INTERFACE — additional staging companions for downstream PDOI data.

Together these objects form the complete PDOI import pipeline for purchasing documents in EBS Release 12.1.1 and 12.2.2.