In this blog post I show you where texts from the text log in the „Text“ assignment block of the CRM WebUI are stored in the database table and how to display them in a readable format.
A use case could be the debugging of control characters and tags on a database level, e.g. when the appearance between applications such as the CRM WebUI and the Focused Build Simple IT Request differs.
The text log of incident number 8000022493 contains some text (in this case two entries of the text types „Description“ and „Reply“).
The first step is to get the ticket GUID from table CRMD_ORDERADM_H (transaction SE16). The timestamp (field CREATED_AT) could also be useful later on. So enter the OBJECT_ID (which is the ticket number, in this case 8000022493) in the selection field and execute (F8) for retrieving the GUID.
Then browse the transparent table STXL (STXD SAPscript Text-Datei Lines) with SE16. Enter the GUID in the selection field TDNAME followed by a wildcard (*) and execute (F8).
So you get a result list with entries for each single text (TDID) in the ticket. As you can see, TDNAME consists of the ticket GUID on the left, the timestamp including milliseconds on the right, filled up with blanks. The texts we need are somehowe stored in the field CLUSTD.
Unfortunately,as you can see in the data dictionary (transaction SE11) the data type of this field is LRAW (a byte-like data type) and therefore cannot be read by human beings.
Next, call the function module READ_MULTIPLE_TEXTS with transaction SE37 (Function Builder) and execute (F8).
Copy TDNAME from table STXL followed by a wildcard (*) to the import parameter NAME and execute (F8).
Depending on the number of texts in the ticket you get one ore more entries in the TEXT_TABLE export parameter. Click on the icon.
Finally, scroll to the field LINES on the right and click the icon.
The number of entries in LINES is the number of lines in each text.
Here is the text!
Reading content from a field of the LRAW data type is not that easy but is sometimes helpful. Feel free to comment on this blog post and tell about your own use cases.