This page (revision-8) was last changed on 26-Nov-2021 10:22 by Karen Parrott

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

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 8 KB Karen Parrott to previous
7 26-Nov-2021 10:22 8 KB Karen Parrott to previous | to last
6 26-Nov-2021 10:22 8 KB Karen Parrott to previous | to last
5 26-Nov-2021 10:22 8 KB Karen Parrott to previous | to last
4 26-Nov-2021 10:22 9 KB Karen Parrott to previous | to last
3 26-Nov-2021 10:22 10 KB Karen Parrott to previous | to last
2 26-Nov-2021 10:22 10 KB Karen Parrott to previous | to last
1 26-Nov-2021 10:22 1 KB Meg McFarland to last

Page References

Incoming links Outgoing links
WETETBWD
WETETBWD

Version management

Difference between version and

At line 3 changed 2 lines
The My Projected Time Sheet - Entered Time By Week Date (WETETBWD) is a form that breaks a bi-weekly timesheet into two weeks, each with it's own subtotal and grand total. This form will allow users to enter work and meal time in one line.
\\ \\
The My Projected Time Sheet - Entered Time By Week Date (WETETBWD) allows users to enter work and meal time in one line.
\\
At line 6 changed 4 lines
\\ \\
__Non Leave Time processing__
*In order to force this type of generation, in IDWR we need to add the 'USE PRJ SCH SHFT' time rule.
*In cases that the work calendar has a shift defined, then the start/end time for work/meal will be prepopulated on the ad hoc time exception.
\\
!Non Leave Time processing
*In order to force this type of generation in IDWR we need to add the 'USE PRJ SCH SHFT' time rule.
*In case that the work calendar has a shift defined then the start/end time for work/meal it will be prepopulated on the ad hoc time exception.
At line 11 changed one line
*For non-leave time, user should entered at least Time In/Out\\Please keep in mind, no time will be generated on time sheet entries if the user enters only hours and the time code associated is not a leave
*For non-leave time, user should entered at least Time In/Out\\Please keep in mind no time will be generated on time sheet entries if the user enters only hours and the time code associate is not a leave
At line 13 changed one line
__Leave Time processing__
!Leave Time processing
At line 22 changed one line
In a case that you use earning codes, EE could not see a distinction between the regular day and a holiday work since the earning code was not populated.
In case that you use earning code, EE could not see a distinction between the regular day and a holiday work since the earning code was not populated.
At line 26 changed one line
If the EE wants to add a second shift in that day, they can see that they need to use holiday work special condition
If the EE wants to add a second shift in that day the they can see that they need to use holiday work special condition
This page (revision-8) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop