Search Results bom_operation_sequences_v




Overview
Explore in AI Chat

Overview

The BOM_OPERATION_SEQUENCES_V view, owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2, presents the routing operation sequences that define the manufacturing steps associated with an assembly in Oracle Bills of Material. Each row represents a discrete operation within a routing sequence, exposing not only the ordered sequence number and department assignment but also standard operation references, lead time, transfer quantity, count point, backflush, and time calculation attributes. Because routing operations are the backbone of work-in-process execution, capacity planning, and cost rollup, this view is a primary reporting and integration surface for any process that programmatically reads or copies routing data.

The view resolves foreign keys to human-readable values by joining the operation sequences table to the standard operations, departments, and lookup tables, so consumers avoid manual joins when they need the operation code, department code, or shutdown type meaning. This makes it a convenient source for custom reports, data extracts, and interface programs that would otherwise need to replicate the join logic themselves.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through the APPS schema:

Because these are synonyms and views rather than the physical base tables, the view remains valid across releases while the underlying definitions are maintained by the BOM product team.

Key Columns

Common Use Cases and Queries

A frequent requirement is to retrieve all operations for a given assembly or standard operation code. For example, to locate routings using a specific standard operation:

SELECT OPERATION_SEQUENCE_ID, OPERATION_SEQ_NUM, STANDARD_OPERATION_CODE, DEPARTMENT_CODE, OPERATION_DESCRIPTION FROM BOM_OPERATION_SEQUENCES_V WHERE STANDARD_OPERATION_CODE = :p_operation_code;

Other uses include building routing extracts for MES or shop floor interfaces, validating that department assignments exist, and reporting operation times and yields for cost or capacity analysis. When querying, restrict by EFFECTIVITY_DATE and DISABLE_DATE to return only currently effective operations.