Using Troubleshooting Tools

The ABAP debugger lets you stop a program during runtime and examine the flow and results of each statement during execution. Stepping through a program with the debugger helps you to detect and correct errors in the source code of an ABAP program.

The ABAP Profiler tools show you where runtime is being consumed, and where effort for refactoring and optimization can best be applied. They also let you analyze and understand program flow, which is useful when you are trying to understand a problem or learn about code you need to analyze or maintain.

If an ABAP program encounters a runtime error, the program writes an ABAP short dump to document the error and help in its analysis. An ABAP short dump provides a great deal of well-structured information for localizing and understanding a runtime error, including a textual description of the error and its likely cause, an excerpt showing the location of the error in the source code, tables of variablesand their values, and more.

Dynamic logpoints have been introduced in order to support logging in quality or productive systems where the source code cannot be changed. For example, you have found a location in the source code for which you need additional monitoring details, or you may be facing a poorly localizable error situation that happens from time to time in a batch job and cannot be debugged.

The AMDP Debugger allows you to debug the embedded AMDP code within the ABAP development IDE.