topic Re: debugging internal table in Application Development and Automation Discussions

debugging internal table

Former Member — Tue, 15 Jan 2008 09:27:05 GMT

hi,

i have 600 rows in my internal table which contains material no.s and its related data.i want to debug the data for 400th row .how can i go directly to 400th row in debugging instead of going each row in 'LOOP AT' statement.please suggest.

Re: debugging internal table

Former Member — Tue, 15 Jan 2008 09:29:22 GMT

Set a Watchpoint on sy-tabix = 400.

Or add some coding within your loop:

If sy-tabix = 400.

breakpoint.

endif.

Regards,

Michael

Please mark question as answered if so...

Re: debugging internal table

Former Member — Tue, 15 Jan 2008 09:34:02 GMT

Please check with sy-tabix

if sy-tabix = 400

regards

hitesh

Re: debugging internal table

Former Member — Tue, 15 Jan 2008 09:36:02 GMT

hard code this

If sy-tabix = 400.

breakpoint.

endif.

Re: debugging internal table

Former Member — Tue, 15 Jan 2008 09:46:09 GMT

how to use watch point.

Re: debugging internal table

Former Member — Tue, 15 Jan 2008 09:50:10 GMT

When you are in the debugging mode there is a button that says "create watchpoint". (Or hit Shift-F8)

A popup will show where you enter the field name (here: sy-tabix), the comparison operator ('EQ') and the comparison value ('400').

That´s it.....

Re: debugging internal table

Former Member — Tue, 15 Jan 2008 09:51:36 GMT

Start your code in debugging mode

Press the button Watchpoint there in Application bar

The give value in field name

then give the relational operator

then the comaprison operator

then it will stop when u will be at 400th row

regards

hitesh

reward if helpful

Re: debugging internal table

Former Member — Tue, 15 Jan 2008 10:08:50 GMT

2. Watch Point.

If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.

(For this, we have to give some

VARIABLE NAME & VARIABLE VALUE - with relational operator)

When this CONDITION gets satisfied,

(anywhere during the execution of the program),

the system will AUTOMATICALLY STOP THERE.

(EG when the value of matnr reaches the specified value)

That is the purpose of WATCHPOINT

(the system will WATCH it, like a dog)

Please go through this link:

http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.htm