Minimum/maximum keys are no more supported in Planning Optimization according to the documentation.
It's a shame. Could you advice how can we plan an increase/decrease of the safety stock easily now? Do you plan to retrofit this feature in Planning Optimization?
It is really important to offer a feature to our customers in order to support business cases. Thank you
Comments
Based on our interaction with Microsoft (TrackingID#2309140060003607) we understood & confirmed that min/max keys are still supported. Planning optimization will always behave as if parameter "minimum periods" is activated. Therefore, a dynamic/rolling safety stock is still supported. We asked the support engineer to update the documentation on docs as well.
So from my perspective the above functionality requested is implemented in planning optimization.
Category: Planning
Upvoting this. My understanding is that min/max keys are still supported by planning optimisation, however the parameter "Minimum periods", that allowed to have a dynamic/rolling safety stock (different for each month, rather than static for all months) is not supported in planning optimisation anymore. From my experience I do not see much value in min/max keys alone without minimum periods, as they cannot be used to make the safety stock dynamic/rolling (different for each month).
Our client is a pharma manufacturer and has governmental recommendations (in spain even regulations) to hold at least x months of forecast as a safety stock. We are currently using the min/max keys to cover this requirement and it's been brilliant to cover this requirement. Their whole planning in Europe and APAC is based on this principle.
The removal of this feature puts us in a very hard position to move to planning optimisation. It would be great to see it on the roadmap, as it has been a good feature.
Category: Planning