Results for “rcv_shipment_lines”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

RCV_SHIPMENT_LINES, owned by the PO schema in Oracle E-Business Suite 12.1.1 and 12.2.2, stores the line-level detail of receiving shipment information. Each row corresponds to a single line on a shipment, capturing what was shipped, from which supplier document, to which destination, and in what quantity. This table is the operational heart of the receiving module: it bridges procurement documents (purchase orders, releases, requisitions) with inventory destinations and downstream accounting. It is populated during ASN import, manual receipt creation, and internal requisition shipment, and it is subsequently referenced by the receiving transactions stack, invoicing, and the JAI (India Localization) tax and excise tables.

Applying a heuristic Data Vault classification to the documented foreign-key structure, RCV_SHIPMENT_LINES behaves as a hub. It is identified by the surrogate key SHIPMENT_LINE_ID, carries business-key candidate pairs through unique indexes RCV_SHIPMENT_LINES_U1 and RCV_SHIPMENT_LINES_U2, and is referenced by numerous dependent satellites and link tables. This classification is a modeling suggestion rather than a published Oracle standard.

Key Information Stored

The table contains 112 documented columns. The most significant are:

• SHIPMENT_LINE_ID — surrogate primary key (RCV_SHIPMENT_LINES_PK, unique index RCV_SHIPMENT_LINES_U1) that uniquely identifies the shipment line.
• SHIPMENT_HEADER_ID and LINE_NUM — composite business key enforced by unique index RCV_SHIPMENT_LINES_U2; together they place the line within its parent shipment and provide the user-visible line sequence.
• QUANTITY_SHIPPED, QUANTITY_RECEIVED, UNIT_OF_MEASURE, PRIMARY_UNIT_OF_MEASURE — quantities and units for the line, with secondary-quantity counterparts available for dual-UOM tracking.
• ITEM_ID, ITEM_DESCRIPTION, ITEM_REVISION, CATEGORY_ID — the item and its receiving category.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID, PO_RELEASE_ID — the procurement document chain that this shipment line fulfills.
• REQUISITION_LINE_ID, REQ_DISTRIBUTION_ID — internal requisition origin, relevant to internal sales-order shipments.
• TO_ORGANIZATION_ID, TO_SUBINVENTORY, LOCATOR_ID — the inventory destination for the receipt.
• SHIPMENT_LINE_STATUS_CODE, SOURCE_DOCUMENT_CODE, INVOICE_STATUS_CODE — status and source context used throughout receiving and matching.
• SHIPMENT_UNIT_PRICE, TRANSFER_COST, TRANSPORTATION_COST, CHARGE_ACCOUNT_ID, TRANSPORTATION_ACCOUNT_ID — cost and accounting attributes.
• ROUTING_HEADER_ID, PACKING_SLIP, CONTAINER_NUM, TRUCK_NUM, BAR_CODE_LABEL — logistics and ASN context.

Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the DFF block (ATTRIBUTE_CATEGORY through ATTRIBUTE15) are also present.

Common Use Cases and Queries

The table is central to receipt inquiry, open-shipment tracking, and reconciliation reporting. A representative query joining the shipment header and purchase order location helps identify expected receipts:

• Receiving pending shipments: filter SHIPMENT_LINE_STATUS_CODE and join to RCV_SHIPMENT_HEADERS for supplier and date context.
• Order-to-receipt reconciliation: join PO_LINE_LOCATION_ID to PO_LINE_LOCATIONS_ALL to compare ordered versus shipped and received quantities.
• Invoice matching: AP_INVOICE_LINES_ALL.RCV_SHIPMENT_LINE_ID links invoices back to shipment lines for two-way, three-way, and four-way match verification.
• India Localization: JAI_MTL_MATCH_RECEIPTS.SHIPMENT_LINE_ID references this table to associate excise and customs matching records with individual shipment lines.
• Inventory destination reporting: group by TO_ORGANIZATION_ID and TO_SUBINVENTORY to summarize inbound volume by warehouse.

A typical join pattern is:

SELECT l.shipment_line_id, l.line_num, l.quantity_shipped, l.quantity_received, h.receipt_num
FROM   rcv_shipment_lines  l,
       rcv_shipment_headers h
WHERE  l.shipment_header_id = h.shipment_header_id
AND    l.shipment_line_status_code = 'EXPECTED';

Related Objects

The following dependencies are the most operationally significant, drawn from the documented FK metadata:

• RCV_SHIPMENT_HEADERS — parent shipment via SHIPMENT_HEADER_ID.
• PO_LINE_LOCATIONS_ALL and PO_DISTRIBUTIONS_ALL — purchase order schedule and distribution references.
• RCV_TRANSACTIONS and RCV_TRANSACTIONS_INTERFACE — receipt transactions and the open interface through which lines are processed.
• AP_INVOICE_LINES_ALL — invoice lines that reference the shipment line for matching.
• MTL_SUPPLY and RCV_SUPPLY — supply records that draw on shipment lines for sourcing.
• JAI_MTL_MATCH_RECEIPTS and JAI_RCV_LINES — India Localization match and excise line records.
• RCV_LOT_TRANSACTIONS and RCV_SERIAL_TRANSACTIONS — lot and serial receipt tracking.

These relationships make RCV_SHIPMENT_LINES a pivotal hub connecting procurement, receiving, inventory, invoicing, and localization processes across the EBS 12.1.1 and 12.2.2 data model.