Search Results rcv_lots_interface




Overview
Explore in AI Chat

Overview

RCV_LOTS_INTERFACE is a receiving lots interface table owned by the PO (Purchasing) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is the staging mechanism through which lot, sublot, and quantity information is submitted to the Receiving open interface for processing against receipt transactions. Rather than being an operational table that users query directly, RCV_LOTS_INTERFACE is a transient staging object: records are inserted by external systems, custom concurrent programs, or EDI/integration processes, then consumed and validated by the Receiving Transaction Processor, which moves accepted rows into the receiving transaction and lot tables.

The table is tightly bound to RCV_TRANSACTIONS_INTERFACE, the parent receiving interface. Each lot line references an interface transaction through INTERFACE_TRANSACTION_ID and a receipt shipment line through SHIPMENT_LINE_ID. The documented physical schema in ETRM 12.2.2 lists 22 columns, all owned by PO.

Under a heuristic Data Vault classification mined from the foreign key structure, RCV_LOTS_INTERFACE models as a link entity. It sits between the receiving transaction interface and receipt shipment lines, carrying the transactional relationship and its descriptive attributes. This classification is a modeling suggestion only; functionally the table behaves as an interface staging structure rather than a persistent data warehouse link.

Key Information Stored

The most significant columns fall into three groups: identifiers, lot attributes, and quantities.

The documented structure does not expose a surrogate primary key column distinct from the business keys; the principal business-key candidates are INTERFACE_TRANSACTION_ID combined with SHIPMENT_LINE_ID and LOT_NUM.

Common Use Cases and Queries

Typical scenarios include loading lot data for receiving integration, diagnosing stuck interface records, and reconciling quantities submitted versus processed.

To inspect pending interface lot rows for a request:

  • SELECT INTERFACE_TRANSACTION_ID, SHIPMENT_LINE_ID, LOT_NUM, QUANTITY, TRANSACTION_DATE FROM RCV_LOTS_INTERFACE WHERE REQUEST_ID = :request_id;

To join lot staging to its transaction interface header:

  • SELECT rli.LOT_NUM, rli.QUANTITY, rti.TRANSACTION_TYPE, rti.SOURCE_CODE FROM RCV_LOTS_INTERFACE rli JOIN RCV_TRANSACTIONS_INTERFACE rti ON rli.INTERFACE_TRANSACTION_ID = rti.INTERFACE_TRANSACTION_ID;

To reconcile against the receipt shipment line:

  • SELECT rli.LOT_NUM, rli.QUANTITY, rsl.SHIPMENT_LINE_ID FROM RCV_LOTS_INTERFACE rli JOIN RCV_SHIPMENT_LINES rsl ON rli.SHIPMENT_LINE_ID = rsl.SHIPMENT_LINE_ID;

Report rows tied to a specific program invocation using PROGRAM_ID and PROGRAM_APPLICATION_ID, or filter by creation date for batch monitoring. Following processing, the Receiving Transaction Processor reconciles staged rows and clears the interface.

Related Objects

The principal related objects and their documented join columns are:

  • RCV_TRANSACTIONS_INTERFACE — the parent receiving interface; joined on INTERFACE_TRANSACTION_ID.
  • RCV_SHIPMENT_LINES — the receipt shipment line; joined on SHIPMENT_LINE_ID.
  • RCV_TRANSACTIONS — populated after successful processing; lot details are ultimately written to receiving lot tables such as RCV_LOTS_SERIAL_NUMBERS.
  • PO_LINE_LOCATIONS_ALL / PO_HEADERS_ALL — upstream purchasing documents referenced through shipment lines.
  • Receiving Transaction Processor concurrent program — the component that consumes and validates RCV_LOTS_INTERFACE rows.

Because RCV_LOTS_INTERFACE is an interface table, direct DML is generally reserved for integration loads, and the supported path for creating receipts remains the Receiving open interface and its associated APIs.