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.
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.
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.
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.
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”.
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:
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