Results for “bom_standard_operations_u1”

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

Overview

BOM.BOM_STANDARD_OPERATIONS is a foundational manufacturing master data table in the Oracle E-Business Suite BOM schema. It stores the definitions of standard operations, events, processes, and line operations that an organization establishes for use in routings and flow manufacturing. When a routing step is created in the Define Routing window, the application defaults the stored attributes of the selected standard operation — including descriptive flexfield content, which is shared with BOM.BOM_OPERATION_SEQUENCES — directly into the routing step. The table therefore serves as the reusable template layer that standardizes shop-floor execution across assemblies.

The table is validated and owned by BOM, with design data registered under FND Design Data as BOM.BOM_STANDARD_OPERATIONS. It resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its primary key, BOM_STANDARD_OPERATIONS_PK, is composed of LINE_ID, OPERATION_TYPE, and STANDARD_OPERATION_ID. Heuristically, the mined foreign-key structure classifies this object as satellite-leaning: it carries descriptive and behavioral attributes attached to the referenced departments, organizations, and production lines rather than acting as a pure transactional intersection. This classification should be treated as a modeling suggestion rather than a documented constraint.

Key Information Stored

The 57-column structure centers on identifying the operation and its execution context:

• STANDARD_OPERATION_ID — the surrogate unique identifier for the standard operation and the target of unique index BOM_STANDARD_OPERATIONS_U2.
• OPERATION_CODE — the user-facing code for the operation; a business-key candidate in BOM_STANDARD_OPERATIONS_U1.
• OPERATION_TYPE — numeric discriminator: 1 for Standard Operation/Event, 2 for Process, 3 for Line Operation. Part of both the primary key and U1.
• ORGANIZATION_ID — the owning organization; part of U1 and the nonunique index BOM_STANDARD_OPERATIONS_N1.
• LINE_ID — the WIP line identifier, used primarily for line operations and included in the primary key and U1.
• DEPARTMENT_ID — the department in which the operation is performed.
• SEQUENCE_NUM — ordering of processes and line operations.
• MINIMUM_TRANSFER_QUANTITY and COUNT_POINT_TYPE — transfer quantity thresholds and count point behavior.
• OPERATION_DESCRIPTION — descriptive text defaulted into routing steps.
• YIELD, OPERATION_YIELD_ENABLED, LOWEST_ACCEPTABLE_YIELD — yield definition and enforcement.
• BACKFLUSH_FLAG, WMS_TASK_TYPE, DEFAULT_SUBINVENTORY, DEFAULT_LOCATOR_ID — material consumption and warehouse defaults.
• QUEUE_MANDATORY_FLAG, RUN_MANDATORY_FLAG, TO_MOVE_MANDATORY_FLAG — shop-floor move transaction controls.
• VALUE_ADDED, CRITICAL_TO_QUALITY, CHECK_SKILL — classification and resource qualification flags.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the descriptive flexfield segment columns shared with BOM_OPERATION_SEQUENCES.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns.

Common Use Cases and Queries

Routing setup and reporting are the dominant scenarios. A typical lookup by organization and type:

SELECT standard_operation_id, operation_code, operation_type, department_id
FROM bom.bom_standard_operations
WHERE organization_id = :org_id AND operation_type = 1;

Joining to BOM_OPERATION_SEQUENCES via the shared flexfield definition supports routing step analysis. Yield and quality reporting frequently filters on lowest_acceptable_yield or critical_to_quality. Interface and conversion scripts resolve STANDARD_OPERATION_ID from OPERATION_CODE to populate routing steps, and flow manufacturing reporting joins LINE_ID to identify line operations. Because the descriptive flexfield is shared, extract programs must reconcile ATTRIBUTE columns across both tables.

Related Objects

• BOM.BOM_DEPARTMENTS — joined on DEPARTMENT_ID.
• BOM.MTL_PARAMETERS — joined on ORGANIZATION_ID for organization context.
• BOM.WIP_LINES — joined on LINE_ID for line operations.
• BOM.FLM_MMM_OPERATIONS — references this table via LINE_ID for mixed-model flow manufacturing.
• BOM.BOM_OPERATION_SEQUENCES — shares the descriptive flexfield definition and receives defaulted standard operation data.
• BOM.BOM_STANDARD_OPERATIONS_U1 / _U2 / _N1 — indexes enforcing business keys and supporting organizational access paths.