RCV_SHIPMENT_HEADERS
Schema: POtransactionReceipt and expected-receipt headers — one row per supplier ASN, receipt, or internal shipment, grouped by receipt source; carries the receipt number, supplier, and expected/shipped dates
The receiving org is SHIP_TO_ORG_ID (an inventory org; RECEIPT_NUM is unique only within it). An ORGANIZATION_ID column exists but holds the source-org context of internal shipments — this catalog deliberately does not anchor on it. ASN-only headers have a shipment number and no receipt number until goods arrive, so counting headers is not counting receipts.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Header & line
RCV_SHIPMENT_HEADERS is the header for its lines in RCV_SHIPMENT_LINES.
Fields
15 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | SHIPMENT_HEADER_ID | Surrogate key of the receipt/shipment header | NUMBER | Key |
| 2 | RECEIPT_SOURCE_CODE | Where the receipt came from — supplier, internal order, or customer return; sources never mix under one header | VARCHAR2 | |
| 3 | RECEIPT_NUM | The receipt number — unique only within the receiving org, and NULL on ASN-only headers until goods arrive | VARCHAR2 | |
| 4 | SHIPMENT_NUM | The supplier's shipment/ASN number — supplier-assigned, not unique | VARCHAR2 | |
| 5 | SHIP_TO_ORG_ID | The receiving INVENTORY org — this table's org filter (not an operating unit) | NUMBER | |
| 6 | VENDOR_ID | The supplier, for supplier-sourced receipts | NUMBER | |
| 7 | VENDOR_SITE_ID | The supplier site | NUMBER | |
| 8 | CUSTOMER_ID | The customer, for RMA (return) receipts | NUMBER | |
| 9 | SHIPPED_DATE | When the source shipped | DATE | |
| 10 | EXPECTED_RECEIPT_DATE | Expected arrival — the inbound-visibility date; the true receipt date lives on the RECEIVE transaction | DATE | Filter date |
| 11 | BILL_OF_LADING | Bill of lading reference | VARCHAR2 | |
| 12 | PACKING_SLIP | Packing slip number | VARCHAR2 | |
| 13 | WAYBILL_AIRBILL_NUM | Carrier waybill/airbill number | VARCHAR2 | |
| 14 | FREIGHT_CARRIER_CODE | Freight carrier | VARCHAR2 | |
| 15 | ASN_TYPE | Ship notice kind — ASN vs ASBN (with billing) | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading RCV_SHIPMENT_HEADERSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- Table : RCV_SHIPMENT_HEADERS — Receipt and expected-receipt headers — one row per supplier ASN, receipt, or internal shipment, grouped by receipt source; carries the receipt number, supplier, and expected/shipped dates
-- Purpose: Column-selected read of RCV_SHIPMENT_HEADERS — auto-generated from field metadata
-- Grain : One row per SHIPMENT_HEADER_ID
-- Notes : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
t.SHIPMENT_HEADER_ID AS "Surrogate key of the receipt/shipment header",
t.RECEIPT_SOURCE_CODE AS "Where the receipt came from — supplier, internal order, or customer return; sources never mix under one header",
t.RECEIPT_NUM AS "The receipt number — unique only within the receiving org, and NULL on ASN-only headers until goods arrive",
t.SHIPMENT_NUM AS "The supplier's shipment/ASN number — supplier-assigned, not unique",
t.SHIP_TO_ORG_ID AS "The receiving INVENTORY org — this table's org filter (not an operating unit)",
t.VENDOR_ID AS "The supplier, for supplier-sourced receipts",
t.VENDOR_SITE_ID AS "The supplier site",
t.CUSTOMER_ID AS "The customer, for RMA (return) receipts",
t.SHIPPED_DATE AS "When the source shipped",
t.EXPECTED_RECEIPT_DATE AS "Expected arrival — the inbound-visibility date; the true receipt date lives on the RECEIVE transaction",
t.BILL_OF_LADING AS "Bill of lading reference",
t.PACKING_SLIP AS "Packing slip number",
t.WAYBILL_AIRBILL_NUM AS "Carrier waybill/airbill number",
t.FREIGHT_CARRIER_CODE AS "Freight carrier",
t.ASN_TYPE AS "Ship notice kind — ASN vs ASBN (with billing)"
FROM <catalog>.<schema>.RCV_SHIPMENT_HEADERS t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.SHIPMENT_HEADER_ID = <SHIPMENT_HEADER_ID>
-- AND t.EXPECTED_RECEIPT_DATE >= DATE '<DATE_FROM>'
-- AND t.EXPECTED_RECEIPT_DATE <= DATE '<DATE_TO>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.SHIPMENT_HEADER_ID;6 parameters not filled: <catalog>, <schema>, <SHIPMENT_HEADER_ID>, <DATE_FROM>, <DATE_TO>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON RCV_SHIPMENT_HEADERS.SHIPMENT_HEADER_ID = RCV_SHIPMENT_LINES.SHIPMENT_HEADER_IDON RCV_SHIPMENT_HEADERS.SHIP_TO_ORG_ID = MTL_PARAMETERS.ORGANIZATION_IDON RCV_SHIPMENT_HEADERS.VENDOR_ID = AP_SUPPLIERS.VENDOR_IDON RCV_TRANSACTIONS.SHIPMENT_HEADER_ID = RCV_SHIPMENT_HEADERS.SHIPMENT_HEADER_IDON MTL_SUPPLY.SHIPMENT_HEADER_ID = RCV_SHIPMENT_HEADERS.SHIPMENT_HEADER_ID