topic Re: Debugging in background in Application Development and Automation Discussions

Debugging in background

Former Member — Thu, 07 May 2009 07:32:05 GMT

Iam running a report which using PP01 transaction.when i run foreground there will be no errors and working fine.

When i run the same in background processing it throws exception like 'Runtime error RAISE_EXCEPTION has occurred'.

any one know what might be the reason?

how to debug the code when it is running batch job.

I tried with sm50 and capture job when in debug but no use.

Re: Debugging in background

Former Member — Thu, 07 May 2009 07:34:10 GMT

hi,

Refer to this link..[Debugging a program running in background|]

Re: Debugging in background

jayanthi_jayaraman — Thu, 07 May 2009 07:35:35 GMT

Hi,

Go to sm37. Choose the job which got cancelled. In the command bar just enter JDBG and then press enter.

Re: Debugging in background

Former Member — Thu, 07 May 2009 07:39:20 GMT

Hi,

Refer thie below thread

Regards,

Jyothi CH.

Re: Debugging in background

RaymondGiuseppi — Thu, 07 May 2009 07:44:03 GMT

PP01 is not allowed in background mode, look at OSS [Note 721791 - Dump when running a batch input session in OM|https://service.sap.com/sap/support/notes/721791]

Reason and Prerequisites
Transactions PP01/PP03 and so on expect an active SAP GUI connection.
For this reason the program terminates during the background processing.

Regards

Re: Debugging in background

Former Member — Thu, 07 May 2009 08:00:21 GMT

1. Run the specified program in the background by choosing program->Execute in Background. This step would execute the required program in background.

2. To debug the background job. Go to the transaction Sm37. You will see the job that was run under your name. Now, type ‘’JDBG’’ in command line and put the cursor on the respective job which you want to debug.

3. Now, press enter. It would directly go into the program in the debugging mode. This would now simulate the exact background scenario with the same selection screen values as used in the job and sy-batch set to ‘X’.

Now, you can debug in the same way as you do in an interactive session of running a program.

Just an extension to the above tip, you can also use the transaction SM50. After going inside the t-code, from the menu, choose Program Mode~~->program~~-> debugging.

Edited by: vinay raj on May 7, 2009 10:01 AM