Results for “lowest_acceptable_yield”

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

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:

• BOM_OPERATION_SEQUENCES (synonym) — the driving table, supplying the sequence identifier, sequence number, department, timing, yield, and descriptive attributes.
• BOM_STANDARD_OPERATIONS (synonym) — supplies OPERATION_CODE, aliased in the view as STANDARD_OPERATION_CODE, resolving the standard operation associated with each routing step.
• BOM_DEPARTMENTS (synonym) — supplies DEPARTMENT_CODE and LOCATION_ID for the assigned department.
• MFG_LOOKUPS (view) — supplies the MEANING value for the shutdown type code.

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

• OPERATION_SEQUENCE_ID and ROUTING_SEQUENCE_ID — primary and parent keys linking the operation to its routing.
• OPERATION_SEQ_NUM — the ordered step number within the routing.
• STANDARD_OPERATION_CODE — the code from BOM_STANDARD_OPERATIONS; this is the column users commonly search for when locating a specific operation definition.
• DEPARTMENT_CODE and LOCATION_ID — the department and location performing the work.
• MINIMUM_TRANSFER_QUANTITY and OPERATION_LEAD_TIME_PERCENT — planning parameters.
• COUNT_POINT_TYPE and the derived COUNT_POINT_FLAG / AUTOCHARGE_FLAG — indicate whether the operation is a count point or autocharge point.
• BACKFLUSH_FLAG and YIELD / CUMULATIVE_YIELD — control material consumption and yield accounting.
• LABOR_TIME_CALC, MACHINE_TIME_CALC, and TOTAL_TIME_CALC — computed operation times.
• EFFECTIVITY_DATE and DISABLE_DATE — date-range validity of the operation.

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.