SQL trigger on offline inventory table?

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

Reply to
kskinne
Loading thread data ...

another option I'm considering is adding a bit of code to an existing class module that i'm already using, that performs some tasks if the transaction type is a recall for return. i thought about setting something up like this:

For x = 1 to posSession.Transaction.Entries.Count If .Entries(x).Item.ItemType itemtypeSerialized And _ .Entries(x).Item.ItemType itemtypeStandard Then .Entries(x).ReturnReasonCode = "" End If Next x

to clear out the reason code on entries where the item entered is not a standard or serialized item. but .Entries(x).ReturnReasonCode = "" does not accomplish this. how can i modify this code so that when run, it correctly removes the reason code off of noninventoried items that appear on the return receipt?

thanks, kevin

"ksk> We have our SO configuration set up so that reason codes are required on all

Reply to
kskinne

..Entries(x).ReturnReasonCode = Nothing

- Evan Culver New West Technologies

ksk> another option I'm considering is adding a bit of code to an existing class

Reply to
Evan Culver

thanks for the reply - unfortunately that is not working either. i know that my code is firing correctly because other parts of it are working, but this is not removing the reason code off of any of the noninventory entries. any other ideas?

thank you, kevin

Reply to
kskinne

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.