Manual Time Entry

1Purpose #

• Every punch an employee makes lands in the time log. A device writes them automatically (Device Log Processing); this page writes one by hand — an employee who forgot to punch, worked at a site without a reader, or punched while the device was down.
• A manual punch is a normal punch to everything downstream: the Time Log Manager pairs it into In/Out for the day, and attendance is generated from it exactly as from a device punch. The only difference is the Manual flag and your login name on the record.
• It does not record extra hours or overtime — those are separate entries (Extra Work Entry, Overtime Assignment) — and it does not by itself create attendance; the attendance run does that from the paired punches.

2Your first manual punch, step by step #

Suppose an employee reached the site at 09:10 but the reader was down. The page opens ready to type — the Mode card reads Add .

1. Pick the Employee — type part of the name or the Emp ID and press Enter on the match.
2. Press Enter ; the cursor moves to Date . Today is already filled in — change it only if the punch was another day (that needs the Change-Date permission).
3. Press Enter and type the Time , 09:10:00.
4. Press Enter and type a Remark — "reader down, confirmed by supervisor" — so the punch explains itself later.
5. Press Enter once more (focus lands on Save ) and press Enter or F5 . Confirm. The banner reports the save, the ID box shows the number, the status chip reads Open , and the Mode card reads View .
6. The evening punch is a second entry: F3 , same employee, 18:05:00, Save. The Time Log Manager now shows 09:10 In / 18:05 Out for the day.

Made a mistake? F2 lists the manual punches; pick one, F4 , correct, F5 . A punch that attendance has already been generated from can not be changed at all — cancel that attendance voucher first.

3How to use it #

1. Find (F2) lists the manual punches (newest first) with employee, date & time, branch (ERP edition) and status; pick one to load it. Device punches are not listed here — they are managed on the Time Log Manager.
2. Add (F3) starts a new punch with today's date; Modify (F4) edits the loaded one; Delete removes it. Each asks first.
3. Save (F5) commits. After saving, the record stays on screen in View mode — press Add (F3) for the next one.
4. Change Status (F7) sets Cancelled, On Hold, Approved … from the statuses your user may set. A cancelled punch stays on file but is ignored by the Time Log Manager and attendance.
5. Enter moves from field to field and lands on Save, so a punch can be keyed without the mouse.

4Field details #

• ID is assigned when the punch is first saved ("Auto" until then) and is the number the Time Log Manager shows in its punch list.
• Branch (shown in the ERP edition only) is your login branch, stamped on the punch; it is not editable here (the desktop did the same).
• Employee is required — name, Emp ID and designation are shown side by side in the list.
• Date and Time together are the punch instant. It can not be in the future, and the employee can not already have a punch at the same second.
• Remarks are optional free text (255 characters).
• Status starts Open . Only Change Status alters it; editing the punch does not.

5Shortcut keys #

• F2 Find · F3 Add · F4 Modify · F5 Save · F7 Change Status · Esc Cancel (or close, when opened as a dialog).
• Enter moves to the next field; from the last one it lands on Save. Ctrl+Enter makes a new line in Remarks.
• Keys belong to the focused copy of the page — with two tabs open, the one you are looking at answers. A dialog's own keys win while it is open.

6Why is a pick-list empty? #

• If Find (F2) is empty, no manual punch has been keyed yet, or your user lacks the Find right on EmpTimeLog (the page says so).

7Rules and integrity #

• One punch per employee per second. The table has a unique index on employee + date-time; the page checks and the server checks again.
• Frozen after attendance. Once attendance has been generated from a punch (ATGenMasSEQ is set) the database trigger refuses every change — edit, delete and status alike. Cancel that attendance voucher first.
• Permissions. Find needs the Find right on the EmpTimeLog object; Change Status needs Approve (and the database demands Alter for the update); saving runs through the permission triggers. Every refusal names the right that is missing.
• Only a manual punch can be edited or deleted here; a device punch is cancelled from the Time Log Manager instead.

8If something does not work #