Search Results rcv_headers_interface_u1

Overview

PO.RCV_HEADERS_INTERFACE is a public, active interface table in the Oracle E-Business Suite Receiving (RCV) module, owned by the PO schema and registered under FND Design Data as PO.RCV_HEADERS_INTERFACE. It stores receiving header information that has been staged for validation and processing by the Receiving Open Interface (ROI) concurrent program. Rather than being written to directly by users, the table is populated by external or feeder processes — Electronic Data Interchange (EDI) feeds, Advanced Shipment Notice (ASN) transactions, supplier collaboration extracts, or custom conversion routines — and is subsequently consumed by the Receiving Transaction Processor, which validates each row and creates or updates the corresponding records in the receiving application tables.

The table resides in the APPS_TS_INTERFACE tablespace with PCT Free 10, consistent with its role as a high-volume staging object that is periodically purged or archived. It participates in the business-entity categories PO_GOODS_RECEIPT, PO_EXPENSE_RECEIPT, PO_SERVICES_RECEIPTS, PO_GOODS_RETURN, and PO_RECEIPT_CORRECTION, reflecting that the interface supports the full breadth of receiving transaction types.

From a dimensional modeling perspective, the provided Data Vault heuristic classifies this object as standalone, with no significant link relationships mined from its foreign keys. This suggests treating it as a hub-like staging record keyed by HEADER_INTERFACE_ID, with descriptive attributes behaving as satellite data. The classification is best regarded as a modeling suggestion rather than a strict constraint, since the interface's true parent-child relationship to its line-level counterpart operates through the shared interface identifier.

Key Information Stored

The documented schema comprises 100 columns. The most operationally significant columns are:

• HEADER_INTERFACE_ID — the surrogate primary key and unique business-key candidate, enforced by the unique index RCV_HEADERS_INTERFACE_U1. It seeds the value that links header rows to their corresponding line-level interface rows.
• GROUP_ID — groups a related set of interface rows for set-based processing by the concurrent program.
• PROCESSING_STATUS_CODE — the processing state of the row; drives the Receiving Transaction Processor's selection logic and error reporting. Indexed (with GROUP_ID) via RCV_HEADERS_INTERFACE_N2.
• RECEIPT_SOURCE_CODE, ASN_TYPE, TRANSACTION_TYPE, and AUTO_TRANSACT_CODE — control the type of receipt operation (for example NEW, REPLACE, ADD, or CANCEL) and whether the transaction originates from an ASN, ASBN, or direct RECEIVE.
• RECEIPT_NUM and RECEIPT_HEADER_ID — identify an existing receipt for replacement, correction, or cancellation scenarios.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_NAME, and VENDOR_SITE_CODE — supplier identification; VENDOR_ID is indexed non-uniquely via RCV_HEADERS_INTERFACE_N1.
• SHIPMENT_NUM — the shipment reference, indexed non-uniquely via RCV_HEADERS_INTERFACE_N3.
• FROM_ORGANIZATION_ID, SHIP_TO_ORGANIZATION_ID, and ORG_ID — source and destination inventory context for the receiving transaction.
• SHIPPED_DATE and EXPECTED_RECEIPT_DATE — key planning dates carried through from the originating document.
• EDI_CONTROL_NUM — the EDI transaction control number when data arrives through EDI channels.
• TEST_FLAG — indicates whether the row is a test transaction that must not affect live balances.
• EMPLOYEE_ID — references PSB_EMPLOYEES, the sole documented foreign key relationship.
• Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY) — audit tracking required for all interface processing.

Common Use Cases and Queries

The primary use case is monitoring rows awaiting processing by the Receiving Open Interface. A typical query retrieves unprocessed headers for a group:

• Locate pending rows: SELECT header_interface_id, group_id, processing_status_code FROM po.rcv_headers_interface WHERE processing_status_code = 'PENDING' AND group_id = :group_id;
• Diagnose interface errors by filtering on rows whose PROCESSING_STATUS_CODE indicates rejection or validation failure, then joining to the line-level interface table on HEADER_INTERFACE_ID.
• Reconcile EDI receipts using EDI_CONTROL_NUM to trace inbound transactions against the interface staging records.
• Report on supplier-level inbound volume by grouping on VENDOR_ID or VENDOR_NAME, leveraging index RCV_HEADERS_INTERFACE_N1.
• Identify stale rows for cleanup by combining CREATION_DATE with PROCESSING_STATUS_CODE and GROUP_ID, since the table resides in an interface tablespace and requires periodic purge.

Because the table is a staging area, direct DML should be limited to correction or purge procedures; standard transaction submission is performed through the Receiving Open Interface API or concurrent program.

Related Objects

• PO.RCV_TRANSACTIONS_INTERFACE — the line-level counterpart; links through HEADER_INTERFACE_ID and must be processed alongside the header row.
• PO.RCV_HEADERS and PO.RCV_SHIPMENT_HEADERS — the production receiving header tables populated after successful validation via RECEIPT_HEADER_ID.
• PO.PSB_EMPLOYEES — documented foreign key target through EMPLOYEE_ID.
• PO.RCV_SHIPMENT_LINES — shipment detail used to resolve receipt lines derived from interface input.
• PO.PO_VENDORS, PO.PO_VENDOR_SITES_ALL, and PO.HZ_PARTIES — supplier and site lookups referenced by VENDOR_ID and VENDOR_SITE_ID.
• The Receiving Open Interface concurrent program and Receiving Transaction API — the principal consumers that read rows and write back processing outcomes.