how to configure Seeburger adapter

[Former Member]

Hi All,

Can you pls guide me on how to configure adapter? and also why do we need mercerator and converstion agent tools along with see burger adapter?

Can't find any doc on how to configure seeburger adapter!!!

Can someone pls put light on the messageflow when seeburger and these converstion agents are used?

Regards,

Ashish

[Former Member]

hi Ashish,

Did you find about adapter parameters that need to be filled in SEEBURGER adapter in communication channel configuration?

Actually that is what you asked in your thread.

I'm searching Seeburger BIS AS2 Adapter parameters. Please let me know if you know about it.

my maild id: ajay_tlk@yahoo.com

Thank you.

[Former Member]

Hi Ashish,

It is similar like other adapters once it is supplied. But take care about security/firewalls settings.

and also why do we need mercerator and converstion agent tools along with see burger adapter?

>>>Not a mandatory to use along with seeburger.

Can someone pls put light on the messageflow when seeburger and these converstion agents are used?Can't find any doc on how to configure seeburger adapter!!!

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

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

Thanks

Sreeram

[Former Member]

Thanks Sreeram,

But can you pls clear some basic doubts:

Why do we need:

<b>1) IDOC to ANSI X12(810,850,855,856 etc.,)

2) Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,)

3) IDOC-XML to EDI-XML format

4) BIC

5) bicmapper

SDA</b>

Regards,

Ashish

[Former Member]

Ashish,

As you read in earlier reply that we use seeburger adapter mostly when we have EDI or other formats which are not easy to ready through stnd Xi adapters.

EDI is nothing but ANSXI and EDIFACT.

when u need to send data to our business partners their is stnd which is followed that EDI.

Why do we need:

1) IDOC to ANSI X12(810,850,855,856 etc.,)

So when u send IDOC to partners if ur partners agrees using ASXI then we use IDCO to ANSX12.

2) Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,)

same as above but EDIFACT is used by european countries as their EDI

3) IDOC-XML to EDI-XML format

same as above.

4) BIC

which contains the bicmapper

5) bicmapper

this where u map ur source to target structure

SDA

when import into XI you import as SDA like Jar or war files.

Thanks

Sreeram.G.Reddy

[Former Member]

Thanks Sreeram,

But what are the adapter parametrs that need to be filled in SEEBURGER adapter in communication chammel step?

Also what are the securities issues that need to be taken care off?

what are 856,855 etc.

also do we have different seeburger adapter for each ANSXI and EDIFACT?

also does the receiver company will provide us their edi structure?

Thanks,

Ashish

[Former Member]

Hey

>>what are 856,855

have a look at the following http://en.wikipedia.org/wiki/Electronic_Data_Interchange

>>also does the receiver company will provide us their edi structure?

you get the xsd for EDI which you have to import in IR and use as data type

thanx

ahmad

[justin_santhanam]

Ashish,

Please see the below thread.

Best regards,

raj.