Hi. I am the new IT Manager of an auto supplier that is initial stages of an implementation of Epicor 10. We will be migrating off of our legacy system over the next year or so. Being an auto supplier, we rely heavily on traditional, automated EDI for our forecasts, releases, and ASN processing. We trade EDI with the OEMs (i.e. Ford/GM/Chrysler) and other Tier 1 customers/suppliers. We communicate to these trading partners using 2 VANs (OpenText & Covisint). Current communication methods are baked into our legacy system using FTP and bisync (yuk) communications.
We have engaged TIE Commerce to assist with EDI map creation. My question to the group here is how are the communications done between Epicor and our VANs? What software is used to actually send/receive transactions with the VANs. I’ve used Inovis Trusted Link previously to perform this type of communication. I’m new to the Epicor world and would like to know what is available/recommended.
We are also currently in process of migrating from an old PC based EDI system(Inovis Trusted Link…now OpenText) with our legacy Epicor product to E10 and TIE. We decided to go with the Epicor VAN for what it’s worth. Communications occurs using the software that was bundled with TIE, CLEO Lexicom. Your TIE workflows will place inbound files in a specific folder location and Epicor will put outbound files in their specific location. The Lexicom software will take care of the transfers to and from the VAN.
Feel free to contact me off list for any additional questions.
Mike Lowe
Director of I.T.
Connor Manufacturing Services
USA-Singapore-China-Malaysia
Phone: +1 (503) 465-3904
Cell: +1 (949) 793-3433
Web: www.ConnorMS.comhttp://www.connorms.com/
[cid:image003.jpg@01CDF32C.EDA5D070]
“Celebrating 100 years of Service”
Any and all technical data identified in this communication as EAR or ITAR Restricted Information is controlled under the Export Administration Regulations (EAR) and under the International Traffic in Arms Regulations (ITAR). The EAR / ITAR restricted information may not be exported to a foreign person, either in the United States or abroad, without a license or exemption from the U.S. Department of Commerce and/or the U.S. Department of State as it applies.
Thanks for the feedback Mike. Not sure we want to add the complexity of migrating VANs at the same time as we switch our ERP system. Would like to be able to leave the VAN relationships untouched.
I had similar feelings. But, we were going to have to have a different kind of account with the Inovisworks VAN (our PC based system used a unique communication protocol not compatible with the new software) so we just decided to make the change.
As an aside, the Lexicom software should be able to handle any type of communication requirements you throw at it.
i believe the TIE software has a component which pulls in your VAN transmit files to a shared area on your local network. from there the epicor EDI import process begins.
Thank you for the information. Is the TIE integration software something that would have come originally from Epicor, or will we need to license that from TIE themselves?
