27
Description of problem:
A production order with open work can't be scheduled. If you're scheduling several production orders at the same time the capacity reservations are set to 'marked for deletion' before open work is checked. The scheduling abords but the capacity reservations stay as 'marked for deletion'.
Repro steps:
Create two production order. Set up one of these that a BOM item will have work. Job schedule both orders against capacity. Release one of the production orders to get work created . You have to have open work for this to be an issue. Mark both production orders and do job scheduling. You get a warning that one production order could not be scheduled due to open work. Check capacity reservations for this production order and you can see, that the capacity reservations are marked for deletion.
Relevant code in AX 2012 is class prodMultiSchedulingJob.run . this.updateProdDeleted() is called before the production order is checked for open work.
Setting up an example in D365 I get the same result.
If we want to reschedule the production order we have to cancel the open work. In this case the customer has thousands of open production orders of which hundreds have open work. Cancelling the open work is no solution as work has to be created once more after scheduling. The items are not yet taken from stock, otherwise the work wouldn’t be open. And if we cancel the work and recreate it afterwards (and that’s a pain, as we have to manually reserve the items beforehand, as they are already allocated to a wave) it will have a different work id.
Currently rescheduling more than one production order at once all production order with open work cannot be scheduled. But capacity reservations for these production orders are marked for deletion.
I can see the following solutions:
- Production orders can be scheduled although there is open work. The date, when the work has to be completed, has to be updated.
- Production orders can’t be scheduled if there is open work. But then capacity reservations for these production orders should be kept reserved.
A production order with open work can't be scheduled. If you're scheduling several production orders at the same time the capacity reservations are set to 'marked for deletion' before open work is checked. The scheduling abords but the capacity reservations stay as 'marked for deletion'.
Repro steps:
Create two production order. Set up one of these that a BOM item will have work. Job schedule both orders against capacity. Release one of the production orders to get work created . You have to have open work for this to be an issue. Mark both production orders and do job scheduling. You get a warning that one production order could not be scheduled due to open work. Check capacity reservations for this production order and you can see, that the capacity reservations are marked for deletion.
Relevant code in AX 2012 is class prodMultiSchedulingJob.run . this.updateProdDeleted() is called before the production order is checked for open work.
Setting up an example in D365 I get the same result.
If we want to reschedule the production order we have to cancel the open work. In this case the customer has thousands of open production orders of which hundreds have open work. Cancelling the open work is no solution as work has to be created once more after scheduling. The items are not yet taken from stock, otherwise the work wouldn’t be open. And if we cancel the work and recreate it afterwards (and that’s a pain, as we have to manually reserve the items beforehand, as they are already allocated to a wave) it will have a different work id.
Currently rescheduling more than one production order at once all production order with open work cannot be scheduled. But capacity reservations for these production orders are marked for deletion.
I can see the following solutions:
- Production orders can be scheduled although there is open work. The date, when the work has to be completed, has to be updated.
- Production orders can’t be scheduled if there is open work. But then capacity reservations for these production orders should be kept reserved.
STATUS DETAILS
Declined
Administrator
Thank you for your feedback. We are not considering the suggestion at this time due to the following reason:
This idea has not received enough votes since it was submitted on: 24-07-2019
Sincerely,
Johan Hoffmann
PM, Microsoft