0% found this document useful (0 votes)
20 views5 pages

Debugging in SAP: Popup Workaround Guide

Switching on the debugger in a popup window is not possible using /H. However, a workaround is to create a shortcut on the desktop by generating a shortcut, setting the type to System Command and command to /H, then dragging the shortcut onto the popup window to start the debugger. To debug a background job, set a breakpoint in the relevant program using transaction SM37. Select the job, navigate to the program, set the breakpoint, then enter JDBG in the job's command field to activate the debugger and reach the breakpoint with F8. This allows analyzing the program to identify errors.

Uploaded by

Jaspal Kumar
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views5 pages

Debugging in SAP: Popup Workaround Guide

Switching on the debugger in a popup window is not possible using /H. However, a workaround is to create a shortcut on the desktop by generating a shortcut, setting the type to System Command and command to /H, then dragging the shortcut onto the popup window to start the debugger. To debug a background job, set a breakpoint in the relevant program using transaction SM37. Select the job, navigate to the program, set the breakpoint, then enter JDBG in the job's command field to activate the debugger and reach the breakpoint with F8. This allows analyzing the program to identify errors.

Uploaded by

Jaspal Kumar
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Note:- The maximum number of dynamic breakpoints are 30 and watch-points are 10 that you can place in ABAP

for
a login.
Have you ever tried to switch on the debugger in a popup window? We cant use /H in the command field in this case. But there is a work around for this
problem.
Switch to other SAP session.

Click on generate a shortcut icon on the standard toolbar.

In the popup screen enter the title for the shortcut, Type as
Finish.

System Command, Command as /H and location to store the shortcut and press

This will create the shortcut on the specified location i.e Desktop in this case.

Find the shortcut on the desktop, drag and drop this shortcut on the popup to start the debugger.

How to Debug a SAP Background Job?


It is easy to debug an error job to find out the cause of the error. To debug the background job, go to transaction code SM37 and display the jobs.

First we need to keep a break-point in the program, so that the control stops at the break-point when the debugger is switched on. To find the name of the
program, select the job that we want to debug and press step in the application toolbar.

Display the program by using the Menu Goto > Program.

Keep a break-point in the program and go back to Job overview screen.

Again select the job that we want to debug and enter JDBG in the command field and press enter.

Once JDBG is entered in the command field the debugger will get switched on. Now press F8 to reach the break-point in the program.

Now we can analyze the program for the cause of the error.

You might also like