How to analyse, debug and optimize your SAP programs with standard tools
There is a phase in development cycle when the programmer needs to optimize his final product. This post focuses on those transactions which help developers to analyse, debug and optimize already finished reports and programs.
This post is part of series about
SAP transaction codes for ABAP Developers:
- Basic SAP transactions for ABAP developers
- How to modify and extend SAP applications
- Transaction codes for database and table handling
- How to analyse, debug and optimize your SAP programs with standard tools
SAP system offers several options how to analyze our programs. Let’s start with the debugger.
Developer tools
Debugger
There are basically two options how to use a debugger. You can either start the debugger when you set a session break point in your code while using se80 or se38. When you run the program additional window with (new) debugger will show up.
The other method to is enter one of these following codes into command field just before you run the report:
- /h – basic and most used command which will run the debugger
- /hs – start debugger and allow system debugging
- /ha – start debugger, skip screen handling and start directly debugging ABAP code
- /hmusa – start debugger and create memory snapshot which can be analysed in transaction S_MEMORY_INSPECTOR
沒有留言:
張貼留言