HR310 TimeEvaluationWithClockTimes

HR310 Time Evaluation With Clock
Times
HR310
Release 640 04/06/2006

0
HR310 Time Evaluation With Clock Times
HR310
Time Evaluation
With Clock Times
SAP AG 1999
R/3 System
Release 4.6C
December 2000
Material number 50043343
0.2
Copyright
Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in
any form or for any purpose without the express permission of
SAP AG. The information contained herein may be changed
without prior notice.
SAP AG 2004
Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,
iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are
trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other
countries all over the world. All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National product specifications
may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and
SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP
Group products and services are those that are set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as constituting an additional warranty.
0.3
Human Resources 4.6 (1)
Level 2 Level 3
CA500 2 days
HR305 3 days CATS The Cross
HR051 1 day Configuration of Application Time Sheet
see HR2
Master Data
Human Resources
Essentials I HR250 2 days
HR306 4 days HR310/311 5 days
Employee Self-Service
Configuration of Time Time Evaluation
Recording
HR580 3 days
HR052 2 days Reporting in Human
Resources
Human Resources HR505 3 days HR506 2 days
Essentials II Organizational Advanced
Management Organizational HR307 2 days
Management
Configuration of HR
HR325 3 days HR520 2 days System Controls
HR053 2 days Benefits Administration Shift and Workforce
Planning
HR540 3 days
Human Resources HR350 5 days
Essentials III Compensation
Management Programming in HR
HR510 3 days
Personnel Development HR530 3 days
HR515 3 days Technical topics in
Training and Event Human Resources
Management
SAP AG 2001
0.4
Human Resources 4.6 (2)
Level 2 Level 3
HR051 1 day HR305 3 days HR390 2 days

Configuration of Introduction
Human Resources Master Data to Payroll
Essentials I
HR400 5 days
Payroll Configuration
HR052 2 days
Human Resources HR490 4 days
Essentials II
Incentive wages
HR053 2 days
Human Resources
Essentials III
Note:
Please note our country specific curriculum and our curriculum
for release 4.6B.
SAP AG 1999
0.5
Course Prerequisites
Required:
HR306 Time Recording
Recommended:
HR050 Human Resources and
HR305 Master Data
SAP AG 1999
0.6
Target Group
Audience:
Members of a project team who are implementing R/3 Time Evaluation
SAP consultants and SAP partners who work with R/3 Time Management
Duration: 5 days
SAP AG 1999
SAP AG
Notes to the user

The training materials are not teach-yourself programs. They complement the course instructor's
explanations. Your material includes space for noting down this additional information.
There may not be enough time to do all the exercises during the course. The exercises are intended to be
additional examples that are dealt with during the course. Participants can also use them to deepen their
knowledge after the course.
1
Course Overview
Contents:
Course Goals
Course Objectives
Course Content
Course Overview Diagram
SAP AG 1999
(C) SAP AG HR310 1

1.2
Course Goals
This course will prepare you to:

Understand SAP Time Evaluation and its role
in the business processes of human resources
Customize time evaluation to suit your
own requirements
SAP AG 1999
SAP AG
(C) SAP AG HR310 2

1.3
Course Objectives
At the conclusion of this course, you will be able to:

Describe the data flow within the time
evaluation process
Explain the technical flow of time evaluation
Modify the standard time evaluation schema
Modify standard personnel calculation rules
and create new ones
Customize tables
SAP AG 1999
SAP AG
(C) SAP AG HR310 3

1.4
Course Content
Preface
Unit 1 Course Overview

Unit 2 Business Overview of Time Evaluation
Unit 3 Time Evaluation in the SAP System
Unit 4 Concept of the Time Evaluation Driver RPTIME00
Unit 5 Time Evaluation Messages
Unit 6 Customizing Time Evaluation
Unit 7 Data Collection in Time Evaluation
SAP AG 1999
(C) SAP AG HR310 4

1.5
Course Content - Continued
Unit 8 Operations as Tools of Time Evaluation

Unit 9 Personnel Calculation Schema TM00
Unit 10 Special Solutions
Unit 11 Alternative Time Evaluation Schemas
Unit 12 Integration with Payroll
Unit 13 Time Statement and Reporting
Appendix
SAP AG 1999
(C) SAP AG HR310 5

1.6
Business Overview of Time Operations as Tools ofTime

Evaluation Evaluation
Time Evaluation in the SAP System Personnel Calculation Schema TM00
Concept of the Time Evaluation Special Solutions

Driver RPTIME00
Time Evaluation Messages Alternative Time Evaluation

Schemas
Customizing Time Evaluation Integration with Payroll
Data Collection in Time Evaluation Time Statement and Reporting
SAP AG 1999
(C) SAP AG HR310 6

2
Business Overview of Time Evaluation
Contents:
Business process of time evaluation
SAP AG 1999
(C) SAP AG HR310 1

2.2
Business Overview of Time Evaluation: Objectives
At the conclusion of this unit, you will be able to:

Describe what time evaluation is and
what it does
Explain how time evaluation is integrated into
human resources business processes
Describe the different time evaluation methods
SAP AG 1999
SAP AG
(C) SAP AG HR310 2

2.3
Business Overview of Time Operations as Tools of Time


Driver RPTIME00
Time Evaluation Messages Alternative

Time Evaluation Schemas
SAP AG 1999
(C) SAP AG HR310 3

2.4
Recording and Evaluating Time Data
Recording... ...evaluating... ... and using time data
Manage time
accounts
Print time
statements
Time sheet
Issue messages
Self-service for postprocessing
Time
.
.
.
.
.
.
administrator
.
.
SAP Time Evaluation Create wage types

for Payroll
Time recording
Run evaluations and
terminals
compile statistics
SAP AG 1999
With the SAP Time Management component, you can use various systems and methods for recording
personnel times, such as working times, business trips, leave, or substitutions:
Online entry by the time administrator
Using front-end time recording systems
Using the SAP Cross-Application Time Sheet (CATS)
Using self-service applications such as Web applications or touch-screen systems
The main objective of time evaluation is to check and classify the recorded personnel times and to
valuate them automatically. It focuses on the checking of working time provisions, the administration of
time accounts, and the formation of wage types for determining gross wages in Payroll. Messages
concerning any special situations that may have occurred, such as missing attendance times, inform time
administrators that postprocessing is required.
(C) SAP AG HR310 4

2.5
Roles for the Time Evaluation Environment
Organized centrally
HR Administrator
Time
Supplements time and labor data
Time and Labor Management
with data relevant for payroll
Analyst Specialist
Creates reports on time Ensures time management
and labor data system runs smoothly
Time Supervisor: Department head,

project leader, foreman
Organized decentrally
Checks and approves time and labor data
Delegates time management tasks:
Shift Planner: Time Administrator:

Scheduler, foreman Secretary, shop-floor
Employee supervisor, foreman
Plans working times,
Records own time data using Records and administrates
shifts, and time off
time sheet, time recording time and labor data
subsystem, and so on
SAP AG 1999
The following roles are relevant for time evaluation where time management is organized in the
individual departments of a company:
Time Management Specialist (Role SAP_HR_PT_TIME-MGMT-SPECIALIST): The Time

Management Specialist is responsible for ensuring that the time management system runs smoothly, and
is familiar with the technical side of the SAP System. His or her duties include making periodically
recurring settings, maintaining interfaces to other systems and SAP applications, and supplementing HR-
specific Customizing, as required.
Time Administrator (Role SAP_HR_PT_TIME-ADMINISTRATOR, composite role SAP_WP_TIME-

ADMINISTRATOR): In the time evaluation environment, Time Administrators process the messages
issued during time evaluation. They check that working time regulations are adhered to and they create
reports, to inform their superiors or to supply information on the status of time-off accounts, for
example.
Time Supervisor (Role SAP_HR_PT_TIME-SUPERVISOR): The Time Supervisor is responsible for

the time and labor data of the employees assigned to him or her. In the time evaluation environment, the
Time Supervisor regularly monitors the amount of overtime worked in the department, creates reports,
and checks employees' time accounts.
(C) SAP AG HR310 5

Employee (Composite role SAP_WP_EMPLOYEE): Employees use Employee Self-Service
applications and MiniApps to check the current status of their time accounts or to display the time
statement, for example.
(C) SAP AG HR310 6

2.6
Business Transactions Using Time Evaluation
SAP Time Employee

Evaluation
Time
Set up working Administrator
time provisions Individual
Time Supervisor departments
Record current Payroll
Customizing time data HR controlling
Evaluate times
Time Time Update time
Management Administrator accounts
Specialist Issue messages
Employee Postprocess
Time
time data
Management Monitor
.
M AR K
DEU TS CHE
MAR K
Specialist Inform employees

DEU TS CHE
M AR K
DEU TS CHE
M AR K
Use the results
SAP AG 1999
When new employees are hired, they are assigned a work schedule. The work schedule depicts the
working times.
Employees record their attendance times using self-service applications, such as time recording
terminals or an intranet application.
The time administrators modify employees' personal work schedules to take account of any short-term
changes, and they record absences such as leave or special absences in the SAP System.
Time evaluation in the SAP System evaluates employees' time data overnight. It compares employees'
times to internal company policy and legal regulations. The SAP System manages time accounts,
determines approved overtime, accrues absence entitlements, and forms wage types and bonus wage
types. It generates messages to document special situations that occur during the evaluation.
The next morning, time administrators follow up any messages using the message processing function in
the Time Manager's Workplace. They grant subsequent approval for overtime or enter any missing time
postings.
At the end of the month, employees receive a statement detailing their time accounts, or they use Web
applications to check their account balances.
The results of time evaluation form the basis for gross payroll, and are used to form statistics and
monitor data.
(C) SAP AG HR310 7

2.7
In Which Format Should Times Be Recorded?
Time evaluation with clock times

Attendance type 0800
Time 08:00 17:00
07:55 Clock-in
17:02 Clock-out
Time evaluation without clock times

Attendance hours 8.00
07:55 Clock-in
= 8.1166 hrs
17:02 Clock-out
SAP AG 1999
Time evaluation can use either the actual length of time worked (for example, 8.1166 hours) or the
clock-in and clock-out times (for example, 07:55 to 17:02). If you implement time evaluation based on
clock times, you can also perform the following business tasks:
You can check working time provisions that determine, for example, which start and end times and
break times employees must abide by.
You can issue and evaluate overtime approvals that relate to specific times of day.
SAP Time Evaluation provides several standard processing methods, each responding to specific
business requirements.
(C) SAP AG HR310 8

2.8
Which Times Should Be Recorded?
Recording all times
Attendance 08:00 11:00
Doctor's appt 11:00 14:00
Attendance 14:00 17:00
Recording only deviations

from the work schedule
Doctor's appt 11:00 14:00
SAP AG 1999
There are two different methods of time data recording:

Recording all times
If you use this method, all employees' working times and absence times are recorded.
Recording only work schedule deviations
If you use this method, only times that represent and exception to an employee's work schedule are
recorded, such as absence due to illness, changes to planned specifications (for example, attendance at
a training class), or leave.
The different methods affect which functions time evaluation performs. For example, you can only set
up complex regulations for overtime if you record all times.
(C) SAP AG HR310 9

2.9
Business Overview of Time Evaluation: Summary
You have learned what time evaluation is

and what it does
You have learned how time evaluation is integrated
into human resources business processes
You know which time evaluation methods are
supported in the SAP System
SAP AG 1999
SAP AG
(C) SAP AG HR310 10

3
Time Evaluation in the SAP System
Contents:
Basics and prerequisites for time evaluation
SAP AG 1999
(C) SAP AG HR310 1

3.2
Time Evaluation in the SAP System: Objectives

Explain what data is required in time evaluation,
and why
Describe the relationship of the different time
evaluation methods
How tasks are distributed between the time recording
system and the SAP System
SAP AG 1999
SAP AG
(C) SAP AG HR310 2

3.3
Business Overview of Operations as Tools of Time

Time Evaluation Evaluation

Driver RPTIME00

Schemas
Data Collection in Time Evaluation

Time Statement and Reporting
SAP AG 1999
(C) SAP AG HR310 3

3.4
Time Evaluation in the SAP System: Business
Scenario
Create employee master data
Set up working time provisions
Record time data
Upload time events from

time recording system
Evaluate time data
SAP AG 1999
(C) SAP AG HR310 4

3.5
Overview of the Master Data Infotypes
Planned Working Time (0007)

12
11
1
10
2
9
3
8
4
7
6
5
Organizational
Assignment (0001)
Time Recording
Information (0050)
Personal Data (0002)
SAP AG 1999
The following master data infotypes must be maintained if you work with time evaluation.
Organizational Assignment (0001)
Personal Data (0002)
Planned Working Time (0007)
The following master data infotypes are optional:
Basic Pay (0008)
Date Specifications (0041)
Employees' leave entitlement is managed in the Absence Quotas infotype (2006).
The Time Recording Information infotype (0050) is mandatory if you:
Use a time recording system
Evaluate time variables from the infotype in time evaluation.
(C) SAP AG HR310 5

3.6
Planned Working Time Infotype (0007)
le
sch edule ru When is the employee scheduled
Work to work?
s
emen t statu Does the employee participate
anag
Time M in time evaluation, and how should
his or her times be evaluated?
or ki n g week How is the employee's working

working
W week defined?
SAP AG 1999
The Planned Working Time infotype (0007) defines employees' planned working time.
The work schedule rule describes the relationship to the work schedule. In turn, working times and
breaks are defined in the work schedule.
The Time Management status indicates whether employees are permitted to take part in time evaluation,
and in which form.
Possible values:
Time Management status:
0 = No time evaluation; time wage types are formed by Payroll
1 = Time evaluation of actual times
2 = Time evaluation (PDC)
7 = Time evaluation without integration to Payroll; time wage types are formed by Payroll
8 = External services
9 = Evaluation of planned times
(C) SAP AG HR310 6

3.7
What the Time Management Status Signifies
How and where is the employee's time data processed?
Time Evaluation Payroll
1
.
.
Integration with
.
.
.
.
Payroll
9
.
Recording all times
2
Recording
deviations to Time data processing
the work schedule
in Payroll
7 Time evaluation
without Payroll
0 No time evaluation
.
.
.
.
integration
.
.
7
.
.
8 Evaluation of external
services
Time evaluation
without Payroll
integration
SAP AG 1999
The Time Management status in the Planned Working Time infotype (0007) has a fundamental
significance for time evaluation: It determines whether and how an employee is processed in time
evaluation.
Processing employee in time evaluation and transferring the time wage types formed to Payroll:
Time evaluation (actual) (1) and Time evaluation (PDC) (2): All times are recorded for the employee.
Time evaluation of planned times (9): Only deviations from the work schedule are recorded for the
employee.
Processing employee in time evaluation without transferring the time wage types formed to Payroll:
Time evaluation without Payroll integration (7): Time evaluation is run to administrate
special time accounts, for example, to accrue absence quotas. When time data is processed in
Payroll, the employee is treated as if he or she had the Time Management status 0.
External Services (8): Status for external employees. The results of time evaluation are transferred to
Materials Management (MM-SRV).
Time data processing in Payroll: Time evaluation of planned times (0). The time data of these employees
is not processed in time evaluation.
(C) SAP AG HR310 7

3.8
Work Schedule
Daily work schedule Public holiday calendar

OFF Off Period work
April
L Late schedule
1 F Good Friday
E Early L L 2 S
L 3 S Easter Sunday
Off
4 M Easter Monday
Planned working hours 8.00 L
Plnd working time 6:00 - 15:00
Off 5 T
6 W
Compensation time 0.40
Work break schedule M3 L E 7 T
8 F
Off E
Off E
Work schedule E E
3/30 3/31 4/1 4/2 4/3 4/4 4/5 4/6 4/7 4/8 4/9 4/10
... L L L Off Off E E E E E Off Off ...
Good Easter Easter
Friday Sunday Monday
SAP AG 1999
Employees' planned working time is described in a work schedule. The work schedule is created from a
period work schedule and a public holiday calendar, for individual months.
The period work schedule is made up of a fixed sequence of daily work schedules that repeats in a
specific pattern. The work schedule takes account of the public holiday calendar.
The work schedule is used as the basis for valuating time data.
Examples:
The work schedule shows how many hours salaried employees have to work to be entitled to a full
salary. Hours over and above this can be flagged as overtime in time evaluation, according to
individual specifications.
If you only record deviations to the work schedule, the planned working time is used as the basis for
time evaluation.
(C) SAP AG HR310 8

3.9
What is a Workday?
Does the employee have to work?
Planned
Planned working
working
hours ?
hours == 00
Yes No
Day View
View
Day off
off Day
Day type?
type? Public
Public holiday
holiday class
class
T553A
T553A
00 11 22 33
**
Work,
Work, Off,
Off, Off,
Off, Off,
Off, Other
Other
paid
paid paid
paid unpaid
unpaid special
special day
day
Workday
Workday
SAP AG 1999
There are two factors that determine whether an employee has to work on a certain day:
1. Non-calendar-dependent
The daily work schedule assigned to the employee on the day being evaluated determines whether
the employee has to work on that day. Days that are assigned a daily work schedule with zero
planned working hours are classified as days off.
2. Calendar-dependent
Days with more than zero planned hours can also be days off (for example, public holidays).
This is determined by the day type.
IMG: Personnel Time Management -> Work Schedules -> Define Public Holiday Classes
IMG: Personnel Time Management -> Work Schedules -> Day Types -> Define Selection Rules
(C) SAP AG HR310 9

3.10
Overview of Time Management Infotypes
Entering actual times: Entering approvals and

absence entitlements:
Absences (2001)
Attendances (2002) Attendance Quotas (2007)
Overtime (2005) Absence Quotas (2006)
Time Events (2011)
Entering changes to Entering corrections to

planned specifications: time accounts:
Substitutions (2003) Time Transfer Specifications (2012)

Availability (2004) Quota Corrections (2013)
11 12
1
10
2
9
3
8
4
7 6 5
SAP AG 1999
You can use the Substitutions infotype (2003) to overwrite the planned specifications in an employee's
personal work schedule. The personal work schedule specifies the working times of individual
employees. Planned specifications are not overwritten for a position substitution and a time substitution
in another position.
To access the time management infotypes, choose Human Resources -> Time Management ->
Administration -> Time Data -> Maintain.
(C) SAP AG HR310 10

3.11
Absences and Attendances: Clock Times or
Hours?
Recording a full-day record:

Only the date is entered The planned working times are
generated automatically, but
without clock times
Recording as clock times:

08:00 - 14:00 = 5.00 hours (1 hour break according to
(8 a.m. - 2 p.m.) the daily work schedule)
Recording as hours: Feature HRSIF

5.00 hours HRSIF = 0
08:00 - 14:00
HRSIF = 1
5 hours
SAP AG 1999
You can use feature HRSIF to determine whether time data can be recorded without clock times, or
whether clock times are generated on the basis of the employees personal work schedule for attendances
or absences lasting less than one day.
IMG: Personnel Time Management -> Time Data Recording and Administration -> Permit
Att./Absences to be Recorded Without Clock Times
(C) SAP AG HR310 11

3.12
Time Events Infotype (2011)
Time event
en?
Wh
Date 04/01/xxxx
Access
control area Time 08:00:00
E001
Time event type P10 Clock-in
Day assignment =
?
ere
Wh Terminal ID E001
Origin indicator
al
Clock-in di tion n
Ad matio
r
08:00:00 info
Attendance/absence reason
Different payment
Cost assignment
SAP AG 1999
Time events are, for example, clock-in and clock-out entries that employees record electronically using a
time recording ID card at a time recording terminal. Employees can also enter information on cost
assignment and on work for a different position. Several SAP enhancements are provided, which you can
use to fill customer-specific fields and transfer them to the R/3 System.
In the Time Events infotype (2011), you can:
Record time events manually or change time events that were imported into the R/3 System with
errors
Enter or supplement information on cost assignment or on a different payment
The time events are stored in transparent table TEVEN.
The day assignment allocates the time event to the day to which it logically belongs (either the current
day or the previous day). The day assignment is determined by the system, but you can override it, if
necessary.
Example: Employee works night shift on March 2:
Clock-in on 02/02 at 22:05 -> day assignment: =
Clock-out on 02/03 at 07:03 -> day assignment: <
We recommend the list entry function because it enables you to check and correct several time events at
the same time. List entry is available for all of the Time Management infotypes.
(C) SAP AG HR310 12

3.13
Distribution of Tasks
Time recording system Time Management
Terminal
Time recording
system
CC1TEV
Terminal
R/3 Time
Time
events
events
Results
Results
SAP AG 1999
The distribution of tasks between the time recording system and R/3 Time Management is clearly
defined.
Tasks of the time recording system:
Transferring the HR mini-master records and selected time accounts from the time recording system
to the time recording terminals
Recording time events
Checking ID number, attendance/absence reason, and so on, for particular dates
Transferring time events to the interface CC1TEV
Tasks of R/3 Time Management:
Transferring time events from interface CC1TEV to table TEVEN
Processing time events
Correcting and supplementing time events (infotype 2011)
Transferring the selected time accounts to the time recording system
(C) SAP AG HR310 13

3.14
Data Flow Between the Time Recording System
and SAP Time Management
PT Time Management
Time Evaluation Flextime balance

Absence
Corrections
entitlements
Upload
Clock-in/clock-out/ Download
attendance/absence
reasons HR PDC Master data
Off-site work Time accounts
Employee
expenditures
Access control
Recording of
Clock-in/clock-out entries
Off-site work
Employee expenditures
SAP AG 1999
There is a constant exchange of data between the time recording system and the SAP Time Management
system.
The transfer of data from the time recording system to Time Management is referred to as the upload.
The transfer of data from Time Management to the time recording system is referred to as the
download.
Upload
The interface is supplied with the unprocessed time events by the time recording system.
Data required by a record:
ID number
Date, clock time, time event type (clock-in/clock-out/off-site work, and so on)
Other possible data: Terminal ID, employee expenditures,
Information on cost assignment and on a different payment
Download
A record containing the following information is passed on to the interface for each personnel number:
ID number
Validity period
Access authorization
Other data (such as personal code, mail indicator)
Information on time accounts (including leave status)
(C) SAP AG HR310 14

3.15
Download to the Time Recording System
PS FI CO PT
Download
TEVEN
(Time Events
Projects Cost centers HR mini-master infotype (2011))
Internal orders Time event types
Attendance/
absence reasons
Positions CC1TEV
Time accounts
Time recording system
Recording Clock-in/clock-out (doctors appointment)

Time events
Off-site work
Change of position
Upload
Change of cost center
SAP AG 1999
The download supplies the time recording system with the data it requires from Personnel Management,
Time Management, Logistics, and Controlling, for validations. For each employee whose HR master is
downloaded to the time recording system, there must be a Time Recording Information infotype record
for at least one day of the HR master records validity period.
Data for the download is categorized as follows:
Supply of master data
Master data from the applications (for example, HR master) has to be supplied to the time recording
system so that it can validate the data. This data may change, therefore the download must be
performed regularly.
Supply of control data
Reasons for an absence or attendance can be specified in Time Management. This information can be
entered into the time recording system. The time recording system must check the data. Since this type
of data rarely changes, it needs to be supplied once and then updated only if there are changes. Data
does not need to be supplied periodically.
Supply of transaction data
Employee time accounts that are calculated in time evaluation change each time that time evaluation is
run. For the data at the time recording system to be current, it must be downloaded frequently.
Menu: Human Resources -> Time Management -> Administration -> Environment -> Subsystem
Connection
(C) SAP AG HR310 15

3.16
Time Recording Information Infotype (0050)
Time
Time recording
recording ID
ID number
number
ID
ID version
version HR System
Time recording terminal
Interface
Interface data
data
Work
Work time time event
event type
type group
group
Subsystem
Subsystem grouping
grouping
.........
.........
Time
Time
Time variables
variables from
from evaluation
time evaluation
time evaluation report
Grouping
Grouping for for time
time evaluation
evaluation rule
rule
Flextime
Flextime maximum/minimum
maximum/minimum
General
General overtime
overtime
............
............
SAP AG 1999
Interface data (interface to the time recording systems):

Time recording ID number and ID version: Valid version of the time recording ID card.
Work time event type group: Which time event types (for example, clock-in and clock-out) are
permitted for the employee?
Grouping for subsystem connection: Distribution of master records and a site-restricted access control
Grouping for attendance/absence reasons: Which attendance/absence reasons are permitted?
Grouping for employee expenditures: Which employee expenditures are permitted for the employee?
Access control group: Time-restricted access control
Mail indicator: A message can be displayed to employees when they record a time event at the time
recording terminal.
Personal code: Employees must enter this code at the time recording terminal in order to be granted
access
Time variables (additional information that can be processed in time evaluation):
Employee grouping for the time evaluation rule
Flextime maximum and minimum
Time bonus/deduction
Indicator for general overtime (can be defined by the user)
Additional indicator
(C) SAP AG HR310 16

3.17
Time Evaluation in the SAP System: Summary
You can explain what data is required by

SAP Time Evaluation, and why
You can discuss the relationship between
the different time evaluation methods
You can describe how tasks are distributed
between the time recording system and the
SAP System
SAP AG 1999
SAP AG
(C) SAP AG HR310 17

3.18Data Sheet
Data Used in the Exercises
Data Data in the training Data in the IDES system

system
Personnel area 1400 1400
Employee subgroup DU DU
Cost center 2200 Human Resources 2200 Human Resources
Work schedule rule FLEX FLEX
NORM NORM
Absences 0200 Illness 0200 Illness
9000 Compensation time
Attendance 0440 Active in works 0440 Active in works
council council
Wage type MD70 - Works council MD70 - Works council
bonus bonus
Parameters for the Profile:
Time Managers Z_HR310_TIME_ADMIN
Workplace Definition set for IDs:
SET_DE
Subset of the definition set:
001
(C) SAP AG HR310 18

Group assignments
Group User name

01 HRTRAIN-01
02 HRTRAIN-02
03 HRTRAIN-03
04 HRTRAIN-04
05 HRTRAIN-05
06 HRTRAIN-06
07 HRTRAIN-07
08 HRTRAIN-08
09 HRTRAIN-09
10 HRTRAIN-10
11 HRTRAIN-11
12 HRTRAIN-12
13 HRTRAIN-13
14 HRTRAIN-14
15 HRTRAIN-15
16 HRTRAIN-16
17 HRTRAIN-17
18 HRTRAIN-18
Initial password: INITPASS
(C) SAP AG HR310 19

3.19Time Evaluation in the SAP System: Exercises
Unit: Time Evaluation in the SAP System

Topic: Basics and Prerequisites for Time Evaluation
Hiring an Employee
1 Hiring an employee
1-1 Use the personnel action type Time recording (mini-master) to create personnel
number 310011## (## = your group number):
Entry date 01/01/yyyy (yyyy = current year)

Personnel area 1400
Employee group 1
Employee subgroup DU (Salaried employees)
Work schedule rule FLEX
Time event type grp 01
Subsystem grouping 001
Grouping for 001
attendances/absences
Grouping for employee 001
expenditures
Do not assign a position in the Organizational Assignment infotype (0001).
Your employee participates in time evaluation, and is assigned the Time
Management status 1. The time recording ID number in the Time Recording
Information infotype is the same as the personnel number.
1-2 Your employee is ill from January 2 through January 6. Record this absence in the
system.
(C) SAP AG HR310 20

To do so, use the Time Managers Workplace. Access the Time Managers
Workplace using the profile Z_HR310_TIME_ADMIN. For the time data IDs, use
the definition set SET_DE with the definition subset 001.
Select the employee group HR310, then select your employee.
2 Information on the planned working time

2-1 You have assigned your employee the work schedule rule FLEX. Which system
settings indicate whether this is a flextime schedule?
2-2 Is January 1 a workday for your employee?
(C) SAP AG HR310 21

3.20Time Evaluation in the SAP System: Solutions
Unit: Time Evaluation in the SAP System

Topic: Basics and Prerequisites for Time Evaluation
1 Hiring an employee
To hire an employee, use the Time Recording (mini master) action. To access the action,
choose Human Resources Personnel Management Administration HR Master
Data Personnel Actions.
In the Planned Working Time infotype (0007), assign the employee the Time Management
status 1 - Time eval. (act).
2 Information on the planned working time
2-1 In the Time Managers Workplace, information on employees planned working

times is displayed for you when you administrate time and labor data.
1. Select the required day and choose Choose Detail. The system displays detailed
information on the most import item of information for that day (the dominant),
in this case, the work schedule assigned to the employee.
You can display additional information, such as details of the personal work
schedule and times stored in the work schedule, by choosing the various tab
pages.
2. Choose the Work Schedule Times tab. The daily work schedule FLEX contains
clock times in the fields for the normal working time.
For flextime schedules:
The planned working time forms the flextime framework
The normal working time defines the number of planned working hours (including breaks
from the work break schedule)
2-2 Choose the Personal Work Schedule tab. January 1 has the day type 1- Off/paid.
The employee does not have to work on this day.
Note: You can also obtain information on the employees planned working time
using the Personal Work Schedule report (RPTPSH10). To run the report for your
employee, choose Human Resources Time Management Administration
(C) SAP AG HR310 22

Information System Report Selection Work Schedule Personal Work
Schedule.
(C) SAP AG HR310 23

4
Concept of the Time Evaluation Driver RPTIME00
Contents:
Environment and process of the time evaluation driver
RPTIME00
SAP AG 1999
(C) SAP AG HR310 1

4.2
Concept of the Time Evaluation Driver RPTIME00:
Objectives

Run time evaluation
Name the periods for which times are evaluated
List the data required by time evaluation
Describe how time pairs are formed
Explain what results are delivered by time evaluation,
and how to find out more information on the results
Explain that the data can be archived
SAP AG 1999
SAP AG
(C) SAP AG HR310 2

4.3


Driver RPTIME00

Schemas
SAP AG 1999
(C) SAP AG HR310 3

4.4
Evaluating Time Data
Select employees and

evaluation period
g
Is hin Provide data
y t
v er K?
e O
Check data for errors
Breaks
Planned working
.
.
.
.
Classify times times
.
.
Overtime
.
.
Select time wage types
Compensate overtime wage types
Manage time accounts
Update results
SAP AG 1999
Time data is evaluated in several processing steps, which are carried out in a fixed sequence. You
determine the sequence and the individual processing steps in an evaluation schema in Customizing.
(C) SAP AG HR310 4

4.5
The Time Evaluation Driver RPTIME00
Evaluation of
time data
Individual test Daily background Maintenance

run processing Information and correction
Time evaluation driver RPTIME00

Time wage types
Time balances
Recalculation Leave entitlement
Past or future
if back-dated Messages
time data
changes are made
Errors
Current Up-to-date
Notes
time data results Information
SAP AG 1999
Time evaluation is performed by the time evaluation driver, RPTIME00. Time evaluation generally runs
daily, overnight, and is scheduled as a background job. The evaluation usually encompasses as large a
group of employees as possible.
You can also run time evaluation for individual employees, employee groups, or for past evaluation
periods for test purposes, for example.
The time evaluation report can also be run for future periods. Evaluating future periods can be useful in
the following situations:
You want time evaluation to determine an employee's anticipated absence entitlements when absence
quotas are accrued automatically
You want to valuate planned times in Shift Planning while taking anticipated overtime into account,
for example.
Important time wage types
Night bonus / bonus for work on a public holiday / overtime wage types
Time wage types are primary wage types that are formed during time evaluation, provided that
predefined conditions are fulfilled. Time wage types are formed on the basis of time information. They
enter Payroll only as a number. They are not valuated on a monetary basis until they enter Payroll.
Important time accounts
Flextime / overtime / attendance hours / attendance and absence quotas / planned working time
To access the time evaluation report, choose Human Resources -> Time Management -> Administration
-> Time Evaluation -> Time Evaluation. You can also access time evaluation at other points in the menu.
(C) SAP AG HR310 5

4.6
Maintaining the Results of Time Evaluation
April yyyy
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
Run 1 Future runs
Recalculation run Y
File PCL2
Results are stored Cluster B2 Cumulated results
for individual days are stored
SAP AG 1999
Time evaluation is usually run once daily, but can also be run for any period of your choice. The results
are then determined for each individual day in the period.
The results are stored in file PCL2 in Cluster B2 according to the day being evaluated and the period.
This includes results that are cumulated over a period, such as the flextime balance.
Storing the results for individual days means that time evaluation can return to the results of a particular
day at any time to perform a recalculation.
Note:
If back-dated changes are made to infotypes, a second evaluation can be triggered for days that have
already been evaluated.
(C) SAP AG HR310 6

4.7
Data Flow
Previous Master infotypes: Time infotypes: TEVEN

evaluation Org. assignment Absences Cluster B1
results
Planned Attendances Personnel time
working time Substitutions events
Payroll status Quotas
Pair formation
Evaluation of time data via the
time evaluation driver RPTIME00
Cluster B2 Master data Quotas/ Time infotypes

Balances infotypes entitlements Absences
Payroll status Absence quotas
Messages Attendances
Attendance
Time wage types
quotas
SAP AG 1999
Time evaluation processes the current master data, time data, and the time events. It groups the time
events into pairs before it processes them. It refers to the previous evaluation results for many
calculations, for example, for managing time accounts.
Balances, time wage types, and messages are generated and stored in file PCL2 in cluster B2. Certain
infotypes are then updated.
(C) SAP AG HR310 7

4.8
Pair Formation
** Status
Status information
information for
for error
error tracking
tracking
** Tracking
Tracking the
the attendance
attendance status
status
Table TEVEN Table PT (Cluster B2)

08:02
Clock-in Start
Start End
End Status
Status Attendance
Attendance
status
status
08:02:00
08:02:00 12:05:00
12:05:00 11
12:05
Start of break
Start
Start End
End Status
Status Attendance
Attendance
status
status
12:05:00
12:05:00 12:40:00
12:40:00 00
12:40
End of break
Start
Start End
End Status
Status Attendance
Attendance
? status
status
12:40:00
12:40:00 33 11
"No clock-out
Message Processing entry"
Time Events infotype (2011)
SAP AG 1999
In pair formation, the time evaluation report groups individual time events that are assigned to the same
day into time pairs. This is necessary for time evaluation to be able to process the time events and
determine, for example, the amount of time worked. Pair formation is only triggered for days on which
unprocessed time events exist.
Warning:
In pair formation, a time event is always assigned to the day on which it was posted or to the previous
day, but never to the following day.
If certain processing conditions occur (for example, a clock-out posting is missing and therefore a pair
cannot be formed), pair formation issues messages so that the data can be postprocessed in the messages
processing function of the Time Managers Workplace.
(C) SAP AG HR310 8

4.9
Forming Pairs from Time Events
Absent Absent
At work On a break At work
Clock-in Start of End of Clock-out

break break
Closes pair and Closes pair and

Opens pair Closes pair
opens new pair opens new pair
SAP AG 1999
At the start of pair formation, the individual time events are assigned to a day. Time events are assigned
to their current date or to the previous day. The employee's daily work schedule determines whether a
time event is assigned to the previous day or to the current day.
For each time event, the system determines the employee's attendance or absence status before and after
the entry so that a pair formed is correct. Each time pair is assigned a status, which informs time
evaluation that the pair is complete.
In Customizing, you can change the standard system reaction to certain situations, for example when:
Time events occur a short time after one another
Two consecutive time events could not be formed into a pair (for example, an employee is absent and
records Start of break).
IMG: Personnel Time Management -> Time Evaluation -> General Settings -> Define Settings for
Pair Formation
(C) SAP AG HR310 9

4.10
Starting RPTIME00: Parameters
Evaluation
Evaluation schema
schema Defines
Defines the
the sequence
sequence of
of the
the processing
processing steps.
steps.
Specifies
Specifies whether
whether the
the evaluation
evaluation results
results are
are
Time
Time statement
statement variant
variant displayed, and how they are laid out.
displayed, and how they are laid out.
Display
Display variant
variant for
for log
log Determines
Determines which
which user
user settings
settings are
are used
used to
to
display the time evaluation log.
display the time evaluation log.
Time
Time evaluation
evaluation is
is recalculated
recalculated as
as of
of this
this date
date
Forced
Forced recalculation
recalculation as
as of
of (inclusive) at the latest.
(inclusive) at the latest.
Time
Time evaluation
evaluation runs
runs up
up to
to and
and including
including the
the date
date
Evaluation
Evaluation up
up to
to entered.
entered.
-- Display
Display log
log
Program
Program options
options
-- Test
Test run (no
run (no update)
update)
-- Stop
Stop at function // operation
at function operation BREAK
BREAK
-- Stop
Stop at
at fixed
fixed positions
positions in
in time
time evaluation
evaluation
SAP AG 1999
Important program options of RPTIME00:

Display log:
All the processing steps and substeps of the evaluation schema are logged.
Test run (no update):
Simulation mode: Time evaluation is run without changes to the database.
Sample variants:
Test run:
Program options Display log and Test run
Background processing:
All parameters BLANK except the schema
(C) SAP AG HR310 10

4.11
First Day to be Evaluated
Payroll Status Unprocessed

infotype (0003) time events
PDC recalculation
Forced
recalculation
Recalculation date
First
First day
day to
to be
be evaluated
evaluated
by
by time
time evaluation
evaluation
Earliest recalculation date
Payroll Status
infotype (0003)
Personal ERD
V_T569R time evaluation
ERD Time evaluation
ERD Pair formation
SAP AG 1999
Prerequisites for a correct evaluation:

Time data must be evaluated without gaps
Back-dated changes to employee data that affect the payroll must lead to a recalculation of the results
already determined (= changes relevant to a recalculation)
If there are no changes relevant to a recalculation, time evaluation returns to the day after the last day
evaluated without errors.
RPTIME00 checks the first day evaluated for each employee by reading the information in the Payroll
Status infotype (0003). The system constantly updates this infotype.
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 to be evaluated.
To prevent the system processing periods that are no longer relevant to Payroll, you can set an earliest
recalculation date:
For individual employees:
Using the Personal earliest recalculation date field in the Payroll Status infotype (0003)
For the whole of time evaluation:
IMG: Personnel Time Management -> Time Evaluation -> General Settings -> Set Earliest
Recalculation Date for Pair Formation/Time Evaluation
(C) SAP AG HR310 11

4.12
Recalculation Trigger
Last day to be evaluated

Next
unn
ttiioonn rru evaluation
luu
evvaal
a
a 06/09 as of:
11sstt e
06/10
Processing of master
Payroll
or time data Valid 05/20/yyyy 05/20/yyyy Status
Attendance type 0800 infotype
Time 10:30 17:00
Relevant to 05/20
recalculation
ruunn
attiioonn r
luua
eevvaal
06/09
22n
ndd
05/20 06/10
First day to be
evaluated
SAP AG 1999
For each infotype, you can determine in the Infotypes view (V_T582A) whether changes are relevant to
retroactive accounting. You can use the Retr.acct.PDC field to define which condition should trigger a
recalculation:
Any changes made to an infotype, or
Only changes made to certain fields in the infotype.
You can determine which fields in the infotype should initiate a recalculation in the Field-Specific
Recalculation Indicator view (V_T588G).
IMG: Personnel Management -> Personnel Administration -> Customize Procedures -> Infotypes ->
Set up Infotypes
Define Fields Relevant for Retroactive Accounting
(C) SAP AG HR310 12

4.13
How Were the Results Achieved?
Log: Time evaluation

General Data
For all personnel Parameters for time evaluation
numbers
Schema
Successful personnel numbers
00012356 John Miller
00012360 Mary Smith
Initialization 02/1998
02/01/1998 Sunday
02/02/1998 Monday
End processing 02/1998
Personnel numbers with errors
00012342 Paul Bond
Personnel numbers ended early
All time evaluation
messages Personnel numbers rejected
Messages
Statistics
SAP AG 1999
RPTIME00 generates a log for every time evaluation run. You can control the scope of the log in the
program options for RPTIME00.
The time evaluation log is divided in the following way:
A non-employee-specific section
Employee-specific sections (dependent on the error status of the personnel numbers)
Multiple-employee sections: all messages, statistics
You can expand the log to a particular level of detail. This allows you to track the input and output of the
individual processing steps when the Display log parameter is activated.
You can save the level of detail as a variant, and access it at the start of RPTIME00 by using the Display
variant log field.
(C) SAP AG HR310 13

4.14
Storing Time Evaluation Messages
Cluster B2: Time Evaluation Results
Period 06 Balances SALDO ZES

C1
Wage types ZL
ZL ALP
Messages FEHLER
Basic data and

PSP
work schedule WPBP
Automatic accrual of
absence quotas
Time pairs PT
QTTRANS
QTTRANS
SKO QTACC
Time data QTACC QTBASE
VERT
AB
ANWES
...
RPCLSTB2
Cluster B1
ci fic
spe
t f or
No riods Unprocessed time events NT1
NT2
pe
Worklist of messages to
be processed ERT RPCLSTB1
...
SAP AG 1999
The file PCL2 contains the cluster B2, which is relevant for time evaluation:
You can use report RPCLSTB2 (Display Time Evaluation Results (Cluster B2)) to view all the results
of time evaluation, and the basic data and time data for each time evaluation period.
The file PCL1 contains the cluster B1, which is relevant for time evaluation:
You can use report RPCLSTB1 (Display Recording Data (Cluster B1)) to obtain an overview of all
the processed and unprocessed time events, generated and not yet corrected or confirmed messages
from time evaluation, and important status fields.
You can use the report RPCLSTxx (xx = name of the cluster) to view different clusters in the databases
PCL1 and PCL2.
Menu: Human Resources -> Time Management -> Administration -> Tools -> Tools Selection ->
Cluster
(C) SAP AG HR310 14

4.15
Archiving the Results of Time Evaluation
Cluster B2 (PCL2)
Cluster B2
...
Personal
earliest Apr. 2001 Data
recalculation
Mar. 2001 Data
to Feb 1, 2001
Feb. 2001 Data
Jan. 2001 Data Buffer
Dec. 2000 Data

Archived to Nov. 2000 Data
Dec. 31, 2000
Oct. 2000 Data Archive
Sep. 2000 Data
...
SAP AG 1999
You can archive the time evaluation results in order to relieve the database PCL2. To do this, you use the
central HR archiving transaction PU22.
Menu: Human Resources -> Time Management -> Administration -> Tools-> Archiving
The archiving is employee-specific. You can use a report to select employees according to particular
factors (for example, employees' leaving dates).
Only periods that are no longer relevant to a recalculation are archived, since archived periods cannot be
recalculated.
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 the earliest recalculation date by changing the Earl.pers.rec.date field in the
Payroll Status infotype (0003).
You can display the archived periods using the report RPCLSTB2 (Display Time Evaluation Results
(Cluster B2)) if the system meets the access requirements.
(C) SAP AG HR310 15

4.16
Overview of Time Evaluation
Recording deviations to the WS Recording actual times

Deviations to the Working times
Master data Master data Time
daily WS
Attendances Time events recording
Daily work e.g. infotype 2001 Daily work Absences system
schedule schedule
2002 Attendance/absence quotas
Time evaluation Pair formation

RPTIME00
Cluster B2 Update
Time wage types Time accounts Messages Infotypes
Payroll ZL ZES FEHLER 2001 2006 0003

ALP SALDO 2002 2007
C1
Time statement Download Message Online

Remuneration list processing in the
balances to Display/change
statement RPTEDT00 subsystem Time Managers
Workplace time infotypes
SAP AG 1999
(C) SAP AG HR310 16

4.17
Concept of the Time Evaluation Driver RPTIME00:
Summary
You are now able to

Run time evaluation
Name the periods for which times are evaluated
List the data required by time evaluation
Describe how time pairs are formed
Explain what results are delivered by time evaluation,
and how to find out more information on the results
Explain that results can be archived
SAP AG 1999
SAP AG
(C) SAP AG HR310 17

4.18Concept of the Time Evaluation Driver RPTIME00Exercises
Unit: Concept of the Time Evaluation

Driver RPTIME00
Topic: Running Time Evaluation
Running Time Evaluation
1 Time evaluation using RPTIME00

1-1 In the Time Managers Workplace, record time infotypes and time events for your
employee for the whole of January. When you record time events, refer to the
employee's planned specifications.
1-2 Return to the SAP Easy Access Menu and run time evaluation. Use the program
option Display log, and check the evaluation results in the time evaluation form.
1-3 Which additional options are available for checking the results of the evaluation?
2 Retroactive Accounting
2-1 Check the status of the recalculation date for time evaluation in the Payroll Status
infotype (0003).
2-2 In January, your employee also worked 2 hours at home, in addition to the normal
work. Record this attendance retroactively.
2-3 Look again at the Payroll Status infotype (0003). Which value has changed?
2-4 Run time evaluation again.
(C) SAP AG HR310 18

4.19Concept of the Time Evaluation Driver RPTIME00 Solutions
Unit: Concept of the Time Evaluation

Driver RPTIME00
Topic: Running Time Evaluation
1 Time evaluation using RPTIME00
1. Choose Human Resources Time Management Administration Time Evaluation

Time Evaluation.
2. Enter the personnel number, the evaluation schema TM00, the time statement variant
SAP&TEDT, and the evaluation up to date.
3. Choose Program options.
4. Select the Display log option.
5. Choose Execute.
The time evaluation log gives you a detailed view of the processing steps, results, and
messages in time evaluation. You can branch from the log to the employees time statement
by choosing Goto Display form.
The report Display Database PCL2 Cluster B2 (RPCLSTB2) provides a view of all the
results of time evaluation for a given period.
To access report RPCLSTB2, choose Human Resources Time Management
Administration Tools Tool Selection Cluster Display Time Evaluation Results
(Cluster B2).
You can choose two additional reports to check the evaluation results:
The time statement form (RPTEDT00):
Human Resources Time Management Administration Time Evaluation Time
Statement
Cumulated time evaluation results time balances and time wage types (RPTBAL00):
Human Resources Time Management Administration Information System
Report Selection Time Accounts Cumulated Time Evaluation Results: Time
Balances/Wage Types
(C) SAP AG HR310 19

2 Retroactive accounting
Choose Human Resources Time Management Administration Time Data
Maintain.
The PDC recalc. date field in the Payroll Status infotype (0003) contains the start date for
the next time evaluation. It is defined by the day after the last day that was evaluated
without errors.
If subsequent changes are made to infotypes that are flagged as relevant to recalculation,
the system automatically resets the date.
(C) SAP AG HR310 20

5
Time Evaluation Messages
Contents:
Time evaluation messages
Processing messages in the Time Manager's Workplace
Customizing message processing
SAP AG 1999
(C) SAP AG HR310 1

5.2
Time Evaluation Messages: Objectives

Explain the significance of messages for Time
Management
Create customer-specific messages
Describe how you can arrange the layout of message
processing in the Time Manager's Workplace
SAP AG 1999
SAP AG
(C) SAP AG HR310 2

5.3


Driver RPTIME00

Schemas
SAP AG 1999
(C) SAP AG HR310 3

5.4
Time Evaluation Messages: Business Scenario
The day-to-day tasks of a time administrator:

Viewing time evaluation messages
Routinely postprocessing messages that recur
frequently
Analyzing messages that occur less frequently
Entering missing time data and correcting
incorrect data
Consulting with employees
SAP AG 1999
(C) SAP AG HR310 4

5.5
Time Evaluation Messages
Is the time data under

?
Correct time The day's evaluation
evaluation complete and data is correct
plausible?
?
Have working time
?
regulations been complied Collate statistics
with? Inform employees
Compliance with
Are time accounts nearing Grant missing approvals working time
critical value limits? regulations is ensured
? ?
Did technical errors occur? The day's evaluation
Correct errors is correct
?
SAP AG 1999
One of the most important tasks of time evaluation is to alert time administrators to errors or situations
that require their attention. System administrators also need to be informed if there are errors in
Customizing or technical errors.
Time evaluation performs the following tasks:
Checking the consistency of the time data being evaluated: Time evaluation checks whether time
data was recorded correctly and does not conflict with working time provisions and other recorded
time data.
Checking working time provisions, company working time regulations, and time accounts
Pointing out technical errors that prevent time data from being evaluated. Possible causes for such
errors may be errors in pair formation or in Customizing.
You can use report RPTERL00 (Display Time Evaluation Messages) to perform statistical evaluations on
the messages.
(C) SAP AG HR310 5

5.6
Origin and Categories of Messages
Origin of messages Categories of messages

Time evaluation
How do you want time evaluation to react if, for example, a
working time violation is issued?
Errors determined
in pair formation Time evaluation terminates
Serious errors
Error message
Messages determined Less serious errors, recalculation
by message types that
have been set in
Customizing and
assigned to particular Information message
situations Describing a particular situation, confirming the message
Errors, warnings,
and notes issued
by RPTIME00 Note
Describing a particular situation
SAP AG 1999
Time evaluation can create messages at various stages of processing. Messages to be output are specified
in the SAP System in the form of message types. The category of the message type indicates what
triggered the messages.
Categories of a message type: Origin of messages for analyzing an error situation
1 - Customer-defined message generated by time evaluation
3 - Technical error from pair formation
4 - Technical error from time evaluation
5 - Warnings and notes generated by time evaluation
IMG: Personnel Time Management -> Time Evaluation -> Time Evaluation With Clock Times or Time
Evaluation Without Clock Times -> Message Output -> Create Message Descriptions
Categories of messages for postprocessing
You can define message types of category 1 in Customizing. In Customizing for Time Evaluation, you
then determine how time evaluation is to react to particular situations. This enables you to control
whether postprocessing is necessary and, if so, which form, and to determine the significance of the
situation for a correct evaluation result.
(C) SAP AG HR310 6

5.7
Processing Messages in the Time Manager's
Workplace
Message list displaying
Balances, work schedule rule, etc.
Category of the message for
postprocessing
Processing status
Time Manager's Workplace

Simple selection
Message list
of period and fast
Calendar
navigation
List of all Time data

employees maintenance Multi-day view:
with Showing the day of the
messages message and the day
or list of all before and after
messages
Details
Message-oriented or
employee-oriented Detailed information
view on the time data
SAP AG 1999
The message processing function is fully integrated in the Time Manager's Workplace. It uses the same
design elements as the time data maintenance function.
This means that time administrators work with the same user interfaces for processing time evaluation
messages as for maintaining time data.
In the message processing function of the Time Manager's Workplace:
All relevant contextual information is displayed for a message
Time administrators can switch between an employee-oriented and a message-oriented view
Time administrators can flag messages that they have already processed
For more information, see:
The SAP Library: Choose Human Resources -> Personnel Time Management (PT) -> Time
Manager's Workplace -> Message Processing
The Implementation Guide: Choose Personnel Time Management -> Time Manager's Workplace
-> Basic Settings -> Set Up Message Processing
(C) SAP AG HR310 7

5.8
Message-Oriented and Employee-Oriented
Processing
Message-Oriented Processing Employee-Oriented Processing

M es Em
sag p loye
el ist e lis
t
Technical Dept North Msg Name St Msg A
Work schedule deviations 3 Oleg Kopp 2
Unapproved overtime exists 2 Elena Lopez 1

Employee at work although OFF 1 Helga Martin 1
Time events with errors 3 Vaclev Mikovics 3
Violation of working time provisions 2
Core time violation 1
Employee not at work 1
EE at work despite full-day absence 1
Quick and dirty processing of messages Processing messages with a focus on

not needing additional research all of the messages for one person
Routine handling of errors that occur Recognize subsequent errors or

frequently dependencies that can be processed
at one time
Quickly reduce number of messages on
list In-depth analysis of situation causing
error message
SAP AG 1999
(C) SAP AG HR310 8

5.9
Structuring of Message Lists Using Message
Functional Areas
View V_T555E_WLIST: Assign Message Types to Functional Areas
PSGrpg Type MsgTyNo Text Functional area text
Functional area
01 1 01 Employee not at work WOTIREG Violation of wkg time prov.
01 1 22 Min. working time not reached WOTIREG Violation of wkg time prov.
01 1 46 Max. weekly plnd time reached WOTIREG Violation of wkg time prov.
01 1 02 At work despite full-day absence
Assignment of No assignment of
functional area
functional area
Grouping together of
message types into message
Technical Dept North
Display
functional areas: Work schedule deviations 3 messagetypes
Messages concerning similar Unapproved overtime exists 2 individually:
business situations time
Employee at work although OFF 1 Message types requiring
administrator processes one
a specific handling
message subject area at a time
Violation of working time provisions 3 method
Identical or similar handling
methods for processing messages Core time violation 2
routine handling requiring similar
steps
Time events with errors 1
SAP AG 1999
Message functional areas enable you to see an overview of messages and to control how the messages
are processed.
Not all message types need to be assigned to a message functional area. Unassigned message types are
displayed in the Message View on the same hierarchy level as the message functional areas.
(C) SAP AG HR310 9

5.10
Processing Methods
Processing methods enable you to provide information and solution strategies to streamline
the processing of your time evaluation messages. As of Release 4.6C, you can display
contextual information on the messages.
d
nn e
Pla
Assignment of
Quickly unlock attendance or
special solution
absence records, for example
strategies
Group of display objects OVER:

C
4.6 Overtime and planned hours
Processing Contextual Overtime
method information = Groups Unapproved overtime
of display objects Planned hours
Message list
Cat. Status Name Date Message text Additional information Msg

Kai Wishids 04/15/2000 Unapproved overtime exists Unapproved OT 4.15 hrs
04/15/2000 Employee at work although OFF OT 0.00/Unapp. OT 4.15/Plnd 0.00
SAP AG 1999
In Release 4.6C, you can use processing methods to provide specific contextual information to
streamline the processing of time evaluation messages. You can have the contextual information
displayed together with the message type or with the message functional area. If, under one message
functional area, there are messages with different contextual information, the information is grouped in
one field.
Typical examples of contextual information:
Planned time and flextime account balances, when violations to working time provisions occur
Planned hours and overtime in the case of overtime approvals
Work schedule
You organize the contextual information into groups of display objects. A group of display objects can
contain up to 10 display objects.
You can assign a group of display objects to each processing method.
In future releases, you will also be able to use special screens, for example.
(C) SAP AG HR310 10

5.11
Assigning Processing Methods
a A
a re fu ssig
n al Processing nc n
io method tio ed
ct na t o
un la m
ef re es
th a sa
to ge
d
ne ty
sig pe
As s
of
Technical Dept North
All assigned message Work schedule deviations 3
types are subtotaled Each message type
Unapproved overtime exists 2 appears under the node
under the functional area
and no longer appear in Employee at work although OFF 1 for the function area in
the message view the message view
Time events with errors 3
Violations of working time provisions 2
Core time violation 1
SAP AG 1999
You can use processing methods in two ways:

You assign a processing method to a functional area. All message types that fall under this functional
area inherit this processing method. The messages are then subtotaled under the functional area, that
is, they no longer explicitly appear in the Message View.
You assign a processing method to a message type. If the message type is not assigned to a functional
area or no processing method is assigned to the functional area, then the processing method is
displayed with the message type.
You may want to use a functional area only to structure the message list, so that particular messages are
not listed separately, for example. In this case, assign a processing method to a functional area that does
not have a group of display objects assigned to it. Make sure that the relevant message types do not have
processing methods.
(C) SAP AG HR310 11

5.12
Time Evaluation Messages: Summary
You are now able to:

Explain the significance of messages for Time
Management
Create customer-specific messages
Describe how you can arrange the layout of
message processing in the Time Manager's
Workplace
SAP AG 1999
SAP AG
(C) SAP AG HR310 12

5.13Time Evaluation Messages: Exercises
Unit: Time Evaluation Messages

Topic: Processing Messages in the Time Managers
Workplace
Correcting Errors Using the Message Processing Function
1 Missing clock-out entry

An employee has forgotten to make a Clock-out entry when leaving work on a workday.
1-1 In the Time Managers Workplace, enter the employees time events for this day.
1-2 Run time evaluation again for the employee. Check the log.
1-3 Correct the error using the message processing function in the Time Managers
Workplace.
2 Check the Customizing settings for message processing

Time evaluation always outputs the message At work despite day type 1 when an
employee works on a public holiday.
Check the Customizing settings for this message type in the Implementation Guide (IMG).
2-1 Which message functional area is the message assigned to?
2-2 Which processing method is assigned to the message type?
2-3 What contextual information is displayed for the message in the Time Managers
Workplace?
(C) SAP AG HR310 13

5.14Time Evaluation Messages: Solutions
Unit: Time Evaluation Messages

Topic: Processing Messages in the Time Managers
Workplace
1 Missing clock-out entry

Time evaluation terminated processing with the message 04 Clock-out cannot be delimited.
1. Correct the error using the message processing function in the Time Managers
Workplace.
2. Access the Time Managers Workplace and choose Goto Process Messages.
3. Select the Employee view, then select your employee.
4. Click on the message Clock-out cannot be delimited.
5. Choose the Time Events tab, and enter the missing time event.
6. Run time evaluation again for the employee: Select your employee in the employee list
and choose Time evaluation.
2 Check the Customizing settings for message processing

1. In the Implementation Guide, choose Personnel Time Management Time Managers
Workplace Basic Settings Set Up Message Processing Assign Processing
Methods to Message Functional Areas and Message Types
2. Choose Assign Processing Methods to Message Types.
The system displays an overview of the message functional areas and processing
methods assigned to the message types. The message type 08 - At work despite day
type 1 is assigned to the message functional area PWS and the processing method
TOVER - Check Overtime Worked.
3. Choose the IMG activity Assign Groups of Display Objects to Processing Methods.
The view indicates that the group of display objects OVER - Overtime and Planned
Hours is assigned to the processing method TOVER.
4. Choose the IMG activity Create Groups of Display Objects.
5. Select the OVER entry, and double-click on Field Customizing.
This view shows that the group contains the display objects Overtime and Planned
hours.
(C) SAP AG HR310 14

6
Customizing Time Evaluation
Contents:
Introduction to the tools used for customizing time evaluation
SAP AG 1999
(C) SAP AG HR310 1

6.2
Customizing Time Evaluation: Objectives

Customize the time evaluation process
Describe the special features of Customizing for
time evaluation, and the purpose of the
Implementation Guide (IMG)
Explain how tables, schemas, and personnel
calculation rules interact in time evaluation
Explain how functions and operations work
Describe how to edit schemas and personnel
calculation rules
Explain the significance of the time type in
time evaluation
SAP AG 1999
SAP AG
(C) SAP AG HR310 2

6.3


Driver RPTIME00

Schemas
SAP AG 1999
(C) SAP AG HR310 3

6.4
Time Evaluation With Clock Times
Personnel Time Management

Work Schedules
Time Data Recording and Administration
Personnel Time Events
Plant Data Collection
Time Evaluation
General Settings
Settings for Time Evaluation
Time Evaluation With Clock Times
Initial Steps
Providing Time Data
Time Data Processing
Time Wage Type Selection and Overtime Compensation
Processing Balances
Message Output
Storing Evaluation Results
Special Problems and Solutions in Time Evaluation
Time Evaluation Without Clock Times
SAP AG 1999
The standard system supplies several personnel calculation schemas (or schemas for short), which have
different requirements for time data to be evaluated, and which follow different evaluation strategies.
The Implementation Guide (IMG) contains two chapters that describe the two most important standard
schemas. They also give a detailed explanation of how you can modify the schemas to suit your own
company's requirements:
Time evaluation with clock times (standard schema TM00)
Time evaluation without clock times (standard schema TM04)
(C) SAP AG HR310 4

6.5
Customizing Time Evaluation
Driver Evaluation Customizing

RPTIME00
RPTIME00 Tables/Views
Tables/Views
Payroll driver
Time Types
Set parameters
Schedule background jobs
General control of
time evaluation
Time wage type selection
Rule Processing/Evaluation Schema
Customize/ Absence quota type sel.

sel.
Carry out
determine
processing steps processing steps
SAP AG 1999
The rules that govern the valuation of time data are not hard-coded. This means that you have a variety
of options for modifying time evaluation to suit your own requirements.
The boxes highlighted in color indicate the areas of time evaluation that you can customize.
The processing steps of time evaluation are grouped together in the schemas. The schema determines
how time evaluation processes the steps and in which sequence. The system reads values from various
Customizing tables during processing.
To start time evaluation, specify in the selection screen for RPTIME00 the schema you want to use to
evaluate times.
Time data processing by the payroll driver has the same processing structure as within time evaluation.
(C) SAP AG HR310 5

6.6
Steps of Time Evaluation
Select employees
Determine evaluation period
Rule Processing/Schema:
Initialization: Set groupings
12 Day processing:
12
Provide data
Classify times
Final processing : Carry out checks
Export evaluation results

Update infotypes Database
SAP AG 1999
The time evaluation driver evaluates employees' time data on a daily basis.
The individual processing steps that are defined in a schema are called functions. They are carried out in
a particular sequence, which is determined by the arrangement of the functions in the schema.
Functions have precisely defined attributes. Some functions are used to carry out necessary, and
therefore standardized, processing steps of time evaluation (for example, selecting time wage types).
(C) SAP AG HR310 6

6.7
How Functions and Operations Work
Function Personnel Sequence

calculation rule of elementary
Operations processing
Planned hrs = 0 ? steps
EE at work?
Trigger EE absent? Evaluation Customizing
processing Day type?
Tables/Views
Tables/Views
...
Time Types
Function Import data

Functions P2001
Time wage type selection
P2002
Carry out
processing Select time wage types
Function GWT
SAP AG 1999
Functions can carry out a variety of tasks, for example:

Set a switch for time evaluation
Carry out processing
Trigger processing
Some functions allow you to describe the individual processing steps more precisely, by accessing
personnel calculation rules. In them, a sequence of elementary processing steps is carried out. The
processing steps are triggered by operations. You can use operations to:
Query whether the employee was at work
Query the day type of the day to be evaluated
Form time balances
Functions and operations can query values that you have set in time evaluation views.
(C) SAP AG HR310 7

6.8
Using HR Documentation Maintenance
HR Documentation Maintenance
Document class Function (Time Management)
Documentation object
Country
Object name
HR documentation: Object name
HR document class FUNT
Country
Object name Description of the logical information object

***
A2003 Process work center substitution
Also available
ACTIO Rule-controlled execution of an action
as a modeless
ADJAB Modify absence records
dialog box BDAY Initiate processing block in day processing
BEND Processing block after day processing
BINI Initiate processing block
SAP AG 1999
Transaction PDSY (HR Documentation Maintenance) accesses the documentation of all schemas,
functions, personnel calculation rules, and operations. If necessary, you can create the documentation for
specific clients.
To obtain a list of these objects, enter the appropriate documentation class, and use the possible entries
help for the Object name field. You can also display the list in a modeless dialog box to keep a list of all
operations while you are creating personnel calculation rules, for example.
Documentation classes relevant to Time Management:
SCHE - Personnel calculation schemas
CYCL - Personnel calculation rules
FUNT - Time Management functions
OPET - Time Management operations
549B - Features
PRCL - Processing class
SKON - Symbolic constant
When you maintain schemas and personnel calculation rules, context-sensitive HR documentation is
displayed when you access the field help (F1).
(C) SAP AG HR310 8

6.9
Maintaining Personnel Calculation Schemas
Personnel Calculation Schemas: Initial Screen
Schema
Create
Sub-objects
Source text
tess
ribbuute
Attributes Attttri
A
Documentation
Program class C Payroll
T Time Management
Display Change Country grouping * , 01, 02, ... 99
Schema can be executed
Person responsible
Changes only by person responsible
SAP AG 1999
You can use the schema editor (transaction PE01) to display and maintain personnel calculation
schemas.
You can determine characteristics of a schema in attributes. You can choose to permit only the person
responsible to change the attributes and the schema.
The program class indicates where the schema is used (C = Payroll; T = Time Management).
The country grouping specifies whether the schema can be used in the country-specific versions of the
payroll driver. There are no country versions of RPTIME00. The country grouping is therefore always
assigned the value "*".
To access the tree structure for the schema to display the individual processing blocks, choose Utilities
-> Structural graphics. You cannot edit the schema in the structural graphic.
Menu: Human Resources -> Time Management -> Administration -> Tools-> Maintain Schemas
(C) SAP AG HR310 9

6.10
Layout of the Schema Editor
Command
Edit Schema: Txxx
line
check
Fct Par1 Par2 Par3 Par4 D Text

000180
000190
c00200 PERT TD20 Evaluate errors from pair form
000210
000220
000230 A2003 * Process work center substitut
a00240
000250
Line
commands
Function Parameters 1- 4 Inactive

function
SAP AG 1999
You can use the schema editor to display, change, and create schemas.
You can use the standard help function (F1 Help) in the schema editor to access documentation
according to context (by positioning the cursor on a function, personnel calculation rule, and so on) as
follows:
F1 help from the command line: Documentation for all permitted commands
F1 help from a line number: Documentation for all permitted line commands
(C) SAP AG HR310 10

6.11
Maintaining Personnel Calculation Rules
Personnel Calculation Rule: Initial Screen
Rule TE20
Create
Sub-objects
Source text
ES grouping *
Wage/time type **** tess
ribbuute
Attttri
A
Attributes
Documentation Program class C Payroll
T Time Management
Country grouping * , 01, 02, ... 99
Display Change
Person responsible
SAP AG 1999
You can use the personnel calculation rule editor (Transaction PE02) to display and maintain personnel
calculation rules.
You edit personnel calculation rules according to the Employee subgroup grouping for personnel
calculation rules and the wage type or time type.
You can determine characteristics of a personnel calculation rule in attributes. You can choose to permit
only the person responsible to change the attributes and the personnel calculation rule.
The program class determines where the personnel calculation rule is used (C = Payroll; T = Time
Management).
The country grouping specifies whether the schema can be used in the country-specific versions of the
payroll driver. There are no country versions of RPTIME00. The country grouping is therefore always
assigned the value "*".
You can choose between two screens for editing personnel calculation rules: If you choose Utilities ->
Structural graphics, the personnel calculation rule is displayed in a tree structure If you choose Utilities
-> Table display, you can edit the personnel calculation rules in a table view
Menu: Human Resources -> Time Management -> Administration -> Tools -> Maintain Personnel
Calculation Rules
(C) SAP AG HR310 11

6.12
Layout of the Rule Editor
TE20 Error checks by day
*
Employee
subgroup ****
grouping for
personnel
calculation rule VARSTFREE Planned hours DWS = 0 ?
Time type N ...
Y
Variable key
VARSTPRSNT Employee at work
COLER00 Note
SAP AG 1999
You can use the rule editor to display, enter, and change personnel calculation rules.
The variable key is used to build a decision tree. The decision tree enables you to perform processing
differently according to organizational aspects, for example. It is only used for decision operations
(indicated in green).
For each personnel calculation rule, the length of the variable key must not exceed 8 characters,
inclusive of the spaces necessary between the keys (not shown on the diagram).
If the length of the variable key is insufficient, you can use operation PCY to branch to another
personnel calculation rule. After this rule is processed, processing returns to the original personnel
calculation rule, and the continues with the next operation in the line.
You can also use operation GCY to branch to another personnel calculation rule. After this rule is
processed, processing does not return to the original personnel calculation rule.
You can access context-sensitive documentation on the operations by using the F1 help. To display a key
of the colors used to identify different objects in the tree display, choose Utilities -> Color legend.
(C) SAP AG HR310 12

6.13
Managing Time Accounts
John Miller Account no. 123999 Date: mm/31/yyyy

Date Debit Credit
...
mm/04/yyyy Deposit 150.00
mm/11/yyyy Withdrawal 235.00
mm/23/yyyy Deposit 120.00
...
Previous balance: 300.00 Current balance: 335.00
Time Account 0050: Productive Hours
John Miller Pers.no.: 00012356

Balance on mm/09/yyyy: 58.90
Debit Credit
Time mm/10/yyyy Productive hours 9.00
evaluation mm/11/yyyy Productive hours 7.50
Balance on mm/11/yyyy: 75.00
SAP AG 1999
You can use time evaluation to manage time accounts such as:
Overtime
Planned times
Flextime balances
Time accounts can be
Accumulated and deducted
Used for employees' information
Used to create statistics
Managing a time account is similar to running a bank account. Bank accounts and time accounts have
the following features in common:
They are person-related
They are time-related
They are credited and debited
They show a certain value (credit) at a certain point in time
RPTIME00 maintains time accounts according to defined processing steps. The value of the respective
time account is updated on every day that is processed in time evaluation.
(C) SAP AG HR310 13

6.14
Time Types
Time Types View (V_T555A)
PS grouping Time typeTime type long text From To

01 0002 Planned time 01/01/1901 12/31/9999
01 0003 Skeleton time 01/01/1901 12/31/9999
01 0005 Flextime balance 01/01/1901 12/31/9999
... ...
Pers. subarea grpg. 01 From To

Time type 0002 Planned time > 01/01/1901 12/31/9999
Balances
Save as day balance 1 Balance formation
Cumulate in period balance 1 Balance formation
ZES SALDO
Rel.
Rel.Date
Date Time
Timetype
type Number
Number Time
Timetype
type Number
Number
01
01 04/01/yyyy
04/01/yyyy 0002
0002 7.50
7.50 0002
0002 155.00
155.00
01
01 04/01/yyyy
04/01/yyyy 0003
0003 8.00
8.00 0003
0003 167.50
167.50
01
01 04/01/yyyy
04/01/yyyy 0005
0005 0.50
0.50 0005
0005 12.50
12.50
01
01 04/02/yyyy
04/02/yyyy ...
... ...
... ...
... ...
...
SAP AG 1999
A time type is a technical name for a 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.
You can use the Time Types view (V_T555A) to determine which time types filled during time
evaluation are stored as evaluation results. The following control options are available:
Transfer to total for day: Save in table ZES
Transfer to total for month: Cumulate in table SALDO
Transfer previous month/year: The value of the time type is passed on at the start of a new period or
year.
Time type start of new period/year: At the start of a new period or year, the value of the time type is
stored under the new time type specified.
Storing for time accounts: You can use report RPTDOW00 (Time Accounts) to evaluate the balances.
Up to 10 balances can be downloaded to the time recording system.
IMG: Personnel Time Management -> Time Evaluation ->Time Evaluation Settings -> Define Time
Types
(C) SAP AG HR310 14

6.15
Time Type as Calculation Tool in Time Evaluation
Group durations together Calculation using

durations
Compare times
Note time points
Attendances
Paid
breaks
Time type
Form balances Transfer times
Flextime Difference of
Flextime
balance time types balance .
.
.
.
.
.
.
.
Cluster B2
SAP AG 1999
Time types perform many tasks during time evaluation. Important balances that are formed by
calculations, transfers, or grouping of time types are collected into time types and made available for
storage in cluster B2.
(C) SAP AG HR310 15

6.16
Processing Structure of Time Evaluation
Time Evaluation Driver Schema Processing Evaluation Customizing
Time
Time evaluation
evaluation driver
driver Function
Function pool
pool Schema
Schema Tables/Views
RPTIME00
RPTIME00 SAPFP51T
SAPFP51T
- Select employees Module - Function

- Function Time types
- Lock personnel numbers
Execution/ - Function
- Determine evaluation coding of - etc.
period functions
- Collect data
- Trigger function pool Time wage type
SAPFP51T selection rule
- Determine next day to be
evaluated
Personnel
Personnel
- Save results of calculation
evaluation
calculation
Module rules
rules Absence quota
- Log data - Operation type selection
Execution/ - Operation
coding of - Operation
operations - etc.
SAP AG 1999
The complex processing structure of the time evaluation driver, schema processing, and evaluation
customizing allow you to set up most of your requirements for time evaluation. If the options available
in the standard system are not sufficient, you can also create your own functions and operations.
Menu: Human Resources -> Time Management -> Administration -> Tools-> Functions/Operations
(C) SAP AG HR310 16

6.17
Customizing Time Evaluation: Summary
In this unit you have learned the different Customizing

options for the processes of time evaluation (the
Implementation Guide, personnel calculation schemas
and rules).
You have been introduced to the personnel
calculation schemas and rule editors.
You have learned the meaning of the time type for
time evaluation.
SAP AG 1999
SAP AG
(C) SAP AG HR310 17

6.18Customizing Time Evaluation Exercises
Unit: Customizing Time Evaluation

Topic: Introduction to the Tools Used for Customizing
Time Evaluation
Creating a Time Type
1 Creating a time type

In your enterprise, employees can accrue a compensation time account. This account is
managed in the time type 90## (where ## = your group number).
Create the time type 90##. The time type is to be transferred to the day totals and period
totals.
(C) SAP AG HR310 18

6.19Customizing Time Evaluation Solutions
Unit: Customizing Time Evaluation

Topic: Introduction to the Tools Used for Customizing
Time Evaluation
1 Creating a time type

You create the time type 91## in the IMG step:
Personnel Time Management Time Evaluation Time Evaluation Settings Define
Time Types.
In the Save as day balance and Cumulate in period balance fields, enter the value 1 (=
balance formation/transfer).
(C) SAP AG HR310 19

7
Data Collection in Time Evaluation
Contents:
Importing the daily work schedule
Providing the time infotypes
Evaluating attendance and absence reasons
Processing using internal tables
Schema section: Collecting data in time evaluation schema TM00
SAP AG 1999
(C) SAP AG HR310 1

7.2
Data Collection in Time Evaluation: Objectives

Describe the functions that are used to import
employees' planned specifications and their
infotypes into time evaluation
Discuss how this information is available in
internal tables for further processing
Explain how data is collected in the time evaluation
schema TM00
SAP AG 1999
SAP AG
(C) SAP AG HR310 2

7.3


Driver RPTIME00

Schemas
SAP AG 1999
(C) SAP AG HR310 3

7.4
Data Collection in Time Evaluation: Business
Scenario
Attendances and absences are recorded for

employees. The time data is entered into time
evaluation, where it is made available for
further processing.
SAP AG 1999
(C) SAP AG HR310 4

7.5
Importing Data
Recording work schedule Recording all times

deviations
Function Work schedule

P2000 incl. substitutions
Function
P2011
Postings
Function Function
P2001 P2001
Absences
Function Function
P2002 P2002
Attendances
SAP AG 1999
Employees' planned specifications, time events, and data from the time infotypes are imported using
special functions. Depending on your method of time recording, you use either function P2000 or P2011
to import employees' planned specifications (from the work schedule).
Additional functions for importing data:
A2003 - You can use function A2003 to take account of position substitutions that lead to a different
payment in time evaluation.
Substitutions that lead to a change in the planned specifications are imported by function P2000 or
P2011.
P2005 - You can use function P2005 to import the overtime of the day that was recorded in the
Overtime infotype (2005). You would normally only use this function if you record work schedule
deviations. If you record actual times, there are checks to determine whether the employee is
permitted to work overtime:
By time evaluation, which checks overtime approvals automatically
By the time administrator, who records overtime in the Attendances infotype (2002)
IMG: Personnel Time Management -> Time Evaluation -> Time Evaluation With Clock Times ->
Providing Time Data
(C) SAP AG HR310 5

7.6
Function P2000: Importing Daily Work Schedule
Table TZP: Planned Specifications

Forms the basis for comparison
with recorded time data:
Enables processing of:
Absence times
Break durations
Breaks
Error checks
Start of End of
work work
Working
hours
Table TIP: Planned Pair
If no actual times are recorded:
The time pair according to the
planned working times forms the
basis for time evaluation
SAP AG 1999
Function P2000 is used for the following tasks:
Recording work schedule deviations

Function P2000 enters the employee's current work schedule in the internal table TZP. It also enters a
time pair according to the day's planned working times in the work table TIP. This pair is flagged as a
planned pair.
Time evaluation without clock times
If you use the recorded attendances from the Attendances infotype (2002) as a basis for the valuation
of times, function P2000 places the daily work schedule in table TZP. You prevent the system forming
a planned pair by entering NOTP in parameter 4 of the function.
Evaluation or simulation of future times
For the evaluation of future times, no information on employees' actual work is available. Time
evaluation therefore uses function P2000 to generate information on the day. It enters the daily work
schedule in table TZP and a planned pair in table TIP.
(C) SAP AG HR310 6

7.7
Function P2000: Providing Planned Specifications
Grpg for daily WS 01 D

Daaiil
Daily work schedule FLEX Flextime
lyy wwoorr
kk
V__TT sscchheed
((V
555500 du
Planned working hours
Planned working hours 8.00 DWS selection rule 01 A)) ullee
A
No planned working hrs
Working times
Fixed working hours
Planned working time -
Flextime
Planned working time 07:00 - 18:00
Normal working time 08:00 - 17:00
Core time 1 09:00 - 11:30
Core time 2 14:00 - 16:00
Breaks
Work break schedule FLEX
...
Valuation
Min. working time Daily WS class 5
...
SAP AG 1999
The planned specifications ("When was the employee scheduled to work?") are based on the employee's
personal work schedule. If a substitution is assigned to the employee on the day being evaluated, the
substitution overrides the daily work schedule.
IMG: Personnel Time Management -> Work Schedules -> Daily Work Schedules -> Define Daily Work
Schedules
(C) SAP AG HR310 7

7.8
Function P2000: Filling Internal Table TZP
Generate entries
in internal table TZP Time Time identifier Break duration
00
00 .0000
.0000 01
01 Overtime
Overtime hours
hours
07
07 .0000
.0000 02
02 Fill
Fill time
time
09
09 .0000
.0000 03
03 Core
Core time
time
09
09 .5000
.5000 04
04 Core
Core time
time break
break 0.25
0.25
10
10 .0000
.0000 03
03 Core
Core time
time
11
11 .5000
.5000 02
02 Fill
Fill time
time
12
12 .0000
.0000 05
05 Fill
Fill time
time break
break 0.75
0.75
13
13 .5000
.5000 02
02 Fill
Fill time
time
14
14 .0000
.0000 03
03 Core
Core time
time
16
16 .0000
.0000 02
02 Fill
Fill time
time
18
18 .0000
.0000 01
01 Overtime
Overtime hours
hours
Further information from

DWS Variant Day type DWS class Planned hours
daily work schedule
FLEX BLANK 5 8
SAP AG 1999
An entry is generated in the internal table TZP for each time point in the daily work schedule; all clock
times are decimalized. Each entry in table TZP is assigned a time identifier, which describes each section
of the daily work schedule.
Time evaluation also uses function P2000 to import the:
Daily work schedule
Daily work schedule variant
Day type
Daily work schedule class
Planned working hours.
(C) SAP AG HR310 8

7.9
Function P2011: Providing Planned Specifications
and Actual Times
Daily work schedule

needd
PPllaannn tiioonnss
iffiiccaat
ssppeecci
Breaks
Start of End of
work Working work TZP
hours
22:00 06:00
meess
aall ttiim Employee postings
Accttu
u
A
22:00 Clock-in
01:10 Start of break TIP
01:40 End of break
05:45 Clock-out
SAP AG 1999
You use function P2011 when you upload time events/time postings from external time recording
systems to the R/3 System. Function P2011 performs two tasks:
Importing the planned specifications:
The employee's current daily work schedule is first imported to the internal table TZP.
Loading the actual times:
The pairs formed from the time postings are then placed in the internal table TIP.
If you use function P2011 in the schema, you require function P2000 only if you want to load planned
specifications for future days.
(C) SAP AG HR310 9

7.10
Daily Input: Table TIP After Function P2011
Time Events (infotype 2011) Table PT

(Cluster B2)
22:00 P10 Clock-in
Start End BR ER S1 P
01:10 P15 Start of break
Pair formation 22:00:00 25:10:00 P10 P15 1
01:40 P25 End of break 25:10:00 25:40:00 P15 P25 0
05:45 P20 Clock-out 25:40:00 29:45:00 P25 P20 1
Function
P2011
TIP
From To 1 P ID Ct P TTyp BR ER C O I BPIN EPIN PT ALP C1 AB Number

22.0000 25.1667 1 00 P10 P15 E 0001 3.1667
25.1667 25.6667 0 00 P15 P25 E 0002 0.15000
25.6667 29.7500 1 00 P25 P20 E 0003 4.0833
Status from Pair type Time event Origin Reference to

pair formation type indicator time pairs (table PT)
SAP AG 1999
Function P2011 transfers the time pairs that were formed from the time postings from table PT (Cluster
B2) to the internal work table TIP. All clock times are decimalized in the process.
If pair formation assigns time events to the previous day, the system adds 24 hours to the time pair.
So that table TIP is not overloaded with information, further data on the TIP entries is stored in other
tables. This separation of data is known as a split. Only the reference to the corresponding table is stored
in table TIP:
PT- Pair table

ALP - Different payment
C1- Cost assignment specifications
AB - Absences
The reference number that is specified under the table name refers to the corresponding record in the
table in cluster B2. The numbers in these tables are assigned automatically.
(C) SAP AG HR310 10

7.11
Processing Using Internal Tables
Internal tables (temporary): Tables in cluster B2
Read, fill, and change data Time evaluation results
Input for TOP

processing steps
in time evaluation
TIP TZP
Day's input Day's clock times
ZES
Results of the TES Day's balances
individual Day's balances
SALDO
processing steps in Period balances
time evaluation
ZML
Overtime wage
types
DZL ZL
Wage types
Wage types
FEHLER FEHLER
Messages
Messages
Output Output
RPTIME00, program option: Display log Report RPCLSTB2

SAP AG 1999
Internal tables are the work tables of Time Evaluation. They are filled and changed during the time
evaluation run. When time evaluation requires specific data for a processing step, it reads it from the
internal tables and then processes it further. At the end of the processing step, time evaluation returns the
modified data to the internal table. The data is then available there for further processing steps.
Internal tables are temporary in nature, and are deleted at the end of time evaluation for each employee.
Data that is required subsequently, such as time balances and time wage types, is exported to tables in
cluster B2 in file PCL2 at the end of time evaluation.
The principal work table is the internal table TIP (daily input). It provides the input for the respective
processing step in the form of the time data that has been imported or evaluated so far by time
evaluation. The entries in TIP are processed line by line and inserted in the internal table TOP (daily
output). Table TOP becomes the new table TIP at the end of the processing step.
The internal table TZP contains the planned specifications from the employee's personal work schedule.
The values in the internal tables that are determined in the individual processing steps are displayed in
the time evaluation log.
(C) SAP AG HR310 11

7.12
Functions P2001 and P2002:
Providing Absences and Attendances
Absences (infotype 2001) Attendances (infotype 2002)
Absence type 0230 Attendance type 0800

Time 08:00 10:30 Time 10:30 17:00
Function Function
P2001 P2002
TIP
Start End 1 P ID Ct P TTyp BR ER C O I BPIN EPIN PT ALP C1 AB Number
08.0000 10.5000 0 2 02 A A 01 2.5000
10.5000 17.0000 0 3 01 P P 6.5000
Reference to:
Different payment (Table ALP)
Cost assignment (Table C1)
Absences (Table AB)
SAP AG 1999
Function P2001 generates an entry in the internal table TIP for each recorded absence (infotype 2001).
Function P2002 enters the attendances from infotype 2002 in the internal table TIP. For full-day
attendances and absences, a time pair is generated according to the planned working times from the daily
work schedule.
Depending on how attendances and absences are recorded and how feature HRSIF is set, the clock times
are stored in table TIP.
When loading full-day attendances or absences, time evaluation generates the times according to the
planned working times. (When full-day attendances and absences are recorded, the attendance or
absence hours are not entered manually, but instead are imported automatically from the daily work
schedule.)
The Processing type/time type class (field CT) is used to group together attendances and absences that
are processed identically in Time Evaluation Without Clock Times. It has no relevance for Time
Evaluation With Clock Times.
(C) SAP AG HR310 12

7.13
Processing Attendance and Absence Reasons
Attendance/absence reason
10:00 P10 0001 Doctor's appointment <1 day
16:00 P20 0004 Time in lieu of flextime
Rule Att./Absence Reasons for Subsystem (V_T705A)

TD80 Att/abs ESgrp PSgrp A/AReas Text Abs/Att Text
0001 1 01 0001 Doctor's appt <1 day 0230 Doctor's appt
0001 1 01 0004 Time in lieu of flextime 0900 Time in lieu of flex.
TIP
08.0000 10.0000 0 2 02 A C 01 2.0000
10.0000 16.0000 0 1 00 P P10 P20 E 0001 0004 0001 6.0000
d
20 01 lo cke
Infotype
Current day: 0230 Doctor's appt 08:00 - 10:00
Following day: 0900 Time in lieu of flex. Full day
SAP AG 1999
Employees can record an attendance or absence reason in conjunction with a clock-in or clock-out entry
at the time recording terminal. Time evaluation can use the attendance or absence reasons to generate
records for the Attendances (2002) and Absences (2001) infotypes automatically.
Rule TD80 evaluates the attendance and absence reasons using the view Att./Absence Reasons for
Subsystem (V_T705A). All the automatically generated records are defined as locked infotype records in
the system. A note is issued in error processing in the Time Management pool. The time recording
administrator can then confirm the record by unlocking it, or delete it.
An additional entry is generated in table TIP and evaluated for records of less than one day. The payroll
for day in question is first run provisionally, since generating a locked attendance or absence record sets
a recalculation for the day.
A full-day attendance or absence is evaluated on the following day by the personnel calculation rule
TD90. If the attendance or absence is still locked and the day is a workday, a planned pair is entered in
TIP. If the following day is not a workday, the automatically generated record can be extended by one
day.
IMG: Personnel Time Management -> Time Evaluation -> Time Evaluation with Clock Times ->
Providing Time Data -> Absences -> Provide Full-Day Absences Recorded at Terminal
IMG: Personnel Time Management -> Time Evaluation -> Time Evaluation with Clock Times ->
Providing Time Data -> Absences -> Provide Full-Day Absences Recorded at Terminal
(C) SAP AG HR310 13

7.14
Dynamic Daily Work Schedule Assignment:
Rule TD30
Personal
work schedule
EARLY LATE NIGHT
06:00 14:00 22:00 06:00
Problem: Personal work schedule not suitable

Suitable daily work schedule?
V_T552V DWS assignment:

Rule TD30 Clock-in DWS
( Operation DYNDP ) 05:00 - 07:00 EARLY
13:00 - 15:00 LATE
21:00 - 23:00 NIGHT
Personal work schedule:
LATE
SAP AG 1999
The dynamic assignment of the daily work schedule allows time evaluation to determine the
appropriate daily work schedule depending on the time of the first clock-in entry for the day. You can use
the dynamic assignment for relief shifts, for example, to assign employees an appropriate work schedule.
Rule TD30 compares the employee's first clock-in posting with the corresponding entries from the
Dynamic Assignment of Daily Work Schedules view (V_T552V) to determine the current daily work
schedule.
Providing Time Data -> Work Schedule and Time Events -> Dynamic Assignment of Daily Work
Schedules -> Dynamic Assignment Based on Clock-Ins
(C) SAP AG HR310 14

7.15
Evaluation and Simulation of Time Data for Future
Periods
Fct
Fct Par1
Par1 Par2
Par2 Par3
Par3 Par4
Par4 D
D Text
Text
CHECK
CHECK FUT
FUT Allow
Allow evaluations
evaluations for
for future
future periods
periods
.. .. ..
IF
IF NOT
NOT SIMF
SIMF No
No simulation
simulation for
for future
future periods
periods
.. .. ..
ELSE
ELSE Simulation
Simulation for
for future
future period
period
COPY
COPY TDT0
TDT0 Provide time data for simulation
Provide time data for simulation
ENDIF
ENDIF Endif
Endif (simulation)
(simulation)
.. .. ..
Fct Par1 Par2 Par3 Par4
P2000
A2003
P2001 1
P2002 1
RTIPA TD70 GEN
SAP AG 1999
You can also run time evaluation for future periods or for periods that end in the future. Evaluation for
future periods triggers a database update. You normally use a special schema that is only valid for
future evaluations.
Simulation for future periods does not trigger a database update. It is used for planning shifts and for
projecting an employee's quota entitlements. Note: If you want to prevent a database update in other
situations, start RPTIME00 using the program option Test run (no update).
You can use function IF to set conditions to control the further processing. IF constructions are formed in
conjunction with functions ELSE and ENDIF.
You can set conditions using a personnel calculation rule. The system supplies some frequently used
conditions. Examples:
IF NEG Time Management status 9 (Recording deviations to the work schedule)
IF POS Time Management status 1 or 2 (Recording all times)
IF EOP Last day of payroll period
You can use parameter 2 of functions P2001 and P2002 to determine that manually recorded attendance
and absence records delimit time pairs already in table TIP.
(C) SAP AG HR310 15

7.16
Data Collection in Schema TM00
Func.
Func. Par1
Par1 Par2
Par2 Par3
Par3 Par4
Par4 D
D Text
Text
.. .. ..
IF
IF NOT
NOT SIMF
SIMF No
No simulation
simulation for
for future
future periods
periods
PERT
PERT TD20
TD20 Evaluate
Evaluate errors
errors from
from pair
pair formation
formation
P2011
P2011 Provide
Provide timetime pairs
pairs and
and daily
daily WS
WS
ACTIO
ACTIO TD10
TD10 End
End ifif the
the daily
daily work
work schedule
schedule still
still active
active
A2003
A2003 Process
Process work
work center
center substitution
substitution
ACTIO
ACTIO TD60
TD60 AB
AB Transfer
Transfer daily WS, if RWH and
daily WS, if RWH and leave
leave
P2001
P2001 Provide
Provide absence
absence data
data
P2002
P2002 Provide
Provide attendance
attendance data
data
PTIP
PTIP TD80
TD80 GEN
GEN Process
Process attendance/absence
attendance/absence reasons
reasons
ACTIO
ACTIO TD90
TD90 Process
Process generated
generated locked
locked records
records
ACTIO
ACTIO TD30
TD30 Dynamic
Dynamic DWS
DWS assignment
assignment -- clock-in
clock-in entry
entry
ELSE
ELSE Simulation for future period
Simulation for future period
COPY
COPY TDT0
TDT0 Provide
Provide time
time data
data for
for simulation
simulation
ENDIF
ENDIF Endif
Endif (simulation)
(simulation)
.. .. ..
SAP AG 1999
Data collection in the schema follows a set sequence.

Two additional personnel calculation rules play an important part in data collection:
Personnel calculation rule TD20 processes the errors generated in pair formation.
Personnel calculation rule TD10 checks whether the daily work schedule of the day to be evaluated is
not yet completed at the time of the evaluation. It terminates processing for the day if the difference
exceeds the value specified in the constant TETOL (Payroll Constants table (T511K)).
(C) SAP AG HR310 16

7.17
Selection Using the Time Management Status
Selection specifications using function CHECK
All personnel numbers

CHECK PON with
with a Time Management status
status
other
other than
than 00 are
are selected
selected
Only
Only personnel numbers
numbers with
with
CHECK NEG
Time
Time Management
Management status 9 are
are selected
selected
SAP AG 1999
Function CHECK uses the Time Management status, which is stored for each employee in the Planned
Working Time infotype (0007), to check whether the employee should be selected for time evaluation
with the relevant schema.
If function CHECK does not feature in the schema with a parameter specifying which employees should
be selected, all employees with the Time Management status 1 or 2 are selected for time evaluation.
Function CHECK can be inserted at any point in the schema.
(C) SAP AG HR310 17

7.18
Data Collection in Time Evaluation: Summary
In this unit, you have learned the functions that

are used to import the planned specifications and
the time infotypes in time evaluation.
You have learned the processing principle
of the internal table TIP.
You know how data is collected in the time
evaluation schema TM00.
SAP AG 1999
SAP AG
(C) SAP AG HR310 18

7.19Data Collection in Time EvaluationExercises
Unit: Data Collection in Time Evaluation

Topic: Providing Time Data
Importing Time Data in a Time Evaluation Schema
1 Assigning costs for works council activities

In your enterprise, times that employees spend active in the works council are documented.
Employees receive special bonuses for working time spent on works council activities.
These bonuses are to be assigned to cost center 2200 Human Resources.
To record times spent on works council activities, use the time data ID BR in the Time
Managers Workplace.
1-1 Record time spent on works council activities, with cost assignment, for your
employee.
1-2 Copy personnel calculation schema TM00, and name it ZM## (where ## = your
group number).
1-3 The recorded attendances may overlap other time data. If you want the recorded
absences to delimit other TIP entries, you can use parameter 2 of function P2002.
In your schema ZM##, modify parameter 2 of function P2002 in such a way that
existing TIP entries are delimited by the recorded attendances.
1-4 Run time evaluation using your schema ZM##, and use the time evaluation log to
check how the recorded attendances are imported within time evaluation.
(C) SAP AG HR310 19

7.20Data Collection in Time Evaluation Solutions
Unit: Data Collection in Time Evaluation

Topic: Providing Time Data
1 Assigning costs for works council activities

1-2 To copy schema TM00, choose Human Resources Time Management
Administration Tools Maintain Schemas. In the Schema field, enter TM00, and
choose Schema Copy.
1-3 To make the import of attendances delimit existing TIP entries, enter an asterisk (*)
in parameter 2 of function P2002.
1-4 The works council activities stored in the Attendances infotype (2002) are imported
to table TIP by function P2002.
Field C1 in table TIP indicates whether a cost assignment is linked to the TIP entry.
The cost information is stored in table C1 of cluster B2.
(C) SAP AG HR310 20

8
Operations as Tools of Time Evaluation
Contents:
Time evaluation operations
Decision operations
Performing calculations
Updating results
Issuing messages
SAP AG 1999
(C) SAP AG HR310 1

8.2
Operations as Tools of Time Evaluation: Objectives

List the principal operations, and describe what
they do
Explain how to find detailed information about
operations
Create and modify a personnel calculation rule
based on a business requirement
SAP AG 1999
SAP AG
(C) SAP AG HR310 2

8.3


Driver RPTIME00

Schemas
SAP AG 1999
(C) SAP AG HR310 3

8.4
Operations as Tools of Time Evaluation:
Business Scenario
Time evaluation determines whether an employee

was scheduled to work on a day being evaluated.
SAP AG 1999
(C) SAP AG HR310 4

8.5
Time Evaluation Operations
Operations that perform

one or more actions
Update results
in table fields Carry out a business
process, generate a
planned pair, for example
Add, multiply,
round values
Decision operations
Operations for
technical control Retrieve and evaluate
information, and update
processing based on result
for example, branch to a
personnel calculation rule
SAP AG 1999
Operations are the basic modules of personnel calculation rules. They carry out elementary processing
steps and influence the structure of the processing and/or the data and values from the internal
processing tables.
(C) SAP AG HR310 5

8.6
Decision Operations
Provide
Provide work
work center
center data
data
OUTWPPERSB
OUTWPPERSB Perform
Perform special
special processing
processing
** ** .....
..... ifif the
the employee belongs to
employee belongs to
XXY Y .....
..... employee
employee subgroup
subgroup XY
XY
Provide
Provide general
general fields
fields
VARSTABSWD
VARSTABSWD Was
Was the
the employee
employee absent
absent for
for the
the
N
N ...
... full
full day?
day? (Yes/No)
(Yes/No)
Y
Y ...
...
VARSTHOLCL
VARSTHOLCL Which
Which public
public holiday
holiday class
class
** .....
..... is
is assigned
assigned to
to the
the day
day being
being
00 .....
..... evaluated?
evaluated?
11 .....
.....
SAP AG 1999
Decision operations control the further processing. To do this, the operation queries conditions that can
be answered as follows, for example:
With Y (Yes) or N (No)
With information on the organizational assignment
With information on the current day
The different methods of processing by a decision operation are depicted in a decision tree. The variable
key is extended by the relevant specification (answer) according to the result of the decision.
Note:
The answer in the variable key must depict each outcome of a decision.
You can use an asterisk (*) to summarize all further outcomes of a decision that do not require special
processing or identical processing. The number of asterisks must correspond to the number of characters
in the answer (for example, time type = ****). A single asterisk also describes the following answer: the
queried field was not filled.
The majority of decision operations start with the letters OUT or VAR. You can display a list of these
decision operations in the HR documentation maintenance. To do so, enter the Document class
Operation (Time Management) or, depending on your view, OPET. In the Object name field, enter
OUT* or VAR*, and choose the possible entries help.
(C) SAP AG HR310 6

8.7
Operation VARST
Was the employee at work? VARSTPRSNT
Was the employee scheduled

VARSTFREE
to work?
Which day type is assigned

VARSTDAYTY
to the day being evaluated?
Is there an absence on the

VARST ______
day being evaluated?
Is there a full-day absence on

VARST ______
the day being evaluated?
SAP AG 1999
Operation VARST is only used as a decision operation. It can be used to enter general status fields
(values from tables, infotypes, data on the weekday, and so on) in the variable key of the personnel
calculation rule.
You use a parameter of operation VARST to query the status fields. The documentation on operation
VARST lists all the possible parameters.
(C) SAP AG HR310 7

8.8
Performing Calculations: Operation HRS
Edit the Number of hours fields
H R S O Y Z Z Z Z Z
Operation
Operation Operator
Operator Operand
Operand
e.g. Origin
Origin indicator
indicator
e.g. ++
== of
of the operand
the operand
--
...
...
SAP AG 1999
The main task of time evaluation is to process and classify time durations. The Number of hours field is
used for calculations.
Operation HRS can be used to fill and change the number of hours field. A number of values can be
referenced, for example:
Number of hours field of an explicitly determined entry in an internal table is provided:
Time type zzzz from table SALDO (period balance table): HRS=Mzzzz
Time type zzzz from table TES (day balances): HRS=Dzzzz
Time type zzzz of previous day: HRS=Lzzzz
Time type zzzz cumulated over the days of the current
payroll period that have already elapsed: HRS=Xzzzz
Number of hours field of an entry in an internal table that is currently being processed is provided:
Current entry from TIP: HRS=Pxxxxx
Current entry from DZL (with function PZL): HRS=Exxx
Current entry from ZML (with function POVT): HRS=Zxxx
Specific number fields:
From infotypes (for example, HRS=I)
Tables (HRS=T....), table specified previously with
operation TABLE
Number fields of the values of a constant zzzzz: HRS=Czzzzz
Explicit values: HRS=2.00
(C) SAP AG HR310 8

8.9
Examples of Operation HRS
Content of current
Number of hours field
Load
Load weekly
weekly working
working hours
hours from
from the
the
HRS=IWEHRS 40.0000
40.0000
Planned
Planned Working
Working Time
Time infotype
infotype (0007)
(0007)
Multiply
Multiply the
the value
value from
from the
the number
number of
of hours
hours
HRS*0.50 20.0000
20.0000
field
field by
by 0.5
0.5
HRS?10.00
HRS?CGLMAX
SAP AG 1999
You can also use operation HRS to compare the contents of two fields.
HRS?PNUM:
Compare value in number of hours field with the number of hours in the current TIP entry
Possible answers:
< Value in Number of hours field is less than the number of hours in the TIP entry.
> Value in Number of hours field is greater than the number of hours in the TIP entry.
= Value in Number of hours field is equal to the number of hours in the TIP entry.
(C) SAP AG HR310 9

8.10
Updating Results: Operations ADD*
Operation ADDDB: Cumulation in internal table TES
A D D D B x x x x y
Operation
Operation Time
Time type
type Control
Control indicator
indicator
TT == Planned
Planned hours
hours
ZZ == Initialization
Initialization
== Subtraction
Subtraction
blank
blank == Addition
Addition
SAP AG 1999
Operation ADDDB (add daily balances) cumulates the value from the number of hours field to the
specified time type and enters the total in the internal day balances table (TES).
Additional important operations that update results:
ADDZL: Operation ADDZL cumulates the value from the number of hours field under the specified
time type and enters it and the clock times in the internal table ZL.
ADDOT: Operation ADDOT enters the wage types in the overtime wage types table ZML. The
operation can be used only in conjunction with function POVT.
(C) SAP AG HR310 10

8.11
Examples of Operation ADDDB
Example 1: Overwrite value

There are 5 hours TES
TES
in time type 9999 HRS=3.00
Day
Daybalances
balances
Time
Time type
type No.
No.
ADDDB9999Z
9999
9999 Test
Test time
time type
type3.0000
3.0000
Example 2: Add value

TES
TES TES
TES
Day
Daybalances
balances Day
Daybalances
balances
HRS=3.00
Time
Time type
type No.
No. Time
Time type
type No.
No.
ADDDB9999
9999
9999 Test
Testtime
time type
type5.0000
5.0000 9999
9999 Test
Test time
time type
type8.0000
8.0000
Example 3: Subtract value

TES
TES
Day
Daybalances
balances
HRS=3.00
Time
Time type
type No.
No.
ADDDB9999-
9999
9999 Test
Test time
time type
type2.0000
2.0000
SAP AG 1999
(C) SAP AG HR310 11

8.12
Issuing Messages: Operation COLER
VARSTFREE Planned hours DWS = 0 ?

N
Y ...
VARSTPRSNT Employee at work

N
Y
COLER00
Message from time evaluation:

"Employee at work although off"
Cluster B1 Cluster B2
ERT FEHLER
Message
Message processing
processing
Download of mail in
in the
the Time
Time Manager's
Manager's
indicator to the Workplace
Workplace
subsystem
SAP AG 1999
If special situations or errors arise during processing, time evaluation can stop for an employee, and/or
messages can be generated and stored in clusters B1 and B2 on the database.
The messages are entered in the message processing function of the Time Manager's Workplace for
postprocessing. You can instruct the system not to generate the same information message or note again
after a recalculation. You can download mail indicators if you use a time recording subsystem that
supports the function.
You can use operation COLER to generate messages if there are errors in time evaluation of which the
administrator should be notified. The code of the message is specified in variable 1 of the operation. You
can define the message codes and corresponding texts under error type 1 in the IMG step: Personnel
Time Management -> Time Evaluation -> Time Evaluation With/Without Clock Times -> Message
Output -> Create Message Descriptions.
You determine how time evaluation reacts to the situation in variable 2 of operation COLER:
COLERxx: Time evaluation continues and a note is generated
COLERxxF: A recalculation indicator is set so that the day is evaluated again; time evaluation
continues
COLERxxE: Time evaluation terminates
COLERxxI: Information is issued. It can be confirmed in the worklist
(C) SAP AG HR310 12

8.13
Exercise: Create a Personnel Calculation Rule
Use personnel calculation schema ZM## (## = group number) for the
following exercise. ZM## is a copy of personnel calculation schema
TM00.
1. Create a new personnel calculation rule Z1## to carry out the

following tasks:
If the employee is at work on a workday, one hour is added to
time type 9000. If there is an absence on the same day, only
half an hour is added to time type 9000. Have the system issue
a note in this case.
2. Incorporate personnel calculation rule Z1## into your personnel
calculation schema.
SAP AG 1999
(C) SAP AG HR310 13

8.14
Decision Tree for Rule Z1##
Planned hours DWS = 0 ?
Yes No
Day type?
0 *
Employee at work?
Yes No
Employee absent?
Yes No
Add 0.5 hours to 9000

Add 1 hour to 9000
Issue a note
SAP AG 1999
(C) SAP AG HR310 14

8.15
Personnel Calculation Rule and Schema Entry
Z1## Exercise HR Time
u l e Z1## Planned hrs DWS = 0 ?

R Day type
Employee at work
Employee absent
. Set
Add day balance
. Set
Add day balance
Note
Schema ZM##
Fct
Fct Par1
Par1 Par2
Par2 Par3
Par3 Par4
Par4 D
D Text
Text
.. Day
Day processing
processing
..
..
PRINT
PRINT TES
TES Time
Time type
type 9000
9000 before
before Z1##
Z1##
000420
000420 ACTIO
ACTIO Z1##
Z1## Exercise
Exercise HR
HR Time
Time
.. PRINT
PRINT TES
TES Time
Time type
type 9000
9000 after
after Z1##
Z1##
..
..
SAP AG 1999
(C) SAP AG HR310 15

8.16
Operations as Tools of Time Evaluation: Summary
In this unit you have:

Learned what the principal time evaluation
operations do
Explain how to find detailed information about
operations
Create and modify a personnel calculation rule
based on a business requirement
SAP AG 1999
SAP AG
(C) SAP AG HR310 16

8.17Operations as Tools of Time EvaluationExercises
Unit: Operations as Tools of Time Evaluation

Topic: Providing Information from an Employee's
Master Data and from Customizing Tables
Working with HR Documentation
1 What do the following lines of a personnel calculation rule mean?

1-1
0 HRS=PNU
M
1 ADDDB99
99
________________________________________
________________________________________
________________________________________
1-2
2 HRS-
IDAHRS
3 ADDDB99
99Z
________________________________________
________________________________________
________________________________________
(C) SAP AG HR310 17

2 Creating a personnel calculation rule
Create a personnel calculation rule (on paper) that enters the planned working time
according to the daily work schedule in time type 9999.
4
5
3 Querying part-time work

Which operation can you use in a personnel calculation rule to query whether an employee
works part-time hours?
(C) SAP AG HR310 18

8.18Operations as Tools of Time EvaluationSolutions
Unit: Operations as Tools of Time Evaluation

Topic: Providing Information from an Employee's
Master Data and from Customizing Tables
1 What do the following lines of a personnel calculation rule mean?

1-1
HRS=PNUM
ADDDB9999
Add the number of hours of the current TIP entry to time type 9999 in table TES.
1-2
HRS-IDAHRS
ADDDB9999Z
Subtract the working hours per day according to the Planned Working Time
infotype (0007) from the value of the current number of hours, and set time type
9999 in table TES to this value.
2 Creating a personnel calculation rule

Enter the planned working time according to the daily work schedule into time type 9999.
HRS=S
ADDDB9999Z
3 Querying part-time work

Operation OUTWP enters values from the work center into the variable key. You can use
operand PARTT to query whether an employee works part-time hours.
(C) SAP AG HR310 19

9
Personnel Calculation Schema TM00
Contents:
Structure of schema TM00
Initialization
Providing time data (reminder)
Tolerances and error checks
Determining planned working times
Determining overtime
Selecting time wage types
Compensating overtime wage types
Managing time accounts
Final processing
SAP AG 1999
(C) SAP AG HR310 1

9.2
Personnel Calculation Schema TM00: Objectives

Explain the meaning of the elementary processing
steps in time evaluation, and how they function
Use the personnel calculation schema TM00 to
control time evaluation
Customize the standard schema TM00 and the
standard personnel calculation rules to suit your
own requirements
SAP AG 1999
SAP AG
(C) SAP AG HR310 2

9.3


Driver RPTIME00

Schemas
SAP AG 1999
(C) SAP AG HR310 3

9.4
Personnel Calculation Schema TM00: Business
Scenario
Attendances and absences are recorded for

employees. The time data is entered into time
evaluation, where it is made available for
further processing.
The system classifies employees' recorded times
by comparing them to the planned specifications.
Time wage types are formed for Payroll and time
accounts are updated.
SAP AG 1999
(C) SAP AG HR310 4

9.5
Structure of a Time Evaluation Schema
Before day processing BINI

BINI
Initialization
Initialization
EINI
EINI
Day processing BDAY

Evaluate
Evaluate data
data for
for each
each day
day
EDAY
After day processing BEND

Final
Final processing
processing
EEND
EEND
SAP AG 1999
The personnel calculation schema is divided into three blocks. Different functions are processed in each
of these blocks.
The first block in the schema (from BINI-EINI) is processed only once for each evaluation, evaluation
period and employee. Groupings are set for each employee and time evaluation run for table accesses.
Day processing (from BDAY-EDAY) is processed once per employee for each day being evaluated.
The final processing block (from BEND-EEND) is processed once only for each evaluation, evaluation
period and employee. The system carries out checks at the end of the period if every day in the period
was evaluated without errors. The results determined are stored at the end of processing.
(C) SAP AG HR310 5

9.6
Day Processing in the Schema
11 12
1
10
2
9
3
8
4
7 6 5
Provide data
Is
Is every-
every-
thing
thing OK?
OK?
Breaks
Planned working
Classify times times
Overtime

.
.
.
.
.
.
.
.
SAP AG 1999
In day processing, time evaluation performs through the following processing steps, in a set sequence:
Imports the day's actual times from the time infotypes and the pair table (time pairs) and the planned
specifications from the daily work schedule. It provides the necessary data from the master data
infotypes and the previous evaluation results.
Carries out error checks for the day being evaluated
Compares the employee's time data with the planned specifications from the personal work schedule
Determines whether the employee has worked overtime and whether it should be approved
Selects time wage types
Determines how any overtime that exists is to be compensated, that is, whether it should be
remunerated and/or compensated with time off
Cumulates the day balances and forms time accounts
(C) SAP AG HR310 6

9.7
Structuring in the Schema: Function BLOCK
Fct Par1 . . . Text PPeerrs

ccaallc soonnnneell
cuula
... sscchhelattiioonn
em
maa
BDAY Day processing
... Log: Time evaluation
...
BLOCK BEG
Provide time data
...
BLOCK END 01/31/2001 Wednesday
Provide time data
BLOCK BEG
Tolerances and error checks Tolerances and error checks
...
BLOCK END .
.
.
... Manage time accounts
...
BLOCK BEG
...
BLOCK END
EDAY End of day processing

...
SAP AG 1999
You can use function BLOCK to structure the time evaluation log. The start and end markings group
together a sequence of time evaluation functions according to their meaning, which appears under the
same node in the log. The parameter BEG in the schema marks the start of a block, the parameter END
the end of a block.
(C) SAP AG HR310 7

9.8
Initialization
Initialization
Provide time data
Determine planned working times
Determine overtime
Final processing
SAP AG 1999
(C) SAP AG HR310 8

9.9
Setting Employee Groupings: Function MOD
ule
PC r T ZZ PAYTP
PAYTP A
A
M OD
Rule
Rule accessed
accessed according
according to
to the
the
employee
employee subgroup grouping for the personnel calculation
subgroup grouping for the personnel calculation rule
rule
ES
ES grouping:
grouping: 11 ES
ES grouping:
grouping: 22 ES
ES grouping:
grouping: 33
Time type: ****
Time type:**** Time type: ****
Time type: **** Time type: ****
Time type: ****
Modif W = 01 Modif W = 02 Modif W = 03

Modif T = 01 Modif T = 01 Modif T = 01
Modif A = 01 Modif A = 01 Modif A = 01
Modif L = 01 Modif L = 01 Modif L = 01
MODIF W : Time wage type selection rule group (V_T510S)

MODIF T : Time type determination group (V_T555Z)
MODIF A : Employee grouping for absence valuation (V_T554C)
MODIF L : Time balance rule group (V_T559P)
SAP AG 1999
Before day processing (initialization block in schema), function MOD is used to determine for each
employee grouping:
Which time wage types are formed
Which time types are formed
How absence are valuated, and so on.
The groupings that time evaluation should use to access the corresponding tables during processing are
specified. To do this, function MOD calls personnel calculation rule MODT.
A personnel calculation subrule is called in rule MODT according to the employee's employee subgroup
grouping for the personnel calculation rule. The groupings for table access are defined here.
You can also control processing individually using the employee grouping for the time evaluation rule in
the Time Recording Information infotype (0050); this is done using PAYTP S.
IMG: Personnel Management -> Personnel Administration -> Payroll Data -> Basic Pay -> Define EE
Subgroup Grouping for PCR and Coll.Agrmt.Prov. (collective agreement provisions)
IMG: Personnel Time Management -> Time Evaluation -> Time Evaluation With Clock Times -> Initial
Steps -> Define Groupings
(C) SAP AG HR310 9

9.10
Providing Time Data
Initialization
Provide time data
Determine overtime
Finalprocessing
Final processing
SAP AG 1999
(C) SAP AG HR310 10

9.11
Providing Time Data in Schema TM00
11 12
10 1
2
9 3
8
7 6
4
Time events
Planned
5
Absence Attendance
working time 10:00 P10 Clock-in
12:45 P20 Clock-out Time 08:00 10:00 Time 13:00 17:00
Function Function Function

P2011 P2001 P2002
TZP
TIP
08.0000 10.0000 0 2 02 A A 01 2.0000
10.0000 12.7500 1 00 P10 P20 E 0001 2.7500
13.0000 17.0000 0 3 03 P P 4.0000
SAP AG 1999
Time data in TM00 is provided using the following functions:

P2011 Import employee's planned specifications to internal table TZP and the pairs
formed from the time postings to internal table TIP
P2001 Import absence from the Absences infotype (2001) to TIP
P2002 Import the attendances from the Attendances infotype (2002) to table TIP
PTIP TD80 GEN Provide attendance/absence reasons
(C) SAP AG HR310 11

9.12
Tolerances and Error Checks
Initialization Process
tolerances
Provide time data
Tolerances and error checks Adjust

absences
Determine overtime Error checks

for each day
Error checks
for each TIP entry
Final processing
SAP AG 1999
(C) SAP AG HR310 12

9.13
Error Checks: Rule TE10
Rule TE10: Adjust absences
Scenario 1 Postings: Absence:

Clock-in 08:00 12:00 - 17:00
Clock-out 11:50
Rule TE10
At work Absence
Absence
08:00 11:50 12:00 17:00
Message
Scenario 2 Postings: Absence:

Clock-in 08:00 12:00 - 17:00
Clock-out 12:05
Rule
Rule
TE10TE10
At work ??? Absence

Absence
08:00 12:05 17:00
SAP AG 1999
Personnel calculation rule TE10 compares the absences of less than one day with the day's attendances.
According to the relative position of the absence, a note or a message is included in the error table. If
attendances and absences overlap, operation INSTP is used to reduce the absence.
Personnel calculation rule TE10 is accessed via function PTIPA.
(C) SAP AG HR310 13

9.14
Error Checks for Each Day: Rule TE20
Decision tree: Daily WS off?

N
N Y
Y
EE at work?
EE at work?
N
N Y
Y
N
N Y
Y
Absence Full-day
ok
ok Message
recorded? absence? Message
Y
Y N
N
Error
Error Day type?
Y
Y
N
N
** 11 22
Gen.
Gen. DAILY
DAILY WS
WS
Day type? Day type? ok
ok plnd
plnd pair
pair off
off
Day
Day types:
types:
** 11 22 ** 11 22 blank
blank == work,
work, paid
paid
11 == off,
off, paid
paid
Gen.
Gen. DAILY
DAILY WS
WS Rule
Rule DAILY
DAILY WS
WS 22 == off,
off, unpaid
unpaid
Error
Error ok
ok
plnd
plnd pair
pair off
off TE21
TE21 off
off
SAP AG 1999
Personnel calculation rule TE20 checks whether employees have to be at work on certain days, or if they
are not permitted to be at work (illness, public holiday, leave, and so on). An error is generated if, for
example, the employee is absent without permission.
To obtain results for a paid public holiday (for hourly wage earners, for example), the system generates a
TIP entry based on the planned working times in the daily work schedule (planned pair).
If an absence has been recorded on a public holiday, you can use personnel calculation rule TE21 to
define whether this day is evaluated as an absence or as a public holiday.
Personnel calculation rule TE20 is accessed using function ACTIO.
(C) SAP AG HR310 14

9.15
Error Checks for Each Pair: Rule TE30
Status from
Table TIP
pair formation
Ex. 1: Start End 1 .... Complete,
08.0000 17.0000 error-free pair
Ex. 2: Error:
Start End 1 ....
Clock-in missing
17.0000 2
Ex. 3: Compare end of

Start End 1 ...
Is employee scheduled planned working time
22.0000 3 to be still at work? with system time
End of planned
working time 06:00 Yes No
No error: Error:
Start End 1 ....
delimit pair, Clock-out missing
22.0000 30.0000 3 set recalculation
SAP AG 1999
Pair formation assigns each pair a status, which defines whether a time pair was able to be formed
correctly.
Personnel calculation rule TE30 performs error checks for each TIP entry being evaluated. Depending on
the missing posting (clock-in, clock-out, end of off-site work), it performs the following actions:
It issues an error message and terminates
It checks whether the employee could still make the posting theoretically, since the end of the planned
working time has not yet been reached or lies in a tolerance interval defined by the constant DELIM.
You can use the constant DELIM (constants table T511K) to define the duration within which a
missing clock-out entry is automatically replaced by the end of planned working time; this happens as
of the end of the planned working time.
It uses operation DELIM to delimit the open pair with the start or end of the planned working time. It
performs a preliminary evaluation for the day, and sets a recalculation.
Personnel calculation rule TE30 is accessed using function PTIP (Process internal table TIP).
Notes:
As an alternative to TE30, you can use personnel calculation rule TE31, which does not delimit
incomplete pairs automatically, but instead ends time evaluation with corresponding messages.
The "difficult" errors to which pair formation could not assign a status are intercepted by personnel
calculation rule TD20.
(C) SAP AG HR310 15

9.16
Functions for Calling Personnel Calculation Rules
eral ACTIO Example TE20

Gen ation
m
infor
Processing table TIP

on
f ormati ntries PTIP Example TE30 tion
In TIP e p era P
f ro m O LO
PTIPA Example TE10 CO
Reading table TIP
RTIP Example TR10
RTIPA Example TP20
SAP AG 1999
Function ACTIO accesses a personnel calculation rule that carries out processing regardless of the
existence of TIP entries (for example, checking the current day for errors, determining the flextime
balance).
Function PTIP accesses a personnel calculation rule that processes the content of table TIP according to
the rule. Each TIP entry is processed according to the specified personnel calculation rule. If a TIP entry
is still available after processing, it must be transferred from the personnel calculation rule to the output
table TOP by operation COLOP* (except for operations that generate a TIP entry, such as INSTP,
GENTG, INSLR or GENTP). After all the TIP entries have been processed, table TOP is converted to
the new table TIP.
Function RTIP accesses a personnel calculation rule that reads the content of table TIP according to the
rules. Function RTIP works in exactly the same way as function PTIP, with the restriction that no
changes can be made to the TIP entries.
Functions PTIPA and RTIPA correspond to functions PTIP and RTIP respectively; the only difference is
that they are processed only if there is an absence on the current day.
(C) SAP AG HR310 16

9.17
Tolerance Times: Function DPTOL
Specifications
Specifications from
from the
the daily
daily work
work schedule
schedule
Start
Start of
of planned
planned working
working time:
time: 07:00
07:00
Start
Start tolerance:
tolerance: 07:00
07:00 -- 07:05
07:05
Scenario 1: Clock-in entry: 07:03
Start time in TIP: Start time in TIP:

DPTOL
07.0500 07.0000
Scenario 2: Clock-in entry: 07:07
Start time in TIP: Start time in TIP:

07.1167
DPTOL 07.1167
SAP AG 1999
Function DPTOL is used to edit TIP entries according to the start and end tolerances in the daily work
schedule. If an employee clocks in during the tolerance interval, for example, all further calculations are
based on the start of planned working time.
Alternatively, or in addition to DPTOL, you can use the standard personnel calculation rule TL10 to
round the first and last TIP entry according to the employee subgroup. Operation ROUND is used for
this purpose.
(C) SAP AG HR310 17

9.18
Determining Planned Working Times
Initialization
Provide time data Planned hours
Determine planned working times Breaks
Determine overtime
Absences
Finalprocessing
Final processing
SAP AG 1999
(C) SAP AG HR310 18

9.19
Two Important Objectives of Time Evaluation
Processing types Time types

S - Planned work 0010 - Attendances
M - Overtime 0030 - Recorded attendances
A - Absence from infotype 2002
P - Attendance 0040 - Overtime
X - Attendance on public holiday 0050 - Productive hours
Time wage type selection Balance formation
Time wage types Balances/time accounts
SAP AG 1999
Balances are formed using time types. Time wage types are formed according to the processing type of
the TIP entry.
What are time types and processing types?
Time type
The time types and the number of hours in the various TIP entries are cumulated to form time
balances.
Processing type
The time wage types are selected according to the processing type
Examples:Processing type S -> Wage types for planned work
Processing type M -> Overtime wage types
(C) SAP AG HR310 19

9.20
Assigning Time Type/Processing Type According
to the Time Identifier and Pair Type
TZP
Time
Time Time
Time ID
ID Break
Break duration
duration
00.0000 01 TIP
00.0000 01 Overtime
Overtime hours
hours
07.0000
07.0000 02
02 Fill
Fill time
time Start
Start End
End PP ID
ID TTyp
TTyp Number
Number
09.0000
09.0000 05
05 Fill
Fill time
time break
break 0.50
0.50 08.0000
08.0000 10.5000
10.5000 22 2.5000
2.5000
09.5000
09.5000 02
02 Fill
Fill time
time
12.0000
12.0000 05
05 Fill
Fill time
time break
break 0.75
0.75
Function
TIMTP
V_T555Z
PSGrpg
PSGrpg Group
Group ID
ID From
From To
To PairType
PairType 00 PairType
PairType 33
01
01 01
01 01
01 01/01/1990
01/01/1990 12/31/9999
12/31/9999 0310
0310 0320
0320 0330
0330
01
01 01
01 02
02 01/01/1990
01/01/1990 12/31/9999
12/31/9999 -- P
P 0110
0110 A
A 0120
0120 P
P 0130
0130
...
...
01
01 01
01 05
05 01/01/1990
01/01/1990 12/31/9999
12/31/9999 -- K
K 0510
0510 0520
0520 K
K 0530
0530
...
...
TIP
Start
Start End
End PP ID
ID P
P TTyp
TTyp Number
Number
07.0000
07.0000 08.0000
08.0000 00 02
02 0000
0000 1.0000
1.0000
08.0000
08.0000 09.0000
09.0000 22 02
02 A
A 0120
0120 1.0000
1.0000
09.0000
09.0000 09.5000
09.5000 22 05
05 0520
0520 0.5000
0.5000
09.5000
09.5000 10.5000
10.5000 22 02
02 A
A 0120
0120 1.0000
1.0000
10.5000
10.5000 12.0000
12.0000 00 02
02 0000
0000 1.5000
1.5000
...
...
SAP AG 1999
Function TIMTP is used to merge the TIP entries (actual times) with the daily work schedule in table TIP
(planned times). This results in new TIP entries.
The TIP entries are assigned a description of their position relative to the daily work schedule (time
identifier). The time identifier of the newly formed TIP entries determines whether the times are in the
core time, fill time, time outside the daily work schedule, and so on.
The time identifier is used to assign a processing type and a time type to each new TIP entry according to
the pair type. To do this, function TIMTP reads the entries that are defined in the Customizing settings in
the Time Type Determination view (V_T555Z).
The function also carries out the following activities:
Planned times for which there are no corresponding actual times are assigned TIP entries with the pair
type 0
The resulting TIP entries are assigned a processing type and a time type according to the Time Type
Determination view (V_T555Z).
IMG: Personnel Time Management -> Time Evaluation -> Time Evaluation With Clock Times -> Time
Data Processing -> Set Time Type Determination
(C) SAP AG HR310 20

9.21
Comparing Times: Function TIMTP
08:00 10:30 19:00
: Absent: At work:
e TIP
T ab l p e
t y Pair type 2 Pair type 1
Pair
TIMTP
Core time
Overtime
Core time
Core time
Fill time
Fill time
Fill time
Fill time
P:
hours
e TZ
Break
Break
r
Tabl identifie
T i m e
02 03 05 03 02 05 02 03 02 01
09:00 10:30 12:00 14:00
10:00
07:00 08:00 09:30 11:30 13:30 16:00 18:00 19:00
0 2 2 2 2 1 1 1 1 1 1 1
e TIP
Tabl IM TP:
T
after pe and 02 02 03 05 03 03 02 05 02 03 02 01
ty
Pair dentifier
e i
Tim
SAP AG 1999
A new TIP entry is formed in table TIP for each new time point in the daily work schedule. In this
process, the entries from TIP are compared with those in TZP.
(C) SAP AG HR310 21

9.22
Layout of the Time Type Determination View
Not At work Absent Off-site (time posting)

at work Planned pair (IT2001) At work (IT2002)
IF T = 01
MOD
Overtime hours 0310 0320 0330
Fill time K 0000 P 0110 A 0120 P 0130
Core time K 0235 P 0210 A 0220 P 0230
Core time break K 0000 K 0510 0520 K 0530
Fill time break K 0000 K 0510 0520 K 0530
Break, paid K 0000 A 0540 A 0540 A 0540
Overtime break,
K 0510 0520 K 0530
unpaid
Overtime break,
M 0540 M 0540 M 0540
paid
Break during
K 0000 K 0510 0520 K 0530
overtime hours
SAP AG 1999
In the Time Type Determination view (V_T555Z), you define which time types and processing types the
TIP entries are assigned, based on the time identifier and the pair type:
Pair type 0: Unrecorded times
Pair type 1: Attendances from time postings and planned pairs
Pair type 2: Absences (infotype 2001)
Pair type 3: Attendances (infotype 2002) and off-site work postings
You can assign the following processing types as a default for time wage type formation:
S: Pair is included in the daily calculation of planned time, without a maximum working time
per day
M:Pair is valuated as an overtime pair; the time is not included in the daily planned working time
P: Pair is valuated as an attendance pair; that is, the time is included in the daily calculation of
planned time
A: Pair is valuated as an absence pair; that is, the time is included in the daily calculation of planned
time
"-": Pair is deleted at a later stage
" ": Pair is not valuated as productive time
(C) SAP AG HR310 22

9.23
Processing Breaks: Definition of Work Breaks
12
Recording
Recording with
with clock
clock times
times
Breaks
Breaks at at fixed
fixed times:
times:
9 3 12:00
12:00 -- 12:30
12:30 0.5
0.5 hours,
hours, unpaid
unpaid
Breaks
Breaks within
within aa specific
specific time
time interval:
interval:
12:00
12:00 -- 13:00
13:00 0.25
0.25 hours,
hours, paid
paid
0.25
0.25 hours,
hours, unpaid
unpaid
6
12
Recording
Recording with
with or
or without
without clock
clock times
times
Dynamic
Dynamic breaks:
breaks:
After
After 44 hours
hours 0.25
0.25 hours,
hours, paid
paid
9 3 0.25
0.25 hours,
hours, unpaid
unpaid
SAP AG 1999
The following information is specified for each break in the work break schedule:
What time the break starts or how many hours the employee must work before taking a break
Whether the break is paid
What duration of the break is paid
The length of the break is the total of the paid break plus the unpaid break.
Note: You can use function DYNBR to control the position of the dynamic breaks. Function DYNBR
must be before function TIMTP in the schema.
Example: Counting starts with the first clock-in time, and not with the start of planned working time
(standard processing).
IMG: Personnel Time Management -> Work Schedules -> Daily Work Schedules -> Define Break
Schedules
Data Processing -> Break Processing -> Set Start of Break Dynamically
(C) SAP AG HR310 23

9.24
Evaluating Break Durations: Function PBRKS
Problem: How are variable breaks set?
Scenario 1:
PBRKS Break in TIP

0.5 hrs break Par 2 user-
defined 12:00 - 12:30
12:00 14:00
Scenario 2:
PBRKS 1 Break in TIP
12:00 - 12:30
0.5 hrs break

Break in TIP
12:00 13:00 14:00
PBRKS 2 13:00 - 13:30
SAP AG 1999
Function PBRKS evaluates the break specifications from the daily work schedule.
You use Parameter 2 of function PBRKS to define the sequence in which the TIP entries for the break
are calculated:
1 Unrecorded times (pair type 0) first, then all others in chronological order
2 Absences (pair type 2) first, then unrecorded times (pair type 0), then all others in chronological
order
3 Absences (pair type 2) first, then attendances or off-site work postings (pair type 1/3), then all
others in chronological order
4 Unrecorded times (pair type 0), then absences (pair type 2), then all others in chronological order
5 Attendances or off-site work postings (pair type 1/3) first, then unrecorded times (pair type 0),
then absences (pair type 2)
6 Attendances or off-site work postings (pair type 1/3) first, then absences (pair type 2), then
unrecorded times (pair type 0)
7 Unrecorded times (pair type 0) first, then attendances or off-site work postings (pair type 1/3),
then absences (pair type 2)
Data Processing -> Break Processing -> Determine Break Times
(C) SAP AG HR310 24

9.25
Opening Break Frames: Function PBRKS
Personal work schedule 0.5 hrs break
08:00 12:00 13:45 14:00 14:15 16:30
Problem: Is 13:45 - 14:15 a break?
Par 3
PBRKS 1 ALL PBRKS 1
Break frame opened Break frame not opened

Break within unrecorded time Attendance reduced
TIP Break TIP
Start End P ID PTypTTyp Number Start End P ID PTypTTyp Number
08.0000 13.7500 3 02 P 0130 4.7500 08.0000 12.0000 3 02 P 0130 4.0000
13.7500 14.2500 0 05 K 0000 0.5000 12.0000 12.2500 3 05 K 0530 0.2500
14.2500 16.5000 3 02 P 0130 2.2500 12.2500 13.7500 3 02 P 0130 1.5000
13.7500 14.0000 0 05 K 0000 0.2500
14.0000 14.2500 0 02 K 0000 0.2500
14.2500 16.5000 3 02 P 0130 2.2500
SAP AG 1999
In parameter 3 of function PBRKS, you specify how unrecorded times are processed:

blank: Only times within the break frame are counted

AFT: Unrecorded times immediately after the break frame are included in the calculation

BEF: Unrecorded times immediately before the break frame are included in the calculation

ALL: Unrecorded times immediately before and after the break frame are included in the
calculation
ABE: All unrecorded times before the break frame are included in the calculation
In parameter 4 of function PBRKS, you specify which TIP entries are taken into account in break
processing. Parameter 4 is only relevant if partial-day attendances or absences are recorded.
OWTI: Breaks are only generated for pairs with clock times
NOTI: The clock times of the pairs are ignored. Breaks must be defined in the break schedule/
daily work schedule in the form "after x hours".
(C) SAP AG HR310 25

9.26
Calculating Planned Working Time: Function
DEFTP
Personal work schedule
08:00 11:00 16:30 17:00
TIP Start End P ID PTypTTyp Number

08.0000 11.0000 2 02 A 0120 3.0000
11.0000 12.0000 3 02 P 0130 1.0000
12.0000 12.5000 3 05 K 0530 0.5000
12.5000 16.5000 3 02 P 0130 4.0000
16.5000 17.0000 3 01 0330 0.5000
S Function Maximum daily

A,P DEFTP working time
TIP Start End P ID PTypTTyp Number TES A P P P P P

A
08.0000 11.0000 2 02 S 0120 3.0000 P PA P P
11.0000 12.0000 3 02 S 0130 1.0000 P
12.0000 12.5000 3 05 K 0530 0.5000 P
12.5000 16.5000 3 02 S 0130 4.0000
16.5000 17.0000 3 01 0330 0.5000 8 hrs 5 hrs
Time type 0000 0001
SAP AG 1999
Function DEFTP is used to determine the planned work TIP entries. The function assigns the processing
type S to TIP entries with processing types A and P, thereby ensuring that processing type S is assigned
until (at most) the maximum daily working time is reached.
You can determine the maximum daily working time in the Daily Work Schedule view (V_T550A). (In
the case of part-time employees, this information is overwritten by the maximum working time in the
Planned Working Time infotype (0007)). If there is no information in the daily work schedule, function
DEFTP uses the value of the constant TGMAX from the Payroll Constants view(V_T511K).
Function DEFTP collects all attendance and absence times in utility time type 0000, and all attendances
in utility time type 0001. Both time types are used for determining overtime and for reducing absences.
TIP entries with processing type "-" are deleted.
Data Processing -> Indicate Planned Working Time Pairs
(C) SAP AG HR310 26

9.27
Reducing Absences: Rule TP10
S:
e DW s
ti m our
Flex ned h
an
8 pl Planned working time frame
08:00 11:00 17:00 18:00
Problem: Planned hours exceeded

Reduce absence?
V_554S_E,
PTIPA TP10 Class for time evaluation
TIP
Start End
Rule TP10
P ID PTypTTyp Number
08.5000 11.0000 2 02 S 0120 2.5000 Absence reduced
11.0000 12.0000 3 02 S 0130 1.0000
12.0000 12.5000 3 05 K 0530 0.5000
12.5000 17.0000 3 02 S 0130 4.5000
17.0000 18.0000 0 02 K 0000 1.0000
SAP AG 1999
In personnel calculation rule TP10, you can reduce certain absences of less than one day so that they do
not increase the flextime balance, that is, the planned specifications are not exceeded by particular
absences.
You specify which absences you want to be reduced by grouping the absence into classes for time
evaluation in the Absence: Time Evaluation view (V_554S_E).
The flextime balance represents the difference between the working time that is calculated as planned
work and the planned working hours stipulated in the daily work schedule. The following count as
planned work, for example:
Attendances
Paid leave
Sickness with certificate
Overtime
Data Processing -> Shorten Absences of Less Than One Day
(C) SAP AG HR310 27

9.28
Determining Overtime
Initialization
Provide time data
Determine overtime
Finalprocessing
Final processing
SAP AG 1999
(C) SAP AG HR310 28

9.29
Processing Overtime
08:00 16:30 19:30
Question: Does overtime exist between

16:30 and 19:30 ?
Overtime approval:
general
Determine overtime:
employee-specific
Identify TIP pairs with processing type M
Select time wage types :

Overtime wage types
Bonuses
Compensate overtime:
.
.
.
.
Time off
Remuneration
SAP AG 1999
Overtime processing consists of the following steps:
1. Overtime is determined. The employee's overtime approvals are checked, if necessary. The hours
of overtime are assigned processing type M.
2. Time wage type selection for the overtime. The overtime wage types formed are stored in a
special internal table, ZML.
3. The overtime wage types stored in ZML are compensated, either with remuneration or with time
off.
Example:
Employees receive an overtime bonus as remuneration and time off in lieu of the hours of overtime they
have worked.
(C) SAP AG HR310 29

9.30
Methods of Overtime Approval
General
General overtime
overtime approval
approval
for
for all
all employees
employees who
who have
have
worked
worked overtime
overtime
TO16
TO16 TO11
TO11
General
General overtime
overtime approval
approval
via
via the
the current
current Determine
Determine TIPTIP Planned
Planned hours
hours completed?
completed?
daily
daily work
work schedule
schedule entries
entries with
with time
time TGMAX
TGMAX not
not exceeded?
exceeded?
Overtime
Overtime automatic
automatic == X
X TO15 identifier
identifier "01"
"01"
Overtime
Overtime hours
hours =>
=> overtime
overtime
Employee-specific TO10
General
General overtime
overtime == X
X
Employee-specific
Employee-specific general
general overtime
overtime
approval
approval in
in the
the Time
Time Recording
Recording
Information
Information infotype
infotype (0050)
(0050)
General
General overtime
overtime == A-Z
A-Z Customer-specific
except
except X
X or
or 0-9
0-9 personnel calculation rule
Overtime
Overtime approval
approval via
via GOT TO20 01
attendance
attendance quota
quota (2007)
(2007) GOT TO20 02
SAP AG 1999
An important factor in overtime determination is the check as to whether the employee being evaluated
is permitted to work overtime, and if so, how many hours. This depends on whether an overtime
approval is necessary for determining hours of overtime.
Schema TM00 contains several standard solutions for evaluating overtime approvals. These range from
evaluating a general overtime approval for all employees, to evaluating individual approvals for a
particular period and number.
(C) SAP AG HR310 30

9.31
Attendance Quotas (Infotype 2007)
Valid: 01/01/yyyy - 01/31/yyyy
Type:: 01 Views V_T556P and V_566P_B
Variant 1:
When and for how many
Number: 20 hours
hours is the employee
permitted to work overtime?
Variant 2:
How is the overtime Time: 16:30-18:00

compensated?
Remuneration
Time off Variant 3:
Time: 16:30-18:00
Number: 20 hours
Overtime
compensation
type
SAP AG 1999
The processing of employee-specific overtime approvals in time evaluation is dependent on the

following factors:
If there is no attendance quota (overtime approval) for the current day, there is no overtime processing
If an attendance approval exists, the processing depends on how it was recorded:
For attendance quotas without clock times, attendance times outside the working time frame are
used for determining overtime
For attendance quotas with clock times, only TIP entries within the specified interval are processed
You can use fast entry functions in the Attendance Quotas infotype (2007) to create overtime approvals
for different groups of employees quickly and easily.
In the Attendance Quotas infotype (2007), you can assign an overtime compensation type to control how
the overtime is remunerated or compensated.
IMG: Personnel Time Management -> Time Data Recording and Administration -> Managing Time
Accounts Using Attendance/Absence Quotas -> Time Quota Types -> Define Attendance Quota Types
(C) SAP AG HR310 31

9.32
Determining Overtime: Function GOT
Personal work schedule Attendance quota
08:00 16:30 19:00 19:30

TIP Start End P ID PTyp TTyp Number
08.0000 12.0000 3 02 S 0130 4.0000
12.0000 12.5000 3 05 K 0530 0.5000 Does an attendance quota
12.5000 16.5000 3 02 S 0130 4.0000
16.5000 19.5000 3 01 0330 3.0000
exist?
Has the planned time been
exceeded?
Function
Has the maximum daily
GOT TO20 01 working time been reached?
TIP Start End P ID PTyp TTyp Number

08.0000 12.0000 3 02 S 0130 4.0000
12.0000 12.5000 3 05 K 0530 0.5000
12.5000 16.5000 3 02 S 0130 4.0000
16.5000 19.0000 3 01 M 0040 2.5000
19.0000 19.5000 3 01 0330 0.5000 No attendance quota exists
SAP AG 1999
The following prerequisites must be fulfilled before overtime on the basis of attendance quotas can be
determined:
The employee has an overtime approval
The planned working time in the daily work schedule has been completed
The attendances do not exceed the daily maximum working time, which you can specify in the daily
work schedule or in constant TGMAX
Personnel calculation rule TO20 checks whether the conditions have been observed for each TIP entry.
Function GOT requires valid overtime approvals before it determines overtime. GOT . XX checks
whether there is an attendance quota (infotype 2007) with the attendance quota type XX in parameter 2
on the current day, and compares the quota with the time data from TIP.
Data Processing -> Determining Overtime -> Determine Overtime from Attendance Quotas
(C) SAP AG HR310 32

9.33
Significance of the Processing Type and the Time
Type
Classification of times
TIP
Start To Proc.type Time type No.
12.5000 16.5000 S 0130 4.0000

16.5000 19.0000 M 0040 2.5000
Time wage type selection: Balance formation

Form wage types Time accounts
DZL ZML TES

Compensate
overtime
ZL ZES
DZL SALDO Time quotas
Payroll
SAP AG 1999
After overtime has been determined, all the information is available for valuating the times. The TIP
entries can now be used to:
Select time wage types for Payroll according to the processing types
Form balances according to the time types. The balances are then used for managing time accounts.
Time evaluation saves the results determined in further processing in internal tables:
Balances in TES (daily balances)
Time wage types in tables DZL (hourly wage and bonuses) and ZML (overtime). After overtime
determination, the overtime wage types are transferred to table DZL
At the end of time evaluation, the results determined are saved to the database:
Balances in ZES (daily balances, Cluster B2) and SALDO (period balances, Cluster B2). The
Attendance Quotas (2007) and Absence Quotas (2006) infotypes are updated, if necessary.
Time wage types are entered in table ZL at the end of time evaluation. Table ZL forms the interface to
R/3 Payroll.
(C) SAP AG HR310 33

9.34
Selecting Time Wage Types
Initialization
Provide time data Time wage type

selection rule group
Function
Determine planned working times DAYMO
Determine overtime
The principle of
Select time wage types the rule group
Time wage type
Manage time accounts selection
Finalprocessing
Final processing
SAP AG 1999
(C) SAP AG HR310 34

9.35
Time Wage Type Selection
TIP
Start End Proc.type No.
12.5000 16.5000 S 4.0000

16.5000 19.0000 M 2.5000
Rules for selecting

.
.
.
.
Function time wage types
.
.
.
.
Time wage type selection (V_T510S)
GWT S DZL GWT M ZML
TIP entries for planned working times TIP entries for overtime
Hourly wage Overtime

Bonuses DZL ZML wage types
SAP AG 1999
In time wage type selection, time wage types are formed from the TIP entries. These time wage types are
then passed on to Payroll, where they are used to determine the gross pay.
Time wage types are selected according to the processing type of the TIP entry. You specify the
processing type for which you want wage types to be selected in parameter 2 of function GWT
(Generate Wage Types).
Planned work wage types are transferred to internal table DZL after time wage type selection, and
overtime wage types are transferred to internal table ZML. You specify in parameter 3 of function GWT
which wage types are transferred to which table.
In the Time Wage Type Selection Rule view (V_T510S), you set regulations according to which time
wage types are selected. These can be in relation to employees, days, and times.
Examples:
You want wage types to be selected for hourly wage earners' planned times, but not for employees
with a fixed salary.
You want different wage types to be selected for work on a public holiday than for a working day.
You want wage type Mxxx to be selected for up to two hours of overtime, and wage type Myyy for
each additional hour of overtime.
(C) SAP AG HR310 35

9.36
Time Wage Type Selection Rule Group
Function MOD,
MOD, Personnel calculation rule MODT
Hourly
Hourly wage
wage earner
earner Salaried
Salaried employee
employee Salaried
Salaried employee
employee
MODIF
MODIF W
W = 01 MODIF W == 02
02 MODIF
MODIF W
W = 03
Hourly wage Bonuses Bonuses

Bonuses Overtime (Overtime as of 10
Overtime extra hours)
SAP AG 1999
You can use the time wage type selection rule group to set specific regulations for time wage type
selection according to an employee's organizational assignment.
In personnel calculation rule MODT, you determine the time wage type selection rule group that time
evaluation uses to access the entries in the time wage type selection table when it is evaluating an
employee. Personnel calculation rule MODT is accessed via function MOD. It is in the initialization
block in the schema.
You can use a personnel calculation rule and operation MODIF W to determine a time wage type
selection rule group in day processing in time evaluation. You can access the table entries according to
criteria which are only available in day processing (for example, the employee's daily work schedule,
Time Management status).
(C) SAP AG HR310 36

9.37
Time Wage Type Selection: Function DAYMO
Set day grouping for time wage type selection
Condition for the day
No public holiday No public holiday Public holiday Public holiday

Monday - Saturday Sunday Monday - Saturday Sunday
PAR 1 PAR 2 PAR 3 PAR 4
DAYMO 01 02 02 02
Day grouping
SAP AG 1999
Function DAYMO sets the day grouping for time wage type selection from the Time Wage Type
Selection table (T510S) to a particular value, depending on the day type.
If the four day categories are not sufficient for your purposes, you can also set the day grouping in a
personnel calculation rule using operation MODIF D=xx.
(C) SAP AG HR310 37

9.38
Principle of the Rule Group: An Example from
Time Wage Type Selection
Rule
g roup
No public holiday
Mon - Sat
Sequential number of
Time wage type rules for time wage
Day grouping
selection rule group
type selection
TIP 01 01 001 Normal hours Wage type MI10
01 01 050 Overtime 25% Rule not observed
01 01 055 Overtime 50% Rule not observed
01 01 070 Night bonus 35% Wage type MQ30
01 01 075 Night bonus 35% Rule not observed
01 02 070 Night bonus 35%
01 02 080 Sunday bonus
SAP AG 1999
Some time management rules for selecting values from tables are so extensive that they can only be
represented by grouping individual rules into rule groups. This ensures that all possible business
regulations can be represented for one employee group.
The system has two options for processing the entries in a rule group:
It processes the individual rules consecutively until it finds the correct one, and then terminates
processing
It processes all the individual rules
In time wage type selection, all the individual rules you have created per time wage type selection rule
group and day grouping are processed for all TIP entries.
You should create the sequential numbers for time wage type selection in multiples of ten, so that you
can add lines at a later stage, if necessary.
(C) SAP AG HR310 38

9.39
Time Wage Type Selection: Structure of a Rule (1)
Bloc
k ning
Mea
Valid processing types For what type of TIP entries?
(planned pairs, overtime pairs)
Conditions for the day On which days?

Weekday
Working day, weekend
Public holiday
Conditions for the time 10

1112 1
2
In which time interval? 9 3
8 4
Within which limits? 7 6 5
Determination of value limits?
Control Control by fixed values?

Exit rule?
SAP AG 1999
In time wage type selection, you define in an individual rule several conditions that must be fulfilled
before a wage type is selected for the employee. If even one of the conditions specified in the rule is not
fulfilled, the wage type is not selected.
So that time wage type selection rules for which start and end times are specified as a condition can be
selected, all the TIP entries for the day being evaluated must contain clock times. If TIP entries without
clock times exist for a day, the time wage types for which the time interval is filled are not selected on
that day.
You can use the Fixed val. field to assign a certain number, regardless of the hours worked. This enables
you to form a rule for guaranteed hours, for example.
You can use the exit rules in time wage type selection to end processing of a rule or of time wage type
selection if a particular time wage type is selected.
Wage Type Selection and Overtime Compensation -> Define Generation Rules
(C) SAP AG HR310 39

9.40
Time Wage Type Selection: Structure of a Rule (2)
Conditions for the time 1112 1

10 2
9 3
8 4
Time
Time interval:
interval: 7 6 5
n?
Whe 20:00 30:00
Value limits Number of hours

explicit symb.
Plnd hrs
n?
wh e Lower limit: S acc. to DWS
From
w hen? Upper limit:

Until
Processing types
S M
ination to be counted:
Deter m mit s?
e li Interval:
of valu
SAP AG 1999
If you only want the wage type to be selected if the TIP entry lies in a particular time period, you can
enter start and end times. This is relevant mainly for selecting night bonuses. Permitted values are
between 0:00 and 47:59 ( = 23:59 on the following day).
If a TIP entry lies only partially within the interval, the wage type is generated only for the period within
the interval.
Upper and lower limits:
If you want upper and lower limits to be evaluated, you can take account of TIP entries with up to four
processing types; these are independent of the processing type used to start GWT. You specify the
processing types to be counted in the field of the same name.
If you only want the wage type to be selected if there is a certain number of hours in the processing
type on the day in question, enter the number of hours in the Min. field. If you only want the wage
type to be generated up to a certain number of hours in the processing type, enter the number of hours
in the Max. field.
If you want to define rules governing the fulfillment of planned hours, for example, for part-time
employees, you can enter predefined symbols instead of a number of hours.
If you have set upper and lower limits and a time interval, you can then activate the Interval field to
specify that only the TIP entries that lie within the specified interval are used for determining the upper
and lower limit.
(C) SAP AG HR310 40

9.41
Selecting Time Wage Types: Function GWT
Select planned time and overtime wage types

1. Wage type for planned working time:
Function GWT with parameter S
V_554C_E
TIP DZL
Start
Start End
End Proc.type
Proc.type AB
AB No.
No. GWT S DZL WTyp
WTyp IFTYP
IFTYP No.
No.
08.0000 10.0000
08.0000 10.0000 S
S 01
01 4.0000
4.0000 MI10
MI10 A
A 4.0000
4.0000
10.0000
10.0000 13.0000
13.0000 S
S 3.0000
3.0000 MI10
MI10 S
S 3.0000
3.0000
14.0000
14.0000 16.0000
16.0000 S
S 02
02 2.0000
2.0000 V_T510S
Entry is not processed

2. Wage type for overtime:
according to "as if" principle
Function GWT with parameter M
TIP ZML
Start
Start End
End Proc.type
Proc.type AB
AB No.
No. GWT M ZML WTyp
WTyp Versl
Versl IFTYP
IFTYP No.
No.
17.0000
17.0000 18.0000
18.0000 M
M 4.0000
4.0000 MM10
MM10 M
M 2.0000
2.0000
V_T510S MM20
MM20 M
M 2.0000
2.0000
SAP AG 1999
Function GWT selects time wage types for TIP entries according to the rules in the Time Wage Type
Selection Rule view (V_T510S).
GWT S DZL: Time wage types for planned work
TIP entries with processing type S are processed in time wage type selection for planned times. For
each time wage type selection rule for planned working time wage types, the system checks which TIP
entries observe the rule. If the rule is observed, the relevant wage type is entered in the internal table
DZL.
GWT M ZML: Time wage type selection for overtime
All TIP entries with processing type M are processed in time wage type selection for overtime. For
each time wage type selection rule for wage types for overtime, the system checks which TIP entries
observe the rule. If the rule is observed, the relevant wage type is entered in internal table ZML.
Function GWT is used in time evaluation to select time wage types for all absences that are valuated on
the basis of the "as if" principle. All other absences are valuated in the gross part of Payroll.
The "as if" principle valuates absences as if the employee had worked (the Time WType selection field in
the Absence Valuation Rule view (V_554C_E) must be activated).
Absences whose processing type has been changed to S or absences that are evaluated using function
GWT A can be valuated according to the "as if" principle.
Wage Type Selection and Overtime Compensation -> Define Generation Rules
(C) SAP AG HR310 41

9.42
Compensating Overtime Wage Types
Initialization
Provide time data
Determine overtime
Final
Final processing
processing
SAP AG 1999
(C) SAP AG HR310 42

9.43
Overtime Compensation
.
.
Time recording at subsystem
(with overtime approval)
Attendance Quotas
Remuneration? infotype (2007)
Overtime comp. Depends on wage type
type 1 Basic pay plus overtime rate
2 Time off plus overtime rate
3 Compensation (time off)
Attendances infotype (2002)

.
Time off, bonuses Overtime comp. Depends on wage type

Overtime remunerated? type 1 Basic pay plus overtime rate
2 Time off plus overtime rate
3 Compensation (time off)
Time recording at subsystem

(general overtime approval)
Depends on wage type

Time off?
SAP AG 1999
To compensate overtime, you can decide whether the overtime hours are to be remunerated or
compensated with time in lieu. There are different options for compensation:
Remuneration
Time off for basic hours, bonuses are remunerated
Time off
You specify the type of compensation for each wage type. You can use the overtime compensation type
in the Attendance Quotas (2007) and Attendances (2002) infotypes to control overtime compensation for
individual employees and periods.
(C) SAP AG HR310 43

9.44
Compensating Overtime Wage Types
Function POVT, personnel calculation rule TC40 10

1112 1
2
9 3
ZML
ZML 8 4
7 6 5
TC40 Wage
Wage type No.
.
type No.
.
Query the value MM##

MM## Overtime
Overtime 25%
25% 5.00
5.00
.
of processing class 17
.
DZL
DZL TES
TES
A Wage
Wage type
type No.
No. Time
Time type
type No.
No.
Remuneration MM##
MM## Overtime
Overtime wage
wage type
type 5.00
5.00 0042
0042 Overtime
Overtime to
to remunerate
remunerate 5.00
5.00
DZL
DZL TES
TES
B 1:1 compensation,
bonuses Wage
Wage type
type No.
No. Time
Time type
type No.
No.
remunerated MQ##
MQ## Bonus
Bonus wage
wage type
type 5.00
5.00 0043
0043 Overtime
Overtime basic
basic pay/time
pay/time off
off 5.00
5.00
0410
0410 Time
Time off
off for
for overtime
overtime 5.00
5.00
DZL
DZL TES
TES
C Compensation
with factor Wage
Wage type
type No.
No. Time
Time type
type No.
No.
from % rates 0041
0041 Overtime
Overtime to to compensate
compensate 5.00
5.00
of wage type 0410
0410 Time
Time off
off from
from overtime
overtime 6.25
6.25
D ....
SAP AG 1999
Function POVT processes the overtime wage types consecutively in the specified personnel calculation
rule. Processing type 17 determines how the wage type is processed. Specifications D-F of the
processing class allow time evaluation to take account of the overtime compensation type from the
infotypes. If no overtime compensation types are specified, processing follows specifications A-C.
In personnel calculation rule TC40, specifications A to F of processing class 17 are interpreted as
described in the documentation. The factor for compensating overtime is determined from the total of the
percentage rates stored for the overtime wage type and the derived wage types in the Wage Type
Valuation view (V_512W_B).
Wage Type Selection and Overtime Compensation -> Compensate Overtime
(C) SAP AG HR310 44

9.45
Data Flow: Time Wage Types and Balances
ADDZL.... Cluster B2
DZL DZL ZL
S
T
W
ADDOT....
G
Classify times
Import data
GWT M POVT
TIP ZML SALDO
TC40
TES TES ZES
ADDDB....
SAP AG 1999
Balances and time wage types can also be formed or changed in personnel calculation rules:
Time wage types using operation ADDZL/ADDOT
Balances using operation ADDDB
(C) SAP AG HR310 45

9.46
Managing Time Accounts
Initialization
Provide time data Balance formation

Time transfer
Determine planned working times specifications
Determine overtime Value limits for

time balances
Compensate overtime wage types Accrual of

absence quotas
Updating
Finalprocessing
Final processing the results
SAP AG 1999
(C) SAP AG HR310 46

9.47
Forming Day Balances: Rule TR10
TIP
Start End Time type No.
12.5000 16.5000 0110 4.0000
TES
+ 0110
0110 == Fill
Fill time
time attendance
attendance
Time
Time type
type 0110
0110 + 0100
0100 == Fill
Fill time
time
== Fill time
Fill time +
attendance
attendance 0010
0010 == Total
Total attendances
attendances
+
0003
0003 == Skeleton
Skeleton time
time
+ 0120
0120 == Fill
Fill time
time absence
absence
Time
Time type
type 0120
0120 + 0100
0100 == Fill
Fill time
time
== Fill
Fill time
time +
absence
absence 0020
0020 == Total
Total absences
absences
+
0003
0003 == Skeleton
Skeleton time
time
SAP AG 1999
Personnel calculation rule TR10 adds the number of hours in the TIP entries to various comprehensive
time types (time balances) to form day totals. The results of processing are entered in table TES (day
balances).
(C) SAP AG HR310 47

9.48
Balance Formation and Time Type Determination
TIMTP Rule TR10

Time type determination (V_T555Z) Form day totals
Pair type Time type:
0 1 2 3
ID
01 ...
02 0110 0120 0130
03 0210 0220 0230 0003 Skeleton time
04 0510 0520 0530

0500 Break
Rule TR10
0010 0020 0030
Attendance
Absence
Off-site work
SAP AG 1999
Time pairs in TIP have been split using function TIMTP and classified by a time type and a processing
type.
Personnel calculation rule TR10 now adds the number of hours in the respective time type to various
comprehensive time types (time balances). You should read the entries in the Time Type Determination
view (V_T555Z) as follows:
Horizontally to determine balances that relate to points of time in the day (for example, breaks,
overtime hours)
Vertically, to determine balances that are based on employees' attendance and absence statuses.
(C) SAP AG HR310 48

9.49
Processing Time Transfer Specifications: Function
P2012
Flextime
balance
Comp. time
Time
Time transfer
transfer specification
specification
Time transfer type
Number of hours
Function P2012
Comp. time
Flextime
balance
SAP AG 1999
Time transfer specifications allow you to change the results determined by time evaluation.
You can use time transfer specifications to transfer hours from a time type, time wage type, or an
absence quota to a:
Time type
Time wage type
Absence quota
You can also set time types to a fixed value.
Function P2012 processes the time transfer specifications for the current day using tables.
Processing Balances -> Time Transfer
(C) SAP AG HR310 49

9.50
Processing Time Transfer Specifications: Control
Valid: 06/01/yyyy - 06/01/yyyy

V_T555P Time transfer type: xxxx
No. of hours: 5.00 hours
Views: V_T555J V_T555K V_T555L
Transfer Transfer Transfer

time balances wage types absence quotas
SAP AG 1999
The time transfer specifications are processed for each day of the infotype's validity period.
Up to three processing steps (transfer time balances, wage types, and absence quotas) can be performed
for each time transfer type. It is therefore possible, for example, to reduce a time type and an absence
quota by five hours and to pass on a wage type with five hours to Payroll.
(C) SAP AG HR310 50

9.51
Forming Important Balances: Rule TR30
e
b alanc
ti me
Flex
0003 0002 0005
Skeleton time Planned time Flextime balance
u rs
tive ho
Produc
0041 OT to compensate
0040
+ 0042 OT to remunerate
+
+ 0043 OT basic pay
+
Attendance 0010
0050
+
Productive hours
Off-site work 0030
SAP AG 1999
Personnel calculation rule TR30 provides an example of how you can use arithmetical operations in a
personnel calculation rule to form important day balances from the balances determined until that point.
Personnel calculation rule TR30 determines the following balances:
Current day's flextime balance
This is done by subtracting the planned working time in the daily work schedule from the skeleton
time (planned hours worked)
Hours of overtime worked
Productive hours
(C) SAP AG HR310 51

9.52
Value Limits for Time Balances: Function LIMIT
Flextime balance Cap?

Transfer to wage type?
Transfer to time type?
Maximum
Message?
Generate deduction
wage type?
Minimum
Rules for checking

time balances
Function LIMIT (V_T559P)
Generate messages
Transfer to wage types
Transfer to time types
Cap time types
SAP AG 1999
Many working time regulations, company agreements and so on stipulate that value limits must be
checked. You can use function LIMIT to process rules for checking the balances determined by time
evaluation. This allows you to check whether time balances exceed or fall short of the individual balance
limits, and to determine appropriate system reactions. A flexible Customizing table is available for
determining the rules. You can use it to meet the following requirements, for example:
Determining the value limits according to fixed values or employees' master and transaction data (for
example, number of planned hours, maximum working time)
Checking value limits within flexibly defined periods
Generating messages to give advance warning, even when the value limit has not yet been exceeded
Transferring the excess to another time balance or another wage type
Storing time balances in another time type over freely-definable periods, for example, weekly
balances
Limiting the validity of the rule depending on the employee's age
Processing Balances -> Balance Formation -> Balance Limits
(C) SAP AG HR310 52

9.53
Defining Value Limits for Time Balances
Rules
Operation Time balance 001
MODIF L=xx rule group 002
...
Rule nnn: Det
erm
inat
Set value limit Value? Type? ion
Which time balance?

Set time balance
Period to be processed?
to be compared Processing?
Process if value limit

Generate messages?
Exceeded
Store excess?
Reached
Store determined time balance?

Control
Check point?
Age Dependent on employee's age?
SAP AG 1999
Function LIMIT determines the balances to be compared with the value limit for a fixed processing
period. It can process the balances in the following ways:
Add (cumulate) day or period balances
Find the highest value (maximum)
Find the lowest value (minimum)
You can use different processing periods and check points, depending on whether you are processing day
or period balances. The check point is the time at which the system applies the rule, for example, at the
end of the evaluation period. Function LIMIT can therefore be placed in the following positions in the
schema:
Processing day balances in day processing
Processing period balances in final processing
When it checks the value limits, time evaluation runs through all the balance rules belonging to a time
balance rule group, and processes the ones that meet the specified conditions.
You can also use function LIMIT to perform a particular type of processing at a particular point in the
schema. The processing is then performed for all employees identically. You can set a time balance rule
group in parameter 2 of the function. Note that you must use operation MODIF to reset the original time
balance rule group after this processing block.
(C) SAP AG HR310 53

9.54
Updating Results: Function CUMBT
Day
Day balances
balances
Day total 1 Transfer
Table
Table ZES
ZES
Day
Day balances Time Types view
TES
TES V_T555A
Period
Period balance
balance
Period balance 1 Transfer
Table
Table SALDO
SALDO
Day
Day wage
wage types
types Wage types
types
DZL
DZL ZL
ZL
SAP AG 1999
Function CUMBT cumulates time types from table TES into tables ZES (day balances) and SALDO
(month balances) according to the rules in the Time Types view (V_T555A). All time wage types are
transferred via function CUMBT (without additional control) from table DZL to table ZL.
Tables ZES, SALDO, and ZL are tables from Cluster B2 in file PCL2.
Note:
In order to ensure an error-free recalculation, SALDO may only be filled using table TES, or at the end
of the time evaluation period.
To do this, proceed as follows:
1. Use function IF EOM to query the end of the time evaluation period.
2. Use operation ADDMB in a personnel calculation rule to enter balances in SALDO.
3. Exit processing with ENDIF.
Processing Balances -> Balance Formation -> Update Cumulated Balances
(C) SAP AG HR310 54

9.55
Accruing Absence Entitlements Automatically
General entitlement for an entire period Proportionate entitlement determined

(for example, a leave year), granted in advance after a calculation period
Leave credit Leave credit

2000 2000
Jan Feb March April Jan Feb March April
Time off credit is accrued once Time off credit is accrued proportionately,
for each leave year periodically
Entitlement based on Realtime calculation of

General annual leave Time off for
work performed in entitlement based on
overtime
the previous year work performed
SAP AG 1999
You can grant absence entitlements to comply with the following business requirements and legal and
contractual regulations:
General absence entitlement for a particular period, for example, general annual leave granted in
advance for one leave year
Periodic, proportionate absence entitlement, for example, annual leave calculated proportionately for
each month or for each payroll period
Proportionate, performance-related absence entitlement, for example, based on the time worked in the
previous period
Absence entitlement based on special activities, for example, time in lieu of overtime
The R/3 System enters the absence entitlements as a deductible quota in the Absence Quotas infotype
(2006).
You can use flexible Customizing tables to represent all your requirements covering the accrual of leave
and other absence entitlements.
Accounts Using Attendance/Absence Quotas -> Calculating Absence Entitlements
(C) SAP AG HR310 55

9.56
Methods for the Automatic Accrual of Absence
Entitlements
rm ined
period ent dete
e n t fo r an entire advance io na te entitlem
ntitle m granted in Propo rt d
General e , n perio
ple, a lea
v e y ea r) alculatio
(for exam after a c
Function QUOTA:
RPTQTA00: Generate
Time evaluation RPTIME00,
Absence Quotas
Schemas TM00, TM04, TQTA
Master data and completed time data Current time data

for past periods
Entitlement accrued once for a

following entitlement period Regular, proportionate accrual
Point of availability for employee

Available immediately after accrual can be determined flexibly
Automatic recalculation Automatic recalculation
SAP AG 1999
You can choose between two procedures to accrue absence entitlements:

Generation of default values for the Absence Quotas infotype (2006):
The absence entitlement is generated either for multiple employees using report RPTQTA00 Generate
Absence Quotas, or online when you create an infotype record.
Automatic accrual:
The absence entitlement is generated by time evaluation. Even if you do not perform time evaluation
for particular employees (who have a Time Management status other than 1, 2, or 9), you can use
schema TQTA to have quotas accrued in time evaluation. The relevant employees must be assigned
the Time Management status 7 in the Planned Working Time infotype (0007).
(C) SAP AG HR310 56

9.57
Automatically Determining Absence Entitlements
in the Absence Quotas Infotype (2006)
Change Absence Quotas (Infotype 2006)
00001234 Mary Miller .

Determine validity ..
Valid 05/01/2000 05/31/2000
interval
Manage
Manage absence
absence
Absence quota entitlements
entitlements
Type 02 Time off for overtime
Determine quota in
in hours
hours or
or days
days
..
number Time
Quota number No. 43.00000 Hours
Deduction 22.25000
Determine deduction 06/01/2000 Neg. deduc. to
Deduction from
period 06/30/2000 16.00000
Deduction to
Jan March April

Negative deduction
permitted
SAP AG 1999
Entitlement to absence quotas (infotype 2006) can be accrued automatically in time evaluation for
individual employees in the following ways:
The system recalculates the entitlement each time and overwrites the previous value in the Absence
Quotas infotype (2006).
The system calculates the entitlement and increases the value in the infotype record.
You cannot manually change the quota number accrued by time evaluation. It is managed and
processed in the quota overview.
Menu: Human Resources -> Time Management -> Administration -> Time Data -> Quota Overview
Automatic accrual also determines the validity and deduction periods in addition to the quota number.
(C) SAP AG HR310 57

9.58
Accruing Absence Entitlements: Function QUOTA
Accrual time Tran

s
time fer
Period 03 04 05 06 07
Accrual Accrual Accrual Accrual Accrual

period period period period period
Accrual
aattee Change Absence Quotas (Infotype 2006)

Crree attee
C
da
Uppd
U
Base period = 1 year / Base entitlement = 20 days
SAP AG 1999
Base entitlement/period: You can store a total entitlement (in days or hours) in relation to a fixed period
(for example, a calendar year) for each absence quota type. This total entitlement (base entitlement)
forms the calculation basis on which the proportionate absence entitlement per accrual period is
calculated. The base entitlement relates to a base period.
Accrual period/time: The time interval for which the absence credit is calculated. At the end of each
accrual period (accrual time) the new value increases or replaces the existing entitlement.
Accrual entitlement: The accrual entitlement is defined as the calculated absence entitlement for an
accrual period. It is calculated on the basis of the base entitlement. A comparison of the base period and
the accrual period converts the base entitlement to the accrual period.
Transfer time: The cumulated accrual entitlement is transferred to the Absence Quotas infotype (2006):
Once a defined key date is reached
When the accrual entitlement exceeds a fixed value limit
Absences cannot be deducted from the cumulated entitlement until it has been transferred.
(C) SAP AG HR310 58

9.59
Determining Quota Type Selection Rule Group
Q UO
U MO
OM O
urree Q
FFeeaattu
Determine using selected
organizational data
ioonn
ittiia
alliizzaatt i
IInni
Function MOD Determine using master data from the
PC rule MODT Organizational Assignment (0001),
MODIF Q=XX Planned Working Time (0007), and
Basic Pay (0008) infotypes
ngg
r o
occeessssiin
D
Daayy ppr
07 Determine using master data and
information on the day being evaluated
Function ACTIO
PC rule XXXX
MODIF Q=XX
SAP AG 1999
You can use the quota type selection rule group to specify rules for absence quota type selection based
on the employee's organizational assignment.
You can determine the quota type selection rule group using the following procedures. You can select the
appropriate procedure based on the specific information you require for selection rules:
Using feature QUOMO. The feature allows you to determine the quota type selection rule group based
on employees' organizational assignments. It is queried by function QUOTA.
Using function MOD in the time evaluation schema. Function MOD accesses the personnel
calculation rule MODT. You can use operation MODIF Q=xx to determine for each of these groupings
the quota type selection rule group. Time evaluation uses the rule group to access the entries from the
Absence Quota Type Selection table for the employees in question.
Using an individually created personnel calculation rule in day processing. The quota type selection
rule group is determined by operation MODIF Q=xx.
Function QUOTA first queries the day processing. If there is no entry there for the employee's quota type
selection rule group, the function checks whether the rule group was set during initialization. If there is
no suitable entry here either, it queries the feature.
(C) SAP AG HR310 59

9.60
Absence Quota Type Accrual (I)
Mea
ning
k
Bloc What is the earliest date an employee can
accrue entitlements?
Applicability For which entry date should a rule be selected?
Is leave for challenged persons involved?
For which accrual period should the

Accrual period entitlements be cumulated?
Which rule for the base entitlement

Base entitlement should be processed?
Which key date should be used to
determine age and seniority?
Should the accrual entitlement be based on

Base entitlement (I) hours worked?
Which time type should be used to
multiply the entitlement?
SAP AG 1999
The generation rules for absence quota selection are processed by function QUOTA.
QUOTA stores the accrual entitlements generated in the time evaluation runs in table QTACC (quota
accrual) in Cluster B2. It stores the cumulated accrual entitlements that are ready for transfer in table
QTTRANS (transfer pool) in Cluster B2.
Accounts Using Attendance/Absence Quotas -> Calculating Absence Entitlements -> Rules for
Generating Absence Quotas -> Define Generation Rules for Quota Selection
(C) SAP AG HR310 60

9.61
Absence Quota Type Accrual (II)
Which rule should be used to reduce the

Accrual entitlement (II) entitlements (for example, for part-time work)?
Should entitlements be rounded?
Should there be a maximum entitlement for each

accrual period which must not be exceeded?
Should differences that arise from a maximum

value being reduced or exceeded
be posted to a special quota?
Transfer time to the How often should the accrual entitlements

Absence Quotas infotype (2006) be transferred?
What is the minimum entitlement that should be
reached before the entitlement is transferred?
Total entitlement Should the absence quotas be rounded

before they are transferred?
What should the maximum total entitlement
for the quota be?
SAP AG 1999
You can use the SAP enhancement HRPTIM03 to fine-tune the criteria for absence quota accrual for
many areas.
(C) SAP AG HR310 61

9.62
Determining the Base Entitlement
Rule 001 Rule 001

Sequence number 002 Sequence number 003
Seniority 005 . 010 years Seniority 010 . 015 years
Constant 20.00000 days Constant 24.00000 days
Base period Base period
Calendar year Calendar year
Absence
Absence quota
quota type
type 10
10 -- Standard
Standard leave
leave
Rule 001
Base entitlement
Sequence number 002 20 days
Seniority 005 . 009 years
PC rule
Individual base
Period balance 0909
entitlement
Base period Base entitlement

22 days
Calendar year
SAP AG 1999
The base entitlement forms the calculation basis that is used to calculate the proportionate absence
entitlement per accrual period.
The base entitlement can be determined on the basis of an employee's age or seniority. If the
differentiation of the employee's age or seniority is not sufficient, or you want to use other criteria, you
can modify the rule. You can create personnel calculation rules in the time evaluation schema in which
you fill your own time type with the base entitlement according to employees' organizational assignment
or the results of time evaluation.
If you want to define different base entitlements for each age or seniority interval, you can group them
together in a rule. You can differentiate the individual intervals in the rule by assigning them a sequential
number.
The base entitlement is related to a fixed period. It can be:
Related to a calendar year or a period of your choice (for example, start of April 2000 to end of March
2001)
Determined on the basis of the time evaluation or payroll period
Determined on the basis of the accrual period
Generating Absence Quotas -> Define Generation Rules for Quota Selection
(C) SAP AG HR310 62

9.63
Validity and Deduction Intervals
View: "Validity/Deduction Interval for Absence Quotas"

Change Absence Quotas /In
Absence quota type 10 Standard leave
Validity interval
01/01/2001 .. 12/31/2001 Valid from Valid to
Valid
Calendar year Calendar year
Absence quota ... ...
Type From To From To

10 Standard leave
. Deduction interval
Deduction from 01/01/2001
Deduction from Deduction to
Deduction to 03/31/2002 Start of validity interval Start of validity interval
End of validity interval End of validity interval
Absence Quotas Relative position Relative position 3 months

infotype (2006) No deduction 01 Expiry of No deduction 02 Temporary
before probation after contract
Evaluation of information for individual Refining the deduction

employees from the Monitoring of Tasks interval
infotype (0019)
SAP AG 1999
For each absence quota type, you can determine which validity and deduction periods are applied to a
record from the Absence Quotas infotype (2006) that has been created by the system.
The validity period of an absence quota type record refers to the period for which time evaluation fills
the quotas in an individual infotype record. If the valid from date lies outside the validity period of an
existing infotype record, time evaluation creates a new record.
The validity period can be defined flexibly. You can use the following options:
Fixed periods, such as the calendar year or the time evaluation period
Periods depending on employees, such as the payroll period or the date type
Periods that are defined in the quota selection rule, such as the accrual period
Periods that you have defined in Customizing, such as the period parameter
The deduction from and deduction to dates define the period within which the absence quota can be
deducted by an absence. It need not be identical to the validity period.
Generating Absence Quotas -> Determine Validity and Deduction Periods
(C) SAP AG HR310 63

9.64
Reduction Rules
Unpaid leave Employee leaves in the

Part-time 5 of 22 days in the middle of accrual period
Employment percentage 80% accrual period (11 of 22 days)
Reduction rule for part-time employees Pct. of inactive days in accrual period 25.00 %
Basic data
No reduction To percentage From percentage
Employment pct (Plnd Wrk.Time) No reduction No reduction
Capacity util. level (Basic Pay) Partial reduction Partial reduction
Weekly workdays Complete reduction Complete reduction
< 25% 25%
Accrual entitlement Accrual entitlement Accrual entitlement

multiplied by 0.8 is not reduced multiplied by 0.5
SAP AG 1999
You use reduction rules to shorten the generated accrual entitlements for part-time employees or
employees with inactive days within an accrual period.
If you use reduction rules, you do not need to set up any absence quota type selection rules of your own
for part-time employees.
You can take account of particular absences in the calculation of inactive time. They can lead to a
reduction of the accrual entitlement. You define in the absence type (Absence: Reduction for Quota
Generation view (V_554S_M)) whether an absence is valuated as inactive time.
You use the absence quota type selection to determine whether the remainder for a reduction is no longer
relevant, or whether it is stored in an additional absence quota.
Generating Absence Quotas -> Define Rules for Reducing Quota Entitlements
(C) SAP AG HR310 64

9.65
Rounding Rules
Round value determined to a whole number
5.21343 RoRul Name No. Lower limit Incl. Upper limit Incl. Tgt value Roll. 5.00000
days 01 Rule 01 001 0.50000 1.50000 1.00000 days
Lower limit is also Rounding rule also valid

rounded for the interval 1.5 - 2.5
2.5 - 3.5
.
Set value determined to the value limit
35.3409 RoRul Name No. Lower limit Incl. Upper limit Incl. Tgt value Roll. 30.00000
days 05 Maximum value 001 30.00000 99,999.99999 30.00000 days
Sequence number
SAP AG 1999
When the system calculates values, these values often have many decimal places, and are therefore not
easy to use. You can use rounding rules to:
Round values up or down
Check value limits
Set fixed values
You define rounding rules using concrete figures. You can specify:
Whether only values within the interval should be rounded, or whether the interval should be rolled
over
Whether the specified upper and lower limits should also be rounded
You can define several subrules for each rounding rule. They should be distinguished using sequence
numbers. The system runs through the subrules consecutively until a rule applies.
Generating Absence Quotas -> Define Rules for Rounding Quota Entitlements
(C) SAP AG HR310 65

9.66
Quota Corrections Infotype (2013)
An employee is hired An employee leaves Correction

Transfer 10 days of leave Evaluate remaining leave and transfer Correct the excess
from previous job the value directly to the infotype entitlement
Valid mm/dd/yyyy Valid mm/dd/yyyy Valid mm/dd/yyyy
Quota correction Quota correction Quota correction
Absence quota type 10 Standard leave Absence quota type 10 Standard leave Absence quota type 02 Time off
Quota number 10.00000 Quota number 2.50000

Transfer Transfer collected
Increase generated Increase generated Reduce generated

entitlement entitlement entitlement
SAP AG 1999
You can use the Quota Corrections infotype (2013) to increase, reduce, or replace entitlements accrued
in time evaluation. This is necessary, for example, if you want to:
Make corrections for periods that are no longer relevant for a recalculation
Have the generated entitlements transferred immediately to the infotype.
The changes are processed in the next time evaluation run. The quota corrections are not taken into
account immediately in the Absence Quotas infotype (2006), since time evaluation only updates the
infotype at the next transfer time.
In exceptional cases - for example, when an employee leaves the company - you can make time
evaluation transfer immediately the total accrued entitlement or the value of the quota correction.
Choose your preferred option in the Transfer field.
The function Transfer collected entitlement immediately is now available for quotas that have been
customized to replace existing entitlements.
(C) SAP AG HR310 66

9.67
Quota Overview
Transfer time
accounts manually
Remain-
Find out ing leave
about absence
entitlements
Annual .
.
leave
.
.
.
.
Quota Overview
.
.
15
3
Project future entitlements
Check deduction
Time accounts
Evaluate Inform employees

employees'
attendances
and absences
SAP AG 1999
The quota overview (transaction PT50) provides all the information and program functions from the
attendance and absence quota management environment.
Menu: Human Resources -> Time Management -> Administration -> Time Data -> Quota Overview
(C) SAP AG HR310 67

9.68
Final Processing
Initialization
Provide time data
Determine overtime
Final processing
SAP AG 1999
(C) SAP AG HR310 68

9.69
Overview: Data Flow During Time Evaluation
Time
Time evaluation
evaluation PAnnnn
Personal Organiz-
input
input work
PCL 1
P2nnn
PCL 2
ational
schedule infor-
mation
Planned pair TIP entries
Rule
Rule processing
processing PAnnnn
Import data TZP TIP SALDO General
status
information
TOP TIP TES

Process internal tables
ZML DZL TES
Time
Time evaluation
evaluation Update infotypes
output
output 0003 2007
2006
ZL ZES SALDO
New records
PCL 2 Cluster B2 2001 2002
2006
SAP AG 1999
Function EXPRT exports the time evaluation results to the database. The function can be placed at any
position in the schema.
(C) SAP AG HR310 69

9.70
Using Functions and Operations to Process Work
Tables
Filled by Processed by
(operation) (function)
TIP (TOP) Time Pairs COLOP Collect in TOP PTIP Process TIP
Add in Daily Process Daily

TES Day Balances ADDDB
Balance Table
PDB
Balances
Add in Monthly Process Monthly

SALDO Period Balances ADDMB
Balance Table
PMB
Balances
Add in Process
ZML Overtime Wage Types ADDOT
Overtime Table
POVT
Overtime Table
Add in ZL
DZL Time Wage Types ADDZL
(time wage types)
PZL Process ZL
SAP AG 1999
There are special functions and operations that you can use to process work tables.
The names of the operations and functions give an indication as to their use.
(C) SAP AG HR310 70

9.71
Personnel Calculation Schema TM00: Summary
You are now able to:
Describe standard schema TM00 step by step, and

explain how time balances and time wage types
are formed from a day's time data
Explain simple personnel calculation rules, and
write your own
Identify parts of the schema that you may have to
modify to suit your customer-specific
requirements, and perform this customizing
SAP AG 1999
SAP AG
(C) SAP AG HR310 71

9.72Personnel Calculation Schema TM00 Exercises
Unit: Personnel Calculation Schema TM00

Topic: Time Evaluation Steps in Schema TM00
Creating and Customizing Personnel Calculation Rules

Representing Special Business Requirements in Time Evaluation
1 Accruing a compensation time account

A reduction of working hours is introduced in your enterprise.
The employees work their normal planned working hours from the daily work schedule.
On each working day, employees receive a time credit (compensation time) if they are at
work. If an employee has a partial day absence, the time credit is halved.
The compensation time is specified in the daily work schedule. The compensation time
credit is accrued in time type 90## (## = your group number).
1-1 Create a personnel calculation rule Z2## (## = your group number), in which the
time credit is accrued.
1-2 Copy personnel calculation schema TM00 and name it ZM## (## = your group
number). Incorporate personnel calculation rule Z2## in your personnel calculation
schema ZM##.
1-3 What further option do you have for specifying a time credit in Customizing and
representing it in a personnel calculation rule? For the solution to this task, check
the documentation for operation HRS.
(C) SAP AG HR310 72

2 Break processing
Variable breaks are defined in work break plan FLEX. Create solutions for the following
problems by customizing the parameters of function PBRKS in schema ZM##:
2-1 In an enterprise, employees make clock-in and clock-out entries when they go for a
break.
Employees are required to adhere to the break times strictly or else the time will be deducted.
If an employee takes a shortened break, the time is deducted from the days attendances or
absences, without any prioritizing.
Customize the parameters of function PBRKS in schema ZM## to represent this
requirement.
2-2 Check the position of the midday break in work break schedule FLEX.
2-3 Enter time events for one day where your employee takes an extended break.
2-4 Run time evaluation for the day, using program option Display log. Check the
effects of the parameter entries.
2-5 Repeat this exercise, taking into account the following business requirements:
In an enterprise, employees do not normally make entries at a time recording

terminal when they take a break. Unrecorded times are used to determine the
position of the break, along with the partial-day absences. Which options do you
have of representing this situation in the system?
Record an additional absence in the break environment. Check how the different
parameter settings affect break processing.
(C) SAP AG HR310 73

3 Processing special times
In your enterprise, employees receive special bonuses for working time spent on works
council activities. These bonuses are to be assigned to cost center 2200 Human
Resources.
To record times spent on works council activities, use the time data ID BR in the Time
Managers Workplace. This ID represents the attendance type 0440.
On working days, the wage type MD70 - Works council bonus is selected for the times in
time wage type selection.
3-1 The easiest way to represent these requirements is to assign a special processing
type for the times. Define the processing type Y - Works council activity in the IMG
under Personnel Time Management Time Evaluation Time Evaluation With
Clock Times Time Wage Type Selection and Overtime Compensation Define
Processing Types.
3-2 In the step Define Generation Rules (see above for menu path), define a time
wage type selection rule. Check first which time wage type selection rule group has
been assigned to your employee in the schema by function MOD.
Define that the time wage type selection rule is processed only for times with
processing type Y.
3-3 Create a personnel calculation rule Z3##. It is used to assign processing type Y to
TIP entries that have been generated according to attendances that have attendance
type 0440 and that are not within a work break.
3-4 Insert personnel calculation rule Z3## into your schema, and add the time wage
type selection for processing type Y. Decide on the best position for it in the
schema.
3-5 Run time evaluation, and check the time wage types that are selected.
(C) SAP AG HR310 74

4 Determining and compensating overtime
The employees in your enterprise are required to work a week of overtime at short notice
to get an order completed. The overtime must be completed by two hours after the end of
the planned working time. A special approval is required. The overtime worked is to be
remunerated in full.
4-1 Create the necessary overtime approval for your employee.
4-2 Enter time events to represent the employees actual times.
4-3 Run time evaluation for your employee and use the log to check the generation and
compensation of overtime.
(C) SAP AG HR310 75

5 Time transfers
You want to allow your employees the option of transferring a flextime excess to a
compensation time account.
5-1 Create the time transfer specification 40## (## = your group number), which
reduces the flextime by the specified amount and increases the compensation time
by the same amount of hours.
5-2 Enter the newly created time transfer specification for an employee. In the Time
Managers Workplace, use the generic time data ID T, and specify the time transfer
type in the detail area.
5-3 Evaluate the employees times, and check the result.
(C) SAP AG HR310 76

6 Balance limits
At the end of the week, you want to check whether your employees have completed their
weekly working hours according to the Planned Working Time infotype (0007). If they
have not completed them, you want a message to be generated.
6-1 Check which time balance rule group function MOD has set for your employee in
the schema.
6-2 In the IMG step Personnel Time Management Time Evaluation Time
Evaluation With Clock Times Processing Balances Balance Formation
Balance Limits, set the rule for balance formation 9## (## = your group number).
This is used at the end of the week (Period field) to cumulate the time type 0003
(skeleton time) over the week, and to compare the result with the weekly working
hours according to the Planned Working Time infotype (0007). If an employees
working time falls short of the weekly working hours, you want a note (message
number Z0) to be issued.
6-3 Change your employees time events so that they fall short of the weekly working
time.
6-4 Run time evaluation for your employee.
6-5 Check whether the message is generated.
(C) SAP AG HR310 77

7 Automatic accrual of a compensation time account
You want an absence quota to be accrued automatically at the end of each month from the
compensation time account 90## (## = your group number). After it has been transferred to
the Absence Quotas infotype (2006), you want the quota to be available for deduction for
three months.
Make the necessary Customizing settings in the IMG section: Personnel Time
Management Time Data Recording and Administration Managing Time Accounts
with Attendance/Absence Quotas Calculating Absence Entitlements.
7-1 Check first whether automatic accrual is permitted for the absence quota.
An absence quota type has been set up for you for this exercise. For your absence
quota type, add 50 to your group number. (Example: Group number 12 plus 50 ->
absence quota type 62).
7-2 The quota type selection rule group for your employee is 01. Check whether this
grouping is specified in feature QUOMO.
7-3 Specify the information to be used to determine the absence entitlement. The basis
for the calculation of the accrual entitlement is the employees base entitlement.
Decide the validity period for the base period.
7-4 Specify the validity and deduction periods for the records from the Absence Quotas
infotype (2006). How do you determine that a new infotype record that can be
deducted for 3 months is generated every month?
Note:
If there is still a valid record for the absence quota when accrual entitlements are
transferred to the infotype, the existing record is changed accordingly. A new record
is only generated if no valid infotype record exists.
7-5 In the Define Generation Rules for Quota Selection step, create the selection rule
9## for your absence quota type 50+##. You want it to be accrued on a daily basis
and then transferred to the infotype at the end of the month. The quota selection
rule group is 01.
7-6 Check the quota accrual by running time evaluation for the whole of January. Use
the quota overview to check the status of the generated quotas.
7-7 The absence quota 50+## can be deducted using the absence type 9000. Enter this
absence type for your employee for the following month, and check the deduction
in the Time Managers Workplace. Use the time data ID VA.
(C) SAP AG HR310 78

9.73Personnel Calculation Schema TM00 Solutions
Unit: Personnel Calculation Schema TM00

Topic: Time Evaluation Steps in Schema TM00
1 Accruing a compensation time account

1-1 For the solution, see the slide Personnel Calculation Rule Z2## in the appendix.
You can use operation HRS=SADV to enter the daily compensation time from the
daily work schedule in the current number of hours field.
1-2 Schema entry ZM## (## = your group number)
You are advised to enter the new personnel calculation rule under dynamic daily
work schedule assignment, since the daily work schedule may possibly still be
changed by personnel calculation rule TD30.
Insert a PRINT TES so that you can track whether table TES is filled.
Note: It is possible to specify for functions which information you want to be
displayed automatically in the log. To do so, use the Input parameters and Output
parameters buttons in the Maintain Functions and Operations transaction (PE04).
In this case, you do not need the PRINT function in the schema.

ACTIO TD30 Dynamic daily work schedule
assignment
ACTIO Z2## HR310: Ex.: Accrual of
Compensation Time Account
PRINT TES
(C) SAP AG HR310 79

1-3 Alternative solutions
HRS=SADD: Enter the daily additional hours from the daily work schedule in the
current hours field.
In personnel calculation rule Z2##, the two calls of HRS=SADV must be replaced
by HRS=SADD.
HRS=Czzzzz: Enter the value of constant zzzz in the current hours field.
In personnel calculation rule Z2##, the two calls of HRS=SADV must be replaced
by HRS=CZ##XX.
View V_T511K (Payroll constants)
Constant Payroll constant From To Value

Z##XX Compensation time credit 01/01/1990 12/31/9999 0.40
(C) SAP AG HR310 80

2 Break processing
2-4 If employees make clock-in and clock-out entries when they take a break, these
times are entered in TIP as non-recorded times. The duration of the entire break is
assigned processing type K.
Schema entry ZM##

PBRKS 1 Evaluate break duration
If the employee reduced the break, for example, only took 30 minutes, the missing
times are deducted at the start of the break frame..
2-5 If you use partial-day absences as well as non-recorded times to determine the
position of the break, you can set parameter 2 of function PBRKS as follows:
Parameter 2
2 First absences, then non-recorded times, then chronologically
This parameter presumes the following:
If planned absences are included in the break times, the break
times are taken into account when the absence is recorded.
Example: The employee has a flexible break of 45 minutes
between 12 noon and 1 p.m. He or she notifies the administrator
of a doctor's appointment between 11 a.m. and 12.30 p.m. The
administrator takes account of the 45-minute break and records
an absence of 11 a.m. to 1.15 p.m.
4 First non-recorded times, then absences, then chronologically

This parameter presumes the following:
The break times are not taken into account when the absence is
recorded. If the employee extends the break time by the break
duration, the time is flagged as non-recorded time. It is used first
when break times are calculated. If the employee does not have
sufficient non-recorded times, the system presumes that his or
her doctors appointment, for example, was shorter than
expected. The break times are deducted from the absence
accordingly.
3 Processing special times

3-1 The processing types Y and Z are available for customer names.
(C) SAP AG HR310 81

3-2 In the IMG step Define Generation Rules, create a time wage type selection rule for
processing type Y, which selects the wage type MD70 irrespective of the day being
evaluated. Create this rule for day grouping 01. The rule is processed by function
DAYMO only on working days. The time wage type selection rule is only
processed for the employee if you have defined the corresponding time wage type
selection rule. This is done using function MOD in personnel calculation rule
MODT.
3-3 The appendix includes the tree display for the personnel calculation rule (slide
entitled Personnel Calculation Rule Z3##).
3-4 Personnel calculation rule Z3## is processed after function GWT M. This allows
the processed attendance times to be included in overtime compensation.
Entry in schema ZM## (## = your group number)

DAYMO 01 02 02 02 Set day grouping for T510S
GWT S DZL Time wage type selection for
planned work
GWT M ZML Time wage type selection for
overtime
PTIP Z3## GEN Exercise: Handling special times
GWT Y DZL Time wage type selection PTYPE Y
(C) SAP AG HR310 82

4 Determining and compensating overtime
4-1 Create an attendance quota of type 01 for your employee for the selected week. You
can specify more information on the overtime approval in the detail area of the
Time Managers Workplace:
Time: From the end of planned
working time to 2 hours after the
end of planned working time
Overtime compensation type: 1
4-3 Technical flow within time evaluation:
Function GOT flags overtime in table TIP with the processing type M.
Function GWT creates overtime wage types.
Function POVT performs the compensation for the overtime wage types; the
bonuses are generated now.
5 Time transfer specifications

5-1 Choose the IMG section Personnel Time Management Time Evaluation Time
Evaluation With Clock Times Processing Balances Time Transfer.
Define Time Transfer Types
PSGrpg Tran Time transfer type text From To TmTy Con

p
01 40## Transfer comp. time 01/01/1990 12/31/9999
Define Rules for Transfer to Time Types
PSGrpg Tran Time transfer type text Time Time type +/- % Min
type text
01 40## Transfer comp. time 0005 Flextime - 100.00 999.99
balance
01 40## Transfer comp. time 90## Comp. time + 100.00 999.99
5-2 You can specify the time transfer type 40## in the detail area of the Time Managers
Workplace.
(C) SAP AG HR310 83

6 Balance limits and error messages
In the initialization block of the schema, function MOD must set the time balance rule
group (MODIF L) to 01.
In the step Personnel Time Management Time Evaluation Time Evaluation With
Clock Times Processing Balances Balance Formation Balance Limits, create the
rule 9## (## = your group number) under the time balance rule group 01.
The weekly working hours from the Planned Working Time infotype (0007) are the value
limit with which the actual working hours are compared. You set the value limit under
Value limit, using operation HRS with the origin indicator I and parameter WEHRS.
Since the rule is only used to check whether the employee has fallen short of the weekly
working hours, the specified value limit is the lower limit for processing.
You want function LIMIT to cumulate the day balance Skeleton time (time type 0003) over
one week. To do this, make the following entries:
Under Time balance, enter the time type 0003.
Under Day balance processed over, enter the period parameter 03 - 1-weekly.
Under Processing in period, activate the Cumulate field.
If the value limit is not reached, you want a note to be issued, which the time administrator
can process later in the message processing function in the Time Managers Workplace.
Under Processing if value limit is exceeded, enter Message Z0.
The balances that are compared in this processing are day balances. Therefore, the time at
which the value limit is compared with the balance is within day processing.
To compare the working hours per week, enter under Check point - During day processing
the period parameter 03 - 1-weekly.
You do not want function LIMIT to carry out further processing, so no additional entries
are necessary.
(C) SAP AG HR310 84

7 Automatic accrual of a compensation time account
You make the necessary Customizing settings in the following section: Personnel Time
Management Time Data Recording and Administration Managing Time Accounts
with Attendance/Absence Quotas Calculating Absence Entitlements.
7-1 To find out whether automatic accrual is permitted for absence quota 50+##, check
the IMG step Automatic Accrual of Absence Quotas Permit Generation of
Quotas in Time Evaluation. Automatic accrual is permitted for the quota if either
the Increase or Replace field is selected.
Since the absence quota is only generated once in our example, it is irrelevant
whether it is to be increased or replaced. However, if you want to accrue an absence
quota over a period of time, the method of accrual depends on the specifications in
the rule.
7-2 In feature QUOMO, a decision tree must have been created for quota type selection
rule group 01.
7-3 In the Rules for Generating Absence Quotas Set Base Entitlements step, you
determine the information on which the accrual entitlement is calculated.
Create the rule 001. To provide the values for the time-off account, enter the Day
balance 90## under Entitlement.
In our example, the base period corresponds to the accrual period. This is because
no proportional entitlement is calculated. You want the cumulated value for the day
balance to be transferred to the accrual entitlement without further calculations, so
enter the Accrual period under Base period.
7-4 In the Define Validity and Deduction Periods step, enter under Validity interval the
Transfer time as the valid from and valid to dates. This ensures that the absence
quota is filled only once.
Under Deduction interval, enter the Start of validity interval as the start date for
the deduction. The transfer of time off entitlements to the infotype allows the
employee to start deduction.
You want to make the absence quota deductible for 3 months. Set the end date for
deduction to 3 months after the Start of validity interval. (Since the start and end
of the validity interval are identical for this rule, you can also enter the End of
validity interval.)
(C) SAP AG HR310 85

7-5 In the Define generation rules for quota selection step, create the selection rule 9##
for your absence quota type 50+##. You can set the accrual entitlement to daily so
that it can always be changed manually in the Quota Corrections infotype (2013) if,
for example, an employee leaves your enterprise.
Choose the time evaluation period as the transfer period (in the standard system,
this corresponds to period 01 - monthly); for the base entitlement, select rule 001.
7-6 To access the quota overview, choose Human Resources Time Management
Administration Time Data Quota Overview. It provides a detailed overview
of the quotas status and accrual information.
7-7 After entering an absence in the Time Managers Workplace you can check the
deduction directly, by choosing the Time Accounts tab page in the Employee
information area.
(C) SAP AG HR310 86

10
Special Solutions
Contents:
Dynamic daily work schedule assignment
Minimum breaks regulations
Guaranteed hours processing
Comparison: The hypothetical earnings principle
and overtime on public holidays
Weekly overtime analysis
Processing instructions for a day
SAP AG 1999
(C) SAP AG HR310 1

10.2
Special Solutions: Objectives

Describe solutions to the special business tasks
presented
Incorporate these solutions in your personnel
calculation schema
SAP AG 1999
SAP AG
For additional special solutions not mentioned in this unit, see the Implementation Guide:
Special Problems and Solutions in Time Evaluation
(C) SAP AG HR310 2

10.3


Driver RPTIME00

Schemas
SAP AG 1999
(C) SAP AG HR310 3

10.4
Dynamic Daily Work Schedule Assignment Based
on an Overlap: Function DYNWS
d ance
Atten
Personal
work schedule
EARLY LATE NIGHT
06:00 14:00 22:00 06:00
Problem: Personal work schedule not suitable

Suitable daily work schedule?
Daily WS to
select from:
V_T552W EARLY
Function DYNWS LATE
NIGHT
Personal work schedule:

LATE
SAP AG 1999
In this form of dynamic assignment of the daily work schedule, the employee's new daily work schedule
is determined from a group of daily work schedules as the one that shows an optimum overlap of the
planned specifications with the actual times.
The dynamic assignment is accessed using function DYNWS. The assignment is made if the TIP entries
for the employee on the day being evaluated come from the following data only:
Time events
Records from the Attendances infotype (2002)
Records from the Overtime infotype (2005)
Records from the Availability infotype (2004)
In parameter 3 of function DYNWS, you determine whether substitutions should be taken into account
in the dynamic assignment.
Providing Time Data -> Work Schedule and Time Events -> Dynamic Assignment of Daily Work
Schedules -> Dynamic Assignment Based on Planned/Actual Overlap
(C) SAP AG HR310 4

10.5
Minimum Break Regulation: Subschema TF20
Attendance (> 9 hours) Minimum break regulation based

on hours worked:
Between 6 - 9 hrs worked
min. 30 mins break
More than 9 hrs worked
08:00 12:00 12:30 16:30 18:00 min. 45 mins break
Minimum break regulation observed?
Check:
Report violations
Subschema TF20 Carry out additional break
deduction
TIP Start End P ID P TTyp Number

08.0000 12.0000 1 02 P 0110 4.0000
12.0000 12.5000 0 02 K 0000 0.5000 Interruption to work
12.5000 16.5000 1 02 P 0520 4.0000
16.5000 17.7500 1 01 0310 1.2500
17.7500 18.0000 1 05 K 0510 0.2500 Additional break deduction
SAP AG 1999
Some working time regulations stipulate that minimum breaks must be observed, depending on the
working hours actually performed. Subschema TF20 allows you to:
Check that the minimum break durations have been observed
Report violations of the break duration
Perform an additional break deduction
Data Processing -> Break Processing -> Determine Minimum Breaks Based on Hours Worked
(C) SAP AG HR310 5

10.6
Processing Guaranteed Overtime Hours:
Subschema TG00
d ance
Atten
06:00 14:00 19:00 - 20:00
Guaranteed hours regulation:

Lengthen isolated pair?
Constant GROVT (V_T511K) Subschema TG00

(= 4 hours)
TIP Start End Proc.type Number

06.0000 14.0000 S 8.0000
14.0000 14.5000 M 0.5000
V_T510S: 19.0000 20.0000 M 1.0000
20.0000 23.0000 G 3.0000
Special time wage types
.
MARK
DEUTS CHE
MARK
SAP AG 1999
If your company has a guaranteed hours regulation for overtime that is not worked immediately after the
planned working time, you can use the personnel calculation schema TG00 to represent this in the
system.
You can define the number of guaranteed hours in constant GROVT. In schema TG00, isolated overtime
pairs are extended by a TIP entry of processing type G, until the value defined in constant GROVT is
reached. You can select special wage types for working hours with processing type G in time wage type
selection.
Data Processing -> Determining Overtime -> Process Guaranteed Overtime
(C) SAP AG HR310 6

10.7
Overtime on Public Holidays: Subschema TOH0
Attendance on public holiday
08:00 13:00 17:00 18:00
Problem:
Attendance 13:00 - 17:00 within planned working time
Special processing or time wage types?
Subschema TOH0
(Compare attendance with planned working time)
TIP Start End Proc.type Number

08.0000 12.0000 S 4.0000
12.0000 13.0000 K 1.0000 V_T510S:
13.0000 17.0000 X 4.0000
17.0000 18.0000 M 1.0000 Special time wage types .
.
.
.
SAP AG 1999
Subschema TOH0 is based on a hypothetical earnings principle: Employees are normally paid for work
on a paid public holiday in the same way as for a normal working day. If an employee now works on a
paid public holiday, he or she should be paid for the hours worked within the planned working time at a
higher rate than colleagues who have not worked on the public holiday.
In schema TOH0, you flag the times that the employee worked within the planned working time with the
processing type X. This enables you to define your own time wage type selection rules for these hours of
work.
Any hours worked outside of the planned working time are assigned processing type M. You can select
special wage types for work on a public holiday for these hours in the Conditions for the day in the Time
wage type selection view.
If you want to take breaks on a public holiday into consideration, you can use schema TOB0.
Data Processing -> Determining Overtime -> Compensate Overtime Worked on a Public Holiday
(C) SAP AG HR310 7

10.8
Variants of Weekly Overtime Analysis
ants ng
Vari ro cessi
P
Higher bonuses as of n
hours of overtime per week Subschema TW00
Overtime as of
n hours worked Subschema TW30
per working week
Weekly overtime analysis Subschemas TPOW

on a daily basis TPOP
SAP AG 1999
(C) SAP AG HR310 8

10.9
Weekly Overtime Analysis (1): Subschema TW00
Downstream processing:
Time wage type selection Generation of higher bonuses
GWT M ZML
Week from mm/xx/ - mm/xx/yyyy
ZML
Overtime 25% Overtime 50%
MM10 MM20 MM10 MM20
Mo
2 hrs 1 2 1
Tu
2 1 Subschema 2 1
TW00
We 2 1 2 1
Th After 10 hours of overtime

2 0 1 1 per week, a higher bonus
is generated
Fr 2 1 0 3
.
.
.
.
SAP AG 1999
In schema TW00, a higher bonus is generated as of the 10th overtime hour per week.
(C) SAP AG HR310 9

10.10
Weekly Overtime Analysis (2): Subschema TW30
"Overtime
"Overtime starts
starts after
after nn hours
hours
have
have been worked in one working week"
been worked in one working week"
Working Weeks View (T559A)
Working week Name Length Start date Time

01 Week with clock times 07 12/29/1996 00:00
As
As of
of 40
40 hours
hours 02 Week without clock times 07 12/29/1996
per
per working
working week
week
(constant
(constant OVERT)
OVERT)
Planned
Planned Working
Working Time
Time
Infotype
Infotype (0007)
(0007)
Week
Week from
from mm/xx/
mm/xx/ -- mm/xx/yyyy
mm/xx/yyyy PersNo
PersNo 3446
3446 Mark
Mark Miller
Miller
Mo
Mo Tu
Tu We
We Th
Th Fr
Fr Sa
Sa Su
Su Working
Working week
week 02
Work.
Work. time
time 10
10 11
11 10
10 10
10 22
Overtime
Overtime 11 22
SAP AG 1999
You can use schema TW30 to determine overtime pairs per working week, after a certain number of
hours is reached. The number of hours is set in constant OVERT.
You can define the length, start date and start time (optional) of the working week. It is stored for each
employee in the Planned Working Time infotype (0007). You can define a default value for the working
week in feature WWEEK.
Alternatively, you can use the subschema TW20. To use it, the following conditions must be met:
You do not need clock times for the working week
You want to define only the start day of a 7-day working week for the whole of your enterprise
If you use subschema TW20, the assignment for individual employees in the Planned Working Time
infotype (0007) is no longer used.
Note:
In the standard system, absence times are not included when overtime is determined.
Data Processing -> Determining Overtime -> Determine Overtime According to the Working Week
(C) SAP AG HR310 10

10.11
Weekly Overtime Analysis (3): Subschema TPOW
Week
Week from
from mm/xx/
mm/xx/ -- mm/xx/yyyy
mm/xx/yyyy
Mo
Mo Tu
Tu We
We Th
Th Fr
Fr Sa
Sa Su
Su Total
Total
Weekly planned
Plnd
Plnd hours
hours worked
worked 88 88 88 66 66 00 00 36
36 working hours
Overtime
Overtime 22 33 22 00 00 00 00 77 not completed
Correction balance 4 hours

Subschema
TPOW
Automatic recalculation
Conversion of overtime
Mo
Mo Tu
Tu We
We Th
Th Fr
Fr Sa
Sa Su
Su Total
Total
Plnd
Plnd hours
hours worked
worked 10
10 10
10 88 66 66 00 00 40
40
Overtime
Overtime 00 11 22 00 00 00 00 33 Final
overtime
SAP AG 1999
Personnel calculation schema TPOW performs weekly overtime analysis on a daily basis. The daily
overtime is recognized only after the employee has completed the weekly planned hours.
If the employee does not complete the weekly planned working hours, the hours of overtime already
issued are retracted, and time evaluation evaluates the week again in the same evaluation run.
The incorrectly issued hours of overtime are identified in the time balance 0928 OT/Wk: Transfer spec.
(wk).
Data Processing -> Determining Overtime -> Analyze Overtime on a Weekly Basis
Subschema TPOP represents a more general processing method of subschema TPOW. It determines
overtime on the basis of a general period.
Data Processing -> Determining Overtime -> Calculate Overtime on the Basis of General Periods
(C) SAP AG HR310 11

10.12
Processing Instructions for a Day
Simplify routine tasks in the Time Manager's Workplace
Time data maintenance in the

Time Manager's Workplace
Overtime approved Example: To approve

overtime, the time
administrator selects a
checkbox
Record of Time
Transfer Function P2012 Customer-specific
Overtime
Specifications in time evaluation processing triggers
approval is
infotype (2012) reads processing deduction of
issued
is generated instruction overtime approval
SAP AG 1999
You can use processing instructions for a day to simplify some of the tasks that time administrators carry
out frequently. Instead of explicitly entering time data, time administrators simply select a checkbox.
You can define the meaning of each checkbox in Customizing.
You can use processing instructions to:
Issue backdated overtime approvals
Grant general time bonuses
Indicate that the day has been processed, for example
In time evaluation, you can use personnel calculation rules to set up customer-specific processing steps,
for example to
Fill time types and wage types
Generate or update infotype records
To do so, call function P2012 as often as needed in the schema. Enter the required personnel calculation
rules in parameter 1 of the function.
IMG: Personnel Time Management -> Time Manager's Workplace -> Basic Settings -> Define
Processing Instructions
(C) SAP AG HR310 12

10.13
Groups of Processing Instructions
Profile for Time

Administrator:
Profile for Time
Secretarial
Administrator: Profile for Time
Profile for Time
Secretarial Profile for Time
Administrators with
Administrator: Administrator:
Approval
Production Secretarial
Authorization
Group of processing instructions: Group of processing instructions:

Time bonus/Day has been processed All processing instructions
Day has been processed Day has been processed
General time bonus General time bonus
Overtime approved
SAP AG 1999
Processing instructions for a day are managed in groups. A group of processing instructions can contain
up to 7 processing instructions. You organize the groups using field selection.
You assign the group of processing instructions to profiles for the Time Manager's Workplace. Each
profile can contain only one group.
Depending on the view in which the checkboxes are to be displayed, the processing instructions appear:
Within the time data table in the Multi-Day View and the Multi-Person view, or
In a line above the time data table in the One-Day View
(C) SAP AG HR310 13

10.14
Special Solutions: Summary
You are now able to

Discuss solutions for special business requirements
Describe how you can use the proposed solutions
in your personnel calculation schema
SAP AG 1999
SAP AG
(C) SAP AG HR310 14

11
Alternative Time Evaluation Schemas
Contents:
Time evaluation schema TM01 for
deviations from the work schedule
Time evaluation schema TM04 for time
evaluation without clock times
SAP AG 1999
(C) SAP AG HR310 1

11.2
Alternative Time Evaluation Schemas: Objectives
At the conclusion of this unit, you will be able to

Describe the special features of the time
evaluation schemas TM01 and TM04
Explain the differences between them
and time evaluation schema TM00
SAP AG 1999
SAP AG
(C) SAP AG HR310 2

11.3


Driver RPTIME00

Schemas
SAP AG 1999
(C) SAP AG HR310 3

11.4
Alternative Time Evaluation Schemas: Business
Scenario
Scenario 1 (schema TM01):

You record only deviations from the work
schedule and want to use time evaluation
to manage time accounts for your employees.
Scenario 2 (schema TM04):
You record employee's attendance times
manually in the Attendances infotype (2002).
You do not use clock times for evaluating time
data.
SAP AG 1999
(C) SAP AG HR310 4

11.5
Criteria for Selecting a Schema
Recording work 8 hours

schedule deviations
8:00 17:00
Actual times:
Attendances +
Absences Break 1 hour
General
Format DWS
Scope Infotype 0050
Attendance
Recording Overtime Quotas
(2007)
Overtime
Results (2005, 2002)
Time wage types Statutory

overtime
.
regulations
Time accounts
.
.
.
e.g. USA: FLSA
SAP AG 1999
The standard system supplies three schemas, which cover many requirements. You can use them as
templates and customize them to suit your customer-specific requirements. The three schemas require
different forms of time data for evaluation and pursue different strategies in evaluating the time data.
The schema you decide to use depends on several factors. However, when you opt for one particular
schema, you are not committing yourself to one particular method of processing the time data. You can
copy functions that are provided by another standard time evaluation schema to your chosen schema and
modify the processing accordingly.
The SAP standard schema you choose to use as a template to customize to suit your user-specific
requirements generally depends on the method of time recording you use and the requirements you make
of time evaluation:
Which time evaluation results are required
How the time data is recorded
The context in which the time data is recorded
The format in which the time data is recorded
How the planned specifications from the daily work schedule are checked
How overtime is determined and approved
(C) SAP AG HR310 5

11.6
Time Evaluation for Work Schedule Deviations
(Schema TM01)
Results Time wage types Time accounts
.
.
.
.
Format
Recording
Recording
Recording
work
work schedule
schedule
Scope deviations
deviations
8:00 17:00
Format
Break 1 hour
Attendances
Overtime outside
planned time
SAP AG 1999
Schema TM01 assumes the following prerequisites and goals:

TM01 forms time wage types and time accounts. It is processed by the time evaluation driver
RPTIME00.
Schema TM01 is used to import and process time data recorded online (that is, in the Time
Management infotypes).
It was developed for evaluating time data, where only the deviations from the work schedule are
recorded. In this case, the actual working times are not recorded.
All the time data recorded online must be clock times and must be full-day records.
(C) SAP AG HR310 6

11.7
Initialization: Setting Employee Groupings
(Function MOD)
ule
PC r N ZZ PAYTP
TM O PAYTP A
A
Rule
Rule accessed
accessed according
according to
to the
the
employee
rule
ES
ES grouping:
grouping: 11 ES
ES grouping:
grouping: 22 ES
ES grouping:
grouping: 33
Time type: ****
Time type: ****


SAP AG 1999
Before day processing (initialization block of the schema) the function MOD determines that, depending
on the employee grouping, only certain time wage types and time types are formed, and that absences
are valuated differently. It determines the groupings with which the time evaluation driver accesses the
corresponding tables during processing.
To do this, function MOD accesses the personnel calculation rule TMON.
A personnel calculation subrule is accessed in rule TMON according to the employee's employee
subgroup grouping for the personnel calculation rule. The groupings for table access are defined here.
Groupings for accessing tables are generally determined in relation to other organizational assignments,
such as the personnel subarea, employee subgroup, and so on.
Processing can also be determined individually via the employee grouping for the time evaluation rule in
the Time Recording Information infotype (0050); the organizational assignments in the standard system
are not relevant in this case. This is done using PAYTP S. Note the effects on table access (for example,
in time wage type selection for hourly wage earners, salaried employees, and so on) in time wage type
selection.
IMG: Personnel Time Management -> Time Evaluation -> Time Evaluation Without Clock Times ->
Initial Steps -> Define Groupings
(C) SAP AG HR310 7

11.8
Providing Time Data in Schema TM01
11 12 1
10 2
9 3
8
4
7 6 5 Start of plnd work 08:00 Absence Attendance
Planned
working time End of plnd work 17:00
Plnd working hrs 8.00 10:00
Time 08:00 Time 17:00 18:30
Function Function Function

P2000 P2001 P2002
TZP
TIP
Start End 1 P ID Ct P TTyp BR ER C O I BPin EPin PT ALP C1 AB Number

08.0000 10.0000 0 2 02 A A 01 2.0000
10.0000 17.0000 1 00 D 7.0000
17.0000 18.5000 0 3 03 P P 1.5000
SAP AG 1999
To enable the planned pair formed by function P2000 to be overwritten by attendances/absences in table
TIP, parameter 2 of functions P2001 and P2002 must have the value 1.
(C) SAP AG HR310 8

11.9
Time Evaluation for Work Schedule Deviations -
Function P2005: Provide Overtime
Overtime (infotype 2005)
Time 17:00 20:30

Unpaid break 18:45 19:00
Function
P2005
TIP
08.0000 17.0000 1 00 D 9.0000
17.0000 18.7500 1 01 00 O 1.7500
18.7500 19.0000 1 07 00 O 0.2500
19.0000 20.5000 1 01 00 O 1.5000
SAP AG 1999
Function P2005 enters recorded overtime with the time identifier 01 (overtime hours) in the internal
table TIP. If the infotype record was recorded with breaks, the breaks are entered with the time identifier
07 for unpaid and 08 for overtime breaks.
(C) SAP AG HR310 9

11.10
Time Evaluation for Work Schedule Deviations:
Time Type Determination
PS grpg Zeitarten- Not Absent At work

PTB for time findungs- Time identifier at work Planned pair (IT2001) (IT 2002)
recording gruppe
01 02 Overtime hours M 0310 M 0320 M 0330
01 02 Fill time - S 0110 S 0120 S 0130
...
01 02 Fill time break - 0000 K 0510 0520 K 0530
01 02 Break, paid S 0540 S 0540 S 0540 S 0540

Overtime break,
01 02 unpaid K 0000 K 0510 0520 K 0530
Overtime break,
01 02 paid M 0540 M 0540 M 0540
Set in the
schema by Processing type
function MOD
SAP AG 1999
In time evaluation for work schedule deviations, the time type determination block is set to 02 in the
initialization block. All times within the planned working time are assigned the processing type S
(excluding the breaks). All attendances outside the planned working time (time identifier 01) are
assigned the processing type M.
The following processing types are used for time wage type selection:
S : The TIP entry is included in the daily calculation of planned time, without a maximum daily
working time.
M : The TIP entry is valuated as overtime; the time is not included in the daily planned working time.
"-" : The TIP entry is deleted later.
" " : The TIP entry is not valuated as productive time.
K : Core night work (Germany only).
You can also use personnel calculation rule TO13 to check the daily maximum working time in TM01.
If it is exceeded, the processing type of the relevant TIP entries are set to blank. This means that no time
wage types are selected for these TIP entries.
(C) SAP AG HR310 10

11.11
Section of Schema TM01
Fct
Fct Par1
Par1 Par2
Par2 Par3
Par3 Par4
Par4 D
D Text
Text
.. .. ..
P2000
P2000 N
N SAVE
SAVE Generate
Generate planned
planned pair/load
pair/load daily
daily WS
WS
A2003
A2003 Process
Process work
work center
center substitution
substitution
P2001
P2001 11 Provide
Provide absence
absence data
data of
of the
the day
day
RTIPA
RTIPA TD70
TD70 GEN
GEN Correct attendance flag
Correct attendance flag
P2002
P2002 11 Provide
Provide attendance
attendance data
dataofof the
theday
day
P2005
P2005 11 Provide overtime data of the day
Provide overtime data of the day
.. .. ..
PTIPA
PTIPA TE10
TE10 GEN
GEN Adjust
Adjust absences
absences
ACTIO
ACTIO TE20
TE20 Check
Check for
for day
day with
with errors
errors
.. .. ..
TIMTP
TIMTP Assign
Assign time
time type
type to
to time
time pair
pair
PBRKS
PBRKS 33 ALL
ALL Evaluate breaks
Evaluate breaks
RTIPA
RTIPA TP20
TP20 GEN
GEN Absences
Absences with
with time
time compensation
compensation
PTIP
PTIP TO13
TO13 GEN
GEN Check
Check maximum
maximum daily
daily working
working time
time
.. .. ..
DAYMO
DAYMO 01
01 02
02 02
02 02
02 Set
Set day
day grouping
grouping for
for T510S
T510S
GWT
GWT SS DZL
DZL Wage
Wage type selection for planned
type selection for planned work
work
GWT
GWT M
M ZML
ZML Wage
Wage type
type selection
selection for
for overtime
overtime
SAP AG 1999
The principal differences in comparison with TM00 are in the following processing steps:
Data collection
Error checks
Classification of planned hours and overtime
Function DEFTP is not required in schema TM01, since planned hours and overtime are classified
completely in Customizing for time type determination.
(C) SAP AG HR310 11

11.12
Time Evaluation Without Clock Times (Schema
TM04)
Results Time wage types Time accounts
.
.
.
.
Format
Recording
Actual
Actual data:
data: Recording
Recording
Attendances
Attendances ++ work
work schedule
schedule
Scope Absences deviations
Absences deviations
8 hours
Format
Weekly Overtime as of Overtime after

Overtime overtime x hours worked z consecutive
regulations per day days worked
SAP AG 1999
Schema TM04 assumes the following prerequisites and goals:

Schema TM04 forms time wage types and time accounts. It is processed by the time evaluation driver
RPTIME00.
It is used to import and process time data recorded online. The employee's working time is recorded in
the Attendances infotype (2002).
It can be used if you record work schedule deviations and if you record all actual working times.
You do not use clock times for evaluating time data. The clock times in the daily work schedule are
therefore irrelevant.
All recorded times are counted as working times for the purposes of determining overtime. The
following types of overtime regulations are possible:
Overtime starts after x hours per day
Overtime starts after y hours per week
Overtime starts after z consecutive days worked
IMG: Personnel Time Management -> Time Evaluation -> Time Evaluation Without Clock Times
(C) SAP AG HR310 12

11.13
Initialization: Setting Employee Groupings
(Function MOD)
ule
PC r N ZZ PAYTP
TM O PAYTP A
A
Rule
Rule accessed
accessed according
according to
to the
the
employee
rule
ES
ES grouping:
grouping: 11 ES
ES grouping:
grouping: 22 ES
ES grouping:
grouping: 33
Time type: ****
Time type: ****


SAP AG 1999
Before day processing (initialization block of the schema) the function MOD determines that, depending
on the employee grouping, only certain time wage types and time types are formed, and that absences
are valuated differently. It determines the groupings with which the time evaluation driver accesses the
corresponding tables during processing.
To do this, function MOD accesses the personnel calculation rule TMON.
A personnel calculation subrule is accessed in rule TMON according to the employee's employee
subgroup grouping for the personnel calculation rule. The groupings for table access are defined here.
Groupings for accessing tables are generally determined in relation to other organizational assignments,
such as the personnel subarea, employee subgroup, and so on.
Processing can also be determined individually via the employee grouping for the time evaluation rule in
the Time Recording Information infotype (0050); the organizational assignments in the standard system
are not relevant in this case. This is done using PAYTP S. Note the effects on table access (for example,
in time wage type selection for hourly wage earners, salaried employees, and so on) in time wage type
selection.
Initial Steps -> Define Groupings
(C) SAP AG HR310 13

11.14
Providing a Planned Pair: Function P2000
No
No recording
recording of
of actual
actual times?
times? Actual
Actual times
times recorded?
recorded?
Planned
Planned pair
pair according
according Import
Import from
from infotypes
infotypes
to
to daily
daily work
work schedule
schedule 2001,
2001, 2002
2002 and/or
and/or
is
is entered
entered in
in TIP
TIP 2011
2011 fills
fills TIP
TIP
Sc
exc hema
Fct
Fct Par1
Par1 Par2
Par2 Par3
Par3 Par4
Par4 DD Text
Text
CHECK
CHECK FUT
FUT Allow
Allowevaluation
evaluationfor
forfuture
futureperiods
periods erpt
. .. .. . TM 0
IFIF POS
POS IfIfTime
TimeManagement
Managementstatus
status==1,
1,22(actual
(actualtimes)
times) 4
IFIF NOT
NOT SIMF
SIMF and
andififititisisnot
notaasimulation
simulation
PERT
PERT TD20
TD20 Evaluate
Evaluateerrors
errorsfrom
frompair
pairformation
formation
P2011
P2011 Provide
Providetime
timepairs
pairsand
anddaily
dailyWS
WS
ACTIO
ACTIO TD10
TD10 End
Endififthe
thedaily
dailywork
workschedule
schedulestill
stillactive
active
A2003
A2003 Process
Processwork
workcenter
centersubstitution
substitution
P2001
P2001 Provide
Provideabsence
absencedata
data
P2002
P2002 Provide
Provideattendance
attendancedata
data
ELSE
ELSE Otherwise
Otherwisesimulation
simulation
COPY
COPY TDT0
TDT0 Provide
Providedaily
dailyWS
WSand
andtime
timedata
data
ENDIF
ENDIF Endif
Endif(simulation)
(simulation)
ELSE
ELSE Fct
Fct Par1
Par1 Par2
Par2 IfIftime
timerecording
recording<><>1,
1,22(actual
(actualtimes)
times)
COPY
COPY TDT0
TDT0 P2000
P2000 Provide
Providedaily
dailyWS
WSandandtime
timedata
data
ENDIF A2003
A2003 Endif
ENDIF P2001 11 Endif(time
(timerecording)
recording)
P2001
. .. .. . P2002
P2002 11
RTIPA
RTIPA TD70
TD70 GEN
GEN
SAP AG 1999
In the standard system, function P2000 enters a planned pair in TIP for all employees with a Time
Management status other than 1 or 2 (parameter 4 = BLANK).
If the employee has a Time Management status of 1 or 2, the work table TIP is filled by functions P2002,
P2001 or P2011 (if you use a time recording system).
(C) SAP AG HR310 14

11.15
Assigning a Time Type and Processing Type
Grp
Grp A/A
A/A ty.
ty. Attendance
Attendance type
type From
From To
To Cl
Cl P/T
P/T V_554S_E
Function 01 V_554S_F
01 0800
0800 Attendance
Attendance hours
hours 01/01/1990
01/01/1990 12/31/9999
12/31/9999 01
01
P2002
TIP
From To 1 P ID Ct P Tty BR ER C O I BPIN EPIN PT ALP C1 AB No.
0 3 01 P P 8.0000
Function
TYPES
PSgrpgGroup
PSgrpgGroup Cl
Cl P/T
P/T From
From To
To PairType1
PairType1 PairType2
PairType2 PairType3
PairType3 T555Y
01
01 02
02 01
01 01/01/1990
01/01/1990 12/31/9999
12/31/9999 S
S 1101
1101 S
S 1201
1201 S
S 1301
1301
(MODIF T = 02)
TIP
From To 1 P ID Ct P Tty BR ER C O I BPIN EPIN PT ALP C1 AB No.
0 3 01 S 1301 P 8.0000
Processing Time type

Wage
Wage types
types Time
Time accounts
accounts
type
SAP AG 1999
If employees' times are recorded as a number of hours, the time data cannot be valuated using the
planned specifications from the daily work schedule. In this case, the Processing type/time type class
enables the time data to be classified.
You can use the Processing type/time type class to group attendance and absence types into categories,
for example, all absences that concern a period of leave or all absences that relate to a period of illness.
Function TYPES is used to assign a time type and a processing type to each TIP entry depending on the
pair type and the Processing type/time type class. If there is a TIP entry without a Processing type/time
type class, the system applies the value 00.
IMG: Personnel Time Management ->Time Evaluation -> Time Evaluation Without Clock Times ->
Time Data Processing -> Assign Time Types and Processing Types
(C) SAP AG HR310 15

11.16
Structure of View T555Y
Processing type Time type

PS grouping Time type PType/ PType/TType PType/TType PType/TType
for time determination TType for pair type 1 for pair type 2 for pair type 3
recording group class
01 02 00 S 1100 S 1200 S 1300
01 02 01 S 1101 S 1201 S 1301
01 02 02 S 1102 S 1202 S 1302
01 02 05 M 0040 S 1204 M 0040

Pair type 1: Pair type 2: Pair type 3:
Attendance, Absence, Attendance or
Set in the imported by imported by off-site work,
P2000 or P2011 P2001 imported by P2002
schema by or P2011
function MOD
SAP AG 1999
The personnel subarea grouping for time recording is a grouping of personnel areas that use the same
Time types
Time transfer specifications
Access control groups
Error definitions
IMG: Personnel Time Management -> Time Evaluation -> Time Evaluation Settings -> Set Personnel
Subarea Groupings for Time Recording
You set the time type determination group in personnel calculation rule TMON, using operation MODIF
T. The time type determination group 02 (MODIF T=02) is used in the standard system for time
evaluation without clock times.
(C) SAP AG HR310 16

11.17
Evaluating Break Periods: Function PBRKS
Parameter 4: NOTI Definition of work break schedule:

After 4 hours, 0.5 hours unpaid break
TIP without clock times after function TYPES TIP without clock times after function PBRKS
Start
Start End
End PP ID
ID CT
CT PP TTyp
TTyp...
... Number
Number Start
Start End
End PP ID
ID CT
CT PP TTyp
TTyp...
... Number
Number
33 01
01 SS 1301
1301 2.0000
2.0000 33 01
01 SS 1301
1301 2.0000
2.0000
33 01
01 SS 1301
1301 3.0000
3.0000 33 01
01 SS 1301
1301 2.0000
2.0000
33 01
01 SS 1301
1301 3.0000
3.0000 33 05
05 01
01 KK 0530
0530 0.5000
0.5000
33 01
01 SS 1301
1301 0.5000
0.5000
33 01
01 SS 1301
1301 3.0000
3.0000
Parameter 4: OWTI Definition of work break schedule:

12:00 - 12:30 0.5 hours unpaid break or
After 4 hours 0.5 hours unpaid break
TIP with clock times after function TYPES TIP with clock times after function PBRKS
Start
Start End
End PP ID
ID CT
CT PP TTyp
TTyp...
... Number
Number Start
Start End
End PP ID
ID CT
CT PP TTyp
TTyp...
... Number
Number
08.0000
08.0000 10.0000
10.0000 33 01
01 SS 1301
1301 2.0000
2.0000 08.0000
08.0000 10.0000
10.0000 33 01
01 SS 1301
1301 2.0000
2.0000
10.0000
10.0000 13.0000
13.0000 33 01
01 SS 1301
1301 3.0000
3.0000 10.0000
10.0000 12.0000
12.0000 33 01
01 SS 1301
1301 2.0000
2.0000
13.0000
13.0000 16.0000
16.0000 33 01
01 SS 1301
1301 3.0000
3.0000 12.0000
12.0000 12.5000
12.5000 33 05
05 01
01 KK 0530
0530 0.5000
0.5000
12.5000
12.5000 13.0000
13.0000 33 01
01 SS 1301
1301 0.5000
0.5000
13.0000
13.0000 16.0000
16.0000 33 01
01 SS 1301
1301 3.0000
3.0000
SAP AG 1999
For time evaluation without clock times, only parameter 4 of function PBRKS is specified:
NOTI: Only after x hour breaks are evaluated via parameter NOTI. The duration of the break is
deducted from the number of attendance hours within the period.
OWTI: Parameter OWTI can be used to evaluate all types of break.
The TIP entries that specify clock times are aligned with the breaks in the daily work schedule.
Entries without clock times are passed on unchanged.
You can call function PBRKS twice, if you want to take account of entries that specify hours and those
that specify clock times. You can use function SORT to sort the TIP entries before function PBREAKS.
In time evaluation without clock times, time pairs are entered automatically in TIP in the following
cases:
1. The system generates a planned pair from the daily work schedule:
If the employee is assigned the Time Management status 9 (function P2000)
For an evaluation of a future period or a simulation
If the day being evaluated is a paid public holiday, for example (operation GENTG, personnel
calculation rule TE20)
2. The system enters time pairs with the planned specifications from the daily work schedule in TIP if
full-day records have been recorded for an employee (for example, functions P2001 and P2002).
(C) SAP AG HR310 17

11.18
Deducting Attendances and Absences from the
Planned Pair
::
eccttss Recording work schedule deviations: Time Management status 9
Affff e
A
Work on paid public holidays
Example: Partial-day absence: 2-hour doctor's appointment
22 hours:
hours:
Increase
Increase the
the
number
number ofof
hours
hours worked?
worked?
08:00 Planned pair: 8 hours 17:00

Absence: 2 hours
Subschema
Subschema TP01,
TP01, personnel
personnel calculation
calculation rule
rule TP06
TP06
Absence: 2 hours 10:00 Planned pair: 6 hours 17:00
SAP AG 1999
If a planned pair is generated for an employee via function P2000 or for paid public holidays (personnel
calculation rule TE20), certain attendances and absences recorded without clock times, such as a doctor's
appointment, should not increase the hours worked.
Subschema TP01 deducts the absences recorded without clock times from the planned pairs. It also
reduces the attendances recorded without clock times where the attendance type has the Time evaluation
class 01.
Providing Time Data -> Deduct Attendances/Absences from Generated Planned Time Pair
(C) SAP AG HR310 18

11.19
Determining Overtime
Times
Times that
that count
count Determining
Determining overtime
overtime in
in time
time evaluation
evaluation
as
as overtime
overtime
are
are determined
determined Overtime after x hours worked per day
Subschema TW15
Overtime after y hours worked per working week
Subschema TW30
Overtime after z consecutive days worked
Subschema TW10
Overtime
Overtime is
is assigned
assigned
processing
processing type
type M
M
Overtime:
Overtime: Online
Online data
data entry
entry
Overtime
Overtime based
based on
on
special
special attendance
attendance types
types
Overtime
Overtime wage
wage types
types Attendances
Attendances infotype (2002)
infotype (2002)
are
are generated
generated in
in time
time
wage
wage type
type selection
selection
SAP AG 1999
The times that qualify as overtime are determined and assigned the processing type M.
Processing type M is used so that special time wage types (basic remuneration for overtime, bonuses)
can be selected for these times in a later processing step.
Overtime can also be recorded online instead of being determined automatically in time evaluation.
There are two methods of doing this:
Overtime can be recorded using special attendance types. If the attendance types meet the following
criteria, they are assigned processing type M in time evaluation:
They are grouped in their own processing type/time type class (V_554S_F).
They are assigned the processing type M in view T555Y for processing type for pair type 1 or
processing type for pair type 3.
Overtime can be entered in the Overtime infotype (2005). The standard schema TM00 contains an
example of this method of processing:
P2005 Provide overtime data of the day
PTIP TD40 GEN Set PTYPE/TTYPE for overtime
(C) SAP AG HR310 19

11.20
Balance Formation: Rule TR11
TIP
Start End Time type No.
1301 4.0000
TES
+ 1301
1301 == Normal
Normal working
working time
time
Time
Time type
type 1301
1301 + 1501
1501 == Total
Total for
for Cltim
Cltim == 01
01
== normal
normal +
working
working time
time 0030
0030 == Total
Total attendances
attendances
+
0003
0003 == Skeleton
Skeleton time
time
+ 1202
1202 == Period
Period of
of illness
illness
+ 1502
1502 == Total
Total for
for Cltim
Cltim == 02
02
Time
Time type
type 1202
1202
== illness
illness times
times +
0020
0020 == Total
Total absences
absences
+
0003
0003 == Skeleton
Skeleton time
time
SAP AG 1999
Personnel calculation rule TR11 adds the number of hours in the TIP entries to various comprehensive
time types (time balances) to form day totals. The results of processing are entered in table TES (day
balances).
(C) SAP AG HR310 20

11.21
Balance Formation and Time Type Determination
(TM04)
TYPES Rule TR11

Processing type and time type according Form day totals
to attendance/absence class (T555Y)
PType/ Pair type Pair type Pair type Time type:
TType class
1 2 3
00 S1100 S1200 S1300 1500 Total for class

PType/TType 00
01 S1101 S1201 S1301
0003 Skeleton time
02 S1102 S1202 S1302
Rule TR11
0010 0020 0030
Post.,Plnd pair
Absence
Att., Off-site
SAP AG 1999
Function TYPES assigns the TIP entries a time type. Personnel calculation rule TR11 then cumulates the
number of hours in the TIP entries in various comprehensive time types (time balances). You can read
the entries in the view Proc. Type and Time Type acc. to Attendance/Absence Class (V_T555Y) in the
following ways:
Horizontally, to determine balances that are based on the classifications of the attendances and
absences by the Processing type/time type class
Vertically, to determine balances that are based on employees' attendance and absence statuses.
(C) SAP AG HR310 21

11.22
Alternative Time Evaluation Schemas: Summary
You are now able to

Discuss the personnel calculation schemas
TM01 and TM04
Describe their special features, and the
differences between them and personnel
calculation schema TM00
SAP AG 1999
SAP AG
(C) SAP AG HR310 22

11.23Alternative Time Evaluation Schemas Exercises
Unit: Alternative Time Evaluation

Schemas
Topic: Introduction to Time Evaluation Schemas TM01
and TM04
Creating a Schema
1 In your enterprise, different groups of employees use different methods of time recording:
Employees who record all actual times. These employees are assigned the Time Management
status 1 in the Planned Working Time infotype (0007).
Employees who only record deviations to the work schedule. These employees are assigned
the Time Management status 9 in the Planned Working Time infotype (0007).
Time evaluation is run nightly for all employees. Since only employees with Time
Management status 1 can be evaluated with your schema ZM## (or standard schema
TM00), and only employees with Time Management status 9 can be evaluated with
standard schema TM01, schemas ZM## and TM01 have to be combined in a
comprehensive schema, Z2## (## = your group number).
1-1 Copy the processing steps from day processing in schemas ZM## and TM01 into
new partial schemas. To do so, copy ZM## to schema Z0##, and TM01 to Z1##.
In schemas Z0## and Z1##, delete all processing steps that are not performed
within day processing (that is, those before the Provide time data block and after
the Manage time accounts block).
Ensure that schemas Z0## and Z1## have the attribute Cannot be executed.
1-2 Copy the initialization section of schemas ZM## and TM01 to the day processing
section. Use the appropriate standard personnel calculation rules. Incorporate them
in schemas Z0## and Z1## using function ACTIO.
1-3 Set up the comprehensive schema Z2##. You can use schema Z299 as a guide, or
copy it, if necessary.
Use function CHECK to ensure that your schema Z2## can be used to evaluate
employees with a Time Management status of 1 or 9.
(C) SAP AG HR310 23

1-4 Use function COPY to call schemas Z0## and Z1## within day processing in your
schema Z2##. Use function IF to control that
For employees with Time Management status 1, schema Z0## is executed
For employees with Time Management status 9, schema Z1## is executed
1-5 Use the personnel action Time recording (Mini-master) to create the personnel
number 310012## (## = your group number):
Entry date 01/01/yyyy (yyyy = current year)
Personnel area 1400
Employee group 1
Employee subgroup DU (Salaried employees)
Work schedule rule NORM
Do not assign a position in the Organizational Assignment infotype (0001). This
employee participates in time evaluation, and should be assigned the Time
Management status 9.
1-6 Run time evaluation using schema Z2## for employees 310011## and 310012##.
Use the time evaluation log to check processing.
(C) SAP AG HR310 24

11.24Alternative Time Evaluation Schemas Solutions
Unit: Alternative Time Evaluation

Schemas
Topic: Introduction to Time Evaluation Schemas TM01
and TM04
1 Creating a schema
1-1 and 1-2:
In the attributes for schemas Z0## and Z1##, the field Schema can be executed should not
be activated.
Schema Z0##:
Schema Z0## contains the processing steps from day processing of schema ZM##.
Personnel calculation rule MODT is called by function ACTIO. TMON sets the groupings
for employees with the Time Management status 1.

ACTIO MODT Define groupings
BLOCK BEG Provide time data
IF NOT SIMF No simulation for future period
...
...
QUOTA Generate absence quotas
BLOCK END ****************
Schema Z1##:
Schema Z1## contains the processing steps from the day processing of schema TM01.
Personnel calculation rule TMON is called by function ACTIO. TMON sets the groupings
for employees with the Time Management status 9.
(C) SAP AG HR310 25

ACTIO TMON Define groupings
BLOCK BEG Provide time data
P2000 N SAVE Generate planned pair/provide daily
WS
...
...
QUOTA Generate absence quotas
BLOCK END ****************
1-3 and 1-4: Schema Z2##:

You use function CHECK, with parameter 2 = PON, to ensure that employees with a Time
Management status of 1 or 9 are selected in time evaluation. Using function IF with
parameter 3 = POS or NEG, you control which processing steps are performed for
employees with a Time Management status of 1 or 9.
(C) SAP AG HR310 26

COM Time Evaluation With Clock Times
COM for Time Management status 1 and 9
**
BDAY Day processing
** Options
CHECK PON Select TM statuses 1 and 9
CHECK RPR Set retro. accounting for payroll, if
required
CHECK FUT Allow evaluations for future periods
DKG Process reduced hours
OPTT MAIL 1 Mail to administrator if errors occur
**
IF POS If Time Mgmt status = 1
COPY Z0## Execute schema Z0##
ENDIF
IF NEG If Time Mgmt status = 9
COPY Z1## Execute schema Z1##
ENDIF
EDAY End of day processing
**
BEND Final processing
ACTIO TS10 Update leave balance
IF EOM If last day of period
LIMIT Adjust flextime balance
ENDIF Endif (last day of period)
EXPRT Export evaluation results
EEND End of processing block
1-5 Assign the employee the Time Management status 9 Time evaluation (planned)
in the Planned Working Time infotype (0007).
1-6 Run time evaluation using schema Z2## in one run for both your employees,
310011## and 310012##.
(C) SAP AG HR310 27

12
Integration with Payroll
Contents:
Table ZL as the interface between time evaluation and
payroll
Retroactive accounting recognition
Time wage type selection in SAP Payroll
Supplying a third-party payroll system
SAP AG 1999
(C) SAP AG HR310 1

12.2
Integration with Payroll: Objectives

Describe how the results of time evaluation are
passed on to Payroll
Explain how to trigger retroactive accounting without
gaps
Describe how SAP Payroll processes time data
Discuss how data is supplied to a third-party payroll
system
SAP AG 1999
SAP AG
(C) SAP AG HR310 2

12.3


Driver RPTIME00

Schemas
SAP AG 1999
(C) SAP AG HR310 3

12.4
Integration with Payroll: Business Scenario
The time wage types formed in time evaluation

are transferred to Payroll and valuated in the
gross part of payroll.
SAP AG 1999
(C) SAP AG HR310 4

12.5
Integration Between Time Evaluation and Payroll
Third-party payroll system
Time evaluation
SAP Payroll
results:
.
.
.
.
ZL
ZL
Time
Time wage
wage types Gross
Gross payroll
.
types payroll
.
.
.
C1
C1
ALP
Update time Time evaluation

infotypes Time wage types not run for
Messages .
all days in the
payroll period?
.
.
.
Time accounts
.
.
.
.
Time data processing by

Link with time
SAP Payroll
recording systems
SAP AG 1999
The results of time evaluation can be supplied to SAP Payroll or a third-party payroll system.
The time wage types in tables ZL, ALP and C1 (cluster B2) form the interface between time evaluation
and payroll. If time wage types have already been formed in the course of time evaluation, SAP Payroll
imports them from cluster B2 and valuates them. The time data for days in the payroll run that have not
been processed by time evaluation is evaluated in Payroll according to schema TC00 or TC04.
(C) SAP AG HR310 5

12.6
Time Evaluation Period and Payroll Period
Time Evaluation Payroll
Stored by period Cluster Payroll

B2 Retroactive
accounting
Time evaluation period Payroll period
- Global setting for the evaluation - Depends on payroll area
of time data for all employees
Set periods
Time evaluation period: One payroll

= monthly - Two-weekly for all payroll areas
Several payroll periods
- Payroll area D1 : Weekly
- Payroll area A2 : Two-weekly
- Payroll area E2 : Monthly
Query in time evaluation schema
IF EOM If the end of the time evaluation IF EOP If the end of the payroll
... period has been reached ... period has been reached
ENDIF ENDIF
SAP AG 1999
The results of time evaluation are stored by time management period in Cluster B2.
You can determine regulations in the schema that relate to the end of the payroll or time evaluation
period.
The time evaluation and payroll periods do not have to be the same length, since Payroll processes the
data it requires irrespective of the time evaluation period.
IMG: Personnel Time Management -> Time Evaluation -> General Settings -> Determine Time
Evaluation Period
(C) SAP AG HR310 6

12.7
Interaction Between Time Evaluation and Payroll
06/01
Payroll
Cluster B2
C1
Time ZL ALP
ALP
evaluation
06/01 ...
...
Payroll period
06/20 ... .
.
.
.
.
.
06/20 .
.
C1
Time wage ZL
ALP Payroll Status
type selection infotype (0003)
06/21 ...
in Payroll ... Earliest MD change
06/30 ... = 06/21/yyyy
06/30
SAP AG 1999
The internal tables ZL, C1, and ALP represent the interface between time evaluation and payroll.
ZL: contains the time wage types
C1: contains the data relevant for cost assignment
ALP: contains information for a different payment
Table ZL contains only the number of hours per time wage type; amounts are not calculated until the
payroll is run.
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 Payroll generates time wage types, it sets a retroactive accounting indicator in the Earliest MD change
field in the Payroll Status infotype (0003). This is done only if the employee takes part in time
evaluation (Time Management status other than 0).
(C) SAP AG HR310 7

12.8
Retroactive Accounting
Accounted up to
roollll
PPaayyr Next
Payroll period 06 Payroll period 07 payroll
run
Period 07
Valid 06/17/yyyy 06/17/yyyy

Time 17:30 19:00
Retroactive
accounting
for payroll
17.06
Period 06
Time Cluster B2 C1 Payroll Status

evaluation ZL ALP
infotype (0003)
Earliest MD change
06/17 ... = 06/17/yyyy
...
SAP AG 1999
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).
The following conditions must be fulfilled for time evaluation to set a retroactive accounting run for
Payroll:
The relevant time infotypes must be flagged as relevant for retroactive accounting for time evaluation
Function CHECK must feature in the time evaluation personnel calculation schema with 'RPR' as the
value of parameter 2
Define Fields Relevant for Retroactive Accounting
(C) SAP AG HR310 8

12.9
Calling Time Wage Type Selection
Schema xT00: Gross time data processing

Call subschema: TC00
Fct
Fct Par1
Par1 Par2
Par2 Par3
Par3 Par4
Par4 D
D Text
Text
..
IF
IF PDC
PDC Time
Time evaluation
evaluation active?
active?
IMPRT
IMPRT B2
B2 Import
Import results
results (cluster
(cluster B2)
B2)
PRINT
PRINT NP
NP ZL
ZL Print
Print ZL
ZL after
after import
import
DAYPR
DAYPR TC00
TC00 PDC
PDC Day
Day processing
processing ofof time
time data
data
ELSE
ELSE Time
Time evaluation
evaluation not
not active
active in
in period
period
DAYPR
DAYPR TC00
TC00 Day
Day processing
time data
data
ENDIF
ENDIF
..
Call subschema: TC04

Fct
Fct Par1
Par1 Par2
Par2 Par3
Par3 Par4
Par4 D
D Text
Text
..
IF
IF PDC
PDC Time
Time evaluation
evaluation active?
active?
IMPRT
IMPRT B2
B2 Import
Import results
results (cluster
(cluster B2)
B2)
PRINT
PRINT NP
NP ZL
ZL Print
Print ZL
ZL after
after import
import
DAYPR
DAYPR TC04
TC04 PDC
PDC Day
Day processing
time data
data
ELSE
ELSE Time
Time evaluation
evaluation not
not active
active in
in period
period
DAYPR
DAYPR TC04
TC04 Day
Day processing
time data
data
ENDIF
ENDIF
..
SAP AG 1999
In Payroll, time evaluation is called in the personnel calculation schema XT00, or in the relevant
country-specific standard personnel calculation schema (for example, UT00). Personnel calculation
schema XT00 is an international personnel calculation subschema of X000.
Function DAYPR calls a subschema with parameter 1 (TC00 or TC04). The main task of the subschema
is time wage type selection. DAYPR ensures that the schema is processed once daily for each employee.
If "PDC is specified as the value of parameter 2, function DAYPR takes the results of time evaluation
into account.
Additional time-related functions in the gross part of payroll:
Absence valuation (function PAB)
Shift change compensation (personnel calculation rule X064)
Valuation bases for different payments (function PALP)
Transfer of time data from ZL to IT (function ZLIT)
(C) SAP AG HR310 9

12.10
Day Processing in Schema TC00 or TC04
11 12
1
10
2
9
3
8
4
7 6 5 Planned pair
acc. to DWS
Provide data Absences
Attendances
Breaks
Planned working
Classify times
times
Overtime

.
.
.
.
.
.
.
.
SAP AG 1999
The steps and rules according to which day processing handles time data in Payroll are set in schema
TC00 or TC04.
The main task of TC00 and TC04 is time wage type selection. The same process is used to determine
time wage types for planned work and overtime in the Time Wage Type Selection Rule view (V_T510S)
and function GWT as for day processing in RPTIME00.
In Payroll, you have the same options as in time evaluation for maintaining time data in table TIP and
forming your own regulations within day processing of time data. Only time evaluation functions and
operations are used for day processing. You use personnel calculation rule TMOD to set the same
groupings for table accesses as in schema TM01 for initialization.
The option of managing time balances and maintaining quotas is unique to time evaluation. Function
POVT in schema TC00 (or TC04) only generates time wage types; it cannot form balances or update
quotas.
For all days that have not been processed by time evaluation, all times within the planned working time
period become planned work and all times outside the planned working time become overtime in TC00
or TC04.
(C) SAP AG HR310 10

12.11
Supplying a Third-Party Payroll System
RPTIME00
Time
Time
Time
evaluation ZL
evaluation
evaluation Interface toolbox
WType
WType IFTYP
IFTYP
.. .. .. .. .. .. Seq.
file
Differences are
formed if there is a
retroactive run
SAP AG 1999
Table ZL also serves as the interface between time evaluation and a third-party payroll system.
Menu: Human Resources -> Time Management -> Administration -> Environment -> Third-
Party Payroll
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. If there is a retroactive calculation, the difference between the wage types already
exported and the new wage types is written to the sequential file.
The third-party payroll system uses the IFTYP to determine whether the wage type is a planned,
overtime or absence wage type.
The Interface Toolbox transaction (PU12) is used as an export program. The interface format "TIME is
used as a reference. If the time evaluation period is identical to the payroll period, you can use the report
RPTEZL00 as an alternative method of supplying the third-party payroll system.
IMG: Personnel Time Management -> Time Evaluation -> Integration with Payroll ->Prepare Payroll
Using a Third-Party System
(C) SAP AG HR310 11

12.12
Integration with Payroll: Summary
You are now able to

Describe the interaction between
time evaluation and payroll
SAP AG 1999
SAP AG
(C) SAP AG HR310 12

13
Time Statement and Reporting
Contents:
Customizing a time statement form
Time Management report tree
Querying time data
Business Information Warehouse
SAP AG 1999
(C) SAP AG HR310 1

13.2
Time Statement and Reporting: Objectives
At the conclusion of this unit, you will be able to

Use special techniques to customize a
time statement form
Use various options for running reports on time
recording data and time evaluation results
SAP AG 1999
SAP AG
(C) SAP AG HR310 2

13.3


Driver RPTIME00

Schemas
SAP AG 1999
(C) SAP AG HR310 3

13.4
Time Statement Form and Reporting: Business
Scenario
You want your employees to receive an

overview of the time accounts and time wage types
formed in time evaluation.
Management wants to find out the amount of
overtime worked in your enterprise.
Management wants to create statistics on employee
productivity in the different areas of the enterprise.
SAP AG 1999
(C) SAP AG HR310 4

13.5
The Time Statement - RPTEDT00
Inform employees Check results Display overviews
Display totals overview

Answer queries
Check time PersNo.Name WrkTime FLEX
Time statement evaluation run

01234 Helga Martin 148.00 - 3.24
02786 Uri Kwan 148.00 12.50
Send 03897 Sang Won 74.00 3.50
statements
Output cappings
PersNo. Name OT Capp.

Up-to-date 01234 Helga Martin 15.50 5.50
information 02786 Uri Kwan 2.00 0.00
03897 Sang Won 12.25 2.25
online
Form class TEDT Form class TELU
SAP AG 1999
You can use report RPTEDT00 (Time Statement) to present the time accounts and time wage types
determined by time evaluation in a clear layout. The statement creates an overview of the time
evaluation results for each day in a time evaluation period.
Menu: Human Resources -> Time Management -> Administration -> Time Evaluation -> Time
Statement
Time data administrators can use the time statement as a method of monitoring employee times, and they
can send statements to employees to keep them informed. Using the self-service application, employees
can access the time statement themselves in the Internet or intranet.
You can use the time statement to check the results of the time evaluation run. To do this, you must enter
a variant for RPTEDT00 in the parameters for RPTIME00.
You set up the time statement form in Customizing. There are two form classes, designed to cover
different requirements:
TEDT: Output of time accounts and time wage types for each employee
TELU: Output of special time accounts for a group of employees
(C) SAP AG HR310 5

13.6
The Time Statement
Attributes Output languages
Wage types and

address layout Individual or
totals overview?
Country grouping 10 USA

Form class TELU Time statement form overview list
Attributes
Form name TFL1 Standard form: Time balance overview
Person responsible
Form name of corresponding TEDT form TF02
Maximum length Current length Form layout

Lines 99 Lines 99 Edit Language
Columns 76 Columns 76
Can branch to
individual overview
SAP AG 1999
Because of the address layout and the output of wage types, time statement forms are country-specific.
You can also output the time statement in the language of the employee, the administrator, or the
personnel subarea, regardless of the country for which the time statement is designed.
In the area menu for the form layout, choose Edit ->Copy language for an existing form to create
another language version of the form, then translate the text elements and headings. The system reads the
employee's language from the Personal Data infotype (0002), and the language of the personnel subarea
from feature SPRSL.
You can assign time statement forms of form class TELU to a form of form class TEDT. This allows you
to double-click a TELU form in the output list to branch to a TEDT form, that is the detail view for one
employee.
Forms are specific to one client. To copy a form from one client to another, choose Extras -> More tools
in the initial screen of the form editor.
IMG: Personnel Time Management -> Time Evaluation -> Evaluations and the Time Management Pool
-> Time Statement Form -> Set Up Time Statement Form Using Form Editor
(C) SAP AG HR310 6

13.7
Form Layout
Header
Windows for arranging
ED .... Individual results per day
form layout
Day 1
HD
Set up
header
Day 2
.. F1
..
Day 31 Output
results
LP Totals overview
SK Time transfer specifications

Groups for
displaying ZL Time wage types
information
objects AN Attendance quotas
Absence quotas
AB
Messages
FE
SAP AG 1999
You should always copy a standard SAP form when you create a time statement form.
You create the layout for the time statement form in two windows:
In the HD window, you create the form header. General data, such as the employee's name, address,
personnel area, cost center, and so on, is displayed here.
In the F1 window, you create the information objects that you want to display on the time statement.
Groups are defined for the different business units. You can use them to output individual results for
each day, totals overviews, or summarized time wage types, for example. The information and
individual fields you can output in the different groups are predefined.
(C) SAP AG HR310 7

13.8
The Form Editor
Text elements
Window
Window + GR
group HD HD ------------------------------------------------------------------------------------------------------------------------------
HD Time statement list
HD Printed on: DATUM_______ Page PA
HD ------------------------------------------------------------------------------------------------------------------------------
HD Employee : PERNR____ ENAME___________________________________
HD Administrator: SACHZ_____________________
HD -------------------------------------------------------------------------------------------------------------------------------
HD Personnel area: WERK Personnel subarea: BTRT
Table P0001 Org. assignment Condition

Table field SACHZ Time data administrator
Output length 20
Specification Conversion 26 Name of administrator
of output Rule Input help single fields
Offset Single field origin Single fields
Window
Selected field P0001-SACHZ Double-click to insert Block HD - Header data
General fields
SCHLW-BEGINN Start date in current period
SCHLW-PAGE Page counter
...
P0001-SACHZ Administrator for time recording
SAP AG 1999
The window display corresponds to the subsequent layout on the form. You enter all text elements and
table fields you want to be output on the user interface, as if writing on the form directly.
You can copy the table fields from the modeless window Input help single fields. To insert a field into
the form layout, double-click on it. You can also copy fields or lines. You can create text elements, which
are stored automatically (area menu of form layout: Goto -> Text modules).
For detailed information on a single field, double-click on the field.
You can specify the following factors:
Output length:
You should specify this in the Output length field, except for texts, for which the output length can be
entered directly in the window.
Conversion:
You can determine the format used to display the data.
Rule:
You can specify conditions to determine the situations in which information is displayed.
Print offset:
You can hide leading characters (such as leading zeros).
(C) SAP AG HR310 8

13.9
Day Data
D
up E
G ro
Individual results
Day Text InT OutT St. time End time Rec. Plnd Skel. time Flex. OT DWS
02 Attendance hours 00:00 07:30 7 .40

Off-site work 08:00 10:00 2 .00 7.75 9.50 1.75 0.00 GLZ
03 Attendance hours 08:00 18:15 10.25 7.75 8.50 0.75 0.00 GLZ
04 Attendance hours 08:00 18:15 10.25 7.75 8.50 0.75 0.00 GLZ
Weekly total 37.25 40.50 3.25 0.00
: s
ups sult
Gro idual re
v
Indi ay
r d
pe ED - Indiv. results, TM status 1-9 ZT - Daily time wage types
EP - Indiv. results, TM status 1, 2 ST - Weekly time transfers
EN - Indiv. results, TM status 9 WS - Weekly totals
PD - Prelim. ind. results, TM status 1-9

PP - Prelim. ind. results, TM status 1, 2
PN - Prelim. ind. results, TM status 9
SAP AG 1999
Individual results for each day: Data for each day, such as the daily actual times, the day balances
formed, and so on, are listed.
A number of groups are available for displaying the day data:
You can display different information according to employees' Time Management status.
If required, you can display preliminary day results that have been determined by time evaluation.
You can display the individual results for each day, with the date and weekday. You determine the last
day of the week in feature LDAYW.
You use table TP to output the time pairs or the number of hours for the following types of time data:
- Time pairs (table PT) - Attendances
- Absences - Substitutions
- On-call duties
You use the TEXT field of table TP to display the text belonging to the corresponding subtypes of the
infotypes.
At the end of each calendar week, you can display a weekly total of the day balances that have been
output. This is done using group WS.
(C) SAP AG HR310 9

13.10
Prioritizing the Information Displayed
What is the most important information for a particular day?
Day Text InT OutT St. time End time Rec. Plnd Skel. time Flex. OT DWS
01 Public holiday EE not at work 4.00 4.00 0.00 0.00 FLEX B

02 Thursday 07:45 09:55 2.17
Doctor's visit <1 day 10:00 14:00 4.00
14:06 17:05 2.98 8.00 8.00 0.23 0.00 FLEX
Only for Only on public Information prioritized

attendances/absences holidays by columns
High 4 Time pair text Balances for each day

Information prio.
2 Public holiday text Public holiday text . ...
prioritized Last line
by lines 1 Time pairs for each day
for each day
0 Weekday text
Day
First line for each day -
only item of information on days off
SAP AG 1999
It is possible for several, conflicting items of information to exist on the same day (for example, an
absence and a public holiday). You can determine which information is displayed on a particular day by
assigning priorities within the groups ED and PD.
You can assign priorities from 1 - 9 and from A - Z, whereby 9 has a higher priority than 1, and Z has a
higher priority than A.
Information for each day is superimposed character by character. This means that information with the
low priority is output if there is no information of a higher priority on that day. When you create a form,
you are recommended to create blocks to put all information that is to be overwritten if required in the
same position.
Before information for a day can be output, the corresponding data must exist for that day (for example,
a day's time pairs are only displayed if time pairs exist for that day).
If, on one day, several items of information exist in table TP, several lines are displayed in the time
statement form.
You can use rules to limit the situations in which information is displayed (for example, only on public
holidays or only on workdays where attendances exist).
If you want to display particular information only once for each day, you can use rules FL or LL to
display it in only the first or last line.
(C) SAP AG HR310 10

13.11
Totals Overview / Time Wage Types per Day
P
up L
G ro Totals Overview
Time type Number Time type Number
Flex. balance prev. period 0.00 Overtime to compensate 0.00

Flex. balance curr. period 5.25 Overtime to remunerate 2.50
Flex. balance total 5.25 Overtime basic/time off 0.00
Productive hours cumul. 42.50 Total overtime 2.50
Remaining leave 10.00
L
r oup Z
G Time wage types
Day OTime BR OT 25% OT 50% OT total Night bonus Hol. bonus
09/06/1999 2.00 0.30 2.30
SAP AG 1999
In group LP (totals overview), you can display time balances in relation to periods. The system reads the
time account statuses from table SALDO. In field SCHLW-QUOTAA, you can display information on
an absence quota, and in field SCHLW-QUOTAP information on an attendance quota.
In group ZL, you can display the time wage types that are determined daily. If you output more than than
one time wage type in each line, the results are compressed for each time wage type, for each day.
If you have a separate line for each time wage type,
You can display cost information from tables C1 and ALP beside the time wage type
You can use report RPTEDT00 (Time Statement) with the parameter Compress time wage types to
display summarized TL entries for a day. In this case it is not possible to display cost information.
(C) SAP AG HR310 11

13.12
Compressing Time Balances and Wage Types
Display table SALDO in Cluster B2
Time type No.

... ...
0002 Planned time 157.45
0003 Skeleton time 156.45
0005 Flextime balance 10.00
0008 Flextime previous period 7.00
... ...
Change layout of total GLZA
Total ID GLZA Flextime balance current period
Table ID Long text RZ

SALDO 0005 Flextime balance +
Tables ZL SALDO 0008 Flextime previous month -
and SALDO
from cluster B2
Time statement list Gro

up L
P
Totals Overview
Time type No. Time type No.
FLEX balance prev. period 7.00 Overtime to compensate 0.00

FLEX balance curr. period 3.00 Overtime to remunerate 0.75
FLEX balance total 10.00 Overtime basic/time off 0.00
Productive hours cumul. 41.50 Total overtime 0.75
Remaining leave 14.00 Total overtime
SAP AG 1999
To summarize time balances or time wage types, choose Goto -> Sums from the form layout. You can
display the summarized information in the time statement in the day view, the totals overview (group
LP), and the time wage types, just as you can display the original data.
You can use this procedure to form totals or differences, without having to modify the corresponding
personnel calculation rules in the time evaluation schema. However, the values calculated are temporary,
and are not stored in the database.
(C) SAP AG HR310 12

13.13
Additional Groupings for Arranging Information
G ro
up S
K
V
up A
G ro
Time transfers
AN
r oups
On-call G AB
and
duties
Attendance and G ro
absence quotas up Z
M
FE
.
.
Messages from time evaluation

roup
.
.
G Time wage types .

.
Date Messages cumulated over

.
.
02/13/2001 Partial-day absence exceeded the period

02/22/2001 Core time violation
SAP AG 1999
You can specify conditions to control how information is displayed. For example, you can use them to:
Limit the amount of information to be displayed. You can specify, for example, that only messages
from time evaluation are displayed (error types 1 and 5).
Specify more details on a wage type or balance. Use the ANZHL field as a print field, and the wage
type and balance as a condition field.
If you edit form class TEDT, you can only use the relational operator EQ (equals). If you edit form class
TELU, you can use LT (less than) and GT (greater than), in addition to EQ.
(C) SAP AG HR310 13

13.14
Converting Output Data
Date format Long texts for fields

ZL-ANZHL
SCHLW-CDATUM Condition: LGART EQ MM10
Conversion
DM 13 LT
05 09/05/1999 0.30 Overtime 25%

Day of the Date in full
month Number field Long text
Absence quotas
SCHLW-QUOTAA Time accounts
DF RD OR ...
05.00 12.00 02.00

Quota reduced by Quota remainder Quota
on key date requested
SAP AG 1999
In the Conversion field,you can specify when you create the form how the field is to be laid out, for
example, the output of quota statuses, short and long texts for fields, amongst other things.
(C) SAP AG HR310 14

13.15
Creating Text Conversions
Display weekday texts

Form layout Change texts
W1 Monday
Table SCHLW
Table field WEEKDAY W2 Tuesday
Conversion TW W3 Wednesday
...
Display day type text

Form layout
Change texts
Table PSP
D0 Workday
Table field TAGTY
D1 Off/paid
Conversion TD
SAP AG 1999
If you want specific texts to be displayed according to the date, day evaluated, and so on, you can define
text conversions for a field in the form. Note that only the first character of a table field can be evaluated.
Text conversions are all conversions that begin with "T".
To create the texts for the text conversions, choose Goto -> Text modules from the form layout view.
When weekday texts are displayed, the system reads the last day of the week (text module W7) from the
specifications in feature LDAYW.
Other common text conversions:
Pair type: TP-PTYPE
Time Management status: WPBP-ZTERF
(C) SAP AG HR310 15

13.16
The Time Management Report Tree
Work
schedule Absences
Time Leveling
RPTCMP00
Time Statement RPTEDT00

(Form class TEDT)
Attendances Time Time Balance Overview

balances RPTEDT00 (Form class
TELU)
Cumulated Time Balances
RPTBAL00
Time Balances for Download
RPTDOW00
SAP AG 1999
The Time Management report tree gives you easy access to the most important reports in Time
Management. To access the report tree, choose Human Resources -> Time Management ->
Administration -> Information System -> Report Selection.
All the important reports from the time evaluation environment are listed under the Time Accounts node.
You can evaluate the balance statuses of individual employees, and find information on the time
accounts of several employees in summarized views.
The standard Time Management reports enable you to run evaluations over individual sources of data,
such as individual infotypes or clusters. It is not possible to evaluate infotype data and cluster data
simultaneously. Therefore, the standard reports may often provide only a section of the relevant data.
(C) SAP AG HR310 16

13.17
Time Types and Quota Types for Reporting
Quota Statuses Time and Labor Personal Work
Schedule
Leave
Absence types Planned
Attend- working
quotas Table
ances time
ZES
Substit-
Infotype Attendance EE remun- Table
Absences utions
data quotas eration info ZL
Time
evaluation Work schedule
Infotype results data
data
Reporting Reporting
quota types time types
Simulated infotypes for SAP Query

InfoSources for Business Information Warehouse
Display objects for the Time Manager's Workplace
SAP AG 1999
Reporting time types (also referred to as time types for reporting) enable you to create a uniform view on
time data from various Time Management datasets (infotype and cluster data). Reporting quota types
(also referred to as quota types for reporting) enable you to create a uniform view on quota data from
various Time Management infotypes.
IMG: Personnel Time Management -> Information System -> Settings for Reporting
Depending on employees' organizational assignments, you can include other values in the reporting time
types and reporting quota types. To do so, maintain feature GRDWT for reporting time types, and
feature GRDWK for reporting quota types.
Simulated infotypes enable you to evaluate data from various sources (infotype data, time evaluation
results (cluster tables ZES, ZL with ALP and C1), and data from the personal work schedule. The data is
not made available from the various database tables until the evaluation runtime. You can use simulated
infotypes for your own ABAP programs and evaluations using SAP Query, in the same way as standard
infotypes.
Note: Previously, when evaluating attendances and absences of more than day, each report had to count
the attendance and absence records itself. This is no longer the case with simulated infotypes, since the
attendance and absence records are counted and made available for each day.
(C) SAP AG HR310 17

13.18
Time and Labor Simulated Infotype (2501)
SAP R/3 time data Reporting

time type
Employee with Time Management Overtime
status 1: 10000004
Time type 0040 - Overtime worked
Salaried employee with Time 10000004

Management status 0:
Wage type MM00 - Overtime
basic remun.
Wage type MM10 - Overtime 25%
Wage type MM20 - Overtime 50%
Master Reporting Act. Unit Debited Organizational

cost time type time cost
center center Assignment
Org. infotype (0001)
4711 10000004 1000 Hrs 4711
Assignment Planned Working
infotype 4711 10000004 100 Hrs 4712 Time infotype (0027)
(0001) 4711 10000004 12 Hrs 4713 Cluster table C1
Interface table ASSOB
SAP AG 1999
The Time and Labor simulated infotype (2501) groups together the following data:
Data from the Organizational Assignment (0001) and Planned Working Time (0007) infotypes
Time and labor data such as the reporting time type (field REPTT) with the number of hours and
days
Cost assignment data
Activity allocation data
Data on a different payment
For more information, see the SAP Library by choosing Human Resources -> Personnel Time
Management -> Information System -> Reports Using SAP Query.
(C) SAP AG HR310 18

13.19
Quota Statuses Simulated Infotype (2502)
Reporting quota type

Leave Entitlement
SAP R/3 quota data 00000001
Absence quotas
- Standard leave
00000001
- Educational leave
- Special leave
Example: Creating
leave statistics
Personnel Reporting Rem. Deduc Compe

quota Expired
area leave ted nsated
type
Org. DE01 00000001 200 100 0 0
Assignment
DE02 00000001 300 130 0 20
infotype
(0001) DE03 00000001 250 120 20 10
SAP AG 1999
The Quota Statuses simulated infotype (2502) groups together the following data:
Data from the Organizational Assignment (0001) and Planned Working Time (0007) infotypes
Quota transaction data:
Reporting quota type (field QUOTA)
Data from the Absence Quotas infotype (2006)
Data from the Attendance Quotas infotype (2007)
Data from the Leave Entitlement infotype (0005)
(C) SAP AG HR310 19

13.20
Standard Time Management Queries
Selection according to
time data IDs used in the
Attendances: List query Time Manager's
Workplace
time data IDs used in the
Absences: List query Time Manager's
Workplace
Selection according to time

data IDs used in the Time
EE Remuneration Info query Manager's Workplace or
wage types
Time and Labor query reporting time types
SAP AG 1999
You can use SAP Query to define your own reports quickly and effectively, without having to do any
programming. You can select data from any SAP R/3 tables. SAP delivers standard queries, which you
can use as a basis for your own customer-specific queries.
Attendances: List query: Overview of each employee's attendances, displaying attendance days and
hours and account assignment information (such as the cost center and order debited)
Absences: List query: Overview of each employees absences, specifying the absence days and hours. It
also displays a set of statistics showing the total quota deduction.
Employee Remuneration Information query: Overview of each employees remuneration information,
specifying the wage type and the number of hours, or the rate, or the amount, and cost assignment
information.
Time and Labor query: Overview of each employees time and labor data, specifying the actual times,
the account-relevant time, and cost assignment information
Time and labor data is attendances, absences, time balances, and time wage types that have been
grouped together in a reporting time type.
Account-relevant time data is counted attendances and absences that deduct from a quota.
Menu: Tools -> ABAP Workbench -> Utilities -> SAP Query -> Queries
(C) SAP AG HR310 20

13.21
Display Objects for the Time Manager's Workplace
Using reporting time types for message processing
Field selection: Screen area WLI

Display objects Groups of display objects for
message processing
Time Reporting time types Time and labor display

types object
Overtime 1000040 - Overtime OVERTIME - Overtime

hours
OVER - Overtime and planned hours
Planned hours 1000002 - Planned PLANNED TIME - Planned
hours hours
V_T557BU V_TBAL_OBJECTS V_PT_FIELD_SEL
Message list
Cat. Status Name Date Message text Additional information Msg

Kai Wishids 15.04.2000 Unapproved overtime exists Unapproved OT 4.15 hrs
15.04.2000 EE at work although OFF OT 0.00//Plnd 0.00
SAP AG 1999
You can use reporting time types to output contextual information in the message processing function of
the Time Manager's Workplace. In addition, you can display contextual information from the employee's
master data or from reporting quota types.
If required, you can also output information from various sources, such as reporting time types and
master data, for example, alongside the contextual information, by arranging display objects into groups.
Personnel Time Management -> Time Manager's Workplace -> Basic Settings -> Select HR Master
Data and Time Data
Personnel Time Management -> Time Manager's Workplace -> Set Up Message Processing -> Create
Groups of Display Objects
(C) SAP AG HR310 21

13.22
Business Information Warehouse
BW time type Business Information

SAP R/3 R/3 time data
Productive time Warehouse
Hourly wage earner: - 00000005
Time type 0050-
Prod. hours
00000
005
Salaried employee:
Overtime
from infotype 2002 00000
009
Planned time from WS
All employees:
00000
Time type 0050- 005
Prod. hours
Cost center Productive time Costs . ..
Hourly wage earner:

Time type 0050-
Prod. hours 00000
005
Salaried employee:
Overtime 00000
009
from infotype 2002
Planned time from WS
SAP AG 1999
The Business Information Warehouse (BW) is a stand-alone SAP product. It is a data warehouse
application, integrated with predefined business contents.
The business content of the SAP R/3 applications is carried by what are known as InfoSources.
InfoSources contained compressed data from R/3 applications.
In addition, you can customize summarization rules to suit your individual requirements.
To customize the Business Information Warehouse, use transaction SBIW.
(C) SAP AG HR310 22

13.23
Time Evaluation in the mySAP Workplace
Internet Application
Components MiniApps
Time Statement Clock In/Out

Real-time posting of clock-in
Monthly overview of recorded and -out times, off-site work,
time data, bonuses, and time and breaks
accounts
Time Accounts
Employee Time Accounts
Overview of absence quotas; Time balances, absence
option of projecting for future entitlements, and attendance
periods approvals
MiniApps
Attendance Check Entitlements Nearing Expiry
Real-time overview of the Overview of the absence

attendance of groups of entitlements due to expire of
employees the employees assigned to
Time administrator/ him or her
Time supervisor
SAP AG 1999
The mySAP Workplace contains several Employee Self-Service applications and MiniApps that provide
your employees and time administrators/time supervisors with the current input and output of time
evaluation:
Employee Self-Service applications
Time Statement (PZ04)
Time Accounts (PZ09)
MiniApps
Time Accounts (PT_TimeBalances)
Clock In/Out (MA_PT_TIMEREC)
Entitlements Nearing Expiry (PT_ExpireQuota)
Attendance Check (MA_ATTCHECK)
The above-mentioned ESS applications and MiniApps represent only a selection of the services
currently available. Additional services may be available in future Web Add-On releases. For up-to-date
information, see SAPNet.
(C) SAP AG HR310 23

13.24
Time Statement and Reporting: Summary
You are now able to

Customize the time statement form to suit
your requirements
Explain the various options for running reports
on time recording data and time evaluation
results
SAP AG 1999
SAP AG
(C) SAP AG HR310 24

13.25Time Statement and Reporting Exercises
Unit: Time Statement and Reporting

Topic: Customizing a Time Statement Form
Customizing the Standard Time Statement Form TF02
1 Customizing the time statement form

In your enterprise, you want the standard time statement form TF02 to be customized to
cater to your special requirements. You want the employees employment percentage and
the status of compensation time account 90## to be displayed.
You make the required Customizing settings in the step Personnel Time Management
Time Evaluation Evaluations and the Time Management Pool Time Statement Form
Set Up Time Statement Form with Form Editor.
1-1 Copy form TF02 to form ZF## (## = your group number).
1-2 Display the Employment percent field from the Planned Working Time infotype
(0007) in the form header. To do so, add another line to the form header.
1-3 In the individual results (group ED), replace the planned working time with the day
balance 90##.
1-4 In the totals overview (group LP), enter the period balance 90## in an additional
line.
(C) SAP AG HR310 25

13.26Time Statement and ReportingSolutions
Unit: Time Statement and Reporting

Topic: Customizing the Time Statement Form
1 Customizing the time statement form

You set up the form in the step: Personnel Time Management Time Evaluation
Evaluations and the Time Management pool Time Statement Form Set Up the Time
Statement Form with the Form Editor.
1-1 To copy form TF02, choose Extras Other tools. In the dialog box, enter the
name of the form to be copied (TF02). In the dialog box that follows, enter the
name of the new form (in the Form name field). Ensure that you do not copy
between two different clients.
1-2 From the initial screen of the form editor, you can branch to the form layout by
choosing the Change button. You can branch from the form layout to the
maintenance of the form header (group HD) by double-clicking window HD.
To display the Employment percentage from the Planned Working Time infotype
(0007), you have to insert a new line:
Enter Employment percentage directly, and confirm by choosing ENTER.
To enter the output field, select the field Employment percentage (WPBP-EMPCT) from the
group Payroll Results: Work Center/Basic Pay in the Input help single fields window.
In window HD, double-click the position where you want the field to be displayed.
Exit the maintenance of the form header by choosing Transfer.
(C) SAP AG HR310 26

1-3 In the F1 area, double-click to branch to window F1:
Change the heading line in group ED by overwriting PTime with your own text.
Replace the planned working time by the compensation time account 90## by double-clicking
the column in which the planned working time is displayed, then double-clicking the field
ANZHL.
Replace the condition ZTART EQ 0002 with condition ZTART EQ 90## (## = your group
number).
1-4 To customize the totals overview, scroll in window F1 to group LP. At the end of
the group, insert a new line to include period balance 90##:
To enter the name of period balance 90##, position the cursor at the place where you want it to
appear, and write the required text directly. Choose ENTER to confirm your entry.
To enter the value of period balance 90##, proceed as described in 1-2. In the Input help single
fields, choose in block LP under Time balances per period the field Number of time balances
in period (ANZHL). Insert the field into the new line. Set the condition ZTART EQ 90## (## =
your group number). Choose ENTER to confirm your entry.
Exit maintenance of window F1 by choosing Transfer. Save your form.
(C) SAP AG HR310 27

14
Appendix
Contents:
Personnel calculation rule Z2##
Personnel calculation rule Z3##
SAP AG 1999
(C) SAP AG HR310 1

14.2
Personnel Calculation Rule Z2##
Comp. time accrual
Planned hrs DWS = 0 ?
Day type
Employee at work
Employee absent
Set
Add day balance
Set
Divide
Add day balance
SAP AG 1999
(C) SAP AG HR310 2

14.3
Personnel Calculation Rule Z3##
Processing special times
Attendance type
TIP ->TOP current time type
Processing type
Processing type
SAP AG 1999
(C) SAP AG HR310 3

HR310 TimeEvaluationWithClockTimes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HR310 TimeEvaluationWithClockTimes

Uploaded by

Copyright:

Available Formats

HR310 Time Evaluation With Clock

Release 640 04/06/2006

Copyright 2004 SAP AG. All rights reserved.

HR051 1 day HR305 3 days HR390 2 days

Notes to the user

(C) SAP AG HR310 1

This course will prepare you to:

(C) SAP AG HR310 2

At the conclusion of this course, you will be able to:

(C) SAP AG HR310 3

Unit 1 Course Overview

(C) SAP AG HR310 4

Unit 8 Operations as Tools of Time Evaluation

(C) SAP AG HR310 5

Business Overview of Time Operations as Tools ofTime

Time Evaluation in the SAP System Personnel Calculation Schema TM00

Concept of the Time Evaluation Special Solutions

Time Evaluation Messages Alternative Time Evaluation

Customizing Time Evaluation Integration with Payroll

Data Collection in Time Evaluation Time Statement and Reporting

(C) SAP AG HR310 6

(C) SAP AG HR310 1

At the conclusion of this unit, you will be able to:

(C) SAP AG HR310 2

Business Overview of Time Operations as Tools of Time

Time Evaluation in the SAP System Personnel Calculation Schema TM00

Concept of the Time Evaluation Special Solutions

Time Evaluation Messages Alternative

Customizing Time Evaluation Integration with Payroll

Data Collection in Time Evaluation Time Statement and Reporting

(C) SAP AG HR310 3

Recording... ...evaluating... ... and using time data

SAP Time Evaluation Create wage types

(C) SAP AG HR310 4

Time Supervisor: Department head,

Delegates time management tasks:

Shift Planner: Time Administrator:

Time Management Specialist (Role SAP_HR_PT_TIME-MGMT-SPECIALIST): The Time

Time Administrator (Role SAP_HR_PT_TIME-ADMINISTRATOR, composite role SAP_WP_TIME-

Time Supervisor (Role SAP_HR_PT_TIME-SUPERVISOR): The Time Supervisor is responsible for

(C) SAP AG HR310 5

(C) SAP AG HR310 6

SAP Time Employee

Specialist Inform employees

Use the results

(C) SAP AG HR310 7

Time evaluation with clock times

Time evaluation without clock times

(C) SAP AG HR310 8

Recording all times

Attendance 08:00 11:00

Doctor's appt 11:00 14:00

Attendance 14:00 17:00

Recording only deviations

Doctor's appt 11:00 14:00

There are two different methods of time data recording:

(C) SAP AG HR310 9

You have learned what time evaluation is

(C) SAP AG HR310 10

(C) SAP AG HR310 1

At the conclusion of this unit, you will be able to:

(C) SAP AG HR310 2

Business Overview of Operations as Tools of Time