Blocking and Destroying Candidate Data Using HRRCF_CAND

Note Note

Please do not use the original delete reports for SAP E-Recruiting any longer if you start to use the data destruction procedure described below. Continued use could lead to data inconsistencies.

If, up to now, you have used the periodic service DELETE_DEREGISTERED_CANDIDATES to delete deregistered candidates and if you scheduled background jobs for this purpose, you now also have to make several settings in Customizing for SAP E-Recruiting. Delete the entries for the DELETE_DEREGISTERED_CANDIDATES service under Start of the navigation path Technical Settings Next navigation step Periodic Services End of the navigation path in the following Customizing activities:

Activate Periodic Services
Determine Rules for Periodic Services

End of the note.

You can use the archiving object HR: E-Recruiting – Candidates (HRRCF_CAND) to block data about candidates and candidate profiles in the talent pool after the duration defined in the residence rules period has expired and destroy it after the duration defined in the retention rules has expired. The system destroys the data when the following prerequisites are met:

The candidate profile is released or blocked.
The candidates have no assignments.

Note
Data about candidates who were internal employees at some point in the past is not destroyed, even if they do not have an assignment.

End of the note.
The candidates have been inactive in the talent pool for a long period of time.

By executing the preprocessing program prior to data destruction, you can send an e-mail to the candidates whose profiles you want to delete. This e-mail informs the candidates that their profiles will be deleted and that their profiles can be retained if they log on to the system before the specified date. This resets the last logon date. The system then recalculates the retention period of a candidate’s profile.

Candidates who have already deregistered will not receive an e-mail.

To gain an overview of the database tables from which the archiving object destroys data, choose DB Tables in Archive Administration (transaction SARA). During a data destruction run, data is not necessarily deleted from all of these tables since the data can belong to different object types (application, candidate, or requisition). The data stays in the system until the related object type is deleted. Only then are all of the related activities and file attachments deleted.

The following programs are available for HRRCF_CAND:

Program	Function
RH_RCF_ARC_CAND_PRE	Preprocessing For more information, see Creating a Preprocessing Variant for HRRCF_CAND
RH_RCF_ARC_CAND_WRI	Write For more information, see Creating a Write Variant for HRRCF_CAND
RH_RCF_ARC_CAND_DEL	Delete

Program

Function

RH_RCF_ARC_CAND_PRE

Preprocessing

For more information, see Creating a Preprocessing Variant for HRRCF_CAND

RH_RCF_ARC_CAND_WRI

Write

For more information, see Creating a Write Variant for HRRCF_CAND

RH_RCF_ARC_CAND_DEL

Delete

Prerequisites

You are familiar with the basics of data destruction, as well as the functions for ILM policies and rules, and have defined the retention rules for the archiving object. For more information, see Introduction to Data Destruction.

Procedure

Familiarize yourself with the data and messages issued in the log.
For more information, see Technical Data for HRRCF_CAND
Familiarize yourself with the condition fields and time references that are available in ILM for defining retention rules for HRRCF_CAND.
For more information, see ILM Information for HRRCF_CAND
Familiarize yourself with the checks for the archiving object.
For more information, see Checks for HRRCF_CAND
Make the application-specific Customizing settings for the archiving object.
For more information, see Performing Application-Specific Customizing for HRRCF_CAND
Create a preprocessing variant for the archiving object.
For more information, see Creating a Preprocessing Variant for HRRCF_CAND
Create a write variant for the archiving object.
For more information, see Creating a Write Variant for HRRCF_CAND.
Familiarize yourself with the authorizations for this archiving object.
For more information, see Authorizations for HRRCF_CAND
Familiarize yourself with the available enhancements for this archiving object.
For more information, see Enhancements for HRRCF_CAND