‎2008 May 16 2:55 PM
Hi All,
Debugging from SM50 for a function module is triggering only in some cases for the same test case....!!!!
I need to debug a Function module which is called from an Event.
To debug this I have written While...EndWhile Infinite Loop, and debugging it from SM50, but the problem is It is going to debugging mode in few cases for he same Test case .
What could be the problem , if some one has come across this kind of problem then please try to help me out ....
Waiting for your Inputs
‎2008 May 16 3:21 PM
Can any one help me out please !!!
I was able to debug today but suddenly it has stopped working
‎2008 May 16 3:24 PM
Well try loging off and login again to reset your session cache. Give it a try,
‎2008 May 16 3:28 PM
Dear FY..thanx for your reply , I have tried the same but no use
Can you give some more inputs or ideas please....!!!!
‎2008 May 16 3:51 PM
Hello.
Do you have to run it in background?
If not, don't use SM50. Just put a break point before the WHILE statement and run it in SE38 normally.
If yes, remeber that SM50 don't stop the processing if it would get a short dump, i.e, if in the second you click debug the runtime is in the middle of a comit process, or something similar, it will wait until give debug to you.
Best regards.
‎2008 May 19 5:13 PM
The other work around is. Go to SM37 and check for your current batch job.
Select it and in the command input box (where you input the transaction codes like SE38 etc) type in JDBG. This will trigger the background debugging mode. This dose work.
Hope this helps.