Categories of ABAP Runtime Errors

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 provides hints on the cause of the error and troubleshooting.

Internal Kernel Error	Error in ABAP Kernel. Recommendation Sending an error message to SAP. When doing this, use the application component displayed in the header of the long text (if displayed). End of the recommendation.
ABAP programming errors Dynpro programming errors Simple transformation programming errors XSLT programming errors ITS programming errors	Programming errors specific to the program type. Example: Division by zero or a catchable exception in an ABAP program that is not caught. Recommendation If you are dealing with a non-modified SAP application, send an error message to SAP. When doing this, use the application component displayed in the header of the long text (if displayed). End of the recommendation.
Installation and administration errors on your ABAP server	These include, for example, inconsistencies between the kernel and the database. A typical installation error is the error `START_CALL_SICK`. Recommendation This is most probably a local problem in your ABAP system. End of the recommendation.
Resource bottleneck on your ABAP server	Example: `SYSTEM_NO_ROLL`: The application does not have enough memory available. Recommendation This is most probably a local problem in your ABAP system. End of the recommendation.
Temporary problem in your ABAP runtime environment	The problem is only temporary. Recommendation This is most probably a local problem in your ABAP system. End of the recommendation.
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.