CC:Rakesh Roy,Samir,Hrishikesh Deshpande,Jyoti Mayne

Hi Jyoti,

As discussed, let's check this issue on priority today.

Regards,
Satya Prakash

Cc: Mandar Kulkarni Samir Vijay Siddha Rakesh Roy

Hi Debbie Kulling,

Please refer following 3'c of this issue:-

Concern: JCCC spending credit allotted is doubling on production.
Cause: This issue occurred because of garbage data in CreditPool_Cashout table.
For example:-
Employee Name:- Gerald Zimmerman
Spending Credit Allotted = Spending Credits Applied + Spending Credits Remaining
= 554.47 + 554.47 = 1108.94

Effective Date of Spending Credits Remaining is '01/01/1900' because of this garbage effective date system calculating remaining credits even employee used whole credits.

We have scanned JCCC client for this issue and found 128 employees impacted by this issue. Please refer attached excel sheet for more details. JCCC_Impacted_Employees.xls

Correction:
Regarding code fix:- We are in-process to fix this issue and as soon as possible we fixed this issue.
Regarding data correction:- For now we have corrected data for impacted employees. Please verify same at your end and let us know in case of any issue/concern.

PLEASE DO NOT RECALCULATED CREDIT POOL using SA utility until this issue fixed on production.

Thanks,
Avnish Y

CC- Jyoti Mayne,Satya,Samir,Vijay Siddha

Hi Alankar Chavan,

Please find 3Cs in recent comment from Avnish Yadav, also find below impacted scenarios of the same :
1. 'Apply Excess Credits' - NO and only flex is selected in 'Benefit Type Mapping'.
2. 'Apply Excess Credits' - NO and other benefit types selection in 'Benefit Type Mapping'.
3. 'Apply Excess Credits' - NO and other benefit types selected with flex in 'Benefit Type Mapping'.
4. All above settings of 'Benefit Type Mapping' with 'Apply Excess Credits' - YES

Thanks and Regards,
:: Umesh Kadam

CC : Jyoti Mayne

Hello Umesh Kadam,

As per your mentioned impacted area and problem description, we reproduced this issue first on stage to get the exact steps we should be performed to test this fix & performed below tests on LB - Fix is Working Well

• On JCCC LB - employee did his enrollments. We recalculated the credits when there was an amount in Remaining Credits. Credit Pool amounts were correct. CashOut Effective Dates were right too (not older ones) - we tested this for current enrollments
• On JCCC LB - employee did his enrollments. We recalculated the credits when there was no available amount in Remaining Credits. Credit Pool amounts were correct. CashOut Effective Dates were right too (not older ones) - we tested this for current enrollments
• On JCCC LB - employee did his enrollments. We recalculated the credits when there was no available amount in Remaining Credits. Credit Pool amounts were correct. CashOut Effective Dates were right too (not older ones) - we tested this for future enrollments
• On JCCC LB - employee did his enrollments. We recalculated the credits when there was an amount in Remaining Credits. Credit Pool amounts were correct. CashOut Effective Dates were right too (not older ones) - we tested this for future enrollments
• We tested above scenarios with Apply Excess Credits as NO
• We tested above scenarios with Apply Excess Credits as Yes [Flex plans in Excess Credits and Non Flex Plans in Mapped Types]
• We tested above scenarios with Apply Excess Credits as Yes [Non Flex plans in Excess Credits and Flex Plans in Mapped Types]
• We tested above scenarios with Apply Excess Credits as Yes [Flex plans in Excess Credits and Non Flex + Flex Plans in Mapped Types]

Ready for Stage

CC - Prasad Pise Sachin Hingole Hrishikesh Deshpande Rakesh Roy Jyoti Mayne

Hi all - are we going to be able to get this to Stage, tested and then to Production ASAP? The Broker and Client are pretty upset by this issue so if we can take this on priority, I would appreciate it.

FYI -
Kira Hamilton
[~chimane@ebsbenefits.com]

Did basis scenario and it seems to be fine as no cost is getting doubled. Will push this production @ 2 May.

Please confirm that this was pushed to production

Hello Debbie Kulling,

We have moved this fix to production and tested the above listed scenarios - this is working as per the expectations.
We won't be facing the credit pool amounts doubling issue henceforth.

Hello Jyoti Mayne,

I tried fetching few employee's record through database whether any of them having older effective date in creditpool_cashout table. I found near about 50 such employees.
When I went on thier confirmation statement - their credit pool amounts are still Double. Ideally this problem should get fixed now with Credit Recalculations if I am not wrong.

Can you proceed further with the corrective actions which will remove these double costs with existing employees on Production and Stage (if any) & update the status ?

CC - Umesh Kadam Prasad Pise Sachin Hingole Hrishikesh Deshpande Rakesh Roy Satya

Hi Alankar Chavan,

We have scanned affected employees in Production and found 13 employee (list given below). We have re-calculated their credit pool and their confirmation statement is looking correct now. Please check and confirm.

Thanks and Regards,
:: Umesh Kadam

CC : Debbie Kulling, Jyoti Mayne

Hi Alankar Chavan,

We have scanned affected employees in Stage and re-calculated credit pools for them as well. Please check and confirm.

Thanks and Regards,
:: Umesh Kadam

CC : Debbie Kulling, Jyoti Mayne

Hello Umesh Kadam,

We have again verified few employees in order to test the double credit pool amounts issue on Stage and Production
Issue is resolved now. The effective dates in creditpool_cashout tables are correct also.

Hello Debbie Kulling,

This fix is deployed & tested on Stage and Production. You may review this at your end once and close the JIRA if everything working as per your expectations.

CC - Jyoti Mayne Prasad Pise Rakesh Roy Hrishikesh Deshpande