3758767 - Candidate anonymized despite active recruiting application — SAP SuccessFactors Recruiting Management

• A candidate has been anonymized despite being actively involved in an ongoing recruiting process.
• The candidate is still linked to an open job requisition and the recruiting process is not completed.
• No manual anonymization action was performed.
• The candidate’s personal data is masked although the candidate has not been rejected, withdrawn, or hired.
• The candidate applied to the job while the requisition was open.

SAP SuccessFactors Recruiting Management

1. Create and launch a candidate purge request that includes profiles reported as inactive.
2. Before the purge request is approved and executed, the candidate logs in and applies to an open job requisition (candidate becomes active in the process).
3. Approve and execute the previously created purge request without regenerating its content.
4. Observe that the candidate is anonymized even though the candidate now has an active application on an open requisition.

The candidate had been included in a previously generated purge report (based on an inactive profile). Although the candidate later applied to a job before the purge was approved and executed, anonymization still proceeded because the candidate remained in the original purge request.

The purge request was initiated after the candidate profile had already been marked as inactive and included in the inactive profiles report. There was a delay between the initiation of the purge request and its eventual approval.

During this interim period, the candidate logged back into the system and applied for a job requisition. However, since the profile had already been identified and included in the purge process earlier, the candidate’s profile was subsequently anonymized as part of the scheduled purge activity.

1. To prevent similar occurrences, use “Invite to Apply” so candidates can be engaged without requiring them to self-apply before purge approval is finalized.
2. Extend the “Period of Non-Acceptance” in Data Retention Management to reduce the chance that recently re-engaged candidates remain in an older purge request.
3. Review purge requests for accuracy immediately before approval and execution to ensure they reflect the latest candidate activity status.
4. Refer to the related guidance below for configuration details and behavior clarification.

• Refer to: KBA 2795899 - candidate purged with an active job application
• Refer to: KBA 2670133 - anonymize candidate
• Refer to: KBA 2080965 - candidate anonymization - recruiting management

candidate anonymized, active application, open requisition, purge request, purge report, anonymization, recruiting process, data retention management, drtm, inactive profile, invite to apply, period of non-acceptance, gdpr, masking, recruiting management , KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , Problem