Share
ReportHi everyone,
I encountered an interesting manufacturing scenario in Business Central and I'm curious whether this behaviour is intentional or if I'm missing something.
I had a released production order where output/capacity activity was posted to a routing operation, then it was discovered the finished good/item number needed to change as a mistake was made when the production order was created.
To correct the issue, I used the standard reversal functionality and reversed the related production transactions. The original entries remain for audit purposes, but matching reversal entries were created and the net operational impact was removed.
However, when attempting to delete or correct the routing operation afterwards, Business Central still blocked the change because Capacity Ledger Entries existed against that routing line.
The error was:
You cannot delete Released Prod. Order Routing Line XX because there is at least one Capacity Ledger Entry associated with it.
What I'm trying to understand is whether Business Central intentionally treats:
Activity that still has an effect, and
Activity that has been fully reversed
the same from a routing editability perspective.
I completely understand preserving the audit trail. What surprises me is that even after reversing the transactions, I still cannot perform what feels like the final correction.
Is there a technical reason for this?
For example:
Costing considerations?
WIP integrity?
Historical routing references?
Something else?
Or is the validation simply based on the existence of Capacity Ledger Entries regardless of whether they have been reversed?
I'd be interested to hear whether others have encountered this and whether anyone has looked at the underlying AL logic.
All responses (
Answers (
524
