Skip to content
Fusion Reference

PO_HEADERS_ALL

Product: POtransactionBU-striped (PRC_BU_ID)

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

Notes

SEGMENT1 is the PO number — a naming collision with key flexfields, not a flexfield (Oracle's unique index PO_HEADERS_U2 makes it unique only with the document type plus the sold-to legal entity SOLDTO_LE_ID for STANDARD orders, or the procurement BU PRC_BU_ID for every other type - so the same number can repeat across legal entities and BUs; join on PO_HEADER_ID). 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
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

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.PurchasingDocumentHeaderExtractPVO
    OTBI: 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 (opens in new tab)

Fields

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1PO_HEADER_IDSurrogate key of the purchasing documentNUMBER
Key
2SEGMENT1The visible PO number — a naming collision with flexfields, unique only with the document type plus SOLDTO_LE_ID (standard orders) or PRC_BU_ID (all other types), per Oracle's PO_HEADERS_U2 index; join on PO_HEADER_IDVARCHAR2
3PRC_BU_IDProcurement business unit that owns the document — Fusion's named BU stripeNUMBER
4REQ_BU_IDRequisitioning business unit the order was raised forNUMBER
5SOLDTO_LE_IDSold-to legal entityNUMBER
6BILLTO_BU_IDBill-to business unit — note the spelling, no underscore in BILLTONUMBER
7TYPE_LOOKUP_CODEDocument type (standard, blanket, contract…)VARCHAR2
8DOCUMENT_STATUSHeader-level document status — there is no CLOSED_CODE in FusionVARCHAR2
9VENDOR_IDSupplier on the documentNUMBER
10VENDOR_SITE_IDSupplier site the document is placed againstNUMBER
11AGENT_IDBuyer on the documentNUMBER
12CURRENCY_CODEDocument currencyVARCHAR2
13RATECurrency conversion rateNUMBER
14APPROVED_FLAGY when the current revision is approvedVARCHAR2
15APPROVED_DATELast approval dateDATE
Filter date
16CLOSED_DATEDate the document was closedDATE
17CANCEL_FLAGY when the document is cancelledVARCHAR2
18REVISION_NUMDocument revision counterNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of PO_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

7 parameters not filled: <catalog>, <schema>, <PRC_BU_ID>, <PO_HEADER_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- 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 the document type plus SOLDTO_LE_ID (standard orders) or PRC_BU_ID (all other types), per Oracle's PO_HEADERS_U2 index; join on PO_HEADER_ID",
  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
  t.PRC_BU_ID = <PRC_BU_ID>  -- business unit — this table stripes by a NAMED BU column, not ORG_ID; see quirks guide #all-means-bu
  -- 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;

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

  • PO_HEADERS_ALLPO_LINES_ALLheader line · 1:N
    ON PO_HEADERS_ALL.PO_HEADER_ID = PO_LINES_ALL.PO_HEADER_ID
  • PO_HEADERS_ALLPOZ_SUPPLIERSforeign key · N:1
    ON PO_HEADERS_ALL.VENDOR_ID = POZ_SUPPLIERS.VENDOR_ID
  • PO_HEADERS_ALLPOZ_SUPPLIER_SITES_ALL_Mforeign key · N:1
    ON PO_HEADERS_ALL.VENDOR_SITE_ID = POZ_SUPPLIER_SITES_ALL_M.VENDOR_SITE_ID
  • PO_HEADERS_ALLFUN_ALL_BUSINESS_UNITS_Vforeign key · N:1
    ON PO_HEADERS_ALL.PRC_BU_ID = FUN_ALL_BUSINESS_UNITS_V.BU_ID
  • POR_REQUISITION_LINES_ALLPO_HEADERS_ALLforeign key · N:1
    ON POR_REQUISITION_LINES_ALL.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_ID
  • AP_INVOICE_LINES_ALLPO_HEADERS_ALLforeign key · N:1
    ON AP_INVOICE_LINES_ALL.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_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.