Solution : https://service.sap.com/sap/support/notes/672503 (SAP Service marketplace login required)
Summary :
Table logging is erroneously enabled for the KONP table, a master data table, leading to potential performance degradation if system profile parameter 'rec/client' is set for logging in DBTABLOG. This issue stems from a delivery error wherein typically only Customizing tables should have logging activated as per R/3 standard delivery. To rectify, users should deactivate 'Log data changes' for the KONP table via Transaction SE13, saving and activating these changes afterwards to ensure optimal performance.
Key words :
addition system profile parameter 'rec/client', start transaction se13, database table konp, ==> log table dbtablog, call table konp, checkbox 'log data, master data table, /3 standard system, table logging, customizing table
Related Notes :
| 781433 | Log table DBTABLOG increases due to tables SKAT, SKAS |
| 608835 | Performance problems due to table logging? |