Table for storing Long Texts in FD33

[Former Member]

Hi everybody!

Iu2019ve been working with tcode FD33 for a report and we had the idea of include some fields in the Status view exactly in Control Area Text.

The transaction for add new entries in this part is OBT3. The problem is that I canu2019t find where the LONG TEXTS are stored, I already have the table for the name (TTXIT, STXH)

Does somebody know about this LONG TEXTS stuff?

Thank you in advance!

Sandra

[RBM · Accepted solution]

Hi,

Try with STXL table.

Hope this helps!

Regards.

[Former Member · Accepted solution]

Hi!

I've already tried it and only shows an extra data: BIN2 data element for SYST: 109

I don't know if it is useful for other table.

Thanks

Sandra

[RBM · Accepted solution]

HI,

I´ve checked on the system and there are stored in STXH.

You need to pass the right parameters, the text for credit management use the text object: KNKK

Use the function READ_TEXT if you want to translate to normal text, for my example:

Text Object: KNKK

Text Name: 00000000010001

Text ID: 0001

I think this solve your issue!

Regards!

[Former Member · Accepted solution]

Hi!

I've already cheeked SHTX table with the parameters that you mentioned, and for my example, i could see the lines which i'm working on but not the field: LTEXT "Long Texts", my objective.

In technical options i could see that is in structure RTEXT but i want to find the table,

Sorry, but maybe i have a misunderstood in Long Texts Terms

Thank you in advance!

Sandra

[RBM · Accepted solution]

Hi Sandra,

I think you are confused about the LTEXT field, all the texts are saved on STXH table, even if it has a lots of lines... if you use multi text line, you could see the first line always is populated on LTEXT field.

Hope this helps!

Regards!

PS: I just realized we both speak Spanish!...

[Jelena]

The long texts are stored in SAP in such a way that they're not easily accessible in the database. The texts are stored as sort of "raw" data and they need to be read using READ_TEXT FM and saved using SAVE_TEXT FM.

Due to that it's usually not a good idea to drag the long texts into any reports or, for that matter, use them to store any data that is needed for reporting purposes.