Search Results icx_po_late_receipts_v




Overview
Explore in AI Chat

Overview

ICX_PO_LATE_RECEIPTS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the ICX (Oracle iProcurement) product family. Its documented purpose is to expose "Overdue Receipts" — purchase order shipment or line-location records where a receipt is expected but has not yet been fully recorded against the demanded or promised date. The view is a reporting and integration artifact rather than a transactional entity; it does not store data of its own and cannot be updated directly.

The view serves as the data source behind iProcurement features that surface late or outstanding receipts to requesters, buyers, and receiving personnel. Because it joins purchasing, receiving-quantity, vendor, and human-resources location information into a single flattened result set, it is well suited to inquiry screens, concurrent reporting, and custom extracts. The presence of QUANTITY_ACCEPTED among its columns is significant: it allows consumers to distinguish quantities that have been both received and accepted from those merely received or still outstanding, which supports accurate three-way match and accrual reporting. In 12.1.1 and 12.2.2 the view retains a VALID status and its definition is essentially unchanged across the two releases.

Underlying Base Objects

The view is defined primarily over PO_LINE_LOCATIONS (aliased PLL), which supplies the shipment-level attributes, and it is enriched by joins to PO_HEADERS (POH), PO_RELEASES (POR), PO_LINES, PO_LINE_TYPES, and PO_DOCUMENT_TYPES. Vendor data is obtained from PO_VENDORS, PO_VENDOR_SITES, and PO_VENDOR_CONTACTS, while ship-to location codes come from HR_LOCATIONS (HRL). Supporting objects include FINANCIALS_SYSTEM_PARAMETERS, MTL_SYSTEM_ITEMS_KFV, and the packages FND_GLOBAL, HR_GENERAL, and PO_INQ_SV. PO_INQ_SV.GET_PERSON_NAME is called to resolve buyer (agent) identifiers into display names, and DECODE logic across PO_RELEASE_ID determines whether the row pertains to a standard purchase order or a release against a blanket agreement.

Key Columns

The view exposes the full line-location attribute set with several derived values. Central columns include:

Common Use Cases and Queries

Typical scenarios include overdue-receipt dashboards, buyer follow-up lists, and reconciliation of received versus accepted quantities. Because QUANTITY_ACCEPTED is available alongside QUANTITY_RECEIVED, reports can isolate shipments where goods arrived but failed to progress through inspection.

A representative query for outstanding receipts is:

SELECT po_header_id, line_location_id, segment1, vendor_name, need_by_date, quantity, quantity_received, quantity_accepted, quantity_rejected FROM apps.icx_po_late_receipts_v WHERE closed_code = 'OPEN' AND quantity_received < quantity - NVL(quantity_cancelled,0) AND need_by_date < SYSDATE ORDER BY need_by_date;

To flag quantities received but not yet accepted, an analyst can filter on quantity_accepted < quantity_received. The view is equally applicable to receipt-required analysis (receipt_required_flag = 'Y') and to buyer-specific workload review using the resolved agent name column.