This page (revision-6) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
6 26-Nov-2021 10:22 4 KB kparrott to previous
5 26-Nov-2021 10:22 4 KB JMyers to previous | to last
4 26-Nov-2021 10:22 5 KB JEscott to previous | to last
3 26-Nov-2021 10:22 5 KB JEscott to previous | to last
2 26-Nov-2021 10:22 5 KB JEscott to previous | to last
1 26-Nov-2021 10:22 5 KB JEscott to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 12 changed one line
Pay Point Tasks are assigned to pay point types. A task may be an [{$applicationname}] logic routine (Legislative Calculations) or may be a user assigned routine (User Calculations, Benefit Plans,or Attendance Policies).
Pay Point Tasks are assigned to pay point types. A task may be an Personality logic routine (Legislative Calculations) or may be a user assigned routine (User Calculations, Benefit Plans,or Attendance Policies).
At line 68 removed 2 lines
;[User Calc Code|USER_CALC_CODE]:This field triggers the UserCalc indicated. The UserCalc code may be used for all pay point types.
At line 70 added one line
;[User Calc Code|USER_CALC_CODE]:This field triggers the UserCalc indicated. The UserCalc code may be used for all pay point types.
At line 72 added 2 lines
;[Override Trace Level|TRACE_LEVEL]:This field will be read and used to trace all employees of a Payrun for this Pay Point Task when UPCALC is run with Exception Level = 0