You have chosen to sponsor your bid up to a maximum amount of .
A new module is required to Import and Export data from/to MYOB to/from SupeRep.
ERP Integration with SupeRep – A Step by Step Guide
1. FTP Location Transfer of ERP files to the WRNTY cloud is executed via FTP file transfer. The customer will be provided with an FTP location, username and password to transfer files. For example: Output URL: ftp://erp.wrnty-online.com/Prod_Output Input URL: ftp://erp.wrnty-online.com/Prod_Input User name: Account_960162 Password: abcdef
2. ERP Output File Formats File formats required for loading Items, Accounts, and other types of entities are detailed in the attached Excel – ERP Integration Template.xlsx. Each entity has a list of fields, which are the column headings. Column headings must be identical to those assigned in the Field Name column. All entities are described in detail in the tabs of the Excel file. The ERP integrator or the on-site ERP admin is responsible for outputting the files in this required format as CSV files. File content must be reviewed to make sure only WANTED data is being loaded into SupeRep, and filtering must be adjusted accordingly.
a. File naming conventions File naming conventions are detailed for each entity at the top of each tab in the ERP Integration Template Excel file. Each entity is transferred in a file named by a generic convention, allowing SupeRep to pick up the file and know exactly what type of data it contains. Here is an example of one convention, which can be applied to understand them all: The Items-Inventory file should be named as follows:
A-I-YYYY-MM-DD_HHMMSS_Distributor_ID.csv (also supported: A-I-Distributor_ID.csv)
A file time/date-stamped from August 24 2012 at time 14:32:45 from the distributor with ID number 153359 would be named:
A-I-2012-08-24_143245_Distributor_153359.csv (also supported: A-I-Distributor_153359.csv)
b. Rate of file transfers WRNTY is constantly checking for files in the Prod_Input directory. The maximum recommended rate of item data file transfers from an ERP system to SupeRep is once every hour. The recommended rate of account data file transfers from an ERP system to SupeRep is once daily. Transfers at a higher rate can slow down your ERP.
3. Initial Creation of Brands and Filters: A sample ERP output file with Items is loaded via the SupeRep manager; this will initiate the Brands and Filters in SupeRep and ensure that data is being displayed in the SupeRep catalog according to the customer's requirements. This is done by the SupeRep admin in the usual way using the Excel mapping procedure.
4. FTP and integration
Once files are being transferred on a regular basis to WRNTY's FTP server, updates will automatically be loaded into SupeRep. Automatic generation of the files in the required WRNTY format, with the required naming convention as well as their transfer to the FTP location are the responsibility of the ERP admin or integrator on the customer's end.
5. Loading Product Image Files Images are loaded via the SupeRep manager interface on a browser. Images are uploaded in bulk. Image files must be named as their corresponding item code (exactly). Files selected will be automatically paired with their items in the catalog. (Images are not loaded from the ERP system. Images stored there are often of lower quality)
6. SupeRep Orders Integration
ERP integration of orders submitted on SupeRep App
Select "Export Order to ERP system" in the ERP -> ERP Setup option in the SupeRep Manager
Submitted SupeRep orders will automatically be placed in the "Prod_Output" FTP directory in XML format (default) or CSV format (one file per order).
The ERP admin or integrator on the customer's end is responsible for checking this FTP directory periodically, grabbing the order files, and then processing them within the given ERP system.
A sample order file in XML is attached.