3189282 - How to Delete multiple candidates via Integration centre

Using the tool Admin Centre > Delete Candidate is possible to delete candidates however there are some limitations:

• you can delete only one candidate at the time, no way to process multiple entries
• the search results may be ambiguous in some circumstances, for example searching a candidate you get two results one candidate with uppercase email and another with the same email but lower case.

To resolve those limitation there is a valid alternative via Integration Centre tool.

SAP SuccessFactors Recruiting Management

IMPORTANT NOTE:

The RCM Entity Anonymization job is limited in the number of records it can process in a single run. It is recommeded that if you are following the steps outlined in this KBA using SFTP, the RCM Entity Anonymization Job should be executed manually (not on schedule).

The integration centre job to update the candidate entity should be ran in batches of maximum 1,000 candidate profiles and after each batch is executed in integration centre. The RCM Entity Anonymization Job must be manually executed via provisioning. After the RCM Entity Anonymization Job completes, the next batch of 1,000 candidate profiles can be updated via integration centre and then execute the RCM Entity Anonymization Job after each batch.

For Previewing the records if less than 10 you can proceed as below, for more than 10 records it is recommended to add the candidate ids in a .csv file hosted on SFTP:

Part 1:

1. Access Integration Centre from Admin Centre
2. Click on My Integration > Create > Scheduled CSV Input Integration
3. Select “CandidateLight” Entity using the search tool on the left
4. Using a simple text editor prepare a CVS file as below:
   CandidateID,agreeToPrivacyStatement
   1234,false
   1235,false
5. Click on “Upload Sample CSV” and select your CSV file created
6. Select Operation: “Upsert Single” (this is very important since this scenario do not support “Upset Multiple”)
7. Via drag&drop map the columns of your CSV to the relevant ODATA files as you see in the screenshot
8. If the preview generate on the left is consistent, you can update the fields via “Run Preview Record”:

Additional notes:

• Always test in Test Instance before to attempt in Production instance
• As first attempt try one candidate ID only by providing one single Candidate ID in CVS file
• You can process several candidates just adding multiple lines in the CSV
• Create a report in Integration centre to monitor the status of “agreeToPrivacyStatement” field. The value should update from true to false. Also the Primary email will get instantly updated as consequence of the Deletion.
• This is the ODATA Payload if you wish to test as manual ODATA Upsert:

      {
        "candidateId": 1234,
        "agreeToPrivacyStatement": "false",
        "__metadata": {
          "type": "SFOData.CandidateLight",
          "uri": "CandidateLight(candidateId=5396)"
        }
      }

Part 2:

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”. 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.

2166333 - How To Set Up Anonymization - Recruiting Management

KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , How To