Verified on Production Environment consider below scenarios:
1]Insert Sub rate through Back end
2]Try to add same rate on UI Getting validation message
3]added Different sub-rate with Different age range.
4]Added sub-rate with different coverage amount
5]If truing to add with same coverage amount it is showing validation message.
6]Also check with same scenario for which issue is getting reproduced.
a] Enrolled employee
b] change sub-rate
c] recalculate sub-rate
d] finalize invoice
try to add new sub rate and update existent one getting validation message
no duplicate entry for sub-rate on Ui and database also.
Working fine as expected

Verified on Stage Environment consider below scenarios:
1]Insert Sub rate through Back end
2]Try to add same rate on UI Getting validation message
3]added Different sub-rate with Different age range.
4]Added sub-rate with different coverage amount
5]If truing to add with same coverage amount it is showing validation message.
6]Also check with same scenario for which issue is getting reproduced.
a] Enrolled employee
b] change sub-rate
c] recalculate sub-rate
d] finalize invoice
try to add new sub rate and update existent one getting validation message
no duplicate entry for sub-rate on Ui and database also.

Working fine as expected

Verified on LB Environment consider below scenarios:

1]Insert Sub rate through Back end
2]Try to add same rate on UI Getting validation message
3]added Different sub-rate with Different age range.
4]Added sub-rate with different coverage amount
5]If truing to add with same coverage amount it is showing validation message.

6]Also check with same scenario for which issue is getting reproduced.
a] Enrolled employee
b] change sub-rate
c] recalculate sub-rate
d] finalize invoice
try to add new sub rate and update existent one getting validation message
no duplicate entry for sub-rate on Ui and database also.

I have deleted the duplicate subrates for Sutter and Quincy. I will forward the action item for the other two groups to the account manager.

Hi Debbie Kulling,

We have resolved this issue today by adding a precautionary check at database level. This will enforce NOT to let any duplicate Age Band entry inserted in database.

This fix is currently in QA Testing at local environment, and we will be deploying this to Stage & Production by tomorrow (05/12).

Action Item: On Production we observed that duplicate entry has been removed from County of Sutter, however can you please correct duplicate entry on above mentioned 4 companies at production. After deploying this patch, system wouldn't allow any duplicate entry, but for 4 stage companies it needs to be corrected.

Regards,
Satya Prakash

Cc: Jyoti Mayne Vijay Siddha Rakesh Roy Samir