This page (revision-8) 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
8 26-Nov-2021 10:22 5 KB kparrott to previous
7 26-Nov-2021 10:22 5 KB kparrott to previous | to last
6 26-Nov-2021 10:22 5 KB kparrott to previous | to last
5 26-Nov-2021 10:22 5 KB kparrott to previous | to last
4 26-Nov-2021 10:22 5 KB kparrott 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 4 KB JEscott to last

Page References

Incoming links Outgoing links
UPRETRO
UPRETRO

Version management

Difference between version and

At line 16 changed one line
|Entity|Mandatory, LOV Available \\Payroll Mandatory, LOV Available
|Entity|Mandatory, LOV Available \\Entity Mandatory, LOV Available
|Payroll|Mandatory, LOV Available \\Payroll Mandatory, LOV Available
At line 22 removed 2 lines
|Update Existing Pays|Optional, Toggle\\Defaults to ‘Yes’. Causes UPRETRO to create the ‘new’ retro assessment amounts \\into an existing pay ([IPPH] record, must have been created prior to running\\UPRETRO, and must be in stage ‘To Be Audited’ or ‘Audited’). This option allows \\users to pay retro on the same pay header as their ‘regular’ pay. \\Note: if users would like a separate pay (to control taxation or sundries, or to \\prevent benefits or attendance calculations from occurring), but do not want multiple\\pay stubs to be created:\\1) Choose ‘No’ for this parameter (create retro into a separate pay);\\2) Use the ‘Consolidate Disbursements’ flag on the Pay Category ([IPPGU] or\\[IPPGC]) to force one pay stub for both pays.
|Batching Method|Optional, LOV Available\\Choose a batching method (the manner in which UPRETRO will group employees \\for batch totals and administration). The same choices exist as for all other ‘batch \\creating’ programs: Authorization Area, Department, Dept. Batch Code, Location, \\Payroll or Work Area.
At line 26 added 3 lines
|Batching Method|Optional, LOV Available\\Choose a batching method (the manner in which UPRETRO will group employees \\for batch totals and administration). The same choices exist as for all other ‘batch \\creating’ programs: Authorization Area, Department, Dept. Batch Code, Location, \\Payroll or Work Area.
|Update Existing Pays|Optional, Toggle\\Defaults to ‘Yes’. Causes UPRETRO to create the ‘new’ retro assessment amounts \\into an existing pay ([IPPH] record, must have been created prior to running\\UPRETRO, and must be in stage ‘To Be Audited’ or ‘Audited’). This option allows \\users to pay retro on the same pay header as their ‘regular’ pay. \\Note: if users would like a separate pay (to control taxation or sundries, or to \\prevent benefits or attendance calculations from occurring), but do not want multiple\\pay stubs to be created:\\1) Choose ‘No’ for this parameter (create retro into a separate pay);\\2) Use the ‘Consolidate Disbursements’ flag on the Pay Category ([IPPGU] or\\[IPPGC]) to force one pay stub for both pays.
|Process New Additions|Mandatory, Toggle\\Defaults to ‘No’. If ‘Yes’, when back dated changes are made to configuration\\(IPPC/IEAS/ISPM, etc), these changes will cause Pay Lines to be generated \\that did not exist on the previous pays.
At line 33 added one line
This page (revision-8) was last changed on 26-Nov-2021 10:22 by kparrottTop