Skip to content
Fusion Reference

DOO_LINES_ALL

Product: DOOtransactionBU-striped (ORG_ID)

Sales order lines — the middle tier between the header and the fulfillment lines, carrying the item, ordered/shipped/fulfilled quantities, selling price, and line status

Notes

Analytics usually runs at the fulfillment-line grain below — lines split as they process, and shipped/fulfilled quantities roll up from there. The org column pair to know: ORG_ID is the business unit, INVENTORY_ORGANIZATION_ID is the item-master org (no plain ORGANIZATION_ID). The hold indicator is ON_HOLD.

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

DOO_LINES_ALL lines join back to their header DOO_HEADERS_ALL — and the org column — so a line never fans out.

DOO_LINES_ALL is the header for its lines in DOO_FULFILL_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.

Fields

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1LINE_IDSurrogate key of the order lineNUMBER
Key
2HEADER_IDParent orchestration order headerNUMBER
3LINE_NUMBERLine number used with fulfillment systemsNUMBER
4ORG_IDThe business unit owning the lineNUMBER
5INVENTORY_ITEM_IDItem on the lineNUMBER
6INVENTORY_ORGANIZATION_IDThe item-master inventory organization — pairs with the item id for item joinsNUMBER
7ORDERED_QTYQuantity orderedNUMBER
8ORDERED_UOMUOM for the ordered quantityVARCHAR2
9SHIPPED_QTYQuantity shipped on the lineNUMBER
10FULFILLED_QTYQuantity used to fulfill the lineNUMBER
11CANCELED_QTYQuantity canceledNUMBER
12STATUS_CODEOrchestration order line statusVARCHAR2
13OPEN_FLAGY while the line is not closed or canceledVARCHAR2
14CANCELED_FLAGY when the line is canceledVARCHAR2
15ON_HOLDLine not accepting further processingVARCHAR2
16UNIT_SELLING_PRICEUnit price the buyer paidNUMBER
17EXTENDED_AMOUNTMonetary amount for the line quantityNUMBER
18FULFILLMENT_DATEDate the line was fulfilledDATE
Filter date

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of DOO_LINES_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>, <business_unit_id>, <LINE_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : DOO_LINES_ALL — Sales order lines — the middle tier between the header and the fulfillment lines, carrying the item, ordered/shipped/fulfilled quantities, selling price, and line status
-- Purpose: Column-selected read of DOO_LINES_ALL — auto-generated from field metadata
-- Grain  : One row per business unit (ORG_ID) + LINE_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.LINE_ID AS "Surrogate key of the order line",
  t.HEADER_ID AS "Parent orchestration order header",
  t.LINE_NUMBER AS "Line number used with fulfillment systems",
  t.ORG_ID AS "The business unit owning the line",
  t.INVENTORY_ITEM_ID AS "Item on the line",
  t.INVENTORY_ORGANIZATION_ID AS "The item-master inventory organization — pairs with the item id for item joins",
  t.ORDERED_QTY AS "Quantity ordered",
  t.ORDERED_UOM AS "UOM for the ordered quantity",
  t.SHIPPED_QTY AS "Quantity shipped on the line",
  t.FULFILLED_QTY AS "Quantity used to fulfill the line",
  t.CANCELED_QTY AS "Quantity canceled",
  t.STATUS_CODE AS "Orchestration order line status",
  t.OPEN_FLAG AS "Y while the line is not closed or canceled",
  t.CANCELED_FLAG AS "Y when the line is canceled",
  t.ON_HOLD AS "Line not accepting further processing",
  t.UNIT_SELLING_PRICE AS "Unit price the buyer paid",
  t.EXTENDED_AMOUNT AS "Monetary amount for the line quantity",
  t.FULFILLMENT_DATE AS "Date the line was fulfilled"
FROM <catalog>.<schema>.DOO_LINES_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.LINE_ID = <LINE_ID>
  -- AND t.FULFILLMENT_DATE >= DATE '<DATE_FROM>'
  -- AND t.FULFILLMENT_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.LINE_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

  • 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_LINES_ALLDOO_FULFILL_LINES_ALLheader line · 1:N
    ON DOO_LINES_ALL.LINE_ID = DOO_FULFILL_LINES_ALL.LINE_ID AND DOO_LINES_ALL.ORG_ID = DOO_FULFILL_LINES_ALL.ORG_ID
  • DOO_LINES_ALLEGP_SYSTEM_ITEMS_Bforeign key · N:1
    ON DOO_LINES_ALL.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND DOO_LINES_ALL.INVENTORY_ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • DOO_HOLD_INSTANCESDOO_LINES_ALLforeign key · N:1
    ON DOO_HOLD_INSTANCES.DOO_LINE_ID = DOO_LINES_ALL.LINE_ID

Browse more Order Management tables

More Order Management 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.