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

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

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
68 26-Nov-2021 10:22 14 KB ihowie to previous
67 26-Nov-2021 10:22 14 KB rthiruppathy to previous | to last
66 26-Nov-2021 10:22 13 KB kparrott to previous | to last
65 26-Nov-2021 10:22 13 KB jescott to previous | to last
64 26-Nov-2021 10:22 13 KB jescott to previous | to last
63 26-Nov-2021 10:22 13 KB jescott to previous | to last Target Time Code Set ==> TARGET_TIME_CODE_SET
62 26-Nov-2021 10:22 13 KB jescott to previous | to last
61 26-Nov-2021 10:22 13 KB rforbes to previous | to last

Page References

Incoming links Outgoing links
IDWR
IDWR

Version management

Difference between version and

At line 83 changed 24 lines
;:__By Day with Time__
;:For a biweekly payroll this would create ten daily transactions, with hours under the pay component attached to the time code indicated.
;:__By Week with Time__
;:For a monthly payroll this would create four to six transactions, each breaking as of the Friday of each week during the month, with hours under the pay component attached to the time code indicated.
;:__By Period with Time__
;:This will create one transaction regardless of the payroll cycle, with hours under the pay component attached to the time code indicated.
;:__By Day w/o Time__
;:For a biweekly payroll this would create ten daily transactions for the pay component attached to the time code indicated with no hours.
;:__By Week w/o Time__
;:For a monthly payroll this would create four to six transactions, each breaking as of the Friday of each week during the month for the pay component attached to the time code indicated with no hours.
;:__By Period w/o Time__
;:This will create one transaction regardless of the payroll cycle for the pay component attached to the time code indicated with no hours.
;:There are three additional Time Generation rules:
;:*Pick List by Day
;:*Pick List by Week
;:*Pick List by Period
;:*Holidays ONLY
;:Choosing one of these will insert separate transactions for each distribution code attached to the assignment that has a split rule of 'Pick List'. --
;:Choosing one of the time transactions will insert separate transactions for each distribution code attached to the assignment that has a split rule of 'Pick List'.
At line 108 changed 3 lines
;:When UPTG generates the pay transactions, the system will generate one transaction per assignment per distribution code on the list. The pay transaction will be overridden with the proper rate and complete GL distribution code.
;:For example, if UPTG is run for an employee with three assignments and each assignment has three distribution records defined on IEAS, we would expect to see nine transaction records in IPTR per week, or eighteen records per pay period.
;:Employees can work in multiple locations (GL Distributions) at multiple rates of pay on multiple timesheets. These enhancements are required to accurately record the time and pay the employee.
;:When [UPTG] generates the pay transactions, the system will generate one transaction per assignment per distribution code on the list. The pay transaction will be overridden with the proper rate and complete GL distribution code.
;:For example, if [UPTG] is run for an employee with three assignments and each assignment has three distribution records defined on [IEAS], we would expect to see nine transaction records in [IPTR] per week, or eighteen records per pay period.
;:Employees can work in multiple locations (GL Distributions) at multiple rates of pay on multiple time sheets. These enhancements are required to accurately record the time and pay the employee.
This page (revision-68) was last changed on 26-Nov-2021 10:22 by ihowieTop