Skip to content
EBS Reference

PO_REQUISITION_HEADERS_ALL

Schema: POtransactionOU-striped (ORG_ID)

Requisition headers — the requisition number, preparer, type (purchase vs internal), and approval status; where demand enters purchasing before it becomes a PO

Identity
Module: PurchasingOperating-unit striped (ORG_ID)
Notes

SEGMENT1 is the requisition number (same naming collision as the PO number). TRANSFERRED_TO_OE_FLAG marks internal requisitions handed to Order Management as internal sales orders.

What the badges mean
Schema: INV
Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

Structural facts — how the table is partitioned, not a trap by itself

OU-striped (ORG_ID)
Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on ORG_ID, and don’t confuse it with ORGANIZATION_ID (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization (plant or warehouse) via ORGANIZATION_ID — a different partition from OU-striped tables (see the quirks guide).
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

View
This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
In field listings, the Key chip marks a primary-key field.

Header & line

PO_REQUISITION_HEADERS_ALL is the header for its lines in PO_REQUISITION_LINES_ALL.

Fields

12 fields · 1 key

12 fields.

Table fields: position, field name, description, data type, and flags. 12 fields.
#FieldDescriptionTypeFlags
1REQUISITION_HEADER_IDSurrogate key of the requisitionNUMBER
Primary-key field
2ORG_IDOperating unitNUMBER
3SEGMENT1The requisition number — the same naming collision as the PO number; not a flexfieldVARCHAR2
4PREPARER_IDWho prepared the requisitionNUMBER
5TYPE_LOOKUP_CODEPurchase vs internal requisitionVARCHAR2
6AUTHORIZATION_STATUSApproval status — Purchasing's own lookup ladderVARCHAR2
7DESCRIPTIONRequisition descriptionVARCHAR2
8TRANSFERRED_TO_OE_FLAGY once an internal requisition was handed to Order Management as an internal sales orderVARCHAR2
9CLOSED_CODEClosure stateVARCHAR2
10CANCEL_FLAGY when cancelledVARCHAR2
11INTERFACE_SOURCE_CODEThe system that created the requisition — planning, iProcurement, manual…VARCHAR2
12APPROVED_DATEWhen the requisition was approved — the primary analysis dateDATE
The table's primary analysis date — a real DATE column, no conversion needed

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading PO_REQUISITION_HEADERS_ALL on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

7 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <REQUISITION_HEADER_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : PO_REQUISITION_HEADERS_ALL — Requisition headers — the requisition number, preparer, type (purchase vs internal), and approval status; where demand enters purchasing before it becomes a PO
-- Purpose: Column-selected read of PO_REQUISITION_HEADERS_ALL — auto-generated from field metadata
-- Grain  : One row per operating unit (ORG_ID) + REQUISITION_HEADER_ID
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.REQUISITION_HEADER_ID AS "Surrogate key of the requisition",
  t.ORG_ID AS "Operating unit",
  t.SEGMENT1 AS "The requisition number — the same naming collision as the PO number; not a flexfield",
  t.PREPARER_ID AS "Who prepared the requisition",
  t.TYPE_LOOKUP_CODE AS "Purchase vs internal requisition",
  t.AUTHORIZATION_STATUS AS "Approval status — Purchasing's own lookup ladder",
  t.DESCRIPTION AS "Requisition description",
  t.TRANSFERRED_TO_OE_FLAG AS "Y once an internal requisition was handed to Order Management as an internal sales order",
  t.CLOSED_CODE AS "Closure state",
  t.CANCEL_FLAG AS "Y when cancelled",
  t.INTERFACE_SOURCE_CODE AS "The system that created the requisition — planning, iProcurement, manual…",
  t.APPROVED_DATE AS "When the requisition was approved — the primary analysis date"
FROM <catalog>.<schema>.PO_REQUISITION_HEADERS_ALL t
WHERE
  t.ORG_ID = <operating_unit_id>  -- operating unit (MOAC does not filter extracts)
  -- AND t.REQUISITION_HEADER_ID = <REQUISITION_HEADER_ID>
  -- AND t.APPROVED_DATE >= DATE '<DATE_FROM>'
  -- AND t.APPROVED_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.REQUISITION_HEADER_ID;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • OE_DROP_SHIP_SOURCESPO_REQUISITION_HEADERS_ALLforeign key · N:1
    ON OE_DROP_SHIP_SOURCES.REQUISITION_HEADER_ID = PO_REQUISITION_HEADERS_ALL.REQUISITION_HEADER_ID AND OE_DROP_SHIP_SOURCES.ORG_ID = PO_REQUISITION_HEADERS_ALL.ORG_ID
  • PO_REQUISITION_HEADERS_ALLPO_REQUISITION_LINES_ALLheader line · 1:N
    ON PO_REQUISITION_HEADERS_ALL.REQUISITION_HEADER_ID = PO_REQUISITION_LINES_ALL.REQUISITION_HEADER_ID AND PO_REQUISITION_HEADERS_ALL.ORG_ID = PO_REQUISITION_LINES_ALL.ORG_ID
  • MTL_SUPPLYPO_REQUISITION_HEADERS_ALLforeign key · N:1
    ON MTL_SUPPLY.REQ_HEADER_ID = PO_REQUISITION_HEADERS_ALL.REQUISITION_HEADER_ID

Browse more Purchasing tables

More Purchasing tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.