Skip to content
Fusion Reference

DOO_HEADERS_ALL

Product: DOOtransactionBU-striped (ORG_ID)

The sales order header — one row per orchestration order, carrying the order number, source-system references, sold-to customer, currency, and the status the whole order-to-cash cycle hangs off; business-unit striped

Notes

Draft rows share the table — filter SUBMITTED_FLAG = 'Y' for real orders. There is no order-total amount column on the header (totals live in a separate totals table, not yet cataloged), and the hold indicator is spelled ON_HOLD, not ON_HOLD_FLAG. SOURCE_ORDER_* columns carry the originating capture system's identifiers.

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

DOO_HEADERS_ALL is the header for its lines in DOO_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.ScmExtractAM.DooBiccExtractAM.HeaderExtractPVO
    OTBI: Order Management - Order Headers Real Time

    Sales Order Headers data store — keyed on HeaderId, mirroring the header's key.

    Oracle data-store documentation →

Fields

18 fields · 1 key

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1HEADER_IDSurrogate key of the orchestration orderNUMBER
Key
2ORDER_NUMBERThe sales order number used with fulfillment systemsVARCHAR2
3ORG_IDThe business unit owning the order — Fusion's BU stripe, not the EBS operating unitNUMBER
4SOURCE_ORDER_SYSTEMWhich capture system the order came fromVARCHAR2
5SOURCE_ORDER_IDOrder id in the originating capture systemVARCHAR2
6SOURCE_ORDER_NUMBEROrder number in the originating capture systemVARCHAR2
7SOLD_TO_PARTY_IDSold-to customer party (TCA)NUMBER
8CUSTOMER_PO_NUMBERThe customer's purchase order referenceVARCHAR2
9STATUS_CODEOrchestration order status codeVARCHAR2
10OPEN_FLAGY while the order is not closed or canceledVARCHAR2
11CANCELED_FLAGY when the order is canceled — canceled orders keep their rowsVARCHAR2
12ON_HOLDOrder not accepting further processing — note the name has no _FLAG suffixVARCHAR2
13SUBMITTED_FLAGN = draft, Y = submitted — filter to Y for real ordersVARCHAR2
14ORDER_TYPE_CODEType of order placedVARCHAR2
15TRANSACTIONAL_CURRENCY_CODEOrder header currencyVARCHAR2
16ORDERED_DATEWhen the items were orderedDATE
Filter date
17REQUEST_SHIP_DATEThe customer's originally requested ship date (header default)DATE
18SUBMITTED_DATEWhen the order was validated and submittedTIMESTAMP

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of DOO_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  : DOO_HEADERS_ALL — The sales order header — one row per orchestration order, carrying the order number, source-system references, sold-to customer, currency, and the status the whole order-to-cash cycle hangs off; business-unit striped
-- Purpose: Column-selected read of DOO_HEADERS_ALL — auto-generated from field metadata
-- Grain  : One row per business unit (ORG_ID) + 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.HEADER_ID AS "Surrogate key of the orchestration order",
  t.ORDER_NUMBER AS "The sales order number used with fulfillment systems",
  t.ORG_ID AS "The business unit owning the order — Fusion's BU stripe, not the EBS operating unit",
  t.SOURCE_ORDER_SYSTEM AS "Which capture system the order came from",
  t.SOURCE_ORDER_ID AS "Order id in the originating capture system",
  t.SOURCE_ORDER_NUMBER AS "Order number in the originating capture system",
  t.SOLD_TO_PARTY_ID AS "Sold-to customer party (TCA)",
  t.CUSTOMER_PO_NUMBER AS "The customer's purchase order reference",
  t.STATUS_CODE AS "Orchestration order status code",
  t.OPEN_FLAG AS "Y while the order is not closed or canceled",
  t.CANCELED_FLAG AS "Y when the order is canceled — canceled orders keep their rows",
  t.ON_HOLD AS "Order not accepting further processing — note the name has no _FLAG suffix",
  t.SUBMITTED_FLAG AS "N = draft, Y = submitted — filter to Y for real orders",
  t.ORDER_TYPE_CODE AS "Type of order placed",
  t.TRANSACTIONAL_CURRENCY_CODE AS "Order header currency",
  t.ORDERED_DATE AS "When the items were ordered",
  t.REQUEST_SHIP_DATE AS "The customer's originally requested ship date (header default)",
  t.SUBMITTED_DATE AS "When the order was validated and submitted"
FROM <catalog>.<schema>.DOO_HEADERS_ALL t
WHERE
  t.ORG_ID = <business_unit_id>  -- business unit — Fusion _ALL means BU, not the EBS operating unit; see quirks guide #all-means-bu
  -- AND t.HEADER_ID = <HEADER_ID>
  -- AND t.ORDERED_DATE >= DATE '<DATE_FROM>'
  -- AND t.ORDERED_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.HEADER_ID;

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

  • DOO_HEADERS_ALLDOO_LINES_ALLheader line · 1:N
    ON DOO_HEADERS_ALL.HEADER_ID = DOO_LINES_ALL.HEADER_ID AND DOO_HEADERS_ALL.ORG_ID = DOO_LINES_ALL.ORG_ID
  • DOO_FULFILL_LINES_ALLDOO_HEADERS_ALLforeign key · N:1
    ON DOO_FULFILL_LINES_ALL.HEADER_ID = DOO_HEADERS_ALL.HEADER_ID AND DOO_FULFILL_LINES_ALL.ORG_ID = DOO_HEADERS_ALL.ORG_ID
  • DOO_HEADERS_ALLFUN_ALL_BUSINESS_UNITS_Vforeign key · N:1
    ON DOO_HEADERS_ALL.ORG_ID = FUN_ALL_BUSINESS_UNITS_V.BU_ID
  • DOO_HOLD_INSTANCESDOO_HEADERS_ALLforeign key · N:1
    ON DOO_HOLD_INSTANCES.DOO_HEADER_ID = DOO_HEADERS_ALL.HEADER_ID

Browse more Order Managementtables →

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.