Search Results net_primary_quantity




Overview
Explore in AI Chat

Overview

ICX_RCV_TRANSACTIONS_V is an APPS-owned database view in Oracle E-Business Suite, delivered under the ICX (Oracle iProcurement) product family. Its documented description is "Receipt Lines View." The view consolidates receiving transaction detail with the associated receipt line, shipment header, purchasing document, supplier, and employee information into a single denormalized projection, which allows iProcurement and downstream reporting components to present receipt information without repeatedly joining the RCV, PO, and HR schemas.

The view carries a VALID status and is present in both Oracle EBS 12.1.1 and 12.2.2. It is defined over synonyms and views owned by APPS, including RCV_TRANSACTIONS, RCV_SHIPMENT_LINES, RCV_SHIPMENT_HEADERS, PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_RELEASES, PO_VENDORS, and HR_LOCATIONS. Because it is a view rather than a table, it exposes no independent storage; all values are derived at query time from the underlying base objects.

Underlying Base Objects

The documented referenced base objects are: FINANCIALS_SYSTEM_PARAMETERS, FND_GLOBAL, FND_PROFILE, HR_EMPLOYEES, HR_GENERAL, HR_LOCATIONS, HR_PERSON_NAME, HR_SECURITY, MTL_SYSTEM_ITEMS_KFV, MTL_TRANSACTION_REASONS, ORG_ORGANIZATION_DEFINITIONS, PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_LOOKUP_CODES, PO_RELEASES, PO_VENDORS, PO_VENDOR_SITES, RCV_ROUTING_HEADERS, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS. The core of the view is the join between RCV_TRANSACTIONS (receiving transaction events) and RCV_SHIPMENT_LINES (receipt line quantities), with RCV_SHIPMENT_HEADERS supplying receipt-level attributes such as receipt number and packing slip. Purchasing context is obtained through PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, and PO_RELEASES, while PO_VENDORS and PO_VENDOR_SITES provide supplier and supplier site names. HR objects supply receiver and ship-to location information, and MTL_TRANSACTION_REASONS supplies the reason name. FND_GLOBAL, FND_PROFILE, and HR_SECURITY are used for session and security context.

Key Columns

The view exposes a broad set of aliased columns. Transaction-level attributes include TRANSACTION_ID, TRANSACTION_TYPE, TRANSACTION_DATE, TRANSACT_QTY (from RT.QUANTITY), TRANSACT_UOM, PRIMARY_UOM, and PRIMARY_QUANTITY. The column the user searched for, NET_PRIMARY_QUANTITY, is aliased from RSL.QUANTITY_RECEIVED on RCV_SHIPMENT_LINES, representing the net quantity received on the receipt line in the item's primary unit of measure.

Common Use Cases and Queries

Typical uses include receipt inquiry screens, iProcurement receipt line display, supplier performance reporting, and reconciliation of received versus ordered quantities. Because NET_PRIMARY_QUANTITY is derived from QUANTITY_RECEIVED, it is frequently used to report net receipts by item, supplier, or PO line.

Example query:

SELECT receipt_num,
       po_num,
       po_line,
       item_desc,
       transaction_date,
       net_primary_quantity,
       primary_uom,
       supplier,
       receiver
  FROM apps.icx_rcv_transactions_v
 WHERE net_primary_quantity > 0
   AND transaction_date >= SYSDATE - 30;

Result sets can be grouped by SUPPLIER or ITEM_ID to obtain net received quantities, or filtered by DESTINATION_TYPE to distinguish inventory receipts from expense and WIP destinations. Joins back to MTL_SYSTEM_ITEMS_KFV by ITEM_ID and to PO_HEADERS by PO_HEADER_ID remain valid, although the view already surfaces many of those attributes directly.