Search Results rcv_enter_receipts_po_v




Overview

The RCV_ENTER_RECEIPTS_PO_V view is an APPS-owned database view in Oracle E-Business Suite, residing in the PO (Purchasing) product module. According to its ETRM documentation it carries the status VALID and is annotated as "10SC ONLY - Retrofitted" — indicating it originated as a customer-specific or release-specific retrofit object rather than a fully generic Receiving view. Its purpose is to present purchasing document lines in a receiving-oriented shape, surfaced within the Receiving interface (the "Enter Receipts" form and the receiving open interface lineage) so that receipt entry, receipt matching, and downstream integration can consume purchase order, release, shipment, and item attributes from a single flat structure.

The view is a UNION-style construct typical of the family of RCV_ENTER_RECEIPTS_*_V views; the PO branch shown generates rows for vendor-sourced purchase order shipments with a literal 'VENDOR' and 'PO' descriptor at the head of the projection. It therefore acts as the PO-document feeder into the unified Receiving data model.

Underlying Base Objects

The view is defined over, or resolves through, the following documented objects as recorded in ETRM 12.2.2:

Key Columns

Common Use Cases and Queries

The view is primarily consumed by the Receiving Enter Receipts form logic and any external interface extracting pending PO shipments for receipt. A representative query retrieving open PO shipments destined for a specific organization is:

SELECT po_header_id, segment1, line_num, shipment_num, vendor_name,
item_number, item_description, quantity, need_by_date,
unit_meas_lookup_code, receiving_routing_id
FROM apps.rcv_enter_receipts_po_v
WHERE ship_to_organization_id = :p_org_id;

Analysts also use it to reconcile expected receipts against RCV_SHIPMENT_HEADERS/RCV_SHIPMENT_LINES, to audit blanket release quantities awaiting receipt, or to feed third-party receiving systems. Because the object is flagged "10SC ONLY - Retrofitted," its availability and exact column set can vary by patch level, so dependent customizations should confirm the view exists and is VALID before use.