Results for “closed_code_dsp”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ICX_PO_REQ_HEADERS_V is a view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ICX (Oracle iProcurement) product family. It exposes requisition header information sourced primarily from the Purchasing requisition schema, presented in a denormalized form suitable for iProcurement requisition inquiry, authorization workflow, and reporting. The view description is documented as "Requisition Headers View."

Because the view already joins in lookup display values, employee name resolution, currency formatting, and package-driven calculations, it is a convenient read model for extensions, custom reports, and integrations that need requisition header data without reimplementing the Purchasing decoding logic. It is available in both 12.1.1 and 12.2.2, and its status is documented as VALID in ETRM.

Underlying Base Objects

ETRM documents the following referenced base objects: FINANCIALS_SYSTEM_PARAMETERS (synonym), FND_CURRENCY (package), FND_GLOBAL (package), FND_LOOKUPS (view), FND_PROFILE (package), GL_SETS_OF_BOOKS (view), HR_EMPLOYEES (view), HR_GENERAL (package), HR_PERSON_NAME (package), HR_SECURITY (package), PO_DOCUMENT_TYPES (synonym), PO_LOOKUP_CODES (view), PO_REQS_INQ_SV (package), PO_REQUISITION_HEADERS (synonym), and PO_REQUISITION_HEADERS_PKG (package).

The central driving table is PO_REQUISITION_HEADERS (aliased PRH in the view text). FND_LOOKUPS and PO_LOOKUP_CODES supply decoded meanings such as authorization status and closed code display values. HR_EMPLOYEES, HR_PERSON_NAME, HR_GENERAL, and HR_SECURITY resolve the preparer's full name while honoring HR security. GL_SETS_OF_BOOKS and FND_CURRENCY supply the ledger currency code and its format mask, used for the formatted requisition total. PO_REQS_INQ_SV and PO_REQUISITION_HEADERS_PKG provide routine-driven values such as the reserved flag and requisition total. PO_DOCUMENT_TYPES resolves the document type name.

Key Columns

• REQUISITION_HEADER_ID — primary key of the requisition header; drives package calls within the view.
• REQUISITION_NUM (SEGMENT1) — the user-visible requisition number; SEGMENT2 through SEGMENT5 are also exposed.
• AUTHORIZATION_STATUS / AUTHORIZATION_STATUS_DSP — the internal status code and its displayed lookup value used by iProcurement workflow.
• NOTE_TO_AUTHORIZER — free-text note entered by the preparer for the approver; a key column for approval-related reporting.
• PREPARER_ID / PREPARER_NAME — the preparer's employee identifier and resolved full name.
• REQ_HEADER_AMOUNT / CURRENCY_CODE — the formatted requisition header total and ledger currency, sourced via PO_REQUISITION_HEADERS_PKG and FND_CURRENCY.
• RESERVED_FLAG — indicates whether funds are reserved, computed by PO_REQS_INQ_SV.
• CANCEL_FLAG — derived as 'Y' when AUTHORIZATION_STATUS is 'CANCELLED'.
• CLOSED_CODE_DSP — decoded closed status meaning.
• DOCUMENT_TYPE_DSP — document type name from PO_DOCUMENT_TYPES.
• Flags — ON_LINE_FLAG, PRELIMINARY_RESEARCH_FLAG, PREPARER_FINISHED_FLAG, RESEARCH_COMPLETE_FLAG, SUMMARY_FLAG, TRANSFERRED_TO_OE_FLAG, and ENABLED_FLAG.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — the standard DFF columns, plus WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent program columns.

Common Use Cases and Queries

Typical uses include approval-cycle reporting, preparer productivity analysis, and custom OAF or BI Publisher reports. A basic inquiry listing requisitions awaiting approval with authorizer notes:

SELECT requisition_num, preparer_name, authorization_status_dsp,
       note_to_authorizer, req_header_amount, currency_code
  FROM apps.icx_po_req_headers_v
 WHERE authorization_status = 'IN PROCESS'
 ORDER BY requisition_num;

Reporting on canceled requisitions is simplified by CANCEL_FLAG:

SELECT requisition_num, preparer_name, authorization_status_dsp
  FROM apps.icx_po_req_headers_v
 WHERE cancel_flag = 'Y';

Aggregating approved value by preparer:

SELECT preparer_id, preparer_name,
       SUM(REQ_HEADER_AMOUNT) total_amt, COUNT(*) req_count
  FROM apps.icx_po_req_headers_v
 WHERE authorization_status = 'APPROVED'
 GROUP BY preparer_id, preparer_name;

Because the view calls PL/SQL packages per row, queries should filter on indexed columns in PO_REQUISITION_HEADERS (for example REQUISITION_HEADER_ID or SEGMENT1) where possible to avoid function evaluation across the full result set.