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

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

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
29 26-Nov-2021 10:22 4 KB jmyers to previous 1ST_DAY_OF_WEEK ==> 1ST_DAY_OF_WEEK(System_Preference)
28 26-Nov-2021 10:22 4 KB JMyers to previous | to last
27 26-Nov-2021 10:22 4 KB JMyers to previous | to last
26 26-Nov-2021 10:22 4 KB Bill Hughes to previous | to last
25 26-Nov-2021 10:22 4 KB Bill Hughes to previous | to last
24 26-Nov-2021 10:22 4 KB Bill Hughes to previous | to last
23 26-Nov-2021 10:22 4 KB Bill Hughes to previous | to last
22 26-Nov-2021 10:22 4 KB JMyers to previous | to last
21 26-Nov-2021 10:22 4 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
DTDP
DTDP

Version management

Difference between version and

At line 3 changed one line
!!!DAILY DEVICE CLOCK PUNCHES(DTDP)
!!!DAILY DEVICE CLOCK PUNCHES (DTDP)
At line 5 changed one line
This function gives managers the ability to see who punched IN/OUT (clock entries) and from what clock device [ITCD] - (''Define Clock Devices'') they came from. \\\Most time clock implementations will have more than one clock device (time clock or punch clock); this calendar based screen allows managers to select a clock device and see clock entries by day and by employee. It also provides information a manager might want to see such as costing or shift information.
This function gives managers the ability to see who punched IN/OUT (clock entries) and from what clock device [ITCD] - (''Define Clock Devices'') they came from.\\ \\
Most time clock implementations will have more than one clock device (time clock or punch clock); this calendar based screen allows managers to select a clock device and see clock entries by day and by employee. It also provides information a manager might want to see such as costing or shift information.
At line 7 changed one line
The definition data for the Daily Device Clock Punches screen is stored in the P2K_TS_CLOCK_DEVICES and P2K_TS_CLOCK_ENTRIES tables.
The definition data for the Daily Device Clock Punches screen is stored in the [P2K_TS_CLOCK_DEVICES] and [P2K_TS_CLOCK_ENTRIES] tables.
At line 9 changed one line
!!Fields on the screen
!Calendar
Dynamic Calendars are used in the [DTSH] form to allow companies to specify the start of the work week. \\ In the [Preference tab of IMST|IMST#PreferencesTab], clients must add [1ST_DAY_OF_WEEK(System_Preference)] preference with a value of 1 through 7 where 1 represents Sunday and 7 represents Saturday.\\ \\The clock entry information below the calendar is derived based on the date in focus on the calendar.
At line 11 removed one line
!Find by
At line 13 removed one line
Users can find clocks devices by the following:
At line 15 removed 9 lines
;[Clock Device|CLOCK_DEVICE_CODE]:This is the user-defined code that uniquely identifies the clock device.
;[Description (Clock Device)|DESCRIPTION]:This field allows the user to give additional information and description about the clock device.
;[Description (Location)|DESCRIPTION]:This field holds a short description of the location ([IDLN]) of the clock device.
!Calendar
Dynamic Calendars are used in the DTSH form to allow companies to specify the start of the work week. \\ In [IMST] in the preference tab clients must add [1ST_DAY_OF_WEEK] preference; with a value of 1 thru 7; 1 representing Sunday to 7 representing Saturday. \\The clock entry information below the calendar is derived based on the date in focus on the calendar.
At line 28 changed one line
The following clock entry details can be seen by day based on the date in focus on the calendar:
The following clock entry details can be seen by day based on the date in focus on the calendar above:
At line 30 changed one line
;[Time Entries|TIME_ENTERED]:
!Time Entry
At line 36 changed one line
;[Type|CLOCK_ENTRY_TYPE]:This field identifies the type of clock entry being made, e.g. In, Out, Break, Lunch or Undetermined.
;[Type|CLOCK_ENTRY_TYPE]:This field identifies the type of clock entry being made. e.g. In, Out, Break, Lunch or Undetermined.
At line 46 changed 2 lines
;[Reference Information|REFERENCE_INFORMATION]:This field will allow the user to include any additional information about the time entry. This field may be used to indicate the clock device if the G1 or G2 interface is used. Each time clock would be given a Machine Name that corresponds to a clock device ([ITCD]) in [{$applicationname}]. This code would be stored in the reference information for each clock entry.
;[Reference Information|REFERENCE_INFORMATION]:This field will allow the user to include any additional information about the time entry. This field may be used to indicate the clock device if the G1 or G2 interface is used. Each time clock would be given a machine name that corresponds to a clock device ([ITCD]) in Personality. This code would be stored in the reference information for each clock entry.
%%information The following areas are view only%%
At line 50 changed one line
;[Time Exception Type|TIME_EXCEPTION_TYPE]: The time exception type is used to record the type of exceptions to the schedule. Time Exception Type is tied to the fixed lexicon [X_TIME_EXCEPTION_TYPE]. The Time Exception Type that defaults in is 'Work Exception'.
;[Time Exception Type|TIME_EXCEPTION_TYPE]: The time exception type is used to record the type of exceptions to the schedule.
At line 59 removed 2 lines
----
;[Clock Entry Status|CLOCK_ENTRY_STATUS]:This field displays the status of the card entry, e.g. Newly Entered or Processed.
At line 62 changed one line
;[Time Exception Status|TIME_EXCEPTION_STATUS]:This field displays the status of the time exception, e.g. Newly Entered or Processed.
!Clocking Details
;[Clock Entry Status|CLOCK_ENTRY_STATUS]:This field displays the status of the card entry. e.g. Newly Entered or Processed.
At line 64 changed one line
;[Start Time|START_TIME]: The actual start time that will be used in time calculations; either the [Original Time|ORIGINAL_CLOCK_TIME] (In) will be used or if there have been rounding rules applied, the [Adjusted Time|ADJUSTED_CLOCK_TIME] (In) will be used instead.
;[Time Exception Status|TIME_EXCEPTION_STATUS]:This field displays the status of the time exception. e.g. Newly Entered or Processed.
At line 66 changed one line
;[Start Time|END_TIME]: The actual start time that will be used in time calculations; either the [Original Time|ORIGINAL_CLOCK_TIME] (Out) or if there have been rounding rules applied, the [Adjusted Time|ADJUSTED_CLOCK_TIME] (Out) will be used instead.
;[Start Time|START_TIME]: This field holds the actual start time that will be used in time calculations; either the [Original Time|ORIGINAL_CLOCK_TIME] (In) will be used or if there have been rounding rules applied, the [Adjusted Time|ADJUSTED_CLOCK_TIME] (In) will be used instead.
;[End Time|END_TIME]: This field holds the actual end time that will be used in time calculations; either the [Original Time|ORIGINAL_CLOCK_TIME] (Out) or if there have been rounding rules applied, the [Adjusted Time|ADJUSTED_CLOCK_TIME] (Out) will be used instead.
----
![Notes|Edit:Internal.DTDP]
[{InsertPage page='Internal.DTDP' default='Click to create a new notes page'}]
This page (revision-29) was last changed on 26-Nov-2021 10:22 by jmyersTop