Results for “bom_operation_sequences_temp”

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

Overview

BOM_OPERATION_SEQUENCES_TEMP is a temporary staging table in the Oracle Bills of Material (BOM) schema. It holds intermediate routing and operation sequence data during the creation, copying, or modification of manufacturing routing structures before that data is validated and committed to the permanent BOM_OPERATION_SEQUENCES table. In Oracle EBS 12.1.1 and 12.2.2 this object supports the routing definition workflow, where operations are assembled and sequenced for a manufactured item, then persisted once the transaction completes.

The table is owned by the BOM schema and is documented as VALID in ETRM 12.2.2, containing 82 columns. Heuristic Data Vault classification mined from the foreign key structure identifies this object as standalone. In Data Vault modeling terms, a standalone classification suggests the object behaves as a hub-like or self-contained entity that does not participate in a heavily interlinked relationship graph through its keys; however, the presence of multiple foreign keys to reference tables indicates a satellite-like dependency on WSM_OPERATION_DETAILS, BOM_DEPARTMENTS, and ENG_REVISED_ITEMS. This classification should be treated as a modeling suggestion rather than a definitive architectural statement.

Key Information Stored

The most operationally significant columns of this table are:

• OPERATION_SEQUENCE_ID — the surrogate primary key uniquely identifying each operation sequence record within the temporary set.
• ROUTING_SEQUENCE_ID — the routing sequence this operation belongs to, linking the operation to its parent routing header.
• OPERATION_SEQ_NUM — the numeric ordering of the operation within the routing.
• STANDARD_OPERATION_ID — foreign key to WSM_OPERATION_DETAILS identifying the reusable standard operation definition.
• DEPARTMENT_ID — foreign key to BOM_DEPARTMENTS identifying the department that performs the operation.
• REVISED_ITEM_SEQUENCE_ID — foreign key to ENG_REVISED_ITEMS tying the operation to the revised item (engineering revision) context.
• OPERATION_DESCRIPTION and LONG_DESCRIPTION — textual descriptions of the operation.
• EFFECTIVITY_DATE and DISABLE_DATE — the effective date range during which the operation is valid.
• OPERATION_LEAD_TIME_PERCENT, MINIMUM_TRANSFER_QUANTITY — planning attributes controlling lead time and transfer quantities.
• BACKFLUSH_FLAG and COUNT_POINT_TYPE — flags governing backflush behavior and count point designation.
• YIELD, CUMULATIVE_YIELD, REVERSE_CUMULATIVE_YIELD — yield calculations across the routing.
• LABOR_TIME_CALC, MACHINE_TIME_CALC, TOTAL_TIME_CALC and their USER counterparts — computed versus user-entered operation times.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.

Business key candidates center on ROUTING_SEQUENCE_ID combined with OPERATION_SEQ_NUM, which together identify the operation's ordinal position within a routing.

Common Use Cases and Queries

This table is principally referenced during routing creation and update processes. Reporting queries typically join it to the reference tables to resolve department and standard operation descriptions:

• Validating a staged routing by joining DEPARTMENT_ID to BOM_DEPARTMENTS and STANDARD_OPERATION_ID to WSM_OPERATION_DETAILS.
• Reviewing operation sequences for a revised item via REVISED_ITEM_SEQUENCE_ID joined to ENG_REVISED_ITEMS.
• Auditing yield and time calculations prior to committing the routing to the permanent table.
• Troubleshooting routing-creation errors by inspecting EFFECTIVITY_DATE and DISABLE_DATE ranges for overlapping or invalid intervals.

A representative pattern selects OPERATION_SEQ_NUM, OPERATION_DESCRIPTION, and DEPARTMENT_ID ordered by OPERATION_SEQ_NUM for a given ROUTING_SEQUENCE_ID, which reconstructs the operation order as staged.

Related Objects

The documented foreign key relationships connect this table to the following significant objects:

• WSM_OPERATION_DETAILS — joined on STANDARD_OPERATION_ID, supplying the standard operation definition.
• BOM_DEPARTMENTS — joined on DEPARTMENT_ID, supplying department context.
• ENG_REVISED_ITEMS — joined on REVISED_ITEM_SEQUENCE_ID, supplying the engineering revision context.
• BOM_OPERATION_SEQUENCES — the permanent counterpart table into which validated rows are committed; the primary downstream dependency in the staging workflow.
• BOM_ROUTINGS — the routing header referenced through ROUTING_SEQUENCE_ID.

These relationships make BOM_OPERATION_SEQUENCES_TEMP a transient staging artifact within the broader BOM routing definition process.