Results for “bom_operation_sequences”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BOM_OPERATION_SEQUENCES is the core routing operation table in the Oracle E-Business Suite Bills of Material (BOM) module, owned by the BOM schema. It stores the individual operations that make up an operational routing, capturing the sequence, department, resource, yield, and timing attributes required to manufacture or process an item. Each row represents one operation within a routing, and the table acts as the central integration point between engineering routings, work-in-process execution, and cost rollup.

Within the routing model, BOM_OPERATION_SEQUENCES sits beneath BOM_OPERATIONAL_ROUTINGS (which defines the routing header) and above BOM_OPERATION_RESOURCES and BOM_COMPONENT_OPERATIONS (which attach resources and components to specific steps). From a Data Vault modeling perspective, the mined foreign-key structure suggests classifying this object as a hub, since OPERATION_SEQUENCE_ID serves as the durable business key anchored to multiple referencing satellites and links.

Key Information Stored

The table contains 83 documented columns. The most significant are:

• OPERATION_SEQUENCE_ID — surrogate primary key (BOM_OPERATION_SEQUENCES_PK); also enforced by unique index U1.
• ROUTING_SEQUENCE_ID — foreign key to BOM_OPERATIONAL_ROUTINGS, identifying the parent routing; part of the business unique key U2.
• OPERATION_SEQ_NUM — the step number within the routing sequence; part of U2.
• OPERATION_TYPE — distinguishes operation categories; part of U2.
• EFFECTIVITY_DATE and DISABLE_DATE — date-range validity of the operation; EFFECTIVITY_DATE participates in U2.
• DEPARTMENT_ID — foreign key to BOM_DEPARTMENTS, indicating where the operation executes.
• STANDARD_OPERATION_ID — reference to WSM_OPERATION_DETAILS for the reusable standard operation definition.
• REVISED_ITEM_SEQUENCE_ID — foreign key to ENG_REVISED_ITEMS linking the operation to a specific engineering revision.
• PROCESS_OP_SEQ_ID and LINE_OP_SEQ_ID — self-referencing pointers to related process and line operations.
• YIELD, CUMULATIVE_YIELD, REVERSE_CUMULATIVE_YIELD — yield percentages used in capacity and planning calculations.
• LABOR_TIME_CALC, MACHINE_TIME_CALC, TOTAL_TIME_CALC — computed time values per operation.
• BACKFLUSH_FLAG and COUNT_POINT_TYPE — WIP material and move-transaction controls.
• MINIMUM_TRANSFER_QUANTITY and OPERATION_LEAD_TIME_PERCENT — scheduling parameters.
• CONFIG_ROUTING_ID, MODEL_OP_SEQ_ID — configuration and model-routing linkage.

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID) are also present, plus ATTRIBUTE1–15 for descriptive flexfield extensibility.

Common Use Cases and Queries

Typical queries retrieve all operations for a routing in sequence order, or join operation data with resources and components for manufacturing reporting:

• List operations for a routing:
  SELECT OPERATION_SEQ_NUM, OPERATION_DESCRIPTION, DEPARTMENT_ID, YIELD FROM BOM_OPERATION_SEQUENCES WHERE ROUTING_SEQUENCE_ID = :routing_id ORDER BY OPERATION_SEQ_NUM;
• Reconcile operations against resources:
  SELECT o.OPERATION_SEQ_NUM, r.RESOURCE_ID FROM BOM_OPERATION_SEQUENCES o, BOM_OPERATION_RESOURCES r WHERE o.OPERATION_SEQUENCE_ID = r.OPERATION_SEQUENCE_ID;
• Capacity and time analysis by department, aggregating TOTAL_TIME_CALC and CUMULATIVE_YIELD.
• Audit of effectivity windows using EFFECTIVITY_DATE and DISABLE_DATE to determine which operations were active on a given date.
• Cost rollup verification joining to CST_ITEM_COST_DETAILS on OPERATION_SEQUENCE_ID.

Related Objects

• BOM_OPERATIONAL_ROUTINGS — parent routing header; joined via ROUTING_SEQUENCE_ID.
• BOM_DEPARTMENTS — department definition; joined via DEPARTMENT_ID.
• BOM_OPERATION_RESOURCES — resources attached to each operation; references OPERATION_SEQUENCE_ID.
• BOM_COMPONENT_OPERATIONS — components assigned to operations; references OPERATION_SEQUENCE_ID.
• BOM_OPERATION_NETWORKS — operation precedence links; references TO_OP_SEQ_ID.
• WIP_OPERATIONS — shop-floor execution records; references OPERATION_SEQUENCE_ID.
• CST_ITEM_COST_DETAILS and CST_ITEM_CST_DTLS_INTERFACE — cost detail and interface rows keyed on OPERATION_SEQUENCE_ID.
• ENG_REVISED_ITEMS — engineering revision linkage via REVISED_ITEM_SEQUENCE_ID.
• WSM_OPERATION_DETAILS — standard operation master via STANDARD_OPERATION_ID.