2166333 - How To Set Up Anonymization - Recruiting Management

According to data privacy regulations, candidates/applicants may require from the Recruiters not to store their data under specific circumstances. Anonymization is an act of editing the database to change the unique data to no longer unique. Anonymization requires a configuration change and setting up a scheduled job in Provisioning.

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 Recruiting Management

Please refer to the article 2103393 - "Which data may be anonymized, when using DPCS 2.0?" explaining which data can be anonymized when using DPCS 2.0.

For more information about anonymization, please refer to the following KBA: 2080965 - "Candidate Anonymization".

1. Prepare a list of available fields for anonymization from the Candidate Profile, Application and Offer Details templates.
2. Change the value from anonymize="false" to anonymize="true" for all fields chosen by the customer.

Please keep in mind there are standard fields, custom field types and background element field types restricted from the anonymization, as mentioned in 2103393:

Standard fields restricted from anonymizing in Candidate Profile:

• Gender
• Ethnicity
• Race
• Disability status
• Veteran status
• dateOfAvail
• minAnnualSal

Custom field types restricted from anonymizing:

• Date
• Percent
• Boolean
• Number
• Instruction
• Currency

Background data field types restricted from anonymizing:

• Date
• int
• float

Standard fields restricted from anonymizing in application template:

• averageRating
• applicationDate
• lastModified
• reviewDate
• source
• statusId
• referralSource
• jobsApplied
• gender
• ethnicity
• race availability
• disabilityStatus
• minAnnualSal
• veteranStatus
• bkgrndChkStatus
• startDate

In offer detail template, only fields of job application can be set to anonymize="true". The job req fields are restricted from anonymizing. For offer detail custom fields, String and picklist custom fields can be set to anonymized.

3. In order to trigger the anonymization, you will have to set up a scheduled job in Provisioning with the job type “RCM Entity Anonymization Job”:

4. It is recommended that the scheduled job runs daily in order to achieve almost real-time anonymization.

NOTE: Setting up this configuration or only part of the configuration is out of SAP Support scope. If any configuration part of the Anonymization process is required, please, engage an implementation partner or SAP Professional Services. To understand what is part and what is within SAP Support scope, please, refer to KBA 2258199 - Software Change Request for SuccessFactors Recruiting Management.

2080965 - Candidate Anonymization - Recruiting

2103393 - Which data may be anonymized, when using DPCS 2.0? - Recruiting Management

2258199 - Software Change Request for SuccessFactors Recruiting Management

Anonymization Job, Data, Anonymization, Candidate, Application, Privacy, DPCS, DRM, Retention, Management , KBA , LOD-SF-RCM-ADM , Admin Center, RBP, Permissions and Settings , How To