TSA Set Up Roll Down Bug

A client recently asked us if it was ok to change the TSA setting on a deduction code that had history. Two of our seasoned Payroll consultants both said “no”, and that if there is history no change can be made in GP to deduction codes with history.

The client changed the TSA flag with their setup and rolled down the setting change from the deduction code setup window and the TSA change was reflected in the employee’s next check. The new TSA setting does not reflect properly in the Employee Deduction Maintenance window.

The screen shots below show the impact to changing the TSA settings at the setup level of a deduction reflecting that is does unmark the TXSHANTY field in the database while leaving the checkboxes marked on the employee deduction card.

Employee deduction card and the SQL query after rolling down the change at the setup level:

TSAblog1

(Click on image to view larger).

TSAblog2

The situation was reported to Microsoft and they have provided workaround scripts until a fix can be included in a service pack for GP2010 and GP2013.

UPDATE UPR00500 SET TXSHANTY = 0 WHERE SFRFEDTX + SHFRFICA + SHFRSTTX + SFRLCLTX = 0 UPDATE UPR00500 SET TXSHANTY = 1 WHERE SFRFEDTX + SHFRFICA + SHFRSTTX + SFRLCLTX > 0 UPDATE UPR00600 SET TAXABLE = 0 WHERE SBJTFDTX + SBJTSSEC + SBJTMCAR + SBJTSTTX + SBJTLTAX + SBJTFUTA + SBJTSUTA = 0 UPDATE UPR00600 SET TAXABLE = 1 WHERE SBJTFDTX + SBJTSSEC + SBJTMCAR + SBJTSTTX + SBJTLTAX + SBJTFUTA + SBJTSUTA > 0

To learn more about Microsoft Dynamics GP and other business solutions offered by InterDyn BMI click here or contact us.

Advertisements