Search This Blog

Thursday, February 14, 2013

When Processing a New Hire Life Event, Automatic Plans Are Not Assigned - Oracle Advanced Benefits(OAB)

Symptoms
 Find that after running the New Hire life event the Automatic plans are not assigned to the employee.
 EXPECTED BEHAVIOR

Expect that after running the New Hire life event, employees are automatically enrolled in the plans with Automatic Enrollment Method.

Steps To Reproduce:
 The issue can be reproduced at will with the following steps:
 1. Login to HRMS Manager Responsibility.
 2. Process a New Hire life event for an employee. Automatic plans are not assigned.

 Cause
 The issue is caused by the following setup: Automatic Enrollment settings for the Plans.
 The setup causes the issue because correct Enrollment code was not used.
Solution
 To implement the solution, please execute the following steps:
 1. Go into the responsibility HRMS Manager Responsibility.
 2. Navigate to Total Compensation > Plans and Programs > Plan Enrollment Requirements form and confirm the following settings:
General tab > Plan tab:
Method = BLANK
General tab > Plan tab:
Enrollment Code = BLANK
Life Event tab > Option tab > Enrollment drop down:
Life Event = New Hire
Option = Enrolled
Enrollment Code = Current Nothing; New Assign (Automatic)
Automatic Enrollment Flag = NOT CHECKED
01-Oct-2006 to EOD
Option = Enrolled
Enrollment Code = Current Nothing; New Assign (Automatic)
Automatic Enrollment Flag = CHECKED
01-Jan-1965 to 31-Sep-2006
Option = Enrolled01Oct2006
Enrollment Code = Current Nothing; New Assign (Automatic)
Automatic Enrollment Flag = CHECKED
01-Oct-2006 to EOD
Option = Contribute
Enrollment Code = Current, Can Keep or Choose; New, Can Choose
Automatic Enrollment Flag = NOT CHECKED
01-Jan-65 to EOD
 Option = Contribute01oct2006
 Enrollment Code = Current, Can Keep or Choose; New, Can Choose
 Automatic Enrollment Flag = NOT CHECKED
 01-Oct-2006 to EOD
 Option = Waive
 Enrollment Code = Current, Can Keep or Choose; New, Can Choose
 Automatic Enrollment Flag = NOT CHECKED
 01-Jan-1965 to EOD
 4. Retest the issue.
 5. Migrate the solution as appropriate to other environments.

No comments:

Post a Comment