We have our SO configuration set up so that reason codes are required on all returns. All of our return reason codes are set up so that the items always get sent to offline inventory first, then the mgr. makes the judgment call on returning to main, transferring out, etc.
When a transaction that is returned contains both inventory and non-inventory type items, it assigns the reason code selected to both types of items, and sends them all to offline inventory. Then when someone returns a non-inventory item to main inventory or transfers it out, it is changing the quantity field of the inventory tab under the item's properties, even though it is non-inventory (???) This seems like a bug to me that MS needs to address.
However, in the meantime I was considering putting a trigger on the InventoryOffline database, so that when a record is inserted, it will check when itemtype it is, and if it is a noninventory item, it will delete the record from the inventoryoffline table. I plan on testing this on a test database first.
Can anyone think of any problems that may arise from doing this? Does this sound like it would be alright? Am I missing anything that I should be considering?
Thanks for the input, Kevin