Results for “req_distribution_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.POR_RCV_REQ_ITEMS_V is a VALID view owned by the APPS schema and associated with the ICX – Oracle iProcurement product family. It presents purchasing and requisition line detail in a flattened, receipt-ready format, exposing the requisition, purchase order, release, shipment, distribution, supplier, and item attributes needed to support receiving and expected-receipt reporting across Oracle EBS 12.1.1 and 12.2.2.

The view's most operationally significant output is EXPECTED_RECEIPT_QTY, computed as NVL((POD.QUANTITY_ORDERED - NVL(POD.QUANTITY_CANCELLED, 0) - NVL(POD.QUANTITY_DELIVERED, 0)), 0). This expression derives the open, still-receivable quantity on each distribution. The driving WHERE clause applies the same logic — (POD.QUANTITY_ORDERED - NVL(POD.QUANTITY_DELIVERED, 0) - NVL(POD.QUANTITY_CANCELLED, 0)) > 0 — so the view returns only lines with a positive outstanding receipt balance. As a result it functions as a ready-made "what remains to be received" data set, supporting iProcurement receipt pages, receiving dashboards, and downstream integration extracts without requiring consumers to re-derive the netting logic.

Underlying Base Objects

The view is defined over a join of requisition, purchasing, and supplier entities. Documented referenced base objects include PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, PO_REQ_DISTRIBUTIONS, PO_HEADERS_ALL, PO_LINES_TRX_V, PO_LINE_LOCATIONS_TRX_V, PO_DISTRIBUTIONS_TRX_V, PO_RELEASES_ALL, PO_VENDORS (view), PO_VENDOR_SITES_ALL (view), MTL_UNITS_OF_MEASURE, MTL_SYSTEM_ITEMS, RCV_SHIPMENT_LINES, PO_SYSTEM_PARAMETERS, HR_ALL_ORGANIZATION_UNITS_TL, and the packages FND_GLOBAL, OE_ORDER_IMPORT_INTEROP_PUB, and PO_CLM_INTG_GRP.

The view text shows direct joins from PO_REQUISITION_HEADERS and PO_REQUISITION_LINES through PO_REQ_DISTRIBUTIONS to PO_DISTRIBUTIONS, PO_LINES, PO_HEADERS, PO_LINE_LOCATIONS, PO_RELEASES, MTL_UNITS_OF_MEASURE, PO_VENDORS, and PO_VENDOR_SITES. The documented metadata also references the transaction views PO_LINES_TRX_V, PO_LINE_LOCATIONS_TRX_V, and PO_DISTRIBUTIONS_TRX_V, which supply the multi-org and transaction-aware line data in 12.2.2. RCV_SHIPMENT_LINES contributes shipment context through POR_RCV_TRANSACTION_SV.GET_SHIPMENT_NUM('PO', POLL.LINE_LOCATION_ID), returned in the RCV_SHIPMENT_NUMBER column.

Key Columns

• EXPECTED_RECEIPT_QTY — open quantity remaining to be received, net of delivered and cancelled quantities.
• ORDERED_QTY, QUANTITY_DELIVERED — ordered and already-delivered quantities on the distribution.
• EXPECTED_RECEIPT_DATE — NVL(POLL.PROMISED_DATE, POLL.NEED_BY_DATE); NEED_BY_DATE and PROMISED_DATE are also exposed separately.
• PO_HEADER_ID, PO_NUMBER, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_RELEASE_NUMBER, PO_LINE_NUMBER, PO_SHIPMENT_NUMBER, PO_NUM_REL_NUM — purchase order and release identifiers.
• REQ_HEADER_ID, REQ_NUMBER, REQ_LINE_ID, REQ_DISTRIBUTION_ID — requisition linkage.
• REQUESTOR_ID — NVL(POD.DELIVER_TO_PERSON_ID, POH.AGENT_ID).
• ITEM_ID, ITEM_DESCRIPTION, PRIMARY_UOM, UOM_CLASS, VENDOR_PRODUCT_NUM.
• VENDOR_ID, SOURCE, VENDOR_SITE_ID, SUPPLIER_SITE.
• TO_ORGANIZATION_ID, SHIP_TO_ORGANIZATION_ID, SHIP_TO_LOCATION_ID, DELIVER_TO_LOCATION_ID, RECEIPT_DATE, USSGL_TRANSACTION_CODE, PO_DISTRIBUTION_ID.

Common Use Cases and Queries

Typical uses include outstanding-receipt lists for buyers, expected-receipt feeds, and iProcurement receiving displays.

-- Open expected receipts by PO
SELECT po_number, po_line_number, item_description,
       expected_receipt_qty, expected_receipt_date
FROM   apps.por_rcv_req_items_v
WHERE  po_number = :p_po_number;

-- Total expected receipt quantity by item
SELECT item_id, SUM(expected_receipt_qty) expected_qty
FROM   apps.por_rcv_req_items_v
GROUP  BY item_id;