Featured

ST22 (ABAP) Errors


Transaction code ST22 is used to lists the ABAP dumps generated in the system, we can restrict for a date, user as required. This each record indicates the reason for the error, transaction code, variables that caused the error. The types of error can be of various kinds for which action is to be taken to fix this error from happening again after analysis
An ABAP program can be terminated during its runtime for a number of different reasons. The database table SNAPTID lists all existing runtime errors (in total, around 1900).
To allow clearer processing, the runtime errors are divided into categories:

Internal errors Error in the VM -> can only be reported to SAP using an error message.
Errors in the ABAP runtime
Errors in the screen runtime
Errors in the database interface

The system was able to roughly determine the area in which the error occurred. Next, clarify whether it was triggered by an internal error or by a programming error.
ABAP programming errors Errors in the ABAP program, such as a division by zero or a catchable exception that was not caught.
Installation errors These include, for example, inconsistencies between the kernel and the database. A typical installation error is therefore the error
START_CALL_SICK
Resource bottleneck Typical example: SYSTEM_NO_ROLL. The application no longer has sufficient memory available.
External errors The error was caused by a call outside the system.
Example:
● The code page of the operating system does not match the SAP system language
● An incorrect logon attempt occurred when calling outside the SAP system (for example, RFC SDK).


End user errors These errors include, for example, incorrect end user printer settings.
No error The program was not terminated due to an error, but rather due to deliberately performed actions.
Example: If an administrator actively cancels a running transaction, the RABAX SYSTEM_CANCELED is thrown. In cases like this, no error correction is required.
ST runtime errors The error occurred during a Simple Transformation (ST). The cause is a programming error in the ST program.
Internal ST errors The error occurred during a Simple Transformation (ST). There is an internal error in the ST VM.
XSLT runtime errors The error occurred during the execution of an XSLT transformation.
ITS errors The error occurred in ITS. These are usually HTMLB errors, however the error could also be due, for example, to a resource error within the ITS.

If you read the entire dump carefully you may notice the following information
1) UserID through which abap dump was resulted
2) Terminal-id from which above user has logged it.
     Using this terminal id you may resolve the ip address using the following command
         ping <terminal-id>
3) Reason of the dump. Which program resulted in the dump
Note
Do you know that the old version of transaction code ST22 is RST22.

Post a Comment

Any difficult to understand and implement this then don’t hesitate to ask me via comments Your comments are always appreciated except spam.

CodeNirvana
Newer Posts Older Posts
© Copyright Full SAP BASIS
Back To Top