POR_REQUISITION_HEADERS_ALL
Product: PORtransactionRequisition 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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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 →
Fields
12 fields · 2 key
| # | 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 | VARCHAR2 | Key |
| 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. 2 key fields.
Boilerplate SQL
Starting point for reading the BICC-landed copy of POR_REQUISITION_HEADERS_ALLon 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.
-- ============================================================
-- 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 + REQUISITION_NUMBER
-- 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",
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
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.REQUISITION_HEADER_ID = <REQUISITION_HEADER_ID>
-- AND t.REQUISITION_NUMBER = '<REQUISITION_NUMBER>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.REQUISITION_HEADER_ID;5 parameters not filled: <catalog>, <schema>, <REQUISITION_HEADER_ID>, <REQUISITION_NUMBER>, <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 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