We have recognized a GAP in the forecasting system for Companies using configured Products.
For certain product the number of configurations can be very high or unlimited. These products must therefore be forecasted on either a "planning item" with at BOM representing the different configurational outcomes or through an item allocation key which is composed of "typical configurations".
The problem is that if the product is sold in a new configuration which does not match the forecasted items exactly on configuration ID, the forecast will not be reduced.
My suggestion is to make a new parameter in Requirement Group called "Forecast reduction on product level": Yes/No.
If this parameter is set, the forecast reduction will work on the forecasted item INDEPENDENT of the sold product configuration. The effect of this will be that the "planning item" forecasted quantity will be properly reduced by all sold configurations for the product.
Comments
Just begun work on a new project that definitely needs this!
Category: Planning
Good suggestion
Category: Planning
Great idea, classic gap with confirued products
Category: Planning
Great idea, recurrent need for integration projetcs !
Category: Planning
Great idea, and should also use unit conversion for products where the variant is a diffents size / mass that the forecast unit, eg forecast on a 100 kg piece, but variants of forecast item is weighing not 100 kg
Category: Planning
Great idea !
Category: Planning
I agree
Category: Planning
I agree
Category: Planning
Administrator on 5/28/2019 12:21:31 PM
Thank you for your feedback.
This is a great suggestion! We will consider this in our roadmap as the votes for this suggestion increases.
Sincerely,
Christian Rytt
PM,
Microsoft.