There is a department within my company responsible for adding NEW items into HQ and for UPDATING existing items (price changes, etc.) in HQ.
Can someone explain to me (in terms that can be understood) if I should run a WS 260 or a WS 250 to "push" the data out to the stores? Under what circumstances should each be run?
Thank you.
The dynamic store data - prices, cost, and quantity, are store-level data and should be changed with worksheets 30x. The 250 does not change these fields.
If you run a 260 after the item is already at the store, all fields at the store level will be overwritten with the HQ data. This might be the intention, but rarely would you want to do this.
I'd set up security so that only you NEW item people have access to the 260.
As much as possible try NEVER to use 260. When you make a new item 250 will also send the new item to store. Using 260 is exceedingly dangerous:
- it overrides prices - it overrides inventory - it overrides cost
The 260 worksheet is when your store info is so bad that oyu cannot rely on. Then at least 260 will make the store and HQ show the same. After which you need to doa stocktake and progress from there.
Afshin Alikhani - [ snipped-for-privacy@retailrealm.co.uk ] CEO - Retail Realm = = = =
Never run a 260. Always use 250.
Glenn Adams Tiber Creek C> There is a department within my company responsible for adding NEW items into
Huh?
You MUST do a 260 for new items. A 250 fails if the item does not already exist at the store level, doesn't it?
Luminox's question deals with new and updated items, so the 260 would certainly apply.
"Glenn Adams [MVP - Retail Mgmt]" wrote in message news: snipped-for-privacy@TK2MSFTNGP06.phx.gbl...
No, a 250 will send the new item to the store. Afshin gave a better reply that should explain the difference. I kept that one maybe a bit too concise:)
Glenn Adams Tiber Creek C> Huh?
I stand corrected, however, I still do not see the benefit of a 250 for new items. The 250 does not update the price, which you are typically trying to send to all stores for new items.
"Glenn Adams [MVP - Retail Mgmt]" wrote in message news:% snipped-for-privacy@TK2MSFTNGP02.phx.gbl...
Maybe it's a special behavior for new items. New items sent to a store using a 250 will indeed get a price - run one and check it out...
Glenn Adams Tiber Creek C> I stand corrected, however, I still do not see the benefit of a 250 for new
Wow - I did not know that. That is directly contrary to what the documentation says.
That's actually good news because now I can further restrict the 260 for more staff and avoid mistakes with overwriten prices, costs, and quantities.
"Glenn Adams [MVP - Retail Mgmt]" wrote in message news: snipped-for-privacy@TK2MSFTNGP04.phx.gbl...
What worksheet will remove alias's from Store operations ?
John M.
"Jas> 260 is for new items.
You should avoid at all cost the use of 260 as it overrides a lot of info at stores that you do not need. In either case t cannot resolve the issue with Alias or other such similar issues [for example if you change the component of an assembly delete a component and add a new component at hq - the component hat is deleted does not get deleted at store]. I have a whole series of free scripts to resolve these issues. Send me an email.
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.