21

Planning Optimization


Currently any change to a Supply Forecast or adding a new supply forecast line within the Frozen Time fence gets forced to one day beyond the time fence. This is just like Planned orders being CREATED by MPS where this behavior makes total sense. However, the reason for a Supply Forecast is to STATE SUPPLY, regardless of demand, whereas a planned order CREATED by MPS is a CALCULATED SUPPLY.


A Frozen Time fence is the only way to achieve a Master Production Schedule as defined by ASCM. It's the only way to manage a decoupled supply plan. A Supply Forecast is the ideal way to maintain a decoupled supply plan as it can be edited without real time explosion (unlike a planned order whether it is approved or not and whether it is in a frozen time fence or not). These edits are essentially instant whereas planned production orders can take minutes to explode. For Supply forecasts the explosion is deferred until the next MPS run (or requirements "Update" request). The user needs to dictate Supply Forecast dates and NOT have them pushed out to beyond the Frozen Time Fence.


I see no reason to ever push supply from a supply forecast to beyond the Frozen time fence, but if there is a need, perhaps add a Boolean checkbox parameter to the Mater Plan setup form to "Disregard Time Fences for Supply Forecasts"

Category: Planning
STATUS DETAILS
New
Ideas Administrator

Thanks for this input. We are though a bit puzzled. When using Planning Optimization, planned supply created from supply forecasts is not postponed beyond the frozen time fence, whereas the deprecated classic master planning engine does move supply outside the frozen period. We are currently awaiting feedback from the creator of this idea to fully understand the gap in Planning Optimization. For now keeping this Idea as New, untill we fully understand the request (and current gap).

Best regards,

Supply Planing Team

Comments

N

PLEASE DISREGARD THIS IDEA.I'm not seeing a way to withdraw an idea, so I am hoping this comment is enough.Henrik Andersen and Anders Sorensen, both top of my list of respected Microsoft experts, informed me that this capability IS ALREADY RELEASED in Planning optimization and was simply not available in Legacy Planning. My testing confirmed this.Thank you all of you that voted that this would be a great feature. Please celebrate with me that it already is.Regards to all,Nigel

Category: Planning

N

NOTE my typo: the Parameter field should be named "Disregard Frozen Time Fence for Supply Forecasts" - emphasis on FROZEN.

Category: Planning

N

CoPilot suggested I add this sentence:“If you’ve ever tried to maintain a true Master Production Schedule using Supply Forecasts and a Frozen time fence, this Idea fixes a behavior that breaks it today.”I also wanted to add that I was told that that one of the main reasons a Supply Forecast existed in AX (I used it in 3.0) was for purchased items to model a Supplier with a limited capacity, to see, in planned orders, their capable deliveries. MPS would critique these with Action Messages and add new planned orders where they did not suffice. These new planned orders would be candidates for alternate sourcing. By the way this was a legacy "trick" to cope with multiple sourcing before Microsoft added the new source by percentage capability. Forcing these forecasts (i.e. the planned orders they would spawn) to beyond the Frozen time fence ALSO makes little sense, whether modelling a constrained supplier or modelling multiple sources.

Category: Planning