Search Results to_person_id




Overview
Explore in AI Chat

Overview

ICX_PO_REQUISITION_OPEN_V is an APPS-owned database view in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2) that exposes open requisition lines created through Oracle iProcurement (ICX). Its documented description is "Open Requisition Lines View." The view denormalizes requisition line data from the purchasing tables into a single flattened projection suitable for iProcurement's requisition review, approval, and tracking screens, as well as for custom reporting and integration extracts.

The view is critical in the requisition lifecycle: it presents quantity, pricing, delivery, sourcing, and status information for lines that are still open (not fully received, delivered, cancelled, or closed). Because it resolves display values — currency formatting, person names, organization names, locations, and item flexfield concatenations — it is typically embedded directly into OA Framework pages and concurrent report queries rather than joined again at runtime.

Underlying Base Objects

The view is defined over PO_REQUISITION_LINES (aliased PRL) as its primary source, joined to PO_REQUISITION_HEADERS, PO_LINE_TYPES (PLT), PO_LINES, MTL_SYSTEM_ITEMS (MSI), MTL_CATEGORIES_KFV (MCA), ORG_ORGANIZATION_DEFINITIONS (OOD1), HR_LOCATIONS (HRL1), PO_VENDORS, GL_SETS_OF_BOOKS (GSOB), GL_DAILY_CONVERSION_TYPES (GDT), and PO_LOOKUP_CODES. It also references PO_DOCUMENT_TYPES.

Server-side logic is supplied by the packages FND_CURRENCY (amount format masks), FND_GLOBAL (session/org context), HR_GENERAL, HR_SECURITY (person and location security), ICX_GET, ICX_UTIL (item flexfield rendering), and PO_INQ_SV (person name resolution). The presence of HR_SECURITY indicates that row-level filtering respects the user's HR security profile.

Key Columns

Common Use Cases and Queries

Typical uses include requisition tracking dashboards, buyer worklists, and custom extracts keyed to the requester or buyer person. Because the user searched for to_person_id, the most common query pattern filters or joins on that column.

  • List open requisition lines for a specific requester:
SELECT requisition_header_id, requisition_line_id, line_num,
       item_description, quantity, to_person_id,
       po_inq_sv.get_person_name(to_person_id) requester,
       need_by_date, closed_code
FROM   apps.icx_po_requisition_open_v
WHERE  to_person_id = :p_person_id;
  • Count open lines by requester within an operating unit:
SELECT to_person_id,
       po_inq_sv.get_person_name(to_person_id) requester,
       COUNT(*) open_lines,
       SUM(quantity) total_qty
FROM   apps.icx_po_requisition_open_v
GROUP  BY to_person_id;
  • Join to the requisition header for header-level attributes (note that HR_SECURITY filtering applies to the person and location columns).

Because the view executes packaged functions per row, high-volume extracts should filter aggressively on requisition identifiers or to_person_id rather than scanning the full result set.