Professional Documents
Culture Documents
TM Configuration
TM Configuration
1.0 Purpose.............................................................................................................
2.0 Preparation.......................................................................................................
2.1 Prerequisites..................................................................................................
3.0 Configuration....................................................................................................
3.1 EHRMS-UNITEN Customizing Settings.........................................................
3.1.1 Work Schedules.......................................................................................
3.1.1.1 Define Public Holiday Classes...............................................................
3.1.1.2 Personnel Subarea Groupings...............................................................
3.1.1.2.2 Group Personnel Subarea for the Daily Work Schedule ..............
3.1.1.3 Daily Work Schedules............................................................................
3.1.1.3.1 Define Break Schedules...................................................................
2|Page
3.1.2.2.1.6..................................Define Indicators for the Personal Calendar
76
3.1.2.3 Attendance/Actual Working Times......................................................
3|Page
3.1.2.6.3.2.3................................. Determine Validity and Deduction Periods
113
4|Page
Time Management Module
1.0 Purpose
This document explains the various steps involved in configuration of Time
Management Module for EHRMS-UNITEN Phase II project. The steps
stated below are in IMG menu path order for easy reference and to
document areas of configuration done in Development client 130
(TNB system) for the above mention project.
2.0 Preparation
2.1 Prerequisites
Before you start configuring, you are require to complete user
requirement workshop and finalize business blueprint. As part of the
EHRMS implementation for UNITEN, a workshop was held on 8th
September 2009 to gather user requirement.
5|Page
3.0 Configuration
3.1 EHRMS-UNITEN Customizing Settings
Please refer to TNB document server path:
Daily Work Schedule (for days off) Day Off / Rest Day
Planned Hours 0.0 hours per day
6|Page
(2001), Attendances (2002) and
Substitutions (2003).
EHRMS Settings
UNITEN will use the same public holiday calendar settings, hence no
config changes was made.
Procedure
Screenshot
7|Page
Important note for customizing:
The public holiday calendar is not updated automatically when you make
changes to the Customizing settings. All changes made within the public
holiday calendar must be transported manually. Use your own transport
connection and take note of the information you receive when the public
holiday calendar is transported.
8|Page
3.1.1.2 Personnel Subarea Groupings
You can use personnel subarea groupings to group your employees for
work schedule rules.
EHRMS Settings
TNB use value 14 for Personnel Subarea Grouping for Work schedule and
existing U001 & U002 will remain as it is (no change). To differentiate
between TNB and UNITEN processing, a new Personnel Subarea grouping
50 is assigned for UNITEN. Table V_001P was configured with 3 new
additional Personnel Area UR01, UT01 and UT02. All the Personnel
Subarea under theses personnel area are tagged to Personnel Subarea
grouping 50 for Work Schedule. Created 33 entries for UNITEN.
Procedure
Screenshot
9|Page
3.1.1.2.2 Group Personnel Subarea for the Daily Work
Schedule
In this step, you define daily work schedules for your enterprise. By
entering the planned working time, the system calculates the planned
hours for one day, taking the break schedule into consideration.
EHRMS Settings
Procedure
10 | P a g e
Transaction Code SPRO
2. Make the following entry:
(a) (b)
PS grouping DWS
grouping
50 50
a) Enter Personnel Subarea grouping assigned to UNITEN.
b) Assign daily work schedules grouping 50 for UNITEN.
3. Result:
Record created.
Screenshot
EHRMS Settings
TNBs work break schedule is assigned to grouping 14. For UNITEN (UR01,
UT01 and UT02) a new work break schedule, LUNF and LUNC was
created. Hence Table T508Z was configured with a new additiDWS
11 | P a g e
grouping = 50 is tagged to work break schedule LUNF (12:30 to 14:30 -
unpaid) and LUNC (13:00 to 14:00 - unpaid).
Procedure
Screenshot
12 | P a g e
Important note for customizing:
You can assign a work break schedule to several daily work schedules.
If you change a break schedule after it has been assigned to daily work
schedules, you must revaluate the daily work schedules in most cases.
Procedure
Screenshot
13 | P a g e
3.1.1.3.2 Define Rules for Variants
In this step, you can define rules for daily work schedules. The rules allow
you to stipulate that a variant of the daily work schedule should apply on
certain days. Taking the following parameters into account, you can set up
rules for daily work schedule variants:
EHRMS Settings
Procedure
14 | P a g e
2. No config change to current settings.
Screenshot
You also define daily work schedules for availability in this step. For more
information, see Determine Daily Work Schedules for Availability.
EHRMS Settings
Unlike TNB, Uniten has only seven different daily Work Schedule. Table
V_T550A was configured additional 7 new DWS; Afternoon Shift-UTN
(AF90), Morning Shift-UTN (MO90), Night Shift-UTN (NG90), UTN Normal
Friday (NOFR), UTN Normal (NORM), Off Day (OFFD) and Rest Day (REST).
Procedure
15 | P a g e
1. Access the activity using one of the following navigation options:
IMG Menu Path Time Management Work Schedules Daily
Work Schedule Define Daily Work Schedules
Transaction Code SPRO
2. Make the following entry:
(a) (b) (b) (c) (d) (e) (f)
DWS Daily Daily work Plann Plann DWS Daily
groupi work schedule ed ed selecti WS
ng schedul text worki worki on rule class
e ng ng
hours time
50 AF90 Aftn Shift- 8.00 15:00 5 2
UTN
23:00
50 M090 Morn Shift- 8.00 07:00 5 1
UTN
15:00
50 NG90 Nght Shift- 8.00 23:00 5 3
UTN
07:00
50 NOFR UTN Normal 7.00 08:00 1
Fri
17:00
50 NORM UTN Normal 8.25 08:00 1
17:15
50 OFFD Off Day 0.00 1
16 | P a g e
Screenshot
17 | P a g e
Important note for customizing:
The values for PS grouping and DWS grouping should be equivalent!
If you choose different values for PS grouping and DWS grouping, you need to
match this new combination of values in IMG Group Personnel Sub-areas for the
Daily Work Schedule.
EHRMS Settings
UNITENs has two type of period work schedule, normal and shift.
Employees on a certain shift work for 7 days in a row due to unpredictable
works chedule. UNITENs timesheet clerk will use infotype 2003
substitution to change the days to rest day or off day. Table T551A
was configured additional 4 new PWS for the first week from Monday
through Sunday from 11:00pm to 7.00am (daily work schedule NG90) as
the starting point. In the second week, they work from Monday to Sunday
from 7:00am.to 3:00pm (daily work schedule MO90) and the thrid week,
they work from Monday to Sunday from 3:00pm to 11:00pm (daily work
schedule AF90).
Procedure
18 | P a g e
2. Make the following entry:
(a) (b) (b) (c) (d) (d) (d) (d) (d) (d) (d)
DW PW Period Wee 01 02 03 04 05 06 07
S S WS k
grp text
.
50 3SHF 3-Shift 001 NG90 NG90 NG90 NG90 NG90 NG90 NG90
UTN
50 3SHF 3-Shift 002 AF90 AF90 AF90 AF90 AF90 AF90 AF90
UTN
50 3SHF 3-Shift 003 MO90 MO90 MO90 MO90 MO90 MO90 MO90
UTN
50 NOR UTN 001 NOR NOR NOR NOR NOR NOR NOR
M Normal M M M M M M M
a) Enter 50 for the personnel subarea grouping for daily work schedules.
b) Enter a name and a long text for the period work schedule.
c) Enter the number of the week in the Week number field. Number the weeks
sequentially if the period work schedule is for several weeks.
d) Enter the names of your daily work schedules in the 01 to 07 fields (e.g.
daily work schedule NG90 under 01). The numbers 01 to 07 stand for
Monday to Sunday.
3. Result:
Record created.
Screenshot
If the number of days in a period is not divisible by seven, indicate the end
of the period by entering * in the relevant column for daily work
schedules.
19 | P a g e
If you create additional period work schedules at a later stage, please
define the counting class for valuating absences.
If you use the SAP time evaluation or payroll components, you should also
define the valuation class of the period work schedule for wage type
generation.
EHRMS Settings
All holidays assigned to public holiday classes 1 which is paid days off
and public holiday classes 2 for non-paid days off. These public holidays
are allocated to day type 1 which means "off/paid" and day type 2 which
means "off/unpaid". Public holidays with class 3 is assigned to day type 3
which means "off/special". No changes to current Table T553T. UNITEN will
follow TNBs setting, day type 1 for "off/paid" and day type 2 for
"off/unpaid".
Procedure
Screenshot
20 | P a g e
3.1.1.5.2 Define Selection Rules
In this step, you set 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.
EHRMS Settings
TNB uses rule 14 for day types where else UNITEN have been assigned to
rule 50. Hence table T553A was added with a new rule.
Procedure
Screenshot
21 | P a g e
3.1.1.5.3 Define Special Days
In this step, you can assign day types to special days or bridge days on a
fixed date.
By assigning a special day type to a particular day, you can define special
days on which employees do not have to work for individual work
schedules or individual employee groupings and personnel subarea
groupings.
You can create a link to one or more work schedule rules/work schedules
by means of a link between a special day and a selection rule for day
types.
EHRMS Settings
This Day types for special day is not use by TNB and UNITEN. No changes
to current Table T553S.
Procedure
22 | P a g e
2. No changes to current settings
Screenshot
Work schedules are not stored all at once, but stored for each month. The
work schedule is created regardless of the length of the period work
schedule and is not person-specific.
EHRMS Settings
TNB and UNITEN employees are tagged to work schedule grouping 2 for
salaried staff. Table V_503_D was configured with additional new values to
cater for UNITEN. New employee group (X,Y,Z) and New employee
subgroup (3U - 3X and 2H - 2K) was added and tagged to work schedule
grouping 2 for salaried staff.
Procedure
23 | P a g e
1. Access the activity using one of the following navigation options:
IMG Menu Path Time Management Work Schedules Work
Schedule Rules and Work Schedule Define
Employee Subgroup Groupings
Transaction Code SPRO
2. For UNITEN select Employee Subgroup grouping 2 (salaried staff).
3. Select country grouping 14.
4. Enter the Employee Subgroups grouping for Work Schedules in the
Employee subgroup grouping field.
Make the following entries:
Screenshot
24 | P a g e
3.1.1.6.2 Define Groupings for the Public Holiday Calendar
In this step, you define the personnel area and personnel sub-area
grouping for the public holiday calendar. This allows you to assign a
unique public holiday calendar to a personnel area or personnel sub-area.
EHRMS Settings
25 | P a g e
TNB personnel area and personnel sub-area grouping for the public
holiday calendar is tagged by states. UNITENs personnel area UR01 and
UT01 and personnel sub-area grouping for the public holiday calendar is
tagged to ZS (selangor state) while personnel area UT02 and personnel
sub-area grouping for the public holiday calendar is tagged to ZC (pahang
state). Table V_001P_M was configured with personnel area UR01, UT01
and UT02 accordingly.
Procedure
Screenshot
26 | P a g e
Important note for customizing:
EHRMS Settings
UNITEN has two types of work schedule rule, one for shift and the other
normal. Table V_T508A was configured with work schedule rule GRP0A,
GRP0B, GRP0C for shift and NORMAL. Work schedule rule GRP0A start
point in period work schedule is set to 015, GRP0B set to 008 and GRP0C
set to 001. The employee subgroup and personnel sub-area groupings for
work schedules and the public holiday calendar are tagged according.
Procedure
27 | P a g e
)E Hol PS WS Start End Perio Ref. Start Rule
Sg . g rule Date Date d date for point for
Cal work PWS in day
. ID sche PWS type
d. s
2 ZS 50 GRP0A 01.01.19 31.12.99 3SHF 01.01.19 015 50
90 99 00
2 ZS 50 GRP0B 01.01.19 31.12.99 3SHF 01.01.19 008 50
90 99 00
2 ZS 50 GRP0C 01.01.19 31.12.99 3SHF 01.01.19 001 50
90 99 00
2 ZS 50 NORMA 01.01.19 31.12.99 NOR 01.01.19 001 50
L 90 99 M 00
2 ZC 50 GRP0A 01.01.19 31.12.99 3SHF 01.01.19 015 50
90 99 00
2 ZC 50 GRP0B 01.01.19 31.12.99 3SHF 01.01.19 008 50
90 99 00
2 ZC 50 GRP0C 01.01.19 31.12.99 3SHF 01.01.19 001 50
90 99 00
2 ZC 50 NORMA 01.01.19 31.12.99 NOR 01.01.19 001 50
L 90 99 M 00
All values concerning the block working time are just for statistic
purposes. Proper Values are e.g.:
Daily working hours 8.00 Monthly working hours 173.00
Weekly working 40.00 Annual working hours 2080.00
hours
Weekly workdays 5.00 Addnl monthly hours
a) Select Esg grouping 2 for salaried staff
b) Select Holiday Calendar ID ZS and ZC for UNITEN.
c) Select PS Grouping 50 for UNITEN.
d) Select UNITEN WS rule.
e) Check/set the start and end date.
f) Select UNITEN Period WS.
g) Enter Ref. Date for PWS.
h) Enter start point in PWS.
i) Select UNITEN rule for the day types.
3. Result:
Record created.
Screenshot
28 | P a g e
Important note for customizing:
Procedure
29 | P a g e
IMG Menu Time Management Work Schedules Work
Schedule Rules and Work Schedules Generate
Work Schedules Manually
Transaction SPRO
Code
3. Result:
Record created.
Screenshot
30 | P a g e
Important note for customizing:
Use the "Create" function to generate the monthly work schedule one
month at a time (with confirmation). Use the "Create all" function to
generate the work schedule for the required period without confirmation.
Procedure
31 | P a g e
2. Make the following entries:
(a) Employee subgroup grouping 2
(b) Holiday calendar ZS
(c) Personnel subarea grouping 50
(PSG)
(d) Work schedule rule Normal
(e) Calendar month from 012010
(MMYYYY)
(e) to (MMYYYY) 122010
(g) Name of batch input session RPTSHF00
(h) BTCI = /online = A or E
a) Select Esg grouping 2 for salaried staff
b) Select Holiday Calendar ID ZS and ZC for UNITEN.
c) Select PS Grouping 50 for UNITEN.
d) Select UNITEN WS rule.
e) Check/set the start and end date.
g) Give a name for creating batch input, say RPTSHF00.
h) Specify the type of batch input. This entry defines how the
generated data is saved.
Permitted values are:
blank : A batch input session is generated. The session must be
started separately.
'A' : The session is processed immediately. All screens
are displayed.
'E' : The session is processed immediately. Only screens which
require error handling are displayed.
'N' : The session is processed immediately. No screens
are displayed.
4. Result:
Record created.
Screenshot
32 | P a g e
Important note for customizing:
If you want to generate all work schedules at once, enter the period only
and leave all other input fields empty. Batch input sessions can be
processed in the background. If you work in several clients, you must
generate the work schedules in all clients.
EHRMS Settings
33 | P a g e
employees, the UNITEN time sheet administrative have to manually
change in infotype 0007 (plan working time). This is because of the
unprediable work schedule for a group of employee (unit keselamatan).
The feature SCHKZ was configured by adding new company code 7562 for
UNITEN R & D Sdn Bhd and for existing company code 7561 was changed
and added by personnel are UR01, UT01 and UT02.
Procedure
Screenshot
34 | P a g e
3.1.1.7.2 Set Which Hour Fields Are Entry Fields
When the system creates a Planned Working Time record (infotype 0007),
the prerequisite is that the employee works full-time. The working hours
per day, week, and year - on which the work schedule rule is based - are
transferred to the infotype record. When you maintain the infotype, you
can overwrite one of these values (that is, number of hours). The system
can then calculate all remaining hours fields by comparing your entry to
the number of hours defined originally.
You can use feature WRKHR to determine which of the four hours fields
should be ready for input. You can base this on the employee's
organizational assignment.
When the infotype record is created, the weekly working days are
automatically taken from the work schedule rule specified in the record.
This value can also be overwritten. You can use feature WRKHR to
determine whether the system should use the value from the current work
schedule rule or the value in the original record when the infotype record
is changed or copied. You want to be able to enter the weekly working hours
for all employees in personnel area 0001 (&WRKHR=W/ ,). Otherwise, you want
the working hours per day to be ready for input (&WRKHR=D/ ,). a) When a
35 | P a g e
Planned Working Time infotype record (0007) is changed or copied, you
want the system to use the weekly working days as specified in the
original record (&WRKHR=D/ ,). It does not matter if the original value was
taken from the work schedule rule or entered manually.
Procedure
2. No changes made:
Screenshot
36 | P a g e
Procedure
2. No changes made.
Screenshot
37 | P a g e
3.1.1.7.4 Set Default Value for Time Management Status
The time management status specifies whether an employee participates
in time evaluation, and if so, which form. Here, you can use a feature to
create a default value for the time management status in the Planned
Working Time infotype. This default value is proposed when you create an
infotype record. It can be determined on the basis of an employee's
organizational assignment.
The following are possible values:
0 No time evaluation
1 Time evaluation - actual times
2 Time evaluation - PDC
7 Time evaluation without payroll integration
8 External services
9 Time evaluation - planned times
EHRMS Settings
TNB uses default value for TM status 9 for Time evaluation - planned time
where else UNITEN was default to TM status 0 for No time evaluation. The
feature TMSTA was change and configured by personnel are UR01, UT01
and UT02.
Procedure
38 | P a g e
IMG Menu Time Management Work Schedules Planned
Working Time Set Default Value for Time
Management Status
Transaction SPRO
Code
3. Result:
Record created.
Screenshot
39 | P a g e
3.1.2 Time Data Recording and Administration
In this section, you make all the settings necessary to allow you to record
working times for individual employees. This includes absences such as
illness, leave, substitutions, overtime, and so on. You define a status for
Time Management which indicates whether all attendances are recorded
for an employee, or only exceptions to the work schedule. You also
determine how the system should react if working time data is entered
which overlaps with existing data (for example, if an illness record
overlaps with a leave record).
3.1.2.1 Substitutions
In this section, you make system settings for infotype 2003, 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.
EHRMS Settings
40 | P a g e
employees will use new Personnel Subarea Grouping 50 for substitution
and availability types.
Procedure
3. Result:
Record created.
Screenshot
41 | P a g e
3.1.2.1.2 Define Substitution Types
In this step, you define substitution types and time constraint classes for a
substitution.
EHRMS Settings
Procedure
42 | P a g e
1. Access the activity using one of the following navigation options:
IMG Menu Path Time Management Time Data Recording and
Administration Substitutions Define
Substitution Types
Transaction Code SPRO
3. Result:
Record created.
Screenshot
43 | P a g e
3.1.2.1.3 Set Defaults for Substitution Types
In this step, you maintain the Define substitution type (VTART) feature. In
this feature, you define which substitution type is to be the standard
default in the Substitutions infotype (2003). You can vary the default
values according to the organizational and personnel structures in your
enterprise.
Procedure
2. No changes made.
Screenshot
3.1.2.2 Absences
In this section, you store all information required for defining and
recording 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.
44 | P a g e
3.1.2.2.1.1 Group Personnel Subareas for
Attendances/Absences
In this section, you make the settings required for recording and
processing absences.
EHRMS Settings
Procedure
3. Result:
Record created.
Screenshot
45 | P a g e
3.1.2.2.1.2 Define Absence Types
In this step, you define absence types for your different personnel subarea
groupings. You can also define the checks the system performs when you
enter an absence.
EHRMS Settings
Procedure
46 | P a g e
1. Access the activity using one of the following navigation options:
IMG Menu Path Time Management Time Data Recording and
Administration Absences Absence Catalog
Define Absence Types
Transaction Code SPRO
3. Result:
Record created.
Screenshot
47 | P a g e
Important note for customizing:
When you define a new absence type, copy one that has already been
defined. Choose an absence type which is similar to the one you want to
define.
48 | P a g e
Remember: when you copy an absence type, the system does not only
copy the information you can see in this step. A number of settings that
are stored in other views are also copied. Familiarize yourself with the
many configuration options before you copy absence types.
The time constraint class controls the system reaction if a new record in
the Absences infotype (2001) overlaps with existing time infotype records.
EHRMS Settings
UNITENs time screens and time constraint classes setting are the same as
TNB. All the absence type entry screen is configure to 2001 with the time
constraint class 1 except for absence type sick leave the time constraint is
tie to 3. Table V_554S_0 was configured by coping the current TNB value
and renaming it to Personnel Subarea grouping 50.
Procedure
49 | P a g e
Urusan Kesatuan 01.01.199 31.12.999
50 CK24
Sekerja 0 9
01.01.199 31.12.999
50 CK26 Aktiviti Sukan
0 9
3. Result:
Record created.
Screenshot
50 | P a g e
51 | P a g e
3.1.2.2.1.5 Absence Counting
In this section, you make the settings for attendance/absence counting.
When an attendance/absence is recorded, the system refers to the
planned working hours in the employee's daily work schedule to calculate
the attendance/absence hours. This is not always desirable. There are
times when you want to apply special regulations for counting
attendances and absences.
EHRMS Settings
TNB employees in U001 and U002 will remain as counting class 1 for
absence and attendance counting. Uniten employees under the personnel
area UR01, UT01 and UT02 will also use counting class 1 for absence and
attendance counting. Table V_T551C was configured with UNITEN value
which is tagged to Personnel Subarea Grouping 50 for period work
schedule valuation.
52 | P a g e
Procedure
01.01.199 31.12.999 1
50 NORM 0 9
3. Result:
Record created.
Screenshot
53 | P a g e
3.1.2.2.1.5.2 Rules for Absence Counting (New)
EHRMS Settings
Procedure
54 | P a g e
2. Make the following entries:
(a) (a) (b) (b) (c)
EE Name of EE EE Name of ESG Time
grou group subgro EE quota types
p up subgroup
X Akademik Kontrak * * X
Lembaga Y
Y * *
Canselor
Z Akademik * * Z
* all EE subgroup under the EE group.
a) Create new EE group X, Y and Z for UNITEN and name the EE group.
b) Enter EE subgroup and name of EE subgroup.
d) Enter counting class 1 for UNITEN.
3. Result:
Record created.
Screenshot
55 | P a g e
3.1.2.2.1.5.2.2Group Personnel Subareas for Time Quotas
In this step, you group your personnel subareas with regard to the
permissibility of time quota types. Personnel subareas for which the same
attendance and absence quota types are defined are assigned to the
same grouping for time quota types.
EHRMS Settings
Procedure
56 | P a g e
2. Make the following entries:
(a) (a) (b) (b) (c)
Person Personnel area text Pers. Pers. PS
nel subar subarea groupi
area ea text ng
Uniten R&D Sdn Bhd,
UR01 A000 R&D 50
Kajang
3. Result:
Record created.
Screenshot
57 | P a g e
3.1.2.2.1.5.2.3Define Rules for Rounding Counted Absences
In this step, you set rounding rules for absence and attendance counting.
If you specify an hours or day multiplier for counting attendances and
absences, the values determined can have several places behind the
decimal point. It is difficult to use these values for quota deduction and
payroll. In this step, therefore, you set rules for rounding the values. You
use concrete numbers for the rounding rules and can specify whether you
want:
You can specify several subrules for a rounding rule and number them
sequentially. The system runs through the subrules in sequential order
until it finds one that applies.
EHRMS Settings
Procedure
58 | P a g e
1. Access the activity using one of the following navigation options:
IMG Menu Path Time Management Time Data Recording and
Administration Absences Absence Catalog
Absence Counting Rules for Absence Counting
(new) Define Rules for Rounding Counted
Absences
Transaction Code SPRO
3. Result:
Record created.
Screenshot
59 | P a g e
3.1.2.2.1.5.2.4Define Counting Rules
In this step, you define 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.
EHRMS Settings
60 | P a g e
a) Create ESG, A for UNITEN.
b) Create PSGpg, 50 for UNITEN.
c) Enter counting rule, 001 for UNITEN.
d) Enter leave text, Annual Leave.
3. Applicability of rule:
Conditions for current day:
Weekday
Monday Friday
Tuesday Saturday
Wednesda Sunday
y
Thursday
Holiday Class
Not a public holiday
Day type
Work acc. To work schedule
Counting:
Hours Days
Quota 100 Quota 100
multiplier % multiplier %
Rounding Rule 01 Rounding 01
61 | P a g e
Rule
Multiply first Multiply first
Round first Round first
Deduction rule:
Absence quotas Attendance quotas
Within 901 AnnualLeave Within entitlement
entitlement
Over 901 AnnualLeave Over entitlement
entitlement
4. Result:
Record created.
Screenshot
62 | P a g e
63 | P a g e
Procedure for Deduction rules for absence
3. Applicability of rule:
Unit of relevent absence quota type
Hours Days
Absence quota types
15 Cuti Lebihan diluluskan Days
14 Baki dibawa kehadapan Days
11 Tahunan (Annual) Days
Quota type sequence for further
deduction
No further deduction
Sort all other quota types in
ascending order
64 | P a g e
Sort all other quota types in
descending order
Deduction priority
Quota types Priority Ascending Descendin
g
Valid from Not Relevant Ascending Descendin
date g
Valid to date Not Relevant Ascending Descendin
g
Deduction Not Relevant Ascending Descendin
from g
Deduction to Not Relevant Ascending Descendin
g
4. Result:
Record created.
Screenshot
65 | P a g e
66 | P a g e
3.1.2.2.1.5.3 Assign Counting Rules to Absence
Counting
In this step, you determine which rule for attendance or absence counting
should be used for each attendance/absence type.
EHRMS Settings
Procedure
3. Applicability of rule:
Counting/Quota deduction
Counting rule 005
Quota deduction
Deduction over interval Blank
end
4. Result:
Record created.
67 | P a g e
Screenshot
68 | P a g e
3.1.2.2.1.5.4 Determine Daily Work Schedule Variants
for Absence
In this step, you define rules for counting certain full-day absences. This
affects payment of absences, and also the formation of time credits. When
you enter a full-day absence, the system automatically refers to the
planned working hours in the relevant daily work schedule to determine
the number of absence hours. Depending on the rules you specify in this
step, you can have the system refer to a different variant of the daily work
schedule which stipulates a different number of planned working hours.
EHRMS Settings
The variants for Daily work schedule for UNITEN employee is tagged to
PSG 50. Table V_T550A was added with new value for UNITEN.
No changes was made in this table V_550X_B - Daily Work Schedule Rules
for Absence Recording.
69 | P a g e
Rest Day 01.01.199 31.12.99
50 REST
0 99
3. Applicability of rule:
Planned working hours
Planned working hours 8.00
No planned working Blank
hours
DWS selection rule 05
Working times
Fixed working hours 15:0 23:00
0
Valuation
Daily WS class 2
4. Result:
Record created.
Screenshot
70 | P a g e
Procedure for Assign Grouping for Daily Work Schedule
Variant
4. Result:
Record created.
Screenshot
72 | P a g e
73 | P a g e
Procedure for Create Rules for Daily Work Schedules
Screenshot
74 | P a g e
Procedure for Check Daily Work Schedule Selection Rule
Screenshot
75 | P a g e
3.1.2.2.1.6 Define Indicators for the Personal Calendar
In this step, you determine whether or not an absence recorded in an
employee's personal calendar should be assigned an absence category.
The absence category is a one-character indicator that can be assigned to
an an absence type.
EHRMS Settings
The symbol for attendance and absence for TNB and UNITEN are the
same. However to differentiate them UNITEN symbol's are tagged to PSG
= 50. Table V_T554P was configured with new value for UNITEN.
76 | P a g e
50 B Cuti Sakit
50 C Cuti Separuh Gaji
50 D Cuti Tanpa Gaji
50 E Cuti Khas
50 F Cuti Lain-Lain
3. Result:
Record created.
Screenshot
77 | P a g e
2. Make the following entries:
(a) (b) (b) (c) (c)
PSGp Abs. Abs. Type text Start End Date
g Type Date
Pertubuhan 01.01.19 31.12.999
50 CK23
Sukarela 90 9
Urusan Kesatuan 01.01.19 31.12.999
50 CK24
Sekerja 90 9
01.01.19 31.12.999
50 CK26 Aktiviti Sukan
90 9
4. Result:
Record created.
Screenshot
78 | P a g e
3.1.2.3 Attendance/Actual Working Times
Attendances are used to record the actual hours worked by an employee.
You make the settings required to enter attendance data in this section. If
attendances are recorded in detail, you can assign the hours worked by a
particular employee to specific orders or cost centers, and to maintain
data on business trips. It is also possible to record all attendance times
manually in the Attendances infotype (2002). You can evaluate them using
the time evaluation report.
79 | P a g e
3.1.2.3.1 Define Attendance Types
In this step, you define attendance types for a personnel subarea grouping
for attendance/absence types. It also describes how to determine the
system reaction to attendances recorded for a day or a period when the
employee has time off. There are four possible system reactions if
attendance records are entered on days off.
EHRMS Settings
The absence input checks for TNB and UNITEN are the same. However to
differentiate them UNITEN absence checks are tagged to PSG = 50. Table
V_554S_B was configured with two new value Normal hours Work
Related (NH) and Overtime for UNITEN.
Procedure
80 | P a g e
Last day is day off Blan
k
Non-working Blan
period k
Second date Blan
required k
Minimum Blan
duration k
Maximum 999
duration
Unit K Calendar
days
4. Result:
Record created.
Screenshot
81 | P a g e
3.1.2.3.2 Define Types of Overtime Compensation
In this step you define overtime compensation types. The type of overtime
compensation for recorded attendance time, recorded overtime and
approved overtime can be entered in the Attendances (2002). The
overtime compensation type indicates whether the employee should
receive remuneration and/or time off for working overtime.
EHRMS Settings
Procedure
82 | P a g e
4. Result:
Record created.
Screenshot
EHRMS Settings
UNITENs time screens and time constraint classes setting are the same as
TNB. All the absence type entry screen is configure to 2002 with the time
constraint class 1 except for overtime the time constraint is tie to 2. Table
V_554S_N was configured by coping the current TNB value and renaming
it to Personnel Subarea grouping 50.
Procedure
83 | P a g e
2. Make the following entries:
(a) (b) (b) (c) (c)
PSGp Attn. Attendance Type text Start End
g Type Date Date
Normal Hrs Work 01.01.19 31.12.99
50 NH
Related 00 99
01.01.19 31.12.99
50 OT Overtime
00 99
a) Create PSGpg for absence and attendance type, value 50 is use for
UNITEN.
b) Create Attendance type code, NH and name the attendance type,
Normal Hours Work Related.
c) Enter Start date, 01.01.1900 and End date, 31.12.9999.
3. Applicability of rule:
Attendance: General
Settings
Check end date Blan (When an attendance is entered, the attendance type for the
start date is read. In this field, you specify whether the end date
k of the attendance must be within the validity period of the
attendance type)
Screen Number 205 (no quota deduction)
(By specifying the screen number for an attendance type, you
1 determine which screen is used for entering, displaying and
maintaining records)
Time cstr. class 1 (The time constraint class is used to check for collisions between
Time Management infotypes (2001 to 2012). It allows you to
specify different regulations for checking for collisions between
individual subtypes)
Att./absence class 10
4. Result:
Record created.
Screenshot
84 | P a g e
3.1.2.4 Overtime
You make the settings for processing overtime in this section.
EHRMS Settings
85 | P a g e
Procedure
Screenshot
3.1.2.5 Availability
You make the settings required to define attendances for availability in
this section.
86 | P a g e
EHRMS Settings
Procedure
Screenshot
87 | P a g e
3.1.2.5.2 Define Availability Types
In this step, you define availability types for a personnel subarea grouping
for availability types.
EHRMS Settings
UNITEN will be using availability type 01- Standby duty and 02- Deleted
Standby Duty, which is tagged to PSG 50. Table V_T557 has been added
wiith two new value for UNITEN.
Procedure
88 | P a g e
Types
Transaction Code SPRO
Screenshot
89 | P a g e
3.1.2.5.3 Determine Daily Work Schedules for Availability
In this step you can carry out the following:
Determine daily work schedules for availabilities
Indicate the daily work schedules permitted for availabilities
You enter availabilities based on the daily work schedule in the Availability
infotype (2004). The daily work schedules you indicated in this step are
then proposed in the Daily work schedule as possible entries. Daily work
schedule processing for availabilities is unique in the following ways:
1. Breaks are not included when processing availabilities. For this
reason, you do not need to create breaks for daily work
schedules for availabilities
2. The SAP System determines the start and end of an availability
during processing:
o For work schedules with fixed start and end times
according to the Planned working time fields.
o For flextime work schedules according to the Normal
working time fields.
3. Specifications for the daily work schedule selection rule (see
Define Rules for Variants) are not included during processing.
4. Absences with an availability recorded for the period are not
counted during processing using the function Determine Daily
Work Schedule Variants for Absence.
90 | P a g e
EHRMS Settings
The daily work schedules for availabilities for UNITEN employee will be
tagged to PSG 50. Table V_T550A was added with new value for UNITEN.
The daily work schedules permitted for availabilities for UNITEN employee
will be tagged to PSG 50. Table V_T550A _B was added with new value
for UNITEN.
Screenshot
91 | P a g e
Procedure for Indicate Daily Work Schedules for Availability
92 | P a g e
2. Make the following entry:
(a) (b) (b) (c) (d) (d) (e)
Grp Daily Daily work Varia Start End Availabi
g work schedule nt Date Date lity
sched text
ule
50 AF90 Aftn Shift- 01.01.19 31.12.99 Blank
UTN 90 99
50 M090 Morn Shift- 01.01.19 31.12.99 Blank
UTN 90 99
50 NG90 Nght Shift- 01.01.19 31.12.99 Blank
UTN 90 99
50 NOFR UTN Normal 01.01.19 31.12.99 Blank
Fri 90 99
50 NORM UTN Normal 01.01.19 31.12.99 Blank
90 99
50 OFFD Off Day 01.01.19 31.12.99 Blank
90 99
50 REST Rest Day 01.01.19 31.12.99 Blank
90 99
a) Enter PS grouping for UNITEN.
b) Enter unique ID to represtent UNITEN daily work schedules and
name the DWS ID.
c) Leave Variant field blank.
d) Enter Start date, 01.01.1900 and End date, 31.12.9999.
e) Use this indicator to determine the admissibility of availability types
for certain daily work schedules.
3. Result:
Record created.
Screenshot
93 | P a g e
3.1.2.5.4 Define Work Schedules Rules for Availability
In this step, you define which work schedule rules are permitted for an
availability.
You can enter an availability in the Availability infotype (2004) that is
based on a work schedule rule. In this way, you can create availabilities
based on the period work schedule. When you display possible entries for
the Work schedule rule field, only those work schedule rules you indicated
as as permitted in this step are displayed. Work schedule rule processing
for availabilities is unique in the following ways:
1. Breaks are not included when processing availabilities.
2. The SAP System determines the start and end of an availability
during processing:
o For work schedules with fixed start and end times according to
the entries in the Planned working time field.
o For flextime work schedules according the the entries in the
Normal working time field.
3. Specifications for the daily work schedule rule are included
during processing for generating the work schedule, but not for
counting absences.
94 | P a g e
EHRMS Settings
The work schedules rule for availabilities for UNITEN Holiday calendar id
ZC & ZS will be tagged to PSG 50. Table V_T508A _B was added with
new value for UNITEN.
Procedure
95 | P a g e
3. Result:
Record created.
Screenshot
96 | P a g e
3.1.2.6.1.1 Group Employee Subgroups for Time Quotas
In this step, you group your employee subgroups for time quota types.
Employee subgroups for which the same attendance and absence quota
types are defined are assigned to the same grouping for time quota types.
EHRMS Settings
Procedure
Screenshot
97 | P a g e
3.1.2.6.1.2 Group Personnel Subareas for Time Quotas
In this step, you group your personnel subareas with regard to the
permissibility of time quota types. Personnel subareas for which the same
attendance types are defined are assigned to the same grouping for time
quota types.
EHRMS Settings
Procedure
98 | P a g e
Attendance/Absence Quotas Setting Groupings
for Time Quotas Group Personnel Subareas for
Time Quotas
Transaction Code SPRO
Screenshot
99 | P a g e
EHRMS Settings
Procedure
100 | P a g e
Deduction
Neg. deduction to Blan Specifies the value in hours or days by which the
time quota can be deducted over and above the
k entitlement.
Rounding Blan This field defines how payroll days are calculated
from absence days.This field is of particular
k significance for calculating leave as, in most cases,
the system accepts only whole or half days of
leave
Payroll-relevant data
No comp. Blan If there is an entry in the field, the current quota
type is locked for compensation.
k
4. Result:
Record created.
Screenshot
101 | P a g e
102 | P a g e
3.1.2.6.3 Calculating Absence Entitlements
In this section you make the settings required for the automatic accrual of
absence quotas.
EHRMS Settings
103 | P a g e
Procedure
a) Enter ES grouping.
b) Enter PS grouping.
c) Enter unique ID to represent UNITEN Absence quota type and name
the quota type.
d) Enter Start date, 01.01.1900 and End date, 31.12.9999.
e) This field specifies the unit of time or measurement which is to be used as
a basis for calculations. Enter Days.
f) Select the No gen. (no generation) field, the absence quota type is
not generated in time evaluation. In this case, you maintain the
absence quota values manually in the Absence Quotas infotype
(2006).
g) Specify whether the entitlement in the Absence Quotas infotype to
be increased by the results of quota generation. Leave this field
blank.
h) Specify whether the entitlement in the Absence Quotas infotype to
be replaced by the results of quota generation. Leave this field
blank.
i) Specifies whether negative deduction is permitted for the quota,
and if so, how much. Leave this field blank.
j) Specify the time constraint class (to check for collisions between
Time Management infotypes), enter 01 for UNITEN.
104 | P a g e
3. Result:
Record created.
Screenshot
Procedure
105 | P a g e
Quotas in Time Evaluation Permit Quota
Generation Without Time Evaluation
Transaction Code SPRO
106 | P a g e
upon a variety of employee organizational assignments.
If you generate the absence quotas in time evalation, the value from
the feature is automatically queried by the system.
2. In time evaluation (standard schemas XMOD, TM04, TM01
and TQTA):
Function MOD calls a personnel calculation rule that has been adapted
to the requirements of the schema (TMON, MODT and so on). The
employee subgroup grouping for the personnel calculation rule is
queried in this rule using operation PAYTP. Using operation MODIF Q=xx,
you can then determine for each of these groupings which quota type
selection rule group should be used in time evaluation to access the
entries in the Absence Quota Type Selection table for the relevant
employees.
3. Using a specially designed personnel calculation rule in the
time evaluation schema:
In this case, you also determine the quota type selection rule group
using operation MODIF Q=xx.
EHRMS Settings
Procedure
107 | P a g e
X Akademik Kontrak -> create node Employee Subgroup
ZC Profesor
ZD Reader
Z Akademik -> create node Pay Scale Group
UT10
UT11
UT12
UT13
3. Result:
Record created.
Screenshot
108 | P a g e
109 | P a g e
3.1.2.6.3.2.2 Set Base Entitlements
In this step, you set rules for determining the total entitlement (base
entitlement) to an absence quota type. The base entitlement forms the
basis for calculating the prorated leave or absence entitlement for each
accrual period.
If you determine the base entitlement according to the employee's age or
seniority, you enter a constant expressed in days or hours.
If you use time evaluation to generate absence quotas, you can make the
rule more specific. You may want to do this if the differentiation based on
an employee's age or seniority is not sufficient for your purposes, or if you
want to use other criteria to determine the base entitlement. You can do
this by incorporating personnel calculation rules in the time evaluation
schema. In the rules, you fill a special time type with the base entitlement
according to the employee's organizational details or the results of time
evaluation. You store the special time type, which the system reads in
order to determine the entitlement, in this view. If you want to vary the
base entitlement according to age or seniority interval, you can
distinguish between the various entitlements by numbering them
sequentially.
The base entitlement is set for a specific period. You have three options
for determining the base period:
110 | P a g e
According to employee-independent periods:
The base period can relate to the calendar year, the time evaluation
period, or an individually specified period in the Period Parameters
table.
According to employee-dependent periods
You can determine the base period according to the payroll period or
a period relating to a date type from the Date Specifications
infotype (0041).
Using date specifications
Some collective agreements and company agreements stipulate
that the base entitlement must be determined in relation to the
period of employment. They state that, after a base period,
employees must receive the exact base entitlement. To comply with
this requirement, you must use a date type.
Example: You accrue entitlements on a daily basis. One employee
joined your company on February 15, 2000, another employee on
March 1, 2000. Both employees have a base entitlement of 20 days
per year. After the employees have been with your company for
exactly a year, the first employee's generated entitlement is slightly
too high, the second employee's slightly too low, because of the
leap year. The reason for this is that the following data was used as
a basis for the calculation:
o In 2000, because of the leap year, 366 days for 20 days'
entitlement
o In 2001, 365 days for 20 days' base entitlement
Note: The differences in the amount of entitlement calculated are only
relevant for the requirements mentioned above.
According to the accrual period
In this case, the period over which you generate employee's quota
entitlements is used as the base period (base period = accrual
period).
EHRMS Settings
Procedure
111 | P a g e
Absence Entitlements Rules for Generating
Absence Quotas Set Base Entitlements
Transaction Code SPRO
2. Make the following entry:
(a) (b) (c) (c) (d) (e) (f) (f)
ES PS AQ Quota text Rule Seq. Start Date End Date
G G type no.
A 50 11 Tahunan (Annual) 001 001 01.01.19 31.12.99
90 99
A 50 11 Tahunan (Annual) 001 002 01.01.19 31.12.99
90 99
A 50 11 Tahunan (Annual) 001 003 01.01.19 31.12.99
90 99
A 50 15 Cuti Lebihan 001 001 01.01.19 31.12.99
diluluskan 90 99
A 50 21 Cuti Sakit 001 001 01.01.19 31.12.99
90 99
a) Enter ES grouping.
b) Enter PS grouping.
c) Enter unique ID to represent UNITEN Absence quota type and name
the quota type.
d) Rules for determining an employee's total entitlement (base
entitlement) to an absence quota type. Enter Rule 001.
e) You can attach several subrules to a rule if you want to determine
the base entitlement according to the employee's seniority or age.
Enter Sequence No 001.
f) Enter Start date, 01.01.1900 and End date, 31.12.9999.
3. Applicability of rule:
Base
entitlement
Seniority 0 005 year Length of service with enterprise (seniority)
- s
Age Blan Specifies the employee's age
k
Entitlement
Constant 16 day An employee's total absence quota
entitlement for a certain period.
s
Period balance Blan A time type is a grouping of times according
to various aspects such as payment
k regulations, internal company requirements
and control tasks.
Relatedto Period
Calendar year Period of 1 year from 01/01/xxxx - 12/31/xxxx
Accrual period Blan Time interval on which the calculation of the entitlement is
based
k
Time Evaluation Blan Time evaluation period as specified in the Determine time
evaluation periods step
period k
Payroll period Blan Payroll period that is valid at the end of the accrual period for
the employee's payroll area
k
Other period Blan Individually defined period; the period parameter is specified in
the Define period parameters in Customizing for Payroll.
112 | P a g e
k
Rel. to date type Blan Period is defined in relation to a date type from the Date
Specifications infotype (0041). You determine the accrual
k period using the length fields (for example, the date the
employee joined the company, with a period of one month).
Length Blan
k
4. Result:
Record created.
Screenshot
113 | P a g e
3.1.2.6.3.2.3 Determine Validity and Deduction
Periods
In this step, you decide which validity and deduction periods you want to
be valid for an Absence Quotas infotype record (2006) created by the
system. You do this for each absence quota type.
114 | P a g e
The deduction from and deduction to dates define the period in which the
absence quota can be reduced by an absence. It need not be identical to
the validity period, and can exceed it.
You only specify a validity period for absence quotas that are generated
during time evaluation. Fields for entering the validity period are therefore
only available for absence quotas for which you have selected replace or
increase in the Generating quotas allowed in time evaluation step.
The validity period represents the period for which the time off
entitlements are filled in one infotype record. If no entitlement of this type
has been generated or if the validity period has been exceeded, a new
record is created.
You have a certain amount of flexibility in defining validity periods. The
validity period can be:
A fixed period such as a calendar year or the time evaluation period
Employee-dependent period, such as the payroll period or the date
type
A period defined in the quota selection rule, such as the accrual
period
A period you have defined in Customizing, such as the period
parameter
EHRMS Settings
Procedure
115 | P a g e
2. Make the following entry:
(a) (b) (c) (c)
ES PS AQ type Quota text
G G
A 50 11 Tahunan (Annual)
A 50 15 Cuti Lebihan
diluluskan
A 50 21 Cuti Sakit
A 50 23 Cuti Sakit Masuk
Wad
A 50 24 Cuti Sakit (Khas
Wabak)
a) Enter ES grouping.
b) Enter PS grouping.
c) Enter unique ID to represent UNITEN Absence quota type and name
the quota type.
3. Applicability of rule:
Deduction interval:
Deduction from
Start of validity The deduction interval specifies the period in which an
employee can deduct records in the Absence Quotas infotype
interval (2006) that have been created
End of validity Blan
interval k
Relative position Blan You can use the Relative positon field to refine the
specifications on the start or end date of the validity intervals.
k
No deduction Blan The deduction interval is specified in relation to the validity
interval. You can base the deduction begin or deduction end
before k date on a date type that is created
Deduction to
Start of validity Blan The deduction interval specifies the period in which an
employee can deduct records in the Absence Quotas infotype
interval k (2006) that have been created
End of validity
interval
Relative position Blan You can use the Relative positon field to refine the
specifications on the start or end date of the validity intervals.
k
No deduction Blan The deduction interval is specified in relation to the validity
interval. You can base the deduction begin or deduction end
before k date on a date type that is created
4. Result:
Record created.
Screenshot
116 | P a g e
3.1.2.6.3.2.6 Define Generation Rules for Quota Type
Selection
In this step, you define rules for automatically accruing absence entitlements for
your employees. If you want to set up rules for generating absence quotas using
the report RPTQTA00 or for determining default values, you can now use a
restricted view of the Customizing table. All non-relevant fields for this method
remain hidden. The system knows which view of the Customizing table to display
according to your specifications made in the Permit Quota Generation Without
Time Evaluation activity.
117 | P a g e
EHRMS Settings
118 | P a g e
d) Selection rule for absence quota types to set rules regarding how an
employee's absence entitlement is generated. Enter as per QUOMO
feature setting.
Name the rule, Uniten.
e) Absence quota type unique ID to forms the subtype of the Absence
Quotas infotype. Enter subtype 11 and name the quota type,
Tahunan (Annual).
f) Enter Start date, 01.01.1900 and End date, 31.12.9999.
3. Applicability of rule:
Applicability tab
Start of accrual
Earliest accrual Blank Specifies the earliest date for calculating the accrual
entitlements
Relationship to enterprise
Entry Date 01.01.180 31.12.99 Employee's
enterprise.
date of entry in the
0- 99
Challenge
Challenge group Blank
The directory for severely challenged persons classifies
Degree of 0 - 100 employees according to their type of challenge. Each
challenge % classification has its own identifier.
Calendar year
Period of one year from 01/01/XX to 12/31/XX
Time evaluation Blank
period Period determined in time evaluation, defined in the
Determine the time evaluation period step in the
Implementation Guide (IMG) for Time Evaluation.
Payroll period Blank
Period determined in payroll; valid payroll period of the
day to be evaluated of the payroll area of the
employee to be evaluated
Other period Blank
Individually specified period; period parameters are
defined in the Define period parameters step in the
IMG for Payroll.
Rel. to date type Blank
Period is defined in relation to a date type from the
Length Blank Date Specifications infotype (0041). You determine the
accrual period using the length fields (for example, the
date the employee joined the company, with a period
of one month).
Take Account of Blank
Change of Work If you do not select this field, the organizational
reassignment, reentry, or leaving is not taken into
Center/Basic Pay account in the accrual period in which the change
takes place.
119 | P a g e
Base entitlement tab
Rule for base 001
entitlement Rules for determining an employee's base entitlement to
an absence quota type.
Base Entitlement
Number 16
Specifies the amount (in days or hours) of a time quota status.
Day Bal. Blank
A time type assigns a meaning to a time interval. The balances
Period Bal. Blank formed in time evaluation are posted to the time types.
Unit Days
This field specifies the unit of time or measurement which is to
Base Calendar be used as a basis for calculations
Period year
FromSenior 000
ity Length of service with enterprise (seniority) By defining a
seniority interval, you can specify special rules for determining
ToSeniority 005 an employee's base entitlement according to his or her
seniority.
Unit text years
This field specifies the unit of time or measurement which is to
be used as a basis for calculations
From age 000
Specifies the employee's age. By specifying an age interval, you
To age 000 can define special rules based on an employee's age.
Unit text blank
This field specifies the unit of time or measurement which is to
be used as a basis for calculations
Calculation of
Seniority
Cal. blank
Process A calculation process is a group of all functions required in the
calculation of an employment period.
Key Date for Determining Senority
For Exact Day blan
k In this field, you specify the key date used to calculate seniority.
Start blan
k If an employee's seniority is to be determined for a particular
date, then any change in the seniority is taken into account
End of Accrual blan within the accrual period. The resulting accrual entitlement is
then calculated proportionately according to the different base
Period k entitlements.
Start blan
k
End of Base blan
Period k
Date Type Seniority
(Revised) In this field, you specify the key date used to calculate seniority.
The length of seniority is calculated from the difference
between the key date of the current year and the date the
employee started working at the company.
Key Date for Determining Senority
For Exact
Day In this field, you enter the time to be used for determining an
employee's age.
Start blank If the employee's age is determined from a certain day, the
system takes account of a change in age within the accrual
End of Accrual blank period. The resulting accrual entitlement is then calculated
proportionately according to the different valid base
Period entitlements.
Start blank
120 | P a g e
End of Base blank
Period
Date Type blank
The date type defines the meaning of a particular date
4. Result:
Record created.
121 | P a g e
Screenshot
122 | P a g e
123 | P a g e
124 | P a g e
Procedure for Quota types
125 | P a g e
Procedure for Base entitlement
Screenshot
126 | P a g e
Procedure for Validity/deduction interval
Screenshot
127 | P a g e
Procedure for Validity period for default values
128 | P a g e
2. Make the following entry for UNITEN:
(a) (b) (c)
ESG for time PSG for time Quota type sel. grp
quotas quota
A 50 01
B 50 01
C 50 01
D 50 01
E 50 01
a) Employee subgroup grouping for time quota types is a grouping of
employee subgroups for which the same absence quota types are
defined. Enter ES grouping, A.
b) Grouping of personnel subareas for time quota types is a division of
personnel subareas for which the same absence quota types are
defined. Enter PS grouping, 50.
c) Quota type selection rule group to control absence quota type
selection based on the employee's organizational assignment. Enter
as per QUOMO feature setting.
3. Applicability of rule:
Valid from date
Calendar year Period of 1 year from 01/01/xxxx - 12/31/xxxx
Time evaluation Blan Time evaluation period, as specified in the Determine time
evaluation periods step
period k
Payroll period Blan
k Payroll period that is valid at the end of the accrual period for
the employee's payroll area
Other period Blan Individually defined period; the period parameter is specified in
the Define period parameters step in Customizing for Payroll.
k
Date type Blan The date type is read from the Date Specifications infotype
(0041). An infotype record must have been created for all
k employees
Start The validity interval for an absence quota should be a calendar
year. The start date is the first day of the calendar year for
End Blan which the accrual entitlement is to be determined. The end
k date should be at least three (3) months after the end of the
Relative position Blan calendar year for which the accrual entitlements is to be
determined.
k
Valid to date
Calendar year Period of 1 year from 01/01/xxxx - 12/31/xxxx
Time evaluation Blan Time evaluation period, as specified in the Determine time
evaluation periods step
period k
Payroll period Blan
k Payroll period that is valid at the end of the accrual period for
the employee's payroll area
Other period Blan Individually defined period; the period parameter is specified in
the Define period parameters step in Customizing for Payroll.
k
Date type Blan The date type is read from the Date Specifications infotype
(0041). An infotype record must have been created for all
k employees
Start The validity interval for an absence quota should be a calendar
year. The start date is the first day of the calendar year for
End Blan which the accrual entitlement is to be determined. The end
k date should be at least three (3) months after the end of the
Relative position Blan calendar year for which the accrual entitlements is to be
129 | P a g e
k determined.
4. Result:
Record created.
Screenshot
130 | P a g e
1. Access the activity using one of the following navigation options:
IMG Menu Path Time Management 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 Type Selection
Transaction Code SPRO
131 | P a g e
3.1.2.6.3.3 Setting up Methods for Quota Accrual
In this section, you make the settings required in Customizing to set up the
following options for generating absence quotas:
EHRMS Settings
132 | P a g e
Procedure for Determine Absence Quota Type for Accrual
133 | P a g e
Procedure for Set Up Report Variants for Absence Quota
Accrual
134 | P a g e
2. Make the following entries:
(a) Program RPTQTA00
(b) Period 01.01.2010
31.12.2010
(c) Selection Blank
(d) Quota to be generated 11
(e) Generation type Test run
(e) Output options Display all quota
records
a) Enter program name, RPTQTA00.
b) Enter period for quota creation, 01.01.2010 31.12.2010.
c) Leave the selection field blank.
d) Enter quota type for Tahunan (Annual), 11.
e) Select generation type, Test run.
f) Select output options, display all quota records.
Screenshot
135 | P a g e
136 | P a g e
Procedure for Set Validity Interval for Quota Accrual
137 | P a g e
3.1.2.6.3.4 Quota Deduction Using Attendance/Absences
EHRMS Settings
Procedure
138 | P a g e
Absence Quota
Transaction Code SPRO
2. Make the following entry for UNITEN:
(a) (b) (c) (c) (d) (d)
ESG PSG Deduction Text Start End
rule Date Date
A 50 901 Annual Leave 01.01.19 31.12.99
90 99
A 50 902 Sick Leave 01.01.19 31.12.99
90 99
A 50 904 Sick Leave (Ward) 01.01.19 31.12.99
90 99
A 50 905 Agency Leave 01.01.19 31.12.99
90 99
A 50 906 Sport Activity 01.01.19 31.12.99
Leave 90 99
a) Employee subgroup grouping for time quota types is a grouping of
employee subgroups for which the same absence quota types are
defined. Enter ES grouping, A.
b) Grouping of personnel subareas for time quota types is a division of
personnel subareas for which the same absence quota types are
defined. Enter PS grouping, 50.
c) Specifies quotas for absences should be deducted and assign
different rules for quota deduction to the counting rules.
d) Enter Start date, 01.01.1900 and End date, 31.12.9999.
3. Applicability of rule:
Unit of relevant absence quota types
Hours Blan
k Specifies the unit (hours or days) in which the specified
absences quotas should be deducted.
Days
Quota type text
Cuti Lebihan 15 An absence quota type forms the subtype of the Absence
Quotas infotype
diluluskan unit
Baki Dibawa 14
Kehadapan unit
Tahunan (Annual) 11
unit
Quota type sequence for further deduction
No further deduction Only the quotas specified under absence quota types are
deducted.
Sort all other quota Blan If the employee has other quotas that are deducted in
the specified time unit, they are sorted in ascending
types in ascending k order for deduction (first 01, then 02, 03, etc.)
order
Sort all other quota Blan
types in descending k All other quota types sorted in descending order
If the employee has other quotas that are deducted in
order the specified time unit, they are sorted in descending
order for deduction (first 99, then 98, 97, etc.)
Deduction priority
Quota types Priority Specifies the priority with which the quota types should
be taken into account when determining the deduction
Valid from date Not sequence.
If you indicate a quota type as not relevant, it is the last
Revelent
139 | P a g e
Valid to date Not sort criterion to be taken into account when the sequence
is determined. Under Deduction priority, you can specify
Revelent whether you want the quota type to be the main criterion
for determining the sequence in which the quotas are
Deduction Not deducted. The start of validity of a quota can also have
from Revelent the highest priority for determining the sequence.
Deduction to Not
Revelent
Ascending Specifies whether the criteria entered is to be sorted in descending
or ascending order. You want to deduct quota for the employee that
Descending Blan will be the first to be forfeited or to expire. To do so, specify the
k Deduction end (date) in ascending order.
4. Result:
Record created.
Screenshot
140 | P a g e
141 | P a g e
3.1.2.6.3.4.2 Assign Deduction Rules to Counting
Rules
In this step, you assign quota deduction rules to counting rules. All
absences and attendances with quota deduction that are counted using
the selected counting rule are processed using these deduction rules. As
well as a deduction rule for deducting the employee's quotas with an
entitlement greater than 0, you can also specify a deduction rule for all
quota types for which the corresponding infotype records can be deducted
over and above the entitlement.
EHRMS Settings
142 | P a g e
To differentiate between TNB Uniten employee Time Quota and Uniten
Time Quota, uniten employee is tagged to counting rule 50. Table T556C
was added with new value for UNITEN
Screenshot
143 | P a g e
144 | P a g e
Procedure for Deduction rules for absence quotas
145 | P a g e
2. Refer to 3.1.2.6.3.4.1 Define Deduction Rules for Absence
Quotas procedures and follow the entries.
Screenshot
146 | P a g e
147 | P a g e
Procedure for Rounding rules
Screenshot
148 | P a g e
3.1.2.7 Specify System Reaction to Overlapping Time
Infotypes
In this step, you determine how the system reacts if existing time infotype
records overlap with new time infotype records. Such collision checks are
also performed for subtypes. The concept of a time constraint class was
developed so that you do not have to define a time constraint reaction for
each subtype with regard to all other infotypes or subtypes within an
infotype. Subtypes within an infotype (attendance/absence type,
attendance/absence quota type, availability type and substitution type)
that have the same time constraint reaction are grouped together by the
time constraint class.
149 | P a g e
A: the old record is delimited, ie. the part of the old record that
overlaps with the new record is deleted. One or two new records can
be derived from the old record.
E: the new record cannot be created. The system displays an error
message.
W: the new record can be created without the old record being
changed. The system displays a warning.
N: the new record can be created without the old record being
changed. The system does not display a warning.
EHRMS Settings
Procedure
3. Applicability of rule:
Reaction when there is an overlap with existing infotype
records (2001)
Infotype 2002
Infotype text Attendanc Infotype for Time data
es
Time cstr. 04 Deduction rule for time constraint class, used to check for
collisions between infotype 2001 and 2002.
class
Reaction E The system does not allow you to create the new record,
and displays all collisions.
indicator
Reaction when there is an overlap with existing infotype
records (2002)
Infotype 2001
Infotype for Time data
Infotype text Absences
Time cstr. 04 Deduction rule for time constraint class, used to check for
collisions between infotype 2002 and 2001.
class
Reaction E The system does not allow you to create the new record,
and displays all collisions.
150 | P a g e
indicator
4. Result:
Record created.
Screenshot
151 | P a g e
152 | P a g e
3.1.2.8 Limit Employee Status for Time Management
The Time Management status indicator shows whether or not an
employee takes part in time evaluation. If you want an employee's time
data to be evaluated using the time evaluation driver, you can use the
indicator to specify the method of evaluation. A Time Management status
is assigned to the employee in the Planned Working Time infotype (0007).
153 | P a g e
The following are the standard specifications for the Time Management
status:
0 - No time evaluation
1 - Evaluation of actual times
2 - Evaluation of actual times and plant data collection (PDC)
8 - External services
9 - Evaluation of planned times (recording of exceptions to the work
schedule)
EHRMS Settings
Procedure
Screenshot
154 | P a g e