Search Results use_org_settings




Overview
Explore in AI Chat

Overview

BOM_STANDARD_OPERATIONS is a reference table in the Oracle E-Business Suite Bills of Material (BOM) module that stores the standard operation definitions used in manufacturing routing and work-in-process (WIP) execution. Each row represents a discrete manufacturing operation — for example, assembly, soldering, testing, or packaging — that can be attached to a routing sequence for a manufactured item or to a standard bill of material. The table is owned by the BOM schema and is validated as of Oracle EBS 12.1.1 and 12.2.2, containing 57 documented columns.

The object is organization-specific. The ORGANIZATION_ID column anchors every standard operation to the inventory organization defined in MTL_PARAMETERS, meaning that operation codes are defined and maintained per organization. Rows are further associated with a producing department (DEPARTMENT_ID) and, when applicable, a canonical WIP line (LINE_ID).

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is satellite-leaning. The table has the character of a business-vault satellite: it holds descriptive and functional attributes attached to a business key (the operation identity) rather than serving as a pure hub of distinct business entities or as a pure link between them. This classification is a modeling suggestion, not an Oracle-imposed structure.

Key Information Stored

The primary key of the table is BOM_STANDARD_OPERATIONS_PK, defined on the surrogate composite of LINE_ID, OPERATION_TYPE, and STANDARD_OPERATION_ID. Business-key uniqueness is enforced by two additional unique indexes: BOM_STANDARD_OPERATIONS_U1 on OPERATION_CODE, ORGANIZATION_ID, OPERATION_TYPE, and LINE_ID, and BOM_STANDARD_OPERATIONS_U2 on STANDARD_OPERATION_ID. The most significant columns include:

  • STANDARD_OPERATION_ID — surrogate identifier for the standard operation; part of the primary key and the U2 business key.
  • OPERATION_CODE — user-visible code that uniquely identifies the operation within an organization; part of U1.
  • ORGANIZATION_ID — foreign key to MTL_PARAMETERS, scoping the operation to an inventory organization.
  • OPERATION_TYPE — classifies the operation and participates in both the primary key and U1.
  • LINE_ID — foreign key to WIP_LINES, tying the operation to a work-in-process line.
  • DEPARTMENT_ID — foreign key to BOM_DEPARTMENTS, assigning the responsible department.
  • OPERATION_DESCRIPTION — free-text description of the operation.
  • SEQUENCE_NUM — default sequencing position used when the operation is added to a routing.
  • MINIMUM_TRANSFER_QUANTITY — quantity at which material may be transferred to the next operation.
  • COUNT_POINT_TYPE — indicates whether the operation acts as a count point for WIP completion transactions.
  • BACKFLUSH_FLAG — controls whether components are backflushed at this operation.
  • YIELD and OPERATION_YIELD_ENABLED — expected yield percentage and its enablement.
  • VALUE_ADDED — identifies whether the operation adds value for cost-rollup purposes.
  • INCLUDE_IN_ROLLUP — determines participation in cost rollup calculations.
  • USE_ORG_SETTINGS — indicates whether organizational defaults override the operation-level settings.

Standard Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are present, along with fifteen descriptive flexfield attribute columns.

Common Use Cases and Queries

Typical usage centers on routing maintenance, WIP transaction validation, and cost rollup reporting. A common query retrieves the operations defined within a specific organization, joined to their departments:

  • Listing all operations for an organization: SELECT operation_code, operation_description, department_id FROM bom_standard_operations WHERE organization_id = :org_id ORDER BY operation_code;
  • Resolving department and line context: SELECT bso.operation_code, bd.department_code, wl.line_code FROM bom_standard_operations bso, bom_departments bd, wip_lines wl WHERE bso.department_id = bd.department_id AND bso.line_id = wl.line_id AND bso.organization_id = :org_id;
  • Identifying count-point and backflush operations for WIP planning: SELECT operation_code, count_point_type, backflush_flag FROM bom_standard_operations WHERE organization_id = :org_id AND backflush_flag = 'Y';
  • Cost rollup exclusion analysis: SELECT operation_code, include_in_rollup, value_added FROM bom_standard_operations WHERE organization_id = :org_id AND include_in_rollup = 'N';

Reporting scenarios include routing standardisation reviews, yield analysis by department, and auditing of operations that appear in routings referenced by open work orders.

Related Objects

The documented foreign key relationships identify the core dependencies of BOM_STANDARD_OPERATIONS:

  • BOM_DEPARTMENTS — referenced through DEPARTMENT_ID; supplies the department that performs the operation.
  • MTL_PARAMETERS — referenced through ORGANIZATION_ID; defines the owning inventory organization and its defaults.
  • WIP_LINES — referenced through LINE_ID; provides the WIP line associated with the operation.
  • FLM_MMM_OPERATIONS — a dependent table that references LINE_ID, OPERATION_TYPE, and STANDARD_OPERATION_ID from BOM_STANDARD_OPERATIONS; it is the primary downstream consumer of this data.

Additional operational dependencies, though not enumerated as foreign keys in the supplied metadata, include the routing and operation sequencing tables within the BOM module, as well as the WIP transaction and costing tables that consume operation attributes during shop-floor execution and cost rollup.