SAP ABAP IMG Activity RCF_LAWPERIOD (Store Legal Periods)
Hierarchy
ERECRUIT (Software Component) E-Recruiting
   PA-ER (Application Component) E-Recruiting
     PAOC_RCF_BL (Package) Recruitment Factory: Business Logic
IMG Activity
ID RCF_LAWPERIOD Store Legal Periods  
Transaction Code S_KER_43000214   (empty) 
Created on 20050324    
Customizing Attributes RCF_LAWPERIOD   Store Legal Periods 
Customizing Activity RCF_LAWPERIOD   Store Legal Periods 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name RCF_LAWPERIOD    

Use

In this IMG activity, you store the time limits that are to be observed for the retention or expiration of data for requisitions and applications in the countries in which you want to use SAP E-Recruiting.

Based on specific legal requirements, certain time limits for deleting or retaining data must be observed for rejected applications or completed recruitment processes. Different time limits apply for different countries and regions.

You can store the following time limits:

  • Expiration Period

    The expiration period indicates the maximum period of time an application and the person-related data of the associated candidate may be saved in the system once the recruitment process has been completed. The process is completed when the application status is set to rejected or withdrawn (see also Workflow After Status Changes to E-Recruiting Objects).

  • Retention Period

    The retention period indicates how long a requisition and all related information (applications, applicant data, activities, audit trails, and so on) must be retained before they can be deleted.

The time limits stored here are automatically stored by the system for the relevant requisition object or application object. In this way it is possible to take retention periods or expiration periods for these objects into account during deletion.

The system recognizes the time limits relevant for a requisition or an application based on the data that is stored for the branch assigned to the requisition. The system reads the country key and the region of the branch and searchs the expiration and retention periods stored in Customizing. If no unique entry is found for the country key and region, then a suitable entry is sought for the region and the country key using a placeholder.

Requirements

Standard settings

SAP delivers the following time limits in the standard system:

Country    Region    Time Limit Type    Time Limit

-    -    Expiration Period    12

US    -    Retention Period     12   

Activities

Example

Expiration Period

Within the jurisdiction of the European Union (EU) you must ensure that all application data and person-related data of the applicant is deleted within a given period from all systems once the recruitment process has been completed (application status rejected or withdrawn) and a certain period of time has elapsed.

In this case, you store an expiration period of 12 months for each of the EU countries where you use SAP E-Recruiting.

Retention Period

Within the jurisdiction of the United States (US) you must ensure that all requisition data and all related information is retained for a certain period of time once the recruitment process has been completed.

In this case, you store a retention period for each of the US federal states where you use SAP E-Recruiting (for example, 24 months for California).

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG RCF_LAWPERIOD 0 ALN0000022 E-Recruiting 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
T77RCF_LAWPERIOD S - Table (with text table) SM30  
History
Last changed by/on SAP  20050324 
SAP Release Created in 600