Hi,
Errors that cannot be detected statically and that occur at runtime are detected by the ABAP runtime environment. Such errors lead to exceptions. If an exception is not handled or cannot be handled, a runtime error occurs. If such a runtime error occurs, the ABAP runtime environment terminates the program, generates a short dump, and switches to a special screen from which you can analyze it.
Short dumps are divided into blocks describing different aspects of the error. In the overview, you can see what information is contained in the short dump, for example, the contents of data objects, active calls, control structures, and so on. The short dump overview also allows you to display the point in the program at which the termination occurred in the ABAP Debugger.
The following kinds of errors can occur:
- Internal error
The kernel encountered an error. In this case, inform SAP.
- Installation and environment or resource error
An error that occurred due to incorrect system installation or missing resources (for example, database closed).
- Error in application program
Typical causes:
1. Contents of a numeric field have the wrong format.
2. Arithmetic overflow.
3. External procedure does not exist.
4. Type conflict when passing parameters to an external procedure.
Please use Transaction ST22 to analysis the short dumps.
Regards,
Ferry Lianto
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.