HR311
Time Evaluation Without Clock
Times
mySAP Human Resources
Date
Training Center
Instructors
Education Website
Participant Handbook
Course Version: 2003 Q3
Course Duration: 5 Day(s)
Material Number: 50064149
An SAP course - use it to learn, reference it for work
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.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Trademarks
•
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are
registered trademarks of Microsoft Corporation.
•
IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®,
S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.
•
ORACLE® is a registered trademark of ORACLE Corporation.
•
INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered
trademarks of Informix Software Incorporated.
•
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
•
Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,
VideoFrame®, MultiWin® and other Citrix product names referenced herein are
trademarks of Citrix Systems, Inc.
•
HTML, DHTML, XML, XHTML 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.
•
SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow,
SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and
mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in
several other countries all over the world. All other products mentioned are trademarks
or registered trademarks of their respective companies.
Disclaimer
THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY
DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING
WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,
INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS
CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,
INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY
KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST
PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED
SOFTWARE COMPONENTS.
About This Handbook
This handbook is intended to complement the instructor-led presentation of
this course, and serve as a source of reference. It is not suitable for self-study.
Typographic Conventions
American English is the standard used in this handbook. The following
typographic conventions are also used.
Type Style
Description
Example text
Words or characters that appear on the screen.
These include field names, screen titles,
pushbuttons as well as menu names, paths, and
options.
Also used for cross-references to other
documentation both internal (in this
documentation) and external (in other locations,
such as SAPNet).
17-09-2004
Example text
Emphasized words or phrases in body text, titles
of graphics, and tables
EXAMPLE TEXT
Names of elements in the system. These include
report names, program names, transaction codes,
table names, and individual key words of a
programming language, when surrounded by body
text, for example SELECT and INCLUDE.
© 2004 SAP AG. All rights reserved.
iii
About This Handbook
HR311
Type Style
Description
Example text
Screen output. This includes file and directory
names and their paths, messages, names of
variables and parameters, and passages of the
source text of a program.
Example text
Exact user entry. These are words and characters
that you enter in the system exactly as they appear
in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate
that you replace these words and characters with
appropriate entries.
Icons in Body Text
The following icons are used in this handbook.
Icon
Meaning
For more information, tips, or background
Note or further explanation of previous point
Exception or caution
Procedures
Indicates that the item is displayed in the
instructor’s presentation.
iv
© 2004 SAP AG. All rights reserved.
17-09-2004
Contents
Course Overview ............................................................................. vii
Course Goals.................................................................................vii
Course Objectives ...........................................................................vii
Unit 1: Time Evaluation with SAP R/3 .....................................................1
Business Overview of Time Evaluation .................................................... 2
Prerequisites for Evaluating Time Data .................................................... 9
Concept of the Time Evaluation Driver RPTIME00 .................................... 24
Unit 2: Time Evaluation Messages ....................................................... 45
Time Evaluation Messages................................................................ 46
Unit 3: Collecting and Processing Time Data.......................................... 59
Customizing Time Evaluation ............................................................. 61
Data Collection in Time Evaluation ....................................................... 78
Operations as Tools of Time Evaluation ................................................. 93
Creating a Personnel Calculation Rule ................................................. 102
Unit 4: Personnel Calculation Schema TM04 ......................................... 113
Structure of the TM04 Schema .......................................................... 115
Providing and Checking Time Data ..................................................... 121
Determining Planned Working Times ................................................... 135
Determining Overtime ..................................................................... 146
Selecting Time Wage Types.............................................................. 162
Compensating Overtime Wage Types .................................................. 180
Managing Time Accounts................................................................. 185
Accruing Absence Quotas ................................................................ 205
Unit 5: Time Evaluation With Clock Times.............................................233
Using Time Recording Systems ......................................................... 234
Processing Time Postings in SAP R/3 .................................................. 245
Time Evaluation With Clock Times ...................................................... 256
Unit 6: Using the Results of Time Evaluation.........................................285
Integration with Payroll.................................................................... 286
17-09-2004
© 2004 SAP AG. All rights reserved.
v
Contents
HR311
Time Statement ............................................................................ 295
Reporting for Time Evaluation ........................................................... 313
Appendix 1: Functions for Calling Personnel Calculation Rules
..............327
Appendix 2: Using Functions and Operations to Process Work Tables
Appendix 3: Overview: Data Flow During Time Evaluation
.....329
.....................331
Appendix 4: Tables in Cluster B1
.....................................................333
Appendix 5: Tables in Cluster B2
.....................................................335
Glossary .......................................................................................339
Index ............................................................................................341
vi
© 2004 SAP AG. All rights reserved.
17-09-2004
Course Overview
In this course, you learn about the time evaluation process and how it is
incorporated in human resources business processes. The focus is on time and
labor data that was recorded as a number of hours, without clock times.
You learn how you can customize time evaluation to suit your requirements.
Target Audience
This course is intended for the following audiences:
•
•
Members of a project team who are implementing R/3 Time Evaluation
SAP consultants and SAP partners who work with R/3 Time Management
Course Prerequisites
Required Knowledge
•
HR306 (Configuration of Time Recording) is a prerequisite.
Recommended Knowledge
•
HR100 (Basics of Personnel Administration) and HR305 (Configuration
of Master Data) are recommended
Course Goals
This course will prepare you to:
•
•
Describe Time Evaluation and its role in the business processes of human
resources
Customize time evaluation to suit your own requirements
Course Objectives
After completing this course, you will be able to:
•
•
•
•
17-09-2004
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
© 2004 SAP AG. All rights reserved.
vii
Course Overview
HR311
•
Customize tables
SAP Software Component Information
The information in this course pertains to the following SAP Software
Components and releases:
•
viii
R/3 6.2
© 2004 SAP AG. All rights reserved.
17-09-2004
Unit 1
Time Evaluation with SAP R/3
Unit Overview
In this unit, you learn the business and technical basics you require to use
time evaluation.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
•
•
•
•
•
Describe time evaluation and its different uses
Describe how time evaluation is integrated in human resources business
processes
Explain the difference between time recording with and without clock
times and the two philosophies of time recording
List the employee master data you require for time evaluation
Illustrate the SAP R/3 technique for determining a workday
Explain the significance of the time management status for time
evaluation
Run time evaluation
Name the periods over which time and labor data can be evaluated
Describe the data required by time evaluation as input
Find out about the results of time evaluation
Unit Contents
Lesson: Business Overview of Time Evaluation ................................... 2
Lesson: Prerequisites for Evaluating Time Data................................... 9
Exercise 1: Basics and Prerequisites for Time Evaluation ................ 17
Lesson: Concept of the Time Evaluation Driver RPTIME00 ................... 24
Exercise 2: Running Time Evaluation ........................................ 37
17-09-2004
© 2004 SAP AG. All rights reserved.
1
Unit 1: Time Evaluation with SAP R/3
HR311
Lesson: Business Overview of Time Evaluation
Lesson Overview
In this lesson, you learn how time evaluation is integrated into human
resources business processes.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Describe time evaluation and its different uses
Describe how time evaluation is integrated in human resources business
processes
Explain the difference between time recording with and without clock
times and the two philosophies of time recording
Business Example
You want to use time evaluation to form wage types to calculate the gross
wage and manage time accounts such as annual working time accounts. You
want to use the results to collate statistics to give detailed information about
how your workforce is being deployed.
2
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Business Overview of Time Evaluation
Business Overview of Time Evaluation
Figure 1: Recording and Evaluating Time Data
With SAP Time Management, you can use various systems and methods for
recording time and labor data, 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
time and labor data and to valuate it 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.
17-09-2004
© 2004 SAP AG. All rights reserved.
3
Unit 1: Time Evaluation with SAP R/3
HR311
Figure 2: Roles for the Time Evaluation Environment
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-MGMTSPECIALIST): The Time Management Specialist is responsible for ensuring
that the time management system runs smoothly. He or she has in-depth
knowledge of 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): 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.
4
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Business Overview of Time Evaluation
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.
Figure 3: Business Transactions Using Time Evaluation
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.
17-09-2004
© 2004 SAP AG. All rights reserved.
5
Unit 1: Time Evaluation with SAP R/3
HR311
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.
Figure 4: In Which Format Should Times Be Recorded?
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.
Time Evaluation provides several standard processing methods, each
responding to specific business requirements.
6
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Business Overview of Time Evaluation
Figure 5: Which Times Should Be Recorded?
There are two different philosophies 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 an 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 set up complex regulations for overtime only if you record
all times.
17-09-2004
© 2004 SAP AG. All rights reserved.
7
Unit 1: Time Evaluation with SAP R/3
HR311
Lesson Summary
You should now be able to:
•
Describe time evaluation and its different uses
•
Describe how time evaluation is integrated in human resources business
processes
•
Explain the difference between time recording with and without clock
times and the two philosophies of time recording
8
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Prerequisites for Evaluating Time Data
Lesson: Prerequisites for Evaluating Time Data
Lesson Overview
In this lesson, you learn about the prerequisites in time data recording and
administration that have to be met before you can run time evaluation for
an employee.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
List the employee master data you require for time evaluation
Illustrate the SAP R/3 technique for determining a workday
Explain the significance of the time management status for time
evaluation
Business Example
In your enterprise, you have employees for whom all attendance times
are recorded and employees for whom only the deviations from the work
schedule are recorded. You want to run time evaluation for all employees.
Prerequisites for Evaluating Time Data
Figure 6: Time Evaluation in the SAP System
17-09-2004
© 2004 SAP AG. All rights reserved.
9
Unit 1: Time Evaluation with SAP R/3
HR311
Figure 7: Overview of the Master Data Infotypes
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:
•
•
10
Use a time recording system
Evaluate time variables from the infotype in time evaluation.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Prerequisites for Evaluating Time Data
Figure 8: Planned Working Time Infotype (0007)
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.
Figure 9: What the Time Management Status Signifies
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.
17-09-2004
© 2004 SAP AG. All rights reserved.
11
Unit 1: Time Evaluation with SAP R/3
HR311
Possible values:
Time Management status:
•
0 = No time evaluation
The employee’s time data is not processed by time evaluation. The time
wage types are formed by Payroll.
•
1 = Evaluation of actual times
All of the employee’s times are recorded.
•
2 = PDC time evaluation
All of the employee’s times are recorded.
•
7 = Time evaluation without Payroll integration
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. The
time wage types are formed by Payroll.
•
9 = Evaluation of planned times
Only deviations to the employee’s work schedule are recorded.
Figure 10: Work Schedule
12
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Prerequisites for Evaluating Time Data
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.
Figure 11: What is a Workday?
17-09-2004
© 2004 SAP AG. All rights reserved.
13
Unit 1: Time Evaluation with SAP R/3
HR311
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.
For more information, see the Implementation Guide for Personnel Time
Management and choose:
•
•
Work Schedules →Define Public Holiday Classes
Work Schedules → Day Types → Define Selection Rules
Figure 12: Overview of Time Management Infotypes
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.
14
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Prerequisites for Evaluating Time Data
For more information about the time management infotypes, see the SAP
Library and choose: Human Resources → Personnel Time Management → Time
Data Recording and Administration → Time Management Infotypes.
Figure 13: Absences and Attendances: Clock Times or Hours?
You can use the HRSIF feature to determine whether time data can be
recorded without clock times, or whether clock times are generated on the
basis of the employee’s personal work schedule for attendances or absences
lasting less than one day.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Data Recording and Administration → Permit
Att./Absences to be Recorded Without Clock Times.
17-09-2004
© 2004 SAP AG. All rights reserved.
15
Unit 1: Time Evaluation with SAP R/3
16
© 2004 SAP AG. All rights reserved.
HR311
17-09-2004
HR311
Lesson: Prerequisites for Evaluating Time Data
Exercise 1: Basics and Prerequisites for
Time Evaluation
Exercise Objectives
After completing this exercise, you will be able to:
•
Hire an employee, whose time and labor data is valuated using time
evaluation
•
Determine whether an employee has to work on a particular day
Business Example
You enter master data and time data for an employee. You want to know
whether and, if so, when the employee has to work on a particular day.
Task 1: Hiring an Employee
Hire an employee and record initial time data for him or her.
1.
Use the personnel action type Time recording (mini-master) to create
personnel number 311101## (## = your group number) for January 1,
20yy (yy = previous year):
Entry date
01/01/20yy
Personnel area
3300
Employee group
1
Employee subgroup
U3 (pay-scale salary)
Work schedule rule
NORM
Time Management status
1
Working week
01 Working week Monday
Time event type grouping
01
Subsystem grouping
001
Grpg. att./absences
001
Grouping for employee
expenditures
001
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
17
Unit 1: Time Evaluation with SAP R/3
HR311
Assign the employee to the default position in the Organizational
Assignment infotype (0001).
This employee participates in time evaluation, and should be assigned
the Time Management status 1 (time evaluation of actual times). The time
recording ID number in the Time Recording Information infotype (0050) is
the same as the personnel number.
2.
Your employee is ill from January 1 through January 6. Record this
absence in the system.
To do so, use the Time Manager’s Workplace. Access the Time Manager’s
Workplace using the profile Z_HR311_TIME_ADM_1. For the time data
IDs, use the definition set SET_HR311 with the definition subset 002.
Task 2:
Getting Information About an Employee’s Planned Working Time
1.
18
Is January 1 a workday for your employee?
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Prerequisites for Evaluating Time Data
Solution 1: Basics and Prerequisites for
Time Evaluation
Task 1: Hiring an Employee
Hire an employee and record initial time data for him or her.
1.
Use the personnel action type Time recording (mini-master) to create
personnel number 311101## (## = your group number) for January 1,
20yy (yy = previous year):
Entry date
01/01/20yy
Personnel area
3300
Employee group
1
Employee subgroup
U3 (pay-scale salary)
Work schedule rule
NORM
Time Management status
1
Working week
01 Working week Monday
Time event type grouping
01
Subsystem grouping
001
Grpg. att./absences
001
Grouping for employee
expenditures
001
Assign the employee to the default position in the Organizational
Assignment infotype (0001).
This employee participates in time evaluation, and should be assigned
the Time Management status 1 (time evaluation of actual times). The time
recording ID number in the Time Recording Information infotype (0050) is
the same as the personnel number.
a)
b)
Hire the employee: Choose in the menu Human Resources →
Personnel Management → Administration → HR Master Data →
Personnel Actions.
Execute the Time Recording (Mini-Master) for the employee.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
19
Unit 1: Time Evaluation with SAP R/3
HR311
Select the Time Recording (Mini-Master) line and enter the following
data:
Personnel number
311101##
From
01/01/20yy (yy = previous year)
Personnel area
3300
Employee group
1
Employee subgroup
U3 (pay-scale salary)
Choose Execute.
c)
Create the Personal Data infotype (0002).
Enter the first and last name of your choice, birth date, and social
security number. Save the data.
d)
Create the Organizational Assignment infotype (0001).
•
Enter personnel subarea 0001.
You want to hire the employee without assigning him or her to
a particular position, so do not enter a position.
•
Save your data.
The Organizational Assignment screen appears.
•
•
Select the No assignment radio button.
Choose Continue.
Your infotype 0001 will now be saved with the default position
number (9999999).
e)
Create the Planned Working Time infotype (0007).
f)
Accept the default work schedule rule NORM.
Select Time Management status 1 - Time Evaluation of
Actual Times.
•
Choose Working week Monday.
•
Save your data.
Create the Time Recording Information infotype (0050).
•
•
•
Enter the time recording ID number 311101## (same as the
personnel number).
Continued on next page
20
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Prerequisites for Evaluating Time Data
•
g)
Accept the defaults for the time event type group, subsystem
grouping, grpg. att./absence, and grouping for EE exp.
•
Save your data.
Skip the Absence Quotas infotype (2006) by choosing Cancel.
We will assign quotas dynamically later in the course.
2.
Your employee is ill from January 1 through January 6. Record this
absence in the system.
To do so, use the Time Manager’s Workplace. Access the Time Manager’s
Workplace using the profile Z_HR311_TIME_ADM_1. For the time data
IDs, use the definition set SET_HR311 with the definition subset 002.
a)
In the menu, choose Human Resources → Time Management →
Administration → Time Manager’s Workplace..
Hint: Before using the Time Manager’s Workplace, you must
choose a profile, a definition set, and a subset.
Choose the profile Z_HR311_TIME_ADM_1, the definition set
SET_HR311, and the definition subset 002.
b)
c)
d)
e)
Choose Execute.
To record time data for your employee, double-click on the name
in the list.
In the calendar area in the upper left-hand screen area, select the
first week of January 20yy. This may include the last few days of
December.
The abbreviation for the employee’s work schedule (NO) is
displayed in the ID column in the Time Data tab page.
Change the NO to ILL (for illness) for January 1 - 6. Save the data.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
21
Unit 1: Time Evaluation with SAP R/3
HR311
Task 2:
Getting Information About an Employee’s Planned Working Time
1.
Is January 1 a workday for your employee?
a)
b)
c)
d)
In the menu, choose Human Resources → Time Management →
Administration → Information System → Report Selection → Work
Schedule → Personal Work Schedule.
Select the Other Period radio button and enter 01/01/20yy.
Enter the personnel number 311101##.
Choose Execute.
January 1 has the day type 1 – Off/paid.The employee does not have
to work on this day.
e)
Alternative solution:
In the Time Manager’s Workplace, information on employees’ planned
working times is displayed for you when you administrate time
and labor data.
•
To do so, select the required day in the Time Data area and
expand the day. Double-click on the time data ID NO.
The Detail area opens.
•
•
22
The Detail screen area displays detailed information about 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.
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.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Prerequisites for Evaluating Time Data
Lesson Summary
You should now be able to:
•
List the employee master data you require for time evaluation
•
Illustrate the SAP R/3 technique for determining a workday
•
Explain the significance of the time management status for time
evaluation
17-09-2004
© 2004 SAP AG. All rights reserved.
23
Unit 1: Time Evaluation with SAP R/3
HR311
Lesson: Concept of the Time Evaluation Driver RPTIME00
Lesson Overview
This lesson gives you an overview of how the time evaluation driver
RPTIME00 works, how it ensures that time and labor data is evaluated
without gaps, and how the data is saved.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
•
Run time evaluation
Name the periods over which time and labor data can be evaluated
Describe the data required by time evaluation as input
Find out about the results of time evaluation
Business Example
You have run time evaluation for an employee. You receive a message during
time evaluation that you cannot explain. You therefore want to analyze the
time evaluation run, correct the error, and run time evaluation again.
24
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Concept of the Time Evaluation Driver RPTIME00
Concept of the Time Evaluation Driver RPTIME00
Figure 14: Evaluating Time Data
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.
Figure 15: Time Evaluation Driver RPTIME00
17-09-2004
© 2004 SAP AG. All rights reserved.
25
Unit 1: Time Evaluation with SAP R/3
HR311
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 time management menu.
26
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Concept of the Time Evaluation Driver RPTIME00
Figure 16: Maintaining the Results of Time Evaluation
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.
Hint: If back-dated changes are made to infotypes, a second evaluation
can be triggered for days that have already been evaluated. This is
controlled by the PDC recalculation field in the Payroll Status infotype
(0003). If a recalculation is performed, RPTIME00 overwrites the
previous results on the database.
17-09-2004
© 2004 SAP AG. All rights reserved.
27
Unit 1: Time Evaluation with SAP R/3
HR311
Figure 17: Data Flow
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.
28
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Concept of the Time Evaluation Driver RPTIME00
Figure 18: Starting RPTIME00: Parameters
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 mode:
Program options Display log and Test run
•
Background processing:
All parameters BLANK except the schema
17-09-2004
© 2004 SAP AG. All rights reserved.
29
Unit 1: Time Evaluation with SAP R/3
HR311
Figure 19: First Day to be Evaluated
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 the Payroll Status infotype (0003).
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.
30
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Concept of the Time Evaluation Driver RPTIME00
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 multiple employees:
You define the date in Customizing. For more information, see the
Implementation Guide for Personnel Time Management and choose:
Time Evaluation → General Settings → Set Modifier for Earliest
Recalculation Date
Time Evaluation → General Settings → Set Earliest Recalculation Date
for Pair Formation/Time Evaluation
The earliest recalculation date for time evaluation specifies the earliest past date
back to which time evaluation can run. This also applies if an employee’s
Personal earliest recalculation date field in the Payroll Status infotype (0003) is
before the value specified in Customizing.
The Personal earliest recalculation data for time evaluation is automatically set
when time evaluation results are archived.
Figure 20: Recalculation Trigger
17-09-2004
© 2004 SAP AG. All rights reserved.
31
Unit 1: Time Evaluation with SAP R/3
HR311
For each infotype, you can determine in the Infotypes view (V_T582A) whether
changes are relevant to a recalculation. 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).
For more information, see the Implementation Guide for Personnel Management
and choose:
•
Personnel Administration → Customize Procedures → Infotypes → Set Up
Infotypes
•
Personnel Administration → Customize Procedures → Infotypes → Define
Fields Relevant for Retroactive Accounting
Figure 21: How Were the Results Achieved?
RPTIME00 generates a log for every time evaluation run. You can control the
scope of the log in the program options for RPTIME00.
32
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Concept of the Time Evaluation Driver 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.
Figure 22: Storing the Results of Time Evaluation
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 time evaluation period is identical for all employees. In the standard
system, it is one month.
17-09-2004
© 2004 SAP AG. All rights reserved.
33
Unit 1: Time Evaluation with SAP R/3
HR311
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
Figure 23: Archiving the Results of Time Evaluation
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.
34
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Concept of the Time Evaluation Driver RPTIME00
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.
For more information about archiving time evaluation results, see the SAP
Library and choose Human Resources → HR Archiving → Archiving Data →
Archiving Payroll Results or Archiving Time Evaluation Results
Figure 24: Overview of Time Evaluation
17-09-2004
© 2004 SAP AG. All rights reserved.
35
Unit 1: Time Evaluation with SAP R/3
36
© 2004 SAP AG. All rights reserved.
HR311
17-09-2004
HR311
Lesson: Concept of the Time Evaluation Driver RPTIME00
Exercise 2: Running Time Evaluation
Exercise Objectives
After completing this exercise, you will be able to:
•
Run time evaluation for an employee
•
Check the results of time evaluation using the time evaluation log
•
Find out about the results of time evaluation using other tools
Business Example
You want to run time evaluation for an employee, check the results, and, if
required, analyze an error situation.
Task 1: Time Evaluation Using RPTIME00
Run time evaluation and check the time evaluation results.
1.
In the Time Manager’s Workplace, record time infotypes (absences and
attendances) for your employee for the whole of January. Use the
employee’s planned specifications as a basis.
Hint: Use only the following attendance/absence types:
•
•
•
Absence type 0200, Illness; time data ID: ILL
Attendance type 0800, Attendance hours; time data ID: AH
Attendance type 0425, Instructor duty; time data ID: INST
2.
Start time evaluation using the program option Display log, and use the
time statement form to check the evaluation results.
3.
What other ways are there of checking the evaluation results?
Task 2:
Recalculation
1.
Check the status of the recalculation date for time evaluation in the
Payroll Status infotype (0003).
2.
In January, the employee also worked an additional 2 hours of instructor
time. Record this backdated attendance.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
37
Unit 1: Time Evaluation with SAP R/3
38
HR311
3.
Look again at the Payroll Status infotype (0003). Which value has
changed?
4.
Run time evaluation again. Check the status of the balances.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Concept of the Time Evaluation Driver RPTIME00
Solution 2: Running Time Evaluation
Task 1: Time Evaluation Using RPTIME00
Run time evaluation and check the time evaluation results.
1.
In the Time Manager’s Workplace, record time infotypes (absences and
attendances) for your employee for the whole of January. Use the
employee’s planned specifications as a basis.
Hint: Use only the following attendance/absence types:
•
•
•
a)
b)
c)
d)
e)
Absence type 0200, Illness; time data ID: ILL
Attendance type 0800, Attendance hours; time data ID: AH
Attendance type 0425, Instructor duty; time data ID: INST
Choose Human Resources → Time Management → Administration →
Time Manager’s Workplace.
Transfer all days in January 20yy (yy = previous year) to the Time
Data area by clicking on the month of January 20yy in the calendar
area.
For the remaining workdays in January, enter the time data IDs
mentioned earlier (ILL, AH, or INST).
When you have filled all the necessary fields, save the data. If there
were any errors, correct them.
Exit the Time Manager’s Workplace.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
39
Unit 1: Time Evaluation with SAP R/3
2.
Start time evaluation using the program option Display log, and use the
time statement form to check the evaluation results.
a)
b)
c)
d)
e)
f)
g)
h)
3.
HR311
In the menu, choose Human Resources → Time Management →
Administration → Time Evaluation → Time Evaluation.
Enter the following data:
•
Personnel number: 311101##
•
Evaluation schema: TM04
•
Evaluation up to: 01/31/20yy
Choose the Program Options button.
Select Display Log.
Double-click the entry or click on the right arrow to transfer it to the
Selected area.
Choose Continue.
Choose Execute.
Check in the log that time evaluation ran without errors. If there
were any errors, correct them.
What other ways are there of checking the evaluation results?
a)
You can view the time evaluation results in the employee’s time
statement. To call up the time statement, choose one of the following
options:
From the time evaluation log, choose Goto → Display Form.
In the menu, choose Human Resources → Time Management →
Administration → Time Evaluation → Time Statement.
•
In the menu, choose Human Resources → Time Management →
Administration → Information System → Report Selection → Time
Accounts → Time Statement.
Alternative solution:
•
•
b)
The report Display Database PCL2 Cluster B2 (RPCLSTB2) provides
a view of all the results of time evaluation for a given period. To
access the report, choose Human Resources → Time Management →
Administration → Tools → Tool Selection → Cluster → Display Time
Evaluation Results (Cluster B2).
Continued on next page
40
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Concept of the Time Evaluation Driver RPTIME00
Task 2:
Recalculation
1.
Check the status of the recalculation date for time evaluation in the
Payroll Status infotype (0003).
a)
b)
c)
d)
2.
In January, the employee also worked an additional 2 hours of instructor
time. Record this backdated attendance.
a)
b)
c)
d)
e)
f)
3.
In the menu, choose Human Resources → Time Management →
Administration → Time Data → Display.
Enter the relevant personnel number.
Choose the Time Management Data tab.
Display the Payroll Results infotype (0003) and make note of the
PDC recalculation date.
In the menu, choose Human Resources → Time Management →
Administration → Time Manager’s Workplace..
In the Time Data area, find a day where you entered AH (Attendance
Hours).
In this line, click on the Expand button in the first column of the
Time Data area.
In the ID column, enter INST under the line AH.
Enter 2 hours in the Duration column.
Save the data and exit the Time Manager’s Workplace.
Look again at the Payroll Status infotype (0003). Which value has
changed?
a)
b)
c)
d)
Choose Human Resources → Time Management → Administration →
Time Data → Display.
Enter the relevant personnel number.
Choose the Time Management Data tab.
Select the Payroll Results infotype (0003). The PDC Recalculation field
has changed to the date on which you entered the new time record.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
41
Unit 1: Time Evaluation with SAP R/3
4.
Run time evaluation again. Check the status of the balances.
b)
In the menu, choose Human Resources → Time Management →
Administration → Time Evaluation → Time Evaluation.
Enter the following data:
c)
d)
e)
f)
g)
h)
•
Personnel number: 311101##
•
Evaluation schema: TM04
•
Evaluation up to: 01/31/20yy
Choose the Program Options button.
Select Display Log.
Double-click the entry and choose Continue.
Choose Execute.
Choose Goto → Execute.
Check that the newly record data is displayed on the time statement.
a)
42
HR311
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Concept of the Time Evaluation Driver RPTIME00
Lesson Summary
You should now be able to:
•
Run time evaluation
•
Name the periods over which time and labor data can be evaluated
•
Describe the data required by time evaluation as input
•
Find out about the results of time evaluation
Related Information
•
17-09-2004
For more information about the concept of time evaluation, see the SAP
Library and choose Human Resources → Personnel Time Management →
Time Evaluation → Time Evaluation Using RPTIME00
© 2004 SAP AG. All rights reserved.
43
Unit Summary
HR311
Unit Summary
You should now be able to:
•
Describe time evaluation and its different uses
•
Describe how time evaluation is integrated in human resources business
processes
•
Explain the difference between time recording with and without clock
times and the two philosophies of time recording
•
List the employee master data you require for time evaluation
•
Illustrate the SAP R/3 technique for determining a workday
•
Explain the significance of the time management status for time
evaluation
•
Run time evaluation
•
Name the periods over which time and labor data can be evaluated
•
Describe the data required by time evaluation as input
•
Find out about the results of time evaluation
44
© 2004 SAP AG. All rights reserved.
17-09-2004
Unit 2
Time Evaluation Messages
Unit Overview
In this unit, you find out how you can process the messages issued during
time evaluation.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
Explain the significance of messages for Time Management
Create customer-specific messages
Structure message processing in the Time Manager’s Workplace
Unit Contents
Lesson: Time Evaluation Messages............................................... 46
Exercise 3: Message Processing in the Time Manager’s Workplace .... 53
17-09-2004
© 2004 SAP AG. All rights reserved.
45
Unit 2: Time Evaluation Messages
HR311
Lesson: Time Evaluation Messages
Lesson Overview
In this lesson, you learn about processing messages in the Time Manager’s
Workplace and customizing message processing.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Explain the significance of messages for Time Management
Create customer-specific messages
Structure message processing in the Time Manager’s Workplace
Business Example
You want to postprocess the messages issued by time evaluation.
You look at the generated messages every day. You process routine, frequently
occurring messages such as missing time postings. In the case of less common
messages, you analyze them using the information provided in the Time
Manager’s Workplace. You enter missing time data or correct errors, and liaise
with employees.
Figure 25: Time Evaluation Messages
46
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation Messages
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 evaluated
Time evaluation checks whether the time data has been entered correctly
and is plausible in relation to 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.
Figure 26: Origin and Categories of Messages
17-09-2004
© 2004 SAP AG. All rights reserved.
47
Unit 2: Time Evaluation Messages
HR311
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.
•
•
•
•
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
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation With Clock Times
or Time Evaluation Without Clock Times → Message Output → Create Message
Descriptions.
You can customize category-1 messages in the Implementation Guide. 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.
Figure 27: Processing Messages in the Time Manager’s Workplace
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.
48
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation Messages
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 Implementation Guide for Personnel Time
Management and choose Time Manager’s Workplace → Basic Settings → Set Up
Message Processing.
Figure 28: Message-Oriented and Employee-Oriented Processing
17-09-2004
© 2004 SAP AG. All rights reserved.
49
Unit 2: Time Evaluation Messages
HR311
Figure 29: Structuring of Message Lists Using Message Functional Areas
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.
Figure 30: Processing method
50
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation Messages
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.
Figure 31: Assigning Processing Methods
17-09-2004
© 2004 SAP AG. All rights reserved.
51
Unit 2: Time Evaluation Messages
HR311
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 grouped 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.
Even if you do not want to output contextual information, you can use
the functional areas to structure the message list. For example, particular
messages would not appear individually in the message list. 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.
52
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation Messages
Exercise 3: Message Processing in the Time
Manager’s Workplace
Exercise Objectives
After completing this exercise, you will be able to:
•
Correct errors using the message processing function
•
Explain the Customizing settings for message processing
Business Example
You want to set up message processing so that the time administrators in your
enterprise can work as efficiently as possible.
Task 1: Message Processing
Your employee is not at work on a workday during the month of February.
He or she is not scheduled to be absent. An absence record has not been
maintained.
1.
In the Time Manager’s Workplace, create the prerequisites to depict this
situation.
2.
Run time evaluation for the employee. Check the log.
3.
Correct the error using the message processing function in the Time
Manager’s Workplace.
Task 2: Customizing 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).
17-09-2004
1.
Which message functional area and processing method is the message
assigned to?
2.
What contextual information is displayed for the message in the Time
Manager’s Workplace?
© 2004 SAP AG. All rights reserved.
53
Unit 2: Time Evaluation Messages
HR311
Solution 3: Message Processing in the Time
Manager’s Workplace
Task 1: Message Processing
Your employee is not at work on a workday during the month of February.
He or she is not scheduled to be absent. An absence record has not been
maintained.
1.
In the Time Manager’s Workplace, create the prerequisites to depict this
situation.
a)
b)
c)
Choose Human Resources → Time Management → Administration →
Time Manager’s Workplace.
Transfer all days in February 20yy (yy = previous year) to the Time
Data area by clicking on the month of February 20yy in the calendar
area.
In the Time Data area, enter time data using the IDs AH, ILL, or
INST for your employee 311101##. Make sure you leave a few days
with no entry.
To enter data for several days at a time, first enter a time data ID for
one day. Double-click on the entry.
The detail area appears at the bottom of the screen, where you can
enter the required attendance or absence period. Some time data
IDs also require you to define the attendance/absence type.
d)
Save the data and exit the Time Manager’s Workplace.
Continued on next page
54
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation Messages
2.
Run time evaluation for the employee. Check the log.
a)
b)
c)
d)
e)
f)
g)
Choose Human Resources → Time Management → Administration →
Time Evaluation → Time Evaluation.
Enter the following data:
Personnel number
311101##
Evaluation schema
TM04
Evaluation up to
02/28/20yy
Choose the Program Options button.
Select Display Log.
Double-click the entry and choose Continue.
Choose Execute.
Review the log and check for messages.
You should receive a yellow error message, Error entry no. 01
Employee not at work.
3.
Correct the error using the message processing function in the Time
Manager’s Workplace.
a)
b)
c)
d)
e)
f)
g)
In the menu, choose Human Resources → Time Management →
Administration → Time Manager’s Workplace..
From the Time Manager’s Workplace, choose Goto → Process Messages.
Choose Employee View.
Select your employee.
Click on the message Employee not at work.
Enter the missing data of your choice (AH, INST, or ILL) and save
your data.
Run time evaluation again for your employee and check the log.
Hint: In the standard system, you can select your employee
in the employee list in the Time Manager’s Workplace and
choose Start Time Evaluation.
However, because the LLREP feature, which determines
the variant used for time evaluation, is not set up with all
variants used in the training courses in the training system,
you have to access time evaluation from the menu.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
55
Unit 2: Time Evaluation Messages
HR311
Task 2: Customizing 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).
1.
Which message functional area and processing method is the message
assigned to?
a)
b)
In the Implementation Guide, choose Personnel Time Management
→ Time Manager’s Workplace → Basic Settings → Set Up Message
Processing → Assign Processing Methods to Message Functional Areas
and Message Types.
Choose Assign Processing Methods to Message Types.
The message type 08 – At work despite day type “1” is assigned to
the message functional area PWS (work schedule deviations) and the
processing method TOVER (Check Overtime Worked).
c)
2.
Return to the IMG.
What contextual information is displayed for the message in the Time
Manager’s Workplace?
a)
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 Check Overtime
Worked processing method (TOVER).
b)
c)
56
Return to the Implementation Guide and choose the Create Groups of
Display Objects activity.
Select the OVER entry, and double-click on Field Customizing. This
view shows that the group contains the display objects Overtime
and Planned hours.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation Messages
Lesson Summary
You should now be able to:
•
Explain the significance of messages for Time Management
•
Create customer-specific messages
•
Structure message processing in the Time Manager’s Workplace
Related Information
For more information, see the SAP Library and choose:
•
•
17-09-2004
Human Resources → Personnel Time Management → Time Evaluation → Day
Processing of Time Data in Time Evaluation → Outputting Messages.
Human Resources → Personnel Time Management → Time Manager’s
Workplace → Message Processing.
© 2004 SAP AG. All rights reserved.
57
Unit Summary
HR311
Unit Summary
You should now be able to:
•
Explain the significance of messages for Time Management
•
Create customer-specific messages
•
Structure message processing in the Time Manager’s Workplace
58
© 2004 SAP AG. All rights reserved.
17-09-2004
Unit 3
Collecting and Processing Time Data
Unit Overview
In this unit, you learn how time evaluation works and its customizing tools,
using the example of data collection.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
•
•
•
•
•
•
Adjust the time evaluation process
Describe the special Customizing features of time evaluation
Explain the interaction between tables, schemas, and personnel
calculation rules
Edit time evaluation schemas and personnel calculation rules
Explain the significance of the time type for time evaluation
Name the functions that are used to import employees’ planned
specifications and their infotypes
Describe how the internal tables in time evaluation work
Describe data collection in time evaluation schema TM04
List the principal operations, and describe what they do
Find detailed information about individual operations
Create a personnel calculation rule
Unit Contents
Lesson: Customizing Time Evaluation ............................................ 61
Exercise 4: Introduction to the Tools Used for Customizing Time Evaluation
..................................................................................... 75
Lesson: Data Collection in Time Evaluation...................................... 78
Exercise 5: Providing Time Data ............................................. 89
Lesson: Operations as Tools of Time Evaluation ................................ 93
Lesson: Creating a Personnel Calculation Rule ................................ 102
17-09-2004
© 2004 SAP AG. All rights reserved.
59
Unit 3: Collecting and Processing Time Data
HR311
Exercise 6: Providing Information from an Employee’s Master Data and
from Customizing Tables ...................................................... 105
60
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Customizing Time Evaluation
Lesson: Customizing Time Evaluation
Lesson Overview
This lesson gives you an overview of the various tools you can use to
customize time evaluation. It introduces you to the central object in time
evaluation, the time type.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
•
•
Adjust the time evaluation process
Describe the special Customizing features of time evaluation
Explain the interaction between tables, schemas, and personnel
calculation rules
Edit time evaluation schemas and personnel calculation rules
Explain the significance of the time type for time evaluation
Business Example
You want to customize time evaluation to suit your enterprise’s specific
requirements by managing customer-specific time accounts.
17-09-2004
© 2004 SAP AG. All rights reserved.
61
Unit 3: Collecting and Processing Time Data
HR311
Customizing Time Evaluation
Figure 32: Implementation Guide for Time Evaluation
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:
•
•
62
Time evaluation with clock times (standard schema TM00)
Time evaluation without clock times (standard schema TM04)
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Customizing Time Evaluation
Figure 33: Customizing Time Evaluation
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.
17-09-2004
© 2004 SAP AG. All rights reserved.
63
Unit 3: Collecting and Processing Time Data
HR311
Figure 34: Steps of Time Evaluation
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).
64
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Customizing Time Evaluation
Figure 35: How Functions and Operations Work
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 the operations to:
•
•
•
Query whether the employee was at work
Query the day type of the day being evaluated
Form time balances
Functions and operations can query values that you have set in time
evaluation views.
17-09-2004
© 2004 SAP AG. All rights reserved.
65
Unit 3: Collecting and Processing Time Data
HR311
Figure 36: Using HR Documentation Maintenance
You can use the PDSY transaction (HR Documentation Maintenance) to access
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 classes
SKON: Symbolic constants
When you maintain schemas and personnel calculation rules, context-sensitive
HR documentation is displayed when you access the field help (F1).
66
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Customizing Time Evaluation
Figure 37: Maintaining Personnel Calculation Schemas
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 Schema.
17-09-2004
© 2004 SAP AG. All rights reserved.
67
Unit 3: Collecting and Processing Time Data
HR311
Figure 38: Layout of the Schema Editor
You can use the schema editor to display, change, and create schemas.
You can use the field help (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:
•
•
68
F1 help from the command line: Documentation for all permitted
commands
F1 help from a line number: Documentation for all permitted line
commands
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Customizing Time Evaluation
Figure 39: Maintaining Personnel Calculation Rules
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 personnel calculation rule 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 user interfaces to edit 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.
17-09-2004
© 2004 SAP AG. All rights reserved.
69
Unit 3: Collecting and Processing Time Data
HR311
Figure 40: Layout of the Rule Editor
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.
For each personnel calculation rule, the length of the variable key must not
exceed 8 characters, inclusive of the spaces necessary between the keys.
If the length of the variable key is insufficient, you can use the PCY operation
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 the GCY operation 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.
70
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Customizing Time Evaluation
Figure 41: Managing Time Accounts
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.
17-09-2004
© 2004 SAP AG. All rights reserved.
71
Unit 3: Collecting and Processing Time Data
HR311
Figure 42: Time types
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.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation Settings → Define
Time Types..
72
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Customizing Time Evaluation
Figure 43: Time Type as Calculation Tool in Time Evaluation
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.
Figure 44: Processing Structure of Time Evaluation
17-09-2004
© 2004 SAP AG. All rights reserved.
73
Unit 3: Collecting and Processing Time Data
HR311
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
74
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Customizing Time Evaluation
Exercise 4: Introduction to the Tools Used
for Customizing Time Evaluation
Exercise Objectives
After completing this exercise, you will be able to:
•
Create a time type
•
Specify the use of a time type
Business Example
In your enterprise, employees receive time off in lieu of particular kinds of
work. You want to collect these times in a time-off account.
You later want to convert these times to an absence quota, so that employees
can take their time off.
Task: Creating a Time Type
Create a time type that you can use to accrue a time-off account.
1.
17-09-2004
In your enterprise, employees can accrue a time-off account. This time-off
account is managed using the time type Z1## (## = your group number).
Create the time type Z1##. The time type should be transferred to the
day totals and to the period totals.
© 2004 SAP AG. All rights reserved.
75
Unit 3: Collecting and Processing Time Data
HR311
Solution 4: Introduction to the Tools Used
for Customizing Time Evaluation
Task: Creating a Time Type
Create a time type that you can use to accrue a time-off account.
1.
In your enterprise, employees can accrue a time-off account. This time-off
account is managed using the time type Z1## (## = your group number).
Create the time type Z1##. The time type should be transferred to the
day totals and to the period totals.
a)
b)
c)
d)
76
To create the time type Z1##, choose the following IMG activity:
Personnel Time Management → Time Evaluation → Time Evaluation
Settings → Define Time Types.
Choose New Entries.
Enter the following data:
PS grouping:
01
Time type
Z1## Time-off account Group ##
Validity period
01/01/20yy to 12/31/9999
Save as day balance:
1 Balance Formation
Cumulate in period balance:
1 Balance Formation
Save your data.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Customizing Time Evaluation
Lesson Summary
You should now be able to:
•
Adjust the time evaluation process
•
Describe the special Customizing features of time evaluation
•
Explain the interaction between tables, schemas, and personnel
calculation rules
•
Edit time evaluation schemas and personnel calculation rules
•
Explain the significance of the time type for time evaluation
Related Information
For more information about the time management infotypes, see the SAP
Library and choose: Human Resources → Personnel Time Management → Time
Evaluation → Time Data Processing in Time Evaluation.
17-09-2004
© 2004 SAP AG. All rights reserved.
77
Unit 3: Collecting and Processing Time Data
HR311
Lesson: Data Collection in Time Evaluation
Lesson Overview
In this lesson, you learn how time evaluation reads employees’ recorded time
data and work schedules so that it can make the data available for further
processing.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Name the functions that are used to import employees’ planned
specifications and their infotypes
Describe how the internal tables in time evaluation work
Describe data collection in time evaluation schema TM04
Business Example
Attendances and absences are recorded for employees. The time data is
loaded into time evaluation, where it is made available for further processing.
78
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Data Collection in Time Evaluation
Data Collection in Time Evaluation
Figure 45: Importing Data
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).
Another function for reading data is A2003. You can use it to take account of
position substitutions that lead to a different payment.
Substitutions that lead to a change in the planned specifications are imported
by the P2000 or P2011 functions.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation With Clock Times or
Time Evaluation Without Clock Times → Providing Time Data.
17-09-2004
© 2004 SAP AG. All rights reserved.
79
Unit 3: Collecting and Processing Time Data
HR311
Figure 46: Function P2000: Importing Daily Work Schedule
The P2000 function is used for the following tasks:
•
Recording work schedule deviations
The P2000 function 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 where actual times are recorded without time recording
devices
If you use the recorded attendances from the Attendances infotype (2002)
as a basis for the valuation of times, the P2000 function places the daily
work schedule in the TZP table. 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 the P2000 function to
generate information on the day. It enters the daily work schedule in the
TZP table and a planned pair in the TIP table.
80
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Data Collection in Time Evaluation
Figure 47: Function P2011: Providing Planned Specifications and Actual Times
You use function P2011 when you upload time events/time postings from
external time recording systems to the R/3 System. The P2011 function
performs two tasks:
•
Importing planned specifications:
The employee’s current daily work schedule is first imported to the
internal table TZP.
•
Providing actual times:
The pairs formed from the time postings are then placed in the internal
table TIP.
If you use the P2011 function in the schema, you require the P2000 function
only if you want to load planned specifications for future days.
17-09-2004
© 2004 SAP AG. All rights reserved.
81
Unit 3: Collecting and Processing Time Data
HR311
Figure 48: Providing Planned Specifications
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.
For more information, see the Implementation Guide for Personnel Time
Management and choose Work Schedules → Daily Work Schedules → Define
Daily Work Schedules.
Figure 49: Filling Internal Table TZP
82
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Data Collection in Time Evaluation
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 the TZP table
is assigned a time identifier, which describes each section of the daily work
schedule.
Time evaluation uses function P2000 or P2011 to import the daily work
schedule, the daily work schedule variant, the day type, the daily work
schedule class, and the planned hours.
Figure 50: Functions P2001 and P2002: Providing Absences and Attendances
The P2001 function generates an entry in the internal table TIP for each
recorded absence (infotype 2001). The P2002 function enters the attendances
from infotype 2002 in the internal table TIP. For full-day absences and
attendances, a time pair is generated according to the planned working times
(planned pair) from the daily work schedule.
Depending on how attendances and absences are recorded and how the
HRSIF feature is set, the clock times are stored in the TIP table.
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.)
17-09-2004
© 2004 SAP AG. All rights reserved.
83
Unit 3: Collecting and Processing Time Data
HR311
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.
So that the TIP table 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 the TIP table:
•
•
•
•
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.
Figure 51: Processing Using Internal Tables
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
84
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Data Collection in Time Evaluation
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.
Hint: For many functions (such as PTIP, PZL, POVT), you have to
use operations (such as COLOP*, ADDZL, ADDDB) in the personnel
calculation rule to ensure that the changed entries are entered in the
internal table again.
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).
The TOP table becomes the new TIP table 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.
For more information, see the SAP Library and choose: Human Resources →
Personnel Time Management → Time Evaluation → Time Data Processing in Time
Evaluation → Processing Using Internal Tables.
17-09-2004
© 2004 SAP AG. All rights reserved.
85
Unit 3: Collecting and Processing Time Data
HR311
Figure 52: Data Collection in Schema TM04
Data collection in the schema follows a set sequence.
You can also run time evaluation for future periods or for periods that end
in the future. Projection 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.
Hint: 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 the IF function 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:
•
•
•
86
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
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Data Collection in Time Evaluation
You can use parameter 2 of functions P2001 and P2002 to determine that
manually recorded attendance and absence records delimit time pairs already
in the TIP table.
Figure 53: Selection Using the Time Management Status
The CHECK function 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 the CHECK function 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.
The CHECK function can be inserted at any point in the schema. The
difference between the use of the CHECK function and the IF function is as
follows:
•
•
You use the CHECK function to set switches that affect the entire time
evaluation run for the employee.
You use the IF function to set conditions so that the processing is carried
out only if the specified condition is met.
For more information, see the SAP Library and choose: Human Resources →
Personnel Time Management → Time Evaluation → Time Data Processing in Time
Evaluation → Using Function CHECK to Select Employees.
17-09-2004
© 2004 SAP AG. All rights reserved.
87
Unit 3: Collecting and Processing Time Data
88
© 2004 SAP AG. All rights reserved.
HR311
17-09-2004
HR311
Lesson: Data Collection in Time Evaluation
Exercise 5: Providing Time Data
Exercise Objectives
After completing this exercise, you will be able to:
•
Read manually recorded time data in accordance with your requirements
for time evaluation
Business Example
In your enterprise, you want to assign bonuses automatically for special kinds
of work.
Task: Assigning Costs for Instructor’s Duties
In your enterprise, times that are spent working as an instructor are
documented. Employees are to receive special bonuses for hours spent
working on instructor’s activities. You want the bonuses to be assigned to
cost center 2200 – Human Resources.
To record times where employees have worked as an instructor, use the time
data ID INST in the Time Manager’s Workplace.
1.
Enter an instructor’s duty with cost assignment for your employee for
the first workday in March.
2.
Copy personnel calculation schema TM04, and name it Z4## (## = your
group number).
3.
Run time evaluation using your schema Z4## for the first workday in
March 20yy (yy = previous year). Check in the time evaluation log how
the attendance that you entered is imported in time evaluation. Check
that the cost center has been correctly assigned to the attendance record.
Hint: You may want to perform a forced recalculation back to the
last workday in February so that you can compare the import of
the attendance record with and without cost assignment.
17-09-2004
© 2004 SAP AG. All rights reserved.
89
Unit 3: Collecting and Processing Time Data
HR311
Solution 5: Providing Time Data
Task: Assigning Costs for Instructor’s Duties
In your enterprise, times that are spent working as an instructor are
documented. Employees are to receive special bonuses for hours spent
working on instructor’s activities. You want the bonuses to be assigned to
cost center 2200 – Human Resources.
To record times where employees have worked as an instructor, use the time
data ID INST in the Time Manager’s Workplace.
1.
Enter an instructor’s duty with cost assignment for your employee for
the first workday in March.
a)
b)
c)
d)
e)
2.
Copy personnel calculation schema TM04, and name it Z4## (## = your
group number).
a)
b)
c)
3.
Choose Human Resources → Time Management → Administration →
Time Manager’s Workplace.
Select the period containing the first workday in March in the
calendar.
In the Time Data area, choose Expand on the first workday in March.
Enter the time data ID INST and the cost center 2200.
Save the data and exit the Time Manager’s Workplace.
In the menu, choose Human Resources → Time Management →
Administration → Tools → Maintain Schemas.
Enter schema TM04 and choose Copy.
In the To Schema field, enter Z4## (## = your group number) and
choose Continue.
Run time evaluation using your schema Z4## for the first workday in
March 20yy (yy = previous year). Check in the time evaluation log how
the attendance that you entered is imported in time evaluation. Check
that the cost center has been correctly assigned to the attendance record.
Hint: You may want to perform a forced recalculation back to the
last workday in February so that you can compare the import of
the attendance record with and without cost assignment.
a)
In the menu, choose Human Resources → Time Management →
Administration → Time Evaluation → Time Evaluation.
Continued on next page
90
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Data Collection in Time Evaluation
b)
c)
Enter the following data:
•
Personnel number: 311101##
•
Evaluation schema: Z4##
•
Forced recalculation as of: Date of last workday in February
•
Evaluation up to: Date of first workday in March
Choose the Program Options button. Double-click on the Display
Log entry and choose Continue.
Hint: At this point, you may want to save your entries as a
variant.
To do so, choose Save.
Name your variant HR311-## and give it a description of
your choice. On future time evaluation runs, you will now
be able to choose a variant that already contains your data.
d)
e)
Choose Execute.
Review the log.
Open the following nodes: First workday in March 20yy → Provide
time data → IF POS → IF NOT SIMF → P2002.
f)
g)
Review the input and the output of this step.
To compare with similar data that does not include cost assignment
information, follow the same path for the last workday in February
20yy.
In both instances, the TIP table contains the time record. Table C1
contains the cost assignment information for the absence on the
first workday in March.
17-09-2004
© 2004 SAP AG. All rights reserved.
91
Unit 3: Collecting and Processing Time Data
HR311
Lesson Summary
You should now be able to:
•
Name the functions that are used to import employees’ planned
specifications and their infotypes
•
Describe how the internal tables in time evaluation work
•
Describe data collection in time evaluation schema TM04
92
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Operations as Tools of Time Evaluation
Lesson: Operations as Tools of Time Evaluation
Lesson Overview
In this lesson, you learn how operations work. You can use operations to
provide important information from master data, Customizing tables, and
so on, and fill internal tables.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
List the principal operations, and describe what they do
Find detailed information about individual operations
Business Example
You want time evaluation to determine whether an employee was scheduled
to work on a day being evaluated.
Figure 54: Time Evaluation Operations
17-09-2004
© 2004 SAP AG. All rights reserved.
93
Unit 3: Collecting and Processing Time Data
HR311
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.
Figure 55: Decision Operations
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.
Hint: 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.
94
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Operations as Tools of Time Evaluation
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.
Figure 56: Operation VARST
The VARST operation 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 the VARST operation to query the status fields. The
documentation for the VARST operation lists all the possible parameters.
17-09-2004
© 2004 SAP AG. All rights reserved.
95
Unit 3: Collecting and Processing Time Data
HR311
Figure 57: Performing Calculations: Operation HRS
The main task of time evaluation is to process and classify time durations. The
Number of hours field is used for calculations.
The HRS operation can be used to fill and change the number of hours field.
Examples of the values that may be used are:
•
Number of hours field of an explicitly determined entry in an internal
table is provided:
–
•
•
Time type zzzz from the SALDO table (period balance table):
HRS=Mzzzz
–
Time type zzzz from the TES table (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 PZL function): HRS=Exxx
–
Current entry from ZML (with POVT function): HRS=Zxxx
Specific number fields:
–
–
•
•
96
From infotypes (for example, HRS=I)
Tables (HRS=T....), table specified previously with the TABLE
operation
Number fields of the values of a constant zzzzz: HRS=Czzzzz
Explicit values: HRS=2.00
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Operations as Tools of Time Evaluation
Figure 58: Examples of Operation HRS
You can also use the HRS operation 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.
Figure 59: Updating Results: Operations ADD*
17-09-2004
© 2004 SAP AG. All rights reserved.
97
Unit 3: Collecting and Processing Time Data
HR311
The ADDDB operation (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:
The ADDZL operation 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:
The ADDOT operation enters the wage types in the overtime wage
types table ZML. The operation can be used only in conjunction with
the POVT function.
Figure 60: Examples of Operation ADDDB
98
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Operations as Tools of Time Evaluation
Figure 61: Issuing Messages: Operation COLER
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 the COLER operation 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.
17-09-2004
© 2004 SAP AG. All rights reserved.
99
Unit 3: Collecting and Processing Time Data
HR311
You determine how time evaluation reacts to the situation in variable 2 of
the COLER operation:
•
•
•
•
100
COLERxx: Time evaluation continues and a note is generated. You can
confirm the message in message processing.
COLERxxF: A recalculation indicator is set so that the day is evaluated
again; time evaluation continues. The day is regarded as having been
evaluated provisionally.
COLERxxE: Time evaluation terminates
COLERxxI: An information message is output. You can confirm the
message in message processing.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Operations as Tools of Time Evaluation
Lesson Summary
You should now be able to:
•
List the principal operations, and describe what they do
•
Find detailed information about individual operations
Related Information
For more information about the topics in this lesson, see the SAP Library and
choose: Human Resources → Personnel Time Management → Time Evaluation →
Time Data Processing in Time Evaluation.
17-09-2004
© 2004 SAP AG. All rights reserved.
101
Unit 3: Collecting and Processing Time Data
HR311
Lesson: Creating a Personnel Calculation Rule
Lesson Overview
In this lesson, you learn how to create a personnel calculation rule. You learn
how to use operations, with the aid of the HR documentation.
Lesson Objectives
After completing this lesson, you will be able to:
•
Create a personnel calculation rule
Business Example
You want time evaluation to determine whether an employee was scheduled
to work on a day being evaluated.
Creating a Personnel Calculation Rule
Figure 62: Exercise: Create a Personnel Calculation Rule
102
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Creating a Personnel Calculation Rule
Figure 63: Decision Tree for Rule Z1##
Figure 64: Personnel Calculation Rule and Schema Entry
17-09-2004
© 2004 SAP AG. All rights reserved.
103
Unit 3: Collecting and Processing Time Data
104
© 2004 SAP AG. All rights reserved.
HR311
17-09-2004
HR311
Lesson: Creating a Personnel Calculation Rule
Exercise 6: Providing Information from
an Employee’s Master Data and from
Customizing Tables
Exercise Objectives
After completing this exercise, you will be able to:
•
Use operations with the aid of the HR documentation
Business Example
You want to use a personnel calculation rule to get information from an
employee’s master data so that you can control further processing.
17-09-2004
© 2004 SAP AG. All rights reserved.
105
Unit 3: Collecting and Processing Time Data
HR311
Task 1: Working with HR Documentation
Use the HR documentation to find out what the following rows of a personnel
calculation rule mean:
a) Choose the PDSY transaction.
b) Choose the documentation class Operation (Time Management).
c) In the Object name field, enter the name of the operation.
d) Choose Display.
1.
What do the following lines of a personnel calculation rule mean?
HRS=PNUM
ADDDB9999
2.
What do the following lines of a personnel calculation rule mean?
HRS-IDAHRS
ADDDB9999Z
Task 2: Creating a Personnel Calculation Rule
Use operations to read values from an employee’s HR master data.
1.
Create (on paper) a personnel calculation rule that enters the planned
working time according to the daily work schedule in time type 9999.
Continued on next page
106
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Creating a Personnel Calculation Rule
Task 3:
Querying Part-Time Work
1.
17-09-2004
Which operation can you use in a personnel calculation rule to query
whether an employee works part-time hours?
© 2004 SAP AG. All rights reserved.
107
Unit 3: Collecting and Processing Time Data
HR311
Solution 6: Providing Information from
an Employee’s Master Data and from
Customizing Tables
Task 1: Working with HR Documentation
Use the HR documentation to find out what the following rows of a personnel
calculation rule mean:
a) Choose the PDSY transaction.
b) Choose the documentation class Operation (Time Management).
c) In the Object name field, enter the name of the operation.
d) Choose Display.
1.
What do the following lines of a personnel calculation rule mean?
HRS=PNUM
ADDDB9999
Answer: Add the number of hours of the current TIP entry to time type
9999 in the TES table.
2.
What do the following lines of a personnel calculation rule mean?
HRS-IDAHRS
ADDDB9999Z
Answer: 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 the TES table to this value.
Task 2: Creating a Personnel Calculation Rule
Use operations to read values from an employee’s HR master data.
1.
Create (on paper) a personnel calculation rule that enters the planned
working time according to the daily work schedule in time type 9999.
Continued on next page
108
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Creating a Personnel Calculation Rule
a)
Enter the planned working time according to the daily work
schedule in time type 9999.
HRS=S
ADDDB9999Z
Task 3:
Querying Part-Time Work
1.
Which operation can you use in a personnel calculation rule to query
whether an employee works part-time hours?
a)
17-09-2004
Operation OUTWP enters values from the work center in the
variable key. You can use the PARTT operand to query whether an
employee works part-time hours.
© 2004 SAP AG. All rights reserved.
109
Unit 3: Collecting and Processing Time Data
HR311
Lesson Summary
You should now be able to:
•
Create a personnel calculation rule
110
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Unit Summary
Unit Summary
You should now be able to:
•
Adjust the time evaluation process
•
Describe the special Customizing features of time evaluation
•
Explain the interaction between tables, schemas, and personnel
calculation rules
•
Edit time evaluation schemas and personnel calculation rules
•
Explain the significance of the time type for time evaluation
•
Name the functions that are used to import employees’ planned
specifications and their infotypes
•
Describe how the internal tables in time evaluation work
•
Describe data collection in time evaluation schema TM04
•
List the principal operations, and describe what they do
•
Find detailed information about individual operations
•
Create a personnel calculation rule
17-09-2004
© 2004 SAP AG. All rights reserved.
111
Unit Summary
112
HR311
© 2004 SAP AG. All rights reserved.
17-09-2004
Unit 4
Personnel Calculation Schema TM04
Unit Overview
In this unit, you learn about the most important processing steps of the TM04
personnel calculation schema in detail.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
17-09-2004
Describe the three main sections in the TM04 schema
Name the processing blocks in day processing
Describe the significance of initialization in the schema
Provide recorded time data for time evaluation
Run error checks
Describe how planned working times are determined
Explain how time types are determined
Process breaks
Reduce absences
Explain the various methods for determining overtime
Describe the process of determining overtime
Describe how the overtime determined is used
Explain the method of using employee and day groupings to represent
your different collective agreement provisions and company agreements
Describe the technical process of time wage type selection
Represent contractual provisions in a time wage type selection rule
Make overtime hours available for remuneration or compensation with
time off
Explain the data flow of time wage types and balances during time
evaluation
Group time types as employees’ time accounts
© 2004 SAP AG. All rights reserved.
113
Unit 4: Personnel Calculation Schema TM04
•
•
•
•
•
HR311
Transfer times to time accounts, wage types, or quotas
Check value limits for time balances and specify appropriate system
responses
Accrue absence entitlements automatically
Make manual changes to absence entitlements that were accrued
automatically
Find information about employees’ absence entitlements
Unit Contents
Lesson: Structure of the TM04 Schema ......................................... 115
Lesson: Providing and Checking Time Data .................................... 121
Exercise 7: Accruing a Time-Off Account .................................. 125
Lesson: Determining Planned Working Times .................................. 135
Lesson: Determining Overtime.................................................... 146
Exercise 8: Determining Overtime ........................................... 153
Lesson: Selecting Time Wage Types ............................................ 162
Exercise 9: Handling Special Times ......................................... 171
Lesson: Compensating Overtime Wage Types ................................. 180
Lesson: Managing Time Accounts................................................ 185
Exercise 10: Managing Time Accounts ..................................... 197
Lesson: Accruing Absence Quotas............................................... 205
Exercise 11: Automatic Accrual of a Time-Off Account ................... 221
114
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Structure of the TM04 Schema
Lesson: Structure of the TM04 Schema
Lesson Overview
In this lesson, you learn how the TM04 schema is structured.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Describe the three main sections in the TM04 schema
Name the processing blocks in day processing
Describe the significance of initialization in the schema
Business Example
Different working time provisions apply to different employees in your
enterprise. You define in the schema the keys you want time evaluation to use
to read the working time provisions defined in the tables for the applicable
employee groupings.
Figure 65: Structure of a Time Evaluation Schema
17-09-2004
© 2004 SAP AG. All rights reserved.
115
Unit 4: Personnel Calculation Schema TM04
HR311
The personnel calculation schema is divided into three blocks. Different
functions are processed in each of these blocks.
•
•
•
Initialization: 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: Day processing (from BDAY – EDAY) is processed once
per employee for each day being evaluated. For example, bonuses are
determined, time accounts managed, working time provisions checked,
on a daily basis.
Final processing: The final processing block (from BEND – EEND)
is processed only once 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.
Figure 66: Structure of Day Processing
116
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Structure of the TM04 Schema
In day processing, time evaluation performs through the following processing
steps, in a set sequence:
•
•
•
•
•
•
•
Importing the day’s actual times from the time infotypes and the planned
specifications from the daily work schedule. It provides the necessary
data from the master data infotypes and the previous evaluation results.
Error checks for the day being evaluated
Determining the employee’s break times and planned working times
Determining whether the employee has worked overtime
Selecting time wage types
Determining how any overtime that exists is to be compensated; that is,
whether it should be remunerated and/or compensated with time off.
Cumulating daily balances and forming time accounts
Figure 67: Structuring in the Schema: Function BLOCK
You can use the BLOCK function to structure the time evaluation log. It does
not have a business-related meaning.
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 BEG parameter in the schema marks the start of a block; the
END parameter, the end of a block.
17-09-2004
© 2004 SAP AG. All rights reserved.
117
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 68: Initialization
Figure 69: Initialization: Setting Employee Groupings (Function MOD)
118
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Structure of the TM04 Schema
Before day processing (initialization block in schema), the MOD function 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, the MOD function calls the
TMON personnel calculation rule.
A personnel calculation subrule is called in the TMON rule 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. The employee subgroup grouping for the personnel calculation
rule in the standard system is not relevant in this case.
You should use the MOD function only in the initialization block, between
BINI and EINI. If the employee has an organizational reassignment, time
evaluation determines the correct table accesses for the appropriate split.
For more information, see the Implementation Guide
•
•
17-09-2004
for Personnel Management and choose Personnel Administration →
Payroll Data → Basic Pay → Define EE Subgroup Grouping for PCR and
Coll.Agrmt.Prov. (collective agreement provisions)
for Personnel Time Management and choose Time Evaluation → Time
Evaluation Without Clock Times → Initial Steps → Define Groupings.
© 2004 SAP AG. All rights reserved.
119
Unit 4: Personnel Calculation Schema TM04
HR311
Lesson Summary
You should now be able to:
•
Describe the three main sections in the TM04 schema
•
Name the processing blocks in day processing
•
Describe the significance of initialization in the schema
120
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Providing and Checking Time Data
Lesson: Providing and Checking Time Data
Lesson Overview
In this lesson, you learn how time evaluation imports the recorded time data
and planned specifications and how it checks that the times are complete
and plausible.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Provide recorded time data for time evaluation
Run error checks
Business Example
In your enterprise, you do not want employees to work on weekends or public
holidays without prior approval. You therefore want time administrators to
be notified immediately if employees have worked on these days.
Providing and Checking Time Data
Figure 70: Providing Time Data
17-09-2004
© 2004 SAP AG. All rights reserved.
121
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 71: Providing Time Data in Schema TM04
The following functions are used to provide time data in TM04:
•
P2000
Import the day’s planned specifications from the daily work schedule to
table TZP.
In the following situations, the system enters a time pair in table TIP:
•
–
Employees with a Time Management status other than 1 or 2
–
Evaluations for future periods
–
Simulations
P2011
Import the day’s planned specifications from the daily work schedule
to table TZP
Import the pairs formed from time postings to table TIP
•
P2001
Imports the absences from the Absences infotype (2001) to the TIP table
•
P2002
Imports the attendances from the Attendances infotype (2002) to the TIP
table
122
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Providing and Checking Time Data
Figure 72: Error checks
Figure 73: Error Checks for Each Day: Rule TE20
17-09-2004
© 2004 SAP AG. All rights reserved.
123
Unit 4: Personnel Calculation Schema TM04
HR311
The TE20 personnel calculation rule 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, an 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).
For technical reasons, the system enters the planned pair in TIP with clock
times. These clock times only affect break processing (see also Function
PBRKS).
If an absence has been recorded on a public holiday, you can use the TE21
personnel calculation rule to define whether this day is evaluated as an
absence or as a public holiday.
The TE20 personnel calculation rule is called using the ACTIO function.
124
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Providing and Checking Time Data
Exercise 7: Accruing a Time-Off Account
Exercise Objectives
After completing this exercise, you will be able to:
•
Create and adjust personnel calculation rules
•
Write time credits to a time account
Business Example
You want to collect your employees’ time credits in a time account. You later
want to convert this time account to an absence entitlement, so that employees
can compensate the times with time off.
Task: Accruing a Time-Off Account
In your enterprise, employees who work as an instructor can accrue a time-off
account.
The employees work their normal planned working hours from the daily work
schedule. On each working day on which the employees carry out instructor’s
duties, they receive a time credit (additional hours). If an employee has an
absence of less than one day, the time credit is halved for that day.
The additional hours are stored in constant ZAH00 in the Payroll Constants
view (V_T511K). The time credit is stored in time type Z1## (## = your
group number). Enter the instructor time using the attendance type 0425 –
Instructor’s duties (time data ID INST).
Hint: The constant ZAH00 has already been created in table T511K.
1.
Create a personnel calculation rule &A## (## = your group number), in
which the time credit is accrued as described above. Make sure that the
time credit is only allocated once per day.
2.
Enter personnel calculation rule &A## in personnel calculation schema
Z4##. You may want to print table TES after running this rule so that you
can see your results immediately.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
125
Unit 4: Personnel Calculation Schema TM04
3.
HR311
Enter a partial-day attendance and a partial-day absence for your
employee on the second workday in March, 20yy (yy = previous year)
so that you can test your personnel calculation rule. Enter regular
attendance hours for your employee for any remaining workdays in
the first full week of March 20yy.
Run time evaluation for March 1 through the last workday of the week
to confirm that your employee received one hour of time-off credit for
the first workday in March and ½ hour of time credit for the second
workday in March.
4.
126
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, see the documentation for operation HRS.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Providing and Checking Time Data
Solution 7: Accruing a Time-Off Account
Task: Accruing a Time-Off Account
In your enterprise, employees who work as an instructor can accrue a time-off
account.
The employees work their normal planned working hours from the daily work
schedule. On each working day on which the employees carry out instructor’s
duties, they receive a time credit (additional hours). If an employee has an
absence of less than one day, the time credit is halved for that day.
The additional hours are stored in constant ZAH00 in the Payroll Constants
view (V_T511K). The time credit is stored in time type Z1## (## = your
group number). Enter the instructor time using the attendance type 0425 –
Instructor’s duties (time data ID INST).
Hint: The constant ZAH00 has already been created in table T511K.
1.
Create a personnel calculation rule &A## (## = your group number), in
which the time credit is accrued as described above. Make sure that the
time credit is only allocated once per day.
a)
In the menu, choose Human Resources → Time Management →
Administration → Tools → Maintain PC Rules.
Figure 74: Personnel Calculation Rule &A00
b)
c)
d)
Enter your rule name, &A##, and choose Create.
Choose Change.
Name your rule, enter program class T and country grouping *.
Save the rule and choose Back to return to the previous screen.
e)
f)
Choose Change.
Place the cursor on the yellow line that includes the name of your
rule and choose Create.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
127
Unit 4: Personnel Calculation Schema TM04
HR311
An open entry box appears in which you can enter an employee
subgroup grouping for the personnel calculation rule.
Enter an asterisk (“*”) and choose ENTER. Another open entry box
appears. Choose ENTER to exit it.
g)
Place your cursor on the line containing the asterisk(*).
Choose Create.
Choose Sub-level.
Enter four asterisks (****) and choose ENTER.
Another open entry box appears. Choose ENTER to exit it.
h)
Place your cursor on the blue line containing the four asterisks.
Choose Create.
Choose Sub-level.
Enter the operation OUTTPPRTYP and choose ENTER. An open
entry box appears on the level below the decision operation.
Enter the series of asterisks as shown above in the diagram of the
personnel calculation rule.
When you have entered the final line containing asterisks (****),
choose ENTER, then enter the attendance type 0425 in the next
open entry box. Choose ENTER twice to open and close the new
entry box.
i)
Place your cursor on the light blue line containing the 0425
attendance type.
Choose Create.
Choose Sub-level.
Enter the operation VARSTABSCE and choose ENTER. An open
entry box appears on the level below the decision operation.
Enter N in the entry box and choose ENTER.
In the next entry box, enter Y and choose ENTER twice to open and
close the new entry box.
j)
Place your cursor on the line containing the N.
Choose Create.
Continued on next page
128
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Providing and Checking Time Data
Choose Sub-level.
Enter the operation HRS=CZAH00 and choose ENTER. An open
entry box appears.
Enter the operation ADDDBZ1##Z and choose ENTER.
In the next box, enter the operation LEAVE.
Choose ENTER twice to open and close the new entry box.
k)
Place your cursor on the line containing the Y.
Choose Create. Choose Sub-level.
Enter the operation HRS=CZAH00 and choose ENTER. An open
entry box appears.
Enter the operation HRS/2.00 and choose ENTER. An open entry
box appears.
Enter the operation ADDDBZ1##Z and choose ENTER.
In the next box, enter the operation LEAVE.
Choose ENTER twice to open and close the new entry box.
l)
Choose Check to run a syntax check, then save your personnel
calculation rule. Return to the Personnel Calculation Rules: Initial
Screen.
m) Check your personnel calculation rule in the table display. Choose
Table Display, then Display. Your personnel calculation rule should
appear as follows:
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
129
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 75: Display Rule: &A## EE subgroup grouping * Wage/time
type****
Hint: Operation HRS=CZAH00 enters the value from
constant ZAH00 from the Payroll Constants view (V_T511K)
in the current number of hours field.
View V_T511K (Payroll constants)
Figure 76: View T511K (Payroll Constants)
To prevent the time credit from being assigned more than
once if, for example, there are several attendance records
for each day, the control indicator Z is used in operation
ADDDB.
In this example, you will attain better system performance
if you use the LEAVE operation. This operation ends
processing of the personnel calculation rule once the value
has been determined.
Continued on next page
130
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Providing and Checking Time Data
2.
Enter personnel calculation rule &A## in personnel calculation schema
Z4##. You may want to print table TES after running this rule so that you
can see your results immediately.
a)
b)
c)
In the menu, choose Human Resources → Time Management →
Administration → Tools → Maintain Schemas.
Enter your schema name, Z4##, and choose Change.
Insert the personnel calculation rule in the schema.
Hint:
•
•
You are advised to enter the personnel calculation
rule &A## after Error checks for specific days (personnel
calculation rule TE20), since you can change the daily
work schedule here, if necessary.
Insert a PRINT TES so that you can track whether table
TES is filled.
To do so, enter I2 in the Line field at the ACTIO TE20 function and
choose ENTER. Insert the two additional functions in the schema
as outlined below.
Figure 77: Schema Entry Z4##
d)
3.
Check the schema and save your data.
Enter a partial-day attendance and a partial-day absence for your
employee on the second workday in March, 20yy (yy = previous year)
so that you can test your personnel calculation rule. Enter regular
attendance hours for your employee for any remaining workdays in
the first full week of March 20yy.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
131
Unit 4: Personnel Calculation Schema TM04
HR311
Run time evaluation for March 1 through the last workday of the week
to confirm that your employee received one hour of time-off credit for
the first workday in March and ½ hour of time credit for the second
workday in March.
a)
b)
In the menu, choose Human Resources → Time Management →
Administration → Time Manager’s Workplace..
Enter time data as follows:
Figure 78: Time Data
c)
Run time evaluation for your employee 311101## from March 1,
20yy through the second workday in March, 20yy.
Hint: (Use the Forced recalculation as of field to start time
evaluation on March 1, 20yy.)
d)
To confirm that your rule functioned properly, review the Error
Checks section of the log on the first workday in March.
Double-click on the log line RTIP &A## GEN to see the processing
of your rule. If you added the line PRINT TES, double-click on this
line to see the value in time type Z1##.
e)
Review the same sections of the log on the second workday in
March to confirm that ½ hour was accrued in time type Z1##.
Continued on next page
132
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Providing and Checking Time Data
4.
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, see the documentation for operation HRS.
a)
b)
Call up the documentation for the HRS operation and branch to the
documentation of the operands.
Go to the documentation of the S indicator (provided from daily work
schedule).
1.
HRS=SADD
Enter the daily additional hours from the daily work schedule
in the current hours field.
In personnel calculation rule &A##, you have to replace each
call of HRS=CZAH00 by HRS=SADD.
17-09-2004
© 2004 SAP AG. All rights reserved.
133
Unit 4: Personnel Calculation Schema TM04
HR311
Lesson Summary
You should now be able to:
•
Provide recorded time data for time evaluation
•
Run error checks
134
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Determining Planned Working Times
Lesson: Determining Planned Working Times
Lesson Overview
In this lesson, you learn how time evaluation determines planned working
times after importing data and running error checks, thereby carrying out
the first step in classifying the times.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
•
Describe how planned working times are determined
Explain how time types are determined
Process breaks
Reduce absences
Business Example
You want time evaluation to determine an employee’s planned working
times and break times so that it can identify any overtime and working time
violations in a subsequent step.
17-09-2004
© 2004 SAP AG. All rights reserved.
135
Unit 4: Personnel Calculation Schema TM04
HR311
Determining Planned Working Times
Figure 79: Determining Planned Working Times
Figure 80: Two Important Objectives of Time Evaluation
136
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Determining Planned Working Times
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 types
The time types and the number of hours of the various TIP entries are
cumulated to form time balances.
•
Processing type
The time wage types are selected according to the processing type.
Example:
Processing type S → planned working time wage types
Processing type M → overtime wage types
Figure 81: Assigning a Time Type and Processing Type
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.
17-09-2004
© 2004 SAP AG. All rights reserved.
137
Unit 4: Personnel Calculation Schema TM04
HR311
The TYPES function 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.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation Without Clock Times
→ Time Data Processing → Assign Time Types and Processing Types.
Figure 82: Structure of View T555Y
In the Processing Type/Time Type According to Abs./Attendance Class view, you
define which time types and processing types the TIP entries are assigned,
based on the pair type:
138
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Determining Planned Working Times
The personnel subarea grouping for time recording is a grouping of personnel
subareas that use the same
•
•
•
•
Time types
Time transfer specifications
Access control groups
Messages
Hint: For more information, see the Implementation Guide for
Personnel Time Management and choose Time Evaluation → Time
Evaluation Settings → Set Personnel Subarea Groupings for Time Recording.
You set the time type determination group in the TMON personnel calculation
rule, using the MODIF T operation. The time type determination group 02
(MODIF T=02) is used in the standard system for time evaluation without clock
times.
Pair types are as follows:
•
•
•
•
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
Hint: SAP R/3 determines the pair type automatically.
You can assign the following processing types as a default for time wage
type formation:
•
•
•
•
•
•
17-09-2004
Processing type S: Pair is included in the daily calculation of planned
time, without a maximum working time per day
Processing type M: Pair is valuated as an overtime pair; the time is not
included in the daily planned working time calculation.
Processing type P: Pair is valuated as an attendance pair, that is, the time
is included in the daily calculation of planned time
Processing type A: Pair is valuated as an absence pair, that is, the time is
included in the daily calculation of planned time
Processing type "-": Pair is deleted at a later stage
Processing type K is relevant for the German country version only. It is
required for determining core night work using the KNTAG function.
© 2004 SAP AG. All rights reserved.
139
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 83: Processing Breaks: Definition of Work Breaks
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.
For more information, see the Implementation Guide for Personnel Time
Management and choose Work Schedules → Daily Work Schedules → Define Break
Schedules.
If you want to evaluate breaks in time evaluation without clock times, you
have to configure the Time Type Determination view (T555Z).
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation With Clock Times →
Time Data Processing → Set Time Type Determination.
140
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Determining Planned Working Times
Figure 84: Evaluating Break Periods: Function PBRKS
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.
17-09-2004
© 2004 SAP AG. All rights reserved.
141
Unit 4: Personnel Calculation Schema TM04
HR311
In time evaluation without clock times, time pairs are entered automatically
in TIP in the following cases:
1.
SAP R/3 generates a planned pair from the daily work schedule in the
following situations:
•
2.
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)
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).
Figure 85: Deducting Attendances and Absences from the Planned Pair
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.
142
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Determining Planned Working Times
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation Without Clock Times
→ Providing Time Data → Deduct Attendances/Absences from Generated Planned
Time Pair.
Figure 86: Reducing Absences: Rule TP10
In the TP10 personnel calculation rule, you can reduce certain partial-day
absences so that they do not increase the flextime balance, that is, the absences
do not exceed the planned specifications.
You specify which absences you want to be reduced by grouping the absences
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 applicable times worked,
for example:
•
•
•
•
Attendances
Paid leave
Sickness with certificate
Overtime
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation Without Clock Times
→ Time Data Processing → Shorten Absences of Less Than One Day.
17-09-2004
© 2004 SAP AG. All rights reserved.
143
Unit 4: Personnel Calculation Schema TM04
144
© 2004 SAP AG. All rights reserved.
HR311
17-09-2004
HR311
Lesson: Determining Planned Working Times
Lesson Summary
You should now be able to:
•
Describe how planned working times are determined
•
Explain how time types are determined
•
Process breaks
•
Reduce absences
17-09-2004
© 2004 SAP AG. All rights reserved.
145
Unit 4: Personnel Calculation Schema TM04
HR311
Lesson: Determining Overtime
Lesson Overview
In this lesson, you learn about the various methods for determining overtime.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Explain the various methods for determining overtime
Describe the process of determining overtime
Describe how the overtime determined is used
Business Example
In your enterprise, you determine overtime on a weekly basis. You want time
evaluation to determine the overtime automatically on the basis of the number
of hours each employee has worked.
Determining Overtime
Figure 87: Determining Overtime
146
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Determining Overtime
Figure 88: Overtime Determination
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 in the Attendances infotype (2002) instead
of being determined automatically in time evaluation. If the attendances meet
the following criteria, they are assigned processing type M in time evaluation:
Hint: The TW10, TW15, and TW30 schemas in the standard SAP
system are compliant with the requirements of the United States FLSA
(Fair Labor Standards Act) for determining overtime.
•
•
17-09-2004
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.
© 2004 SAP AG. All rights reserved.
147
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 89: Determining Overtime on a Daily Basis: Subschema TW15
Subschema TW15 determines overtime on the basis of the hours worked on
each day.
•
Personnel calculation rule TO01 is used to set valid limits on the number
of hours.
In the 0900 time type (Daily overtime after x hours) you define in the rule
the limit after which overtime begins for each day. You can define
different value limits in the decision tree of the PC rule, depending on
the properties of a day. If you do not want overtime analysis to run in
a particular situation (such as on a workday), you set the value limit
to 99.00.
•
Personnel calculation rule TO02 is used to evaluate the daily overtime
limits. Once the limit is reached, the attendance times are assigned
processing type M.
Hint:
•
•
148
In the standard system, absence times are not included when
overtime is determined.
You can also use the TW15 subschema in conjunction with weekly
overtime determination in the TW30 schema.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Determining Overtime
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation Without Clock
Times → Time Data Processing → Determining Overtime → Determine Overtime
According to Days Worked.
Figure 90: Determining Overtime on the Basis of a Working Week: Subschema
TW30
You can use constant OVERT to set a number of hours after which overtime
is calculated.
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 the WWEEK feature.
Alternatively, you can use the TW20 subschema. To use it, the following
conditions must be met: You do not need clock times for the working week
and you only want to define the start day of a 7-day working week for the
whole of your enterprise.
Hint:
•
•
17-09-2004
Note: In the standard system, absence times are not included
when overtime is determined.
If you use subschema TW20, the assignment for individual
employees in the Planned Working Time infotype (0007) is no
longer used.
© 2004 SAP AG. All rights reserved.
149
Unit 4: Personnel Calculation Schema TM04
HR311
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation Without Clock
Times → Time Data Processing → Determining Overtime → Determine Overtime
According to the Working Week.
Figure 91: Schema TW30: Working Week With and Without Clock Times
You can define the working week with or without clock times, however you
can only evaluate a working week with clock times if you record employees’
time data with clock times.
Different bases are used for calculating overtime depending on whether you
define the working week with or without clock times:
•
With clock times:
Only times that lie within the specified time frame are included in the
overtime calculation.
•
Without clock times:
All times whose start time lies within the working week are included in
the calculation of overtime.
150
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Determining Overtime
Figure 92: Schema TW30: 9x80 Flex Schedule
To represent the working time model 9x80 Flex Schedule, the working week
is defined over a period of 7 days.
9x80 Flex Schedule means that an employee works 36 hours in one week and
44 hours the next. In order to calculate overtime using a constant number of
hours, the start of the working week is set to Friday at 12:00 (midday).
Figure 93: Significance of the Processing Type and the Time Type
17-09-2004
© 2004 SAP AG. All rights reserved.
151
Unit 4: Personnel Calculation Schema TM04
HR311
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:
•
•
152
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 the ZL table at the end of time evaluation.
Table ZL acts as the interface to R/3 Payroll.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Determining Overtime
Exercise 8: Determining Overtime
Exercise Objectives
After completing this exercise, you will be able to:
•
Determine overtime
•
Run a combination of daily and weekly overtime analysis
Business Example
In your enterprise, you want to determine overtime on a weekly basis.
However, at peak times, you want employees to be credited for overtime that
they work on particularly intensive days, regardless of the weekly overtime
analysis.
Task: Determining Overtime on a Weekly and Daily Basis
In your enterprise, you use the following combination of daily and weekly
overtime determination:
All working times that exceed 40 working hours per working week are treated
as overtime.
If an employee works more than 10 hours on any one workday, all hours that
exceed the 10 hours are treated as overtime.
Represent these overtime determination provisions in your time evaluation
schema Z4##. The weekly overtime regulation is covered by subschema TW30.
The overtime regulation described requires you to modify subschema TW15.
1.
Copy personnel calculation rule TO01, and name it &B## (## = your
group number). Modify &B##.
2.
Copy subschema TW15, and name it Z5## (## = your group number).
Insert your personnel calculation rule &B##.
3.
Check that subschema TW30 is present in your personnel calculation
schema Z4##. Insert subschema Z5## in schema Z4##. It should come
before subschema TW30.
4.
Enter time data for your employee as follows for the second full week of
March 20yy. Run time evaluation using your schema. Check the results
in the time evaluation log.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
153
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 94: Time Data
5.
Change the time data for your employee as follows and run time
evaluation through the Friday for which you entered time data. Review
your results and note the changes.
Figure 95:
154
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Determining Overtime
Solution 8: Determining Overtime
Task: Determining Overtime on a Weekly and Daily Basis
In your enterprise, you use the following combination of daily and weekly
overtime determination:
All working times that exceed 40 working hours per working week are treated
as overtime.
If an employee works more than 10 hours on any one workday, all hours that
exceed the 10 hours are treated as overtime.
Represent these overtime determination provisions in your time evaluation
schema Z4##. The weekly overtime regulation is covered by subschema TW30.
The overtime regulation described requires you to modify subschema TW15.
1.
Copy personnel calculation rule TO01, and name it &B## (## = your
group number). Modify &B##.
a)
b)
c)
d)
e)
In the menu, choose Human Resources → Time Management →
Administration → Tools → Maintain PC Rules.
Enter the personnel calculation rule TO01 and choose Copy.
Enter your rule name &B## in the To Rule field, and choose Continue.
Your rule is now the active rule to be edited.
Choose Change.
In the structural graphic rule editor, open the following path and
change the final operation to match that shown (the change is in
bold): Employee subgroup grouping for personnel calculation rule * →
Wage/Time Type **** → VARSTDAYTY → 0 → VARSTFREE →
N HRS=10.00.
Hint: To change the operation HRS=99.00 to HRS=10.00,
place the cursor on the line to be changed and choose Change
Entry. After typing your change and without relocating
your cursor, choose ENTER.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
155
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 96: Personnel Calculation Rule &B00
Figure 97: Time Data
Figure 98: Display Rule: &B## EE subgroup grouping * Wage/time
type ****
Continued on next page
156
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Determining Overtime
2.
Copy subschema TW15, and name it Z5## (## = your group number).
Insert your personnel calculation rule &B##.
a)
b)
c)
d)
e)
In the menu, choose Human Resources → Time Management →
Administration → Tools → Maintain Schemas.
Enter the schema TW15 and choose Copy.
Enter your rule name Z5## in the To Schema field, and choose
Continue. Your schema is now the active schema to be edited.
Choose Change.
Replicate the line ACTIO TO01 by entering an R in the Line field
and choosing ENTER: Deactivate one of the ACTIO TO01 lines by
entering an asterisk (*) in the “D” column. Replace TO01 with your
rule &B## in the active line. Save your subschema. Return to the
schema main editor screen.
Figure 99: Schema Z5##
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
157
Unit 4: Personnel Calculation Schema TM04
3.
HR311
Check that subschema TW30 is present in your personnel calculation
schema Z4##. Insert subschema Z5## in schema Z4##. It should come
before subschema TW30.
a)
b)
Access the Z4## schema in change mode.
Modify your schema Z4## to read as follows in the Determine
Overtime block:
Figure 100: Schema Entry Z4##
c)
d)
4.
Use the line replication method from to enter your subschema Z5##
in your schema.
Save your schema.
Enter time data for your employee as follows for the second full week of
March 20yy. Run time evaluation using your schema. Check the results
in the time evaluation log.
Continued on next page
158
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Determining Overtime
Figure 101: Time Data
a)
b)
In the menu, choose Human Resources → Time Management →
Administration → Time Manager’s Workplace.
Enter time data for your employee:
In the calendar, select the second working week in March.
Enter the time data as specified.
Save the data and exit the Time Manager’s Workplace.
c)
d)
In the menu, choose Human Resources → Time Management →
Administration → Time Evaluation → Time Evaluation.
Choose Get Variant and choose your variant. Enter the appropriate
date in the Evaluation up to field. Remove the date in the Forced
Recalculation as of field, if necessary.
Execute the program.
e)
f)
Review the results in the log by following the path: (Tuesday date)
→ Determine Overtime → PTIP TO02 GEN → Output. Confirm the
change in processing type for all hours worked beyond 10 hours
within the day.
Review the log section for the Friday date: Choose Determine
Overtime → Overtime Calculation after x hours/week → IF WW → ELSE
→ PTIP TW35 GEN → Output. The time entered on Friday will not
be converted to processing type M.
Times that are recognized as overtime in the daily overtime
determination (that is, in schema Z5##) are not used in the weekly
overtime analysis, since they are already assigned processing type
M.
5.
Change the time data for your employee as follows and run time
evaluation through the Friday for which you entered time data. Review
your results and note the changes.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
159
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 102:
a)
Change your employee’s time data and check the log again as
described above. Note the changes to the processing of time data on
Friday of the second full working week in March.
All hours over and above 40 hours per week are now recognized
as overtime, not including those which were previously assigned
processing type M in daily overtime determination.
160
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Determining Overtime
Lesson Summary
You should now be able to:
•
Explain the various methods for determining overtime
•
Describe the process of determining overtime
•
Describe how the overtime determined is used
17-09-2004
© 2004 SAP AG. All rights reserved.
161
Unit 4: Personnel Calculation Schema TM04
HR311
Lesson: Selecting Time Wage Types
Lesson Overview
In this lesson, you learn how time evaluation forms time wage types. You
also learn how you can represent in SAP R/3 agreements relating to the
remuneration of work that are specified in the employment contract.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Explain the method of using employee and day groupings to represent
your different collective agreement provisions and company agreements
Describe the technical process of time wage type selection
Represent contractual provisions in a time wage type selection rule
Business Example
In your enterprise, you want to form time wage types for work carried out by
hourly-wage earners during their planned working time. The time wage types
are subsequently valuated in Payroll.
No wage types have to be created for salaried employees’ work during the
planned working time. They receive a fixed salary each month.
162
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Selecting Time Wage Types
Selecting Time Wage Types
Figure 103: Selecting Time Wage Types
Figure 104: Time Wage Type Selection
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.
17-09-2004
© 2004 SAP AG. All rights reserved.
163
Unit 4: Personnel Calculation Schema TM04
HR311
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. This enables SAP R/3 to access the overtime wage types more quickly
in subsequent processing. You specify in parameter 3 of the GWT function
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.
Figure 105: Time wage type selection rule group
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.
164
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Selecting Time Wage Types
In personnel calculation rule TMON, 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 TMON is accessed via function MOD. It is in the initialization block in
the schema.
You can use a personnel calculation rule and the MODIF W operation 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).
Figure 106: Time Wage Type Selection: Function DAYMO
The DAYMO function 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.
Hint: You can specify conditions for the day being evaluated in
individual rules in Customizing. For a better system performance,
however, you may prefer to use the DAYMO function to specify the
conditions for the day.
If the four day categories are not sufficient for your purposes, you can also
set the day grouping in a personnel calculation rule using the MODIF D=xx
operation.
17-09-2004
© 2004 SAP AG. All rights reserved.
165
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 107: Principle of the Rule Group: An Example from Time Wage Type
Selection
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 the following 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.
Hint: 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.
166
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Selecting Time Wage Types
Figure 108: Time Wage Type Selection: Structure of a Rule (1)
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 select a particular number of wage types,
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 time wage type selection if a particular time wage type is selected. The
remaining sequence numbers are no longer processed in this case.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation Without Clock Times
→ Time Wage Type Selection and Overtime Compensation → Define Generation
Rules.
17-09-2004
© 2004 SAP AG. All rights reserved.
167
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 109: Time Wage Type Selection: Structure of a Rule (2)
If you want the wage type to be selected only 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).
Hint: The way the clock time is written is important:
A clock time such as 24:00 to 30:00 indicates a night shift that started
on the previous day.
A clock time such as 00:00 to 06:00 indicates working time that is to
be evaluated for the current day.
If a TIP entry lies only partially within the interval, the wage type is generated
only for the period within the interval.
168
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Selecting Time Wage Types
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 want the wage type to be selected only 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 want the wage type to be generated
only 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.
Figure 110: Selecting Time Types: Function GWT
17-09-2004
© 2004 SAP AG. All rights reserved.
169
Unit 4: Personnel Calculation Schema TM04
HR311
The GWT function 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 type selection 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
TIP entries with processing type M are processed in time wage type
selection for overtime. For each time wage type selection rule for
overtime wage types, the system checks which TIP entries observe the
rule. If the rule is observed, the relevant wage type is entered in internal
table ZML.
The GWT function 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).
Valuation according to the “as if” principle can be carried out for absences
•
•
Whose processing type was changed to S
Whose processing type remained A and which are evaluated using the
GWT A function
For more information, see:
170
•
The Implementation Guide for Personnel Time Management and choose
Time Evaluation → Time Evaluation Without Clock Times → Time Wage Type
Selection and Overtime Compensation → Define Generation Rules.
•
The SAP Library and choose Human Resources → Payroll → Payroll
<country xx> → Gross → Time Management Aspects in Payroll → Absences.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Selecting Time Wage Types
Exercise 9: Handling Special Times
Exercise Objectives
After completing this exercise, you will be able to:
•
Specify special processing for time wage type selection in Customizing
•
Create a time wage type selection rule
•
Assign a processing type to a time
Business Example
In your enterprise, you want to pay special bonuses for particular activities.
You want this to be processed automatically in time evaluation without having
to enter information about the bonuses online.
Task: Handling Special Times
In your enterprise, employees receive special bonuses for hours they have
worked as an instructor. The cost center 2200 – Human Resources is debited
with these bonuses.
To record times where employees have worked as an instructor, use the
attendance type 0425 - Instructor’s duty (time data ID INST) in the Time
Manager’s Workplace.You can also carry out cost assignment at this stage.
On working days, the wage type MQ10 – Overtime bonus 25% is selected for
these times in time wage type selection.
1.
The easiest way to represent these requirements is to assign a special
processing type for the times. Processing type Z – Instructor’s attendance
has been defined for you for this purpose.
Check the setting in Customizing.
2.
In the IMG activity Define Generation Rules, verify that a time wage type
selection rule exists for processing type Z which selects the wage type MQ10
irrespective of the day being evaluated. There is already a time wage type
selection rule in Customizing that fulfils these criteria. It is selected by the
DAYMO function only on workdays.
3.
Create a personnel calculation rule &C## (## = your group number). It is
used to assign processing type Z to TIP entries that have been generated
according to attendances with the attendance type 0425 and that are not
within a work break.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
171
Unit 4: Personnel Calculation Schema TM04
172
HR311
4.
Insert personnel calculation rule &C## into your schema, and add the
time wage type selection for processing type Z. Decide on the best
position for it in the schema.
5.
Add the call of the GWT function for times with processing type Z.
6.
Run time evaluation using a forced recalculation to March 01, 20yy.
Review the results for the first workday in March, 20yy to confirm that
wage type MQ10 was selected for your employee for the attendance type
0425 – attendance hours.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Selecting Time Wage Types
Solution 9: Handling Special Times
Task: Handling Special Times
In your enterprise, employees receive special bonuses for hours they have
worked as an instructor. The cost center 2200 – Human Resources is debited
with these bonuses.
To record times where employees have worked as an instructor, use the
attendance type 0425 - Instructor’s duty (time data ID INST) in the Time
Manager’s Workplace.You can also carry out cost assignment at this stage.
On working days, the wage type MQ10 – Overtime bonus 25% is selected for
these times in time wage type selection.
1.
The easiest way to represent these requirements is to assign a special
processing type for the times. Processing type Z – Instructor’s attendance
has been defined for you for this purpose.
Check the setting in Customizing.
a)
In the IMG, choose Personnel Time Management → Time Evaluation →
Time Evaluation Without Clock Times → Time Wage Type Selection and
Overtime Compensation → Define Processing Types.
The processing type Z – Instructor’s attendance has been defined
for you.
Hint: The processing types Y, Z, and special characters are
available for customer names.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
173
Unit 4: Personnel Calculation Schema TM04
2.
HR311
In the IMG activity Define Generation Rules, verify that a time wage type
selection rule exists for processing type Z which selects the wage type MQ10
irrespective of the day being evaluated. There is already a time wage type
selection rule in Customizing that fulfils these criteria. It is selected by the
DAYMO function only on workdays.
a)
b)
c)
In the Implementation Guide, choose Personnel Time Management →
Time Evaluation → Time Evaluation Without Clock Times → Time Wage
Type Selection and Overtime Compensation → Define Generation Rules.
Select the Define Generation Rules activity.
Make sure that there is an entry for the wage type MQ10 with the
time wage type selection rule group 02 and the day grouping for time
wage types selection 01.
Hint: To find the entries quickly, choose the Positioning
button.
d)
3.
Double-click on the entry to view the details of the time wage type
selection rule.
Create a personnel calculation rule &C## (## = your group number). It is
used to assign processing type Z to TIP entries that have been generated
according to attendances with the attendance type 0425 and that are not
within a work break.
a)
b)
c)
In the menu, choose Human Resources → Time Management →
Administration → Tools → Maintain PC Rules.
Enter your rule name, &C##, and choose Create.
The tree display of the personnel calculation rule is shown below:
Figure 111: Personnel Calculation Rule &C00
d)
e)
Name your rule, enter program class T and country grouping *.
Save the rule and choose Back to return to the previous screen.
Choose Change.
Continued on next page
174
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Selecting Time Wage Types
f)
Place the cursor on the yellow line that includes the name of your
rule and choose Create.
An open entry box appears in which you can enter an employee
subgroup grouping for the personnel calculation rule.
Enter an asterisk (“*”) and choose ENTER. Another open entry box
appears. Choose ENTER to exit it.
g)
Place your cursor on the line containing the asterisk(*).
Choose Create.
Choose Sub-level.
Enter four asterisks (****) and choose ENTER. Another open entry
box appears.
Choose ENTER to exit it.
h)
Place your cursor on the blue line containing the four asterisks.
Choose Create.
Choose Sub-level.
Enter the operation OUTTPPRTYP and choose ENTER. An open
entry box appears on the level below the decision operation.
Enter the series of asterisks as shown above in the diagram of the
personnel calculation rule.
When you have entered the final line containing asterisks (****),
choose ENTER, then enter the attendance type 0425 in the next
open entry box.
Choose ENTER twice to open and close the new entry box.
i)
Place your cursor on the light blue line containing the asterisk(*).
Choose Create.
Choose Sub-level.
Enter the operation COLOP*.
Choose ENTER twice to open and close the new entry box.
Repeat this process for the lines containing two, three, and four
asterisks.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
175
Unit 4: Personnel Calculation Schema TM04
j)
HR311
Place your cursor on the light blue line containing the 0425
attendance type.
Choose Create.
Choose Sub-level.
Enter the operation OUTTPVTYPE and choose ENTER. An open
entry box appears on the level below the decision operation.
Enter * in the first entry box and choose ENTER.
Enter K in the next entry box and choose ENTER twice to open and
close the next entry box.
k)
Place your cursor on the line containing the asterisk(*).
Choose Create.
Choose Sub-level.
Enter the operation FILLPVZ and choose ENTER.
Enter the operation COLOP* and choose ENTER twice to open and
close the next entry box.
l)
Place your cursor on the line containing the K.
Choose Create.
Choose Sub-level.
Enter the operation COLOP* and choose ENTER twice to open and
close the next entry box.
m) Choose Check to run a syntax check. Return to the Personnel
Calculation Rules: Initial Screen.
n) Check your personnel calculation rule in the table display. Choose
Table Display, then Display. Your personnel calculation rule should
appear as follows:
Continued on next page
176
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Selecting Time Wage Types
Figure 112: Display Rule__&C##__EE Subgrp Grpg *__W/TTYPE_****
4.
Insert personnel calculation rule &C## into your schema, and add the
time wage type selection for processing type Z. Decide on the best
position for it in the schema.
a)
b)
c)
In the menu, choose Human Resources → Time Management →
Administration → Tools → Maintain Schemas.
Enter your schema name, Z4##, and choose Change.
It is recommended that you enter the new personnel calculation rule
&C## after the selection of processing type M wage types (function
GWT M). This enables the processed attendance times also to be
included in the overtime compensation.
Use the function PTIP to call rule ZC##. Insert the rows in the
schema as outlined below.
To insert the lines in the schema, enter I2 in the line number of the
line after which you want to insert your new entries.
5.
Add the call of the GWT function for times with processing type Z.
a)
Add the call of function GWT Z DZL to your schema as follows:
Figure 113: Schema Entry Z4##
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
177
Unit 4: Personnel Calculation Schema TM04
6.
HR311
Run time evaluation using a forced recalculation to March 01, 20yy.
Review the results for the first workday in March, 20yy to confirm that
wage type MQ10 was selected for your employee for the attendance type
0425 – attendance hours.
a)
b)
In the menu, choose Human Resources → Time Management →
Administration → Time Evaluation → Time Evaluation.
Choose Get Variant and choose your variant.
Enter the date of the Friday of the second full working week in
March in the Evaluation up to field.
Enter 03/01/20yy in the Forced recalculation as of field.
Execute the program.
c)
Review the results for the first workday in March, 20yy to confirm
that wage type MQ10 was selected for your employee for the
attendance type 0425 – attendance hours.
In the log, review the path: (First workday in March) → Select time
wage types → PTIP &C## GEN.
Review the input, processing, and output of this rule to confirm that
the processing type for the hours worked was changed to Z. Break
times should still have processing type K.
Review the next step in the log, GWT Z DZL.
Confirm the selection of wage type MQ10 for all hours holding
processing type Z.
178
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Selecting Time Wage Types
Lesson Summary
You should now be able to:
•
Explain the method of using employee and day groupings to represent
your different collective agreement provisions and company agreements
•
Describe the technical process of time wage type selection
•
Represent contractual provisions in a time wage type selection rule
17-09-2004
© 2004 SAP AG. All rights reserved.
179
Unit 4: Personnel Calculation Schema TM04
HR311
Lesson: Compensating Overtime Wage Types
Lesson Overview
In this lesson, you learn how to make the overtime available for remuneration
and/or compensation with time off.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Make overtime hours available for remuneration or compensation with
time off
Explain the data flow of time wage types and balances during time
evaluation
Business Example
In your enterprise, employees receive the agreed bonuses for overtime they
work. Employees can take time off in lieu of overtime hours they work.
Compensating Overtime Wage Types
Figure 114: Compensating Overtime Wage Types
180
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Compensating Overtime Wage Types
Figure 115: Overtime Compensation
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 Attendances infotype (2002) to control
overtime compensation for individual employees and periods.
17-09-2004
© 2004 SAP AG. All rights reserved.
181
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 116: Compensating Overtime Wage Types
The POVT function processes the overtime wage types consecutively in the
specified personnel calculation rule. Processing class 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 the TC40 personnel calculation rule, 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).
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation Without Clock Times
→ Time Wage Type Selection and Overtime Compensation → Compensate Overtime.
182
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Compensating Overtime Wage Types
Figure 117: Data Flow: Time Wage Types and Balances
Balances and time wage types can also be formed or changed in personnel
calculation rules:
•
•
17-09-2004
Time wage types using the ADDZL/ADDOT operation
Balances using the ADDDB operation
© 2004 SAP AG. All rights reserved.
183
Unit 4: Personnel Calculation Schema TM04
HR311
Lesson Summary
You should now be able to:
•
Make overtime hours available for remuneration or compensation with
time off
•
Explain the data flow of time wage types and balances during time
evaluation
184
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Managing Time Accounts
Lesson: Managing Time Accounts
Lesson Overview
This lesson provides an introduction to the various methods you can use to
manage time accounts in time evaluation.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Group time types as employees’ time accounts
Transfer times to time accounts, wage types, or quotas
Check value limits for time balances and specify appropriate system
responses
Business Example
In your enterprise, you want to set up time accounts to:
•
•
•
17-09-2004
Collate statistics for important key figures such as overtime levels,
productivity rates, or absence rates
Check that working time provisions have been observed
Transfer times between time accounts, for example, converting hours
worked into time-off entitlements
© 2004 SAP AG. All rights reserved.
185
Unit 4: Personnel Calculation Schema TM04
HR311
Managing Time Accounts
Figure 118: Managing Time Accounts
Figure 119: Balance Formation: Rule TR11
186
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Managing Time Accounts
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 the TES table (day balances).
Figure 120: Balance Formation and Time Type Determination (TM04)
The TYPES function assigns a time type to the TIP entries. The TR11 personnel
calculation rule then cumulates the number of hours in the TIP entries in
various comprehensive time types (time balances). You can read the entries in
the Processing Type and Time Type acc. to Attendance/Absence Class (V_T555Y)
view in the following ways:
•
•
17-09-2004
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 relate to employees’ attendance
and absence statuses
© 2004 SAP AG. All rights reserved.
187
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 121: Processing Time Transfer Specifications: Function P2012
Creating a record of the Time Transfer Specifications infotype (2012) allows
you to change the results determined by time evaluation. You can use them
to represent special situations related to individual employees or to ensure
legacy data is transferred (such as the transfer of the flextime balance).
You can use time transfer specifications to transfer hours from a time type,
time wage type or an absence quotas to a:
•
•
•
Time type
Time wage type
Absence quota
You can also set time types to a fixed value.
The P2012 function processes the time transfer specifications for the current
day using tables.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation Without Clock Times
→ Processing Balances → Time Transfer.
188
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Managing Time Accounts
Figure 122: Processing Time Transfer Specifications: Control
The time transfer specifications are processed for each day of the infotype’s
validity period. You would typically create a time transfer specification for a
day.
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.
17-09-2004
© 2004 SAP AG. All rights reserved.
189
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 123: Processing instructions for a day
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. SAP R/3 then saves
a record of the Time Transfer Specifications infotype (2012) in the background.
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 the P2012 function as often as needed in the schema. Enter the
required personnel calculation rules in parameter 1 of the function.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Manager’s Workplace → Basic Settings → Define
Processing Instructions.
190
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Managing Time Accounts
Figure 124: Groups of Processing Instructions
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 a 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
Hint: If you use the calendar views, the checkboxes are not
available. In this case, time administrators have to enter time transfer
specifications directly.
17-09-2004
© 2004 SAP AG. All rights reserved.
191
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 125: Forming Important Balances: Rule TR30
The TR30 personnel calculation rule provides an example of how you can use
arithmetical conversions in a personnel calculation rule to form important day
balances from the balances determined until that point. The TR30 personnel
calculation rule determines the following balances:
•
The flextime balance of the current day
To do so, it subtracts the planned working time according to the daily
work schedule from the skeleton time (planned hours worked).
•
•
Hours of overtime worked
Productive hours
The TR30 personnel calculation rule is important in a business sense. The
results of balance formation are used
•
•
•
•
As a basis for generating absence quotas (QUOTA function)
To check working time regulations
To display on the employee’s time statement
To compile statistics such as overtime levels, productive times, absence
times
You can add any additional time accounts to the standard processing.
192
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Managing Time Accounts
Figure 126: Value Limits for Time Balances: Function LIMIT
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
Outputting messages. You can also use messages as a warning if a time
account is at risk of going above or below a value limit.
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
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation Without Clock Times
→ Processing Balances → Balance Formation → Balance Limits.
17-09-2004
© 2004 SAP AG. All rights reserved.
193
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 127: Defining Value Limits for Time Balances
The LIMIT function 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. The LIMIT function 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.
194
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Managing Time Accounts
You can also use the LIMIT function 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 the MODIF operation to reset the
original time balance rule group after this processing block.
Figure 128: Updating Results: Function CUMBT
The CUMBT function 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 the CUMBT
function (without additional control) from the DZL table to the ZL table.
17-09-2004
© 2004 SAP AG. All rights reserved.
195
Unit 4: Personnel Calculation Schema TM04
HR311
Tables ZES, SALDO and ZL are tables from Cluster B2 in file PCL2.
Hint: After the CUMBT function, there must be no more functions
in day processing in the schema that change the day balances in the
TES table and the wage types in the DZL table. These results are no
longer saved.
In order to ensure an error-free recalculation, the SALDO table may
only be filled using the TES table, or in final processing (between
BEND and EEND) at the end of the time evaluation period.
To do so, proceed as follows in final processing:
1.
2.
3.
Use the IF EOM function to query the end of the time evaluation
period.
Use the ADDMB operation in a personnel calculation rule to enter
balances in the SALDO table.
Exit processing with ENDIF.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation Without Clock Times
→ Processing Balances → Balance Formation → Update Cumulated Balances.
196
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Managing Time Accounts
Exercise 10: Managing Time Accounts
Exercise Objectives
After completing this exercise, you will be able to:
•
Transfer times from one time account to another
•
Check employees’ time accounts automatically using value limits
•
Issue messages if times exceed or fall short of value limits
Business Example
In your enterprise, you want to transfer time accounts flexibly from one
to the other.
You want to monitor particular employee time accounts automatically. You
want to do so to ensure that working time provisions and legal regulations are
adhered to.
Task 1: Time Transfers
You want to enable the time data administrator to change the time-off account
Z1## (where ## is your group number) in special situations, such as when
an employee works as an instructor over a weekend. In this case, you want
time-off account Z1## to be increased by an additional time credit, the value of
which is at the time data administrator’s discretion.
1.
Set up the time transfer specification 41## (## = your group number) that
increases the time-off account by the specified number.
2.
Enter the time transfer specification that you have just created for your
employee on the first workday in March. In the Time Manager’s Workplace,
use the generic time data ID T, and specify the time transfer type in the
detail area.
3.
Evaluate the employee’s times, and check the result.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
197
Unit 4: Personnel Calculation Schema TM04
HR311
Task 2: 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.
1.
In your schema Z4##, add a second call of the function LIMIT
immediately following the function LIMIT in the Day Processing section.
Do not deactivate the first call of the LIMIT function. On your new call
of the function LIMIT, set the parameter 2 value to your time balance rule
group 50 + ## (## = group number).
Hint: The LIMIT function is now processed twice in the schema.
In the second call, only the balance rule you created in this
exercise is processed.
2.
Enter the rule for balance formation 900 in the following IMG activity:
Personnel Time Management → Time Evaluation → Time Evaluation Without
Clock Times → Processing Balances → Balance Formation → Balance Limits.
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 employee’s working time falls short of the weekly working hours,
you want a note (message number Z0) to be issued.
198
3.
Enter time data for your employee for the third week of March 20yy. On
at least one day, enter a record for less than 7.5 hours (not a full-day
record). Use attendance type 0800 or 0425 (time data ID AH or INST).
4.
Run time evaluation for your employee through the end of the third
week of March, 20yy, and check whether the message is generated.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Managing Time Accounts
Solution 10: Managing Time Accounts
Task 1: Time Transfers
You want to enable the time data administrator to change the time-off account
Z1## (where ## is your group number) in special situations, such as when
an employee works as an instructor over a weekend. In this case, you want
time-off account Z1## to be increased by an additional time credit, the value of
which is at the time data administrator’s discretion.
1.
Set up the time transfer specification 41## (## = your group number) that
increases the time-off account by the specified number.
a)
b)
In the IMG, choose Personnel Time Management → Time Evaluation →
Time Evaluation Without Clock Times → Processing Balances → Time
Transfer → Define Time Transfer Types.
Choose New Entries and enter the following data:
Figure 129: Defining Time Transfer Types
c)
d)
In the IMG, choose Personnel Time Management → Time Evaluation →
Time Evaluation Without Clock Times → Processing Balances → Time
Transfer → Define Rules for Transfer to Time Types.
Choose New Entries and enter the following data:
Figure 130: Defining Rules for Transfers to Time Types
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
199
Unit 4: Personnel Calculation Schema TM04
2.
HR311
Enter the time transfer specification that you have just created for your
employee on the first workday in March. In the Time Manager’s Workplace,
use the generic time data ID T, and specify the time transfer type in the
detail area.
a)
b)
c)
d)
In the menu, choose Human Resources → Time Management →
Administration → Time Manager’s Workplace..
In the calendar area, select any date in the first two weeks of March,
20yy.
Choose Create details to display the Detail screen area.
Enter T (for transfer) as the time data ID and choose ENTER.
The system issues an error message indicating that you have to
enter a valid time transfer type. Enter your time transfer type (41##)
on the right-hand side and save your data.
e)
3.
Exit the Time Manager’s Workplace.
Evaluate the employee’s times, and check the result.
a)
b)
c)
In the menu, choose Human Resources → Time Management →
Administration → Time Evaluation → Time Evaluation.
Choose Get Variant and choose your variant. Enter the date of Friday
of the second full working week in March in the Evaluation up to
field. Execute the program.
Review the results in the log in the following area: (Date of infotype
record) → Manage Time Accounts → P2012. Review the input and the
output of this step. Your employee should have additional hours
in time type Z1##.
Continued on next page
200
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Managing Time Accounts
Task 2: 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.
1.
In your schema Z4##, add a second call of the function LIMIT
immediately following the function LIMIT in the Day Processing section.
Do not deactivate the first call of the LIMIT function. On your new call
of the function LIMIT, set the parameter 2 value to your time balance rule
group 50 + ## (## = group number).
Hint: The LIMIT function is now processed twice in the schema.
In the second call, only the balance rule you created in this
exercise is processed.
a)
b)
c)
d)
2.
In the menu, choose Human Resources → Time Management →
Administration → Tools → Maintain Schemas.
To do so, enter an i in the row that calls the LIMIT function in day
processing, and choose ENTER.
In the newly created line, enter the function LIMIT and in parameter
2 enter the value 50+## (## = group number).
Save your schema.
Enter the rule for balance formation 900 in the following IMG activity:
Personnel Time Management → Time Evaluation → Time Evaluation Without
Clock Times → Processing Balances → Balance Formation → Balance Limits.
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).
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
201
Unit 4: Personnel Calculation Schema TM04
HR311
If an employee’s working time falls short of the weekly working hours,
you want a note (message number Z0) to be issued.
a)
b)
c)
3.
In the Implementation Guide, choose Personnel Time Management →
Time Evaluation → Time Evaluation Without Clock Times → Processing
Balances → Balance Formation → Balance Limits.
Choose Define Limits for Balance Formation.
Choose New Entries and enter the following data:
PS grouping
01
Time balance rule group
50 + ##
Balance rule
900
Validity period
01/01/20yy - 12/31/9999
Origin indicator of operation HRS
I
Parameter of operation: HRS
WEHRS
Type of value limit
Lower limit
Time type
0003 Skeleton time
Day balance processed over
Period 03 – weekly
Processing in period
Cumulate
Message
Z0
Check point
End of period 03 – weekly
Enter time data for your employee for the third week of March 20yy. On
at least one day, enter a record for less than 7.5 hours (not a full-day
record). Use attendance type 0800 or 0425 (time data ID AH or INST).
a)
b)
In the menu, choose Human Resources → Time Management →
Administration → Time Manager’s Workplace..
Enter the time data for your employee in such a way that you can test
the balance rule. You will want to enter attendances and absences
during the third full week of March 20yy. On one or more days, give
your employee a partial-day record for less than 7.5 hours.
Continued on next page
202
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Managing Time Accounts
4.
Run time evaluation for your employee through the end of the third
week of March, 20yy, and check whether the message is generated.
a)
b)
17-09-2004
In the menu, choose Human Resources → Time Management →
Administration → Time Evaluation → Time Evaluation.
Select your variant and run time evaluation through the end of the
third full week in March, 20yy. Check in the log whether the ZO
message (Weekly working time not reached) was issued under Manage
time accounts → LIMIT (second call).
© 2004 SAP AG. All rights reserved.
203
Unit 4: Personnel Calculation Schema TM04
HR311
Lesson Summary
You should now be able to:
•
Group time types as employees’ time accounts
•
Transfer times to time accounts, wage types, or quotas
•
Check value limits for time balances and specify appropriate system
responses
204
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Accruing Absence Quotas
Lesson: Accruing Absence Quotas
Lesson Overview
In this lesson, you learn how to automatically accrue absence entitlements,
such as leave or time off from overtime, in time evaluation.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Accrue absence entitlements automatically
Make manual changes to absence entitlements that were accrued
automatically
Find information about employees’ absence entitlements
Business Example
In your enterprise, employees have a leave entitlement of 20 days each year.
You do not want to make the entire annual entitlement available in January;
instead, you want to add entitlement at the end of each month/payroll period.
Accruing Absence Quotas
Figure 131: Accrue absence entitlements automatically
17-09-2004
© 2004 SAP AG. All rights reserved.
205
Unit 4: Personnel Calculation Schema TM04
HR311
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
SAP R/3 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.
You can continue to use the Absence Quotas infotype (2006) to record absence
entitlements that are seldom used, such as special leave. In the infotype, you
specify for each employee the amount of entitlement and the validity period.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Data Recording and Administration → Managing
Time Accounts Using Attendance/Absence Quotas → Calculating Absence
Entitlements.
206
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Accruing Absence Quotas
Figure 132: Methods for the Automatic Accrual of Absence Entitlements
You can choose between two procedures to accrue absence entitlements
automatically:
•
Generating default values for the Absence Quotas infotype (2006)
In this procedure, you either generate the absence entitlement for
multiple employees using the RPTQTA report (Generate Absence Quotas)
or online by creating an infotype record.
•
Automatic accrual in time evaluation
In this procedure, 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 the TQTA schema 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).
You use the absence quota type in Customizing to specify which procedure
you want to be used.
17-09-2004
© 2004 SAP AG. All rights reserved.
207
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 133: Automatically Determining Absence Entitlements in the Absence
Quotas Infotype (2006)
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 in the Absence Quotas infotype (2006). It is managed and
processed in the Quota Overview. To access the Quota Overview in SAP
R/3, choose Human Resources → Time Management → Administration →
Time Data → Quota Overview.
Automatic accrual also determines the validity and deduction periods in
addition to the quota number.
208
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Accruing Absence Quotas
Figure 134: Accruing Absence Entitlements: Function QUOTA
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
17-09-2004
© 2004 SAP AG. All rights reserved.
209
Unit 4: Personnel Calculation Schema TM04
HR311
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
The absence entitlements that have not yet been transferred are saved in
cluster B2 in tables QTACC and QTTRANS. The entitlement cannot have
absences deducted from it until the accrued entitlement is transferred to the
Absence Quotas infotype (2006).
Figure 135: Determining Quota Type Selection Rule Group
You can use the quota type selection rule group to specify rules for absence quota
type selection based on the employee’s organizational assignment.
210
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Accruing Absence Quotas
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 the QUOMO feature
The feature allows you to determine the quota type selection rule group
based on employees’ organizational assignments. It is queried by the
QUOTA function and used in generating default values and accruing
quotas by means of the RPTQTA00 report.
•
Using the MOD function in the time evaluation schema
The MOD function calls the MODT personnel calculation rule. You can
use operation MODIF Q=xx to determine the quota type selection rule
group for each of these groupings. 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 also determined by the MODIF Q=xx
operation.
The QUOTA function 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.
The QUOTA function works in the same way as the GWT and LIMIT
functions. It processes a set of rules that you have created and grouped in
Customizing according to the quota type selection rule group.
17-09-2004
© 2004 SAP AG. All rights reserved.
211
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 136: Absence Quota Type Accrual (I)
The generation rules for absence quota selection are processed by the QUOTA
function.
QUOTA stores the accrual entitlements generated in the time evaluation runs
in the QTACC table (quota accrual) in cluster B2. It stores the cumulated
accrual entitlements that are ready for transfer in the QTTRANS table (transfer
pool) in cluster B2.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Data Recording and Administration → Managing
Time Accounts Using Attendance/Absence Quotas → Calculating Absence
Entitlements → Rules for Generating Absence Quotas → Define Generation Rules
for Quota Selection.
212
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Accruing Absence Quotas
Figure 137: Absence Quota Type Accrual (II)
You can use the SAP enhancement HRPTIM03 to fine-tune the criteria for
absence quota accrual for many areas.
Hint: You can use the RPTQUOTA_CHECK report (Overview
of Customizing Settings for Quota Generation) to check your
Customizing settings for calculating absence entitlements. The report
helps you identify incorrect or incomplete Customizing settings. For
information about individual fields, display the field help by choosing
F1 on a field.
17-09-2004
© 2004 SAP AG. All rights reserved.
213
Unit 4: Personnel Calculation Schema TM04
HR311
Figure 138: Determining the Base Entitlement
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 2003 to end of March 2004)
Determined on the basis of the time evaluation or payroll period
Determined on the basis of the accrual period
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Data Recording and Administration → Managing
Time Accounts Using Attendance/Absence Quotas → Calculating Absence
Entitlements → Rules for Generating Absence Quotas → Set Base Entitlements.
214
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Accruing Absence Quotas
Figure 139: Validity and Deduction Intervals
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
Employee-dependent periods such as the payroll period or dependent
on a date type
Periods that are defined in the quota selection rule, such as the accrual
period
Periods that you have defined in Customizing using the period parameter
The deduction from and deduction to dates define the period within which
absences can be deducted from the absence quota. It need not be identical
to the validity period.
17-09-2004
© 2004 SAP AG. All rights reserved.
215
Unit 4: Personnel Calculation Schema TM04
HR311
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Data Recording and Administration → Managing
Time Accounts Using Attendance/Absence Quotas → Calculating Absence
Entitlements → Rules for Generating Absence Quotas → Determine Validity and
Deduction Periods.
Figure 140: Reduction Rules
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.
216
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Accruing Absence Quotas
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Data Recording and Administration → Managing
Time Accounts Using Attendance/Absence Quotas → Calculating Absence
Entitlements → Rules for Generating Absence Quotas → Define Rules for Reducing
Quota Entitlements.
Figure 141: Rounding Rules
When the system calculates values, they 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 are differentiated
using sequence numbers. The system runs through the subrules consecutively
until a rule applies.
Rounding rules are also used elsewhere in Time Management, for example,
within personnel calculation rules using the ROUND operation.
17-09-2004
© 2004 SAP AG. All rights reserved.
217
Unit 4: Personnel Calculation Schema TM04
HR311
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Data Recording and Administration → Managing
Time Accounts Using Attendance/Absence Quotas → Calculating Absence
Entitlements → Rules for Generating Absence Quotas → Define Rules for Rounding
Quota Entitlements.
Figure 142: Quota Corrections Infotype (2013)
You can use the Quota Corrections infotype (2013) to increase, reduce, or
replace entitlements accrued in time evaluation. This is necessary if, for
example, 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 transfer collected entitlement immediately function is now available for
quotas that have been customized to replace existing entitlements.
218
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Accruing Absence Quotas
Figure 143: Quota Overview
The quota overview (transaction PT50) provides all the information and
program functions from the attendance and absence quota management
environment.
To access the quota overview from the menu, choose Human Resources → Time
Management → Administration → Time Data → Quota Overview.
17-09-2004
© 2004 SAP AG. All rights reserved.
219
Unit 4: Personnel Calculation Schema TM04
220
© 2004 SAP AG. All rights reserved.
HR311
17-09-2004
HR311
Lesson: Accruing Absence Quotas
Exercise 11: Automatic Accrual of a Time-Off
Account
Exercise Objectives
After completing this exercise, you will be able to:
•
Automatically transfer the value of a time type to a time-off entitlement
Business Example
In your enterprise, you want to collect employees’ additional times worked
in a time account. You later want to convert this time account to an absence
entitlement, so that employees can compensate the times with time off.
Task: Automatic Accrual of a Time-Off Account
You want an absence quota to be accrued automatically from your employee’s
time-off account Z1## (## = your group number), which you filled in the
previous exercises. The quota is to be transferred on a monthly basis to the
Absence Quotas infotype (2006), and be available for deduction for three
months after the transfer.
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 60 to your group number. (Example: group
number 60 plus 12 = absence quota type 72).
2.
The quota type selection rule group for your employee is 01. Check whether
the grouping has been set by feature QUOMO.
3.
Specify how you want the time-off entitlement to be determined. The
basis for calculating the accrual entitlement is the employee’s base
entitlement.
Consider first how long you want the base period to be. Create the rule
for the base entitlement 001. The base entitlement is to be determined on a
daily basis, using the day balance Z1##. Because the entitlement is to be
accrued daily, the base period should be identical to the accrual period.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
221
Unit 4: Personnel Calculation Schema TM04
4.
HR311
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?
Hint: You must take account of the following information so that
a new infotype record can be created each month: 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 generated only if no valid infotype
record exists. Consider how you can make the validity period
not longer than one day.
5.
In the Rules for Generating Absence Quotas → Define Generation Rules
for Quota Selection IMG activity, create the selection rule 9## for your
absence quota type 60+##. You want it to be accrued on a daily basis
and then transferred to the infotype at the end of the month. The quota
type selection rule group is 01.
6.
In the Time Manager’s Workplace, enter time data for your employee for
the rest of March. Enter attendances using attendance type 0800 or 0425
(ID AH or INST) for all remaining workdays in March, 20yy.
Hint: The instructor duty with attendance type 0425 leads to
a time credit, which you stored in time type Z1## in the first
previous exercises.
222
7.
Check the absence quota accrual by running time evaluation for the
whole of March. Check the status of the generated quotas in the log
and in the Quota Overview.
8.
The absence quota 60+## can be deducted using the absence type 9000.
Enter this absence type with the time data ID QD for your employee on
the first workday in April, 20yy, and check the deduction.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Accruing Absence Quotas
Solution 11: Automatic Accrual of a Time-Off
Account
Task: Automatic Accrual of a Time-Off Account
You want an absence quota to be accrued automatically from your employee’s
time-off account Z1## (## = your group number), which you filled in the
previous exercises. The quota is to be transferred on a monthly basis to the
Absence Quotas infotype (2006), and be available for deduction for three
months after the transfer.
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 60 to your group number. (Example: group
number 60 plus 12 = absence quota type 72).
a)
In the Implementation Guide (IMG) for Personnel Time Management
, choose Time Data Recording and Administration → Managing Time
Accounts Using Attendance/Absence Quotas → Calculating Absence
Entitlements.
All IMG activities that you require for this exercise are under this
section of the IMG.
b)
c)
Choose → Automatic Accrual of Absence Quotas → Permit Generation of
Quotas in Time Evaluation.
Locate the line Employee subgroup grouping for quota type 1, personnel
subarea grouping for quota type 10, quota type 60 + ##.
Automatic accrual is permitted for the quota if either the Increase
or Replace field is selected. Select either Increase or Replace
and save your entry.
Hint: 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.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
223
Unit 4: Personnel Calculation Schema TM04
2.
HR311
The quota type selection rule group for your employee is 01. Check whether
the grouping has been set by feature QUOMO.
a)
b)
c)
In the IMG, within the main section specified above, choose: Rules
for Generating Absence Quotas → Specify Rule Groups for Quota Type
Selection.
Choose Modify Feature QUOMO.
Open the decision tree to check whether an entry has been created
for the for your quota selection rule group 01 for your country grouping.
The entry 01 is also listed under the Otherwise node.
3.
Specify how you want the time-off entitlement to be determined. The
basis for calculating the accrual entitlement is the employee’s base
entitlement.
Continued on next page
224
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Accruing Absence Quotas
Consider first how long you want the base period to be. Create the rule
for the base entitlement 001. The base entitlement is to be determined on a
daily basis, using the day balance Z1##. Because the entitlement is to be
accrued daily, the base period should be identical to the accrual period.
a)
b)
c)
Choose the Rules for Generating Absence Quotas → Set Base
Entitlements activity.
Choose Base Entitlement for Absence Quota Generation.
Determine the basis on which you want the accrual entitlement
to be calculated. Create the rule for the base entitlement with the
following values:
Figure 144: Rule for Base Entitlement
Hint: In our example, the base period corresponds to the
accrual period. This is because no proportional entitlement
is calculated. You want the cumulated value of the day
balance to be transferred to the accrual entitlement without
any additional calculations. Enter the accrual period in the
related to period area.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
225
Unit 4: Personnel Calculation Schema TM04
4.
HR311
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?
Hint: You must take account of the following information so that
a new infotype record can be created each month: 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 generated only if no valid infotype
record exists. Consider how you can make the validity period
not longer than one day.
a)
b)
c)
Choose the Rules for Generating Absence Quotas → Determine Validity
and Deduction Periods activity.
Choose New Entries.
Enter the following data:
Figure 145: Determining Validity and Deduction Periods
Hint: * By specifying the transfer time in the validity interval
from – to section, you ensure that the absence quota is filled
only once and cannot be extended.
Continued on next page
226
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Accruing Absence Quotas
5.
In the Rules for Generating Absence Quotas → Define Generation Rules
for Quota Selection IMG activity, create the selection rule 9## for your
absence quota type 60+##. You want it to be accrued on a daily basis
and then transferred to the infotype at the end of the month. The quota
type selection rule group is 01.
a)
b)
c)
In the IMG, within the main section specified above, choose: →
Define Generation Rules for Quota Selection.
Choose New Entries.
Enter the following data:
Figure 146: Defining Generation Rules for Quota Selection
d)
Choose the Accrual Period tab.
Accrual period: Daily
e)
Choose the Base Entitlement tab.
Rule for base entitlement: 001
f)
Choose the Accrual Entitlement tab.
Select the No pro rata calculation field.
g)
Choose the Transfer Time tab.
Select the Per Time Eval. Period radio button.
This corresponds to the period 01 - monthly in the standard system.
You do not need to fill the Applicability and Total Entitlement tab
pages for the purposes of this exercise.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
227
Unit 4: Personnel Calculation Schema TM04
6.
HR311
In the Time Manager’s Workplace, enter time data for your employee for
the rest of March. Enter attendances using attendance type 0800 or 0425
(ID AH or INST) for all remaining workdays in March, 20yy.
Hint: The instructor duty with attendance type 0425 leads to
a time credit, which you stored in time type Z1## in the first
previous exercises.
a)
b)
c)
7.
Choose Human Resources → Time Management → Administration →
Time Manager’s Workplace.
Enter attendances using attendance type 0800 or 0425 (ID AH or
INST) for all remaining workdays in March, 20yy.
Save your data.
Check the absence quota accrual by running time evaluation for the
whole of March. Check the status of the generated quotas in the log
and in the Quota Overview.
a)
b)
c)
In the menu, choose Human Resources → Time Management →
Administration → Time Evaluation → Time Evaluation.
Run time evaluation using your variant and a forced recalculation
from March 01, 20yy through March 31, 20yy.
In the log, review the path: → (First workday in March) → Manage
time accounts → QUOTA.
Review the output tables. Review the table ZES in the Input area to
confirm the value in time type Z1##.
Review the time type in the Processing and Output sections. To see
the transfer of the accrued quota, review the time evaluation log for
03/31/20yy → Manage time accounts → QUOTA.
d)
e)
In the menu, choose Human Resources → Time Management →
Administration → Time Data → Quota Overview.
Review the quota accrual in the quota overview. Choose the required
validity and deduction period and open the Absence Quotas tab page.
It provides a detailed overview of your quota’s status and accrual
information. You should see accrued leave for your employee in
quota type 60+##. Note how much absence time has been accrued.
Continued on next page
228
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Accruing Absence Quotas
8.
The absence quota 60+## can be deducted using the absence type 9000.
Enter this absence type with the time data ID QD for your employee on
the first workday in April, 20yy, and check the deduction.
a)
In the menu, choose Human Resources → Time Management →
Administration → Time Manager’s Workplace..
Enter an absence for your employee on the first workday in April
using absence type 9000 Quota Reduction (HR311) (time data ID =
QD). This absence type will be deducted from absence quota 60+##.
Review the deduction.
b)
c)
d)
e)
f)
17-09-2004
Select the first workday in April, 20yy from the calendar.
From the Time Data area on the right, enter QD in the ID field.
Save the data and exit the Time Manager’s Workplace.
In the menu, choose Human Resources → Time Management →
Administration → Time Data → Quota Overview.
Choose the required validity and deduction period and open the
Absence Quotas tab page. Review the deduction.
© 2004 SAP AG. All rights reserved.
229
Unit 4: Personnel Calculation Schema TM04
HR311
Lesson Summary
You should now be able to:
•
Accrue absence entitlements automatically
•
Make manual changes to absence entitlements that were accrued
automatically
•
Find information about employees’ absence entitlements
Related Information
For more information about automatic accrual of absence quotas, see the SAP
Library and choose Human Resources → Personnel Time Management → Time
Data Recording and Administration → Quotas.
230
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Unit Summary
Unit Summary
You should now be able to:
•
Describe the three main sections in the TM04 schema
•
Name the processing blocks in day processing
•
Describe the significance of initialization in the schema
•
Provide recorded time data for time evaluation
•
Run error checks
•
Describe how planned working times are determined
•
Explain how time types are determined
•
Process breaks
•
Reduce absences
•
Explain the various methods for determining overtime
•
Describe the process of determining overtime
•
Describe how the overtime determined is used
•
Explain the method of using employee and day groupings to represent
your different collective agreement provisions and company agreements
•
Describe the technical process of time wage type selection
•
Represent contractual provisions in a time wage type selection rule
•
Make overtime hours available for remuneration or compensation with
time off
•
Explain the data flow of time wage types and balances during time
evaluation
•
Group time types as employees’ time accounts
•
Transfer times to time accounts, wage types, or quotas
•
Check value limits for time balances and specify appropriate system
responses
•
Accrue absence entitlements automatically
•
Make manual changes to absence entitlements that were accrued
automatically
•
Find information about employees’ absence entitlements
17-09-2004
© 2004 SAP AG. All rights reserved.
231
Unit Summary
232
HR311
© 2004 SAP AG. All rights reserved.
17-09-2004
Unit 5
Time Evaluation With Clock Times
Unit Overview
In this unit, you learn how you can use the TM04 schema in conjunction with
time recording systems.
You are also introduced to the TM00 schema, which you can use the evaluate
time data that was entered as clock times.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
•
•
•
Describe the distribution of tasks between the time recording system
and SAP R/3
Name the infotypes required for processing time postings
Explain the formation of time pairs from the time postings
Explain how time pairs are read into time evaluation
Run special error checks for the time pairs
Name the special requirements for time evaluation with clock times
Describe the special features of the TM00 schema
Explain the differences in relation to schema TM04
Unit Contents
Lesson: Using Time Recording Systems ........................................ 234
Lesson: Processing Time Postings in SAP R/3................................. 245
Exercise 12: Processing Data from Time Recording Systems .......... 249
Lesson: Time Evaluation With Clock Times ..................................... 256
Exercise 13: Evaluating Time Data Using Personnel Calculation Schema
TM00 ............................................................................ 273
17-09-2004
© 2004 SAP AG. All rights reserved.
233
Unit 5: Time Evaluation With Clock Times
HR311
Lesson: Using Time Recording Systems
Lesson Overview
This lesson provides an overview of how external time recording systems
are connected to SAP R/3 and how the time recording system and SAP R/3
interact.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Describe the distribution of tasks between the time recording system
and SAP R/3
Name the infotypes required for processing time postings
Explain the formation of time pairs from the time postings
Business Example
In your enterprise, employees post their clock-in and clock-out times and
breaks using time recording systems. You want to upload the time postings to
SAP R/3. You want employees’ time and labor data to be valuated alongside
the manually recorded time data in time evaluation.
234
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Using Time Recording Systems
Using Time Recording Systems
Figure 147: Using Time Recording Systems
Using time recording systems is the most popular form of employee
self-service. It considerably reduces the workload of time administrators.
Time recording systems allow you to:
•
Record attendance times automatically
At the time recording system, employees record when they:
17-09-2004
–
Enter the premises
–
Take a break (optional)
–
Start off-site work or a business trip (optional)
–
Leave the premises
•
Let employees record certain absence reasons. Locked absence
records are generated, which are approved by time administrators in
postprocessing.
•
Carry out access controls. This means that unauthorized employees
cannot enter sensitive production areas.
© 2004 SAP AG. All rights reserved.
235
Unit 5: Time Evaluation With Clock Times
HR311
Figure 148: Distribution of Tasks
The distribution of tasks between the time recording system and 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 table CC1TEV
Tasks of Time Management:
•
•
•
•
236
Transferring time events from interface table CC1TEV to table TEVEN
Processing time events
Correcting and supplementing time events (infotype 2011)
Transferring the selected time accounts to the time recording system
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Using Time Recording Systems
Figure 149: Data Flow Between the Time Recording System and Time
Management
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,
absence/attendance reasons
Information about cost assignment and a different payment
Download
17-09-2004
© 2004 SAP AG. All rights reserved.
237
Unit 5: Time Evaluation With Clock Times
HR311
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)
Figure 150: Download to the Time Recording System
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
(0050) record for at least one day of the HR master record’s validity period.
238
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Using Time Recording Systems
Data for the download is categorized as follows:
•
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.
•
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.
•
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
Figure 151: Time Recording Information Infotype (0050)
The Time Recording Information infotype (0050) contains two types of data:
interface data and employee-related control data (time variables).
17-09-2004
© 2004 SAP AG. All rights reserved.
239
Unit 5: Time Evaluation With Clock Times
HR311
Interface data (interface to time recording systems): Provides information
about which time recording terminals the employee’s mini-master data is
sent to. Other data such as the mail indicator and access control group are only
evaluated if the time recording system supports these functions.
•
•
•
•
•
•
•
•
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: Can be evaluated using the HRS and OUTTI operations in time
evaluation.
•
•
•
•
•
240
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
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Using Time Recording Systems
Figure 152: Time Events Infotype (2011)
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
SAP system.
The Time Events infotype (2011) is usually filled by a time recording
system. You process time events in the SAP system only under exceptional
circumstances, for example, if time events are missing or incorrect. In the
Time Events infotype (2011), you can:
•
•
Record time events manually or change time events that were imported
into the SAP system with errors
Enter or supplement information on cost assignment or on a different
payment
The time events are stored in the 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.
17-09-2004
© 2004 SAP AG. All rights reserved.
241
Unit 5: Time Evaluation With Clock Times
HR311
Example: Employee works night shift on March 2:
•
•
Clock-in entry on March 02 at 22:05 → day assignment: =
Clock-out entry on March 03 at 06:03 →: day assignment: <
We recommend that you use the Time Manager’s Workplace to postprocess
time events, because it enables you to check and correct multiple time events
simultaneously.
Figure 153: Pair Formation
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 triggered as of the day on which
there is a new time event.
Pair formation is integrated into time evaluation. Time evaluation runs pair
formation automatically when it is required (that is, if there are unprocessed
time events).
Caution: 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.
242
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Using Time Recording Systems
If certain processing conditions occur (for example, a start of break time event
is followed by a clock-out posting and therefore a pair cannot be formed),
pair formation issues messages so that the data can be postprocessed in the
message processing function of the Time Manager’s Workplace.
Figure 154: Forming Pairs from Time Events
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).
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → General Settings → Define Settings
for Pair Formation.
Note: An attendance check does not require time evaluation to have run or
pairs formed; only the time postings have to have been uploaded.
17-09-2004
© 2004 SAP AG. All rights reserved.
243
Unit 5: Time Evaluation With Clock Times
HR311
Lesson Summary
You should now be able to:
•
Describe the distribution of tasks between the time recording system
and SAP R/3
•
Name the infotypes required for processing time postings
•
Explain the formation of time pairs from the time postings
244
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Processing Time Postings in SAP R/3
Lesson: Processing Time Postings in SAP R/3
Lesson Overview
In this lesson, you learn how time evaluation reads the time pairs formed
from time postings and then checks them for errors.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Explain how time pairs are read into time evaluation
Run special error checks for the time pairs
Business Example
In your enterprise, employees post their clock-in and clock-out times and
breaks using time recording systems.
You want to run an additional check on the imported time postings once
they have been read and formed into pairs by time evaluation. For example,
for night shift employees, you do not always want an error to be issued if
employees’ clock-out postings have not been entered in time for the overnight
time evaluation run.
Figure 155: Function P2011: Providing Planned Specifications and Actual Times
17-09-2004
© 2004 SAP AG. All rights reserved.
245
Unit 5: Time Evaluation With Clock Times
HR311
You use function P2011 when you upload time events/time postings from
external time recording systems to the R/3 System. The P2011 function
performs two tasks:
•
Importing planned specifications:
The employee’s current daily work schedule is first imported to the
internal table TZP.
•
Providing actual times:
The pairs formed from the time postings are then placed in the internal
table TIP.
If you use the P2011 function in the schema, you require the P2000 function
only if you want to load planned specifications for future days.
You can also allow your employees to enter particular absences at the time
recording system. The attendance/absence reasons are processed in the
schema by personnel calculation rules TD80 and TD90.
Figure 156: Daily Input: Table TIP After Function P2011
The P2011 function transfers the time pairs that were formed from the time
postings from the PT table (cluster B2) to the internal work table TIP. All clock
times are decimalized in the process.
246
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Processing Time Postings in SAP R/3
If pair formation assigns time events to the previous day, the system adds 24
hours to the time pair.
Figure 157: Error Checks for Each Pair: Rule TE30
Pair formation assigns each pair a status, which defines whether a time pair
was able to be formed correctly.
The TE30 personnel calculation rule carries out 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 DELIM constant.
You can use the DELIM constant (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.
•
17-09-2004
It uses the DELIM operation to delimit the open pair with the start or
end of the planned working time. The day is evaluated provisionally,
and a recalculation is set.
© 2004 SAP AG. All rights reserved.
247
Unit 5: Time Evaluation With Clock Times
HR311
The TE30 personnel calculation rule is called by the PTIP function (process
internal table TIP).
Hint:
•
•
248
As an alternative to TE30, you can use the TE31 personnel
calculation rule, 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 the TD20 personnel calculation rule.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Processing Time Postings in SAP R/3
Exercise 12: Processing Data from Time
Recording Systems
Exercise Objectives
After completing this exercise, you will be able to:
•
Enter time postings for an employee
•
Enter missing time postings
Business Example
You want to run time evaluation for an employee who posts working times
using time recording systems. You want to check the results and rectify any
errors as required.
Task 1: Processing Data from Time Recording Systems
In your enterprise, employees post their attendance times at a time recording
terminal as of April 01, 20yy (yy = previous year).
1.
2.
Check whether the Time Recording Information infotype (0050) has been
created for your employee. If not, create the infotype using the following
data:
Time event type grp
01
Subsystem grouping
001
Grpg. att./absences
001
Grpg for EE expend.
001
Time rec. ID no.
311101##
Enter time events for your employee for the next three working days in
April, 20yy. However, change your Time Manager’s Workplace profile first.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
249
Unit 5: Time Evaluation With Clock Times
HR311
Using transaction PTMW_PROF, change your profile to
Z_HR311_TIME_ADM_2, your definition set to SET_HR311, and your
definition subset to 001.
Hint: You previously entered a full-day absence for your
employee on the first workday in April. Therefore you should not
enter any time events for this day.
3.
Run time evaluation using your schema Z4##. Use the time evaluation
log to check how the time events are imported and processed.
Task 2: Missing clock-out
Your employee forgot one day to make a clock-out entry when he or she was
leaving the company. Correct the error using the Time Manager’s Workplace.
250
1.
Enter the employee’s time events for this day by creating only one time
event for your employee on the fifth workday in April. Enter only a
clock-in without a matching clock-out entry.
2.
Run time evaluation for this day using schema Z4##, and use the time
evaluation log to check how the system reacts to the error.
3.
Correct the error using the message processing function in the Time
Manager’s Workplace.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Processing Time Postings in SAP R/3
Solution 12: Processing Data from Time
Recording Systems
Task 1: Processing Data from Time Recording Systems
In your enterprise, employees post their attendance times at a time recording
terminal as of April 01, 20yy (yy = previous year).
1.
Check whether the Time Recording Information infotype (0050) has been
created for your employee. If not, create the infotype using the following
data:
Time event type grp
01
Subsystem grouping
001
Grpg. att./absences
001
Grpg for EE expend.
001
Time rec. ID no.
311101##
a)
b)
2.
In the menu, choose Human Resources → Time Management →
Administration → Time Data → Maintain.
Choose the Time Management Data tab page and ensure that the
information above is entered in the Time Recording Information
infotype (0050).
Enter time events for your employee for the next three working days in
April, 20yy. However, change your Time Manager’s Workplace profile first.
Using transaction PTMW_PROF, change your profile to
Z_HR311_TIME_ADM_2, your definition set to SET_HR311, and your
definition subset to 001.
Hint: You previously entered a full-day absence for your
employee on the first workday in April. Therefore you should not
enter any time events for this day.
a)
b)
Choose the PTMW_PROF transaction to change your access
information for the Time Manager’s Workplace as shown below:
Enter the following data:
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
251
Unit 5: Time Evaluation With Clock Times
c)
d)
e)
f)
3.
HR311
Profile:
Z_HR311_TIME_ADM_2
Definition set:
SET_HR311
Definition subset:
001
Choose Execute.
Select the appropriate period from the calendar.
In the Time Data area, click on the Time Events tab. Enter P10 for
Clock-in in the ID field and enter the time as displayed in the table
below. Enter P20 for Clock-out and add the time as listed below.
Proceed to the next day and enter the data that appears in the table
below.
Date
Time
Time event
type/time data
ID
2nd workday in
April
08:00
P10 Clock in
2nd workday in
April
16:30
P20 Clock out
3rd workday in April 08:00
P10 Clock in
3rd workday in April 16:30
P20 Clock out
4th workday in April 08:00
P10 Clock in
4th workday in April 16:30
P20 Clock out
Save your data. SAP R/3 creates the individual infotype records.
Run time evaluation using your schema Z4##. Use the time evaluation
log to check how the time events are imported and processed.
a)
b)
c)
In the menu, choose Human Resources → Time Management →
Administration → Time Evaluation → Time Evaluation.
Run time evaluation using your schema Z4## for evaluation through
the last day on which you entered time data.
In the time evaluation log, check the processing of the time events in
the function P2011 in the Provide Time Data section (path: [any day]
→ Provide time data → IF POS → IF NOT SIMF → P2011). Review the
input and the output of this step.
Continued on next page
252
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Processing Time Postings in SAP R/3
Task 2: Missing clock-out
Your employee forgot one day to make a clock-out entry when he or she was
leaving the company. Correct the error using the Time Manager’s Workplace.
1.
Enter the employee’s time events for this day by creating only one time
event for your employee on the fifth workday in April. Enter only a
clock-in without a matching clock-out entry.
a)
b)
c)
d)
2.
In the menu, choose Human Resources → Time Management →
Administration → Time Manager’s Workplace..
Select the next workday in April, 20yy from the calendar.
Using the same steps as above, enter a clock-in as indicated in the
table below. Do not enter a clock-out.
Date
Time
Time event
type/time data ID
5th workday in April
8:00
P10 Clock in
Save the data and exit the Time Manager’s Workplace.
Run time evaluation for this day using schema Z4##, and use the time
evaluation log to check how the system reacts to the error.
a)
b)
In the menu, choose Human Resources → Time Management →
Administration → Time Evaluation → Time Evaluation.
Run time evaluation for the evaluation period through the last day
on which you entered time data.
Check the log for error messages.
Time evaluation should terminate processing with the error message
04 Clock-out cannot be delimited. The error is issued in personnel
calculation rule TE30 in the Error Checks section of the log (Error
Checks → PTIP TE30 GEN).
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
253
Unit 5: Time Evaluation With Clock Times
3.
HR311
Correct the error using the message processing function in the Time
Manager’s Workplace.
a)
b)
c)
d)
e)
f)
In the menu, choose Human Resources → Time Management →
Administration → Time Manager’s Workplace..
Choose Goto → Process Messages.
Choose Employee View.
Click on the message Clock-out cannot be delimited.
Choose the Time Events tab, and enter the missing time event as
described in step 1-2.
Save your data and run time evaluation again.
Hint: In the standard system, you can select your employee
in the employee list in the Time Manager’s Workplace and
choose Start Time Evaluation.
However, because the LLREP feature, which determines
the variant used for time evaluation, is not set up with all
variants used in the training courses in the training system,
you have to access time evaluation from the menu.
To do so, choose Time Evaluation.
254
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Processing Time Postings in SAP R/3
Lesson Summary
You should now be able to:
•
Explain how time pairs are read into time evaluation
•
Run special error checks for the time pairs
17-09-2004
© 2004 SAP AG. All rights reserved.
255
Unit 5: Time Evaluation With Clock Times
HR311
Lesson: Time Evaluation With Clock Times
Lesson Overview
In this lesson, you learn about schema processing where time data entered
using clock times is evaluated. The focus is on realizing business requirements
that enable you to check time points in the work schedule, evaluate overtime
approvals, and form special bonuses.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Name the special requirements for time evaluation with clock times
Describe the special features of the TM00 schema
Explain the differences in relation to schema TM04
Business Example
You record employees’ time data using a time recording system. You record
the time data with clock times in order to check in time evaluation whether
working time provisions that are based on clock times are observed, including:
•
•
•
256
Checking whether employees were punctual
Determining whether employees are permitted to work overtime at
particular times
Forming bonuses if employees have worked at night
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation With Clock Times
Time Evaluation With Clock Times
Figure 158: Day Processing in the Schema
In day processing, time evaluation performs through the following processing
steps, in a set sequence:
1.
2.
3.
4.
5.
6.
7.
17-09-2004
Time evaluation 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.
It carries out error checks for the day being evaluated.
It compares the employee’s time data with the planned specifications
from the personal work schedule.
It determines whether the employee has worked overtime and whether it
has been approved.
It selects time wage types.
It determines how any overtime that exists is to be compensated; that is,
whether it should be remunerated and/or compensated with time off.
It cumulates the day balances and forms time accounts.
© 2004 SAP AG. All rights reserved.
257
Unit 5: Time Evaluation With Clock Times
HR311
Figure 159: Setting Employee Groupings: Function MOD
Before day processing (initialization block in schema), the MOD function 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, the MOD function calls the
MODT personnel calculation rule.
A personnel calculation subrule is called in the MODT rule 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. The employee subgroup grouping for the personnel calculation
rule in the standard system is not relevant in this case.
For more information, see the Implementation Guide
•
•
258
for Personnel Management and choose Personnel Administration →
Payroll Data → Basic Pay → Define EE Subgroup Grouping for PCR and
Coll.Agrmt.Prov. (collective agreement provisions)
for Personnel Time Management and choose Time Evaluation → Time
Evaluation With Clock Times → Initial Steps → Define Groupings.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation With Clock Times
Figure 160: Error Checks: Rule TE10
The TE10 personnel calculation rule compares the absences of less than one
day with the day’s attendances.
If the position of the partial-day absence results in a period of time with
undocumented time, time evaluation enters a note or error in the error table. If
attendances and absences overlap, time evaluation uses the INSTP operation
to adjust the absence in line with the position of the attendance.
Hint: The original record in the Absences infotype (2001) is not updated
in the process.
The TE10 personnel calculation rule is called by the PTIPA function.
17-09-2004
© 2004 SAP AG. All rights reserved.
259
Unit 5: Time Evaluation With Clock Times
HR311
Figure 161: Dynamic Daily Work Schedule Assignment: Rule TD30
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.
The TD30 rule 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.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation With Clock Times →
Providing Time Data → Work Schedule and Time Events → Dynamic Assignment of
Daily Work Schedules → Dynamic Assignment Based on Clock-Ins..
260
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation With Clock Times
Figure 162: Tolerance Times: Function DPTOL
The DPTOL function is used to edit TIP entries according to the start and end
tolerances stored 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.
17-09-2004
© 2004 SAP AG. All rights reserved.
261
Unit 5: Time Evaluation With Clock Times
HR311
Figure 163: Assigning Time Type/Processing Type According to the Time
Identifier and Pair Type
The TIMTP function is used to merge the TIP entries (actual times) with the
daily work schedule in the TZP table (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, the TIMTP function
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).
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation With Clock Times →
Time Data Processing → Set Time Type Determination.
262
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation With Clock Times
Figure 164: Comparing Times: Function TIMTP
A new TIP entry is formed in the TIP table for each new time point in the
daily work schedule. In this process, the entries from TIP are compared with
those in TZP.
Figure 165: Layout of the Time Type Determination View
17-09-2004
© 2004 SAP AG. All rights reserved.
263
Unit 5: Time Evaluation With Clock Times
HR311
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
Hint: The meaning of the pair type is fixed. You cannot change it in
Customizing.
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
K: Core night work (valid for the German country version only)
Hint:
•
•
264
Processing type A is assigned for paid breaks so that the times are
not included in the calculation of the daily maximum working
time.
The processing type "K" is required for the German country
version only. It is assigned for breaks because it is required for
determining core night work using the KNTAG function.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation With Clock Times
Figure 166: Calculating Planned Working Time: Function DEFTP
The DEFTP function 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 specify the maximum daily working time in the Daily Work Schedule
view (V_T550A). If there is no information in the daily work schedule, the
DEFTP function uses the value of the TGMAX constant from the Payroll
Constants view (V_T511K).
The TIP entries with processing type S are only preliminary planned working
time pairs; they could partially become overtime pairs when overtime is
determined.
The DEFTP function collects
•
•
All attendance and absence times in auxiliary time type 0000
All attendance times in the auxiliary time type 0001
Both time types are used for determining overtime and for reducing absences.
Time evaluation uses them to ensure that
•
•
17-09-2004
Overtime is not generated until after the planned working hours per day
have been reached
Partial-day absences do not increase the actual working time
© 2004 SAP AG. All rights reserved.
265
Unit 5: Time Evaluation With Clock Times
HR311
TIP entries with processing type "-" are deleted.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation With Clock Times →
Time Data Processing → Indicate Planned Working Time Pairs.
Figure 167: Overtime Processing
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 types are selected 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.
266
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation With Clock Times
Figure 168: Methods of Overtime Approval
An important factor in overtime determination in time evaluation based on clock
times (schema TM00) 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.
The TM00 schema contains several standard solutions for evaluating overtime
approvals. These range from evaluating a flat-rate overtime approval for all
employees, to evaluating individual approvals for a particular period and
number.
17-09-2004
© 2004 SAP AG. All rights reserved.
267
Unit 5: Time Evaluation With Clock Times
HR311
Figure 169: Attendance Quotas (Infotype 2007)
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.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Data Recording and Administration → Managing
Time Accounts Using Attendance/Absence Quotas → Time Quota Types → Define
Attendance Quota Types.
268
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation With Clock Times
Figure 170: Determining Overtime: Function GOT
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 the TGMAX constant
The TO20 personnel calculation rule checks for each TIP entry whether the
conditions have been observed.
The GOT function requires valid overtime approvals before it determines
overtime. GOT TO20 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.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Time Evaluation With Clock Times
→ Time Data Processing → Determining Overtime → Determine Overtime from
Attendance Quotas.
17-09-2004
© 2004 SAP AG. All rights reserved.
269
Unit 5: Time Evaluation With Clock Times
HR311
Figure 171: Forming Day Balances: Rule TR10
The TR10 personnel calculation rule 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 the TES table (day balances).
Figure 172: Balance Formation and Time Type Determination
270
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation With Clock Times
Time pairs in TIP have been split using the TIMTP function and classified by
a time type and a processing type.
The TR10 personnel calculation rule 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 relate to employees’ attendance
and absence statuses
Figure 173: Criteria for Selecting a Schema
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:
•
•
•
TM00: Time evaluation with time events
TM01: Time evaluation for work schedule deviations
TM04: Time evaluation for times entered as hours
The three schemas require different forms of time data for evaluation and
pursue different strategies in evaluating the time data.
17-09-2004
© 2004 SAP AG. All rights reserved.
271
Unit 5: Time Evaluation With Clock Times
HR311
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:
•
•
•
•
•
•
272
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
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation With Clock Times
Exercise 13: Evaluating Time Data Using
Personnel Calculation Schema TM00
Exercise Objectives
After completing this exercise, you will be able to:
•
Evaluate time data entered as clock times
•
Run time evaluation using the TM00 personnel calculation schema
Business Example
In your enterprise, you want to record some employees’ working times with
clock times so as to comply with special contractual provisions.
You want to valuate these employees’ times using time evaluation.
Task: Time Evaluation With Clock Times
Create a new employee, whose time data is to be entered with clock times.
Run time evaluation for the employee, using schema TM00.
1.
Use the personnel action type Time recording (mini-master) to create
personnel number 311102## (## = your group number):
Entry date
01/01/20yy (yy = previous year)
Personnel area
3300
Employee group
1
Employee subgroup
U1 (Hourly rate/wage)
Personnel subarea
0001
Work schedule rule
NORM
Time Management status
1
Working week
01 Working week Monday
Time rec. ID no.
311102##
Time event type grouping
01
Subsystem grouping
001
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
273
Unit 5: Time Evaluation With Clock Times
HR311
Grpg. att./absences
001
Grouping for employee
expenditures
001
Quotas
You may skip this infotype
Do not assign a position in the Organizational Assignment infotype (0001).
2.
Ensure that the system generates clock times automatically when you
record attendances and/or absences, even when you enter a number of
hours.
3.
In the Time Manager’s Workplace, record time infotypes with clock
times and time events for your employee 311102##, for January. Use
the employee’s planned specifications as a guide when you enter time
events. Use the TMW profile Z_HR311_TIME_ADM_2, definition set
SET_HR311, and subset 001.
4.
In January, your employee is permitted to work two hours of overtime
after the end of the planned working time. Enter an overtime approval
for the employee in the Attendance Quotas infotype (2007). Use the time
data ID AQ.
On the 4th workday in January, enter time events with clock-in and
clock-out times that include 3 hours beyond the end of the employee’s
planned working time (08:00 - 19:30).
5.
274
Run time evaluation for the employee, using schema TM00. Use the
time evaluation log to check how the time data is imported, and how
overtime is processed.
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation With Clock Times
Solution 13: Evaluating Time Data Using
Personnel Calculation Schema TM00
Task: Time Evaluation With Clock Times
Create a new employee, whose time data is to be entered with clock times.
Run time evaluation for the employee, using schema TM00.
1.
Use the personnel action type Time recording (mini-master) to create
personnel number 311102## (## = your group number):
Entry date
01/01/20yy (yy = previous year)
Personnel area
3300
Employee group
1
Employee subgroup
U1 (Hourly rate/wage)
Personnel subarea
0001
Work schedule rule
NORM
Time Management status
1
Working week
01 Working week Monday
Time rec. ID no.
311102##
Time event type grouping
01
Subsystem grouping
001
Grpg. att./absences
001
Grouping for employee
expenditures
001
Quotas
You may skip this infotype
Do not assign a position in the Organizational Assignment infotype (0001).
a)
b)
Choose in the menu Human Resources → Personnel Management →
Administration → HR Master Data → Personnel Actions.
Select the Time Recording (Mini-Master) action with start date
01/01/20yy (yy = previous year) for employee 311102## (## = your
group number).
Enter the following data in the Personnel Action screen:
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
275
Unit 5: Time Evaluation With Clock Times
HR311
Personnel area
3300
Employee group
1
Employee subgroup
U1 (Hourly rate/wage)
Choose Execute. Save your data.
c)
Create the Personal Data infotype (0002).
Enter the first and last name of your choice, birth date, and social
security number.
Save your data.
d)
Create the Organizational Assignment infotype (0001).
Enter personnel subarea 0001.
You want to hire the employee without assigning him or her to a
particular position, so do not enter a position.
Save your data. The Organizational Assignment screen appears.
Select the No assignment radio button.
Choose Continue.
Your infotype 0001 will now be saved with the default position
number (9999999).
e)
Create the Planned Working Time infotype (0007).
Accept the default work schedule rule NORM.
Select Time Management status 1 - Time Evaluation of Actual Times.
Choose 01 Working week Monday.
Save your data.
f)
Create the Time Recording Information infotype (0050).
Enter the time recording number 311102## (same as the personnel
number).
Accept the defaults for the time event type group, subsystem grouping,
grpg. att./absence, and grouping for EE exp.
Save your data.
g)
Skip the Absence Quotas infotype (2006) by choosing Cancel.
Continued on next page
276
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation With Clock Times
2.
Ensure that the system generates clock times automatically when you
record attendances and/or absences, even when you enter a number of
hours.
a)
b)
In the IMG, choose: Personnel Time Management → Time Data
Recording and Administration → Permit Att./Absences to be Recorded
Without Clock Times.
Open the decision tree structure to confirm that HRSIF=0 is set for
employee subgroup U1.
Hint: You use feature HRSIF=0 to instruct the system to
generate clock times on the basis of the employee’s personal
work schedule when partial-day attendances and absences
are recorded.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
277
Unit 5: Time Evaluation With Clock Times
3.
HR311
In the Time Manager’s Workplace, record time infotypes with clock
times and time events for your employee 311102##, for January. Use
the employee’s planned specifications as a guide when you enter time
events. Use the TMW profile Z_HR311_TIME_ADM_2, definition set
SET_HR311, and subset 001.
a)
In the menu, choose Human Resources → Time Management →
Administration → Time Manager’s Workplace..
Enter the time data in the Time Events tab page. Enter time data for
the first three working days in January, 20yy.
Select a period that includes the first three workdays in January.
Hint: You do not need to enter data on January 1 as it is a
holiday.
b)
c)
d)
Choose the Time Events tab.
Enter the following data: Make sure you specify clock-in and
clock-out times for each workday. Use the employee’s work schedule
as a basis.
Date
Time
Time event type/time
data ID
1st workday in
January
08:00
P10 Clock in
1st workday in
January
16:30
P20 Clock out
2nd workday in
January
08:00
P10 Clock in
2nd workday in
January
16:30
P20 Clock out
3rd workday in
January
08:00
P10 Clock in
3rd workday in
January
16:30
P20 Clock out
Save your data.
Continued on next page
278
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation With Clock Times
4.
In January, your employee is permitted to work two hours of overtime
after the end of the planned working time. Enter an overtime approval
for the employee in the Attendance Quotas infotype (2007). Use the time
data ID AQ.
On the 4th workday in January, enter time events with clock-in and
clock-out times that include 3 hours beyond the end of the employee’s
planned working time (08:00 - 19:30).
a)
Create an attendance quota of type 01 in the Attendance Quotas
infotype (2007) for the employee for January. To do so, remain in
the Time Manager’s Workplace.
Choose the Time Data tab.
Enter the time data ID AQ for the whole of January. To do so,
expand one day in January and double-click on the blank field for
the time data ID. The Detail area opens.
Enter the following data:
Time Data ID
AQ
Date
01/01/20yy - 01/31/20yy
Choose Enter. Enter the following data in the Attendance Quotas
tab:
Attendance quota type
01 Approved overtime
Time
From the end of planned working time
until 2 hours after the end of planned
working time16:30 - 18:30
Quota number
Do not enter anything in this field
Overtime
compensation type
Depends on wage type
Save your data.
b)
Enter time events for your employee for the fourth workday of
January 20yy. Enter a clock-in time of 08:00 and a clock-out time of
19:30.
Choose the Time Events tab.
Enter the following data:
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
279
Unit 5: Time Evaluation With Clock Times
c)
HR311
Date
Time
Time event type/time
data ID
4th workday in
January
08:00
P10 Clock in
4th workday in
January
19:30
P20 Clock out
Save your data. SAP R/3 creates the infotype record.
Continued on next page
280
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Evaluation With Clock Times
5.
Run time evaluation for the employee, using schema TM00. Use the
time evaluation log to check how the time data is imported, and how
overtime is processed.
a)
In the menu, choose Human Resources → Time Management →
Administration → Time Evaluation → Time Evaluation.
Enter the following data:
b)
c)
Personnel number:
311102##
Time evaluation schema:
TM00
Evaluation up to:
The last day for which you
entered time data
Display log:
Selected
Execute the report.
Review the time evaluation log in the following areas:
•
•
•
[any day] → Determine planned working times → TIMTP:
Determination of time type and processing type (based on employee’s
planned working times)
[any day] → Determine planned working times → DEFTP:
Determination of planned working time (processing type S)
[last day evaluated] → Determine overtime → GOT TO20 01:
Process the time quota
This function compares the overtime pair with the attendance
quota record. It assigns processing type M to the portion of
the time pair that matched the quota record (16:30 to 18:30)
It separates the time pair (18:30 to 19:30) that will not be
compensated because there is no overtime quota assigned.
•
17-09-2004
[last day evaluated] → Select time wage types → GWT M ZML: The
overtime wage types are generated during time wage type selection
for the processing type M.
© 2004 SAP AG. All rights reserved.
281
Unit 5: Time Evaluation With Clock Times
HR311
Lesson Summary
You should now be able to:
•
Name the special requirements for time evaluation with clock times
•
Describe the special features of the TM00 schema
•
Explain the differences in relation to schema TM04
282
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Unit Summary
Unit Summary
You should now be able to:
•
Describe the distribution of tasks between the time recording system
and SAP R/3
•
Name the infotypes required for processing time postings
•
Explain the formation of time pairs from the time postings
•
Explain how time pairs are read into time evaluation
•
Run special error checks for the time pairs
•
Name the special requirements for time evaluation with clock times
•
Describe the special features of the TM00 schema
•
Explain the differences in relation to schema TM04
17-09-2004
© 2004 SAP AG. All rights reserved.
283
Unit Summary
284
HR311
© 2004 SAP AG. All rights reserved.
17-09-2004
Unit 6
Using the Results of Time Evaluation
Unit Overview
In this unit, you learn how you can use the results of time evaluation for other
business processes.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
•
•
•
Describe how time evaluation results are transferred to payroll
Explain the trigger for retroactive accounting without gaps
Describe how time data is processed in SAP Payroll
Explain the structure of a time statement
Set up a time statement
Apply special techniques for customizing the form
Describe the various reporting options for time recording data and time
evaluation results
Use reporting time types and reporting quota types to group time and
labor data that is related from a business point of view
Unit Contents
Lesson: Integration with Payroll................................................... 286
Lesson: Time Statement ........................................................... 295
Exercise 14: Customizing a Time Statement Form ....................... 307
Lesson: Reporting for Time Evaluation .......................................... 313
17-09-2004
© 2004 SAP AG. All rights reserved.
285
Unit 6: Using the Results of Time Evaluation
HR311
Lesson: Integration with Payroll
Lesson Overview
In this lesson, you learn how the time wage types formed in time evaluation
are transferred to payroll. In payroll, they are available for the calculation of
the gross wage.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Describe how time evaluation results are transferred to payroll
Explain the trigger for retroactive accounting without gaps
Describe how time data is processed in SAP Payroll
Business Example
The time wage types formed in time evaluation are transferred to payroll and
valuated there. You also want subsequent changes to the time data and newly
determined time wage types to automatically trigger a retroactive accounting
run in payroll.
286
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Integration with Payroll
Integration with Payroll
Figure 174: Integration Between Time Evaluation and Payroll
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 the TC00 or TC04 schema.
17-09-2004
© 2004 SAP AG. All rights reserved.
287
Unit 6: Using the Results of Time Evaluation
HR311
Figure 175: Time Evaluation Period and Payroll Period
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.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → General Settings → Determine Time
Evaluation Period.
288
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Integration with Payroll
Figure 176: Interaction Between Time Evaluation and Payroll
Payroll performs day processing for the time data for days that have not yet
been processed by time evaluation. Day processing is carried out for the
remaining days in the payroll period on the basis of the planned specifications
and any infotypes that have already been entered. The aim of day processing
in payroll is to select time wage types.
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
The ZL table 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).
17-09-2004
© 2004 SAP AG. All rights reserved.
289
Unit 6: Using the Results of Time Evaluation
HR311
Figure 177: Recalculation
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
The CHECK function must feature in the time evaluation personnel
calculation schema with RPR as the value of parameter 2
Hint: You can use the CHECK function with parameter 3 = MACO to
instruct SAP R/3 to set the matchcode W for a retroactive accounting
run if payroll is running or in the correction phase.
If you run payroll before the end of the payroll period and you use the
MACO switch, this may result in delays in completion of payroll, since
the W matchcode is constantly refilled.
290
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Integration with Payroll
For more information, see the Implementation Guide for Personnel
Administration and choose Customize Procedures → Infotypes → Define Field
Relevant for Retroactive Accounting..
Figure 178: Calling Time Wage Type Selection
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). The XT00 personnel calculation schema is an international
personnel calculation subschema of X000.
The DAYPR function 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, the DAYPR function takes the results of time
evaluation into account.
Additional time-related functions in the gross part of payroll:
•
•
•
•
17-09-2004
Absence valuation (PAB function)
Shift change compensation (X064 personnel calculation rule)
Valuation bases for different payments (PALP function)
Transfer of time data from ZL to IT (ZLIT function)
© 2004 SAP AG. All rights reserved.
291
Unit 6: Using the Results of Time Evaluation
HR311
Figure 179: Day Processing in Schema TC00 or TC04
The steps and rules according to which day processing handles time data in
payroll are set in the TC00 or TC04 schema.
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 the GWT function
as for day processing in RPTIME00.
In payroll, you have the same options as in time evaluation for maintaining
time data in the TIP table and forming your own regulations within day
processing of time data. Only time evaluation functions and operations are
used for day processing. You use the TMOD personnel calculation rule to set
the same groupings for table accesses as in the TM01 schema for initialization.
The option of managing time balances and maintaining quotas is unique to
time evaluation. The POVT function in the TC04 (or TC00) schema 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.
292
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Integration with Payroll
Figure 180: Supplying a Third-Party Payroll System
The ZL table also serves as the interface between time evaluation and a
third-party payroll system.
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. To access the interface toolbox
from the menu, choose Human Resources → Time Management → Administration
→ Environment → Third-Party Payroll.
If the time evaluation period is identical to the payroll period, you can use
the RPTEZL00 report as an alternative method of supplying the third-party
payroll system.
For more information, see the Implementation Guide for Personnel Time
Management and choose Time Evaluation → Integration with Payroll→ Prepare
Payroll Using a Third-Party System.
17-09-2004
© 2004 SAP AG. All rights reserved.
293
Unit 6: Using the Results of Time Evaluation
HR311
Lesson Summary
You should now be able to:
•
Describe how time evaluation results are transferred to payroll
•
Explain the trigger for retroactive accounting without gaps
•
Describe how time data is processed in SAP Payroll
Related Information
For more information about the topics in this lesson, see the SAP Library and
choose: Human Resources → Payroll → Gross Part of Payroll → Time Management
Aspects in Payroll → Integration with Time Management.
294
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Statement
Lesson: Time Statement
Lesson Overview
You use the time statement to inform your employees about the times they
have worked and their time accounts. In this lesson, you learn how to tailor
the time statement to suit your requirements.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Explain the structure of a time statement
Set up a time statement
Apply special techniques for customizing the form
Business Example
You want your employees to receive an overview of the time accounts and
time wage types formed in time evaluation.
Time Statement
Figure 181: The Time Statement - RPTEDT00
17-09-2004
© 2004 SAP AG. All rights reserved.
295
Unit 6: Using the Results of Time Evaluation
HR311
You can use the RPTEDT00 report (Time Statement) to present the time
accounts and time wage types determined by time evaluation in a formatted
layout. The statement creates an overview of the time evaluation results for
each day in a time evaluation period.
To access the time statement from the menu, choose Human Resources → Time
Management → Administration → Time Evaluation → Time Statement.
Time 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 also 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 using the Time Management Form Editor
(transaction PE50). To access the time statement form editor from the menu,
choose Human Resources → Time Management → Administration → Tools →
Form Editor.
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
Figure 182: The Time Statement
296
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Statement
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 the SPRSL feature.
You can assign time statement forms of the TELU form class to a form of the
TEDT form class. 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.
Figure 183: Form Layout
You should always copy an R/3 standard form when you create a time
statement form.
17-09-2004
© 2004 SAP AG. All rights reserved.
297
Unit 6: Using the Results of Time Evaluation
HR311
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.
Figure 184: The Form Editor
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 Input help single fields modeless window.
To insert a field into the form layout, double-click on it.
You can also copy fields or rows. You can create text elements. These are
saved automatically (from the area menu for the form layout, choose Goto
→ Text Modules).
For detailed information on a single field, double-click on the field.
298
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Statement
You can specify the following factors:
•
Output length
You should specify the output 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.
•
Offset
You can hide prefixes (such as the country and plant indicators for cost
centers).
When editing the form, it is helpful if the cursor remains in the place where
you positioned it. You can configure this by setting the SAP R/3 options for
the cursor setting.
1.
2.
3.
4.
5.
17-09-2004
Position the cursor on the color pushbutton on the top right of the R/3
window.
Choose Options.
Choose the Cursor tab page.
Deactivate the Position cursor to end of text field.
Choose OK.
© 2004 SAP AG. All rights reserved.
299
Unit 6: Using the Results of Time Evaluation
HR311
Figure 185: Day Data
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.
Time evaluation forms preliminary day balances if it is ended using the
COLER F operation. In such cases, time evaluation continues evaluating,
but sets a recalculation on that day. You specify the preliminary balances
under the P* page type.
You can display the individual results for each day, with the date and
weekday. You determine the last day of the week in the LDAYW feature.
You use the TP table to output the time pairs or the number of hours for the
following types of time data:
•
•
•
•
•
300
Time pairs (PT table)
Attendances
Absences
Substitutions
On-call duties
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Statement
You use the TEXT field of the TP table 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 the WS group.
Figure 186: Prioritizing the Information Displayed
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 ED and PD groups.
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. Always use either letters
or numbers.
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).
17-09-2004
© 2004 SAP AG. All rights reserved.
301
Unit 6: Using the Results of Time Evaluation
HR311
If, on one day, several items of information exist in the TP table, 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 the FL or LL rules to display it in only the first or last line.
Figure 187: Totals Overview / Time Wage Types per Day
In the LP group (totals overview), you can display time balances in relation to
periods. The system reads the time account statuses from the SALDO table.
In the SCHLW-QUOTAA field, you can display information on an absence
quota, and in the SCHLW-QUOTAP field information on an attendance quota.
In the ZL group, 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.
302
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Statement
If you have a separate line for each time wage type,
•
•
You can display information relevant to cost accounting from tables C1
and ALP beside the time wage type
You can use the RPTEDT00 report (Time Statement) with the Compress
time wage types parameter to display summarized ZL entries for a day.
In this case it is not possible to display information that is relevant for
cost accounting.
Figure 188: Compressing Time Balances and Wage Types
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.
Hint: If you want to save the summarized totals or differences, you
have to add personnel calculation rules to your schema to summarize
the data.
17-09-2004
© 2004 SAP AG. All rights reserved.
303
Unit 6: Using the Results of Time Evaluation
HR311
Figure 189: Additional Groupings for Arranging Information
Figure 190: Converting Output Data
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, and short
and long texts for fields.
304
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Statement
You can also specify the situations in which you want a field to be printed.
An overview of the allowed conversions, rules, and special fields can be found
in the possible entries help.
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 the TEDT form class, you can only use the EQ (equals) relational
operator. If you edit the TELU form class, you can use LT (less than) and
GT (greater than), in addition to EQ.
Figure 191: Creating Text Conversions
In the time statement form, you can output specific texts depending on
variables such as the date, the day evaluated, and so on. This enables you
to display the text of variables such as the day of the week or the pair type
on the time statement.
To do so, you can store text conversions for a field in the form. Text
conversions are all conversions that begin with “T”. Note that only the first
character of a table field can be evaluated.
To create the texts for the text conversions, choose Goto → Text Modules from
the form layout view.
17-09-2004
© 2004 SAP AG. All rights reserved.
305
Unit 6: Using the Results of Time Evaluation
HR311
When weekday texts are displayed, the system reads the last day of the week
(text module W7) from the specifications in the LDAYW feature.
Other common text conversions:
•
•
306
Pair type: TP-PTYPE
Time Management status: WPBP-ZTERF
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Statement
Exercise 14: Customizing a Time Statement
Form
Exercise Objectives
After completing this exercise, you will be able to:
•
Print information from employees’ master data on the time statement
•
Print a time account on the time statement
Business Example
You want to tailor a standard time statement form to suit your enterprise’s
requirements.
Task: Customizing a 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 employee’s
employment percentage and the status of the time-off account Z1## to be
displayed.
17-09-2004
1.
Copy form TF02 to form ZT## (## = your group number).
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.
3.
In the individual results (group ED), replace the planned working time
(time type 0002) with the day balance Z1##.
4.
In the totals overview (group LP), enter the period balance Z1## in an
additional line.
5.
Check your settings by creating a time statement for your employee
311101# for March, 200yy.
© 2004 SAP AG. All rights reserved.
307
Unit 6: Using the Results of Time Evaluation
HR311
Solution 14: Customizing a Time Statement
Form
Task: Customizing a 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 employee’s
employment percentage and the status of the time-off account Z1## to be
displayed.
1.
Copy form TF02 to form ZT## (## = your group number).
a)
b)
In the IMG, choose: Personnel Time Management → Time Evaluation →
Evaluations and the Time Management Pool → Time Statement Form →
Set up the Time Statement Form Using Form Editor → Form Editor.
Enter the name of the form that you want to copy (TF02) and choose
Copy.
A dialog box appears.
c)
d)
Enter the country grouping 10.
In the Form Name field, enter the new name of the form, ZT##.
Continued on next page
308
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Statement
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.
a)
Go to the form layout by selecting the Form Layout field and
choosing Change.
Go from the form layout to the maintenance of the form header
(group HD) by double-clicking window HD.
b)
To display the Employment percentage from the Planned Working Time
infotype (0007), you have to insert a new line:
Place the cursor on the row above the line that you want to insert
and choose New Line.
c)
d)
Enter a dividing line (using AltGr and |), enter the term
Employment Percentage, and choose ENTER to confirm your entry.
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.
Hint: The window may be minimized, in which case you
can select it from the toolbar.
Open the tree to find the Employment Percentage field
(WPBP_EMPCT). Click on the Employment Percentage button.
e)
In window HD, double-click the position where you want the field
to be displayed.
Hint: You should not have the Position Cursor to End of Text
field selected in the Cursor tab page of the options for your
R/3 system.
f)
Exit the maintenance of the form header by choosing Transfer.
Continued on next page
17-09-2004
© 2004 SAP AG. All rights reserved.
309
Unit 6: Using the Results of Time Evaluation
3.
In the individual results (group ED), replace the planned working time
(time type 0002) with the day balance Z1##.
a)
b)
c)
4.
HR311
In the F1 area, double-click to branch to window F1.
Change the column header in group ED by overwriting Plnd with
QAcct.
Replace the planned working time by the time-off account Z1## 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 Z1## (##
= your group number).
In the totals overview (group LP), enter the period balance Z1## in an
additional line.
a)
b)
c)
To do so, scroll in the F1 window to the LP group.
Insert a new row at the end of the group.
To enter the name of period balance Z1##, position the cursor at
the place where you want it to appear, and write the required text
directly.
Enter a dividing line (using AltGr and |).
Confirm your entry by choosing ENTER.
d)
Enter the value of the period balance Z1## by proceeding as
described above.
In the Input help single fields window, choose in block LP under
Time balances per period the field Number of time balances in period
(SALDO-ANZHL).
Double-click to insert the field into the new line.
Set the condition ZTART EQ Z1## (## = your group number).
Confirm your entry by choosing Enter.
Exit maintenance of window F1 by choosing Transfer.
Save your form.
Continued on next page
310
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Time Statement
5.
Check your settings by creating a time statement for your employee
311101# for March, 200yy.
a)
b)
c)
d)
17-09-2004
In the menu, choose Human Resources → Time Management →
Administration → Time Evaluation → Time Statement.
Enter the following data:
Period
03/01/20yy (yy = previous year) 12/31/20yy
Personnel number
311101##
Form name
ZT##
Format form in color
Select this field
Run the time statement
Review your changes in the form.
© 2004 SAP AG. All rights reserved.
311
Unit 6: Using the Results of Time Evaluation
HR311
Lesson Summary
You should now be able to:
•
Explain the structure of a time statement
•
Set up a time statement
•
Apply special techniques for customizing the form
Related Information
For more information about the topics in this lesson, see the SAP Library and
choose: Human Resources → Personnel Time Management → Time Evaluation →
Time Statement Form.
312
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Reporting for Time Evaluation
Lesson: Reporting for Time Evaluation
Lesson Overview
In this lesson, you learn about the various options for reports about time data.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Describe the various reporting options for time recording data and time
evaluation results
Use reporting time types and reporting quota types to group time and
labor data that is related from a business point of view
Business Example
•
•
Management wants to find out the amount of overtime worked in your
enterprise.
Management wants to analyze productivity statistics over various areas
of the enterprise.
Reporting for Time Evaluation
Figure 192: The Time Management Report Tree
The Time Management report tree gives you easy access to the most important
reports in Time Management.
17-09-2004
© 2004 SAP AG. All rights reserved.
313
Unit 6: Using the Results of Time Evaluation
HR311
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 summarize time accounts.
Figure 193: Reporting According to the Data Source
Time management data is stored in the various infotypes and in the B2 cluster
(time evaluation results).
The standard reports enable you to run evaluations over individual data
sources, such as infotype data (for example, the RPTABS20 report) or cluster
data (for example, the RPTBAL00 report), but not for both infotype data and
cluster data simultaneously.
Therefore, the standard reports may often provide only a section of the
relevant data.
314
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Reporting for Time Evaluation
Figure 194: Time Types and Quota Types for Reporting
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.
Hint: You do not form the 00000009 reporting time type (planned time
according to the work schedule) in Customizing. It is hard-coded and is
always filled. If you use the SAP Business Information Warehouse,
it is always transferred.
Depending on employees’ organizational assignments, you can include other
values in the reporting time types and reporting quota types. To do so, maintain
the GRDWT feature for reporting time types, and the GRDWK feature for
reporting quota types.
Simulated infotypes enable you to evaluate data from various sources (infotype
data, time evaluation results (cluster tables ZL with ALP and C1, ZES), and
data from the personal work schedule). The data is not made available from
the various database tables until the evaluation runtime.
17-09-2004
© 2004 SAP AG. All rights reserved.
315
Unit 6: Using the Results of Time Evaluation
HR311
The following simulated infotypes are available:
•
Personal Work Schedule (2500)
The Personal Work Schedule simulated infotype (2500) provides
information from the personal work schedule.
•
Time and Labor Data (2501)
The Time and Labor Data simulated infotype (2501) enables you to use a
reporting time type to create a uniform view on time and labor data from
various Time Management datasets (infotype and cluster data).
•
Quota Statuses (2502)
The Quota Statuses simulated infotype (2502) enables you to use a
reporting quota type to create a uniform view on quota data from various
Time Management data sources.
You can use simulated infotypes for your own ABAP programs and evaluations
using SAP Query, in the same way as standard infotypes.
Hint: 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.
For more information, see the Implementation Guide for Personnel Time
Management and choose Information System → Settings for Reporting.
316
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Reporting for Time Evaluation
Figure 195: Reporting Time Types
Reporting time types (or time types for reporting) provide time and labor data
for evaluations using SAP Query, SAP BW (the SAP Business Information
Warehouse), and for information purposes in the Time Management user
interfaces.
You can use reporting time types to group and summarize time and labor data
from time infotypes, time wage types, and time types according to business
aspects. You can use a reporting time type to group time and labor data from
the following inhomogenous time management datasets:
•
•
•
•
•
•
•
Absences infotype (2001)
Attendances infotype (2002)
Employee Remuneration Information infotype (2010)
Time types (ZES table, cluster B2)
Time wage types (ZL table, cluster B2)
Information about cost assignment (C1 table, cluster B2)
Information about a different payment (ALP table, cluster B2)
The time and labor data is grouped in the reporting time type (REPTT field)
with the number of hours and days. You can also use the reporting time type
to group datasets from one data source (such as subtypes of the Absences
infotype (2001)) to classify the time and labor data at a higher level.
17-09-2004
© 2004 SAP AG. All rights reserved.
317
Unit 6: Using the Results of Time Evaluation
HR311
For more information, see the Implementation Guide for Personnel Time
Management and choose Information System → Settings for Reporting → Time
and Labor Data.
Figure 196: Reporting Quota Types
Reporting quota types (or quota types for reporting) provide time and labor data
for evaluations using SAP Query, SAP BW (the SAP Business Information
Warehouse), and for information purposes in the Time Management user
interfaces.
You can use reporting quota types to group time and labor data that relates to
employees’ attendance and absence entitlements. You can use a reporting quota
type to group data from the following time management infotypes:
•
•
•
Attendance Quotas (2007)
Absence Quotas (2006)
Leave Entitlement (0005)
The attendance and absence entitlements are grouped in the reporting quota
type (QUOTA field) with the number of hours and days. You can also use the
reporting quota type to group datasets from one data source (such as subtypes
of the Absence Quotas infotype (2006)) to classify the absence entitlements
at a higher level.
For more information, see the Implementation Guide for Personnel Time
Management and choose Information System → Settings for Reporting → Quota
Statuses.
318
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Reporting for Time Evaluation
Figure 197: Display Objects for the Time Manager’s Workplace
In the message processing function of the Time Manager’s Workplace, you can
output contextual information from employee master data, reporting time
types, and reporting quota types.
If required, you can also output information from various sources, such as
reporting time types and master data, by arranging display objects into groups.
For more information, see the Implementation Guide for Personnel Time
Management and choose:
•
•
17-09-2004
Time Manager’s Workplace → Basic Settings → Select HR Master Data and
Time Data.
Time Manager’s Workplace → Set Up Message Processing → Create Groups of
Display Objects.
© 2004 SAP AG. All rights reserved.
319
Unit 6: Using the Results of Time Evaluation
HR311
Figure 198: SAP Query for Time Management
Time management InfoSets define a time-management-specific view of the
fields of the logical database PNP. You can use queries to display and evaluate
the fields.
You can use SAP Query to define your own reports quickly and effectively,
without having to do any programming. SAP delivers standard queries,
which you can use as a basis for your own customer-specific queries. The
queries are in the /SAPQUERY/HT user group (time management).
You can use the Time and Labor query to receive an overview of each employee’s
time and labor data, specifying the actual times, the account-relevant time,
and cost assignment information
Hint: Account-relevant time data is counted attendances and absences
that deduct from a quota.
You access the SAP Query from the menu by choosing Tools → ABAP
Workbench → Utilities → SAP Queries → Queries.
320
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Reporting for Time Evaluation
Figure 199: Business Information Warehouse
The SAP Business Information Warehouse (SAP 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. You can enter data summarized in Customizing in the
InfoSources, to output monthly totals, for example.
The InfoSources use the same data structures as the simulated infotypes. This
means that SAP BW provides the same view of data as the SAP Query or
your customer-specific reports.
For more information, see the Implementation Guide and choose Integration
with Other mySAP.com Components → Business Information Warehouse →
Business Content DataSources → Settings for Application-Specific DataSources
→ Human Resources.
17-09-2004
© 2004 SAP AG. All rights reserved.
321
Unit 6: Using the Results of Time Evaluation
HR311
Figure 200: Time Evaluation in the Enterprise Portal
Several Employee Self-Service and Manager Self-Service applications are
available for your enterprise portal that provide your employees and time
administrators/time supervisors with the current input and output of time
evaluation:
•
Employee Self-Service applications
–
–
–
–
•
Time Statement
Time Accounts
Time Accounts
Clock In/Out
Manager Self-Service applications
–
–
Entitlements Nearing Expiry
Attendance Check
The above-mentioned Web applications represent only a selection of the
services currently available. Additional services may be available in future
releases. For up-to-date information, see the SAP Service Market Place under
the alias /hrtime.
322
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Lesson: Reporting for Time Evaluation
Lesson Summary
You should now be able to:
•
Describe the various reporting options for time recording data and time
evaluation results
•
Use reporting time types and reporting quota types to group time and
labor data that is related from a business point of view
Related Information
For more information about the topics in this lesson, see the SAP Library and
choose: Human Resources → Personnel Time Management → Information System.
17-09-2004
© 2004 SAP AG. All rights reserved.
323
Unit Summary
HR311
Unit Summary
You should now be able to:
•
Describe how time evaluation results are transferred to payroll
•
Explain the trigger for retroactive accounting without gaps
•
Describe how time data is processed in SAP Payroll
•
Explain the structure of a time statement
•
Set up a time statement
•
Apply special techniques for customizing the form
•
Describe the various reporting options for time recording data and time
evaluation results
•
Use reporting time types and reporting quota types to group time and
labor data that is related from a business point of view
324
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Course Summary
Course Summary
You should now be able to:
•
•
•
•
•
17-09-2004
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
© 2004 SAP AG. All rights reserved.
325
Course Summary
326
HR311
© 2004 SAP AG. All rights reserved.
17-09-2004
Appendix 1
Functions for Calling Personnel Calculation Rules
Figure 201: Functions for Calling Personnel Calculation Rules
Function ACTIO
The ACTIO function 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
17-09-2004
© 2004 SAP AG. All rights reserved.
327
Appendix 1: Functions for Calling Personnel Calculation Rules
HR311
Function PTIP accesses a personnel calculation rule that processes the content
of the TIP table 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 the COLOP* operation (except for operations that
generate a TIP entry, such as INSTP, GENTG, INSLR, or GENTP).
After all the TIP entries have been processed, the TOP table is converted to
the new TIP.
Function RTIP
Function RTIP accesses a personnel calculation rule that reads the content
of the TIP table according to the rules. The RTIP function works in exactly
the same way as the PTIP function, with the restriction that no changes can
be made to the TIP entries.
Functions PTIPA and RTIPA
The PTIPA and RTIPA functions correspond to the PTIP and RTIP functions
respectively; the only difference is that they are processed only if there is an
absence on the current day.
Hint: The absence must also have an “absence flag.” The flag is
assigned to the absence in the TE21 personnel calculation rule.
For more information, see the documentation for the TFLAG operation.
328
© 2004 SAP AG. All rights reserved.
17-09-2004
Appendix 2
Using Functions and Operations to Process Work Tables
Figure 202: Using Functions and Operations to Process Work Tables
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.
17-09-2004
© 2004 SAP AG. All rights reserved.
329
Appendix 2: Using Functions and Operations to Process Work Tables
330
© 2004 SAP AG. All rights reserved.
HR311
17-09-2004
Appendix 3
Overview: Data Flow During Time Evaluation
Figure 203: Overview: Data Flow During Time Evaluation
The EXPRT function exports the time evaluation results to the database. The
function can be placed at any position in the schema.
17-09-2004
© 2004 SAP AG. All rights reserved.
331
Appendix 3: Overview: Data Flow During Time Evaluation
332
© 2004 SAP AG. All rights reserved.
HR311
17-09-2004
Appendix 4
Tables in Cluster B1
NT1
The NT1 table contains pointers to all time events that have
not yet been processed. It is used for recalculation recognition
and pair formation. The time events themselves are located in
the TEVEN table.
NT2
The NT2 table contains pointers to time events where there
was an error in processing.
17-09-2004
ERT
The ERT tabel contains all messages of the last time evaluation
run.
NCT
The NCT table contains dates for days which require pair
formation to be rerun entirely.
IFT1
The IFT table is used only internally at SAP.
© 2004 SAP AG. All rights reserved.
333
Appendix 4: Tables in Cluster B1
HR311
IFT2
The IFT2 table is the interface table for incentive wages. It
describes the changes made in the WST table (wage types and
other documents) from cluster B2 to the time tickets already
posted in incentive wages.
For more information, see the documentation about Integration
with Logistics → Plant Data Collection in the Posting Time Tickets
to Incentive Wages section.
ST
The ST table contains selected balances that are downloaded
for employees’ information.
QT
The QT table contains a variety of information, which is
redetermined daily, such as:
•
•
334
The date of the last day for which pair formation and
generation was executed
The start and end of planned working time, the public
holiday class, the day type, and the daily work schedule
class of that day
© 2004 SAP AG. All rights reserved.
17-09-2004
Appendix 5
Tables in Cluster B2
Basic data and work schedule
WPBP
The WPBP table contains data about the employee’s work
center and basic pay.
PSP
The PSP table contains the employee’s personal work schedule
data for each day.
Balances, wage types, and quota transactions
17-09-2004
ZES
The ZES table contains the daily balances.
SALDO
The SALDO table contains all cumulated balances. The
balances are cumulated in month-end processing from the TES
table to the SALDO table.
ZKO
The ZKO table stores all quota transactions of the period.
© 2004 SAP AG. All rights reserved.
335
Appendix 5: Tables in Cluster B2
ZL
HR311
The ZL table represents the interface between time evaluation
and payroll. The existing time wage types are a result of time
wage type selection using the Time Wage Type Selection Rule
table (T510S).
The entries in the ZL table contain pointers to the following
tables:
ALP: Different payment
C1: Cost distribution
AB: Absences
The selected time wage types are assigned an IFTYP, which is
an indicator for payroll. It describes the origin of the wage
type:
S: Planned working time
M: Overtime
A: Absence
ALP
The ALP table contains information about a different payment.
C1
The C1 table contains information about a cost distribution
(account assignment).
VS
The VS table contains variable balances which can be
determined individually. The balances can be entered in the
table using the ADDVD operation in time evaluation. They are
then available for customer-specific evaluations.
CVS
The CVS table contains the cumulated balances from the VS
table. The CVS table is filled automatically.
FEHLER
The FEHLER table stores all messages that were generated
within time evaluation.
KNTAG
Relevant for Germany only.
Automatic accrual of absence quotas
336
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Appendix 5: Tables in Cluster B2
QTACC
The QTACC table contains the accrual entitlements that were
generated by time evaluation on the relevant day of the
accrual. You can double-click on a row to display detailed
information about the generation.
QTBASE
The QTBASE table contains information about the base
entitlement on which the calculation of the accrual entitlements
is based. Any changes to the base entitlement within an
accrual period are highlighted.
QTTRANS
The QTTRANS table indicates the status of the transfer pool
for each day. The accrued entitlements are indicated until they
have been transferred to the Absence Quotas infotype (2006)
or until the entitlement has expired.
You can view detailed information about the transfer pool and
the transfer by double-clicking the appropriate row.
URLAN
The URLAN table contains information on the updating of the
Leave Entitlement infotype (0005).
Time pairs and time tickets
PT
The PT table contains the time pairs generated by pair
formation. You require the table only if you use time recording
terminals.
WST
The WST table contains the generated time tickets.
CWST
The CWST table contains the cumulated time tickets.
AT
The AT table is an assignment table that links time pairs and
time tickets.
Time data
17-09-2004
AB
The AB table contains all absences.
ANWES
The ANWES table contains all attendances that were entered
in the Attendances infotype (2002).
VERT
The VERT table contains all substitutions that were entered in
the Substitutions infotype (2003).
RUFB
The RUFB table contains all availabilities that were entered in
the Availabilities infotype (2004).
© 2004 SAP AG. All rights reserved.
337
Appendix 5: Tables in Cluster B2
HR311
MEHR
The MEHR table contains all overtime records that were
entered in the Overtime infotype (2005).
ABWKONTI
The ABWKONTI table contains all absence quotas from the
Absence Quotas infotype (2006) that fulfill one of the following
conditions:
•
•
•
Absence quotas that are valid on at least one day of the
time evaluation period
Absence quotas that are deductible on at least one day
of the time evaluation period and whose validity period
is in the past
Absence quotas that are deductible on at least one day of
the time evaluation period and whose validity-from date
is on at least one day of the current time evaluation period
ANWKONTI
The ANKONTI table contains all attendance approvals from
the Attendance Quotas infotype (2007).
SKO
The SKO table contains all time transfer specifications that
were entered in the Time Transfer Specifications infotype (2012).
Status information
BEZUG
338
This table contains the recalculation data for time evaluation
and the time statement and retroactive accounting data for an
external payroll system.
© 2004 SAP AG. All rights reserved.
17-09-2004
Glossary
Balance
An employee’s time account determined during time evaluation.
Message
Information issued by time evaluation referred to a situation where
postprocessing may be necessary.
Pair type
An indicator used to classify times in time evaluation. The pair type
indicates times at which an employee was at work or absent, and times
for which there is no data.
Planned pair
The time pair automatically generated in time evaluation or in the
processing of time data in payroll according to the start and end of
working time stipulated in the employee’s work schedule.
Planned working time
An employee’s scheduled working time for a specific period. Planned
working time can be defined as a start and end time or as a number of
hours to be worked.
Time account
An account for managing an employee’s working times, absence
times, time credits, and approvals for working times. Laws, collective
agreements, company policy, and company regulations determine which
time accounts must be set up. Time accounts are used, amongst other
things, to:– Monitor time and labor data– Collate statistics– Make working
time more flexible– Satisfy record-keeping responsibilities required by
authorities and employees
Time identifier
Description of time intervals according to their relative position to the
daily work schedule. The time identifier is used in time evaluation and
time data processing in payroll. Time data for a day is divided into
separate periods for further classification. This includes all times in the
daily work schedule, that is, times within the start and end times as well
as before and after the start and end times, break times, and so on. In
time evaluation with clock times, all time intervals in the daily work
schedule are defined using a time identifier. In time evaluation based on
17-09-2004
© 2004 SAP AG. All rights reserved.
339
Glossary
HR311
clock times, all time intervals in the daily work schedule are described
using a time identifier, in time evaluation without clock times, only the
break times are assigned an identifier.
Time Management status
The Time Management status specifies whether an employee’s time and
labor data is valuated in time evaluation and, if so, how. You use the
Time Management status to determine whether an employee’s time data
is valuated in time evaluation, forwarded to Payroll, or processed only
in Payroll.
Time type
Grouping of time and labor data that can be determined in time
evaluation. 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.
Time wage type
A remuneration specification for bonuses, such as overtime or night
bonus, as well as for employees paid by the hour. These primary wage
types are selected in time evaluation, or time data processing in payroll.
They are used in payroll to determine gross pay.
Working week
A regularly repeating sequence of days that can differ from a calendar
week.The work week can start and end on any weekday at any time. It
can be assigned to one employee and used for determining overtime or
managing time accounts, for example.
340
© 2004 SAP AG. All rights reserved.
17-09-2004
Index
A
Absence entitlement, 206
Absence flag, 328
Absence Quotas infotype
(2006), 208–209, 218
Accrual entitlement, 209
Accrual period, 209
Accrual time, 209
Archiving, 34
"As if" principle, 170
Attendance Quotas infotype
(2007), 268
Attendances infotype (2002),
181
B
Balance formation, 187
Balance limit, 193–194
Base entitlement, 209, 214
Base period, 209
C
Class for time evaluation,
143
Constant DELIM, 247
Constant OVERT, 149
Customizing, 63
D
Day balance, 187, 192, 270
Day processing, 116
Day type, 14
Decision operation, 94
Deduction, 215
Display object, 51
Download, 238
17-09-2004
Dynamic assignment of the
daily work schedule, 260
E
Earliest recalculation date, 31
Employee, 5
Employee Self-Service, 322
Enterprise portal, 322
F
Feature HRSIF, 15, 83
Feature QUOMO, 211
Feature WWEEK, 149
Final processing, 116
Forced recalculation, 30
Form class, 296
Function, 65
Function ACTIO, 327
Function BLOCK, 117
Function CHECK, 87
Function CUMBT, 195
Function DAYMO, 165
Function DAYPR, 291
Function DEFTP, 265
Function DPTOL, 261
Function EXPRT, 331
Function GOT, 269
Function GWT, 164, 170, 292
Function IF, 86–87
Function LIMIT, 193–194
Function MOD, 119, 211, 258
Function P2000, 80, 122, 246
Function P2001, 83, 122
Function P2002, 83, 122
Function P2011, 81, 122, 246
Function P2012, 188
© 2004 SAP AG. All rights reserved.
341
Index
HR311
Function PBRKS, 141
Function POVT, 182
Function PTIP, 327
Function PTIPA, 143, 327
Function QUOTA, 212
Function RTIP, 327
Function RTIPA, 327
Function TIMTP, 262
Function TYPES, 138, 187
G
GCY operation, 70
P
H
Pair formation, 242–243
Pair type, 138–139, 264
Payroll period, 288
PCY operation, 70
Personnel calculation rule
MODT, 258
Personnel calculation rule
TD30, 260
Personnel calculation rule
TMON, 119, 165
Personnel calculation rule
TR10, 270
Personnel calculation rule
TR11, 187
Personnel calculation rule
TR30, 192
Personnel subarea grouping
for time recording, 139
Planned pair, 142
Planned Working Time
Infotype (0007), 11
Processing class 17, 182
Processing instructions for a
day, 190–191
Processing method, 51–52
Processing type, 137–139,
152, 169, 264
Processing type/time type
class, 84, 137
Projection for future period,
86
HR documentation
maintenance, 66
I
Implementation Guide, 62
InfoSet, 320
Initialization, 116
Integration with payroll, 287
Interface data, 240
Interface toolbox, 293
Internal Table, 84
M
Manager Self-Service, 322
Master Data Infotype, 10
Maximum daily working
time, 265
Message, 47–48
Message functional area, 50
Message processing, 48
Message Processing, 99
O
Operation, 65
Operation ADDDB, 98
Operation ADDOT, 98
Operation ADDZL, 98
Operation COLER, 99
Operation COLOP, 328
Operation DELIM, 247
342
Operation HRS, 96–97
Operation MODIF, 165, 211
Operation ROUND, 261
Operation VARST, 95
Overtime approval, 267
Overtime Compensation,
181
Overtime compensation
type, 181–182, 268
Overtime determination, 268
© 2004 SAP AG. All rights reserved.
17-09-2004
HR311
Index
Q
T
Quota Corrections Infotype
(2013), 218
Quota Overview, 219
Quota type selection rule
group, 210
Table ALP, 287, 289
Table C1, 287, 289
Table DZL, 84, 329
Table FEHLER, 84
Table PT, 246
Table SALDO, 84, 329
Table T510S, 164
Table T555Y, 138
Table TES, 329
Table TIP, 83–84, 246, 329
Table TOP, 84
Table TZP, 80, 83–84
Table ZL, 84, 287, 289
Table ZML, 84, 329
Time account, 71
Time Administrator, 4
Time evaluation period, 288
Time event, 241–243
Time Events Infotype (2011),
241
Time identifier, 83, 262, 264
Time infotype, 14
Time management form
editor, 296, 298
Time Management
Specialist, 4
Time Management status,
11, 87
Time Manager’s Workplace,
5, 48, 190–191, 319
Time Recording Information
Infotype (0050), 10, 239
Time Recording
Philosophies, 7
Time recording system,
235–237
Time Statement, 296
Time statement form,
297–298, 300–305
Time Supervisor, 4
R
Recalculation, 27
Reduce absences, 143
Reduction rule, 216
Report RPCLSTB2, 33
Report RPTEDT00, 296, 303
Report RPTQTA00, 207
Report RPTQUOTA_CHECK, 213
Reporting quota type, 315,
318–319
Reporting time type, 315,
317, 319
Rounding rule, 217
RPCLSTB1 report, 34
RPTIME00 report, 26, 29
Rule editor, 69–70
Rule group, 166
S
SAP Business Information
Warehouse, 321
SAP Query, 320
Schema editor, 67–68
Schema TC00, 292
Schema TC04, 292
Schema TM00, 257
Schema TQTA, 207
Schema XT00, 291
Simulated infotype, 315
Simulation for future period,
86
Standard schemas, 271
Substitution, 82
17-09-2004
© 2004 SAP AG. All rights reserved.
343
Index
HR311
Time transfer specification,
188–189
Time Transfer Specifications
infotype (2012), 188
Time type, 72–73, 137, 152
Time type determination,
187, 262, 264, 271
Time wage type, 26
Time Wage Type Selection,
167–168
Time wage type selection
rule, 167
Time wage type selection
rule group, 164
Time-off credit, 206
344
© 2004 SAP AG. All rights reserved.
TMW, 5, 48
Tolerances, 261
Transfer time, 209
U
Upload, 237
V
Validity period of absence
quota, 215
Value limit, 193–194
Variable key, 94
W
work schedule, 13
Working week, 149–151
17-09-2004
Feedback
SAP AG has made every effort in the preparation of this course to ensure the
accuracy and completeness of the materials. If you have any corrections or
suggestions for improvement, please record them in the appropriate place in
the course evaluation.
17-09-2004
© 2004 SAP AG. All rights reserved.
345