The code was set up in error as an hourly code and has been used. They want to change it to Vacation. They want to do the following. Is this all they will need to do?
In UPR40600
change the PAYTYPE from 1 to 8
change the BSPAYRCD from null to STHR
In UPR00400
change the PAYTYPE from 1 to 8
change the BSPAYRCD from null to STHR
Thanks!
*This post is locked for comments
Echoing the others, for sure, but adding that you may want to rename it to start with a "Z" zVACold - or something like that. Inactive codes can be excluded in most lookups but pushing old, unusable codes to the end of lists, this way, is helpful (in my experiences anyway).
Hi,
I couldn't agree more with Isaac. There are so many interrelated objects in payroll that I wouldn't attempt to back-end it when you have a great way to handle it through the user interface. As a last resort, SQL is often the only solution, but I would not use it for this situation.
Leslie
Hello,
I will leave this open to the community, but our recommended front end solution would be to rename the paycode from VAC to VACold or whatever you want, using the Paycode Modifier tool. Then inactivate it on employees. After that you can create a new VAC paycode since that name is now free to use and assign it appropriately.
(HR & Payroll >> Utilities >> Payroll >> Payroll Code Modifier)
As far as which tables you are updating, those are the relevant tables, but we wouldn't recommend or support updating these through SQL. You could enter a test vacation code to compare all of the values against on those two tables as well to verify if you are correct or if you need to chance any other fields.
I hope this helps!
Microsoft Support
Share
Report
All responses (
Answers (
1,456
