For internal table with key defined, the index table is created at runtime. Can we see the index table(basically its content) while debugging?

[former_member210333]

For e.g., if we create an internal table of type /SAPAPO/MATLOC which has a secondary index LID(LOCID) with fields MANDT and LOCID as the keys. So if we write a report to fetch the data from the DB table to our internal table and do some read/append operation in it. And while doing the read/write operation is there any way to see the content of the index table which was built over the index LID?

[bernd_dittrich]

Good question, also very keen to get the answer. Another follow on question from my side would be if there is a way to get this information at runtime in my coding efficiently, e.g. if I only have to do a read once it can be more efficient to do this without using the index as the index will be build up which takes more time than the full table scan, however, if the index already has been build up in a previous read we should use this index, of course.

[bernd_dittrich]

Found this posting which might help for the debugger part: http://zevolving.com/2013/03/abap-new-debugger-keys-in-table-tool-from-7-0-ehp2/

[former_member210333]

Hi Bernd,

This link you provided talks about displaying the internal table content sorted based on the secondary key but provides no information about if we can see the content of the index table.

Thanks for your reply.

Regards,

Vineet Raman