Академический Документы
Профессиональный Документы
Культура Документы
R/3 System
Instructor
Guide
Level 3
Release 4.0
(C) SAP AG
ISG.HR
4-1
Contents:
Revisions to Previous Instructor Guide...................................................................3
Course Details.............................................................................................................4
Duration............................................................................................................................................. 4
Course Materials and other Materials (Training Manual)....................................................................4
Country-Specific Units........................................................................................................................ 4
ISG.HR
4-2
Because new topics such as the accrual of absence quotas have been introduced, some topics can no longer
be handled in the same degree of detail.
(C) SAP AG
ISG.HR
4-3
Course Details
Duration
4 days
(C) SAP AG
ISG.HR
4-4
You should be familiar with time evaluation's Customizing tools (personnel calculation schemas and
their editors in particular).
You should understand the interaction between R/3 Time Management and Payroll Accounting. You
should know how data from time recording is imported to time evaluation and payroll accounting and
how it is processed.
A general overview of the options for integrating R/3 Time Management and Cost Accounting (activity
allocation and cost assignment) and an overview of the link to time recording systems is desirable.
Knowledge of Shift Planning is not required, but is desirable.
If the course is held in January or February, you may want to choose another month or maintain data for the
previous year in the first exercise.
(C) SAP AG
ISG.HR
4-5
Training System
Transport from ID3
Data Required
IDES data and additional training data:
## stands for group numbers 00 to 18. You can use group number 00 for demonstrations. Group
numbers 01 - 18 are for the course participants.
Time Management elements from the IMG (work schedules, subtypes and so on) that you display or
use as a template are grouped with country grouping 01.
Note: The absence type 0100 leave is not used in this course, since in the standard system it is only
used for maintaining leave in the Leave Entitlement infotype (0005). As of Release 4.0, users are
advised to maintain leave in the Absence Quotas infotype (2006). You should note that the full range of
functions for automatic accrual of absence quotas is not available until Release 4.5A.
Customers who have already implemented leave in the old form (in the Leave Entitlement infotype
(0005)) can convert to the new form of maintaining leave. There is, however, no method of carrying out
the conversion automatically.
The Leave Entitlement infotype (0005) will not be developed further. Users can, however, continue
using the functions.
Ensure that the table lock is lifted (ENQUEUE OFF), since the course participants work in the IMG
views at the same time for the exercises. Ensure that feature HRSIF is set so that recording absences
and attendances without clock times is possible.
Example ABAPs
None
Technical Hints
(C) SAP AG
ISG.HR
4-6
ISG.HR
4-7
4. The unit The Time Management Pool describes the tool used by the time data administrator to check
the evaluated data and carry out any error handling required.
5. The unit Customizing Time Evaluation describes the range of tools used to customize time evaluation.
The emphasis is on the tools for maintaining personnel calculation schemas and rules, which are a
special feature of time evaluation and payroll accounting.
6. The unit Data Retrieval in Time Evaluation describes how the time data is made available in time
evaluation. The unit has purposely been kept very general in nature and does not refer directly to
schema TM00. It should be clear to the participants that the type of data retrieval depends on the
philosophy behind time data recording and the method of time data recording.
7. The unit Operations as Tools of Time Evaluation describes the use of operations in time evaluation. The
participants are shown how to use the documentation to find out about working with the operations.
8. The unit Personnel Calculation Schema TM00 describes the individual processing steps of time
evaluation in schema TM00. The unit is divided into several sections which correspond to the different
blocks in the schema.
The unit only deals with the processing steps that are of particular significance in a business context or
provide good examples of how to modify personnel calculation rules.
9. The unit Special Solutions describes some sample solutions for representing specific business
requirements. Some of these solutions may relate specifically to Germany; you may therefore want to
leave out some of these slides.
10. The unit Alternative Time Evaluation Schemas describes the standard schemas TM01 and TM04, in
particular how they differ from schema TM00.
11. The unit Integration With Payroll Accounting describes how the wage types determined in time
evaluation can go on for further processing in payroll accounting. You should place particular emphasis
on the following features of integration:
Processing time data in payroll accounting for periods that have not yet been evaluated
12. The unit The Time Statement Form describes the tools and steps for setting up the time statement form.
(C) SAP AG
ISG.HR
4-8
10:00-10:30
Organizational details
Unit: Introduction
10:30-11:00
Instructor: Explanation
11:00-11:45
11:45-12:00
Coffee break
Break
12:00-12:30
Participants: Exercise
12:30-13:30
Lunch break
Break
13:30-14:30
14:30-15:00
Participants: Exercise
14:30-15:00
Coffee break
Break
15:30-16:05
16:05-16:30
Participants: Exercise
16:30-17:00
(C) SAP AG
ISG.HR
4-9
Approx. 30 minutes
Introduce yourself
Give a summary of what is covered in the course (short explanation of the individual
units)
Ask the participants to introduce themselves
Organizational details (times, breaks, and so on)
(C) SAP AG
ISG.HR
4-10
How tasks are distributed between the time recording system and the R/3
System
Overview of the Master Data Infotypes; The Planned Working Time Infotype
Explain that a mini master (infotypes 0001, 0002, 0007, and 0050) must be
created for each employee before he or she can take part in time evaluation.
Explain the significance of the Planned Working Time infotype (0007), in
particular the relationship of the time recording status to the time evaluation
philosophies. Explain the concept of the working week. Demonstrate the
Planned Working Time infotype (0007) in the R/3 System.
Work Schedule; What is a Workday?
The participants should already be familiar with the concept of the work
schedule from HR306. Go over the concept again if necessary. Explain the
meaning of the terms daily work schedule and day type. Note that the meaning of
daily work schedule class 0 has been redefined for Release 4.5A, and a day off is
recognized by the fact that the relevant daily work schedule specifies zero
planned hours.
Overview of Time Management Infotypes; Absences and Attendances:
Clock Times or Hours?
Explain the different categories of time infotypes. Explain how the decision as to
whether time evaluation is performed with or without clock times is made using
feature HRSIF.
(C) SAP AG
ISG.HR
4-11
How the time events are passed on to the Time Events infotype (2011)
(C) SAP AG
ISG.HR
4-12
Which results are provided by time evaluation and how to access them
First explain how time evaluation is carried out and for whom:
Time evaluation is generally run once daily (during the night as a
background job) for a large number of employees. The results of that day are
then available the next morning.
Time evaluation can also be run for individual employees for a given period,
for example, for test purposes.
Mention the types of results again (messages, time wage types and time
accounts, infotype updates).
Next, explain that the results of time evaluation are usually stored for a
month at a time and that the time evaluation period is the same for all
employees. There are technical reasons for the monthly periodicity used by
the database: customers can, however, use a time evaluation period of their
choice.
Time evaluation ensures that there are no gaps in the evaluation run; you can
only run time evaluation for a given day if the previous day has been
correctly evaluated. This is controlled by the PDC recalculation field in the
Payroll Status infotype (0003). If a recalculation is performed, the previous
results are overwritten.
(C) SAP AG
Based on the data flow, explain which data is required by time evaluation
and which results are generated. The previous results are required in order to
ISG.HR
4-13
When the time events are uploaded from the time recording system. This is
not recommended for performance reasons, however.
Important: An attendance check can be carried out before pair formation or time
evaluation (RPTIME00).
In special situations, the customer can intervene in pair formation by
determining fixed processing statuses in the PDC Processing Statuses view
(V_T705B). Show the participants the view in the R/3 System if required.
Starting Time Evaluation
Show the RPTIME00 selection screen in the R/3 System.
First Day to be Evaluated; Recalculation Trigger
The first day to be evaluated is determined by the R/3 System.
A recalculation for periods that are no longer allowed to be evaluated can be
prevented by setting the earliest recalculation date. The earliest recalculation
date is usually set for groups of employees using the Earliest Recalculation
Dates for Time Management view (V_T569R). If the Personal earliest
recalculation date for time evaluation field is set for an employee in the Payroll
Status infotype (0003) and specifies a later date that in the view, the later date
has priority.
The field is set when cluster B2 is archived.
Important Results of Time Evaluation; Displaying the Results of Time
Evaluation; How Were the Results Achieved?
Show the participants the cluster report RPCLSTB2 so that they can see the
complete results of a time evaluation run.
Explain the meaning of the time evaluation log and how to use the log, referring
to an example in the R/3 System. Show the participants how to access the time
statement form from the time evaluation log.
Managing Time Accounts
Explain to the participants what time accounts are by pointing out the similarity
of running a time account to running a current account.
(C) SAP AG
ISG.HR
4-14
The participants should learn how to use the functions of the Time
Management pool, in particular the error handling function.
(C) SAP AG
ISG.HR
4-15
Time types
How tables, schemas, and personnel calculation rules are interrelated in time
evaluation
ISG.HR
4-16
(C) SAP AG
ISG.HR
4-17
09:00-09:15
Instructor: Explanation
09:15-09:30
09:30-09:45
Participants: Exercise
09:45-11:00
11:00-11:15
Coffee break
Break
11:15-12:00
12:00-12:30
Participants: Exercise
12:30-13:30
Lunch break
Break
13:30-14:00
Exercise: Accruing a
Compensation Time Account
Participants: Exercise
15:25-15:45
Coffee break
Break
15:45-16:30
Participants: Exercise
(C) SAP AG
ISG.HR
4-18
Importing Data
Make sure you point out that the planned specifications are loaded either by
function P2000 or by function P2011, according to the time evaluation
philosophy.
Function P2000: ...
Explain how the internal table TZP is built up from the daily work schedule.
Demonstrate in particular how table TZP is read, that is, how the different
sections of the daily work schedule are depicted in table TZP.
Function P2011:...
Point out that function P2011 covers all the functionality of function P2000.
Function P2011 can also import the actual times from table PT (cluster B2) to
the internal table TIP.
Explain table TIP. Use an example from the R/3 System to show which of the
fields in table TIP are filled at this stage. Also show the participants table TZP.
Processing Using Internal Tables
Explain the TIP-TOP principle. Bring in operation COLOP* at this point.
ISG.HR
4-19
the pointers C1 and ALP. Show a relevant example in the R/3 System.
Processing Attendance and Absence Reasons
You are recommended to introduce personnel calculation rule TD80 using an
example from the R/3 System.
Locked attendance/absence records are created because the system assumes that
the generated attendance/absence must still be approved (that is, unlocked) by
the time data administrator. The records are unlocked using the Time
Management pool, for example.
Dynamic Daily Work Schedule Assignment: Rule TD30
You can illustrate the problems by showing an example in the R/3 System.
Important: If the daily work schedule is assigned dynamically, a record is not
generated in the Substitutions infotype (2003). This must be done by the time
data administrator. The daily work schedule that has been assigned can be seen
from the time evaluation log or from table PSP (Personal Work Schedule) in
cluster B2.
Evaluation and Simulation of Future Time Data; Data Retrieval in Schema
TM00
Data retrieval for Simulation of future times is equivalent to data retrieval for
Recording work schedule deviations (compare unit Alternative Time Evaluation
Schemas. Demonstrate schema TM00 in the R/3 System, if necessary.
Selection Using the Time Management Status
Use RPDSYS00 to show other parameter settings for function CHECK. Also
explain the differences to function IF.
(C) SAP AG
ISG.HR
4-20
Initialization
(C) SAP AG
ISG.HR
4-21
Note
The unit follows the same sequence as the processing steps in the schema. The best approach is to show the
individual processing steps on slides and then live in the R/3 System. You can also show the participants
how to read the time evaluation log.
The participants should learn:
The significance of the basic processing steps in time evaluation and how
they work
How the standard schema TM00 and the standard personnel calculation rules
can be modified to cater to different business requirements
ISG.HR
4-22
ISG.HR
4-23
You may want to show an example in the R/3 System to illustrate how the
entries in TIP is split.
Processing Breaks: Definition of Work Break Schedules; Evaluating Break
Periods; Opening Break Frames: Function PBRKS
If only break schedules without variable breaks require processing, function
TIMTP determines the correct positions for the break. Therefore customers who
do not implement variable breaks do not need to use function PBRKS.
If break schedules with variable breaks require processing, however, function
PBRKS provides all the necessary information on the position of the breaks.
The utility time type 0000 is assigned to all times of the TIP entries flagged
as A and P that became S
The utility time type 0001 is only assigned to the times of the TIP entries
flagged as P that became S
The utility time types 0000 and 0001 are used when overtime is determined. This
ensures that overtime is only generated once the planned working hours for a
day are completed.
Use an example to show how TIP is updated by functions TIMTP, PBRKS, and
DEFTP in turn.
Reducing Absences: Rule TP10
Personnel calculation rule TP10 is particularly relevant to flextime models. The
absence is shortened in table TIP and can therefore only be used within time
evaluation.
If the participants are interested in the technical aspects, you may want to
explain the personnel calculation rule in detail.
The utility time type 0000, which is used in rule TP10, contains all times in the
TIP entries for processing type S. The time type is built up in the schema using
personnel calculation rule TP09.
If required, show an example in the R/3 System.
Exercise: Break Processing
Approx. 30 minutes
This exercise gives the participants a better understanding of the business
background to the complexity of function PBRKS.
(C) SAP AG
ISG.HR
4-24
09:00-09:15
Instructor: Explanation
09:15-10:00
Participants: Exercise
Coffee break
Break
11:05-11:45
Participants: Exercise
11:45-12:30
Lunch break
13:30-14:15
Participants: Exercise
15:00-15:20
Coffee break
Break
15:20-17.00
Overtime determination
(C) SAP AG
ISG.HR
4-25
Balance formation
You do not need to show the personnel calculation rules in detail. If the
participants request it, however, you can show them personnel calculation rule
TO16.
Attendance Quotas (Infotype 2007); Determining Overtime: Function GOT
You should use an example in the R/3 System to demonstrate the process of
determining overtime with the approval procedure using attendance quotas. Pay
special attention to the Attendance Quotas infotype (2007).
It is not necessary to discuss personnel calculation rule TO20 in detail.
Significance of the Processing Type and the Time Type
Point out that only now does TIP contain all information (time type and
processing type) required to trigger time wage type selection and balance
formation. Only now are all times in TIP classified.
Time Wage Type Selection; Time Wage Type Selection Rule Group; Time
Wage Type Selection: Function DAYMO; Principle of the Rule Group: An
Example from Time Wage Type Selection
Explain the principle of time wage type selection.
For each relevant rule specified in the Time Wage Type Selection view, the whole
of TIP is run through to check whether the conditions for the time wage type
selection rule are fulfilled and whether the wage type should be generated. The
relevant rules are defined using the rule group.
The principle of the rule group is an important concept in time evaluation; it
comes up again when discussing functions LIMIT and QUOTA.
For time wage type selection, the rule group is defined using the time wage type
selection rule and the day grouping. The time wage type selection rule is the
main element; the day grouping is used to improve system performance. It
makes a finer distinction between the rules which are grouped according to
(C) SAP AG
ISG.HR
4-26
organizational aspects.
Time Wage Type Selection: Structure of a Rule (1), (2)
Demonstrate the Time Wage Type Selection view in the R/3 System and explain
it to the participants. Make sure they understand the concept of the check strings.
Point out that the EXIT rules should only be used in exceptional cases.
You may want to use an example to show how time wage types are formed for
an employee. Also show the participants the time evaluation log for time wage
type selection.
Selecting Time Wage Types: Function GWT
Explain the case for carrying out time wage type selection for absences during
time evaluation (as if principle). Demonstrate the Absence Valuation Rule
view (V_554C_E) in the R/3 System.
Exercise: Processing Special Times
Approx. 40 minutes
(C) SAP AG
ISG.HR
4-27
ISG.HR
4-28
09:00-09:30
Instructor: Explanation
09:30-09:45
Instructor: Explanation
Exercise: Accruing a
Compensation Time Account
Participants: Exercise
10:30-11:00
Instructor: Explanation
(C) SAP AG
ISG.HR
4-29
11:00-11:15
Coffee break
Break
11:15-12:00
Instructor: Explanation
12:00-12:30
Instructor: Explanation
12:30-13:30
Lunch break
13:30-14:15
14:15-14:30
Coffee break
Break
14:30-15:00
Participants: Exercise
Final processing
Final Processing
Mention that function LIMIT can also be used in final processing. If LIMIT is
used, only regulations relating to the period end are processed, for example,
compensation of the flextime balance.
Overview: Data Flow During Time Evaluation; Using Functions and
Operations to Process Work Tables
You can use these two slides to revise the technical process of time evaluation.
You can also show the slides when revising day three.
Exercise: Automatic Accrual of a Compensation Time Quota
Approx. 45 minutes
(C) SAP AG
ISG.HR
4-30
ISG.HR
4-31
Time evaluation schema TM04 for Time evaluation without clock times
The aim is to point out the special features of the different schemas and to view the differences to schema
TM00.
The participants should
Learn about the special features of schemas TM01 and TM04
(C) SAP AG
ISG.HR
4-32
ISG.HR
4-33
If customers also want to evaluate breaks for TIP entries without clock times,
functions PBRKS can also be accessed twice in the schema.
Determining Overtime
Only mention the special methods for determining overtime and the business
requirements that are catered to in the individual subschemas.
Balance Formation: Rule TR11; Balance Formation and Time Type
Determination (TM04)
Balance formation is technically identical to TM00.
Note:
Schema TM01 for Time evaluation for work schedule deviations is generally directed to the interests of the
participants. The special business requirements catered to by schema TM04 for Time evaluation without
clock times are not relevant in some countries, in which case you can adjust the coverage of TM04
accordingly.
Retroactive accounting
ISG.HR
4-34
(C) SAP AG
ISG.HR
4-35
Form Layout
In the Totals overview block, the predefined sequence of blocks is fixed and
cannot be modified by the customer. At this point, you should use RPTEDT00 to
show the standard time statement form TF02 for a specific employee and explain
the layout of the form. If necessary, also explain the selection screen for
RPTEDT00.
Form Layout: Header Data; Day Data, Weekly Total; Totals Overview
Refer to the Implementation Guide for an overview of the fields that can be
displayed in the individual blocks.
Provisional balances can be displayed if time evaluation has been cancelled
using operation COLER. In this case, the time evaluation run is completed
(provisionally) and the provisional balances are displayed under the page type
P*.
Point out that time types can also be entered for time statement forms in the
Wage type field in view V_T512Q.
Prioritizing the Displayed Information
This method is used to determine which of the items of information for a day
should have priority on the time statement form.
Compressing Time Balances and Wage Types
Explain that the summarized time types and time wage types are only available
temporarily for the time statement form. If the time types and time wage types
are also to be available on the database, they must be determined in personnel
calculation rules in the schema.
Formatting Output Data; Special Conversions; Special Fields and Texts
Point out that, as well as the position and length, the following can be specified
on the time statement form for each field being displayed:
An overview of the allowed conversions, rules, and special fields can be found
in the Implementation Guide. It is not possible here to create customer-specific
(C) SAP AG
ISG.HR
4-36
(C) SAP AG
ISG.HR
4-37