Group Reporting Data Audit

[HengyeZhu]

In this blog, we are going to share with you some insights with regards to the audit feature in Group Reporting from technical perspective. In BPC NetWeaver standard model, it is possible to track transaction data change as well as activities / tasks. For Group Reporting which is part of S/4 HANA, it might be possible to achieve the similar functionality as following.

1. Master Data Change Log
    The majority of the Group Reporting master data table is delivered with "log activated" which could be confirmed via SE11 -> Technical  Settings. For example, table FINCS_BUNIT is used to store consolidation unit master data.

It is possible to track the data change log via transaction code SCU3 if system is configured properly as per note 2437986 - SCU3 | How to enable logging in the system.

2. Transaction Data Change Log

Each of group reporting tasks will log the data posting in the log table such as FINCS_LOG_HEADER (Log Header) and FINCS_LOG_ITEM (Log Details). So it is possible to track the data change by leveraging such consolidation log.
If some tasks are enabled delta posting (majority of the reclassification tasks as of S/4 HANA 2022), which means the execution will not remove the previous populated data, then ACDOCU table itself could be leveraged to track transaction data change.

3. Activity Log

Transaction code STAD records all the user activities in the system and keep such records for three days. Such statistic log could be leveraged to track user activities similar to GRC AC feature.

Hope the above information could give you some idea on how to build custom audit program to display the audit report similar to BPC.