Procedure documentationDestroying Requisition Data Using HRRCF_REQ

 

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_REQUISITION to delete requisitions 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_REQUISITION 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 HR: E-Recruiting - Requisitions (HRRCF_REQ) archiving object to destroy the data for candidacies and applications that are connected to requisitions with the status Closed or To Be Deleted.

You can destroy the following data:

  • Applications and candidacies that do not have the status In Process

  • Related attachments and activities

  • You can also opt to destroy the related requisition including posting texts and other publications.

Note Note

The data about the candidate remains in the system.

End of the note.

To select the data, you can use the requisition types Job-Specific Requisition and Application Group. The system destroys the data at the end of the defined retention period. You can, however, define different retention rules for each requisition type.

You can restrict the selection of data for data destruction to a country, region, or company.

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, the system does not necessarily delete data 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 connected activities and file attachments deleted.

The following programs are available for HRRCF_REQ:

Program

Function

RH_RCF_ARC_REQ_WRI

Write

For more information, see Creating a Write Variant for HRRCF_REQ.

RH_RCF_ARC_REQ_DEL

Delete

For more information, see the application Archiving Object Definition (transaction AOBJ).

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

  1. Inform yourself about the data and messages issued in the log.

    For more information, see Technical Data for HRRCF_REQ

  2. Familiarize yourself with the condition fields and time references that are available in ILM for defining retention rules for HRRCF_REQ.

    For more information, see ILM Information for HRRCF_REQ

  3. Familiarize yourself with the checks for this archiving object.

    For more information, see Checks for HRRCF_REQ

  4. Perform application-specific Customizing.

    For more information, see Performing Application-Specific Customizing for HRRCF_REQ

  5. Create a write variant for the archiving object.

    For more information, see Creating a Write Variant for HRRCF_REQ

  6. Familiarize yourself with the authorizations for this archiving object.

    For more information, see Authorizations for HRRCF_REQ

  7. Familiarize yourself with the enhancements for this archiving object.

    For more information, see Enhancements for HRRCF_REQ