PA61 — Maintain Time Data via Calendar Entry

PA61 is the time management counterpart to PA30, scoped to a fixed subset of infotypes: absences (2001), attendances (2002), substitutions (2003), availability (2004), overtime (2005), and the various quota and time-related infotypes. It presents a monthly calendar per personnel number; clicking a day opens the create screen for the chosen infotype with the begin date pre-filled. The structural fact that explains most of the confusion around it: PA61 is not a separate data store. Every record saved through it lands in the same PA infotype tables (PA2001, PA2002, and so on) that PA30 writes to. The two transactions are different front doors onto identical storage. A record created in PA61 shows up unchanged in PA30, and a record fixed in PA30 shows up unchanged in PA61's calendar the next time it is opened.

Time administrators use PA61 for routine day-by-day entry of absences and attendances when the work is confined to time infotypes and the calendar view speeds up navigation across many days for one employee, or across many employees one day at a time. It is reached for instead of PA30 by anyone whose job is specifically time administration, because the menu is shorter and the calendar avoids retyping dates. It is reached for instead of a self-service Fiori time app when there is no employee-facing leave app deployed, when the administrator is entering data on behalf of the employee, when a correction or backdated entry is needed that self-service does not allow, or when the organization has not yet moved time-off processes to Employee Central and still runs time management on-premise.

In SE16N, open PA2001 or PA2002 and filter on PERNR for the employee, SUBTY for the absence or attendance type in question, and a date range that brackets BEGDA and ENDDA. Sort by BEGDA to spot overlapping intervals visually. Check AEDTM and UNAME to confirm who last touched the record and when, which distinguishes a record entered through PA61 from one entered through PA30, a batch load, or an interface, even though the table content looks identical.

PA61 remains available in S/4HANA on-premise HCM for backend time infotype maintenance; the transaction itself and the underlying infotype tables did not change. Where time off has moved to Employee Central in a SuccessFactors landscape, PA61 typically survives as a backend correction and reconciliation tool used by integration or payroll teams rather than as the primary entry point for employees, since day-to-day leave requests move to the Employee Central time-off process instead.

Functional HCM time management territory first. Basis gets involved only if the issue is a genuine table lock contention or background job scheduling problem tied to time evaluation. A good handover includes the personnel number, infotype and subtype, the exact date range being entered, the full error message text, and whether a time evaluation run was active at the time of the save attempt.

Read PA30 first to understand that PA61 is a restricted view onto the same infotype framework, not a separate application. Read PT60 and PT61 to understand how time evaluation consumes the records PA61 creates and why locking and retroactive recalculation happen. PA20 is useful as the read-only counterpart for checking a record without risking an accidental change. PA40 matters when time infotypes are triggered as part of a personnel action rather than entered standalone.