Microsoft Dynamics AX Support

This blog contains posts by the Microsoft Dynamics AX Support Teams Worldwide

"Locked for rescheduling" and implications on Capacity reservation reductions

This article will describe the interaction between Capacity reservations when you use the ‘Locked for rescheduling’ function in the Microsoft Dynamics AX 2012 Production Control module. Assume that you have the following scenario:

  • Finished good item FG.
  • Component item COMP.
  • Finished good item FG has a BOM configured where the COMP Item is a component.
  • Finished good item FG has a Route configured that uses the following two 2 Route operation:  Cutting 8 Hours for Process Quantity of 1.00 uses Resource MACHINEA; and Assembly 2 Hours for Process Quantity of 1.00 uses Resource MACHINEB.

A Production order is created in the system for the FG Item for a quantity of 1.00, and this Production order is estimated, released, and started. 2 hours of ‘Cutting’ labor has then been recorded relative to the manufacturing of FG. This 2 hours of labor was posted in AX 2012 via a Route card journal against the ‘Cutting’ Route operation tied to the FG Production order’s Route.

The expectation after this scenario is that when you review Capacity reservations for the MACHINEA Resource (Resource assigned with the ‘Cutting’ Route operation), the following will take place depending upon if the Production order has been ‘Locked for rescheduling’:

1.  If your Production order for FG has been ‘Locked for rescheduling’, Capacity Reservations for MACHINEA will continue to reflect 8 Hours remaining.

2.  If your Production order for FG has NOT been ‘Locked for rescheduling’, Capacity Reservations for MACHINEA will now reflect 6 Hours remaining.

The point is that if you use the ‘Locked for rescheduling’ function in the Production control module of Microsoft Dynamics AX 2012, it is important to take into consideration that posting of labor via Route\Job card Journals will not reduce Capacity reservations because the posting of Route\Job card journals is considered a ‘rescheduling’ action. By using ‘Locked for rescheduling’, you are essentially telling Microsoft Dynamics AX 2012 to not reduce Capacity reservations when Route\Job card journals are posted.