You can choose which parts to store: current layout (customized desktops), debugger settings, options and breakpoints.As of release NetWeaver 7.0 it fully replaces in the scope of its functionality the old-fashioned Classic ABAP Debugger.During the last SAP TechEds I learned that more and more people use the New ABAP Debugger (that is a great news) but still many are not aware of some of its useful features.
The purpose of this blog is to point you to these features so that you can make the most of the New ABAP Debugger. Abap Debug In Task How To Use ThemHere you will find some helpful debugger settings with instructions on when and how to use them. You can access debugger settings in the debugger by using Settings-DisplayChange Debugger Settings: System Debugging: if you have problems that involve system programs (such as a function that cant be accessed in the debugger), turn on this setting (or use menu Settings-System debugging OnOff or the command hs in the debugger command field). You can declare a program as a system program by setting Status to System Program in its attributes in the ABAP Editor (SE38) (check the radiobutton Attributes and press Change button). Update Debugging: turn on this setting if you need to analyze asynchronous updates, which are functions that are called as follows: CALL FUNCTION. IN UPDATE TASK. These functions are executed asynchronously in a special update work process (after the next COMMIT WORK statement). The debugger cant follow them since it is attached to a single process. Set a breakpoint in the function that is called IN UPDATE TASK, start debugging, turn on this setting, and the debugger will reach the breakpoint in your update function. TRFC (In Background Task): Block Sending: turn on this setting if you need to analyze transactional Remote Function Calls (TRFC), which are called as follows: CALL FUNCTION. IN BACKGROUND TASK. These functions are called asynchronously, along with other TRFC functions of this logical unit of work (LUW), after the next COMMIT WORK statement. When you turn on this setting, these TRFC functions are stored in the system for debugging instead of being sent. Use the TRFC Monitor (transaction SM58) to analyze the unprocessed LUWs and select Edit-Debug LUW to debug them. ![]() If you switch on this setting, then the debugger will be closed automatically after pressing Continue (F8), when the roll area (internal session) is ended. Always Create Exception Obj.: turn on this setting if you need to analyze exception objects (if you catch ABAP exceptions in your program via the CATCH CXMYEXCEPTION without specifying a reference variable to which the exception object can be assigned). You can then examine the created exception objects in the debugger via Display Exception Obj. You have finally found the function module which doesnt work properly under certain conditions. You may need to hand over this debugging session for further analysis to a colleague who has expert knowledge of this function module. In order to ensure that your colleague can reproduce the problem, you must create a very detailed description: the source lines at which to set breakpoints, the debugger settings that must be active, and so on. This is time consuming and there is still a chance that you might forget critical information. In such situations, use a debugger variant (menu Debugger-Debugger Session-Save ) to store your debugger session.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |