Skip to Content
author's profile photo Former Member
Former Member

Seeburger Adapter

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.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 02:14 PM


    Refer to this thread

    SEEBURGER EDI adapter



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      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 .


  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 11:08 AM

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


    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 11:23 AM


    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

    In MappingDesigner select File Import Generator Mappings Zip File 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


    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:



    Ansi X 12






    XML Ansi X 12


    XML Tradacom



    Go through this links..

    Some more..

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


    Satya Kumar..

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.