Skip to Content

XI: How to test your mapping (in real life scenarios)

As we can see on the XI forum many new users are experiencing some problems with mapping tests.

This weblog shows a very simple path on how to test them with two scenarios:

a) if you’re not using BPM (integration process)

b) if you’re using BPM

When you send the data to XI you might see that your mapping program doesn’t always work the way
you’d like it to work. Very often it’s because either your Data Type or your inbound message
does not have a correct format. Your mapping program works when you test it from the Test Tab
(inside Integration Repository) but you wonder why is shows mapping errors when you send a real message.
The best (and only?) way to resolve such errors is to use the REAL inbound message.

Testing mapping programs without BPM.

Step 1


– choose you message

– choose the payload of the inbound message


Step 2

– copy the source XML of your message


Step 3

– paste the source of your message into your mapping program


Now you can be sure that you test a correct message.

Testing mapping programs with the use of BPM.

Step 1

– open the Technical workflow log of your BPM

– choose Show container option (from your mapping step)

– choose your inbound message


Step 2

– open your message and now follow the same steps as for testing without BPM


With these few steps you can be sure that the message you test has a correct format – exactly the one
that was sent to your adapter, so you can debug it easily inside your mapping program.

You must be Logged on to comment or reply to a post.
  • Hi Michal,

    Am just trying a simple multi-mapping scenariuo using enhanced interface determination. In the TEST tab of both Message Mapping as well as Interface Mapping the execution is compleetd successfully but in the MONI am getting follwoing error –

      RuntimeException in Message-Mapping transformatio~
      com/sap/xi/tf/ in Message-Mapping transformatio~

    Can u help me to solve this issue ???

    • Hi Divya,
      you can try to better understand the error by viewing the trace of the message: it reports where, in the mapping, something throws this runtime exception, as in the “error” section you can see only the stack initial part.
    • Hello  Divya<br/> <br/>Could you remember how you solved this problem?<br/>I get the same error like you with my mapping<br/>in a Mail to File scenario with use of BPM<br/><br/>SAP:P2></SAP:P2> <br/><SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3> <br/><br/>With regards<br/>Roy

  • before reading this blog, i didnt know to get the BPM messages through mapping-container …

    Thats really gr8.Keep blogging 🙂

  • Hi Michal,

    This is a nice blog. In my case i am doing CREAMS to file. When i do manual testing mapping works fine. But when I post a idoc which is already created in R/3, using bd14 T.C.
    Failed to map it. That means who created idoc in R/3 is incorrectly created?