Tayo Rolls HR Configuration Guide
Tayo Rolls HR Configuration Guide
Index
Sub Modules
Page No.
1. Organizational Management
___________________ 2
2. Personnel Administration
___________________23
3. Time Management
___________________67
4. Payroll
___________________117
5. Recruitment
___________________327
___________________346
1. Organizational Management
Introduction
"Organizational Management" forms the base for the Personnel Planning and Development
area (as well as Organizational Management, this includes the Personnel Development,
Personnel Cost Planning and Training and Event Management components) and allows you to
analyze and adjust your organizational plan as well as maintain structure data.
In this step, you make the necessary system settings for the implementation of the
"Organizational Management" component.
The Implementation Guide for "Organizational Management" includes a description of the
system settings necessary for "Personnel Cost Planning".
Plan Version
General Description
Plan versions allow you to create several organizational plans in the system at the same time.
You can simulate and compare various scenarios using plan versions. A plan version also
enables you to carry out various simulations and compare plans in the system in parallel. As a
rule, only one plan version depicts your enterprise's current organizational plan
Purpose
A plan version allows changing, modifying and comparing various organizational plans
maintained as different plan versions. If an organization has two different organizational
plans, one as per the FI hierarchy and one as per the sales hierarchy, both can be maintained
as a different plan version. However, only one of them can be active. The SAP provided plan
version suffices the need of TAYONAME.
Maintain Plan Versions for TAYO
Set Active Plan Version, In this step, you specify which plan version is to be the active plan
version, that is, the plan version in which you maintain current valid information on your
enterprise.
The following Plan Version has been defined for Tayo Rolls Limited as per the configuration:
Configuration Details
Activity
Transaction
Code
OOPV
Activity
Transaction
Code
Purpose
In this step, you make the settings necessary for changing standard object types and creating
new object types.
You can make the following settings:
You can define the relationship that should be proposed in the course of the
authorization check. For more information on this, please refer to the section
"Structural authorization".
You can create or change external object types that are not administered in PD (e.g.
object type "employee" from HR Master Data Management).
In this case, you must specify the interface program used to access these object types.
You can define an object type hierarchy for evaluations (reporting).
You can, if necessary, change the ID of a standard object type ("O" for organizational
unit, "T" for task).
Maintain Object Types for TAYO
The following action is done for maintaining Object types for TAYOas a company:
Note: You can create two-digit object types in the range "01" to "99".
Info-Types Mentioned in IN BBP
IN
Infotypes - OM
Descriptions
1000
Organization Objects
1001
Object Relationships
1003
Department/Staff
1007
Vacancy Infotype
1008
1013
Employee Group/Subgroup
Descriptions
Organization units
Positions
Jobs
Cost Centers
Person/Employee
Configuration Details
Activity
Transaction
Code
Maintain Relationship
General Description
The various object types which forms a part of organizational plan are linked to each other
using relationships. Relationships hence give meaning to the organizational plan. Standard SAP
provides a large number of relationships which are sufficient for TAYOto maintain the
organizational structure. However, there is a certain customization required regarding the
time constraint on position to person.
Purpose
In this step, you can change the attributes of an info type. An info type is a collection of
logical or business-related characteristics of an object. You can make the following settings:
You can assign infotypes to standard object types or to customer- specific object
types.
In the case of infotypes with underlying subtypes, the time constraint is defined per subtype.
If you wish to create your own subtypes, you have to carry out the step "Maintain subtypes"
and define a time constraint per subtype.
(Attach Relationship Details for CLIENT NAME)
Maintain Relationships for TAYO
The following action is done for maintaining Relationships for TAYO as a company:
Relationships
Description
A002
A003 + A012
A004
A008
A011
Reports to
Belongs to
Reports -to- Dotted Line Manager
Holder
Has cost centers
Configuration Details
Activity
Maintain Relationships
Transaction
Code
OOIT
Enter 'X' in the field Value abbr. to activate number assignment for all plan versions.
Leave the field Value abbr. blank to deactivate this function.
Save your entries.
Configuration Details
Activity
Transaction
Code
Purpose
To assign a unique number range to all the objects, we have to specify number ranges for the
objects. Specifying separate number ranges for different objects helps us in better
identification of various objects. In this step, you specify the number ranges for your PD
objects and the type of number assignment. The actual number ranges to be used will be
provided during the UAT phase for configuration on to Parallel testing TAYO and Production
CLIENT NAME.
Maintaining Number Ranges for TAYO
The following action is done for maintaining number ranges for TAYO as a company:
Enter the subgroup for which you wish to set up number assignment. The following
entries are allowed (when number assignment is not valid for all plan versions).
o
$$$$ (plan version and object type are generic)
o
Configuration Details
Activity
Transaction
Code
10
Transaction
Code
11
2. Participating in integration
The feature "PLOGI" contains criteria with which you can determine the persons in your
enterprise or personnel structure for which integration should apply.
12
Company code
Personnel subarea
Employee group
Employee subgroup
You can combine any of these criteria for integration. You can activate integration for all
employed or just for certain company codes, personnel subareas, employee groups, and
employee subgroups or for different combinations.
Make the following settings in the recommended order:
Using the entry "PLOGI ORGA", determine whether integration between Organizational
Management and Personnel Administration is active. If you do not want integration to
be active, enter ' ' (blank).
You should not change the entry "PLOGI PRELI". You can, however, change the name of
a position with this number (see Value of semantic abbreviation for the entry "PLOGI
PRELI") in Customizing for Personnel Administration.
In the entry "PLOGI PRELU", determine whether Master Data is to be updated online or
by batch input.
In the entry "PPABT PPABT", determine whether only organizational units indicated as
info type 1003 "Department" for a position are to be read.
Determine the default value for the personnel subarea in the entry "PPINT BTRTL".
Determine the default for the personnel area in the entry "PPINT PERSA".
In the entry "PLOGI TEXTC", determine whether the short texts rather than the long
text for jobs created in Organizational Management are to be transferred into
Personnel Administration.
In the entry "PLOGI TEXTO", determine whether the short texts rather than the long
texts for organizational units created in Organizational Management are to be
transferred to Personnel Administration.
In the entry "PLOGI TEXTS", determine whether the short texts, rather than the long
texts for positions created in Organizational Management are to be transferred into
Personnel Administration.
In the feature "PLOGI", determine for which persons integration should be activated
for based on the criteria company code, personnel subarea, employee group and
employee subgroup.
Note: In the standard system, the switch &PLOGI is set to "X" (all).
If you set the switch PLOGI EVENB to 'X' set Zen, you can make organizational changes
that include a change of company code.
According to the set up in your enterprise (see Activating integration), start one of the
reports in the step "Tools for Integration".
Configuration Details
13
Activity
Transaction
Code
Activity
Transaction
Code
14
Transaction
Code
15
Configuration Details
Activity
Transaction
Code
Transaction
Code
16
(We can change after getting org unit information from TAYONAME)
Define Jobs
General Description
A job describes a group of tasks, authorities and responsibilities and defines the level of
education required to perform this work. It is assigned to different positions on the basis of
the amount of work to be performed.
Jobs are areas of activity in a company, which are described by tasks.
Examples include "secretary", "clerk", or "financial accountant". Jobs can be created across
organizational units.
Purpose
In this step, you define jobs i.e. the professional activities and the areas of responsibility
within your company.
Define Jobs for TAYO
To carry out the activity for CLIENT NAME, choose the following navigation options and
perform the following:
Delete the entries that you do not need.
Create your own job definitions.
17
Configuration Details
Activity
Define Jobs
Transaction
Code
Activity
Define Jobs
Transaction
Code
18
Only position your cursor on the entries for object type S (position) in the Personnel
Administration application.
Delete the entries that you do not need.
Create your own positions and the corresponding data.
19
The following action is done for activating / de-activating Vacancy info type for TAYO as a
company:
Configuration Details
Activity
Define Positions
Transaction
Code
20
Functional requirements
Allocation criteria
Physical location
Purpose
By assigning cost centers to organizational objects, determine where costs are incurred by the
object are to be charged. The inheritance principle applies: If an organizational object is not
assigned a cost center, the cost center assigned to the superior object applies. An
organizational object may also be assigned more than one cost center.
Create Cost Centres for TAYO
To carry out the activity for CLIENT NAME, choose the following navigation options:
In this activity you make settings for cost centers. These include:
Configuration Details
Activity
Transaction
Code
21
2. Personnel Administration
Introduction
This document provides the specifications in detail to define and setup the Personnel
Administration elements such as defining company code, Personnel Area, Personnel sub-area,
employee group and sub-group.
Enterprise Structure
General Description
Enterprise structure is used to portray the specific Organizational structure of the business in
the R/3 System.
SAP assigns employees to a part of the Enterprise structure. This is performed through
assignment to a company code, personnel area and personnel sub area. All these 3 elements
are held in infotype 0001 Organisation Assignment.
Purpose
The definition of Enterprise structure is the fundamental step in a project. It is a critical
factor in how the project will be structured.
Define Company
General Description
The first level of the enterprise structure is the Company code. A company is an
organizational unit in Accounting, which represents a business organization according to the
requirements of commercial law in a particular country.
Company code is the top level of the SAP HR Enterprise structure. The company code in SAP
represents an independent company or legal entity with a separate financial accounting.
Purpose
The enterprise structure requires creation of company, which draws its own balance sheet.
Company for TAYO
The following Company has been defined for TAYO:
22
Configuration Details
Activity
Define Company
Transaction
Code
For INDIA
23
Activity
Transaction
Code
Transaction
Code
24
The following action is done for maintaining personnel areas for TAYO as a company:
a. To carry out the activity, choose the following navigation option.
b. Choose New Entries, enter the values and SAVE the entries.
Configuration Details
Activity
Transaction
Code
Personal Area
Description
CA09
U108
TAYO International
U109
TAYO INDIA
For INDIA
25
Purpose
Personnel sub-areas are a subdivision of the personnel area. The personnel sub-area is a unit
within the enterprise structure that is only used in PA. Organizational control of the main HR
sub-areas, namely the pay scale and wage type structures and work schedule planning, takes
place at the personnel sub-area level.
In this step, you define the Personnel Sub Areas in your company, adapting the functional
scope of a Personnel and Time Management to your organization for a Personnel Area.
Define Personnel Sub-Area for TAYO
Personnel sub-areas are identified by a four-character, alphanumeric code. They are used to
store the respective country-specific control features
The following action is done for Personnel Sub Areas for TAYO as a company:
a. To carry out the activity, choose one of the following navigation options:
b. Choose appropriate Personnel Area, New Entries, enter the values and SAVE the
entries.
Configuration Details
Activity
Transaction
Code
26
27
Transaction
Code
28
The following action is done for Employee Sub-Group for TAYO as a company:
To carry out the activity, choose the following navigation options:
Configuration Details
Activity
Transaction
Code
29
30
Configuration Details
Activity
Transaction
Code
Transaction
Code
31
Internal number assignment: In this case, the SAP System assigns the personnel
numbers and the number ranges are indicated by the letters "IN".
External number assignment: In this case, the user assigns the personnel numbers
and the number ranges are indicated by the letters "EX".
Purpose
The Number range intervals can be defined as per requirements and the intervals enable
assigning different number ranges to different employee groups. For TAYO, the following are
the SAP standard number ranges, it is recommended to use the standard settings.
Maintain number Range Intervals for Personnel Numbers for TAYO
The number range intervals need to be provided for TAYO
32
Configuration Details
Activity
Transaction
Code
Transaction
Code
33
34
Transaction
Code
35
Choose New entries Enter Pay scale type Title and the description.
To carry out the activity for TAYO, choose the following navigation
Configuration Details
Activity
Transaction
Code
Transaction
Code
36
criterion
Different Salary / job Grades, in TAYO are identified as Pay Scale Group.
Transaction
Code
37
Purpose
To provide the forms of addresses for employees / applicants.
Create forms of Address for TAYO
c. Choose New entries Enter Form of Address key, Title and the description, choose the
appropriate gender and the save the details
d. To carry out the activity for TAYO, choose the following navigation options:
Configuration Details
Activity
Transaction
Code
38
General Description
In this step you create possible academic titles, aristocratic titles and marks of nobility for
employees/applicants and family members.
Purpose
Name affixes are created and maintained as follows:
'S' - academic title after name (INDIA only)
'T' - academic title before name (e.g. Dr)
'V' - Aristocratic prefixes between first and second name (e.g. von, van)
'Z' - Aristocratic titles between first and second name (e.g. Baron, Count)
Create Name Affixes for TAYO
a. Choose New entries Select type of name affix, enter Name affix, Output text and
save the details
b. To carry out the activity for TAYO, choose the following navigation options:
Configuration Details
Activity
Create Name Affixes.
IMG Menu Path
Transaction
Code
39
Titles
AT
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
Name affix
ARQ.
CONT.
DIPL.-ING.
DIPL.ING.
DIPL.VW.
DIRECTOR
DR.
DR.MATH.
DR.MED.
DR.RER.NAT.
DRA.
DRS.
ING.
IR.
LIC.
MANAGER
MR.
PROF.
PROF. DR.
SUB-DIRECTOR
Output text
Arquitecto(a)
Contador(a)
Dipl.-Ing.
Dipl.Ing.
Dipl.Vw.
Director
Dr.
Dr.Math.
Dr.Med.
Dr.Rer.Nat.
Doctora
Drs.
Ing.
Ir.
Lic.
Manager
Mr.
Prof.
Prof. Dr.
Sub-director
40
Maintain Titles
General Description
In this step you create possible academic titles or aristocratic titles you use for your
employees.
Example
Purpose
This is to set up the academic/aristocratic titles for employees / applicants.
Maintain Titles for TAYO
a. Choose New Entries enter the Name affix, Output text and save the details entered
b. To carry out the activity for TAYO, choose the following navigation options:
Configuration Details
Activity
Maintain Titles.
Titles
IMG Menu Path
IMG Personnel Management Personnel Administration
AT
Name affix
Output text
Personal Data Personal Data Maintain titles
T
ARQ.
Arquitecto(a)
Transaction
T SPRO
CONT.
Contador(a)
Code
T
DIPL.-ING.
Dipl.-Ing.
T
T
T
T
T
T
T
T
T
T
T
DIPL.ING.
DIPL.VW.
DIRECTOR
DR.
DR.MATH.
DR.MED.
DR.RER.NAT.
DRA.
DRS.
ING.
IR.
Dipl.Ing.
Dipl.Vw.
Director
Dr.
Dr.Math.
Dr.Med.
Dr.Rer.Nat.
Doctora
Drs.
Ing.
Ir.
41
T
T
T
T
T
T
LIC.
MANAGER
MR.
PROF.
PROF. DR.
SUB-DIRECTOR
Lic.
Manager
Mr.
Prof.
Prof. Dr.
Sub-director
42
Transaction
Code
MarSt
0
1
2
3
4
5
6
9
43
Transaction
Code
44
General Description
In this step various address types can be created which can be subtypes of infotype 006,
Addresses.
Example: Possible address types include the following:
Permanent residence, Secondary residence, Mailing address, Standard settings
The standard SAP system contains the most common address types, It is recommend adopting
the standard settings.
Purpose
To create and maintain address types for employees / applicants to track their location of
stay while employed in the company.
45
Transaction
Code
General Description
In this step you define the valid communication types, which will be stored for addresses.
Examples
Employees may have a second telephone and fax machine at an address.
46
Purpose
This infotype enables you to record an employees various forms of communication contacts
such as a cell phone, email address, etc.
Transaction
Code
47
Activity
Transaction
Code
IMG Path: Personnel Management -> Personnel Administration>Evaluation Basis-> Monitoring of Tasks-> Determine Task Type
Transaction
Code
SPRO
48
Activity
IMG Path: Personnel Management -> Personnel Administration>Evaluation Basis->Date Specifications->Define Day Type
SPRO
Transaction
Code
49
Activity status (1 = Active employee, 2 = Retiree, 3 = Early retiree, 9 = Other, 4 = Par time
work for retirees)
Employment status (1 = Industrial worker/hourly paid worker, 2 = Salaried employee, 3 =
Civil servant, 9 = Other)
Education and training status (1 = Trainee/apprentice, 2 = Trained, 9 = Other)
50
Configuration Details
Activity
Transaction
Code
Infotype Menu
General Description
These menus can be defined so that they are dependent on the user group (user parameter
UGR).
If there are no entries for an infotype menu for the user's user group or if the user has not
maintained his/her user group, then the infotype menu is determined using the reference
user group.
Example
You want to include an infotype in an infotype menu or define a new infotype menu for a user
group.
Purpose
In this step, you define the infotype menus for maintaining and displaying Human Resources
master data.
Infotype Menu for TAYO
a. Choose menu category "I" and the infotype menu.
b. Define whether the menu is to be dependent on the user group.
c. If necessary, assign the system response for the case where the user has not
maintained the user group or where there are no entries in the menu.
d. Assign a reference user group which can be used to set up the menu, if necessary.
Infotypes in the infotype menu
a. Choose menu category "I" and the infotype menu.
b. Copy the infotypes into the menu for the user group.
e. Carry out the activity for TAYO, choose one of the following navigation options
51
Configuration Details
Activity
Infotype Menu.
Transaction
Code
Activity
Infotype Menu.
Transaction
Code
52
53
4. If necessary, assign the system response for the case where the user has not
maintained his/her user group or where no entries exist.
5. Assign a reference user group, which can be used to set up the menu if necessary.
Infotype menus in infotype menu choice
a) Choose menu category "S" and menu "01" for the infotype menu choice.
b) Include the infotype menus for the user group.
6. Carry out the activity for TAYO, choose the following navigation options:
Configuration Details
Activity
Transaction
Code
Activity
Transaction
Code
54
55
56
57
character 1 for first entries, 7 for first entries with data transfer from recruitment
and 0 for all other personnel action types.
d) If required, define the status indicator STAT1 (customer specific). This status
indicator is not used in the standard system. You can use this indicator individually.
e) Define the status indicator STAT2 (recruitment) and STAT3 (Special payment).
f) Decide whether you require standard decision rules to define plausibility rules for
the sequence of personnel action types (check feature). Note: Never change the
standard decision rules.
g) Decide whether organizational assignment data may be changed whilst personnel
actions are being carried out. When you set the indicator P, the position field in
the Actions infotype (0000) is ready for entry. You can process the fields Personnel
area, Employee group and Employee subgroup with the indicatorsPA, EG and ES.
h) Assign an infotype group number to the IG field in the personnel action type. You
can then process the the individual infotypes from the selected group in the
personnel action type in the appropriate sequence. You defined the infotype
groups in the " Define Infogroups" step.
i) Specify whether the date entered on the initial screen of the Actions infotype
(0000) is the start date for new infotype records or the end date for old infotype
records. This is especially important in the case of leaving actions.
j) Use the indicator U0000 to determine whether your personnel action type should
create a new record for the Actions infotype (0000).
k) Use the Country change indicator to determine whether the personnel action type
is a country change.
6. If you have activated the Additional Actions infotype (0302), determine whether your
personnel action type should be logged in the Additional Actions infotype (0302) using the
U0302 indicator. Call up the view Priority list for personnel action types.
7. Specify a priority list for the personnel actions which do not change the status, and for
which you have set the indicator to U0000.
8. In the Priority field assign sequential numbers with a maximum of two digits to each of the
personnel action types. The smaller the number, the higher the priority of the
accompanying personnel action type.
Do not define any new personnel action types if only the infotype group should be different
for the personnel administrator. To achieve this, you can define the infogroups as user group
dependent.
The keys for personnel action types, which you carry out for an employee, for example,
hiring, organizational change, leaving, are stored in the infotype Actions (0000).
The existence of a personnel number is ruled out by the existence of a record in this infotype.
Only one record can exist for this infotype on the database at any one time.
When an employee has left, there is also a record in the system for the personnel action
Leaving. The most important information in this infotype is the employee's employment
status: active, leave of absence, retired, left.
Personnel actions that are only used to process several infotypes in an infogroup should not be
saved in the infotype Actions (0000). SAP recommends that you log personnel actions of this
kind automatically using the Additional actions infotype (0302).
Notes on the creation of batch-input sessions:
58
If you want to carry out a batch-input for a personnel action, do not call up transaction PA40
(Actions menu). Instead, call up transaction PA30 (infotype menu). In the actions menu place
your cursor on the line containing the relevant action; this assumes you know the exact set-up
of the menu.
Proceed as follows:
1. Call up transaction PA30.
2. Choose the Actions infotype (0000).
3. Enter the personnel action type in the Type field.
4. When processing entry actions, enter the function code '=INS', for other actions, enter the
function code '=COP'.
Steps to proceed :
Choose - Activation 'Additional Actions', Remove the tick mark from TEST and execute, the
proceed with maintaining data in Personnel Action Types.
Carry out the activity for TAYO, choose the following navigation options:
Configuration Details
Activity
Transaction
Code
59
Transaction
Code
60
61
Activity
IMG Menu Path
Transaction
Code
62
IMG Path: Personnel Management->Personnel Administration>Customizing User Interface ->Change Screen Header->Infotype
header data selection control
Transaction
Code
SPRO
63
Configuration Details
64
Activity
IMG Path: Personnel Management->Personnel Administration>Customizing User Interface ->Change Screen Modifications
Transaction
Code
SPRO
65
4. Time management
The Time Management component offers support in performing all human resources processes
involving the planning, recording, and valuation of employees work performed and absence
times.
The scope of functions within Time Management encompasses:
The existing work schedule at Corporate Office and Factory for all the shifts needs to be well
defined. Time Recording will enable entering employee time data for Attendance, Absence,
Leave, Off etc. This data shall be entered as clock times or in hours. The user will update the
attendance record manually in SAP and the data is transferred for payroll. Swipe Card Time
recording machine would be integrated with SAP system.
Time Management supports centralized data entry by time data administrators, decentralized
data entry by production supervisors, for example, if an employee applies for leave, the
supervisor if he is an authorized SAP user can fill up the required leave type infotype.
Time Management performs all human resources processes involving the planning, recording,
and valuation of employees work performed and absence times This also takes care of special
rules for personnel sub areas, employee subgroups, or even individual employees in the SAP
System.
The business requirements shared are mentioned below:
The items specified in the following sections, will be configured in SAP to address the
requirements of the processes.
66
Tcode: SPRO
to create work schedule first create Holidays for the current year and assign public holidays
to Holiday calendar and this holiday calendar is assigned to Work schedule.
The menu path below gives the way path from where holidays and calendar can be created.
67
For Fixed Holidays like August 15th or 26th Jan use this option
68
Create as many holidays as possible for the following calendar year. Finally can view
all this holiday in the below mentioned table.
For Floating public Holidays Like Bengali New year, Dulhendi, Dussera, Diwali which is
not constant every year use this option
69
70
71
Click this to
include delete
holidays from
the calendar
72
Activities
1. Assign grouping 40 for work schedules to your personnel areas or subareas.
2. If necessary, you can assign your personnel areas and subareas different groupings for work
schedules at a later stage.
Activities
1. Check SAP's reference entries and do not change them for the first step.
2. You can specify new assignments later, if necessary.
73
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.
In the following steps, you set up daily work schedules.
Activities
1. Check the standard work break schedules.
2. Create new work break schedules if necessary.
a) Assign your work break schedules to grouping 01 for daily work schedules.
b) Enter the name of your work break schedule in the Work break schedule
field.
c) Assign as many planned working time breaks as you wish to your break
schedule, and a maximum of four overtime breaks, and number them
sequentially.
d) Enter the start and end times of the break in the fields provided.
e) Specify the break duration for each break type in the Unpaid break period or
Paid break period fields (in industry minutes).
f) Use the P field to indicate breaks after 12 midnight during night shifts.
g) If the break does not have to be taken at a specific time but after x hours of
work, enter the number of hours in After hrs. The Start and End fields remain
74
empty in this case. In the standard system, the start of planned working time is
taken as the starting point for calculating dynamic breaks. You can change this
in time evaluation.
h) If you only want selected breaks to be processed in time evaluation, enter
an indicator of your choice in the Type 1 or
Type 2 field. Use operation TFLAG to specify which breaks should
be taken into account in time evaluation, according to the entries
in the Type 1 and Type 2 fields.
i) Enter "0" in field Type 1 for breaks outside of planned working
You also define daily work schedules for availability in this step.
Activities
1.
2.
3.
4.
5. In the Planned working hours field, enter the working time that an employee has to
work each day.
75
By entering the working time, the planned working hours are calculated by the system.
Paid break times are added and unpaid breaks are deducted.
6. Select the Planned working hours = 0 field if this daily work schedule reflects a nonworking day.
7. If you want to create a basic variant of a daily work schedule, you can enter a rule
number or name for a daily work schedule selection rule in the Daily work schedule
selection rule field, from which the daily work schedule variants are determined.
8. Enter the desired working time using one of the following definitions of working
time:
a) Fixed working time
b) Flextime
o Enter the times you want to use to calculate the planned working hours in the
Normal working time field. No entries should be made here for other daily
work schedules.
o
Enter up to two core times in the Core time 1 and Core time 2 fields.
c) Breaks
In the Work break schedule field, enter the break schedule containing your
desired break times.
d) Tolerance times
In the Start of tolerance and End of tolerance fields, enter the tolerance times
if postings within a given tolerance timeframe should be adjusted to the start
or end of planned working time in time evaluation.
9. Enter a valuation.
You can use the Minimum working time, Maximum working time, Compensation time
and Additional hours fields in the personnel calculation rules in time evaluation.
10. Classify the daily work schedule for time wage type selection or time evaluation
using a value from 0-9.
Based on the work schedule class, you can then specify special regulations in time
wage type selection or time evaluation.
11. Select the Automatic overtime if you want working time that exceeds the
specified planned working time to be valuated as overtime in time evaluation.
The personnel calculation rule T015 calculates overtime in time evaluation.
12. If you use the Overtime infotype (2005), you can use the Reaction to overtime and
Reaction to overtime in core time fields to set reaction indicators for flextime daily
work schedules.
76
77
78
79
Activities
1. Check the sample entries in the standard system.
2. If necessary, create new entries.
a) Call the detail screen to create new work schedule rules by choosing the
New entries function.
b) Make entries in the Employee subgroup grouping, Holiday calendar ID, and
Personnel subarea grouping fields, and enter an appropriate validity period.
c) Enter a name for the work schedule rule in the Work schedule rule field.
d) Enter the agreed working time per day, week, month, and year in the
"Working time" block. Under Working hours per day, you can enter a different
number of planned working hours than is specified in the daily work schedule.
Your entries can be accessed in the Planned Working Time infotype (0007), and
can be queried in Time Evaluation and Payroll.
e) Enter the appropriate rule in the Rule for day types field.
f) Enter the period work schedule for the work schedule rule in the Period
work schedule field.
g) In the Reference date field, enter a date to indicate the start of your period
work schedule.
h) In the Starting point field, enter the number of the day in the period work
schedule on which you want the reference date to fall. If you want it to be the
fourth day of the third week in the period work schedule, enter 2*7+4=18.
80
Activities
1. Enter the employee subgroup grouping
2. Enter the public holiday calendar ID
3. Enter the personnel subarea grouping
4. Enter the work schedule rule you want to generate
5. In the Calendar month from - to fields, enter the time span for which you want to
generate, change or delete the work schedule
81
82
83
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.
Example
You want to define the Educational leave absence type for a particular personnel subarea
grouping. When this absence is recorded for an employee and the start or end date is a day
off, the system should reject the entry.
Activities
1. Decide which absence types you want to define for your enterprise.
2. Decide how the system should react in each of the following situations:
a) The first day of the absence is a day off
b) The last day of the absence is a day off
c) The entire period consists of days off
3. Enter the minimum duration of the absence in the Minimum number of days field.
If you want to define an absence, which can last less than one day (e.g. leave), enter
000 in this field.
4. In the Maximum number of days field, you can limit the duration of an absence
(e.g. illness with continued pay).
o Default value 999 - unlimited absence
o
5. Activate the Second date obligatory field, if you must specify the end date as well
as the start date when you are assigning the absence type.
84
85
Activities
86
1. Decide whether one employee subgroup grouping for time quota types is adequate.
2. Group your employee groups and subgroups for time quota types.
87
Activities
1. Decide which types of entitlement to time off your employees have.
2. Define the absence quota types you want to use based on the groupings.
Use the SAP standard entries as a guide. If necessary, define additional absence quota
types.
3. In the field Unit of Time/Measurement define whether you want the entitlement to
time off to be maintained in hours or in days.
4. Assign a time unit to the quota type.
5. If you define an absence quota type with a time unit in hours, you can enter default
values for the start and end times. These are proposed in the Absence Quotas infotype
when you enter absence quotas.
Example: In your enterprise, employees are only allowed to take time off for
overtime in the afternoon. Enter 12:00 (noon) to 24:00 (midnight) as the default
values for start and end times.
88
6. Enter the time constraint class for the absence quota type. The step Specify
System Reaction to Overlapping Time Infotypes contains information on the concept
of defining time constraint classes.
7. In the field Negative deduction to, specify whether and to what extent there can be
negative deduction of entitlement to time off.
9.
In the Rounding field, specify how absences of less than one workday should be
deducted from a quota which is maintained in whole days.
89
90
Activities
1. Enter the Employee subgroup grouping and the Personnel subarea grouping for time
quota types for which you want the deduction rule to be valid.
2. Enter the deduction rule. Use an easy to recognize name so that you can easily
remember your rule.
Make sure to specially Indicate deduction rules that can be used to enable deduction
over and above entitlement. This will make it easier to assign deduction rules to the
counting rules.
3. Enter the unit for the attendance/absence quota types that are to be deducted
using this rule.
4. If required, enter the attendance/absence quota types that should be deduction
using this rule.
91
92
Activities
To get a better overview, you can access a view cluster in this step. This allows you to check
the entries you have made so far.
1. Call the Counting Rule view. To do this, choose Counting rule under Navigation.
2. Choose the required counting rule.
3. Under Quota deduction, enter the deduction rule that applies until the employee's
quota entitlements have been used up.
4. If required, enter the deduction rule for the absence and attendance quota types
that can be deducted over and above the entitlement.
The deduction rules in the Within entitlement and Over entitlement fields must
deduct absence and attendance quotas using the same time unit. This applies to all
sequential numbers of a counting rule.
The deduction rules for absence and attendance quotas can deduct in different time
units.
93
94
95
96
97
Activities
98
99
Activities
1. Under Define base entitlement; determine the employee groupings for which you
want to specify a base entitlement.
2. Define a rule for the base entitlement
3. Enter a sequential number if you want to create a number of different rules for
determining the base entitlement according to the age or seniority interval
4. If applicable, enter the age or seniority intervals to which you want the base
entitlement to apply; the intervals are inclusive
If you do not make any entries here, the base entitlement is determined
independently of the employee's age or seniority
5. Enter a constant for the base entitlement, or if you use time evaluation, a day or
period balance from which the system can read the base entitlement
6. Enter the base period; this is the period for which the base entitlement is valid
7. If you want the base entitlement to be calculated during time evaluation, create
the prerequisites: Use the Refine calculation of base entitlement activity to create a
personnel calculation rule in which you specify the entitlement according to further
organizational assignments, for example. Use the Adapt schema activity to insert the
personnel calculation rule in your time evaluation schema before functions CUMBT and
QUOTA
100
101
102
103
104
105
Deduction interval
The deduction interval specifies the period in which an employee can deduct records in the
Absence Quotas infotype (2006) that have been created during time evaluation (2006).
106
A period defined in the quota selection rule, such as the accrual period
107
Validity interval
By entering the validity period, you specify the valid from and valid to date of the record
from the Absence Quotas infotype (2006) that is created during time evaluation for the
specified absence quota type.
Use
108
Use
By selecting the relevant field, you can specify whether you want the absence quota type to
be generated in time evaluation and how you want it to be generated.
If you 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).
109
Use
Quota type selection takes place in the time evaluation schema using function QUOTA.
Procedure
The confirmation value of the feature is a two-digit numerical quota type selection rule
group.
110
111
3. Specify the time constraint class for the attendance type. The section Specify
System Reaction to Overlapping Time Infotypes contains information on the concept
of defining time constraint classes, using absences as an example.
112
5. Enter the conditions for the current day if you want attendances and absences to be
counted differently on certain days.
113
114
115
4. Payroll
Glossary
AlGrp
BBP
CI
CAP
EE
EG
ER
EDLI
ESG
HRA
IMG
INVAL
LTA
LTC
PA
PSA
PCR
PF
RAPs
RPFC
PTax
WT
Allowance Grouping
Business Blueprint
Configurable Item
Collective Agreement Provision
Employee
Employee Group
Employer
Employee Deposit Linked Insurance
Employee Subgroup
House Rent Allowance
Implementation Guide
Indirect Valuation
Leave Travel Allowance
Leave Travel Concession
Personnel Area
Personnel Subarea
Personnel Calculation Rule
Provident Fund
Reimbursements, Allowances & Perks
Regional Provident Fund Commissioner
Professional tax
Wage Type
116
B A S I C PAY
General Information
This section describes the Configurable Item in brief:IMG Path
Personnel Management
Payroll Data
Personnel
Administration
Basic Pay
This section describes the Configurable Item in detail:Purpose
In this section, input values for the Basic Pay infotype (0008) shall be created which
will be used for Payscale classification and standard pay increase.
Description
Monthly regular earnings of the employees are created in the Basic pay Infotype.
Wage types will be defaulted based on the wage type models assigned to Employee
Subgroups (Reference: LGMST Feature) are created in this Infotype. Also wage types
which will be defaulted based on the data maintained in Infotype: 581
(HRA/COA/CLA) and Infotype: 583 (Car & Conveyance) are incorporated in this basic
pay infotype.
Explanation
Infotypes
Populated
0008
Tables
storing
relevant
data
117
Remarks
Unlike other Infotypes (0014, 0015) Basic pay Infotype cannot be delimited.
118
1. 0008
Tables
storing
relevant
data
1. Table: V_503_B
Relationship
with Other
Nodes
1. Not Applicable
119
120
Remarks
The meanings of the grouping for the personnel calculation rule are fixed and must
not be changed.
1.1
Payscale Type
Enter Payscale Type and Payscale Type text in the appropriate columns
in the screen Change View Payscale Type.
Click on Save Button
0008
Tables
storing
relevant
data
Table: V_T510A
121
Remarks
Delete any entries you do not require.
Set up the pay scale types with the appropriate data according to your requirements
Payscale Area
This section describes the Configurable Item in detail:Purpose
In this section, Payscale areas for TAYO ROLLS LIMITED shall be determined. This will
be based on the geographical applicability of wage types.
Description
Payscale areas shall be decided based on the geographical location affects the
compensation of the employee. This can be determined based on the Collective
Agreement and location based requirements of TAYO.
Explanation
0008
Tables
storing
Table: V_T510G
Basic Pay
122
relevant
data
Relationship Not Applicable.
with Other
Nodes
Configuration Description - Payscale Area
Remarks
Delete any entries you do not require.
Set up the pay scale areas with the appropriate data according to your requirements
123
Description
Payscale Types and Payscale areas shall be assigned to Personnel Areas and Personnel
Sub areas based on the applicability. This is a link created between the Payscale
structure and Enterprise Structure. The Payscale Area and the Payscale Type can be
assigned to the personnel area and personnel sub area that have already been
configured.
This node cannot be maintained where more than one combination of Payscale type
and Payscale area are assigned to a combination of Personnel Area and Personnel
Subareas. This assignment is possible at the IT8 level only.
Explanation
Infotypes
Populated
1. 0008
Tables
storing
relevant
data
1. Table: V_001P_C
Relationship
with Other
Nodes
1. Check
Pay
Scale 2.4
2. Check
Area
Pay
Scale 2.5
Type
Basic Pay
124
125
Remarks
This node shall be configured only in case of One combination of Payscale Area and Payscale Type for a combination of Personnel
Area and Personnel Subarea.
One combination of Payscale Area and Payscale Type for multiple combinations of
Personnel Area and Personnel Subarea.
126
Description
Feature provides default values based on the decisive operations. TARIF Feature
provides default Payscale Type and Payscale Area based on the decisive operations
defined (Country Grouping, Company Code, Personnel Area, Personnel Sub Area,
Employee Group and Employee Sub Group). This feature helps in defining more than
one Payscale Type and Payscale area to Personnel Area / Personnel Area based on
Employee Group / Employee Subgroup.
Feature helps in reducing data entry.
n
Explanatio
2. Select TARIF
in
or Choose F5.
(Enter).
4. Choose WERKS from the displayed list and press Enter button
(F5)
on
(Enter).
9. Choose BTRTL from the decision criteria list and click on Create
127
Personnel Areas.
10. Select required personnel Subareas displayed in the tree structure
(F5)
which lead to sub screen: TARIF: Choose node type for new nodes.
12. Choose field for decision operation in sub screen opened and Click
on
(Enter Button). Select PERSG from the decision criteria list
displayed in the Filed selection for decision operation screen and
Click on
(Enter Button), which will display
in the tree structure.
13. Select
choose create
and choose
(F5)
button, which will open Choose Node Type for New Nodes.
16. Choose Return Value in the sub screen and click on
(Enter
Button) which lead to sub screen: Return value for field value.
(Transfer) which
18.Repeat the same steps to create default values for all the
Personnel Areas/Personnel Subareas/Employee Groups.
19. Choose
by system
(F5) which
20. Choose Return Value in the sub screen opened and Click on
(Enter) which lead to another sub screen: Return value for Field
Value otherwise.
Infotypes
Populated
1. 0008
Basic Pay
Tables
storing
relevant
data
1. Table: V_001P_C
Relationship
with Other
Nodes
1. Check
Pay
Scale
Pay
Scale
Type
2. Check
Area
129
Remarks
This is not a mandatory and this assignment can be at employee level.
130
Purpose
In this step, you represent the collective agreement governing payment of your employees in
the SAP system. This grouping shall be based on the Payscale Area, Payscale Type, Payscale
Group and ESG grouping determined earlier.
Description
Payscale Groups & Levels shall be decided based on the Payscale Type and Payscale Areas and
compensation structure applicable. Indirect Valuation of Wage Types in Basic Pay Infotype
(INVAL A Default Amount) shall be entered here. This Grouping can be done based on the
Employee Subgroup grouping for Collective Agreement Provisions, Payscale Group, Payscale
Level, Payscale Type and Payscale Areas.
Explanation
2. Enter Payscale Area and Payscale Type in the appropriate fields of the
subsequent screen Determine Work Area: Entry.
3. Click on Enter Button
Groups screen.
4. Click on
and Enter ESG Grouping, Payscale Group,
Payscale Level, Wage Type, Start date, End date and Default amount
(where ever necessary).
5. Save data by clicking on
6. Click on Back button
Infotypes
Populated
1. 0008
Tables
storing
relevant
data
1. Table: V_T510
Relationship
with Other
Nodes
or by pressing Ctrl + S.
Basic Pay
131
132
Remarks
Before configuring this node, first Wage Types for Basic Pay Infotype (0008) Permissibility shall
be created.
Purpose
In this step, Wage Types for infotype Basic Pay (0008) can be created by copying the model
wage types in the standard system.
Description
Wage types are nothing but salary/pay components of the employee remuneration. Only
wage types, which are to be used in infotype Basic Pay (0008) shall be created here. There
are two types of wage types are available in SAP: Technical Wage Types and Model Wages
Types.
Technical wage types starts with / and Model Wage Types starts with M. Always
Wage Types shall be copied from Model Wage Types. For example, to create Basic Pay Wage
Type choose MB10 Model wage Type.
Explanation
1. Click on
2. Select
3. Click on.
Select
5. Enter Wage Type Number and Text and Short Text in the appropriate
columns.
6. Remove Flag Mark from Test Run Indicator.
wage types.
7. Click on Copy Button
8. Ensure Error Status is
9. Click on
before copying
.
in Copy Wage types screen.
10. Select
in the Wage Type Maintenance Screen. Enter Wage
Types to be deleted in the Delete wage Type Column. Remove Test Run
Indicator before clicking on the
Infotypes
Populated
1. 0008
Tables
1. Table: V_T511
Basic Pay
133
storing
relevant
data
2. Table: V_T512T
Relationship
with Other
Nodes
Not Applicable
3. Table:V_512W_D
134
135
136
Remarks
Please note that Wage Types shall be copied from relevant Model Wage Types only, so that
wage type characteristics shall be copied and updated in relevant tables automatically. If
suitable wage types are not available in the system, choose most suitable/relevant model
wage types and update the required characteristics in Table:V_512W_D.
Purpose
In this section, assign wage types crated in this node to wage type group 0008.
Description
Model wage types are already assigned to wage type group in the standard system. While
copying wage types some wage types shall be grouped in Basic Pay Infotype and some are in
other Infotypes like 0014 & 0015. Wage types which are created for Basic Pay Infotype
purpose shall be checked and assigned here, if not automatically updated.
Explanation
Click on
for wage type group Basic Pay Infotype Screen.
Check all wage types under this group are reflecting are not.
If some wage types are not found, Click on
, and enter the missing
wage type code in the wage type Column.
Click on Save button
(Ctrl + S) to save entries made.
Infotypes
Populated
Tables
storing
relevant
data
137
138
139
140
Remarks
If wage types shall be moved from one wage type group to another wage type group this table
shall be updated first.
Purpose
This section allows for changing the text of the wage type.
Description
Changing of Wage Types Text and Short Text can be changed here based on the requirements
like change in Wage Type Name, Wrong Entry of Wage Type Text etc.
Explanation
Infotypes
Populated
Tables
storing
relevant
data
Click on
for Check Wage Type Text screen.
Check and Update required Wage Types Long Text and Short Text.
Click on
to save the changes made.
Click on Back button
(F3) to come out of the screen.
0008
Basic Pay
V_512W_T
141
Remarks
Wage type short texts are used when printing out payroll accounts.
Purpose
This section allows you to define the date on which wage types may be entered.
Description
Entry permissibility of the wage types for Basic Pay Infotype shall be entered here. Depending
on the (time based) requirements permissibility of the wage type shall be updated by entering
the desired date in Start Date field of the particular wage type.
Explanation
1. 0008
Tables
storing
relevant
data
1. V_T512Z
Relationship
with Other
Nodes
1. Not Applicable
Basic Pay
142
Remarks
Enter default end date for each wage type as 31.12.999.
Purpose
In this section, you can define which wage types may be entered for primary wage type
groupings. Permissibility of wage types to Employee groups shall be assigned in this node
based on the requirements.
143
Description
Permissibility of wage types to Employee Subgroups and Personnel Sub areas shall be
configured here. Permissibility values shall be assigned based on the groupings of
Employee Subgroups and Personnel Subareas to Primary wage type. There are 3 types
indicators provided in the system. Wage type is totally permissible if indicator: 1 is
put in the appropriate column, Wage Type is permissible with warning if Indicator is 2
and if Blank wage type is not permitted. Before configuring this node, configuration of
Employee Subgroups for Primary wage types and Personnel Subareas for Primary wage
types shall be configured.
Explanation
Infotypes
Populated
1. 0008
Basic Pay
Tables
storing
relevant
data
1. V_511_B
Relationship
with Other
Nodes
1.
2.
Configuration Description: Wage type permissibility for each ESG & PSA.
144
145
146
Remarks
Employee Subgroups for primary wage types and Personnel Subareas for primary wage types
nodes shall be configured first.
Assign appropriate indicators to wage types based on the requirement and applicability.
Purpose
Wage type characteristics for shall be configured in this node.
Description
Wage Type Characteristics like Payment / Deduction wage type, Minimum and Maximum
amount permissible, Indirect Valuation method of wage type, Rewritable Indicator and period
of validity of wage type characteristics shall be configured here. Wage Type Characteristics
has to be maintained individually for each wage type.
Explanation
147
1. 0008
Tables
storing
relevant
data
1. V_T511
Relationship
with Other
Nodes
1.
Basic Pay
2.
Create Wage Type Catalogue.
148
Remarks
Wage Characteristics for each wage type shall be maintained individually for each wage type.
If overwrite indicator is marked INVAL Wages, system shall allow to over write the defaulted
amounts, otherwise changing of amounts is not possible.
Purpose
This section allows to combine different employee subgroups for primary wage types
Description
In order to differentiate wage types applicability to Employee Groups and Employee
Subgroups in the Company, Grouping for the primary wage types must be finalized. You can
use these groupings to specify which wage types may be entered for which employee
subgroups. These wage type grouping shall be used in configuring Define Wage Type
Permissibility for PS & ESG.
149
Explanation
Infotypes
Populated
1. 0008
Basic Pay
Tables
storing
relevant
data
1. V_503_G
Relationship
with Other
Nodes
1.
2.
150
Screen 1 :
Remarks
Grouping shall be permitted between 0 to 9 only.
Groupings for this purpose shall be defined keeping in view of wage types in other infotypes
also.
151
Purpose
This section allows to combine primary wage types applicability for different personnel
subareas.
Description
In order to differentiate wage types applicability to Personnel Subareas (location based) in
the Company, Personnel Subarea Grouping for primary wage types shall be defined.
These
groupings can be used to specify applicability wage types to employees of the personnel
subarea by defining Wage Type Permissibility for PS & ESG.
Explanation
Infotypes
Populated
1. 0008
Basic Pay
Tables
storing
relevant
data
1. V_001P_K
Relationship
with Other
Nodes
1.
2.
152
153
Remarks
Grouping shall be permitted between 0 to 9 only.
This activity is not mandatory and should be carried out only if you want to limit the entry of
wage types to certain personnel Subareas.
Groupings for this purpose shall be defined keeping in view of wage types in other infotypes
also.
Purpose
In this section LGMST Feature (Planned Remuneration specification) shall be configured.
154
Description
Feature provides default values based on certain decisive operations. This LGMST Feature
(Planned Remuneration specification) provides default wage types based on the decisive
criteria like Personnel Area / Personnel Subarea / Employee Group and Employee Subgroup.
Whenever an employee is hired / transferred to other personnel subarea, system will provide
list of applicable wage types in Basic Pay Infotype (0008).
Explanati
on
3. Choose field for decision operation in sub screen LGMST: Choose node
type for new nodes and Click on
(Enter).
4. Choose MOLGA (Country Grouping) in the list of decisive operations
displayed in the sub screen: Field selection for decision operation and
Click on
(Enter/Copy).
5. Choose MOLGA displayed in the LGMST: decision tree and Click on Create
(F5), which lead to sub screen Country grouping. Choose Country
Grouping (40) India and on
(Enter/Copy), which shall copy to
decision tree structure.
6. Select (40) India in the displayed tree structure and choose Create
(F5), which lead to sub screen: 40: Choose node type for new nodes.
7. Choose Filed for decisive operations in the sub screen and Click on
(Enter) which lead to another screen: Field selection decision operation.
8. Select BUKRS (Company Code) and Choose
same to LGMST: tree structure.
9. Select BUKRS (Company Code) in the tree structure and Choose Create
(F5) which lead to sub screen: Company code
10. Choose Company Code form the list displayed in the tree structure and
click on
(Enter) to transfer Company code to LGMST tree structure.
11. Select Company Code & Company displayed in the tree structure and
Choose
(F5) to reach sub screen: Choose Node type for New nodes.
12. Select field selection for decisive operation in the sub screen opened and
click on
(Enter) which lead to another sub screen Filed selection for
decisive operation.
13. Choose BTRTL (Personnel Subarea) in the sub screen opened and choose
(Enter) to transfer the same to tree structure.
155
16. Choose Field for decision operation in the sub screen opened and choose
(Enter) which lead to another sub screen: Field selection for decision
operation.
17. Select PERSG (Employee Group) in subsequent screen opened and choose
(Enter) transfer the same to tree structure.
18. Choose PERSG in the tree structure and Choose
(F5) which lead to sub
screen Values for PERSG. Enter applicable Employee Groups in the
appropriate columns (PERSG Table) of the sub screen opened and Choose
(Enter) to transform the values to the tree structure.
19. Select on of the Employee Groups displayed in the tree structure and
choose
nodes.
(F5) which will lead to Sub screen Choose Node type for new
20. Select Field for Decision operation in the sub screen opened and Choose
(Enter) which will lead to another sub screen Field selection for
decision operation.
21. Select PERSK in the sub screen opened and choose
transform the value to LGMST: Tree Structure.
22. Select PERSK node in the tree structure and choose
lead to Values for PERSK sub screen.
(Enter) to
(F5) which will
23. Enter list of applicable Employee Subgroups in the table displayed in the
sub screen and choose
(Enter) to transform the value to LGMST: Tree
Structure.
24. Select one of the Employee Subgroups and choose
Sub screen Choose Node type for new nodes.
25. Select Return value in the sub screen opened and choose
enter decision criteria (wage type model).
to enter to
26. Enter applicable wage type model (20/----ILJ1) in the Enter a value filed
of the sub screen: Return value for field value E3 and choose
to
transfer the wage type model to the Employee Subgroup in the LGMST
sub screen.
27. Repeat the same steps to all the employee subgroups of all personnel
subareas to assign applicable wage type models.
28. Click on
156
(Ctrl
29. If default value applicability is changed during the period, select the
value to be changed and Choose
(Shift + F3), which lead to sub
screen: Change return value for field value.
Infotypes
Populated
1. 0008
Tables
storing
relevant
data
1. T539A
Relationshi
p
with
Other
Nodes
Basic Pay
Remarks
Not Applicable.
Purpose
In this step, default wage types for the Basic Pay infotype (0008) shall be configured. Wage
types will be defaulted, based on the Wage type model determined for the Employee
Subgroup/Location determined in the, at the time of hiring action.
Description
Wage Type Models shall be created to default wage types for the Basic Pay Infotype (0008)
based on the Company Structure. Personnel Areas / Personnel Sub Areas / Employee Groups /
Employee Subgroups can de used as decision criteria while deciding Wage Type Models. Wage
type model is nothing but list / group of wage types applicable to the employee groups. Mode
Indicator F shall be used to Wage Types which are mandatory for the Wage Type Model and
Mode Indicator O shall be use for the wage Types which are not mandatory and these wage
158
types can be changed based on the requirement and applicability. By configuring LGMST
Feature using these Wage Type Models, system displays list of applicable wage types in Basic
Pay Infotype (0008) when ever the employee is hired, promoted and transferred to another
department / personnel area / personnel sub area. This helps in reducing Administrative
problems and reducing data entry work.
Explanation
Infotypes
Populated
1. 0008
Basic Pay
Tables
storing
relevant
data
1. V_T539A
Relationship
with Other
Nodes
159
Purpose
In this step, indirect valuation for wage types shall be defined based on the Module variant
mentioned in the Wage Type Characteristics node (INVAL B).
Description
Indirect Evaluation is a method to calculate the eligible amounts (default) for some of the
wage types. INVAL is the Indirect Evaluation Module used to meet the Indian specific business
requirements. INVAL with Module variant A shall be used to default fixed amounts and Variant
B
shall be used to calculate amount on percentage basis on some other wage type.
Amounts for wage types calculated on percentage basis (INVAL B) shall be configured here.
INVAL and module variants shall be maintained for required wage types in Wage Type
characteristics node.
Enter Indirect Valuation Module Name (PRZNT), Valuated Wage Type (Wage Type Code for
which amount is calculated by using INVAL - B), Enter serial no, if the amount is calculated
on wage types, start date and end date for the, Base Wage Type (on which amount is
calculated for valuated wage type) and percentage (to be calculated on base wage type).
Explanation
3. Details of module name, valuated wage type, base wage type and
percentage in the appropriate fields of the table as mentioned in the
below mentioned screen.
4. Click on
6.
Infotypes
Populated
1. 0008
Tables
storing
relevant
data
1. V_T539J
Relationship
with Other
Nodes
1.
Basic Pay
2.
Wage Type Characteristics.
160
Screen shot
Remarks
INVAL details shall be entered for required wage types in Wage Type Characteristics, specify
Percent in Time / Measurement Unit and requirement of overwrite Indicator.
Unlike the wage types that are evaluated through INVAL A, where a wage type can have
different values for different groupings, here a wage type can have a single relationship for
all Allowance groupings.
Purpose
This SAP Enhancement is developed to update default values / increment amount in case of
promotion / transfer of employee in TAYO.
Description
161
Promotion Action: Grade wise promotion benefit (increment) amount, which shall be added
to basic salary (wag type: 1000) and other benefits (Conveyance Allowance, Transport
Allowance and other Car related benefits) are hard coded in the programme. Incase of
Promotion Action, first it checks to which grade to employee is promoted (Employee Subgroup
in Infotype: 0001). Programme automatically updates the revised basic salary, which will be
arrived after adding up the eligible increment amount to existing basic salary. Also it will
compares the other benefits currently the employee is entitled and the benefits employee is
eligible for due to promotion and will be updated accordingly.
Trigger Point
This USER EXIT will be triggered automatically only incases of Promotion and Transfer
Actions executed in Personnel & Administration Module.
Output
This USER EXIT updates automatically the increment amount and other allowances (in
Infotype: 0008) applicable based on the new grade. This also updates the locations based
allowances based on the personnel subarea to which employee is transferred. This helps in
reducing data entry and administrative convenience to Administrator.
162
R e c u r r i n g P ay m e n t s & D e d u c t i o n s
General Information
This section describes the Configurable Item in brief:IMG Path
Purpose
Payment and deduction wage types with periodic / regular in nature are configured in this
section.
Description
Recurring payments/deductions are wage elements which are paid or deducted in every
payroll period. In contrast to additional payments, recurring payments/deductions are paid or
deducted within a defined periodicity.
Explanation
1. Click on
1. 0014
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable
163
2.1
Purpose
In this step, Payment & Deduction Wage Types for infotype Recurring Payments & Deductions
(0014) shall be created by copying the model wage types in the standard system.
Description
Wage types which are to be used in infotype Recurring Payments and Deductions (0014) shall
be created in this step, which shall be copied from Model Wage Types which starts with M.
Choose Model wage Types with payment characteristics for Payment Wage Types and with
deduction characteristics for Deduction wage types.
Explanation
1. Click on
2. Select
3. Click on.
Select
5. Enter Wage Type Number and Text and Short Text in the appropriate
columns.
6. Remove Flag Mark from Test Run Indicator
wage types.
before copying
10. Select
in the Wage Type Maintenance Screen. Enter Wage
Types to be deleted in the Delete wage Type Column. Remove Test Run
164
1. 0014
Tables
storing
relevant
data
1. Table: V_T511
Relationship
with Other
Nodes
1. Not Applicable
2. Table: V_T512T
3. Table:V_512W_D
Screen 2 :
165
166
Purpose
In this section, assign wage types to a wage type group - 0014.
Description
Model wage types are already assigned to wage type group in the standard system. While
copying wage types based on the characteristics copied wage types shall be grouped in
Infotypes: 0008, 0014 & 0015. Wage types which are created for Infotype Recurring Payments
& Deductions shall be grouped here.
Explanation
2. Check all wage types under this group are reflecting are not.
3. If some wage types are not found, Click on
missing wage type code in the wage type Column.
4. Click on
1. 0014
Tables
storing
relevant
data
1. VV_52D7_B_0014_AL0
Relationship
with Other
Nodes
1. Not Applicable.
167
Purpose
This section allows changing the texts of the wage types.
Description
Changing of Wage Types Text and Short Text can be changed here based on the requirements
like change in Wage Type Name, Wrong Entry of Wage Type Text etc.
Explanation
1. Click on
2. Check and Update required Wage Types Long Text and Short Text.
3. Click on
1. 0014
Tables
storing
relevant
data
1. V_512W_T
168
Relationship
with Other
Nodes
1. Not Applicable.
Purpose
This section allows defining wage types, which are allowed for this infotype.
Description
Entry permissibility of the wage types for Recurring Payments & Deductions Infotype shall be
entered here. Depending on the (time based) requirements permissibility of the wage type
shall be updated by entering the desired date in Start Date field of the particular wage type.
Explanation
169
2. Check and Update wage types if by clicking on the New Entries in the
Permitted Wage Types Screen opened.
3. Enter required Wage Types, period start date, end date and flag mark in
the required fields of the Table: Allowed Wage Types for Recurring
Payments & Deductions.
4. Click on
1. 0014
Tables
storing
relevant
data
1. V_T512Z
Relationship
with Other
Nodes
1. Not Applicable.
170
Purpose
In this section, permissibility of wage types shall be defined based on Employee Subgroup
Grouping and Personnel Subarea grouping for primary wage types.
Description
Permissibility of wage types to Employee Subgroups and Personnel Sub areas shall be
configured here. Permissibility values shall be assigned based on the groupings of Employee
Subgroups and Personnel Subareas to Primary wage type. There are 3 types indicators
provided in the system. Wage type is totally permissible if indicator: 1 is put in the
appropriate column, Wage Type is permissible with warning if Indicator is 2 and if Blank (no
indicator) - wage type is not permitted. Before configuring this node, configuration of
Employee Subgroups for Primary wage types and Personnel Subareas for Primary wage types
shall be configured.
Explanation
1. Click on
Infotypes
Populated
1. 0014
Tables
storing
relevant
data
1. V_511_B
Relationship
with Other
Nodes
1.
2.
171
Remarks
172
Employee Subgroups for primary wage types and Personnel Subareas for primary wage types
nodes shall be configured first.
Assign appropriate indicators to wage types based on the requirement and applicability.
Purpose
Wage type characteristics for shall be configured in this node.
Description
Wage Type Characteristics like Payment / Deduction wage type, Minimum and Maximum
amount permissible, Indirect Valuation method of wage type, Rewritable Indicator and period
of validity of wage type characteristics shall be configured here. Wage Type Characteristics
shall be maintained individually for each wage type.
Explanation
1. 0014
Tables
storing
relevant
data
1. V_T511
Relationship
with Other
Nodes
1.
173
174
Remarks
Wage Characteristics for each wage type shall be maintained individually for each wage type.
If overwrite indicator is marked INVAL Wages, system shall allow to over write the defaulted
amounts, otherwise changing of amounts shall not possible.
Purpose
This section allows you to combine primary wage types applicability for personnel subareas.
Description
In order to differentiate/restrict wage types applicability to Personnel Subareas (location based)
in the Company, Personnel Subarea Grouping for primary wage types shall be defined. You can
use these groupings to specify applicability wage types to employees of the personnel subarea by
defining Wage Type Permissibility for PS & ESG.
Explanation
1. Click on
Types.
Infotypes
Populated
1. 0014
Tables
storing
relevant
data
1. V_001P_K
Relationship
with Other
Nodes
1.
2.
175
Remarks
Grouping shall be permitted between 0 to 9 only.
This activity is not mandatory and should be carried out only if you want to limit the entry of
wage types to certain personnel Subareas.
176
These Tables need not be updated every time, since groupings defined in the Basic Pay
Infotype will be reflected automatically here also. Hence, grouping has to be defined keeping
in view of wage types in all infotypes.
Purpose
In TAYO, certain allowances payable to employees are considered for Tax exemption as per
Income Tax Rules. Since no standard functionality available in SAP tax exemption are rules are
customized in Schema.
Description
Some of the allowances payable to employees are exempted from tax, partially or fully, as
per Income Tax rules. Allowances which are commonly used in all Industry are exempted from
tax as per the standard tax rules/codes available in SAP. Certain Customer Specific
Allowances will also get Tax exemption as Income Tax Rules, which are not in use for all the
industries. In order to full fill this requirement rules has been written for each allowance
wage types and attach to the Schema ZN00 (The copy of standard schema IN00).
Explanation
1. Enter Transaction Code PE02 in the command field of the SAP Easy
Access Screen and choose
(Enter).
2. Enter the name of the Rule (ZXM1) and create.
3. Select Source Text in the Sub objects block and choose
to change / modify the copied Personnel Calculation Rules as per
requirement.
4. Then create two EE Subgroup Nodes ( * and 3).
5. Click on
(Create + F3) to create node. Enter * in the Node created
and Choose
(Enter).
6. Select * in the tree structure and choose
open insert object sub screen.
177
12. Enter code of the wage type which needs to be tax exempted.
13. Choose
14. Repeat the same steps in order to create sub node and enter ADDWT *
which will not affect the amount of wage type.
15. Choose Wage Type Code Field and choose
open insert object sub screen.
16. To create operation for this rule, click on Sub level which will open
another sub node.
17. Enter ELIMI* operation which will eliminates Period Indicators (Split
Indicators).
18. Enter
19. Enter
(Enter).
20. Enter
in the sub node opened and
(Enter) to Reset the time period indicator.
21. Enter
number and
22. Enter
to the sub node opened to get exemption under
section 10 (/130: Exemption u/s10.)
23. Enter
to the subsequent sub node
opened to restore the actual amount to the wage type after calculating
projection factor.
24. Click on
Check (Shift 5) to ensure the correctness the personnel
calculation rules created.
25. Click on Save to button
rules created.
26. Click on
screen.
(F3) button to come out of the screen and to come out of the
27. Enter PE01 in the command field and choose enter which will lead to
another screen Personnel Calculation Schemas: Initial Screen.
28. Enter ZN00 Schema (Copied from IN00 Schema), choose source text and
click on
29. Double click on ZNN1 to incorporate ZXM1 PCR for tax exemption
calculating purpose during payroll run.
30. Insert ZXM1 PCR after IN76 rule in the Schema.
178
31. Click on
32. Choose F7 or Generate in the Schema (Tab) to generate and activate the
schema.
33. Click on
(F3) button to come out of the screen and to reach IMG
configuration node.
Infotypes
Populated
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable.
Table 1 :
179
ZNP1 pcr.htm
Personnel Calculation Rules
180
181
182
Additional Payments
General Information
This section describes the Configurable Item in brief:IMG Path
Additional Payments
This section describes the Configurable Item in detail:-
Purpose
In this step, wage types which are not in regular and periodic nature are configured.
Description
Wage types that are paid irregularly and therefore are only entered when needed, are stored
in the Additional Payments infotype (0015). This Infotype used to enter one off, annual or
irregular earnings or deductions from the employee such as Bonus, LTC, Medical etc.
Explanation
1. Click on
1. 0015
Tables
storing
relevant
data
1. Not Applicable
Relationship
with Other
Nodes
Additional Payments.
Not Applicable
183
Purpose
In this step, Payment & Deduction Wage Types for infotype Additional Payments (0015) shall
be created by copying the model wage types in the standard system.
Description
Wage types which are to be used in infotype Additional Payments (0015) shall be created in
this step, which shall be copied from Model Wage Types which starts with M. Choose Model
wage Types with payment characteristics for Payment Wage Types and with deduction
characteristics for Deduction wage types.
Explanation
1. Click on
2. Select
3. Click on.
Select
5. Enter Wage Type Number and Text and Short Text in the appropriate
columns.
6. Remove Flag Mark from Test Run Indicator
wage types.
before copying
184
9. Click on
10. Select
in the Wage Type Maintenance Screen. Enter Wage
Types to be deleted in the Delete wage Type Column. Remove Test Run
Indicator before clicking on the
Infotypes
Populated
1. 0015
Tables
storing
relevant
data
1. Table: V_T511
Relationship
with Other
Nodes
1. Not Applicable
Additional Payments.
2. Table: V_T512T
3. Table:V_512W_D
185
Remarks
Carry test run before actual copying of wage types to ensure error free copying.
186
Purpose
In this section, wage types related to wage type group 0015 can be assigned.
Description
Model wage types are already assigned to wage type group in the standard system. While
copying wage types based on the characteristics copied wage types shall be grouped in
Infotypes: 0008, 0014 & 0015. Wage types which are created for Infotype Additional Payments
shall be grouped here.
Explanation
1. Click on
2. Check all wage types under this group are reflecting are not.
3. If any wage types are not reflecting, click on
missing wage type code in the wage type Column.
4. Click on
1. 0015
Tables
storing
relevant
data
1. VV_52D7_B_0015_AL0
Relationship
with Other
Nodes
1. Not Applicable
187
188
Purpose
This section allows changing the texts of the wage types.
Description
Changing of Wage Types Text and Short Text can be changed here based on the requirements
like change in Wage Type Name, Wrong Entry of Wage Type Text etc.
Explanation
1. Click on
2. Check and Update required Wage Types Long Text and Short Text.
Infotypes
Populated
1. 0015
Tables
storing
relevant
data
1. V_512W_T
Relationship
with Other
Nodes
1. Not Applicable
Additional Payments.
189
Purpose
This section permissibility of wage types shall be defined for this infotype.
Description
Entry permissibility of the wage types for Additional Payments Infotype shall be entered here.
Depending on the (time based) requirements permissibility of the wage type shall be updated
by entering the desired date in Start Date field of the particular wage type.
Explanation
Infotypes
Populated
1. 0015
Additional Payments.
Tables
storing
relevant
data
1. V_T512Z
Relationship
with Other
Nodes
1. Not Applicable
190
Purpose
In this section, wage types that shall be permissible for Additional payments Infotype shall be
configured.
Description
Permissibility of wage types to Employee Subgroups and Personnel Sub areas shall be
configured here. Permissibility values shall be assigned based on the groupings of Employee
Subgroups and Personnel Subareas to Primary wage type. There are 3 types indicators
provided in the system. Wage type is totally permissible if indicator: 1 is put in the
appropriate column, Wage Type is permissible with warning if Indicator is 2 and if Blank wage
type is not permitted. Before configuring this node, configuration of Employee Subgroups for
Primary wage types and Personnel Subareas for Primary wage types shall be configured.
Explanation
1. Click on
Infotypes
Populated
1. 0015
Additional Payments.
Tables
storing
relevant
data
1. V_511_B
Relationship
with Other
1.
2.
191
Nodes
Configuration Description wage type permissibility for ESG & PSA.
Remarks
192
Employee Subgroups for primary wage types and Personnel Subareas for primary wage types
nodes shall be configured first.
Assign appropriate indicators to wage types based on the requirement and applicability.
Purpose
Wage type characteristics for shall be configured in this node.
Description
Wage Type Characteristics like Payment / Deduction wage type, Minimum and Maximum
amount permissible, Indirect Valuation method of wage type, Rewritable Indicator and period
of validity of wage type characteristics shall be configured here. Wage Type Characteristics
shall be maintained individually for each wage type.
Explanation
1. 0015
Tables
storing
relevant
data
1. V_T511
Relationship
with Other
Nodes
1.
Additional Payments.
193
194
Remarks
Wage Characteristics for each wage type shall be maintained individually for each wage type.
If overwrite indicator is marked INVAL Wages, system shall allow to over write the defaulted
amounts, otherwise changing of amounts shall not possible.
Purpose
This section allows defining and assigning employee subgroups for primary wage types
195
Description
In order to differentiate wage types applicability to Employee Groups and Employee
Subgroups in the Company, Grouping for the primary wage types must be defined first. U se
these groupings to specify which wage types may be entered for which employee subgroups.
These wage type grouping shall be used in configuring Define Wage Type Permissibility for PS
& ESG.
Explanation
1. Click on
Types.
Infotypes
Populated
1. 0015
Additional Payments.
Tables
storing
relevant
data
1. V_503_G
Relationship
with Other
Nodes
1.
2.
196
Remarks
Grouping shall be permitted between 0 to 9 only.
These Tables need not be updated every time, since groupings defined in the Basic Pay
Infotype will be reflected automatically here also. Hence, grouping has to be defined keeping
in view of wage types in all infotypes.
197
Purpose
This section need to be configured to combine primary wage types applicability for personnel
subareas.
Description
In order to differentiate/restrict wage types applicability to Personnel Subareas (location
based) in the Company, Personnel Subarea Grouping for primary wage types shall be defined.
You can use these groupings to specify applicability wage types to employees of the personnel
subarea by defining Wage Type Permissibility for PS & ESG.
Explanation
1. Click on
Types.
Infotypes
Populated
1. 0015
Additional Payments.
Tables
storing
relevant
data
1. V_001P_K
Relationship
with Other
Nodes
1.
2.
198
Remarks
Grouping shall be permitted between 0 to 9 only.
This activity is not mandatory and should be carried out only if you want to limit the entry of
wage types to certain personnel Subareas.
These Tables need not be updated every time, since groupings defined in the Basic Pay
Infotype will be reflected automatically here also. Hence, grouping has to be defined keeping
in view of wage types in all infotypes.
199
Purpose
In this section, settings for the organizational environment for Payroll can be made.
Frequency of TAYO ROLLS LIMITEDPayroll runs shall be defined in this node.
Description
The period parameter determines how often payroll is run for a payroll accounting area. Each
payroll accounting area is assigned one period parameter. Payroll periods are defined for each
period parameter. In this section duration of each payroll period with start date and end date
shall be defined.
A time unit defines the exact period of payroll period. Examples of standard time units are
monthly, weekly and bi-weekly. Unlike the period parameter, the time unit is the same for all
countries. Time unit can be assigned to different period parameters.
For India period parameter is 67 and time unit is 01 (Monthly).
Explanation
1. Click on
Define Period Parameters for Change view Period
Parameters overview.
2. Click on New Entries to enter Period Parameter, Time Unit and Start
Date in the appropriate fields.
3. Click on
1. Not Applicable
Tables
1. V_T549R
200
storing
relevant
data
Relationship
with Other
Nodes
1. Not Applicable.
Remarks
Create separate payroll periods for each period parameter configured.
201
Purpose
In this step Date Modifiers can be defined for Payroll Areas.
Description
Date Modifiers are mainly to determine payment dates for payroll areas. If the payment is
same for all payroll areas, no need to make any settings in this step. Date modifiers are
required to configure in case of different payment dates for various payroll areas with same
period parameter. (Use 00 Standard Modifier).
Explanation
1. Click on
Define Date Modifier, which will open Change View Date
Modifiers: Overview.
2. Click on
if required
3. Click on
1. Not Applicable
Tables
storing
relevant
data
1. Table: V_T549L
Relationship
with Other
Nodes
1. Not Applicable.
202
Purpose
In TAYO ROLLS LIMITEDsalaries of employees are processed at different locations of the
Company. Payroll Areas are defined based on the Payroll processing locations.
Description
Payroll area groups together the personnel numbers that are to be processed on the same
date and it determine the exact payroll periods. The payroll area to which employee belongs
to depending on the organizational assignment of the employee. Employees who belong to
different Company codes can be included in the same payroll area. Different payroll areas can
be created in cases of Payroll Periodicity is different (Weekly, bi-weekly, Monthly), Payroll
Period is varied (Salaried employees, workmen, pensioners etc), payment date is varied
(Weekly Fourth day of the following week, for salaried employees 1st day of the subsequent
month, Retroactive limit is varied (Payroll should not be able to be run as far back for one
group of employees as for another) and No Payroll Run for some employees.
Explanation
1. Click on
Check Payroll Accounting Area, which leads to sub screen:
Choose Activity.
2. Select Check Payroll Areas in the displayed sub screen and click on
Choose button
.
3. Click on
in the subsequent screen and enter Payroll Area,
Payroll Area Text, Period parameter and Date Modifier. Blank space in
the Date Modifier Column indicates Standard Date Modifier00.
4. Click on Save
5. Click on
Infotypes
Populated
1. 0001
Organizational Assignment
2. 0008
Basic Pay
Tables
storing
relevant
data
1. V_T549A
Relationship
with Other
Nodes
1. Not Applicable.
203
Remarks
SAP recommends use of few payroll areas as possible.
204
Payroll Areas and Control records can also be created in Personnel Management Module.
(Personnel Management Personnel Administration Organizational Data Organizational
Assignment Create Payroll Area, Check default Payroll Area (ABKRS Feature), Control
Record).
Purpose
In this step Default Payroll Areas Feature ABKRS shall be configured in below mentioned
node. In TAYO ROLLS LIMITED Personnel Subareas are considered as impact levels for
defaulting payroll areas since the scope of Payroll in SAP is Officers only.
(Personnel Management Personnel Administration Organizational Data Organizational
Assignment Check default Payroll Area (ABKRS Feature).
Description
Feature provides default values based on the certain decisive operations. ABKRS Feature
provides default Payroll Areas based on the decision criteria mentioned in the feature.
Explanatio
n
2. Select ABKRS
tree displayed and Click on Create
in the decision
or Choose F5.
3. Choose field for decision operation in the sub screen ABKRS: Choose
node type for new nodes and Click on
(Enter), which lead to sub
screen Field Selection for decision operation.
4. Select MOLGA (Country Grouping) and choose
decision criteria MOLGA to ABKRS decision tree.
(Enter) to transfer
or
8. Select Filed for decision operation in the sub screen and Click on
(Enter) which lead to another sub screen: Field selection for decision
operation.
205
9. Select BTRTL (Personnel Subarea) in the sub screen opened and choose
(Enter) to transfer the same to decision tree.
10. Select BTRTL (Personnel Subarea) in the ABKRS: Decision Tree structure
and choose Create
(F5).
17. Choose Return Value in the sub screen opened and Click on
(Enter)
which lead to another sub screen: Return value for Field Value
otherwise.
18. Enter Payroll Area which has to be defaulted for other personnel areas
or enter
-- incase of no value to be defaulted.
19. Click on
1. 0001
Organizational Assignment.
2. 0008
Basic Pay
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
206
Remarks
SAP recommends use of few payroll areas as possible.
Purpose
In TAYO, for each payroll area a Control record has been created.
Description
Control Record shall be created for each payroll area.
Control Record has the following
Functions in the Payroll.
It determines the current payroll period for exact date.
It determines earliest retroactive accounting period.
It locks the master data and time data being changed during payroll run.
Explanation
1. Click on
Check Payroll Accounting Area, which leads to sub screen:
Choose Activity.
2. Select Create Control Record in the displayed sub screen and click on
Choose button
.
3. Enter Payroll area in the subsequent screen for which Control Record
has to be created and choose
which will leads to Payroll Control
207
Record Screen.
4. In the Payroll Control record Screen, enter 12, 2004 in the Payroll
Period and in the earliest retroactive accounting period 01, 2005 which
shall be treated as First period of the financial year i.e. April,2005.
Infotypes
Populated
Tables
storing
relevant
data
1. Not Applicable
Relationship
with Other
Nodes
208
Remarks
Payroll Areas and Control records can also be created in Personnel Management Module.
(Personnel Management Personnel Administration Organizational Data Organizational
Assignment Create Payroll Area, Control Record).
209
Purpose
In this section, payroll periods shall be generated for processing TAYO ROLLS LIMITED payroll.
Description
In this step, Date specifications shall be generated for a selected period for the payroll
periods that are to be valid in the system. Specify the period start dates and end dates of
the periods as well as the payment dates for each payroll period parameter assigned to a
payroll accounting area. Flag mark the Carry out table changes field to save the generated
payroll periods, otherwise it will become a simulation run.
Explanation
1. Click on
1. Not Applicable
Tables
storing
relevant
data
1. Not Applicable
Relationship
with Other
Nodes
1. Not Applicable.
210
211
Remarks
Put Flag mark the Carry out table changes field to save the generated payroll periods,
otherwise it will become a simulation run.
Generate Payroll Periods for several periods in advance.
Check data in date of pay day and check dates of periods tables, which were automatically
updated while generating payroll periods.
Purpose
In this section, Calendar for cumulations shall be generated
Description
In this step, calendar for the cumulations of wage types shall be generated. Certain wage
types are cumulated over several periods during payroll in order, for example, to form
monthly, quarterly or annual totals. Before the wage types can be cumulated, you must
determine the month, quarter, half-year or year to which the payroll period belongs.
Explanation
1. Click on
Generate Calendar for Cumulations, to open Generate
Calendar for Cumulations and Deductions screen.
2. Enter data in Period Parameter, Date Modifier, Initial year, Final Year,
Start date of fiscal year and Determine period number.
3. Flag the Carry out table change column to save the Cumulation Periods
generated.
4. Click on Execute button
5. Click on Back button
Infotypes
Populated
1. Not Applicable.
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
1. Not Applicable
212
Remarks
Put Flag mark the Carry out table changes field to save the generated payroll periods;
otherwise it will become a simulation run.
Generate the calendar for cumulations and deductions for the same period as generated for
the payroll periods
213
Payscale Groupings
General Information
This section describes the Configurable Item in brief:IMG Path
Purpose
In this section, pay scale groupings for allowances shall be defined. These groupings are used
to select employees based on their eligible compensation benefits.
Description
Payscale Grouping for Allowances are defined to differentiate between sets of employees for
the purpose of payroll. These groupings determine the eligibility of the employees for various
allowances, reimbursements and perks
The Five important parameters in deciding Allowance Groupings are Payscale Type, Payscale
Area, Payscale Group, Payscale Level and ESG for CAP.
214
Purpose
In TAYO, different benefits and privileges are defined for different employee groups. In this
activity, pay scale groupings for allowances are defined to differentiate between employee
groups.
Description
The Five important parameters in deciding Allowance Groupings are Payscale Type, Payscale
Area, Payscale Group, Payscale Level and ESG for CAP. Allowance groupings are defined based
on the privileges and benefits employees are entitled as per the Company Policy
Explanation
1. Click on
which will open Screen:
Change View Payscale Grouping for Allowances; Over View.
2. Click on
determined.
3. Enter Payscale Grouping for Allowances (4 Char Code) and Text in the
appropriate columns.
4. Click on
1. Not Applicable.
Tables
storing
relevant
data
1. V_T7INA1
Relationship
with Other
Nodes
1. Not Applicable
215
216
Purpose
In this activity Payscale structure, defined in the previous nodes as per TAYO ROLLS LIMITED
requirements, assigned 'Pay Scale groupings for Allowance' created in the previous step.
Description
In this activity assign pay parameters to each 'Pay Scale groupings for Allowance' created in
the previous step, based on parameters Payscale Type, Payscale Area, Payscale Group,
Payscale Level and ESG for CAP.
Explanation
1. Click on
which will open
Associating Pay parameters to pay scale grouping screen.
2. Click on
grouping.
1. 8,14,15,45,581,583,590
Tables
storing
relevant
data
1. V_T7INA3
Relationship
with Other
Nodes
1. Not Applicable
217
218
219
220
Purpose
In this activity, you assign a basic wage type to each pay scale grouping for allowances
created under Pay Scale Groupings
Description
In this activity, you assign a basic wage type to each pay scale grouping for allowances
created under Pay Scale Groupings -> Define Pay Scale Groupings for Allowances. These wage
types are assigned to the pay scale groupings for the purpose of identifying a wage type and
associating this for the purpose of payment of the base
Explanation
1. Click on
Change View Basic Wages screen.
2. Click on
to assign Allowance Groupings, Basic salary Wage
Type, Start date and End Date.
3. Click on
1. Not Applicable
Tables
storing
relevant
data
1. V_T7INB1
Relationship
with Other
Nodes
1. Not Applicable
221
222
223
224
R e i m b u r s e m e n t , Al l o w a n c e s & P e r k s
General Information (RAPs)
This section describes the Configurable Item in detail:-
Purpose
As per the TAYO ROLLS LIMITED Company Policy employees are eligible for Reimbursements,
Allowances and perks based on their grade during their tenure of service. These benefits
(RAPs) are captured in this section.
Description
Reimbursements, Allowances and Perks (RAPS) provided to the employee during the tenure of
service shall be configured in this section. Allowances are a part of the employee's total
salary, which a normally paid through the pay slip and are paid on a regular basis. These could
be monthly, like House Rent Allowance (HRA) or on an annual basis like Leave Travel
Allowance (LTA). These are always cash components and not paid in kind. Reimbursements
are those components that are paid against a claim or an expense incurred by an employee.
Perks are that component of the total salary, which are generally availed by the employee in
terms of kind on which the employer specifies a limit. In some cases, no amounts are
specified and it is claimed against actual expenses incurred.
The eligibility and amounts for any of these components depend on the geographical location,
department, grade and employee group and the years of experience in the organization.
Explanation
Infotypes
Populated
1. Basic pay:0008
2. Recurring Payments & Deductions:0014
3. Additional Payments: 0015
Tables
storing
relevant
data
1. Not Applicable
Relationship
with Other
Nodes
1. Not Applicable
225
Purpose
In this activity, wage type model shall be assigned to each Payscale grouping for allowances.
This will determine applicability of benefits to TAYO ROLLS LIMITED employees based on the
eligibility criteria defined.
Description
Assigning wage type model to Payscale grouping for allowances helps in determining the
applicability of benefits to employees. Enter a four character alphanumeric value for pay
scale grouping for allowances in the AlGrp field. Enter the wage type model to be assigned in
the WT model field. The Wage Type Models must be prefixed with '20/' to indicate that, a
maximum of 20 wage types can be stored in a particular Wage type model.
Explanation
1. Click on
Assign wage type model for pay scale grouping for
allowances node to assign allowance grouping with wage type model.
2. Click on
button in the screen: Change View wage type
model for pay scale grouping for allowances.
3. Enter the corresponding Wage Type Model in the WT model field, for
each 'Pay Scale Grouping for Allowances'.
4. Click on
1. Not Applicable.
226
Tables
storing
relevant
data
1. V_T7INA5
Relationship
with Other
Nodes
1. Not Applicable.
227
Remarks
One Allowance grouping cannot assigned to more than one wage type model. One wage type
model can be assigned to different allowance groupings.
Wage type model prefixed with 20/ indicates maximum 2o wage types are permissible for that
wage type model.
Purpose
In this step default wage types shall be determined based on TAYO ROLLS LIMITED company
structure for the Basic Pay infotype (0008).
Description
Details configured in the previous node Default wage types for basic in Basic Pay node will be
reflected automatically here. Details can be maintained in either of these nodes. Data will
be stored in one table only.
Explanation
4. Click on
1. Not Applicable
Tables
storing
relevant
data
1. V_T539A
Relationship
with Other
Nodes
1. Not Applicable.
228
229
Purpose
Wage type characteristics can also be configured and maintained in this section.
Description
Wage Type Characteristics like Payment / Deduction wage type, Minimum and Maximum
amount permissible, Indirect Valuation method of wage type, Rewritable Indicator and period
of validity of wage type characteristics shall be configured here. Wage Type Characteristics
has to be maintained individually for each wage type.
Wage Type characteristics maintained in the previous nodes are reflected here automatically.
Maintenance of wage type characteristics shall be made in any of these nodes.
Explanation
1. Click on
230
3. Click on
4. Click on
Infotypes
Populated
Tables
storing
relevant
data
1. V_T511
Relationship
with Other
Nodes
1. Not Applicable.
231
Purpose
Wage types (Basic Pay) applicable to employee groups shall also be maintained from this
node.
Description
Payscale Groups & Levels shall be decided based on the Payscale Type and Payscale Areas and
compensation structure applicable. Indirect Valuation of Wage Types in Basic Pay Infotype
(INVAL A Default Amount) shall be entered here. This Grouping can be done based on the
Employee Subgroup grouping for Collective Agreement Provisions, Payscale Group, Payscale
Level, Payscale Type and Payscale Areas.
Details maintained in the Section2.8 will be reflected here.
Explanation
1. Click on
4. Click on
1. 0008
Tables
storing
relevant
data
1. V_T510
Relationship
with Other
Nodes
1.
Basic Pay
232
Remarks
Wage types that are evaluated indirectly through INVAL A i.e. a fixed amount as defaulted in
Infotype: 0008 can be entered here.
233
Purpose
In this step, as per TAYO ROLLS LIMITED requirement, indirect valuation for wage types shall
be defined based on the Module variant mentioned in the Wage Type Characteristics node
(INVAL B).
Description
Indirect Evaluation is a method to calculate the eligible amounts (default) for some of the
wage types. INVAL is the Indirect Evaluation Module used to meet the Indian specific business
requirements. INVAL with Module variant A shall be used to default fixed amounts and Variant
B shall be used to calculate amount on percentage basis on some other wage type.
Amounts for wage types calculated on percentage basis (INVAL B) shall be configured here.
INVAL and module variants shall be maintained for required wage types in Wage Type
characteristics node.
Enter Indirect Valuation Module Name (PRZNT), Valuated Wage Type (Wage Type Code for
which amount is calculated by using INVAL - B), Enter serial no, if the amount is calculated on
wage types, start date and end date for the, Base Wage Type (on which amount is calculated
for valuated wage type) and percentage (to be calculated on base wage type).
Explanation
1. Click on
4. Click on
Infotypes
Populated
Tables
storing
relevant
data
1. V_T539J
Relationship
with Other
Nodes
1. Not Applicable.
234
235
Remarks
INVAL details shall be entered for required wage types in Wage Type Characteristics, specify
Percent in Time / Measurement Unit and requirement of overwrite Indicator.
Unlike the wage types that are evaluated through INVAL A, where a wage type can have
different values for different groupings, here a wage type can have a single relationship for
all Allowance groupings.
Purpose
In this activity, eligibility details to calculate any employee's Reimbursement, Allowance or
Perk (RAP) shall be maintained.
Description
In this activity, you set up the eligibility details to calculate any employee's Reimbursement,
Allowance or Perk (RAP). Amount shall be entered against each wage type which indicates
the eligibility or limit for that particular allowance group if they have.
Explanation
1. Click on
Infotypes
Populated
Tables
storing
relevant
data
1. V_T71NA9.
Relationship
with Other
Nodes
1. Not Applicable.
236
237
L e a v e Tra v e l
General Information
This section describes the Configurable Item in detail:-
Purpose
In TAYO, LTA benefit is provided to employees as an annual benefit. Leave rules related to LTA
requirement shall be configured in this node.
Description
LTA is an annual component of any employees' gross salary normally paid against a claim and is
subject to a minimum period of leave taken by the employee. In this section of the IMG, LTA
related leave rules shall be configured. LTA (travel) and tax exemption based on the expenses
incurred by the employee shall be captured in Exemptions Infotype (0582) sub type: LTA.
Explanation
1.
Tables
storing
relevant
data
1. V_T7INL1
Relationship
with Other
Nodes
1. Not Applicable
238
239
Purpose
To meet TAYO ROLLS LIMITEDLTC Process requirements a Custom report has been developed.
This report helps in processing annual / biannual LTC claims, LTC Advance Claims, Update LTC
Claims, Cancellation of LTC Advance Claimed, Conversion of LTC advance to LTC claim.
Description
In order to meet LTC requirements of TAYO ROLLS LIMITED a custom has been developed. This
report is used in administering Annual/ biannual claims, LTC Advance claims, Update LTC
Claims, Cancel LTC Claims and convert LTC Advances to LTC claimed records. The total LTC
process is processed through ESS, Work Flow and Custom Report.
Explanation
1. Maintaining LTC Block years (Sub Blocks): Enter sub blocks in the Table:
T511K (Payroll Parameters : LTABG and LTAEN).
2. LTC Eligibility details shall be maintained in V_T7INT9 Table.
3. Employees leave details shall be captured through ESS, which shall be
maintained by employee only.
4. Once the employee applies for LTC leave, work flow will be triggered in
the background and details are passed to Payroll Administrator.
5. Based on the applicability Payroll administrator will process LTC claim
and the feedback will be provided to employee through mail.
6. LTC claims details are captured in YHRMT_LTC
7. While processing LTC advance claims, system will check employees
eligibility and applicability of LTC claims from YHRMT_LTC created.
8. Payroll Administrator shall update the LTC Claim based on the proof
submitted by the employee. Details of the LTC claims will be updated
in YHRMT_LTC and LTC payment wage type in Infotype 15 for further
processing in payroll.
9. Employee can cancel the LTC advance by providing advance deposit
receipt number, which will be provided by the Finance department
after receiving the advance amount from the employee. These details
will be updated automatically in the YHRMT_LTC.
10. Payroll Administrator can convert LTC Advance amount to LTC paid after
the verification of proof of expenditure. System updates automatically
LTC Advance Wage type with Negative value and payment amount shall
be uploaded to LTC payment wage type for further processing in Payroll
and tax computation purpose.
11. Payroll Administrator shall update Infotype: 582 (LTC amount) for tax
exemption computation purpose, otherwise total LTC paid amount will
be treated as taxable component only.
240
Infotypes
Populated
1.
Tables
storing
relevant
data
1. YHRMT_LTC
Relationship
with Other
Nodes
2. Not Applicable
241
242
Gratuity
General information
This section describes the Configurable Item in detail:-
Purpose
In this section of IMG, configuration related to Gratuity, retrial benefit for the TAYO ROLLS
LIMITED employees, shall be configured.
Description
In this section of the Implementation Guide (IMG), settings that define the employer's
contributions towards funds that support the employee's retirement plan can be made.
Gratuity component for Payroll India can be configured in this node.
Gratuity is a benefit provided to the employee on the cessation of his or her services. This is a
statutory component, applicable to all employees of an organization. The employer
contributes to a gratuity trust so as to provide for payment at the time of termination or
retirement.
The system calculates gratuity as per the Gratuity Act. If the rate of gratuity provided by the
company is higher, the system will instead, compute gratuity as per the company rules.
Explanatio
n
1. Not Applicable
Tables
storing
relevant
data
1. Not Applicable
Relationship
with Other
Nodes
1. Not Applicable
243
Purpose
In order to meet the administrative and other statutory requirements of Gratuity a separate
gratuity Trust was established. Id of the trust shall be captured in this configuration node.
Description
In this activity, Gratuity Trust Id maintained by the company shall be configured. This is a
Four digit Alphanumeric code which shall be entered in the Gratuity ID Filed.
Explanatio
n
3. Enter Gratuity Trust ID in the GRA ID field and Name of Gratuity Trust in
the Text field in the Gratuity ID maintenance table.
244
1. Not Applicable
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable.
Purpose
In this node, Gratuity contribution frequency rate and related wage types shall be defined.
245
Description
In this activity Gratuity contribution frequency shall be defined, whether contribution to the
gratuity trust is to be made annually or monthly, annual contribution is to be made at the end
of financial year or calendar year. Also required to define whether the wage type for gratuity
contributions made on a monthly basis or annual basis, the wage type used to calculate the
provisional monthly gratuity contributions, in case the contribution to the trust is made
annually. This wage type needs to be defined only if provisional wage types per month needs
to be calculated and posted to a provisional account. Assign the Gratuity trust ID to technical
wage types and frequency monthly contribution details in the table.
Explanatio
n
1. Not Applicable
Tables
storing
relevant
data
1. Not Applicable
Relationship
with Other
Nodes
1. Not Applicable.
246
Purpose
As per the requirement of TAYO, Gratuity contribution rate (provision every month) shall be
defined in this node.
Description
Contribution rates used to calculate the gratuity contributions made by the employer shall be
defined in this activity. These company-specific rules are linked to gratuity funds and enable
the system to calculate and store gratuity amounts during the payroll run. Assign these
contribution rates to Allowance Grouping and Gratuity Trust Ids as applicable.
Explanation
1. Not Applicable
Tables
storing
relevant
data
1. V_T7ING1
Relationship
1. Not Applicable
2.
247
with Other
Nodes
2.
248
Purpose
Gratuity eligibility period for the employee shall be configured in this node of IMG.
Description
In this step, the minimum number of years of service after which the employer begins to
contribute towards gratuity is specified here. The Number of Gratuity years Constant
(GRTYR) in the table view Payroll Constants, stores the value for the minimum number of
years.
Explanation
2. Enter start date, end date and no of years (value) in the appropriate
fields of Value of constants table.
3. Click on save button
1. Not Applicable
Tables
storing
relevant
data
1. V_T511K
Relationship
with Other
Nodes
1. Not Applicable.
249
Screen 3 :
250
Superannuation
General information
This section describes the Configurable Item in detail:-
Purpose
TAYO ROLLS LIMITED is providing Superannuation benefit to the employees as a retrial benefit
for the welfare of the employees. Superannuation related requirements are captured in this
part of IMG.
Description
In this section of the Implementation Guide (IMG), settings that define the employer's
contributions towards funds that support the employee's retirement plan can be made.
Superannuation component for Payroll India can be configured in this node.
Superannuation is a non-statutory benefit provided to the employee on the cessation of his or
her services. The employer contributes to a Superannuation trust so as to provide for payment
at the time of retirement.
Infotypes
Populated
1. Not Applicable
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable.
251
Purpose
ID of the Superannuation Trust of the Company shall be maintained in this activity.
Description
Superannuation Trust Id maintained by the company shall be configured in this node. This is a
four digit alphanumeric code which shall be entered in the SAN ID Filed.
Explanatio
n
3. Enter Superannuation Trust ID in the SAN ID Trust Filed and Name in the
Text field of the Superannuation ID maintenance table.
252
1. Not Applicable
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable
Purpose
In this node, Superannuation contribution frequency rate and related wage types shall be
defined.
253
13.3.1
Description
Explanatio
n
2. Click on
in the subsequent screen - Superannuation Id and
related wage types.
3. Enter Superannuation Trust ID, Frequency contribution, Monthly
contribution, Monthly WT, Annual WT and Provisional WT in the required
fields of Superannuation ID and related wage types table.
4. Click on save button
5. Click on back (F3) button
Infotypes
Populated
1. Not Applicable
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable.
254
Purpose
Superannuation contribution rate shall be defined in this node.
Description
Ccontribution rates used to calculate the Superannuation contributions made by the employer
shall be defined in this activity. These company-specific rules are linked to gratuity funds and
enable the system to calculate and store gratuity amounts during the payroll run. Assign
these contribution rates to Allowance Grouping and Superannuation Trust Ids as applicable.
Explanation
1. Not Applicable.
Tables
storing
relevant
data
1. V_T7INS1
Relationship
with Other
Nodes
1. Not Applicable.
2.
255
256
P r o v i d e n t Fu n d
General information
This section describes the Configurable Item in detail:-
Purpose
In this section of the Implementation Guide (IMG), Employer and Employee contributions of
TAYO ROLLS LIMITED towards Provident Fund shall be captured.
Description
Provident Fund (PF) is a statutory contribution scheme applicable to all employees.
Contributions are based on a percentage set by the Government. The contribution
percentage may vary provided the amount of contribution is equal to or more than the
statutory amount. Both the employee and the employer contribute to this fund. Pension is a
benefit in which an employee receives regular payment from the employer after retirement
or termination provided he or she meets the eligibility criteria. The contribution to pension is
deducted from the employer's contribution to PF. In case of Coal Mines Provident Fund, both
employer and employee contribute towards Pension Fund. No need to contribute towards PF
Admin charges, EDLI & EDLI Admn. Charges.
There are three types of PF trusts: Excluded Trust, where no contributions are made towards
EDLI, EDLI administration or Pension. The entire contribution is made to the trust in the form
of Provident Fund. Exempted Trust, where EDLI, EDLI Admin and Pension (8.33%) are
contributed to the Government. Provident fund is maintained by a trust other than Regional
provident fund commissioner (RPFC). Regional Provident Fund Commissioner (RPFC) Trust,
where all the contributions are made to the government. Based on the type of trust,
contribution towards PF, Pension and EDLI may vary.
1. Path for Statutory Social Contribution: IMG Payroll Payroll India
Statutory Social Contribution.
Explanatio
n
Infotypes
Populated
Tables
storing
relevant
data
1. Not applicable.
Relationship
with Other
Nodes
1. Not Applicable.
257
Purpose
Provident Fund contributions of the employees & employer are deposited at the various
Provident Fund Trusts at different locations. All the PF Trusts details are captured in this
section of IMG.
Description
In this activity, you define the different Provident Fund (PF) trusts that the employer and
employee contribute to, and set the wage types used to calculate contributions made to the
trusts and its associated handling charges. Separate Trusts are to be configured in case of
Contribution rates and rules are different. Enter Trust details in the Trust ID, Trust details,
and Wage types used to calculate contributions shall be entered in the appropriate fields.
Explanatio
258
2. Click on
3. Enter PF Trusts IDs, Trust Name, Trust Type and appropriate wage types
in the contributions fields in the Trust Master table.
4. Click on save button
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable.
259
Purpose
As per statutory requirement Employer also (TAYO) shall contribute towards Provident fund.
TAYO ROLLS LIMITED contribution rate towards Employer provident fund shall be configured in
this node.
Description
Contribution rates used to calculate the Provident Fund contributions made by the employer
shall be defined in this activity. This is a non-statutory rate and can be any amount that is
equal to or greater than the statutory rate (prescribed by Government).
Explanation
1. Not Applicable.
Tables
storing
relevant
data
1. V_T7INF5
Relationship
1. Not Applicable.
260
with Other
Nodes
Company Rate of Provident Fund Contributions - Configuration description
Purpose
TAYO ROLLS LIMITEDis depositing Employee and Employer PF contributions at various Trusts.
Validity period of the shall be captured in this IMG node.
Description
Provident Fund (PF) trusts and validity period of the trusts applicable to the company shall be
defined in this node of IMG. The provident fund trusts defined in this step are used as a basis
for selection in the infotype (587) Provident Fund Contributions.
261
Explanation
3. Enter PF Trust ID, start date, end date, rate of interest paid by the trust
and EDLI payee details in the appropriate columns of the Trust Details.
4. Click on save button
1. Not Applicable.
Tables
storing
relevant
data
1. V_T7INF7
Relationship
with Other
Nodes
1.
262
Purpose
In this activity, contributions rates shall be attached to PF trusts where PF contributions of
TAYO ROLLS LIMITED employees are deposited.
Description
This feature is used to determine the type of the establishment and the Trust identification
number. Type of the establishment gives information about the statutory percentages of
contribution by employer and employee. In this configuration node, rates of contributions
shall be assigned to PF trusts for the further processing in payroll and to meet statutory
requirements. This feature is being called in Payroll function INEPF and uses the return values
for PF processing and reporting. Structure for Decision tree for this feature consists of:
Company code, Personal area, Personal Subarea, Employee group, Employee subgroup,
Country Grouping and Provident fund Trust id.
Explanation
to configure
(Enter) to transfer
(F5) which
8. Enter Trust Ids in the Values for TSTID in the sub screen opened. Choose
(New Line F5) to enter more trust IDs and choose
transfer the same to decision structure.
(Enter) to
(Enter)
263
11. Enter contribution type applicable to the Provident Fund Trust in the
appropriate field of the Return value (M/ER REF No. /ER PENSION REF.
No.).
12. Repeat the same steps for the other provident fund trusts mentioned in
the tree structure.
13. Click
Tables
storing
relevant
data
1. V_T7INF3, V_T7INF7
Relationship
with Other
Nodes
1. Not Applicable.
264
265
Purpose
In this activity the contribution rates have been assigned to types of pf trusts.
Description
In this activity the contribution rates have been assigned to types of pf trusts . Also required
to specify contribution rates for Employer PF & Pension Contribution, Employee PF
Contribution, PF Admn. Charges and EDLI Admn. Charges.
Explanatio
n
3. Enter contribution type, period start date, end date, and percentages
of EE Contrib, Er Contrib, Er Pen Ctr, PF Adm Chr and EDLI Admin in the
statutory rates of Provident Fund.
4. Click on save button
1. Not Applicable.
Tables
storing
relevant
data
1. V_T7INF3
Relationship
with Other
Nodes
1. Not Applicable.
266
Tayo Pension:
This is the deduction, which is only applicable for both old and New pay type workers.
Description: As a part of Employee welfare deduction, Tayo pension is deducted every
month from employees Earned Basic and DA contribution.
This contribution is made to the Tayo pension trust.
This contribution is 2% of earned Basic and DA.
To set this, a wage type is created called Tayo Pension with the code of 1102.
Menu path to maintain this is as follows
SPRO Personnel administration basic pay and followed by the screen below
267
Once this is saved the deduction is maintained through IT 0014 with subtype as wage
type 1102.
268
P r o f e s s i o n a l Tax
General information
This section describes the Configurable Item in detail:-
Purpose
Professional tax details of the applicable states shall be captured in this node of the IMG.
Professional Tax shall be deducted from the employees of TAYO ROLLS LIMITED working at
various states
Description
Professional Tax is a tax on employment and it is deducted from the wages payable to all
employees with the exception of certain categories such as disabled and so on but may vary in
different States as per the laws that govern them.
It is a statutory deduction administered by the State. Deductions are based on the salary slabs
for all the employees who are specified by the respective state governments or local bodies
(authorities).
Explanatio
n
Infotypes
Populated
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable
269
Purpose
Personnel area and Personnel Subareas shall be grouped for the purpose of Professional Tax
requirements from the TAYO ROLLS LIMITED employees working at different locations.
Description
In this activity, personnel area and subarea groupings for Professional Tax (PTax), which are
used to group all personnel areas, and subareas that contribute to the same professional tax
circle shall be defined.
Explanatio
n
1.
Tables
1. Not Applicable
270
storing
relevant
data
Relationship
with Other
Nodes
1. Not Applicable
Purpose
In this node, Professional Tax assignment with applicable Personnel Areas and Personnel
Subareas shall be grouped.
271
Description
Based on the professional tax details configured in the previous node, professional tax
groupings shall be attached to applicable personnel areas and personnel areas for the further
processing in the payroll.
Explanatio
n
1.
Tables
storing
relevant
data
1. V_7IN0P
Relationship
with Other
Nodes
1. Not Applicable.
272
Purpose
Professional tax slab / rates shall be configured details of the applicable states shall be
captured in this node of the IMG.
Description
In this activity, you assign a Professional Tax (Ptax) rate to a slab code, if existing P Tax slabs
are changed or for new requirements. Slabs are salary brackets as specified for a State by the
respective State Government or local authority. To assign rates to slab codes for a state, first
define the slab code and then assign serial numbers, maximum limits and the rates.
1. Click on IMG Activity button
deductions.
Explanatio
n
2. Click on
to enter required professional tax details in the
subsequent screen Professional tax Slab Amount Screen.
3. Enter slab code, serial number, maximum limits and the rates in
appropriate columns of the Professional tax slab amounts table.
4. Click on save button
1. Not Applicable
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
1. Not Applicable
V_T7INP4
273
Purpose
Professional tax slab codes shall be linked with applicable states/regions & Form Layout shall
be captured in this node of the IMG.
274
Description
In this activity, you link a Professional Tax (Ptax) slab code to the region & Form Layout.
2. Click on
3. Enter slab code, serial number, maximum limits and the rates in
appropriate columns of the Professional tax slab amounts table.
4. Click on save button
2. Not Applicable
Tables
storing
relevant
data
2.
Relationship
with Other
Nodes
2. Not Applicable
V_T7INP4
IMG Path to maintain method & Form layout for Ptax grping.
275
276
Tax
General information
This section describes the Configurable Item in detail:-
Purpose
In this section of the Implementation Guide (IMG), you make the settings that affect the
calculation of tax during a payroll run.
Description
Income tax is deducted from all employee's gross salary for as per the Income Tax Act of
1961. This is deducted by the employer on a monthly basis and is transferred to a particular
bank under a unique identification as specified. A summary of the tax return for all employees
is submitted by the employer to the local tax authority at the end of each financial year. A
summarized calculation of the tax returns is given to the employee at the end of the financial
year or on termination of employment. The laws for the calculation of taxes are subject to
change with changes in the Income tax act. In addition to overall taxation, statutory
requirements enforce different kinds of tax exemption for different types of allowances.
Some exemptions are based on limits with specified frequency (for example, monthly or
annual) depending on the individuals specific data. Tax rates for calculation, personnel
subarea grouping for tax, deductions under section 80 and section 88, exemption limits on the
components mentioned in the RAPs Table shall be configured in this node.
Explanatio
n
Infotypes
Populated
1. Not Applicable
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable.
277
278
Define Personnel Area and Personnel Sub Area Grouping for Tax
This section describes the Configurable Item in detail:-
Purpose
In this section of the Implementation Guide (IMG), settings that affect the calculation of tax
during a payroll run shall be configured.
Description
In this activity, employees at different locations shall be grouped together based on the
personnel area and personnel subarea to whom the same tax office is applicable.
1. Path: IMGPayrollPayroll IndiaTaxBasic settings.
Explanatio
n
3. Click on
button to enter Tax Grouping related details in the
subsequent screen Personnel Sub Area grouping for Tax.
4. Enter Tax Grouping, TDS Circle, Ward No and Payee key in the
appropriate columns of the Personnel Subarea Grouping for Tax Table.
5. Click on save button
1. Not Applicable.
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable
279
Assign tax grouping details for Personnel Areas and Sub Areas
This section describes the Configurable Item in detail:-
16.3.1
Purpose
In this section of the Implementation Guide (IMG), settings that affect the calculation of tax
of TAYO ROLLS LIMITED employees during a payroll run shall be configured.
16.3.2
Description
In this activity, assign tax-grouping details to personnel areas and personnel sub areas based
on the requirements.
Explanatio
n
1. Not Applicable
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
1. Not Applicable.
V_7IN0P_TAX
280
Purpose
In this section of the Implementation Guide (IMG), Sec.80 deductions and Investments, made
by TAYO ROLLS LIMITED employees, under section 88 made through payroll shall be captured
for Income tax calculation purpose.
16.4.1
Description
The legal system provides for deductions from taxable income and rebates that are
subtracted from the income tax otherwise payable by an employee. Sometimes employer
facilitates deductions from employee's salary once in a year or any other frequency suggested
by employee to contribute to the relevant Funds/Trusts etc, so that employee can avail
deductions under section 80 and / or rebate under section 88. In this section of the IMG, we
can assign wage types to be deducted for various heads under section 80 and section 88.
Contributions or investments made under Section 80 are considered as deductions from Gross
Total Income (GTI) as per the limits specified by Central Government. By assigning a wage
281
type, we ensure that the annual value of the wage type along with the entries made in
Section 80 Deductions, Infotype (0585) becomes eligible for deduction from GTI for the
specified sub-section / division combination.
Wage types configured in Infotype 57 (Membership Fees) which attracts tax exemptions under
this section shall be configured here Income tax calculation purpose in Payroll processing.
Explanatio
n
2. Assign wage type code to the Tax Saving Type mentioned in the Table.
3. If more than one wage type has to be assigned to same Tax saving type,
copy the appropriate deduction from list of Tax saving schemes
mentioned in the table and enter sequence number in the Sequence
filed.
4. Click on save button
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
1. Not Applicable
V_T7INIC
282
Remarks
More than one wage type can be associated with same sub-section / division combination
using the sequence field.
283
16.5.1
Purpose
In this section of the Implementation Guide (IMG), Sec.80 deductions and Investments under
section 88 made through payroll shall be captured for Income tax calculation purpose.
16.5.2
Description
The legal system provides for deductions from taxable income and rebates that are
subtracted from the income tax otherwise payable by an employee. Sometimes employer
facilitates deductions from employee's salary once in a year or any other frequency suggested
by employee to contribute to the relevant Funds/Trusts etc, so that employee can avail
deductions under section 80 and / or rebate under section 88. In this section of the IMG, we
can assign wage types to be deducted for various heads under section 80 and section 88.
Contributions or investments made under Section 88 are considered as rebates from the total
tax payable by the employee. By assigning a wage type, we ensure that the annual value of
the wage type along with the entries made in Section 88 Deductions infotype (0586) becomes
eligible for rebate from tax payable otherwise for the specified investment.
Wage types configured in Infotype 57 (Membership Fees), which attracts tax exemptions
under this section, shall be configured here Income tax calculation purpose in Payroll
processing.
1. Click on IMG Activity income tax exemptions.
2. Assign wage type code to the Tax Saving Type mentioned in the Table.
Explanatio
n
3. If more than one wage type has to be assigned to same Tax saving type,
copy the appropriate deduction (investments) from list of Tax saving
schemes mentioned in the table and enter sequence number in the
Sequence filed.
4. Click on save button
1. Not Applicable.
Tables
storing
relevant
data
1.
Relationship
with Other
1. Not Applicable.
V_T7INIA
2.
284
Nodes
Configuration Description Third party (Section.88).
Purpose
In this section of the Implementation Guide (IMG), we can make the settings that affect the
calculation of tax on reimbursements, allowances and perks during a payroll run.
285
Description
Tax code limits, wage types and other criteria shall be assigned to appropriate tax code
mentioned in the system. This value is taken into account when calculating the employees tax
liabilities on certain benefits. Settings that will affect the calculation of tax on
reimbursements, allowances and perks during a payroll run shall be made in this section.
These tax limits or rates and other details are used for verification during a payroll run.
1. Path: Payroll IndiaTax Tax Liability on RAPs.
2. Click on IMG Activity 3. Click on
types screen.
Explanatio
n
4. Enter Wage type, tax type, frequency, exemption amount, tax code,
period start date and end date in the appropriate fields of the
taxability of wage types screen.
5. Click on save button
1. Not Applicable.
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
1. Not Applicable.
V_T7INT9
286
287
O f f C y c l e P ay r o l l
General information
This section describes the Configurable Item in detail:-
Purpose
In this section of the IMG Off cycle payroll related parameters shall be configured. TAYO
ROLLS LIMITED requirements like Payment of Bonus, SAF Payment, and Annual Bonus etc will
be paid to employees during the month (apart from payroll).
Description
Payroll run that is carried out in addition to the regular payroll run for a specific day and for
individual employees. This activity helps in issuing a check to replace payments that were
originally made or employee lost or damaged the check, to make a bonus payment or to pay
LTC or leave advances.
Explanatio
n
Infotypes
Populated
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable.
288
Purpose
In this activity, you check those wage types you want to be paid through the One-Time
Payments Off-Cycle Infotype (0267) for an Off cycle payroll run.
Description
Wage types shall be configured in this node that is allowed for onetime Off cycle payroll.
System shall permit these wage types only while performing Off cycle payroll activities.
1. Click on IMG Activity (0267)
Explanation
2. Click on
activities.
3. Enter Wage type code, start date, end date and flag mark frequency
column in the appropriate fields of Allowed wage types for Off cycle
payments table.
4. Click on save button
1. Not Applicable
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
1. Not Applicable
V_T512Z
289
Screen 4 :
17.3.1
Purpose
In this step, default wage types for certain payments shall be configured.
17.3.2
Description
Default wage types for certain payment methods like Bonus payment shall be configured in
this IMG node. System defaults these wage types based on the off cycle reason selected by
the Administrator.
Explanation
3. Enter Off cycle reason, Wage type code, start date and end date shall
290
1. Not applicable.
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
1. Not Applicable.
V_T52OCW
17.2
17.4.1
Purpose
291
17.4.2
Description
For off-cycle payroll, a payment method is already specified in the group box Specify
payment method, which the administrator can change at any time. In this step, you specify
the default payment method for off-cycle payroll. You can specify payment method for each
off-cycle reason.
Explanatio
n
3. Off cycle reason, valid period start date, end date and flag mark
default payment method IT009/Check/Man.check based on the
applicability.
4. Click on save button
1. Not applicable
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
1. Not applicable.
V_T52OCB
292
Deductions
General information
This section describes the Configurable Item in detail:-
Purpose
In this section, determine how deductions with priorities and arrears are processed during
TAYO ROLLS LIMITED payroll run for various locations.
Description
Deduction priorities and arrears processing for calculating deductions shall be customized in
this part of IMG. Based on the deduction priorities and arrears processing methods assigned
to each deduction wage type system will prioritize which deduction shall be taken into
consideration incase of insufficient salary during payroll processing. This will also helps in
determining what happens to the deduction amount when the available net amount is not
sufficient. The remaining amount can be transferred into the next period via the arrears
table. The deduction is then reprocessed in this period.
Explanation
Infotypes
Populated
1. Not Applicable.
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable.
293
Remarks
For maintaining priorities for deductions only this section has to be maintained otherwise no
need to customize this section.
Purpose
In this step, wage types shall be assigned to a wage type group Deductions for arrears.
Description
All the deduction wages must be assigned to Wage Type Group 7001 Deduction for Arrears for
prioritising of deductions for arrears processing during payroll run. These priorities helps in
determining which deduction has to be taken first and processing of amounts in case of
insufficient salary of the employee. Based on the arrears characteristics assigned system will
determine whether the deductions are to be ignored or to deduct available amount and
processing of remaining amount.
Explanatio
n
2. Check all the wage types are reflecting in the Wage types Group (7001).
3. Click on
if wage types to be included and wage type code in
the WT field and press Enter
4. Click on save button
1. Not Applicable.
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
1. Not Applicable.
VV_52D7_B_7001_AL0
294
Remarks
The standard system contains model wage types for arrears deductions that are already
assigned to the wage type group.
Purpose
In this step, deduction wage type characteristics for priorities and arrears processing shall be
determined.
Description
Each deduction wage type shall be prioritized based on the requirements. During payroll run
these deductions are sorted out based on the priorities assigned and processed in that order.
If the net amount is insufficient for all deductions, then system will consider arrears
characteristics assigned to each wage type and process accordingly. Following are the options
for while processing deductions and arrears: 1 Deduct the whole amount: 2 deduct as much as
possible 3 deduct as much as possible, remaining amount in arrears table 5 Deduct everything
or nothing 6 Deduct everything or nothing, remaining amount in arrears table. Deduction
Priority: A (highest) to Z (least) The deductions in the arrears table are transferred to the
295
next payroll period; here the system tries once again to withhold the deduction from the net
amount.
Explanatio
n
2. Enter start date, end date of the period, priorities for deductions and
arrears in the respective fields of the table in the sub screen
Characteristics of arrears; deductions, priority, character.
3. Click on save button
1. Not Applicable.
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
1. Not Applicable.
V_51P6_B
Screen 5 :
296
Purpose
Processing of deduction arrears during retro accounting shall be determined in this node.
Description
In this step, how deduction arrears are processed in retroactive accounting shall be
determined. During a retroactive run, the same amount is deducted as during the original run
for the payroll period, regardless of whether or not the amount has changed retroactively.
For this reason, it must be determined how any difference between the old and new
deduction amounts is to be processed. It is possible to carry the difference through to the
next payroll period, either in full, or only if the amount is positive or negative, or to ignore it
completely. The arrears table is used to carry the differences forward to the next original
period, in which they are then processed further. Assign a parameter to deduction wage type
to determine how it has to be processed during payroll run.
Parameters for retro accounting: 1 Deduct old amount, difference to Arrears table, 2 Deduct
old amount only positive difference to arrears 3 Deduct old amount, only negative amount to
arrears 4 Deduct old amount, ignore difference.
Explanatio
n
2. Enter start date, end date of the period, Retro accounting arrears in the
respective fields of the table in the sub screen Characteristics of
arrears; deductions, retro-Accounting.
3. Click on save button
1.
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable.
V_51P6_C
2.
297
298
Company Loans
General Information
This section describes the Configurable Item in detail:-
Purpose
TAYO ROLLS LIMITED is providing various types loans to their employees with different loan
conditions. This loan amount is deducted from the salary in regular installments during
payroll processing. In this section, required settings shall be made to enter data and process
Company loans.
Description
This section of the IMG shall be configured to administer Company Loans in SAP. The amount
of administration is kept low as the processing of formalities, payment of the loan, repayment
and interest payment by the employee, can simply be processed using Payroll. Loan
repayment and interest calculation are automatically processed in Payroll and, according to
entries made, withheld from the employees salary. The loan accounting data is saved
together with the payroll results. Loan types distinguish between loans using the purpose and
the loan category. At least one loan condition is assigned to a loan type. The interest rate and
repayment pattern for the loan are stored in this type of loan condition. Enter Loan data of
the employee in Loans Infotype (0045).
Explanation
Infotypes
Populated
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
1. Not Applicable.
Not Applicable.
299
Remarks
For administering Company Loans in SAP only this section has to be maintained otherwise no
need to customize this section.
Activate Calculation
This section describes the Configurable Item in detail:-
Purpose
In TAYO ROLLS LIMITED different Loans are provided to employees for the benefit of the
employees. Data related to Loans provided to employees shall be captured in infotype: 45. In
this step, processing of Loans data stored in Loans Infotype shall be activated to calculate
during payroll processing.
Description
Loans provided to employees by the Companies in order to meet different requirements of
the employees. These loans includes Initial settling loans, computer loans, vehicle loans, soft
furnishing loans and non refundable pf loans, which shall be provided to employees based on
their eligibility as per Company Policy. Loans provided to employees shall be captured in
Loans Infotype: 0045. In order to process the loans (data stored in infotype) during payroll
processing Personnel Calculation (Sub) Schema: INLN shall be activated in Payroll Schema:
ZN00.
300
Explanatio
n
ZN00
Customer
specific
payroll
schema
and
choose
Click
not.
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable
301
302
Purpose
In TAYO ROLLS LIMITED different types of loans are provided to employees based on the
eligibility as per Company Policy. Loans provided to employees shall be deducted on
installments basis, as per the data provided in the Infotype: 0045, from the employees salary
during payroll processing. The repayment installment computation date, whether it is from
start of the month or end of the month, shall be captured in this node.
Description
Loans provided to the employees, as per Company Policy, shall be deducted from employees
salary on installment basis every month. Details of the Loans provided to the employees like
Loan amount, repayment installment, no of installments and other loan conditions are
captured in the Infotype: 0045. The repayment installment, which shall be deducted from
employee salary every month during payroll processing, shall reduce the interest yielding
capital (interest calculation method) either from the start day of the month or last day of the
month. This repayment installment method shall be configured in this IMG node as per
Company Policy / requirement.
303
Explanatio
n
Infotypes
Populated
Tables
storing
relevant
data
1. V_T506S
Relationship
with Other
Nodes
1. Not Applicable
304
Purpose
In this step, interest calculation method shall be maintained and assigned.
Description
Interest calculation shall be done in accordance with the specifications mentioned in this
section. Standard interest calculation method assumes 30 days in a month and 360 days in a
year. Interest calculation method shall be assigned to INTLO Feature, which will default
calculation method to all Loan types, which will applicable to the whole system. If different
calculation methods are required for different loan types, specify interest calculation method
in maintain loan types node. This interest calculation method will ride the interest
calculation method assigned in INTLO feature. Thus different loan conditions shall be
assigned to different loan types based on the requirements.
Explanatio
n
305
opened
4. Select MOLGA country grouping in the sub screen Field Selection for
decision operation to choose
(transfer), which will display MOLGA in
tree structure.
5. Select MOLGA in the tree structure and choose
(F5) which lead to
sub screen Value for MOLGA. Enter Country grouping for India 40 in
the values table and choose
(transfer) and the same shall be
displayed in the tree structure.
6. Select 40 India and choose
Choose nodes for new nodes.
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable
306
Feature INTLO.
307
Purpose
Loan types that exist in the company shall be configured here.
Description
All the loan types that exist in the Company with their characteristics shall be configured in
this node. Different interests rate for a loan type shall be configured here by assigning
number to loan conditions. In the country assignment, each loan type shall be assigned to
Infotype: 0045, Country Grouping 40 and permissibility of loan types shall be maintained. In
the technical attributes of loan types, Loan conditions for each loan type shall be maintained.
Loan interest rate, ref Interest rate, Interest rate advantage shall be calculated for tax
computation purpose, interest computation method, interest cycle, payment shall be assigned
to each loan type for further processing in payroll.
Explanatio
n
4. Enter Loan Type code and text in the Subtype and Name fields of the
sub type characteristics Table.
5. Click on Save to button
6. Click on back (F3) button
7. Click on
screen.
10. Repeat the same for all loan types and save the entries made.
11. Click on back (F3) button
12. Click on
13. Select Loan type and double click on Conditions folder which will lead
to, a Table for Loan type, in the conditions screen.
14. Enter condition number, description of term and period start date and
308
16. Repeat the above steps to define conditions for all loan types and save
the entries.
17. Click on back (F3) button
configuration node.
Infotypes
Populated
Tables
storing
relevant
data
1. Not Applicable.
Relationship
with Other
Nodes
1. Not Applicable
309
310
Purpose
In this step, default values for Loans Infotype (0045) shall be defined.
Description
Before configuring this feature, Loan groups shall be defined and assign loan types and
conditions (maximum eligible amount) to those groups. These conditions shall be defaulted in
the Loans infotype (0045) by configuring the Feature ALOAN. Assign the loan groups to
employees groups in the feature to default values while configuring loans infotype for
individual employees.
Explanation
4. Select filed for decision in the sub screen opened and choose
lead to field selection for decision operation screen.
which
5. Select MOLGA country grouping in the sub screen Field Selection for
decision operation and choose
(transfer), which will display MOLGA
in tree structure.
6. Select MOLGA in the tree structure and choose
311
sub screen Value for MOLGA. Select Country grouping for India 40 in
the values table and choose
(transfer) and the same shall be
displayed in the tree structure.
7. Select 40 India and choose
nodes for new nodes.
12. Choose PERSK (Employee Subgroup) in the sub screen for decision
operation and choose
(transfer) and the same shall be displayed in
the tree structure.
13. Select PERSK displayed in the tree structure and choose
(F5) which
lead to sub screen 40: Choose nodes for new nodes choose
(transfer).
14. Choose desired Employee Sub Groups from the list in the sub screen
opened and choose
(transfer) to transform the value to feature tree
structure.
15. Select each employee subgroup listed in the tree structure and choose
(F5) which lead to sub screen 40: Choose nodes for new nodes.
16. Choose Return Values in the sub screen opened and press
(transfer)
to enter the applicable loan group to the employee subgroup.
17. Enter Loan Group in the appropriate column in the sub screen Enter a
Value and choose
(transfer) to transform the value to feature tree
structure.
18. Click
not.
Tables
1. Not Applicable
312
storing
relevant
data
Relationship
with Other
Nodes
1. Not Applicable.
313
Feature ALOAN.
314
Purpose
In this step, default values for Loans Infotype (0045) shall be defined. In TAYO ROLLS LIMITED
certain Loan types applicable to some employee groups, as per Company Policy. These
default loan types shall be configured in this feature.
Description
Loan types shall be defaulted based on the applicability to the employees as determined in
the Company Policy. In order to configure this feature Loan groups shall be determined based
on the applicability criteria to the employees as per Company policy. System will default the
values while maintaining Company Loans Infotype, based on this feature configuration.
Feature helps in reducing the data entry and it will provide Administrative control.
1. Click on IMG Activity feature.
(F5).
3. Select filed for decision in the sub screen opened and choose
leads to Field selection for decision operation screen.
which
4. Select MOLGA country grouping in the sub screen Field Selection for
decision operation and choose
(transfer), which will display MOLGA in
tree structure.
5. Select MOLGA in the tree structure and choose
(F5) which lead to sub
screen Value for MOLGA. Select Country grouping for India 40 in the
values table and choose
(transfer) and the same shall be displayed in
the tree structure.
6. Select 40 India and choose
nodes for new nodes.
7. Select filed for decision in the sub screen opened and choose
leads to Field selection for decision operation screen.
8. Select LTYPE Loan Type and choose
decision tree.
9. Select LTYPE Loan Type and choose
Loan Type Sub screen.
which
10. Enter the Loan Types determined in the subsequent screen in the Values
column and choose
(Enter) and the same shall be displayed in the
tree structure.
315
11. Select Loan Type in the displayed tree structure and choose
which will lead to Sub Screen: Values for LTYPE.
(F5)
12. Enter Loan Types in the appropriate columns of the sub screen opened,
which required to configure in this feature to default values to
applicable Allowance Groupings and choose
(Enter) to transfer the
values to the decision tree).
13. Choose one of the Loan Types displayed in the decision tree and choose
(F5) which will lead to Sub Screen: Choose Node for New Nodes.
14. Select Field for decision operation in the sub screen opened and choose
(Enter) to get the screen Field selection for decision operation.
15.
(F5) which
17. Enter the required Payscale Grouping for Allowances in the appropriate
columns and choose
(Enter) to transfer the same to decision tree
structure.
18. Select one of the Allowance Groupings (ALGRP) displayed in the tree
structure and choose
for New Nodes.
316
Infotypes
Populated
Tables
storing
relevant
data
1. Not Applicable
Relationship
with Other
Nodes
1. Not Applicable.
317
Purpose
In this step, loans which attract exemptions under Section.24 shall be configured.
Description
Housing Loans which will attract exemptions under section 24 of the Income Tax Act shall be
configured in this node. Housing Loans processed in the Loans Infotype (0045) will get tax
exemptions automatically in Payroll processing of that particular employee.
1. Click on IMG Activity Maintain deduction details under Section-24
which will lead to sub screen : Section 24 deduction details
maintenance screen.
2. Click on New Entries button to enter loan types which will attract
exemptions under Section.24.
3. Enter Housing related Loan types in the Loan type Column and mark the
check box in the Column Section.24 of the table Section 24 deduction
details maintenance.
4. Click on Save to button
5. Click on
(F3) button to come out of the screen and to reach IMG
configuration node.
Infotypes
Populated
1.
0045 (Loans)
2.
Tables
storing
relevant
data
1. V_T7INJ1
Relationship
with Other
Nodes
1. Not Applicable
318
Remarks
Loan types configured in this node shall also be updated in Infotype:584 (Income from
other sources) to process exemptions in Payroll.
319
P o s t i n g P a y r o l l R e s u l t s t o Ac c o u n t i n g
General Information
This section describes the Configurable Item in detail:IMG Path
Purpose
In this section posting of payroll results to Accounting system shall be configured. Payroll
creates payroll components for each payroll period. Payroll results contain information that
is relevant to accounting. These results shall be posted to Accounting system for various
reasons like updating of accounts under different accounts (Expense accounts, Payables
accounts, Sub ledger accounts, Vendor Accounts), MIS reports, Balance sheet preparation etc.
Hence; this configuration can be considered as interface between FI and HR (Payroll)
modules.
Description
This section deals with the configuration related to posting of payroll results to accounting
system.
Explanation
Infotypes
Populated
1.
Not Applicable
Tables
storing
relevant
data
1. Not Applicable
Relationship
with Other
Nodes
1.
Not Applicable
320
Remarks
If Human resource and accounting system are implemented in separate system , Carryout the activities
in HR system and other account system.
Purpose
In this step, define the symbolic accounts Payroll object used when posting results to
accounting.
Description
The number of symbolic accounts and the respective characteristics represent the
different expenses and payables that occur as personnel costs within payroll and must
be posted to accounting. The symbolic accounts are assigned to financial accounts.
This ensures that account determination takes place during posting to accounting.
Explanation
to Symbolic accounts
2. Click on
the values
Infotypes
Populated
1.
Not Applicable
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
1. Not Applicable.
V_T52EK
321
Remarks
Employee group indicator. If this indicator is set for an account, posting to this
account also considers employee grouping for account determination.
Purpose
In this step, maintain the Posting characteristic for wage type according to significance of
wage type for posting to accounting.
Description
We can use the processing type to assign the posting characteristic of wage for
posting payroll results.
Explanation
322
4. Save
the values.
Infotypes
Populated
2.
Not Applicable
Tables
storing
relevant
data
2.
Relationship
with Other
Nodes
2. Not Applicable.
V_T52EL
Remarks
The symbolic account must have account assignment type C. The wage type basic pay is entered in the
payroll result with a '+' sign. The sign is not changed as positive amounts are posted to the debit side;
you therefore enter a +. In this case, you do not have to set up special processing or additional account
assignment.
323
Purpose
In this step, assign expense accounts to the symbolic accounts used for posting.
Description
Expense accounts are often used for employee groupings for account determination.
Explanation
the values.
Infotypes
Populated
1.
Not Applicable
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
3. Not Applicable.
Not Applicable
324
Remarks
Check the assignment between employee grouping for account determination, the symbolic account,
G/L account.
Purpose
In this step, assign Balance Sheet accounts to the symbolic accounts used for posting.
Description
Balance sheet accounts are often used for employee groupings for account
determination.
Explanation
325
the values.
Infotypes
Populated
1.
Not Applicable
Tables
storing
relevant
data
1.
Relationship
with Other
Nodes
4. Not Applicable.
Not Applicable
Remarks
Check the assignment between employee grouping for account determination, the symbolic account,
G/L account.
5.
Recruitment
326
Recruitment
The ability to meet personnel requirements is key for enterprises. The success of an enterprise depends
on such factors as the quality and availability of personnel. It is particularly important for the
development and success of expanding enterprises that they have quick access to adequate personnel.
The Recruitment component can be used to recruit personnel based on the organizations
requirements. The applicants available to the organization may be included in the selection procedure
for vacancies, by advertising for personnel (e.g. job advertisements) or by receiving unsolicited
applications.
This component enables the definition of a recruitment procedure that suits the needs of the
organization. Tasks and responsibilities can be distributed and to different people involved in the
recruitment process. Recruitment enables dividing and assigning administrative and decision-making
task areas.
The Recruitment component enables automation of many processes. This reduces the administrative
tasks of the HR Department.
This component has all the functions for working through the entire recruitment procedure, from
creating applicant data to filling vacant positions.
The Recruitment component contains an entire range of powerful, flexible functions that can be
used to implement an effective and largely automated recruitment strategy.
This book explains how to make the necessary settings to configure your Recruitment system
Menu path: SPRO Personnel Management Recruitment
327
Feature PRELI is used to specify whether data on internal applicants can be read from the
employee database and whether applicant data can be transferred from Recruitment to the
employee database.
Feature PRELR (Integration of employees/applicants)
Feature PRELR is used to specify whether employee master data on line managers can be read
from the employee database.
Feature PAPLI (Integration between Personnel Administration and Recruitment)
Feature PAPLI is used to control whether applicant data is available within Personnel
Administration.
If you run Recruitment and Personnel Administration in separate systems, you must import the
employee master data on line managers into Recruitment at the start of customizing to ensure
access to this data.
2. Integration between Recruitment with Organizational Management
This integration enables you to administer your Positions and vacancies using Organizational
Management.
Note that integration to Recruitment is switched on when the following entries exist in the
T775S0 (V_T77S0) view of Organizational Management.
sem.abbr.
PLOGI
PRELI
PPVAC
value. abbr.
01
99999999
1
328
Activities
1. Check the extent to which your company uses Personnel Administration, Organizational
Management and Personnel Development. Discuss the subject so that these three modules of
Human Resource Management can be integrated.
2. Maintain feature PRELI, referring to the feature documentation.
3. Maintain feature PRELR, referring to the feature documentation.
4. Maintain feature PAPLI, referring to the feature documentation.
5. Make the appropriate settings in the T775S0 view.
329
You can use this feature to determine whether the system checks the personnel numbers of the
above employees (reference employees, contact employees, and line managers) against the employee
master data file at the time of entry, and to specify how the system should react.
330
In this section you make all the necessary system settings for the administration of workforce
requirements and advertising.
A company's workforce requirements are reflected in Recruitment by means of vacancies. Vacancies are
positions, which must be filled either partially or completely. They are created and maintained by the
331
user as transaction data but a user can only create vacancies if the positions available within the
company have already been set up. Vacancies are published in
job advertisements. Advertisements are transaction data and are created and maintained by the user.
Recruitment instruments and media are set up during customizing.
Create positions
In this step you set up the positions available within your company.
A company's workforce requirements are represented in the Recruitment system by means of vacancies
created and maintained by the user. A user can only create a vacancy if the positions available within
the company have already been set up.
332
Create media
For example, the recruitment instruments "Washington Post" and "New York Times" are
classified under the medium "Press".
It is also used to indicate the medium through which an unsolicited applicant came into contact
with the company.
The applicant class is an attribute of the medium and indicates whether a medium is used to attract
internal or external applicants
333
In the Below screen User can enter Instrument number and the medium from F4 selection and Address
of the Recruitment Instrument.
334
Applicant Selection
In this section you make all the settings necessary for the applicant selection procedure.
Application Status
Two types of selection procedure take place in the Recruitment system:
a global selection procedure
Every applicant entered in the system takes part in the global selection procedure for a company. This
selection procedure determines whether or not an applicant is of interest to the company. If this
proves to be the case, i.e. the applicant is not rejected, he/she can then be included in one or more
selection procedures for a vacancy. For this purpose, the applicant must be assigned to the vacancies in
question.
You can make a decision at any point during either of these selection procedures as to whether the
applicant continues to be of interest. Your decision is reflected in the applicant status, of which there
are two types to correspond to the two types of selection procedure:
Overall status
335
336
Applicant Actions
In this step you make the necessary system settings for the Applicant Actions transaction.
The term "applicant action" is used in two senses in Recruitment. These are:
1. The Applicant Actions transaction
The Applicant Actions transaction enables you to perform system-controlled operations
(applicant action types), which change the applicant's overall status (e.g. hire applicant). Each
operation can be assigned a sequence of infotypes, which are processed one after the other in
the course of the action.
2. Infotype 4000, Applicant Actions
When the Applicant Actions transaction is carried out, a new record for the applicant is usually
added to infotype 4000, Applicant Actions. The key of the action carried out, as well as the
status reason, if necessary, is recorded in the infotype. The applicant's overall status (e.g.
processing, invite, to be hired) is also recorded here.
337
Applicant Activities
Applicant activities document the administrative steps through which an applicant passes during the
selection procedure. Activities are assigned to the candidate's job applications, regardless of whether
these applications exist simultaneously or in a chronological sequence. An activity is assigned uniquely
to one applicant and to one of his/her applications.
Activities can be created manually or generated automatically using a feature. Activities that must be
performed for all applicants, such as "Mail confirmation of receipt", are normally generated
automatically by the system. The user determines all other activities. One processing step enables you
to generate one or more activities automatically for the following purposes:
To record an applicant's position in the selection procedure
338
Mail contract
339
340
341
Select new entries from the Tool tab or to copy any existing entries click on the building
address type and copy it to make changes as per your requirement.
342
Create Location
In this step, you set up business event locations.
You can assign locations to business events when you create the events. You can also relate a
location with location-dependent resources such as rooms. You create these relationships in
the steps Create Room and Create Other Resources.
The text you store here is included in the business event brochure.
Relationship - "Belongs to business event group"
Here you assign a business event group to an overlying business event group. The
hierarchy is always created top down.
343
If you are using internal number assignment, just enter the validity start date
of the object and choose Create.
2. Enter data for the business event type on the data screen as required.
3. There are two possible ways to continue editing:
o If you do not want to use the "Fast data entry" function, save your entries now.
o
If you want to use the "Fast data entry" function, choose Fast entry.
344
Further in front screen the user creates Business events, which are actual Training event to
which Employee is assigned and which changes every year based on the Training
requirements.
345
7. Appraisal
Introduction:
This Implementation Guide contains all the necessary information for implementing the
Personnel Development component.
The Personnel Development component enables you to maximize your employees' utility to
your company. You can plan and implement personnel and training measures to promote your
employees' professional development. By taking into account employees' preferences and
suitability, you can increase their job satisfaction. Personnel development also sets out to
ensure that all of the employees in all of the functional areas in your company are always
qualified to the standards required. This is achieved by developing qualification potentials.
Integration
Control parameters for the integration of Personnel Planning and Development (PD) with
other applications (such as Personnel Administration (PA) and Cost Accounting (CO), etc.) are
specified in the "PLOGI" group.
346
Integration
This section contains the steps you will need to work through to set up integration between
the Personnel Development component and the Personnel Administration and Recruitment
components.
Integration with Personnel Administration and Recruitment
In this step, you activate integration between the Personnel Development component
and the Personnel Administration and Recruitment components.
Transfer Qualifications from Personnel Administration
In this step, you import any infotype 0024 (Qualifications) records from the Personnel
Administration component into the Personnel Development component.
Transfer Qualifications from Recruitment
In this step, you import any infotype 0024 (Qualifications) records from the
Recruitment component into the Personnel Development component.
Transfer Appraisals from Personnel Administration
In this step, you import any infotype 0025 (Appraisals) records from the Personnel
Administration component into the Personnel Development component.
Edit Scales
In this step, you define and change the proficiency scales that are used in the Qualifications
and Requirements and Appraisal Systems components.
You define a scale by specifying a unique numeric identifier and a name for the scale. You will
also have to define proficiencies for each scale.
There are two basic types of scale:
You define a scale by specifying a unique numeric identifier and a name for the scale. You will
also have to define proficiencies for each scale.
347
348
can define quantities with 12 digits before the decimal point, and 3 after. You can use the
proficiency 0. Quantity scales can be used in the Appraisal Systems component ONLY.
349
Activities
1. Before you work through any of the following activities, specify a validity start date
for the changes. Choose Settings -> Set period... in the Catalog: Change Qualifications
screen. Specify a date in the Key date field.
Note
The end date of the validity period of the qualification catalog is always the highest
possible system date (12/31/9999).
The Catalog: Change Qualification(s) screen appears.
List of the activities you can perform:
Translate entry
350
Translate description
351
352
353
Note
You can only insert a qualification or qualification group under a qualification group
that has the same scale. ist.
Caution!
Always assign qualifications to a qualification group for the entire
validity period.
4. Choose Entry -> Move.
354
355
Right click on root catalog and create an new Category. Select Objective setting and
continue.
select tabs and give relevant entries by selecting Roles Columns that you want to display at
appraisal. Also select the status.
356
357
358
To create KRAs Template right click on category and create new Template and follow the
Wizard settings.
After creating the Template select the relevant setting from various tabs provided below in
the screen and follow the screen settings.
359
Also put a Note setting for each column where Appraise can write comments.
360
Default the column and Planner and Reviewer column access to change always to enable the
fields during Appraisal to allow to enter the values.
In Roles Tab check the Manager and Self button to enable the Rater and ratee during Appraisal
process.
361
In this screen user can set the check whether to allow the appraise to assess himself or to
display the template name or other settings like allowing multiple appraisees.
362
To create KRA, right click on template and create elements as directed in the screen.
363
New criterion can be named as per the Requirement. Also can mention the Description of the
KRA in the space provided.
If the KRA s are fixed one need not to check the free input button, else if check the free
input button. So, that this KRA s are free to change as per the objective at the start of the
year. And can be edited as per the requirement. Finally save the template and Release it for
to carryout the Appraisal Program.
364
365