SAP ST22 Tcode

It displays ABAP runtime errors (short dumps), the detailed record of a program that terminated abnormally, essential for diagnosing crashes and errors.

• 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.

• 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).

• TIME_OUT (long-running online program, run in background).
• MESSAGE_TYPE_X (a program-issued abort).
• Storage/memory dumps from inefficient code.

• Reading the source position before the runtime error name. The name is the diagnosis; the line only says where the program gave up.
• Assuming a dump means nothing happened. The current transaction rolled back, and anything committed earlier in the session, or sent to another system, still stands.
• Waiting. Dumps are deleted by a standard reorganisation job, often within days, so the evidence expires while somebody decides whether to look.
• Reading one dump instead of the list. Whether it is one user, one job, or everybody is most of the answer, and only the list shows that.
• Searching notes before checking whose code it is. A dump in a Z program is yours and no note will exist.