Skip to Content

How to find a Text table, if it exists

Have you ever wondered how to find a text table of a table ?

Well one would say it is lot easier to find. Just  go to the table in SE11, Press on Goto and click on “Text Table”. It will take you to the Text table.


Assume that we are programming and want to know whether a table has a text table ? if it exists we would to get texts from that table. So, how to find whether a table has a text table ?

We have a table “DD08L” which has information about relationships. This table has two fields CHECKTABLE and FRKART. These two feilds provide information what we are looking for.

We need to pass the table name, for which we would like to find out whether a text table exists, to field “CHECKTABLE” and pass “TEXT” to field “FRKART”. Execute to know the results.

As we know text table exists, we can find its relevant texts now.

You must be Logged on to comment or reply to a post.
      • Um... Open another session? Same way you'd use SE16 shown in the screenshots?

        Sorry, I still don't understand your point. We have a very simple way of finding a text table in SE11 and this blog just seems to offer a more convoluted way to do the same. Why?

        • This blog explains one of the scenario, when we have list of tables and expected to fetch it's relevant  text table on the go while coding instead of manually finding from SE11.

          • How many tables are we talking about "while coding" that you have to use a mass look-up? I might be missing something but this need just never occurred for me. Usually there is some sort of specification and all the tables/fields are identified there already. When we work frequently with the same tables, we learn this by heart usually. And I'd say it's unusual to see a program where you'd need, say, more than 3 text tables. So I'm still scratching my head...

            Could you provide a more specific example of scenario when this would be helpful?

            I feel it would be more helpful if the blog started with this kind of information already. E.g. "I had a business requirement to provide a report with such and such data. This involved many text tables. Using SE11 in this case seemed cumbersome, so I found this easier way." That would make more sense than "here is a simple way that everyone knows and here is a more complex way" without any context, I think.

            Thank you.

          • Hi Jelena


            I have not mentioned my exact business case, because it is confidential.  I cannot say anything about my requirement as of now. I am sorry.




          • In my instance, I had been given a business requirement to make changes to an existing report used for displaying Condition records in ALV format ( has additional functionality than standard VK13 Condition Info display ) .

            User I/Ps were Condition type and its Key combination.

            Corresponding to V/03 maintenance of "Text field" for the Key combination chosen, I had to show its description in the report.

            To get the Text table for the element marked as text field, I used FM
            "DDUT_TEXTTABLE_GET" ( which is essentially a simple select statement ).

            Here, knowing the tables / FM was the key .

  • Like Jelena Perfiljeva, I'm little confused about the real (confidential) use case for it.

    However, if you really wish to find text table of table programmatically, you may use FM DDUT_TEXTTABLE_GET (which does exactly the same explained in the blog).


  • Thanks Siva!

    It's always good to know how and where information is stored in database tables.

    SE11 and function module DDUT_TEXTTABLE_GET will not help for mass selections or inverse investigations which sometimes are needed.