Configuring Automated Data Transfer in Counterpoint

Article Number: 355 | Rating: Unrated | Last Updated: Fri, Jul 19, 2013 at 10:59 AM

Purpose:
Configuring the Automated Data Transfer connects Counterpoint to your NCR Retail Online (NRO) store, so it automatically transfers data between both products.

*IMPORTANT: Before installing the Integration Agent, please remove all CPTOCPOL-###.txt files from your Ecommerce directory (CPOnline folder). To do so, follow these steps:

1. In Counterpoint, navigate to Setup / Ecommerce / Control . From the main tab of the ecommerce control file, click the hyperlink in the field labeled Ecommerce Directory. This will open your CPOnline folder. Either completely delete all of the CPTOCPOL-###.txt, or archive them to a sub-folder.

Solution: Use the ADT tab on the Ecommerce Control window ( Setup > Ecommerce > Control ) to enable the automatic transfer of data between Counterpoint and your NCR Retail Online (NRO) store.

To enable Automatic Data Transfers, select the check box Use ADT .
NRO does not require an FTP site , FTP user or FTP password but these values must be populated for your scheduled task(s) to work. Populate these values with the following data:

FTP site - ftp://adt.nrostores.com

FTP user - ADT

FTP password - 123456

Note: Selecting the Test connection button will return an error. This is expected, since the FTP data is invalid.

Important Note: ADT is another layer of automation on top of the Integration Agent (IA). The only functions ADT serves with regards to NRO are creating publish files on a schedule and importing orders that have been pulled down by the IA.

If you see errors in Counterpoint stating it could not transfer data to the FTP site, this is normal. These errors can be ignored. FTP credentials are required in Counterpoint to activate the ADT function, but NRO does not require the use of an FTP location to pass data to NRO. The credentials above are dummy information so that ADT can be used.

TIP: If you have not defined the ITEMS and UPDATE publish codes used by ADT, at this time, review the Configuring Your ADT Publishing Codes article for instructions on creating these publish codes, then return to this step to complete ADT setup.

Map the Full publishing code to your ITEMS publish code.
Map the Update publishing code to your UPDATE publish code.

In the # of updates between full runs field, specify 23. This is the number of times ADT will use the Update publishing code before using the Full publishing code during its schedule.

TIP: To calculate the value to enter in the # of updates between full runs field, divide the number of minutes in a day (i.e., 1440) by the number of full updates you want to occur each day, divide the result by the number of minutes between each scheduled instance of the ADT task, and then subtract 1 (i.e., ((1140 ÷ # of full updates) ÷ scheduled task frequency) – 1 ).

The # of updates done field indicates the number of times the Updating publishing code has been used by ADT since the last use of the Full publishing code . You can modify this value to reset your ADT schedule or to change the number of quantity and prices-only updates remaining before the next complete update.