Skip to Content
Product Information
Author's profile photo Uwe Radtke

Introducing the SRT_MONI Generic Search Framework (GSF) – a new way of filtering SOAP Web Service Messages by content


The transaction SRT_MONI is used to monitor ABAP-Web-Service-Messages (WS Messages). This transaction enables you to search for WS Messages, and filter them based on criteria like date, time, message ID, sender-, and receiver information etc. However, it is so far missing the functionality to filter the messages based on their content easily (transaction SRT_MONI also provides the possibility to search for content values, but that is more complex and can’t be run in background.

Therefore, the SRT MONI Generic Search Framework (GSF) was developed. It introduces a new modular way to filter the messages based on the information extracted from their corresponding XML data. The goal of this development is to create an easy and customizable way to filter WS Messages based on their content.

Details on the technical background can be found in the article Extension and enhancement of the SRT_MONI Generic Search Framework (GSF) 

The new functionality is available by transaction code: SRT_MONI_GSF

To run this transaction the user needs to have the authorization to run transaction SRT_MONI.

User Interface

Figure 1 shows a screenshot of the User Interface. So far, the user interface consists of two major sections. The standard selection criteria, which is not customizable, and the enhanced selection criteria, which is customizable using the GSF. The customization is explained below.

The standard selection criteria are used to pre-select messages as shown in Figure 2 (the uppermost box). The section containing the enhanced selection criteria is used to browse the content of the WS message. The two dropdown menus “Search Object”, and “Selection Parameter” are used to group the technical names into different categories. The “Search Object” defines herby the generic term (e.g. Business Partner, Customer, Vendor etc.). The “Selection parameter” defines the subcategory (e.g. ID, Name etc.). Every Selection Parameter corresponds to an unlimited number of technical names. The grouping of the technical names is further explained in the enhanced technical description of Transaction SRT_MONI_GSF.

Figure 1 – User Interface

The pushbutton “Service Selection” provides the user with a popup (Figure 2) on which they can select the webservices they want to search for. By default, all webservices are selected. It is mandatory to select at least one webservice.

Figure 2 – Select / De-select Services

In the field “Value(s)”, enter the values you want to search for, e.g. different Business Partner IDs. After all fields are filled, the search can be started either by pressing F8, by clicking the button “Execute” in the lower right corner, or by choosing “More” -> “Program” -> “Execute”. The search starts in the foreground. The screen is locked until the program is done. An example of a result list is shown in Figure 3.

Figure 3 – Example of a result list

The performance can be low due to a high number of messages that need to be extracted and analyzed. For that reason, foreground processing might not be useful. To offer more utility, background processing is available in the SRT Moni Generic Search Framework. By choosing “More” -> “Program” -> “Execute in Background”, the search gets submitted as a job. You can display the running Job e.g. using transaction SM37 or via “More” -> “System” -> “Own Jobs”. After the job has finished, the message IDs found are displayed in the print job log as shown in Figure 4.

Figure 4 – Example of a result list as job log

The message IDs can be easily copied and transported for further analysis to transaction SRT_MONI.

Delivery and initial usage hints

The new transaction is available via the following SAP notes:
2971973 – SRT_MONI_GSF Creation of package
2972601 – SRT_MONI_GSF Interface Note
2972602 – SRT_MONI_GSF Application Note Business Partner
2980590 – SRT_MONI_GSF Application Note T100 Messages

The SAP notes have to be applied in the given order.

Per default the new functionality is delivered for mainly Business Partner Services searching the name, number of the Business Partner or the number of the customer / supplier. Technically the supplier ID is listed as Vendor ID for historical reasons.

The search itself for the names of the Business Partner does support wildcard search – the standard SAP search parameters are provided.

Additionally all Services are used for an error message search. The error message search is very broad and should be provided with the following syntax:

(R11)046                                                                                                                  (see Figure 5)

Figure 5 – Syntax for searching for message within the service messages

The message search also provides Wildcard search as well as a search containing only the corresponding message number.

Final remarks

As this is a very new functionality which hopefully enables easier acess to data echange via Web Services, a follow up Blog post will be provided to explain the technical bckground in more dtail and also will provide a step-by-step description of the very easy to use enhancement concept.

In case an error occurs you would need to raise an incident on application component LO-MD-BP-WS.

We have taken all measures possible to make this post as accurate as possible, but things sometimes fall through the cracks. In case you find any errors or inconsistencies please let us know.
The above given dates and times might change without notice and/or reflection in this blog. For latest accurate dates and times, please check out the referenced, and non-referenced information available from SAP


With SAP Notes 3101750 and 3101780 also the sender interface name is introduced. The purpose and usage is analogues to the receiver (e.g. instead of receivernametable use sendernametable) interface name.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Vipindas Vidyadharan
      Vipindas Vidyadharan

      Hi Uwe,

      Thanks for introducing this new tool (or building).  Really worth it.



      Author's profile photo Claas Barjenbruch
      Claas Barjenbruch

      Hi Uwe,

      Thank you for the information. We are looking for a way how we can setup automatically email notification when there are errors in SRT_MONI. How can we achive this? I tried to run this in background and then with email notification, but then we only get the notification that the job was completed.

      Any ideas?

      Best regards,


      Author's profile photo Michael Ohlendorf
      Michael Ohlendorf

      Hello Uwe,

      Thank you very much for your blog. During business partner integration testing we are currently experiencing many replication errors in the SOA Webservice interface between our MDG-hub and the S/4 target system.

      Issue our build team is experiencing troubleshooting all failed messages is that messages are huge and it takes too long to go through all the messages content to find the error message(s).

      Could you please confirm if TCODE: "SRT_MONI_GSF" can be used to find all error messages in a SOA Webservice message and list the BP-IDs next to it for which the error messages did occur? E.g. by performing an error message wild card search "(R*)". They need to be able to find the error messages without already knowing them in advance as well as the affected BP-IDs.

      Thanks in advance!



      Author's profile photo Felix Moehler
      Felix Moehler

      Hello Michael,

      at the moment the SRT_MONI_GSF will only show the WS messages in which the error did occur, but it will not show for which BP ID exactly.

      The SRT_MONI_GSF will redirect to transaction SRT_MONI after the analysis and show all the relevant messages.

      I hope this clarifys your questions.

      Best regards



      Author's profile photo Uwe Radtke
      Uwe Radtke
      Blog Post Author

      Hi all,

      maybe to clarify the answer a bit more - via SRT_MONI_GSF it's possible to search for WS messages containing a specific partner - identified e.g. via number or name. It's also possible to search for a specific error message. BUT the combination of both is unfortunately not available. The intention was to see which WS messages were exchanged in a given time frame for one specific partner or how many WS messages with the same error message did occur. But we did not think to combine this approach as that would have made the framework too complex.

      Kind regards

      Author's profile photo Shivang Bhatt
      Shivang Bhatt

      Thanks for the blog, this is definitely helpful for business partners.

      However, I was looking for how can we use this tool for Inbound/Outbound delivery search.



      Author's profile photo Uwe Radtke
      Uwe Radtke
      Blog Post Author

      Hi Shivang,

      this highly depends. See the linked article how an own implementation could be achieved - should not take too long for an experienced developer. You could implement your own class and maintain the needed data. But be aware - the transaction has to scan ALL messages and the payloads for the given time and type of message. Here you might need to include background processing with automated workflow generation. But the transaction itself enables you to perform context based searches without much effort on the SRT_MONI configuration via SOAMANAGEr.

      Kind regards