Manual Leave Posting

1Purpose #

• The leave balance is never stored — it is computed from the posting ledger. When the computed figure is wrong (an employee joined with unused leave, a correction after a data fix), the remedy is a POSTING, not an edit of history: an OPENING adds a starting balance, an ADJUSTMENT moves the balance by its signed value.
• The legacy "Leave Adjustment (Manual)" form let the operator write any value type, including the engine's own — the port narrows the choice to the two operator movements, so engine rows stay untouchable and the provenance of every row is unambiguous (Flag = 'Manual').
• Deleting a manual row is allowed (it corrects a mistaken entry); deleting engine rows is not — correct those with a counter-ADJUSTMENT instead.

2Your first posting, step by step #

Suppose an employee joins with 6.5 days of leave carried from a previous system.

1. Pick the employee — the grid loads their existing manual postings.
2. Press Add Row (F3) ; leave the type at OPENING.
3. Set the date the balance takes effect (typically the joining or go-live date).
4. Pick the leave policy the balance belongs to.
5. Enter 6.5 as the value and a reason ("Balance carried from previous system").
6. Press Save (F5) — the batch writes in one transaction and the grid reloads from the ledger.
7. Verify on the Leave Balance page: the opening appears in the policy's card.

3Field details #

• Type — OPENING (a granted starting balance, always positive) or ADJUSTMENT (a signed correction: plus adds, minus reduces).
• Date — when the movement takes effect; it decides which leave year the row lands in. The saved row also carries the entry time, so two rows on the same day never collide.
• Leave Policy — which policy's balance moves.
• Value — days (or the policy's unit). Never zero; OPENING refuses a minus.
• Reason — mandatory. It is the row's Description in the ledger and shows on the Leave Balance drill-down.
• Remove — marks the row for deletion; the delete happens on Save.

4Shortcut keys #

• F2 Reload the employee's rows · F3 Add a row · F5 Save · Esc Discard unsaved changes.
• Enter moves to the next field.
• Keys belong to the focused copy of the page; a dialog's own keys win while it is open.

5Why is a pick-list empty? #

• Leave Policy lists the Leave Policy master (PAY-06) — create policies there first. A posting does NOT require an assignment (an opening can precede it), but only ASSIGNED policies accrue.

6Rules and integrity #

• One transaction. Adds, edits and removals of one save commit or roll back together.
• Only OPENING and ADJUSTMENT. The engine's rows (ACCRUAL, CARRYOVER, LAPSE, UTILIZATION) are not editable here — the server refuses even a hand-crafted request.
• Reason mandatory. A posting without a reason is refused, client and server alike.
• Signs. The ledger stores every value positive with a direction word; the grid shows adjustments signed and converts on save. An OPENING can not be negative — reduce with an ADJUSTMENT.
• One posting per employee + policy + instant (the ledger's primary key). New rows carry the entry time-of-day, so same-day postings coexist.

7If something does not work #