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

Regarding Seeburger Implementation

Hi All,

We want to implement Seeburger Using SAP XI.

We have Installed SAP XI & Generic Seeburger has been Installed in XI & Configured.

We are using FTP VAN Protocol .


We want to Send the EDI ANSI X12 data to SAP R/3 IDOC ( Purchage Orders ).


Now iam able to see in IR-->>>>Seeburger Software Component>>>>>> Mapping>>>1 to 1 Mapping Between ANSI X12 & ORDERS Idoc.

Q1) Can We Use these Predefined Mappings Between EDI ANSI X12 & IDOC ?? If YES means How to Make Use of them ???

Q2) How to Get the XSD File Structure From EDI ANSI X12 to Import into IR as External Def , So that we can use it for Source Mapping.

Q3) Should we Install the BIC Maper Separately OR Will it comes with the Installation of the Seeburger ????? I Heard it is a Standalone Tool.

From Which Step Should I Start the Process to Fulfill the Whole Requirement ?????



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Nov 29, 2007 at 12:00 PM


    Q1: Of course, you can use it.. Do it exactly like woth other mapping objects.. You use message mapping in interface determination object. Of course, you must use appripriate source & target messages..

    Q2: Do you have the XSD? Then just import it as a file in this external definition.. Then use this external definition in your interface


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      1) I Asked How to Generate the XSD Structure From EDI ANSI X12 use it in IR.

      A) I think i have forwarded you the BIC pdf which has the step by step procedure for the same.

      2) What is the Role of BIC Mapper in this Particular Requirement ????

      A) BIC is the standalone application which is installed on PC.

      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

      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.



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.