Skip to content
Fusion Reference

RCV_SHIPMENT_HEADERS

Product: RCVtransaction

Receipt and expected-receipt headers — one row per supplier ASN, receipt, in-transit shipment, or RMA return, grouped by receipt source; carries the receipt number, supplier, and expected/shipped dates

Notes

The receiving org is SHIP_TO_ORG_ID; an ORGANIZATION_ID column exists but holds the FROM (shipping) org of in-transit shipments — this catalog deliberately does not anchor on it, because filtering it as "the org" inverts inter-org flows. RECEIPT_SOURCE_CODE separates VENDOR / INVENTORY / TRANSFER ORDER / CUSTOMER (RMA) flows; ASN-only headers have a shipment number and no receipt number until goods arrive.

What the badges mean
Product: EGP
Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.

Structural facts — how the table is partitioned, not a trap by itself

BU-striped (ORG_ID)
Rows are scoped to a business unit. The column is still named ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization via ORGANIZATION_ID — always pair it with INVENTORY_ITEM_ID on item-level joins (see the quirks guide).
Set / ledger / named-BU striped
Some tables stripe by a named column instead of ORG_ID: reference data set (SET_ID — see the quirks guide), ledger (LEDGER_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned.
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part of the key. Join without a window filter and every fact multiplies by history (see the quirks guide).
View
This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

Header & line

RCV_SHIPMENT_HEADERS is the header for its lines in RCV_SHIPMENT_LINES.

Extract access

The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.

  • FscmTopModelAM.ScmExtractAM.RcvBiccExtractAM.ReceivingInboundShipmentHeaderExtractPVO
    OTBI: Receiving - Receipts Real TimeOTBI: Receiving - Purchase Receipts Real Time

    Inbound Shipment Headers data store — keyed on ShipmentHeaderId. Receiving stores live in the SCM extract book, not the Procurement one.

    Oracle data-store documentation (opens in new tab)

Fields

16 fields · 1 key

16 fields.

Table fields: position, field name, description, data type, and flags. 16 fields.
#FieldDescriptionTypeFlags
1SHIPMENT_HEADER_IDSurrogate key of the receipt/shipment headerNUMBER
Key
2RECEIPT_SOURCE_CODESource of the shipment — VENDOR, INVENTORY, TRANSFER ORDER, CUSTOMER (RMA), OUTSOURCERVARCHAR2
3RECEIPT_NUMReceipt number for this header — ASN-only headers have none until goods arriveVARCHAR2
4SHIPMENT_NUMSource-assigned shipment number (ASN, in-transit, or transfer order)VARCHAR2
5ASN_TYPEASN / ASBN advance notice, or STD plain receiptVARCHAR2
6VENDOR_IDSupplier on the shipmentNUMBER
7VENDOR_SITE_IDSupplier siteNUMBER
8ORGANIZATION_IDThe FROM (shipping) org of in-transit shipments — NOT the receiving org; deliberately unanchoredNUMBER
9SHIP_TO_ORG_IDThe receiving inventory org where the receipt is createdNUMBER
10SHIP_TO_LOCATION_IDReceiving locationNUMBER
11CUSTOMER_IDCustomer — RMA (customer-return) receipts onlyNUMBER
12EMPLOYEE_IDPerson who created the receiving transactionNUMBER
13BILL_OF_LADINGBill of lading numberVARCHAR2
14PACKING_SLIPPacking slip numberVARCHAR2
15SHIPPED_DATEWhen the shipment was created/shippedDATE
16EXPECTED_RECEIPT_DATEExpected arrival dateDATE
Filter date

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of RCV_SHIPMENT_HEADERS on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) 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

6 parameters not filled: <catalog>, <schema>, <SHIPMENT_HEADER_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : RCV_SHIPMENT_HEADERS — Receipt and expected-receipt headers — one row per supplier ASN, receipt, in-transit shipment, or RMA return, 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 Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. 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 "Source of the shipment — VENDOR, INVENTORY, TRANSFER ORDER, CUSTOMER (RMA), OUTSOURCER",
  t.RECEIPT_NUM AS "Receipt number for this header — ASN-only headers have none until goods arrive",
  t.SHIPMENT_NUM AS "Source-assigned shipment number (ASN, in-transit, or transfer order)",
  t.ASN_TYPE AS "ASN / ASBN advance notice, or STD plain receipt",
  t.VENDOR_ID AS "Supplier on the shipment",
  t.VENDOR_SITE_ID AS "Supplier site",
  t.ORGANIZATION_ID AS "The FROM (shipping) org of in-transit shipments — NOT the receiving org; deliberately unanchored",
  t.SHIP_TO_ORG_ID AS "The receiving inventory org where the receipt is created",
  t.SHIP_TO_LOCATION_ID AS "Receiving location",
  t.CUSTOMER_ID AS "Customer — RMA (customer-return) receipts only",
  t.EMPLOYEE_ID AS "Person who created the receiving transaction",
  t.BILL_OF_LADING AS "Bill of lading number",
  t.PACKING_SLIP AS "Packing slip number",
  t.SHIPPED_DATE AS "When the shipment was created/shipped",
  t.EXPECTED_RECEIPT_DATE AS "Expected arrival date"
FROM <catalog>.<schema>.RCV_SHIPMENT_HEADERS t
WHERE
  1 = 1  -- no automatic partition anchor 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>'  -- the column incremental BICC extracts key on
ORDER BY t.SHIPMENT_HEADER_ID;

Verified September 2026 · docs release 26C

Column names differ in BICC extracts — see PVO header drift.

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Loading relationship diagram…

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_HEADERSPOZ_SUPPLIERSforeign key · N:1
    ON RCV_SHIPMENT_HEADERS.VENDOR_ID = POZ_SUPPLIERS.VENDOR_ID
  • RCV_SHIPMENT_HEADERSINV_ORG_PARAMETERSforeign key · N:1
    ON RCV_SHIPMENT_HEADERS.SHIP_TO_ORG_ID = INV_ORG_PARAMETERS.ORGANIZATION_ID
  • RCV_TRANSACTIONSRCV_SHIPMENT_HEADERSforeign key · N:1
    ON RCV_TRANSACTIONS.SHIPMENT_HEADER_ID = RCV_SHIPMENT_HEADERS.SHIPMENT_HEADER_ID

Browse more Receiving tables

More Receiving tables

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 Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.