Skip to content
Fusion Reference

PO_HEADERS_ALL

Product: POtransaction

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 (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.
In field listings, K marks a primary-key field.

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 →

Fields

18 fields · 1 key

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 PRC_BU_ID + document typeVARCHAR2
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_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  : 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

  • 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

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.