SAP HRM

Contents:
 Organizational Management
 Personnel Administration
 Recruitment
 Time Management
 Payroll
 Travel Management
 CATS
 ESS.
 Schema & PCR
 E-Recruitment

Organizational Management

 Existing Organizational Units

 Staff Functions for Organizational Units
 Organizational Structure with Persons
 Organizational Structure with Work Centers
 Existing Jobs
 Job Description
 Complete Job Description
 Periods for Unoccupied Positions
 Existing Positions
 Position Description
 Vacant Positions
 Obsolete Positions
 Complete Position Description
 Reporting Structure without Persons
 Reporting Structure with Persons
 Existing Tasks
 Activity Profile of Positions
 Activity Profile of Positions with Persons
 Existing Objects
 Structure Display/Maintenance

Organizational Management

1
Organizational Structure

2
OVERALL ORGANISATION STRUCTURE
The overall organization structure can be summarized in the figure below. The
various organizational elements are described with the code to be used in
configuration alongside.

Enterprise Structure:

3
Define Company:

4
Define Company Code:

Define Personnel Areas:

5
Personnel Sub areas:

Employee Groups:

6
Employee Sub groups:

Assignment:

1. Assignment of Company code to Company:

2. Assignment of Personnel area to Company Code:

3. Assign employee sub group to Employee group:

7
Plan Version:

Set Active Plan Version:

Maintain Number Ranges for Organizational Objects:

Set up Number assignment for all plan versions:

Data Model Enhancement:

Maintain Object types:

8
Maintain Infotypes:

Maintain Sub types:

9
Maintain Relationships:

Maintain Evaluation paths:

Integration:

10
Set up Integration with Personnel Administration:

Transfer data from Personnel Administration (RHINTE00)

11
Prepare Integration with Personnel Administration.(RHINTE01)

12
 Transfer Data to Personnel Administration (RHINTE30)

Check Integration Consistency (RHINTE20)

13
Personnel Administration

14
Maintain User Parameters:

Maintain Number Range Intervals for Personnel numbers:

15
Determine Default for Number Ranges:

PERSONAL DATA

In this section, the system settings are configured for all the infotypes that store
personal data for the employee.

This group includes the following infotypes:

16
  Addresses (Infotype 0006)
 Personal Data (Infotype 0002)
 Family/Related Person (Infotype 0021)
 Identification (Infotype 0185).

Create Forms for Address:

Create Names Affixes:

17
Maintain Titles:

Create Marital Status:

18
Family/Related Person (Infotype 0021)
Data concerning, the employee’s family members / other related persons stored in
the Family Members/Dependents infotype (0021).

All necessary configurations pertaining to this infotype is done under this section.

Family Members

In this step, the type of relationship between employees and their relatives are
defined.

SAP R/3 Role Personal Data

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management -> Personnel
Administration -> Personal Data -> Family ->
Define possible family members
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy

SUBT OBJR
Y ZEITB Q STEXT

01 3 Father

02 3 Mother

03 3 Spouse

04 3 Son

05 3 Daughter

06 3 Brother

19
 07 3 Sister

Addresses (Infotype 0006)

In the Addresses infotype (0006), the address data of an employee/applicant is

stored. The employee’s address is used in conjunction with the
employee’s/applicant’s name, taken from the Personal Data infotype (0002), for
employee lists of different kinds, for forms, or for address labels.

In this step, the system settings for the infotype Addresses (0006) is done.

The Addresses infotype is used to store an employee's/applicants address(es).

Address Types

In this step, create the address types as per requirement.

The address types are defined as subtypes of infotype 0006, Addresses.

SAP R/3 Role Personal Data

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management -> Personnel
Administration -> Personal Data -> Addresses
-> Create address types
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy

SUBT ZEIT
Y STEXT B

1 Permanent Address 1

2 Temporary residence 3

3 Home address 2

4 Emergency address 2

5 Mailing address 2

6 Nursing address 2

Address provided during

7 Separation. 2

8 Present Address 2

20
Identification (Infotype 0185)
This infotype is used to store personal identification details of an employee.

In this section, settings which affect the infotype Identification (0185) need to be
maintained.

SAP R/3 Role Personal Data

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management -> Personnel
Administration -> Personal Data ->
Identification -> Maintain types of
identification

Contractual and Corporate Agreements

Contract Elements (Infotype 0016)
In the Contract Elements infotype (0016), data related to the employee’s
employment contract is stored.

21
Contractual Regulations
With the Contract type field, you can subdivide contracts of employment in
accordance with the planned duration of the work relationship and the employee’s
legal status.

You can or must also record the following information here:

 For temporary work relationships, you must enter the contract’s expiry date
(valid until).
Contract Types

In this step, contract categories are configured.

SAP R/3 Role Personal Data

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management -> Personnel
Administration -> Contractual and Corporate
Agreements -> Contract Elements -> Define
contract types

Determine default Contract elements:

22
Evaluation Basis
Monitoring of Task (Infotype 0019)

The infotype monitoring of dates (0019) is provided so that HR personnel can

monitor certain dates. In this infotype, all the dates that affect an employee and
dates which the personnel administrators should be reminded of by the system,
are stored.

Task type

In this step, task types with standard lead times and standard follow-up times as
well as indicators for additional tests are defined.

SAP R/3 Role Personal Data

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management -> Personnel
Administration -> Evaluation Basis ->
Monitoring of Tasks -> Determine Task Type

Description and Configuration Values

23
The following table reproduces the initial values configured for Cairn Energy

Date Specifications:

24
Calculation of Employment Period:

Define Conversion Rules:

25
Employee Qualifications
This group includes the following infotypes:
 Education (Infotype 0022)
 Other/Previous Employers (Infotype 0023)

Education (Infotype 0022)

All data pertaining to employee’s/ applicant’s education qualifications is stored in

the Education infotype (0022).

The standard system contains different educational establishment types as

subtypes: If you want to store information about the complete education and
training history of an employee/applicant, you have to create as many data
records as necessary for the respective subtypes of this infotype. Enter the
respective dates of the training period as the validity period.

You can enter the following data for each educational establishment type:

 Education/training or occupation the employee/applicant has acquired.

 Education and training category.
 Institute/Place (e.g. University for applied science).
 Country Key, i.e. the country in which the education/training institution is
based.
 Certificate.
 Duration of course.
 Final mark.
 Branch of study.

26
 SAP R/3 Role Menu Personal Data

Transaction Code SPRO

IMG Menu Implementation Guide for R/3 Customizing (IMG)
-> Personnel Management -> Personnel
Administration -> Employee Qualifications ->
Education and Training -> Create education
establishment types
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy

Natur
e Educ. est. text

01 Certificate Course

02 Diploma

03 Doctorate

04 Graduate

05 Master Diploma (2yea

06 Post Graduate

07 Post Graduate Diplom

08 Professional

09 Under Graduate

10 Vocational

SAP R/3 Role Personal Data

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management -> Personnel
Administration -> Employee Qualifications ->
Education and Training -> Define
Education/Training

27
Other and previous employers:

Other/Previous Employers (Infotype 0023)

In the Other/Previous Employers infotype (0023), information on other work

contracts of an employee or applicant is stored.

If more than one of an employee’s or applicant’s employers need to be enter,

create many data records within this infotype, each with their respective validity
period.

Specify the employer’s name and the country it is based in for each employer.
Following details can be also stored:

 City in which the company is based.

 Industry in which the company is active.
 Job that the employee or applicant carried out or carries out.
 Work contract with other employer.

In this section, the necessary settings for infotype Previous Employment (0023)
are done.

28
 SAP R/3 Role Personal Data
Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management -> Personnel
Administration -> Employee Qualifications ->
Other/Previous Employers -> Create
employer's industry sector
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy

Indu
s. Description

0001 Oil & Gas Ind.

0002 Consulting

0003 Consumer

0004 Hi-Tech

0005 Insurance

0006 ITES

0007 Oil & Gas - Downstream

0008 Oil & Gas - Upstream

0009 Telecom

0010 Manufacturing

0011 Pharmaceutical

0012 Others

0013 NGO

0014 Hotels

0015 FMCG

0017 Service Industry

0018 Others

29
 SAP R/3 Role Personal Data
Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management -> Personnel
Administration -> Employee Qualifications ->
Other/Previous Employers -> Create activities
in employment
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy

Job Text

000000
01 Geologist

000000
02 Site Engg.

000000
03 Surveyor

Communication: infotyoe:0105.

Communication
Communication (Infotype 0105)
An employee’ communication ID is stored in the Communication infotype (0105).

An employee’s communication ID is valid for a certain type of communication

(such as ERP system, Internet).

In this chapter, all necessary customizing is prepared for this infotype.

SAP R/3 Role Personal Data

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management -> Personnel
Administration -> Communication -> Create
communication types

30
31
Customizing procedures
In this chapter, system will be set up so that a large part of the work processes
used in the enterprise are reflected in the HR System.

For example, we can determine which infotypes are to be proposed as defaults

when a person is hired or if an employee's organizational assignment changes.

In the HR System, hiring is considered to be a personnel action; one can define

and describe personnel actions as per requirement of an organization.

One can set up own menus as per requirement.

One can initiate actions so that they depend on the existence of certain infotypes
and/or their contents.

Actions

In this chapter, personnel actions together with the possible reasons are defined
and the work contents and the choice of actions for the administrator.

32
Define info groups

SAP R/3 Role Personal Data

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing (IMG)
-> Personnel Management -> Personnel
Administration -> Customizing Procedures ->
Actions -> Define infogroups
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy

Hirin
Info group 01 g

User Infogrmo ITyp STy

group d. No Op. e SC . Infotype text

000
99 00 INS 1 Organizational Assignment

000
99 01 INS 2 Personal Data

000
99 03 INS 6 8 Addresses

000
99 04 INS 6 1 Addresses

000
99 05 INS 7 Planned Working Time

000
99 06 INS 8 Basic Pay

000
99 07 INS 9 Bank Details

002
99 09 INS 1 Family Member/Dependents

002
99 10 INS 1 Family Member/Dependents

002
99 11 INS 1 Family Member/Dependents

002
99 12 INS 1 Family Member/Dependents

33
 002
99 13 INS 1 Family Member/Dependents

Info group AA Confirmation

User Infogrmod. No Op. IType SC STy. Infotype text

group

Info group AB Promotion

User Infogrmod. No Op. IType SC STy. Infotype text

group

Organizational
99 01 COP 0001 Assignment

Basic Pay

99 02 COP 0008

Infogroup AC Transfer

User
group Infogrmod. No Op. IType SC STy. Infotype text

Organizational
99 01 COP 0001 Assignment

Basic Pay

99 02 COP 0008

Re-
Infogroup AD designation

User
group Infogrmod. No Op. IType SC STy. Infotype text

Organizational
99 00 COP 0001 Assignment

34
 Mid Year
Infogroup AE Salary Review

User
group Infogrmod. No Op. IType SC STy. Infotype text

Basic Pay

99 00 COP 0008

Infogroup AF Secondment

User
group Infogrmod. No Op. IType SC STy. Infotype text

Basic Pay

99 03 COP 0008

Planned Working
99 04 COP 0007 Time

External
Organizational
99 05 COP 0395 Assignment

Expatriation

99 06 COP 0396

Infogroup AG Repatriation

User
group Infogrmod. No Op. IType SC STy. Infotype text

External
Organizational
99 01 COP 0395 Assignment

99 03 COP 0008 Basic Pay

Infogroup AH Repatriation

User
group Infogrmod. No Op. IType SC STy. Infotype text

Organizational
99 01 COP 0001 Assignment

35
 Monitoring of
99 02 COP 0019 Tasks

Going to be
Infogroup AI Separated

User
group Infogrmod. No Op. IType SC STy. Infotype text

Organization
al
99 00 COP 0001 Assignment

Temporary
Infogroup AJ Assignment

User
group Infogrmod. No Op. IType SC STy. Infotype text

99 03 COP 0008 Basic Pay

Planned Working
99 04 COP 0007 Time

External
Organizational
99 05 COP 0395 Assignment

promotion
Infogroup AK & Transfer

User
group Infogrmod. No Op. IType SC STy. Infotype text

Organizational
99 01 COP 0001 Assignment

99 02 COP 0008 Basic Pay

Transfer &
Re-
Infogroup AL designation

User
group Infogrmod. No Op. IType SC STy. Infotype text

99 01 COP 0001 Organizational

36
 Assignment

99 02 COP 0008 Basic Pay

Infogroup AM Relocation

User
group Infogrmod. No Op. IType SC STy. Infotype text

Organizational
99 01 COP 0001 Assignment

99 02 COP 0008 Basic Pay

Temp
Assignment
to
Infogroup AN Secondment

User
group Infogrmod. No Op. IType SC STy. Infotype text

99 03 COP 0008 Basic Pay

Planned
99 04 COP 0007 Working Time

External
Organizational
99 05 COP 0395 Assignment

Infogroup 84 Separation

User
group Infogrmod. No Op. IType SC STy. Infotype text

Organizational
99 02 COP 0001 Assignment

99 09 LIS9 0185 Personal IDs

99 10 LIS9 0185 Personal IDs

99 11 LIS9 0008 Basic Pay

Create customer-specific status

37
 SAP R/3 Role Menu Personal Data
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing (IMG)
-> Personnel Management -> Personnel
Administration -> Customizing Procedures ->
Actions -> Create customer-specific status
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy

Sta
t. Name

1 On Probation

2 Confirmed

On Temp. Assignment /
3 Secondment

4 Inactive Employee

Set up personnel actions

SAP R/3 Role Personal Data

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management -> Personnel
Administration -> Customizing Procedures ->
Actions -> Set up personnel actions
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy

Name of action Cust. Empl. Spe. Cntry

Act. type FC Stat. Stat. Stat. Check IG Dte U0000 U0302 Reass

01 Hiring 1 1 3 10 X X

20 Separation 0 0 0 84 1 X X

62 Hire applicant 7 1 3 1 48 X X

AA Confirmation 0 2 3 AA X X

AB Promotion 0 2 3 AB X X

AC Transfer 0 2 3 AC X X

AD Re-designation 0 2 3 AD X X

38
 Mid Year
AE Salary Review 0 2 3 AE X X

AF Secondment 0 3 3 AF X X

AG Repatriation 0 2 3 AG X X

Probation
AH extension 0 1 3 AH X X

Going to be
AI Separated 0 1 3 AI X X

Temp.
AJ Assignment 0 3 3 AJ X X

Promotion &
AK Transfer 0 2 3 AK X X

Transfer & Re-

AL designation 0 2 3 AL X X

A
AM Relocation 0 2 3 M X X

Temp Assign
conv to
AN Secondment 0 3 3 AN X X

Create reasons for personnel actions

SAP R/3 Role Personal Data

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing (IMG)
-> Personnel Management -> Personnel
Administration -> Customizing Procedures ->
Actions -> Create reasons for personnel actions
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy

Act. Name of action type ActR Name of reason for action

01 Hiring

20 Separation

20 Separation 01 Retirement

20 Separation 02 Resignation

20 Separation 04 Termination

39
 20 Separation 09 Death of employee

62 Hire applicant

AA Confirmation

AB Promotion

AC Transfer

AC Transfer 01 Vacancy

AC Transfer 02 Career progression

AC Transfer 03 Personal reason

AD Re-designation Better Reflection Of Role

AD Re-designation 01 Change in Job /Role

AD Re-designation 02 Change in titling Protocol

AE Mid Year Salary Review

AE Mid Year Salary Review 01 Internal Parity

AE Mid Year Salary Review 02 Market Correction

AF Secondment

AG Repatriation

AH Probation extension Unsatisfactory Performance

AI Going to be Separated

AI Going to be Separated 01 Retirement

AI Going to be Separated 02 Resignation

AJ Temp. Assignment

Temp Assign conv to

AN Secondment 01

Change action menu

SAP R/3 Role Personal Data

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing (IMG)
-> Personnel Management -> Personnel
Administration -> Customizing Procedures ->
Actions -> Change action menu
Description and Configuration Values

40
The following table reproduces the initial values configured for Cairn Energy

Actio
Menu 01 ns

User N Actio
group o n Name of Action type

99 01 01 Hiring

99 02 AA Confirmation

99 03 AB Promotion

99 04 AC Transfer

99 05 AD Re-designation

99 06 AE Mid Year Salary Review

99 07 AF Secondment

99 08 AG Repatriation

99 09 20 Separation

99 10 62 Hire applicant

99 11 AH Probation extension

99 12 AI Going to be Separated

99 13 AJ Temp. Assignment

99 14 AK Promotion & Transfer

99 15 AL Transfer & Re-designation

99 16 AM Relocation

Temp Assign conv to

99 17 AN Secondment

Dynamic Actions

Configuration is done to control the initiation of actions when maintaining an

infotype record.

This can be the maintenance of an additional infotype record or performing a

routine.

For each action, it can be determined whether it is always carried out when
changes made an infotype or a subtype or whether it is only carried out if changes
made to certain fields.

41
Settings can be made to specify whether the action is to be carried out for
"Change", "Create" and/or "Delete" record.

We can also specify default values for a record that is to be created.

SAP R/3 Role Personal Data

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing (IMG)
-> Personnel Management -> Personnel
Administration -> Customizing Procedures ->
Dynamic Actions
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy

IType STy. Field FC No. S Variable function part

0000 04 227 *** CALL ROUTINE FOR LETTER*

0000 04 228 P *P0000-MASSN='AD'

0000 04 229 P *T001P-MOLGA='40'

*SUB_REDESIGNATION

0000 04 230 F (ZHRG_INC_DYNAMICACTION)

0000 04 231 P P0000-MASSN='AH'

0000 04 232 P T001P-MOLGA='40'

SUB_PROBATION_EXT

0000 04 233 F (ZHRG_INC_DYNAMICACTION)

0000 04 234 P P0000-MASSN='AA'

0000 04 235 P T001P-MOLGA='40'

SUB_CONFIRMATION

0000 04 236 F (ZHRG_INC_DYNAMICACTION)

0000 04 237 P *P0000-MASSN='AC'

0000 04 238 P *T001P-MOLGA='40'

*SUB_TRANSFER

0000 04 239 F (ZHRG_INC_DYNAMICACTION)

42
0000 04 240 P P0000-MASSN='20'

0000 04 241 P T001P-MOLGA='40'

0000 04 242 F SUB_SERVICE_LETTER(ZHRG_INC_DYNAMICACTION)

0000 04 243 P P0000-MASSN='AI'

0000 04 244 P P0000-MASSG='01'

0000 04 245 F SUB_RETIREMENT_LETTER(ZHRG_INC_DYNAMICACTION)

0000 04 246 P P0000-MASSN='AI'

0000 04 247 P P0000-MASSG='02'

0000 04 248 F SUB_ACCEPT_RESIGNATION(ZHRG_INC_DYNAMICACTION)

0000 04 249 P P0000-MASSN='20'

0000 04 250 P P0000-MASSG='02'

0000 04 251 F SUB_RELIEVING_ORDER(ZHRG_INC_DYNAMICACTION)

0000 04 252 P P0000-MASSN='AI'

0000 04 253 P T001P-MOLGA='40'

0000 04 254 M S0001

0001 04 228 P P0000-MASSN='AD'

0001 04 229 P T001P-MOLGA='40'

0001 04 230 F SUB_REDESIGNATION(ZHRG_INC_DYNAMICACTION)

0001 04 237 * P0000-MASSN='AC'

0001 04 238 * T001P-MOLGA='40'

0001 04 239 * SUB_TRANSFER(ZHRG_INC_DYNAMICACTION)

0001 04 249 * P0000-MASSN='AC'

SUB_TRANSFER_MAIL_NOTIFICATION(ZHRG_INC_DYNAMIC
0001 04 253 * CTION)

0008 04 237 P T001P-MOLGA='40'

0008 04 238 P PSPAR-MASSN='AC'

0008 04 239 F SUB_TRANSFER(ZHRG_INC_DYNAMICACTION)

0008 04 241 P T001P-MOLGA='40'

0008 04 249 P P0000-MASSN='AC'

0008 04 250 F SUB_TRANSFER_MAIL_NOTIFICATION(ZHRG_INC_DYNAMIC

43
 CTION)

0008 04 253 P T001P-MOLGA='40'

0008 04 254 P PSPAR-MASSN='AB'

0008 04 255 F SUB_PROMOTION_LETTER(ZHRG_INC_DYNAMICACTION)

0008 04 259 P T001P-MOLGA='40'

0008 04 260 P PSPAR-MASSN='AE'

SUB_REVISED_SALARY_LETTER(ZHRG_INC_DYNAMICACTIO
0008 04 261 F N)

0395 04 001 P T001P-MOLGA='40'

0395 04 002 P PSPAR-MASSN='AF'

0395 04 003 F SUB_SECONDMENT_LETTER(ZHRG_INC_DYNAMICACTION)

0395 04 004 P T001P-MOLGA='40'

0395 04 005 P PSPAR-MASSN='AJ'

0395 04 006 F SUB_ASSIGNMENT_LETTER(ZHRG_INC_DYNAMICACTION)

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.
This component has all the functions needed 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.
The Recruitment component can be used to recruit human resources according
to requirements, at any time. Applicants data can be stored that have not
deemed suitable for a particular vacancy in the Applicant Pool, where they can
be considered for other or future vacancies.
This component enables to define a recruitment procedure that suits the needs
of enterprise. Tasks can be distributed and responsibilities can be fixed to
different people, involved in the recruitment process. Recruitment supports in
dividing and assigning administrative and decision-making task areas. Many
tasks can be processed via mass processing.
The Recruitment component provides dynamic actions to enable to automate
many processes. For example, when initial data for applicant is entered, the
system creates a confirmation of receipt in the form of an applicant activity and
a letter confirming receipt of application. This reduces the administrative tasks
required of the HR department for applicant correspondence.

44
Workforce Requirements and Advertising
The Recruitment component enables to document workforce requirements
and the way it is been advertised in the SAP system.
A company's workforce requirements are represented in the Workforce.
Requirements and Advertising component by means of vacancies. A
vacancy is a description of a position that must be staffed, either
completely or partially. The recruitment process is triggered by the
creation of a vacancy. The recruitment procedure is initiated by the
creation of a vacancy, and its purpose is to fill vacancies. Vacancies are
published in advertisements.
If a candidate applies for a job in response to an advertisement, he or she
must be assigned to this advertisement during the initial entry of basic
data phase. By assigning an applicant to an advertisement here, the
system can propose a likely vacancy assignment for the applicant. This
proposed vacancy assignment can be overwritten if unsuitable.
Assignment of an unsolicited applicant to a vacancy depends solely on the
decisions of the personnel officer or line manager responsible. For this
reason, default values cannot be proposed here.

If the candidate has applied in response to an advertisement, he / she

must be assigned to a recruitment instrument and a medium using the

45
advertisement. This assignment means that you can analyze the
effectiveness of the recruitment instruments and media used by company.

In this section, all the necessary system settings are done for the
administration of workforce requirements and advertising.

Create media

In this step we create the media used by company.

The medium serves two purposes in Recruitment:

 It is used to classify all recruitment instruments.

For example, the recruitment instruments "Washington Post" and

"New York Times" are classified under the medium "Press".

The applicant class is an attribute of the medium and indicates whether a medium is used to
attract internal or external applicants.

SAP R/3 Role Personal Data

Menu
Transaction SPRO
Code
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management ->
Recruitment -> Workforce Requirement and
Advertisement -> Create Media
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy

Applicant class
Medium Name of medium ApCl text

External
01 Press AP applicant

External
02 Employment office AP applicant

Exec.search External
03 agency AP applicant

04 Posters P Internal applicant

05 Mail P Internal applicant

46
 06 Internal press P Internal applicant

External
10 University AP applicant

External
11 Trade fairs AP applicant

External
12 Headhunter AP applicant

External
15 Internet AP applicant

Create recruitment instruments

In this step, the recruitment instruments, which company uses, are being
configured.
Every job advertisement is published in a recruitment instrument.
Recruitment instruments are classified according to the media used.
We can store a contact name and address key for each recruitment
instrument. The address key can be used to store the address (of a
contact) for a recruitment instrument in step "Create addresses for
recruitment instruments".
SAP R/3 Role Personal Data
Menu
Transaction SPRO
Code
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management ->
Recruitment -> Workforce Requirement
and Advertisement -> Create recruitment
instrument
Description and Configuration Values

The following table reproduces the initial values configured for Cairn
Energy

Instrum Mediu Name of Addres Conta

. Instrument m medium s ct

000000
01 Times of India 01 Press

47
 000000
02 Indian Express 01 Press

000000
03 Monster.com 15 Internet

000000
04 Cairn Portal 15 Internet

000000 Internal Internal

05 magazine 06 press

000000
06 Outlook email 05 Mail

000000
07 Anna University 10 University

000000
08 Naukri.com 15 Internet

000000
09 Hindu 01 Press

000000 Economic
10 Times 01 Press

Applicant Administration
This component is used to coordinate and monitor all the steps involved in
applicant administration. The two-tiered data entry concept provides a
fast and easy way to enter and structure unsolicited applications, and
applications in response to a specific advertisement.

Create Personnel Officer

In this step we create company's personnel officers.

Personnel officers process the applications assigned to them according to
their authorization from the Personnel Department.
Personnel officers for Recruitment must be created as part of administrator group APPL. We can use
an ID of our choice for the personnel officer.

48
 SAP R/3 Role Personal Data
Menu
Transaction SPRO
Code
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management ->
Recruitment -> Applicant Administration ->
Create Personnel Officer
Description and Configuration Values

The following table reproduces the initial values configured for Cairn
Energy:

Administrator
Grp Ad. name Title Tel.no. SAP Name

APPL NID Nidhi Ms

APPL NIR Nirmal Mr

PR
APPL V Pravin Mr

PU
APPL R Purnima Ms

PU
APPL S Pushpendra Mr

SH
APPL B Shoba Ms

ST
APPL U Stuti Ms

SU
APPL N Sunayna Ms

Applicant Structure
When their data is first entered in the system, applicants are structured
according to the following criteria:

 Internal or external applicants.

 Unsolicited applicants / Applicants who applied in response to an
advertisement.
 Applicant Groups.
 Applicant range.

49
Internal applicants are those employed by the company on the date that
the job application is received. External applicants are those not
employed by the company on this date. This latter grouping can therefore
also include former employees of the company.

The procedure for entering data is different for internal and external
applicants. We have to manually enter all required data on external
applicants. When dealing with internal applicants, however, we can import
data such as name and address simply by specifying the candidate's
personnel number. We can overwrite this data, if necessary.

Both internal and external applicants can submit unsolicited applications,

or apply in response to an advertisement. We need to assign applicants
who file an unsolicited application to an unsolicited application group
during initial data entry. An unsolicited application group is a user-
definable criterion for use in structuring unsolicited applications.

An applicant group is used to group together applicants on the basis of the

type of work relationship for which they have applied (for example,
employees with a permanent contract, employees with a temporary
contract, freelance workers, and so on). The applicant class is a
characteristic of the applicant group. The applicant class indicates
whether the applicant is internal (applicant class P) or external (applicant
class AP).

The applicant range is another user-definable criterion used for classifying

applicants. Generally speaking, it classifies applicants on the basis of
either hierarchical or functional criteria. Classifying the applicants
hierarchically involves dividing them into groups, such as executive
employees, salaried employees, skilled workers, and so on. Functional
classification involves dividing them according to areas of employment,
such as executive board, administration department, production, and so
on.

Applicant Group

50
 SAP R/3 Role Personal Data
Menu
Transaction SPRO
Code
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management ->
Recruitment -> Applicant Administration ->
Applicant Structure -> Create Applicant
Group

Description and Configuration Values

The following table reproduces the initial values configured for Cairn
Energy

A App.grou ApC Applicant

G p l Class Text

National External
1 s AP applicant

Expatria External
2 tes AP applicant

Applicant Range

SAP R/3 Role Personal Data

Menu
Transaction SPRO
Code
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management ->
Recruitment -> Applicant Administration ->
Applicant Structure -> Create Applicant
Range
Description and Configuration Values

The following table reproduces the initial values configured for Cairn
Energy:

A
R Applicant range

01 Employee

51
 02 Consultants

Third Party
03 Consult

Unsolicited application groups

SAP R/3 Role Personal Data

Menu
Transaction SPRO
Code
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Personnel Management ->
Recruitment -> Applicant Administration ->
Applicant Structure -> Create unsolicited
application groups
Description and Configuration Values

The following table reproduces the initial values configured for Cairn
Energy

UAGp Unsol.app.group

001 Bihar Asset

Business
002 Development

003 CEO's Office

004 Communications

005 COO's Office

006 Design Office

007 Drilling

008 Exploration

009 Finance

010 HR & Admin

011 HSE,CSR & LAND Acq.

012 IT&C and IM

013 Legal

014 Petroleum Engg

52
 015 Procurement

016 Production

017 Production -RV & CB

Applicant Selection
Applicant Activities

In the Recruitment component, applicant activities are used to enter, log,

and plan all the tasks performed for an applicant during the selection
procedure. Applicant activities are administrative stages through which an
applicant passes during the course of the application procedure.

The following characteristics are among those used to identify an

applicant activity:

 Activity type

The activity type denotes the activity that is to be carried out for an
applicant (e.g. Mail confirmation of receipt, Mail invitation to interview,
Appointment for interview).

 Activity status

The activity status indicates whether the activity has already been
performed for an applicant (completed) or is still to be performed
(planned).

 Performance date

For planned activities, the performance date indicates the date by or

on which the activity is to be carried out; for completed activities it
indicates the date on which they were actually carried out.

 Person responsible for activity

This employee is responsible for ensuring that the activity is carried

out on or by the deadline specified, and may be responsible for
carrying it out him/herself.

Applicant Activity types

53
 SAP R/3 Role Personal Data
Menu
Transaction SPRO
Code
IMG Menu Implementation Guide for R/3 Customizing (IMG)
-> Personnel Management -> Recruitment ->
Applicant Selection -> Applicant Activities ->
Applicant Activity Types -> Create applicant
activity types

Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy

System
Ac Activ. sh.text Act.type long text Fnction System Function Text

Mail confirmation Applicant

001 Receipt of receipt P correspondence

Transfer applicant
002 Transfer file file

003 File returned File returned

Video Applicant
004 interview Video Conference P correspondence

Telecon- Applicant
005 Intrvue Phone based P correspondence

Face-Face- Applicant
006 Intrw Face to face P correspondence

Test Mail invitation to Applicant

007 invitation test P correspondence

Date of applicant
008 Test date test

009 Appraisal Hand in appraisal

Applicant
010 Mail contract Mail contract P correspondence

Mail rejection Applicant

011 Rejection letter P correspondence

54
 Travel Travel expense
012 expenses accounting

Approve
013 hiring Approve hiring

014 Hiring date Hiring date

Transfer applicant Transfer data to

015 Transfer data data D employee

Applicant
016 Interim reply Mail interim reply P correspondence

Hire
017 applicant Hire applicant

Medical Medical
018 exam. examination

Contr.returne Contract returned

019 d by applicant

020 Reject appl. Reject applicant

Offer Mail offer of Applicant

021 contract contract P correspondence

Put applicant on Applicant

022 On hold hold P correspondence

Work Send work

023 contract contract

Telephonic Telephonic Applicant

090 Int. Interview P correspondence

Face-to-face Applicant
091 Face-face Int. Interview P correspondence

________________________

Default Values

Feature : PACPA

PACPA Parameter Settings for Follow-up Actions

Object

Feature

55
 Task

This feature defines how the parameters are to be set for actions
proposed as follow-up actions. Follow-up actions are defined using feature
PACPP.

Use

In transaction PB60 using "Foll.actions" function key.

Procedure

The return matrix of the feature has the following structure: XXXXX

ZZZZZ.

XXXXX: Field name for an action (APLACTI4)

o PLDAT Performance date (mandatory field).

o PLTIM Performance time.

o RECTK Indicator as to whether 'planned' actions are to be carried

out using recurring tasks.

o IDTXT Text number for standard text.

o PERNR Pers.no. of person responsible for action.

ZZZZZ: Value entered in field, 20 characters long.

o PLDAT ZZZZZ = nn Number of days, added to date of previous

action to obtain performance date. If this date is already

past, the system proposes the current date as a default.

o RECTK ZZZZZ = X Planned action is carried out using recurring

tasks.

o PERNR ZZZZZ = 8-digit personnel number from the master database.

The next line in the feature is accessed by means of operation NEXTR.

The last line of an action ends with a comma (not NEXTR).

Variable
Line key F C Operations

56
00001
0 D APACT

00002 &PACPA=IDTXT
0 004 INTERVIEW_INTIMATION_LETTER, NEXTR A

000030 004 A &PACPA=RECTK X, NEXTR B

000040 004 B &PACPA=PLDAT 1,

&PACPA=IDTXT INTERVIEW_INTIMATION_LETTER,
000050 005 NEXTR A

000060 005 A &PACPA=RECTK X, NEXTR B

000070 005 B &PACPA=PLDAT 1,

&PACPA=IDTXT INTERVIEW_INTIMATION_LETTER,
000080 006 NEXTR A

000090 006 A &PACPA=RECTK X, NEXTR B

000100 006 B &PACPA=PLDAT 1,

000110 007 &PACPA=IDTXT INVITATION, NEXTR A

000120 007 A &PACPA=RECTK X, NEXTR B

000130 007 B &PACPA=PLDAT 1,

000140 008 &PACPA=PLDAT 10,

000150 010 &PACPA=IDTXT OFFER-CONTRACT, NEXTR A

000160 010 A &PACPA=RECTK X, NEXTR B

000170 010 B &PACPA=PLDAT 20,

000180 011 &PACPA=IDTXT REJECTION_LETTER, NEXTR A

000190 011 A &PACPA=RECTK X, NEXTR B

000200 011 B &PACPA=PLDAT 20,

000210 016 &PACPA=IDTXT PRELIMINARY-RECEIPT, NEXTR A

000220 016 A &PACPA=RECTK X, NEXTR B

000230 016 B &PACPA=PLDAT 2,

000240 020 &PACPA=PLDAT 2,

000250 *** &PACPA=PLDAT 2, NEXTR A

000260 *** A &PACPA=PERNR 2, NEXTR B

57
000270 *** B &PACPA=PERN1 3, NEXTR C

000280 *** C &PACPA=PERN2 4,

Time Management
The Time Management component offers the support in performing all human
resources processes involving the planning, recording, and valuation of internal
and external employees’ work performed and absence times.

Time Management has user-oriented interfaces that support centralized and

decentralized entry and administration of time and labor data. Data can be
processed centrally by administrators in the human resources department or
else in individual departments by time administrators such as supervisors,
secretaries, and employees themselves.

Work Schedules

i. Define Public Holiday Classes

Personal Sub Area Groupings

i. Group Personal Sub Areas for the Work Schedule

ii. Group Personal Sub Areas for the Daily Work Schedule
Daily Work Schedule

 Define Break Schedule

 Define Rules for variants
 Define Daily work Schedule
Period Work Schedule

 Define Period Work Schedules

Day Types
 Define Day Types
 Define Selection rules
 Define Special days
Work Schedule rules and Work Schedules

 Define Employee subgroup Groupings

 Define Groupings for the Public Holiday Calendar
 Set Work Schedule Rules and Work Schedules

58
  Generate Work Schedules Manually
 Generate Work Schedules in Batch
Planned Working Time

 Set Default Value for the Work Schedule

 Set Which Hour Fields Are Entry Fields
 Define Working Weeks
 Set Default Value for Time Management Status
Time Data Recording and Administration

 Absences
1) Absence Catalog:
 Group Personnel Sub areas for
Attendances and Absences.
 Define Absence Types
 Define Illness Types
 Determine Entry Screens and Time
Constraint Classes.
2) Absence Counting:
 Define Counting Classes for the Period
Work Schedule.
3) Rules for Absence Counting (New):
 Group Employee Subgroups for Time
Quotas.
 Group Personnel Sub areas for Time
Quotas.
 Define Rules for Rounding Counted
Absences.
 Define Counting Rules.
 Assign Counting Rules to Attendance
Types.
4) Special Absence Data:

 Maternity Protection
 Set Eligibility for Info type
 Define Absence Types
 Define Types of Birth
 Define Maternity Protection Periods
 Define Default Absence Types
Managing Time Accounts Using
Attendance/Absence

Quotas:

 Setting Groupings for Time Quotas

 Group Employee Subgroups for Time
Quotas
 Group Personnel Sub areas for Time
Quotas.
 Time Quota Types
Create Number Range Intervals

Define Absence Quota Types

59
 Define Absence Quota Types and Indicate

leave.

 Calculating Absence Entitlements

Automatic Accrual of Absence Quotas

Rules for Generating Absence Quotas

Setting up Methods for Quota Accrual

 Quota Deduction Using Attendances /

Absences.
Define Deduction Rules for Absence and

Attendance Quotas.

Assign Deduction Rules to Counting Rules.

60
61
Define Public Holidays:

62
Public Holiday Calendar
The public holiday calendar plays an important role in the Human Resources
modules. It affects the definition of the organizational structure of the
enterprise and plays a central role in the scheduling process as well in
generating monthly work schedules.
The public holiday calendar is based on an actual year and allows you to apply
your working time models to a specific time period.
It is essential to use the public holiday calendar for recording your employees’
attendances and absences: the payroll program can only be run correctly if
Sundays and public holidays and so on are taken into account.
Create Public Holiday Calendar
The public holiday calendar is created on the basis of the regional and national
holidays that are valid for your personnel areas and subareas. Company-specific
days off for the festivals can also be entered in the calendar. All National and
Festival Holidays for different Locations can be created in the system and
assigned to the holiday calendar.
Create Public Holiday Calendars

In this step create the public holiday calendars for locations and assign the public
holidays to these calendars.

63
 SAP R/3 Role Define Public Holiday Classes
Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Work Schedules
-> Define Public Holiday Classes
Description and Configuration Values

The following table reproduces the holiday calendars configured for various
locations of Cairn Energy.

Calendar id: CB - Cairn Barmer & Jodhpur

Public Holiday Valid From Valid To

Christmas 1900 2098

Diwali 1900 2098

Gandi Jayanthi 1900 2098

Good Friday 1900 2098

Holi 1900 2098

Independance Day
(India) 1900 2098

Maharana Pratap
Jayanti 1900 2098

May Day 1900 2098

Ramazan 1900 2098

Republic Day (India) 1900 2098

Sri Krishna Jayanti 1900 2098

Calendar id: CC - Cairn Chennai

Public Holiday Valid From Valid To

Christmas 1900 2098

Deepavali 1900 2098

Gandi Jayanthi 1900 2098

Ganesha Chaturthi 1900 2098

64
 Independance Day
(India) 1900 2098

May Day 1900 2098

Ramazan 1900 2098

Republic Day (India) 1900 2098

Sri Krishna Jayanti 1900 2098

Tamil New Year 1900 2098

Ugadi Telugu New

Year 1900 2098

Calendar id: CG - Cairn Gurgaon

Public Holiday Valid From Valid To

Christmas 1900 2098

Diwali 1900 2098

Diwali1 1900 2098

Gandi Jayanthi 1900 2098

Good Friday 1900 2098

Holi 1900 2098

Independance Day
(India) 1900 2098

May Day 1900 2098

Ram Navami 1900 2098

Ramazan 1900 2098

Republic Day (India) 1900 2098

Sri Krishna Jayanti 1900 2098

Calendar id: CK - Cairn Kakinada

Vali
d
Fro
Public Holiday m Valid To

190
Christmas 0 2098

Deepavali 190 2098

65
 0

Dussehra / Ayudha 190

Puja 0 2098

190
Gandi Jayanthi 0 2098

190
Good Friday 0 2098

Independance Day 190

(India) 0 2098

190
Makra Sankaranti 0 2098

190
May Day 0 2098

190
Ramazan 0 2098

190
Republic Day (India) 0 2098

Ugadi Telugu New 190

Year 0 2098

Calendar id: CM - Cairn S’yanam

Vali
d
Fro
Public Holiday m Valid To

190
1 Ramadan 0 2098

190
Deepavali 0 2098

Dussehra / Ayudha 190

Puja 0 2098

190
Gandi Jayanthi 0 2098

190
Good Friday 0 2098

Independance Day 190

(Indi 0 2098

66
 190
Makra Sankaranti 0 2098

190
May Day 0 2098

190
Ramazan 0 2098

190
Republic Day (India) 0 2098

Ugadi Telugu New 190

Year 0 2098

Calendar id: CP - Cairn Patna

Public Holiday Valid From Valid To

Chhath Puja 1900 2098

Christmas 1900 2098

Diwali 1900 2098

Gandi Jayanthi 1900 2098

Good Friday 1900 2098

Holi 1900 2098

Independance Day (In 1900 2098

May Day 1900 2098

Ramazan 1900 2098

Republic Day (India) 1900 2098

Sri Krishna Jayanti 1900 2098

Calendar id: CR - Cairn Rajahmundry

Public Holiday Valid From Valid To

Christmas 1900 2098

Deepavali 1900 2098

Dussehra / Ayudha
Puja 1900 2098

Gandi Jayanthi 1900 2098

Good Friday 1900 2098

Independance Day 1900 2098

67
 (India)

Makra Sankaranti 1900 2098

May Day 1900 2098

Ramazan 1900 2098

Republic Day (India) 1900 2098

Ugadi Telugu New

Year 1900 2098

Calendar id: CS - Cairn Suvali

Public Holiday Valid From Valid To

Christmas 1900 2098

Deepavali 1900 2098

Dhulati (Holi Second

day) 1900 2098

Gandi Jayanthi 1900 2098

Good Friday 1900 2098

Gujarati New Year 1900 2098

Independance Day
(India) 1900 2098

Makra Sankaranti 1900 2098

May Day 1900 2098

Ramazan 1900 2098

Republic Day (India) 1900 2098

Assign Public Holiday Calendars to Locations

The holiday calendar is assigned to a Personnel Subarea / Location. As Employees
are assigned to Personnel Sub areas/locations, all the holidays applicable for that
location automatically applies to the employee.

Any required changes to the public holiday calendar can be made at any time.

Assign Personnel Subarea to Public Holiday Calendar

In this step assign the public holiday calendars to the defined personnel subareas
(locations).

68
 SAP R/3 Role Define Public Holiday Classes
Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Work Schedules
-> Work Schedule Rules and Work Schedules
-> Define Groupings for the Public Holiday
Calendar

Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

Personnel Personnel Area Personnel Personnel Holiday

Area Text Sub Area Sub Area Text Calendar ID

001 Cairn India 01 Gurgaon CG

001 Cairn India 02 S`yanam CM

001 Cairn India 03 Rajahmundry CR

001 Cairn India 04 Kakinada CK

001 Cairn India 05 Barmer CB

001 Cairn India 06 Jodhpur CB

001 Cairn India 07 Patna CP

001 Cairn India 08 Suvali CS

001 Cairn India 09 Chennai CC

Work Schedules
With this component, the settings required for creating work schedules for the
employees in the enterprise can be made. Work schedules are shift schedules
which must be generated for all employees, even those with a set working time
(salaried employees) or flextime. A work schedule consists of several different
elements. Elements of the work schedule include daily work schedules, period
work schedules, and work schedule rules.
Work schedules can be defined with flextime models or rotating shifts for
particular organizational units. It can also set up the legislative regulations,
collective agreements and internal company policies that stipulate employee
working time in the system.

Personnel Subarea Groupings

Personnel subarea groupings are used to group the employees for work schedule
rules based on the personnel subareas / locations.

69
Group Personnel Subareas for the Work Schedule

In this step, group the personnel areas and personnel subareas for work
schedules.

SAP R/3 Role Personnel Subarea Groupings

Menu

Transaction Code SPRO

IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Work Schedules
-> Personnel Subarea Groupings -> Group
Personnel Subareas for the Work Schedule

Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

Personnel
Personnel Personnel Personnel Personnel Sub Subarea
Area Area Text Sub Area Area Text Grouping

001 Cairn India 01 Gurgaon 40

001 Cairn India 02 S`yanam 40

001 Cairn India 03 Rajahmundry 40

001 Cairn India 04 Kakinada 40

001 Cairn India 05 Barmer 40

001 Cairn India 06 Jodhpur 40

001 Cairn India 07 Patna 40

001 Cairn India 08 Suvali 40

001 Cairn India 09 Chennai 40

Group Personnel Subareas for Daily Work Schedule

In this step, assign a personnel area grouping for daily work schedules to a
personnel area grouping for work schedules.

70
 SAP R/3 Role Personnel Subarea Groupings
Menu

Transaction Code SPRO

IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Work Schedules
-> Personnel Subarea Groupings -> Group
Personnel Subareas for the Daily Work
Schedule

Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

PS Grouping DWS Grouping

01 01

02 02

03 03

04 04

05 05

06 06

07 07

08 08

Daily Work Schedules

The daily work schedule determines the structure of working times in the
enterprise at the daily level. Also actual normal working conditions can be defined
and those that differ from externally or internally determined daily working times.
In this way, sets of working times can be defined for specific set of employees.

The planned working time specified in a daily work schedule is the basis for
payment calculation of actual working times that are relevant for payroll, as well
as the valuation of attendances and absences.

The daily work schedule, along with Break Schedules, comprise of the working
times for a particular day. The break rules in the work schedule for any particular

71
working day can be defied and can be assigned to a personnel sub area grouping
for work schedules. This grouping enables to assign a break schedule to as many
of the grouping’s daily work schedules as we want, thereby achieving maximum
flexibility in combining all elements of the daily work schedule.

Define Break Schedules

In this step, define work break schedules for the enterprise. We can specify
exactly when breaks may be taken within the daily work schedule, and whether
they are paid or unpaid.

SAP R/3 Role Menu Daily Work Schedules

Transaction Code SPRO

IMG Menu Implementation Guide for R/3 Customizing (IMG)
-> Time Management -> Work Schedules -> Daily
Work Schedules -> Define Break Schedules

Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

Groupin Brea N Star Unpai Pai Afte RefTi Type Type

g k o t End P d d r m 1 2

40 12:0 13:0
6DAY 01 0 0 1.00

40 NOR 12:0 13:0

M 01 0 0 1.00

Define Daily Work Schedules

In this step, daily work schedules for the enterprise are defined. By entering the
planned working time, the system calculates the planned planed hours for one
day, taking the break schedule into consideration. The daily work schedules for
availability are also defined in this step.

72
 SAP R/3 Role Daily Work Schedules
Menu

Transaction Code SPRO

IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Work Schedules
-> Daily Work Schedules -> Define Daily Work
Schedules

Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

Groupin Daily Work Varia Start

g Schedule nt Daily WS Text Date End Date

73
 01.01.19 31.12.99
40 12HR 12 Hrs Working 90 99

01.01.19 31.12.99
40 6DAY 6 day 90 99

01.01.19 31.12.99
40 ASFT A shift (Morng) 90 99

01.01.19 31.12.99
40 BSFT B shift (eving) 90 99

01.01.19 31.12.99
40 CSFT C shift (night) 90 99

01.01.19 31.12.99
40 FLEX Flextime 00 99

01.01.19 31.12.99
40 FREE Free 00 99

Normal 01.01.19 31.12.99

40 NORM Working 90 99

Period Work Schedules

The period work schedule consists of a defined sequence of daily work schedules.
It reflects a work pattern that is repeated after a defined period of time. Period
work schedules can extend over one week, several weeks, or a period that is not
divisible by seven.

Period work schedule can be created for any length of time: The period work
schedule can provide the working time model for one week, as do flextime
models, or for an entire year.

Period work schedules can also be created for longer term working models, such
as those that cover the entire year. The week number distinguishes between the
individual elements of a period.

Define Period Work Schedules

In this step, the period work schedules are created by specifying the sequence of
daily work schedules for a work schedule for one or more weeks.

74
 SAP R/3 Role Period Work Schedules
Menu

Transaction Code SPRO

IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Work Schedules
-> Period Work Schedules -> Define Period
Work Schedules
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

Period WS
Grp PWS Text Week 01 02 03 04 05 06 07

10 Day On 4
40 10D4 Day Off 001 NORM NORM NORM NORM NORM NORM NORM

10 Day On 4
40 10D4 Day Off 002 NORM NORM NORM FREE FREE FREE FREE

14 Days
40 14DY Rotational 001 12HR 12HR 12HR 12HR 12HR 12HR 12HR

14 Days
40 14DY Rotational 002 12HR 12HR 12HR 12HR 12HR 12HR 12HR

14 Days
40 14DY Rotational 003 FREE FREE FREE FREE FREE FREE FREE

14 Days
40 14DY Rotational 004 FREE FREE FREE FREE FREE FREE FREE

15 Days
40 15DY Rotational 001 NORM NORM NORM NORM NORM NORM NORM

15 Days
40 15DY Rotational 002 NORM NORM NORM NORM NORM NORM NORM

15 Days
40 15DY Rotational 003 NORM FREE FREE FREE FREE FREE FREE

21 Days
40 21DY Rotational 001 12HR 12HR 12HR 12HR 12HR 12HR 12HR

21 Days
40 21DY Rotational 002 12HR 12HR 12HR 12HR 12HR 12HR 12HR

21 Days
40 21DY Rotational 003 12HR 12HR 12HR 12HR 12HR 12HR 12HR

40 21DY 21 Days 004 FREE FREE FREE FREE FREE FREE FREE

75
 Rotational

21 Days
40 21DY Rotational 005 FREE FREE FREE FREE FREE FREE FREE

21 Days
40 21DY Rotational 006 FREE FREE FREE FREE FREE FREE FREE

28 Days
40 28DY Rotational 001 12HR 12HR 12HR 12HR 12HR 12HR 12HR

28 Days
40 28DY Rotational 002 12HR 12HR 12HR 12HR 12HR 12HR 12HR

28 Days
40 28DY Rotational 003 12HR 12HR 12HR 12HR 12HR 12HR 12HR

28 Days
40 28DY Rotational 004 12HR 12HR 12HR 12HR 12HR 12HR 12HR

28 Days
40 28DY Rotational 005 FREE FREE FREE FREE FREE FREE FREE

28 Days
40 28DY Rotational 006 FREE FREE FREE FREE FREE FREE FREE

28 Days
40 28DY Rotational 007 FREE FREE FREE FREE FREE FREE FREE

28 Days
40 28DY Rotational 008 FREE FREE FREE FREE FREE FREE FREE

Six days
40 6DAY working 001 6DAY 6DAY 6DAY 6DAY 6DAY 6DAY FREE

6/2 Days
40 6DRO Rotatioanl 001 ASFT ASFT BSFT BSFT CSFT CSFT FREE

6/2 Days
40 6DRO Rotatioanl 002 FREE *

6 Week On 1
40 6WK1 Week Off 001 NORM NORM NORM NORM NORM NORM NORM

6 Week On 1
40 6WK1 Week Off 002 NORM NORM NORM NORM NORM NORM NORM

6 Week On 1
40 6WK1 Week Off 003 NORM NORM NORM NORM NORM NORM NORM

6 Week On 1
40 6WK1 Week Off 004 NORM NORM NORM NORM NORM NORM NORM

40 6WK1 6 Week On 1 005 NORM NORM NORM NORM NORM NORM NORM

76
 Week Off

6 Week On 1
40 6WK1 Week Off 006 NORM NORM NORM NORM NORM NORM NORM

6 Week On 1
40 6WK1 Week Off 007 FREE FREE FREE FREE FREE FREE FREE

6 Week On 2
40 6WK2 Week Off 001 NORM NORM NORM NORM NORM NORM NORM

6 Week On 2
40 6WK2 Week Off 002 NORM NORM NORM NORM NORM NORM NORM

6 Week On 2
40 6WK2 Week Off 003 NORM NORM NORM NORM NORM NORM NORM

6 Week On 2
40 6WK2 Week Off 004 NORM NORM NORM NORM NORM NORM NORM

6 Week On 2
40 6WK2 Week Off 005 NORM NORM NORM NORM NORM NORM NORM

6 Week On 2
40 6WK2 Week Off 006 NORM NORM NORM NORM NORM NORM NORM

6 Week On 2
40 6WK2 Week Off 007 FREE FREE FREE FREE FREE FREE FREE

6 Week On 2
40 6WK2 Week Off 008 FREE FREE FREE FREE FREE FREE FREE

8 Week On 2
40 8WK2 Week Off 001 NORM NORM NORM NORM NORM NORM NORM

8 Week On 2
40 8WK2 Week Off 002 NORM NORM NORM NORM NORM NORM NORM

8 Week On 2
40 8WK2 Week Off 003 NORM NORM NORM NORM NORM NORM NORM

8 Week On 2
40 8WK2 Week Off 004 NORM NORM NORM NORM NORM NORM NORM

8 Week On 2
40 8WK2 Week Off 005 NORM NORM NORM NORM NORM NORM NORM

8 Week On 2
40 8WK2 Week Off 006 NORM NORM NORM NORM NORM NORM NORM

8 Week On 2
40 8WK2 Week Off 007 NORM NORM NORM NORM NORM NORM NORM

40 8WK2 8 Week On 2 008 NORM NORM NORM NORM NORM NORM NORM

77
 Week Off

8 Week On 2
40 8WK2 Week Off 009 FREE FREE FREE FREE FREE FREE FREE

8 Week On 2
40 8WK2 Week Off 010 FREE FREE FREE FREE FREE FREE FREE

5 Days
40 NORM Working 001 NORM NORM NORM NORM NORM FREE FREE

Work Schedule Rules and Work Schedules

A work schedule rule is a precise description of the work schedule that specifies
the working times of a group of employees.

A work schedule rule is assigned a period work schedule, which in turn is made
up of daily work schedules. Rotating shifts are set up by assigning a period work
schedule to several work schedule rules.

Work schedules are not stored all at once, but stored for each month. The work
schedule is created regardless of the length of the period work schedule and is
not person-specific.

Define Employee Subgroup Groupings

The employee subgroup grouping for work schedules allows us to group several
employee subgroups and base their work schedules on the same rules.

SAP R/3 Role Work Schedule Rules and Work Schedules

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Work Schedules
-> Work Schedule Rules and Work Schedules
-> Define Employee Subgroup Groupings

Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

Define Employee Subgroup Grouping

ESGrp
g ES Grpg for WS

0 Applicants

1 Hourly wage

78
 earners

Salaried
2 employees

3 Executive

4 Executive - PH

6 Holder

7 Non-holder

Group Employee Subgroups for Work Schedules

Emp Emp Group Emp Emp Sub Group Text ES Grouping

Group Text Sub
Group

1 Nationals 01 Employee 2

1 Nationals 02 Direct Consultants 2

Third Party
1 Nationals 03 Consultant 2

2 Expatriates 01 Employee 2

2 Expatriates 02 Direct Consultants 2

Third Party
2 Expatriates 03 Consultant 2

Set Work Schedule Rules and Work Schedules

In this step, you define the work schedule rules that are assigned to employees in
the Planned Working Time infotype (0007). The work schedule rule is assigned to a
period work schedule and the holiday calendars.

SAP R/3 Role Menu Work Schedule Rules and Work Schedules
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing (IMG)
-> Time Management -> Work Schedules -> Work
Schedule Rules and Work Schedules -> Set Work
Schedule Rules and Work Schedules

79
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

ES ES Grpg for Holiday Text PS WS Start End Date

Grp WS Calend Gropin Rule Date
g ar g

Cairn
Salaried Barmer & 01.01.19 31.12.99
2 employees CB Jodhpur 40 10D4 90 99

Cairn
Salaried Barmer & 01.01.19 31.12.99
2 employees CB Jodhpur 40 15DY 90 99

Cairn
Salaried Barmer & 01.01.19 31.12.99
2 employees CB Jodhpur 40 21DY 90 99

Cairn
Salaried Barmer & 01.01.19 31.12.99
2 employees CB Jodhpur 40 28DY 90 99

2 Salaried CB Cairn 40 6WK1 01.01.19 31.12.99

80
 Barmer &
employees Jodhpur 90 99

Cairn
Salaried Barmer & 01.01.19 31.12.99
2 employees CB Jodhpur 40 6WK2 90 99

Cairn
Salaried Barmer & 01.01.19 31.12.99
2 employees CB Jodhpur 40 8WK2 90 99

Cairn
Salaried Barmer & NOR 01.01.19 31.12.99
2 employees CB Jodhpur 40 M 90 99

Salaried Cairn NOR 01.01.19 31.12.99

2 employees CC Chennai 40 M 90 99

Salaried Cairn 01.01.19 31.12.99

2 employees CG Gurgaon 40 10D4 90 99

Salaried Cairn NOR 01.01.19 31.12.99

2 employees CG Gurgaon 40 M 90 99

Salaried Cairn 01.01.19 31.12.99

2 employees CM S’yanam 40 21DY 90 99

Salaried Cairn NOR 01.01.19 31.12.99

2 employees CM S’yanam 40 M 90 99

Salaried 01.01.19 31.12.99

2 employees CP Cairn Patna 40 21DY 90 99

Salaried 01.01.19 31.12.99

2 employees CP Cairn Patna 40 6DAY 90 99

Salaried NOR 01.01.19 31.12.99

2 employees CP Cairn Patna 40 M 90 99

Cairn
Salaried Rajahmundr NOR 01.01.19 31.12.99
2 employees CR y 40 M 90 99

Salaried 01.01.19 31.12.99

2 employees CS Cairn Suvali 40 14DY 90 99

Salaried 01.01.19 31.12.99

2 employees CS Cairn Suvali 40 6DAY 90 99

Salaried 01.01.19 31.12.99

2 employees CS Cairn Suvali 40 6DRO 90 99

Generate Work Schedules Manually

81
Work schedules can be generated in this step. The existing work schedules can
also be changed or deleted.

Create all function can be used to generate for more than a month. The function
can be called via the 'Edit' menu option.

If the work schedules need to be created from January through December of a

particular year, December of the previous year and January of the following year
must be included.

"Create" function can be used to generate the monthly work schedule one month
at a time (with confirmation). the "Create all" function can be used to generate
the work schedule for the required period without confirmation.

SAP R/3 Role Work Schedule Rules and Work Schedules

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Work Schedules
-> Work Schedule Rules and Work Schedules
-> Generate Work Schedules Manually

Planned Working Time

The Planned Working Time infotype (0007) allows us to enter a work schedule to
define individual working times for employees. It also allows store the time
management status for that employee.

The time management status specifies whether an employee participates in time

evaluation, and if so, which form.

The following are possible values for the time management status:

0 No time evaluation

1 Time evaluation - actual times

2 Time evaluation - PDC

7 Time evaluation without payroll integration

8 External services

9 Time evaluation - planned times

82
Set Default Value for Time Management Status

In this step a feature is used to create a default value for the time management
status in the Planned Working Time infotype. This default value is proposed when
we create an infotype record. It can be determined on the basis of an employee's
organizational assignment.

SAP R/3 Role Planned Working Time

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Work Schedules
-> Planned Working Time -> Set Default Value
for Time Management Status

Time Data Recording and Administration

The time structures in the company can be represented using working time
models, the calendar, and by maintaining the Time Management infotypes. These
options allow us to enter all time data and related information for your employees.
This time data includes attendance and absence times, availability times, and
overtime, for example.

83
With this component, all the necessary settings can be made to allow the
recording of working times for individual employees. This includes absences such
as illness, leave, substitutions, overtime, and so on.

A status for Time Management is defined which indicates whether all attendances
are recorded for an employee, or only exceptions to the work schedule.

It is also determined that how the system should react if working time data is
entered which overlaps with existing data (for example, if an illness record
overlaps with a leave record).

Absence Catalog
Absences are paid or unpaid planned working times during which the employee
has not worked. They therefore represent a deviation to the employee's work
schedule. Information required for defining and recording absences can be stored
in this area.
In this section, the settings required for recording and processing absences are
made.
Group Personnel Subareas for Attendances and Absences

In this step, personnel areas and subareas are grouped for attendance and
absence types.
For example, if the same attendance and absence types are to be assigned to
personnel subareas 01 and 02, same grouping for these both personnel areas
needs to be defined.

SAP R/3 Role Absence Catalog

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Time Data
Recording and Administration -> Absences ->
Absence Catalog -> Group Personnel Subareas
for Attendances and Absences
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

Personnel text Personne Text PS Grouping

Area l Subarea

001 Cairn India 01 Gurgaon 40

001 Cairn India 02 S`yanam 40

001 Cairn India 03 Rajahmundry 40

001 Cairn India 04 Kakinada 40

001 Cairn India 05 Barmer 40

84
 001 Cairn India 06 Jodhpur 40

001 Cairn India 07 Patna 40

001 Cairn India 08 Suvali 40

001 Cairn India 09 Chennai 40

Define Absence Types

In this step, absence types for different personnel subarea groupings are defined.
Also the checks which the system performs can be defined when the absence is
entered.

SAP R/3 Role Absence Catalog

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Time Data
Recording and Administration -> Absences ->
Absence Catalog -> Define Absence Types

Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

Personn Absence Absence Text Start End Date

el Area Type Date

01.01.19 31.12.99
40 100 Annual Leave 90 99

85
 01.01.19 31.12.99
40 200 Casual Leave 00 99

01.01.19 31.12.99
40 300 Sick leave 00 99

Maternity Leave-14 01.01.19 31.12.99

40 400 Weeks 90 99

01.01.19 31.12.99
40 500 Paternity leave 90 99

01.01.19 31.12.99
40 600 Compassionate leave 90 99

01.01.19 31.12.99
40 700 Compensatory Off 90 99

01.01.19 31.12.99
40 800 Half day Casual 90 99

01.01.19 31.12.99
40 900 Unpaid Absence 90 99

Determine Entry Screens and Time Constraint Classes

Use the data entry screen number for an absence to determine which screen
(entry screen) is used to enter, display and maintain a record of this particular
absence type.

The time constraint class controls the system reaction if a new record in the
Absences infotype (2001) overlaps with existing time infotype records.

In the standard system, the following numbers are allocated to the screens:

1. 2000 - General absence

86
This screen is used for all absences which do not require special processing
(such as paid leave of absence for getting married).

2. 2001 - Quota deduction

This screen is used for entering data on leave or time in lieu of overtime.

3. 2002 - Work incapacity

Use this screen for all absence types where continued pay should be taken into
account automatically by the system.

4. Special screens have been developed for the following absence types:

2003 - Maternity protection, parental leave

2004 - Military and non-military service

2005 - Work incapacity (Netherlands)

SAP R/3 Role Absence Catalog

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Time Data
Recording and Administration -> Absences ->
Absence Catalog -> Determine Entry Screens
and Time Constraint Classes
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

Personnel Absence Absence Text Start Date End Date

Area Type

40 0100 Annual Leave 01.01.1990 31.12.9999

40 0200 Casual Leave 01.01.1900 31.12.9999

40 0300 Sick leave 01.01.1900 31.12.9999

Maternity Leave-14
40 0400 Weeks 01.01.1990 31.12.9999

40 0500 Paternity leave 01.01.1990 31.12.9999

40 0600 Compassionate leave 01.01.1990 31.12.9999

40 0700 Compensatory Off 01.01.1990 31.12.9999

40 0800 Half day Casual 01.01.1990 31.12.9999

40 0900 Unpaid Absence 01.01.1990 31.12.9999

87
Absence Counting
When an attendance/absence is recorded, the system refers to the planned
working hours in the employee's daily work schedule to calculate the
attendance/absence hours. This is not always desirable.
There are times when the special regulations for counting attendances and
absences need to be applied, such as:
 on specific days (public holidays, weekdays)
 for specific attendance and absence types
 for specific daily and period work schedules

The daily duration of an absence can be counted according to the rules which are
defined in this section. Thus, it can valuate the duration of attendances/absences
differently depending on business requirements.
Define Counting Classes for the Period Work Schedule

In this section, the settings for attendance/absence counting are made.

SAP R/3 Role Absence Counting

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Time Data
Recording and Administration -> Absences ->
Absence Catalog -> Absence Counting ->
Define Counting Classes for the Period Work
Schedule
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

PS Grpg Period Start End Counting

WS Class

40 10D4 01.01.1990 31.12.9999 1

40 14DY 01.01.1990 31.12.9999 1

40 15DY 01.01.1990 31.12.9999 1

88
 40 21DY 01.01.1990 31.12.9999 1

40 28DY 01.01.1990 31.12.9999 1

40 6DAY 01.01.1990 31.12.9999 1

40 6DRO 01.01.1990 31.12.9999 1

40 6WK1 01.01.1990 31.12.9999 1

40 6WK2 01.01.1990 31.12.9999 1

40 8WK2 01.01.1990 31.12.9999 1

40 NORM 01.01.1990 31.12.9999 1

Group Employee Subgroups for Time Quotas

In this step, employee subgroups for time quota types are grouped. Employee
subgroups for which the same attendance and absence quota types are defined
are assigned to the same grouping for time quota types.

SAP R/3 Role Absence Counting

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Time Data
Recording and Administration -> Absences ->
Absence Catalog -> Absence Counting -> Rules
for Absence Counting (New) -> Group
Employee Subgroups for Time Quotas
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

EE EE
Group Text Subgroup Text ESG Time Quota Types

1 Nationals 1 Employee 2

1 Nationals 2 Direct Consultants 2

1 Nationals 3 Third Party Consulta 2

89
 2 Expatriates 1 Employee 2

2 Expatriates 2 Direct Consultants 2

2 Expatriates 3 Third Party Consulta 2

Group Personnel Subareas for Time Quotas

In this step, personnel subareas are grouped with regard to the permissibility of
time quota types. Personnel subareas for which the same attendance and
absence quota types are defined are assigned to the same grouping for time
quota types.

SAP R/3 Role Absence Counting

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Time Data
Recording and Administration -> Absences ->
Absence Catalog -> Absence Counting -> Rules
for Absence Counting (New) -> Group
Personnel Subareas for Time Quotas

Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

EE EE
Group Text Subgroup Text ESG Time Quota Types

1 Nationals 1 Employee 2

1 Nationals 2 Direct Consultants 2

1 Nationals 3 Third Party Consulta 2

2 Expatriates 1 Employee 2

2 Expatriates 2 Direct Consultants 2

90
 2 Expatriates 3 Third Party Consulta 2

Define Rules for Rounding Counted Absences

In this step, you set rounding rules for absence and attendance counting.

Concrete numbers for the rounding rules are used. We can specify whether we
want:

 Only values within the specified interval to be rounded or the interval to be

rolled
 The specified upper and lower limits to be included in the calculation
 You can specify several subrules for a rounding rule and number them
sequentially. The system runs through the subrules in sequential order until
it finds one that applies.
SAP R/3 Role Absence Counting
Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Time Data
Recording and Administration -> Absences ->
Absence Catalog -> Absence Counting -> Rules
for Absence Counting (New) -> Define Rules
for Rounding Counted Absences

Define Counting Rules

In this step, you define rules for counting attendances and absences. The rules
are used to determine the payroll days and hours for an attendance or absence.
The payroll days and hours that have been counted are used to control the
deduction of quotas. They can be used in Payroll to valuate the absence.

91
SAP R/3 Role Absence Counting
Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Time Data
Recording and Administration -> Absences ->
Absence Catalog -> Absence Counting -> Rules
for Absence Counting (New) -> Define
Counting Rules

92
Assign Counting Rules to Absence Types

In this step, we determine which rule for attendance or absence counting should
be used for each attendance/absence type.

SAP R/3 Role Absence Counting

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Time Data
Recording and Administration -> Absences ->
Absence Catalog -> Absence Counting -> Rules
for Absence Counting (New) -> Assign
Counting Rules to Absence Types

93
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

Absence Counting
PSG Type Text Start Date End Date Rule

40 100 Annual Leave 01.01.1990 31.12.9999 010

40 200 Casual Leave 01.01.1900 31.12.9999 020

40 300 Sick leave 01.01.1900 31.12.9999 060

Maternity Leave-14
40 400 Weeks 01.01.1990 31.12.9999 030

40 500 Paternity leave 01.01.1990 31.12.9999 040

40 600 Compassionate leave 01.01.1990 31.12.9999 050

40 700 Compensatory Off 01.01.1990 31.12.9999 070

40 800 Half day Casual 01.01.1990 31.12.9999 080

900 Unpaid Absence 01.01.1990 31.12.9999 010

Managing Time Accounts Using Attendance/Absence

Quotas
An Absence quota specifies an employee's entitlement to time off for a limited
period. It is dependent on an absence quota type.

The Absence Quotas infotype (2006) can be used to manage all employees' time
off entitlements and leave types. The infotype's special functions ensure that an
employee can only claim the leave days stipulated in the contract as the absence
type Leave.

When an absence is recorded in the Absences infotype, the system checks

whether the employee possesses sufficient time off entitlement.

94
An Attendance quota specifies a limited period in which an employee has
approval for certain activities. It is dependent on an attendance quota type.

Setting Groupings for Time Quotas

Time quotas (time off entitlements and attendance approvals) can be grouped or
refined according to the following factors:
 Employee subgroups for time quotas (type of employee)
 Personnel subareas for time quotas (where is the employee assigned?)
 If time evaluation is used: Personnel subareas for time recording (time type
determination)
 For generating absence quotas: quota type selection rule group (which
conditions and rules apply when absence quotas are generated)
In this section, employee subgroup grouping and the personnel subareas are
grouped together based on the time quota types permitted.
Group Employee Subgroups for Time Quotas

In this step, employee subgroups for time quota types are grouped.
Employee subgroups for which the same attendance and absence quota types are
defined are assigned to the same grouping for time quota types

SAP R/3 Role Setting Groupings for Time Quotas

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Time Data
Recording and Administration -> Managing
Time Accounts Using Attendance/Absence
Quotas -> Setting Groupings for Time Quotas
-> Group Employee Subgroups for Time Quotas
Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

EE EE ESG Time Quota

Group Text Subgroup Text Types

1 Nationals 01 Employee 2

1 Nationals 02 Direct Consultants 2

1 Nationals 03 Third Party Consulta 2

2 Expatriates 01 Employee 2

2 Expatriates 02 Direct Consultants 2

2 Expatriates 03 Third Party Consulta 2

Group Employee Subgroups for Time Quotas

95
In this step, personnel subareas are grouped with regard to the permissibility of
time quota types.
Personnel subareas for which the same attendance and absence quota types are
defined are assigned to the same grouping for time quota types.

SAP R/3 Role Setting Groupings for Time Quotas

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Time Data
Recording and Administration -> Managing
Time Accounts Using Attendance/Absence
Quotas -> Setting Groupings for Time Quotas
-> Group Personnel Subareas for Time Quotas

Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

PS Groping
Personnel Personnel for time
Area Text Subarea Text quotas

1 Cairn India 01 Gurgaon 40

1 Cairn India 02 S`yanam 40

1 Cairn India 03 Rajahmundry 40

1 Cairn India 04 Kakinada 40

1 Cairn India 05 Barmer 40

1 Cairn India 06 Jodhpur 40

1 Cairn India 07 Patna 40

1 Cairn India 08 Suvali 40

1 Cairn India 09 Chennai 40

Time Quota Types

In this section the attendance and absence quota types are defined for managing
time accounts. Also we specify how attendances and absences are to be
deducted from the employees' quotas.
Define Absence Quota Types

In this step, the valid absence quota types (entitlement to time off and leave
types) for the employee subgroup and personnel subarea groupings for time quota
types are defined.

96
 SAP R/3 Role Time Quota Types
Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing
(IMG) -> Time Management -> Time Data
Recording and Administration -> Managing
Time Accounts Using Attendance/Absence
Quotas -> Time Quota Types -> Define Absence
Quota Types

Description and Configuration Values

The following table reproduces the initial values configured for Cairn Energy.

Absence
Quota
ESGpg PSGpg Type Quota Text Start Date End date

2 40 10 Annual leave(Cairn) 01.01.1990 31.12.9999

2 40 20 Casual Leave 01.01.1900 31.12.9999

2 40 21 Suwali 01.01.1900 31.12.9999

Maternity Leave-14
2 40 30 Weeks 01.01.1900 31.12.9999

97
 2 40 40 Paternity leave 01.01.1900 31.12.9999

2 40 50 Compassionate leave 01.01.1900 31.12.9999

2 40 60 Compensatory Off 01.01.1900 31.12.9999

Permit Generation of quotas in Time Evaluation

Specify Rule groups for time quota type selection:

QUOMO

98
Set Base Entitlement:

99
Determine validity and Deduction periods:

Define generation Rules for Quota type Selection:

100
Define Deduction Rules for Absence quotas:

101
Assign Deduction rules to Counting rules:

102
Setting Methods for Quota accrual:

Set up Automatic accrual using report RPTQTA00:

103
Output:

PAYROLL-INDIA

104
1 SCOPE OF THE DOCUMENT

The Payroll document contains the configuration details of the module. As part of
business process mapping following configuration has been carried out in this
module.

1.1 Payroll Module Configuration Scope

Process Functions

Payroll Area
Organizational Data
Default payroll area

Control record

Payscale type and areas

Payscale structure and Enterprise structure

Default Payscale data

ESG grp PCR and Collective agreement provision

Payscale groups and levels

Basic pay
Wagetypes characteristics and groupings

Wagetypes group Basicpay

Enterprise structure for wagetype model

Default Wagetypes for basic pay

Maintain Valuation of Base Wage Types

Wagetypes characteristics and groupings

Recurring payments and Wagetypes group Recurring payments and

deductions deductions

Maintain Valuation of Base Wage Types

Wagetypes characteristics and groupings

Wagetypes group Recurring payments and

Additional Payments
deductions

Maintain Valuation of Base Wage Types

Employee remuneration Wagetypes characteristics and groupings

105
Process Functions

Wagetypes group Recurring payments and

deductions

Assign Wage Type Model for Pay Scale Grouping for

Allowances

Maintain Default Wage Types for Basic Pay

Reimbursements,
Allowances and Perks Maintain Allowance Rules based on Slabs

Calculate Eligibility for RAPs

Maintain Extra Eligibility Criteria for RAPs

Claims and eligibilities

Claims Maintain Salary Year and Period End Treatment of
RAP

Define Accomodation Types

Housing Maintain the Processing Options for CLA

Housing allowance and perk

LTA eligibility

Leave Travel Integration with Absences

LTA exemption and period end processing

Define Vehicle Details

Define Conveyance Types

Define Amounts and Numbers for Car Schemes

Car and Conveyance Assign Type and Age of Car for Car Schemes

Assign Eligibility Criteria for Conveyance Allowance

and car maintenance

Maintain car Rate of Perquisite

Superannuation Maintain Superannuation Trust ID

Maintain Superannuation Contrib. Freq and Rel.

Wage Types

Define Contribution Rates for Superannuation

Maintain Eligibility Details for Superannuation

106
Process Functions

Wage types configuration, integration with

termination workbench

Define Trust Details for Provident Fund

Assign Company Rates for Provident Fund

Define PF Trust Validity Period

Provident Fund
Maintain Contribution Details for Provident Fund

Define Contribution type for Statutory rates for

Provident Fund

Define Personnel Area and Sub area Groupings for

LWF

Labour Welfare Fund Assign LWF Groupings for Personnel Area and
Subarea

Maintain Contribution Rates for Labour Welfare Fund

Define Professional Tax Grouping Details

Assign PTax Groupings for Personnel Areas and

Subareas

Assign Amounts for Professional Tax Deduction

Professional Tax Maintain Method and Form Layout for PTax

Groupings

Maintain Cumulation Rules for Professional Tax

Define Personnel Area and Subarea Groupings for

Tax

Assign Tax Groupings for Personnel Areas and

Subareas

Maintain Feature to Return Employer IncomeTax

Income tax Related Data

Third Party Deductions

Tax Liability on Reimbursements, Allowances and

Perks

Section 89(1) Relief

Recovery of Rounded Off

Recovery of Rounded Off Amounts during payroll run
Amounts

107
Process Functions

Determine Periods of Notice

Determine Deadline Type

Termination Maintain Calculation Factor for Retiral Benefits

Calculation method for Notice Pay

Termination workbench configuration

Specify Interest Calculation Method

Maintain Rule for Interest Rate Advantage Taxation

Maintain Loan Types

Control Allocation of Loans

Maintain Loans Grouping

Maintain Salary Components

Maintain Maximum Number of Loans Allowed

Maintain Maximum amount for loans outstanding

Company Loans Maintain Loans Eligibility Checks and Limits

Maintain Loans Disbursement Schedule

Maintain the Description for the Event Codes

Tranche

Maintain Penal Amount Percentage for Special

Repayment

Maintain Deduction Details Under Section 24

Automate Addition of Principal Repayment Amount

to Sec 88

Loan balances processing

Data Medium Exchange Bank transfers

Integration with Time Leave Encashment

Management Absences processing

Integration with accounting Define Employee Grouping Account Determination

Define Symbolic Accounts

Define Posting Characteristics of Wage Types

108
Process Functions

Assign Balance Sheet Accounts

Assign Expense Accounts

Assign Technical Accounts

Assign Vendor Accounts

Set Up Postings for Fixed Costs

Assign Substitute Cost Centers

Payroll Schema Payroll Schema

Personnel calculation rules Personnel calculation rules

Remuneration statement Remuneration statement

Create Payroll Area:

PM--> PA--> Organizational Data--> Organizational Assignment:

 Create Payroll area

109
  Check Default Payroll area
 Create Control Record

Payroll Area:

Check Default Payroll area(ABKRS):

Control Record-PA03:

110
Payroll Basic Settings:

Define Employee sub group grouping for PCR & CAP:

Purpose:

The employee subgroup grouping for the personnel calculation rule is required in
Payroll Accounting. The collective agreement provisions grouping are required
for indirect valuation of wage types in the Basic Pay Infotype (0008).

IMG Menu Path

SAP R/3 Role Basic Pay

Menu
Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing (IMG) 
Personnel Management Personnel Administration 
Payroll Data Basic Pay  Define EE Subgroup Grouping
for PCR and Coll.Agrmt.Prov.
Description and Configuration Values

Employee groups and subgroups must be set up before this activity.

The meanings of the grouping for the personnel calculation rule are fixed and
may not be changed.
For each employee subgroup, we define the personnel calculation rule grouping
that indicates the system, which set of personnel calculation rules are to be
processed / applicable to each Employee Subgroup.

111
The following table shows the details of the Employee sub group groupings
configured for Cairn Energy:

Pay scale Structure:

Pay Scale Type

Pay scale type is a collective agreement type in accordance with the collective
agreement in an enterprise.

IMG Menu Path

SAP R/3 Role Menu Basic Pay

Transaction Code SPRO

Implementation Guide for R/3 Customizing (IMG) 

IMG Menu Personnel Management  Personnel Administration 
Payroll Data  Basic Pay  Check Payscale type.

Description and Configuration Values

In this step we set up the enterprise's pay scale types. The Basic Pay Infotype
(0008) is derived from the pay scale type.
We have configured, the Payroll Scale Types of Cairn Energy as shown in the
following table.

112
Pay Scale Area
A pay scale area is a special area in which a collective agreement is valid.

When human resources of an organization are located in different Geographic’s, it

is necessary to design company’s pay structure considering the respective state
laws and employee unions.

IMG Menu Path

SAP R/3 Role Menu Basic Pay

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG)
IMG Menu  Personnel Management Personnel Administration
Payroll Data  Basic Pay Check Payscale Area
Description and Configuration Values

In this section, we set up different pay scale areas in accordance with the
collective agreement in an enterprise.
The Pay scale Type configuration details applicable for Cairn Energy are shown in
the following table.

Assign Pay Scale Structure to Enterprise Structure

In this step, we assign pay scale types and areas defined in the above steps to the
personnel areas and Personnel sub areas.

IMG Menu Path

113
SAP R/3 Role Menu Basic Pay
Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) 
Personnel Management Personnel Administration 
IMG Menu
Payroll Data Basic Pay  Check Assignment of Pay
Scale Structure to Enterprise Structure
Description and Configuration Values

We have to set up the following before configuring this step:

 The Personnel areas must be defined.

 Pay scale areas and types must be defined.
 Determine which pay scale types and areas are assigned to which
personnel areas.

The following Configuration has been done for CEIL:

Pay
Personnel
Personnel Personnel Personnel Payscale Payscale Payscale Type
Sub Area
Area Area Text Sub Area scale Area Text Type Text
Text
Area

Payscale
Cairn Payscale Type
1 1 Gurgaon 25 Area 25
India Gurgoan
Gurgoan

Payscale
Cairn Payscale Type
1 2 S`yanam 26 Area 26
India S’yanam
S’yanam

Payscale
Cairn Rajahmundr Payscale Type
1 3 25 Area 25
India y Gurgoan
Gurgoan

Payscale
Cairn Payscale Type
1 4 Kakinada 25 Area 25
India Gurgoan
Gurgoan

Payscale
Cairn Payscale Type
1 5 Barmer 25 Area 25
India Gurgoan
Gurgoan

Payscale
Cairn Payscale Type
1 6 Jodhpur 25 Area 25
India Gurgoan
Gurgoan

Payscale
Cairn Payscale Type
1 7 Patna 25 Area 25
India Gurgoan
Gurgoan

Cairn Payscale Payscale Type

1 8 Suvali 27 27
India Area Suvli Suvli

114
 Payscale
Cairn Payscale Type
1 9 Chennai 25 Area 25
India Gurgoan
Gurgoan

Payscale
Cairn Payscale Type
1 10 Mumbai 25 Area 25
India Gurgoan
Gurgoan

Cairn Payscale Payscale Type

1 11 Pipavav 27 27
India Area Suvli Suvli

Cairn Gandhinaga Payscale Payscale Type

1 12 27 27
India r Area Suvli Suvli

Determine Default for pay scale data:

Pay scale groups and Levels:

A pay scale group is a criterion used for grading job evaluation. A pay scale
group is divided up into several pay scale levels.

Each of these groups, share a set of characteristics, to which a standard set of

rules can be applied.

IMG Menu Path

115
SAP R/3 Role Menu Basic Pay
Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) 
Personnel Management  Personnel Administration 
IMG Menu
Payroll Data Basic Pay  Revise Pay Scale Groups and
Levels
Description and Configuration Values

Pay scale types and areas must be defined, before configuring this step.

The following Payscale groups and levels have been configured after analyzing
the requirements of location wise Payroll grades and levels of Cairn Energy’s
Payroll system.

Payscale Type: 25 (Payscale Type Gurgaon)

Payscale Area: 25 (Payscale Area Gurgaon)

Payscale Type: 26 (Payscale Type S' Yanam)

Payscale Area: 26 (Payscale Area S' Yanam)

116
 WAGE TYPE STRUCTURE
Wage types for Basic Pay Infotype (0008)
Earnings and deductions of an Employee are represented in SAP as Wagetypes.

In other words, Wagetypes are the payroll and personnel administration objects
used to differentiate between monetary or time units, which are used in different
ways to calculate Employees Remuneration.

The name range reserved for the customer Wagetypes has been described by SAP.
The entire customer Wagetypes should begin with a number.

Hence, all the Wagetypes configured for Cairn Energy’s Payroll System start with a
number.

Create / Copy wage types

We create the wage types for the Infotype Basic Pay (0008) by copying the
model wage types in the standard SAP system.

Only wage types for use in Infotype Basic Pay (0008) are proposed in this step.

IMG Menu Path

117
SAP R/3 Role Menu Wage Types
Transaction Code SPRO

Implementation Guide for R/3 Customizing (IMG) ->

Personnel Management Personnel Administration
IMG Menu
Payroll Data Basic pay  Wage Types  Create wage
type catalog
Description and Configuration Values

These copied wage types will be available in Infotype 0008 for further
processing. We can also modify the copies to suit our requirements.

The following are the Wage types defined as part of Basic Pay Infotype 0008, after
analyzing the requirements of Cairn Energy’s Payroll System.

Wage Type Code Wage Type long text Short Text

6CFE Consultancy Fee 6CFE

6BLC Barmer Loc Allow. 6BLC

6LOC Location allowance 6LOC

Check Wage Type Text

This section allows us to change the texts of the sample wage types that we have
copied in the above step.

IMG Menu Path

SAP R/3 Role Menu Wage Types

Transaction Code SPRO

Implementation Guide for R/3 Customizing (IMG) ->

Personnel Management Personnel Administration
IMG Menu
Payroll Data Basic pay  Wage Types  Check wage
type catalog  Check wage type text
Description and Configuration Values

Wage type short texts are used when printing out in Pay slip.

The following table shows the Long text and short text assigned to the wage
types.

Wage Type Code Wage Type long text Short Text

6CFE Consultancy Fee 6CFE

118
 Wage Type Code Wage Type long text Short Text

6BLC Barmer Loc Allow. 6BLC

6LOC Location allowance 6LOC

Check Entry Permissibility per Infotype

We can define the date on which wage types may be entered. For example the
"special bonus" wage type may only be entered up to 12/31/2010.

IMG Menu Path

SAP R/3 Role Menu Wage Types

Transaction Code SPRO

Implementation Guide for R/3 Customizing (IMG) 

Personnel Management Personnel Administration
IMG Menu
Payroll Data Basic pay  Wage Types  Check wage
type catalog Check enter permissibility per Infotype
Description and Configuration Values

To perform this step we have to have set up the wage type catalog and have
configured which wage types can be entered in which Infotype.

The details of the Wage type’s validity have been shown in the following table

Wage Type Code Wage Type long text Start date End date

6CFE Consultancy Fee 01.01.1900 31.12.9999

6BLC Barmer Loc Allow. 01.01.1900 31.12.9999

6LOC Location allowance 01.01.1900 31.12.9999

Employee Sub Group Grouping For Primary Wage Types

This section allows combining employee subgroups for primary wage types, i.e.
We group the employee subgroups already named to groups.

The Employee sub group grouping determines the applicability of wage types to
Employee group and subgroup assigned to an employee in Organizational
Assignment Infotype (0001).

IMG Menu Path

SAP R/3 Role Menu Wage Types

Transaction Code SPRO

119
 Implementation Guide for R/3 Customizing (IMG) 
Personnel Management  Personnel Administration
IMG Menu
 Payroll Data  Wage Types  Employee
Subgroups for Primary Wage Type

Description and Configuration Values

The following table represents the Grouping of Employee sub groups for Primary
wage types.

Name of Employees
Employee Name of employee
EE Group employee subgroup
subgroup subgroup
group grouping

1 Nationals 2 Direct Consultants 1

Wage Type Permissibility

IMG Menu Path

SAP R/3 Role Menu Check Wage Type Catalog

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) 
Personnel Management Personnel Administration
IMG Menu Payroll Data Basic Pay Wage Types  Check wage
type catelog  Define Wage Type Permissibility for each
PS and ESG
Description and Configuration Values

Before defining the wage type permissibility, we have to ensure the following

 Employee groups and subgroups must be defined.

 Personnel areas and sub areas must be defined.
 Employee groups, subgroups and personnel areas must be defined for
primary wage types.
 The wage type catalog must be defined.
Assign the appropriate indicators to the wage types, in the details section of
each Wage type.

The indicator must be "1", if we define this wage type as permissible. A blank
signifies that the wage type may not be entered.

120
 Wage Type Code Wage Type long text Start date End date

6CFE Consultancy Fee 01.01.1900 31.12.9999

6BLC Barmer Loc Allow. 01.01.1900 31.12.9999

6LOC Location allowance 01.01.1900 31.12.9999

Check Wage Type Characteristics

The Wagetype characteristics describe how the wagetype should behave while
entering in Infotypes.

IMG Menu Path

SAP R/3 Role Menu Wage Types

Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing (IMG) 
Personnel Management Personnel Administration
Payroll Data Basic Pay Wage Types  Check wage
type CatalogCheck wage type characteristics
Description and Configuration Values

Wagetype Characteristics determine the following based on the entries made:

 Whether the wagetype is a payment wagetype or deduction wagetype

 The Unit of the wage type
 Indirect valuation

121
Valuation of Wagetypes
After we configure the wagetype characteristics, for each wagetype, defined the
indirect valuation in the step "Check wage type characteristics".

122
Depending on which module we use for indirect valuation (Module name), we
need to define additional procedures to ensure that indirect valuation functions
correctly.
IMG Menu Path

SAP R/3 Role Menu Wage Types

Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing (IMG) 
Personnel Management Personnel Administration
Payroll Data Basic Pay Wage Types  Define
valuation of base wage types
Description and Configuration Values

The following table shows the details of valuation base

Valuated Base
Wage Type Wage Type
Module Wage No Start Date End Date Wage Percent
long text long text
Type Type

HRA Basic
PRZNT 1CLA 1 01.01.1900 31.12.9999 1BAS 40
Differential Salary

Deputation /
Basic
PRZNT 1DSA secondment 1 01.01.1900 31.12.9999 1BAS 20
Salary
Alw

Deputation /
House Rent
PRZNT 1DSA secondment 2 01.01.1900 31.12.9999 1HRA 20
Allowance
Alw

Deputation /
Conveyance
PRZNT 1DSA secondment 3 01.01.1900 31.12.9999 1CON 20
Allowance
Alw

Deputation / Car
PRZNT 1DSA secondment 4 01.01.1900 31.12.9999 1OAL (Allowance- 20
Alw PY)

Deputation /
Activity
PRZNT 1DSA secondment 5 01.01.1900 31.12.9999 1ACT 20
Allowance
Alw

Deputation /
Hard Duty
PRZNT 1DSA secondment 6 01.01.1900 31.12.9999 1HDA 20
Allw
Alw

Deputation /
HRA
PRZNT 1DSA secondment 7 01.01.1900 31.12.9999 1CLA 20
Differential
Alw

Deputation /
Special
PRZNT 1DSA secondment 8 01.01.1900 31.12.9999 1SPA 20
Allowance
Alw

House Rent Basic

PRZNT 1HRA 1 01.01.1900 31.12.9999 1BAS 40
Allowance Salary

123
 Valuated Base
Wage Type Wage Type
Module Wage No Start Date End Date Wage Percent
long text long text
Type Type

Special
Allw- Basic
PRZNT 1SAS 1 01.01.1900 31.12.9999 1BAS 15
Superanuati Salary
n

Temporary
Basic
PRZNT 1TAA Assignment 1 01.01.1900 31.12.9999 1BAS 20
Salary
Allw

Temporary
House Rent
PRZNT 1TAA Assignment 2 01.01.1900 31.12.9999 1HRA 20
Allowance
Allw

Temporary
Conveyance
PRZNT 1TAA Assignment 3 01.01.1900 31.12.9999 1CON 20
Allowance
Allw

Temporary Car
PRZNT 1TAA Assignment 4 01.01.1900 31.12.9999 1OAL (Allowance- 20
Allw PY)

Temporary
Activity
PRZNT 1TAA Assignment 5 01.01.1900 31.12.9999 1ACT 20
Allowance
Allw

Temporary
Hard Duty
PRZNT 1TAA Assignment 6 01.01.1900 31.12.9999 1HDA 20
Allw
Allw

Temporary
HRA
PRZNT 1TAA Assignment 7 01.01.1900 31.12.9999 1CLA 20
Differential
Allw

Temporary
Special
PRZNT 1TAA Assignment 8 01.01.1900 31.12.9999 1SPA 20
Allowance
Allw

Wagetypes for Infotype 0014

Create/Copy Wagetypes
In the Recurring Payments/Deductions infotype (0014), we can enter an amount
and/or a value and a unit of measurement for a wage type that is always paid or
deducted during payroll accounting.

Recurring payments/deductions are wage elements that are not paid / deducted in
every payroll period. In contrast to additional payments, recurring
payments/deductions are paid or deducted with a defined periodicity.

IMG Menu Path

124
SAP R/3 Role Menu Wage Types
Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) 
Personnel Management Personnel Administration
IMG Menu
Payroll Data Recurring payments and deductions
Wage Types Create wage type catalog
Description and Configuration Values

All deduction wage types and Recurring payments (Excluding Statutory)

designed for Cairn Energy is listed in the table.

Original
Wage Type long text
Wage Type Starting Date End Date

6CRD Credit Card Recovery 31.12.9999

01.01.1900
6DED Other Deductions - Cons 31.12.9999
01.01.1900
6LUN Lunch Recovery 31.12.9999
01.01.1900
6ORV Other Recovery 31.12.9999
01.01.1900
6PMR Perl Mobile Recovery 31.12.9999
01.01.1900
6REA Relocation Allowance 31.12.9999
01.01.1900
6TAR Trvl Adv Recovery - Cons 31.12.9999
01.01.1900
6TDS Tax deduction 31.12.9999
01.01.1900
Permissibility of Wage Types for Infotype 0014
We can define the date on which wage types may be entered in Infotype 0014. For
example the "Special bonus" wage type may only be entered up to 12/31/1995.

\IMG Menu Path

SAP R/3 Role Menu Check Wage type catalog

Transaction Code SPRO

Implementation Guide for R/3 Customizing (IMG) 
Personnel Management Personnel Administration
IMG Menu Payroll Data Recurring payments and deductions
Wage Types Check Wage type catalogCheck entry
permissibility per Infotype
Description and Configuration Values

125
To perform this step we have to have set up the wage type catalog and have
decided which wage types can be entered in which infotype.

The details of the Wagetypes validity have been shown in the following table

Wage Several
Wage Type long text Start Date End Date Once
Type Times

6CRD Credit Card Recovery 01.01.1900 31.12.9999 x

6DED Other Deductions - Cons 01.01.1900 31.12.9999 x

6LUN Lunch Recovery 01.01.1900 31.12.9999 X

6ORV Other Recovery 01.01.1900 31.12.9999 X

6PMR Perl Mobile Recovery 01.01.1900 31.12.9999 X

6REA Relocation Allowance 01.01.1900 31.12.9999 X

6TAR Trvl Adv Recovery - Cons 01.01.1900 31.12.9999 x

6TDS Tax deduction 01.01.1900 31.12.9999 X

IT 0014 Screen:

126
Wage types for Infotype 0015
Create / Copy Wage Types
By specifying a wage type in the Additional Payments (0015) infotype, we can
store an amount and/or a value and a unit of measurement that should be paid or
deducted in a certain period by Payroll.

Additional payments are wage elements which are not paid or deducted in every
payroll period in contrast to recurring payments and deductions which are paid or
deducted within a defined periodicity.

IMG Menu Path

SAP R/3 Role Menu Wage Types

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) 
Personnel Management Personnel Administration
IMG Menu
Payroll Data Additional Payments Wage Types
Create Wage type catalog
Description and Configuration Values

All the additional payment Wagetypes designed for Cairn Energy Payroll Process
are listed in following table.

127
 Original Wage
Wage Type long text Starting
Type End Date
Date
6AOI Other Allowances 01.01.1998 31.12.9999

6CLU Club Membership 01.01.1998 31.12.9999

6COM Compensatory Allow 01.01.1998 31.12.9999

6DIS Disturbance Allowance 01.01.1998 31.12.9999

6IMB Impact Bonus 01.01.1998 31.12.9999

6JOB Joining Bonus 01.01.1998 31.12.9999

6NTP Other-Non Taxable 01.01.1998 31.12.9999

6OER Other Earnings 01.01.1998 31.12.9999

6OMH Mobile Handset Allow 01.01.1998 31.12.9999

6PEI Performance Incentive 01.01.1998 31.12.9999

6REA Relocation Allowance 01.01.1998 31.12.9999

6REB Referral Bonus 01.01.1998 31.12.9999

6TPR Telephone reimbursement 01.01.1998 31.12.9999

Permissibility of Wage Types for Infotype 0015

IMG Menu Path

SAP R/3 Role Menu Check Wage Type Catalog

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) 
Personnel Management Personnel Administration
IMG Menu Payroll Data Additional Payments Wage Types
Check Wage type catalog Check entry permissibility for
Additional payments
Description and Configuration Values

To perform this step we have to set up the wage type catalog and have decided
which wage types can be entered in which infotype.

The details of the Wagetypes validity and permissibility of Wagetypes have been
shown in the following table:

128
Wage Several
Wage Type long text Start Date End Date Once
Type Times

6AOI Other Allowances 01.01.1900 31.12.9999 x

6CLU Club Membership 01.01.1998 31.12.9999 x

6COM Compensatory Allow 01.01.1998 31.12.9999 x

6DIS Disturbance Allowance 01.01.1900 31.12.9999 x

6IMB Impact Bonus 01.01.1998 31.12.9999 x

6JOB Joining Bonus 01.01.1900 31.12.9999 x

6NTP Other-Non Taxable 01.01.1998 31.12.9999 x

6OER Other Earnings 01.01.1900 31.12.9999 x

6OMH Mobile Handset Allow 01.01.1998 31.12.9999 x

6PEI Performance Incentive 01.01.1900 31.12.9999 x

6REA Relocation Allowance 01.01.1900 31.12.9999 x

6REB Referral Bonus 01.01.1998 31.12.9999 x

6TPR Telephone reimbursement 01.01.1998 31.12.9999 x

IT 0015-Screen:

Payscale groupings for allowances:

129
In this activity, we define pay scale groupings for allowances to differentiate
between employee groups. These groupings determine which benefits apply to a
particular group of employees.
To enable this:
1. Identify the different benefits each person is entitled too
2. Create groupings for each category, and assign the privileges
IMG Menu Path

SAP R/3 Role Menu Pay Scale Groupings

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG)
IMG Menu  Payroll: India Pay scale groupingsDefine pay scale
groupings for allowances
Description and Configuration Values

Pay scale grouping for allowances has been configured as shown in the following table,
after analysing the different set of requirements Region Wise / Location Wise & Grade
Wise.

Assign Pay Scale Groupings for Allowances

The defined Payscale groupings are to be assigned to the following parameters.
These parameters configuration is mandatory before configuring the Allowance
groupings.
 Pay Scale Area
 Pay Scale Type
 Pay Scale Group
 Pay Scale Level and
 Employee Sub Grouping for Collective Agreement Provision (ESG for CAP)
IMG Menu Path

130
SAP R/3 Role Menu Pay Scale Groupings
Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) 
IMG Menu Payroll Payroll: IndiaPay scale groupingsAssign pay
scale groupings for allowances
Description and Configuration Values

Payscale Payscale Payscale Payscale Allowance

ESG/CAP
Area Type Group Level Grouping

25 25 3 CS 01 CS01

25 25 3 CS 01 CS01

25 25 3 CS 01 CS01

Maintain Default Wage Types for Basic Pay

In this step, we can set up default wage types based on the internal company
structure for the Basic Pay Infotype (0008) using the feature Planned
remuneration specification (LGMST) defined in the next step.

When we create a record in Basic pay Infotype, certain wage types will be
defaulted based on the Payscale group and Level assigned to the particular
employee.

IMG Menu Path

SAP R/3 Role Menu Pay Scale Groupings

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) 
IMG Menu Payroll Payroll: India Reimbursement Allowances and
Perks Maintain Default Wagetypes for BasicPay
Description and Configuration Values

131
 Wage Wage Type
Seq.
Type Start Date End Date Mode Wage Type
No
Model Long Text

Consultancy
CS01 1 01.01.1900 31.12.9999 O 6CFE
Fee

Location
CS01 2 01.01.1900 31.12.9999 O 6LOC
allowance

Assign Wage type Model for Pay Scale Grouping For

Allowances
The “Wage Type Models” is assigned to each “Pay scale grouping for allowances”
that was created. The Wage Type Model will indicate which benefits would apply
to or what amounts will be deducted from a particular Pay Scale Grouping for
Allowance.
Wage type Models are a set of 'Wage Types' used by SAP. These Wage types can
be an amount or a deduction.
IMG Menu Path

SAP R/3 Role Menu Reimbursements, Allowances and Perks

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG)
Payroll  Payroll: India  Reimbursements,
IMG Menu
Allowances and Perks  Assign Wage Type Model for
Pay Scale Grouping for Allowances
Description and Configuration Values

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 types model.

Allowance Grouping Wage Type Model

CS01 20/CS01

132
Eligibility for RAPs
In this step, we set up the eligibility details to calculate the employee's
Reimbursement, Allowance or Perk (RAP).

We associate the eligibility criteria for a salary bracket to a Wage type and
specify the type of allowance. These Wage types are read by the Basic Pay
Infotype (0008) and processed as per the criteria applicable for the employee's
'Pay Scale Grouping for Allowances'.

IMG Menu Path

SAP R/3 Role Menu Reimbursements, Allowances and Perks

Transaction Code SPRO

Implementation Guide for R/3 Customizing (IMG) Payroll

IMG Menu Payroll: IndiaReimbursements, Allowances and Perks
Calculate Eligibility for RAPs

Description and Configuration Values

The following Allowance groupings contain the Wage types and the eligibility
which are configured in the Table V_T7INA9.

The configuration details can be accessed in the details section of each

Allowance grouping.

Allowance Grouping Start Date End Date

CS01 01.01.1900 31.12.9999

133
Maintain Salary Year and Period End Treatment of RAP
In this activity, we assign the salary year or calendar type and period end
treatment for a particular reimbursement.
The Tax Code field defined in T7INT9 and eligibility amounts for pay scale
grouping for allowances in T7INA9 determines the Tax exemption process, while
processing the LTA claim submitted by the employee.
Based on the Period end treatment configured here, the claim can be a carry
forward of balance or disbursement of balance which is paid and accordingly
taxed.

IMG Menu Path

SAP R/3 Role Menu Leave Travel Assistance

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) Payroll
 Payroll: India Reimbursements, Allowances and
IMG Menu
perks Claims  Maintain Salary Year and Period end
treatment
Description and Configuration Values

The following table shows the allowance grouping wise LTA details like Tax code,
carry forward and the calendar type assigned to LTA claim.

Allowance Pay& Tax

Tax code Cal Type C/F Period
Grouping Wagetype

000N SLTA C 1

000R SLTA C 1

001N SLTA C 1

001R SLTA C 1

1A1N SLTA C 1

1A1R SLTA C 1

134
COMPANY LOANS
We make the settings in this section that are required to enter data on employer
loans and to enable you to process loans.

Activate Calculation
In this step, we specify whether the data that has been stored in the Loans
Infotype (0045) is to be processed in Monthly Payroll. In the standard system, loan
processing is active, which means that loans are processed in Payroll.

IMG Menu Path

SAP R/3 Role Menu Company Loans

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) Payroll
IMG Menu
 Payroll: India Company Loans Activate calculation
Adjust Value Date
We have to adapt the value date for payroll to the payment date for the payroll
areas.

In an enterprise, payroll is performed for salaried employees at the start of the

month using payroll area. In this case, the repayment installment should reduce
the interest-yielding capital on the first of every month. Payments and special
payments made via payroll should also be made at the start of the month.

IMG Menu Path

SAP R/3 Role Menu Company Loans

Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing (IMG)
Payroll Payroll: IndiaCompany LoansAdjust Value
Date

Description and Configuration Values

The following table shows the details of Payroll and Loan adjustment value period;

Payroll Area Text

Payroll
Start Date End Date Value date
Area

Start of the
25 Payroll Area Cairn - Nationals 01.01.1900 31.12.9999
Period

135
Master Data
The settings for master data editing in the Loans infotype (0045) are maintained
in this section:

Maintain Loan Types

Employees in the enterprise have the option of taking out different kinds of Loans.

Loans can an be loans with constant repayment (installment loans) and loans
with a constant total made up of repayment and interest payment (annuity loans).

IMG Menu Path

SAP R/3 Role Menu Company Loans

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG)
IMG Menu Payroll Payroll: India Company Loans Masterdata
Maintain Loan Types
Description and Configuration Values

The following are the Loan Types configured for Cairn Energy’s Payroll system
after analyzing company loans requirements:

Loan Sub Type Name of the Loan

9000 Short term Loan > Rs.20,000

9001 Short term Loan < Rs.20,000

9002 Gurgaon Loan

The details section of each Loan Type allows us to configuration the following:

 The Debit Interest Rate

 The Reference Interest Rate (The difference between the company
interest rate and the market interest rate)
 Interest Advantage calculation
 Interest Calculation method
 Interest cycle

HOUSING

Define Accommodation Types

The code for Housing type is defined here and then associated with a taxability
code. The taxability code can be one which has been pre-defined.

136
The wage type corresponding to the Housing type is maintained in table
V_T7INA9 against each Allowance grouping.

The tax code assigned to Housing wagetype establishes the calculation process
of Housing exemption or Housing perquisite during monthly Payroll Run.
IMG Menu Path

SAP R/3 Role Menu Housing

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) Payroll 
IMG Menu Payroll: India  Housing  Define Accommodation Types

Description and Configuration Values

The configured Housing Types are available in Infotype HRA/CLA/COA (0581).

Following pre-configured codes for Housing Type have been configured.

HRA Type Tax Code Rent City Category Text

1 SHRA Mandatory Non-mandatory Rented Accom.

4 SHRA Hidden Hidden Own Accom.

5 SCLA Mandatory Hidden Company Leased

6 SCOA Non-mandatory Mandatory Company Owned

Based on the chosen code for housing type in Infotype 0581, wage type default
or substitution will happen in Infotype 0008.

CAR AND CONVEYANCE

Define Conveyance Types

We define the conveyance types required for an organization after analyzing the
requirements on Conveyance / Car eligibility, Allowance groupings and Tax
computations.

Based on the chosen code for Conveyance type in Info type Car and Conveyance
(0583), the wagetype placement or substitution will take place in Infotype
Basicpay (0008).
The tax codes for conveyance type will be associated with the exemptions and
perquisite calculations during monthly Payroll Run.
IMG Menu Path

137
SAP R/3 Role Menu Wage Types
Transaction Code SPRO

Implementation Guide for R/3 Customizing (IMG) Payroll

IMG Menu  Payroll: India  Car & Conveyance  Define
Conveyance types

Description and Configuration Values

Following pre-configured codes for Conveyance type have been provided to Cairn
Energy Payroll System. They are:

Car & Conveyance Type Text

6 Conveyance Allowance

7 Car Running Expenses(FI)

8 Other Allowance (PY)

Define Amounts & Numbers for Car Schemes

In this activity, we maintain details about the employee’s entitlement to a
company-owned car. For each allowance group, we define the total value of the
car and the number of cars, employees in the group is entitled to.
IMG Menu Path

SAP R/3 Role Menu Car and Conveyance

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) Payroll 
Payroll: India  Car & Conveyance  Define Amounts &
IMG Menu Numbers for Car Schemes

Description and Configuration Values

The following table shows the allowance grouping wise car scheme eligibility
details:
Allowance Car No. of Amount
Currency From To
Grouping Scheme Cars Limit

2A1N 7 2 150,000.00 INR 01.01.1999 31.12.9999

2A1N 8 2 150,000.00 INR 01.01.1999 31.12.9999

2A1R 7 2 160,000.00 INR 01.01.1999 31.12.9999

2A1R 8 2 160,000.00 INR 01.01.1999 31.12.9999

2A2N 7 2 160,000.00 INR 01.01.1999 31.12.9999

138
Allowance Car No. of Amount
Currency From To
Grouping Scheme Cars Limit

2A2N 8 2 160,000.00 INR 01.01.1999 31.12.9999

2A2R 7 2 150,000.00 INR 01.01.1999 31.12.9999

2A2R 8 2 150,000.00 INR 01.01.1999 31.12.9999

2A3N 7 2 160,000.00 INR 01.01.1999 31.12.9999

2A3N 8 2 160,000.00 INR 01.01.1999 31.12.9999

2A3R 7 2 150,000.00 INR 01.01.1999 31.12.9999

2A3R 8 2 150,000.00 INR 01.01.1999 31.12.9999

2B1N 7 2 150,000.00 INR 01.01.1999 31.12.9999

2B1N 8 2 150,000.00 INR 01.01.1999 31.12.9999

2B1R 7 2 160,000.00 INR 01.01.1999 31.12.9999

2B1R 8 2 160,000.00 INR 01.01.1999 31.12.9999

2B2N 7 2 150,000.00 INR 01.01.1999 31.12.9999

2B2N 8 2 150,000.00 INR 01.01.1999 31.12.9999

2B2R 7 2 160,000.00 INR 01.01.1999 31.12.9999

2B2R 8 2 160,000.00 INR 01.01.1999 31.12.9999

2B3N 7 2 160,000.00 INR 01.01.1999 31.12.9999

2B3N 8 2 160,000.00 INR 01.01.1999 31.12.9999

2B3R 7 2 160,000.00 INR 01.01.1999 31.12.9999

2B3R 8 2 160,000.00 INR 01.01.1999 31.12.9999

2B4N 7 2 160,000.00 INR 01.01.1999 31.12.9999

2B4N 8 2 160,000.00 INR 01.01.1999 31.12.9999

2B4R 7 2 160,000.00 INR 01.01.1999 31.12.9999

2B4R 8 2 160,000.00 INR 01.01.1999 31.12.9999

2B5N 7 2 160,000.00 INR 01.01.1999 31.12.9999

2B5N 8 2 160,000.00 INR 01.01.1999 31.12.9999

2B5R 7 2 160,000.00 INR 01.01.1999 31.12.9999

139
Allowance Car No. of Amount
Currency From To
Grouping Scheme Cars Limit

2B5R 8 2 160,000.00 INR 01.01.1999 31.12.9999

2B6N 7 2 160,000.00 INR 01.01.1999 31.12.9999

2B6N 8 2 160,000.00 INR 01.01.1999 31.12.9999

2B6R 7 2 160,000.00 INR 01.01.1999 31.12.9999

2B6R 8 2 160,000.00 INR 01.01.1999 31.12.9999

2C1N 7 2 150,000.00 INR 01.01.1999 31.12.9999

2C1N 8 2 150,000.00 INR 01.01.1999 31.12.9999

2C1R 7 2 160,000.00 INR 01.01.1999 31.12.9999

2C1R 8 2 160,000.00 INR 01.01.1999 31.12.9999

2C2N 7 2 150,000.00 INR 01.01.1999 31.12.9999

2C2N 8 2 150,000.00 INR 01.01.1999 31.12.9999

2C2R 7 2 160,000.00 INR 01.01.1999 31.12.9999

2C2R 8 2 160,000.00 INR 01.01.1999 31.12.9999

2C3N 7 2 160,000.00 INR 01.01.1999 31.12.9999

2C3N 8 2 160,000.00 INR 01.01.1999 31.12.9999

2C3R 7 2 150,000.00 INR 01.01.1999 31.12.9999

2C3R 8 2 150,000.00 INR 01.01.1999 31.12.9999

2C4N 7 2 160,000.00 INR 01.01.1999 31.12.9999

2C4N 8 2 150,000.00 INR 01.01.1999 31.12.9999

2C4R 7 2 150,000.00 INR 01.01.1999 31.12.9999

2C4R 8 2 160,000.00 INR 01.01.1999 31.12.9999

2C5N 7 2 160,000.00 INR 01.01.1999 31.12.9999

2C5N 8 2 150,000.00 INR 01.01.1999 31.12.9999

2C5R 7 2 150,000.00 INR 01.01.1999 31.12.9999

2C5R 8 2 160,000.00 INR 01.01.1999 31.12.9999

2C6N 7 2 160,000.00 INR 01.01.1999 31.12.9999

2C6N 8 2 150,000.00 INR 01.01.1999 31.12.9999

140
Allowance Car No. of Amount
Currency From To
Grouping Scheme Cars Limit

2C6R 7 2 150,000.00 INR 01.01.1999 31.12.9999

2C6R 8 2 160,000.00 INR 01.01.1999 31.12.9999

2C7N 7 2 160,000.00 INR 01.01.1999 31.12.9999

2C7N 8 2 150,000.00 INR 01.01.1999 31.12.9999

2C7R 7 2 150,000.00 INR 01.01.1999 31.12.9999

2C7R 8 2 160,000.00 INR 01.01.1999 31.12.9999

3A1N 7 2 160,000.00 INR 01.01.1999 31.12.9999

3A1N 8 2 160,000.00 INR 01.01.1999 31.12.9999

3A1R 7 2 150,000.00 INR 01.01.1999 31.12.9999

3A1R 8 2 150,000.00 INR 01.01.1999 31.12.9999

3B1N 7 2 160,000.00 INR 01.01.1999 31.12.9999

3B1N 8 2 160,000.00 INR 01.01.1999 31.12.9999

3B1R 7 2 150,000.00 INR 01.01.1999 31.12.9999

3B1R 8 2 150,000.00 INR 01.01.1999 31.12.9999

3C1N 7 2 160,000.00 INR 01.01.1999 31.12.9999

3C1N 8 2 160,000.00 INR 01.01.1999 31.12.9999

3C1R 7 2 150,000.00 INR 01.01.1999 31.12.9999

3C1R 8 2 150,000.00 INR 01.01.1999 31.12.9999

Eligibility Criteria for Conveyance Allowance

We assign Wage type and conveyance type that will be used to calculate the
eligibility amounts for Conveyance Allowance.

These inputs are used to calculate the eligible amounts payable to employees
who belong to the respective allowance grouping.
IMG Menu Path

SAP R/3 Role Menu Car and Conveyance

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) Payroll 
Payroll: India Car & Conveyance  Assign Eligibility
IMG Menu
Criteria for Conveyance Allowance

141
Description and Configuration Values

The eligibility amounts for Conveyance Allowance have been configured for each
Allowance Grouping as shown in the following table.

Allowance Car & Conveyance

Wage Type From To
Grouping Type

000N 6 1CON 01.01.1900 31.12.9999

000R 6 1CON 01.01.1900 31.12.9999

001N 6 1CON 01.01.1900 31.12.9999

001R 6 1CON 01.01.1900 31.12.9999

1A1N 6 1CON 01.01.1900 31.12.9999

1A1R 6 1CON 01.01.1900 31.12.9999

1A2N 6 1CON 01.01.1900 31.12.9999

1A2R 6 1CON 01.01.1900 31.12.9999

1A3N 6 1CON 01.01.1900 31.12.9999

1A3R 6 1CON 01.01.1900 31.12.9999

1A4N 6 1CON 01.01.1900 31.12.9999

1A4R 6 1CON 01.01.1900 31.12.9999

1A5N 6 1CON 01.01.1900 31.12.9999

1A5R 6 1CON 01.01.1900 31.12.9999

1A6N 6 1CON 01.01.1900 31.12.9999

1A6R 6 1CON 01.01.1900 31.12.9999

1A7N 6 1CON 01.01.1900 31.12.9999

1A7R 6 1CON 01.01.1900 31.12.9999

1A8N 6 1CON 01.01.1900 31.12.9999

1A8R 6 1CON 01.01.1900 31.12.9999

1B1N 6 1CON 01.01.1900 31.12.9999

1B1R 6 1CON 01.01.1900 31.12.9999

1B2N 6 1CON 01.01.1900 31.12.9999

1B2R 6 1CON 01.01.1900 31.12.9999

1B3N 6 1CON 01.01.1900 31.12.9999

142
Allowance Car & Conveyance
Wage Type From To
Grouping Type

1B3R 6 1CON 01.01.1900 31.12.9999

1B4N 6 1CON 01.01.1900 31.12.9999

1B4R 6 1CON 01.01.1900 31.12.9999

1B5N 6 1CON 01.01.1900 31.12.9999

1B5R 6 1CON 01.01.1900 31.12.9999

1B6N 6 1CON 01.01.1900 31.12.9999

1B6R 6 1CON 01.01.1900 31.12.9999

1B7N 6 1CON 01.01.1900 31.12.9999

1B7R 6 1CON 01.01.1900 31.12.9999

1B8N 6 1CON 01.01.1900 31.12.9999

1B8R 6 1CON 01.01.1900 31.12.9999

1B9N 6 1CON 01.01.1900 31.12.9999

1B9R 6 1CON 01.01.1900 31.12.9999

1C1N 6 1CON 01.01.1900 31.12.9999

1C1R 6 1CON 01.01.1900 31.12.9999

1C2N 6 1CON 01.01.1900 31.12.9999

1C2R 6 1CON 01.01.1900 31.12.9999

1C3N 6 1CON 01.01.1900 31.12.9999

1C3R 6 1CON 01.01.1900 31.12.9999

1C4N 6 1CON 01.01.1900 31.12.9999

1C4R 6 1CON 01.01.1900 31.12.9999

2A1N 7 2OAL 01.01.1900 31.12.9999

2A1N 8 1OAL 01.01.1900 31.12.9999

2A1R 7 2OAL 01.01.1900 31.12.9999

2A1R 8 1OAL 01.01.1900 31.12.9999

2A2N 7 2OAL 01.01.1900 31.12.9999

143
Allowance Car & Conveyance
Wage Type From To
Grouping Type

2A2N 8 1OAL 01.01.1900 31.12.9999

2A2R 7 2OAL 01.01.1900 31.12.9999

2A2R 8 1OAL 01.01.1900 31.12.9999

2A3N 7 2OAL 01.01.1900 31.12.9999

2A3N 8 1OAL 01.01.1900 31.12.9999

2A3R 7 2OAL 01.01.1900 31.12.9999

2A3R 8 1OAL 01.01.1900 31.12.9999

2B1N 7 2OAL 01.01.1900 31.12.9999

2B1N 8 1OAL 01.01.1900 31.12.9999

2B1R 7 2OAL 01.01.1900 31.12.9999

2B1R 8 1OAL 01.01.1900 31.12.9999

2B2N 7 2OAL 01.01.1900 31.12.9999

2B2N 8 1OAL 01.01.1900 31.12.9999

2B2R 7 2OAL 01.01.1900 31.12.9999

2B2R 8 1OAL 01.01.1900 31.12.9999

2B3N 7 2OAL 01.01.1900 31.12.9999

2B3N 8 1OAL 01.01.1900 31.12.9999

2B3R 7 2OAL 01.01.1900 31.12.9999

2B3R 8 1OAL 01.01.1900 31.12.9999

2B4N 7 2OAL 01.01.1900 31.12.9999

2B4N 8 1OAL 01.01.1900 31.12.9999

2B4R 7 2OAL 01.01.1900 31.12.9999

2B4R 8 1OAL 01.01.1900 31.12.9999

2B5N 7 2OAL 01.01.1900 31.12.9999

2B5N 8 1OAL 01.01.1900 31.12.9999

2B5R 7 2OAL 01.01.1900 31.12.9999

2B5R 8 1OAL 01.01.1900 31.12.9999

144
Allowance Car & Conveyance
Wage Type From To
Grouping Type

2B6N 7 2OAL 01.01.1900 31.12.9999

2B6N 8 1OAL 01.01.1900 31.12.9999

2B6R 7 2OAL 01.01.1900 31.12.9999

2B6R 8 1OAL 01.01.1900 31.12.9999

2C1N 7 2OAL 01.01.1900 31.12.9999

2C1N 8 1OAL 01.01.1900 31.12.9999

2C1R 7 2OAL 01.01.1900 31.12.9999

2C1R 8 1OAL 01.01.1900 31.12.9999

2C2N 7 2OAL 01.01.1900 31.12.9999

2C2N 8 1OAL 01.01.1900 31.12.9999

2C2R 7 2OAL 01.01.1900 31.12.9999

2C2R 8 1OAL 01.01.1900 31.12.9999

2C3N 7 2OAL 01.01.1900 31.12.9999

2C3N 8 1OAL 01.01.1900 31.12.9999

2C3R 7 2OAL 01.01.1900 31.12.9999

2C3R 8 1OAL 01.01.1900 31.12.9999

2C4N 7 2OAL 01.01.1900 31.12.9999

2C4N 8 1OAL 01.01.1900 31.12.9999

2C4R 7 2OAL 01.01.1900 31.12.9999

2C4R 8 1OAL 01.01.1900 31.12.9999

2C5N 7 2OAL 01.01.1900 31.12.9999

2C5N 8 1OAL 01.01.1900 31.12.9999

2C5R 7 2OAL 01.01.1900 31.12.9999

2C5R 8 1OAL 01.01.1900 31.12.9999

2C6N 7 2OAL 01.01.1900 31.12.9999

2C6N 8 1OAL 01.01.1900 31.12.9999

2C6R 7 2OAL 01.01.1900 31.12.9999

145
 Allowance Car & Conveyance
Wage Type From To
Grouping Type

2C6R 8 1OAL 01.01.1900 31.12.9999

2C7N 7 2OAL 01.01.1900 31.12.9999

2C7N 8 1OAL 01.01.1900 31.12.9999

2C7R 7 2OAL 01.01.1900 31.12.9999

2C7R 8 1OAL 01.01.1900 31.12.9999

3A1N 7 2OAL 01.01.1900 31.12.9999

3A1N 8 1OAL 01.01.1900 31.12.9999

3A1R 7 2OAL 01.01.1900 31.12.9999

3A1R 8 1OAL 01.01.1900 31.12.9999

3B1N 7 2OAL 01.01.1900 31.12.9999

3B1N 8 1OAL 01.01.1900 31.12.9999

3B1R 7 2OAL 01.01.1900 31.12.9999

3B1R 8 1OAL 01.01.1900 31.12.9999

3C1N 7 2OAL 01.01.1900 31.12.9999

3C1N 8 1OAL 01.01.1900 31.12.9999

3C1R 7 2OAL 01.01.1900 31.12.9999

3C1R 8 1OAL 01.01.1900 31.12.9999

PROFESSIONAL TAX
Define Professional Tax Grouping Details
The personnel area and sub area groupings for Professional Tax (PTax), which
are used to group all personnel areas, and sub areas that contribute to the same
professional tax circle (or) Region.
IMG Menu Path

SAP R/3 Role Menu Professional Tax

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG)
IMG Menu Payroll Payroll: IndiaProfessional TaxDefine
Professional Tax Grouping Details
The following table provides the details of Professional Tax Regions and the
circles configured for Cairn Energy.

146
 Regn.
Office Ptax
PT PT Grp Regi Zone
Division Circle Circle End date Start date
Grp. destination on no. Cert.
name no.
No.

EAST
Vijay Wada RGCRT
1 1 VIJAYAW 35903 31.12.9999 01.01.1800
Region 0412
ADA

CHENNA
Chennai
RGCRT I
7 Corporatio 22 ZN65 D002 79894 31.12.9999 01.01.1800
0709 CENTRA
n
L

Assign PTax Groupings for PA and PSA

Professional tax groupings created in the previous step are assigned to personnel
areas and Subareas.

IMG Menu Path

SAP R/3 Role Menu Professional Tax

Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing (IMG) Payroll
 Payroll: India  Professional Tax  Assign PTax
Groupings for Personnel Areas and Subareas
Description and Configuration Values

The Personnel Area and Personnel Sub Area are grouped as mentioned in the
following table with respect to Professional Tax:

Personnel Personnel Area Personnel Personnel PS grp. for

Area Text Subarea Subarea Text Ptax

1 Cairn India 1 Gurgaon 0

1 Cairn India 2 S`yanam 1

1 Cairn India 3 Rajahmundry 1

1 Cairn India 4 Kakinada 1

1 Cairn India 5 Barmer 0

1 Cairn India 6 Jodhpur 0

1 Cairn India 7 Patna 0

1 Cairn India 8 Suvali 2

1 Cairn India 9 Chennai 7

3 Cairn Bangladesh 1 Cairn Bangladesh 0

147
Assign Amounts for Professional Deduction
Professional Tax (PTax) rate is assigned to a slab code. 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, for example Gujarat, we must first
define the slab code and then assign serial numbers, maximum limits and the
rates.
IMG Menu Path

SAP R/3 Role Menu Professional Tax

Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing (IMG) Payroll
 Payroll: India Professional Tax  Assign Amounts
for Professional Tax Deduction
Description and Configuration Values
The following table shows the details of Professional tax slab codes and the
deductible amounts for each slab.

Professional
Slab Code Sr. No Range End Currency
Tax amount

AP01 1 1,499.99 INR

AP01 2 1,999.99 16.00 INR

AP01 3 2,999.99 25.00 INR

AP01 4 3,999.99 35.00 INR

AP01 5 4,999.99 45.00 INR

AP01 6 5,999.99 60.00 INR

AP01 7 9,999.99 80.00 INR

AP01 8 14,999.99 100.00 INR

AP01 9 19,999.99 150.00 INR

AP01 10 9,999,999.99 200.00 INR

TN01 1 21,000.99 INR

TN01 2 30,000.99 75.00 INR

TN01 3 45,000.99 188.00 INR

TN01 4 60,000.99 390.00 INR

TN01 5 75,000.99 585.00 INR

148
 TN01 6 9,999,999.99 810.00 INR

INR

Method and Form Layout for PTax Groupings

In this activity, we assign the calculation method used for a slab code in a region
and specify the layout of the form to be submitted, to the statutory Authorities.

The form layout and the method used for calculation, refer to a time dependent
entry in the HR Subroutines table.

Professional Tax deduction amount will be arrived in the Payroll Run, based on
the employee assignment to Personnel Subarea and the slab code / Region code
assigned to the Personnel Subarea.

IMG Menu Path

SAP R/3 Role Menu Professional Tax

Transaction Code SPRO
IMG Menu Implementation Guide for R/3 Customizing (IMG)
Payroll Payroll: India Professional Tax Maintain
Method and Form Layout for Professional Tax Groupings

Description and Configuration Values

The following table shows the details of Professional “Tax slab codes”
assigned to the regions Andhra Pradesh and Tamil Nadu.

Type of
Slab Form Basis
Region Method Carry Start date End date
code Layout Type
Forward

Gross
AP0 40PTXCA 40PTXFA Due 31.12.999
01 Carry 01.01.1998
1 P P Basis 9
forward

Gross
TN0 40PTXCT 40PTXFT Due 31.12.999
22 Carry 01.01.1998
1 N N Basis 9
forward

INCOME TAX

Basic Settings
Personnel Area and Subarea Groupings for Income Tax
We have to create the personnel area and sub area groupings for tax, to group
employees, who belong to the same tax office circle.

149
In the next step we assign the groupings to the relevant personnel areas and sub
areas.

IMG Menu Path

SAP R/3 Role Menu Professional Tax

Transaction Code SPRO

Implementation Guide for R/3 Customizing (IMG)
IMG Menu Payroll Payroll: IndiaTax Basic Settings Define
Personnel Area and Subarea Groupings
Description and Configuration Values

The following table shows the details of Personnel Subarea groupings for Income
Tax.

Tax Group TDS circle Ward No Payee Key

1 ACIT TDS CIRCLE I SALARY WARD 3(1) INPAY01

2 ACIT TDS CIRCLE I SALARY WARD 3(1) INPAY01

Assign Tax Groupings for Personnel Areas and Sub areas

In this step we assign the groupings defined in the above step to the relevant
personnel areas and sub areas

IMG Menu Path

SAP R/3 Role Menu Basic Settings

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG)
IMG Menu Payroll Payroll: India Tax Basic settings Assign
Tax Groupings for Personnel Areas and Subareas
Description and Configuration Values

The professional tax groupings created in the previous step are assigned to
personnel areas and sub areas.

Personnel Personnel Area Personnel Personnel Subarea

PS grp Tax
Area Text Subarea Text

1 Cairn India 1 Gurgaon 1

1 Cairn India 2 S`yanam 1

1 Cairn India 3 Rajahmundry 1

1 Cairn India 4 Kakinada 1

150
 1 Cairn India 5 Barmer 1

1 Cairn India 6 Jodhpur 1

1 Cairn India 7 Patna 1

1 Cairn India 8 Suvali 1

1 Cairn India 9 Chennai 1

3 Cairn Bangladesh 1 Cairn Bangladesh 1

Maintain Feature to Return Employer Income Tax Related Data

In this feature, we set up the criteria to return the following information about the
employer based on the company code:

 Employer Classification Code

 Employer Permanent Account Number (PAN)
 Employer Tax Account Number (TAN)
 Employer GIR Number
These values are required for the purpose of reporting.

This feature returns a table with the above information as records.

IMG Menu Path

SAP R/3 Role Menu Basic Settings

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG)
IMG Menu Payroll Payroll: India Tax Basic settings Maintain
Feature to Return Employer Income Tax Related Data

Third party Deductions

Details of Section 80 and Section 80 C
Contributions or investments made under Section 80 and Section 80 C are
considered as deductions from Gross Total Income (GTI) as per the limits
specified by Central Government. By assigning a wage type, we ensure that the
annual value of the wage type along with the entries made in Section 80
Deductions, Infotype (0585) and Section 80 C Deductions, Infotype (0586)
becomes eligible for deduction from GTI for the specified sub-section / division
combination.

More than one wage type can be associated with same sub-section / division
combination using the sequence field.
IMG Menu Path

151
SAP R/3 Role Menu Third Party Deductions
Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG)
IMG Menu Payroll Payroll: India Tax Third Party Deductions
Configure Wage types for Section 80 and Section 80 C
Description and Configuration Values

The following are the table entries. These are SAP Standard entries.

Sub Wage
Division Sequence Division Description
section Type

1 1 Contribution to Certain Pension Funds

2 1 Medical Insr Premium (Non-Senior Ctz)

2 1 1 Medical Insr Premium (Non-Senior Ctz)

2 2 Medical Insr Premium (Senior Citizen)

Deduction for dependent with

3 1
disability

4 1

5 1 Medical Treatment

5 2 Medical Trtmnt for Senr Citizen

Repayment of Interest on Loan for

6 1
Higher Education

7 1 Donation to CRY

7 2 Donation to PM's Relief Fund

8 1 Deduction in respect of rent paid

9 1 Donation for Scientific/Rural Devlpmnt

Interest on Certain
10 1
Securities/Dividends

Interest on Certain
10 2 Securities/Dividends (incl Govt
Securities)

12 1 Prof Income from Foreign Sources

Remuntn recvd for services rendrd

13 1
abrd

152
 14 1 Deduction for self disability

Details of Section 80C

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.

More than one wage type can be associated with the same investment type by
using the sequence number field.

IMG Menu Path

SAP R/3 Role Menu Third Party Deductions

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) 
IMG Menu Payroll: India  Tax  Third Party Deductions 
Configure Wage types for Section 88
Description and Configuration Values

Wage
Investment Investment Text Sequence
Type

1 Payment towards Life Insurance Policy

2 Contribution to Superannuation Fund

Subscription to notified Central

3
Government security (NSS)

4 Contribution to ULIP

Subscription to approved equity shares

5
or debentures (Infrastructure)

Subscription to approved mutual fund

6
(Infrastructure)

7 Contribution to Public Provident Fund

Contribution to Recognised Provident

8
Fund

Deposit under Post Office Savings

9 Bank(Cumulative Time Deposits)
Rule1959

Subscr to notified Central Govmt

11
Savings certificate (NSC VIII issue)

153
 Wage
Investment Investment Text Sequence
Type

Contribution to notified unit linked

12
insurance plan of LIC Mutual Fund

Contribution to provident fund as per PF

13
Act,1925

14 Repayment of Housing loan

16 Interest on NSC VIII issue

Contribution to notified annuity plan of

17
LIC

18 Subscription to notified mutual fund

19 Subscription to notified pension fund

Subscription to notified deposit scheme

20
of the National Housing Bank

Subsr to dpst schm of a pblc sectr com

21 or any constituted athry in house
constrc

Contract for a deferred annuity on life

22
of specified persons

Deduction from salary for a deferred

23
annuity

Tax liability on Reimbursements, Allowances and Perks

Define Tax Codes
In this activity we define Tax Codes and describe them briefly.
IMG Menu Path

SAP R/3 Role Menu Tax Liability on Reimbursements, Allowances and Perks
Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG)
Payroll Payroll: India Tax Tax Liability on
IMG Menu
Reimbursements, Allowances and Perks Define Tax
Codes
Description and Configuration Values
The following tax codes are in the system:

Tax Code Tax Code description

SAGA Taxation as per gratuity act

154
 Income Tax Deduction at Source for
SBON
Bonus

SCAR Car maintenance Reimbursement 1

SCEA Children Education Allowance

SCLA Company Leased Accomodation

SCNE Conveyance Act Expenditure

SCNO Conveyance Act Expenditure OTHERS

SCNV Conveyance Allowance

SCOA Company Owned Accomodation

Assign tax Code limits to Wage Types

We assign the tax code limits, wage types and other criteria to a tax code. This
value is taken into account when calculating the employees tax liabilities on
certain benefits.

IMG Menu Path

SAP R/3 Role Menu Tax Liability on Reimbursements, Allowances and Perks
Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) Payroll
 Payroll: India  Tax  Tax Liability on
IMG Menu
Reimbursements, Allowances and Perks  Assign Tax
Code Limits to Wage Types
Description and Configuration Values

In this activity, we assign the tax code limits, wage types and other criteria to a
tax code as shown in the following table. This value is taken into account when
calculating the employees tax liabilities on certain benefits.

Example

Similarly, employees who claim exemption on Medical allowance (Tax code SMED)
benefit from tax exemption of up to a maximum of Rs.15, 000.

These tax limits or rates and other details are used for verification during a
payroll run, to calculate Tax Exemptions.

Wage Exemption Tax

Tax type Frequency Currency Start To
Type Limit Code

Tax
exemption
1CLA 0 SCLA INR 01.01.1999 31.12.9999
is Rule
Based

155
 Tax
Limit for Tax
exemption
1CON Exemption is 800 SCNV INR 01.01.1999 31.12.9999
is Limit
Monthly
Based

Tax
exemption
1HRA 0 SHRA INR 01.01.1999 31.12.9999
is Rule
Based

Tax
Limit for Tax
exemption
1LEN Exemption is 240,000.00 SLEA INR 01.01.1999 31.12.9999
is Limit
Annual
Based

Tax
exemption
1LTA 0 SLTA INR 01.01.1999 31.12.9999
is Rule
Based

Tax
Limit for Tax
exemption
1OAL Exemption is 0 SEXM INR 01.01.1999 31.12.9999
is Limit
Monthly
Based

Tax
Limit for Tax
exemption
2OAL Exemption is 0 SEXM INR 01.01.1999 31.12.9999
is Limit
Monthly
Based

Tax
Limit for Tax
exemption
3MER Exemption is 0 SLEA INR 01.01.1999 31.12.9999
is Limit
Annual
Based

Tax
Limit for Tax
exemption
3TPR Exemption is 0 SLEA INR 01.01.1999 31.12.9999
is Limit
Annual
Based

Tax
Limit for Tax
exemption
4OAL Exemption is 0 SLEA INR 01.01.1999 31.12.9999
is Limit
Annual
Based

PAYROLL SCHEMA AND PERSONNEL

CALCULATION RULES

Payroll Schema
The payroll schema contains calculation rules to be used by the payroll driver
during payroll. SAP has developed country-specific schemas.
A schema consists of Personnel Calculation Rules, Operations and Functions. A
schema performs the following:
 Imports required Infotypes

156
  Updates the databases
 Gross calculation of pay
 Processes basic data and time data
 Reads payroll account of the last period accounted
 Processes time data and calculates the individual gross values
 Performs factoring
 Net calculation of pay

IMG Menu Path or Transaction code

SAP R/3 Role Menu Payroll Schema and Personnel Calculation Rules
Transaction Code PE01

Description and Configuration Values

The following table shows the modified schema for Cairn Energy Payroll system:

Schema Text of the Schema

ZN00 Payroll Schema_Cairn Energy_ Nationals

New requirement – W.e.f. 01st Apr, 09

Requirement:
In accordance with the provisions of Income Tax under u/s 10(14) read with rule
2BB, location allowance of an employee working at Barmer site is eligible for
income tax exemption @ Rs. 1000 per month as “Compensatory Modified Field
Area Allowance”.
Solution:
We planned to use INCTX function for this exemption.
We have created one wage type 5LOC (Location allowance) from M200.
Eligibility is getting varied from grade to grade for this allowance.
(ExampleRs.5000 to 10000 per month). As per the requirement, we have to
configure this wage type for exemption of Rs.1000 per month u/s 10.

In V_T7INA9, we maintained this wage type and mentioned that it is Allowance.

In V_T7INT9, we mapped the Standard Tax code SLOC to the wage type 1LOC
and mentioned the frequency as Monthly & Exemption amount as Rs. 1000.

In T591A, we have copied the standard subtype SEXM and named the subtype
as SLOC – Generic Tax exemption and in the T7INT7, the tax code as SLOC –
Generic Tax exemption.

5LOC Wage type is maintained in the Infotype 0008 & Exemption for the month
April 09 in Infotype 0582 as Rs. 1100 against the subtype SLOC.

We copied annual & monthly customer specific exemption wage types MCAX &
MCMX and created as 1LAX & 1LMX.

In Schema, it is maintained as INCTX SLOX 1LAX A 1LMX

157
Since we maintained the maximum limit as Rs.1000 in V_T7INT9, System
considers only Rs. 1000 but In 0582 Infotype, exemption amount entered for the
month of April 09 is Rs.1100.

In May 09, we entered Rs. 300, so the system automatically projects the value
and display the annual exemption as Rs.4300.
Schema – ZN00

Schema ZN00 is used for Cairn energy nation employees Payroll run.

Activate INCTX

158
Copy IN71 & Create ZN71

Modifications in ZN71 as per our requirements :

159
Copy wage type MCAX & MCMX and create wage type 1LAX & 1LMX

160
In Table : V_T7INA9

In Table : V_T7INT9

161
In Table : V_T7INT7

In Table : V_T591A

In Infotype 0582 : Subtype SLOC is maintained

162
1LOC Wage type maintained Infotype 0008

Result : Exemption is displayed u/s 10

163
Tax Calculation :

Income 5120000

Std. dedn. 150000

4970000

10% 150000 15000

4820000

20% 200000 40000

4620000

30% 1386000

10% Edu
TDS Sur Cess Tot Tax

1441000 144100 1585100 47553 1632653

Income 5120000

u/s 10
Exemp 12000

164
 5108000

Std. dedn. 150000

4958000

10% 150000 15000

4808000

20% 200000 40000

4608000

30% 1382400

10% Edu
TDS Sur Cess Tot Tax

1437400 143740 1581140 47434.2 1628574

Last Month Exemption –

April 2009 1000

Current Month
Exemption – May 2009 300

Projection ( Including
Current Month ) 11

Balance month
including Current month 3300

165
Total Exemption 4300

Tax Calculation :

Income 5120000

u/s 10
Exemp 4300

5115700

Std. dedn. 150000

4965700

10% 150000 15000

4815700

20% 200000 40000

4615700

30% 1384710

10% Edu
TDS Sur Cess Tot Tax

166
 1439710 143971 1583681 47510.43 1631191

Personnel calculation Rules

Personnel Calculation Rule is an instruction to execute defined tasks in Time
Management and Payroll. Personnel calculation rules consist of one or more
operations. They have a decision tree structure.

A personnel calculation rule may contain one or more sub areas.

A personnel calculation rule is a type of work instruction that checks the existing
conditions and executes individual actions.

The country-specific payroll module by SAP takes the statutory and

administrative regulations of a country into account and designs the Payroll
schemas and Personnel calculation rules.

IMG Menu Path or Transaction code

SAP R/3 Role Menu Payroll Schema and Personnel Calculation Rules

Transaction Code PE02

Description and Configuration Values

Since each country payroll has a modular structure, we can use the Customizing
functions/Rules to quickly modify the payroll procedure to meet the particular
requirements of an enterprise.

On this way, we have designed the following customer specific Personnel

Calculation rules to suit the requirements of the Payroll module of Cairn Energy:

Rule Text of the Personnel Calculation Rule

ZEDL HR-IN: Employer EDLI contrib. as 0.005% (0.01) and multiply by 1lakh
ZERC HR-IN: Employer PF/Pen contributions 1lakh division
ZNRT HR-IN: Cumulate Payments for TDS in Regular Run
ZNVT HR-IN: Voluntary tax deduction
ZPER HR-IN: Adding the Monthly Perk to Annual Perk
ZRET HR-IN: PF and PT Retro Carry forward in case of Arrears

PCR ZEDL:

167
PCR: ZERC:

PCR: ZNRT:

168
PCR: ZNVT:

169
PCR: ZRET:

170
 PAYROLL ORGANISATION

Period Parameters
In this step, the period parameters for payroll are defined.

Period parameter is a two-digit numerical parameter that defines the time

interval for running payroll.
IMG Menu Path

SAP R/3 Role Menu Payroll Organization

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) 
Payroll Payroll: India Basic settings Payroll
IMG Menu
organization Define Period Parameters

Description and Configuration Values

In Cairn Energy the Payroll run is Monthly Payroll run for all the employees. We
have configured the Monthly Payroll to suit the requirement as shown in the
following table

Period Parameters Name Time Unit Start Date

1 Monthly 1 01.01.1990

67 Monthly - IN 1 01.04.1998

Date Modifiers
The data modifier is only a means of differentiation allowing defining different
payment dates for various employee groups.

Date Modifiers defined in this step are assigned to Payroll Areas.

IMG Menu Path

171
SAP R/3 Role Menu Payroll Organization
Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG)  Payroll
 Payroll: India  Basic settings  Payroll organization 
IMG Menu
Define Date modifiers

Description and Configuration Values

The following date modifier has been configured for Cairn Energy

Date Modifier Name

00 Standard Modifier

Generate Payroll Periods

The period for which payroll regularly runs. In an abstract sense, payroll period is
the name given to the interval for which Payroll regularly runs, such as Weekly or
monthly payroll periods.

For each period parameter that is assigned to a payroll area, the system requires
the following date specifications:

 Start date and end date of each payroll period (Ex: 01.04.2007 – 31.04.2007)
 Payment date of each payroll period (Ex: Payment date for April 2007 is
30.04.2007)
IMG Menu Path

SAP R/3 Role Menu Basic Pay

Transaction Code SPRO
Implementation Guide for R/3 Customizing (IMG) 
IMG Menu Payroll Payroll: India Basic settingsPayroll
organization Generate Payroll Periods
Description and Configuration Values

We have generated the payroll periods for the period parameters i.e. MONTHLY for
the years 2006 to 2010.

The start and end dates of the periods should be the same as the start and end
dates of the calendar months. The period’s payment dates should be three days
before the end of the period.

The following table represents the Payroll Periods defined for Cairn Energy’s
Payroll Nationals.

Payroll Payroll Previous Previous Payroll

Start date End date
year Period Payroll year Period

2007 1 01.04.2007 30.04.2007 2006 12

172
Payroll Payroll Previous Previous Payroll
Start date End date
year Period Payroll year Period

2007 2 01.05.2007 31.05.2007 2007 1

2007 3 01.06.2007 30.06.2007 2007 2

2007 4 01.07.2007 31.07.2007 2007 3

2007 5 01.08.2007 31.08.2007 2007 4

2007 6 01.09.2007 30.09.2007 2007 5

2007 7 01.10.2007 31.10.2007 2007 6

2007 8 01.11.2007 30.11.2007 2007 7

2007 9 01.12.2007 31.12.2007 2007 8

2007 10 01.01.2008 31.01.2008 2007 9

2007 11 01.02.2008 29.02.2008 2007 10

2007 12 01.03.2008 31.03.2008 2007 11

2008 1 01.04.2008 30.04.2008 2007 12

2008 2 01.05.2008 31.05.2008 2008 1

2008 3 01.06.2008 30.06.2008 2008 2

2008 4 01.07.2008 31.07.2008 2008 3

2008 5 01.08.2008 31.08.2008 2008 4

2008 6 01.09.2008 30.09.2008 2008 5

2008 7 01.10.2008 31.10.2008 2008 6

2008 8 01.11.2008 30.11.2008 2008 7

2008 9 01.12.2008 31.12.2008 2008 8

2008 10 01.01.2009 31.01.2009 2008 9

2008 11 01.02.2009 28.02.2009 2008 10

2008 12 01.03.2009 31.03.2009 2008 11

2009 1 01.04.2009 30.04.2009 2008 12

2009 2 01.05.2009 31.05.2009 2009 1

2009 3 01.06.2009 30.06.2009 2009 2

2009 4 01.07.2009 31.07.2009 2009 3

173
Payroll Payroll Previous Previous Payroll
Start date End date
year Period Payroll year Period

2009 5 01.08.2009 31.08.2009 2009 4

2009 6 01.09.2009 30.09.2009 2009 5

2009 7 01.10.2009 31.10.2009 2009 6

2009 8 01.11.2009 30.11.2009 2009 7

2009 9 01.12.2009 31.12.2009 2009 8

2009 10 01.01.2010 31.01.2010 2009 9

2009 11 01.02.2010 28.02.2010 2009 10

2009 12 01.03.2010 31.03.2010 2009 11

2010 1 01.04.2010 30.04.2010 2009 12

2010 2 01.05.2010 31.05.2010 2010 1

2010 3 01.06.2010 30.06.2010 2010 2

2010 4 01.07.2010 31.07.2010 2010 3

2010 5 01.08.2010 31.08.2010 2010 4

2010 6 01.09.2010 30.09.2010 2010 5

2010 7 01.10.2010 31.10.2010 2010 6

2010 8 01.11.2010 30.11.2010 2010 7

2010 9 01.12.2010 31.12.2010 2010 8

2010 10 01.01.2011 31.01.2011 2010 9

2010 11 01.02.2011 28.02.2011 2010 10

2010 12 01.03.2011 31.03.2011 2010 11

2011 1 01.04.2011 30.04.2011 2010 12

2011 2 01.05.2011 31.05.2011 2011 1

2011 3 01.06.2011 30.06.2011 2011 2

2011 4 01.07.2011 31.07.2011 2011 3

2011 5 01.08.2011 31.08.2011 2011 4

2011 6 01.09.2011 30.09.2011 2011 5

2011 7 01.10.2011 31.10.2011 2011 6

174
Payroll Payroll Previous Previous Payroll
Start date End date
year Period Payroll year Period

2011 8 01.11.2011 30.11.2011 2011 7

2011 9 01.12.2011 31.12.2011 2011 8

ABAP DEVELOPMENTS

Transaction
Sl. No. Description
Code

1 Car running Expenses Monthly Report ZPY007

2 Car running Expenses Period end treatment Report ZPY008

3 Telephone reimbursement Period end process Report ZPY004

4 Telephone reimbursement Display claim details Report ZPY004_Disp

ZPY001_Outst
5 Telephone reimbursement Outstanding balance Report
anding

6 Medical Reimbursement Period end process Report ZPY017

7 Medical Reimbursement claim display details Report ZPY017_Disp

8 Medical Reimbursement Outstanding balance Report ZPY018

9 FHPL Monthly Report ZPY005

10 Leave encashment details Report(Display mode only) Zpy014

11 Coff encashment details Report(Display mode only) Zpy015

12 N/F Holidays History of Employee Report ZPY010_D

13 Pay register Report ZPY019

14 Generation of Allow. in lieu of Superannuation report ZPY009

15 Updation of data table (ZPY_SUPER_ANNU) ZPY009

16 Generation of Monthly Superannuation report ZPY012

17 Standard Vs Actual Reconciliation ZPY021

Allowance in lieu of superannuation automatic updation

18 ZPY026
IT0008

19 Full & Final settlement Infotype updation Report ZPY020

175
 20 Salary Transfer ZPY016

Mode wise Reconciliation of Salary Disbursement

21 ZPY013
Monthly Report

22 Income Tax computation Statement ZPY024

23 Full & Final settlement Final Report ZPY023

24 Telephone Reimbursement Claim creating process ZPY001

25 Car running Expenses Claim Creation Process ZPY002

26 Salary Advance ZPY003

27 Medical Reimbursement Claim creating process ZHR007

28 Medical Reimbursement claim approval by CMO ZHR007

29 FHPL Claim creating process ZHR007

30 FHPL Claim approval by CMO ZHR007

31 LTA application process ZLTACF

32 National/Festival holidays Pay application process ZPY010

Processing Classes:

176
177
178
179
180
181
182
183
184
185
186
Cumulation Classes:
1. Total gross amount

187
 10. Net payments/Deductions
11. EPF Basis
12. ESI Basis
13. ESI Basis Nominal
14. HRA Basis
15. COA/CLA Basis
16. Gratuity Basis
17. Super anuation basis
18. Ptax Basis
19. Ptax basis Nominal
28. Leave Encashment basis
32. Monthly Exceptions
33. Annual Exceptions
39. VPF basis
40. LWF basis
Evaluation Classes:

PA30- Master Data:

188
IT-0000-Actions:

IT-0001- Organizational Assignment

189
IT-0002- Personal Data:

IT-0003- Payroll Status:

190
IT-0006- Address:

IT-0007- Planned Working Time:

191
IT-0008-Basic pay:

IT-0009-Bank Details:

192
IT-0014- Recurring payments/ Deductions:

IT-0015 Additional Payments:

193
IT-0016- Contract elements:

IT-0019 Monitoring of Tasks:

194
IT-0021 Family Members/Dependence:

IT-0022 Education:

195
IT-0023 Other/ Previous Employers:

IT-0031 Reference Personal Numbers:

196
IT-0045- Loans:

IT-0050 Time Recording Info:

197
IT-0105- Communication:

IT-0185 Personal ID’s:

198
IT-0580- Previous Employment Tax Details:

IT-0581-HRA:

199
IT-0582- Exceptions:

IT-0583- Car & Conveyance:

200
IT-0584- Income From Other Sources:

IT-0585- Section 80 Deductions:

201
IT-0586- Section 80C Deductions:

IT-0587- PF:

202
IT-0588- Other Statutory Deductions:

203
IT-0589- Individual Reimbursement:

Payroll-Run:

204
PC00_M40_CALC_SIMU- Simulation:

PC00_M99_PA03_RELEA- Release Payroll:

205
PC00_M40_CALC- Start Payroll:

PC00_M99_PA03_CHECK- Check Results

PC00_M99_PA03_CORR- Corrections

206
PC00_M99_PA03_END- Exit Payroll

PC00_M40_CEDT- Remuneration Statement

207
Payroll Results: T.Code: PC_payresults, PC_M40_CLSTR

208
RT Table:

CRT Table:

209
BT Table:

Reporting for Posting Payroll Results to Accounting:

210
Employee Grouping for Account Determination:

Define Symbolic Accounts:

211
Define Posting Characteristics of Wage Types:

Other Steps:

Maintain Posting date for Payroll Periods

Create Posting Variants

Activities in AC System (Assigning Accounts)

Posting Run:

Execute Run: PC00_M99_CIPE

212
Edit Run-PCP0

213
Other Legal Reports:

LOANS CONFIGURATION

Payroll >> Payroll India >> Company Loans >> Master Data >> Maintain
Loan Types >> Loan Types Definition

214
Payroll >> Payroll India >> Company Loans >> Master Data >> Maintain
Loan Types >> Country Assignment

Payroll >> Payroll India >> Company Loans >> Master Data >> Maintain
Loan Types >> Technical Attributes

Payroll >> Payroll India >> Company Loans >> Master Data >> Maintain
Loan Types >> Conditions

215
Payroll >> Payroll India >> Company Loans >> Master Data >> Customer Pay
Types >> Set up Customer Payment Types >> Define Payment Types

Payroll >> Payroll India >> Company Loans >> Master Data >> Customer Pay
Types >> Set up Customer Payment Types >> Assignment of Wage types to
payment types

216
Payroll >> Payroll India >> Company Loans >> Master Data >> Customer Pay
Types >> Control Allocation of Loans >> Adopt Feature

Payroll >> Payroll India >> Company Loans >> Master Data >> Customer Pay
Types >> Control Allocation of Loans >> Define Values

217
Payroll >> Payroll India >> Company Loans >> Master Data >> Customer Pay
Types >> Maintain Loans Grouoping

Payroll >> Payroll India >> Company Loans >> Master Data >> Customer Pay
Types >> Maintain Salary Components

218
Payroll >> Payroll India >> Company Loans >> Master Data >> Customer Pay
Types >> Maintain Maximum No. of Loans allowed >> Maintain Maximum No.
of Loans allowed at a time (Country Grouping 40)

Payroll >> Payroll India >> Company Loans >> Master Data >> Customer Pay
Types >> Maintain Maximum No. of Loans allowed >> Maintain Maximum No.
of Loans allowed

Payroll >> Payroll India >> Company Loans >> Master Data >> Customer Pay
Types >> Maintain maximum amount for Loans Outstanding

219
Payroll >> Payroll India >> Company Loans >> Master Data >> Customer Pay
Types >> Maintain Loans Eligibility Checks and Limits

Payroll >> Payroll India >> Employee Self Services >> Claims >>
Reimbursement Type Settings >> Maintain Attributes of Reimbursement Types

Payroll >> Payroll India >> Employee Self Services >> Claims >>
Reimbursement Type Settings >> Define Groups for Reimbursement Types

220
Payroll >> Payroll India >> Employee Self Services >> Claims >>
Reimbursement Type Settings >> Define Payment mode of Reimbursement
Types

Payroll >> Payroll India >> Employee Self Services >> Claims >>
Reimbursement Type >> Map Subtypes of Loan infotype to Reimbursement
Types

221
Payroll >> Payroll India >> Employee Self Services >> Loans >> Loans >>
Define Number Range for Loans

Payroll >> Payroll India >> Employee Self Services >> Loans >> Node Text
Not Found >> Define Loan types and conditions (Country Grouping 40)

222
Payroll >> Payroll India >> Employee Self Services >> Loans >> Node Text
Not Found >> Define Loan Payment Types (Country Grouping 40)

Payroll >> Payroll India >> Employee Self Services >> Loans >> Node Text
Not Found >> Define Loan Re-Payment Types (Country Grouping 40)

Payroll >> Payroll India >> Employee Self Services >> Loans >> Node Text
Not Found >> Map Loan Types to Approvers

Travel Management

SCOPE OF THE DOCUMENT.........ERROR! BOOKMARK NOT DEFINED.

Human Resources – Travel Management Configuration Scope......216
223
 2.3 Define Control parameter for Travel Expenses...................217
2.3.1 Define Trip Provision Variant.............................................217
2.3.2 Define Global Settings.....................................................218
2.4 Define Control parameter for Travel Data.........................219
2.4.1 Define Trip Areas............................................................219
................................................................................................219
3.3.2 Define Trip Activity Types.................................................220
You have to define the various Trip Reasons in this activity................................220
2.5 Travel Expense Types....................................................220
2.5.1 Create Travel Expense Types for Individual Receipts............220
2.6 Dialog and Travel Expenses Control.................................221
2.6.1 Define Schema and Individual Field Control........................221
You have to define the screen layout for the various Trip Provision Variant in this activity.221
2.6.2 Restrict travel expense types for Trip Schemas...................222
2.6.3 Travel Management Travel Expenses Dialog and Travel Expenses Control
Dialog Control Restrict travel expense types for Trip Schemas..........................223
2.6.4 Field Control for Additional Receipt Information...................223
You define the field status of the additional receipt........................................223
2.6.5 Setup variable layout for Account assignment objects..........225
................................................................................................226
2.7 Travel Expenses Control................................................226
2.8 Wage Types for Interfaces.............................................227
2.8.1 Assign Wage Types to Travel Expense Types for Indiv. Receipts227
Here in this activity we assign wage type to the expense type............................227
2.9 Transfer to Accounting..................................................228
2.9.1 Number Ranges for Posting Runs......................................228
You have to provide number ranges for posting run for transfer to accounting...........228
2.9.2 Number Ranges for Trip transfer documents.......................229
You have to define the number range interval for the internal assignment of trip transfer
document.....................................................................................229
2.9.3 Assignment of Wage Type to Symbolic Account...................229
You have to provide a symbolic account to each wage type for transfer to accounting. .229
2.9.4 Conversion of Symbolic Account to Expense Account............230
You have to provide a symbolic account to actual expense GL and Employee Account for
transfer to accounting........................................................................230
................................................................................................230

Human Resources – Travel Management Configuration

Scope
The Travel Management section contains the configuration details of the module.
As part of business process mapping following configuration has been carried out
in this module.

224
Define Trip Number Ranges

You have to define number ranges personnel area wise for creation of trip in this activity

Access the activity using one of the following navigation options:

IMG Menu SPRO  Financial Accounting →Travel
ManagementSet Up Trip Number Ranges

Transaction Code SPRO

Define Control parameter for Travel Expenses

Define Trip Provision Variant

You have to define the trip provision variant under which all the customizing settings will be
done.

Access the activity using one of the following navigation options:

IMG Menu Travel ManagementTravel ExpensesMaster Data Control

Parameters from Travel Expenses Define/Delete/Restore Trip
Provision Variants

225
 Transaction Code SPRO

Define Global Settings

You have to define the global settings in the trip provision variant.

Access the activity using one of the following navigation options:

IMG Menu Travel ManagementTravel ExpensesMaster Data Control
Parameters from Travel Expenses Define Global Settings

Transaction Code SPRO

226
Define Control parameter for Travel Data
Define Trip Areas

You have to define the trip areas for to allow entitlement as per the area/region. But in order
to suit the Business requirements, instead of defining trip country, we have used this field to
define ‘Self travel – Yes or No’.

Access the activity using one of the following navigation options:

IMG Menu Travel ManagementTravel ExpensesMaster Data Control
Parameters from Trip Data Define Trip Areas

Transaction Code SPRO

227
 Define Trip Activity Types
You have to define the various Trip Reasons in this activity
Access the activity using one of the following navigation options:

IMG Menu Travel ManagementTravel ExpensesMaster Data Control

Parameters from Travel Privileges Control Parameters from Trip
Facts Define Trip Activity Types

Transaction Code SPRO

Travel Expense Types

Create Travel Expense Types for Individual Receipts

You have to define the various Trip expense types in this activity.

Access the activity using one of the following navigation options:

IMG Menu Travel ManagementTravel ExpensesMaster
DataTravel Expense TypesCreate Travel Expense Types
for Individual Receipts

228
 Transaction Code SPRO

Dialog and Travel Expenses Control

Define Schema and Individual Field Control
You have to define the screen layout for the various Trip Provision Variant in this activity.
Access the activity using one of the following navigation options:

229
 IMG Menu Travel ManagementTravel Expenses Dialog and Travel
Expenses Control Dialog Control Define Schema and
Individual Field Control

Transaction Code SPRO

Restrict travel expense types for Trip Schemas

In this step, you assign to a trip schema those travel expense types that need to be available
under that trip schema.

If you do not specify any travel expense types for a trip schema, then all expense types
stored in the system apply to that trip schema.

230
Access the activity using one of the following navigation options:
IMG Menu 1.1.1 Travel Management Travel Expenses Dialog and
Travel Expenses Control Dialog Control Restrict
travel expense types for Trip Schemas

Transaction Code SPRO

Field Control for Additional Receipt Information

You define the field status of the additional receipt
Like

1. Required
2. Optional
3. Display
4. Hidden
Access the activity using one of the following navigation options:
IMG Menu Travel Management Travel Expenses Dialog and Travel Expenses
Control Dialog Control Field Control for Additional Receipt
Information

231
Transaction Code SPRO

232
Setup variable layout for Account assignment objects

In this IMG activity you define the screen layout for the account assignment objects - the
selection and order of these objects. In addition you can specify the field characteristics for
each of the account assignment objects.

Access the activity using one of the following navigation options:

IMG Menu Travel Management Travel Expenses Dialog and Travel Expenses
Control Dialog Control Setup variable layout for Account
assignment objects

Transaction Code SPRO

233
Travel Expenses Control
Travel Expenses Control (Expert View)

In this IMG activity, you can edit the matrix of accounting rules. For each position in the
matrix, you can access documentation (F1 Help) and input help (F4 Help).

Access the activity using one of the following navigation options:

IMG Menu Travel Management Travel Expenses Dialog and Travel Expenses
Control Travel Expenses Control Travel Expenses Control (Expert
View)

234
 Transaction Code SPRO

Wage Types for Interfaces

Assign Wage Types to Travel Expense Types for Indiv. Receipts
Here in this activity we assign wage type to the expense type
Access the activity using one of the following navigation options:
IMG Menu Travel Management Travel Expenses Wage Types for Interfaces
Assign Wage Types to Travel Expense Types for Individual Receipts

Transaction Code SPRO

235
Transfer to Accounting
Number Ranges for Posting Runs
You have to provide number ranges for posting run for transfer to accounting
Access the activity using one of the following navigation options:
IMG Menu Travel Management Travel Expenses Transfer to Accounting Set
Up Number Ranges for Posting Runs

Transaction Code SPRO

236
Number Ranges for Trip transfer documents
You have to define the number range interval for the internal assignment of trip transfer
document.
Access the activity using one of the following navigation options:
IMG Menu Travel Management Travel Expenses Transfer to Accounting Set
Up Number Ranges for Trip transfer document

Transaction Code SPRO

Assignment of Wage Type to Symbolic Account

You have to provide a symbolic account to each wage type for transfer to accounting
Access the activity using one of the following navigation options:

IMG Menu Travel Management Travel Expenses Transfer to Accounting

Define Assignment of Wage Type to Symbolic Account

Transaction Code SPRO

Conversion of Symbolic Account to Expense Account

You have to provide a symbolic account to actual expense GL and Employee Account for
transfer to accounting
Access the activity using one of the following navigation options:

237
IMG Menu Travel Management Travel Expenses Transfer to Accounting
Conversion of Symbolic Account to Expense Account

Transaction Code SPRO

238
CATS-Configuration:

239
SCOPE OF THE DOCUMENT
The Time Sheets document contains the configuration details of the module. As
part of business process mapping following configuration has been carried out in
this module.

SETTINGS FOR ALL USER INTERFACES

Create Authorizations for data entry profiles
Use

To assign users authorization for specific data entry profiles, you do not have to assign each
user all the relevant profiles individually. Instead you can define profile authorization groups
and use them to group data entry profiles with common attributes.

Procedure
Access the activity using one of the following navigation options:
IMG Menu SPRO  Cross Application Components > Time Sheet > Settings for all
user interfaces > Authorizations > Create Authorizations for data entry
profiles

Transaction Code SPRO

Result

SPECIFIC SETTINGS FOR CATS REGULAR

Setup data entry profiles
Use

In this activity, you set up the Web application CATS regular for the Cross-Application Time
Sheet

240
Procedure
Access the activity using one of the following navigation options:
IMG Menu SPRO  Cross Application Components > Time Sheet > Specific
settings for CATS regular > Record working time > Set up data entry
profiles

Transaction Code SPRO

Result

241
*The ‘ADMIN’ profile is without an approval procedure & changes even after approval of
Time Sheets are possible.

242
*The ‘EMPLOYEE’ profile is with an approval procedure & changes after approval of Time
Sheets are not possible.

SPECIFIC SETTINGS FOR CATS REGULAR

Define Field Selection
Use

In this step, you decide which fields should appear on the screen when maintaining or
displaying the time sheet, and also define their attributes

Procedure
Access the activity using one of the following navigation options:
IMG Menu SPRO  Cross Application Components > Time Sheet > Specific
settings for CATS regular > Record working time > Define field
Selection

Transaction Code SPRO

Result

243
*Select Worklist & click Influencing to select a data entry profile.

Worklist fields need to chosen for both the data entry profiles, which are ‘ADMIN’
& ‘EMPLOYEE’.

Similarly, fields for Data entry section of time sheet can be

selected in the below screen.

244
*Select Data entry section & click Influencing to select a data entry profile.

245
Data entry section fields need to chosen for both the data entry profiles, which
are ‘ADMIN’ & ‘EMPLOYEE’.

TIME DATA RECORDING & ADMINISTRATION

Define Attendance types
Use

In this step, you define attendance types for a personnel subarea grouping for
attendance/absence types.

Procedure
Access the activity using one of the following navigation options:
IMG Menu SPRO  Time Management > Time data recording & Administration >
Attendance/Actual working times > Define Attendance types

246
 Transaction Code SPRO

Result

*Attendance types represent the kind of work done by a time-writer and these
attendance types would be available under the field ‘Activity type’ on ESS.

247
Group employee subgroups for time quotas
Use

In this step, you group your employee subgroups for time quota types.

Employee subgroups for which the same attendance and absence quota types are defined
are assigned to the same grouping for time quota types.

Procedure
Access the activity using one of the following navigation options:
IMG Menu SPRO  Time Management > Time data recording & Administration >
Attendance/Actual working times > Attendance counting > Rules for
Attendance Counting (New) > Group employee subgroups for time
quotas

Transaction Code SPRO

Result

Group Personnel subareas for time quotas

Use
In this step, you group your personnel subareas with regard to the permissibility of time
quota types.
Personnel subareas for which the same attendance and absence quota types are defined are
assigned to the same grouping for time quota types.

248
 Procedure
Access the activity using one of the following navigation options:
IMG Menu SPRO  Time Management > Time data recording & Administration >
Attendance/Actual working times > Attendance counting > Rules for
Attendance Counting (New) > Group personnel subareas for time
quotas

Transaction Code SPRO

Result

Define Counting Rules

Use
In this step, you define rules for counting attendances.
Procedure
Access the activity using one of the following navigation options:
IMG Menu SPRO  Time Management > Time data recording & Administration >
Attendance/Actual working times > Attendance counting > Rules for
Attendance Counting (New) > Define counting rules

Transaction Code SPRO

Result

249
250
Assign Counting Rules to Attendance types
Use

In this step, you determine & assign the respective counting rule for attendance counting to
each attendance type.

Procedure
Access the activity using one of the following navigation options:
IMG Menu SPRO  Time Management > Time data recording & Administration >
Attendance/Actual working times > Attendance counting > Rules for
Attendance Counting (New) > Assign counting rules to attendance
types

Transaction Code SPRO

Result

Select Allowed Absence types

Use
In this section, you define the absence types that the employees are allowed to enter in
CATS Regular.
To do this, deactivate / tick all the absence types that are not be entered using ESS.
Procedure
Access the activity using one of the following navigation options:
IMG Menu SPRO  Cross Application Components > Time Sheet > Specific
settings for CATS regular > Record working time > Select Allowed
Absence types.

251
Result

Define rejection Reasons

Use

In this step, you define the rejection reasons that the person approving the data can attach
to a rejected record.

We have simply created a rejection reason ‘RC-For Rejection’ with long-text functionality as
active in order to enable the approver write a comment while rejecting the time entry.

Procedure
Access the activity using one of the following navigation options:
IMG Menu SPRO  Cross Application Components > Time Sheet > Settings for All
User Interfaces > Approval procedure > Define rejection reasons

Result

Personnel Development

The following standard reports are available in the Personnel Development

component:

252
  Profile Match-up
 Profiles
 Find Objects
 For Qualifications
 For a Development Plan
 For a Development Plan Item
 Appraisals
Following reports can be executed for Organization unit

 Profile Match-up: Position/Holder

 Profiles
 Succession Overview
Training and Event Management
Training and Event Management offers extensive and comprehensive reporting
functions. One can request a wide variety of reports for business events,
resources, and attendees. One can also get reports for training and event costs,
business event appraisals, attendee appraisals, or missing resources.

For attendance

 Attendee List
 Attendance List
 Employee list
 Bookings per Attendee
 Attendee's Training History
 Attendance Prerequisites
 Attendee's Qualifications
 Prerequisites Matchup
 Attendee Appraisal
 Prebookings per Business Event Type
 Prebookings per Attendee
 Attendees to Be Rebooked
 Attendance Statistics
 Attendance and Sales Statistics
 Cancellations per Business Event
 Cancellations per Attendee
 Budget Comparison
For resources

 Resource Equipment
 Resource Reservation
 Instructor Information
 Graphical Resource Reservation
 Available/Reserved Resources
 Resource Reservation Statistics
 Resources Not Yet Assigned per Resource Type

253
For business events

 Business Event Demand

 Business Event Schedule
 Business Event Appraisal
 Business Event Hierarchy
 Attendance Statistics
 Business Event Brochure
 Business Event Information
 Business Event Dates
 Resource List per Business Event
 Resources Not Yet Assigned per Business Event
 Material Requirements per Business Event
Business Event Prices

ESS- Configuration:
Customizing Screen (PTARQ)

254
Working Time – Leave Request

1) Processing Process

Step-1

i) Create a Rule Groups

ii) Maintain WEBMO Feature assigning the Rule Group

255
Step-2

Step-3

256
i) Define Absences/Processing Processes -> This leave types will be appeared
in ESS while raising the leave request.

257
258
2) Layout of Web Application

Step-1

259
Specify how leave is displayed.

Step-2

Specify Display of Absence Quotas

260
261
Working Time – Record Working Time

Step-1

Setup Data Entry Profile

262
Step-2

Select the allowed absence type

263
CATSDB -> CATS: Database Table for Time Sheet

Benefits and Payments -> Claims

Basic Settings

Step-1

264
Perquisites: Tax Codes should already been created in Payroll

Step-2

Maintain attributes: Customized Fields for Expart Claims:

Table Name:

V_T7INFLD_OUTLK

265
 Request Reimursement
Customer Field Field Lable
Type Type

Payment Mode -
CL Claim ECHR CUS_FLD3 INR/USD/GBP

CL Claim ECUB CUS_FLD2 Name of the Club

Payment Mode -
CL Claim ECUB CUS_FLD3 INR/USD/GBP

CL Claim ECUB CUS_FLD9 Amount Spent

CL Claim ECUB JBGDT From Date

CL Claim ECUB JENDT To Date

CL Claim EDSL CUS_FLD9 Bills Attached (Y/N)

Payment Mode -
CL Claim EGEN CUS_FLD3 INR/USD/GBP

CL Claim EGEN CUS_FLD9 Amount Spent

CL Claim EIDT CUS_FLD9 Bills Attached (Y/N)

Payment Mode -
CL Claim EIMU CUS_FLD3 INR/USD/GBP

CL Claim EIMU CUS_FLD9 Amount Spent

CL Claim EPME CUS_FLD2 Name of Membership

Payment Mode -
CL Claim EPME CUS_FLD3 INR/USD/GBP

CL Claim EPME CUS_FLD4 Membership Cost

CL Claim EPME JBGDT From Date

CL Claim EPME JENDT To Date

Payment Mode -
CL Claim EREF CUS_FLD3 INR/USD/GBP

CL Claim ERLT CUS_FLD9 Bills Attached (Y/N)

Payment Mode -
CL Claim ERNR CUS_FLD3 INR/USD/GBP

CL Claim ERNR FAMSA1 Family Details

CL Claim ERNR OBJPS1 Child

Payment Mode -
CL Claim ESHC CUS_FLD3 INR/USD/GBP

CL Claim ESHC CUS_FLD9 Amount Spent

CL Claim ESPE CUS_FLD3 Payment Mode -

266
 INR/USD/GBP

CL Claim ESPE CUS_FLD9 Bills Attached (Y/N)

Payment Mode -
CL Claim ESPR CUS_FLD3 INR/USD/GBP

CL Claim ESPR CUS_FLD9 Bills Attached (Y/N)

Payment Mode -
CL Claim ESUP CUS_FLD3 INR/USD/GBP

Payment Mode -
CL Claim ETEL CUS_FLD3 INR/USD/GBP

CL Claim ETEL CUS_FLD9 Amount Spent

Payment Mode -
CL Claim ETFE CUS_FLD3 INR/USD/GBP

CL Claim ETFE CUS_FLD6 Name of Child

CL Claim ETFE CUS_FLD9 Amount Spent

CL Claim SCLB CUS_FLD2 Name of the Club

CL Claim SCLB CUS_FLD4 Membership Cost

CL Claim SCLB CUS_FLD9 Bills Attached (Y/N)

CL Claim SCLB JBGDT From Date

CL Claim SCLB JENDT To Date

CL Claim SEDD CUS_FLD1 Course Fee

CL Claim SEDD CUS_FLD5 Name of the Course

CL Claim SEDD CUS_FLD9 Bills Attached (Y/N)

CL Claim SEDD JBGDT Course Start Date

CL Claim SEDD JENDT Course End Date

CL Claim SEDO CUS_FLD1 Course Fee

CL Claim SEDO CUS_FLD5 Name of the Course

CL Claim SEDO CUS_FLD9 Bills Attached (Y/N)

CL Claim SEDO JBGDT Course Start Date

CL Claim SEDO JENDT Course End Date

CL Claim SGEN CUS_FLD9 Bills Attached (Y/N)

CL Claim SLTA DESTN Destination point of Journey

CL Claim SLTA FAMSA1

CL Claim SLTA JBGDT Start Date of Journey

267
CL Claim SLTA JENDT End Date of Journey

CL Claim SLTA OBJPS1

CL Claim SLTA STPNT Start point of Journey

CL Claim SLTA TKTNO Bills Submitted Amount

CL Claim SLTA TXEMP Tax Exemption

CL Claim SPFM CUS_FLD2 Name of Membership

CL Claim SPFM CUS_FLD4 Membership Cost

CL Claim SPFM CUS_FLD9 Bills Attached (Y/N)

CL Claim SPFM JBGDT From Date

CL Claim SPFM JENDT To Date

CL Claim STEL CUS_FLD7 Telephone No1

CL Claim STEL CUS_FLD8 Telephone No2

CL Claim STEL CUS_FLD9 Bills Attached (Y/N)

CL Claim STEL JBGDT From Date

CL Claim STEL JENDT To Date

Step-3

Maintain Approvers:

268
Step-4

Define Approver Privileges:

269
Step-5

Mapping approver groups to reimbursement types:

Reimbursement Type Settings

270
Step-1

Maintain attributes for reimbursement types:

Step-2

Group reimbursement types:

271
Step-3

Maintain payment mode for reimbursement types:

272
Travel Management:

Travel Requests personalized fields on portal front end:

TRAVEL REQUEST

Field description Changed to

General Data Travel details

Start Date Start date of trip

End Date End date of trip

Planned Activity Trip type

First
Location Destination

273
Fields removed

Time

Time

Country/Region

Estimated Costs

My Trips & Expenses

Screen

Tabs kept:

All my travel requests

All my expense reports

In Edit Advances button:

Fields removed:-

Exchange rate

Amount

Accounting in

In travel services button:

Fields removed:-

Credit card information

Screen after 'review'

Fields removed:-

Summary

credit card info

i) Travel Expense report:

EXPENSE REPORT

removed Fields in display only

274
 All fields to be made display
Schema Selection only

Time

Time

per-deims

Mileage

Edit Advances' - Only the button

Changed
Field description to

Type of
Schema trip

Screen after 'Enter receipts'

Fields removed:-

Summary

credit card info

Available credit card receipts ' - Only the

button

Scanned receipts' - Only the button

Screen after 'New entry'

Fields removed:-

Amount

local currency

short info

confirmed

Origin

country/region

participants

enter participants

275
from - to

number

Screen after 'Review'

Fields removed:-

Entire Summary screen

CONFIGURATION STEPS:
Interface Configuration for Webdynpro Interface in Travel
Management:
For ESS Settings for Travel management go to -> FITVFELD_WEB Tcode

1) Activate Request/Plan/Expense Report in Travel Manager

2) Set Up Variable Field Control via Feature TRVFD

3) Schema and Single Field Control for Web Dynpro

276
Select the CN Trip Provision variant and after that ----

277
Features Used for Travel (For ESS):
Form Variant for Travel Request: TRVFR

YFITP_REQUEST_FORM smart form used for travel request

Form Variant for Travel Planning: TRVFP

278
Form Variant for Travel Expenses: TRVFE

Travel Expense Report for ESS modifications: ZZPTRV_EXPENSE_FORM Smart

Form

5) Personal Information:

SM 30 -> Table -> V_T7XSSPERSUBTYP

Country use
Infotype Subtype
Group case

40 2 B1

40 6 1 A1

40 6 4 A2

40 6 5 A2

40 9 0 B1

40 9 1 B3

40 9 2 B2

279
 40 21 1 A1

40 21 2 A6

40 21 3 A4

40 21 4 A4

40 21 1 A1

40 21 2 A6

BACKGROUND
Cairn Energy India Pty. Limited is one of the leading Oil Exploration and
Production Company with an exciting growth portfolio of assets in India. The
parent company Cairn Energy Plc, located in Edinburgh, Scotland is one of
Europe’s largest independent Oil and Gas companies. The world class oil and gas
discoveries in Rajasthan, along with existing joint venture production in Andhra
Pradesh and Gujarat, have the potential to contribute significantly to India’s
growing energy needs.

Scenario: Employee Self Service

Employee Self-Service (ESS) enables employees to create, display, and change
their own data in the intranet used at their enterprise. By enabling employees to
access their own data, HR processes are standardized and simplified. As a result,
employees in the Human Resources Department can concentrate on other tasks
of greater strategic importance.

Process Group: Process on ESS

Who’s Who
This feature enables employees to search for other employees in the organization
based on various parameters. The following search fields shall be made available
–

 Personnel Number (D)

 First Name, Last Name
 Residence Telephone Number (D for all)(M for self)
 Cubicle Number (D for all)
 Extension Number (D for all)
 Office Email (D for all)
 Mobile Number (D for all)(M for self)
 Company Code
 Employee Group (Search)
 Employee Sub Group (Search)
 Personnel Area (Search)
 Personnel Sub Area (Search)
 Position (Designation)
 Immediate Manager (D)
 Organization Unit
 On ESS other than employee photograph will not be displayed
WHO’S WHO ESS SCREEN:

280
Employee Search:

i) Who’s Who
ii) Change Own Data

Personal Information
i) Personal details

Employees access the personal details through “Personal Information” tab.

The following fields shall be available –

 First Name
 Last Name
 Date of birth (Display only)
 Marital status
 Marriage date
ii) Address check

Employees access the address data through “Personal Information” tab. The
infotype maintained in R/3 is available for maintenance. The following
address types shall be available –

 Permanent address
 Mailing address
 Emergency address
 Onsite Address
 Current Location
iii) Family details

Employees access the family data through “Personal Information” tab. The
infotype maintained in R/3 is available for maintenance. The following
relationship types shall be available –

 Spouse
 Father
 Mother
 Son

281
  Daughter

iv) Bank details

Employees access the family data through “Personal Information” tab. The
infotype maintained in R/3 is available for maintenance. Using this link,
employee can change bank key and account number. Bank key will be
displayed as a label on Bank tab page. These will be only salary bank keys.

v) Other details – Link to Infotypes (Suggestion)

 Infotype 0185 – Personal ID – Subtype - 4 wheeler license

 Infotype 0185 – Personal ID – Subtype - PAN Number
 Infotype 0105 – Communication ID – Subtype - Personal email id
Changes done on any infotype link will update the changes in R/3

PERSONAL INFORMATION ESS SCREEN:

Training and Event Management

This feature enables the employees to view the Training Calendar and make the
bookings (book, cancel, rebook).

i) Training center

 List of Events
 Find Events

282
  Book Events (Workflow is triggered)
 Shopping Basket
ii) My Bookings

 Display Bookings
 Display Status
 Participation Status
 Cancel Booking (Workflow is triggered)
 Appraise Event
iii) Training Feedback

Online Training Feedback link will be available on ESS, where employee can log
on to the ESS and give the feedback of the Training/Course.

(The Training Feedback template for the feedback will be developed in the
Backed end system)

TRAINING ESS SCREEN:

Training:

i) My Bookings
ii) Business Event Catalog (Training Center)

Key Data Structure

i) Booking Priority: To set up a booking priority that is specially assigned
to bookings made using ESS services for Training and Event
Management.
ii) Cancelation reason for employee in ESS: This enables you to store
information about the cancellationreason from table T77CAR to be used
when an employee cancels an event booking in the Employee Self-
Service My Bookings (transaction PV8I).

Reporting Requirements
i) Training programs attended

283
Travel Management
In the Employee Self-Service application Travel and Expenses, employees can
perform the following tasks:

 Create travel requests

 Travel Request is sent through workflow to the relevant DOA for
approval. (Workflow is configured at the Backend system R/3)
 Enter travel expenses for the trip after completion of their Trip.
 Now the travel expense report is sent for approval to the Immediate
Supervisor and one copy goes to Finance Administrator.
 Any charges incurred while rescheduling / cancellation of travel are
captured in the travel expense report by the travel desk.
 Process trips for other employees (requires authorization for
Administrator)

TRAVEL ESS SCREEN:

Travel:

i) Create Travel request

ii) Crate Travel Expense report
Screen 1:

Screen 2:

284
Payroll and Payments
This process shall be applicable to the following types of payroll reimbursements:

Reimbursement

 LTA Process
 Club Membership
 Medical Reimbursement
 Telephone Reimbursement
 Remote Location Allowance
 Educational Assistance
 Professional Membership
Once an employee selects the appropriate reimbursement type, a detailed screen
will open up. This will have details like – Bill date, Amount, Family members etc.

Employee fills in the necessary details and submits the claim form. This triggers a
mail is sent to the concerned person/departments. Employee shall take a print of
this and submit to the concerned person/departments and send the intimation.
The details of the individual payments made shall be through payroll.

Salary Statement

If current remuneration statement to be displayed on ESS there is a standard

feature available and will be displayed on ESS in PDF format. If PDF format to be
changed like company logo etc to be displayed on Salary statement the “Z”
development to be made in Smart forms (Z report needs to be developed
separately in R/3).

Note: Developments on Claims to be discussed

PAYEMENT ESS SCREEN:

285
Time & Leave Management
Leave Request:

 Any leave approval request will take place through ESS workflow.
Employee has to apply for the leave (preferably in advance).
 Leave balance will be displayed for information purpose, which can be
used for availing leave.
 All leave requests go to the superior and from UWL he/she can
approve/reject the approvals.

Time Management:

 Link for Time Sheet entry would be visible only to the time-writers.
 Working Time function enables time-writers to book their working
times. Through in-built checks, system can determine whether they
have recorded sufficient working times or not (8.50 hrs / day. Mon-Fri
except for weekends & holidays).
 Employee would release the Time sheet and the same goes to the
approver through workflow for review / rejection.
 Time Sheets are deemed approved if not rejected.
 Relevant reports can be churned-out by Finance administrators.
 Employee should not be able to fill Time Sheets for anyone else apart
from his own Id.
 Administrators to have authorization to edit time data for others.
WORKING TIME ESS SCREEN:

i) Time Management
a. Record Working Time
ii) Leave Management
a. Leave Request
b. Quota Overview
c. Leave Request Approver

286
Key Data Structure
i) Message Output to be customized
Appraisal System
Process To be decided.

Standard Appraisal Template:

287
 Baseline Training - Payroll

Maintenance of Payroll Masterdata

288
1) Basicpay Infotype 0008

STEP I

Transaction PA 30
In this screen enter OR select the personnel number in the personnel no. field, and enter
0008 or Basic pay in the info type field. Then click on the create icon on top of the screen.
Then Basic pay info type screen will appear.

STEP II

In this screen enter the start date in the date field and select the pay scale group and pay
scale level in the respective fields, Where the Pay scale type and pay scale area are
defaulted.

Next enter in the Wage type field, Then automatically all Basic wage components will be
defaulted. Enter the Direct amounts of Wage components in the amount coloum.Indirect

amounts of wage types will be defaulted automatically. Then click on the save icon.

2) Recurring payments & Deductions Info type 0014

STEP I

Transaction PA 30
In this screen enter OR select the personnel number in the personnel no. field, and enter
0014 in the info type field. Then click on the create icon on top of the screen. Then Recurring
payments & deductions info type screen will appear.

289
STEP II
In this Info type screen enter the start date and End date in the respective fields. Then select
the wage type in the wage type field and enter the amount and unit/number in those fields. If
the selected wage type is valuated indirectly the amount will be defaulted in the amount
column. Then click on the save icon.

3) Additional payments Info type 0015

STEP I

Transaction PA 30
In this screen enter OR select the personnel number in the personnel no. field, and enter
0015 in the info type field. Then click on the create icon on top of the screen. Then Additional
payments info type screen will appear.

STEP II
In this Info type screen enter the wage type in the wage type field and enter the amount in
the amount field. Enter the start date of the particular payment of the month in the Date of
origin field. Then save the entries.

290
4) Housing Infotype 581

STEP I

Transaction PA 30

In this screen enter OR select the personnel number in the personnel no. field, and enter
0581 in the info type field. Then click on the create icon on top of the screen. Then Housing
Infotype 0580 screen will appear.

STEP II
Enter the date in the start date filed and select the housing type. Select the City Category
and enter the rent amount. Save the entries.

The system dynamically updates the Basic Pay infotype (0008), with respective wagetype
and the amount based on the Housing type selected in IT581.

5) Car and Conveyance Infotype 0583

Transaction PA 30

In this screen enter OR select the personnel number in the personnel no. field, and enter
0583 in the info type field. Then click on the create icon on top of the screen. Then car and
conveyance Infotype 0583 screen will appear.

STEP II

291
Enter the date in the start date filed and select the conveyance type. Enter the car details if
you selected Car scheme. Save the entries.

The system dynamically updates the Basic Pay infotype (0008), with respective wagetype
and the amount based on the Conveyance type selected in IT583.

6) Section 80 Deductions Infotype 585

STEP I

Transaction PA 30
In this screen enter OR select the personnel number in the personnel no. field, and enter
0585 in the info type field. Then click on the create icon on top of the screen. Then Section
80 Deductions info type screen will appear.

STEP II
In this screen enter the amounts against each sub section in the proposed contribution or in
the actual contribution field he contributions for the current financial year. The Limit & Tax
exemptions and currency of the each contribution are defaulted. Then save the entries.

The tax exemption is calculated during the payroll run.

7) Section 80 C Deductions Infotype 586

STEP I

292
Transaction PA 30
In this screen enter OR select the personnel number in the personnel no. field, and enter
0586 in the info type field. Then click on the create icon on top of the screen. Then Section
80 C deductions info type screen will appear.

STEP II
In this screen enter the amounts in the proposed investment field or in the actual investment
field in respect of the contributions for the current financial year. The Limit and currency of
the each investment are defaulted. Then save the entries.

The tax rebate is calculated during the payroll run.

8) Provident fund contribution Info type 587

STEP I

Transaction PA 30

293
In this screen enter OR select the personnel number in the personnel no. field, and enter
0587 in the info type field. Then click on the create icon on top of the screen. Then Provident
fund contribution info type screen will appear.

STEP II

In this Info type screen enter the provident fund and Pension Trust ID employee belongs to.
Enter the PF Number & Pension Number of the employee in the fields. Enter the VPF % in
the VPF field if the employee opted for voluntary PF contribution.

Basis of contribution is selected as PF Basis by default.

Select the check box ‘Contribution towards Pension’ and save the entries.

PF contribution will deducted from employee salary during the payroll run.

Other statutory Deductions Info type 588

Professional tax (Subtype 0003)

STEP I

Transaction PA 30
In this screen enter OR select the personnel number in the personnel no. field, and enter
0588 in the info type field and select the subtype Professional tax in the subtype field. Then
click on the create icon on top of the screen. Then other statutory deductions screen of PTax
will appear.

STEP II

294
In this screen enter the start date of professional Tax deduction in the From Field and also
select the check box ‘Eligible for PTax field’. Then click on save icon.

PTax is calculated and deducted during monthly payroll run.

Payroll Process

Simulation (Test Run):

Before you start the payroll run for all employees, you can run a Pay roll simulation for
individual employees. To do this follow the below path. & procedure.

STEP I
From the SAP Easy Access screen, choose Human Resources  Payroll  Asia/Pacific
India Payroll Accounting  Simulation or TC PC00_M40_CALC_SIMU
Now Double click on Simulation or Select the Simulation and Enter. Then Payroll Driver,
India Screen will appear.

STEP II
In this screen first enter the Payroll Area as 26 and select the current period or other period
Radio button depends upon running the payroll.
Enter the personnel number and payroll area in those fields. In the schema field Schema
IN00 is defaulted, change this to ZN00.

295
Select the Display variant remuneration statement field to show the Remuneration
statement. Then click on Execute icon of the top of the screen.

STEP III
In the Display Log screen Successful Personnel numbers and Rejected Personnel numbers
will be displayed. If the rejected personnel numbers are displayed, we have to correct the
master data according to the error message.
To see the remuneration statement click on the Display form icon on the top of screen. Then
Remuneration statement will be displayed.

Release the payroll:

STEP I
From the SAP Easy Access screen, choose Human ResourcesPayrollAsia/Pacific
India Payroll Accounting  Release payroll or TC PC00_M99_PA03_RELEA

STEP II
Now Double click on Release payroll or Select the Release payroll, then specify the payroll
area 26 for which you want to release payroll in popup box confirm the message to continue.

Start payroll
STEP I
From the SAP Easy Access screen, choose Human Resources Payroll Asia/Pacific
India Payroll Accounting Start payroll or TC PC00_M40_CALC
Here Double click on Start payroll or Select the Start payroll and enter. Then payroll Driver,
India Screen will appear.

STEP II
In this screen Payroll area, current period, schema fields are defaulted. Select the check
box in the test run field.
Select the Display variant remuneration statement field to see the remuneration
statement
Then click on Execute icon of the top of the screen.

STEP III
The Display Log screen will appear in the Display Log Screen. Then Select the Form Icon
for Displaying the “PAY SLIP” or Remuneration statement.

STEP IV

296
If no errors in the Display Log, deselect the check box in the test run field and Execute the
payroll again.
The payroll has been run for all P.Nos of the payroll area

Released for corrections

STEP I

From the SAP Easy Access screen, choose Human Resources Payroll  Asia/Pacific India
Payroll Accounting  Corrections or TC PC00_M99_PA03_CORR

STEP II
Here Double click on Corrections or Select the corrections and enter to release for
corrections. Now the master data is unlocked for corrections.
Then maintain the required master data in the info types as per the errors displayed in the
Display log.
Repeat the process of Release the payroll and Start payroll.

Repeat these steps until payroll has been performed for all personnel numbers successfully
without errors.

Check Results
STEP I
From the SAP Easy Access screen, choose Human Resources Human Resources Payroll 
India Payroll Accounting  Check Results or TC PC00_M99_PA03_CHECK.

STEP II
If any errors are displayed in the payroll log after executing the payroll, then it should be
corrected.

Exit payroll
STEP I
From the SAP Easy Access screen, choose Human Resources Payroll  Asia/Pacific India
Payroll Accounting  Exit payroll or PC00_M99_PA03_END

297
STEP II
‘Exit Payroll’ dialog message appears, confirm the message
When you exit payroll, payroll is finished for all the personnel numbers in the payroll area
and the payroll period is complete. The personnel numbers for the payroll area can be
processed again.

298
Generation of Statutory Reports
PF Monthly Reports
1) Form 5 - Return of Employees qualifying for membership

STEP I
From the SAP Easy Access screen, choose Human Resources Payroll  Asia/ Pacific India
Subsequent Activities Per Payroll period Legal ReportsEmployees Provident fund Form5,
Form10 & From12A or TC - PC00_M40_EPF

STEP II
Here Enter the following details:

 Payroll Area.
 Period
 PF Trust ID
 Report Name as Form 5
Select ‘Execute’ button
2) Form 10 - Return of Members leaving the service

STEP I
From the SAP Easy Access screen, choose Human Resources  Payroll  Asia/ Pacific
India Subsequent Activities Per Payroll period Legal ReportsEmployees Provident
fund Form5, Form10 & From12A or TC - PC00_M40_EPF

STEP II
Enter the following:

 Payroll Area.
 Period
 PF Trust ID
 Report Name as Form 10
Select ‘Execute’ button
3) Form 12A- Monthly contribution statement

STEP I
From the SAP Easy Access screen, choose Human Resources Payroll Asia/ Pacific
India Subsequent Activities Per Payroll period Legal ReportsEmployees Provident
fund Form5, Form10 & From12A or TC - PC00_M40_EPF

STEP II
Enter the following:

299
  Payroll Area.
 Period
 PF Trust ID
 Report Name as Form 12A
Select ‘Execute’ button

PF Annual Reports
1) Form 3A - Contribution Statement For Unexempted Establishments

STEP I
From the SAP Easy Access screen, choose Human Resources Payroll Asia/ Pacific
India Subsequent Activities Annual  Legal ReportsPFAnnual PF Report ( Form 3A
, Form 6A ) or TC - PC00_M40_PFY

STEP II
Enter the following:
 Payroll Area.
 PF Trust ID
 Year
 Report Name FORM3A
Select ‘Execute’ button
2) Form 6A -Consolidated Contribution statement

STEP I
From the SAP Easy Access screen, choose Human Resources Payroll Asia/ Pacific India
Subsequent Activities Annual  Legal ReportsPFAnnual PF Report ( Form 3A , Form
6A ) or TC - PC00_M40_PFY

STEP II
Enter the following:
 Payroll Area.
 Period
 PF Trust ID
 Report Name as Form 6A
Select ‘Execute’ button

Pension Monthly Reports

1) Form 4 - Return of Employees qualifying for membership

STEP I
From the SAP Easy Access screen, choose Human Resources  Payroll  Asia/ Pacific India
Subsequent Activities Per Payroll period Legal ReportsPension Form4,Form5 &
Form6 with Annexure for Trust wise Detls or TC - PC00_M40_EPN

300
STEP II
Enter the following:
 Payroll Area.
 Period
 PF Trust ID
 Report Name as Form 4
Select ‘Execute’ button

2) Form 5 -Return of Members leaving the service

STEP I
From the SAP Easy Access screen, choose Human Resources Payroll Asia/ Pacific
India Subsequent Activities Per Payroll period Legal ReportsPension
Form4,Form5 & Form6 with Annexure for Trust wise Detls or TC - PC00_M40_EPN

STEP II
Enter the following:
 Payroll Area.
 Period
 PF Trust ID
 Report Name as Form 5
Select ‘Execute’ button
3) Form 6 -Monthly contribution statement

STEP I
From the SAP Easy Access screen, choose Human Resources  Payroll Asia/ Pacific
India Subsequent Activities Per Payroll period Legal ReportsPension
Form4,Form5 & Form6 with Annexure for Trust wise Detls or TC - PC00_M40_EPN

STEP II
Enter the following:
 Payroll Area.
 Period
 PF Trust ID
 Report Name - FORM6 1995
Select ‘Execute’ button

Pension Annual Reports

1) Form 7 (FPF) - Yearly Reports in Detail for Exempted Establishment
STEP I
From the SAP Easy Access screen, choose Human Resources  Payroll Asia/ Pacific
India Subsequent Activities Annual  Legal ReportsPensionAnnual Pension
Reports (Form8, Form 7 ) or TC - PC00_M40_PNY

301
STEP II
Enter the following:
 Payroll Area.
 PF Trust ID
 Year
 Report Name FORM 7(EPF)
Select ‘Execute’ button
2) Form 8 (FPF) -Yearly Report For Exempted Establishment - 1971/95

STEP I
From the SAP Easy Access screen, choose Human Resources PayrollAsia/ Pacific
India Subsequent Activities Annual  Legal ReportsPensionAnnual Pension
Reports (Form8, Form 7 ) or TC - PC00_M40_PNY

STEP II
Enter the following:
 Payroll Area.
 Period
 PF Trust ID
 Report Name as Form 8(FPF)
Select ‘Execute’ button

Professional Tax Monthly Return

STEP I
From the SAP Easy Access screen, choose Human Resources PayrollAsia/ Pacific India
Subsequent Activities Per Payroll period Legal ReportsProfessional Tax Professional Tax
Reports or PC00_M40_PTX

STEP II
1) Enter the following:
 Payroll Area.
 Period
 PT Group
 State /Region
2) Select ‘Execute’ button

Form 16
STEP I
From the SAP Easy Access screen, choose Human Resources PayrollAsia/ Pacific
India Subsequent Activities Annual  Legal ReportsIncome Tax Form 16 or
PC00_M40_F16

302
STEP II
1) Enter the following:
 Payroll Area.
 Company code
 Taxation Year
 Report Name FORM3A
2) Select ‘Execute’ button

Form 24
STEP I
From the SAP Easy Access screen, choose Human Resources PayrollAsia/ Pacific
India Subsequent Activities Annual  Legal ReportsIncome Tax Form 24 or
PC00_M40_F24

STEP II
1) Enter the following:
 Payroll Area.
 Company code
 Taxation Year
2) Select ‘Execute’ button

Features Used In Payroll:

ABKRS

303
TARIF

304
LGMST:

40EPF:

305
40ECS:

40CLM:

306
16EVA:

40LTR:

40SAN:

40LCM:

307
40PTX:

40ECC:

OCEDT:

308
ALOAN:

EDTIN:

EDPDF:

309
DTAKT:

PPMOD:

NUMKR:

PINCH:

310
VDSK1:

PLOGI:

SCHKZ:

TMSTA:

311
QUOMO:

PFREQ:

312
Monthly Payroll-Run- End User manual:

Simulation Run Payroll

We can simulate payroll for individual employees before performing the regular
payroll run for all the employees in an enterprise.

If we have made any changes to an employee’s master data, which may lead to
far-reaching changes in his or her payroll results, stimulation comes into play.

In this way, we can recognize sources of errors in time to make corrections

before the regular payroll run.

We can even simulate payroll for individual employees at any time during the
regular payroll process, in order to trace the cause of any errors.

A simulation run corresponds to a regular payroll run with the following

restrictions:

 The results of a simulated payroll run are not saved on the data base. We
can view and print the results in the payroll log.
 The system does not lock any master data.
 The current payroll period in the payroll control record is not changed.
 The steps Release payroll and Exit payroll do not apply.

Simulation of Payroll
Path:-

313
 1. From the SAP Easy Access screen, choose Human Resources  Payroll 
Asia / Pacific  India Payroll Accounting Payroll Simulation in the SAP
menu.
Screenshot:

Enter Payroll Area number

25 – Payroll Area Nationals

Enter P.No, we want to run payroll.

If we do not enter P.No, payroll will

run for whole Payroll Area 25;
choose the period to be return.
Enter the schema “ZN00”.

This is the schema designed for

Cairn Energy National Employees

This is the test Run

Select the Variant Remuneration

Statement, to view Pay slip.

After entering the above details, click “Execute” button. Then, payroll
schema will run payroll and displays the Payroll Log and Pay slip.

2. Enter the necessary data and choose “Execute” button.

We can access the initial screen of the payroll program.

The Test Run (No Update) indicator is set and cannot be changed.

Releasing Payroll

This is to release the Payroll Area to enable the Payroll Driver to run payroll.
When we release payroll system automatically increase the payroll period by 1
from the existing payroll period.

Path:-

1. From the SAP Easy Access screen, choose Human Resources  Payroll
Asia/Pacific  India Payroll Accounting Release Payroll in the SAP
menu.

Screenshot:

314
2. Choose Yes.

We can run payroll for this payroll area.

The system has increased the period number in the payroll control record for the
payroll area by 1. The payroll control record is used to lock the personnel
numbers in the payroll area for changes to the master and time data reflecting
the past and
present.

Start Payroll (Live Payroll)

We have released the payroll area or areas for which we want to run payroll.

Path:-

1. From the SAP Easy Access screen, choose Human Resources  Payroll 
Asia / Pacific  India Payroll Accounting Start Payroll in the SAP
menu.

We can access the selection screen of the payroll program as shown in the
Step Simulation Payroll.
2. Enter the data required.

 The current period indicator is set in the Payroll period group.

Depending on the payroll area specified, the system reads the
current period from the payroll control record.

If we flag Display log, we get a detailed payroll log after the payroll run.
 The Test run (no update) indicator must not be flagged because
otherwise the system will not save the payroll results.

3. Choose Program Execute button.

 The system performs payroll (usually in the background). If errors

occur, we will get a list with the relevant error messages after
payroll.

315
Use the error messages to check whether personnel numbers have been
rejected or not selected.
 If personnel numbers are rejected or not selected, we must not exit the
payroll program. We must correct the master and time data (Infotype) for
the relevant employee and finally perform a correction run.

Displaying the Payroll Log

The payroll log gives us clear and detailed information on the payroll run and its
results. It is divided into different levels that we can display depending on the
amount of detail required.

The General data level gives information on the processed data and shows the
payroll schema used by the system.

The Successful personnel numbers and Rejected personnel numbers include

processing of the schema for each personnel number

 Navigation in the log tree.

To display lower levels, click on the structure node belonging to the level
that we wish to open. To display all levels behind a higher level, place the
cursor on the relevant level and choose Expand.

 Old log
If we use customer functions with their own logs, we can display these
logs by clicking on the Old log pushbutton.
If Payroll is running retroactively, for any employee, we can display the details of
Retro Active results

316
Screenshot:

Click here to view the

Remuneration
Statement

The Payroll log

displays the
sequential steps of
Payroll Run

The status of Selected

and Rejected P.Nos

Correcting Payroll-Relevant Master and Time Data

When we run payroll occurrence of in error is possible. To complete the payroll

run successfully, it is necessary to correct the master data of the employee.

Path:-

1. From the SAP Easy Access screen, choose Human Resources  Payroll 
Asia / Pacific  India Payroll Accounting Corrections in the SAP menu.

Screenshot:

317
 2. Choose Yes

The system sets the payroll status for the payroll area to Released for
correction. Master and time data processing for the personnel numbers in the
payroll area has been released again.

3. Choose Human resources  Personnel management  Administration

HR master data  Maintain. (PA 30)

4. Correct the relevant infotypes.

Running Payroll for Error P.Nos

Now, we have released the payroll area or areas for which we want to run
payroll.
1. From the SAP Easy Access screen, choose Human Resources  Payroll 
Asia / Pacific  India Payroll Accounting Start Payroll in the SAP
menu.

We access the selection screen of the payroll program as shown in the

step Simulation Payroll
2. Enter the data required.

 The current period indicator is set in the Payroll period group.

Depending on the payroll area specified, the system reads the current
period from the payroll control record.

If we flag the Display log, we get a detailed after the payroll run
 The Test run (no update) indicator must not be flagged because
otherwise the system will not save the payroll results.

3. Choose “Program Execute” button.

 The system performs payroll (usually in the background). If errors

occur, we will get a list with the relevant error messages after payroll.

318
Use the error messages to check whether personnel numbers have been
rejected or not selected.

Simulating a Posting Run

We recommend that we simulate a posting run both before and after completing
(Exit Payroll) payroll. In this way, we can recognize posting-relevant errors in
the payroll results early on, and avoid errors when creating a live posting run.
We can repeat simulation of posting runs as often as we require, as this does
not, unlike creating a live posting run, lead to the payroll results being selected.
Note: - The detailed explanation has been provided in the section posting to
Accounts User Manual.

Exiting Payroll
We have made all master data corrections, have run payroll for all the
employees of the Payroll Area with out errors.
Path:-
1. From the SAP Easy Access screen, choose Human Resources  Payroll
Asia/Pacific  IndiaPayroll AccountingExit Payroll, form the SAP
menu.

Screenshot:

2. Choose Yes
When we exit payroll, payroll is finished for all the personnel numbers in the
payroll area and the payroll period is complete.
 If we want to exit the payroll run for several payroll areas, it is easier to
use the payroll control record. To do so, proceed as when releasing
several payroll areas.
 If we exit payroll using the payroll control record, we can simultaneously
change the earliest possible retroactive accounting period for the relevant
payroll area.

 As long as we have not performed the payroll run without errors, it is not
suggestible to change the earliest possible retroactive accounting period.
For this reason, we can only make entries in this field in the payroll

319
 control record after we have chosen End of payroll and before we save
the payroll control record.

Display Payroll Results

We can use report H99_DISPLAY_PAYRESULT (Display Payroll Results) to display

the payroll results for one or several personnel numbers.

Path:-
1. From the SAP Easy Access screen, choose Human Resources  Payroll
Asia/Pacific  India utilitiesCluster display from the SAP menu.

Screenshot:

Double click on the line to view

the details and Results tables

2. Enter the personnel numbers

The symbol in the Results column shows if there are results available in
the selected period.
 Results exist (Green Symbol)
 No results exist (Red Symbol)
 We have no authorization to display results (Grey colour Symbol)
If the current personnel number is no longer selected (for example
because we selected a column), we can renew the selection by choosing
Update Result.
3. Overview of all the payroll results for a personnel number (cluster CU)
4. Overview of Tables for a Payroll Result
We have displayed the payroll results for a personnel number. If we want
to display the tables for a payroll result, select this payroll result and
choose Display Overview. The system displays the overview of all tables of
the payroll result that are relevant to the country of the employee, and
the number of entries per table.
Remuneration Statement

320
In the Remuneration Statement, SAP R/3 lists amounts and information for the
employee per payroll period. This includes, for example:

 Gross amount (for example, payments)

 Net amount (for example, after deductions)
 Outgoing payment (for example, bank transfer)
 Additional information (for example, organizational assignment, leave,
notes to the employee)

1. We can access the Pay slip, directly while running payroll, using Payroll
Driver.

2. After Payroll run and exiting the payroll run, we can generate the
Remuneration Statement.
Path:

1) From the SAP Easy Access screen, choose Human Resources  Payroll
Asia/Pacific  IndiaPayroll AccountingRemuneration Statement,
from the SAP menu.

Screenshot:

Enter Payroll Area number

25 – Payroll Area Nationals

Enter P.No, to view Payslip of one

employee. Do not enter P.No, to
view for entire Payroll Area 25

2) Enter the details as mentioned and Chose “Execute” button.

The Remuneration statement will appear as shown in the following screenshot.

321
Double-clicking on a sub-schema will take you to the maintenance screen for that schema.
Double-clicking on any of the rules (PCR's) will take you to the rule editor. You can tell the difference between
sub-schemas a rules by looking at the parameters. The name of the sub-schema can be found in the Par 1
column. The main schema generally calls all the different sub-schemas. The sub-schemas will then call the
payroll rules. In most cases, when a rule is called, there will be parameters in the Par 2 or Par 3 columns.
In the main, most sub-schemas are called by the "copy" command.
Schemas, rules and features in SAP use the following line editor commands. This allows you to move, delete,
copy and insert lines. All the commands are entered in the area used for the line numbers. Overwrite any of the
numbers with the commands shown below. For the commands using 1 letter - hit the return key once you have
entered the letter. For the commands using 2 letters - hit the return key after the first 2 letters have been entered
or after both sets have been entered.
The most commonly used commands are:
Line Command Description

D Deletes a line

I Inserts a line

M Moves a line

C Copies a line

322
 DD Indicates the start of a block to be deleted

DD Indicates the end of a block to be deleted

CC Indicates the start of a block to be copied

CC Indicates the end of a block to be copied

MM Indicates the start of a block to be moved

MM Indicates the end of a block to be moved

Once you have chosen the block to move or copy, you need to show where to move or copy it to in the
schema. The following commands indicate where you can copy or move the lines to.
Line Command Description

A Places the block after the chosen line

B Places the block before the chosen line

Remember when calling the PCR from the schema: GEN means that the wagetype is **** i.e. you haven't
specified one and NOAB means that it will look at any EE Sub-Grouping. If you want the rule to use specific
wage types or groupings, then leave either blank.
Use the print option and VAR (PAR 2) in the schema to output the variable table during processing.
Position is very important for schemas. Look to see where a similar piece of processing has taken place. If in
doubt, place the rule after the similar data has been read and processed.
Commonly used Functions
Function Description

PIT Process Input Table

PRT Process Results Table

COPY Calls a schema placed in PAR1.

BLOCK Defines the start and end of a nested node

IF/ELSE/ENDIF The schema is processed if the condition is fulfilled

Pxxx Processes the information held in infotype xxxx.

Actio calls a PCR. It is processed, irrespective of whether the wage type

ACTIO
exists or not.

Commonly used Parameters

Parameter Description

GEN Process any wage type

9000 Processes only wage type 9000

323
 NOAB Process for any EE sub-group groupings

1 Processes the rule only for EE sub-group grouping of 1

Payroll PCR's

Transaction Code: PE02

Menu Path:
Human Resources Payroll Europe Great Britain Tools Maintenance Tools Rules

Commonly used operations in payroll configuration

Operation Description

This covers all the remaining entries not already specified. If you leave the line
* blank for the operation then the WT is dropped. Remember you always have to
have an option for * in your PCR.

Cumulates the wage type into the relevant cumulation (/101...) and
ADDCU
valuation(/201...) wage types

From the IT, Number and Amt are cumulated into the OT. Blank is OT whilst E
ADDNA *
refers to the RT.

ADDNA 4067 Current Num and Amt are added in to wage type 4067.

This operation is very similar to ADDWT. The only difference is that it writes the
ADDWSE9N03
value to table V0 as well

ADDWSI* Store the current wage type in the IT.

ADDWT * Store wage type in IT/OT

All the current values for amt, num and rte are added to the values that are
ADDWT 1103
currently held in wt 1103

Adds the current wage type to the variable table as T - which can be used at a
ADDWT&T
later stage

The values in the wage type are copied to the previous employer table VAG -
ADDWTA*
called in the rules XDPI, XDPR & XDPT

ADDWTC* The values in the current wage type are added into the CRT

The values in the current wage type are added into the CRT for the technical
ADDWTC/101
wage type /101

ADDWTD* The values in the current wage type are added into the Difference table DT

ADDWTD/551 The values in the current wage type are added into the difference table DT for

324
 the technical wage type /551

ADDWTD/APO Add the current wage type to the difference table (DT)

ADDWTE Store amount in Results Table (RT) - difference with line below

ADDWTE* Add the current wage type to the results table RT

ADDWTE/101 Add the current wage type to the results table as /101

ADDWTH/201 Add the current wage type to the old results table (ORT) as wage type /201

ADDWTI* Add the current wage type to the input table IT

The values in the current wage type are added into the input table IT for the
ADDWTI/101
technical wage type /101

ADDWTL* Add the current wage type to the results table last payroll (LRT)

ADDWTN Used in XLON

ADDWTN/LRP (Loans - XLON)

ADDWTW Add the current wage type to the wage maintenance table

Subtract amount field from wage type 9023 from Table IT (if wage type 9023 is
AMT- 9023
available.)

AMT%33.33 Multiply the amount by 33.33%

AMT%KSAPRO Multiply the amount by the value SAPRO held in table T511k

AMT-& T Amount minus the value held in variable T

AMT*-1 Amount multiplied by negative 1

AMT*12 Multiply amount by 12

Multiply the amount by the constant GENAU held in table T511k. GENAU is
AMT*KGENAU used to factor up by 4 or 5 factors of 10 to avoid the issue of errors caused by
rounding.

AMT-.04 Subtract 0.4 from the amount field

AMT/2 Divide the amount by 2

AMT/KGENAU Divide the amount by the factor GENAU held in the constants table T511k

AMT/KPKWPR Amount divided by the constant PKWRP held in table T511K

AMT/KZF001 Amount is divided by constant ZF001 from table T511K

AMT? * Compare the value held in the amount field for all wage types

325
AMT? /GPY Compare the value held in the amount field for wage type /GPY

AMT?& ZAPR Compare the value held in the amount field against the constant ZAPR

AMT?0 Compare the value held in the amount field against 0

Compare the amount against the value of the amount held in the results table
AMT?E /167
RT for wage type /167

AMT?IGRUEB Compare the current amount against the limit held for the bank transfer

AMT+ /564 Add the amount from wage type /564 from the IT

Add amount field from wage type 0001 from Table IT (if wage type 0001 is
AMT+ 0001
available.)

Add amount field from wage type 9013 from Table IT (if wage type 9013 is
AMT+ 9013
available.)

Add the value held in the variable ZSAP to the amount for the current wage
AMT+& ZSAP
type being processed

AMT+E 910B Add the current amount to the RT and place in wage type 910B

AMT+O /ZPO Add Amt from wage type /ZPO into VORT (Summarised ORT)

Checks whether the currently held amount is less that that held in the wage
AMT< /562
type /562

AMT= * This sets the amount = zero for the wage type in question

Store the value in the amount field of wage type /111 in the amount field of
AMT= /111
wage type 2110

Store the value in the amount field of wage type 1000 in the amount field of
AMT= 1000
wage type 2110

Let the amount equal the value held in the BETRG (amount) field for the wage
AMT= BETRG
type in question

Reset the amount on wage type xxxx to that held in the value for KWWR held
AMT= PKWWR
in T511K

AMT= PLANS Sets the amount = position number

AMT=& /426 Set the amt = amt held on technical WT /426

Reset the amount on wage type xxxx to that held in the temporary wage type
AMT=& TASA
TASA

AMT=0 Let the amount equal zero

326
AMT=A * The amount is set to the value held in the table VAG - previous employee data

AMT=E * Lets the Amt = the Amt held for the current wage type in the RT

AMT=E /167 Lets the Amt = the Amt held for technical wage type /167 in the RT

AMT=KSAPLR Set the amount = the value SAPLR held in table T511k

Lets the Amt = the Amt held for the current wage type in the LRT - last result
AMT=L *
table

AMT=L /561 Lets the Amt = the Amt held for the wage type /561 in the LRT - last result table

Add the amount value in technical loan wage type /LBB (loan balance) to
AMT=N /LBB
specific loan balance wage type

Add the amount value in technical loan wage type /LOP (loan payment) to
AMT=N /LOP
specific loan payment wage type

Add the amount value in technical loan wage type /LRP (loan repayment) to
AMT=N /LRP
specific loan repayment wage type

Lets the Amt = the Amt held for the wage type /561 in the OCRT - old
AMT=Q /GPY
cumulative result table

AMT=ZERO Reduce the value in the amount field to zero

"Maximum formation: The greater value of * and the current value of the AMT
AMT>*
field is determined and written to the current AMT field."

AMT-1 Multiply the amount by -1 - I think this should be subtract 1 from the amt

If the amount field value is smaller than 50, it is retained. Otherwise it is set at
AMT50
50 (forming a minimum amount).

AMT-E /167 Subtract the Amt value held in the RT for /167 from the currently stored amount

AMT-K43301 Take the value held against payroll constant 43301 from the annual salary

Subtract the Amt value held in the ORT for /167 from the currently stored
AMT-O /167
amount

Amt for the current wage type less the value held in the RT for 9019 (Results
AMT-R 9019
wage types using exact splits)

AMTS /564 Subtraction to zero - the value cannot be less than zero.

AMTS* Subtraction to 0 (not negative) for the current wage type

AMTS* 9013 Subtraction to 0 (not negative). Current wage type less 9013

327
 Subtraction to 0 (not negative). Current wage type less Amt held in the RT for
AMTSE 9043
wage type 9043

"Sets the recipient data for bank transfers. Can only be run after bank transfer
data has been read from an infotype. Data on wage type and amount are
BTREC /558
transferred from the current fields (OT) and retained in the transfer table
together with data on the recipient of the record last read."

CMPER 0510 Compares the current amount with that held for period 10 in year 05.

D Expect a decision in this line

The amount field value is compared with 0, and the result ('>', '=' or '<') is
D AMT?0
placed in the variable key.

D VWTCL 01 Make a decision on processing class 01

DIVID ANR Divide the amount by the number and store the result in the rate field

Divide the value in amount field by the value in the rate field and put the result
DIVID ARA
in the amount field

DIVID ARR Divide the amount by the rate and store the answer in the rate for the wagetype

DIVID NRN Divide the number by the rate and store the answer in the number field

ELIMI * Eliminate all splits

ELIMI A Eliminate splits - work center period (WPBP)

ELIMI K Eliminate splits - cost accounting

Eliminate the splits for cost accounting, alternative payments and variable
ELIMI KTX
assignment

ELIMI R Eliminate splits - employee sub-group grouping for PCRs

ELIMI T Eliminate splits - alternative payments (ALP)

ELIMI U Eliminate splits - bank transfer (BT)

ELIMI X Eliminate splits - variable assignment

ELIMI Y Eliminate splits - absence assignment

ELIMI Z Eliminate splits - time unit

ERROR Processing terminates for the current employee

Restore the original values for the amount - i.e. The values that were held for
FILLF A
the amount field in the WT before any processing in this rule

FILLF N Restore the original values for the number - i.e. The values that were held for

328
 the number field in the WT before any processing in this rule

Restore the original values for the number, rate and amount - i.e. The values
FILLF NRA that were held for the number, rate and amount fields in the WT before any
processing in this rule

Restore the original values for the rate - i.e. The values that were held in the
FILLF R
WT before any processing in this rule

"GB specific processing of AWE operation GB specific operation to overwrite

GBVRT the average RATE of wage type /MAE in table RT in case of a retro
calculation."

GCY ZUM2 Call PCR ZUM2

GCYGXALQ Calls PCR XALQ for all wage types - sets wage type to ****

GEWRT Elimination of WPBP split in the RT

GSXP2 New Changes Across End of Year solution active for GBSXP phase 2

Check on Implementation Date of AVERA for SxP AWE. Called in GG70 and
GSXPD ensures that the old and new technical wage types for averages don't both
exist.

Evaluates the status of the LRT table. Processing is only continued if the
LRTST Y
previous month falls in the current year.

MEANV 01 Calculation of averages for 01 (from table T511A)

Calcualation of averages for 03 (from table T511A) - not sure what the G
MEANVG03
implies

Can use a 5 character message. Comes up whether the log is turned on or off.
MESSGxxxxx
Can be used as a customised error message.

Sets the modifier for Wage type generation (T510S) to 02 as the employee
MODIF 1=02
grouping

Sets the modifier for Constant valuations (T510J) to 01 as the employee

MODIF 2=01
grouping

MODIF A=01 Sets the modifier for the absence valuation rule (T544C) to 01

Multiply the amount by the number and store as the number field for the wage
MULTI ANN
type

Multiply the value in number field by the value in the rate field and put the result
MULTI NRA
in the amount field

Process the next line. Placing an * in the last column in the operation column
NEXTR has the same effect as "nextr". Remember to put a letter or number in the next
line under the NL column.

329
 Continuation line. A...Z followed by 0...9 Don't forget to put in the letter following
NEXTR A
the NEXTR in the continuation line of the next line.

Continuation line. A...Z followed by 0...9 Don't forget to put in the letter following
NEXTR B
the NEXTR in the continuation line of the next line.

Multiply the value in the number field by the value held against the capacity
NUM* BSGRD
utilization level on infotype 0008

NUM*1.5 Multiply the value in the number field by 1.5

NUM/100 Divide the value in the number field by 100

NUM?0 Test the value in the number field against 0

Add the value in the number field of wage type 3710 to the number field in the
NUM+ 3710
WT being processed

Adds the number held in the temporary variable ZNIL to the currently held
NUM+& ZNIL
value for the number

NUM+39 Add a value of 39 to the number field

Add to the NUM value from wage type 3000 held in the CRT table - to the NUM
NUM+C 3000
value of the WT being processed

Adds the number held in technical wage type /852 to the currently held value
NUM+E /852
for the number

Adds the number from the partial period parameter for the paid absence
NUM+TSAP** measured in working hours for xx is the sum of all paid absences (totalled over
all classes)

NUM= 3000 Set the current NUM to the value held in wage type 3000

NUM= ANZHL Transfers the value of the ANZHL field to the number field.

NUM= BWGRL Sets the number equal to the valuation basis per hour

NUM = Capacity utilization level from P0007 (called record layout fields in SAP
NUM= EMPCT
Help)

NUM= PLANS Sets the number equal to the position number of the employee

NUM= STDAZ Sets the number equal to the number of hours taken from IT 0007

NUM=& ZSHF Sets the number equal to the number held in the temporary variable ZSHF

NUM=0 Set the number field to zero

NUM=39 Store 39 in the number field

NUM=BJRSTD Sets the number equal to the position number of the employee

330
NUM=BTGSTD Sets the number equal to the daily hours worked by the employee

NUM=BWOSTD Sets the number equal to the weekly hours worked by the employee

NUM=E /SSP Set the NUM = the value of /SSP held in the results table

Sets the number equal to the working hours for the employee for the entire
NUM=GSDIVP
payroll period

Set the number = planned working time measured in working hours taken from
NUM=GSSOLL
the work schedule rule

NUM=TSAU** See part period parameter help (function PARTT)

NUM=TSAX** See part period parameter help (function PARTT)

NUM=TSDIVI See part period parameter help (function PARTT)

NUM=WOSTD See part period parameter help (function PARTT)

NUM=YCURPP Set the NUM = current payroll period (?)

NUM-51 Reduce the hours held in the number field by 51

Take away the number for technical wage type /845 held in the RT from the
NUM-E /845
currently held number

Current value in the number field less the total working time measured in
NUM-TSDIVP
working hours taken from the total working time in payroll accounting period

Evaluates operation indicator - used immediately after a database record has

OPIND
been read. Multiplies by -1.

OUTWPABART Load Work Center and Basic Pay Data - payroll area

OUTWPCTYMO Load Work Center and Basic Pay Data - country modifier

OUTWPPAYSB Decide which payroll accounting area the employee is in

OUTWPPERSB Load Work Center and Basic Pay Data - employee sub-group

OUTWPPERSG Load Work Center and Basic Pay Data - employee group

OUTWPPLANT Load Work Center and Basic Pay Data - personnel area

OUTWPPLTSC Load Work Center and Basic Pay Data - personnel sub-area

OUTWPSHIFT Load Work Center and Basic Pay Data - shift indicator

OUTWPTRFAR Load Work Center and Basic Pay Data - pay scale type

331
OUTWPWWEEK Load Work Center and Basic Pay Data - working week from IT 0007

PCY X05D* Runs PCR X05D for all employee subgroup groupings

PCY X93B Runs PCR X93B

PPPAR A Reads part period parameters: leavers during payroll period

PPPAR B Reads part period parameters: paid absences during payroll period

PPPAR E Reads part period parameters: new joiners during payroll period

PPPAR F Reads part period parameters: leavers on the first day of the next payroll period

Reads part period parameters: if the time unit for the payroll area is different to
PPPAR P
the time unit for the pay scale type and area

PPPAR R Reads part period parameters: is the employee is in an active work centre?

PPPAR S Reads part period parameters: basic pay changes during payroll period

PPPAR U Reads part period parameters: for unpaid absences in the period

PRINT Prints the IT

PRINT& WTG Prints WTG from the variable table

PRINTC Prints the contents of the CRT

PRINTE Prints the contents of the RT

PRINTL Prints out the contents of the old results table (LRT)

PRINTO Prints the summarised ORT (VORT)

R Employee work centre is inactive, therefore do nothing

You want to know if there is an entry in table T51P1 with indicator 10 for the
R51P1?10N
current IT wage type. If an entry is found, processing should be continued.

You want to read the entry in table T51P1 with indicator 01 for the current IT
R51P1=01R
wage type, and store it in the OT table. If an entry is found it should be rejected

"Operation R51P6 reads an entry from table T51P6. This table determines the
R51P6A characteristics of the deduction wage types. The value of the arrears
characteristic should be placed in the variable key."

RE510T Read Pay Scale Table - group and level

RESET * Sets the splits back up again - has the opposite effect to the ELIMI * operation.

RESET 1 Resets the first national split (/SI)

332
 Resets the amount and the rate - is the opposite of ELIMI. Reset * - resets all
RESET AR the split indicators. Give the meaning of all the other variables elsewhere in the
document.

RESET KR Resets the cost accounting and employee subgroup grouping values

Resets R - is the opposite of ELIMI - resets the employee subgroup groupings

RESET R
for the employee

RETRO Checks if the payroll run is a retroactive accounting run

ROUND Rounds off the AMT field - see SAP help for specifics

ROUND 005 Rounds the AMT field up so that it is divisible by 005

ROUND +100 Rounds the AMT field to the next available number

ROUNDA Rounds off the NUM field - see SAP help for specifics

ROUNDB Rounds off the RTE field - see SAP help for specifics

ROUNDG Rounds off the AMT field - see SAP help for specifics

RTE%33.33 Multiply the value held in the rate by 33.33% - so effectively multiply by .3333

RTE-& HALF Subtract the value held in the constant HALF from the rate

Multiply the value held in the rate by the capacity utilization level field on
RTE* BSGRD
infotype 0008

RTE*-1 Multiply the rate by negative 1 - effectively switch the sign for the value

RTE*100 Multiply percentage held in rate field by 100

RTE*KGENAU Multiply the rate by the constant GENAU held in table T511k

RTE*KGENAU Multiply the value in the rate field by the payroll constant GENAU (10,000).

RTE/100 Rate divide by 100

RTE/GKDIVI RTE/ total working time in calendar days

RTE/TADIVI RTE/ total working time in working days

RTE/TASOLL RTE/ planned working time measured in work days

RTE/TKDIVI RTE/ Total working time measured in calendar days

Divide the value in the rate field by the worked hours for pay period being
RTE/TSDIVI
processed.

RTE/TSDIVP RTE/ total working time measured in working hours

333
 Check to see how the current rate compares against the value held in the
RTE?& VLBS
temporary variable VLBS

RTE?0 Check to see how the current rate compares against a value of zero

RTE+ 1001 Adds the rate held in wage type 1001 to the currently held rate

RTE+& MM Adds the rate held in the variable MM to the currently held rate

RTE+* Adds the current rate to the IT

RTE+100.00 Adds a value of 100 to the currently held rate

RTE+BBETRG Add the amount from table to the currently held rate

Add the unpaid absences measured in calendar days for counting class 10
RTE+TKAU10
from table T554C

RTE= 1001 Set the rate equal to the value held in the rate field for wage type 1001

RTE= BETRG Set the rate equal to the amount

RTE= BSGRD Set the rate equal to the capacity utilization level held on infotype 0008

RTE= BWGRL Sets the rate equal to the valuation basis per hour

RTE=& AB Sets the rate equal to the value held in the temporary variable AB

RTE=0 Set the rate field to zero

RTE=10000 Store 10000 in the rate field of wage type xxxx

RTE=BBETRG Set the rate equal to the amount pulled from the table

RTE=BWOSTD Sets the RTE equal to the weekly hours worked by the employee

RTE=GKSOLL Set the rate as the planned calendar days

Store the value held against payroll constant 30551 in table T511 in the rate
RTE=K30551
field of wage type xxxx

RTE=KGENAU RTE set to the value of GENAU from table T511K (default set at 10 000)

RTE=TADIVP RTE = Total working time measured in working days

RTE=TASOLL RTE = planned working time measured in work days

RTE=TKDIVI RTE = Total working time measured in calendar days

Store the planned calendar days in the rate field of the wage type being
RTE=TKSOLL
processed

RTE=TSAU07 RTE = unpaid absence measured in working hours for counting class 07

334
RTE=TSDIVP RTE = total working time measured in working hours

RTE=TSSOLL RTE = planned working time measured in working hours

RTE=ZERO Reduce the value in the amount field to zero

Rate subtract the part period unpaid absences in calendar days for all unpaid
RTE-GKAU**
absences (totalled over all absence counting classes)

Rate subtract the part period unpaid absences in working days for all unpaid
RTE-TAAU**
absences (totalled over all absence counting classes)

Take away any unpaid absence, in calendar days, from the current rate
RTE-TKAU**
(totalled over all absence counting classes)

Take away any unpaid absence, in calendar days, from the current rate (for
RTE-TKAU20
absence counting class 20)

Take away any unpaid absence, in worked hours, from the currently held rate
RTE-TSAU**
(totalled over all absence counting classes)

SCOND=F IF The condition for function IF is false

SCOND=T AL Set condition for Function LPBEG when the condition is true

SCOND=T IF The condition for function IF is true

SCOND=T IF The condition for function IF is true

SETIN A=01 Set the work center - basic pay split for the wage type as 01

SETIN R=1 Set the ESG for PCR as 1

You want to set X with number 01 as a variable split; the number of the split is
SETIN X=NX
to be increased by 1 by every call.

Status field 2 which is valid at the start of the in-period is entered in the variable
STATU 2P
key.

SUBRC?SET The return code set in the second example must be evaluated.

SUBRC=0 The internal return code is set to the value 0

SUBWT * Subtracts the current wage type - effectively changing the sign of the NRA.

SUBWT 1025 Subtracts the current wage type (signs change) and stores it as 1025.

SUBWT&ZREG Subtracts the current wage type and stores it as a temporary variable ZREG.

SUBWTD* Subtracts the current wage type (sign change) of the NRA in the difference

335
 table (DT)

Subtracts the current wage type and stores it in the difference table (DT) as a
SUBWTD/551
temporary variable ZREG.

Flicks the sign for NRA of the currently processed wage type and stores it in
SUBWTE
the RT

Subtracts the current wage type (sign change) of the NRA and stores in the
SUBWTE*
results table (RT)

Flicks the sign for NRA of the currently processed wage type and stores it in
SUBWTE/121
the RT as technical wage type /121

Flicks the sign for NRA of the currently processed wage type and stores it in
SUBWTI*
the input table (IT)

Flicks the sign for NRA of the currently processed wage type and stores it in
SUBWTI/101
the input table (IT) as technical wage type /101

TABLE 503 Table query on employee groupings / areas

TABLE 508A Table query on shifts / time groups

TABLE 510P Table query on premium table

TABLE 512W Table query on valuation of wage types

TABLE 528B Table query on positions table in PA

TABLEALP Table query on the Alternative Payments table

TABLEP0014 Table query on data held in infotype 0014 - recurring payments and deductions

TABLEP0015 Table query on data held in infotype 0015 - additional payments

VAKEYALZNR Place in the variable key - Y/N alternative payment

VAKEYAUFKZ Place in the variable key - extra pay indicator for overtime

VAKEYBNKSA Place in the variable key - variable keys are held in a certain table

VAKEYBNKSA Place in the variable key - type of bank details P0009

VAKEYLGART Store in the variable key the wage type

VAKEYLNCLS Place in the variable key - loan type

VAKEYLNTPY Place in the variable key - loan type P0045

VAKEYLNTYP Place in the variable key - loan type P0045

VAKEYPAYTY Place in the variable key - payroll type

336
VAKEYPRAKN Place in the variable key - premium indicator time ITs

Place in the variable key - variable key is filled out based on the values in the
VAKEYTGRLE
TRFGR and TRFST fields from the current PZ record

VAKEYVERSL Place in the variable key - clearing key for overtime

VAKEYZEINH Place in the variable key - time unit

VAKEYZLSCH Place in the variable key - payment key for bank transfers

VALBS? The system checks to see whether a valuation base exists

The system checks if a valuation basis is for the current wage type in table
VALBS?0
T512W. (That the "0" line of view V_T512_B is read).

The current wage type is evaluated with the valuation basis that is entered for
VALBS0
the current wage type itself. (That is, the "0" line of view V_512W_B).

The system multiplies an entry that already exists in the RTE field for the
current wage type with the percentage rate from a line 0 of view V_512W and
VALBS0 *
then replaces the wage type names of the current wage type with the name of
the wage type from the same line in V_512W.

VALBS0 B Same as VALBS0 * with the exception that the data from infotype 2010 is used.

Replaces the current wage type with the statement wage type that is entered in
VALBS1 table T512W for the second wage type derived from the current wage type, and
then you want to valuate this using the corresponding valuation basis.

VALEN 2 Sets the length of the variable key to 2

VALEN 3 Sets the length of the variable key to 3

VAOFF 2 Variable offset - set here to 2. The system with then ignores the first 2 digits.

VARGBINDBW Place the table field "indicator for indirect valuation" in the variable key

VARGBPRAKN Place the table field "premium number" in the variable key

Place the table field "ES grouping for collective agreement provision" in the
VARGBTRFKZ
variable key

VWTCL 64 Interrogate processing class 64

WGTYP? Usually part of a decision - where the wage type is queried

WGTYP=* Passes through the wage type as unchanged

WPALL?LAST Decide if employee has had a pay change in pay period & if the one being

337
 processed is the last

Operation WPBPC distributes the amount of the current wage type to the active
WPBPC
WPBP periods in the payroll period.

This operation splits the amounts but does not distribute them to the different
WPBPCW
periods

Z Expect to call another PCR in this line

ZERO= AN Sets the AMT and NUM to zero

ZERO= RNA Set the values for the rate, number and amount equal to zero

ZERO=& ABCD Initialises the variable ABCD

ZERO=NRA Sets the NUM RTE and AMT to zero

Wishing to retrieve previous payroll period results to be used in a PCR?

You can do so by using the operation IMPRE with parameter NN (NN periods before current payroll period). Also
have a look at the documentation of IMPRE.
An example in using this operation is as follows (reading the period 6 months ago):
D ZERO = NRA IMPRE 6 SUBRC?IMP *
0 AMT = O 1001SETIN A=01SETIN R=3 ZERO= NR ADDWTI1001

338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
Customized- SCHEMA’S:

357
INAL:

INAP:

358
INEI:

INLN:

YNC0:

359
ZNNC:

360
SAP Overview

1. Explain the structure of the client/server framework.

2. Project Implementation Tools

1. What is the IMG?

361
2. What is a project IMG?

3. Basics of Human Resources

1. What are the most important processes supported in Human Resources (HR)?

2. What are the most important structures in HR?

3. What is meant by Employee Self-Service?

4. What ways are there to select an Infotype?

5. How do you hire a new employee?

6. Which steps make up the payroll process?

7. Why is there a cross-application time sheet?

What are the possible target components?

8. What is the purpose of time evaluation?

9. Which reporting tools do you know of?

10. How is the recruitment component integrated with the other HR components?

11. What is an applicant action?

12. What is the difference between qualifications and requirements?

13. What is the difference between career planning and succession planning?

What is a development plan?

14. Describe the day-to-day activities in Training and Event Management.

15. What is the appraisal system component used for?

16. What are the main functions of Compensation Management?

17. What personnel cost planning methods are there in SAP HR?

18. Which Infotypes do you need to implement Travel Management?

4. Organizational Management

1. What are plan versions used for?

2. What are the basic object types?

3. What is the difference between a job and a position?

4. What is the difference between an organizational unit and a work center?

5. Where can you maintain relationships between objects?

362
6. What are the main areas of the Organization and Staffing user interfaces?

7. What is Expert Mode used for?

8. Can you create cost centers in Expert Mode?

9. Can you assign people to jobs in Expert Mode?

10. Can you use the organizational structure to create a matrix organization?

11. In general structure maintenance, is it possible to represent the legal entity of

organizational units?

12. What is the Object Infotype (1000) used for?

13. What is the Relationships Infotype (1001) used for?

14. Which status can Infotypes in the Organizational Management component have?

15. What is an evaluation path?

16. What is Managers Desktop used for?

17. Is it possible to set up new evaluation paths in Customizing?

18. Which situations require new evaluation paths?

19. How do you set up integration between Personnel Administration and Organizational

Management?

5. Master Data

1. Which elements make up the enterprise structure?

2. Which elements make up the personnel structure?

3. Which elements make up the organizational structure?

4. Which criteria play a role in establishing these structures?

5. Which control features are controlled using the personnel subarea?

6. Which control features are controlled using the employee subgroup?

7. What is a payroll area?

8. What is an Infotype?

9. Which criteria determine payroll areas?

10. What is the organizational key used for?

11. In which Infotype are administrators defined?

12. Why are administrators defined?

363
13. What can features be used for?

14. What is the connection between Planned Working Time (Infotype 7) and Basic Pay

(Infotype 8)?

15. Which ways are there to define default values for the pay scale area and pay scale type? 16.
What is the employee subgroup grouping for collective agreement provisions used for? 17. Where are
pay scale groups and pay scale levels defined?

18. How are wage types created in the SAP R/3 system?

19. Can all wage types be entered into all Infotypes?

20. What does the input permissibility of a wage type depend upon?

21. What is the personnel subarea grouping for primary wage types used for?

22. What is the employee subgroup grouping for primary wage types used for?

23. What ways are there to valuate wage types? Where are wage type valuations defined? 24. How
can you evaluate wage types indirectly?

25. How can you define default wage types for the Basic Pay Infotype?

26. What ways are there to perform pay scale reassignments?

27. What ways are there to perform standard pay increases?

28. What is the difference between the simple and extended pay increases?

29. Can several personnel actions be performed on the same day?

30. What is the Additional Actions Infotype used for?

31. If an employee leaves the enterprise, are all Infotypes delimited?

32. Which control options do you have for Customizing when configuring Infotypes?

33. Can a screen in HR data consist of several Infotypes?

34. Which ways are there to modify screens in Customizing?

35. What is an Infotype menu and what is its purpose?

36. What is an info group? What is a personnel action?

37. How can a personnel action change the status feature of an employee in Infotype 0000? 38. How
are personnel actions and dynamic actions linked?

6. Authorizations

1. What is a role and what is it made up of?

2. How are the authorizations in a role maintained?

3. Are authorization objects or profiles assigned to users?

4. Which authorization object can you use to control an employee’s access to his or her own

364
 personal data?

5. What are the main advantages of the Profile Generator?

6. Can roles and their authorization profiles be assigned to a user for a limited time period?

7. How do you create structural profiles?

7. Payroll

1. How does the system know when to trigger retroactive accounting for a particular

employee?

2. How is the earliest retroactive accounting date determined for an employee?

3. What is the payroll control record used for?

4. Is the exact date of the payroll period for an employee determined by the payroll area or

the payroll control record?

5. What activities are possible when the payroll control record is set to “Released for Payroll”? 6. Is it
possible to branch directly from the payroll log to master data and time data

maintenance?

7. What is Matchcode W used for?

8. What effect does grouping employee subgroups have on personnel calculation rules?

9. Can you evaluate payroll results using SAP Query/Ad Hoc Query?

10. What steps are required to post payroll results to Accounting?

11. Can a posting run be deleted?

12. Where do you specify whether an employee is paid in cash or whether the money is

transferred to a bank account?

8. Time Data

1. What are the basic concepts for recording time data?

2. What steps are required to set up work schedules?

3. Can you define your own public holidays?

4. How do you define which public holiday calendar is valid for an employee?

5. Which characteristics does a public holiday class blank have?

6. Is there an employee subgroup grouping for daily work schedules?

7. What is a variant of a daily work schedule?

8. Is there an employee subgroup grouping for time quotas?

365
9. What ways are there to define breaks within a break schedule?

10. Which characteristics does a daily work schedule with daily work schedule class 1 have? 11.
Which elements make up a period work schedule?

12. Which characteristic does a day with day type 1 have?

13. Which ways are there of representing part-time work in the SAP R/3 system?

14. Which ways are there of representing substitutions in the SAP R/3 system?

15. What is the difference between absences (Infotype 2001) and attendances (Infotype

2002)?

16. What is an absence quota? Give examples.

17. What is the difference between a validity interval and a deduction interval for time quotas? 18. You
need to deduct an absence from a quota. Which Customizing settings are required? 19. Should a
quota be assigned directly to an absence?

20. What is the remuneration Infotype used for?

21. What are counting rules used for?

22. Can you set up default values to create absence quotas?

23. Can you generate absence quotas?

24. What is the schema TQTA used for?

25. What ways are there of entering information for Controlling when recording time data in

the Time Management Infotypes?

9. Reporting in Human Resources Management

1. Which reporting tools are available in Human Resources Management?

2. Is the Business Information Warehouse part of the SAP R/3 system?

3. What is HIS?

4. Where do you find standard reports in HR?

5. Can you also evaluate cross-client data with standard reports?

6. Can customer-specific reports be incorporated in the Managers Desktop?

7. What is a logical database used for?

8. Which logical databases exist in HR?

9. What is a user group, what is an infoset and how are the two related?

10. What is a field group? Give examples from HR.

11. What are selection and output fields?

366
12. What can an Ad Hoc Query be used for?

13. What are the steps for configuring an SAP Query?

14. What are payroll Infotypes used for?

E-Recruitment Configuration Guide

Contents

1. System Prerequisites.........................................................................361
2. User Administration..........................................................................363
3. Business Partner Configuration.............................................................368
4. Workflow Configuration.....................................................................378
5. Search Engine Configuration................................................................384
5. Periodic services..............................................................................395
6. SAP ECC Integration..........................................................................398
7. Basic Settings..................................................................................402
8. Talent Warehouse............................................................................409
9. Applicant Tracking............................................................................432
10. Requisition Management...................................................................448
11. Additional Tools.............................................................................454
12. ICM (Internet Communication Manager) Tasks.........................................457

367
1.1.2 1. System Prerequisites

1.1. Required Components

 Software Component ERECRUIT 604

 SAP NetWeaver 7.0, Enhancement Package 1
o Enterprise Portal
o TREX 7.00.48.00 or higher.
Alternately, TREX 7.10 can be used from EhP4 onwards.

TREX 7.10 does not support Oracle platform, supports only Linux and Windows
based systems.

o ADS (Adobe Document Server) – for certain functionality such as data Overviews
o SAP NetWeaver Virus Scan Interface (NW-VSI) compatible software, optional
o Adobe Forms 8.1
 ERP 6.0 EhP4 (Manager Involvement)

1.2. Latest versions of ERecruiting

 Install Enhancement Package 4,

 Activate Business Function HCM, SAP E-Recruiting 2 - HCM_ERC_CI_2 (Transaction SWF5).

Pre-requisite for business function HCM_ERC_CI_2:

1. Activate business function HCM, SAP E-Recruiting 1- HCM_ERC_CI_1

2. Activate business function HCM, SAP E-Recruiting Search Functions 1 - HCM_ERC_SES_1

1.3. Portal Content for SAP EhP4 for SAP ERP 6.0

Business Package Name Software Component Version Role

BP for Recruiter BP ERP RECRUITER 1.40 Recruiter

BP for E-Recruiting Admin. BP ERP RECRUITING ADMIN 1.40 E-Recruiting

Administrator

 To install portal content (Business Packages) for E-Recruiting, you must install the following
product instances and software components.
 Product instance SAP NW - EP Core is required as a basis. As part of SAP ERP 6.0 SAP NW –
EP Core based on SAP NetWeaver 7.0 – Usage Type Application Server Java. As of

368
 enhancement package 4 for SAP ERP, the usage type is available on enhancement package 1
for SAP NetWeaver.

 Always refer to the latest version of the Master Guide - SAP enhancement package 4 for SAP
ERP 6.0 which contains important information about the installation sequence and the
components to be installed. It links to all other documents that are required for the
implementation of a specific scenario. (http://service.sap.com/erp-inst)

369
1.1.3 . User Administration

IMG Path : SPRO -> SAP E-Recruiting -> Technical Settings -> User Administration
Description: This IMG activity is used for creation and maintenance of ERecruiting specific users,
roles and

User categories. The logical sequence is –

- Creation of authorization profiles/roles

- Creation of ERecruiting specific special users
- Assignment of authorization profiles to reference users
- Assignment of reference users to each ERecruiting end user in SU01.
- Optionally, grouping the internal end users in user categories.

2.1. Creation of Authorisation Profiles

IMG Path : SPRO -> SAP E-Recruiting -> Technical Settings -> User Administration -> Create User
Profiles

Transaction: PFCG

All ERecruiting specific standard roles have prefix as “SAP_RCF”.

Copy the standard roles provided by SAP to custom roles. This is done to keep the standard roles
untouched and refer at a later stage in case of issues in the custom roles.

We have configured the roles with prefix as “ZER”.

370
We are using roles ZER_RECRUITER_EHP4 and ZER_BUSINESS_ADMIN_EHP4 for recruiter and
administrator respectively instead of roles ZER_BUSINESS_ADMINISTRATOR and ZER_RECRUITER
which become obsolete on activation of WebDynpro versions in EhP4.

2.2. Creation of Special users

IMG Path : SPRO -> SAP E-Recruiting -> Technical Settings -> User Administration -> Create
Special Users

Transaction: SU01

Users can be grouped in 3 categories:

1. Reference users
2. Communication Users
3. Service Users
4. System users
Reference users are used as templates for assigning security authorizations. They are not dialog
users but are assigned to dialog users. The dialog users inherit all authorizations of the assigned
reference user.

Communication users are used for remote communication between 2 systems. These are not dialog
users and must be used purely for communication purposes in the system.

In ERecruiting framework, communication users are used for connecting ERecruiting system and the
Content Server.

Service Users enables system access for unnamed users. In e-recruiting these are used for
unregistered candidates (e.g., RCF_UNREG). Certain BSP/Webdynpro services are accessible to
candidates who are not registered applicants. For such services, the service user RCF_UNREG is
assigned against username in transaction SICF. This eliminates the need to key in username
password when the service is instantiated on the internet.

System Users

System users are required during the execution of specific SAP processes. ERecruiting requires
system users in the form of workflow user WF-BATCH. All background workflow tasks are executed
using the WF-BATCH id.

Special users do not exist in the standard system. They need to be created.

Reference User User Type Role to be assigned Role Description

371
RCF_ADMIN Reference ZER_BUSINESS_ADMIN_EHP4 Administrator

RCF_CONTENT Communication ZER_CONTENT_SERVER Access to Search Engine

RCF_CAND_EXT Reference ZER_EXTERNAL_CANDIDATE External Candidate

RCF_CAND_INT Reference ZER_INTERNAL_CANDIDATE Internal Candidate

RCF_MANAGER Reference ZER_MANAGER Manager

RCF_RECRUIT Reference ZER_RECRUITER_EHP4 Recruiter

RCF_REQUEST Reference ZER_REQUISITION_REQUESTER Requester (not used)

RCF_TC Reference ZER_TALENT_CONSULTANT Talent Consultant (not used)

RCF_UNREG Service ZER_UNREGISTERED_CANDIDATE Unregistered Candidate

Creation of Sample Reference User RCF_CAND_INT is shown below:

Go to SU01, enter RCF_CAND_INT in User field and click the New icon.

Enter the required details.

372
Select the User Type as “Reference”. Also enter the password.

For reference users, once the password is set, it shows a “Deactivated” status as shown below:

Assign the custom internal candidate role created in the above step.

Similarly, create other reference users.

373
2.3. Define Roles in ERecruiting

IMG Path : SPRO -> SAP E-Recruiting -> Technical Settings -> User Administration -> Create
Special Users

View: T77RCF_ROLE

Here we map the special users against the user categories to be used.

The reference users need to have exactly same name as above. In case of a requirement which
demands a different reference username, the names in the “Reference User” column should be
updated accordingly.

374
1.1.4 3. Business Partner Configuration

The component SAP Business Partner enables you to create and manage business partners centrally.
You can create a business partner in different business partner roles, and during the course of the
business relationship the business partner can assume other business partner roles. No new data has
to be created each time, meaning that redundant data creation and retention is avoided, and there
can be no inconsistencies.

In E-Recruiting, the Business Partner concept is used for maintaining personal data of all entities
involved (candidates -> employees -> candidates) and for the addresses of the various branches of
your company.

IMG Path: SPRO -> IMG ->Cross Application Components -> SAP Business Partner

375
3.1. Define Business Partner Roles

IMG Path : SPRO -> Cross-Application Components -> SAP Business Partner -> Business Partner ->
Basic

Settings -> Business Partner Roles -> Define BP Roles

View Cluster: BUPA_TB003

Description : In this IMG activity, you define business partner roles and its attributes. These
attributes show

effect in transaction BP used for business partner maintenance.

The roles that need to be configured are:

1. BUP003

2. RCFAGY

3. RCFBRA

4. RCFVEN

BUP003

376
To configure, choose the row and click on the detail icon .

The fields that need to be entered for each role are:

1. BP Role Cat.

2. Std. Assignment BP Role –> BP Role Cat.

3. BP View

The values in these fields should be:

1. BP Role Cat. – Same as BP Role (in this case, BUP003)

2. Std. Assignment BP Role –> BP Role Cat. – Should be Checked.

3. BP View - Same as BP Role

Follow the same procedure for remaining business partner roles.

3.2. Define Number Ranges for Business Partners

IMG Path : SPRO -> Cross Application Components -> SAP Business Partner -> Business

Partner -> Basic Settings -> Number Ranges and Groupings -> Define Number Ranges

377
Transaction: BUCF

Description : Here, you maintain the number ranges for business partners. Two number ranges, one
each for

internal and external number range should be defined. The external number range is
required

for business partners transferred from external systems.

No changes are required here. We are using the SAP delivered standard settings.

Ensure that the current number is set to 0.

3.3. Define Groupings and Assign Number Ranges

IMG Path : SPRO -> Cross Application Components -> SAP Business Partner -> Business Partner ->
Basic

Settings -> Number Ranges and Groups -> Define Groupings and Assign Number Ranges.

View : V_TB001

Description: The number range grouping determines the number range to be used during business
partner

378
 number generation.

Standard SAP delivered settings are used. No changes required.

3.4. Address Determination

IMG Path: SPRO -> IMG -> Cross Application Components -> SAP Business Partner -> Business Partner
-> Basic

Settings -> Address Determination

Description: Address determination describes the procedure with which the system identifies the

business partner address that is used in a particular business transaction.

The following steps are carried out consecutively until an address is found:

1. If there is a fixed address for a particular object (e.g. contract account in FI-CA)
and this

address still exists, it is used.

2. If an address type is assigned to the BP role in the implementation guide (IMG),

and at least

one address usage for it has been created, the standard usage for this address type
will be

used.

3. In all other cases, the standard address of the business partner is used.

379
Define Transactions

XXDFLT is the standard SAP delivered entry. No changes are required.

Define Address Types:

XXDEFAULT is the standard SAP delivered entry. No changes are required.

Assign Transaction to Address Type:

Assign the address type XXDEFAULT to transaction XXDFLT.

380
3.5. Forms of Address

IMG Path : SPRO -> IMG -> Cross Application Components -> SAP Business Partner -> Business

Partner -> Basic Settings -> Forms of Address.

View : V_TSAD3

Description: In this node, you maintain the forms of address for business partners.

These entries should be in line with the forms-of-address of Personnel Administration.

3.6. Data Origin

IMG Path : SPRO -> IMG -> Cross Application Components -> SAP Business Partner -> Business

Partner -> Basic Settings -> Data Origin

View : V_TB005

Description: The data origin type determines how the business partner data comes into the system.

381
Add the entry 0004 as shown below:

3.7. Name Formatting Rules

IMG Path : SPRO -> IMG -> Cross Application Components -> SAP Business Partner -> Business

Partner -> Persons -> Maintain Name Formatting Rules

View Cluster: NAMEFORMAT

Description : For business partners that belong to the category 'natural persons' the name
components are

stored in several different fields. Country-specific rules can be applied to format the
name components. If you do not state any specific rule, the standard setting applies.

382
We will be using Country “IN” and Format as “01”.

The components of this name format are organized as –

<Form of address> <first name> <middle initial> <last name>

Position should be in numeric integers. The order given in the "Position" determines how the name
of the business partner (candidate) will be concatenated in the system.

NOTE: 1. This transaction also should be done in both the HR and the E Recruitment systems, in

separate instance scenario.

3.8. Marital Status

IMG Path: SPRO -> IMG -> Cross Application Components -> SAP Business Partner -> Business

383
 Partner -> Persons -> Marital Statuses -> Maintain Marital Status

View : TB027

Description: Here you maintain the marital statuses for business partners

This completes the E Recruitment related configuration of Business Partners

384
1.1.5 4. Workflow Configuration
4.1. Workflow Auto-Customizing

Transaction: SWU3

Description : The activities performed in this transaction must be executed so that workflows can
be

executed. It provides a runtime environment to all workflows in the client.

Important: The user performing auto-customizing must have SAP_ALL authorizations and must
belong to SUPER user group.

Click “Configure RFC Destination” and click

The user WF-BATCH, if does not exist, is auto created with same authorizations as the current user.
Enter the password and click .

Now, click the main node in the tree “Maintain Runtime Environment” and click Generate.

The tree now appears as below:

385
To activate individual nodes, click on the node and press .

Similarly, execute all the nodes. Finally the status should be as follows:

386
The node “Check Entries from HR Control Tables” will initially show the following error.

To eliminate the errors, execute the report RHSOBJCH. Execution of the report will yield following
kind of output.

387
Select all the entries and click “Adjust”. Exit the report and try re-executing it.

Output should look as below:

Now refresh/execute the “Check Entries from HR Control Tables” node in SWU3. It should have
against it.

4.2. Activate Event Linkages

IMG Path : SAP E-Recruiting -> Technical Settings -> Workflow

Description: This node lists all the ERecruiting workflows that can be activated and used.
Activation of these

workflows is optional and should be strictly need basis.

388
Activation Procedure:

To activate the workflow for Candidate’s request to delete Registration, execute the node
“Workflow after Candidate’s Request to Delete Registration”.

Click “Activate event linking”.

Click the “Detail View” icon under the “Details” column.

389
Check mark “Event linkage activated”, if unchecked and Save.

The event linkage overview screen shows the activation status of the workflow indicated by green
icon “ Activated. Activate all other required workflows in a similar manner.

390
1.1.6 5. Search Engine Configuration
The Search Engine in ERecruiting contains 2 main sub-divisions:

1. Full Text Search

2. Attribute based search
In general, we differentiate between 3 search types:
1.1. Full-text search for documents
1.2. Full-text search for objects
2.1. Attribute based search for objects

For documents (for example, the creation of a candidate), the data is unstructured. For
unstructured data, a KPRO index is used. KPRO index is accessible from transaction SKPR07.

For objects, the data is structured. In other words, the data from the infotypes of the HR objects to
be indexed is extracted and transferred to the SES framework. In TREX, an SES object index exists
for each business object. The SES indexes can either be accessed from SPRO IMG or using
transaction SES_ADMIN.

If you perform a full-text search, the system always performs a full-text search for objects. At the
same time, the system performs a full-text search for documents - if there are attachments and
you want to search for them too. During the Attribute-based search, the system only searches for
objects.

5.1. Set up Indices of SES Object

IMG Path: SPRO -> SAP E-Recruiting -> Technical Settings -> Search Engine -> Set up Indices of SES
Object

Transaction: SES_ADMIN

This step focuses on Attribute based Search for Objects. The standard system contains the
following objects.

Business object Short description

ERC_CAND SES business object Candidate

ERC_CDCY SES business object Candidacy

391
ERC_REQ SES business object Requisition

EXT_POST SES business object External Publication

INT_POER SES business object Internal Publication

This node starts the transaction SES_ADMIN. Initially there will be no indexes created.

Index can be created using the menu item: Index -> Create/Activate Indexes

A dialog box with existing indexable objects pops up. Select the relevant object and continue. It
should be noted that the objects should be selected one at a time, not multiple entries
simultaneously.

We select object EXT_POST of object type NC.

392
The index as shown below has been created for object NC.

This index should be created for other object types also.

Below is the complete sequence of steps to be followed.

1. Create the object index for EXT_POST/NC.

2. Create the object index for INT_POER/NC.
3. Create the object index for ERC_REQ/NB.
4. Create the object index for AES_DOC/00000100.
5. Create the object index for ERC_CAND/NA. When you create this index, the system issues an
error message since you still cannot create the join index. Ignore this message.
6. Create the object index for ERC_CDCY/NE. When you create this index, the system creates the
corresponding relation index.
7. Create the relation index for ERC_CAND/NA.
Now the indexes are created but documents are yet to be indexed. For indexing the documents, we
have to start the full indexing for each of the indexes which will physically send the documents
corresponding to each object for indexing.

But before that we have to execute program RCF_SES_JOIN_INDEX_CREATE. You can use this
program to add further information to the join indexes. Join indexes contain Meta information
about the relationships between business objects. This program should always be executed when
you delete or re-create one or several indexes.

Once the join index is created we should perform the full indexing for all the ERecruiting specific
objects.

393
Select the objects in the same sequence in which they were created and click Index Immediately.

In the pop-up that follows, select Full (full indexing) only for the first run of indexing. Every
subsequent time, Delta (delta indexing) should be used. Full indexing indexes all the documents
corresponding to the selected object. Delta indexing selects only the new documents since last run
for indexing.

Although, selecting Full indexing for subsequent runs would do harm to the system, when the
number and size of documents on the content server increase full indexing would definitely take
longer time for execution and may put load on the system

When indexing is in progress, the program shows Active status.

394
The status is Completed once the indexing is done.

Once the status displayed is Active for all the indexes created, Attribute based search for objects
can be successfully performed from the portal.

The SES object based search can be tested using program COM_SE_SEARCH_IIF_TEST.

You may face a situation in future where the index becomes corrupt or the indexing accidently
stops working due to some hardware or compatibility related issues. In such situations, you may be
required to delete one or more existing indexes. Index can be deleted using menu path: Index ->
Delete Index.

Click Yes on the pop-up that follows. This will delete the respective index. You can then re-create
it.

395
5.2. Set up Access to Documents

IMG Path : SPRO -> SAP E-Recruiting -> Technical Settings -> Search Engine -> Set Up Access to
Documents

Transaction: SICF

In this Customizing activity, you set up access to the CONTENTSERVER service of the SAP
ERecruiting system. This enables users to access documents of the document area HR_KW
(Document Storage for HR Objects). Attachments, search profiles, and so on, are stored in this
document repository.

NOTE: KPro Search/Free Text Search to be accessed using transaction SKPR07 configuration starts at

this point.

This service, if deactivated, should be activated by right clicking the node and clicking Activate
Service.

5.3. Initialize KPRO Directory

IMG Path: SPRO -> SAP E-Recruiting -> Technical Settings -> Search Engine -> Initialize KPro
Directory

Structure for SAP E-Recruiting

This node simply executes a program that does the necessary initializations w.r.t. KPro. Care
should be taken that during the execution of this program, the RCF_PERIODIC_SERVICES program is
not being executed.

5.4. Activate Indexing

IMG Path: SPRO -> SAP E-Recruiting -> Technical Settings -> Search Engine -> Activate Indexing

View: V_SDOKIDSP

396
Here, you select the document area HR_KW for KPRO indexing by checking the Index release
checkbox. Indexing is required to enable the search engine to search the search profiles.

The column Search Srv should contain the search server relation Id which will be created in the
next step. We have created EREC as the search server relation.

Note: HR_KW is the Document storage for HR objects.

5.5. Check Settings

IMG Path: SPRO -> SAP E-Recruiting -> Technical Settings -> Search Engine -> Check Settings

Transaction: SKPR07

This transaction is used for creating TREX KPro index to be used for free-text-based search.

KPro index creation consists of following steps:

1. Search Server Relation creation

2. Index Category creation
3. Trigger indexing.

397
Search Server relation creation:

IMG Path : SPRO -> SAP E-Recruiting -> Technical Settings -> Search Engine -> Check Settings ->
SSR Monitor

Transaction: SRMO

Description : The SSR is created to connect KPro and TREX search engine using RFC connection. We
specify

the search engine type and name of the RFC connection.

398
Click on the Create SSR button to create Search Server Relation.

Enter required name for SSR identification and click Create SSR.

DRFUZZY is the search Engine to be used by ERecruiting. Standard recommendation.

TREX_Q50 is the RFC Connection created in SM59 connecting SAP backend (KPro) with TREX engine.

399
The newly created SSR is now visible in the list of SSRs. To set this SSR as default select the entry
and click Set SSR as default.

Index Category Creation and Document Indexing:

IMG Path : SPRO -> SAP E-Recruiting -> Technical Settings -> Search Engine -> Check Settings

Transaction: SKPR07

The index category can be created from the section Mass Actions of transaction SKPR07.

 Uncheck Limited to selected language indicator.

 Select Document Area indexing area

Create Index category by clicking Re-Index button. This will create a unique index category which
can be viewed by F4 on Index Category field.

400
The index category in F4 list looks as below.

Once the index category has been created, the documents can now be sent for indexing.

The Index/De-index section of SKPR07 can be used for document indexing.

Trigger Process will index the documents in the foreground. However, indexing needs to be
scheduled on a periodic basis. Program RCF_PERIODICAL_SERVICES can be scheduled for indexing.

Status of document indexing can be viewed from transaction TREX_ADMIN.

401
1.1.7 5. Periodic services
5.1. Define Periodic Services

Here, you specify services in the system that can be performed periodically. To do so, you assign
each service a class containing instructions on how to perform the service.

A range of periodic services are delivered in the standard system that are required for the search
within E-Recruiting. The search engine TREX (Text Retrieval and Information Extraction) does not
search using the operational data, but rather using search profiles. These are an extract of the
operational data. To keep the database up-to-date for the search, the search profiles must be
updated periodically. For the same reason, the documents that are included for the full-text search
and the search profiles must be indexed from time to time and communicated to the search engine
TREX. This indexing is performed by TREX and is prepared and activated using the service
INDEX_DOCUMENTS.

402
.2. Activate Periodic Services

Here you activate the relevant periodic services for each client from the available list of periodic
services. Errors that occur while performing a service are written to the application log and can be
analyzed by the administrator.

5.3. Determine Rules from Periodic Services

In this activity, you set up attributes that influence a periodic service according to your
requirements.

For Example: When a candidate decides to De-register or when the requisition status is set to “To
be deleted”, these objects are not permanently deleted but are stored in database buffer for
specific period. This time period is determined by the field “Attribute Value” in the below table.

5.4. Schedule Background Process for Periodic Services

Schedule the report RCF_PERIODICAL_SERVICES as a periodic background process. This report

automatically executes the services specified in “Active Periodic Services” table as specified
above. Choose a period between 10 and 30 minutes to ensure the search results are up-to-date
5.5. BADI’s Activation

BAdi: HRALE00SPLIT_INBOUND

Implementation: HR_INB_PROCESS_IDOC.

The BAdI must be implemented for SAP E-Recruiting so that the data of the Person object (object
type P) may be used exclusively in the E-Recruiting application.

403
This BAdi is executed during ALE transfer when the data from IDoc needs to be used for module-
specific conversions or processing.

BAdi: HRALE00INBOUND_IDOC.

Implementation: HRRCF00_DELETE_SPREL.

This BAdi deletes all S-P relationships between positions and persons from the inbound IDocs.
NOTE: Both the BAdi must be active and implemented in the ALE destination
client/server i.e. the

404
1.1.8 6. SAP ECC Integration
IMG Path : SPRO -> SAP E-Recruiting -> Technical Settings -> SAP ERP Central Component (ECC)
Integration

Description: This IMG node describes the activities to be performed in HR and ERecruiting systems
under

various system scenarios i.e.

 HR and ERecruiting are on same instance

 HR and ERecruiting are on separate instances.
We have HR and Recruitment both on same instance.

The HR system is the main system for the following employee data. The data of an employee is
processed using Personnel Management (personnel actions, master data). Changes to the data in
the following infotypes are then reconciled with SAP E-Recruiting.
 Actions (0000)
 Organizational Assignment (0001)

 Personal Data (0002)

 Addresses (0006)

 Communication (0105)

 Qualifications (1001, subtype 032)

Data Reconciliation between HR Master Data and ERecruiting Data

 Initial Data Conversion (One time activity)

Every user of the ERecruiting system, internal or external, has the Candidate object NA associated
to it. The NA object is connected to Business partner object BP via, Central Person object CP.
To get access to ERecruitment specific applications, services and to work on ERecruitment portal
without errors, HR Master Data needs to be integrated with Business Partner data i.e., each
internal user has to be translated in terms of ERecruiting objects.

405
Report – HRALXSYNC – is used for the initial data conversion.
Pre-requisite –
Maintain the following entry in table T77S0.
GRPID SEMID GSVAL TEXT
HRALX OBPON ON Integraion O-BP Active

This report enables you to run a consistency check for the integration of HR Master Data and
Business Partner data. If not all data exists for the business partner, you can first synchronize data.
When synchronization is run for organizational units, the basic data (name, description) and the
address data is included;
When synchronization is run for central persons, bank information is included in addition to the
basic data and address data.

You can restrict the employees to be synchronized based on various selection criteria as shown
above.
We are using Central Person object for synchronization. Execution of the program will display the
status of data updating.

Green Signal – Business Partner data is consistent with HR object data.

Yellow Signal – Business Partner exists but data is not consistent with HR object data.
Red Signal – Business Partner does not exist or data is incomplete.

406
In case the record as shown above shows status in Yellow or Red, select the entry as shown below
and click Start Repair.

The program then tries to correct the error and if unsuccessful, displays the error or if successful
shows either a warning or no message.

This process has to be done for all employees or central persons once initially.

Refer the following section for auto data synchronization of newly hired employees and changes to
existing employees to be replicated in business partner tables on a continual basis.

 Synchronous Data Conversion (Subsequent Data Update)

With the synchronization, the data is written automatically to SAP E-Recruiting after changes have
been made using HR standard transactions (for example, PA30, PA40, maintaining the qualification
profile).
Activate the following Business Add-ins for activating synchronous data conversion.
BAdI Definition Name = HRSYNC_P

BAdI implementation = CONV_HR_DATA_TO_EREC

407
Description: Conversion of Employee's HR Data in E-Recruiting. The BADI is executed every time
changes are

done to HR master data using PA30, PA40 or other master data transactions.

BAdI Definition Name = HRBAS00INFTY

BAdI implementation = HRRCF00_STORE_HRQUAL

Description: Updating of HR Qualifications in E-Recruiting Infotype 5105

408
1.1.9 7. Basic Settings
7.1. Determine Languages Available

IMG Path : SPRO -> SAP E-Recruiting -> Basic Settings -> Determine Languages Available

Description:

Here you specify which languages are supported in SAP E-Recruiting.

 You can perform searches only in the languages stored here.

 You can save attachments in these languages only.
 You can enter texts in questions and questionnaires in these languages only. A separate tab
page is available for each language to enter the texts.
 You can enter job postings in these languages only. A tab page is available for each
language to enter texts.

7.2. Define Enterprise Structure

IMG Path : SPRO -> SAP E-Recruiting -> Basic Settings -> Enterprise Structure

Description: Here you define the companies, the branches for the companies and assign the
branches to the

company.

7.2.1. Define Company

IMG Path : SPRO -> SAP E-Recruiting -> Basic Settings -> Enterprise Structure -> Define Company

Table : T77RCF_COMPANY

Description:

In this Customizing activity, you define the individual independent companies in your business
concern. You can differentiate your application processes on the basis of the companies. This
enables different companies to integrate forms for correspondence activities, for example.

409
7.2.2. Define Branches

IMG Path : SPRO -> SAP E-Recruiting -> Basic Settings -> Enterprise Structure -> Define and Assign
Branches

To Companies

Transaction: BP

Description : A branch can be defined by creating a business partner with role as RCFAGY i.e.
Agency.

7.2.2. Assign Branches to Companies

IMG Path : SPRO -> SAP E-Recruiting -> Basic Settings -> Enterprise Structure -> Define and Assign
Branches

To Companies

Transaction: V77RCFBRANCHCOMP

Description : Here you assign the branches created in the above step to Holding companies.

410
7.2. Attachment Types

7.2.1. Define Attachment Types

IMG Path : SPRO -> SAP E-Recruiting -> Basic Settings -> Attachment Types -> Define Attachment
Types

Table : T77RCF_ATTTYPE_T

Description: Define the attachment types that should be available in ERecruiting. Attachment
types specify

the thematic content of attachments, for example resume, job posting, reference.

7.2.2. Determine Use of Attachment Types

IMG Path : SPRO -> SAP E-Recruiting -> Basic Settings -> Attachment Types -> Determine Use of

Attachment Types

411
View : V_7RCF_ATTTYPE_U

Description:

Determine which attachment types are possible for an HR object type.

For example, attachment type Resume is possible for Candidate (NA) object type in the Resume
area or subtype. Attachment Sub-types specify the various areas on the UI from where attachments
can be uploaded for the selected object.

7.2.3. BAdi: Upload documents

IMG Path : SPRO -> SAP E-Recruiting -> Basic Settings -> Attachment Types -> BAdi: Upload
Documents

BAdi Name : HRRCF00_DOC_UPLOAD

Description: This BAdi can be used to incorporate custom checks during document upload as
attachments.

7.2.4. Identify Attachment Type as Resume

IMG Path : SPRO -> SAP E-Recruiting -> Basic Settings -> Attachment Types -> Identify attachment
type as

Resume

View : V77RCF_ATTTYPE_U

Description:

Specifies whether documents of this attachment type are resumes. Documents can be classified as
Resumes or formatted Resumes.

412
Identify as Resume the attachment type to which resumes are uploaded that were created by the
candidates themselves. Identify as Formatted Resume the attachment type to which resumes are
uploaded that were created by a vendor using Resume Parsing.

7.2.5. BAdi: Filter for Attachments for Data Overviews

IMG Path : SPRO -> SAP E-Recruiting -> Basic Settings -> Attachment Types -> BAdi: Filter for
attachments

for Data Overviews

BAdi Name : HRRCF00_DATAOVR_ATTACHMENTS

Description:

Every Data Overview application in ERecruiting has an Attachments table at the bottom of the page
with link to attachments as table elements. You can use this BAdi to restrict the display of links to
attachments on the user interface for data overviews for SAP E-Recruiting objects. In this way, you
can make certain attachments inaccessible for specific users. By default, the system displays links
to all attachments that are linked with the relevant HR object.

7.3. Status Reasons

7.3.1. Define Status Reasons
IMG Path : SPRO -> SAP E-Recruiting -> Basic Settings -> Status Reasons -> Define Status Reasons

Table : T77RCF_RSNCODE_T

Description:

Users assign status reasons to an object when they make a status change. Status reasons describe
why a certain status is set.

413
Status Reasons are assigned to Object Statuses.

7.3.2. Assign Status Reasons to Statuses in Recruitment

IMG Path : SPRO -> SAP E-Recruiting -> Basic Settings -> Status Reasons -> Assign Status Reasons to
Statuses

in Recruitment

Table : T77RCF_RSNCODE_T

Description: The status reasons are assigned possible statuses of required objects.

414
415
1.1.10 8. Talent Warehouse

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse

Description: This IMG node is concerned with maintaining all candidate related data required by
the

recruiting organization.

8.1. Maintain Candidate Qualifications

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Qualifications

Description: Qualifications refer to the competency dictionary defined within the organization. The
qualification catalog is actually created as a part of Organization Management and can be used
here to give the applicants the option of selecting their strengths as a tool for self assessment.

8.1.1. Define Views for Qualifications catalog

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Qualifications -> Define Views for
Qualification catalog

Table : V_T77QC_VIEW_ID

Description: Standard setting. Use SAP_ERECRUITING view.

8.1.2. Restrict View of Qualifications catalog

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Qualifications -> Restrict Views of
Qualification

catalog

Table : V_T77QC_VIEW

Description:

416
The recruiting organization may have a large number of qualifications/competencies defined for
various job types. However it may want only a subset of these qualifications to be exposed to
ERecruiting. Restrict views feature will help to achieve this goal.

Qualifications are currently not used. The screenshot shown below is for understanding purposes.

8.1.3. Define Scales for Qualifications

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Qualifications -> Define Scales for
Qualification

Transaction: OOSC

Description : Scales and scale proficiencies to be used by Qualification catalog are defined here.

417
8.1.4. Define Qualifications Catalog
IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Qualifications -> Define
Qualifications catalog

Transaction: OOQA

Description : Qualification catalog needs to be defined here.

8.2. Work Experience/Desired Employment

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Work
Experience/Desired

Employment

Description: In this customizing node, you maintain all value lists used in work experience and
employment

Infotypes.

8.2.1. Define Hierarchy Levels

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Work
Experience/Desired

Employment -> Define Hierarchy Levels

Table : T77RCF_HIER_T

Description:

The hierarchy levels represent the pecking order in your company with relation to professional
capabilities and management responsibility.

418
8.2.2. Define Work Contract Types
IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Work
Experience/Desired

Employment -> Define Work Contract types

Table : T77RCF_CONTTY_T

Description:

Here, you define the different categories of work contracts that your company has with its
employees. The work contract type is part of the terms of employment while applying for a job.

8.2.3. Define Industries

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Work
Experience/Desired

Employment -> Define Industries

Table : T77RCF_INDU_T

Description:

Here, you define the industries that are relevant for your recruitment process. This should include
industries that exist in your company and industries in which a candidate could have gained work
experience.

419
8.2.4. Define Functional Areas

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Work
Experience/Desired

Employment -> Define Functional Areas

Table : T77RCF_FUNC_T

Description:

Here, you define the task areas in your company that contribute to the achievement of the
corporate goal.

420
8.2.5. Define Employment Fractions
IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Work
Experience/Desired

Employment -> Define Employment Fractions

Table : T77RCF_WORKTI_T

Description:

Here, you define the employment fractions that exist in the company. In the process, you specify
the limit for the number of working hours per week as of which a certain employment fraction
exists.

421
8.2.6. Salary Ranges
IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Work
Experience/Desired

Employment -> Salary Ranges

Description: Here, you define the currency list to be used for recruitment and corresponding salary
ranges.

The recruiter/candidate will have to first select

8.2.6.1. Determine Currencies for Salary Ranges

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Work
Experience/Desired

Employment -> Salary Ranges -> Determine currencies for salary ranges

Description: The currencies to be maintained in ERecruiting are to be listed here. This will be
required to

get salary related details from the applicants.

8.2.6.2. Define Salary Ranges

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Work
Experience/Desired

Employment -> Salary Ranges -> Define salary ranges

View : V_T77RCF_SAL_RNG

Description: Here, you determine the salary ranges for the payment information of the jobs and
salary

expectations of the candidates for each currency.

422
8.3. Education/Training
IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Education/Training

Description: In this IMG node, you configure all education related value lists.

8.3.1. Define Education Types

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Education/Training ->
Define

Education Types

Table : T77RCF_EDUTYP_T

Description:

Here you specify those education types that you want to use as selection criteria for the candidate
search in the talent pool and that a candidate can specify when entering his or her education data.

8.3.2. Define Broad Field of Education

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Education/Training ->
Define

Education Types

423
Table : T77RCF_EDUTYP_T

Description: Here, you maintain the various fields of education considered acceptable by your
organization.

8.3.3. Define Educational Certificates/Degrees

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Education/Training ->
Define

Educational Certificates/Degrees

Table : T77RCF_DEGREE_T

Description: Here, you maintain the education certificates and degrees recognized by your
organization.

8.4. Interest Groups

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Other Features ->
Define

Interest Groups

Table : T77RCF_TGROUP_T

424
Description:

Interest Groups can be used by candidates to associate themselves to specific job types or industry
or areas of interest to provide more clarity to internal recruitment team on role desired by
candidate. Alternatively, a recruiter can specify in the requisition which interest group is suitable
for the open job.

8.5. Communication Channels

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Other Features ->

Communication Channels

View : V_T77RCF_COM_CHN

Description:

In this IMG activity, you define the communication channels that can be used to contact
candidates.

All channels specified here are available on the applicant contact details UI for data input.

8.6. Candidate Search

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search

Description:

Search in ERecruiting is enabled using Search Profiles and Search Templates which are referred to
by TREX for text retrieval.

425
8.6.1. Search Profile
8.6.1.1. Define Search Profile types
IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Profile -> Define Search Profile Types

View : V_T77RCF_SPT

Description:

In this IMG activity, you define the search profile types that you want to use for the job postings,
candidates, requisitions, and assignments (candidacies). Fields from information categories are
assigned to a search profile type that serves as a template for creating search profiles for the
objects of a specific object type.

5 Search Profile types are delivered by SAP Standard. These are usually adequate to meet the
search needs. No changes are required to the standard entries.

8.6.1.2. Define Information Categories

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Profile -> Define Information Categories

View : T77RCF_SPT_IC

Description:

 Information categories map to individual tables from which information is required to be

extracted.
 Information categories are used to specify the business-specific content of structures.
 The extraction classes contain the code logic for fetching the data based on search criteria.

426
You create new information categories, for example, in the following cases:

 You have created your own infotype and a corresponding structure and want to make their
fields available for the search.
 You want to use a different content extraction class to retrieve the information of an
information category.

The customer namespaces are: information categories Y* and Z*

8.6.1.3. Assign Languages to a Search Profile Type

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Profile -> Assign Languages to a Search Profile Type

View : V_T77RCF_SPT_LAN

Description:

In this Customizing activity, you determine for each search profile type the languages in which the
search profiles of this search profile type are to be created. You can search for relevant objects
only in these languages.

427
8.6.1.4. Assign Information Category Fields to a Search Profile Type
IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Profile -> Assign Information Category Fields to a Search Profile Type

View : V_T77RCF_SPT_LAN

Description:

In this IMG activity, you specify which fields from the information categories are included for the
creation of search profile type. You can search for only these fields. You also assign the Field type
to each field.

Field type specifies the type of the field that is assigned to an information category. The type
determines how the system can search in the associated field.

 Free Text:
Only Free text search is possible.

 Entity
Values will be derived from tables in a dropdown.

 Both, Free Text and Entity:

Both methods are applicable.

8.6.1.5. Assign Attachment Types to a Search Profile Type

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Profile -> Assign Attachment Types to a Search Profile Type

View : V77RCF_SPT_AATYP

428
Description:

In this Customizing activity, you determine for each search profile type which attachment types
should be taken into account during the full text search.

8.6.1.6. Update Search Profile

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Profile -> Update Search Profile

Transaction: HRRCF_RECREATE_SP

Description:

 This IMG activity enables you to update the search profiles that have been created on the
basis of a search profile type.
 This activity must be performed whenever the user changes the assignment of fields in an
information category to a search profile type.
 Creating search profiles for a large number of objects (candidates, job postings) can take a
long time. It is recommended to start the report as a background process if several changes
have been done.

8.6.1.7. Update Search Profile

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Profile -> Update Search Profile

Report : RCF_UPD_DOC_ATTRIB_INDX_FULL

Description:

You use this report to correct the search-relevant attributes of the attachments in Knowledge
Provider (KPro).

8.6.2. Search Templates

429
Search Templates represent the actual UI elements available on the ERecruiting screens during
search.

In the above screenshot, the highlighted dropdown represents Search Templates.

For example, the already selected template above is “Candidate’s Work Experience”.

Search Template Elements represent the individual fields within each Search Template.

For example, Country/Employer represents search template elements.

8.6.2.1. Define Search Templates

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Templates -> Define Search Templates

View : V_T77RCF_SMASK

430
Description:

Here, you define the search templates that should be available on the user interface for search
purposes.

You specify for each search template the search profile type on which it should be based on. In
addition, you determine how the search template is displayed on the user interface.

8.6.2.2. Define Search Templates Elements

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Templates -> Define Search Templates Elements

View : V_T77RCF_SM_ELEM

Description:

Here, you define all the fields on which search should be possible from the web front end.

The possible values for element type are:

List Box, Multi-line Input field, Display field, Checkbox, Radio button, Date type, Salary
Expectations,

Job Family Potential, Performance Management.

To define a new search template element, a nomenclature should be followed as follows:

Z<object>_<information category>_<field name as in table>

For example: ZCAND_EDU_EDULEVEL

431
8.6.2.3. Assign Search Templates Elements to Search Templates
IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Templates -> Assign Search Templates Elements to Search Templates

View : V_T77RCF_SM_ASME

Description:

In this Customizing activity, you specify which search template elements appear in the search
template and in what order.

In the above screenshot, Search Template “Candidate’s Education” consists of 5 Search Template
Elements as shown.

8.6.2.4. Define Search Templates Groups

432
IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Templates -> Define Search Template Groups

View : T77RCF_SM_GROUPT

Description:

In this Customizing activity, you define search template groups. You assign the search templates
you require to display a certain search on the user interface to the search template groups. Should
any new Search Template groups be required to be defined, they can only be defined in the
customer namespace starting with 9*.

8.6.2.5. Assign Search Templates to Search Template Groups

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Templates -> Assign Search Templates to Search Template Groups

View : T77RCF_SM_GROUPT

Description:

In this Customizing activity, you assign the search templates that should be available on the user
interface for the display of a special search to a search template group. At the same time, you
determine the order in which the search templates are displayed on the user interface.

433
Search in Talent Warehouse group corresponds to the Candidate Search screen.

8.6.2.6. Assign Search Template Groups to Search Applications

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Templates -> Assign Search Template Groups to Search Applications

View : V77RCF_SMG_NAVI

Description:

In this Customizing activity, you specify which search template groups are used in the different
scenarios

Standard settings delivered for the relevant search applications (search template groups) for
Recruiting Administrator and Recruiter portal roles:

CompID of Calling Controller Scenario (Search Template Group)

cdcycandsearch Candidate Search in the context of a requisition or an application

434
 group (recruiter)

Search for Requisitions in the context of an external candidacy for

cdcyreqsearchexternalpostings recruiters (with external postings or with and without external
postings (you can alternate between the two scenarios))

Search for Requisitions in the context of an internal candidacy for

cdcyreqsearchinternalpostings recruiters (with internal postings or with and without internal
postings (you can alternate between the two scenarios))

trmcandsrch Search for Candidates in Talent Warehouse for Recruiters

Simple Search for internal and external candidates in the context of

simplesearch_audittrail
an audit trail (Recruiting Administrator)

Simple Search for external candidates in the context of deletion

simplesearch_delcand
(Recruiting Administrator)

Simple Search for external candidates in the context of

simplesearch_deregcand
deregistration (Recruiting Administrator)

quicksearch Quick Search

Standard settings are delivered for the relevant search applications (search template groups) for
the following scenarios that are realized for the Candidate:
CompID of Calling Controller Scenario (Search Template Group)

EMPLOYEE2POSTING Search for Internal Job Postings for Registered Internal Candidates

REGISTERED2POSTING Search for External Job Postings for Registered External Candidates

UNREGEMPLOYEE2POSTING Search for Internal Job Postings for Unregistered Internal Candidates

UNREGISTERED2POSTING Search for External Job Postings for Unregistered Candidates

With this, the configuration of Search Templates and Groups is complete.

The final step is to set up the Search Applications which is an optional step.

8.6.2.7. Set Up Search Applications

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Search ->
Search

Templates -> Set Up Search Applications

View : V77RCF_SRCH_ATTC

Description:

In this Customizing activity, you set the attributes for the search scenarios. In this way, you can
determine for different search applications which interface elements they contain and which
options for creating search queries are available.

435
SAP delivers the standard entries in table T77RCF_SRCH_ATTR. These entries get overridden by
entries from this table.

The various columns have the following meaning:

Display Ranking: If this indicator is set, the column displaying the match is shown in the result list.
The indicator is relevant only for candidate scenarios.
Display Documentation: If this indicator is set, a link to the documentation of the search
application is provided on the user interface. The indicator is relevant only for candidate scenarios.
Display variants: If this indicator is set, the user can save search variants for later use.
Display Maximum Number of Hits: If this indicator is set, the settings for the maximum number of
hits are displayed on the user interface.
Maximum Number of Hits: This number specifies how many hits are displayed in the hit list.
Note: If you do not enter a value, then there are no entries in the hit list.
Display Threshold: If this indicator is set, the settings for the match threshold are displayed on the
user interface.
Threshold: This number specifies by how much a hit must agree with the search criteria for it to be
displayed in the hit list.
Display Operator: If this indicator is set, operators are available for the recruiter on the user
interface of the search application for combining values of the same search template element. In
this way, the recruiter can override the standard system behavior.
Operator: Contains the operator that dictates the standard system behavior for the recruiter's
search applications when combining values of the same search template element. Specify AND or
OR to determine the relationship between the criteria.

8.7. Candidate Services

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Services

Description : Candidate Services node has been added as a part of EhP4. Two services have been
provided:

 Job Agent
 Tell-a-Friend
8.7.1. Job Agent
IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Services
->Job Agent

436
Description:

It may happen that the organization may currently not have any openings for the job category or
role the applicant is looking out for. In such cases if the applicant wants the company to keep him
posted on the job openings that match his role and profile, he will select the role criteria; select
the frequency for receiving notifications and save it as a Job Agent. The Job Agent service will then
automatically send periodic mailers to the applicant whenever openings satisfying the saved
criteria are posted.

8.7.1.1. Define Periodic Services for Job Agent

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Services
->Job Agent–>

Define Periodic services for Job Agent

Table : T77RCF_AS_SERV

Description: Standard SAP delivered settings is used. No changes required

8.7.1.2. Specify Rules for Periodic Services of Job Agent

IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Services
->Job Agent–>

Specify Rules for Periodic Services of Job Agent

Table : T77RCF_AS_SERV

Description:

In this IMG activity, you set the attributes that influence a periodic service for the job agent to suit
your requirements.

Periodic service Attributes Description

JOB_AGENT MAX_JOB_AGENTS Maximum number of job agents that a candidate can create

Maximum number of job postings that can be sent by a job

JOB_AGENT MAX_POSTINGS
agent that was created by a candidate

437
8.7.1.3. Set Up Background Job for Job Agent
IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Services
->Job Agent–>

Set Up Background Job for Job Agent

Description:

Schedule report RCF_AGENT_SERVICES as a daily background job.

Note that this service will not be run if program RCF_PERIODICAL_SERVICES runs simultaneously.
For all other services, the RCF_AGENT_SERVICES report can be run simultaneously.

8.8. Tell-a-Friend
IMG Path : SPRO -> SAP E-Recruiting -> Talent Warehouse -> Candidate -> Candidate Services ->
Set up Tell

A Friend service

Description: This service is available to the external candidate on the Job search screen.

Pre-requisite:

1. A service user needs to be assigned to parameter SERVICE_USER in table V77RCF_MDL_PRMC. We

have

assigned the service user RCF_UNREG for this service.

This table can be accessed from IMG path: IMG -> SAP ERecruiting -> Technical Settings ->User
Interfaces->

Manager Involvement -> Assign Values to Interface Parameters (WebDynpro ABAP)

438
1.1.11 9. Applicant Tracking
IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking

Description: Applicant tracking is done by performing a series of Activities.

Activities are grouped into Processes and linked to any of the available HR objects.

Applicant tracking also forms the basis for Applicant Ranking.

9.1. Assign Scales to Scale Types

IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Assign Scales to Scale Types

View : V_T77RCF_SCALES

Description:

Applicant tracking involves ranking candidates on the basis of their suitability. Suitability is
expressed via customizable ranking scales. Scales need be created and assigned to Scale types.

Here, Scale type refers to the scenario in ERecruiting where the ranking functionality can be
executed.

Three types of ranking scales are distinguished:

 Assignment Rating: Expresses how well a candidate suits a requisition.

 Candidate Classification: Expresses how well a candidate suits the company (independent
of requisition assignment)
 Weighting for Search and Match: This scale type is needed to express how important
criteria are in search.

9.2. Define Application Source Types and Assign to Application Sources

439
IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Define Application Source Types

View : V_T77RCF_APPLSTY, V_T77RCF_APPLSRC

Description:

In this IMG activity, you define the application source categories you require when you want to
report on where candidates learned about your job postings. In addition, you store an OTR (object
text repository) text for each source category. This text is displayed on the user interface together
with a free-form text field.

Applicants can enter their “Source of application” in the final step of an application.

Fig 1. Application Source Types

Fig 2. Assign Application Source Types to Application Sources

The OTR’s can be accessed from transaction SOTR_EDIT.

440
9.3. Activities
IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities

Description:

Activities are foundation of Applicant tracking. They are individual steps taken on a candidate.

For example: Invite for Interview, Send Offer Notification, Initiate ATO.

 Activities have a Status. They can either have status Planned or Completed. You can enter
a Due Date for activities with status as “Planned”.
 Activities have Notes and Attachments.
 An activity is always assigned to an Object Type.

9.3.1. Define Activity Types

IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Define Activity Types

View : V77RCF_ACT_TYPE

Description:

Here you define the activity types that you require for your processes within SAP E-Recruiting. To
do so, you assign an Activity Category to each activity type. This controls what data the activity
type contains and what system functions can be executed for it.

Activity Categories delivered in ERecruiting:

 Simple Activity
 Simple Correspondence
 Qualifying Event
 Invitation
 Status Change
 Data Transfer for new employees
 Questionnaire

441
9.3.2. Define Processes
IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Define Processes

View : T77RCF_ACTPROC_T

Description:

A Process is a grouping of activities used to structure the applicant tracking process from a business
point of view. We can define custom processes and assign existing or custom activities to it.

9.3.3. Assign Processes to Recruitment

IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Assign Processes to
Recruitment

442
View : V77RCF_PROC2SUB

Description:

In this Customizing activity, you assign the processes you want to use to the Recruitment area. In
doing so, you use the process groups to define the subarea of Recruitment in which your processes
will be used.

 Processes that are assigned to the Candidate Shortlist subarea focus on processing
assignments of candidates to Requisitions or Application Groups.
 Processes that are assigned to the Talent Relationship Management subarea focus on
maintaining relationships with candidates in the Talent Pool.
Within a process group, you use the sequential number to specify the order in which the processes
are offered for selection on the user interface.

9.3.4. Assign Activity Types to Recruitment Processes

IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Assign Activity Types to

Recruitment Processes

View : V77RCF_ACT2PROC

Description:

In this Customizing activity, you assign Activity Types to Processes in the Recruitment subarea. By
doing so, you store the possible activity types that are included in the relevant process.

9.3.5. Assign HR Object Types to Activity Types

IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Assign HR Object Types
to

Activity Types

View : V77RCF_ACT2OTYPE

443
Description:

You assign HR object types from E-Recruiting to your activity types

It is recommended to assign the activity types as follows

Activity Types HR Object

Activity Types for Talent Relationship Management Candidate

Activity Types for Application Management Application

Activity Types for Selection Process Candidacy

9.3.6. Assign Status to Status-Changing Activity Types

IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Assign Status to Status-
Changing

Activity Types

View : V77RCF_ACT2OTYPE

Description:

Here, you assign the possible statuses for each ERecruiting object.

444
9.3.7. Link Activity Types with Referencing Activity Types
IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Assign Status to Status-
Changing

Activity Types

View : V77RCF_ACT2PROCR

Description:

In this Customizing activity, you link activity types of the activity categories Status Change,
Qualifying Event, and Questionnaire with activity types of the category Invitation. When the user
creates the relevant activity, a suitable linked activity of the category Invitation is then available
that the user can use to send the activity.

9.3.8. Correspondence
IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Correspondence

Description:

All the settings related to correspondence activities viz. defining letter templates, changeable
sections, assigning forms to activity types, etc are configured in this step.

445
9.3.8.1. Adapt User for Correspondence
IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Correspondence ->
General

Settings -> Adapt user for Correspondence

Transaction: SU01

Description:

Here, you configure users so that they can send or print correspondences.

You must make the following settings:

 You need to assign a printer to the user (output device field in SU01) so that he or she can
print the correspondence. You also need to make this entry for correspondence output by
e-mail to ensure the formatting is correct.
 You need to assign an e-mail address to the user so that he or she can send the
correspondence by e-mail. If an e-mail address is stored for candidates assigned to the
user, the system uses this e-mail address.
9.3.8.2. Specify ITF-HTML Mapping
IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Correspondence ->
General

Settings -> Specify ITF-HTML Mapping

View : T77RCF_MAPPING

Description:

The system saves letter templates as Smart Form templates with text modules (letter sections).
The user can change these letter sections when sending correspondence. The system reads the text
modules when loading in Interchange Text Format (ITF) format. This cannot be displayed with
WebDynpro.

446
The FormattedTextEdit control (Control for Editing of Letter Sections) used by SAP expects a subset
of XHTML as the code for the formatted text display. Therefore it is necessary to convert the ITF
format to HTML format, which can be interpreted by FormattedTextEdit.

SAP delivered entries has not been changed.

In this Customizing activity, you assign corresponding HTML formats to the ITF (Interchange Text
Format) tags that you use in the styles of your Smart Form forms. In this way, you can specify how
the system converts the formatting of the Smart Form templates to HTML formatting. This is
necessary as the editor for individualizing letter sections uses HTML formats.

9.3.8.3. Assign Document Categories to Activity Categories

IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Correspondence ->
Create Letter

Templates -> Assign Document Categories to Activity Categories

Transaction: SU01

Description:

Document categories group together correspondence documents of the same type and specify the
technology with which the documents can be customized by the user.

Activity Categories specify the types of activities available in ERecruiting.

447
SAP delivered entries has not been changed.

Create Forms and Changeable Letter Sections

IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Correspondence ->
Create Letter

Templates -> Create Forms and Changeable Letter Sections

Transaction: SMARTFORMS

Description:

Here, you create the Smart forms and Text Modules (used in smartforms) that are used to create
letters for correspondence in SAP E-Recruiting.

The sample forms have the prefix HRRCF_CS_IT_*.

The sample text modules have the prefix HRRCF_CS_MT_*.

9.3.8.4. Assign Changeable Letter Sections to Forms

IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Correspondence ->
Create Letter

Templates -> Assign Changeable Letter Sections to Forms

448
View : T77RCF_INCL2FORM

Description:

In this customizing activity, you assign to the forms the text modules that are available to users in
correspondence activities as changeable letter sections for customizing the correspondence.

When a correspondence activity is created, only the specified Text Module contents are available
for editing on the WebDynpro UI.

449
9.3.8.5. Assign Forms to Activity Types
IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Correspondence ->
Create Letter

Templates -> Assign Changeable Letter Sections to Forms

View : T77RCF_INCL2FORM

Description:

Here, you assign forms as letter templates to the activity types. These forms determine the
appearance and the content of the letter that is generated by the correspondence activity being
created.

You can assign several forms to an activity with the same attributes (companies, interest groups,
candidate classes) by using sequential numbers. These forms are offered for selection (if more than
1) as letter templates when the user creates a correspondence activity.

9.3.8.6. Assign Templates for Cover Letter to Letter Templates

IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Correspondence ->
Create Letter

Templates -> Assign Templates for Cover Letter to Letter Templates

View : T77RCF_COV2FORM

Description:

In this Customizing activity, you assign templates for the cover letters to the letter templates.

450
The system sends the letters via e-mail. The e-mail sent consists of a cover letter and the actual
letter in the form of an attached document. By using cover letters, you can separate the actual
content of the letter from the formal cover letter.

9.3.8.7. Assign Document Formats to Output Channels

IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Activities -> Correspondence ->
Output

Channels -> Assign Document Formats to Output Channels

View : T77RCF_CS_CH2FMT

Description:

In this customizing activity, you assign document formats to output channels. In E-Recruiting,
documents can be output in various formats using various output channels.

SAP delivered entries has not been changed.

9.4. Questionnaires
IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Questionnaires

Description:

A questionnaire is a set of questions that can be completed by a person (e.g. candidate, recruiter)
during the applicant tracking process. Questions first need to be created forming a question bank.

A sample questionnaire is displayed below.

451
9.4.1. Set Up Categories
IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Questionnaires -> Set Up Categories

Transaction: OO_HRRCF_CAT_CREATE

Description:

This IMG node is a report that automatically makes the basis settings and generates the relevant
table entries. You only need to execute the report once when ERecruiting is being set up.

452
9.4.2. Assign Categories to Activity Types
IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Questionnaires -> Assign Categories
to Activity

Types

View : V77RCF_QACAT2ACT

Description:

Each Questionnaire activity needs to be assigned with a Category viz. Evaluable Information or
Equal employment information.

We are not using Equal Employment Information category. The standard one itself is used.

 You identify the activity types whose questionnaires are to be integrated in the application
wizard.
 You identify the activity types whose assigned questionnaires are to be included in the
automatic ranking of the candidate's questionnaires.

The system includes all questionnaires of an identified activity type on the user interface of the
candidate shortlist in the Questionnaires column; the other questionnaires are included in the
Feedback column.

9.4.3. Define Questionnaire Groups

IMG Path : SPRO -> SAP E-Recruiting -> Applicant Tracking -> Questionnaires-> Define
Questionnaire Groups

View : VT77RCF_QA_GROUP

Description:

In this Customizing activity, you define the questionnaire groups in which you can group together
questionnaires or questions on a specific topic in Questionnaire or Question Maintenance.

The system uses the names of the questionnaire groups on the user interface as titles for the
relevant tab pages for data storage.

453
454
1.1.12 10. Requisition Management
IMG Path : SPRO -> SAP E-Recruiting -> Requisition Management

Description:

Requisition is a formal agreement between managers and recruiters to initiate the recruitment
process

It is an internal document –

 Determining the positions for which candidates are to be sought

 Defining the complete job description and key requirements that candidates must fulfill
 Sources/channels where the advertisements for the vacancies should be published.

10.1. Requisition
10.1.1. Define Hierarchy Levels
IMG Path : SPRO -> SAP E-Recruiting -> Requisition Management -> Requisition -> Job Description
-> Define

Hierarchy Levels

Table : T77RCF_HIER_T

Description:

In this IMG activity, you define the hierarchy levels that exist in your company. The hierarchy levels
represent the pecking order in your company with relation to professional capabilities and
management responsibility.

455
10.1.2. Define Work Contract types
IMG Path : SPRO -> SAP E-Recruiting -> Requisition Management -> Requisition -> Job Description
-> Define

Work Contract Types

Table : T77RCF_CONTTY_T

Description:

Here, you define the different categories of work contracts that your company has with its
employees. The work contract type is part of the terms of employment that apply to a job.

10.1.3. Define Industries

IMG Path : SPRO -> SAP E-Recruiting -> Requisition Management -> Requisition -> Job Description
-> Define

Work Contract Types

Table : T77RCF_INDU_T

Description:

In this IMG activity, you define the industries that are relevant for your recruitment process. This
should include industries that exist in your company and industries in which a candidate could have
gained work experience.

456
10.1.4. Define Functional Areas
IMG Path : SPRO -> SAP E-Recruiting -> Requisition Management -> Requisition -> Job Description
-> Define

Functional Areas

Table : T77RCF_FUNC_T

Description:

In this IMG activity, you define the task/functional areas in your company that contribute to the
achievement of the corporate goal.

10.1.5. Define Employment Fractions

IMG Path : SPRO -> SAP E-Recruiting -> Requisition Management -> Requisition -> Job Description
-> Define

457
 Employment Fractions

Table : T77RCF_WORKTI

Description:

This customizing activity specifies the minimum number of working hours per week that constitute
a given employment fraction.

Threshold expresses the individual weekly working time (in No. of hours) as a portion or fraction of
the standard weekly working time.

10.1.6. Currencies for Salary ranges

IMG Path : SPRO -> SAP E-Recruiting -> Requisition Management -> Requisition -> Job Description
-> Salary

Ranges -> Determine Currencies for Salary Ranges

Table : V_T77RCF_SAL_CUR

Description:

In this Customizing activity, you determine the currencies for the salary ranges. These are the
currencies in which the payment information can be specified for the job and salary expectations.

10.1.7. Define Salary Ranges

IMG Path : SPRO -> SAP E-Recruiting -> Requisition Management -> Requisition -> Job Description
-> Salary

Ranges -> Define Salary Ranges

Table : V_T77RCF_SAL_RNG

Description:

In this customizing activity, you determine the salary ranges for the payment information of the
jobs and salary expectations of the candidates for each currency.

458
10.2. Job Posting
Posting is an Advertisement. It contains all relevant information you wish to communicate to the
public about the vacancy.

For example: Company information, Department, Project, Tasks/Responsibilities, Requirements.

10.2.1. Define Posting Channels

IMG Path : SPRO -> SAP E-Recruiting -> Requisition Management ->Job Posting -> Define Posting
Channels

Table : V_T77RCF_POSTCHN

Description:

Posting channels refer to recipients to whom you want to send your job postings for publishing, for
example, a daily newspaper, a specific job board, or your intranet.

When a manager releases a posting instance for publishing, the publisher starts the necessary
routine (publisher class) for publication of the posting. He generates a document in a specific
format using the information contained in the posting instance, for example.

10.2.2. BAdI: Generate Reference Codes

459
IMG Path : SPRO -> SAP E-Recruiting -> Requisition Management -> Job Posting -> BAdI: Generate
Reference

Codes

BAdi Definition : HRRCF00_GET_EXT_CODE

BAdi Implementation: ZHRRCF_GET_EXT_CODE_01

Description:

When a publication is created for posting, the recruiter can either manually enter the reference
code or if this BAdi is activated can get the reference code auto generated by the system. The
recruiter can do this by clicking the button Generate Reference Code.

The standard system, by default, generates a 40 character alphanumeric code. The BAdi can be
used to include customer-specific logic for the reference code.

10.2.3. BAdI: Specify Proposal Texts for Postings

IMG Path : SPRO -> SAP E-Recruiting -> Requisition Management -> Job Posting -> BAdI: Specify
Proposal

Texts for Postings

BAdi Definition : HRRCF00_GET_DEFAULT_POST_TEXTS

BAdi Implementation: Does not exist. Can be created, if required.

Description:

This BAdi can be used to provide default texts for the free-text fields when creating a posting text.
The fields on the posting screen that can be defaulted are - Company, Department, Project, Tasks,
and Requirements.

The interface of the BAdI permits the transfer of the logon language of each user so that it is
possible to create language-dependent texts. The interface also permits the transfer of the
position, industry, functional area, and hierarchy level to determine the default text.

460
1.1.13 11. Additional Tools
11.1. Delete External Candidates
IMG Path : SPRO -> SAP E-Recruiting -> Delete External Candidates

Transaction: OO_HRRCF_DEL_EXTCAND

Description:

This program can be used to delete external candidates with all associated links.

Enter your selection criteria. The following selection criteria are available:

Candidate: If you want to delete a candidate, enter the candidate ID.

Talent Group: If you want to delete candidates that are grouped together in a talent group, enter
the talent group ID. You can only select the talent groups for which you are a member of the
support team.

Deregistered Candidates: If you set this indicator, candidates are deleted only if their registration
in the Talent Pool has also been deleted.

Check Legal Conformance: If you set this indicator, the program checks whether there are
assignments of the candidate to requisitions and which retention periods are stored for each of the
requisitions. If there are no assignments to requisitions or the retention periods have expired, the
relevant candidate is deleted.

Test Mode: If you set this indicator, the program performs a test run without any changes being
made to the database.

Run the program. The system displays a result list. A message appears for candidates that were not
deleted.

When the candidates are deleted, the associated business partners are not deleted, but are
archived. You can delete business partners later from the database using the transaction BUPA_DEL
(Delete Business Partners).

11.2. Create Internal Users and Candidates for SAP E-Recruiting

IMG Path : SPRO -> SAP E-Recruiting -> Create Internal Users and Candidates for SAP E-Recruiting

461
Transaction: OO_HRRCF_CREATE_USER

Note : This program should not be executed where HR and ERecruiting systems are on
same

Instance i.e. integrated scenario To be used only when

HR and ERecruitment reside on separate servers’ i.e. non-integrated scenario.

Description:

You should run this program when initially creating the first user (for example, the administrator).
The administrator then creates all other users on his start page using the User Maintenance
function.

As a rule, however, the external candidates register themselves using the appropriate Web
scenarios, and the internal candidates (employees) are imported from an HR system using the
master data interface (ALE).

In the integrated scenario, you cannot run the program as this then result in data inconsistencies.

This program creates all ERecruiting specific objects for an employee i.e. executing this program
will create BP, CP, US, and NA objects for the employee.

11.3. Create Internal Users and Candidates for SAP E-Recruiting

IMG Path : SPRO -> SAP E-Recruiting -> Create Internal Users and Candidates for SAP E-Recruiting

Transaction: OO_HRRCF_CHECK_SRCH

Description:

In this Customizing activity, you can check the consistency of the settings that you entered in the
Customizing for the search.

462
463
1.1.14 12. ICM (Internet Communication Manager) Tasks
1. Transaction RZ11
2. Display parameter “icm/host_name_full”.
The fields “ProfileVal” and “Currentvalue” should have Host URL entry.

For example: dv35.rel.co.in

3. Also, check the transaction SMICM -> GoTo -> Host Name Buffer -> Display.
It should have the Fully Qualified Host entries which looks as follows:

12.1. SICF Services Activation

Listed below are some services that must be activated in the system depending on the operational
scenario:

 Support for the Internet protocol (HTTP, HTTPS and SMTP) in the SAP Web Application Server
/default_host/sap/public/icman

Through this the ICMan process can (for example) make decisions concerning the distribution of
HTTP requests to the corresponding server.

 Using load distribution

- with the message server

/default_host/sap/public/icf_info

/default_host/sap/public/icf_info/logon_groups

/default_host/sap/public/icf_info/urlprefix

- with the Web Dispatcher

/default_host/sap/public/icf_info

464
 /default_host/sap/public/icf_info/icr_groups

/default_host/sap/public/icf_info/icr_urlprefix

 Using Business Server Pages (BSP)

/default_host/sap/bc/bsp/sap

/default_host/sap/bc/bsp/sap/system

/default_host/sap/bc/bsp/sap/public/bc

/default_host/sap/public/bc (available for 620 with Support Package 34)

/default_host/sap/public/bc/ur (available for 620 with Support Package 34)

/default_host/sap/public/bsp/sap/public

/default_host/sap/public/bsp/sap/public/bc

/default_host/sap/public/bsp/sap/system

/default_host/sap/public/bsp/sap/htmlb (as of Release 620 Support Package

SAPKB62026)

 Using the BSP logon procedure

/default_host/sap/public/bsp/sap

/default_host/sap/bc/bsp/sap/system

/default_host/sap/public/bsp/sap/public

/default_host/sap/public/bsp/sap/system

BSP test applications for troubleshooting

/default_host/sap/bc/bsp/sap/it00

/default_host/sap/bc/bsp/sap/sbspext_htmlb

/default_host/sap/bc/bsp/sap/sbspext_xhtmlb

/default_host/sap/bc/bsp/sap/htmlb_samples

As of Release 6.30: /default_host/sap/bc/bsp/sap/bsp_verificatio

 For e-Recruitment, activate all services with the prefix HRRCF.

Before testing the e-Recruiting specific BSP applications, test the standard BSP Test applications
specified above for troubleshooting of web environment.

 ICF test applications

/default_host/sap/bc/echo

- Among other things, this service returns information about the registration procedure
being used, the header and form fields, and the generated SSO cookie for the executed
request. Therefore, this service should only be activated for troubleshooting purposes.

/default_host/sap/bc/error

465
 - This service generates some error situations in the system and should only be activated
for troubleshooting purposes.
/default_host/sap/bc/srt/xip/sap

- You want to fix the Web service error message "Could not determine WSDL address
(ICF_ERROR), SRT_REG038" in connection with XI services.
NOTE: Above details are as per Note 517484.

12.2. Services to which a Service User must be assigned

hrrcf_apply_ext Apply with Reference Code (Non Registered Candidate)

hrrcf_cand_reg External Candidate, Registration

hrrcf_unrg_srch Non Registered Candidate, Job Search

hrrcf_search General Search Application

hrrcf_unrg_appl Non Registered Candidate, Application Wizard

hrrcf_pinst_pbl Posting Instance Publication Internal / External

hrrcf_pinstappl Posting Instance Publication Internal/External branches to the application wizard

hrrcf_password Administration of User Passwords

hrrcf_ee_srch Search for Internal Postings (without first logging on to the system)

Application Wizard (Entry)

hrrcf_ee_awzd (application wizard is called after a successful search for internal postings)

466