Study guide
2.2 BOM Versions, Activation, Approvals, and Circularity Checks
Microsoft Dynamics 365 Supply Chain Management Functional Consultant MB-330
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Product Master and Released Products
1.1 Product Masters, Variants, and Configuration Technologies 1.2 Product Templates, Category Hierarchies, and Product Lifecycle States 1.3 Product Attributes, Attribute Types, and Attribute Groups
2 Chapter 2: Bills of Materials (BOM) and Formulas
2.1 BOM Lines, Line Types, and Component Configurations 2.2 BOM Versions, Activation, Approvals, and Circularity Checks 2.3 BOM Calculations, Cost Group Types, Flushing Principles, and Scrap Handling
3 Chapter 3: Product Prerequisites and Dimension Groups
3.1 Product, Storage, and Tracking Dimension Groups 3.2 Item Model Groups, Inventory Models, and Physical/Financial Posting 3.3 Reservation Hierarchies and Unit Sequence Groups
4 Chapter 4: Additional Product Details and Warehouse Fit
4.1 Bar Codes, GTINs, and Product Unit Conversions 4.2 Default Order Settings and Site-Specific Order Settings 4.3 Product Filter Codes and Physical Warehouse Dimensions
5 Chapter 5: Inventory Costing and Pricing
5.1 Costing Versions, Costing Sheets, and Standard Costing 5.2 Base Item Prices, Price Groups, and Price Tolerances 5.3 Trade Agreements, Price/Discount Journals, and Smart Rounding
6 Chapter 6: Inventory Journals and Core Transactions
6.1 Movement, Adjustment, and Transfer Journals 6.2 Counting Journals, Tag Counting, and Cycle Count Adjustments 6.3 Item Arrival Journals, Output Orders, and BOM Journals
7 Chapter 7: Inventory Operations, Blocking, and Closing
7.1 Transfer Orders, In-Transit Warehouses, and Delivery Schedules 7.2 Inventory Blocking Mechanisms, Batch Disposition Codes, and Inventory Status 7.3 Inventory Closing, Recalculation, Settlement, and ABC Classification
8 Chapter 8: Quality Management and Nonconformance
8.1 Quality Control Setup: Tests, Test Groups, and Item Sampling 8.2 Quality Associations, Automatic Generation, and Quality Orders Processing 8.3 Nonconformances, Corrections, Corrective Operations, and Quarantine Orders
9 Chapter 9: Asset Management: Setup and Maintenance
9.1 Assets, Asset Types, and Functional Locations Setup 9.2 Asset Lifecycle Models, Lifecycle States, and Asset Loans 9.3 Work Orders Configuration, Work Order Settings, and Maintenance Capacity Management 9.4 Maintenance Plans, Maintenance Requests, Work Order Scheduling, and Journal Consumption
10 Chapter 10: Procurement and Sourcing Configuration
10.1 Vendors, Vendor Groups, and Procurement Category Hierarchies 10.2 Purchasing Policies, Spending Limits, Procurement Workflows, and Charge Codes 10.3 Purchase Agreements, Vendor Rebates, and Vendor Collaboration Portal
11 Chapter 11: Purchase Order Lifecycle and Consignment
11.1 Purchase Requisitions, Requests for Quotation (RFQs), and Bidding Processes 11.2 Purchase Orders Creation, Over/Under-Delivery Tolerances, Delivery Schedules, and Product Receipt 11.3 Consignment Inventory Replenishment/Ownership Change and Vendor Return Orders
12 Chapter 12: Landed Cost and Inbound Logistics
12.1 Landed Cost Architecture: Voyages, Shipping Containers, Folios, and Journey Templates 12.2 Cost Type Codes, Auto-Costs, and Allocation Methods 12.3 Tracking Control Center, Goods in Transit Orders, and Over/Under Tolerances
13 Chapter 13: Sales Management and Order Processing
13.1 Customers, Customer Groups, Sales Agreements, and Sales Quotations 13.2 Sales Order Processing, Manual and Automatic Reservation, and Sales Returns 13.3 Order Promising: ATP, CTP, Delivery Schedules, and Product Bundles 13.4 Intercompany Trading Chains, Sales Commissions, and Customer Rebates
14 Chapter 14: Warehouse Setup and Core Infrastructure
14.1 Warehouse Topology: Sites, Warehouses, Locations, Profiles, Formats, and Zones 14.2 Work Policies, Work Breaks, and Packing Dimensions 14.3 Wave Templates, Work Templates, and Location Directives Configuration 14.4 Label Layouts, Document Routing, Wave Label Printing, and GS1 Number Sequences
15 Chapter 15: Warehouse Execution Processes
15.1 Inbound Receiving Processes, Planned Cross-Docking, and Putaway 15.2 Outbound Waves, Wave Processing, Picking (Order, Cluster, Batch), and Manual Packing 15.3 Replenishment Strategies (Wave vs. Min/Max) and Inventory Movements via Warehouse Work 15.4 Cycle Counting Plans, Thresholds, Blind Counting, and Automated Containerization
16 Chapter 16: Transportation Management and Logistics
16.1 Shipping Carriers, Carrier Groups, Carrier Services, and Rate/Route Engines 16.2 Route Plans, Route Guides, Inbound/Outbound Loads, and Dock Appointment Scheduling 16.3 Freight Bills, Freight Invoicing, and Manual/Automatic Freight Reconciliation
17 Chapter 17: Warehouse Management Mobile App
17.1 Mobile App Installation, Display Settings, Connection Profiles, and Warehouse Worker Setup 17.2 Mobile Device Menus, Work-Based and Indirect Menu Items, and Inventory Inquiries 17.3 Step Detours Configuration and GS1 Barcode Scanning Implementation
18 Chapter 18: Master Planning and Planning Optimization
18.1 Master Planning Parameters, Coverage Groups, and Planning Optimization Cloud Service Architecture 18.2 Item Coverage Settings, Positive/Negative Days, Time Fences, and Action Messages 18.3 Running Master Planning, Analyzing Results, Planned Orders Firming, and Supply Schedule 18.4 Safety Stock Journals, Safety Margins, and Copilot in Dynamics 365 Supply Chain Management
2.2 BOM Versions, Activation, Approvals, and Circularity Checks
Key Takeaways Explain This Topic AI
D365 SCM decouples BOM headers from released products using a 1:N relationship mediated by BOM versions, enabling BOM reuse across multiple products and facilities.
Multiple active BOM versions can coexist concurrently for the same product, provided their validity criteria (Site, Date ranges, and Quantity breaks) do not conflict.
The BOM approval workflow enforces a mandatory two-stage hierarchy: the BOM header must be approved before its associated BOM version can be approved.
Master Planning and production order generation will only select a BOM version if it is simultaneously marked as both Approved and Active.
The Circularity check utility detects recursive cyclic dependencies across multi-level structures, preventing infinite loops during MRP explosion and cost calculations.
Last updated: September 2026
2.2 BOM Versions, Activation, Approvals, and Circularity Checks
In enterprise discrete manufacturing, engineering specifications change continuously, facilities utilize different machinery, and production methods evolve as batch quantities scale. Dynamics 365 Supply Chain Management (D365 SCM) manages this complexity by decoupling the component definition (the BOM Header ) from its application to an item (the BOM Version ).
Governing this relationship requires strict adherence to approval workflows, activation controls, and circularity validations.
1. Header vs. Version Relationship (1:N Architecture)
D365 SCM architecturally separates the component structure from the finished good:
BOM Header ( BOMTable ) : A standalone master record containing component lines ( BOM ). It defines the BOM ID, description, site (optional), and unit of measure. A BOM header exists independently and can be linked to multiple released products.
BOM Version ( BOMVersion ) : The associative entity that connects a released product ( InventTable ) to a BOM header under specific operational rules.
Operational Advantages of 1:N Decoupling
Reusability : A single standard packaging BOM header (e.g., standard shipping carton, protective foam, and manual) can be linked to dozens of finished goods via individual BOM versions.
Facility Differentiation : A product can use BOM Header A at Site 1 (using local components) and BOM Header B at Site 2 (using alternate components).
Batch Sizing : A product can use BOM Header 100 for small manual runs and BOM Header 200 for automated high-volume runs.
Core Attributes of a BOM Version
Item number : The parent finished product.
BOM number : The associated BOM header ID.
Site : Target production facility (blank indicates all sites).
From date / To date : Temporal effectivity window.
From quantity : Minimum order quantity threshold (quantity break).
Approved : Engineering sign-off status ( Yes / No ).
Approved by : Worker ID of the authorized employee.
Active : Operational status enabling selection by Master Planning and production orders.
2. Coexistence of Multiple Active BOM Versions
A released product can have multiple active BOM versions concurrently. To prevent ambiguity during order creation, active versions must be distinguished by clear validity boundaries:
- Version ID Site From Date To Date From Quantity Operational Context
- BM-VER-001 Site 1 2026-01-01 2026-06-30 1.00 H1 Site 1 Standard Assembly
- BM-VER-002 Site 1 2026-07-01 Open-ended 1.00 H2 Site 1 Engineering Revision
- BM-VER-003 Site 1 2026-01-01 Open-ended 500.00 High-Volume Automated Cell
- BM-VER-004 Site 2 2026-01-01 Open-ended 1.00 Site 2 Regional Sourcing
- Active Version Selection Sequence During Order Entry
When a sales order, production order, or planned order is created, D365 SCM evaluates active versions in the following deterministic order:
Item Match : Must match the ordered product.
Site Match : Must match the order site (site-specific version takes priority over blank-site global version).
Date Match : The order requirement date must fall between From date and To date .
Quantity Threshold : The order quantity must be greater than or equal to From quantity . If multiple versions qualify, the system selects the version with the highest matching From quantity .
Status Validation : Both Approved = Yes and Active = Yes are strictly required.
3. BOM Approval Workflow and Employee Credentials
Engineering governance enforces a mandatory two-stage approval hierarchy:
Stage 1: Approving the BOM Header
Navigation: Product information management > Bills of materials and formulas > Bills of materials > Action Pane > BOM > Approve
Validates line completeness and locks the structure. Once approved, the BOM header and lines become read-only . Users cannot add, delete, or modify component lines.
- Stage 2: Approving the BOM Version
- Navigation: Released products > Engineer tab > BOM > BOM versions > Approve
Mandatory Precedence : A BOM version cannot be approved if the underlying BOM header is unapproved . The system halts the action with a validation error.
Employee Authorization Setup
To execute approvals, the user must be an authorized employee:
Navigation: Human resources > Workers > Employees
The user login must link to a valid Worker record authorized for BOM approvals under Production control parameters or Inventory and warehouse management parameters . Unauthorized users cannot approve headers or versions.
4. Activating BOM Versions for Master Planning
Understanding the functional boundary between Approved and Active is critical:
Approved = Yes, Active = No : Signed off by engineering, but withheld from operations. Master Planning (Planning Optimization) ignores the version, and production orders cannot automatically select it.
Approved = Yes, Active = Yes : Fully released. Master Planning explodes this version to generate planned supply, and production order creation defaults to it.
Warning
Unapproving an active BOM version automatically clears its Active flag. Re-approving the version does not automatically reactivate it; planners must explicitly activate it again.
If a user activates a version that duplicates the Site, Date range, and Quantity break of an already active version, D365 SCM alerts the user and prompts to deactivate the conflicting version.
5. Circularity Check Diagnostics
A circular reference occurs when a parent item is included as a component of itself in a multi-level BOM (e.g., Item A requires Subassembly B, which requires Item A).
Operational Risks of Circularity
Master Planning (Planning Optimization) enters infinite recursion loops during net requirements calculation, causing batch jobs to fail.
BOM Cost Calculations fail with stack overflow exceptions.
Production Estimation hangs indefinitely.
Running Circularity Checks
Navigation: Product information management > Bills of materials and formulas > Circularity check (or BOM Header Action Pane > Check > Circularity ).
Circularity Level : Defines the maximum recursion depth (default is 50 levels).
If circularity is detected, the Infolog identifies the exact item, BOM ID, and recursive node level, allowing engineers to sever the loop before activation.
6. Version Copying and Manual Overrides
Copying Versions : Via Released products > Engineer tab > BOM > BOM versions > Copy , users can duplicate BOM lines, apply scaling factors, and copy routing operations.
Manual Overrides : While D365 SCM defaults to the best-matching active version, authorized planners can manually select an alternate approved BOM version on the production order header prior to estimation.
Exam Tips and Common Traps
Approval Hierarchy Trap : You cannot approve a BOM version without first approving the BOM header.
Active Requires Approved : A version can be approved without being active, but it cannot be active without being approved . Master Planning requires both flags to be Yes .
Quantity Break Hierarchy : When multiple active versions share the same site and date, D365 SCM selects the version with the highest From quantity that is less than or equal to the order quantity.