Search Results pos_rcv_transactions_v




Overview
Explore in AI Chat

Overview

POS_RCV_TRANSACTIONS_V is a registered APPS schema view belonging to the POS – iSupplier Portal product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view presents receiving transaction activity in a denormalized, reporting-friendly form. Rather than requiring a caller to join the RCV receipt and transaction tables to purchasing, supplier, item, and HR entities, POS_RCV_TRANSACTIONS_V exposes a single flattened row per receiving transaction, enriched with shipment, purchase order, supplier, item, and receiver attributes. Its documented purpose is simply to "Display Receiving Transactions," and it serves as the primary read model behind iSupplier Portal receiving pages and related reporting extracts.

Because it is a view rather than a table, no storage is allocated to it and no direct DML is permitted. It is intended strictly for query and integration consumption, particularly in self-service supplier-facing flows where a receiving transaction must be rendered together with its originating PO, supplier site, packing slip, and inspection status.

Underlying Base Objects

The view is defined over two logical clusters of objects. The transaction cluster is anchored on RCV_TRANSACTIONS, with RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES supplying receipt header and line context. The purchasing cluster contributes PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_RELEASES_ALL, providing PO number, line, shipment, and release detail. Supplier data is drawn from the PO_VENDORS and PO_VENDOR_SITES_ALL views, while HR and item context come from PER_ALL_PEOPLE_F (receiver name), HR_LOCATIONS_ALL_TL and HR_ALL_ORGANIZATION_UNITS_TL (ship-to locations), and MTL_SYSTEM_ITEMS_KFV (item description and concatenated segments).

Two programmatic dependencies are material: the POS_PO_RCV_QTY package supplies the TRANSACT_QTY value via GET_NET_RECEIVED_QTY, and FND_GLOBAL supplies session context such as organization and user identifiers used to scope the results.

Key Columns

The exposed columns map directly to the documented select list. Transaction identity and type are carried by TRANSACTION_ID, PARENT_TRANSACTION_ID, TRANSACTION_TYPE, and TRANSACTION_DATE. Quantities and units appear as TRANSACT_QTY, TRANSACT_UOM, PRIMARY_UOM, PRIMARY_QUANTITY, and NET_PRIMARY_QUANTITY.

Common Use Cases and Queries

Typical scenarios include inspection-status reporting, supplier receipt confirmation, and reconciliation of received quantities against PO shipments. A query to list pending inspections for a supplier would resemble:

SELECT transaction_id, receipt_num, po_num, po_line, item_desc, transaction_type, transaction_date, inspection_status_code, transact_qty, transact_uom FROM pos_rcv_transactions_v WHERE inspection_status_code = 'PENDING' AND supplier_id = :p_vendor_id ORDER BY transaction_date DESC;

Because TRANSACT_QTY is computed through POS_PO_RCV_QTY, callers should expect a function call per row and should filter aggressively on ORGANIZATION_ID, TRANSACTION_DATE, or supplier identifiers to keep result sets bounded. The view is read-only and should be treated as a reporting surface, not a staging target.