Hook type to use

I need to prevent HQ from changing the primary supplier at the store level. We have stores in multiple states....they often carry the same items but will get them from different suppliers. However, if a primary supplier is changed in HQ and a 250 then processed for one store, if I ever process a 250 for that item and send it to another store, it will change its primary supplier.

Will Hook: 10 SaveSupplier allow me to prevent 250's from overwriting primary supplier for each store?

Reply to
cesmi1
Loading thread data ...

Hooks only work within POS and SO Manager. There are no HQ Hooks, and I don't believe that HQClient will cause the SO hooks to fire.

You could use SaveItem to catch a change to the primary supplier that is being made at the store level and writing it to your own table in the DB. Then you could use triggers or a scheduled job to make sure that the Primary Suppliers are the ones that were set through Store Ops.

I'm assuming that you have done testing to verify that a 250 will in fact change the primary supplier at a store. I've never looked at that myself, but I didn't think that would be included on a 250 - it would be on a 260.

Glenn Adams Tiber Creek C> I need to prevent HQ from changing the primary supplier at the store level.

Reply to
Glenn Adams [MVP - Retail Mgmt]

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.