Business Integration Converter Mapping Designer: a Step By Step Approach

Applies to:
SAP NetWeaver PI 7.0, Seeburger BIC Mapping Designer Tool, Version 6.2.2. For more information, visit the Data Management and Integration homepage.

Summary
This document is useful to guide the user to develop the E2X (EDI to XML) and X2E (XML to EDI) mappings that are used as deployable units in PI 3.0 and above. Author: Harikrishna Adepu

Company: Intelligroup Asia Pvt ltd Created on: 10 November 2008

Author Bio
Harikrishna Adepu is working as a SAP Consultant in Intelligroup Asia Pvt Ltd. with close to 4 years of SAP experience. His core field of work is SAP Netweaver XI with a strong background in ABAP.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 1

Business Integration Converter Mapping Designer: a Step By Step Approach

Table of Contents
Introduction: ........................................................................................................................................................3 Generating the E2X Mappings........................................................................................................................3 Related Content..................................................................................................................................................9 Disclaimer and Liability Notice..........................................................................................................................10

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 2

Business Integration Converter Mapping Designer: a Step By Step Approach

Introduction:
The Seeburger BIC Mapping Designer is a tool used to create the E2X / X2E mappings. Generating the E2X Mappings Go to the folder EDI Message Catalog in the Seeburger folder. This contains all the EDI messages in their XML versions for the different standards. In our example, we are going to use the EDI Message 860 of the ANSI X12 Standard which stands for Purchase Order Change.

Note: The path to the EDI Message Catalog might differ. In our system, it was under the Seeburger/HT folder.

Select the EDI Standard for which the X2E or E2X mappings are to be generated and copy the EDI message into the local hard disk. In our example, Im going to use the ANSI X 12 standards. Lets select the EDI message 860 with the 4030 version of the ANSI X12 standards. This folder will contain the XML representation of the EDI message as shown in the below screenshot.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 3

Business Integration Converter Mapping Designer: a Step By Step Approach

Open the BIC Mapping Designer and import the XML representation of the 860 message by right clicking on Active Mappings and Import as shown in the below screenshot. Now, the message will appear under the ANSI_X12 segment with the name 860_V4030.

In the sub menu for New select the option ANSI X12 message. This will open up the popup window as in the below screenshot. Select the 860 message.

Now, the XML version of the 860 message will be added to the list of existing messages as shown in the below screenshot.

Now, select the node Generator Mappings and click on the button Testing Environment button in the application toolbar. This will open a new window. Provide the XML representation of the EDI message as the source and provide the name of the mapping program to be generated as the destination along with the path in the local drive where it is to be stored. Here I will save it in the same folder from where we actually imported the EDI message.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 4

Business Integration Converter Mapping Designer: a Step By Step Approach

The naming convention followed here is NV_E2X_ANSIX12_860_V4030. Select the mapping as createMappingEDIToXML and click on the Convert, Compile and Show button. This will compile the mapping and generates an XML file with the name of the mapping program (NV_E2X_ANSIX12_860_V4030). This file is saved in the same folder that contains the XML representations of the EDI message.

Now, the XML file for the E2X mapping is generated. Import that file into the Mappings node of Active Mappings. Right click on Mappings and click import. Select the XML file for the E2X mapping from the folder.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 5

Business Integration Converter Mapping Designer: a Step By Step Approach

Now, the mapping will be displayed under the Mappings Node.

Now, double click on the mapping program name. This will open the mapping in a separate editor and allows us to select any specific characteristics as per our requirement such as specifying the delimiters etc.
Note: The delimiters can be specified only for the X2E mappings.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 6

Business Integration Converter Mapping Designer: a Step By Step Approach

Now, to test the mapping, click on the Testing Environment button on the application tool bar.

Provide the EDI 860 file as the source and provide the name of the output file as the Destination (usually the output file name would be out.xml by default and we can provide a different name also along with the path). Provide the name of our newly created mapping in the Mapping text box and click on Compile, Convert and Show button. This will execute the mapping and will create the output file in the specified location in the xml format. Once the testing is done, now is the time to deploy the file into the system. To accomplish this, right click on the Active Mappings node and select Create deploy file as shown in the screenshot below.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 7

Business Integration Converter Mapping Designer: a Step By Step Approach

This will open a popup window. Select the path to create the SDA file and click on Generate SDA file.

This will create a file with the .sda extension, usually with the name mappings_user.sda. Once the file is generated, contact the basis team to deploy this SDA file in the XI system. The generation of the XML-to-EDI (X2E) mappings is also the same as the generation of the EDI-to-XML (E2X) mappings.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 8

Business Integration Converter Mapping Designer: a Step By Step Approach

Related Content
http://www.chaseconsultancy.com/Downloads/BIS%205%20Whitepaper.pdf http://www.english.icg.pl/sap/index.php/lg/en/page/co_robimy/sub/seeburger/sub1/bis/sub2/bic https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/9807

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 9

Business Integration Converter Mapping Designer: a Step By Step Approach

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 10