Time Management data considers information on the work performed by

employees and their availability to work. Time Management in SAP

HR provides you with a flexible means of setting up, recording, and
evaluating working times.
There are two different methods for time management in SAP HR:
• Recording only deviations from the work schedule - Only time data
that represents an exception to the employee's work schedule is
recorded (illnesses, annual leave, substitutions). This method is also
known as Negative time management
• Recording actual times - This method records all actual times
(actual working times, clock-in and clock-out, absences). This method
is also known as Positive time management
Employees’ time data is valuated in time evaluation. Time evaluation
determines planned working times and overtime, creates wage types,
updates time quotas, etc. The time wage types created during time
evaluation are valuated in Payroll.

RPTIME00
RPTIME00 is a time evaluation program. You can execute it
using transaction SA38 or SE38.

Time management status

You determine whether and how an employee is processed in time
evaluation using time management status in Planned Working Time infotype
(IT0007). Following are possible values:
• 0 or blank - No time evaluation (means, that employee’s time data
is not processed by time evaluation, so the time wage types are
formed by Payroll)
• 1 - Evaluation of actual times (means, all of the employee’s times
are recorded, time data is taken from clock-in/out system)
• 9 - Evaluation of planned times
Default values for IT0007
You can use two features to set default values (transaction PE03):
• SCHKZ - Default value for shift indicator
• TMSTA – Default value for Time Management Status
Time management infotypes
Following infotypes are specific for TM. You must remember that for the
integration of time management master data records infotypes IT0001,
IT0002, IT0007 (with appropriate Time Management status set) have to exist
for employee.
You can maintain those infotypes using both transactions PA20 and PA30 or
special for TMPA61
KEY DESCRIPTION
Time Recording Info – used only if time evaluation is used. Contains interface
0050
data for the subsystem and additional employee information for time evaluation.
2001 Absences

2002 Attendances

2003 Substitutions

2005 Overtime

2006 Absence Quotas

2007 Attendance Quotas

2010 Employee Remuneration Info

2011 Time Events

2013 Quota Corrections

2050 Annual Calendar

2051 Monthly Calendar

Work Schedule Configuration

Groupings
Before start of TM configuration you have to define time specific groupings,
both for employee subgroups and personnel subareas.
Firstly you define Personnel Subarea Grouping for Work Schedule and Daily
Work Schedule, which controls whether a work schedule is permitted within
the personnel subareas
Daily Work Schedule
Then you have to define all Daily Work Schedules (DWS) which exist in
your company. DWS describes a working day of employee with start and end
of working time, planned working hours, and scheduled breaks. To define a
day-off we use also appropriate DWS (in attributes a day-off flag is set). You
can also add variants to the daily work schedule, e.g. a shorter version of the
day.
Example:
NORM – DWS for normal office workday 9.00-17.00
1SHT – DWS for 1st shift 6.00-14.00
OFF – DWS for day-off
Period Work Schedule
After you have defined DWS you need to define Period Work
Schedules (PWS). PWS is the work pattern defined using appropriate DWS
set in specific sequence. PWS covers one week or even more weeks (e.g. in
case of shifts) and is the basis for generating a work schedule.
Example:
NORM, NORM, NORM, NORM, NORM, OFF, OFF
Day type
Next step is to define Day types. They determine whether employees must
work on a specific day and whether or not they are paid. Possible values:
• Working and paid day
• Not working but paid day
• Not working and not paid day
• Other, customer specific day
Work Schedule Rules
After the individual elements have been set up for work schedules, you can
start defining Work Schedule Rules (WSR), which contain employees’
average working times. WSR defined based on Day Type Rule and PWS. You
have to indicate the starting point in the PWS, so from which point the WSR
starts on the reference day. You are advised to use a reference date that falls
on a Monday.
NOTE: that one PWS could be used for different work schedule rules in
rotating shifts. To do so, you only have to move the starting point by one
week (starting point 001, 008, and so on).
WSR also need to have specific groupings set.
After you defied WSR, they must be generated for a specific period of time.
You can do this either manually or in batch.
Planned Working Time infotype (IT0007)
The work schedule is assigned to an employee using the work schedule
rule in the Planned Working Time infotype (IT0007). The employee's place in
the enterprise and personnel structure defined in the Organizational
Assignment infotype (IT0001) determines which work schedules can be
assigned to him or her.
Downloaded from website: http://forums.sdn.sap.com/thread.jspa?
threadID=1210886&start=0&tstart=0

The basic difference is , in Negetive time management we record only

the deviations to the set work schedule , for example it is assumed that the
employee will work for 8 hours and given number of days , only his or her
absences are recorded for the purpose of salary calculation accordingly.

But in case of possitive time management , employees movements like

comming to office , going out from office are recorded using the time
machines where the employee swipes his ID card every day, at the end of
a given interval the data is pulled into SAP system and all the related
information of time pairs is updated in relevant infotypes , time evaluation
is run and then the data is processed in payroll

For configuration you can always refer to help.sap.com

Regards
Sameer

i want to know how can we use TM04 both for positive and negative time
management.
and while using it in negative and positive time mangement what is the
time management status set to in 0007.
Sikinder has sent very good threads but this point is not clear to me if u
can tell me in details.
Preeti

You can assign the following Time Management statuses in the Planned
Working Time infotype (0007):

Time evaluation with planned times (0): Employees with this status are not
selected for time evaluation. They cannot therefore be processed in time
evaluation. The employee’s time wage types are determined in Payroll
time data processing.
Time Management Status for processing time data in Time Evaluation and
passing on time wage types formed there to Payroll

Time evaluation of actual times (1) and Time Evaluation PDC (2):
Employees with these statuses have all their actual times, that is, all
attendance and absence data, recorded*. It makes no difference whether
attendance times are recorded at time recording terminals or in the
Attendances infotype (2002).
Time evaluation with planned times (9): These employees have only the
deviations from their work schedule recorded for them. The employees’
planned working times from their personal work schedule are used as the
basis for time evaluation.
Time Management Status for processing time data in Time Evaluation
without passing on time wage types formed there to Payroll

Time evaluation without integration with Payroll (7): You use this status to
run time evaluation to handle special time accounts – to accrue absence
quotas, for example. It makes no difference whether all of the employees’
actual times are recorded or only the deviations from the work schedule.
The system stores the results of this time evaluation run in cluster B2,
which enables you to run reports on the data, for example. The results are
not passed on to Payroll. The time data processing part of Payroll treats
the employees as if they had the time management status No time
evaluation (0).
External services (8): Status for external employees. It makes no
difference whether all of the employees’ actual times are recorded or only
the deviations from the work schedule. The results of time evaluation are
transferred to Materials Management (MM-SRV), and are not passed on to
Payroll.

Positive and negetive time management are two different options that are
available in TM. In Negetive time , we consider the work schedules as
working time and in positve we take the actual timings of the employee.
Here the time in and time out will be considered as time pairs and based
on the considated out put employees working time will be considered.

This is just an overview of positive and negetive time.

But the major difference is with the schemas.

For Posive : TM00 (Time Evaluation with Personnel Time)

For Negetive : TM04 (Time Evaluation Without Clock Times).

You have to maintain these schemas .

Hope you have a clear pciture now.

Regards,
Sri..

https://forums.sdn.sap.com/click.jspa?
searchID=21428115&messageID=6878545
https://forums.sdn.sap.com/click.jspa?
searchID=21428115&messageID=6542681
https://forums.sdn.sap.com/click.jspa?
searchID=21428115&messageID=6868627
https://forums.sdn.sap.com/click.jspa?
searchID=21428115&messageID=6430663

instead of going into Technical way lets have a clear picture hear

- time management here we wont capture any actual deviations i mean

clock in and clock out of the employee which are actual

at the end of the month we upload the data thru LSMW i mean absence we
run the pay roll

if the employee works OVER TIME the end user will caluculate the amount
and gives it in 0015 or we can right the rule

Here we maintains the status as 0 as we dont have time evaluation

if we take same require ment in Positive time management the Clock in

and Clock out will be recorded in the system

and will we Uploaded in the system in infotype 2011 time events and run
the TE so the system will generte the OT amount also

Here we can use time status 7 without integration of PY and time status 9

fisrt understand the basic concepts i will update u the rest

xxxxxx
U made me clear about time management status .
Urs knowledge is no doubt opening doors of my brain.
But mine question is:
1) Time schema TM04 is used why both for positive and negative time
management?
2) while we use
TM04 negative time mangement- what must be time evaluation status in
0007?
TM04 positive time management- what must be time evaluation status be
setted to in 0007?
TM00 Postive time mangement- what must be time evaluation status
setted to in 0007?
Here i am confused.
3) What is BDC and how can we upload data of negative time
management through this.
Preets.

Xxxxx
Time Evaluation is used to evaluate the recorded time datas to run the
time evaluation u need three basic information like master record ,
attendences , absences planned working ime and there are four possible
out pits after the time evaluation
Time wage types ,time accounts messages ,updated quotas
So we need to run time evaluation to get these out put which will be
processed in the pay roll to the payments .
Time evaluation is based on Time Schema

Xxxxxx
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PT/PT.pdf
http://help.sap.com/erp2005_ehp_04/helpdata/EN/54/095faf72f911d1a910
080009ab6b44/content.hthttp://www.insightcp.com/res_16.htm

xxxxx

You cannot use both because this is principal difference between positive
and negative time:

1. In positive: time pairs for normal working time are fromed from Time
Events, e.g. clock in / clock out times.
2. In negative:: time pairs for normal working time are fromed from work
schedule configuration.

So you use either or and not both methods.

If you use negative time, you should register abcense for late comming
(e.g. 30 minutes) then you can analyze it in time evaluation.

If you use CATS you can enter attendance: e.g. 9:30 to 18:00 against
standard 9:00 - 18:00. Then you can overwrite standard working time from
WSR configuration during formation of time pairs.

Cheers!

Xxxxx
Hi Ajay thanks for the thread that have posted its got lot of information.

yes attendance is uploaded to 2002 info type, here we are entering time
data through CATS for workers and we are entering time events 2011 for
staff employees. the difference between workers and staff employees is
overtime.

Can we process all employees through CATS rather than using Time
Events 2011 or shall we use both CATS as well as Time Events. if we use
only CATS then the scenario that i mentioned in my question may not work
i believe. Just confused.

can any one guide me to right way.

Thanks in advance,
Dolly

Xxxxxxx
http://forums.sdn.sap.com/thread.jspa?
threadID=1724683&messageID=9286913#9286913

Here the employee strength is 240 and they don't have the swipe system.
if they want to go with positive time management they have to upload time
data manually in 2011 info type and also they have CATS integrated with
this. All workers time data captured in CAT2 T code and then transferred to
2002 attendance info type.

Scenario :- Employee comes to office 3 times late ( Ex- His in In time is

9.30, he comes at 9.45, 9.47 and 9.50 respectively)

Condition :- His half day salary or half day leave eligibility has to be
deducted.
Here the issue client uses negative time management.

Can this scenario possible through negative time management.

Xxxxx