Skip to content
EBS Reference

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

Grain note

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

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.
In field listings, K marks a primary-key field.

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

Table fields: position, field name, description, data type, and flags. 20 fields.
#FieldDescriptionTypeFlags
1LINE_IDSurrogate key of the order line — what shipping, reservations, and invoicing join onNUMBER
Key
2HEADER_IDThe parent order headerNUMBER
3ORG_IDOperating unit — striped on lines as well as headersNUMBER
4LINE_NUMBERDisplay line number — rows multiply under it as lines splitNUMBER
5LINE_TYPE_IDThe line transaction typeNUMBER
6LINE_CATEGORY_CODEOrder vs return lineVARCHAR2
7ITEM_TYPE_CODERow kind in configured products — standard, model, option, included, config; filter it or double-countVARCHAR2
8INVENTORY_ITEM_IDThe item sold — joins the item master together with the ship-from orgNUMBER
9SHIP_FROM_ORG_IDThe fulfilling warehouse — an inventory org, the org half of the item join (see quirks guide #two-orgs)NUMBER
10ORDERED_QUANTITYCurrent ordered quantity — already reduced by cancellationsNUMBER
11SHIPPED_QUANTITYQuantity ship-confirmedNUMBER
12CANCELLED_QUANTITYQuantity cancelled off the line — what ORDERED_QUANTITY no longer includesNUMBER
13FULFILLED_QUANTITYQuantity fulfilled — what drives invoicing in fulfillment setsNUMBER
14ORDER_QUANTITY_UOMUOM of the line quantitiesVARCHAR2
15UNIT_SELLING_PRICENet unit price after adjustmentsNUMBER
16REQUEST_DATECustomer-requested date — the demand-side analysis dateDATE
Filter date
17SCHEDULE_SHIP_DATEScheduled ship date from schedulingDATE
18ACTUAL_SHIPMENT_DATEActual ship date — the OTIF numeratorDATE
19FLOW_STATUS_CODEWorkflow-derived line status — a different lookup type than the header'sVARCHAR2
LINE_FLOW_STATUS
20OPEN_FLAGY while the line is still openVARCHAR2

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.

Query parameters
-- ============================================================
-- 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

  • OE_ORDER_HEADERS_ALLOE_ORDER_LINES_ALLheader line · 1:N
    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_ID
  • OE_ORDER_LINES_ALLOE_TRANSACTION_TYPES_ALLforeign key · N:1
    ON 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_ID
  • OE_ORDER_LINES_ALLMTL_SYSTEM_ITEMS_Bforeign key · N:1
    ON 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_ID
  • OE_ORDER_LINES_ALLFND_LOOKUP_VALUESFND lookup decode · N:1
    ON 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>'
  • OE_ORDER_HOLDS_ALLOE_ORDER_LINES_ALLforeign key · N:1
    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_ID
  • OE_PRICE_ADJUSTMENTSOE_ORDER_LINES_ALLforeign key · N:1
    ON OE_PRICE_ADJUSTMENTS.LINE_ID = OE_ORDER_LINES_ALL.LINE_ID
  • OE_DROP_SHIP_SOURCESOE_ORDER_LINES_ALLforeign key · N:1
    ON OE_DROP_SHIP_SOURCES.LINE_ID = OE_ORDER_LINES_ALL.LINE_ID AND OE_DROP_SHIP_SOURCES.ORG_ID = OE_ORDER_LINES_ALL.ORG_ID
  • MTL_RESERVATIONSOE_ORDER_LINES_ALLforeign key · N:1
    ON MTL_RESERVATIONS.DEMAND_SOURCE_LINE_ID = OE_ORDER_LINES_ALL.LINE_ID
  • WSH_DELIVERY_DETAILSOE_ORDER_LINES_ALLforeign key · N:1
    ON WSH_DELIVERY_DETAILS.SOURCE_LINE_ID = OE_ORDER_LINES_ALL.LINE_ID AND WSH_DELIVERY_DETAILS.ORG_ID = OE_ORDER_LINES_ALL.ORG_ID
  • RCV_SHIPMENT_LINESOE_ORDER_LINES_ALLforeign key · N:1
    ON RCV_SHIPMENT_LINES.OE_ORDER_LINE_ID = OE_ORDER_LINES_ALL.LINE_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 E-Business Suite are registered trademarks of Oracle and/or its affiliates.