Open Forum

Like what you see? Discover the benefits of the D365UG/AXUG Community. Learn More

Topic: Released items must be reversed first.

  • AX 2012 R2

1.  Released items must be reversed first.

Posted 10 days ago
​​I am receiving this message when attempting to delete and/or end a couple production orders, any ideas on what causes this?  Thanks.

------------------------------
Trent Aschliman
Business Analyst
Fort Wayne Metals
Fort Wayne IN
------------------------------


2.  RE: Released items must be reversed first.

Posted 7 days ago
​To delete a production order it must be in the created status. To do this you can use the reset status function to take it back to created , depending on your setup you may have to do several resets taking it a step back at a time. When this order is taken below started it will automatically reverse any journals you have posted such as Pick route or RAF. If you get the error on trying to end a production order it simply means that you have a quantity that has not been released, to handle this the simplest action to take is to do a RAF and in the general tab set the accept error to true, since you are trying to end the order, you should also select the end mark pick and end mark route and end job checkboxes to put your order into a reported as finished status with the next status being end.
Hope this helps

------------------------------
Paul Martin
Expert ERP Analyst
TempurSealy Inc.
Trinity NC
------------------------------



3.  RE: Released items must be reversed first.

Posted 6 days ago
​Paul,

Thank you very much for your suggestions.  We are currently doing what you suggested and are still receiving the error.  Any other suggestions would be appreciated.  Thanks.

------------------------------
Trent Aschliman
Business Analyst
Fort Wayne Metals
Fort Wayne IN
------------------------------



4.  RE: Released items must be reversed first.

Posted 6 days ago
Hi Trent -

You should be able to reset the Production Order Status down to Created as Paul recommended. This reverses all prior work.

Are you getting a hard error when you try to reset the Status?

Thanks....Dave

------------------------------
Dave Phillips
MSFT Senior PFE
Microsoft
Fargo ND
------------------------------



5.  RE: Released items must be reversed first.

Posted 6 days ago

​Hi Dave,

Here is the warning message I get, the one thing I noticed is that the production order is referencing a SO that has been invoiced.  All Markings and remaining reservations have been removed.  Thanks.


------------------------------
Trent Aschliman
Business Analyst
Fort Wayne Metals
Fort Wayne IN
------------------------------



6.  RE: Released items must be reversed first.

Posted 6 days ago
Is the production order you are trying to reverse an independent production order or does this have pegged supplied production orders?

------------------------------
Marek Chrzanowski
Manufacturing Engineer
Cyclone Mfg
Mississauga ON
------------------------------



7.  RE: Released items must be reversed first.

Posted 5 days ago
​Marek,

Yes, the item on the production order is setup to pegged supply.  I did, however, reset to Created and removed any residual markings to ensure the referencing was broke.  Is there more I need to do to ensure there aren't any references?  Thanks for the reply.

------------------------------
Trent Aschliman
Business Analyst
Fort Wayne Metals
Fort Wayne IN
------------------------------



8.  RE: Released items must be reversed first.

Posted 5 days ago
​Have you tried resetting the pegged supply production orders to created as well then tried to delete?

------------------------------
Paul Martin
Expert ERP Analyst
TempurSealy Inc.
Trinity NC
------------------------------



9.  RE: Released items must be reversed first.

Posted 4 days ago
I have tried in my TEST environment and the following happens for Pegged Supply.

Top Level Production Order status can be backed to Estimated without References checkmark.  However when you go from Estimated back to Created AX 2012 R3 is automatically placing checkmark References on.  So when the Top Level Production Order status is changed to created then all pegged supply produciton orders statuses are reversed back to Created.

I have a suspicion that 1 of your pegged supply production orders is not fully reversed on the status.  Check 1 by 1 if they all are in created status.

Let us know.

MArek



------------------------------
Marek Chrzanowski
Manufacturing Engineer
Cyclone Mfg
Mississauga ON
------------------------------



10.  RE: Released items must be reversed first.

Posted 4 days ago
​Marek,

Thanks for the information, I will definitely check that out.

------------------------------
Trent Aschliman
Business Analyst
Fort Wayne Metals
Fort Wayne IN
------------------------------



11.  RE: Released items must be reversed first.

Posted 4 days ago
Marek did an excellent suggestion. If the message seems to make no sense in the context of a single production order, it could very well be caused by a referenced production order. I have seen this. Using referenced production orders is  feature but it opens of course the door for complications.

I have never seen this message. The terms "released items" certainly does not talk about our "item masters" because it would have said 'released products' in that case. And there is nothing to "reverse" on items anyhow. I am adding a link to the technet explanation on reversing prod order status, which is good info to have in any case.
About reversing production order status [AX 2012]
Microsoft remove preview
About reversing production order status [AX 2012]
When you reverse the status from Scheduled back to Estimated, the scheduled start and end dates and times are removed. Capacity reservations that were made during scheduling are removed, and jobs that were created during job scheduling are deleted. All information about operation scheduling and job scheduling that is recorded in the Production order details form is reset.
View this on Microsoft >



What we sometimes can do is double click hard on that error.. it does reveal the code where the error was generated. This can give a big clue to even a non programmer.
If the problem is not fixed, I would report it to Microsoft and they would be able to tell you what the error is really trying to say.

------------------------------
Evert Bos
AX Solution Architect
Sikich LLP
Naperville IL
------------------------------



'