Skip to content
EBS Reference

RCV_SHIPMENT_HEADERS

Schema: POtransaction

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

Module: ReceivingNot org-partitioned
Notes

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.
In field listings, K marks a primary-key field.

Header & line

RCV_SHIPMENT_HEADERS is the header for its lines in RCV_SHIPMENT_LINES.

Fields

15 fields · 1 key

Table fields: position, field name, description, data type, and flags. 15 fields.
#FieldDescriptionTypeFlags
1SHIPMENT_HEADER_IDSurrogate key of the receipt/shipment headerNUMBER
Key
2RECEIPT_SOURCE_CODEWhere the receipt came from — supplier, internal order, or customer return; sources never mix under one headerVARCHAR2
3RECEIPT_NUMThe receipt number — unique only within the receiving org, and NULL on ASN-only headers until goods arriveVARCHAR2
4SHIPMENT_NUMThe supplier's shipment/ASN number — supplier-assigned, not uniqueVARCHAR2
5SHIP_TO_ORG_IDThe receiving INVENTORY org — this table's org filter (not an operating unit)NUMBER
6VENDOR_IDThe supplier, for supplier-sourced receiptsNUMBER
7VENDOR_SITE_IDThe supplier siteNUMBER
8CUSTOMER_IDThe customer, for RMA (return) receiptsNUMBER
9SHIPPED_DATEWhen the source shippedDATE
10EXPECTED_RECEIPT_DATEExpected arrival — the inbound-visibility date; the true receipt date lives on the RECEIVE transactionDATE
Filter date
11BILL_OF_LADINGBill of lading referenceVARCHAR2
12PACKING_SLIPPacking slip numberVARCHAR2
13WAYBILL_AIRBILL_NUMCarrier waybill/airbill numberVARCHAR2
14FREIGHT_CARRIER_CODEFreight carrierVARCHAR2
15ASN_TYPEShip 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.

Query parameters
-- ============================================================
-- 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

  • RCV_SHIPMENT_HEADERSRCV_SHIPMENT_LINESheader line · 1:N
    ON RCV_SHIPMENT_HEADERS.SHIPMENT_HEADER_ID = RCV_SHIPMENT_LINES.SHIPMENT_HEADER_ID
  • RCV_SHIPMENT_HEADERSMTL_PARAMETERSforeign key · N:1
    ON RCV_SHIPMENT_HEADERS.SHIP_TO_ORG_ID = MTL_PARAMETERS.ORGANIZATION_ID
  • RCV_SHIPMENT_HEADERSAP_SUPPLIERSforeign key · N:1
    ON RCV_SHIPMENT_HEADERS.VENDOR_ID = AP_SUPPLIERS.VENDOR_ID
  • RCV_TRANSACTIONSRCV_SHIPMENT_HEADERSforeign key · N:1
    ON RCV_TRANSACTIONS.SHIPMENT_HEADER_ID = RCV_SHIPMENT_HEADERS.SHIPMENT_HEADER_ID
  • MTL_SUPPLYRCV_SHIPMENT_HEADERSforeign key · N:1
    ON MTL_SUPPLY.SHIPMENT_HEADER_ID = RCV_SHIPMENT_HEADERS.SHIPMENT_HEADER_ID

Browse more Receivingtables →

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice →

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.