Results for “vendor_serial_num”

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

Overview

RCV_SERIALS_INTERFACE is the receiving serial interface table owned by the PO (Purchasing) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to serve as the inbound staging area for serial number and lot number information associated with receiving transactions before that information is validated and written to the permanent receiving tables. When receiving data is loaded through the Receiving Open Interface, serial and lot details can be supplied alongside transaction header and line data, and this table holds those details until the concurrent Receiving Transaction Processor consumes and validates them.

Each row in RCV_SERIALS_INTERFACE is associated with a pending interface transaction by way of INTERFACE_TRANSACTION_ID, which references RCV_TRANSACTIONS_INTERFACE. In Data Vault modeling terms, the table's foreign key structure classifies it heuristically as satellite-leaning — it functions as a dependent detail record keyed to the parent interface transaction, rather than as an independent hub or an associative link.

Key Information Stored

The table is documented with 19 columns. The most significant are described below.

• INTERFACE_TRANSACTION_ID — the foreign key to RCV_TRANSACTIONS_INTERFACE; identifies the parent interface transaction to which the serial or lot record belongs.
• FM_SERIAL_NUM and TO_SERIAL_NUM — the from and to serial numbers defining a range of serial numbers to be received.
• SERIAL_PREFIX — an optional prefix applied to generated serial numbers.
• VENDOR_SERIAL_NUM and VENDOR_LOT_NUM — the supplier's own serial and lot identifiers, retained for traceability.
• LOT_NUM — the lot number associated with the received quantity.
• ITEM_ID and ORGANIZATION_ID — the inventory item and destination organization for which the serial or lot data applies.
• TRANSACTION_DATE — the effective date of the receiving transaction.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — the concurrent request and program context that created or last processed the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns.

No separate surrogate primary key column is documented in the metadata; the interface transaction identifier acts as the business key linking each detail row to its parent interface record.

Common Use Cases and Queries

Typical usage centers on monitoring, troubleshooting, and reconciling the Receiving Open Interface. Common scenarios include:

• Detecting records that have not been processed because the Receiving Transaction Processor has not yet run or has rejected the parent interface row.
• Validating that supplied serial ranges (FM_SERIAL_NUM/TO_SERIAL_NUM) and quantities agree with the parent transaction.
• Reconciling vendor-supplied serial and lot identifiers against internal lot and serial numbers after receipt.
• Reporting on inbound receiving activity by item and organization.

A representative query joins the interface detail to its parent transaction:

• SELECT s.interface_transaction_id, s.item_id, s.organization_id, s.fm_serial_num, s.to_serial_num, s.lot_num, s.vendor_serial_num FROM rcv_serials_interface s, rcv_transactions_interface t WHERE s.interface_transaction_id = t.interface_transaction_id;

Related Objects

The following objects are most significant in relation to RCV_SERIALS_INTERFACE:

• RCV_TRANSACTIONS_INTERFACE — the parent interface table joined on INTERFACE_TRANSACTION_ID.
• RCV_HEADERS_INTERFACE and RCV_LOTS_INTERFACE — companion interface tables for header and lot data used in the same receiving load.
• RCV_TRANSACTIONS — the permanent receiving transactions table populated after processing.
• RCV_SERIAL_NUMBERS — the permanent serial number repository for validated receipts.
• MTL_SERIAL_NUMBERS and MTL_LOT_NUMBERS — the inventory serial and lot master tables referenced during validation.
• Receiving Transaction Processor — the concurrent program that consumes this table's rows.