SRT_UTIL — Web Service Utilities: Error Log and Traces
SRT_UTIL is the web service utilities transaction of the ABAP SOAP runtime. It shows the error log for failed web service calls and lets administrators activate payload or performance traces for a user or service, so the exact request and response can be analysed. It is a first stop when a SOAP call fails between SAP and another system.
Displays web service error logs and lets administrators activate payload and performance traces for SOAP services and consumers.
Published 31 Oct 2026· 456 words
What SRT_UTIL is for
SOAP service providers and consumers configured in SOAMANAGER can fail because of security, mapping, endpoint or application errors. SRT_UTIL collects the runtime errors and, when tracing is switched on, stores the messages exchanged. This lets support teams see what was actually sent and received instead of guessing from the partner's description.
When it is used
It is used when integrations with partners or middleware fail, including calls to and from SAP Integration Suite, when a new service is tested, and when certificate or WS-Security settings change. It complements SRT_MONI, which monitors asynchronous message sequences.
How it is used in practice
Open the error log, filter by time, user or service, and read the error details. To see payloads, activate a trace for the relevant user or service with a limited duration, reproduce the call, then display the trace. Switch traces off afterwards because they store data that may include personal information.
Fields and objects that matter
- Error log entries with service, user and error text
- Payload trace and performance trace settings
- Trace duration and the user or service filter
- Request and response messages captured during tracing
- Logical port or endpoint the consumer used for the call
How to prove it in the data
For a failing call, find the error log entry at the time of the failure and compare its message with the partner's error. With a payload trace active, the stored request should show the endpoint and content actually sent, which proves whether the problem lies in SAP, in middleware or in the receiving system.
ECC vs S/4HANA
Available in S/4HANA and other ABAP systems using the SOAP runtime, including integrations with SAP Integration Suite through SOAP adapters and with external partners directly.
Common pitfalls and how they show up
Traces are powerful and easy to leave on.
- Leaving payload traces active, storing sensitive data and filling the database
- Looking only at the partner's log instead of the SAP-side error
- Confusing synchronous call errors with asynchronous sequence issues shown in SRT_MONI
- Ignoring certificate and WS-Security errors that appear only in the detailed log
- Tracing all users at once, which makes the right message hard to find
Whose problem this is
Owned by Basis or integration support, who decide when traces are switched on and off. Application teams are involved when the error is in the service implementation, and data protection rules should govern who may read stored payloads.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Learn this properly
Lessons and topics
Source: ERPClimb — https://erpclimb.com/sap-tcodes/srt-utilERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.