SAP Time Management: Work Schedules, Attendance & Absence Types Explained
A clear, jargon-free walkthrough of how SAP tracks when employees work, when they’re away, and how it all rolls up to accurate, auditable time data — built for HR students and working professionals.
Ask any HR professional what causes the most payroll disputes, and “time data” will be near the top of the list. A single misclassified absence or an incorrectly configured work schedule can throw off attendance records, leave balances, and salary calculations for an entire team. This is exactly the problem SAP Time Management was built to solve — and once you understand its three core building blocks, the whole module clicks into place.
01 The Big Picture: Three Pillars of SAP Time Management
Before diving into configuration details, it helps to see the forest before the trees. SAP Time Management rests on three interconnected pillars, and almost everything else in the module is a variation or extension of these:
Work Schedules
Define when an employee is expected to work — which days, which shifts, and which are holidays or off-days.
Attendance
Record how much time was actually worked — clock-ins, clock-outs, overtime, and shift confirmations.
Absence Types
Capture why an employee wasn’t at work — leave, sickness, training, or any approved time away.
Work Schedule = the plan. Attendance = what actually happened. Absence = the exceptions to the plan. Payroll and reporting depend on all three being accurate and in sync.
02 Work Schedules: The Foundation of Everything
A work schedule is essentially SAP’s answer to the question: “On this specific day, is this employee supposed to be working, and if so, for how long?” Every other time calculation in the system builds on top of this foundation.
How a Work Schedule Is Built
SAP constructs a work schedule in layers, almost like stacking transparent sheets on top of each other:
- Daily Work Schedule (DWS). Defines a single day’s working pattern — start time, end time, and break duration. For example, a standard shift of 9:00 AM to 6:00 PM with a 1-hour lunch break.
- Period Work Schedule. Combines daily work schedules into a repeating weekly or monthly pattern — for instance, Monday to Friday working, Saturday and Sunday off.
- Holiday Calendar. A list of public and organizational holidays specific to a region or location, layered on top of the period schedule.
- Work Schedule Rule. Brings the period work schedule and holiday calendar together into one rule that gets assigned to an employee or group of employees.
Remember the flow bottom-up: Daily → Period → Rule (with Holiday Calendar feeding in). If you can explain this chain in an interview, you already understand 70% of SAP Time Management basics.
03 Attendance: Capturing What Actually Happened
Once the schedule defines the “plan,” attendance data captures the “reality.” This is where SAP tracks actual clock-ins, clock-outs, and time spent on the job — either through time recording terminals, employee self-service, or manual entry by HR/timekeepers.
Two Ways SAP Manages Time Data
| Approach | How it works | Best suited for |
|---|---|---|
| Positive Time Management | Every attendance and absence must be actively recorded; the system calculates nothing by default | Hourly workers, shop floor, shift-based roles |
| Negative Time Management | The system assumes the employee worked the planned schedule unless an exception (like leave) is recorded | Salaried staff, office-based roles |
Most organizations run a hybrid model — negative time management for office staff and positive time management for factory or field employees — all within the same SAP system.
Common Attendance-Related Infotypes
- Infotype 2002 (Attendances): Records actual attendance hours and types.
- Infotype 2011 (Time Events): Captures raw clock-in/clock-out punches from time terminals or biometric devices.
- Infotype 2001 (Absences): Records approved absences that override the planned schedule.
Accurate attendance data isn’t just a compliance checkbox — it’s the single source of truth payroll, overtime calculations, and workforce planning all depend on. — A principle every SAP Time Management consultant learns early
04 Absence Types: Recording the “Why”
Absence types are how SAP categorizes every reason an employee isn’t at work — and each type can carry its own rules for pay, quota deduction, and approval workflow.
Annual Leave
Planned time off deducted from an employee’s yearly leave quota.
Sick Leave
Medical absence, often with certificate requirements after a defined threshold.
Maternity/Paternity Leave
Statutory leave types with specific legal entitlements by country.
Unpaid Leave
Approved absence with no quota deduction but a corresponding pay impact.
How Absence Quotas Work
Every absence type can be linked to an absence quota — a running balance the system tracks and deducts from automatically. For example, if an employee is entitled to 18 days of annual leave per year, SAP maintains that balance, subtracts each approved leave day, and flags when the quota runs low or has been exceeded.
| Component | What it does | Common T‑code |
|---|---|---|
| Work Schedule Rule | Assigns the combined daily/period schedule and holiday calendar to employees | PT01 |
| Absence Type Config | Defines each leave/absence category and its rules | SPRO → Absences |
| Time Evaluation | Runs daily/periodic calculation of attendance vs. schedule vs. absences | PT60 |
| Absence Quota Overview | View or adjust an employee’s leave balances | PT50 |
| Time Statement | Displays an employee’s recorded time data for a given period | PT_QTA00 |
05 How It All Comes Together: A Day in the Life of Time Data
Let’s trace a simple, real-world scenario to see the three pillars interact.
- Monday, the schedule says work. The employee’s Work Schedule Rule marks Monday as a planned working day, 9 AM–6 PM.
- The employee clocks in and out. Attendance data is captured via the time terminal or self-service, recorded under Infotype 2011/2002.
- Wednesday, the employee is sick. An absence is recorded under Infotype 2001, coded as “Sick Leave” — this overrides the planned working day.
- The system runs time evaluation. SAP’s time evaluation engine (via PT60) compares the schedule, attendance, and absence data to compute actual hours worked, any overtime, and quota deductions.
- Payroll picks up the results. The processed time data flows directly into payroll for accurate salary, overtime, and leave-balance calculations.
06 Why This Matters: The Business Case
✅ What Gets Better When Time Management Is Configured Right
- Payroll accuracy: Salary, overtime, and deductions calculate correctly the first time, every time.
- Compliance confidence: Statutory leave entitlements and working-hour regulations are enforced automatically.
- Reduced HR workload: Fewer manual corrections, disputes, and reconciliations at month-end.
- Better workforce visibility: Real-time view of who’s working, who’s away, and why — critical for planning.
- Fair, consistent policy application: The same rules apply uniformly across the organization, with a full audit trail.
07 Common Mistakes to Avoid
Overcomplicating work schedules
Creating too many schedule variants makes maintenance a nightmare — group similar shift patterns wherever possible.
Ignoring the holiday calendar mismatch
Assigning the wrong regional holiday calendar leads to incorrect “working day” flags and payroll errors.
Poorly defined absence quota rules
Unclear accrual or carry-forward rules cause leave balance disputes — test these thoroughly before go-live.
Skipping time evaluation testing
Always test time evaluation with real employee scenarios (late clock-ins, overnight shifts, partial-day leave) before production rollout.
08 Frequently Asked Questions
What’s the difference between attendance and absence in SAP?
Attendance records time an employee was actually present and working (Infotype 2002), while absence records approved time away from work, like leave or sick days (Infotype 2001). Both feed into time evaluation but represent opposite sides of the same coin.
Can one employee have multiple work schedules?
Not simultaneously as an active assignment, but an employee’s Work Schedule Rule can change over time — for example, moving from a day shift to a rotating shift — and SAP maintains the history for accurate historical reporting.
Do I need to run time evaluation for every employee?
Only employees using positive or hybrid time management typically need daily time evaluation. Employees on pure negative time management may only need periodic evaluation, since the system assumes the schedule was followed unless an exception is recorded.
How should HR students start learning SAP Time Management?
Start conceptually: sketch out a simple company’s work pattern (say, Monday–Friday, 9-to-5, with public holidays) and map out what absence types they’d need. Once the logic is clear on paper, exploring the SAP screens and T-codes becomes far easier to follow.
09 Key Takeaways
- SAP Time Management rests on three pillars: Work Schedules (the plan), Attendance (the reality), and Absence Types (the exceptions).
- Work schedules are built in layers — daily, period, holiday calendar, then combined into a Work Schedule Rule.
- Positive and negative time management represent two different philosophies for capturing time data — most organizations use both, depending on employee type.
- Absence types carry their own rules for quota deduction, pay impact, and approval — getting this configuration right prevents leave-balance disputes.
- Time evaluation is the engine that reconciles schedule, attendance, and absence data before it flows into payroll.
