Search Results icx_po_req_lines_v




Overview
Explore in AI Chat

Overview

ICX_PO_REQ_LINES_V is an APPS-owned database view in Oracle E-Business Suite that presents requisition line information for Oracle iProcurement. It is a denormalized, presentation-oriented view: rather than exposing raw purchasing tables directly, it joins requisition line data to line types, hazard classes, United Nations numbers, HR organizations, locations, and currencies so that the iProcurement UI and its related inquiries can render a complete requisition line without issuing multiple joins per row. The view carries a status of VALID in both 12.1.1 and 12.2.2 and is defined on the PO schema synonyms that underlie Oracle Purchasing requisitions.

The view is primarily consumed by iProcurement pages that display, edit, or re-display requisition lines, and by reporting or integration routines that need requisition line detail in a single query. Because it is a view rather than a table, it inherits the security and row-level behavior of the underlying tables and does not persist data.

Underlying Base Objects

The view is defined chiefly over PO_REQUISITION_LINES (synonym for PO.PO_REQUISITION_LINES) aliased PRL, with PO_LINE_TYPES (PLT) supplying the line type description, and a set of lookup and reference tables that enrich the output. Documented base objects include:

Key Columns

Core identifiers include REQUISITION_HEADER_ID, REQUISITION_LINE_ID, LINE_NUM, and LINE_TYPE_ID. Quantities and pricing are represented by QUANTITY, QUANTITY_RECEIVED, QUANTITY_DELIVERED, QUANTITY_CANCELLED, UNIT_PRICE, and the formatted DISPLAY_UNIT_PRICE derived through FND_CURRENCY.GET_FORMAT_MASK.

Destination and sourcing columns include DESTINATION_TYPE_CODE, SOURCE_TYPE_CODE, DESTINATION_SUBINVENTORY, SOURCE_SUBINVENTORY, DELIVER_TO_LOCATION_ID, and TO_PERSON_ID, the latter expanded through PO_INQ_SV.GET_PERSON_NAME. Supplier suggestion columns include SUGGESTED_VENDOR_NAME, SUGGESTED_VENDOR_LOCATION, SUGGESTED_VENDOR_CONTACT, and SUGGESTED_VENDOR_PRODUCT_CODE.

Of particular interest to users searching on purchasing_agent_id, the view exposes SUGGESTED_BUYER_ID, which is the requisition-line reference to the suggested purchasing agent, along with its resolved person name via PO_INQ_SV.GET_PERSON_NAME(PRL.SUGGESTED_BUYER_ID). The purchasing agent field on the requisition header is represented in the base tables; within this view the agent relationship is surfaced through the buyer suggestion column rather than a literal PURCHASING_AGENT_ID column name. Currency context is provided by CURRENCY_CODE, RATE, RATE_TYPE, and RATE_DATE.

Common Use Cases and Queries

Typical uses include iProcurement requisition line displays, non-catalog request reviews, and custom reports that list open requisition lines with supplier and buyer suggestions.

Listing requisition lines with suggested buyer information:

  • SELECT requisition_header_id, requisition_line_id, line_num, item_description, quantity, unit_price, suggested_buyer_id, suggested_vendor_name FROM apps.icx_po_req_lines_v WHERE suggested_buyer_id = :p_agent_id;

Retrieving lines for a requisition by need-by date:

  • SELECT line_num, item_description, need_by_date, quantity, display_unit_price FROM apps.icx_po_req_lines_v WHERE requisition_header_id = :p_header_id ORDER BY line_num;

Reviewing destination and inventory routing detail:

  • SELECT line_num, destination_type_code, destination_subinventory, organization_name, location_code FROM apps.icx_po_req_lines_v WHERE requisition_header_id = :p_header_id;

Because the view calls PL/SQL functions and joins several HR and GL objects, queries should filter on indexed requisition identifiers where possible, and joins to HR security should be respected so that organization-restricted rows are not exposed to unauthorized users.