Time Management - Definitions

Day type
An indicator that a certain calendar day is payment-relevant, that is, an employee is paid
for working that day.
Work schedule
The work schedule defines working time models such as shifts, continuous working
times, or flextime for scheduling working time provisions for workforce or work
processes
Daily Work Schedules
The daily work schedule represents the actual working time for a particular
employee on a given day. It can differ from the employee's agreed daily working time
stipulated in the work contract or collective agreement.
Core time
If employees work flextime, the core time defines the period during which they must be
at work each day.

Planned working time

The planned working time specifies when the employee should start and finish work.
Tolerance time
Daily work schedule tolerances define the period within which a clock-in or clock-out
entry is rounded up or down. They prevent the system from interpreting clock-in/-out
times which are shortly before/after the start or end of planned working time as
overtime or working time violations.
Times are rounded in the personnel calculation schema of RPTIME00 using
functionDPTOL.
Daily Work Schedule Class
The daily work schedule class is a feature used to define daily work schedules. You use it
to create evaluation criteria for a daily work schedule. According to the evaluation
criteria, daily work schedules can be used in differen ways in time wage type selection,
attendance and absence counts, or in time evaluation.
The working times defined in a daily work schedule are not influenced by the
assignment of a daily work schedule class. As a result, the daily work schedule class
respresents an additional evaluation of a daily work schedule.
Daily work schedule classes can be identified by any number between 0 and 9.
Time quota
A time interval during which employees can be at work or absent, under certain
conditions.
Absence quota
An employee's entitlement to absence.
The quota has a limited validity period and is reduced each time an absence of this type
is recorded.
Time type
A grouping of personnel times determined during time evaluation.
Work break schedule
A break schedule includes as many breaks during an employee's planned working time
as you require, and up to four breaks during overtime.
Fixed, dynamic, and variable breaks can be defined in the break schedule. By assigning
the break schedule to a work schedule, you specify the breaks for a given workday.

Dynamic breaks

Dynamic breaks are breaks for which no start/end time is specified in the break
schedule. Instead, a number of hours is stipulated in the After hrs. field. The employee
can take a break after completing this number of hours

Period work schedule

A period work schedule is made up of a sequence of daily work schedules over a
defined period.
Period work schedules can extend over one week, several weeks, or a period that is not
divisible by seven.
Selection Rules
rules according to the public holiday class to specify which day types should be
assigned to public holidays on weekdays and public holidays on weekends.
Planned Working Time
The Planned Working Time infotype (0007) allows you to enter a work
schedule to define individual working times for employees.
Substitutions
Substitutions. Substitutions are planned exceptions to an employee's work schedule
for a defined period of time. Substitutions are treated as planned specifications in time
evaluation.
An employee substitutes for his/her foreman on a particular day; another employee
works a different shift for three days and receives different payment on these days.
Time constraint class
A rule that determines whether collisions in time data are allowed, and if so, specifies
how the system reacts to such collisions.
Time contraints comprise the following:
 Time constraint classes that determine which collisions in time data records are
allowed
 Time constraint table that contains the time-based collisions allowed in the time
data records
 Time constraint indicator that displays whether a new data record that collides
with an existing time data record can be transferred to the system or whether the
transfer is prohibited
Absences
Absences are paid or unpaid planned working times during which the employee has not
worked. They therefore represent an deviation to the employee's work schedule.
Counting Rules
rules for counting attendances and absences. The rules are used to determine the payroll
days and hours for an attendance or absence. The payroll days and hours that have been
counted are used to control the deduction of quotas. They can be used in Payroll to
valuate the absence.
A counting rule can comprise several individual sub-rules. The sub-rules are numbered
sequentially. The system runs through the individual sub-rules until it finds a rule that
applies.
Rounding rule
Specifies how values determined by the system should be rounded.
You can use rounding rules in absence counting or in automatic absence quota accrual.

Plant Data Collection (PDC)

Plant Data Collection (PDC) is the collection and display of operational plant data and
any related information on its processing, preparation, evaluation, and transfer. This
information is used to accumulate required data on machine use, order status, quality,
and so on.
Time Evaluation
Time evaluation evaluates the attendance and absence times that have been recorded for
or by your employees. The system uses the results of time evaluation to form time
balances and time wage types, and to update attendance and absence quotas.
There are three potential evaluation scenarios, depending on the type of data recorded:
1. Only exceptions to the work schedule such as leave or sickness are recorded.
In this case, time data is usually evaluated in payroll.
2. All attendance times are recorded electronically at a front-end time recording
system, not just exceptions to the work schedule. The time data is then uploaded
to the SAP system to be evaluated.
3. As in point 2), all attendance times are recorded, but manually in
the Attendances infotype (2002). You should use this method if cost distribution
data is to be recorded along with the attendance.
Time wage type
A time wage type is a remuneration specification for bonuses, such as overtime or
nighttime bonus, as well as for employees paid by the hour.
These primary wage types are selected in time evaluation or when processing time data
in payroll accounting. They are used in payroll accounting to determine gross pay.

Time Manager's Workplace

The Time Manager's Workplace (TMW) is a user-friendly interface developed for

recording and maintaining enterprise time data. This new interface can be individually
customized to meet your business requirements. Two TMW scenarios, Time
Data and Message Processing, are included in the standard SAP System. Time
administrators can easily toggle between the two scenarios (when assigned to them) to
complete their daily tasks, without leaving the application.

Time event
The time postings stored in the SAP system (such as clock-in and clock-out or start and
end of working time) that employees enter at a time recording terminal.
Time Management - Reports
Work Schedule
RPTPSH10 - Personal Work Schedules
RPTDSH20 - Daily Work Schedules

Attendance
RPTABS20 - Attendance/Absence Data: Overview
RPTABS50 - Attendance/Absence Data: Calendar View
RPTABS60 - Attendance/Absence Data: Multiple Employee View
RPTEAB00 - Attendance Check
RPTLEA40 - Attendances/Absences Overview Graphic

Absence
RPTABS20 - Attendance/Absence Data: Overview
RPTABS50 - Attendance/Absence Data: Calendar View
RPTABS60 - Attendance/Absence Data: Multiple Employee View
RPTLEA40 - Attendances/Absences Overview Graphic

Time Accounts
RPTCMP00 - Time Leveling
RPTEDT00 - The Time Statement
RPTBAL00 - Cumulated Time Evaluation Results: Time Balances and Time Wage
Types
RPTDOW00 - Time Accounts
RPTQTA10 - Displaying Absence Quota Information
RPTERL00 - Displaying Time Evaluation Messages

Time Management - schemas

Schemas:

• Most of the logic in time evaluation is built in Time Management schemas.

• The result of time evaluation are stored mainly in clusters B1 and B2.

• There are also some infotypes which are updated by time evaluation. These infotypes
are:
– Payroll Status infotype (0003)
– Absence Quotas infotype (2006)
– Attendance Quotas infotype (2007)
– Time Events infotype (2011)

• SAP provides the following four standard Time Management schemas, which are
copied and customized to suite business requirements:
TM00 Time Evaluation with Personnel Time Events

TM01 Time Evaluation for Work Schedule Deviations

Time Evaluation for External Services

TM02
Management

TM04 Time Evaluation Without Clock Times

Schema TM00: Time Evaluation with Personnel Time Events

• TM00 is used to form time balances and time wage types from the time data.

• If the employee has recorded their actual times at a Time Recording Terminal, at a
PDC system or via IT2011 (Time Events), then TM00 is the most suitable schema to
work with. Time Pairs are formed, Attendances, Absences are imported and then the
data is evaluated.

• Schema TM00 is based on positive recording of time data, which means recording all
times that count as working time (actual times).

• Schema TM00 only evaluates time data with clock times (or full-day records).

• The main task of schema TM00 is to classify the actual times by comparing them to the
planned specifications in the daily work schedule (start and end of planned working
time, core times, breaks, and so on).

• To determine overtime in schema TM00, time worked before the start of planned
working time or after the end of planned working time is not counted as working time
unless it has been approved. (Schema can also handle a case where Overtime need not
be approved).

• TM00 can calculate Overtime on a daily or weekly basis.

• To determine Flextime in Schema TM00, all times worked between the start and end
of the planned hours is considered. First, we need to meet to requirements for the daily
planned hours. Any excess hours are treated as Flextime.

• For a personnel number to be processed in the TM00 schema, the “Time Management
status” indicator in the Planned Working Time infotype (0007) should be set to 1 (1 –
Time evaluation of actual times).

Schema TM01: Time Evaluation for Work Schedule Deviations

• Schema TM01 evaluates data that has been entered as clock times to record only
exceptions to the work schedule.

• The valuation basis for time evaluation forms a planned pair, which is generated
according to the planned specifications in the employee’s personal work schedule.

• The planned pairs generally correspond to the time worked. Only attendances from
infotype 2002 and absences from infotype 2001 can result in a difference between
planned and actual.

• Schema TM01 automatically generates overtime for all attendance times recorded over
and above the planned specifications in the personal work schedule. If overtime is
recorded in infotype 2005, it can be approved systematically taking account of overtime
breaks.

• The schema TM01 forms time balances, time wage types, and time quotas.

• TM01 is based on negative time recording methodology.

• For a personnel number to be processed in TM01 schema, the “Time Management

status” indicator in the Planned Working Time infotype (0007) should be set to 9 (9 –
Time evaluation of planned times).

Schema TM02: Time Evaluation for External Services Management

• Schema TM02 carries out time evaluation for External Service Providers who record
their hours in the Materials Management module.

• Typically, in the HCM module, TM02 is not implemented.

• For each external employee, Attendance (IT2002) is evaluated and wage-types are
created accordingly.

• For a personnel number to be evaluated in schema TM02, the “Time Management

status” indicator in Planned Working Time infotype 0007 should be set to 8 (8 –
External services).

• Use the standard schemas TM00 or TM04 as you guide if you want to include
additional functions in the schema TM02.
Schema TM04: Time Evaluation without Clock Times

• Schema TM04 is used for the evaluation of time data that is entered online, either in
hours or in pair of actual times.

• This schema evaluates actual working hours as well as exceptions to the work schedule.
The aim is to form time balances and time wage types from the time data.

• TM04 is intended as an alternative to the TM00 schema.

• You can use schema TM04 to process attendances and absences that specify a number
of hours only, rather than concrete start and end times.

• The times stipulated in the daily work schedule are not relevant. Only specifications
such as planned hours and minimum daily working time are evaluated from the daily
work schedule.

• TM04 caters both for negative time recording (recording of exceptions to the work
schedule) and positive time recording (recording all attendances or actual times).

• If negative recording is used, the planned hours are generated on the basis of the daily
work schedule. Recorded absences and some attendance times are deducted.

• Overtime can be calculated using the following regulations:

– Overtime after x hours per day
– Overtime after y hours per week
– Overtime after z consecutive working days in a week
– Overtime recorded in IT2005 will be considered for evaluation

• For a personnel number to be evaluated in schema TM04, the “Time Management

status” indicator in the Planned Working Time infotype (0007) should be set to 1 (Time
Evaluation of actual times) or 9 (Time Evaluation of planned times) depending upon
how the schema is customized.

Time Management - Definitions