Search Results transaction_type_dsp




Overview

APPS.POR_RCV_RETURN_TO_VENDOR_V is a reporting view within Oracle E-Business Suite (validated on 12.1.1 and 12.2.2) owned by the APPS schema and catalogued under the ICX – Oracle iProcurement product group. Its documented purpose is to present receipt transactions that represent items being returned to a supplier (vendor), consolidating receiving, purchasing, and inventory attributes into a single denormalized result set. In practice the view is consumed by iProcurement return-to-vendor flows, RCV (Receiving) self-service pages, and downstream reporting or integration layers that need a purpose-built projection of returnable receipt lines rather than the raw RCV_TRANSACTIONS table.

The view can be used to identify which receipt quantities remain eligible for return and to retrieve the full documentary context of the originating order, requisition, and shipment. Users searching for a shelf_days column will not find it here; shelf-life calculations are not part of this view's definition. Shelf-life days typically derive from MTL_SYSTEM_ITEMS_B.SHELF_LIFE_CODE and MTL_ITEM_LOCATIONS/lot attributes, so any shelf-day logic must be added by joining to those objects rather than queried directly from POR_RCV_RETURN_TO_VENDOR_V.

Underlying Base Objects

The view is defined over a join of receiving, purchasing, inventory, and HR objects. Documented referenced base objects include:

Because it depends on HR security and MO/operating-unit views, query results can be filtered implicitly by the responsibility's organization and personnel security profile.

Key Columns

Common Use Cases and Queries

Typical scenarios include building a list of returnable receipt lines in iProcurement, deriving remaining returnable quantity, and reconciling returns against purchase orders. A representative query follows:

  • SELECT transaction_id, receipt_num, line_num, item_description, quantity, vendor_id, po_header_id, organization_id, transaction_date FROM apps.por_rcv_return_to_vendor_v WHERE vendor_id = :p_vendor_id AND organization_id = :p_org ORDER BY transaction_date DESC;
  • To reconcile against the order: SELECT v.quantity, v.quantity_ordered, v.po_unit_price, v.currency_code FROM apps.por_rcv_return_to_vendor_v v WHERE v.po_line_location_id = :p_line_location_id;

Where shelf life is required, join the view to MTL_SYSTEM_ITEMS_B and lot/serial attributes; the view itself exposes no shelf-day measure. Always constrain by organization and, where RLS applies, rely on the embedded HR security packages to limit results.