RCV_SHIPMENT_LINES
Schema: POtransactionReceipt/shipment lines — one row per item per shipment header with cumulative shipped and received quantities, line status, the source-document pointers (PO, requisition, or RMA), and the default putaway destination
Org columns are TO_ORGANIZATION_ID (receiving inventory org — the item-join org half) and FROM_ORGANIZATION_ID (source org on internal shipments); there is no plain ORGANIZATION_ID. The item column is ITEM_ID. Quantities here are cumulative — receiving events live in the transaction ledger.
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_LINES lines join back to their header RCV_SHIPMENT_HEADERS — and the org column — so a line never fans out.
Fields
18 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | SHIPMENT_LINE_ID | Surrogate key of the shipment line | NUMBER | Key |
| 2 | SHIPMENT_HEADER_ID | The parent header — unique with LINE_NUM | NUMBER | |
| 3 | LINE_NUM | Line number within the header | NUMBER | |
| 4 | ITEM_ID | The item — this table's name for it; pairs with TO_ORGANIZATION_ID for item-master joins | NUMBER | |
| 5 | QUANTITY_SHIPPED | Quantity on the ASN/shipment | NUMBER | |
| 6 | QUANTITY_RECEIVED | Cumulative quantity received — a balance; events live in the transaction ledger | NUMBER | |
| 7 | UNIT_OF_MEASURE | Transaction UOM, in its 25-character name form (not the 3-char code) | VARCHAR2 | |
| 8 | SHIPMENT_LINE_STATUS_CODE | Line status — expected, partially received, fully received, cancelled | VARCHAR2 | |
| 9 | SOURCE_DOCUMENT_CODE | What kind of document the line receives against — PO, requisition, RMA, or inventory | VARCHAR2 | |
| 10 | DESTINATION_TYPE_CODE | Where the goods are headed — receiving, inventory, expense, shop floor | VARCHAR2 | |
| 11 | PO_HEADER_ID | The PO being received, for PO-sourced lines | NUMBER | |
| 12 | PO_LINE_ID | The PO line | NUMBER | |
| 13 | PO_LINE_LOCATION_ID | The PO shipment schedule | NUMBER | |
| 14 | REQUISITION_LINE_ID | The requisition line, for internal-order receipts | NUMBER | |
| 15 | OE_ORDER_LINE_ID | The sales order line, for RMA (customer-return) receipts | NUMBER | |
| 16 | TO_ORGANIZATION_ID | The receiving inventory org — the item-join org half | NUMBER | |
| 17 | FROM_ORGANIZATION_ID | The shipping org, on internal shipments | NUMBER | |
| 18 | TO_SUBINVENTORY | Default putaway subinventory | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading RCV_SHIPMENT_LINESon 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_LINES — Receipt/shipment lines — one row per item per shipment header with cumulative shipped and received quantities, line status, the source-document pointers (PO, requisition, or RMA), 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 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_LINE_ID AS "Surrogate key of the shipment line",
t.SHIPMENT_HEADER_ID AS "The parent header — unique with LINE_NUM",
t.LINE_NUM AS "Line number within the header",
t.ITEM_ID AS "The item — this table's name for it; pairs with TO_ORGANIZATION_ID for item-master joins",
t.QUANTITY_SHIPPED AS "Quantity on the ASN/shipment",
t.QUANTITY_RECEIVED AS "Cumulative quantity received — a balance; events live in the transaction ledger",
t.UNIT_OF_MEASURE AS "Transaction UOM, in its 25-character name form (not the 3-char code)",
t.SHIPMENT_LINE_STATUS_CODE AS "Line status — expected, partially received, fully received, cancelled",
t.SOURCE_DOCUMENT_CODE AS "What kind of document the line receives against — PO, requisition, RMA, or inventory",
t.DESTINATION_TYPE_CODE AS "Where the goods are headed — receiving, inventory, expense, shop floor",
t.PO_HEADER_ID AS "The PO being received, for PO-sourced lines",
t.PO_LINE_ID AS "The PO line",
t.PO_LINE_LOCATION_ID AS "The PO shipment schedule",
t.REQUISITION_LINE_ID AS "The requisition line, for internal-order receipts",
t.OE_ORDER_LINE_ID AS "The sales order line, for RMA (customer-return) receipts",
t.TO_ORGANIZATION_ID AS "The receiving inventory org — the item-join org half",
t.FROM_ORGANIZATION_ID AS "The shipping org, on internal shipments",
t.TO_SUBINVENTORY AS "Default putaway 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>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
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 = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND RCV_SHIPMENT_LINES.TO_ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_IDON RCV_SHIPMENT_LINES.PO_LINE_ID = PO_LINES_ALL.PO_LINE_IDON RCV_SHIPMENT_LINES.OE_ORDER_LINE_ID = OE_ORDER_LINES_ALL.LINE_IDON RCV_TRANSACTIONS.SHIPMENT_LINE_ID = RCV_SHIPMENT_LINES.SHIPMENT_LINE_ID