Skip to content
EBS Reference

PO_HEADERS_ALL

Schema: POtransactionOU-striped (ORG_ID)

Purchasing document headers — one row per purchase order, agreement, quotation, or RFQ (seven document types share the table), with supplier, buyer, currency, approval status, and closure state; operating-unit striped

Module: PurchasingOperating-unit striped (ORG_ID)
Notes

SEGMENT1 is the PO number — a naming collision with key flexfields, not a flexfield (the physical unique key is SEGMENT1 + document type + ORG_ID, so PO numbers repeat across operating units). Status columns decode through Purchasing's own lookup table, not the generic FND one.

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema 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.

Fields

17 fields · 1 key

Table fields: position, field name, description, data type, and flags. 17 fields.
#FieldDescriptionTypeFlags
1PO_HEADER_IDSurrogate key of the purchasing document headerNUMBER
Key
2ORG_IDOperating unit — PO numbers are unique only within it (plus document type)NUMBER
3SEGMENT1The PO number — a naming collision with key flexfields, not a flexfield; repeats across operating unitsVARCHAR2
4TYPE_LOOKUP_CODEDocument type — standard/blanket/contract families; decodes through the purchasing document-types table, not FNDVARCHAR2
5AUTHORIZATION_STATUSApproval status code — decodes through Purchasing's own lookup table (type 'AUTHORIZATION STATUS'), not the generic FND oneVARCHAR2
6APPROVED_FLAGY once approvedVARCHAR2
7APPROVED_DATELast approval date — the primary analysis date (nullable on unapproved documents)DATE
Filter date
8CLOSED_CODEClosure state — open, closed, closed for invoicing/receiving; Purchasing lookup type 'DOCUMENT STATE'VARCHAR2
9CLOSED_DATEWhen the document closedDATE
10CANCEL_FLAGY when cancelled — the row persistsVARCHAR2
11VENDOR_IDThe supplier — joins the supplier masterNUMBER
12VENDOR_SITE_IDThe supplier site — OU-striped on the site tableNUMBER
13AGENT_IDThe buyerNUMBER
14CURRENCY_CODEDocument currencyVARCHAR2
15RATECurrency conversion rateNUMBER
16COMMENTSHeader comments/descriptionVARCHAR2
17FROM_HEADER_IDThe source document this one was created from (a quotation, for example)NUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading PO_HEADERS_ALLon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark 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, agreement, quotation, or RFQ (seven document types share the table), with supplier, buyer, currency, approval status, and closure state; operating-unit striped
-- Purpose: Column-selected read of PO_HEADERS_ALL — auto-generated from field metadata
-- Grain  : One row per operating unit (ORG_ID) + PO_HEADER_ID
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. 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 header",
  t.ORG_ID AS "Operating unit — PO numbers are unique only within it (plus document type)",
  t.SEGMENT1 AS "The PO number — a naming collision with key flexfields, not a flexfield; repeats across operating units",
  t.TYPE_LOOKUP_CODE AS "Document type — standard/blanket/contract families; decodes through the purchasing document-types table, not FND",
  t.AUTHORIZATION_STATUS AS "Approval status code — decodes through Purchasing's own lookup table (type 'AUTHORIZATION STATUS'), not the generic FND one",
  t.APPROVED_FLAG AS "Y once approved",
  t.APPROVED_DATE AS "Last approval date — the primary analysis date (nullable on unapproved documents)",
  t.CLOSED_CODE AS "Closure state — open, closed, closed for invoicing/receiving; Purchasing lookup type 'DOCUMENT STATE'",
  t.CLOSED_DATE AS "When the document closed",
  t.CANCEL_FLAG AS "Y when cancelled — the row persists",
  t.VENDOR_ID AS "The supplier — joins the supplier master",
  t.VENDOR_SITE_ID AS "The supplier site — OU-striped on the site table",
  t.AGENT_ID AS "The buyer",
  t.CURRENCY_CODE AS "Document currency",
  t.RATE AS "Currency conversion rate",
  t.COMMENTS AS "Header comments/description",
  t.FROM_HEADER_ID AS "The source document this one was created from (a quotation, for example)"
FROM <catalog>.<schema>.PO_HEADERS_ALL t
WHERE
  t.ORG_ID = <operating_unit_id>  -- operating unit (MOAC does not filter extracts)
  -- 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>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.PO_HEADER_ID;

7 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <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

  • OE_DROP_SHIP_SOURCESPO_HEADERS_ALLforeign key · N:1
    ON OE_DROP_SHIP_SOURCES.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_ID AND OE_DROP_SHIP_SOURCES.ORG_ID = PO_HEADERS_ALL.ORG_ID
  • PO_HEADERS_ALLPO_LINES_ALLheader line · 1:N
    ON PO_HEADERS_ALL.PO_HEADER_ID = PO_LINES_ALL.PO_HEADER_ID AND PO_HEADERS_ALL.ORG_ID = PO_LINES_ALL.ORG_ID
  • PO_HEADERS_ALLAP_SUPPLIERSforeign key · N:1
    ON PO_HEADERS_ALL.VENDOR_ID = AP_SUPPLIERS.VENDOR_ID
  • PO_HEADERS_ALLAP_SUPPLIER_SITES_ALLforeign key · N:1
    ON PO_HEADERS_ALL.VENDOR_SITE_ID = AP_SUPPLIER_SITES_ALL.VENDOR_SITE_ID AND PO_HEADERS_ALL.ORG_ID = AP_SUPPLIER_SITES_ALL.ORG_ID
  • PO_HEADERS_ALLHR_OPERATING_UNITSforeign key · N:1
    ON PO_HEADERS_ALL.ORG_ID = HR_OPERATING_UNITS.ORGANIZATION_ID
  • PO_RELEASES_ALLPO_HEADERS_ALLforeign key · N:1
    ON PO_RELEASES_ALL.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_ID AND PO_RELEASES_ALL.ORG_ID = PO_HEADERS_ALL.ORG_ID
  • MTL_SUPPLYPO_HEADERS_ALLforeign key · N:1
    ON MTL_SUPPLY.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_ID
  • WIP_TRANSACTIONSPO_HEADERS_ALLforeign key · N:1
    ON WIP_TRANSACTIONS.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_ID

Browse more Purchasingtables →

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 E-Business Suite are registered trademarks of Oracle and/or its affiliates.