Search Results rcv_shipment_headers_u1

Overview

RCV_SHIPMENT_HEADERS is the Receiving module's receipt header table, owned by the PO schema and stored in the APPS_TS_TX_DATA tablespace. Every receiving transaction in Oracle EBS — whether a supplier shipment, an internal requisition receipt, or an inter-organization transfer — is grouped under a shipment header row before individual item lines are recorded. The table captures the common attributes of that grouping: who shipped the goods, from where, when they arrived, and the commercial terms surrounding the delivery. Oracle Purchasing does not permit receipts from different sources to share a single header, so the RECEIPT_SOURCE_CODE (Supplier or Internal Order) governs which of the optional columns become meaningful. When an intransit shipment is created by Oracle Inventory, the header row is inserted immediately, but RECEIPT_NUM remains unpopulated until the shipment is physically received. From a dimensional modeling perspective the ETRM dependency heuristics classify this table as hub-leaning, suggesting it be treated as a foundational parent entity whose descriptive attributes could be split into satellite structures in a data vault build.

Key Information Stored

The surrogate primary key is SHIPMENT_HEADER_ID, which is also the sole documented business-key candidate, enforced by the unique index RCV_SHIPMENT_HEADERS_U1 in the APPS_TS_TX_IDX tablespace. RECEIPT_NUM holds the user-visible receipt number, while SHIPMENT_NUM and PACKING_SLIP carry the supplier's own references. RECEIPT_SOURCE_CODE determines whether the receipt relates to a purchase order or an internal order; in the internal case ORGANIZATION_ID and SHIP_TO_ORG_ID identify the destination inventory organization. VENDOR_ID and VENDOR_SITE_ID reference the supplying party for supplier-source receipts, and SHIP_TO_LOCATION_ID identifies the delivery destination. Dates are recorded through EXPECTED_RECEIPT_DATE, SHIPPED_DATE, CREATION_DATE, and LAST_UPDATE_DATE. Shipping details include SHIP_TO_LOCATION_ID, FREIGHT_CARRIER_CODE, WAYBILL_AIRBILL_NUM, and BILL_OF_LADING. Invoice-level information such as INVOICE_NUM, INVOICE_AMOUNT, INVOICE_STATUS_CODE, TAX_AMOUNT, and FREIGHT_AMOUNT supports receipt-to-invoice matching. The table also exposes fifteen ATTRIBUTE columns and standard WHO audit columns (CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) for extensions and accountability.

Common Use Cases and Queries

Receiving inquiries and reconciliation reports typically begin at this header and join downward to RCV_SHIPMENT_LINES. A frequent pattern joins headers to lines and to RCV_TRANSACTIONS to reconstruct the full receipt history for a PO:

• Listing all open expected receipts by expected date: SELECT receipt_num, shipment_num, expected_receipt_date FROM rcv_shipment_headers WHERE receipt_source_code = 'VENDOR' AND expected_receipt_date BETWEEN :from_date AND :to_date;
• Locating a receipt by supplier reference: filtering on VENDOR_ID, PACKING_SLIP, or WAYBILL_AIRBILL_NUM using the corresponding nonunique indexes (RCV_SHIPMENT_HEADERS_N3, N11).
• Auditing receipts created after a given point in time under index N10 on CREATION_DATE, useful for period-close verification.
• Reporting inbound volume and carrier mix by joining FREIGHT_CARRIER_CODE and SHIPPED_DATE to supplier master data.
• Feeding Receiving Open Interface processes, which stage rows in RCV_TRANSACTIONS_INTERFACE before headers and lines are committed.

Related Objects

The dominant dependent is RCV_SHIPMENT_LINES, joined on SHIPMENT_HEADER_ID, which holds the individual receipt lines. RCV_TRANSACTIONS and RCV_TRANSACTIONS_INTERFACE both reference the header via SHIPMENT_HEADER_ID, as do MTL_SUPPLY and RCV_SUPPLY for supply-chain visibility. The header's own foreign keys point to PO_VENDORS (VENDOR_ID), PO_VENDOR_SITES_ALL (VENDOR_SITE_ID), and PSB_EMPLOYEES (EMPLOYEE_ID). Numerous localizations — including JAI_RCV_LINES, JAI_RCV_TRANSACTIONS, JAI_CMN_BOE_MATCHINGS, and the JAI_AP_MATCH family — carry SHIPMENT_HEADER_ID as a foreign key, making this table a central anchor for downstream receiving and tax reporting structures.