Results for “requisition_num”

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

Overview

ICX_PO_REQUISITION_HEADERS_V is a reporting and integration 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 from the purchasing schema in a form adapted to the iProcurement inquiry and display requirements. The view is documented as VALID in both 12.1.1 and 12.2.2 and carries the description "Requisition Headers View."

Functionally, the view presents one row per requisition header, drawing from PO_REQUISITION_HEADERS and enriching it with derived values such as a decoded cancellation flag, a formatted requisition total, a preparer name, a displayed authorization status, a document type description, and a reserved-funds indicator. The view is defined with a ROWID-based ROW_ID column, which allows Oracle Forms-based iProcurement screens and other consumers to perform optimistic locking and navigate to the base header row. Because it is a view rather than a table, it performs no storage of its own; all values are resolved at query time against requester context and system setup.

Underlying Base Objects

The view is defined over PO_REQUISITION_HEADERS (exposed through an APPS synonym) as its primary driver, with PRH serving as the table alias in the view text. It joins and references a broad set of supporting objects documented in the ETRM 12.2.2 metadata: PO_ACTION_HISTORY, PO_DOCUMENT_TYPES and PO_LOOKUP_CODES for document type and status display; GL_SETS_OF_BOOKS (SOB) for the functional currency; FINANCIALS_SYSTEM_PARAMETERS for ledger context; and the HR_EMPLOYEES and HR_PERSON_NAME views together with the HR_GENERAL, HR_SECURITY and FND_GLOBAL packages to resolve the preparer's full name. FND_LOOKUPS, FND_PROFILE and FND_CURRENCY provide lookup values, profile option values and currency formatting. Two PL/SQL packages supply computed columns: PO_REQS_INQ_SV (GET_RESERVED_FLAG) and PO_REQUISITION_HEADERS_PKG (GET_REQ_TOTAL).

Key Columns

• REQUISITION_HEADER_ID — Primary key of the underlying requisition header, used to join to lines and distributions.
• REQUISITION_NUM — Exposed from PRH.SEGMENT1; the user-visible requisition number.
• ROW_ID — The ROWID of the base PO_REQUISITION_HEADERS row, supporting update and locking.
• AUTHORIZATION_STATUS / AUTHORIZATION_STATUS_DSP — The stored status code and its displayed (translated) value from the lookup.
• CANCEL_FLAG — Derived via DECODE to 'Y' when the authorization status is 'CANCELLED', else NULL.
• CLOSED_CODE — NVL-adjusted so a NULL stored closed code is presented as 'OPEN'.
• REQ_HEADER_AMOUNT / CURRENCY_CODE — The requisition total returned by PO_REQUISITION_HEADERS_PKG.GET_REQ_TOTAL, formatted using the ledger currency's format mask.
• PREPARER_ID / PREPARER_NAME — The creator identifier and the resolved HR full name.
• RESERVED_FLAG — Result of PO_REQS_INQ_SV.GET_RESERVED_FLAG, indicating whether funds are reserved.
• DOCUMENT_TYPE_DSP — Descriptive name from PO_DOCUMENT_TYPES for the requisition document type.
• TYPE_LOOKUP_CODE, ENABLED_FLAG, ON_LINE_FLAG, PREPARER_FINISHED_FLAG, RESEARCH_COMPLETE_FLAG, SUMMARY_FLAG, TRANSFERRED_TO_OE_FLAG — Status and control flags used by iProcurement workflows.
• SEGMENT2 through SEGMENT5, ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — Descriptive flexfield and key flexfield segment values.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID — Standard WHO and concurrent program audit columns.

Common Use Cases and Queries

The view is typically used to report requisition header status, values and ownership without needing to reconstruct the display logic that iProcurement applies. A representative query lists open requisitions with formatted amounts:

• SELECT requisition_num, preparer_name, authorization_status_dsp, req_header_amount, currency_code FROM apps.icx_po_requisition_headers_v WHERE NVL(closed_code,'OPEN') = 'OPEN' ORDER BY creation_date DESC;
• SELECT requisition_header_id, requisition_num, cancel_flag, reserved_flag, document_type_dsp FROM apps.icx_po_requisition_headers_v WHERE authorization_status = 'IN PROCESS';
• SELECT requisition_num, req_header_amount, segment2, attribute1 FROM apps.icx_po_requisition_headers_v WHERE preparer_id = :p_preparer_id AND creation_date >= :p_from_date;

Performance considerations apply: because REQ_HEADER_AMOUNT and RESERVED_FLAG are PL/SQL functions executed per row, queries filtering on those derived columns force function evaluation across candidate rows and should be avoided in large extracts. Filtering on indexed base columns such as REQUISITION_HEADER_ID, PREPARER_ID or CREATION_DATE is preferable. As with all APPS views, the view is subject to row-level security through HR_SECURITY and MO/operating unit profiles, so results reflect the responsibility's access.