Figuring out order deletion policy

[Borvik]

I'm not sure what others do, but I'm having difficulty in coming up with (and implementing) a deletion policy for orders.

The problem stems from special order items that get ordered, purchasing then purchases the items to come into our warehouse before getting shipped out again to the customer.

Sometimes the customer cancels the order, and the sales rep dutifully cancels it for the customer - without going through proper channels, and we end up with this item in our warehouse that is difficult to get rid of (returning or selling to another customer).

So we implemented a password to delete orders. This presents other problems. Such as the sales rep starting an order, and chooses the wrong customer - suddenly they can't delete it to try again. Or perhaps they are sneaky and delete all the line items and then tell the person in charge that they made a mistake on the customer to get them to delete it.

Is there something in the GP system that can help us solve our problem and enforce this policy?

Thanks.

 

[jazgeek]

you could write yourself a sql trigger that would fire off an email anytime an order line is deleted from an order that has been in your system for longer than say....2 days.

we have a similar problem, and we use this trigger to alert people that someone has done the nasty.

we also have a custom trigger that copies the before and after information to a user table in the database so we have an exact record of what an order looked like before and after modifications.



-----------
and they wonder why they call it Great Pains!

jaz