Dynamics Community Forum Thread Details

Planning Optimization Phantom Bom Lines

How should the coverage group be set for bom line items with the type phantom?

We use this option extensively for packaging and hardware bills of materials. (not to be confused with Item Details Phantom items) They are currently set with a Period coverage type. We are just switching from Master Planning to Planning Optimization. Currently our phantom bom components create a planned order that never gets firmed. In Master Planning a nightly job deleted these. In Planning Optimization, they are just stacking up. I also see that they don't have any pegging, but I need to investigate that further.

Thanks!

Categories:

Dynamics 365 Supply Chain Management

Hi Iispyi,

When dealing with phantom BOM line items in D365 Supply Chain Management and switching from Master Planning to Planning Optimization, phantom BOM components might behave differently:

- In Planning Optimization, phantom components may generate planned orders that don’t get firmed and accumulate if not managed properly
- Ensure that the phantom items are not set to be stocked, and that their coverage group aligns with the parent item’s planning strategy

0) Recommended Coverage Type: "Period"

- This groups demand over a time period, reducing the number of planned orders
- Ideal for phantom items used in packaging or hardware kits
- Helps avoid excessive planned orders for each demand instance

0.1) Avoid "Requirement" Coverage Type

- This creates a planned order for every demand, which is inefficient for phantom items
- Can lead to a buildup of unfirmed planned orders, especially since phantom components lack pegging in Planning Optimization

0.2) Positive Days Setting

- In Planning Optimization, positive days are treated as infinite, meaning demand is grouped regardless of the value set
- This supports the use of "Period" coverage type by naturally grouping demand

1) Phantom BOMs Are Flattened:
- In Planning Optimization, phantom BOMs are exploded during planning, and their components are planned directly
- The phantom item itself does not generate a planned order - only its components do

2) No Pegging for Phantom Components:
- Planned orders for components of phantom items lack pegging to the parent demand
- This can lead to accumulating unfirmed planned orders if not managed properly

3) No Automatic Cleanup:
- Unlike Master Planning, Planning Optimization does not automatically delete unfirmed planned orders for phantom components
- You may need to implement manual cleanup routines or adjust coverage settings to reduce noise

For a more fitting answer, provide a more detailed description of the requirement.

Rg,

Alexander

*Due to the complex and different possibilities of deploying Dynamics 365 I highly recommend not to setup the application without some expert/partner or support. (For more information contact me under anassl@inno-solutions.info or visit www.inno-solutions.de)

*The Information comes directly from the manufacturer or provider and are validated (not guaranteed) up to date of creation of the posting.

References: