‎2007 Mar 20 10:06 AM
I am processing a internal table which has got more than 10 lakh records. When I executed the program in background i found that the control is getting struck at record 89,998 and its stuck for more than an hour from now. So I started debugging the program in foreground, and created a watchpoint for Sy-TABIX for the value 89,998. But the control is not going to the required postion. Can anyone explain to create a watchpoint so that I debug why the control is stuck over there.
Regards
Ganesh
‎2007 Mar 22 6:43 PM
Hi Ganesh
Try this:
IF SY-TABIX EQ '89998'.
BREAK-POINT.
ENDIF.
Place this in you LOOP AT <itab> statement.
Regards
‎2007 Mar 20 10:08 AM
hi Ganesh,
Try placing even before that i.e, at 89,990 or 89,995.
Regards,
Santosh
‎2007 Mar 20 10:09 AM
I did that but putting at 88,000. But the control is not stopping.
‎2007 Mar 20 10:11 AM
Hi!
You can enter values for the breakpoints in the abap debugger.
Go into debug mode with /h. Set a breakpoint into the LOOP.
Click on the breakpoints button. You'll see your breakpoint in the table. There's an empty fields beside your breakpoint, write the number into it (f.e. 89985) and press enter. Then F8 and your program will stop after the 89985th loop.
Regards
Tamá
‎2007 Mar 20 10:14 AM
‎2007 Mar 20 10:20 AM
The control is still looping sequential rather than jumping the condition for which i have created the watchpoint.
‎2007 Mar 20 1:57 PM
hi,
Can you try this.
pass the sy-tabix to a variable in the internal table and keep a watch point for the variable at your record number.
Br,
Laxmi
‎2007 Mar 22 6:43 PM
Hi Ganesh
Try this:
IF SY-TABIX EQ '89998'.
BREAK-POINT.
ENDIF.
Place this in you LOOP AT <itab> statement.
Regards
‎2007 Mar 23 2:03 AM
I could have done that. But now the code is already in quality box (the only place where we are facing the problem, no problem with any of the settings everthing has been cross checked more than twice by the BASIS guys). I dont have rights to re-transport the program.
‎2007 Mar 23 2:05 AM
I didnt had any choice, and took help of my colleagues to actually go to that record by debugging sequentially. I didnt had any other better solution.