I have a client who upgraded from SL 7.0 to SL 2015 CU1 and ran into an interesting problem. When they calculated the payroll under 2015, every employee who had benefits had those benefits reset as if they were brand new benefits (whatever they had on the books was lost). They made no changes to the benefit attached to the employees. They had 3 databases and this happened in all 3. However, we caught it just before calculating in the 3rd database and made a copy of the benemp table. Upon investigation of what was going on, I determined that the records that were "trashed" all had the lastcloseddate as blank. In one of the other databases where we did not catch this, if I manually edited back in the benefit values and calculated again, that calculation did not wipe out the benefit history. During the manual entry I noticed that the screen required a date be entered into the lastcloseddate field (which seems to be a new requirement). So, in the database that we caught, I restored the benemp table and calculated and all the benefit values were cleared. I then restored the benemp table again. The restored table had the correct benefit values but the last closed date was blank on all those records. So, I ran an update query to set the lastcloseddate field to 01/01/2016 and calculated again and the benefit values were not cleared.
So, it appears that the lastcloseddate being blank is causing the calculation process to clear out the benefit records (or delete the current ones and create new ones). the questions is why is it doing this and how did the lastcloseddate field get cleared. Several of the employees are long time employees where the benefit record would have had a last closed date.