on 08-04-2006 12:00 AM
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,
if you need a free converter for EDIFACT you can try my stuff:
Regards
Matthias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Karma,
SAP Conversion Agent by Itemfield is a data conversion system that enables you to create interfaces between any data formats and XML-based systems. The Conversion Agent can convert unstructured, semi-structured, and structured formats to XML, and the other way around.
Have a look at these links:
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
Seeburger EDI Adapter provides an EDI solution on internet via HTTP or AS2 to replace the expensive VAN. It provides some pre-built mappings for IDOC to ANSI X12(810,850,855,856 etc.,) and Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,) and has the ability to build your own. These pre-defined mappings transform the IDOC-XML to EDI-XML format.
These transformed EDI-XML messages are then converted to EDI specific format using the Seeburger's BIC(Business Integration Converter)adapter. In addition, Seeburger provides adapters like AS2,FTP(EDI specific) and so on to route these EDI messages to external EDI Partners.
For more i would suggest you to go through these links:
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.
The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:
1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)
2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.
3. create a one to one mapping between input en output.
4. export the metadata in xsd or sda format for import in XI.
5. generate an SDA which can be deployed in XI and used as a module.
Please go through the following links which clearly explains what you want and it also helps you in understanding the same in depth:
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
There are also a few ways to use EDI with the ALE system of R3.
inbound EDI to R3
-
1.use a 3rd party adapter for the EDI protocol(eg.SEEBURDER) from the EDI system,send the produced XML to the XI ,map the xml message to a matching IDoc using the IDoc adapter.
outbound ALE message from R3 to EDI system
-
1. Configure the ALE system to point to the XI the relevant IDoc (SM59,WE21,WE20...)
2.use a file adapter3rd party EDI adapter and map the fields to the target structure.
have a look at this example:
http://www.ean.se/EANCOM%202000/iftmin/example.htm
Details on how to configure can be found on SDN
I hope this helps....
Regards,
Abhy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Karma,
You could have a look at this too..
http://www.ids-scheer.com/us/rmail/mscheer/pdfs/SAP-Netweaver-Supports-Most-2-14-06.pdf
cheers,
Prashanth
P.S Please mark helpful answers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
One advantage of using Seeburger adapter would be that there is no seperate entity that you have to use as conversion agent would be one
1. One more installation
2. calling the same in the module of the adapter by which you are connecting to the conversion agent may be HTTP.
Please read here for more on seeburger:
https://websmp106.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002575392003E
XI use Case:
https://websmp106.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002175332003E
http://www.seeburger.com/sap-xi
Regards
Vijaya
Hi Karma,
You might take a look at this too to explore multiple options: www.aedaptive.com.
<a href="http://www.aedaptive.com">http://www.aedaptive.com</a>
You find details in the download area.
Best,
Gordon,.
Hi Karma,
Please see this
/people/lionel.biennier/blog/2006/07/21/sap-xi-supports-edi-x12
For ur second quesion... See the comments at the bottom of this blog...
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
cheers,
Prashanth
P.S Please mark helpful answers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
79 | |
9 | |
9 | |
7 | |
7 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.