Search Results po_headers_inq_rel_v




Overview
Explore in AI Chat

Overview

PO_HEADERS_INQ_REL_V is a Purchasing (PO) inquiry view owned by the APPS schema in Oracle E-Business Suite, delivered as a retrofitted object in both 12.1.1 and 12.2.2. Rather than exposing a single table, the view presents a union-style projection of blanket purchase agreement releases (from PO_RELEASES) joined to their parent documents (from PO_HEADERS_ALL), materializing the release as a header-like row. The literal 'RELEASE' constant in the SELECT list distinguishes these rows from header-level records when the view is consumed alongside its sibling inquiry views.

The view exists primarily to support Purchasing inquiry forms, Flexfields, and reporting that must present blanket release information using the same column shape as a purchase order header. It exposes the release's rowid as its key, enabling tools such as Oracle Forms and OA Framework to treat a release as an addressable header record. The heavily NVL-wrapped columns (for example NVL(POR.CLOSED_CODE,'OPEN'), NVL(POR.FROZEN_FLAG,'N'), and NVL(POR.AUTHORIZATION_STATUS,'INCOMPLETE')) guarantee deterministic output for records where the underlying release columns are null, which is important for inquiry screens and LOV queries that filter on status.

Underlying Base Objects

The view is defined over PO_RELEASES (aliased POR) as the driving row source, joined to PO_HEADERS_ALL (aliased POH) on the blanket agreement. The documented base objects further include AP_SUPPLIER_CONTACTS, AP_TERMS, HR_LOCATIONS_ALL_TL, HZ_PARTIES, PO_DOCUMENT_TYPES_ALL_B, PO_DOCUMENT_TYPES_ALL_TL, PO_VENDORS, and PO_VENDOR_SITES_ALL, together with the FND_GLOBAL package. These are supplied through the inquiry attribute set to resolve supplier, site, contact, terms, and document-type descriptions, and to supply the current operating unit and user context via FND_GLOBAL. Because PO_VENDORS and PO_VENDOR_SITES_ALL are themselves views, the supplier dimension is resolved through the standard supplier inquiry layer common to 12.1.1 and 12.2.2.

Key Columns

Common Use Cases and Queries

The principal use case is inquiry reporting on blanket releases filtered by closure status. The following query lists open releases against their blanket agreements:

  • SELECT po_header_id, segment1, vendor_id, closed_code, authorization_status FROM apps.po_headers_inq_rel_v WHERE closed_code = 'OPEN';
  • SELECT po_header_id, closed_date, amount_limit FROM apps.po_headers_inq_rel_v WHERE closed_code = 'CLOSED' AND closed_date >= SYSDATE - 30;
  • SELECT segment1, SUM(amount_limit) FROM apps.po_headers_inq_rel_v WHERE authorization_status = 'APPROVED' GROUP BY segment1;

Because CLOSED_CODE is defaulted, queries need not guard against nulls. For lookup-driven screens, join the exposed value to FND_LOOKUPS on lookup type CLOSED_CODE to obtain the closed_code_dsp display value. All queries should be executed with an appropriate MO or operating unit context, since the underlying base objects are secured through the standard Purchasing inquiry layer.