Solution : https://service.sap.com/sap/support/notes/608835 (SAP Service marketplace login required)
Summary :
You can enable table logging in your SAP system by using the `rec/client` profile parameter, especially for Customizing tables where logging is pre-activated due to audit requirements. These tables generally have fewer data changes and thus lower impact on performance. Conversely, master and transaction tables, heavily altered, are not set up for logging by SAP to avoid performance issues. Use caution when logging these as it can lead to both resource and performance constraints. If needed, you can track and manage logging activities through transaction SCU3 to diagnose and resolve any related problems efficiently.
Key words :
rec/client system profile parameter, dbtablog ursache und voraussetzungen, weitere begriffe activity log, memory problems occur unexpectedly, dbtablog log table, selection screen displayed, table selection empty, activate table logging, rec/client, delivers customizing tables
Related Notes :
| 1589734 | |
| 1499357 | |
| 1497672 | |
| 1303671 | Logging data changes for the table /SAPAPO/TSTROBJR |
| 1303588 | Logging the data changes for the table TTSTR |
| 781433 | Log table DBTABLOG increases due to tables SKAT, SKAS |
| 672503 | Performance: Log table DBTABLOG increases because of KONP |
| 1916 | Logging table changes in R/3 |