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.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

debugging

Former Member
0 Likes
498

hi,

how can u find the error directly for example i have 10000 records but the error is in 9990th record.before i dont know the exact after checking only it will find.but it will take time by setting break point every where?

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
466

Are you talking about BDC using call transaction?

In that case you have to use MODE = 'E' (error mode).

if you are talking debugging in general, you can go for watchpoints.

YOu have to create a watchpoint with a condition that,

sy-tabix = 9990

Regards,

Ravi

3 REPLIES 3
Read only

Former Member
0 Likes
467

Are you talking about BDC using call transaction?

In that case you have to use MODE = 'E' (error mode).

if you are talking debugging in general, you can go for watchpoints.

YOu have to create a watchpoint with a condition that,

sy-tabix = 9990

Regards,

Ravi

Read only

Former Member
0 Likes
466

u have an option like u can set the watch point fro which ever u require u give the

tab-fieldname and operator like > or < or = and give the value as 9990

and save it

wn u excute like f8 it will directly stops at that 9990th record

Read only

Former Member
0 Likes
466

Hi Surendra,

If you know the Internal table in which the error is occurring, then when there is LOOP AT <itab>.

....

ENDLOOP..

Statement, create a WATCH POINT, for SY-TABIX EQ 9990, click on Execute (F8) button. When the value of sy-tabix is 9990 or when the loop reaches 9990 entry it stops saying watch point has been reached.

Be careful, in specifying whether it ai local watch point or not and check the number of entries in your internal table.

Please let me know if further details are required.

Regards,

Goutham.