Can anyone explain the 1 EDI Source integration with E10? All the Tech Guides reference TIE which is what I’m familiar with. I can’t find anything about 1 EDI Source but I know Epicor purchased them several years ago. With eVision going away I’m trying to understand if it makes sense to transition to 1 EDI Source or stick with the new TIE product. Any good or bad experiences to share?
Thanks,
Jennifer
So what was your decision Jennifer? I am at the same point deciding between them.
No decision yet. Personally I feel like going forward 1 EDI Source will be the best choice. In the past the biggest issue with EDI has been every version upgrade killing the maps. My hope is that 1 EDI Source will provide more support for this going forward since they are owned by Epicor.
With E10 you can create your own EDI Definition files as excel files. Then use this excel file to manage the output. As long your excel file does not change and RDD has the field not excluded, your EDI output file will always be the same. Also adding fields is also easy to manage, since you can then add the new field at the end of the list.
The excel EDI definition can be created from Actions>Generate EDI definition under Report Style.
Vinay Kamboj
@Vinaykamboj Thank you for that thought as I had not thought about that. Can all RDD be exported that way? What about XML?
@jentar17 we are looking to sign with 1 edi source for a number of reasons including what you have mentioned. This could be today or soon say this week.
John
There was a bug in 10.2.100 that was triggered by using EDI Definitions. Epicor would no longer output the Company row for each new document, so VANs that use the Company row to detect the beginning of a new document would merge all your documents together. I wrote library for reading and manipulating EDI files that worked around this bug and another one. One of the bugs was supposed to be fixed in a later 10.2.x release, but I can’t remember which.
Consulting companies also offer EDI services. I wrote an end-to-end solution when I was a consultant, they may even still offer it as a product.
Though, I intend to write my own again if our company goes down the EDI route anytime soon. Pretty cost effective. 
We use a third party VAN which manages the maps. Very cost effective, and only ongoing charges are based on the volume of data that goes through.
John,
Did you all end up going with 1 EDI Source? How is it going?
Jennifer
We did select 1 EDI source and we have been working for the last month. There where so additional setting we needed to complete first. First testing on 850,856, and 810 to occur today/tomorrow. We made to call to go with the bi directional communication of rest api using json files rather then traditional flat file. big reason is for reporting to make sure we are not missing orders, invoices or asn.
Over the next 2 weeks I will have some more updates and we are looking to move 40 accounts during phase 1.
Phase 2 will look at smaller accounts and the user of a portal entry / csv / pdf to bring in those orders and remove the manual step. (Last 1st qtr/2nd qtr 2022)
Phase 3 would for the supplier side (2nd qtr 2022 ).
Hope that helps.
so far some frustrations but have worked through them pretty quickly and the team seems to be right on point.
@jentar17 or anyone if you have specific questions please let me know and I will answer as best as possible. Today I finished the set up of electronic reports (creating JSON files). Creating new data directives for Invoice and ASN (from Customer shipment entry and master pack as we send from both).
Testing tomorrow.