Overview: Abbadabba’s does everything in Retail Pro 9 with the exception of reporting, for that, they use Retail Pro 8 reports. Since the two versions can communicate via ECM, Retail IQ has set up a process for Retail Pro 9 to push data down to Retail Pro 8 every 5 minutes or so. This applies to just the main/warehouse location.
Computer Involved:
SimpleHelpLocation Computer Name
Warehouse/Tucker AbbaCorpServer
General Sequence of Events - Retail Pro 9 ECM runs a batch file which:
1. Processes out for the V8 station
2. Copies the XML files to the proper \Proc\In folder inside the V8’s ECM installation folder
3. Moves the XML files to the proper \Out\Sent folder inside the RP9’s ECM installation folder
4. Runs Process In from the V8 ECM installation to process those XML files into V8
5. Copies any the “confirmation files” *.cnf from V8 (C:\POS\V8\ECM_V8\Polling\001000A\OUT folder) to the proper RP9 ECM folder (C:\POS\ECM\Polling\001000A\PROC\IN folder)
6. Moves those *.cnf files from the V8’s C:\POS\V8\ECM_V8\Polling\001000A\OUT folder to its C:\POS\V8\ECM_V8\Polling\001000A\OUT\SENT folder.
7. Runs an RP9 ECM Process In for the V8 station to process in any confirmation files
8. Runs a Recalc SRO in V8 to update SRO in V8.
How it works:
It all starts with the directories involved:
If you expand the “V8” folder, you get this:
Once you know the directory structure, all you need to know is the batch file and how it runs. The batch file is located in C:\POS\ECM\Batch and looks like this:
Summary: Essentially, since RP9 and V8 are stored on the same server, there is just one batch file that handles all the updating of V8 data so Abbadabba’s can run some V8 reports.
Common Issues:
There are no common issues that occur with this setup. The only thing that is requested a few times a year at most is that Abbadabba’s will make a bunch of DCS or VC changes to inventory and ask for the V8 data to be updated. This involves backing up V8, turning off the scheduled task, deleting the V8 data files, then doing a manual Process Out of ALL RP9 data down to V8, and then syncing it back and forth until it’s caught up. This process can take the better part of the day to complete and is typically done over a weekend to limit the impact of losing V8 reporting during the weekday.