PT60 — Time Evaluation Driver (RPTIME00)
PT60 runs the SAP Time Evaluation report RPTIME00. It evaluates employee time and labor data using the selected time-evaluation schema and period, producing time-evaluation results used for time accounts, wage types, quotas, and downstream payroll according to configuration. It is commonly scheduled as a recurring background job and also run manually for testing or recalculation.
This page covers PT60, the Off-Cycle Workbench used for out-of-schedule payroll runs in SAP HCM Payroll. It focuses on the diagnostic side: why the workbench cannot find an eligible employee, when it silently triggers a retro, and how off-cycle results interact with the regular run's lock status.
Published 20 Sept 2026· 622 words
Esta página ainda não está disponível em português.
Purpose
PT60 is the transaction code for the Time Evaluation Driver, report RPTIME00. Time evaluation reads employee master/time data and time events, applies the configured time-evaluation schema, and writes time-evaluation results used by later Time Management and payroll processes. It is not an off-cycle payroll workbench.
When it is used
Organizations commonly schedule RPTIME00 daily so recently recorded time is evaluated before downstream payroll or reporting. Consultants also run PT60 manually for a specific employee, employee group, or evaluation period when testing a time schema, investigating a discrepancy, forcing a controlled recalculation, or forecasting future time results where the configuration permits it.
How to use it in practice
- Select the personnel number or employee population to evaluate.
- Enter the evaluation period and the time-evaluation schema used by the organization.
- Choose the log/display options needed for diagnosis; use a detailed log only for a focused population because it can become large.
- For a retroactive issue, verify the employee's recalculation status/date before forcing a broader recalculation.
- Run in a controlled test or background job, then review the time-evaluation log and resulting balances/wage types before passing the result downstream.
Key data objects
Time evaluation behavior is driven by employee master data, time data, schema configuration, and recalculation status.
- Personnel selection and evaluation period — define which employees/dates RPTIME00 processes.
- Evaluation schema — defines the sequence of time-evaluation rules and operations.
- Infotype 0007 Time Management Status — determines whether and how an employee participates in time evaluation.
- Infotype 0003 recalculation/PDC status — relevant when retroactive time evaluation must restart from an earlier date.
- Time-evaluation result clusters/log — use standard SAP result/log tools rather than attempting to interpret compressed cluster storage with generic table display.
How to prove it in the data
Start with the employee's recorded time data and planned working time for the period, then run or inspect PT60 with the same schema and dates. Use the RPTIME00 log to identify the rule/function that produced the time type, wage type, quota, or error in question. If the expected correction is missing, verify the recalculation date/status and confirm that the rerun actually covered the affected period.
ECC vs S/4HANA
SAP's current HCM support documentation still identifies PT60 as the transaction for RPTIME00 Time Evaluation, including SAP HCM for SAP S/4HANA/Employee Central Payroll-related support content. SuccessFactors Time Tracking can change the architecture and system of record, but PT60 remains relevant where classic SAP Time Evaluation is used.
Common pitfalls and how to diagnose them
- Calling PT60 an off-cycle payroll transaction — PT60 is Time Evaluation; off-cycle payroll uses payroll-specific processes/tools.
- Running a huge detailed log in dialog and creating unnecessary runtime/memory pressure.
- Changing a time record but not recalculating far enough back to include the correction.
- Using the wrong schema or Time Management Status and then diagnosing the resulting evaluation behavior as bad time data.
- Repeatedly rerunning evaluation before correcting the source time/master-data error.
Whose problem this is
Primary ownership is HCM Time Management. Payroll owns downstream payroll interpretation, Basis helps with scheduled-job/runtime capacity issues, and ABAP/time-schema specialists join when a custom rule, operation, function, or enhancement is proven to be involved.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/pt60ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.