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
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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.
- FscmTopModelAM.ScmExtractAM.DooBiccExtractAM.LineExtractPVOOTBI: Order Management - Order Lines Real Time
Sales Order Lines data store — keyed on LineId.
Oracle data-store documentation →
Fields
18 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | LINE_ID | Surrogate key of the order line | NUMBER | Key |
| 2 | HEADER_ID | Parent orchestration order header | NUMBER | |
| 3 | LINE_NUMBER | Line number used with fulfillment systems | NUMBER | |
| 4 | ORG_ID | The business unit owning the line | NUMBER | |
| 5 | INVENTORY_ITEM_ID | Item on the line | NUMBER | |
| 6 | INVENTORY_ORGANIZATION_ID | The item-master inventory organization — pairs with the item id for item joins | NUMBER | |
| 7 | ORDERED_QTY | Quantity ordered | NUMBER | |
| 8 | ORDERED_UOM | UOM for the ordered quantity | VARCHAR2 | |
| 9 | SHIPPED_QTY | Quantity shipped on the line | NUMBER | |
| 10 | FULFILLED_QTY | Quantity used to fulfill the line | NUMBER | |
| 11 | CANCELED_QTY | Quantity canceled | NUMBER | |
| 12 | STATUS_CODE | Orchestration order line status | VARCHAR2 | |
| 13 | OPEN_FLAG | Y while the line is not closed or canceled | VARCHAR2 | |
| 14 | CANCELED_FLAG | Y when the line is canceled | VARCHAR2 | |
| 15 | ON_HOLD | Line not accepting further processing | VARCHAR2 | |
| 16 | UNIT_SELLING_PRICE | Unit price the buyer paid | NUMBER | |
| 17 | EXTENDED_AMOUNT | Monetary amount for the line quantity | NUMBER | |
| 18 | FULFILLMENT_DATE | Date the line was fulfilled | DATE | Filter date |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of DOO_LINES_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.
-- ============================================================
-- 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;7 parameters not filled: <catalog>, <schema>, <business_unit_id>, <LINE_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
ON DOO_HEADERS_ALL.HEADER_ID = DOO_LINES_ALL.HEADER_ID AND DOO_HEADERS_ALL.ORG_ID = DOO_LINES_ALL.ORG_IDON DOO_LINES_ALL.LINE_ID = DOO_FULFILL_LINES_ALL.LINE_ID AND DOO_LINES_ALL.ORG_ID = DOO_FULFILL_LINES_ALL.ORG_IDON 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_IDON DOO_HOLD_INSTANCES.DOO_LINE_ID = DOO_LINES_ALL.LINE_ID