OE_ORDER_LINES_ALL
Schema: ONTtransactionOU-striped (ORG_ID)Sales order lines at their most granular workflow unit — shipment splits, model options, included items, and configuration items each get their own row, individually statused and quantity-tracked through booking, shipping, and invoicing
Quantities are running counters and lines split as they ship — cancelled lines persist with ORDERED_QUANTITY driven to 0, and model/option/config structures add rows; filter ITEM_TYPE_CODE and sum knowingly
Open quantity is arithmetic (ORDERED_QUANTITY − SHIPPED_QUANTITY, with CANCELLED_QUANTITY already removed from ORDERED_QUANTITY) — there is no open-quantity column. SHIP_FROM_ORG_ID is the fulfilling inventory org and pairs with the item id for every item-master join. Line and header statuses diverge: they decode through two different FND lookup types.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Header & line
OE_ORDER_LINES_ALL lines join back to their header OE_ORDER_HEADERS_ALL — and the org column — so a line never fans out.
Fields
20 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | LINE_ID | Surrogate key of the order line — what shipping, reservations, and invoicing join on | NUMBER | Key |
| 2 | HEADER_ID | The parent order header | NUMBER | |
| 3 | ORG_ID | Operating unit — striped on lines as well as headers | NUMBER | |
| 4 | LINE_NUMBER | Display line number — rows multiply under it as lines split | NUMBER | |
| 5 | LINE_TYPE_ID | The line transaction type | NUMBER | |
| 6 | LINE_CATEGORY_CODE | Order vs return line | VARCHAR2 | |
| 7 | ITEM_TYPE_CODE | Row kind in configured products — standard, model, option, included, config; filter it or double-count | VARCHAR2 | |
| 8 | INVENTORY_ITEM_ID | The item sold — joins the item master together with the ship-from org | NUMBER | |
| 9 | SHIP_FROM_ORG_ID | The fulfilling warehouse — an inventory org, the org half of the item join (see quirks guide #two-orgs) | NUMBER | |
| 10 | ORDERED_QUANTITY | Current ordered quantity — already reduced by cancellations | NUMBER | |
| 11 | SHIPPED_QUANTITY | Quantity ship-confirmed | NUMBER | |
| 12 | CANCELLED_QUANTITY | Quantity cancelled off the line — what ORDERED_QUANTITY no longer includes | NUMBER | |
| 13 | FULFILLED_QUANTITY | Quantity fulfilled — what drives invoicing in fulfillment sets | NUMBER | |
| 14 | ORDER_QUANTITY_UOM | UOM of the line quantities | VARCHAR2 | |
| 15 | UNIT_SELLING_PRICE | Net unit price after adjustments | NUMBER | |
| 16 | REQUEST_DATE | Customer-requested date — the demand-side analysis date | DATE | Filter date |
| 17 | SCHEDULE_SHIP_DATE | Scheduled ship date from scheduling | DATE | |
| 18 | ACTUAL_SHIPMENT_DATE | Actual ship date — the OTIF numerator | DATE | |
| 19 | FLOW_STATUS_CODE | Workflow-derived line status — a different lookup type than the header's | VARCHAR2 | LINE_FLOW_STATUS |
| 20 | OPEN_FLAG | Y while the line is still open | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading OE_ORDER_LINES_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.
-- ============================================================
-- Table : OE_ORDER_LINES_ALL — Sales order lines at their most granular workflow unit — shipment splits, model options, included items, and configuration items each get their own row, individually statused and quantity-tracked through booking, shipping, and invoicing
-- Purpose: Column-selected read of OE_ORDER_LINES_ALL — auto-generated from field metadata
-- Grain : One row per operating unit (ORG_ID) + LINE_ID
-- Caution: Quantities are running counters and lines split as they ship — cancelled lines persist with ORDERED_QUANTITY driven to 0, and model/option/config structures add rows; filter ITEM_TYPE_CODE and sum knowingly
-- 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.LINE_ID AS "Surrogate key of the order line — what shipping, reservations, and invoicing join on",
t.HEADER_ID AS "The parent order header",
t.ORG_ID AS "Operating unit — striped on lines as well as headers",
t.LINE_NUMBER AS "Display line number — rows multiply under it as lines split",
t.LINE_TYPE_ID AS "The line transaction type",
t.LINE_CATEGORY_CODE AS "Order vs return line",
t.ITEM_TYPE_CODE AS "Row kind in configured products — standard, model, option, included, config; filter it or double-count",
t.INVENTORY_ITEM_ID AS "The item sold — joins the item master together with the ship-from org",
t.SHIP_FROM_ORG_ID AS "The fulfilling warehouse — an inventory org, the org half of the item join (see quirks guide #two-orgs)",
t.ORDERED_QUANTITY AS "Current ordered quantity — already reduced by cancellations",
t.SHIPPED_QUANTITY AS "Quantity ship-confirmed",
t.CANCELLED_QUANTITY AS "Quantity cancelled off the line — what ORDERED_QUANTITY no longer includes",
t.FULFILLED_QUANTITY AS "Quantity fulfilled — what drives invoicing in fulfillment sets",
t.ORDER_QUANTITY_UOM AS "UOM of the line quantities",
t.UNIT_SELLING_PRICE AS "Net unit price after adjustments",
t.REQUEST_DATE AS "Customer-requested date — the demand-side analysis date",
t.SCHEDULE_SHIP_DATE AS "Scheduled ship date from scheduling",
t.ACTUAL_SHIPMENT_DATE AS "Actual ship date — the OTIF numerator",
t.FLOW_STATUS_CODE AS "Workflow-derived line status — a different lookup type than the header's", -- decode t.FLOW_STATUS_CODE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'LINE_FLOW_STATUS', LANGUAGE-filtered) — see quirks guide #lookups
t.OPEN_FLAG AS "Y while the line is still open"
FROM <catalog>.<schema>.OE_ORDER_LINES_ALL t
WHERE
t.ORG_ID = <operating_unit_id> -- operating unit (MOAC does not filter extracts)
-- AND t.LINE_ID = <LINE_ID>
-- AND t.REQUEST_DATE >= DATE '<DATE_FROM>'
-- AND t.REQUEST_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.LINE_ID;7 parameters not filled: <catalog>, <schema>, <operating_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 OE_ORDER_HEADERS_ALL.HEADER_ID = OE_ORDER_LINES_ALL.HEADER_ID AND OE_ORDER_HEADERS_ALL.ORG_ID = OE_ORDER_LINES_ALL.ORG_IDON OE_ORDER_LINES_ALL.LINE_TYPE_ID = OE_TRANSACTION_TYPES_ALL.TRANSACTION_TYPE_ID AND OE_ORDER_LINES_ALL.ORG_ID = OE_TRANSACTION_TYPES_ALL.ORG_IDON OE_ORDER_LINES_ALL.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND OE_ORDER_LINES_ALL.SHIP_FROM_ORG_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_IDON OE_ORDER_LINES_ALL.FLOW_STATUS_CODE = FND_LOOKUP_VALUES.LOOKUP_CODE AND FND_LOOKUP_VALUES.LOOKUP_TYPE = 'LINE_FLOW_STATUS' AND FND_LOOKUP_VALUES.LANGUAGE = '<language>'ON OE_ORDER_HOLDS_ALL.LINE_ID = OE_ORDER_LINES_ALL.LINE_ID AND OE_ORDER_HOLDS_ALL.ORG_ID = OE_ORDER_LINES_ALL.ORG_IDON OE_PRICE_ADJUSTMENTS.LINE_ID = OE_ORDER_LINES_ALL.LINE_IDON OE_DROP_SHIP_SOURCES.LINE_ID = OE_ORDER_LINES_ALL.LINE_ID AND OE_DROP_SHIP_SOURCES.ORG_ID = OE_ORDER_LINES_ALL.ORG_IDON MTL_RESERVATIONS.DEMAND_SOURCE_LINE_ID = OE_ORDER_LINES_ALL.LINE_IDON WSH_DELIVERY_DETAILS.SOURCE_LINE_ID = OE_ORDER_LINES_ALL.LINE_ID AND WSH_DELIVERY_DETAILS.ORG_ID = OE_ORDER_LINES_ALL.ORG_IDON RCV_SHIPMENT_LINES.OE_ORDER_LINE_ID = OE_ORDER_LINES_ALL.LINE_ID