Search Results order_quantity




Overview
Explore in AI Chat

Overview

The RCV_COR_SUP_LOTS_V view is an Oracle E-Business Suite database object owned by the APPS schema and classified under the PO - Purchasing product family. ETRM metadata identifies its description simply as "Retrofitted," indicating that the object was carried forward into the current release to preserve compatibility with earlier customizations or dependent reporting. The view is documented as VALID in both 12.1.1 and 12.2.2 environments.

Functionally, RCV_COR_SUP_LOTS_V presents a consolidated lot-level picture of receiving transactions. Its name — combining receiving (RCV), correction (COR), and supplier lots (SUP_LOTS) — reflects the business scenario it supports: reconciling received lot quantities against lot-issue activity. The most searched column, ORDER_QUANTITY, is an alias for the primary transaction quantity in RCV_LOT_TRANSACTIONS, making the view relevant to quantity-reconciliation reporting rather than to operational processing. Oracle does not publish this view as a supported API; it should be treated as a read-only reporting construct.

Underlying Base Objects

The view is defined over two documented objects. The first, RCV_LOT_TRANSACTIONS, is referenced as a synonym and supplies the driving rows — one row per lot-controlled receiving transaction. The second, RCV_UNPROCESSED_LOT_ISSUES_V, is itself a view that identifies lot issue transactions not yet processed, and it participates in an outer join.

The join condition is significant. The view text connects the two sources on PARENT_TRANSACTION_ID = TRANSACTION_ID, ITEM_ID = ITEM_ID, and LOT_NUM = LOT_NUM, with the Oracle outer-join operator (+) applied to all three columns of RCV_UNPROCESSED_LOT_ISSUES_V. Because the join is outer on the issues side, every qualifying lot transaction in RCV_LOT_TRANSACTIONS is retained even where no corresponding unprocessed lot issue exists; in those cases the LOT_QUANTITY and SHIPMENT_LINE_ID columns return null.

Key Columns

  • LOT_NUMBER — sourced from RLT.LOT_NUM; the supplier lot identifier associated with the receiving transaction.
  • EXPIRATION_DATE — sourced from RLT.EXPIRATION_DATE; the lot expiry recorded at receipt.
  • SHIPMENT_LINE_ID — sourced from RUI.SHIPMENT_LINE_ID; the shipment line linked to the unprocessed lot issue, null when no issue row matches.
  • ITEM_ID — sourced from RLT.ITEM_ID; the inventory item on the transaction.
  • TRANSACTION_ID — sourced from RLT.TRANSACTION_ID; the receiving transaction identifier.
  • ORDER_QUANTITY — an alias for RLT.PRIMARY_QUANTITY; the primary quantity of the lot transaction, expressed in the item's primary unit of measure.
  • LOT_QUANTITY — sourced from RUI.PRIMARY_QUANTITY; the primary quantity recorded against the corresponding unprocessed lot issue.

Common Use Cases and Queries

The view is most often used to compare received lot quantities with pending lot-issue quantities, and to retrieve lot and expiry attributes for a given transaction, item, or shipment line. A typical query filtering on the searched column is:

  • SELECT lot_number, item_id, transaction_id, order_quantity, lot_quantity FROM apps.rcv_cor_sup_lots_v WHERE order_quantity > 0;
  • SELECT lot_number, expiration_date, order_quantity FROM apps.rcv_cor_sup_lots_v WHERE item_id = :item_id AND transaction_id = :transaction_id;
  • SELECT shipment_line_id, order_quantity, lot_quantity, order_quantity - NVL(lot_quantity,0) variance FROM apps.rcv_cor_sup_lots_v WHERE shipment_line_id IS NOT NULL;

Because the join is outer, queries intended to expose only matched issue activity should include WHERE lot_quantity IS NOT NULL. Reports that require lot-level receipt detail combined with pending-issue quantities can join this view to receiving headers or shipment lines using TRANSACTION_ID and SHIPMENT_LINE_ID respectively. As with all retrofit views in the APPS schema, execution should be limited to reporting accounts, and column aliases such as ORDER_QUANTITY should not be assumed stable across upgrades.