Logging Long Texts 
You can activate and deactivate the logging of long texts without technical modification by setting up the logging facility for the tables STXH and STXL. Long texts are texts that you enter in certain applications in the form of comments or explanations.
Like changes in tables, each change to these long texts is written to a logging table. You can use the evaluation function (S_AUT10) to search for the logged long texts according to your own predefined criteria.
Prerequisites
The system profile parameter rec/client must be active for each client in which you want to log the long text tables STXL and STXH (see below).
You have activated table logging for the tables STXH and STXL in the transaction S_AUT01.
Ensure that all long texts are archived with the archiving object S_AUT_LTXT. See also: Archiving Long Text Logs (BC-SRV-ASF-AT)
Features
Logging of Long Texts in the Logging Table DBTABLOG
When an SAP system is customized, the user has the option of enhancing the data for certain applications through supplementary comments or explanations. The system stores these long texts in the tables STXL (actual text) and STXH (header data) along with various attributes such as object value and ID. If you have activated table logging for the tables STXL and STXH, the old long text is stored in the logging table DBTABLOG each time a change is made to a long text. The system writes all changed long texts to the table DBTABLOG. As a result, the volume of data in this table rapidly increases. To limit the extent and speed of this increase, only logging-relevant long texts (for example, long texts entered in the pharmaceutical industry for work in a controlled environment) and their history should be stored.
You can use the filter for long text logging to define restrictions: You can specify in advance whether changes are to be logged with regard to a series of long texts.
Deletion Flag and Deletion Reports for Long Texts That You Did Not Want to Be Logged
To remove unwanted logged long texts from the table DBTABLOG, you can set (or subsequently unset) a deletion flag in transaction S_AUT04. In this transaction, all long text objects in the system are listed.
You can then immediately start the deletion report with transaction S_AUT05.
Note
We recommend that you carry out transaction S_AUT05 for test purposes only and with small volumes of data.
Report S_AUT_DEL, which can be run as a background job, checks the list created by transaction S_AUT04 to determine whether the Deletion Flag has been set for a long text object. It then removes the relevant long text logs from table DBTABLOG. If the Deletion Flag is unset at a later point in time, the system saves all subsequent changes to the long text of this data object in the table DBTABLOG again as of that time.