Search Results ordered_uom




Overview
Explore in AI Chat

Overview

POR_CONFIRM_INTERNAL_RECEIPT_V is a database view owned by the APPS schema and shipped as part of the Oracle iProcurement (ICX) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its status is VALID in the ETRM repository. The view consolidates information required by the iProcurement internal requisition receiving flow, exposing quantities, need-by dates, shipment references, and unit-of-measure attributes that the receipt confirmation UI and its underlying validation logic depend on.

The view is not a standalone reporting object; it is a runtime dependency of the iProcurement confirm-receipt page, which is invoked when a requester receives goods against an internal (inventory-sourced) requisition. Because internal requisitions source material from another inventory organization rather than from an external supplier, the view joins requisition, order management, receiving, and organization data to produce a single row per eligible requisition line. Practically, it functions as a projection layer that presents the iProcurement receipt confirmation screen with the values it needs without forcing the page to query the base transaction tables directly.

Underlying Base Objects

The view is defined over a set of synonyms and packaged APIs documented in ETRM. The base synonyms include PO_REQUISITION_LINES and PO_REQUISITION_HEADERS, which supply the requisition line detail and header segment used to link to the sales order; OE_ORDER_HEADERS and OE_ORDER_LINES, which provide the internal sales order number and its originating system references; RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES, which link the requisition line to its shipment; MTL_UNITS_OF_MEASURE, which supplies the UOM class; HR_ALL_ORGANIZATION_UNITS_TL, which supplies the destination organization name in the user's language; and PO_SYSTEM_PARAMETERS, which supplies the order source identifier.

Two packaged objects are referenced: POR_RCV_TRANSACTION_SV, invoked through GET_SHIPMENT_NUM to derive the shipment number for the requisition line, and PO_CORE_S2, referenced through PO_SYSTEM_PARAMETERS processing. Joins are largely inner joins keyed on requisition line, order line, and shipment line identifiers, with outer joins applied to the unit-of-measure and organization name lookups. The driving filter restricts rows to internal requisitions whose delivered quantity has not exhausted the ordered quantity.

Key Columns

Common Use Cases and Queries

The primary use case is the iProcurement internal receipt confirmation page, which reads eligible lines before the requester posts the receipt. Secondary uses include reconciliation reports that compare ordered versus delivered quantities on internal requisitions and diagnostics that trace a requisition line to its shipment and sales order.

A typical query filtering on the searched column is:

SELECT ORDERED_QTY, ORDERED_UOM, QUANTITY_DELIVERED, EXPECTED_RECEIPT_QTY FROM APPS.POR_CONFIRM_INTERNAL_RECEIPT_V WHERE ORDERED_UOM = :p_uom;

To review all outstanding internal receipts for a destination organization:

SELECT TO_ORGANIZATION_ID, ITEM_ID, ORDERED_QTY, QUANTITY_DELIVERED, NEED_BY_DATE FROM APPS.POR_CONFIRM_INTERNAL_RECEIPT_V WHERE TO_ORGANIZATION_ID = :p_org ORDER BY NEED_BY_DATE;

Because the view returns a broad projection of requisition, order, and shipment attributes, ad-hoc queries should always restrict by organization, item, or requisition line to avoid full scans across the joined base objects.