The current code in the planning worksheet calculation will set the planning flexibility to None if you assign a lot to the production order line to be used when the order is released and you output to it.

So instead of telling the user to reschedule to an earlier date the calculation suggests a NEW order be created and also will not recommend cancelations, etc. It works the same as if the lines planning flexibility is set to None.

This is really unexpected and there should at minimum be a setting to skip this code for firm planned and even released production orders.

Note on released orders there is additional code in the planning calculations where there are entries (output / consumption) it sets the planning flexibility to None as they view the order in-process. This code can stay but we should not be considering an order "in-process" when there is only a lot assigned to the production order line (or at least have a way to exclude this).

I have asked several of our customers using lots if this is expected and everyone of them said NO and its not desirable. I suspect most users and partners have know this is happening.

We did a mod to work around this code but it would be nice to have this as stock functionality.

Details -

Code Summary for issue with the Lot assignment and Production Order Scheduling

• During the calc regen plan – Codeunit Inventory Profile Offsetting in function Unfold Item Tracking:
• The Code is setting the Production Order line to Planning flexibility None when there is a Lot assigned to the production order line (reservation) and the “binding” is NOT Order to Order.
• Basically if a lot is assigned to any production order it is setting the planning flexibility to NONE which prevents the order from being re-scheduled. We feel this is not a correct assumption and it does not meet customers actual expectations and use cases.
• When you run Calculate Regenerative Plan from the Planning Worksheet it Creates/finds/updates the demand and supply inventory profiles and where it is updating the supply inventory profile is where it is causing the issue.
• Unfortunately I can't add screen shots to show the issue but MSFT has confirmed the behavior.