Debug

To collect all the FM’s called by some application during the work a good way will be to using Debugger-Scripting:
Log of all ABAP commands of an application can be provided by script RSTPDA_SCRIPT_STATEMENT_TRACE

Drill down to debugging as usual, select the RSTPDA_SCRIPT_STATEMENT_TRACE
Check the box “Breakpoint reached” and create new one on “CALL FUNCTION” then start the script.

When everything will be done, /h into the command line, press F3 and then stop the script.

The transaction SAS can show the results:

If you have got a program which calls another program in background e.g. Smartforms print routine, you may need to debug it or get it to stop at a break-point set in the background program. To do this all you need to do is turn update debugging on from the ABAP debugger (Settings->Change debugger profile->Update debugging).

Last week we have found an error in our Z-Smartform, which says nothing except “SSFCOMPOSER 152: Events are already defined.”
It didn’t say what data related to the error, or even which part of the smartform acted wrong.

After a bit debugging we’ve found the module with the proper position for a breakpoint:

1. Open SE80 and “Function groups” inside it.
2. Functional group STXBC.
3. Open the subroutines folder.
4. Set a breakpoint in ERR_WRITE routine.

Now, carry out the smartform and we will get all the data related to the error with all the parameters.

© Programador Sergio Paton