Thanks for the answer,
Yes at table level the problem indeed is that we have the same lot with different expiry dates in Item Ledger Entry; this is as a result of the reclass. journal.
I just want to confirm with the community that this is a bug in Microsoft's code, and if there is any news about the release of a hotfix.
We can't just modify the item ledger entry, as we need a permanent solution in the case a lot is reclassified and changed the expiry date.
We're thinking maybe to modify the code of the reclass. journal, so that the wrong expiry date record is marked somehow but a hotfix would be better of course. :)
