Results for “rcv_serial_transactions”

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

Overview

RCV_SERIAL_TRANSACTIONS is a receiving table owned by the PO schema in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2). It records serial-controlled movement events that occur during the receiving process, capturing the association between a serialized item, the receipt transaction that moved it, and the shipment line against which the receipt was booked. In effect, it is the audit link between the serial number master/interface and the receiving transaction history, allowing the system to track which serial numbers were received, delivered, returned, corrected, or otherwise adjusted through receiving.

Under a heuristic Data Vault classification mined from its foreign key structure, this table is best modeled as a link table. It resolves the many-to-many relationship between receiving transactions (RCV_TRANSACTIONS), shipment lines (RCV_SHIPMENT_LINES), and individual serial numbers. It carries transactional attributes (such as transaction date and usage status) alongside its key columns, so it also exhibits satellite-like characteristics, but its dominant role is that of a relationship/link entity.

Key Information Stored

The table is defined with 20 documented columns. The most significant are:

• SERIAL_TRANSACTION_TYPE — the type of serial movement (e.g., receive, deliver, return, correct). Part of both unique keys and central to interpreting any row.
• SERIAL_NUM — the serial number of the item involved; part of both unique keys.
• SHIPMENT_LINE_ID — foreign key to the shipment line against which the serial was received/corrected.
• TRANSACTION_ID — foreign key to RCV_TRANSACTIONS; the primary receiving transaction that generated the event.
• SOURCE_TRANSACTION_ID — foreign key to RCV_TRANSACTIONS; identifies the originating transaction for corrections or derived events.
• CORRECTION_TRANSACTION_ID — foreign key to RCV_TRANSACTIONS; identifies the correcting transaction when the serial event is a reversal or adjustment.
• USAGE_STATUS_CODE — indicates the usage status of the serial at the time of the transaction.
• LOT_NUM — the lot associated with the serial, where lot-controlled items are also serialized.
• VENDOR_SERIAL_NUM and VENDOR_LOT_NUM — the supplier's own serial and lot numbers, preserved for reconciliation with the vendor's shipment.
• TRANSACTION_DATE — the effective date of the serial movement.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and the concurrent program context columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

The documented unique keys are RCV_SERIAL_TRX_UK01 (SERIAL_TRANSACTION_TYPE, SHIPMENT_LINE_ID, SERIAL_NUM) and RCV_SERIAL_TRX_UK02 (SERIAL_TRANSACTION_TYPE, TRANSACTION_ID, SERIAL_NUM). These composite unique indexes are the business-key candidates; there is no single-column surrogate primary key.

Common Use Cases and Queries

Typical uses include serial traceability reporting, receipt reconciliation, and correction auditing. A frequent query joins the table to the receiving transactions to report serial movements per receipt:

• Serial receipt history: join RCV_SERIAL_TRANSACTIONS to RCV_TRANSACTIONS on TRANSACTION_ID to list all serial numbers received on a given transaction or date range.
• Correction analysis: filter rows where CORRECTION_TRANSACTION_ID IS NOT NULL, or join on that column, to trace which corrections affected a serial.
• Vendor reconciliation: compare VENDOR_SERIAL_NUM against SERIAL_NUM to detect discrepancies between the supplier's records and the internal serial assigned at receipt.
• Shipment-line drilldown: filter by SHIPMENT_LINE_ID to enumerate every serial movement against a specific line.

Related Objects

• RCV_TRANSACTIONS — referenced three times via TRANSACTION_ID, SOURCE_TRANSACTION_ID, and CORRECTION_TRANSACTION_ID; the core receiving transaction table.
• RCV_SHIPMENT_LINES — referenced via SHIPMENT_LINE_ID; provides the shipment-line context.
• RCV_SHIPMENT_HEADERS — reached transitively through RCV_SHIPMENT_LINES for receipt-level reporting.
• MTL_SERIAL_NUMBERS / MTL_SERIAL_NUMBERS_INTERFACE — inventory serial definitions and open-interface staging, commonly joined on SERIAL_NUM.
• PO_RECEIVING APIs — receiving and correction APIs (e.g., RCV_Receipt_Transaction) that populate this table during receipt and correction processing.