 |
| ||||||
| Scripting - When Dealing with a Client that Only has Double Time Rules (OTthreshold Scripts) | ||||||
| ||||||
| Question | |
| ||||
| Have a client that does not calculate any overtime just double time. But when I script it using the overtime threshold scripts it gives me erroneous totals. | ||||||
| Answer | ||||||
| Usually when doing scripts (overtime threshold) of this nature where you try to negate the overtime and go straight into double time because of its linear nature you will still need to include them. Scripts like this are as mentioned linear and go in this sequence: 1. ot1threshold (overtime in a week) 2. ot1daythreshold (overtime in a day) 3. ot2threshold (doubletime in a week) 4. ot2daythreshold (doubletime in a day) So if you exclude 1 and 2 as in this example and just script for the double time the calculations may become off as the system will try to look for these missing parameters (overtime in the week/day). To remedy this you must script in the overtime rules also. For example you only want to calculate double time after 8 hours in a day and 40 hours in a week. You would also add the overtime rules and have them duplicate their double time hour ranges like below: TimeWorks: otrules = "-"; ot1threshold = "40"; ot1daythreshold = "8"; ot2threshold = "40"; //DT in a week ot2daythreshold = "8"; //DT in a day TimeWorks Plus (goes in OTThresholdScript box): otrules(""); ot1threshold = "40"; ot1daythreshold = "8"; ot2threshold = "40"; //DT in a week ot2daythreshold = "8"; //DT in a day The overtime rules will be over ridden by the double time rules and should work correctly. We use a duplicate hour range in the OT scripts so that it will first promote to OT but then immediately promote to double time. | ||||||
| Back to Search Results | ||||||