Reschedule does not happen when this is "Lot-for-Lot" and reoder cycle is defined
Do you like this story?
With Lot-for-Lot items, the reorder cycle needs to be considered when a change on the demand profile arise. As an example, we have a lot-for-lot item for which a replenishment exist which is consistent with demand profile. Now, the user changes a demand shipment date to an earlier date and the assumption is that new shipment date is within the reorder cycle. The result is that NAV suggest to Cancel the existing replenishment and creates a New one. Why?
As a general rule, it should respect the reorder cycle and reschedule the existing replenishment. However, what if an exception exists? An example is when the change on the shipment date impacts safety stock availability (stock goes below safety stock). In this case, this is an exception as well. As mentioned on an earlier post, NAV raise this as an exception so they user can decide how to address this.
Read the complete post at http://feedproxy.google.com/~r/MicrosoftDynamicsNavTeamBlog/~3/ZfUMG6g1hfw/reschedule-does-not-happen-when-this-is-quot-lot-for-lot-quot-and-reoder-cycle-is-defined.aspx
Posted Feb 23, 2011 12:58 by Microsoft Dynamics NAV Team Blog Filed under: SCM
This post was written by: Rahil Anouar
Rahil Anouar is a professional blogger, web designer and Linux user. Follow him on Twitter
0 Responses to “Reschedule does not happen when this is "Lot-for-Lot" and reoder cycle is defined”
Post a Comment