Skip to content
EBS Reference

BOM_OPERATION_SEQUENCES

Schema: BOMmaster

Routing operations — one row per operation per routing per effectivity window, department-assigned, with the count-point and backflush controls that decide where work is recorded

Grain note

Date-effective operation rows — the same operation number reappears per revision window; as-of filtering applies here just like components

Notes

No org column — the organization resolves through the routing header. Components tie to operations by the OPERATION_SEQ_NUM value, not a foreign key (1 is the default when no routing exists).

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_OPERATION_SEQUENCES lines join back to their header BOM_OPERATIONAL_ROUTINGS — and the org column — so a line never fans out.

Fields

14 fields · 1 key

14 fields.

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1OPERATION_SEQUENCE_IDSurrogate key of the operation — what operation resources hang offNUMBER
Primary-key field
2ROUTING_SEQUENCE_IDThe routing the operation belongs to — also where the organization resolves fromNUMBER
3OPERATION_SEQ_NUMThe operation number practitioners see — what components and jobs reference by valueNUMBER
4DEPARTMENT_IDThe department (work center) the operation runs inNUMBER
5EFFECTIVITY_DATEWhen the operation row becomes effective — the as-of filter columnDATE
The table's primary analysis date — a real DATE column, no conversion needed
6DISABLE_DATEEffectivity end — NULL while activeDATE
7IMPLEMENTATION_DATENULL on unimplemented engineering changesDATE
8STANDARD_OPERATION_IDThe standard operation this one was created fromNUMBER
9OPERATION_DESCRIPTIONOperation descriptionVARCHAR2
10COUNT_POINT_TYPECount-point/autocharge behavior — where work must be recordedNUMBER
11BACKFLUSH_FLAGWhether moves backflush pull components hereNUMBER
12OPTION_DEPENDENT_FLAGWhether the operation appears only when its option is chosenNUMBER
13MINIMUM_TRANSFER_QUANTITYMinimum quantity moved between operationsNUMBER
14YIELDOperation yieldNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading BOM_OPERATION_SEQUENCES 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

6 parameters not filled: <catalog>, <schema>, <OPERATION_SEQUENCE_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : BOM_OPERATION_SEQUENCES — Routing operations — one row per operation per routing per effectivity window, department-assigned, with the count-point and backflush controls that decide where work is recorded
-- Purpose: Column-selected read of BOM_OPERATION_SEQUENCES — auto-generated from field metadata
-- Grain  : One row per OPERATION_SEQUENCE_ID
-- Caution: Date-effective operation rows — the same operation number reappears per revision window; as-of filtering applies here just like components
-- 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.OPERATION_SEQUENCE_ID AS "Surrogate key of the operation — what operation resources hang off",
  t.ROUTING_SEQUENCE_ID AS "The routing the operation belongs to — also where the organization resolves from",
  t.OPERATION_SEQ_NUM AS "The operation number practitioners see — what components and jobs reference by value",
  t.DEPARTMENT_ID AS "The department (work center) the operation runs in",
  t.EFFECTIVITY_DATE AS "When the operation row becomes effective — the as-of filter column",
  t.DISABLE_DATE AS "Effectivity end — NULL while active",
  t.IMPLEMENTATION_DATE AS "NULL on unimplemented engineering changes",
  t.STANDARD_OPERATION_ID AS "The standard operation this one was created from",
  t.OPERATION_DESCRIPTION AS "Operation description",
  t.COUNT_POINT_TYPE AS "Count-point/autocharge behavior — where work must be recorded",
  t.BACKFLUSH_FLAG AS "Whether moves backflush pull components here",
  t.OPTION_DEPENDENT_FLAG AS "Whether the operation appears only when its option is chosen",
  t.MINIMUM_TRANSFER_QUANTITY AS "Minimum quantity moved between operations",
  t.YIELD AS "Operation yield"
FROM <catalog>.<schema>.BOM_OPERATION_SEQUENCES t
WHERE
  1 = 1  -- no partition column on this table; the filters below are optional
  -- AND t.OPERATION_SEQUENCE_ID = <OPERATION_SEQUENCE_ID>
  -- AND t.EFFECTIVITY_DATE >= DATE '<DATE_FROM>'
  -- AND t.EFFECTIVITY_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.OPERATION_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_OPERATION_SEQUENCESBOM_DEPARTMENTSforeign key · N:1
    ON BOM_OPERATION_SEQUENCES.DEPARTMENT_ID = BOM_DEPARTMENTS.DEPARTMENT_ID
  • BOM_OPERATION_RESOURCESBOM_OPERATION_SEQUENCESforeign key · N:1
    ON BOM_OPERATION_RESOURCES.OPERATION_SEQUENCE_ID = BOM_OPERATION_SEQUENCES.OPERATION_SEQUENCE_ID
  • CST_ITEM_COST_DETAILSBOM_OPERATION_SEQUENCESforeign key · N:1
    ON CST_ITEM_COST_DETAILS.OPERATION_SEQUENCE_ID = BOM_OPERATION_SEQUENCES.OPERATION_SEQUENCE_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.