Search Results po_requisition_headers_n3

Overview

PO.PO_REQUISITION_HEADERS_ALL is the master header table in the Oracle Purchasing (PO) schema that stores one row for every internal requisition created in Oracle E-Business Suite. It represents the top level of the requisition model, corresponding to the Header region of the Requisitions window, and is populated whenever a user or an external source — such as Purchasing, iProcurement, or an interface program — creates a requisition. In Oracle EBS 12.1.1 and 12.2.2 the table is owned by the PO schema, resides in the APPS_TS_TX_DATA tablespace, contains 94 documented columns, and carries a status of VALID. It is one of three core tables (header, lines, and distributions) that together describe a complete requisition document, and it participates in the Oracle Workflow approval process, the purchasing document region, and downstream order creation.

Based on the heuristic Data Vault classification derived from the foreign-key structure, this object is modeled as a hub. It serves as the anchor point for the requisition number and requisition header identifier, with surrounding tables acting as links and satellites that reference it.

Key Information Stored

The table is anchored by the surrogate primary key REQUISITION_HEADER_ID, which is a system-generated, internally used value invisible to end users. Two unique indexes define business-key candidates: PO_REQUISITION_HEADERS_U1 on REQUISITION_HEADER_ID, and PO_REQUISITION_HEADERS_U2 on the combination of SEGMENT1, ORG_ID, and REVISION_NUM. SEGMENT1 is the human-readable requisition number seen in forms and reports; Oracle Purchasing generates it via PO_UNIQUE_IDENTIFIER_CONTROL when automatic numbering is enabled.

• REQUISITION_HEADER_ID — surrogate primary key and internal document identifier.
• SEGMENT1 — the visible requisition number, a unique business-key component.
• PREPARER_ID — the employee or user who created the requisition; indexed via PO_REQUISITION_HEADERS_N1.
• ORG_ID — the operating unit that owns the requisition, part of multi-org security and U2.
• AUTHORIZATION_STATUS — approval state of the header; indexed via PO_REQUISITION_HEADERS_N3.
• TYPE_LOOKUP_CODE — requisition type (purchase or internal).
• DESCRIPTION and NOTE_TO_AUTHORIZER — free-text justification and approver notes.
• CLOSED_CODE and CANCEL_FLAG — lifecycle/closure indicators.
• CREATION_DATE — creation timestamp, indexed via PO_REQUISITION_HEADERS_N2.
• REVISION_NUM — supports conformed and amended requisitions.
• WF_ITEM_TYPE / WF_ITEM_KEY — Oracle Workflow linkage; indexed via PO_REQUISITION_HEADERS_N5.
• CONFORMED_HEADER_ID and CONTRACTOR_STATUS — conformed requisition linkage and contractor requisition handling.

Common Use Cases and Queries

Typical usage includes requisition status reporting, approval-cycle analysis, purchasing KPI dashboards, and integration of external sourcing systems. A representative query joins the header to its lines:

SELECT prh.segment1, prh.authorization_status, prl.line_num, prl.item_description
FROM po_requisition_headers_all prh
JOIN po_requisition_lines_all prl
  ON prh.requisition_header_id = prl.requisition_header_id
WHERE prh.org_id = :p_org_id
  AND prh.authorization_status = 'APPROVED';

Other scenarios include tracking requisitions awaiting approval via AUTHORIZATION_STATUS, identifying preparer activity using PREPARER_ID and CREATION_DATE, and reconciling open requisitions by CLOSED_CODE for period-end.

Related Objects

The table is a hub referenced by many dependent objects through REQUISITION_HEADER_ID:

• PO_REQUISITION_LINES_ALL — child lines sharing REQUIREISITION_HEADER_ID.
• PO_REQUISITIONS_INTERFACE_ALL — staging interface for inbound requisitions.
• PO_ACTION_HISTORY and PO_NOTIFICATIONS_ALL — reference the header through OBJECT_ID.
• PO_HISTORY_REQUISITIONS_ALL — archived requisition data joined on SEGMENT1.
• OE_DROP_SHIP_SOURCES and SO_DROP_SHIP_SOURCES — drop-ship sourcing references.
• PON_BACKING_REQUISITIONS and PON_AWARD_ALLOCATIONS — sourcing and award linkages.
• MTL_SUPPLY and RCV_SUPPLY — supply/demand planning references via REQ_HEADER_ID.