RCV_SHIPMENT_LINES
Product: RCVtransactionReceipt/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
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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.ReceivingInboundShipmentLineExtractPVOOTBI: Receiving - Purchase Receipts Real TimeOTBI: Receiving - Receipts Real Time
Inbound Shipment Lines data store — keyed on ShipmentLineId.
Oracle data-store documentation →
Fields
18 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | SHIPMENT_LINE_ID | Surrogate key of the shipment/receipt line | NUMBER | Key |
| 2 | SHIPMENT_HEADER_ID | Parent shipment header | NUMBER | |
| 3 | LINE_NUM | Line number within the shipment | NUMBER | |
| 4 | ITEM_ID | Item on the line | NUMBER | |
| 5 | ITEM_REVISION | Item revision | VARCHAR2 | |
| 6 | CATEGORY_ID | Item category | NUMBER | |
| 7 | QUANTITY_SHIPPED | Net (cumulative) quantity shipped on the line — a running total, not an event | NUMBER | |
| 8 | QUANTITY_RECEIVED | Net (cumulative) quantity received on the line | NUMBER | |
| 9 | UOM_CODE | UOM of the line quantities | VARCHAR2 | |
| 10 | TO_ORGANIZATION_ID | Receiving inventory org — the item-join org half | NUMBER | |
| 11 | FROM_ORGANIZATION_ID | Source org on in-transit lines | NUMBER | |
| 12 | SHIPMENT_LINE_STATUS_CODE | EXPECTED / PARTIALLY RECEIVED / FULLY RECEIVED / CANCELLED | VARCHAR2 | |
| 13 | SOURCE_DOCUMENT_CODE | Which document type the line receives against | VARCHAR2 | |
| 14 | PO_HEADER_ID | PO header pointer | NUMBER | |
| 15 | PO_LINE_ID | PO line pointer | NUMBER | |
| 16 | PO_LINE_LOCATION_ID | PO schedule pointer | NUMBER | |
| 17 | DESTINATION_TYPE_CODE | Destination type of the line | VARCHAR2 | |
| 18 | TO_SUBINVENTORY | Default destination subinventory | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of RCV_SHIPMENT_LINESon 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.
-- ============================================================
-- 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 partition column 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;4 parameters not filled: <catalog>, <schema>, <SHIPMENT_LINE_ID>, <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_LINES.ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND RCV_SHIPMENT_LINES.TO_ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_IDON RCV_SHIPMENT_LINES.PO_LINE_LOCATION_ID = PO_LINE_LOCATIONS_ALL.LINE_LOCATION_IDON RCV_SHIPMENT_LINES.CATEGORY_ID = EGP_CATEGORIES_B.CATEGORY_IDON RCV_TRANSACTIONS.SHIPMENT_LINE_ID = RCV_SHIPMENT_LINES.SHIPMENT_LINE_ID