Skip to content
EBS Reference

RCV_SHIPMENT_LINES

Schema: POtransaction

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

Notes

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

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

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1SHIPMENT_LINE_IDSurrogate key of the shipment lineNUMBER
Key
2SHIPMENT_HEADER_IDThe parent header — unique with LINE_NUMNUMBER
3LINE_NUMLine number within the headerNUMBER
4ITEM_IDThe item — this table's name for it; pairs with TO_ORGANIZATION_ID for item-master joinsNUMBER
5QUANTITY_SHIPPEDQuantity on the ASN/shipmentNUMBER
6QUANTITY_RECEIVEDCumulative quantity received — a balance; events live in the transaction ledgerNUMBER
7UNIT_OF_MEASURETransaction UOM, in its 25-character name form (not the 3-char code)VARCHAR2
8SHIPMENT_LINE_STATUS_CODELine status — expected, partially received, fully received, cancelledVARCHAR2
9SOURCE_DOCUMENT_CODEWhat kind of document the line receives against — PO, requisition, RMA, or inventoryVARCHAR2
10DESTINATION_TYPE_CODEWhere the goods are headed — receiving, inventory, expense, shop floorVARCHAR2
11PO_HEADER_IDThe PO being received, for PO-sourced linesNUMBER
12PO_LINE_IDThe PO lineNUMBER
13PO_LINE_LOCATION_IDThe PO shipment scheduleNUMBER
14REQUISITION_LINE_IDThe requisition line, for internal-order receiptsNUMBER
15OE_ORDER_LINE_IDThe sales order line, for RMA (customer-return) receiptsNUMBER
16TO_ORGANIZATION_IDThe receiving inventory org — the item-join org halfNUMBER
17FROM_ORGANIZATION_IDThe shipping org, on internal shipmentsNUMBER
18TO_SUBINVENTORYDefault putaway subinventoryVARCHAR2

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.

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

  • RCV_SHIPMENT_HEADERSRCV_SHIPMENT_LINESheader line · 1:N
    ON RCV_SHIPMENT_HEADERS.SHIPMENT_HEADER_ID = RCV_SHIPMENT_LINES.SHIPMENT_HEADER_ID
  • RCV_SHIPMENT_LINESMTL_SYSTEM_ITEMS_Bforeign key · N:1
    ON RCV_SHIPMENT_LINES.ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND RCV_SHIPMENT_LINES.TO_ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • RCV_SHIPMENT_LINESPO_LINES_ALLforeign key · N:1
    ON RCV_SHIPMENT_LINES.PO_LINE_ID = PO_LINES_ALL.PO_LINE_ID
  • RCV_SHIPMENT_LINESOE_ORDER_LINES_ALLforeign key · N:1
    ON RCV_SHIPMENT_LINES.OE_ORDER_LINE_ID = OE_ORDER_LINES_ALL.LINE_ID
  • RCV_TRANSACTIONSRCV_SHIPMENT_LINESforeign key · N:1
    ON RCV_TRANSACTIONS.SHIPMENT_LINE_ID = RCV_SHIPMENT_LINES.SHIPMENT_LINE_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.