-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Module:BenAdmin - Enrollment
-
Reported by:Harbinger
-
Item State:Production QA - Production Deployed
-
Issue Importance:Must Have
Customization: HRA is force contingent on Medical plan.
1. Employee is enrolled in Medical plan with effective date 01/01/2016 and due to forced contingency, EE got election and rate in HRA plan with 01/01/2016. Termination date for both election is NULL.
2. QE is raised with Effective date 07/01/2016.
3. Employee is enrolled in Medical plan with effective date 07/01/2016 and different health tier.
4. Admin approve's enrollment from Pending queue.
5. Ideally, Medical and HRA enrollments should terminate with termination date 06/30/2016 and with proper Qualifying event. As well as EE should get enrolled in Medical and HRA plan with effective date '07/01/2016'.
And we are getting correct qualifying event for enrollment effective from '07/01/2016', but for terminated enrollments NULL value is inserted in DB for Qualifying event ID.
- relates to
-
-
- Closed
-
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Vijay Siddha [ vijays ] | Abhijeet Khandagale [ abhijeet.khandagale ] |
| Status | Open [ 1 ] | In Development [ 10007 ] |
| Description |
Customization: HRA is force contingent on Medical plan. 1. Employee is enrolled in Medical plan with effective date 01/01/2016 and due to forced contingency, EE got election and rate in HRA plan with 01/01/2016. Termination date for both election is NULL. 2. QE is raised with Effective date 07/01/2016. 3. Employee is enrolled in Medical plan with effective date 07/01/2016 and different health tier. 4. Admin approve's enrollment from Pending queue. 5. Ideally, Medical and HRA enrollments should terminate with termination date 06/30/2016 and with proper Qualifying event. As well as EE should get enrolled in Medical and HRA plan with effective date '07/01/2016'. And we are getting |
| Description |
Customization: HRA is force contingent on Medical plan. 1. Employee is enrolled in Medical plan with effective date 01/01/2016 and due to forced contingency, EE got election and rate in HRA plan with 01/01/2016. Termination date for both election is NULL. 2. QE is raised with Effective date 07/01/2016. 3. Employee is enrolled in Medical plan with effective date 07/01/2016 and different health tier. 4. Admin approve's enrollment from Pending queue. 5. Ideally, Medical and HRA enrollments should terminate with termination date 06/30/2016 and with proper Qualifying event. As well as EE should get enrolled in Medical and HRA plan with effective date '07/01/2016'. And we are getting |
Customization: HRA is force contingent on Medical plan. 1. Employee is enrolled in Medical plan with effective date 01/01/2016 and due to forced contingency, EE got election and rate in HRA plan with 01/01/2016. Termination date for both election is NULL. 2. QE is raised with Effective date 07/01/2016. 3. Employee is enrolled in Medical plan with effective date 07/01/2016 and different health tier. 4. Admin approve's enrollment from Pending queue. 5. Ideally, Medical and HRA enrollments should terminate with termination date 06/30/2016 and with proper Qualifying event. As well as EE should get enrolled in Medical and HRA plan with effective date '07/01/2016'. And we are getting correct qualifying event for enrollment effective from '07/01/2016', but for terminated enrollments NULL value is inserted in DB for Qualifying event ID. |
| Item State | Parent values: Development(10200)Level 1 values: In Progress(10206) | Parent values: LB QA(10201) |
| Assignee | Abhijeet Khandagale [ abhijeet.khandagale ] | Aniruddha Dev [ aniruddha.dev ] |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
| Item State | Parent values: LB QA(10201) | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) |
related ticket to WT-1763 "Must Have" so making issue importance as "Must Have"
Vijay Siddha (Inactive)
added a comment - - edited related ticket to WT-1763 "Must Have" so making issue importance as "Must Have" Vijay Siddha (Inactive)
made changes -
| Issue Importance | Must Have [ 11800 ] |
Marking this as ready for stage as there are errors on script execution on UND for Banner Payroll testing on LB so this patch will be tested directly on Stage.
| Item State | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) |
| Item State | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) | Parent values: Stage QA(10202)Level 1 values: In Testing(10214) |
We got this company on stage at 5:50 PM today. We will continue our testing on Monday
| Status | Local Testing [ 10200 ] | Stage Testing [ 10201 ] |
| Component/s | BenAdmin [ 10000 ] | |
| Production Due Date | 05/Jul/2016 | |
| Stage Due Date | 1/Jul/16 [ 2016-07-01 ] |
Verified the fix on stage on UND banner payroll Test company . Proper QE codes for all plans (including for force contingent plans ) along with Qualifying event dates are getting exported on the file for Termination as well as for active records.
Working as expected on Stage
Ready for Production
| Item State | Parent values: Stage QA(10202)Level 1 values: In Testing(10214) | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) |
| Developer | Abhijeet Khandagale [ abhijeet.khandagale ] |
| Item State | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) | Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) |
Sachin Hingole (Inactive)
made changes -
| Issue Category | EBS [ 10350 ] | Harbinger [ 10700 ] |
Verified the fix on Production on UND For Banner Payroll Testing for HSPL company on Production for QE-married scenario. which is working as expected.
Observed one issue as below for another record exported on file other than my scenario.
Issue on file : When Group file is exported found one record for HRB (2016 Health Reimbursement Account) for an Employee which have BLANK QE Code and QE Date on the file.
Description:
Employee has changed Child's status from 'Active' to 'Deceased' on 06/16/2016 due to this High Deductible Heath Plan CHA got terminated on 6/30/2016 and Continued from 07/01/2016 with another child.
now the above mentioned Heath Plan CHA is force contingent on '2016 Health Reimbursement Account - Family - Prior to 7/1' .
Can you please check why the QE date did not appear on the file.? Please find attached screenshot for your reference.
(Note: QE Code for Employee Data Change is Configured as Blank on template so it will export as blank. But QE date should be exported on the file )
Below are the employee Details
Employee Name : Carolyn M Stohler
Company Name: UND for Banner Payroll Testing
Please let us know if any code change is required for this so that I'll create another JIRA for the same
CC: Rohan J Khandave Ganesh Sadawarte Hrishikesh Deshpande Vinayak Kulkarni Jyoti Mayne
| Assignee | Aniruddha Dev [ aniruddha.dev ] | Abhijeet Khandagale [ abhijeet.khandagale ] |
| Attachment | Employee_History.JPG [ 21314 ] |
Hi Rohan J Khandave,
Could you please check whether is breaking because of my code changes? I don't have much knowledge of Export functionality.
CC: Jyoti Mayne Vinayak Kulkarni Ganesh Sadawarte Aniruddha Dev
| Assignee | Abhijeet Khandagale [ abhijeet.khandagale ] | Rohan Khandave [ rohan.khandave ] |
Hello Aniruddha Dev,
We checked from back end enrollment of plan "2016 Health Reimbursement Account - Family - Prior to 7/1" added on 03/18 by "Admin Change" qualifying event.
But in "RaisedQualifyingEvent" table only one entry exists for this employee on date "06/17/2016" of qualifying event "Death" and no entry for "Admin Change". Due to this in-consistent data blank QE date exported on file.
CC – Abhijeet Khandagale Jyoti Mayne Vinayak Kulkarni Ganesh Sadawarte
| Assignee | Rohan Khandave [ rohan.khandave ] | Aniruddha Dev [ aniruddha.dev ] |
| Status | Stage Testing [ 10201 ] | Production Testing [ 10202 ] |
Closing this JIRA as above mentioned scenario is not an issue and it is due to Inconsistent Data . The fix is working as expected
| Resolution | Fixed [ 1 ] | |
| Status | Production Testing [ 10202 ] | Production Complete [ 10028 ] |
| Status | Production Complete [ 10028 ] | Closed [ 6 ] |
| Transition | Time In Source Status | Execution Times |
|---|
|
4m 54s | 1 |
|
5d 15h 35m | 1 |
|
5d 34m | 1 |
|
9d 8h 4m | 1 |
|
14s | 1 |
|
5s | 1 |
Please find 3C's of mentioned issue below,
Concern: Qualifying event is not getting saved after termination of forced contingent plan election.
Cause: In business logic, as per current logic, we are not getting Qualifying event ID passed in a function where enrollment
is terminated. And in this function default value of Qualifying Event id is 0. Because of which, QE is not getting saved.
Correction: We have made code changes in Business logic so that we can get correct Qualifing ID passed to a function where enrollment
is terminated. We are testing this changed functionality on local environment.
We will move this on LB after testing.