POR_REQUISITION_HEADERS_ALL
Product: PORtransactionBU-striped (REQ_BU_ID)Requisition headers — the requisition number, preparer, status, and justification; where demand enters procurement before it becomes a purchase order
Owned by Self Service Procurement (POR), a different product family than the PO tables. The EBS-isms are gone: the number is a real REQUISITION_NUMBER column (no SEGMENT1) and the status is DOCUMENT_STATUS (no AUTHORIZATION_STATUS). REQ_BU_ID is the requisitioning business unit.
What the badges mean
- Product: EGP
- Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
- BU-striped (ORG_ID)
- Rows are scoped to a business unit. The column is still named
ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization via
ORGANIZATION_ID— always pair it withINVENTORY_ITEM_IDon item-level joins (see the quirks guide). - Set / ledger / named-BU striped
- Some tables stripe by a named column instead of
ORG_ID: reference data set (SET_ID— see the quirks guide), ledger (LEDGER_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned. - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart of the key. Join without a window filter and every fact multiplies by history (see the quirks guide). - View
- This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Header & line
POR_REQUISITION_HEADERS_ALL is the header for its lines in POR_REQUISITION_LINES_ALL.
Extract access
The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.
- FscmTopModelAM.PrcExtractAM.PorBiccExtractAM.RequisitionHeaderExtractPVOOTBI: Procurement - Requisitions Real TimeOTBI: Procurement - Procure To Pay Real Time
Requisition Headers data store — keyed on RequisitionHeaderId; note the separate PorBiccExtractAM path (Self Service Procurement).
Oracle data-store documentation (opens in new tab)
Fields
12 fields · 1 key
12 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | REQUISITION_HEADER_ID | Surrogate key of the requisition | NUMBER | Key |
| 2 | REQUISITION_NUMBER | The visible requisition number — a real column, not a flexfield segment; Oracle documents it only in non-unique indexes (even with REQ_BU_ID), so it is not a key here | VARCHAR2 | |
| 3 | REQ_BU_ID | Requisitioning business unit | NUMBER | |
| 4 | PRC_BU_ID | Procurement business unit | NUMBER | |
| 5 | PREPARER_ID | Employee who created the requisition | NUMBER | |
| 6 | DESCRIPTION | Requisition description | VARCHAR2 | |
| 7 | DOCUMENT_STATUS | Requisition status — no AUTHORIZATION_STATUS in Fusion | VARCHAR2 | |
| 8 | APPROVED_DATE | Approval timestamp | TIMESTAMP | |
| 9 | SUBMISSION_DATE | When submitted for approval | TIMESTAMP | |
| 10 | JUSTIFICATION | Note to the approver | VARCHAR2 | |
| 11 | FUNDS_STATUS | Overall budgetary-control status | VARCHAR2 | |
| 12 | INTERFACE_SOURCE_CODE | Source system when loaded via requisition import | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of POR_REQUISITION_HEADERS_ALL on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
5 parameters not filled: <catalog>, <schema>, <REQ_BU_ID>, <REQUISITION_HEADER_ID>, <watermark>
-- ============================================================
-- Table : POR_REQUISITION_HEADERS_ALL — Requisition headers — the requisition number, preparer, status, and justification; where demand enters procurement before it becomes a purchase order
-- Purpose: Column-selected read of POR_REQUISITION_HEADERS_ALL — auto-generated from field metadata
-- Grain : One row per REQUISITION_HEADER_ID
-- Notes : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. 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.REQUISITION_NUMBER AS "The visible requisition number — a real column, not a flexfield segment; Oracle documents it only in non-unique indexes (even with REQ_BU_ID), so it is not a key here",
t.REQ_BU_ID AS "Requisitioning business unit",
t.PRC_BU_ID AS "Procurement business unit",
t.PREPARER_ID AS "Employee who created the requisition",
t.DESCRIPTION AS "Requisition description",
t.DOCUMENT_STATUS AS "Requisition status — no AUTHORIZATION_STATUS in Fusion",
t.APPROVED_DATE AS "Approval timestamp",
t.SUBMISSION_DATE AS "When submitted for approval",
t.JUSTIFICATION AS "Note to the approver",
t.FUNDS_STATUS AS "Overall budgetary-control status",
t.INTERFACE_SOURCE_CODE AS "Source system when loaded via requisition import"
FROM <catalog>.<schema>.POR_REQUISITION_HEADERS_ALL t
WHERE
t.REQ_BU_ID = <REQ_BU_ID> -- business unit — this table stripes by a NAMED BU column, not ORG_ID; see quirks guide #all-means-bu
-- AND t.REQUISITION_HEADER_ID = <REQUISITION_HEADER_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.REQUISITION_HEADER_ID;Verified September 2026 · docs release 26C
Column names differ in BICC extracts — see PVO header drift.
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
ON POR_REQUISITION_HEADERS_ALL.REQUISITION_HEADER_ID = POR_REQUISITION_LINES_ALL.REQUISITION_HEADER_IDON POR_REQUISITION_HEADERS_ALL.REQ_BU_ID = FUN_ALL_BUSINESS_UNITS_V.BU_ID
More Procurement tables
- POR_REQUISITION_LINES_ALLRequisition lines — item, quantity, price, need-by date, destination org, and suggested supplier per line; carries the keys of the resulting PO header, line, and schedule once sourced
- POZ_SUPPLIER_SITES_ALL_MSupplier sites — the transactable endpoints purchase orders and payments point at, one row per supplier address per procurement business unit, with purchasing/pay/RFQ purpose flags and payment defaults
- POZ_SUPPLIERSThe supplier master — one row per supplier with the supplier number, type, business relationship level, and tax attributes, backed by the trading community architecture through its party id
- PO_DISTRIBUTIONS_ALLPO accounting distributions — how each schedule's quantity charges out: destination type and org, deliver-to, the GL charge account, project costing columns, and the requisition distribution it fulfills
- PO_HEADERS_ALLPurchasing document headers — one row per purchase order or agreement (standard, blanket, contract), with supplier, buyer, currency, and the document status; striped by the procurement business unit
- PO_LINE_LOCATIONS_ALLPO schedules — one row per shipment schedule (or blanket price break) with need-by/promised dates and the system-maintained received/accepted/rejected/billed quantity buckets; the workhorse grain for open-PO analytics