Results for “bom_operation_networks”

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

Overview

BOM_OPERATION_NETWORKS is a table in the BOM (Bills of Material) schema of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores routing operation networks, which define the allowable transitions between consecutive operations in a manufacturing routing. Where BOM_OPERATION_SEQUENCES records the individual steps of a routing, BOM_OPERATION_NETWORKS records the directed relationships that link one operation (the "from" operation) to another (the "to" operation), forming a network graph that the routing engine and shop floor scheduling functions traverse. The table supports advanced routing constructs such as operation overlap, yield-based flow, and alternate transition paths that cannot be expressed by a simple linear sequence alone.

Under a heuristic Data Vault classification derived from its foreign key structure, BOM_OPERATION_NETWORKS is satellite-leaning. This suggests it is best modeled as a dependent structure attached to a parent hub or link, capturing descriptive attributes about the operation-to-operation relationship rather than acting as an independent business entity. In practice it serves as an associative entity whose grain is the pairing of two operation sequences.

Key Information Stored

The table's business grain is defined by two columns that together form the unique index BOM_OPERATION_NETWORKS_U1: FROM_OP_SEQ_ID and TO_OP_SEQ_ID. These identify the originating and destination operations within the routing and are the principal business-key candidates. The foreign key relationship documented is BOM_OPERATION_NETWORKS.TO_OP_SEQ_ID referencing BOM_OPERATION_SEQUENCES.

Among the 32 documented columns, the most significant for functional and reporting purposes include:

• FROM_OP_SEQ_ID and TO_OP_SEQ_ID — the operation sequence identifiers defining the network edge.
• TRANSITION_TYPE — classifies how the transition between operations behaves (for example overlap or standard flow).
• PLANNING_PCT — the percentage of work planned to flow across the transition, used in capacity and scheduling calculations.
• EFFECTIVITY_DATE and DISABLE_DATE — effective-dating columns that control when a network relationship is active.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS who-columns for audit.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the DFF (descriptive flexfield) segment columns for client-specific extensions.
• ORIGINAL_SYSTEM_REFERENCE — source-system reference for data migration and integration.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program tracking columns.

No single surrogate primary key column is documented; the unique index on the two operation sequence columns acts as the effective business key.

Common Use Cases and Queries

Typical uses include routing network analysis, validation of operation flow, and shop floor scheduling reports. A common query resolves the full network edge with operation detail:

• Join BOM_OPERATION_NETWORKS to BOM_OPERATION_SEQUENCES twice — once on FROM_OP_SEQ_ID and once on TO_OP_SEQ_ID — to display the operation names and sequence numbers at both ends of each transition.
• Filter on EFFECTIVITY_DATE and DISABLE_DATE to return only currently active network relationships.
• Aggregate PLANNING_PCT by routing to analyze planned flow distribution across operations.
• Cross-check transition types to identify non-standard flows or overlaps that affect lead-time and capacity calculations.

Reporting commonly surfaces these edges alongside routing headers and operation resources to support manufacturing scheduling and cost analysis.

Related Objects

• BOM_OPERATION_SEQUENCES — the parent of the documented foreign key via TO_OP_SEQ_ID, and the referenced table for FROM_OP_SEQ_ID in practice; supplies operation-level detail such as operation codes, resources, and run times.
• BOM_ROUTINGS / routing headers — group the operation sequences that the networks connect.
• BOM_OPERATION_RESOURCES — resources attached to each operation involved in the network.
• BOM_DEPARTMENTS — departments associated with the operations referenced here.
• Import and maintenance routines for bills of material and routings that insert and update network rows.

Together these objects allow the BOM module to represent complex, non-linear routing flows for a manufacturing environment.