I have an RMS 2.0 FP2 environment running Headquarters with several stores. All of our customers are setup as Global Customers.
We just opened a new store last week. Prior to the store opening, we had run the usual worksheets, including the 401 worksheet. At first glance, it looked Ok, and we thought that all of the customers from HQ downloaded to the store.
Well, nearly all, it seems.
The manager at this store used to be the manager at another store. She noticed that some of the customers which were in the old store are not showing up in Store Operations at this new store.
We checked and verified that the customers from her old store are in Headquarters.
For some of the customers she identified as missing in the new store, we edited the customer in HQ, adding a space to their name or billing address, just enough of a change so HQ would recognize that the customer information has been "touched". The next time a 401 worksheet is run for the new store, it downloads that customer to the new store's Store Operations system.
This old store had several thousand customers, and we don't want to manually "touch" each customer.
Also, even if we change the customer's name or billing address, the shipping address may not get reloaded in the store.
Is there some way that we could force all customers and their shipping addresses to be redownloaded to the store? I didn't see a worksheet in HQ to force customers from HQ down to the store; that usually happens automatically when the customer in HQ is added or updated (as we saw when we "touched" the customer in HQ).
If we need to run a SQL script against the HQ database, updating the LastUpdated field on the Customer and ShipTo tables, then run a 401 worksheet, that's fine.
However, I don't have the slightest idea how or even if I should update the DBTimeStamp field on those records in HQ. That looks like a hexadecimal value, and I'm assuming it's some sort of offset from a fixed datetime (maybe the number of milliseconds since a baseline datetime), but that's one field that I have never altered.
Any suggestions?
Bill Yater
Blue Horseshoe Solutions, Inc