KB 93052 Fixed on Payroll Update 2.18.4.0.  Should be in the read-me notes.  This was a conversion issue so the fix was in the conversion program.  In order to get the prior years history fixed, you would need to perform a new migration/conversion. The prior year-to-date history is does have the correct value and this does not affect current year data.  We are aware that this affected only Prior year Earnings and Deductions quarters.   I have not heard anything about the Benefits as that does not store data by quarters.  Please let me know if I have missed something.

KB 93052 Fixed on Payroll Update 2.18.4.0.  Should be in the read-me notes.  This was a conversion issue so the fix was in the conversion program.  In order to get the prior years history fixed, you would need to perform a new migration/conversion. The prior year-to-date history is does have the correct value and this does not affect current year data.  We are aware that this affected only Prior year Earnings and Deductions quarters.   I have not heard anything about the Benefits as that does not store data by quarters.  Please let me know if I have missed something.

So if they are live onv2018 pu4 and have the issue. I need to migrate the same data and then convert it even though it’s on the same version?? 

If they are live on version 2018, I would NOT recommend to remigrate and convert the data again.  This would wipe out the data that was updated after going live on version 2018.  The best solution I have for fixing the prior year data WITHOUT disturbing new current year data entered on version 2018, is to edit the data files to put in the correct periods which would be a large task.  We did request a utility to fix the existing data in this situation but it was determined using resources on current projects would be a greater value.  We weren't sure this could be done with a utility which also would have taken some time.  This only affected prior year quarter data which the ytd was correct.  The problem is the conversion used the current period to populate the data and it should have populated Qtr 4 and the YTD - Qtr 4 would have gone into Qtr 3.   That change would not provide much benefit.  It did not affect the current year data.

Thank you for the clarification.   I have a test environment for we are reviewing tomorrow.  I’ll try migrating and converting again for them    As for live v2018   I thought about going through dfdm but that is a huge project and I doubt clients would want to pay for it   

You did understand why I said I would NOT remigrate???

It’s a test environment.  I have to re migrate no matter what. 

Yes I understood!  Live environment nothing can be done it sounds like.   But a test environment requires another migration.   

 Good Morning!  I am trying to get some direction on this issue.  I have a test environment on PU3 and 2.18.3.   I can uninstall and reinstall to PU4 and see if I experience the same results and report back to you.  Can we take this offline?  I have two other clients that has the issue with tips taxes reporting to the correct departments that was supposed to have been fixed in PU4. They are both on  PU1 and they do not have the issue on the earnings tab or benefit tab.  I can not upgrade them to  PU 4 to fix one thing and break another.  Please provide some direction. 

my mistake i have been doing so many upgrades my test environment for the client is pu4 and 2.18.4.  still has the earning and deduction issue in employee maintenance.  I am happy to say benefits came over correctly!!

I won't have time today to do this but I can reach out to you next week.  Please private message me with your contact and a best time to reach you.    Thanks

???  I noted that this fix was supposed to be effective for 2.18.4,  but I'm still seeing the issue with clients converting using 2.19..0.