Skip to content
Fusion Reference

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

Identity
Module: ProcurementBU-striped (REQ_BU_ID)
Notes

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.

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

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 with INVENTORY_ITEM_ID on 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_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in 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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part 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.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

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.RequisitionHeaderExtractPVO
    OTBI: 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.

Table fields: position, field name, description, data type, and flags. 12 fields.
#FieldDescriptionTypeFlags
1REQUISITION_HEADER_IDSurrogate key of the requisitionNUMBER
Key
2REQUISITION_NUMBERThe 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 hereVARCHAR2
3REQ_BU_IDRequisitioning business unitNUMBER
4PRC_BU_IDProcurement business unitNUMBER
5PREPARER_IDEmployee who created the requisitionNUMBER
6DESCRIPTIONRequisition descriptionVARCHAR2
7DOCUMENT_STATUSRequisition status — no AUTHORIZATION_STATUS in FusionVARCHAR2
8APPROVED_DATEApproval timestampTIMESTAMP
9SUBMISSION_DATEWhen submitted for approvalTIMESTAMP
10JUSTIFICATIONNote to the approverVARCHAR2
11FUNDS_STATUSOverall budgetary-control statusVARCHAR2
12INTERFACE_SOURCE_CODESource system when loaded via requisition importVARCHAR2

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.

Query parameters

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

  • POR_REQUISITION_HEADERS_ALLPOR_REQUISITION_LINES_ALLheader line · 1:N
    ON POR_REQUISITION_HEADERS_ALL.REQUISITION_HEADER_ID = POR_REQUISITION_LINES_ALL.REQUISITION_HEADER_ID
  • POR_REQUISITION_HEADERS_ALLFUN_ALL_BUSINESS_UNITS_Vforeign key · N:1
    ON POR_REQUISITION_HEADERS_ALL.REQ_BU_ID = FUN_ALL_BUSINESS_UNITS_V.BU_ID

Browse more Procurement tables

More Procurement 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 Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.