PO_HEADERS_ALL
Product: POtransactionPurchasing 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
SEGMENT1 is the PO number — a naming collision with key flexfields, not a flexfield (unique only with PRC_BU_ID + document type, so PO numbers repeat across BUs). The BU stripe is the NAMED column PRC_BU_ID (procurement BU), with REQ_BU_ID (requisitioning) and BILLTO_BU_ID alongside — no literal ORG_ID. Status is DOCUMENT_STATUS; there is no CLOSED_CODE.
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
PO_HEADERS_ALL is the header for its lines in PO_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.PoBiccExtractAM.PurchasingDocumentHeaderExtractPVOOTBI: Procurement - Purchasing Real TimeOTBI: Procurement - Procure To Pay Real Time
Purchasing Document Headers data store — keyed on PoHeaderId; covers purchase orders AND agreements in one store. From the Procurement extract book (oadpr).
Oracle data-store documentation →
Fields
18 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | PO_HEADER_ID | Surrogate key of the purchasing document | NUMBER | Key |
| 2 | SEGMENT1 | The visible PO number — a naming collision with flexfields, unique only with PRC_BU_ID + document type | VARCHAR2 | |
| 3 | PRC_BU_ID | Procurement business unit that owns the document — Fusion's named BU stripe | NUMBER | |
| 4 | REQ_BU_ID | Requisitioning business unit the order was raised for | NUMBER | |
| 5 | SOLDTO_LE_ID | Sold-to legal entity | NUMBER | |
| 6 | BILLTO_BU_ID | Bill-to business unit — note the spelling, no underscore in BILLTO | NUMBER | |
| 7 | TYPE_LOOKUP_CODE | Document type (standard, blanket, contract…) | VARCHAR2 | |
| 8 | DOCUMENT_STATUS | Header-level document status — there is no CLOSED_CODE in Fusion | VARCHAR2 | |
| 9 | VENDOR_ID | Supplier on the document | NUMBER | |
| 10 | VENDOR_SITE_ID | Supplier site the document is placed against | NUMBER | |
| 11 | AGENT_ID | Buyer on the document | NUMBER | |
| 12 | CURRENCY_CODE | Document currency | VARCHAR2 | |
| 13 | RATE | Currency conversion rate | NUMBER | |
| 14 | APPROVED_FLAG | Y when the current revision is approved | VARCHAR2 | |
| 15 | APPROVED_DATE | Last approval date | DATE | Filter date |
| 16 | CLOSED_DATE | Date the document was closed | DATE | |
| 17 | CANCEL_FLAG | Y when the document is cancelled | VARCHAR2 | |
| 18 | REVISION_NUM | Document revision counter | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of PO_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 : PO_HEADERS_ALL — Purchasing 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
-- Purpose: Column-selected read of PO_HEADERS_ALL — auto-generated from field metadata
-- Grain : One row per PO_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.PO_HEADER_ID AS "Surrogate key of the purchasing document",
t.SEGMENT1 AS "The visible PO number — a naming collision with flexfields, unique only with PRC_BU_ID + document type",
t.PRC_BU_ID AS "Procurement business unit that owns the document — Fusion's named BU stripe",
t.REQ_BU_ID AS "Requisitioning business unit the order was raised for",
t.SOLDTO_LE_ID AS "Sold-to legal entity",
t.BILLTO_BU_ID AS "Bill-to business unit — note the spelling, no underscore in BILLTO",
t.TYPE_LOOKUP_CODE AS "Document type (standard, blanket, contract…)",
t.DOCUMENT_STATUS AS "Header-level document status — there is no CLOSED_CODE in Fusion",
t.VENDOR_ID AS "Supplier on the document",
t.VENDOR_SITE_ID AS "Supplier site the document is placed against",
t.AGENT_ID AS "Buyer on the document",
t.CURRENCY_CODE AS "Document currency",
t.RATE AS "Currency conversion rate",
t.APPROVED_FLAG AS "Y when the current revision is approved",
t.APPROVED_DATE AS "Last approval date",
t.CLOSED_DATE AS "Date the document was closed",
t.CANCEL_FLAG AS "Y when the document is cancelled",
t.REVISION_NUM AS "Document revision counter"
FROM <catalog>.<schema>.PO_HEADERS_ALL t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.PO_HEADER_ID = <PO_HEADER_ID>
-- AND t.APPROVED_DATE >= DATE '<DATE_FROM>'
-- AND t.APPROVED_DATE <= DATE '<DATE_TO>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.PO_HEADER_ID;6 parameters not filled: <catalog>, <schema>, <PO_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 PO_HEADERS_ALL.PO_HEADER_ID = PO_LINES_ALL.PO_HEADER_IDON PO_HEADERS_ALL.VENDOR_ID = POZ_SUPPLIERS.VENDOR_IDON PO_HEADERS_ALL.VENDOR_SITE_ID = POZ_SUPPLIER_SITES_ALL_M.VENDOR_SITE_IDON PO_HEADERS_ALL.PRC_BU_ID = FUN_ALL_BUSINESS_UNITS_V.BU_IDON POR_REQUISITION_LINES_ALL.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_ID