Search Results rcv_headers_interface




Overview
Explore in AI Chat

Overview

RCV_HEADERS_INTERFACE is the receiving header interface table owned by the PO schema in Oracle E-Business Suite. It stores receiving header information prior to validation and import into the permanent receiving tables. In the Oracle Purchasing and Receiving modules, this table functions as the staging area between external or internal source systems and the Oracle Receiving application. Data loaded into RCV_HEADERS_INTERFACE is processed by the Receiving Open Interface, which validates the rows, applies business rules, and ultimately creates receipt records in the destination tables (RCV_SHIPMENT_HEADERS and its dependent children).

The table supports both inbound EDI transactions and manual or programmatic data loads. Its column set reflects the broad range of receiving scenarios that Oracle supports: standard receipts, ASN (Advance Shipment Notice) receipts, corrections, returns to vendor, and internal transfer receipts. Based on the foreign key relationship to PSB_EMPLOYEES through EMPLOYEE_ID, the table maintains an association with employee records, though the heuristic Data Vault classification for this object is standalone — it does not function as a classic hub, link, or satellite in the modeled sense. This classification should be treated as a modeling suggestion rather than a definitive architectural designation.

Key Information Stored

The primary surrogate key is HEADER_INTERFACE_ID, which is also the sole documented unique index (RCV_HEADERS_INTERFACE_U1). This is the business-key candidate for uniquely identifying each interface header row. The GROUP_ID column groups related interface records into a single logical batch. PROCESSING_STATUS_CODE indicates the processing state (for example, Pending, Running, Error, or Success), while PROCESSING_REQUEST_ID links the row to the concurrent request that processed it.

The table contains 100 documented columns in the 12.2.2 physical schema, but the columns above are the ones most frequently referenced by integrations and reports.

Common Use Cases and Queries

The most common use case is populating RCV_HEADERS_INTERFACE from an external system, then running the Receiving Open Interface concurrent program to import the receipts. A typical monitoring query checks rows that failed validation:

  • SELECT HEADER_INTERFACE_ID, RECEIPT_NUM, PROCESSING_STATUS_CODE, PROCESSING_REQUEST_ID FROM RCV_HEADERS_INTERFACE WHERE GROUP_ID = :group_id AND PROCESSING_STATUS_CODE = 'ERROR';
  • SELECT GROUP_ID, PROCESSING_STATUS_CODE, COUNT(*) FROM RCV_HEADERS_INTERFACE GROUP BY GROUP_ID, PROCESSING_STATUS_CODE;
  • Join to the shipment interface via GROUP_ID to reconcile header and line records after import.
  • Report on receipts by vendor, ship-to organization, or expected date for inbound logistics dashboards.

Related Objects

The following objects are most significant in relation to RCV_HEADERS_INTERFACE. The documented foreign key relationship links EMPLOYEE_ID to PSB_EMPLOYEES.

  • RCV_SHIPMENT_HEADERS — destination table where validated receipt headers are created; the interface feeds records into this table via the open interface.
  • RCV_TRANSACTIONS_INTERFACE — companion interface table for transaction-level data loaded alongside the header.
  • PSB_EMPLOYEES — referenced via the EMPLOYEE_ID foreign key, the only documented FK relationship for this table.
  • PO_HEADERS_ALL — supplier and purchase order context used during receipt validation.
  • PO_VENDORS and PO_VENDOR_SITES_ALL — source of vendor and vendor site validation for VENDOR_ID and VENDOR_SITE_ID.
  • HR_ALL_ORGANIZATION_UNITS — organization source for SHIP_TO_ORGANIZATION_ID and FROM_ORGANIZATION_ID.
  • Receiving Open Interface (RCV_OPEN_INTERFACE) concurrent program — the processing engine that consumes rows in this table.