SAP documentation<\/a> for details.<\/p>\n2.1 SAP Transaction AUT03<\/h2>\n
Again let\u2019s look at the purchase order table EKKO using transaction AUT03. It is the same screenshot we used to explain for the chapter above, but with different focus:<\/p>\n
![\"SAP](\"https:\/\/www.dab-europe.com\/\/wp-content\/uploads\/2024\/04\/SAP01.png\")
<\/p>\n
Sharp-Eyed readers may have spotted there that the checkbox \u201eLogging\u201c was not set \u2013 however we claimed that changes were logged in CDHDR and CDPOS. The reason is that the field \u201cLogging\u201d is telling us, whether log entries will be made in the table \u201eDBTABLOG\u201c. The tables CDHDR\/CDPOS are being the container for business object related changes, and DBTABLOG is the container for changes of customizing objects. So let us have a look at a typical customizing table, for example T003, containing document types. For that table the Logging checkbox is activated; this means, changes for that one are going to table DBTABLOG. It will not be recorded in CDHDR\/CDPOS as no Change document object class is assigned.<\/p>\n
![](\"https:\/\/www.dab-europe.com\/\/wp-content\/uploads\/Publ\/cD\/SAP02.png\")
<\/p>\n
2.2 SAP transaction SE11<\/h2>\n
The settings can be looked up in transaction SE11 as well. For the first example, we will start with purchase order header table EKKO.<\/p>\n
![\"SAP](\"https:\/\/www.dab-europe.com\/\/wp-content\/uploads\/2024\/04\/SAP03.png\")
<\/p>\n
Clicking on \u201eTechnical Settings\u201c we can see that \u201eLog Data Changes\u201c is not active.<\/p>\n
![](\"https:\/\/www.dab-europe.com\/\/wp-content\/uploads\/2024\/04\/SAP04.png\")
<\/p>\n
However we remember that changes have been logged in CDHDR\/CDPOS. So this option here is about whether it is getting logged in table DBTABLOG, and this is not the case for table EKKO.<\/p>\n
The same approach for the document type table T003 leads us to the following result:<\/p>\n
![](\"https:\/\/www.dab-europe.com\/\/wp-content\/uploads\/2024\/04\/SAP05.png\")
<\/p>\n
Here the checkbox is active, this means that changes of document types which are stored in customizing table T003 are getting protocolled in the change log table named DBTABLOG.<\/p>\n
2.3 SAP transaction SCU3<\/h2>\n
A complete list of those tables which are customizing tables with activated logging can be retrieved using SAP\u00ae transaction SCU3. It offers a button named \u201eList of the logged tables\u201c and returns all customizing tables, for which the changes are getting recorded.<\/p>\n
![\"SAP](\"https:\/\/www.dab-europe.com\/\/wp-content\/uploads\/2024\/04\/SAP06.png\")
<\/p>\n
Summary<\/h2>\n
Understanding the change records in SAP is an important, yet special topic, which sometimes is difficult to differ clearly, as scenarios may overlap. Having similar checkboxes in the same dialogs (\u201eLogging\u201c in AUT03 or \u201eLog data changes\u201c vs. \u201eChange document\u201c in SE11) which actually do have different meaning can be confusing.
I hope that this article will help you to sort things out \u2013 just keep in mind the differentiation between \u201cbusiness objects\u201d (more business related) logged in CDHDR\/CDPOS and \u201ccustomizing objects\u201d (a more technical perspective) which will be recorded in table DBTABLOG.
Should you have comments to that article, or if you want to share your own (probably different) experiences with me, contact us anytime!<\/p>\n\n\n