Skip to Content

In this blog I will explain how you can easily retrieve the long error text from the Adapter Engine. In this case your alert will give a better error text trace.


Following the SAP Library it is only possible to retrieve the first part of the error message (SXMS_TO_ADAPTER_ERRTXT):

This results into an error text that shortens the rest from the error message.


To retrieve the entire error message you just have to use following container variable:

This container variable will fill up the entire error message in your alert, no need to define a separate container variable:


This will result in the complete stack trace alert:

This example is tested on a SAP PI 7.11 system.
For a detailed overview concerning this feature you can access following note:
SAP Note 1294312 XI alerting: SXMS_TO_ADAPTER_ERRTXT is truncated.

To report this post you need to login first.


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

  1. Former Member
    But, i have a strong opinion that the stcaktrace thrown by various PI engines could be improved tremendously by SAP. I was fortunate enough to be in the adapter development team of another middleware product and we did the exercise of creating standard Error Ids and Error text for each try catch blocks in the adapter code. This way each error thrown will have a clear error id/error text(and NOT the ugly stacktrace) and the SAP PI documentation should have clear instructions as to what this error id/text is and how it could be resolved. We did this exercise 7 years back in the other middleware i am referring to here. But, still in Pi we see ugly stacktaces which leave us clueless in Adapter monitors or on the central monitor like SXMB_MONI.
    Take a product, e.g. Oracle db, the ORA-XXX errors are std and has clear cut documentation, i am talking an improvement something of this kind. Hope it happens in PI too. well i digressed a bit, but wanted to :).

    Good effort.



Leave a Reply