3755888 - DPCS-Declined Candidates Not Anonymized Within 24 Hours: RCM Entity Job Batching and Timing Explained – Recruiting Management

• Candidates who reject the data privacy consent statement (dpcs) while their application is in an in‑progress status are not anonymized or deleted within 24 hours in production.
• A large number of applications remain visible beyond 24 hours despite being marked for anonymization by dpcs decline.
• The rcm entity anonymization job runs but does not immediately purge the affected records.

SAP SuccessFactors Recruiting Management

1. Log in with support access.
2. Proxy as a recruiting user.
3. Open a job requisition containing applications that moved to the “declined dpcs” status while in progress.
4. Observe that these applications remain unpurged and data is still visible beyond 24 hours.
5. Verify via reporting that both candidate profile and job application are flagged “marked for anonymization by dpcs decline”.
6. Confirm that the rcm entity anonymization job is running; observe it does not immediately pick up and purge these records.

There is no fixed timeframe for when a candidate or application will be anonymized by the RCM Entity Anonymization Job, as processing time can vary significantly. However, the following factors should be considered:

1. 1. Batch Processing: The job processes records in batches of 5,000. The total time required will depend on the volume of records as well as the number of fields within the entity and related entities that need to be processed. Larger volumes of data naturally increase processing time.
   2. System Load and Scheduling: Other jobs, such as purge jobs, running concurrently can impact the execution time of the RCM Entity Anonymization Job due to competition for shared system resources. Frequent execution of the job itself may also cause conflicts. For optimal performance, it is recommended to schedule the job daily during off-peak hours.
   3. Monitoring and Recovery: Regularly monitor the job for any failures, which may occur due to high system load. If failures are detected, terminate the job and re-run it to ensure all records are anonymized successfully.

• 3703006 - Candidate is not anonymized after revoking their DPCS - Recruiting Management
• 3430495 - Application Withdrawn By Candidate is anonymized by the RCM Entity Anonymization
• 3626881 - Disqualified applications are being picked by RCM Entity Anonymization job - Recruiting Management
• 2784326 - Applications in Hired Status are Getting Purged by the System - Recruiting Management

dpcs, data privacy consent, declined dpcs, anonymization, anonymisation, rcm entity anonymization job, batch processing, purge, candidate profile, job application, processing time, throughput, scheduling, 5000 records, off‑peak hours , KBA , LOD-SF-RCM-ADM , Admin Center, RBP, Permissions and Settings , Problem