Witnessed in 3.6.2, although I assume it affects previous versions too.
When you cancel a lineitem, it also deletes any attached copies in the catalog. This is a nice timesaver. However, it blindly deletes those copies, no matter what state they are currently in.
It's entirely possible that line items might need some cleanup work, especially at fiscal year end. In our particular circumstance where this came up, we needed to release encumbrances from line items that were no longer valid. The way to do that is to cancel line items. But in the intervening time, for several reasons, those copies had been cataloged and were in various statuses, including checked out. So when the line items were cancelled, those copies--even the checked out ones--were auto-deleted.
I'm not sure if the solution is to put a check on the item deletion to see if the status is anything other than on-order (would any other statuses need to be included?), or if it should check the item statuses and throw back a confirmation message to let the user know that it will delete those copies? Or if there should be an option to create a cancel reason that doesn't keep debits but does keep copies?
But whatever the solution, it's entirely possible to need to make Acquisitions edits that shouldn't automatically affect the catalog.
Found this old bug that is somewhat related and including it here in case it's useful: https:/
The original bug report is on a different topic, but it does touch on including an alert before deleting the copies when you're trying to delete/cancel a lineitem.