Solved: Seeburger Adapter Scenario

rajasekhar_reddy14 · ‎05-20-2008

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

Former Member · ‎05-20-2008

Hi,

for CIDX adapter step by step guidelines you can visit www.saptechnical.com...on the main page itself you can find 2 parts............

for seeburger........

reward points if its helpful

Thanks,

Madhu

former_member537867 · ‎05-20-2008

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:

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