After updating our BOM in configuration management to version 3.0 for several assemblies, the supply planning workbench continues to use the old BOM version 2.0 for planning calculations. We’ve run the collections multiple times, but the planning profile mapping doesn’t seem to pick up the new BOM structure. The BOM is active and approved in PLM, but supply planning shows outdated component requirements. Collections complete successfully without errors, yet planned orders still reference the old component list. Is there a specific sequence or additional setup required to force supply planning to recognize BOM version updates?
Your issue involves three interconnected configuration areas that need to be validated in sequence.
BOM Version Control: First, verify the BOM version control settings in your planning profile. Navigate to Plan Inputs > Manage Planning Item Attributes. Search for your assembly items and check the ‘BOM Version Control’ attribute. This should be set to ‘Latest Approved’ rather than a specific frozen version. If it’s frozen to version 2.0, planning will ignore version 3.0 regardless of collections. Update this to ‘Latest Approved’ for all affected assemblies.
Collections Process: The standard collections process has specific dependencies for BOM data. Your collections job needs to include these tasks in order: 1) Collect Items, 2) Collect Bills of Material, 3) Collect Planning Attributes. If you’re running these separately or out of sequence, BOM changes may not propagate correctly. Additionally, verify the collections scope includes the specific organizations where these assemblies are planned. Go to Scheduled Processes > Supply Plan Collections and check the Advanced Parameters section. Ensure ‘Incremental Collections’ is enabled - this parameter determines whether collections detect changed BOMs.
Planning Profile Mapping: The critical missing step is the planning profile item attribute refresh. After BOM updates, you must explicitly refresh the planning profile mapping. Run the ‘Refresh Planning Profile Item Attributes’ process for your affected assemblies. This process synchronizes the planning profile’s BOM version references with the current configuration management state. Without this refresh, planning continues using cached BOM version pointers even after collections complete.
Also check your change order status in configuration management. The BOM version must have ‘Implemented’ status, not just ‘Approved’, for planning to recognize it. Finally, verify that version 3.0’s effectivity date is at least one day before your planning horizon start date - same-day effectivity can cause timing issues in the collections process.
After making these corrections, run a targeted collections refresh for the specific items rather than a full plan refresh. This will be faster and you can validate the BOM version change immediately in the supply planning workbench component explosion view.
Good points. I verified the effectivity dates and they’re correct - version 3.0 is effective from December 1st, and our planning horizon starts December 5th. The collections job does include the BOM task and completes successfully. We’re using the primary BOM alternate. Could there be a caching issue at the planning profile level?
This is typically a collections configuration issue. The standard collections process has specific tasks for BOM data. Go to Scheduled Processes and check if your collections job includes the ‘Collect Bills of Material’ task. Sometimes this gets deselected if you’re using a custom collections profile. Also verify that the Item-Organization assignment for your assemblies is set to use the correct BOM alternate. If you’re using a non-primary alternate, you need to specify it in your planning profile item attributes.
I’ve encountered this before. The issue is usually with the effectivity dates on your BOM. Supply planning uses the plan start date to determine which BOM version to use. If your new BOM version has an effectivity date that’s after your planning horizon start, it won’t be picked up. Check the effectivity dates on both BOM versions and make sure version 3.0 is effective before your plan start date.