Seeburger Adapter

[Former Member]

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

[Former Member]

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 (DTD‘s 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_Integratio...

Reward Points if it is really useful to you.....

Thanks,

Satya Kumar..

[Former Member]

Hello Nithiyanandam...

BIC Mapping Designer :

Steps :-

1) Right click on Data type and Export structure (msg_....xml).

2) Run “CreateXMLmessage”, (source file msg_....xml, target file XML_....xml).

3) Import XML….xml to your Project XML Message.

4) Run “CreateMappingXMLToEdi” source file (msg_...xml),target file (X2E_....xml) if you are converting XML to Edi format.

5) Run “CreateMappingEdiToXML” source file (msg_....xml),target file (E2X_....xml) if you are converting Edi to XML format.

6) Import X2E/E2X_.....xml to your project mappings.

Reward Points if it is useful...

Satya Kumar...

Thanks

[Former Member]

Hi,

Refer to this thread

Rgds,

Kumar

[Former Member]

HI,

If you do not have the VAN connectivity right now then what you can do is you can use the File adapter and place the EDIFACT file in the file directory or place the file at application server and use the BIC mapping program for converting the EDI to XML in the file adapter modult parameter.

This will help you only for testing purpose in order to check your scenario is working properly or not till you dont have the VAN connectivity parameters.

Just go through the below thread for the midult configuration and which talks about the mapping program name to be used.

Module parameters to be used for conversion this is explained with the AS2 adapter but you can use the same in the file adapter module parameter.

Under the party identifiere tab

Agency will be seeburger

Scheme=AS2ID

Name = WAN network no of the partner who is sending the file

Few changes in the module parameter tab.

localejbs/CallBicXIRaBean bic

CallSapAdapter 0

Module configuration:

bic= destSourceMsg = MainDocument

bic= destTargetMsg = MainDocument

bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A

Thnx

Chirag Gohil

[Former Member]

Hi Chirag,

Thanks for your reply.

we have few doubts like, how to we go abt the design part..

Can we use the xsd that is available for the ANSI X12 850 format from the installed seeburger or i should provide this as a file structure in Datatype and create MT, MI, MM and IM.

And in the configuration I will be creating 2 comm. channel in which the sender comm. channel for the EDI structure will be added with the module and the module parameters.

Please confirm.

Also share any documents for the design structure in XI.

Regards,

Nithiyanandam

[Former Member]

HI,

You do not need to create an Data type for any of the std seeburger EDIFACT structure it is available in BIC mapping tool.

What you need to do is you need to generate a XSD using BIC tool and import that XSD in XI and use that structure as a data type.Other design will remains the same.

As I said in my thread you just use the File adapter and use the Module program in the module parameter tab for conversion.

You need to deploy the mapping which does the conversion on XI and then only you can use the mapping name in module parameter tab.

I once again insist you to Refer my all reply in the thread this will help you a lot.

Feel free to ask me if you have any other doubts

Thnx

Chirag Gohil

[Former Member]

Hi Chirag,

We have the Seeburger BIC adapter installed with XI, is that enough to have the BIC mapping to be done or do we need to have the BIC map designer tool to perform the mapping. In that case we dont have the BIC mapping tool, so what could be the posible solution to perform the mapping between the ANSI X12 and Idoc scenario.

<b>Since we have already installed the SEEBURGER_GENERIC_EDI adapter, we could see the default structures of ANSI X12 850, 810 etc under external definition. So can we go ahead with this xsd structure for mapping.</b> In that case what will be the use of BIC mapper tool which converts the EDI(ANSI X12 structure to xml structure).

Regards,

Nithiyanandam

[Former Member]

HI,

To give brief overview about BIC:

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

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.

1) We have the Seeburger BIC adapter installed with XI, is that enough to have the BIC mapping to be done or do we need to have the BIC map designer tool to perform the mapping. In that case we dont have the BIC mapping tool, so what could be the posible solution to perform the mapping between the ANSI X12 and Idoc scenario.

A) 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

This tool will give you the XSD strucutre,mapping program which does the conversion etc..You do not need BIC if you know the mapping program name and you have a XSD with you.

2) Since we have already installed the SEEBURGER_GENERIC_EDI adapter, we could see the default structures of ANSI X12 850, 810 etc under external definition. So can we go ahead with this xsd structure for mapping. In that case what will be the use of BIC mapper tool which converts the EDI(ANSI X12 structure to xml structure).

A) if this is the XSD which is required for your scenario then please go ahead with that, you do not need to genetate the XSD using BIC but you need to know the std mapping name which does the conversion of E2X and X2E for your scenario which need to be deployed on XI but if it is deployed then you do not need BIC tool. Requirement for fulfilling this scenario:

Mapping name must be known and the mapping program should be deployed on XI.

Thnx

Chirag

[Former Member]

Hi,

BIC will be used only when you want to create your own mapping programme to convert any file format into xml or xml to anyfile format.

But in your case you want to use the standard mapping and you have the xsd avialable.then forget abt the BIC and do as the normal scenario how you will do for file to idoc .

(For the customised mappings the names will start with See_E2X_ORDRSP_UN_D96A -- if you want to convert to file to xml or

See_X2E_ORDRSP_UN_D96A -- if you want to convert the xml into file)

Add finally add the Module parameters given by chirag .

-Seema.