Search Results rcv_serials_supply




Overview
Explore in AI Chat

Overview

RCV_SERIALS_SUPPLY is a receiving serial supply table owned by the PO (Purchasing) schema in Oracle EBS 12.1.1 and 12.2.2. It records the serial number attributes associated with receiving transactions in Oracle Purchasing and Oracle Receiving. The table captures vendor serial numbers, internal serial numbers, lot numbers, and supply type information for goods received against shipment lines. It is a supporting detail table within the Receiving (RCV) data model, sitting beneath the transactional structure defined by RCV_TRANSACTIONS and the shipment structure defined by RCV_SHIPMENT_LINES.

From a Data Vault modeling perspective (heuristic classification mined from the foreign key structure), RCV_SERIALS_SUPPLY is best treated as a link table. It connects shipment lines to receiving transactions while carrying descriptive serial/lot attributes. This classification reflects its role as a bridge between two core business entities: the shipment line (the physical movement of goods) and the receiving transaction (the accounting and inventory event).

Key Information Stored

The table contains 15 documented columns. The most significant are grouped below.

The metadata does not document a surrogate primary key or unique index for this table, so no surrogate key is named here. Where a primary key exists in the underlying schema, it would typically be a composite of SHIPMENT_LINE_ID, TRANSACTION_ID, and SERIAL_NUM, but this is not confirmed in the provided metadata. The columns LAST_UPDATE_DATE and LAST_UPDATED_BY serve as the effective date for a satellite-style attribute set if the table is treated as a satellite within the Data Vault model.

Common Use Cases and Queries

RCV_SERIALS_SUPPLY is used primarily for serial number tracking, vendor serial reconciliation, and audit reporting. Typical scenarios include:

  • Identifying all serial numbers received on a specific shipment or receipt.
  • Comparing vendor serial numbers against internally assigned serial numbers for reconciliation.
  • Reporting lot and serial details for lot-controlled or serial-controlled items.
  • Auditing receiving transactions to determine which serial numbers were associated with a given receipt or correction.

A common join pattern uses SHIPMENT_LINE_ID and TRANSACTION_ID to reach the parent tables:

SELECT rs.SERIAL_NUM, rs.VENDOR_SERIAL_NUM, rs.LOT_NUM,
       rt.TRANSACTION_ID, rt.TRANSACTION_TYPE,
       rsl.SHIPMENT_LINE_ID, rsl.ITEM_ID
FROM   RCV_SERIALS_SUPPLY rs,
       RCV_TRANSACTIONS   rt,
       RCV_SHIPMENT_LINES rsl
WHERE  rs.TRANSACTION_ID   = rt.TRANSACTION_ID
AND    rs.SHIPMENT_LINE_ID = rsl.SHIPMENT_LINE_ID
AND    rt.TRANSACTION_ID   = :p_transaction_id;

For serial-controlled items, the query above returns the receipt-level serial supply records needed for inventory and quality reporting.

Related Objects

The following objects are most significant relative to RCV_SERIALS_SUPPLY:

  • RCV_SHIPMENT_LINES — Referenced by RCV_SERIALS_SUPPLY.SHIPMENT_LINE_ID. Parent table defining the shipment line for which serial supply is recorded.
  • RCV_TRANSACTIONS — Referenced by RCV_SERIALS_SUPPLY.TRANSACTION_ID. Parent table defining the receiving transaction event.
  • RCV_TRANSACTIONS_INTERFACE — Interface table through which receiving transactions are loaded; serial supply data is often validated against it.
  • MTL_SERIAL_NUMBERS — Inventory serial number master; used to validate internal serial numbers.
  • MTL_LOT_NUMBERS — Inventory lot master; used to validate LOT_NUM values.
  • PO_RECEIPTS and PO_LINES — Purchasing receipt and line tables used to reconcile receiving serial data back to the originating purchase order.

These relationships make RCV_SERIALS_SUPPLY an integration point between Purchasing receiving, Inventory serial/lot management, and downstream audit reporting.