Search Results source_doc_uom




Overview

The APPS.POS_RCV_RETURNS_V view is a reporting object within the Oracle E-Business Suite iSupplier Portal (POS) module. Its documented purpose is to display returns for shipments, consolidating receipt transaction data with shipment header, shipment line, purchasing, and supplier information into a single queryable structure. In EBS 12.1.1 and 12.2.2 the view serves as a denormalized presentation layer that allows both internal reporting and iSupplier Portal integration components to retrieve return-related shipment transactions without directly joining the underlying Receiving (RCV) and Purchasing (PO) base tables.

The view is owned by the APPS schema and is documented as VALID. It exposes return transaction records through a wide column projection that spans organization, transaction, sourcing, supplier, and purchasing dimensions. This makes it suitable for supplier-facing returns reporting, receipt reconciliation, and downstream integration extracts.

Underlying Base Objects

The view is defined over the core Receiving tables — RCV_TRANSACTIONS, RCV_SHIPMENT_HEADERS, and RCV_SHIPMENT_LINES — which supply the transaction and shipment grain. Purchase order context is provided by PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_RELEASES_ALL. Supplier data is drawn from PO_VENDORS, PO_VENDOR_SITES_ALL, and related vendor site views.

Supporting master and reference data comes from MTL_SYSTEM_ITEMS_KFV (item information), MTL_TRANSACTION_REASONS (return reasons), HR_LOCATIONS_ALL and ORG_ORGANIZATION_DEFINITIONS (ship-to locations and organizations), PER_ALL_PEOPLE_F (receiver names), and HR_ALL_ORGANIZATION_UNITS_TL. The view also references the POS_PO_RCV_QTY package for computed quantity values, and security/context packages (FND_GLOBAL, HR_SECURITY, HR_GENERAL) that enforce organization and user access. The package POS_PO_RCV_QTY is central to the view's computed columns, invoking GET_RECEIVE_RCV for received quantities and GET_NET_QTY for net primary quantities.

Key Columns

Common Use Cases and Queries

The view is typically queried to list supplier returns against shipments, to reconcile returned quantities with received quantities, and to report exceptions flagged on receipts. A representative query retrieves returns for a given organization, filtering on the exception flag:

SELECT transaction_id, transaction_date, transaction_type, transact_qty, transact_uom, item_desc, supplier, supplier_site, receipt_num, receipt_exception_flag FROM apps.pos_rcv_returns_v WHERE organization_id = :org_id AND receipt_exception_flag IS NOT NULL ORDER BY transaction_date DESC;

Another common pattern joins or filters by shipment to support iSupplier Portal return views:

SELECT shipment_header_id, shipment_line_id, po_num, po_line, rma_reference, net_primary_quantity FROM apps.pos_rcv_returns_v WHERE shipment_header_id = :header_id;

In integration scenarios the view is used as a read-only staging source to extract return transactions for external systems, relying on the pre-computed POS_PO_RCV_QTY columns to avoid re-deriving net quantities. Because the view embeds HR security and organization context packages, queries are automatically restricted according to the session's organization and security profile, which should be considered when scheduling background reports.