Results for “po_requisition_headers_inq_v”

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

Overview

PO_REQUISITION_HEADERS_INQ_V is an APPS-owned inquiry view in the Oracle E-Business Suite Purchasing (PO) module. The ETRM documentation marks its status as VALID and describes it with the terse annotation "10SC ONLY - Retrofitted," indicating that the object originated as a customer-specific or localized retrofit rather than a standard out-of-the-box Oracle deliverable. In the context of EBS 12.1.1 and 12.2.2, it remains a read-only projection whose purpose is to expose purchase requisition header data together with descriptive lookup and document-type information, sparing report writers from repeatedly joining those reference objects manually.

The view is primarily a reporting and inquiry construct. It does not store data; every row returned is derived at runtime from PO_REQUISITION_HEADERS and several supporting reference objects. Because it resolves the authorization status display and the requisition document subtype name, it is suited to concurrent programs, custom forms, OAF pages, and ad-hoc SQL where a human-readable requisition header listing is required.

Underlying Base Objects

The documented TETRM metadata identifies the following referenced objects, all accessed through APPS synonyms:

• PO_REQUISITION_HEADERS (SYNONYM) — the driving table, aliased PRH in the view text; supplies virtually all transactional columns.
• PO_DOCUMENT_TYPES_ALL_B (SYNONYM) — the base document type definition, aliased PODB, restricted to DOCUMENT_TYPE_CODE = 'REQUISITION'.
• PO_DOCUMENT_TYPES_ALL_TL (SYNONYM) — the translated document type table, aliased PODT, supplying TYPE_NAME filtered by the session language.
• PO_LOOKUP_CODES (VIEW) — aliased PLC_STA, resolving the AUTHORIZATION STATUS lookup and its DISPLAYED_FIELD.
• FND_GLOBAL (PACKAGE) — referenced for USERENV('LANG') language resolution used to constrain the translated table.

Joins are established on authorization status versus lookup code, and on the requisition TYPE_LOOKUP_CODE matching the document subtype, with ORG_ID and language predicates applied to the document type tables.

Key Columns

The view exposes the requisition header primary key REQUISITION_HEADER_ID and the ROWID, together with descriptive attributes such as DESCRIPTION, SEGMENT1 through SEGMENT5 (the requisition number and descriptive flexfield segments), and ATTRIBUTE_CATEGORY with ATTRIBUTE1 through ATTRIBUTE15.

Status-related columns include AUTHORIZATION_STATUS, an NVL-wrapped CLOSED_CODE defaulting to 'OPEN', ENABLED_FLAG, ON_LINE_FLAG, and a DECODE that returns 'Y' when the authorization status is 'CANCELLED'. Document classification is provided by TYPE_LOOKUP_CODE and the joined PODT.TYPE_NAME. The view also surfaces the DISPLAYED_FIELD from PO_LOOKUP_CODES, which is the column historically associated with the search term "document_type_dsp" — it presents the descriptive alias for the status lookup.

Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the concurrent manager columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID) are included, as are ORGANIZATION_ID and SECURITY_LEVEL_CODE from PO_DOCUMENT_TYPES_ALL_B.

Common Use Cases and Queries

Typical uses include requisition status dashboards, approval workflow reporting, and reconciliation extracts where the descriptive document type name and the displayed authorization status field are required without additional joins.

• Listing open requisitions by organization with a readable status.
• Reporting requisitions by document subtype name.
• Identifying cancelled requisitions using the derived cancellation flag.
• Auditing requisition creation and last update activity.

A representative query follows:

SELECT requisition_header_id, segment1, description, type_name, displayed_field, authorization_status, organization_id FROM apps.po_requisition_headers_inq_v WHERE authorization_status IS NULL OR authorization_status <> 'CANCELLED' AND organization_id = :p_org_id ORDER BY creation_date DESC;

Because the view depends on PO_LOOKUP_CODES and the document type tables, results are sensitive to lookup configuration, the requisition subtype setup, and the session language; missing setup in any of these areas can suppress rows. The "10SC ONLY" annotation also warrants caution before reuse in a standard 12.2.2 instance, where the retrofit may not be supported or certified.