Am 12.09.2014 17:16, schrieb Dominique Chabord: > Le 12/09/2014 16:52, Axel Braun a écrit :> > >> I would avoid EDI as much as I could. > EDI is the only official approach to do it
We have to deal with such requests in real life and the two statements above are right: it's a standard and a p.i.t.a as well. So for example we have one customer which could get his delivery requests via EDI - but as protocol Odette File Transfer Protocol is used. This requires a dedicated hardware setup which is expensive and very old fashioned. But this is usual in all communication related to Volkswagen, because everything is set up since ages and every change needs expert groups and millions of meetings. So they implemented a so called WEB-EDI for suppliers without the needed infrastructure which is nothing more than a web frontend to get and put some data into a SAP based system. But it would be great if Tryton supports a subset of EDI. The first what we have to care about is that there is no EDI - there are a lot of standards and protocols - SWIFT in Banking, openTrans for interchanging documents, ANSI ASC in America, VDA in German automotive industries but ODETTE in France .... As protocols everything from HTTP to X.400 is used. In fact EDI means nothing if you don't know the needed structure of the message and the used protocols. So possibly we talk about implementing EDIFACT and there from a subset of service messages which are covering the concepts of the core modules. Possibly we should have have a talk about this issue at Unconferences - I could ask at HTWK if there is someone who can give us a general overview about this .... Jan
