BOM_OPERATION_SEQUENCES
Schema: BOMmasterRouting 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
Date-effective operation rows — the same operation number reappears per revision window; as-of filtering applies here just like components
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
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
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | OPERATION_SEQUENCE_ID | Surrogate key of the operation — what operation resources hang off | NUMBER | Key |
| 2 | ROUTING_SEQUENCE_ID | The routing the operation belongs to — also where the organization resolves from | NUMBER | |
| 3 | OPERATION_SEQ_NUM | The operation number practitioners see — what components and jobs reference by value | NUMBER | |
| 4 | DEPARTMENT_ID | The department (work center) the operation runs in | NUMBER | |
| 5 | EFFECTIVITY_DATE | When the operation row becomes effective — the as-of filter column | DATE | Filter date |
| 6 | DISABLE_DATE | Effectivity end — NULL while active | DATE | |
| 7 | IMPLEMENTATION_DATE | NULL on unimplemented engineering changes | DATE | |
| 8 | STANDARD_OPERATION_ID | The standard operation this one was created from | NUMBER | |
| 9 | OPERATION_DESCRIPTION | Operation description | VARCHAR2 | |
| 10 | COUNT_POINT_TYPE | Count-point/autocharge behavior — where work must be recorded | NUMBER | |
| 11 | BACKFLUSH_FLAG | Whether moves backflush pull components here | NUMBER | |
| 12 | OPTION_DEPENDENT_FLAG | Whether the operation appears only when its option is chosen | NUMBER | |
| 13 | MINIMUM_TRANSFER_QUANTITY | Minimum quantity moved between operations | NUMBER | |
| 14 | YIELD | Operation yield | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading BOM_OPERATION_SEQUENCESon 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 : 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;6 parameters not filled: <catalog>, <schema>, <OPERATION_SEQUENCE_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 BOM_OPERATIONAL_ROUTINGS.ROUTING_SEQUENCE_ID = BOM_OPERATION_SEQUENCES.ROUTING_SEQUENCE_IDON BOM_OPERATION_SEQUENCES.DEPARTMENT_ID = BOM_DEPARTMENTS.DEPARTMENT_IDON BOM_OPERATION_RESOURCES.OPERATION_SEQUENCE_ID = BOM_OPERATION_SEQUENCES.OPERATION_SEQUENCE_IDON CST_ITEM_COST_DETAILS.OPERATION_SEQUENCE_ID = BOM_OPERATION_SEQUENCES.OPERATION_SEQUENCE_ID