topic Re: Problem in Background RFC Debug. in Application Development and Automation Discussions

Problem in Background RFC Debug.

Former Member — Fri, 13 Jan 2012 07:24:28 GMT

Hello ,

we have a RFC runs in background , written as Call fn. 'ZFN' in background task.

I switched on the System-Update debug, even preesing f9 i gave the fn module name .

Even I hardcoded breakpoint statements inside the fynction-module source .

But not able to bebug the function module .

Expecting to get ur guidance.

Moderator Message: Please use more meaningful subject lines in future.

Edited by: Suhas Saha on Jan 13, 2012 1:10 PM

Re: Problem in Background RFC Debug.

Former Member — Fri, 13 Jan 2012 07:28:11 GMT

Please follow the below processu2026.to debug the back ground job.

1. Use SM37 to get list of jobs , type 'JDBG' in the command line ( no '/' ), put the cursor on the job and press ENTER

2. You are in debug mode now. Step through SAP program (press F7 couple of times) until you get to code you need.

Re: Problem in Background RFC Debug.

Sandeep_Panghal — Fri, 13 Jan 2012 07:30:03 GMT

You can try debugging the job itslef by selecting the job in SM37 and put jdbg in command box.

Re: Problem in Background RFC Debug.

SuhaSaha — Fri, 13 Jan 2012 07:37:12 GMT


> we have a RFC runs in background , written as Call fn. 'ZFN' in background  task.

RFC via BACKGROUND TASK triggers a transactional-RFC(tRFC), it doesn't run in background!

I switched on the System-Update debug, even preesing f9 i gave the fn module name .

You cannot use "System-Update" debug to debug a tRFC call. You need to activate the "[TRFC (In Background Task): Block Sending|http://help.sap.com/saphelp_nwpi71/helpdata/en/43/fc78b4482a6bede10000000a11466f/content.htm]" option in the debugger settings & debug via SM58(tRFC monitor).

BR,

Suhas

Re: Problem in Background RFC Debug.

Former Member — Fri, 13 Jan 2012 09:26:15 GMT

while you start debugging.. goto settings-> change debugger profile/setting -> here check the 3 check boxes (system, update, trfc) and then(or before) you keep external break point with the user name the RFC is executing in that RFC FM.

you will be able to trigger almost all debug points