3774540 - How to make a Custom Object field available in Read Audit Reports for Sensitive Data

• Users need to report who accessed custom attachments stored on MDF objects.
• I need to audit the visibility of a custom MDF object
• Can we use custom MDF objects in the Read Audit reports?

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

SAP SuccessFactors HCM Suite

To make a field from a custom MDF object available to the Read Audit Reports, it is necessary to define the field as containing sensitive personal data:

• In the Configure Object Definitions page, from "Create New", select Legislatively Sensitive Personal Data. The page below will open and it is necessary to fulfill the custom object information, as per demo environment screenshot below: 

Use the guide Defining a Custom Object as Containing Sensitive Personal Data for a Given Module | SAP Help Portal to fulfill the information. 

Important Notes:

You can’t enable read access logging for the following scenarios:

• If the field is of data type Auto Number, Auto Complete, or Data Source.
• If the field is a system field.
• If the field is configured as a searchable field, context field, or a value help parameter.
• If the field is one of the standard fields: externalCode, externalName, effectiveStartDate, effectiveEndDate, transactionSequence, and effectiveLatestChange.

• Defining a Custom Object as Containing Sensitive Personal Data for a Given Module | SAP Help Portal
• Configuring Fields for Read Access Logging | SAP Help Portal
• Configuring Read Audit | SAP Help Portal

mdf, metadata framework,  audit report, access audit, successfactors, document access, mdf attachments, sf , KBA , LOD-SF-PLT-RAL , Read Access Logs , How To