Configuring the Seeburger Message Splitter Using Seeburger Workbench

Applies to:
SAP XI 3.0 and above, Seeburger Adapter, Seeburger Workbench Tool. For more information, visit the Data Management and Integration homepage.

Summary
This document explains how to configure the Seeburger Message Splitter in a PI (Process Integration)/XI (eXchange Infrastructure) based EDI (Electronic Data Interchange) Integration scenario. Author: Ravi Kanth Talagana

Company: Intelligroup Asia Pvt. Ltd. Created on: 09 February 2009

Author Bio
Ravi Kanth Talagana is working as a Senior SAP XI Consultant in Intelligroup.He has an overall experience of 5 and half years in SAP and around 3 years SAP XI.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 1

Configuring the Seeburger Message Splitter Using Seeburger Workbench

Table of Contents
The Scenario ......................................................................................................................................................3 Assumptions....................................................................................................................................................3
Message Splitter in Seeburger Workbench..................................................................................................................4

Related Content..................................................................................................................................................7 Disclaimer and Liability Notice............................................................................................................................8

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 2

Configuring the Seeburger Message Splitter Using Seeburger Workbench

The Scenario
In a PI/XI based EDI integration scenario, we use the Seeburger AS2 adapter to exchange EDI messages with a VAN (Value Added Network) or any system capable of sending or receiving EDI messages over internet using AS2(Applicability Statement 2) protocol. In a typical inbound scenario, the EDI files transmitted over the internet enter into the XI system via the Seeburger AS2 adapter. The adapter has primarily three functions viz. Classify, Convert and Split. The adapter will classify the EDI message into either ANSIX12 or EDIFACT. It will convert the EDI format into XML format making use of the Seeburger E2X (EDI to XML) Mappings. The adapter will then split the incoming EDI document into the main document and the Functional Acknowledgement, which is later mapped to the XMML form of EDI 997 document. This XML form of EDI997 document will be converted into EDI format and sent back to the customer via another Seeburger AS2 Outbound adapter.

VAN or EDI Sender

Seeburger Adapter(Adapter Engine) Class ifier Conv erter Splitt er

SAP XI Integration Engine

Note: The Black lines indicate the inbound raw EDI File. The Blue line indicates the XML Payload corresponding to the EDI Message and the Red line indicates the Functional Acknowledgement which is later converted into EDI 997

In this document we look into the settings that are to be made in the Seeburger Workbench to achieve the splitting of the EDI inbound messages. Assumptions It is assumed that the Seeburger AS2 adapter is available for the XI/PI system to make use of. It is also assumed that all the EDI to XML and XML to EDI conversion mappings are generated using the Seeburger Mapping Designer and deployed in the SAP XI system. In the integration directory, the Inbound Seeburger AS2 adapters and the Split 997 adapters are properly configured.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 3

Configuring the Seeburger Message Splitter Using Seeburger Workbench

Message Splitter in Seeburger Workbench Seeburger Workbench is a web based tool which is useful in Configuring the Message Splitter amongst other things that it can be used in. Typically, the URL that you need to use to launch this workbench is: http://<SAP XI System host name>:<Port Number>/seeburger/index.html The home page will look like the following:

In this document we will look into the function of Message Splitter in particular. Step 1) Click on the Message Splitter link. Enter the same user id and password that is used to logon to SAP XI system.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 4

Configuring the Seeburger Message Splitter Using Seeburger Workbench

Step 2) Click on the New Button in the Data Management area. The following screen will appear.

Step 3) Enter the details that are to be filled. a) Sender: Enter the EDI ID of the partner who is sending the EDI Document. Each EDI Customer will have a Unique EDI ID for identification. This will be available in the Raw EDI file. b) Mapping name: Enter the name of the E2X Mapping, which is generated using the Seeburger Mapping Designer and Deployed into the XI system. Typically it follows the following pattern for ANSIX12 classification: <Seeburger Classifier Mapping ID>_E2X_ANSIX12_<Transaction Set Number>_V<EDI Version Number>. Eg: NV_E2X_ANSIX12_850_V4010, NV_E2X_ANSIX12_860_V4030 c) State: Chose the radio button Accepted. d) Quality of Service: Chose whichever is applicable to your scenario. e) Channel: Chose the name of the Split 997 adapter corresponding to the customer for which you are configuring the splitter. f) Click on the Search Parties button and chose the correct Party.

g) Click on the Search Services and chose the correct Sender service. h) Click on search bindings and chose the correct Sender Agreement corresponding to the split997 adapter.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 5

Configuring the Seeburger Message Splitter Using Seeburger Workbench

i)

Click on Submit.

An entry will be created in the Message Splitter Configuration screen. These steps will ensure to dynamically determine which sender agreement is to be chosen based on the EDI ID of the sender of the EDI File. The configuration in the Integration Directory will determine the subsequent steps. The Seeburger Message Splitter Configuration is complete.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 6

Configuring the Seeburger Message Splitter Using Seeburger Workbench

Related Content
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33 http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 7

Configuring the Seeburger Message Splitter Using Seeburger Workbench

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 COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 8