| Subject: | Need a New Time and Attendance Rule as 'Maximum hours to be considered as the same work day' to split Time entries [Created from case 10372] |
| Summary: | Important notes on creating a new case (Remove this before saving the case) - Subject line should be clear and concise
- Case header should have a clear explanation of requirements with examples where possible
- Justification for New Feature/Change Request
- Suggestions or notes relevant to the case
- Test plan and Pass/Fail scenarios
1. Summary of requirements:
We need a rule in Time and Attendance Module to be able to define the maximum work hours in a day so that system can split the entries accordingly and timesheet entries are correctly created. Currently if user has clocked In for one day, there are no other entries for that day, the following day does not have a clock in time but there is a clock out for the that day, this is merged as one line of entry. In some cases users use incorrect Punch Type, example instead of Out, they use Resume or Done. This also causes discrepancies in time and system ends up merging the time entries for staff. Below are the common Punch types in the various machines we have integrated with our Payroll
| PunchTypeNo | Punch Type Description | | 00 | Check In | | 01 | Check Out | | 02 | Break | | 03 | Resume | | 04 | OT | | 05 | Done |
Currently we have a rule to mark these entries as Invalid if they are exceeding certain hours however we can enhance the rule to split the entries in different days based on the configured work hours per day to simplify editing for the supervisors. Below is a snapshot as an example which I have come across with my setup at Motibhai Group of Companies and Tappoos . I have been able to reproduce the same internally using our demo database. See figure 1.1 and figure 1.2 below to review the current behavior of the system. Figure 1.1 
Notice that employee has used some incorrect punch type and system has merged 3 days time in one day.
Figure 1.2
 Notice that employee has used some incorrect punch type and system has merged 2 days time in one day.
2. Request Information (Requester to fill in) | ID | Description (*Required Fields) | Value | | 1 | Customer Name* | Tappoos Group of Companies, Motibhai Group of Companies, ITaukei Land Trust Board, Danam Fiji Limited, Goodman Fielder International | | 4 | Estimated Cost (hrs/$) |
| | 5 | Cost Covered By * | Link Technologies | | 7 | Workarounds? | Manual Editing of the Time by the supervisors and create new entries | | 8 | Date Required by * | The quicker the better so I can roll out more of the sites and see the strength of our Time and Attendance |
1. Change Details: (Requester to fill in)
Add a new Time and Attendance Rule as 'Maximum Work hours to be considered as the same work day' with a default value as 16. This rule will ensure that entries exceeding the configured hours to be marked as a new working day and separate Time Entry Line created for these entries. This rule has been taken from Time Control Management System, version 2. Formula: Add 16 hours to the start time of the employee. Hours Exceeding 16th hour be part of a new day. 2. TEST PLAN: Place all possible test cases relating to this new feature/Change request (Requester to fill in) Below is the required setup for the Test Plan. Shift DS: Start Time 07.30 am End Time 04:30 pm with no configured breaks in the shift.
Shift NS: Start Time 07:00 pm End Time 04:00 am with no configured breaks in the shift.
Shift AS: Start Time 02:00 pm End Time 12:00 am with no configured breaks in the shift.
Buffer Before Shift Start is 15mins
Buffer After Shift Start is 15mins
Buffer Before Shift End is 15mins
Buffer After Shift Start is 15mins
Timesheet Import Computation Method : B
Assuming we have this configuration 'Maximum Work hours to be considered as the same work day ' set with default value of 16, below are some test scenarios : Business Scenario 1: Employee E001 working on a DS Shift has the below Time Entries. | LineNo | LogDateTime | Punch Type | | 1 | 2019-04-28 08:01:39.000
| IN | | 2 | 2019-04-28 10:21:39.000
| OUT | | 3 | 2019-04-28 11:17:39.000
| IN | | 4 | 2019-04-28 20:12:45.000
| OUT | | 5 | 2019-04-29 17:01:39.000
| OUT |
Expected Result: Line 1 - 4 : will form a valid entry foe Date 28-04-2019
Line 5 : Will form an Invalid entry with a Out time only Business Scenario 2: Employee E002 working on a NS Shift has the below Time Entries. | LineNo | LogDateTime | Punch Type | | 1 | 2019-04-28 19:01:39.000
| IN | | 2 | 2019-04-28 22:21:39.000
| OUT | | 3 | 2019-04-28 22:17:39.000
| IN | | 4 | 2019-04-29 04:12:45.000
| OUT | | 5 | 2019-04-30 04:01:39.000
| OUT |
Expected Result: Line 1 - 4 : will form a valid entry foe Date 28-04-2019
Line 5 : Will form an Invalid entry with a Out time only for 29/04/2019 Business Scenario 3:
Employee E003 working on a DS Shift has the below Time Entries. | LineNo | LogDateTime | Punch Type | | 1 | 2019-05-02 07:03:03.000
| IN | | 2 | 2019-05-02 10:14:14.000
| OUT | | 3 | 2019-05-02 11:18:22.000
| IN | | 4 | 2019-05-02 16:08:55.000 | OUT | | 5 | 2019-05-03 07:01:39.000
| Resume | | 6 | 2019-05-03 09:34:28.000
| OUT | | 7 | 2019-05-03 10:09:56.000
| Resume | | 8 | 2019-05-03 16:00:07.000
| OUT | | 9 | 2019-05-04 07:06:43.000
| Resume | | 10 | 2019-05-04 10:22:18.000
| OUT | | 11 | 2019-05-04 11:30:08.000
| IN | | 12 | 2019-05-04 16:42:04.000
| OUT |
Expected Result: Line 1 - 4 : will form a valid entry foe Date 02-05-2019
Line 5 - 8 : Will form an Invalid entry with a Out time only for 03-05-2019. (Rule: Add 16 hours to start time of previous day, use the next available time available after the 16th hour as In for the next Day and keep calculating to split the entries by day)
Line 9 - 12: Will Form a Valid entry (Rule: Add 16 hours to start time of previous day, use the next available time available after the 16th hour as In for the next Day and keep calculating to split the entries by day)
3. Costing (excluding tax) (Project Manager to fill in) | ID | Task Description | Hours | | 1 | Analysis and Design | 2 | | 2 | Development | 8 | | 3 | System test and UAT | 3 | | 4 | Documentation | 2 |
- Rate: $125 AUD + tax
- Total Cost:
5. Detail Design (Development Team) |
| Audit Notes: | Edited by alvis on 08/08/19 16:40. Edited by sanjay on 18/07/19 16:10. Edited by sanjay on 18/07/19 16:10. |
| 18 Jul 2019 | 04:07PM Comment 1 by Sanjay (Link Technologies) Created from case 10372 |
| 19 Jul 2019 | 01:40PM Comment 2 by Aarti Pooja Gayaneshwar (Link Business Solutions) Assigned To: Development Followup Date: 22-07-2019 12:00 AM Time Taken: 1.75 |
| Bula Vinaka Sanjay, Further to Vineet's discussion with the client (Motibhai), they have agreed to wait for this in V11. Also, Motibhai has agreed to be the early adopters for V11. Kind Regards
Aarti Gayaneshwar |
|
| 08 Aug 2019 | 04:40PM Comment 3 by Alvis (Link Technologies) Case 10520 added to project 11.0 |
| 08 Aug 2019 | 04:44PM Comment 4 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 08-08-2019 04:44 PM Time Taken: 3.50 |
| Development work for this case has been completed. The change will be available in version: 11.0.0808 1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Added configurations under devices to set up the codes for IN, OUT and BREAK
- Added a configuration for "New Entry Hours Buffer" under the rule "Timesheet processing rules". Description "New entry hours buffer. Number of hours to wait before creating a new entry. Recommended minimum 19 hours."
- Changed the timesheet computations to split time entry when consecutive entries exceed the "New entry hours buffer".
2. The issue was caused by: - Change request
3. Next Step: - UAT
4. Notes: |
|
| 16 Aug 2019 | 02:56PM Comment 5 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 16-08-2019 02:56 PM Time Taken: 1.50 |
| For UAT |
|
| 12 Sep 2019 | 10:50AM Comment 6 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 12-09-2019 10:50 AM Time Taken: 2.00 |
| Hi Alvis, The following was done Shift DS: Start Time 07.30 am End Time 04:30 pm with no configured breaks in the shift.
Shift NS: Start Time 07:00 pm End Time 04:00 am with no configured breaks in the shift.
Shift AS: Start Time 02:00 pm End Time 12:00 am with no configured breaks in the shift.
Buffer Before Shift Start is 15mins
Buffer After Shift Start is 15mins
Buffer Before Shift End is 15mins
Buffer After Shift Start is 15mins
Timesheet Import Computation Method : B
Maximum Work hours to be considered as the same work day ' set with default value of 16. Scenario 1 - Employee - E003, Mapping Code - 53
- Shift - DS
- The following time was pulled:
| Date | Time | Punch Type | 05/09/19
| 08:01
| 01 | 05/09/19
| 10:21
| 03 | 05/09/19
| 11:17
| 01 | 05/09/19
| 20:12
| 03 | 06/09/19
| 17:01
| 03 |
- When the time was pulled, 2 entries was created for date 05/9/2019. This was less than 16 hours. No record was created for the 06/09/2019.
Scenario 2 - Employee - E004, Mapping Code - 54
- Shift - NS
- The results do not match the expected outcome in case header. Time imported for 05/09/2019 and 06/09/2019.
The backup of the database has been placed at \\10.0.0.14\d\Temp. File Name - LINKSOFT-CASE10520.
Thanks
Rashna |
|
| 12 Sep 2019 | 04:00PM Comment 7 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 12-09-2019 04:00 PM Time Taken: 2.00 |
| Development work for this case has been completed. The change will be available in version:11.002.0912 1. The following changes were made(Include Database object names, Program classes and any other relevant information): - When buffer setting was used, the invalid entry for 6th September was not created. We have resolved this scenario when buffer is enabled.
2. Affected Areas: - Timesheet Import using buffer
3. The issue was caused by:
4. Notes:
5. Next Step: UAT |
|
| 18 Sep 2019 | 08:20AM Comment 8 by Rashna (Edge Business Solutions) Assigned To: Rashna (Edge Business Solutions) Followup Date: 18-09-2019 08:20 AM Time Taken: 2.00 |
| Hi Sajay, Test Results
Below is the required setup for the Test Plan. Shift DS: Start Time 07.30 am End Time 04:30 pm with no configured breaks in the shift.
Shift NS: Start Time 07:00 pm End Time 04:00 am with no configured breaks in the shift.
Shift AS: Start Time 02:00 pm End Time 12:00 am with no configured breaks in the shift.
Buffer Before Shift Start is 15mins
Buffer After Shift Start is 15mins
Buffer Before Shift End is 15mins
Buffer After Shift Start is 15mins
Timesheet Import Computation Method : B Scenario 1
LineNo | LogDateTime | Punch Type | Punch Time | Expected Results | System Result |
1 | 05/09/2019 - 8.01 | IN | 01 |
Line 1 - 4 : will form a valid entry for Date 28-04-2019
Line 5 : Will form an Invalid entry with a Out time only | 
|
2 | 05/09/2019 - 10.12 | OUT | 03 |
3 | 05/09/2019 - 11.17 | IN | 01 |
4 | 05/09/2019 - 22.12 | OUT | 03 |
5 | 06/09/2019 - 17.01 | OUT | 03 |
Scenario 2
LineNo | LogDateTime | Punch Type | Punch Time | Expected Results | System Result | 1 | 05/09/2019 - 19.01 | IN | 01 |
Line 1 - 4 : will form a valid entry foe Date 28-04-2019
Line 5 : Will form an Invalid entry with a Out time only for 29/04/2019 | 
| 2 | 05/09/2019 - 22.21 | OUT | 03 | 3 | 05/09/2019 - 22.17 | IN | 01 | 4 | 05/09/2019 - 04.12 | OUT | 03 | 5 | 7/09/2019 - 04.1 | OUT | 03 |
Scenario 3 - Enabled rule R012. Tested with Vineet on a GTM session | LineNo | LogDateTime | Punch Type | Punch Type | Expected Results | System Results (Enabled Rule R012) | | 1 | 2019-05-02 07:03:03.000
| IN | 01 |
Line 1 - 4 : will form a valid entry foe Date 02-05-2019
Line 5 - 8 : Will form an Invalid entry with a Out time only for 03-05-2019.
Line 9 - 12: Will Form a Valid entry | 
| | 2 | 2019-05-02 10:14:14.000
| OUT | 03 | | 3 | 2019-05-02 11:18:22.000
| IN | 01 | | 4 | 2019-05-02 16:08:55.000 | OUT | 03 | | 35 | 2019-05-03 07:01:39.000
| Resume | 02 | | 6 | 2019-05-03 09:34:28.000
| OUT | 03 | | 7 | 2019-05-03 10:09:56.000
| Resume | 02 | | 8 | 2019-05-03 16:00:07.000
| OUT | 03 | | 9 | 2019-05-04 07:06:43.000
| Resume | 02 | | 10 | 2019-05-04 10:22:18.000
| OUT | 03 | | 11 | 2019-05-04 11:30:08.000
| IN | 01 | | 12 | 2019-05-04 16:42:04.000
| OUT | 03 |
Thanks
Rashna |
|
| 02 Oct 2019 | 08:45AM Comment 9 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 02-10-2019 08:45 AM Time Taken: 1.00 |
| Hi Sanjay, Documentation has been updated at this link Thanks
Rashna |
|
| 09 Oct 2019 | 08:22AM Comment 10 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - Cleared queue due to large number of calls |