ST11 — Developer Traces
ST11 is used to display developer trace files written by SAP work processes and system components for low-level technical troubleshooting. It is most useful when a work process, gateway, dispatcher or other kernel-level component reports a problem that application logs do not explain. For reliable SAP support, capture the exact system, client, user, time and object context first, then use the transaction's evidence before making configuration or data changes.
Verified practitioner reference for ST11 — Developer Traces. It explains what the transaction does, when it is appropriate, which parameters and evidence matter, how to use it safely, common diagnostic traps, and how its role changes or remains relevant in S/4HANA.
Published 19 Sept 2026· 641 words
Purpose
display developer trace files written by SAP work processes and system components for low-level technical troubleshooting. The transaction is most valuable when used as part of an evidence chain rather than as a shortcut. Start from the exact business or technical incident, preserve its user, time, system and object context, and distinguish display/analysis functions from actions that can alter system state.
When it is used
ST11 is typically used when a work process, gateway, dispatcher or other kernel-level component reports a problem that application logs do not explain. Consultants also use it during project testing and post-change validation because a repeatable selection gives objective evidence. In production, keep the initial scope narrow and widen it only after confirming that the first result matches the reported incident.
How to use it in practice
- Identify the server and component involved before opening traces.
- Match the exact incident timestamp to the appropriate dev_* file.
- Read the surrounding sequence rather than one isolated error line.
- Increase trace level only for a controlled reproduction and return it afterward.
- Correlate kernel traces with SM21, dumps and application logs.
Key data objects
These are the most useful anchors for work in ST11. Capture them in incident notes or test evidence so another consultant can reproduce the same result.
- trace file — verify the exact value and its relationship to the affected execution or business object.
- application server — verify the exact value and its relationship to the affected execution or business object.
- process/component — verify the exact value and its relationship to the affected execution or business object.
- timestamp — verify the exact value and its relationship to the affected execution or business object.
- trace level and error sequence — verify the exact value and its relationship to the affected execution or business object.
How to prove it in the data
Build a reproducible before-and-after proof. Capture the exact selection or object, record the status, log or result that demonstrates the issue, then apply one controlled correction and repeat the same check. Correlate with neighboring SAP logs, documents or repository objects where needed. A successful retry with changed input is not the same as proving the original root cause.
ECC vs S/4HANA
ST11 remains a standard ABAP-platform tool for viewing developer traces in S/4HANA systems. Availability of a classic transaction does not automatically make it the preferred implementation pattern for new work; distinguish support compatibility from clean-core and cloud-oriented design guidance.
Common pitfalls and how to diagnose them
- Reading a trace from the wrong application server. Validate the exact object, user, timestamp and release context before applying a fix.
- Leaving elevated trace levels active and generating excessive files. Validate the exact object, user, timestamp and release context before applying a fix.
- Treating low-level trace text as a business root cause without application context. Validate the exact object, user, timestamp and release context before applying a fix.
Whose problem this is
Primary ownership is usually with the BASIS team. Bring in Basis, Security, functional or development specialists only when the evidence crosses those boundaries. A high-quality escalation includes the exact transaction, selection or object, timestamp, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/st11ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.