EDIFACT TODESADV(IDOC)

Hi,
I want to perform EDIFACT to IDOC scenario.Please advise me step by step document. I tried to perform..But I m confused.Firstly i imported EDIFACT_96A.xsd to external definition and used as source.As target i used idoc.And I mapped tit each other In ID i defined Communication channel for sender EDIFACT adapter and IDOC for receiver.But it is not work.The Error :
Unable to interpret IDoc interface SI_Edifact_To_Idoc_Receive
Also i dont know that it is true way.In some documents there are different format ant it have to convert xml format.How to follow way for this? In my procet i used XML schema definition.But for EDI format how to convert XML in PI?
exemplarily:
UNBUNOA:2111222333:1222333444:1060705:154512345'UNH1ORDERS:D:01B:UN:EAN010'BGM220::91009239'DTM137:20060705:102'DTM2:20060705:102'NADBY5400152201228::9'NADSU5410256000099::9'NADDP5400152201228::9'CUX2:EUR:9'LIN1+5410256410013:SRV'PIA1388:SA::91'QTY21:10'PRIAAA:15.99::LIU'UNSS'UNT141'UNZ112345'
how to convert XML in PI?
Thanks in Advance
Nurhan

Hi nurhan,
Here you go:
Open PI Conversion
Module for EDIFACT
Configuration Guide
http://www.mirrorservice.org/sites/dl.sourceforge.net/pub/sourceforge/o/project/op/opi2/Documentation%20(all%20releases)/EDIX%20Conversion%20Module%20for%20PI%207.1/opi2_EDIX_Module_PI71_Configuration_Guide_v12.pdf
http://www.mirrorservice.org/sites/dl.sourceforge.net/pub/sourceforge/o/project/op/opi2/Documentation%20(all%20releases)/Conversion%20Module%20for%20PI%207.0%20(3.0)/opi2_EDIFACT_ConversionModule_Configuration_Guide_v11.pdf

Similar Messages

EDIFACT to Idoc

Hi All,
Iam working on EDIFACT to Idoc scenario.I have installed conversion agent, i need a sampe edi file(pref ORDERS) to test the scenario.
can you tell me where to find it.
Thanks in advance.
Disney.

Hi,
I don't have test file. But this blog may help on this-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
If you search some of the exercises are here...
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/fc39c16bfb025ee10000000a1553f7/content.htm
Regards,
Moorthy

Mapping EDIFACT to IDoc: IFTMIN to DELVRY / SHPMNT

Hi,
because we haven't done this before we want to ask if there is someone whos has done this before us.
So our business case is that we have to map IFTMIN to any appropriate SAP-Format.
We found that SHPMNT might be the best solution but as we checked the structure we saw that this IDoc contains so much overhead information that we thought we might map it to DELVRY - whereas this is included in SPHMNT.
So has someone of you done this before and can give us a hand on how to map this? maybe there is a mapping template to offer?
I know this sounds silly - but maybe someone might help.
We are also open to any other suggestions on how to map IFTMIN - perhaps to a BAPI?!
br

Hi Fritz,
This blog gives you the realtion between most EDIFACt messages and sap idocs:
/people/community.user/blog/2009/10/12/mapping-idocs-to-x12-transactions-and-edifact-messages
It says SHPMNT04 is the IDOC for Inbound Interfaces and DESADV.DELVRY03 for Outbound Idocs.
Can you check how much of the overhead information is actually "mandatory" on the sap side?
You can probably leave the information that you wont need.
You can find the detailed documentation (filed level) in WE60 transaction of sap.
Regards,
Ravi Kanth Talagana

B2B in PI 7.0 - EDIFACT format to IDOC and vice versa

We need to establish B2B scenario in PI 7.0
IDOC to EDIFACT and EDIFACT to IDOC.
Please let me know the solution without using any third party adapter like seeburger.
Any example scenario of the same case will be helpful

Hi ,
If you are decided to not using SeeBurger then its difficult to implement B2B Scenario
Your requirement IDOC 2 EDIFACT or Vice VERSA, you have to do more analyzation about EDIFACT.
You can acheive using Adapter module, you have to about EJB's stuff to write Adapter module to support EDIFACT Message, Search for info about Adapter Module in SDN you wil find some lot off stuff about Adapter MODULE.
then coming to mapping its really challenging to do Mapping between IDOC TO EDIFACT.
You have to alalyze the EDIFACT Structure .
I implemented B2B scebario in my project SeeBurger.
Regards,
Raj

IDOC acknowledgement in XI

Hello All,
I am working on Asynchronous scenario (EDIFACT to IDOC). Please, explain me step-by-step procedure to receive an acknowledgement to XI.
Regards,
Amit..

Hi,
Check this links
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Regards
Ramesh

EDI-SEEberger-XI-IDOc-R/3

Hi
i am a starter in using EDis and Seeburger
could please provide me with the relavant webblogs
of how to implement the scenario of EDI-SAp r/3 using seeburger and idoc adapters

For the same requirement you need to follow the below steps:
1) First deploye the Std seeburger mapping provided by see burger on XI
2) If you are using the AS2 adapter then you have to install the AS2 server on XI server.
3) Once you install the std seeburger on SAP XI server you will see the AS2,X400,OFTPS,VAN adapter on XI ID.
5) You need to call the std mapping in the adapter module which does the conversion from EDI to XML and XML to EDI.
If you wanted to know more about seebuger and the configuration then refer the below breif into about seeburger and the reply to many of my threads.
Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
Refer this forum which is replied by me which talka about the configuration which need to be done for AS2 adapter. This is very helpful:
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Re: Seeburger AS2 adapter...
Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
AS2 adpater-- Configuration details for both SND and RCV.
AS2 Sender Adapter -- Need few details.
Seeburger info:
Re: seeburger adapter
Re: SEEBURGER's VAN Adapter
AS2 info:
Re: Regarding Seeburger AS2 Adapter
SEEBURGER EDI adapter
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/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
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
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
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
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
Thnx
Chirag
Reward points if it helps.

EDI - XI - IDOC

Hello XI Experts,
I know that there were lot of blogs about edi scenarios in XI but I'm still a bit confused and I appreciate any help.
I need to configure scenario where we receive EDI message VDA 4905 format through ISDN using OFTP protocol.
As I understand it correctly there is no standard functionality in XI to perform this configuration so I have to use third party products, am I right?
What will I need?
1. Technical adapter like SEEBURGER? (but what about conversion then?)
2. Conversion agent? (but what about communication via OFTP then? another third party adapter?)
3. Business adapter for automotive industry from SEEBURGER? (with conversion but how it is with data types, does SEEBURGER provide library of standards in form of XSD? Does anyone has any experience using this adapter? And if specification change how it is with upgrading?)
Does exist any documentation about SEEBURGER adapters? What it can do and so on? And where can I find information about licence fees? Should I contact SEEBURGER directly or is there any direct link? Because I coudln't find any.
My last question is about OFTP and security, is the data using OFTP encrypted or not?
This is my first EDI scenario so maybe I've missed some critical issue to configure this or I've something misunderstood so if you'll give me some hints I'll very appreciate it and will give you reward points.
Regards,
Pavol

Hi,
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
Here is the link for your reference:
/people/ricardoandres.maienza/blog/2007/04/06/edifact-to-xml--stylus-studio-solution
http://www.stylusstudio.com/edi/EDIFACT_translate.html
The steps to convert EDI to XML / XSD can be found at the following link:
http://www.stylusstudio.com/edifact_to_xml.html
Stylus studio download link: http://www.stylusstudio.com/xml_download.html
Using the Conversion agent
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/18/conversion-agent-a-free-lunch
/people/alexander.bundschuh/blog/2006/03/14/integrate-sap-conversion-agent-by-itemfield-with-sap-xi
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
Thanks and Regards,
Chirag Gohil

Ansi X12, equivalent IDOCs list....

Hi all,
Any body please provide me the information about IDOCs list equivalent to EDI ANSI X12,EDIFACT formats.
Ex:
Transaction Set/Document -
>Purchase Order
                          ANSI X12------->850
EDIFACT* ------->ORDERS
                                 IDOC -
>ORDERS
   Any links or Tcodes where i can get the information will be very helpful
Thanks,
Ram.

Hi Kopparaju,
You can get teh complete list here:
http://www.linkedin.com/news?viewArticle=&articleID=55241305&gid=41612&articleURL=http%3A%2F%2Fit%2Etoolbox%2Ecom%2Fblogs%2Fehadzipetros%2Fsap-edi-mapping-an-idoc-for-every-interface-33013&urlhash=3x2A&trk=news_discuss
Thanks a lot for the EDI guru Emmanuel.
Regards,
---Satish

How to deal with digital signatures when converting messages?

Hi there,
this it not (yet) about the actual implementation. It's more of a logical problem that I'm facing.
There are two partners A and B. A is sending an EDIFACT document which is digitally signed to B.
B has a XI instance that is converting all incoming messages into IDocs, in this particular case INVOIC. This IDoc is received by the R/3 system.
All invoices must be archived due to an eventual tax inspection.
In order to fulfill the security requirements all archived data must be digitally signed.
So far so good.
I guess I'm not allowed to sign my invoices with my own private key due to the fact that i could alter the containing data and sign it again.
It's obvious that I cant apply the digital signature from the EDIFACT message to my IDoc because the data has changed and therefore the signature is invalid.
The only solution to this problem, that I can imagine, is to archive EDIFACT alongside IDoc.
Have you experienced a similar problem or do you have any other idea in order to solve this issue?
I hope my problem is well defined.
Any comment is appreciated.
Thanks in advance
Bastian Stratmann

Hi Bastian,
it is not possible to separate the signature from the document signed.
The system A generates and EDIFACT message -> A has the responsibility on this message and so A sign it.
XI manipulate the message received from A, that means XI generates a new message. -> XI has the responsibility on it, so if you want a signature this should be generated by XI.
As the IDoc was generated by XI it cannot be signed by A (neither technically nor logically) because A has no responsibility on it.
XI <b>is</b> altering the message so XI is responsible for it.
In this case you have to store both the EDIFACT message and the IDOC and maybe sign this new document (EDIFACT+IDOC) with XI signature .
Kind Regards,
Sergio

Seeburger AS2 Adapter

Hi,
I need few information how to implement seeburger adapter(Using AS2 or FTP) with XI. I have a requirement to convert the EDI Ansi X12 messages from a EDI system and post it into a R/3 system using XI.
The client system(EDI system) is in US has VAN and we have the R/3 in India. So do we need to establish a VAN connectivity or it can directly access the client VAN to take the EDI messages.
Do clarify whether to go for AS2 or FTP, and what are the advantages of each.
I went thro few documents from Seeburger which comes up with the package of Generic FTP adapters or we have a Standalone AS/2, or BIS:HUB and spoke.
Regards,
Nithiyanandam

HI,
Brief about the FTP/VAN adapter:
The SEEBURGER FTP/VAN Adapter is responsible for transmitting files according to the File Transfer Protocol, with the particular support of various VANs. This protocol was installed as a user gateway protocol by several of the largest VAN providers, such as IBM, GE and Sterling IIB and Sterling Commerce.
The FTP/VAN adapter must be configured in the configuration part of the Integration Builder. The adapter is based on the Adapter Framework and is executed by the SAP J2EE Adapter Engine as shown in the diagram below.
The FTP/VAN Adapter supports the following protocols:
IBMIE VAN, all report options.
GEIS (GeMarkIII) and GeMark3000, all report options, report file is only extracted, if needed.
EXITE (ECODEX), EDIFACT file processing, DISPATCHED reports.
Sterling Commerce and Sterling IIB.
MCI EDI*Net.
The following FTP options are supported:
SSL, both IMPLICIT and AUTH_TLS support, server authentication.
All popular FTP proxy types like: USERWL, USERWOL, SITEWL, OPENWOL.
Active and Passive connection modes.
"KeepAlive" feature.
Binary, ASCII and custom transfer types.
Refer the below thresd which taks about the AS2 adapter configuration inroder to convert the EDI to XML message the similar configuration needs to be done in case of VAN/FTP adapter.
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Seeburger adapters like FTP,OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
Seeburger provides the std mapping program which has to be deploy on to XI and we need to give it to module tab in adapter which does the conversion.
Here are the some of the std mapping program which is provided by seeburger.
See_E2X_INVOIC_UN_D96A
See_E2X_INVOIC_UN_D99A
See_E2X_ORDERS_UN_D96A
See_E2X_OSTRPT_EAN_D96A.
We need to take the license from seeburger and we need to deploye the seeburger adapters then only we can see in adapter list on XI.
Thanks and Regards,
Chirag Gohil

Seeburger Adapter

Hi all,
I have installed a generic seeburger FTP adapter, but I dont have any VAN connectivity at present. Can I convert the EDI ANSI X12 format to xml with this installation or it requires VAN connectivity to do this.
In this case do we require the BIC mapper? if so how to work with BIC mapper?
In the communication channel, I am able to see the installed Seeburger FTP adapter but it does not show the transport and message protocol. Is this related to the Installation/setup of VAN connection.
Regards,
Nithiyanandam

Hello..
SeeBurger is a leading provider of global business integration solutions.
Market launch of the most successful EDI solution for the automotive industry in 1986.
the company today serves more than 7,000 customers in 42 countries and more than 15 industries through its flagship B2B Gateway and related products and services.
First company worldwide to receive certification for SAP R/3
Building a closer partnership with SAP.
Extended any-to-any-conversion.
The SEEBURGER Business Integration Converter (BIC) is an Any-To-Any Format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex,high performance XML-to-XML mappings or to interface to existing JDBC Data Sources.
Supported EDI formats include: ANSI, EDIFACT, INHOUSE, IDOC, XML Schema, XML DTD, CSV,Delimited Data, positional data, SWIFT, EANCOM and many more.
Mapping Designer, a graphical tool, easily defines data format conversions via drag and drop functionality, enabling easy integration between source and destination files. A central mapping reposiu00ADtory enables comprehensive support of versioning and deployment support, such as self-testing and auditing.
The SAP Exchange Infrastructure message format is based on XML, but it also can work with non-XML data using attachments. In some cases it may be necessary to convert the main XML document in a message, into a non-XML document. The use of BIC is very common in Business-to-Business scenarios where EDI standards are in use.
The Business Integration Converter (BIC) of Seeburger is based on Java JIT Technology and can be used for small real-time messages, as well as very large master data (i.e.Catalogs) batches.
BIC can convert outbound invoices from XML format (used in SAP XI) to an EDIFACT invoice. The conversion can be executed before the message is transmitted to the business partner. The other way around, once an EDIFACT message has been received from the business partner, it must first be converted to XML format, which is the format SAP XI supports.
The most direct way of using the Seeburger adapters is to configure the BIC as a module. BIC will allow you to do the following
Once you install BIC, you need to do Import the Generator Mappings into the Project Explorer of BIC MappingDesigner.
You can find Generator Mappings as a ZIP file in the following location <BICMappingDesignerInstallationDirectory>\user\bicmd\Exchange and select the file prj_GeneratorMappings.zip.bicmd.
In MappingDesigner select File Import Generator Mappings Zip File prj_GeneratorMappings.zip.bicmd Clik on Add and OK.
Once Import is done you can see Generator Mappings in BIC Mapping Designer.
The SEEBURGER Adapter runs on the SAP WEB AS (J2EE Engine)
The SEEBURGER Adapter is integrated into the SAP Exchange Infrastructure over JCA (Java Connector Architecture)
Consequence :
Supply of the complete SEEBURGER EDI/B-to-B-Technology-Suite within SAP NetWeaver
Central File of Business Content (mappings, integration processes) in the Integration Repository of SAP XI
Central configuration and design by using the Tools of XI in the configuration
Central monitoring and alerting over SAP XI
Seeburger Solutions Overview
BIC Mapping Module
Functional Acknowledgement Solution
Operational Dashboard / Archiving
Invoice Solutions
Communication
The Business Integration Converter (BIC) from SEEBURGER is a converter for the implementation of data formats.
Following formats are available:
ANSI X.12 (American National Standards Institute)
CSV (Comma Separated Variable formats)
EDIFACT (all subsets)
INHOUSE (VDA, flatfiles, e. g. SAP IDoc)
SWIFT (banks)
TRADACOM (Trading Data Communications Standard)
XML (DTDs and SCHEMATA)
Able to classify messages into the following message types:
XML
EDIFACT
Ansi X 12
Tradacom
VDA
IDOC
Swift
Inhouse
XML Ansi X 12
XML EDIFACT
XML Tradacom
XML VDA
XML IDOC
Go through this links..
Some more..
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Reward Points if it is really useful to you.....
Thanks,
Satya Kumar..

Seeburger AS2 Adapter scenario ?

Hi Frnds,
I want See Burger ,AS2 Adapter end to end scenario with screen shots, If anybody know link or having end to end scenario pls share to me its too urgent.
Regards,
Ravi kumar

Hi ,
Ravi, I am also looking for seeburger scenario, i got information from forum, i providing info, i hope it will give some idea... if its not excuse me....
The SEEBURGER FTP/VAN Adapter is responsible for transmitting files according to the File Transfer Protocol, with the particular support of various VANs. This protocol was installed as a user gateway protocol by several of the largest VAN providers, such as IBM, GE and Sterling IIB and Sterling Commerce.
The FTP/VAN adapter must be configured in the configuration part of the Integration Builder. The adapter is based on the Adapter Framework and is executed by the SAP J2EE Adapter Engine.
The FTP/VAN Adapter supports the following protocols:
IBMIE VAN, all report options.
GEIS (GeMarkIII) and GeMark3000, all report options, report file is only extracted, if needed.
EXITE (ECODEX), EDIFACT file processing, DISPATCHED reports.
Sterling Commerce and Sterling IIB.
MCI EDI*Net.
The following FTP options are supported:
SSL, both IMPLICIT and AUTH_TLS support, server authentication.
All popular FTP proxy types like: USERWL, USERWOL, SITEWL, OPENWOL.
Active and Passive connection modes.
"KeepAlive" feature.
Binary, ASCII and custom transfer types.
Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
AS2 vs OFTPS:
AS2 & OFTPS
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
Please see the below blogs
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/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
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
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
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
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
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration
https://www.sdn.sap.com/irj/sdn/forums
/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
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
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
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
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
EDI Adapter by SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
Regards,
Raj

3rd party adapter integration into XI

Dear Experts
I wanted to know how 3rd party adapters are integrated into XI?

Hi Dheer,
There many third party adapters available in market.
One example is seeburger:
U need to follow the below steps for integration into XI:
For the same requirement you need to follow the below steps:
1) First deploye the Std seeburger mapping provided by see burger on XI
2) If you are using the AS2 adapter then you have to install the AS2 server on XI server.
3) Once you install the std seeburger on SAP XI server you will see the AS2,X400,OFTPS,VAN adapter on XI ID.
5) You need to call the std mapping in the adapter module which does the conversion from EDI to XML and XML to EDI.
if u need process then let me know I will send u the configuration threads which is required for integration.
EDI Adapter by SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
Brief about seeburger:
Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
refer belwo weblog:
/people/nithiyanandam.au2/blog/2008/02/20/handling-edi-interfaces-using-seeburger-bic-modules
Thnx
Chirag
Edited by: Chirag Gohil on Feb 25, 2008 12:51 PM

Seeburger Adapter Scenario

Hi Frnds,
I want See Burger ,CIDX Adapter end to end scenario with screen shots, If anybody know link or having end to end scenario pls share to me its too urgent.
Regards,
Raj

Hi Rajshekar,
The SEEBURGER FTP/VAN Adapter is responsible for transmitting files according to the File Transfer Protocol, with the particular support of various VANs. This protocol was installed as a user gateway protocol by several of the largest VAN providers, such as IBM, GE and Sterling IIB and Sterling Commerce.
The FTP/VAN adapter must be configured in the configuration part of the Integration Builder. The adapter is based on the Adapter Framework and is executed by the SAP J2EE Adapter Engine.
The FTP/VAN Adapter supports the following protocols:
IBMIE VAN, all report options.
GEIS (GeMarkIII) and GeMark3000, all report options, report file is only extracted, if needed.
EXITE (ECODEX), EDIFACT file processing, DISPATCHED reports.
Sterling Commerce and Sterling IIB.
MCI EDI*Net.
The following FTP options are supported:
SSL, both IMPLICIT and AUTH_TLS support, server authentication.
All popular FTP proxy types like: USERWL, USERWOL, SITEWL, OPENWOL.
Active and Passive connection modes.
"KeepAlive" feature.
Binary, ASCII and custom transfer types.
Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
AS2 vs OFTPS:
AS2 & OFTPS
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
Please see the below blogs
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/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
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
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
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
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
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration
https://www.sdn.sap.com/irj/sdn/forums
/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
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
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
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
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
EDI Adapter by SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
Regards,
Vinod.

SEEBURGER adapter - How much does it help?

We have a PI box just installed and we'll be implementing a few EDI transactions with some business partners.
I was told that SEEBURGER is the preferred EDI adapter for EDI transmissions from PI (XI).
1 - How much does SEEBURGER help the development of PI EDI interfaces? Is there a way to estimate on how much work is saved using it instead of relying on standard? (lets say 10, 20 or 30%)?
2 - I am considering here 2 options (Use SEEBURGER or not). Is there a better alternative?
Thanks
Leonardo

Hi,
For EDI implementation there are ways by which u can implement with XI
1) Using third party seeburger adapter.
2) Conversion agent
3) Writing module.
Preferred one is seeburger.
1) It has std XSD available which we just need to import into External definition
2) It has std mappings for all the message type which converts EDI to XML and XML to EDI format.
3) Provides different adaters
4) BIC tool
5) Many adapter modules.
Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
It provides std mapping program which does the conversion of EDI to XML and XML to EDI which need to used in XI comm channel module tab.
Thnx
Chirag

EDIFACT TODESADV(IDOC)

Similar Messages

Maybe you are looking for