Dynamics Community Forum Thread Details

My company is in the process of testing/validating planning optimization, and we are running into an issue with the way that planning optimization handles requirements dates that are in the past. It appears that net requirements is "double counting" issues related to inventory that was put on a hold status & removed from available inventory (ie: Inventory Journal for a negative quantity), in which those batches have also exceeded their best before date (ie: expired Batch for a negative quantity). The problem we are seeing is that planning optimization puts all requirement date issues in the past on todays date, yet expired batch dates still appear in the past on whatever the best before date was. Because of this, we have situations where planning optimization is "double counting".

Take the following for example: Consider today it is Month 3. An item was put on hold due to quality concerns (status changed to remove from available inventory) in Month 1, but also expires in Month 2. In deprecated master planning, Net requirements would only see the inventory status change in Month 1, and ignore the expired batch in Month 2, since that batch was already removed from available inventory. Now, in planning optimization, we are seeing that Net Requirements shows negative issue for the Expired batch in Month 2, but then ALSO shows another negative issue for the Inventory status change in Month 3 on todays date, effectively double counting the negative issues for this batch. This results in Planning Optimization overplanning in the future to compensate for this.

Does anyone have experience with this issue, or does anyone have any advice on how to navigate around this issue? Screenshots below for context, plans were refreshed on 10/8 in the below pictures...

Planning Optimization Output