XI/PI: Throwing Generic Exceptions from any type of Mapping

[MichalKrawczyk]

How do you handle your mapping errors ? Do you think XI admins are happy with the way that you throw your mapping errors ?

Do you use any more practical error throwing methods like the one from Alessandro:
Throwing Smart Exceptions in XI Graphical Mapping ?

What if you could throw even more generic exceptions from your mappings ?

What does it mean you may ask...

At first we need to define what we'd like to have:

a) our method should allow to inform about the error in ERROR segment of our mapping pipeline service

b) our method should work with every mapping (java, message mapping, abap, XSLT)

c) we should be able to create our method just once and never have to change it again

So it there any way to achieve the above in XI ?

Let me show you one solution:

1. At first we will use any mapping and in case we'd like to throw an exception we will fill dynamic configuration value
(we can do it from any type of mapping). In my example I do it from Message Mapping User Defined Function.

DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);DynamicConfigurationKey keyHeader1 = DynamicConfigurationKey.create( "<a href="http://sap.com/xi/XI/System/ERROR" target="_blank">http://sap.com/xi/XI/System/ERROR</a>", "ERROR");conf.put(keyHeader1, a);return "";

2. Then we will create an ABAP mapping class that will do the "hard" part:

a) it will read dynamic configuration

b) if the dynamic configuration will be filled we will raise an exception with the value from dynamic configuration

DATA l_record type mpp_dynamic.DATA our_error type String.*  getting dynamic configuration value *  filled in by any previous mapping  CALL METHOD DYNAMIC_CONFIGURATION->GET_RECORD  EXPORTING    NAMESPACE = '<a href="http://sap.com/xi/XI/System/ERROR" target="_blank">http://sap.com/xi/XI/System/ERROR</a>'    NAME      = 'ERROR'  RECEIVING    RECORD    = l_record    .our_error = l_record-value.*raising exception with our message RAISE EXCEPTION TYPE CX_MAPPING_FAULT  EXPORTING*    TEXTID =*    PREVIOUS =    ERROR_CODE = '888'    ERROR_TEXT = our_error    .

3. Then we need to add our abap mapping class as a second mapping
(right after any mapping in which we execute our "exception") in the Interface Mapping.



4. Next you can try to execute your scenario and you will see that the message ended up with mapping error



5. Now inside the message you can see the error in Error segment of the XI Message.



Thanks to this approach throwing mapping exceptions can become very easy, your administrators will be very happy
(as they will get descriptive errors) and you will have one method for all mapping types.