SAP TCodes · LessonBy Arjun, SAP Solution Architect · Published · SAP S/4HANA 2023 · all levels
ST22
ST22 is the SAP transaction code for ABAP Dump Analysis (Basis/ABAP). It displays ABAP runtime errors (short dumps), the detailed record of a program that terminated abnormally, essential for diagnosing crashes and errors.
Quick answer
ST22 displays ABAP runtime errors (short dumps), the detailed record of a program that terminated abnormally, essential for diagnosing crashes and errors.
Key takeaways
- Date/time selection of dumps.
- Dump list with error category and program.
- Full dump: error, source position, variables, call stack.
- Watch out: Using the wrong variant (create vs change vs display).
Purpose
It displays ABAP runtime errors (short dumps), the detailed record of a program that terminated abnormally, essential for diagnosing crashes and errors.
Key fields and screen
- Date/time selection of dumps.
- Dump list with error category and program.
- Full dump: error, source position, variables, call stack.
- Long text with cause and possible fixes.
Tips
- Read the error text and the source line where it failed.
- Note the runtime error name (e.g. TIME_OUT, MESSAGE_TYPE_X) to search SAP Notes.
- Correlate the dump time with the user’s action (and SM21).
Common errors
- TIME_OUT (long-running online program, run in background).
- MESSAGE_TYPE_X (a program-issued abort).
- Storage/memory dumps from inefficient code.
Common pitfalls
- Using the wrong variant (create vs change vs display).
- Missing prerequisite master data or authorization.
- Not checking the resulting document/log.
Practice challenge
+0 XPStreak ×0
Question 1 of 2
Which statement is true of ST22?
Frequently asked questions
What does ST22 stand for in SAP?
ST22 is the SAP transaction code for ABAP Dump Analysis (Basis/ABAP). It displays ABAP runtime errors (short dumps), the detailed record of a program that terminated abnormally, essential for diagnosing crashes and errors.
What is worth checking when troubleshooting ST22?
Read the error text and the source line where it failed. Note the runtime error name (e.g. TIME_OUT, MESSAGE_TYPE_X) to search SAP Notes. Correlate the dump time with the user’s action (and SM21).
What is another point to note about ST22?
Date/time selection of dumps. Dump list with error category and program. Full dump: error, source position, variables, call stack.
What tends to go wrong with ST22?
Using the wrong variant (create vs change vs display). Missing prerequisite master data or authorization. Not checking the resulting document/log.