You’re offline. This is a read only version of the page.
5
When running the Mandatory Arrears process for selected Audit Trail Codes, we are receiving duplicate rows of same deduction codes. Same deduction code appears two or more times with same rate. Also, some rows appear twice for same deduction code with different rates (rate for two pays of year and new rate updated pay period 3). This issue makes using the Post feature unmanageable due to the volume to scroll thru of duplicated rows. Did something change with GP18 that put this window out of sync? Thanks for any feedback or advice if anyone else has seen this happen.
Hi,
Currently, there are no known Quality Issues around what you’re seeing (duplicated records per employee in the Mandatory Arrears window). I double checked to be sure and tested mandatory arrears on version 18.2.1060 and I cannot replicate what you’re seeing. We haven't heard of others experiencing this either.
We did have an issue early on in GP 2018 in which the APR_APR30300 table would not get updated when a pay run was posted (when Advanced Payroll was not marked as registered). However, this resulted in the opposite of what you are experiencing - in that no records would be available to be posted as arrears in the Mandatory Arrears window. This issue was fixed with the release of version 18.00.0672.
When I see the duplication in your screenshot, it makes me wonder if there may be duplication elsewhere in the payroll tables. If there was a posting interruption during the payroll posting process and duplication occurred as a result, that could cause something similar in the Mandatory Arrears window. Have you had any problems/errors with payroll posting?
Can you actively replicate the problem? If you post a new pay run for one of the employees, do you see duplication for that arrear in the Mandatory Arrears window?
All in all, I would have to take a closer look at your system (data, steps being taken) to determine what is causing the problem. Our support team would be happy to help you dig into this further via a support case (as again, we’d really need to take a look at the data along with the steps being taken):
Others in the community may have more to offer as well.
Hope this helps!
Thank you for using Dynamics Communities,
Andrea Melroe | Sr. Technical Advisor | Microsoft Dynamics GP
Share
Report
All responses (
Answers (
