Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Enter JDBG(no / before JDBG) in command field and place the cursor on the job name. Now press ENTER button.
It takes you to debug mode
F8 and you will hit your break point. If this does not work, place the cursor in the program/function module and press F7 three times. It takes you to the program
the process would be vague but I used to do this for debugging any Background Jobs. You can create a Temporary Table. then you can update or insert values from the program to this table and varous location where you feel to check for values. once the proces is completed go to the table and check if the values entered there are correct if not you'll know the position where it has ended up with error so you can then fix it up.
We however are facing a problem. as wen fetching data into BI system trhough RFC call. BI logs into R/3 using ALEREMOTE and starts a job in background.
we tried endless while loop and debug the code through SM50 it didnt get into debugging. surprisingly system let me debug all dialog programs through SM50.
apart from writing values in table, is there any better way?
The best way to do it is SM66, then click on "Debugging", this works for the various process thread types.
It usually depends if the program is at a point where it will support debugging (ie if it's spending minutes waiting for a return from the database, then the debugger has to wait as well)
Enter JDBG(no / before JDBG) in command field and place the cursor on the job name. Now press ENTER button.
It takes you to debug mode
F8 and you will hit your break point. If this does not work, place the cursor in the program/function module and press F7 three times. It takes you to the program
if you want debug the background job then you have to create infinite loop in your programme.
Goto SM50
Select the work processor executing this processor.
Select Program/Mode -> Program -> Debugging. Now the execution of the program would be opened in debug mode.
Change the value of the variable, causing the program executing in endless loop and click F8. Now the program execution would successfully be completed
SAP has standard F'tn C160_HOLD_FOR_DEBUG which you can use in combination with Parameter ESN to create endless loop. If you set the User-Parameter ESN = 'X' (EHS: (developers only) = 'X': activate INC14Z_HOLD_FOR_DEBUG) then endless loop starts and via TRx SM50 you can get the process in debugging mode.
As suggest by all above reach out to the required Job first.
Place the cursor on the Job and type JDBG in the command Bar.
Now once the Debugger screen triggers you will not find the relevant program for the Job. You have to pass through the initial Debugger screen by pressing F7 (Nearly 7-10 Times you have to press F7). The initial debugger screens are part of standard execution. keep pressing the F7 until you reach the desired program.
If you give the same answer as someone else, but maybe you want to add something constructive, probably it's better to just "comment" on the existing answer so that to complete it?
Bluesky
