SAP ABAP IMG Activity OHFBNESS01 (Define Date Type for Data Analysis in Enrolment Reminder Report (FLEX))
Hierarchy
☛ EA-HRCGB (Software Component) Sub component EA-HRCGB of EA-HR
   ⤷ PA-BN-FB-XX (Application Component) General Parts
     ⤷ PAOC_BEN_FBN (Package) Flexible Benefits System
IMG Activity
ID OHFBNESS01 Define Date Type for Data Analysis in Enrolment Reminder Report (FLEX)  
Transaction Code S_P2H_60000039   (empty) 
Created on 20040202    
Customizing Attributes OHFBNESS01   Define Date Type for Data Analysis in Enrolment Reminder Report (FLEX) 
Customizing Activity OHFBNESS01   Define Date Type for Data Analysis in Enrolment Reminder Report (FLEX) 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHFBNESS01    

Define Date Type for Data Analysis in Employee Enrolment Reminder Report (FLEX)

Use

In this step you configure which date types you use to record two key dates used in the GB Flexible Benefits report Employee Enrolment Reminder Report (RPUFBNREMIND)These dates are:

  • The date that an employee accessed Employee Self-Service (ESS) enrolment without submitting their Flexible Benefits selections ("logon" date).
  • The date that the employee actually submitted their flexible benefits selections ("submit" date).

For each participating employee, these two dates are recorded in their infotype Date Specifications (0041) record with your selected date type.

When an employee runs the ESS enrolment scenario, the Flexible Benefits system records these two key dates in infotype 0041 separately. Therefore, this infotype can be read for any dates where the employee logged on to an enrolment session without making a selection, and for the date when an employee actually submitted his or her benefit plans selections.

These dates are read by report RPUFBNREMIND. The Benefits Administrator can then run this report at any point in time during the annual (open) enrolment period to:

  1. Generate data on the following:
    1. Numbers of eligible employees for specific benefits plans
    2. How many employees have logged onto ESS, but have not yet actually enroled in any benefits plans ("logon" date)
      3. Note:
      For any given selection period, the report provides the latest date in the period when an employee logged on without selecting benefits, if he or she has made multiple logins during the period upon which the report is generating data.
    3. How many employees have actually enroled their benefits choices for the upcoming benefits year ("submit" date)
    4. Employees who have yet to enrol in specific plans
  2. Send reminder e-mails to those employees who are eligible to enrol in at least one benefits plan but have not as yet enroled.

For example, report RPUFBNREMIND is run mid-way through the annual enrolment period. The Benefits Administrator produces data showing that out of 1000 eligible employees, 600 have logged onto ESS. Of this 600, only 250 have actually enroled some plans at that point in time.

Reminder e-mails are then generated by the report and sent to the remaining 750 employees who have yet to enrol any plans.

Prerequisites

You must have previously also maintained the "logon" and "submit" date types in the Personnel Administration IMG, under: Evaluation Basis -> Date Specifications -> Define Date Type.

Activities

  1. Execute this IMG activity.

    For each of your Benefit Areas, each adjustment reason contained in this customising table has the corresponding fields Logon Date type and Submit Date type in the right-hand column.

  2. Select a Benefit Area, and for each adjustment reason assigned to that Benefit Area, maintain your required date type in the fields Logon Date type and Submit Date type.
  3. Repeat Step 2 for each of your Benefits Areas.
  4. Save your entries.

    The system will update the employee's infotype 0041 record according to the two date type settings you have maintained in this step.

Example

In your organisation, for Benefit Area G1, there is only one "Annual Enrolment" adjustment reason assigned. In this, and in the previous IMG step described above, you have maintained the "logon" date with type "LO" and the "submit date" with type "SM". In this example, the date DD/MM/XXXX is used, where XXXX represents the current benefits year.

  1. On 01/03/XXXX, a female employee runs ESS Flexible Benefits enrolment using the adjustment reason "Annual Enrolment". She views the Flexible Benefit plans available to her in the upcoming benefits year, but does not make any selections. As a result, her infotype 0041 record stores the date 01/03/XXXX marked as "LO", to signify she has used ESS enrolment on this date, but made no selections.
  2. On 03/03/XXXX, she re-enters ESS, and again views her options but does not make any selections. As a result, her infotype 0041 record is updated and the date 03/03/XXXX marked as "LO", to signify the latest occasion when she used ESS enrolment, but made no selections.
  3. Finally, on 05/03/XXXX, she enters ESS and actually submits her benefits selections. Her infotype 0041 record is now updated to store the date 05/03/XXXX with the date type "SM". Infotype 0041 is also updated to store the date 05/03/XXXX marked with the date type "LO".
  4. On 08/03/XXXX, the Benefits Administrator runs the Flexible Benefits report RPUFBNREMIND for the period 01/03/XXXX to 08/03/XXXX. The data produced by the report for this employee, relating to enrolment status, is:
    1. Date type "LO" : 05/03/XXXX
    2. Date type "SM" : 05/03/XXXX

Business Attributes
ASAP Roadmap ID 207   Establish Reporting 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
OHFBNESS01 GB United Kingdom
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHFBNESS01 0 PLN0000014 Great Britain 
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_T74_FBN10_ESS1 V - View SM30  
History
Last changed by/on SAP  20040625 
SAP Release Created in 200