PA61 — Maintain Time Data
PA61 is the classic SAP HCM transaction for maintaining employee Time Management infotypes. Time administrators use it to create or change records such as absences and attendances for a personnel number. It is a maintenance transaction; PT61 is different and runs the time-statement report RPTEDT00 rather than correcting time data.
This page covers PA61, the time-specific infotype maintenance transaction built around a per-employee calendar view. It focuses on how PA61 relates to PA30 under the hood, the sequence for entering time records, and the diagnostic categories behind the errors time administrators hit most often - overlaps, locking with time evaluation, and quota timing.
Published 20 Sept 2026· 572 words
Esta página ainda não está disponível em português.
Purpose
PA61 maintains employee time data in classic SAP HCM. It provides access to time-relevant infotypes such as absences and attendances and applies the Time Management rules configured for those records. SAP documentation explicitly identifies PA61 as the Maintain Time Data transaction and recommends Time Manager's Workplace for some high-volume or concurrent-employment scenarios.
When it is used
Use PA61 when a time administrator needs to enter, correct, delimit, or review maintainable time-infotype records in the backend. Common examples include correcting an absence, entering an attendance on behalf of an employee, or resolving an exception that cannot be handled in the employee self-service or upstream time system.
How to use it in practice
- Enter the personnel number and confirm the correct assignment where concurrent employment applies.
- Choose the time infotype and subtype required by the business event.
- Review existing records for the date range before creating or changing a record, especially where time constraints can cause collisions.
- Enter dates, times, reason/subtype, and any required account-assignment information.
- Save, then verify whether time evaluation must be rerun or will automatically recalculate the affected period according to configuration.
Key data objects
The precise fields depend on the time infotype being maintained.
- Personnel number and assignment — confirm the correct employee/employment relationship.
- Time infotype/subtype — common examples include 2001 Absences and 2002 Attendances.
- Begin/end date and time — critical for collision checks and valuation.
- Planned working time and Time Management Status — influence later evaluation.
- Quota/account-assignment fields — relevant to absence deduction and attendance costing depending on configuration.
How to prove it in the data
Compare the PA61 record with the corresponding time-infotype data for the same personnel number, subtype, and validity range. If the reported problem is in time evaluation rather than entry, capture the PT60/RPTIME00 log for the same period and confirm Time Management Status and retroactive recalculation settings before changing the time record again.
ECC vs S/4HANA
PA61 remains documented for SAP HCM for SAP S/4HANA and classic HCM environments. In SuccessFactors-led landscapes, Employee Central Time/Time Off or another application may be the system of record, so direct PA61 maintenance should follow the integration and data-ownership design rather than becoming an unofficial bypass.
Common pitfalls and how to diagnose them
- Creating overlapping time records instead of changing or delimiting the correct existing record.
- Correcting backend data that is owned by an upstream Employee Central or self-service process, causing the next replication to overwrite the change.
- Assuming a saved time record immediately changes payroll results — time evaluation and payroll processing may still need to run.
- Confusing PA61 with PT61: PA61 maintains time data; PT61 is the RPTEDT00 time-statement report.
Whose problem this is
Primary ownership is HCM Time Management. Payroll becomes involved when valuation/payroll results are wrong, Security for personnel/infotype authorization, and integration teams when the authoritative time record originates outside the SAP HCM backend.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/pa61ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.