Skip to content
EBS Reference

BOM_OPERATIONAL_ROUTINGS

Schema: BOMmasterPer inventory org

The routing header — one routing per assembly item, organization, and alternate designator, with the common-routing pointer and the completion subinventory finished assemblies land in

Identity
Module: BOM & CostingInventory-org partitioned (ORGANIZATION_ID)
Notes

Same alternate and common-pointer traps as bills: NULL alternate designator is the primary routing, and a common routing's operations live under the shared routing.

What the badges mean
Schema: INV
Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

Structural facts — how the table is partitioned, not a trap by itself

OU-striped (ORG_ID)
Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on ORG_ID, and don’t confuse it with ORGANIZATION_ID (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization (plant or warehouse) via ORGANIZATION_ID — a different partition from OU-striped tables (see the quirks guide).
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 (see the quirks guide).

Join & extract hazards — verify before you rely on this

View
This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
In field listings, the Key chip marks a primary-key field.

Header & line

BOM_OPERATIONAL_ROUTINGS is the header for its lines in BOM_OPERATION_SEQUENCES.

Fields

11 fields · 1 key

11 fields.

Table fields: position, field name, description, data type, and flags. 11 fields.
#FieldDescriptionTypeFlags
1ROUTING_SEQUENCE_IDSurrogate key of the routing — what operations hang offNUMBER
Primary-key field
2ASSEMBLY_ITEM_IDThe assembly the routing buildsNUMBER
3ORGANIZATION_IDOwning inventory organizationNUMBER
4ALTERNATE_ROUTING_DESIGNATORNULL for the primary routingVARCHAR2
5ROUTING_TYPE1 = manufacturing, 2 = engineering (per the data dictionary's own comment)NUMBER
6COMMON_ROUTING_SEQUENCE_IDThe shared routing the operations actually live under — equals the own id when not commonNUMBER
7COMPLETION_SUBINVENTORYWhere completed assemblies land by defaultVARCHAR2
8COMPLETION_LOCATOR_IDDefault completion locatorNUMBER
9CFM_ROUTING_FLAGFlow-manufacturing routing markerNUMBER
10PRIORITYRouting priority among alternatesNUMBER
11TOTAL_PRODUCT_CYCLE_TIMETotal product cycle time for flow routingsNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading BOM_OPERATIONAL_ROUTINGS on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <ROUTING_SEQUENCE_ID>, <watermark>

-- ============================================================
-- Table  : BOM_OPERATIONAL_ROUTINGS — The routing header — one routing per assembly item, organization, and alternate designator, with the common-routing pointer and the completion subinventory finished assemblies land in
-- Purpose: Column-selected read of BOM_OPERATIONAL_ROUTINGS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + ROUTING_SEQUENCE_ID
-- 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.ROUTING_SEQUENCE_ID AS "Surrogate key of the routing — what operations hang off",
  t.ASSEMBLY_ITEM_ID AS "The assembly the routing builds",
  t.ORGANIZATION_ID AS "Owning inventory organization",
  t.ALTERNATE_ROUTING_DESIGNATOR AS "NULL for the primary routing",
  t.ROUTING_TYPE AS "1 = manufacturing, 2 = engineering (per the data dictionary's own comment)",
  t.COMMON_ROUTING_SEQUENCE_ID AS "The shared routing the operations actually live under — equals the own id when not common",
  t.COMPLETION_SUBINVENTORY AS "Where completed assemblies land by default",
  t.COMPLETION_LOCATOR_ID AS "Default completion locator",
  t.CFM_ROUTING_FLAG AS "Flow-manufacturing routing marker",
  t.PRIORITY AS "Routing priority among alternates",
  t.TOTAL_PRODUCT_CYCLE_TIME AS "Total product cycle time for flow routings"
FROM <catalog>.<schema>.BOM_OPERATIONAL_ROUTINGS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- AND t.ROUTING_SEQUENCE_ID = <ROUTING_SEQUENCE_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.ROUTING_SEQUENCE_ID;

Verified September 2026

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

  • BOM_OPERATIONAL_ROUTINGSBOM_OPERATION_SEQUENCESheader line · 1:N
    ON BOM_OPERATIONAL_ROUTINGS.ROUTING_SEQUENCE_ID = BOM_OPERATION_SEQUENCES.ROUTING_SEQUENCE_ID
  • BOM_OPERATIONAL_ROUTINGSMTL_SYSTEM_ITEMS_Bforeign key · N:1
    ON BOM_OPERATIONAL_ROUTINGS.ASSEMBLY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND BOM_OPERATIONAL_ROUTINGS.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • BOM_OPERATIONAL_ROUTINGSBOM_OPERATIONAL_ROUTINGSforeign key · N:1
    ON BOM_OPERATIONAL_ROUTINGS1.COMMON_ROUTING_SEQUENCE_ID = BOM_OPERATIONAL_ROUTINGS2.ROUTING_SEQUENCE_ID AND BOM_OPERATIONAL_ROUTINGS1.ORGANIZATION_ID = BOM_OPERATIONAL_ROUTINGS2.ORGANIZATION_ID
  • WIP_DISCRETE_JOBSBOM_OPERATIONAL_ROUTINGSforeign key · N:1
    ON WIP_DISCRETE_JOBS.COMMON_ROUTING_SEQUENCE_ID = BOM_OPERATIONAL_ROUTINGS.ROUTING_SEQUENCE_ID AND WIP_DISCRETE_JOBS.ORGANIZATION_ID = BOM_OPERATIONAL_ROUTINGS.ORGANIZATION_ID

Browse more BOM & Costing tables

More BOM & Costing 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 E-Business Suite are registered trademarks of Oracle and/or its affiliates.