Related to the tickets: 861974, 953576

Planning optimization does not support 'Dimension-based configuration'.

MS support replied, that it is a known problem, but currently, it is not clear when Microsoft will solve it. This issue has low priority.

Currently Planning Optimization ignores such setup as ‘Configuration group’ for BOM\Formula lines. As a result, it generates the planned production order with all the components from BOM\Formula lines in 'Derived requirements' regardless of what Configuration of the finished goods was planned for production. However, deprecated MRP covers such cases.

Without it customers have to increase efforts to manage their BOM data: generate separate BOM for each item configuration.

Example of case:

Item FG001 has 3 configurations: default, config1 and config2.

FG001 has 1 BOM to cover all the configurations:

Mat 1 - common material and used in all configurations.

Mat 2 - common material and used in all configurations

Mat 3 - used only for config1 + default

Mat 4 - used only for config2 + default

When deprecated MRP is running it generates planned production orders with the next info in Derived requirements:

FG001 default configuration: Mat 1, Mat 2, Mat 3, Mat 4

FG001 config1: Mat 1, Mat 2, Mat 3.

FG001 config2: Mat 1, Mat 2, Mat 4

Planning Optimization generates planned production orders where Derived requirements are the same for all FG001 configurations.

It would be very nice to return this functionality in Planning Optimization.

Microsoft insists on using Planning Optimization as an improved high-performed MRP engine, and at the same time deprecated MRP engine is not supported.

Currently, it is strange, that we have to propose customers use functionality, which does not work correctly in comparison with deprecated functionality.