Solved: Conversion From EDI Format to XML Using Seburger

Hi,

We have a Seburger and the XI Setup, please let us now the steps to be performed for converting the EDI format(ANSI X12 850) to XML and further to send out as an IDOC from the XI server.

plz chk the Process flow mentioned below and let me know if i m wrong:

xml msg posted

to XI via FTP

adapter IDOC adapter

EDI MSG~~> Seeburger~~

>XI--

>SAP R/3

Please Send Any Doc's Regarding these Steps

Regards,

Giri

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hi Seshagiri,

Refer the below thread , you can find the useful links abt Seeburger adapter.

Cheers

Veera

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

Brief About FTP/VAP 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.

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.

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.

Thanks and Regards,

Chirag Gohil

Hi Chirag,

Okay, I Understood the Overview Process Which you Given, But I Want the Steps How to Convert the EDI Format To XML.( Steps to do in Seburger to Convert into XML )

Please Provide the Step-By-Step Solution Or Any Guide How to Do this Conversion.

Regards

Giri