Hi Jeshurun Harris,

We have investigated on your request of deletion of the 18 classes and observed that there are still 11 employees with active status which have the class value in classes given for deletion. Please find the attached sheet for information on those active employees. Password will be sent in an another mail. Also note that deleting these 18 classes would affect the Subrates,PayrollSchedule,Adminusers tables. If you want us to delete these classes please provide us which class1 value should be saved for the 211 employees belonging to this class.

Thanks,
Venkatesh

Hi Venkatesh:

I'm checking on the 11 active enrollments. I will get back to you.
Thanks!!

Kiyo

Hi Venkatesh:
The client has moved all of the active records from the divisions that they were requesting to move.
Can you please check to see if we can now remove the divisions? Also, so even though the records are moved, you still show past records of employees in these divisions that have to be reassigned to another class 1 value correct? Help me understand that process to I can discuss with the client
Thanks!!

Kiyo

Yes, unless and until we have those class 1 values assigned someone, we can not delete them from system. This means, if a employees is belongs to the class 1, that we want to delete in past, we have to correct the past records also for this employee.
secondly, we have to make sure that all those eligibility rules using class 1 that needs to be deleted, should be replaced by the value that we are going to used as replacement value, otherwise, it will result in unnecessary loss of coverage.

Hi Kiyo Takahashi,

consider below scenario,

Employee is in system effective from 01/01/2015 with class 1 say A. Now, we change his class 1 from A to B effective from 01/01/2017. So employee will be having class 1 B, but employee history records are having old records where employee belongs to A. If we try to delete A, we are not allowed to do so, as though employee belongs to B, but in history he was belongs to A and that records are still present in database. For this, A either need to be replaced by NULL or B from day one the employee has been present in system.

Hi Jaideep:

I understand. I will contact the client.
Thanks!!

Kiyo

From: Jaideep Vinchurkar (JIRA) jira@workterra.atlassian.net
Sent: Wednesday, November 23, 2016 12:13 AM
To: Kiyo Takahashi <kiyo.takahashi@ebsbenefits.com>
Subject: [JIRA] (WT-6128) Removal of Old Classes

[cid:image001.png@01D24529.EB9630B0]

Jaideep Vinchurkar<https://workterra.atlassian.net/secure/ViewProfile.jspa?name=jaideep.vinchurkar> commented on [Support Activity] WT-6128<https://workterra.atlassian.net/browse/WT-6128>

Re: Removal of Old Classes <https://workterra.atlassian.net/browse/WT-6128>

Hi Kiyo Takahashi<https://workterra.atlassian.net/secure/ViewProfile.jspa?name=ktak>,

consider below scenario,

Employee is in system effective from 01/01/2015 with class 1 say A. Now, we change his class 1 from A to B effective from 01/01/2017. So employee will be having class 1 B, but employee history records are having old records where employee belongs to A. If we try to delete A, we are not allowed to do so, as though employee belongs to B, but in history he was belongs to A and that records are still present in database. For this, A either need to be replaced by NULL or B from day one the employee has been present in system.

[Add Comment]<https://workterra.atlassian.net/browse/WT-6128#add-comment>

Add Comment<https://workterra.atlassian.net/browse/WT-6128#add-comment>

This message was sent by Atlassian JIRA (v1000.552.6#100018-sha1:e2f2197)

[Atlassian logo]

Kiyo Takahashi Is this pending?

New ticket created per client additional needs.