Data Synchronization Monitoring in Multi-Site Version 7.5.X

Under normal circumstances, data flows reliably between  a Hub Location and your remote stores when Multi-Site is used.

However, over time, polling errors related to phone line/modem instability can occur, Software errors, such as  "Batch Out of Sequence" conditions, that have gone undetected can create situations where the data is not in sync between one or more locations.  If there have been periods when this has been and issue, left unresolved, the situation can become unnecessarily more complicated.

Evidence of Synchronization errors can also be found in the daily Multi-Site error (MSERR.*) logs.  They are located in the "MSOVN" sub-folder of your CounterPoint Top-Level directly at each location.  Examples of Multi-Site import errors are:

• Cannot update IMITMF (followed by a key that includes the item reference) - Item is not on file at this physical location.

• Cannot update IMINVF (followed by a key that includes the item and stocking location reference) -  Item Inventory Stocking record for location is not on file at this physical location.

• Cannot Update ARCUSF ((followed by a key that includes the customer number) - Customer is not on file at this physical location.

As a general rule, the Multi-Site software assumes that the Hub information is always correct. There is a utility that allows sending replacement data (Set-up, Items, Customers, etc.) to the remote stores.  However, this won't deal with issues outside of the norm, such as where there are items at a remote store that do not exist at the Hub.   Resolving this sort of issue involves doing work that is more invasive and is not in the standard documentation.

Please contact the CCS Retail Systems Support Department if you need further assistance in this area.