Search Results po_requisition_headers_v




Overview
Explore in AI Chat

Overview

PO_REQUISITION_HEADERS_V is an APPS-owned view in the Oracle E-Business Suite Purchasing (PO) module, documented in ETRM with a status of VALID. Its ETRM description is the terse notation "10SC ONLY - Retrofitted," which indicates that the object was carried over from an earlier documentation baseline and, in the 12.2.2 metadata set, is catalogued primarily to preserve lineage rather than to describe a supported, generally available interface. The view sits on top of the base requisition header entity and presents a denormalized, report-oriented projection of purchase requisition header data — one row per requisition header — enriched with display values that would otherwise require joins and package calls to resolve. Because it exposes preparer names, authorization status display text, document type descriptions, functional currency, computed requisition totals, and the maximum requisition line number, it is oriented toward inquiry screens, concurrent reports, and integration extracts that need human-readable requisition header information in a single query.

Underlying Base Objects

The view is defined over PO_REQUISITION_HEADERS (exposed as a synonym) as its primary driving table, aliased PRH, with ROWID also projected. It joins the following documented base objects:

Because two columns are derived from stored PL/SQL functions, the view's performance and correctness depend on the availability and state of the PO_REQUISITION_HEADERS_PKG and PO_REQ_LINES_SV1 package bodies, not solely on the base table.

Key Columns

Common Use Cases and Queries

Typical usage is requisition header reporting: listing open, incomplete, or cancelled requisitions with preparer names and displayed authorization status, and summarising requisition value by operating unit. Filters should always include ORG_ID for multi-org security.

  • A report of incomplete requisitions by preparer.
  • An extract of requisition totals by currency for ledger reconciliation.
  • An inquiry joining REQUISITION_HEADER_ID to PO_REQUISITION_LINES_ALL for line detail.
  • Workflow monitoring using WF_ITEM_TYPE and WF_ITEM_KEY.

Sample query:

SELECT h.segment1 requisition_number, h.full_name preparer, h.displayed_field auth_status, h.type_name document_type, h.currency_code, h.requisition_header_id FROM po_requisition_headers_v h WHERE h.org_id = :p_org_id AND NVL(h.cancel_flag,'N') = 'N' AND h.authorization_status = 'INCOMPLETE' ORDER BY h.creation_date DESC;

Because Get_Req_Total and Get_Max_Line_Num are invoked per row, restricting the result set before selecting those columns materially improves response time on large requisition volumes.