Skip to Content
In this blog I will try to explain message transformation 1..N using ABAP mapping. I would like to thank my friend and colleague Anish Raghavan who helped and supported me in contributing to this blog.     The below explained scenario splits the input message into two output messages using ABAP mapping. Here the content of the ABAP code has to be changed based on the transformation to be done on the XML. Screenshots of the steps to be followed has been included in this document wherever required. Details about the scenario configuration is not in the scope of this article. In my blog How to test ABAP mapping when transforming messages  (How to test ABAP mapping when transforming messages 1..N), I have illustrated how to test ABAP mapping while splitting messages 1..n. *Pre-requisite for *doing ABAP Mapping:* * The following entry: R3_ABAP|Abap-class need to be added to Exchange profile under IntegrationBuilder ->IntegrationBuilder.Repository -> *Message split using ABAP mapping:* I will be using the following payload as input to XI: image  The objective is to create two different messages (two xml files) in output which should look like below. I have highlighted the different file names that are created. !file:///C:/Documents%20and%20Settings/hsasidha/Desktop/SDN|height=1|alt=Picture1|width=1|src=file:///C:/Documents%20and%20Settings/hsasidha/Desktop/SDN|border=0! image image
To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member
    Hello Hari,
    Nice Blog from your experience. I want to add the following “This 1:N transformation using ABAP mapping is much useful while delaing with huge size of messages like >15MB or 20 MB.”



Leave a Reply