How to Run Time Evaluation: SAP PT60

By : Kaelyn Flynn Kaelyn Flynn
Hours Updated

⚡ Smart Summary

Running Time Evaluation in SAP with transaction PT60 processes each employee’s recorded attendances and absences into time wage types for payroll. This resource explains what time evaluation does, its prerequisites, schemas, the PT60 process, and how to resolve common errors.

  • ⚙️ Purpose: Time Evaluation converts recorded attendances and absences into time wage types and updates quotas.
  • 🔑 Transaction PT60: PT60 launches the RPTIME00 program that evaluates each selected employee.
  • ✅ Prerequisites: A valid work schedule, time management status, and evaluation schema must be in place first.
  • 🔀 Schemas: TM00 handles positive time recording; TM04 handles negative time recording.
  • 📄 Results: A processing log shows successes and errors; view results later with transaction PT66.
Read More

Run SAP HR Time Evaluation with PT60

Time Evaluation

Time Evaluation processes the employees’ attendance at work and absences from work to make sure they are paid accordingly.

  • It evaluates the employee’s actual working time and absences.
  • It calculates time-related payments.
  • It updates absences quotas.
  • It generates time wage types which are transferred to the Payroll Program.

Before executing the Payroll Program, all employees need to be processed successfully by the Time Evaluation Program. But time evaluation needs to run for relevant employees. Some employee populations may not have time evaluation requirements.

Run Time Evaluation

Prerequisites for Running Time Evaluation

Before you execute Time Evaluation with PT60, a few configuration and master-data conditions must be in place. Missing any of them is the most common reason the run fails or skips employees:

  • Time Management status: Infotype 0007 (Planned Working Time) must set a time management status that requires evaluation, such as status 1 (positive) or 9 (time evaluation of planned times).
  • Work schedule: Each employee needs a valid work schedule rule so the system knows their planned hours.
  • Time data: Attendances, absences, and any overtime should already be recorded through infotypes 2001, 2002, 2005, and related types.
  • Evaluation schema: A schema such as TM00 or TM04 must be assigned and active.
  • Personnel numbers: The employees to be processed must be selectable and not locked by another user.

Once these prerequisites are met, Time Evaluation can process each employee cleanly and produce reliable time wage types for payroll.

Understanding Time Evaluation Schemas

A time evaluation schema is the program logic that PT60 follows when it processes an employee’s time data. SAP delivers standard schemas that most companies copy and adapt to local rules. The schema is executed by the RPTIME00 program and is made up of functions and personnel calculation rules that run in sequence.

The two most widely used standard schemas are TM00 and TM04. TM00 is designed for positive time recording, where every attendance and absence is captured, often from a time clock or terminal. TM04 is designed for negative time recording, where only deviations from the planned work schedule—such as leave or overtime—are entered, and normal working hours are assumed automatically.

Choosing the correct schema is important because it determines how the system forms time wage types, updates absence quotas, and reacts to errors. When you enter the schema in PT60, make sure it matches the time management status set for the selected employees.

RELATED ARTICLES

Process to Run SAP Time Evaluation

Step 1) To Run Time Evaluation, Enter PT60 in the SAP Transaction Code Box

Run Time Evaluation

Step 2) In the next SAP Screen

  1. Enter Personnel Number
  2. Enter Evaluation Schema
  3. Enter Evaluation Up to Date (The date until which Time Data will be evaluated)

Step 3) Enter any other selection field if required. Click Execute

Run Time Evaluation

Step 4) Time should be evaluated and a log must be displayed.

Run Time Evaluation

You can view the Time Results Generated, using transaction PT66

Time Evaluation Statuses and Common Errors

After a PT60 run, each employee receives a processing status that tells you whether evaluation finished successfully. Reviewing these statuses is essential before you start payroll.

Typical outcomes include:

  • No errors – the employee’s time data was evaluated fully and time wage types were generated.
  • Errors – the run stopped for that employee, usually because of missing or conflicting time data, and must be corrected and rerun.
  • Recalculation – a retroactive change was detected, so the system re-evaluates from an earlier date.

Common causes of errors are an incomplete work schedule, an absence recorded outside its quota, overlapping time entries, or a missing time management status on infotype 0007. To fix them, correct the underlying master data or time record, then rerun PT60 for the affected personnel numbers. Because payroll can only run for employees who have been evaluated without errors, resolving these issues promptly keeps the whole time-to-payroll process on schedule.

FAQs

RPTIME00 is the standard SAP program that performs time evaluation. It is called by transaction PT60 and executes the assigned schema, such as TM00 or TM04, to process attendances, absences, and quotas for each selected personnel number.

PT60 runs time evaluation and processes an employee’s time data. PT66 (Time Evaluation Results) displays the cluster B2 results that PT60 generated, letting you inspect time balances, wage types, and quotas without reprocessing anything.

TM00 supports positive time recording, where all attendances and absences are captured, often from a time clock. TM04 supports negative time recording, where only deviations from planned working hours are entered and normal hours are assumed automatically.

Infotype 0007, Planned Working Time, holds the work schedule rule and the time management status. The status—for example 1 for positive or 9 for planned times—tells PT60 whether and how to evaluate the employee.

Yes. Time evaluation is usually scheduled as a background job so it runs for all relevant employees overnight. You define a variant with the schema and date range, then schedule the RPTIME00 program in transaction SM36.

Retroactive time evaluation happens when a change is made to past time data or master data. SAP detects the earliest changed date and re-evaluates from that point, ensuring balances and wage types stay correct for later payroll runs.

AI can read time evaluation logs, group recurring error messages, and point to likely causes such as missing schedules or quota gaps. This speeds diagnosis, though the fixes should be applied and rerun by an administrator in SAP.

GitHub Copilot and similar Copilot assistants can draft ABAP snippets, SAP GUI scripts, and variant setups that automate PT60 batch runs and log parsing. Machine learning can also flag anomalies, but administrators should test each generated routine before running it in production.

Summarize this post with: