Skip to Content

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

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?

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Dec 11, 2015 at 05:03 AM

    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.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 11, 2015 at 05:08 AM

    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/

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.