EDI to IDOC

[Former Member]

Hi All,

I have One Requirment with me.

My Clients Customer is sending the data in EDI ANSIX12 Format , So that EDI ANSIX12 Format data should be Posted into Sap R/3 Using IDOC.

<u><b>Questions:</b></u>

Q1) How & Who will the Conversion From EDI ANSIX12 Format to XML , So that XI Can do the Processing ????

Q2)If My Clients Customer is proving the XSD File Directly means, Will it become a Normal File -XIIDOC Scenario ????? Or Do we need to do Any thing in the Module TAB of the File Adapter ??

Regards

Suman

[Former Member]

THis guide will tell you everything:)

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e...

Thanks

Farooq.

*Rewards Points if you find it useful*

[prabhu_s2]

the xml conversion happens and is taken care by xi itself. it is just required from us to define the mapping like u defining the mapping instrution in a typical edi scenario.

[Former Member]

<i>> Q1) How & Who will the Conversion From EDI ANSIX12

> Format to XML , So that XI Can do the Processing

> ????</i>

See the ANSI XI12 is standard EDI message.you can send this message to XI using third party adapter called Seeburger...this adapter will convert this EDI standard message to XML format that can be processed in Integration Server.

<i>> Q2)If My Clients Customer is proving the XSD File

> Directly means, Will it become a Normal File

> -XIIDOC Scenario ????? Or Do we need to do Any

> thing in the Module TAB of the File Adapter ??</i>

If you have XSD meand you dont have to create the DT and Message Type for the incoming message. else you have to create in manually..based on the input message.

So here the only game is of Adapter rest is same as any scenario...u can say as File to File:-)

Thanks

Farooq.

*Rewards Points if you find it useful*

[Former Member]

Hi,

Okay, Then Who will convert this EDI ANSIX12 Format to XML Using this Seburger Adapter. ???? What are all the chances for this ???

As a Developer Should we Do this Conversion OR Our Clients Customer will doit & Place the XSD File in the FTP Server ????

Regards

Suman

[prabhu_s2]

for holding the data at runtime u need a container for source and target. this can be done by either creating it mannauly or if u have a xsd u can import it and use it in IR. For the actual processing the original file neds to be placed in the ftp server and normally it is a part of the business process and is made aviable not by the developers (in the case of sender)

[Former Member]

Hi,

What is my Doubt is How to convert this EDI ANSIX12 Format to XML Using this Seburger Adapter.

Here the Requirement is My Clients Customer is Using EDI & My Client is Using SAP r/3.So they will send the Data in the Form of EDI ANSIX12 & the Data will be Stored in R/3 Using IDOC.

Then tel me the Process for this.

Regards

Suman

[Former Member]

Hi,

Seeberger Adapeter also provide the metadata for standard EDI messages. So like other adapter you have to create a communication channel..and have to select the adapter (provided by seeburger....and it has to imported in XI also).

if EDI standard message is coming then only adapter can on convert it to EDI-XML.

Thanks

Farooq.

[Former Member]

Hi,

UR Client Customer will send the data in EDI format only and ur receiver is SAP ECC in between u will have XI..........so first of all u have to install the Third party software that is seeburger into XI server.

Seeburger is a tool in which there is predefined Mappings will be there so no need to do in mapping u have to use the standdard mappings in the XI.

While call the adapter that is sender and in sender u will use File adapter and in that u will have Module TAB in that u have to give the standard mapping which ur using....so while executing the adapter will first call the mapping and then the file adapter will excute.so dont worry about mapping every thing will be done predifined.............98% we use standard mapping which are difined in seeburger.........only 2% chance we have to do cutom mapping............

Check Some links on Seeburger.

SEEBURGER

http://www.seeburger.com

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-8f2...

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

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_Integratio...

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_Integratio...

Regards,

Phani

Reward points if Helpful

[Former Member]

Hi,

Q1) You mean We can Able to see the Seburger Adaper in the Adapters List in the Communication channel of the ID ???? Then We can Do it ???

Q2) Should we have the EDI Seburger Adapter in the Both My Client Side & Clients Customer Side Also ???

Regards

Suman

[Former Member]

Hi,

Its not an ADAPTER its an Third party tool which is used to convert the EDI standard format into XML..........XI cant understand the EDI format so they use Seeburger tool to conver the EDI format.

So u cant see it in ID ok........u ahve to install the tool into XI server so that u can use tha mappings defined in seeburger.

So when ur using the adapter in that u have to give the mapping name so that while executing first it will check for mapping and then it will excute the adapter.

Regards,

Phani

[Former Member]

Hi,

Q1)So here we need to Use the File Adapter Only ...Is It ?????

Q2) If we use File Adapter means there in Module TAB We need to specify the Pre defined Mapping. So Can you tel me what i need to give there Exactly ??

Regards

Suman

[Former Member]

In my first reply I already said it is Third Party Adapter...meaning it does not come with SAP XI installed adapter..so this adapter has to installed in J2EE engine...then and only then you are able to see it in the list of communication channel.

Also as you mentioned your requirement is EDI to Idoc..so only in XI you have to think...thre will be no change in source and target system...

Thanks

Farooq.

[Former Member]

Sorry but at this moment I like to suggest you to just once again go through the XI architevture..and Adapter Engine..it will clear your lot of doughts..then you can easliy get an idea how you can achive EDI to Idoc.

Thanks

Farooq.

[Former Member]

Hi,

In the Adapter u have to specify the mapping that is standard mapping name,that will be given to u by seeburger guys,were u will bought the tool.

u can check the links with i have given to u,

Regards,

phani

[Former Member]

HI Suman,

Please have a look at the thread which will help you in understanding the scenario.

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.

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.

Do let me know if you need further help.

Thanks and Regards,

Chirag Gohil