An ABAP program can be terminated during its runtime for a number of different reasons. The database table SNAPTID lists all potential runtime errors (in total, around 1900).
To allow clearer processing, the runtime errors are divided into categories. The category of the runtime error returns hints on cause of the error and troubleshooting.
Internal Kernel Error | Error in ABAP Kernel. RECOMMENDATION Sending an error message to SAP. |
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. RECOMMENDATION If you are dealing with a non-modified SAP application, send an error message to SAP. |
Installation errors | These include, for example, inconsistencies between the kernel and the database. EXAMPLE A typical installation error is the error START_CALL_SICK. |
Resource bottleneck | EXAMPLE Example: SYSTEM_NO_ROLL: The application does not have enough memory available. |
External errors | The error was caused by a call outside the system. EXAMPLE
|
End user errors | Incorrect printer settings at end user. |
No error | The program was not terminated due to an error, but rather due to deliberately performed actions. EXAMPLE If an administrator cancels a running transaction, the runtime error SYSTEM_CANCELED is thrown. |
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. This is usually an HTMLB error. |
No comments:
Post a Comment