Iain Sharp said Has anyone used the EDIFACT standards to create/consume an EDI solution?  I'd like to determine if I need a third party app to convert to something useful, or if I can write something which will work directly in Uniface (or as a COM/DLL plugin).  If anyone has done similar, could you briefly say how difficult a task it was?  Regards,  Iain  

Hi Iain We did part of the TBG5 (finance) branch of EDIFACT. As all characters in EDIFACT are (printable) ASCII, there is no need to use other languages then UnifAce :-) The major challenge in EDIFACT is to unterstand the logic behind it. Once you got it, it's very easy to write code. Okay, you have to do some counters. http://www.edifactory.e/msglist.D96A If you have any question ... (but it's a long time ago when I did EDIFACT :-) ) Ingo

just adding to Ingo's reply: this is the correct link http://www.edifactory.de/msglist.D96A

Thanks, wow that's a lot of standards. 

Iain Sharp said Thanks, wow that's a lot of standards.   

Hi Iain But you don't need all of them :-) If you want to implement some finance transactions, two message are (almost) enough to initiate a money transfer * PAYMUL (Multiple payment order message) * DIRDEB (Direct debit message) TBG5 defines the necessary messages: http://www.tbg5-finance.org/?mtcemig.shtml This is the first segment, used in all messages: http://www.tbg5-finance.org/unece/mig/tbg5-service-segments.pdf Ingo

Iain Sharp said Thanks, wow that's a lot of standards.   

BTW: ISO 20022 does also define a lot of messages :-) https://www.iso20022.org/payments_messages.page

Yeah, we're looking at EBIS sales, despatch and invoicing, so different messages.  As it happens both the third party and their message broker are being very uncommunicative about how we even get the files in the first place so I'm still waiting to see what they need.