Skip to content
Fusion Reference

POR_REQUISITION_HEADERS_ALL

Product: PORtransaction

Requisition headers — the requisition number, preparer, status, and justification; where demand enters procurement before it becomes a purchase order

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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

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 →

Fields

12 fields · 2 key

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 segmentVARCHAR2
Key
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. 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.

Query parameters
-- ============================================================
-- 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

  • 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 Procurementtables →

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.