Hi,
We are using Sales Analysis 9,2A (150527), and we have created satellite stores at multiple locations all using Adagio and running off an RDP server from a central location, basically our own private cloud running Adagio.

Each store has a defined location, and it's own customers.

We are trying to use the Maintenance function in Sales Analysis to Scan Data from other Adagio systems (locations), to scan the Adagio Order Entry sales at other store locations, to get a consolidated view of sales of all locations.

We have put filters on our Gridviews so that the interlocation quantities and sales $ are excluded.

We thought this functionality used to work and it allowed you to select the path of the other system that you are hoping to scan. Right now, this version of Sales Analysis seems to be only allowing you to scan the same Order Entry system that you can retrieve from. The documentation sort of alludes to this functionality but is vague.

Is there a setting that allows you to retrieve other OE data from other Adagio OE datasets? It seems weird that you would have a retrieve and scan function on the same dataset and not allow you to select the path?

Or if this is a limiting functionality, what is the file name that has the OE sales details to feed Sales Analysis, and we'll use the Adagio Console to run an automation macro to copy the file out, rename it and retrieve it into the primary reporting dataset.

Thanks,
Brian

Hi Brian,

Scan Data from other Systems (OE and Invoices) has always been for the same data location and extension, and has never allowed browsing to a different company. Same thing for Retrieve data - always just for the same company with no browsing elsewhere.

If you want to copy the retrieval file from OE 9.2A, that file is OESSISY.dat.

Please make sure that you have the SalesAnalysis 9.2A (2016.06.08) service pack installed if you choose to copy that file from one place to another, in the case where the live OE data is at one location, but the intention is to send the created OESSISY data file to a different place. The reason is that when creating the 'dummy' SalesAnalysis data at the OE site, the version of SA you quoted had a problem during the data creation process - and thus caused problems in OE and the invoice audit list area.

If you have already created the dummy SR data for the satellite OE locations, there may be a missing line in the SRWININI.dat data file, that you could use a text editor to manually put in to solve a potential problem (which really is to indicate to SalesAnalysis to look for a 'new style' file):

[ConversionOE81D]
Done=1

Hope this helps.