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

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 3 KB rforbes to previous
7 26-Nov-2021 10:22 3 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 3 KB JEscott to previous | to last
4 26-Nov-2021 10:22 3 KB JEscott to previous | to last
3 26-Nov-2021 10:22 3 KB JEscott to previous | to last
2 26-Nov-2021 10:22 2 KB JEscott to previous | to last
1 26-Nov-2021 10:22 2 KB JEscott to last

Page References

Incoming links Outgoing links
CLOCKING PROCESS FLOW
CLOCKING PROCESS FLOW

Version management

Difference between version and

At line 4 changed one line
**This function is designed to be re-runable.
**This function is designed to be re-runnable.
At line 7 changed one line
# Employees may creat clock punches thru [WPCIO] (Public Kiosk), or Managers may clock in their employees thru [WMTCI] (Self Service Clock IN/OUT) or Administrators (Professional [DTCI] and [DTCP]
# Employees may create clock punches through [WPCIO] (Public Kiosk), or Managers may clock in their employees through [WMTCI] (Self Service Clock IN/OUT) or Administrators may create clock punches in the Professional application through [DTDP] or [DTCP].
# Clock punches may also originate from a clock device such as Genius G1 or Genius G2.
# Clock Punches from an external source may be loaded into the application by running the [LTCE] function.
# If an employee punches in for a scheduled job and then punches in again for a different job without punching out in between the system will automatically create an 'out' punch for the first job as it is considered a costing change.
# If an employee punches in for a non-scheduled job and then punches in again for a different job (whether it is scheduled or not) without punching out in between the system will not create an out punch.
At line 9 changed one line
**The [UTCIO] process is used to load clock entries from external sources. When running [UTCIO], the clock entries are loaded and processed at the same time.
**The [UTCIO] is an update process designed to process clock entries into time exceptions.
At line 11 changed 3 lines
**With the G1 or G2 interface the clock entries will be processed immediately.
#Missing Clock punches are available to be viewed by the employee ([WETCP]), the Manager ([WMTCP]) or an administrator (Self Service [WATCP] or Professional [DTMCP]).
# Administrators may approve/authorize/verify clock punches thru [WVTAPC].
**With the G1 or G2 interface the clock entries will be processed immediately.
#Missing Clock punches are available to be viewed by the employee ([WETMCP]) the Manager ([WMTMCP])or a Scheduler [WSTMCP] in Self Service. A user of the Professional application may see missing clock punches in [DTMCP]. The page [Missing Clock Punches|MISSING CLOCK PUNCHES] provides more information on how missing punches are handled.
# Administrators may approve/authorize/verify clock punches through [WVTAPC].
At line 24 added 5 lines
----
![Notes|Edit:Internal.CLOCKING+PROCESS+FLOW]
[{InsertPage page='Internal.CLOCKING+PROCESS+FLOW' default='Click to create a new notes page'}]
This page (revision-8) was last changed on 26-Nov-2021 10:22 by rforbesTop