Hello together,
I am also facing the same issue now.
A production order that should have been ended 31.12.2022 has a report as finished on 02.01.2023. With the report as finished a time consumption is also booked (also on 02.01.2023).
So first when I try to end the production i got the error, that there is a report as finished on 02.01.2023 and I can not end it.
Then i reversed the report as finished AND the time consumption 1:1.
I tried to end the production again - now i get the error that i have a time consumption on 02.01.2023 and therefore can not end it.
So somehow, the reverse of the report as finished itself worked - but not the reverse of the time consumption?!
Error: "Production order XXXX has time consumption on date 02.01.2023 and cannot be ended before that."
Does anybody has a idea to this?
Thanks and BR
Jonas
EDIT:
I created a Microsoft ticket for the issue and received the following answer.
Short summary: It is not possible to reverse time consumptions just like picking lists. The only way to handle this issue would be to reverse the whole production order until all journals are reversed and than create all the journals again and post them with correct date.
Full answer:
The reason why we are still getting the error like "Production order %1 has time consumption on date %2 and cannot be ended before that." is because, even if journals for route postings have been manually reversed, this type of transactions/postings do not behave in the same way as material transactions.
The difference between reversing material transactions/postings and the route transactions/postings is that, while reverse of material transactions is marking inventory transactions as reversed, for the route transactions the system behaves in a different way.
So, if route transactions are reported as of date later than ending date (e.g. human error class of issues) it will throw the error.
Now, the option to address the situation would be to use the Reset menu option to return the production order to a status prior to Started.
This action will reverse all posted journals and will mark route transactions as cancelled.
So, please look into the option of resetting the status of production order back to Released and reprocess all journals with proper dates.
Above information is also stated under below LCS link which was created when same situation was reported to Product team:
https://fix.lcs.dynamics.com/Issue/Details?bugId=674818&dbType=3
