Skip to Content
Author's profile photo Michal Krawczyk

XI/PI: Personalized logging & tracing

If you follow any standard XI best practices one of them will for sure be: Turn off logging of sync messages
on your production server!…also don’t use Trace Level = 3!


If you want to find out how to turn it on (or off) have a look at my weblog:
XI: I cannot see some of my messages in the SXMB_MONI

But the question some of you may ask yourself is: is there any way I can log my message
without changing the global parameter LOGGING_SYNC ? As you probably can imagine – there is a standard way.
You can use Error Analisys Settings to do that. You can access them via transaction SXMB_ADM


Step 1

I disabled LOGGING_SYNC paramter on my XI server. As you see the logging is swiched off.
(the reason why I see this message in SXMB_MONI is that is has a mapping error)


Step 2

Next we can open Error Analisys Settings and create a condition for which logging will be swiched on.
In my case this will be username as I will start the message via http test HTML page and use my user.


As you see there are a few more options you can choose from.


Step 3

Next we need to choose an action – this is place where we can specify that our message needs to be logged.
When configuring your settings here remember to set expiry date so your rule will become inactive
if you forget to disactivate it youself.


Now when we run our flow we will see that he message was logged even though the LOGGING_SYNC parameter is not set.


Even though this is avery basic setting it’s not very commonly used but if SAP gives us such tools why not use it ?

In one of my next blogs I will try to describe one more parameter (probably more intereting for those who like
ABAP debugging – and who doesn’t) from those error settings – DEBUGSTRING

Assigned tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member
      Hello Michal,

      SAP has a small disclaimer regarding error analysis. There will be a significant performance with error analysis as each call will be scanned for the error condition.

      It is higly adviced to keep very few much needed error conditions in production.


      Author's profile photo Michal Krawczyk
      Michal Krawczyk
      Blog Post Author
      Hi Naveen,

      thanks for the info
      that's probably why expiry
      sets itself till the next day by default 🙂


      Author's profile photo Former Member
      Former Member
      Hi Michal,

      I am using this blog to prevent the logging of a particular synchronus interface and i could not acheive it. My scenario is B2B and i want to turn off logging only for a particular synchronus interface and i dont want to turn off the logging for other synchronus interfaces.

      can you please suggest how can i acheive this by using this blog or any suggestions or help would be really appreciated



      Author's profile photo Former Member
      Former Member
      Hi Michal,

      I tried this

      IF Client -- XYZ (Name of partnet)
      THEN LOGGING - 0

      But i still see the payload from the call Adapter. Can you please let me know how can i remove this payload as well.