SAP Knowledge Base Article - Public

2603939 - How to enable Change Audit for MDF objects? Usage of version History on Object definition page.

Symptom

  • How to enable change audit for MDF objects?
  • How is MDF version history field useful in Object Definition?

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Environment

  • SAP SuccessFactors HCM Suite
  • Metadata Framework (MDF)

Cause

If the 'MDF Version History' is not set to 'Complete History', it is not possible to run an audit as this information was not being stored by the system. [Reference: Help Guide - Basic Configurations in Object Definition -MDF Version History ]

Resolution

The MDF Version History allows you to capture the MDF audit information about added, updated, and deleted field values and records. This type of audit information is captured as change audit and can be viewed in Change Audit Report.

This is important in integrations such as Employee Central Payroll and Employee Central to user management.

Possible values are:

  • No: If this option is selected, or no selection is made, history records aren’t stored for any operation and no audit records are generated.
  • Delete History: If this option is selected, only the audit records from the delete operation of that object type are generated. The data deleted by a full purge import and translatable fields are also included.
  • Complete History: If this option is selected, every update or delete operation generates a copy of the current record and stores it as audit information. The data deleted by a full purge import and translatable fields are also included.

Eg:

  • MDF Version History is used to fetch the history from the audit table.
  • There are three options to select from MDF Version History when you open an  MDF object definition.

version history.png

Q) Can We use audit information to restore deleted data?

A) Enable MDF version history for the objects you want to capture the audit information. If not enabled, SAP will not be able to provide any audit report through support tickets.( Open an case under the Foundation & Tools category (LOD-SF-MDF)). By default, MDF Version History for picklists is set to Complete History, so that you can generate a change audit report for all picklist changes.

Q) How can we audit on Position Data Changes?

A) Check reference KBA 2875676 - How can we audit on Position Data Changes? Note that the system will only begin storing Audit information for Position once the 'MDF Version History' has been enabled. Hence, if you have just enabled the 'MDF Version History' you will not be able to retroactively look back at audit data from changes before you enabled it

Q) I suspect a user has deleted data related to specific custom MDF object, can I audit this person changes ? 

A) If MDF Version History is not enabled then it is not possible to provide Audit data.

Q) I have MDF version history enabled I want to run a change audit report related to this specific custom MDF object

A) If MDF Version History is enabled, follow KBA 2790859 and ensure to filter by user by specifying the externalCode=<User ID>. Note: Commonly, the filter set is ChangeBy=<User ID> wich is not accurate if you are looking for the user related MDF changes.

 

See Also

Keywords

MDF Version history, MDF history, Audit, MDF audit, Audit logs, MDF history, MDF change audit, MDF change history data, MDF Configuration data, MDF Version History, Complete History, Delete History, NO, MDF Change History Data , KBA , LOD-SF-MDF-AUD , MDF Audit , LOD-SF-EC-ADM , Admin Tools (EC Core only) , LOD-SF-PLT-AUDR , Request Audit Report (Not Change Audit) , LOD-SF-MDF , Metadata Framework , How To

Product

SAP SuccessFactors HCM Core all versions