When using packages together with the barcode app sometimes you may face the following error:
The issue usually happens like this:
- A user scans a package in the barcode app, but for some reason the move is not completed and the transfer remains in draft (instead of confirmed).
- Another user tries to scan and confirm the same package in a different transfer or another location.
The system correctly blocks it and shows the above error, so it's fine from a system perspective, but in real life we may have many draft or open transfers. Therefore it’s very difficult to manually open them one by one just to find out which transfer contains the package that is causing the conflict in order to delete or cancel it.
Is there a way (via UI, debug mode, or even technical/log SQL search) to know exactly:
- Which package is causing the problem, and
- Which transfer/move that package is already scanned in?
That would help us resolve these situations much faster without trial and error.
Thanks in advance for any tips or best practices.
