While there is no way around the work involved in troubleshooting problems in your ABAP programs, SAP provides a variety of standard logging, analysis, and trace tools that help you identify, understand, and resolve problems without using the ABAP Debugger, a tool that can consume excessive time and resources when used in the wrong situation. However, only the ABAP Debugger can perform a detailed analysis at the source code level, to determine the value of a specific variable or to figure out where a special variable is changed, for example. This article shows you how to use the ABAP Debugger appropriately and effectively, so that when you must use it, you will be able to do so with confidence and a minimum of time and effort.
Boris Gebhardt
Boris Gebhardt studied physics at the University of Erlangen-Nürnberg, Germany. He joined SAP AG in 1998, where he currently works in the ABAP QM group. Boris is responsible for customer support and SAP internal consulting for the ABAP programming language and its surrounding tools. He is also involved in the development of ABAP tools, including the New ABAP Debugger, and was engaged in a development project for the public sector.
If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.