Overtime Assignment

1Purpose #

• Overtime is authorised per employee per day, in advance or after the fact. Attendance joins the day's punches to an Approved assignment: Late Hrs. pays shift-end to last-punch, Early Hrs. pays first-punch to shift-start, Both pays both.
• The shift decides the rest — whether the employee is OT-eligible at all, the OT window, the conversion of attendance to OT hours (Shift master). The assignment is the per-day switch.
• It does not record hours itself (the punches do) and it is not an extra-work claim (that is Extra Work Entry).

2Your first assignment, step by step #

Suppose a driver is asked to stay late on Friday for a delivery. The page opens ready to type — the Mode card reads Add .

1. Date shows today; pick Friday.
2. Press Enter , pick the Employee by name, ledger code or Emp ID.
3. Press Enter , pick the Eligibility type : Late Hrs.
4. Press Enter , type a Description — "evening delivery, approved by the branch head".
5. Press Enter (focus lands on Save ) and press Enter or F5 . Confirm. The status chip reads Open when approval is required.
6. The approver loads the assignment (F2), presses F7 , picks Approved , confirms. From that moment attendance for Friday pays the late hours.

With approval switched off (setting 205) step 6 is not needed — the save lands Approved. Editing an approved assignment sets it back to Altered and it must be approved again.

3How to use it #

1. Find (F2) lists the assignments newest first — employee, ledger code, date, type, branch (ERP edition), status; pick one to load it.
2. Add (F3) , Modify (F4) , Delete — each asks first. Save (F5) commits and stays in View mode.
3. Change Status (F7) is how an assignment is approved, held or cancelled; it lists the statuses your user may set.
4. Enter moves from field to field and lands on Save.

4Field details #

• ID — assigned at the first save.
• Branch (shown in the ERP edition only) — your login branch, stamped on the assignment.
• Date — required; with the employee it forms the unique key.
• Employee — required; the ledger account, shown with its code, Emp ID and designation.
• Eligibility type — required; Early Hrs. / Late Hrs. / Both.
• Description — optional, 255 characters.
• Status — Open / Altered while waiting, Approved when it pays, Cancelled / Rejected / On Hold otherwise.

5Shortcut keys #

• F2 Find · F3 Add · F4 Modify · F5 Save · F7 Change Status · Esc Cancel.
• Enter moves to the next field; from the last one it lands on Save.

6Why is a pick-list empty? #

• Employee — every Employee-master record with a ledger account; inactive accounts are marked. An employee without a ledger account does not appear — complete the record in the Employee master, or use "Create new employee" in the list footer.
• Eligibility type — fixed; never empty.
• Find (F2) empty — no assignment exists yet, or your user lacks the Find right on EmpOvertimeAssignment (the page says so).

7Rules and integrity #

• One per employee per day. The table's primary key; the page checks and the server checks again.
• Approval. Setting 205 ON: saved Open / Altered and pays only once Approved (F7). OFF: saved Approved.
• Finger-print gate. The desktop could demand the branch head's finger-print before saving (setting 89). A browser has no finger reader, so while that setting is on this page refuses the save and says why — use the desktop or switch the setting off.
• Cancelled is final ; enter a new assignment instead of editing a cancelled one.
• Permissions. Find needs the Find right on EmpOvertimeAssignment; Change Status needs Approve (plus Alter); saving runs through the permission triggers.

8If something does not work #