SAP ABAP IMG Activity OHBEN0077 (Assign Dynamic Eligibility Conditions to Date Types)
Hierarchy
☛ SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR
   ⤷ PA-BN (Application Component) Benefits
     ⤷ PBEC (Package) Benefits - Customizing
IMG Activity
ID OHBEN0077 Assign Dynamic Eligibility Conditions to Date Types  
Transaction Code S_AHR_61002222   IMG-Aktivität: OHBEN0077 
Created on 19981221    
Customizing Attributes BEN_00_AD_1_1_A0000   Administration - mandatory - critical - all countries 
Customizing Activity BEN_00_T74HF   View V_T74HF 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHBEN0077    

In this step, you define the dynamic eligibility conditions associated with the date types that you have created.

Example 1

Date type 1K is defined as 'Savings eligibility 1000 hours'.

The dynamic eligibility condition for date type 1K states the employee must work 1000 productive hours from the hire date. This condition must be checked at the end of each month until it is met by the employee.

When the Dynamic Eligibility Check report (RPUBEN47) is run, cumulation of hours takes place during the period from the hire date to the end of the last complete week within the report selection period.

The check is carried out only if the employee does not yet have a Date Specifications record (infotype 0041) with the date type 1K stored on it.

Example 2

Date type 4W is defined as 'Health eligibility 120 hours/4 weeks'.

The dynamic eligibility condition for date type 4W states the employee must work 120 productive hours in 4 weeks.

This condition must be checked at the end of each calendar week as non-compliance will lead to a loss of health plan eligibility. However, the condition is not to be checked before the end of the employee's probation period.

When the Dynamic Eligibility Check report (RPUBEN47) is run, cumulation of hours takes place over each period of four weeks that ends within the report selection period, provided the four week period does not begin before the end of the probation.

Example 3

Date type 6D is defined as '6 months dynamic'.

The dynamic eligibility condition for date type 6D states the employee must accumulate 6 months service.

When the Dynamic Eligibility Check report (RPUBEN47) is run, service is calculated place using the calculation process BNEL. The report determines length of service on the last key date of the last valuation period that falls within the report selection period.

Requirements

  • If you want to set up dynamic eligibility conditions based on length of service, you have already defined a calculation process in the Benefits IMG in the section Plans -> Saving Plans -> Retirement Plan Service.
  • You have defined any adjustment reasons that you want the system to automatically create when an employee becomes eligible (see step 5 below).

Note

Standard settings

Recommendation

Activities

Defining an Actual Hours Worked Condition

  1. Specify that you want to determine dynamic eligibility on the basis of actual hours worked.
  2. Enter the date type for which you are defining conditions.
  3. Specify the number of actual hours that are required and the relevant time type.

In the next steps, you set up parameters that determine how the Dynamic Eligibility Check report (RPUBEN47) functions.

  1. Select a Period to determine the key date(s) for data evaluation during a report run.

    Data is evaluated on the last day of the selected period for all periods other than Days. Depending on the report selection period, cumulated data may be evaluated on more than one key date.

  2. If required, specify an adjustment reason associated with the eligibility condition.

    Enter an adjustment reason if you want a corresponding Adjustment Reason record (infotype 0378) to be automatically created once an employee fulfills the condition. An adjustment reason then appears in Enrollment to indicate that the employee can be enrolled in the relevant plan.

  3. Define the period over which daily time balances are to be cumulated and evaluated.
    1. Select Employment period if you want to evaluate data cumulated from an employee's hire date.
      2. This option is appropriate if the conditions that you specify define a waiting period (in this case, the condition must only be fulfilled once).
    2. Select In period and specify a period if you want to evaluate data cumulated within a specific period.
      3. This option is appropriate if the conditions that you specify define minimum working time requirements (in this case, the condition must be continuously fulfilled).
  4. If you only want the eligibility condition to be checked as of a certain date, specify an earliest start date for the evaluation by entering a date type (for example, end of probation period).

    An employee must have a Monitoring of Dates record (infotype 0019) with this date type before his actual hours are checked.

  5. Determine how the report proceeds for employees who already have a Date Specification record (infotype 0041) with the date type in question:
    1. Select On every evaluation key date if you want the conditions to be checked and the infotype delimited if the employee is no longer eligible. This is the case if you use the condition to define a minimum number of actual hours to be worked over a period of time.
    2. Select Only check if not fulfilled if you want no changes to be made to the infotype once the conditions are fulfilled. This is the case if you use the condition to define a waiting period.

Defining a Length of Service Condition

  1. Specify that you want to determine dynamic eligibility on the basis of length of service.
  2. Enter the date type for which you are defining conditions.
  3. Define the calculation of the required length of service
    1. Specify the required length of service itself.
    2. Specify a calculation process that you have already set up for determining length of service.
    3. Specify the plan to which the condition relates.
      4. You must enter a plan here if the calculation process that you are using determines length of service using the hours-counting method. For this method, hours are cumulated using a separate compensation wage type for each plan, and are subsequently stored on plan-specific Retirement Plan Cumulations record (infotype 0602).
      The system must, therefore, know from which record it should read hours in order to determine whether the eligibility condition is fulfilled.

  4. Select a Period to determine the key date(s) for data evaluation during a report run.

    Data is evaluated on the last day of the selected period for all periods other than Days. Depending on the report selection period, cumulated data may be evaluated on more than one key date.

  5. If required, specify an adjustment reason associated with the eligibility condition.

    Enter an adjustment reason if you want a corresponding Adjustment Reason record (infotype 0378) to be automatically created once an employee fulfills the condition. An adjustment reason then appears in Enrollment to indicate that the employee can be enrolled in the relevant plan.


Further notes

For more information on how definition of the dynamic eligibility condition is taken into account when the Dynamic Eligibility Check is run, see the SAP Library (Human Resources -> Personnel Management -> Benefits Administration (PA-BN) -> Benefits Administration -> Dynamic Eligibility Check).

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency I   Valid for countries specified 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHBEN0077 0 HLA0006759 Administration 
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
V_T74HF V - View HRBEN0041  
History
Last changed by/on SAP  20000117 
SAP Release Created in