Professional Documents
Culture Documents
Time Evaluation
Time Evaluation
Applies to:
SAP ERP 6.0 (SAP HR)
Summary
This document helps a user to understand different types of Time Evaluation and important Infotypes
required as pre-requisite to implement the same. The internal process flow during Time Evaluation run is
explained which is followed by details of internal and cluster B2 tables to store the results.
Author(s): Pranav Prajapati
Company: Infosys Technologies Ltd
Created on: 06 August 2007
Author Bio
Pranav Prajapati is a certified SAP HR functional consultant working with Infosys Technologies Ltd. His
areas of interest are Time Management and Payroll. He was involved in Time Evaluation schema
development for an extended time while working on SAP platform.
© 2007 SAP AG 1
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
Table of Contents
Applies to:................................................................................................................................... 1
Summary .................................................................................................................................... 1
Author Bio................................................................................................................................... 1
What is Time Evaluation?............................................................................................................ 4
Time Evaluation Schema......................................................................................................... 4
Types of Time evaluation......................................................................................................... 4
Recording, Evaluating and Using time data.............................................................................. 4
Recording Time data............................................................................................................ 4
Evaluating Time data............................................................................................................ 5
Using Time data................................................................................................................... 5
Infotypes in Time Evaluation ....................................................................................................... 6
Required Infotypes .................................................................................................................. 6
Optional Infotypes.................................................................................................................... 6
Time Management Infotypes.................................................................................................... 6
Actual Times ........................................................................................................................ 6
Quotas................................................................................................................................. 6
Changes to Planned specifications....................................................................................... 7
Time Accounts correction..................................................................................................... 7
Planned Working Time (0007) ................................................................................................. 7
Work Schedule Rule ............................................................................................................ 7
Time Management status..................................................................................................... 7
Time Transfer Specifications Infotype (2012) ........................................................................... 7
Process Flow in Time Evaluation execution................................................................................. 9
Define Employee Groupings .................................................................................................... 9
Provide Time data ................................................................................................................. 10
Error Check for the day.......................................................................................................... 10
Calculation of Actual working time and overtime .................................................................... 11
Select Time Wage types........................................................................................................ 11
Compensate Overtime wage types ........................................................................................ 11
Manage Time Accounts ......................................................................................................... 11
Final Processing.................................................................................................................... 11
How to run Time Evaluation Driver RPTIME00? ........................................................................ 12
© 2007 SAP AG 2
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
© 2007 SAP AG 3
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
Time Evaluation, performed by Time Evaluation report RPTIME00, evaluates recorded employee time data
in several processing steps, which are carried out in a defined sequence.
Time Evaluation is generally run once daily and it is a scheduled over night job. Time Evaluation can be run
for an individual employee or for group of employees. It can be run for past period or for a future period.
Evaluating future periods can be useful in situation when it is required to determine an employee's
anticipated absence entitlements when absence quotas are accrued automatically.
Time Evaluation is done according to Time Evaluation Schema (or Personnel Calculation Schema) passed
as input parameter to the RPTIME00.
Recording Actual times: In this method employee’s all working times and absence times are recorded. This is
recorded in Infotype Time Events (2011). The Time Evaluation which uses all actual recorded time is called
Time Evaluation with clock times (TM00) or just Positive Time Evaluation
Recording only deviation from PWS: In this method only times that represent exceptions from the employee’s
planned work schedule are reported. Like absence due to illness, Doctor’s appointment, attending a training
or Leave. The Time Evaluation which uses only exceptions is called Time Evaluation without clock times
(TM04) or just Negative Time Evaluation
© 2007 SAP AG 4
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
© 2007 SAP AG 5
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
Required Infotypes
Following Employee master data Infotypes must be maintained if time evaluation is to be implemented:
Time Recording Information Infotype (0050) is mandatory only if time recording system is used. Time Events
Infotype (2011) is mandatory only when Time Evaluation with clock times method is used for Time Evaluation
Optional Infotypes
Following Employee master data Infotypes are optional:
1) Basic Pay (0008)
2) Date Specifications (0041)
Actual Times
Absences (2001)
Attendances (2002)
Overtime (2005)
Time Events (2011): Recorded time events (i.e. check in and check out at time recording terminal) are
imported into this Infotype. This is used only when Time Evaluation with clock times is implemented
Quotas
Attendance Quotas (2007)
Absence Quotas (2006)
© 2007 SAP AG 6
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
© 2007 SAP AG 7
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
During Time Evaluation run, time balances are formed for Time Types according to calculations made. Time
transfers are used to make changes to the time balances thus created based on value entered in Infotype
2012. This means that in exceptional cases changes the results of time evaluation, as desired.
You transfer times by choosing a particular time transfer type. Time transfer types are subtypes of the Time
Transfer Specifications infotype (2012).
© 2007 SAP AG 8
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
Time Evaluation is done according to Time Evaluation Schema (or Personnel Calculation Schema) send as
input parameter to the RPTIME00. Time Evaluation Schema defines sequence in which the time evaluation
steps will be processed.
Time Management Schema is divided in to three parts known as blocks: Initialization, Day Processing and
Final Processing.
Final Processing
The sequential processing during Time Evaluation Schema execution can be divided in to following –
© 2007 SAP AG 9
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
Personnel Calculation Rule. Employee data from Organizational Assignment (0001) is used to define
groupings.
Groupings, for each employee and time evaluation run, are set like-
Time Wage type selection group
Time Type determination group
Absence Valuation
Time balance rule group
For the day being processed, Time data from following Infotypes are imported -
Absences (2001)
Attendances (2002)
Substitution (2003)
Availability (2004)
Time Transfer Specifications (2012)
Time Events (2011) - Only if Time Evaluation with Clock times is used
SAP delivered Personal Calculation Rule TE20 could be used for the same. This rule can be accessed in
transaction PE02 with PCR name as TE20.
© 2007 SAP AG 10
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
Each Attendance and Absence code is assigned a Processing Type, which is used to group attendances and
absences together which are processed alike (Refer section 6.4) All Attendance/Absence with similar
Processing type are grouped together in same Time Types.
Final Processing
Final Processing block is processed once for each employee for each evaluation. The system check for error
free processing and stores results from Internal tables to Cluster B2 tables at the end of processing. (Refer
section 4.3 & 4.4)
© 2007 SAP AG 11
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
This is SAP delivered standard RPTIME00 program. Following are the input parameters that can be entered-
Personnel Number: RPTIME00 can be executed for one Pernr, a Pernr range or on whole population.
Evaluation Schema: This field will be populated with customized schema name which has to be used for
evaluation. A schema defines sequence of processing steps.
Time Statement Variant: Specifies whether the evaluation results are displayed, and how they are laid out.
Layout for log: Determines which user settings are used to display the time evaluation log.
Forced recalculation as of: Time evaluation is recalculated as of this date (inclusive) at the latest. (Refer to
Appendix 7.2)
Evaluation up to: Time evaluation runs up to and including the date entered.
Program Option:
Display log
Test run (no update)
Stop at function / operation BREAK
Stop at fixed positions in time evaluation
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
© 2007 SAP AG 12
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
Note: All the processing steps and sub steps of the evaluation schema will be displayed on the screen if
Display log is checked. If Test run (no update) is checked, the Time Evaluation will run and the changes will
not be written in the data base tables known as RPCLSTB2 or Cluster B2.
When the Display log option is checked, RPTIME00 creates following screen after execution-
The out put data for each day evaluated for each successful Pernr are stored in ZES, SALDO and ZL tables.
Those tables can be viewed by expanding particular section as shown below-
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
© 2007 SAP AG 13
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
Personnel Numbers rejected: All Pernrs who are rejected and could not be included in RPTIME00 run are
listed here.
Messages: All Time Evaluation messages that should be attended by Time Administrator are listed here.
TIP: The system imports time data which has been entered manually for the day to be evaluated. i.e. Time
data available in Infotypes 2001, 2002 etc.
TZP: Planned Working Time data from the employee’s Daily Work Schedule is transferred to this table for
the current day. Substitutions from infotype 2003 that replace the employee’s daily work schedule are
also imported if any.
TES: All Time balances of the day are finally totaled in to this table. This balances are finally transferred to
out put table ZES in Cluster B2
DZL: Time Wage Types created from Planned working times are stored in to this table
© 2007 SAP AG 14
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
ZML: Time Wage Types created from Over time wage types are stored in this table.
Time Wage type data from DZL and ZML are transferred to out put table ZL in Cluster B2.
ZES: Daily Time Balances are transferred to the ZES (individual daily balances) according to the
specifications in the Time Types table
SALDO: Time Balances are cumulated for a time evaluation period in SALDO.
ZL: All Time Wage Types of each day processed are stored in this table.
ALP: Stores data related to differential payment.
C1: Stores data related to Cost distribution.
FEHLER: Stores custom defined Messages that appears during Time Evaluation run.
The data stored in ZES, SALDO and ZL has unit as Number of Hours. Report RPCLSTB2 (Display Time
Evaluation Results (Cluster B2) Transaction code PT66) can be used to view all the results of time
evaluation, and the basic data and time data for each time evaluation period stored in Cluster B2.
The archiving is employee-specific. As archived periods cannot be recalculated, only periods that are no
longer relevant to a recalculation are archived. When archiving the data, the transaction uses a buffer of an
evaluation period to guarantee that any possible recalculations are taken into account if the previous day
assignment is changed. The archiving transaction limits the earliest recalculation date by changing the
Earliest personal recalculation date field in the Payroll Status infotype (0003).
Report RPCLSTB2 (Display Time Evaluation Results (Cluster B2) Transaction code PT66) can used to view
archived results if necessary access permissions are set up.
© 2007 SAP AG 15
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
Time Wage Types generated in Time Evaluation run are transferred to SAP Payroll for third party payroll
system to calculate employee gross pay. Time Wage Type data in tables ZL, ALP and C1 in Cluster B2
become the input for Payroll run, which acts as interface between Time Evaluation and Payroll.
In most scenarios Time Evaluation Period (generally monthly) and Payroll Period (Weekly, Bi-weekly or Semi
monthly) has different values. Also Time evaluation is generally run till current date while Payroll might runs
for the future days i.e. Running payroll on 5th of the month for the entire month. In this case If the payroll is
run before the end of the time evaluation period, time evaluation passes on only the time wage types
generated up to this point. For the rest of the payroll period, Payroll generates time wage types on the basis
of the work schedule and any existing Time Management Infotypes for the period that has not been
evaluated.
If time Infotypes such as absences or attendances are recorded for a past payroll period that has already
been accounted, time evaluation can set a retroactive accounting run in the Earliest MD change field in the
Payroll Status infotype (0003).
If third party Payroll is used, The Interface Toolbox transaction (PU12) is used as an export program. The
export program retrieves the data from the internal table ZL in cluster B2 to supply the third-party payroll
system. The wage types are written to a sequential file, which can then be imported into the third-party
system.
© 2007 SAP AG 16
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
Appendix
If it is an Unscheduled day (Planned working hours = 0), it is classified and Day off
If it is Scheduled day (Planned working hours != 0), whether the employee has to work and whether he/she
will be paid will depend on the day type.
If there are no Retroactive changes relevant to a recalculation, Time Evaluation returns to the day next to the
last day evaluated without errors. It uses this day to start Evaluation from. If you want to evaluate a period
before the last day to be evaluated without errors, you can use the RPTIME00 parameter Forced
recalculation as of to reset manually the first day from where you want to start the evaluation.
Time Type
A Time Type is a technical name for duration, and assigns it a concrete meaning. Time types that are related
in a business administration context can be cumulated during time evaluation to form balances. Time Type is
central object in Time Evaluation. These are used to group durations, which are to be evaluated equally, and
give them a meaning.
© 2007 SAP AG 17
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
IMG: Time Management > Time Evaluation > Time Evaluation Settings > Define Time Types
Processing Type
Each Attendance and Absence code is assigned a Processing Type, which is used to group attendances and
absences together which are processed alike. Following are example-
IMG: Time Management > Time Evaluation > Time Evaluation with clock times > Time Wage Type selection
and Over Time compensation > Define Processing Types
© 2007 SAP AG 18
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
Related Content
Time Evaluation
http://help.sap.com/erp2005_ehp_02/helpdata/en/8a/9852ee46c411d189470000e829fbbd/frameset.
htm
The Time Management Status
http://help.sap.com/erp2005_ehp_02/helpdata/en/db/0e8ca876d011d5b3040050da4ce665/frameset.
htm
Public Holiday Calendars
http://help.sap.com/erp2005_ehp_02/helpdata/en/8a/98472a46c411d189470000e829fbbd/frameset.
htm
© 2007 SAP AG 19
Time Evaluation RPTIME00 Report – Prerequisites, Process Flow and Storing results on Cluster B2
This document may discuss sample coding or other information that does not include SAP official interfaces
and therefore is not supported by SAP. Changes made based on this information are not supported and can
be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods
suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of
this technical article or code sample, including any liability resulting from incompatibility between the content
within this document and the materials and services offered by SAP. You agree that you will not hold, or
seek to hold, SAP responsible or liable with respect to the content of this document.
© 2007 SAP AG 20