SAP XI and EDI

[Former Member]

Hi all,

I have some questions about SAP XI and EDI.

We are planning to get the SAP XI to handle EDI message e.g. ANSI 850, but it looks like XI does not handle EDI out of the box. From what I read we still need to buy an EDI adaptor to handle the EDI-to-IDOC and IDOC-to-EDI processing. e.g. Seeburger adaptor.

Actually I don't quite get this, isn't it XI contains a set of tools that allows us to do the mapping? Can we just use those tools to create EDI map without buying the seeburger adaptor? If we cannot create EDI map ourselves, then isn't it SAP XI is just an expensive message router??

Any inputs are greatly appreciated. Thanks.

[Former Member · Accepted solution]

XI has its own built-in message mapping tool (drag and drop GUI), upon which you can do "any-to-any" mapping. You can also do your mapping in ABAP, Java, or XSLT environments if you feel that the message (graphical) mapping tool doesnt enable you to do everything you want.

So yes ... you can use XI's mapping functionality to map from iDoc to EDI format. However, this can be quite a complex exercise: you will need to setup the structure of the (target) EDI message/data type, and then carry out the mapping yourself - depending on the type of interface, this could be quite a complex exercise (typically EDI structures contain a very large number of fields).

Once the iDoc has been mapped into the EDI format ... you will need to transmit (send) the EDI message to your (business) partner system, who is typically outside of your firewall (B2B). This means you need to communicate with them using a secure communication protocol (typically OFTP via VAN in EDI scenarios). And this is where the SeeBurger EDI adapters add value. They enable you to connect to VANs (Value Added Networks) using OFTP (or x.400), and also provide mappings for some EDI scenarios (which you can use).

iWay also provide adapters for this purpose.

[Former Member]

Actually the EDI Adapters are used to convert the EDI Syntax to XML Syntax, then you can use the XI Mapper to map to XML-IDOCS or XML-RFC and call the backend application.

Some Solutions however also ship ready-made map samples and additional tools you need for splitting ,merging, acknowledgement, compression encryption and stuff.

Besdies using the XI mapper, you can also use a one step any-to-any converter. SEEBURGER is offering both options. Eisting Seeburger customers with a lot of mappings normally run them unaltered, and dont use the XI mapper. Using the SEEBURGER provided XI mappings (and extensions like counters, dupicate check and stuff) is an option for XI consutants who have already had mapper experiences.

Greetings

Bernd, Chief Architect

--

www.SEEBURGER.com

[former_member232424]

Hello Jockey Ng,

of course, you can do the EDI-mapping for your own. But you need not only the mapping, you need also an adapter for the necessary protocols, like OFTP.

You can also develop our own adpaters, but for this, you need a lot of time.

We have implemented the Seeburger Adapter to do EDI with partners, but we use XI not only for communication with EDI, we use XI also for the internal communication.

Regards

Stefan

[Former Member]

and what about SmartEdi: Edi-tool written in abap??

[former_member187339]

Hi Jockey,

Go thru these links, they might be useful :

Regards

Suraj