HR306 – Configuration of Time Recording — Lesson 2: Attendance and Absence Types, Counting Rules, Day Rules, Collision Checks, and Recording Interfaces

Learning Objectives

• Explain the SAP structures, data, settings, roles, and dependencies governing attendance and absence configuration.
• Perform and validate counting, collision, and recording controls using reviewable system evidence.
• Evaluate the condition where an absence is recorded but quota and payroll results are wrong because counting classes, deduction priorities, work schedules, and time-evaluation rules conflict and select proportionate corrective action.

Detailed Topics

• Attendance and Absence Types applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Counting Rules applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Day Rules applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Collision Checks applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• and Recording Interfaces applied to the course scenario, expected SAP behavior, dependencies, and evidence.

Instructor Demonstration

The instructor traces an HR time team configuring consistent working-time rules for varied employee groups and operational schedules. The walkthrough connects navigation, configuration or process logic, system messages, and evidence captured in the HR306 time-recording configuration, test, and reconciliation workbook. It also tests the exception where an absence is recorded but quota and payroll results are wrong because counting classes, deduction priorities, work schedules, and time-evaluation rules conflict.

Hands-On Exercise

Complete a controlled SAP exercise covering Attendance and Absence Types, Counting Rules, Day Rules, Collision Checks, and Recording Interfaces and preserve the verified result in the HR306 time-recording configuration, test, and reconciliation workbook.

1. Confirm scope, prerequisites, master data, roles, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, transactions, outputs, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, and handover actions.

Scenario Analysis

• Identify which object, rule, setting, or process step most strongly influences attendance and absence configuration.
• Compare two defensible responses and explain business, technical, control, and support trade-offs.
• Determine how the HR306 time-recording configuration, test, and reconciliation workbook should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected SAP behavior first differs from the observed result. Check master data, configuration sequence, authorization, integration, status, and transaction evidence separately. Treat “an absence is recorded but quota and payroll results are wrong because counting classes, deduction priorities, work schedules, and time-evaluation rules conflict” as a hypothesis until system settings, logs, documents, and outcomes confirm the cause.

Validation Checklist

• Required SAP structures, master data, roles, settings, and dependencies are present.
• The HR306 time-recording configuration, test, and reconciliation workbook connects each conclusion to objective, reviewable evidence.
• Normal processing, the boundary condition, integration behavior, and exception were tested.
• Corrections, ownership, retest criteria, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Attendance and Absence Types, Counting Rules, Day Rules, Collision Checks, and Recording Interfaces, explain the resulting SAP behavior, and defend the outcome through the HR306 time-recording configuration, test, and reconciliation workbook.