| Purpose & Benefits |
|---|
| This function lets you import into TAS a set of Sales Orders in an ASCII CSV text file, which has been produced in accordance with the specification for Freeway Commerce’s Spectrum Pro from EDI orders received from your Customers. |
Important
Before you start to import EDI Sales orders, ensure that all the Setup Procedures have been followed – if not, the imports will fail. The file containing the records for import must be output from your third party software or spreadsheet as a CSV file and stored in an accessible folder. The order, format and size of the fields/columns for each record are critical for the import to succeed. Full details of the current file specifications, which must be used to output your data from your third party software, are documented separately in TAS Data Transfer File Specs which you can obtain from the Infoplex website, together with a TAS Data Transfer Toolkit containing sample files. It is crucial that you and/or your third party software provider follow these specifications. The specifications also give you useful information about how the program behaves if the import file contains blank or invalid data in the various fields/columns. To maximise performance, the data import process requires the exclusive use of the TAS Sales Order files. All users are therefore required not to use the TAS Sales Order system in the target company during the import process.
You need to ensure that the CSV file is correctly named and located in the correct folder, otherwise you will get a “file not found” error message (use Maintain Central Information to set the filename and correct folder).
TAS Delivery Addresses checkbox
If delivery addresses in the import file are to be ignored (the default), you can tick this checkbox to ensure that only those set up in TASBooks are used, if any.
Click the Import button to continue. When the import has completed you are informed by the final statement in the progress bar. If there have been any errors you are asked to check the Log file which is created for each import run. To troubleshoot any errors, you can use the Troubleshooting ASCII CSV File Data Errors section in the Appendices.
Click the Close button and, in the case of errors, you are asked if you wish to view the Log file.
The import file is renamed to help prevent processing twice by mistake and the Log file is assigned a corresponding name.