Professional Documents
Culture Documents
Subscrib
SAP XI supports EDIFACT e
Béla Suranyi
Print
Business Card
Company: TeamWork Management Permali
Posted on Jun. 08, 2006 08:34 AM in SAP Process Integration (PI), Standards nk
In order to process an EDIFACT message inside XI, we have to convert the incoming EDI stream to an XML
document.
Introduction
Until recently it was complex to handle industry formats such as EDIFACT within SAP XI.
SAP XI includes from SP15 an optional component called SAP Conversion Agent aimed at simplifying the
processing of EDIFACT messages. This weblog describes how to use SAP Conversion Agent for
EDIFACT/XML conversions.
For additional background information on SAP XI / SAP Conversion Agent integration you can also read the
weblog of Alexander Bundschuh : Integrate SAP Conversion Agent by Itemfield with SAP XI
We can check the generated output file and the event log:
How to Deploy a Content Master Project to the XI Server
Execute the Content Master Configuration Utility in order to set the CM repository:
We have to import into the XI repository the XSD provided with the EDIFACT library:
Once imported,the EDIFACT XML message structure is available as an external definition. It will be used as
a source document in the mapping.
Once the conversion agent service is deployed, we can call it from within any adapter that runs on the SAP
XI Adapter Framework by using the EJB module : localejbs/sap.com/com.sap.nw.cm.xi/CMTransformBean
In the module tab we have to configure the module name and set the parameter TransformationName to
the service that we deployed before.
This weblog was co-authored by Béla Suranyi and Lionel Biennier.
Béla Suranyi is a SAP Certified XI Consultant and works with TeamWork Management based in Geneva.
hi,
i have tried it and it has come successfully til importing my xsd from the conversion agent.
Now, when i import the xsd into my message mapping,i see that only one segment can be
imported. but your weblog shows that the entire structure can be brought into the message
mapping...?
what should i do?
• Good One
2006-07-24 06:08:25 Piyush Srivastava Business Card [Reply]
Thanks for the Blog, but as Ajay also said Seeburger Adapter is not at all replaced by this content manager
tool because of following reasons
1) seeburger Adapter(AS2) Provides a way of handling various delimeters needed for X12 and EDIFACT
data.
2) Seeburger Adapter is usefull in handling many verions of mapping with one entry in Seeburger Work
bench, example if tradepartner XYZ want to use 850 of various versions(4010,4030,4060) with one vendor
he can do that with AUTO mapping and the coresponding mapping will be picked up from the deployed
SDA automaticaly.
3) The only benefit that i see of this is that Seeburger Mapping Designer tool does not work directly on .edi
files so we have to get the equivalent xml files from Seeburger which is time consuming and structures
are not correct some times but the content manager tool works directly on .edi files which is good.
Regards
Piyush
This is very usefull blog. Only question i have is do we need to go for seeburger adapter for
converting EDIFACT message into IDoc.
Dear Ajay,
You have to analyze more accurately your requirements in order to be able to decide which is the best
option for you.
The output of the conversion agent can be mapped to IDOC using standard XI mapping functionality.
Best regards,
Bela
Bela
Hi Bela,
We have implemented Seeburger's EDI solution at a client, and our another client
wants to an EDI solution for them.
I cam across this weblog, and it is very interesting. I have some questions.
1. Does Converstion Agent support the converstion of all versions of native EDI
X12 and EDIFACT to the corresponding XML verions, and vice versa.
2. What are the differences between Seeburger's and XI Conversion Agent's EDI
soultions?
Your feedback would be greatly appreciated.
Thanks a lot.
Karma
Hi Karma,
We wanted to do the seeburger implementation for one of our client.We wanted to convert the EDIFACT to
XML struture using the seeburger adpater.
Do you have any helpful documents which helps us implementing the same.
Thanks in advance
Chirag Gohil
Hi,
We are going to implement EDI-2-SAP R3 intigration using Seeburger
Adapter. I have couple of doubts reg. this.
1)How to configure the Seeburger Adapter on the outbound side to intigrate with XI?
2)Is there any tool available to convert the native EDIFACT to EDI-XML format, other than Conversion
agent procedure?
would be very much thankful to you, if you would send me along with screen shots of any existing
scinerio.