Search Results note_to_agent




Overview
Explore in AI Chat

Overview

POR_HEADER_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite, defined against the Oracle iProcurement (ICX) product. It is documented in ETRM as the "Requisition Header View." The view presents a denormalized, presentation-ready projection of requisition header data drawn from the purchasing tables at the core of the iProcurement and Purchasing stack. Its purpose is to expose requisition header attributes already translated into their display values — authorization status, document state, cancellation, and requisition type are all resolved to their lookup meanings rather than stored codes — so that iProcurement pages, Oracle Workflow notification content, and custom reports can consume requisition headers without repeatedly joining the lookup tables themselves.

Because the view surfaces the WF_ITEM_TYPE and WF_ITEM_KEY columns from PO_REQUISITION_HEADERS, it is directly relevant to the search term "workflow_item_key." These columns hold the Oracle Workflow item type and item key associated with the requisition approval process, allowing callers to correlate a requisition header with its live workflow instance and to invoke Workflow APIs such as WF_ENGINE.Item_Key or construct notification lookups from within a query on this view.

Underlying Base Objects

The documented base objects for the view are: PO_REQUISITION_HEADERS (SYNONYM), PO_REQUISITION_LINES (SYNONYM), PO_LOOKUP_CODES (VIEW), HR_EMPLOYEES (VIEW), AP_CARDS (SYNONYM), and the FND_GLOBAL, FND_PROFILE, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages. Functionally, PO_REQUISITION_HEADERS is the driving table, aliased PRH. PO_LOOKUP_CODES is joined four times to decode AUTHORIZATION_STATUS, CLOSED_CODE, CANCEL_FLAG, and TYPE_LOOKUP_CODE. HR_EMPLOYEES is joined on PREPARER_ID = EMPLOYEE_ID to obtain the preparer's full name. AP_CARDS is an outer join on PCARD_ID for procurement card details. PO_REQUISITION_LINES is outer-joined on REQUISITION_HEADER_ID, which means header rows are retained even when no line rows exist.

Key Columns

  • REQUISITION_HEADER_ID — primary key of the requisition header, used to join to lines, distributions, and workflow.
  • SEGMENT1 — the user-visible requisition number.
  • PREPARER_ID / FULL_NAME — the preparer's employee identifier and resolved name.
  • AUTHORIZATION_STATUS, CANCEL_FLAG, CLOSED_CODE (via NVL to 'OPEN') — decoded status fields, each accompanied by a DISPLAYED_FIELD from PO_LOOKUP_CODES.
  • WF_ITEM_TYPE, WF_ITEM_KEY — the Oracle Workflow item type and item key for the requisition approval workflow; WF_ITEM_KEY corresponds to the workflow_item_key used when querying workflow tables and calling Workflow APIs.
  • ORG_ID — operating unit, enforcing multi-org security in queries.
  • PCARD_ID, CARD_NUMBER, DESCRIPTION — procurement card association, populated through the outer join to AP_CARDS.
  • LAST_UPDATE_DATE and CREATION_DATE — formatted with TO_CHAR, with the creation date mask driven by the ICX_DATE_FORMAT_MASK profile option.

Common Use Cases and Queries

Typical uses include iProcurement requisition search and detail pages, workflow notification bodies that must display requisition context, and custom extracts that report requisition status by operating unit. A common pattern is to locate the workflow instance for a requisition:

  • SELECT REQUISITION_HEADER_ID, SEGMENT1, WF_ITEM_TYPE, WF_ITEM_KEY, AUTHORIZATION_STATUS FROM APPS.POR_HEADER_V WHERE SEGMENT1 = :requisition_number;
  • SELECT SEGMENT1, FULL_NAME, PLC_AUTH_DISPLAY FROM APPS.POR_HEADER_V WHERE ORG_ID = :org_id AND AUTHORIZATION_STATUS = 'APPROVED';

Because the date columns are already formatted in the view, applications reading POR_HEADER_V should not re-apply TO_CHAR masks. Queries should generally filter on ORG_ID to respect operating unit security, and joins against PO_REQUISITION_LINES should account for the outer join built into the view definition.