Absence Management in Oracle Fusion is powerful — and easy to get wrong. The accrual plan is where most of the complexity lives. Here is a design checklist based on real implementations.
Accrual Plan Design Decisions
| Decision | Options | Typical Choice |
|---|---|---|
| Accrual frequency | Daily, Weekly, Bi-weekly, Monthly, Annual | Monthly or Annual |
| Carryover rule | None, Limited, Unlimited | Limited (with max days) |
| Proration on hire/termination | Yes / No | Yes |
| Ceiling (max balance) | None / Fixed / Formula-based | Formula-based for seniority tiers |
| Negative balance allowed | Yes / No / Formula | Depends on policy |
The Seniority Tier Problem
Many organisations give more leave to longer-tenured employees: 15 days for <5 years, 20 days for 5–10 years, 25 days for 10+ years. In Oracle Fusion, this is handled via a Band Matrix on the accrual plan, linked to a Fast Formula that returns the employee's tenure band.
/* Tenure band formula skeleton */ DEFAULT FOR PER_ASG_SERVICE_MONTHS IS 0 l_months = PER_ASG_SERVICE_MONTHS IF l_months < 60 THEN ACCRUAL_RATE = 15 ELSIF l_months < 120 THEN ACCRUAL_RATE = 20 ELSE ACCRUAL_RATE = 25 END IF RETURN ACCRUAL_RATE
✦ Test the carryover rule at year-end with a Sandbox simulation before go-live. Carryover calculations run as a batch process — errors here affect every employee's opening balance for the new year.
