Search Results rcv_unprocessed_lot_issues_v




Overview
Explore in AI Chat

Overview

RCV_UNPROCESSED_LOT_ISSUES_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, first introduced in release 8.0 and still valid in EBS 12.1.1 and 12.2.2. It belongs to the PO - Purchasing product family and is catalogued in the E-Business Suite Technical Reference Manual (ETRM) with the status VALID. As its name implies, the view exists to surface receiving lot records that remain in the open interface tables and therefore represent unprocessed lot issues. It is not a master data entity; rather it is a diagnostic and reconciliation reporting construct that aggregates pending lot-level receiving activity before the Receiving Transaction Processor (RTP) or the Receiving Open Interface has consumed those rows into permanent inventory and receiving transaction tables.

The view is registered against the RCV_LOTS_INTERFACE and RCV_TRANSACTIONS_INTERFACE interface tables, which are the staging ground for the Receiving Open Interface (ROI). By reporting on data that has not yet been processed, RCV_UNPROCESSED_LOT_ISSUES_V gives supply chain and technical users a window into stuck, failed, or pending receiving transactions at lot granularity. In integration scenarios, particularly where third-party systems or external feeders insert rows into the receiving interface tables, this view is frequently used to monitor queue depth and identify rows that did not reach the processor.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both exposed to the view as synonyms:

  • RCV_LOTS_INTERFACE (SYNONYM) — alias RLI in the view text; holds lot-level detail for receiving interface transactions.
  • RCV_TRANSACTIONS_INTERFACE (SYNONYM) — alias RTI in the view text; holds the header/transaction-type context for each interface transaction.

The two are joined on the shared INTERFACE_TRANSACTION_ID column, which is the logical key linking a lot record to its parent receiving transaction. Because the definition joins the lot interface to the transaction interface, the view can derive net quantities from the transaction type recorded on RTI. The output is grouped by LOT_NUM, ITEM_ID, SHIPMENT_LINE_ID, and PARENT_TRANSACTION_ID, producing one aggregated row per lot-item-shipment-parent combination. This makes the view a consolidated, transaction-flattened representation of otherwise row-level interface data.

Key Columns

The ETRM lists six columns for this view:

  • LOT_NUM — the lot number carried on the interface lot record; the primary identifying attribute for the unprocessed issue.
  • ITEM_ID — inventory item identifier for the lot being received or returned.
  • SHIPMENT_LINE_ID — the shipment line on which the lot is being received; links the issue to the originating purchase order line or shipment.
  • PARENT_TRANSACTION_ID — reference to the parent receiving transaction, used to group related interface rows back to a single logical transaction.
  • PRIMARY_QUANTITY — aggregated primary-unit quantity, computed with DECODE logic so that DELIVER, CORRECT, and RECEIVE add quantity, while RETURN TO RECEIVING and RETURN TO VENDOR subtract it. CORRECT uses SIGN(PRIMARY_QUANTITY) to honour the direction of the correction.
  • QUANTITY — the aggregated secondary-unit quantity, computed with the same DECODE and SIGN logic applied to the QUANTITY column instead of PRIMARY_QUANTITY.

Common Use Cases and Queries

Typical uses include monitoring the Receiving Open Interface for lot receipts that have not yet been processed, investigating why a particular lot is not available in inventory, and validating data feeds from external systems. A basic query listing pending lot issues is:

SELECT lot_num, item_id, shipment_line_id, parent_transaction_id, primary_quantity, quantity FROM apps.rcv_unprocessed_lot_issues_v ORDER BY lot_num;

To focus on a single item, constrain by ITEM_ID; to investigate a specific receipt, constrain by SHIPMENT_LINE_ID or PARENT_TRANSACTION_ID. Because the view aggregates across transaction types, rows with a net zero PRIMARY_QUANTITY indicate that receipts and returns have cancelled out at lot level, a useful signal when reconciling interface exceptions. Users should remember that the view reads only the interface tables; once the Receiving Transaction Processor clears those rows, the records disappear from this view and become visible through standard receiving and inventory inquiry screens instead.