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 Techinques for BDC or Bapi

Former Member
0 Likes
1,302

Hi Experts ,

                   I am debugging an Bapi Program with plenty of records ,my internal table has 250 records, i would like to debug 200th record , as i

                   know that error would be in that record , is there any direct method to jump to 200 th record,how can it be achieved?

                   Please suggest any other debugging techinques, points will be rewarded.

                  Thanks

                  Prakash .J

1 ACCEPTED SOLUTION
Read only

Phillip_Morgan
Contributor
0 Likes
1,269

Hello,

You can still set up your watchpoint. If it gets triggered at every turn, the use the skip parameter in debugger:

In your case, put 200 in this field and it will not stop for the first 199 times.

8 REPLIES 8
Read only

Former Member
0 Likes
1,269

Hi Prakash,

Try set a watching point when you debugging, condition is 'SY-TABIX EQ 200'.

regards,

Archer

Read only

0 Likes
1,269

HI Zhyang ,

                   Thanks for the answer , but my loop consists nested loops,watchpoint is getting triggered

                    for all nested loops, any more better way.

                   Thanks,

                   Prakash Rao

Read only

0 Likes
1,269

creation of watchpoint is the only option to jum to specific record. If you know unique valuen for that record, create a watchpoint for the same instead of creating on the basis of sy-tabix.

e.g. wa_mara-matnr = '2100000123'.

Read only

Former Member
0 Likes
1,269

Hi,

Watch point is the better option if u can manage to put. Other way, may be u can delete all other entries by selecting them all in one go and then uncheck the one u want to keep and select delete entries button in new debugger.

Read only

Former Member
0 Likes
1,269

Check the primary keys of the 200th record. Use conditional watchpoint for the workarea or table line variable writing those. You can write 'AND' conditions in watchpoint to get the exact entry.

Read only

Phillip_Morgan
Contributor
0 Likes
1,270

Hello,

You can still set up your watchpoint. If it gets triggered at every turn, the use the skip parameter in debugger:

In your case, put 200 in this field and it will not stop for the first 199 times.

Read only

0 Likes
1,269

Just tested what you said, it works great. I like this 'Skip'. thanks.

regards,

Archer

Read only

0 Likes
1,269

Glad it helped. There is more info here.