Search Results closed_code_dsp




Overview
Explore in AI Chat

Overview

APPS.ICX_PO_REQ_HEADERS_V is a reporting and inquiry view over Oracle Purchasing requisition header data, exposed in the Internet Computing Architecture (ICX) schema used by Oracle iProcurement and related self-service applications. In Oracle EBS 12.1.1 and 12.2.2 it provides a denormalized, display-ready projection of purchase requisition headers, joining the base requisition table to lookups, document type definitions, employee name resolution, set of books currency information, and several PL/SQL server-side functions that compute derived values at query time. The view is not a stored table; every column is resolved when the query executes, which means its cost is dominated by the packaged function calls embedded in the SELECT list.

Its principal role is to support requisition search, summary, and status displays without requiring callers to replicate the join and decoding logic used by the purchasing forms. The column list deliberately mixes raw identifiers (REQUISITION_HEADER_ID, PREPARER_ID, SEGMENT1 through SEGMENT5) with presentation columns (PREPARER_NAME, AUTHORIZATION_STATUS_DSP, DOCUMENT_TYPE_DSP, CLOSED_CODE_DSP, CANCEL_DSP) so that a single query can drive both a result table and its drill-down.

Underlying Base Objects

The view is defined over PO_REQUISITION_HEADERS (referenced through a synonym) as its driving table, aliased PRH in the view text. It joins GL_SETS_OF_BOOKS to obtain the functional currency code used for amount formatting, FND_LOOKUPS for lookup meanings, PO_DOCUMENT_TYPES for the document type display name, and HR_EMPLOYEES for the preparer's full name, with HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages applied for name formatting and security. Additional supporting objects include FINANCIALS_SYSTEM_PARAMETERS, PO_LOOKUP_CODES, HR_EMPLOYEES, and the FND_GLOBAL, FND_CURRENCY, FND_PROFILE, and PO_REQUISITION_HEADERS_PKG packages. Derived values come from PO_REQS_INQ_SV and PO_REQUISITION_HEADERS_PKG.

Key Columns

Common Use Cases and Queries

Typical usages include iProcurement requisition summary pages, approval and funds-check reporting, and custom operational reports that must reconcile requisitions against reservations. Because several columns invoke PL/SQL, filtering on RESERVED_FLAG in the WHERE clause forces the function to execute for each candidate row; restricting by REQUISITION_HEADER_ID or a date range first materially improves performance. It is also advisable to select only the columns required, since REQ_HEADER_AMOUNT and RESERVED_FLAG are the costliest.

SELECT requisition_num,
       description,
       preparer_name,
       authorization_status_dsp,
       reserved_flag,
       req_header_amount,
       currency_code
  FROM apps.icx_po_req_headers_v
 WHERE requisition_header_id = :req_header_id;

SELECT requisition_num,
       preparer_name,
       req_header_amount
  FROM apps.icx_po_req_headers_v
 WHERE start_date_active >= :from_date
   AND reserved_flag = 'Y';

In 12.1.1 and 12.2.2 the definition is materially identical; differences observed between environments generally reflect patch level rather than release, so any query built against this view should be validated against the target instance's compiled view text.