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
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Header & line
PO_REQUISITION_HEADERS_ALL is the header for its lines in PO_REQUISITION_LINES_ALL.
Fields
12 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | REQUISITION_HEADER_ID | Surrogate key of the requisition | NUMBER | Key |
| 2 | ORG_ID | Operating unit | NUMBER | |
| 3 | SEGMENT1 | The requisition number — the same naming collision as the PO number; not a flexfield | VARCHAR2 | |
| 4 | PREPARER_ID | Who prepared the requisition | NUMBER | |
| 5 | TYPE_LOOKUP_CODE | Purchase vs internal requisition | VARCHAR2 | |
| 6 | AUTHORIZATION_STATUS | Approval status — Purchasing's own lookup ladder | VARCHAR2 | |
| 7 | DESCRIPTION | Requisition description | VARCHAR2 | |
| 8 | TRANSFERRED_TO_OE_FLAG | Y once an internal requisition was handed to Order Management as an internal sales order | VARCHAR2 | |
| 9 | CLOSED_CODE | Closure state | VARCHAR2 | |
| 10 | CANCEL_FLAG | Y when cancelled | VARCHAR2 | |
| 11 | INTERFACE_SOURCE_CODE | The system that created the requisition — planning, iProcurement, manual… | VARCHAR2 | |
| 12 | APPROVED_DATE | When the requisition was approved — the primary analysis date | DATE | Filter date |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading PO_REQUISITION_HEADERS_ALLon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- 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;7 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <REQUISITION_HEADER_ID>, <DATE_FROM>, <DATE_TO>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
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_IDON 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_IDON MTL_SUPPLY.REQ_HEADER_ID = PO_REQUISITION_HEADERS_ALL.REQUISITION_HEADER_ID