Hi Pete. Well, it is clear that EDI consists of following:
1. communication (no XI) 2. translation (50% XI covered) 3. mapping (100% XI covered) XI provides mapping and (may be with some extra features) translation. Communication is out of XI's scope. Anyway, a simple communication interface can be installed on almost any other computer used for thispurpose. To solve 1 and 2 with SAP XI naturally, you would need some special adapter engine (Seeburger and ATOS have its own) which will act as communication interface and also provide automatic translation (from/to XML). This is a kind of XI add-in... We decided (becose of price) not to use this kind of adapter. So: XI alone will not replace EDI system fully. It provides integration engine, no EDI communication interfaces. XI has default communication adapters as can be seen in attachement (sorry for quality). Other can be bought. As communication interface we are using OFTP communication software RVS (by Gedas) which is able to send and receive EDI files over ISDN, X.25, TCP/IP and others. Currently I am searching for EDIINT/AS2 software solution being able to do the same job over HTTPS. (any recommendations appreciated!!!) Anyway, our communication and translation engines are not part of SAP XI. If you want to replace your current existing solution, it may be an interesting idea to stay with current communication engine (communication itself is not as complex as mapping; you keep your existing licenses) and replace only mapping engine with XI. Another great advantage of XI (which I daily appreciate) is that it supports standard XSLT engine with full J2EE support. The mapping can be prepared and tested with any other XSLT engine (I am using standard Java 5) and after that uploaded to XI. The mapping itself is therefore independent from developer environment and can be created/tested/finihed everywhere even without on-line connection to target XI system. IMHO this feature is not so common in other EDI systems. Gabriel Gajdos ----- Original Message ----- From: "Pete Peters" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [email protected] Sent: Wed, 1 Mar 2006 16:31:22 -0500 Subject: RE: [EDI-L] SAP and XI. > > > We too may evaluate SAP XI and how it may fits into our edi environment > with SAP. I would like to confirm from your message that you in fact > have an existing edi system that is not being replaced by SAP XI but in > fact you are using XI to integrate your edi system into SAP. > > I have been confused as to whether XI can fully replace an edi system > (mapping, translation and processing of X12 data) or whether it is the > new interface replacement for IDOCS. I have been lead to believe both > scenarios are true. > > Regards, > > Pete Peters > > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Wednesday, March 01, 2006 2:43 AM > To: [email protected] > Subject: RE: [EDI-L] SAP and XI. > > Hello! > > We are now implementing EDI solution based on SAP XI mapping > capabilities. > We are using EDIFACT and VDA messages. SAP XI processes IDOCs (inbound > and > outbound) in XML format which is much simplier than natural (text) IDOC > format. > For incomming EDI messages we use following scenario: > 1. receive EDI > 2. Translate EDI to XML (using predefined scheme) 3. Transform EDI.xml > to IDOC.xml using XSLT processor in SAP XI 4. Send generated IDOCs to > target R/3 system (in our case we use 2 target > systems: mySAP Business Suite and SAP SCM/APO). > > For outgouing EDI messages we use following scenario: > 1. generate outbound IDOC > 2. Transform IDOC to EDI-1.xml using XSLT 3. Next transform EDI-1.xml to > EDI-2.xml (adding some generated fields) 4. Final XSLT transformation > (output="text") to resulting EDI. > 5. Send data to adapter interface running on PC with communication > interface (ISDN). > > There are some commercial adapters (ATOS, Seeburger...) which simplifies > this process and provides also communication interface. Anyway these > solutions are expensive and can be substituted by other solutions. > > For further discussion use direct mail contact. > > Regards, > > Gabriel Gajdos > > > ----- Original Message ----- > From: "Uppaji Kothapalli" <[EMAIL PROTECTED]> > To: [email protected] > Sent: Tue, 28 Feb 2006 13:14:23 -0800 (PST) > Subject: [EDI-L] SAP and XI. > > > Hello all, > > we are migrating from Baan to SAP. We are debating on wheher to use > > SAP XI or not. > > Could you please throw some light on this and share any of your > > experiences/recommondations about SAP XI. > > > > > > Also do you know if there is a SAP IDOC readily available for EDI 870 > > (Order Status Report/ Booking and Backlog). > > > > Your response is greatly appreciated. > > UK. > > > > > > . > Please use the following Message Identifiers as your subject prefix: > <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the > list online at: http://groups.yahoo.com/group/EDI-L > > Yahoo! Groups Links > > > [Non-text portions of this message have been removed] . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
