Avoid debugging SAP standard code.

[Former Member]

Hi,

I would like to know whether it is possible to avoid debugging SAP standard code, a lot of the times it just complicates the specific debugging process. I know it is possible to step out of functions etc., but I would like to have an option that says "Do not show any SAP standard code when debugging."

Does such an option exist or do you have any other tips and tricks

Thank you in advance...

[Former Member]

Hi Michael,

I'm sure you are talking about debugging in the development environment. If that is the case, then you can use breakpoints in the (custom) code, so that you can always start from the point where you are interested.

Among the break points, you could use programmed break points as well as breakpoints set explicitly after the code is generated.

Regards,

Anand Mandalika.

[Former Member]

Yes, I'm talking about debugging in the development environment.

I know about the breakpoints, but if you want to debug a longer sequence of program execution, e.g., if you have a program with screens and subscreens and want trace a program flow, then you will be entering SAP standard code when changing screens.

I was hoping for a more simple solution than placing breakpoint several places to be able to skip SAP standard code faster.

Michael Jakobsen

[Former Member]

Hi Michael,

I believe that using the breakpoints and the features of the debugger judiciously, you will be able to avoid entering the SAP code while in the Debug Mode.

It all depends on where you have placed the breakpoints AND what steps you follow to reach those breakpoints. For Example, when you have a breakpoint set in your program , there's no points using the single-step (F5) option in the debug mode. You can directly choose the continue (F8) option.

This is just one scenario. For virtually every case, you can choose the breakpoints in such a way that the SAP code will never have to be debugged.

It also requires some practice, I suppose, to master the art of debugging !!:-)

Regards,

Anand Mandalika.

[Former Member]

With all due respect I think you are talking idealistic. It is great to use breakpoints and get used to it but sometimes it is hard to skip SAP std code to do specific value check.

From my experience I can tell you that if you debug a std prog. then you should always open a parallel window and look for specific functionality of the SAP prog. then you can always decide if you would like to process the code step by step F5 or skip it with F6 moving to the next module. Yes with practice and specific search you will be able to make judgement very easily.