ILM Information for HRRCF_CAND
The following information is relevant for the definition of ILM policies for HRRCF_CAND
.
You create policies and rules for HRRCF_CAND
for the related ILM object HRRCF_CAND
using the Retention Management functions of SAP Information Lifecycle Management (ILM).
To define retention rules and residence rules using ILM policies
(transaction IRMPOL
), you can use the following condition fields and time references (start time for determining the retention period).
Available Condition Fields
Condition Field | Description | Comment |
|---|---|---|
|
|
|
|
| For example, US federal states |
|
|
|
|
| Interest groups assigned to the candidate |
|
| Yes/No |
|
| Yes/No |
|
| Yes/No |
|
| Additional condition fields are available with this field: 1 2 3 4 5 6 7 8 9 |
Available Time Reference
Last Change Date
(LAST_CHANGE_DATE
): Last date on which the candidate logged on to the system; for applications entered manually this is the date on which the candidate's profile was created
Available Time Reference
END_OF_MONTH
The start of the retention period is determined based on the following logic:
The reference date is always based on the date on which the candidate last logged onto the system.
Exception: For applications entered manually, the date on which the application was created, that is, the date on which the candidate profile was created, is used.
When evaluating rules, the system determines the last date on which the candidate logged onto the system or the date on which the candidate profile was created (LAST_CHANGE_DATE
) and uses it as the reference date. You can use the time offset to override the reference date.
If you specified the time offset END_OF_MONTH
when defining your retention rules, the system uses it on the determined reference date when evaluating rules. This means that the retention period starts at the end of the month in which the last logon date or creation date lies.
For more information, see Settings for ILM Objects in Retention Management.
If you block data, it cannot be displayed or edited. The Business Partner ILM
(BUPA_ILM_BF
) business function provides you with the block function of Information Lifecycle Managements
(ILM) for sensitive data.
To set up data blocks, you define residence rules (transaction IRMPOL
). The same condition fields that you use to create retention rules also apply here. Create the residence rule for the object category SAP Business Suite and audit area GENERAL.
You can use retention rules and residence rules individually or jointly. You can design the rules so that in the first step, data is blocked, and in the second step, the data is destroyed in accordance with the retention rules.
Once you have defined residence rules, start the program for blocking business partners
(BUPA_PREPARE_EOP
) to block the candidate data.
Once you have blocked the data, neither recruiters nor other users can access the blocked data of candidates and their applications via the SAP E-Recruiting user interface. At the same time, candidates whose data has been blocked cannot log onto their candidate pages.
To view the blocked data, the user must have display authorization (activity 03) for the authorization field ACTVT
of the authorization object B_BUP_PCPT
.
Note
Only assign this authorization to a few people.
For information on scheduling the report BUPA_PREPARE_EOP
, see SAP Note 1825608
.
You define the settings for blocking and unblocking data in Customizing at .
You can find information about using ILM to block and delete business partner data in the SAP Library at Deletion of Business Partner Data.
The following prerequisites must be met before the block function can be used.
Software component SAP_BASIS must be at least Release 731.
You must have activated the following business functions:
BUPA_ILM_BF
ILM
HCM_ERC_CI_3
You define policies for HRRCF_CAND
in the SAP Business Suite
object category (OT_FOR_BS
) with the Retention Rules
and Residence Rules
policy categories.