PA51 — Display Time Data
PA51 is a display transaction for employee Time Management data. It is used to review time-related infotype records without changing them, such as absences, attendances, substitutions, or other configured time data. Use PA61 or the Time Manager's Workplace for maintenance; PA51 itself is a read-only investigation and verification tool.
This page covers PA51, the list-format display transaction for HR master data, and explains how it differs structurally from PA20 and PA30. The diagnostic focus is on why records appear missing or out of sequence in the list view, and how to trace that back to the underlying infotype table.
Published 20 Sept 2026· 606 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
PA51 provides read-only access to Time Management data for a personnel number. It is designed for time administrators and support consultants who need to inspect recorded time data without the risk of changing it. SAP support documentation lists PA51 among the important Time Management transactions as 'Display time data'.
When it is used
Use PA51 when an absence, attendance, substitution, quota-related record, or other time entry must be verified before changing anything. It is useful when time evaluation or payroll produced an unexpected result and you first need to establish what time data was actually recorded for the employee and period.
How to use it in practice
- Enter the personnel number and the time period relevant to the incident.
- Select the time infotype or data category you need to inspect.
- Review the records chronologically and note subtype, validity dates, hours, and any account-assignment or reason fields relevant to the process.
- Compare the recorded data with the employee's planned working time and the source approval/request where applicable.
- If a correction is required, move to PA61 or the organization's approved time-maintenance application rather than attempting to treat PA51 as an edit screen.
Key data objects
Time Management data is infotype-driven, so the exact tables and fields depend on the record type being displayed.
- Personnel number and evaluation/display period — always match these to the incident date.
- Infotype/subtype — for example Absences (2001), Attendances (2002), or Substitutions (2003), depending on the process.
- Validity dates and hours — verify overlaps, gaps, partial-day values, and cross-midnight scenarios.
- Planned working time context — compare the recorded time with the employee's work schedule when the issue concerns evaluation.
- Source/approval context — where time originated in self-service, CATS, Employee Central, or an interface, verify the upstream record as well.
How to prove it in the data
Use PA51 to establish the read-only business view, then compare the relevant time-infotype record for the same personnel number and date range. For a time-evaluation discrepancy, also review PT60/RPTIME00 logs and the employee's Time Management Status. The proof should show the source time record, the evaluation period, and the resulting time-evaluation/payroll outcome.
ECC vs S/4HANA
PA51 remains part of classic SAP HCM Time Management. In S/4HANA HCM or hybrid SuccessFactors landscapes, the authoritative entry point can differ: Employee Central Time or another cloud application may be the system of record, while PA51 is used to verify replicated backend time data.
Common pitfalls and how to diagnose them
- Using PA51 as if it were broad Personnel Administration history — its purpose is Time Management display.
- Looking at the wrong personnel number or period, especially for concurrent/multiple assignments.
- Assuming a missing backend record means the employee never submitted time — check the upstream cloud/self-service integration where applicable.
- Diagnosing a time-evaluation issue from the time record alone — PT60 schema/status and planned working time can change the result.
Whose problem this is
Primary ownership is HCM Time Management. Integration teams join when the upstream source is Employee Central, CATS, terminals, or another time system; Payroll joins when the issue is visible only after payroll consumes time results.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/pa51ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.