We are using custom software that is integrated to our current order processing. Luckily we are only doing 850/855 and 810 at the moment. And I'm sure 856 in the future.....
Where it's getting difficult (at the expense of expense) - is doing direct ftp with partners to bypass the VANs and The IMO absolutely outrageous transmissions costs. So we are doing a combination of XML with our VAN, and edi with our direct partners - the XML side doesn't need 997's Whereas the edi side does. What our system does is converts the XML -> edi , then converts the edi to an internal multivalued format Our order entry, and billing is based off that internal format. Then when we need to send out a document The internal format is converted back to either edi or xml and then FTP'd to each of the appropriate servers. It's annoying in every time we gain a new partner, the software needs to be tweeked to each of their uniqueness Within their document requirements. As standards go, EDI is the most non standardized standard I have seen. -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Robert Frailey Sent: Tuesday, December 31, 2013 11:46 AM To: U2 Users List Subject: Re: [U2] EDI Question... EDI brings up a whole can of worms for me in the new year. We currently use softshare as our van, I would really like to do EDI in house or find something more affordable. Does anyone have any suggestions. Thank You Robert Frailey Manager Information Systems Utah Medical Products Inc. Utah Medical Products Ltd. Femcare-Nikomed Ltd. Femcare Australia rfrai...@utahmed.com 801-569-4016 _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
