Results for “rcv_supply_u1”

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

Overview

RCV_SUPPLY is a summary table in the Oracle E-Business Suite Purchasing (PO) module that consolidates information about items currently in receiving or inspection. Owned by the PO schema, the table provides a denormalized, high-performance snapshot of supply activity tied to requisitions, purchase orders, releases, shipments, and receiving transactions. Rather than serving as a transactional detail table, RCV_SUPPLY aggregates the key attributes of a supply record into a single row, making it efficient for inquiry screens, receiving workbenches, and downstream reporting.

Based on the foreign-key topology, the heuristic Data Vault classification for this object is a link. The table's 43 columns consist almost entirely of foreign-key references to surrounding hub entities—requisitions, purchase orders, releases, shipments, distributions, and receiving transactions—plus descriptive attributes such as quantity and unit of measure. This pattern is characteristic of a link table that resolves many-to-many or many-to-one relationships between core business entities. The composite primary key RCV_SUPPLY_PK (SUPPLY_TYPE_CODE, SUPPLY_SOURCE_ID) reinforces this interpretation, since the business identity of a supply row is expressed through its source type and source identifier rather than a synthetic sequence.

Key Information Stored

The table carries a composite primary key of SUPPLY_TYPE_CODE and SUPPLY_SOURCE_ID, which together uniquely identify a supply record. A separate unique index, RCV_SUPPLY_U1 on RCV_TRANSACTION_ID, provides an alternate business-key candidate linking each supply summary row back to a specific receiving transaction.

• SUPPLY_TYPE_CODE / SUPPLY_SOURCE_ID — the composite primary key defining the supply record's identity.
• RCV_TRANSACTION_ID — foreign key to the originating receiving transaction and the source of the RCV_SUPPLY_U1 unique index.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID — the purchase order hierarchy linking supply to its originating order, line, shipment, and distribution.
• REQ_HEADER_ID, REQ_LINE_ID — requisition context when the supply originates from an internal or purchase requisition.
• SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID — receiving shipment references.
• FROM_ORGANIZATION_ID, FROM_SUBINVENTORY, TO_ORGANIZATION_ID, TO_SUBINVENTORY — source and destination organization and subinventory, with FROM_SUBINVENTORY and TO_SUBINVENTORY referencing MTL_SECONDARY_INVENTORIES.
• ITEM_ID, ITEM_REVISION — the item and revision being received or transferred.
• QUANTITY, UNIT_OF_MEASURE, SECONDARY_QUANTITY, SECONDARY_UNIT_OF_MEASURE — primary and secondary quantities and units of measure.
• RECEIPT_DATE, DESTINATION_TYPE_CODE, LOCATION_ID, TO_LOCATOR_ID — receipt timing, destination type, and locator information.
• LPN_ID — license plate number reference for warehouse management scenarios.

Common Use Cases and Queries

RCV_SUPPLY supports receiving inquiries, supply-demand analysis, and reconciliation of receiving activity against purchasing documents. A typical query joins RCV_SUPPLY to PO_HEADERS_ALL and PO_LINES_ALL to report open supply against purchase orders:

SELECT rs.supply_source_id, ph.segment1 AS po_number,
       rs.item_id, rs.quantity, rs.unit_of_measure
FROM   rcv_supply rs,
       po_headers_all ph
WHERE  rs.po_header_id = ph.po_header_id
AND    rs.supply_type_code = 'PO';

Because the user searched for MTL_SECONDARY_INVENTORIES, the most relevant query pattern joins on the subinventory columns to translate destination codes into meaningful subinventory names:

SELECT rs.supply_source_id, msi.secondary_inventory_name,
       rs.quantity
FROM   rcv_supply rs,
       mtl_secondary_inventories msi
WHERE  rs.to_subinventory = msi.secondary_inventory_name
AND    rs.to_organization_id = msi.organization_id;

Reporting use cases include in-transit inventory analysis, subinventory-level receiving summaries, and reconciliation between RCV_TRANSACTIONS and their summarized supply rows.

Related Objects

The most significant related objects are the tables referenced by RCV_SUPPLY foreign keys. MTL_SECONDARY_INVENTORIES appears twice, via FROM_SUBINVENTORY/FROM_ORGANIZATION_ID and TO_SUBINVENTORY/TO_ORGANIZATION_ID. The purchasing chain includes PO_REQUISITION_HEADERS_ALL (REQ_HEADER_ID), PO_REQUISITION_LINES_ALL (REQ_LINE_ID), PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, and PO_RELEASES_ALL (PO_RELEASE_ID). Receiving-related dependencies include RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS (RCV_TRANSACTION_ID), the latter also supporting the RCV_SUPPLY_U1 unique index.