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

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
17 26-Nov-2021 10:22 6 KB JMyers to previous
16 26-Nov-2021 10:22 6 KB JMyers to previous | to last
15 26-Nov-2021 10:22 6 KB JMyers to previous | to last
14 26-Nov-2021 10:22 5 KB JMyers to previous | to last
13 26-Nov-2021 10:22 4 KB JAiken to previous | to last
12 26-Nov-2021 10:22 4 KB JEscott to previous | to last
11 26-Nov-2021 10:22 4 KB JEscott to previous | to last
10 26-Nov-2021 10:22 5 KB JEscott to previous | to last
9 26-Nov-2021 10:22 5 KB JEscott to previous | to last
8 26-Nov-2021 10:22 4 KB JEscott to previous | to last
7 26-Nov-2021 10:22 4 KB JEscott to previous | to last
6 26-Nov-2021 10:22 3 KB JEscott to previous | to last
5 26-Nov-2021 10:22 2 KB JEscott to previous | to last
4 26-Nov-2021 10:22 1 KB JEscott to previous | to last
3 26-Nov-2021 10:22 1 KB JEscott to previous | to last
2 26-Nov-2021 10:22 1 KB JEscott to previous | to last
1 26-Nov-2021 10:22 809 bytes JEscott to last

Page References

Incoming links Outgoing links
WMTTSE
WMTTSE

Version management

Difference between version and

At line 1 changed one line
!!!Manage Time Sheet Time Code Exceptions
[{TableOfContents }]
!!!MANAGE TIME SHEET TIME CODE EXCEPTIONS
At line 3 changed one line
WMTTSE (Manage Time Exceptions) which allows managers the ability to manage time exceptions for a pay period. The functionality can only be used for shift based (start/end time) time sheets. As an exception is handled, it is removed from the exception list. The screen will only display previous day(s) time exceptions; users can define the time frame for which a manager can handle the exceptions, through a where clause. Although this is a user-definable value, High Line does not recommend setting this to a large value as it may result in a performance issue.
WMTTSE (Manage Time Exception) was developed to give managers the ability to manage their employees' time exceptions for a pay period. This functionality can only be used for employees whose time sheets are generated with shifts (start and end time sheets). As an exception is handled, it is removed from the exception list.
At line 5 changed 9 lines
;[PERS_ASSIGN]:
;[Date|ENTRY_DATE]:
;[Start Time|START_TIME]:
;[End Time|END_TIME]:
;[Hours|TIME_OR_AMOUNT]:
;[Time Code|TIME_CODE]:
;[Reason For Time|REASON_FOR_TIME]:
;[Time Sheet|TIME_SHEET_NUMBER]:
;[Include Indirectly Managed Employees|ACT_SHOW_INDIRECT]:
The screen will only display previous day(s) time exceptions. Clients have the ability to define the time frame for which they want the exceptions to display in the list. This may be done by modifying the where clause called ‘EX_TM_TYP_MGR’. By default the exception period is 7 days from yesterday. Although users have the ability to change the exception period, we do not recommend making the interval too long as it may result in performance issues.
At line 8 added 13 lines
!Time Code Exceptions
This section displays all employees who have exceptions that must be handled.
;[Employee|PERS_ASSIGN]: The employee's person code, name and assignment are displayed in this field.
;[Date|ENTRY_DATE]:The date of the time exception is indicated in this field.
;[Start Time|START_TIME]:This field holds the time exception's start time.
;[End Time|END_TIME]:This field holds the time exception's end time.
;[Hours|TIME_OR_AMOUNT]:The number of hours the time exception is for is indicated here. The time codes listed here are those that are defined in the lexicon [X_TM_EXCEPTIONS].
;[Time Code|TIME_CODE]:The time code used to record the time exception is indicated here.
;[Reason For Time|REASON_FOR_TIME]:The employee's chosen reason for time is displayed here.
;[Time Sheet|TIME_SHEET_NUMBER]:The employee's time sheet number that the time exception was entered for will display here.
;[Include Indirectly Managed Employees|ACT_SHOW_INDIRECT]:This toggle allows the Manager to extend the list to display employees who the Manager is indirectly responsible for.
At line 16 changed 3 lines
;[Change Work|ACT_CATEGORIZE_WORK]:
;[Add Leave|ACT_ADD_AWAY_FROM_WORK]:
;Go To Time Sheet:
There are 2 dialogs that can be used to manage exceptions listed in the grid:
At line 24 added one line
;[Change Work|ACT_CATEGORIZE_WORK]: This button allows managers to allocate the time for the specific transaction against a specific time code or use special conditions. Once the time sheet has been approved the dialog will no longer be available.
At line 21 changed 3 lines
!Day Details
;Person:
;[Date|ENTRY_DATE]:
;[Add Leave|ACT_ADD_AWAY_FROM_WORK]:This button allows managers to place the employee on leave by selecting the appropriate time code or special condition.Once the time sheet has been approved the dialog will no longer be available.
At line 25 changed 7 lines
;[Start Time|START_TIME]:
;[End Time|END_TIME]:
;[Time Type|TIME_ENTRY_TYPE]:
;[Expected Punch^Prediction|CLOCK_ENTRY_TYPE]:
;[In^ Punch|DRV_IS_IN]:
;[Out^ Punch|DRV_IS_OUT]:
;[Time Code|TIME_CODE]:
;Go To Time Sheet:The dialog ‘Go to Time Sheet’ is used to take the user to the time sheet screen ([WMTTS]). In order to use this functionality, the Time Sheet form ([WMTTS]) must be available on the self-service menu.
----
!Day Details
This section displays the details for a specific transaction. It identifies whether or not there is a missing punch and allows for the creation of missing punches (if required). The ‘Expected Punch Prediction’, ‘In Punch’ and ‘Out Punch’ columns were added to allow managers to quickly identify whether the exception is the result of a missing punch.
;Person: The employee's person code and name will display in this field.
;[Date|ENTRY_DATE]:The date of the time exception is displayed in this field.
At line 37 added 8 lines
;[Start Time|START_TIME]: The start time of the transaction is indicated here.
;[End Time|END_TIME]:The end time of the transaction is displayed here.
;[Time Type|TIME_ENTRY_TYPE]:The type of time entry of the transaction is indicated here.
;[Expected Punch Prediction|CLOCK_ENTRY_TYPE]:This field will display what the expected punch will be, ie: In, Out
;[In Punch|DRV_IS_IN]:This field will indicate if the clock punch was an IN punch type.
;[Out Punch|DRV_IS_OUT]:This field will indicate if the clock punch was an OUT punch.
;[Time Code|TIME_CODE]:The time code used to track the time within the transaction will be indicated.
\\
At line 34 changed one line
;[Create Missing Punch|ACT_CREATE_INOUT]:
;[Create Missing Punch|ACT_CREATE_INOUT]:This button allows the Manager to create a clock punch if one is missing. The ‘Create Missing Punch’ dialog will always be enabled, however once a time sheet has been submitted and if a punch is added to the time sheet it will not be processed in the system. The Maintain Clock Entry form ([ITCE]) will store the punch with a [status|CLOCK_ENTRY_STATUS] of ‘Un-generated’. The Audit Info field will display a message indicating that the time sheet has been closed.
At line 48 added one line
----
At line 37 changed 3 lines
;[Leave Policy Code|LEAVE_POLICY_CODE]:
;[Description|DESCRIPTION]:
;[Balance To Date|DRV_BALANCE_TO_DATE]:
This section displays the employee’s leave balances and is intended to provide managers a reference when entering leave information to know exactly how much time an employee has available in their banks.
;[Leave Policy Code|LEAVE_POLICY_CODE]:The leave policy code is indicated in this field.
;[Description|DESCRIPTION]:The leave policy's description is displayed in this field.
;[Balance To Date|DRV_BALANCE_TO_DATE]:The system will derive the employee's leave balance for the leave policy indicated.
\\
----
!!Restrictions on Changing the Time Sheet
The following restrictions have implemented on the time sheet:
#The ‘Change Work’ and ‘Add Leave’ dialogs will be disabled once a time sheet has been approved (i.e. Time Sheet Status = Ready for Payroll)
#The ‘Create Missing Punch’ dialog will always be enabled, however once a time sheet has been submitted and if a punch is added to the time sheet it will not be processed in the system. The Maintain Clock Entry form will store the punch with a status of ‘Un-generated’. The Audit Info field will display a message indicating that the time sheet has been closed.
\\
----
!!Defining the Time Codes to Display in the Exceptions List
Each client can identify which time codes they would like to display in the exceptions list by setting up the lexicon ‘X_TM_EXCEPTIONS’. Each time code must be setup in the lexicon ‘X_TM_EXCEPTIONS’ as follows:
|Saved Value|Time Code (this must be identical to the time code definition)
|Displayed Value|It is recommended that this value be identical to the saved value
|Meaning|It is recommended that this value be identical to the saved value
|Usage|User-Defined
\\
----
!!Defining the Time Frame for Displaying Exceptions
Clients have the ability to define the time frame for which they want the exceptions to display in the list. A where clause called ‘EX_TM_TYP_MGR’ should be defined.
[WMTTSE.JPG]
\\
By default the exception period is seven days from yesterday. Although users have the ability to change the exception period, it is not recommended to make the interval too long as it may result in performance issues.
\\
----
!!Making the Function Available in Self-Service
As with any other Self Service function, this must be attached to the manager menu in [IMMU] and appropriate execution rights granted to the function in [IMER].
----
![Notes|Edit:Internal.WMTTSE]
[{InsertPage page='Internal.WMTTSE' default='Click to create a new notes page'}]
This page (revision-17) was last changed on 26-Nov-2021 10:22 by JMyersTop