Skip to content
Fusion Reference

RCV_SHIPMENT_LINES

Product: RCVtransaction

Receipt/shipment lines — one row per item per shipment header with cumulative shipped and received quantities, line status, the source-document pointers, and the default putaway destination

Notes

Org columns are TO_ORGANIZATION_ID (receiving org — the item-join org half) and FROM_ORGANIZATION_ID (source org on in-transit lines); there is no plain ORGANIZATION_ID. QUANTITY_SHIPPED / QUANTITY_RECEIVED are net running totals — receiving events live in the transaction ledger. The item column is ITEM_ID.

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_LINES lines join back to their header RCV_SHIPMENT_HEADERS — and the org column — so a line never fans out.

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.ReceivingInboundShipmentLineExtractPVO
    OTBI: Receiving - Purchase Receipts Real TimeOTBI: Receiving - Receipts Real Time

    Inbound Shipment Lines data store — keyed on ShipmentLineId.

    Oracle data-store documentation (opens in new tab)

Fields

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1SHIPMENT_LINE_IDSurrogate key of the shipment/receipt lineNUMBER
Key
2SHIPMENT_HEADER_IDParent shipment headerNUMBER
3LINE_NUMLine number within the shipmentNUMBER
4ITEM_IDItem on the lineNUMBER
5ITEM_REVISIONItem revisionVARCHAR2
6CATEGORY_IDItem categoryNUMBER
7QUANTITY_SHIPPEDNet (cumulative) quantity shipped on the line — a running total, not an eventNUMBER
8QUANTITY_RECEIVEDNet (cumulative) quantity received on the lineNUMBER
9UOM_CODEUOM of the line quantitiesVARCHAR2
10TO_ORGANIZATION_IDReceiving inventory org — the item-join org halfNUMBER
11FROM_ORGANIZATION_IDSource org on in-transit linesNUMBER
12SHIPMENT_LINE_STATUS_CODEEXPECTED / PARTIALLY RECEIVED / FULLY RECEIVED / CANCELLEDVARCHAR2
13SOURCE_DOCUMENT_CODEWhich document type the line receives againstVARCHAR2
14PO_HEADER_IDPO header pointerNUMBER
15PO_LINE_IDPO line pointerNUMBER
16PO_LINE_LOCATION_IDPO schedule pointerNUMBER
17DESTINATION_TYPE_CODEDestination type of the lineVARCHAR2
18TO_SUBINVENTORYDefault destination subinventoryVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of RCV_SHIPMENT_LINES 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

4 parameters not filled: <catalog>, <schema>, <SHIPMENT_LINE_ID>, <watermark>

-- ============================================================
-- Table  : RCV_SHIPMENT_LINES — Receipt/shipment lines — one row per item per shipment header with cumulative shipped and received quantities, line status, the source-document pointers, and the default putaway destination
-- Purpose: Column-selected read of RCV_SHIPMENT_LINES — auto-generated from field metadata
-- Grain  : One row per SHIPMENT_LINE_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_LINE_ID AS "Surrogate key of the shipment/receipt line",
  t.SHIPMENT_HEADER_ID AS "Parent shipment header",
  t.LINE_NUM AS "Line number within the shipment",
  t.ITEM_ID AS "Item on the line",
  t.ITEM_REVISION AS "Item revision",
  t.CATEGORY_ID AS "Item category",
  t.QUANTITY_SHIPPED AS "Net (cumulative) quantity shipped on the line — a running total, not an event",
  t.QUANTITY_RECEIVED AS "Net (cumulative) quantity received on the line",
  t.UOM_CODE AS "UOM of the line quantities",
  t.TO_ORGANIZATION_ID AS "Receiving inventory org — the item-join org half",
  t.FROM_ORGANIZATION_ID AS "Source org on in-transit lines",
  t.SHIPMENT_LINE_STATUS_CODE AS "EXPECTED / PARTIALLY RECEIVED / FULLY RECEIVED / CANCELLED",
  t.SOURCE_DOCUMENT_CODE AS "Which document type the line receives against",
  t.PO_HEADER_ID AS "PO header pointer",
  t.PO_LINE_ID AS "PO line pointer",
  t.PO_LINE_LOCATION_ID AS "PO schedule pointer",
  t.DESTINATION_TYPE_CODE AS "Destination type of the line",
  t.TO_SUBINVENTORY AS "Default destination subinventory"
FROM <catalog>.<schema>.RCV_SHIPMENT_LINES t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.SHIPMENT_LINE_ID = <SHIPMENT_LINE_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.SHIPMENT_LINE_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.

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_LINESEGP_SYSTEM_ITEMS_Bforeign key · N:1
    ON RCV_SHIPMENT_LINES.ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND RCV_SHIPMENT_LINES.TO_ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • RCV_SHIPMENT_LINESPO_LINE_LOCATIONS_ALLforeign key · N:1
    ON RCV_SHIPMENT_LINES.PO_LINE_LOCATION_ID = PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID
  • RCV_SHIPMENT_LINESEGP_CATEGORIES_Bforeign key · N:1
    ON RCV_SHIPMENT_LINES.CATEGORY_ID = EGP_CATEGORIES_B.CATEGORY_ID
  • RCV_TRANSACTIONSRCV_SHIPMENT_LINESforeign key · N:1
    ON RCV_TRANSACTIONS.SHIPMENT_LINE_ID = RCV_SHIPMENT_LINES.SHIPMENT_LINE_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.