HCM BBP Inlogistics v02
HCM BBP Inlogistics v02
HCM BBP Inlogistics v02
Document History:
Design Specification Title:
Module:
Business Process:
Version: 1.0
Page:
Page 1 of 86
Date Created:
Date Approved:
Change History:
Date Modified
Modified By
Transport No.
Version: 1.0
Page:
Page 2 of 86
Table of Contents
1. Project Introduction........................................................................................................................................6
2. Introduction to HR module in SAP.................................................................................................................6
3. Organizational Structure.................................................................................................................................7
4. General Process Details Personal Administration.......................................................................................9
1.1.1Personal Action -> Hiring
9
Current Business Process........................................................................................................................................9
Explanations of Functions and Events....................................................................................................................9
1.1.3Solution in SAP.............................................................................................................................................10
1.1.3.1Process Diagrams ......................................................................................................................................11
1.1.3.2Changes to Existing Organization processes.............................................................................................11
1.1.3.3Description of Improvements.....................................................................................................................11
1.1.4Integration considerations.............................................................................................................................12
1.1.5Authorization Requirements.........................................................................................................................12
1.1.6File Conversion / Interface Considerations...................................................................................................12
1.2Confirmation
12
1.2.1Business Process...........................................................................................................................................12
1.2.2Business Requirements.................................................................................................................................12
Description of Improvements................................................................................................................................12
1.2.3Solution in SAP.............................................................................................................................................13
1.3Transfer
13
1.3.1Business Process...........................................................................................................................................13
1.3.2Business Requirements.................................................................................................................................14
1.3.3Solution in SAP.............................................................................................................................................14
1.3.3.1Process Diagrams ......................................................................................................................................15
1.4Promotion
15
1.4.1Business Process...........................................................................................................................................15
1.4.2Business Requirements.................................................................................................................................15
1.4.3Solution in SAP.............................................................................................................................................15
1.4.3.1Process Diagrams ......................................................................................................................................16
1.5Salary Revision
16
1.5.1Business Process...........................................................................................................................................16
1.5.2Business Requirements.................................................................................................................................17
1.5.3Solution in SAP.............................................................................................................................................17
1.6Separation
17
1.6.1Business Process...........................................................................................................................................17
Description of Improvements................................................................................................................................19
1.6.3Solution in SAP.............................................................................................................................................19
1.7Define Number Ranges
19
1.7.1Business Process...........................................................................................................................................20
1.7.2Business Requirements.................................................................................................................................20
1.7.3Solution in SAP.............................................................................................................................................20
5. General Process Details Organizational Management...............................................................................20
General Explanations............................................................................................................................................20
1.10.2Process Diagrams .......................................................................................................................................23
1.11Integration considerations..............................................................................................................................24
Last changed on:
Last saved by: xxx
Version: 1.0
Page:
1/20/2014 1/20/2014 Draft for discussion purposes only
Page 3 of 86
Version: 1.0
Page:
Page 4 of 86
Version: 1.0
Page:
Page 5 of 86
1. Project Introduction
Inlogistics is currently in the process of implementing SAP ERP 6.0 as a central ERP application for
managing their business operations. Bristlecone India Ltd. has been selected as the external service
provider for providing services to Inlogistics for this project.
The following modules of SAP ERP are being implemented as part of this project:
Sales & Distribution
Materials Management
Finance & Controlling
Human Resources
The business blueprint document (this document) captures the high level requirement, and its solution
into SAP for the Human Resources function as applicable in the Inlogistics.
This document is organized into 12 major Sections, including this section. Following is a brief description
of all sections:
Version: 1.0
Page:
Page 6 of 86
Section
Description
1.
Introduction
2.
Enterprise Structure
3.
Organization Management
4.
Personnel Administration
5.
Recruitment
6.
Personnel Development
7.
8.
Time Management
9.
Payroll
10. ESS
11. MSS
3. Organizational Structure
Enterprise structure is used to define the company structure with respect to Human Resources. First
analyze the structures and procedures in the company, and then match them to the SAP structures.
The business requirements shared by Core Team Members are mentioned below: To capture all the physical locations where the offices have been situated.
Last changed on:
1/20/2014 1/20/2014
Version: 1.0
Page:
Page 7 of 86
To group the employees in officers category according to type of their employment in the
enterprise. Example: Active, Pensioner, Trainee etc.
To capture the employees according to their level in the enterprise.
The following items will be configured in SAP to address the requirements of the processes mentioned by
core team:
Company Code
A four character alpha numeric code is used to define the company.
Personnel Area
Personnel Area: A four character alpha numeric code is used to define the geographical location.
Naming Convention:
o First two characters will be the first two characters of company code to which that particular
personnel area belong.
o Next two characters will be running serial numbers.
Personnel Subarea
In Inlogistics, personnel sub areas are defined in terms of different departments operating in the
company. Personnel sub areas are created under one particular personnel area.
Naming Convention:
o Four digit running serial number.
Employee Group
A category of employees are grouped in one group and are defined by one alphanumeric
character in SAP.
Naming Convention:
o Employee groups are defined by single alpha numeric character.
Employee Subgroup
Employees are further divided into subgroups according to similar scales / grades or levels.
Employee subgroups are defined by two alphanumeric characters in SAP.
In Inlogistics employees are subdivided according to their designations.
Naming convention:
o Employee sub groups are defined by two alpha numeric characters.
Assignment of Personnel Area to Company Code
Personnel area is linked with the company code by assigning company code to personnel areas.
List of Structure Items that will be configured for Inlogistics:
Groups.xls
Version: 1.0
Page:
Page 8 of 86
Version: 1.0
Page:
Page 9 of 86
Hiring Actions along with reasons will be configured in SAP. The structure of the actions and
reasons thereof has been changed in order to make it more comprehensive, qualitative and more
meaningful specifically for Inlogistics purpose.
The history of change at info type level can be maintained and can be viewed subsequently.
The following actions and reason for actions are identified in INLOGISTICS.
When a person is hired he/she shall be assigned an employee number based on the employee
range defined.
The generation of personnel numbers is explained in Sub Process Define number ranges of this
BBP document.
Mandatory Info types are maintained during the Hiring action and other applicable info types are
maintained using transaction PA30.
Every new Employee undergoes Induction program and integrating through the Training and
Event Management Module can capture this.
The reasons for personnel action Hiring are given below:
Expansion
Replacement
Re Hire
New Hire
Post Retirees
0000
0001
0002
0006
0007
0008
0014
0009
0016
0019
0021
0022
0023
0041
2002
Action
Organizational Assignment
Personal Data
Addresses
Planned Working Time
Basic Pay
Recurring Payments and Deductions
Bank Details
Contract Elements
Monitoring of Tasks
Family Member/Dependents
Education
Previous Employers details
Date Specification
Attendance types
Version: 1.0
Page:
Page 10 of 86
Infotype
16
17
0105
0185
Infotype Text
Communication
Personal Ids
For a particular personnel number only one action can be recorded on a particular day, under Actions Info
type. 0000. This action shall be the one which is associated with change of Employment status of the
employee. Any additional actions that are performed shall be recorded in Info type 0302, Additional
Actions. Direct entry in this info type is not possible
1.1.3.1
Process Diagrams
Dataflow from Recruitment
Dataflow from Recruitment
Module to PA Module (If
Module to PA Module (If
required)
required)
1.1.3.2
In SAP, each Infotype record is stored with from and to date. So, only those actions, which are significant
and necessitate change in more than one Infotype, will be passed through Action Transaction.
All activities related to change in employee data would have to be carried out in SAP. E.g. Change in Pay,
Promotions, and Transfers etc.
In case an employee data changes with respect to his/her Personnel Area, Personnel Sub Area,
employee Group or Employee Sub Group then the same must be communicated to HR
Department. In case these changes are not intimated to HR Department or HR Department does
not make changes on the system then the system shall display incorrect data in all reports and
the employee headcount reports shall also be incorrect.
Any change in employee details with respect to family details and other personal data must also
be updated in the system to enable the system to display updated information in all reports.
No change in salary of the employee will happen unless an action, which resulted in change in
pay, is maintained in SAP along with all revised data.
1.1.3.3
Description of Improvements
Version: 1.0
Page:
Page 11 of 86
1.2 Confirmation
Confirmation process is initiated when an employee successfully completes the probation period.
Description of Improvements
Usage of actions ensures that all master data records are maintained for each employee
Version: 1.0
Page:
Page 12 of 86
All information regarding the employee will be immediately available online across the various
locations/divisions.
There will be standardization of processes across locations/divisions.
Employee history shall be maintained in the system.
0000
0002
0001
0008
0014
0016
0016
Subtype
Actions
Personal Data
Organizational Assignment
Basic Pay
Recurring Payments and Deductions
Contract Elements
Limited Contract
Contract Elements
Unlimited Contract
The possible reasons for the personnel action - Confirmation are given below:
1. Successful completion of probation
2. Successful completion of Training
1.3
Task for the reminder of the Confirmation date will be maintained in the Infotype 0019
Monitoring of Tasks so that monthly reports can be generated and employees due for
confirmation can be tracked.
List of employees due for confirmation will be generated by HR by maintaining info type
0019(Monitoring of Task).
On Dissatisfactory performance probation may be extended and is dealt with under Extension of
Probation BBP.
On successful completion of probation if employees are promoted or transferred then these
processes will be handled by different action and the same is described in BBP documents of
Promotion and Transfer Actions respectively.
Transfer
Version: 1.0
Page:
Page 13 of 86
Currently, when the employee is transferred to the new location, the date of reporting is
considered as date of transfer.
On transfer, leaving date from the old location to the new location is also maintained.
All transfer orders are generated from the corporate office.
After the transfer order, the date of relieving and date of reporting are tracked. A consolidated
report is generated on monthly basis.
Transfer can be given either with promotion or without promotion which may affect change in pay
as well.
Transfer-cum-Promotion will be effective from the date of reporting.
The Info types used for recording the relevant information are as follows:
No.
Infotype
Infotype Text
01
0000
Actions
02
0001
Organizational Assignment
03
0006
Addresses
05
0007
Planned Working Time
06
0008
Basic Pay
07
0009
Bank Details
Transfer means initiating the process of assigning a different position / location to an employee in any of
the following cases:
Change in Org Unit
Change in Personnel Area / Personnel Sub area
Change in Pay roll area
Change in work schedule
Change in Reporting relationship
Change in grades, pay structure
Change in Address
Last changed on:
1/20/2014 1/20/2014
Version: 1.0
Page:
Page 14 of 86
1.3.3.1
Process Diagrams
Receive
Receive
Approval
Approval
from the
from the
Appropriate
Appropriate
Authority
Authority
1.4
Update
Update
Time/PA
Time/PA
information in
information in
SAP
SAP
For location
For location
change, Org.
change, Org.
assignments data
assignments data
will be updated.
will be updated.
Promotion
Promotion process is initiated when an employee qualify to move to next level on the basis of his
performance.
Version: 1.0
Page:
Page 15 of 86
0000
0001
0008
0014
0015
Actions
Organizational Assignment
Basic Pay
Recurring Payments and Deduction
Additional Payments
Promotion Letter to be generated through SAP System and will be given to the employee through HOD.
1.4.3.1
Process Diagrams
Promotion action is
Promotion action is
carried out in SAP
carried out in SAP
1.5
Mail is sent to
Mail is sent to
employee. (Non-SAP)
employee. (Non-SAP)
Payroll information is
Payroll information is
updated in SAP
updated in SAP
Salary Revision
Version: 1.0
Page:
Page 16 of 86
System to update Employee Master Data when there is a change in Salary Structure
To reflect changes in all fields pertaining to earning.
0000
0001
0008
0014
0015
Subtype
Action
Organizational Assignment
Basic Pay
Recurring Payments / Deductions
Additional Payments
Salary Increment Letter to be generated through SAP system and will be given to the employee through
HOD.
1.6
Separation
Separation process is initiated when an employee leaves or is terminated from the services of the
organization.
Version: 1.0
Page:
Page 17 of 86
Version: 1.0
Page:
Page 18 of 86
Description of Improvements
All Separated employee details like date of separation, reason for separation will be available online
Ceasing of Apprenticeship
Probation Termination
Resignation
Termination
Retirement
Deceased
Dismissal
Abandonment
Infotypes to be maintained
The Infotypes used for recording the relevant information are as follows:
No.
Infotype
Infotype Text
01
02
03
04
05
06
07
0000
0001
0002
0006
0007
0014
2006
Action
Organizational Assignment
Personal Data
Addresses
Planned Working Time
Recurring Payment and Deduction
Absence Quota
All the Infotypes listed above other than Infotype 0001 Organizational Assignment, IT 0002 Personal
Data, IT 0008 Basic Pay will be delimited. In Infotype 0001 a record is created for the post-separation
period with Position as the Default Position, so that the employee ceases to be shown in Organization
Chart after his separation.
1.7
Version: 1.0
Page:
Page 19 of 86
The Personnel Number in SAP shall be a serial number internally generated by SAP.
Numbering of the existing employees of all categories will be on the basis of date of joining.
Category
00000001-19999999
General Explanations
Currently the HR department maintains the organization units and the reporting structure using the
following:
Departments
Designations
Grade
Category
Employees
Version: 1.0
Page:
Page 20 of 86
Based on the requirement for new positions, the HOD of the particular department discusses the same
with the Functional head and gets approval from FH and forwarded to Head HR. The new positions are to
be approved by the BG Head / CMD /MD. Once it is approved, the same is created in the organization
structure.
1.9
Business Requirements
Current requirement and expectation from INLOGISTICS side for OM processes are as follows:
To reflect the functional structures of the organization.
To reflect the reporting structures of the organization.
To get a glance of the entire organization structure with all the positions and persons
Identification of Jobs on system for each employee / position.
List of position drop down is required based on the organization units
For new position / organization unit on line request and approval process is required
Manpower status reports is required based on location, organization unit
Dual / dotted (functional / administrative) line reporting relationships to be maintained
Management of new positions,
Monitoring and managing unoccupied positions
On-line creation /change of positions/Job/Task subject to authorization
Version: 1.0
Page:
Page 21 of 86
Object
Relationship
Belongs to
Incorporates
Describes
Is Described
Describes
Is Assigned To
Related Object
Organizational Unit (O)
Position (S)
Position (S)
By Specific Tasks (Ts)
Position (S) & Job (C)
Position (S)
Creation of existing Organizational Units will be deemed to be same as date of creation of Cost Center in
FI/CO.
Last changed on:
1/20/2014 1/20/2014
Version: 1.0
Page:
Page 22 of 86
1.10.1 Purpose
Based on the requirement, all new departments/sections are to be approved by the BG Head /
CMD/MD. The communication will be intimated to all by HR Department.
To maintain Dual / dotted line (functional / administrative) reporting relationships.
To maintain Roles for each position.
To assign Cost centers on Org. Unit base only.
To generate Manpower status report based on grade / location/ org. unit wise by HO on monthly
basis.
P
KOPCS Relationship
O Organizational Unit
K Cost centre
C Jobs
S Positions
P Person
.
Version: 1.0
Page:
Page 23 of 86
While creating new Jobs/ Positions, care has to be taken to ensure that these are role-based and
not designation-based, and that the process outlined is followed. Proper Manpower Planning will
have to be made while depicting the role-based organization
1.10.4 Prerequisites
None
Transaction Code
S_AHR_61016498
S_AHR_61018869
S_AHR_61016502
S_AHR_61016509
S_AHR_61016492
Version: 1.0
Page:
Page 24 of 86
Solution in SAP
This will be maintained in wage type for CTC,
Basic and PLI HR user will maintain these wage
type in info type 0008 Basic Pay
This data will be maintained by HR user in info
type 2001 Absences for respective absence
types
This will be maintained in wage type for PF, HR
user will maintain this PF wage type in info type
0014 Recurring deductions
This will be maintained in wage type for cafeteria
deduction, HR user will maintain this deduction
wage type in info type 0014 Recurring
deductions
This will be maintained in wage type for loan
deduction, HR user will maintain loan type in info
Version: 1.0
Page:
Page 25 of 86
Solution in SAP
type 0014 Recurring deductions.
This will be maintained in wage type for
Telephone excess usage deduction, HR user will
maintain Telephone excess usage type in info
type 0014 Recurring deductions.
This will be maintained in wage type for Advance
deduction, HR user will maintain loan type in info
type 0014 Recurring deductions.
This will be maintained in wage type for Other
deduction, HR user will maintain loan type in info
type 0014 Recurring deductions.
This will be maintained in wage type for
Miscellaneous Payments, HR user will maintain
loan type in info type 0015 Additional
Payments.
1.17.1 Purpose
Maintenance of salary wage type amount in infotype 0008 employee wise (Personnel no.) in the
specific period.
Maintenance of deduction wage type amount in infotype 0014 employee wise (Personnel no.) in
the specific period.
Maintenance of additional payment wage type amount in infotype 0015 employee wise
(Personnel no.) in the specific period.
Payroll Infotypes where data shall be collected are listed below along with the upload strategy
S. No
Infotype
Infotype Name
Upload Mechanism
1
0008
Basic Pay
Last saved by: xxx
Draft for discussion purposes only
BDC/ LSMW
Version: 1.0
Page:
Page 26 of 86
0009
Bank Transfers
BDC/ LSMW
0014
BDC/ LSMW
0015
Additional Payments
BDC/ LSMW
Through BDC (Batch Data Collection Processing) or through LSMW (Legacy System Migration Work
Bench) data shall be loaded in to the system.
1.17.4 Prerequisites
None
Transaction Code
PC00_M99_CWTR
S_PH0_48000512
Description
Master data of the employee and the actions related to processes
Version: 1.0
Page:
Page 27 of 86
Wage Type
Description of Improvements
Followings are the improvements of payroll process been executed in SAP:
Single window for monitoring all the payroll related activity
General Explanations
Personnel Development (PD) module is a very powerful tool in SAP HR, enabling value added HR
services to an organisation. This module provides the organisation effective systems to automate HR
functions such as Development Plans, Succession Plans, Appraisals, and Profile Match-up etc. Another
interesting feature of this module is the Qualification catalogue which finds applications in the above
mentioned functions.
This section deals with use of appraisals in SAP HR PD used for evaluating performance of an officer in
Inlogistics. This is a multi stage appraisal and would involve Objective setting and evaluation on multiple
appraisal criteria
Version: 1.0
Page:
Page 28 of 86
Version: 1.0
Page:
Page 29 of 86
In SAP, Competencies (Qualification) / job skill sets available for each position/job means
Qualification catalog. If available, Inlogistics will be able to map the entire list of Qualifications
being used in the organization.
Various qualifications will be grouped under qualification groups so that the qualifications can be
accessed easily in the qualification catalogue
Qualification catalogue will be interfaced with the following modules
o Organization Management
o Training & Event Management
The following objects will be used for maintaining the Qualification Catalogue:
o Qualification Group
o Qualification
The user may create multiple qualification groups within a qualification group. This helps the user
in segregating the qualifications, rather than cluttering them together.
Qualifications will be standardized as far as possible to be incorporated in the qualification
Catalogue. This is to enable the users to compare employees qualifications among various
business units.
The system will provide the provision to create the qualification requirement profile for jobs as well
as positions.
Any qualification requirement profile attached to the job will be inherited by the position linked to
this job.
The provision for identifying Qualification Requirement profile can be implemented only if the
Standard Qualifications are identified across businesses. As the job list is common among
businesses, the standardized common qualifications can only be attached to Jobs.
The system allows performing the profiles match-up between a set of persons and positions/jobs
resulting into display of qualification deficit or additional qualifications.
In case of qualification deficit for an employee, the employee can be booked / pre booked for the
Business Event (training course) that imparts the qualification.
The user can update the employees qualifications on completion of a Business Event (Training
course) so that the qualification imparted by the Business Event can be updated to the employees
qualification profile.
The qualification catalogue on the whole will look something like as given below Qualification
catalogue:
Qualification Catalogue
Qualification Group
Sub Qualification Group e.g. Management
Qualification e.g. Leadership
Qualification e.g. Cooperation
Sub Qualification Group e.g. Languages
Qualification e.g. French
Qualification e.g. Deutsche
Qualification group
Sub Qualification Group
Qualification
Version: 1.0
Page:
Page 30 of 86
And so on
Profile Match-Up:
Profile Match-Up is used to compare an employee/applicant qualifications with the requirements
of the position to see how suited the employee/applicant to that position.
Profile Match-Up can be performed for several objects.
Profile Match-Up provides option to:
Find out how suitable one or more persons for a position.
Identify persons who are over-qualified or under-qualified.
Identify suitable applicants for a vacancy.
Identify appropriate training options for persons.
Check the current level of qualification in an organizational unit.
Check the need for training in an organizational unit.
Profile Match-Up compares the qualifications and requirements of objects (employees, applicants) with
jobs/positions. The required and existing proficiency of each qualification is also taken into account. The
following options are available for selecting the objects to be included in a profile match up
The objects to be included in the match up are specified individually.
The profile matchup is executed directly from the profile of a person/position for the position.
The profile matchup is executed for all persons in an organizational unit and the positions they
currently hold.
The following selection options are available:
Restrict the selection to qualification deficits (in other words, the proficiency of the Qualification
held is lower than the proficiency required).
Determination of training proposals for qualification deficits.
Key date for the evaluation.
The results of the profile match up can view as graphics and tables.
Performance Management System
Sequential organization of functions and activities is described as process. The process adherence
respective to this module is explained in the following.
This is a multi stage appraisal based on Objective setting and evaluation. The process flow for the Annual
Performance Evaluation is given in the following figure
This appraisal would have the instruction steps visible to the appraisers and appraise for facilitating the
process
Version: 1.0
Page:
Page 31 of 86
Support Team like HR, IT etc employee group. The rating for each KRAs are noted down
for appraises, part appraiser and appraiser.
SAP Process -> This in SAP will be equivalent to updating the appraisal form by
appraise, part appraiser and appraiser at the end of each 4 months or half year based on
their employee groups. Her in SAP only the scale for rating will be populated, the criteria
for deriving on a particular rating will not be considered in SAP.
1.25.1 Purpose
Significance of KRA Ratings: (To Be Discussed)
For Support team KRA appraisal will take place two times in a year.
For Sales, Marketing and Operations group employees KRA appraisal will take place 3 times in a
year.
Diagrammatic representation of the KRA appraisal process for Support team is described below:
Version: 1.0
Page:
Page 32 of 86
Discussion
Discussion&&
approval
approvalofofKRA
KRA
&&Targets
Targets
Part
Appraiser/Appraiser
KRA
KRAaddition/
addition/
deletion/
deletion/
modification
modification
Appraiser
Appraiser
Evaluation
Evaluation
Reviewer
Reviewer
Evaluation
Evaluation
Appraiser
Performance contracting
Identification
Identification
ofofKRA
KRA&&
Targets
Targets
Self
Discussion
Discussion&&
approval
approvalofofKRA
KRA
&&Targets
Targets
Part Appraiser/Appraiser
Superior
Superior
evaluation
evaluation
Appraiser
Compilation
Compilation
ofofoverall
overall
score
scoreby
byHRD
HRD
HRD
Communication,
Communication,
Counseling
Counseling&&
Feedback
Feedback
HRD
Version: 1.0
Page:
Page 33 of 86
Starting
Date
20th March
Closing Date
30th March
1st July
7th July
1st Oct.
7th Oct
1st Jan
7th Jan
11th March
31st March
1st April
20th April
7th April
30th April
Transaction Code
Profile Matchup
PEPM
Appraisals
APPSEARCH
Careers
S_AHR_61015524
Succession Overview
S_PH9_46000017
Qualifications Overview
S_PH9_46000016
Description
Organizational Management
Version: 1.0
Page:
Page 34 of 86
S. No
1
2
3
Object
Object Type
BADI
BADI
New form of appraisal
Version: 1.0
Page:
Page 35 of 86
Behavioral
Technical
General
Calculate the Competency gap for all the employees from the required level
Also fill the additional training list which is required to define all the core competencies as well the
additional competencies which is required to perform the respective job
Preparation of Training Calendar on the basis of all the training needs identified
In case if any have to go outside for attending any particular training which may not be possible to
arrange within the company then all these external training should be approved duly in advance from the
approving authority
List of participants of the training
Scheduling of training as per training calendar and ensure the training has been done
Attendance of all the participants in the training attendance sheet
After completion of following defined period the training effectiveness is to be evaluated in which the skill
level is also defined.
Level 1 (within 5days of training)
Level 2 (after 1 month of training)
Level 3 (After 3 months of training) only for technical trainings
Updating of individual training records as & when he undergo any training program
Version: 1.0
Page:
Page 36 of 86
Behavioral
Technical
General
Version: 1.0
Page:
Page 37 of 86
1.33
HR user
for each
PV33 template
format
Solution in SAP
The following items will be configured in SAP to address the requirements of the processes mentioned by
core team:
Business Event Group
Business Event Group serves to classify business event types that share the same characteristics or deal
with related subject matter, such as Management Courses. A business event group Communication
Skills can contain a number of business event types, such as Oral Communication Skills, Effective
Presentation Skills etc.
Following information for business event groups are stored:
Long and short name like code CO with description, CHANGE ORIENTATION
Description of contents
Relationship to other event groups (belongs to) and to business event types (incorporates).
Business Event Type
A Business Event Type is a generalized description of an event including the relevant information such as
description, Target Audience, Categorization, Course contents, price, capacity, Notes (Program
Objectives/deliverables) and language etc. It is not scheduled to take place on a fixed date. It serves as
the blueprint from which actual event dates can be scheduled.
When business event type is created, it is possible to store any data that is not time-sensitive such as:
Version: 1.0
Page:
Page 38 of 86
Each Business Event Type should have a relationship with its Business Event Group. Other resources
are also related to the Business Event type.
Resource Types & Resources
A resource type is a classification of resources that share the same characteristics or attributes, such as
PCs, training material and so on.
Resource Types are categorized as under:
Room
Instructor
Material
Version: 1.0
Page:
Page 39 of 86
Internal / external
o An internal business event is an event that company is responsible for organizing.
o An external business event is organized by a third-party (Indian/Foreign). It is not
possible to plan an external business event; resource reservation for it is not taken care
of. External events are created one at a time.
Schedule
o There are two possible ways to specify the actual time schedule of a business event. The
schedule will contain four or more sessions in a day.
- By copying the schedule model defined for the business event type.
- By creating schedule for the business event - Schedule is required to be created for
different business event type.
Number of attendees
o The capacity i.e. the number of attendee for each event type is given as minimum,
optimum or maximum. There is a facility for booking of waiting list attendee for the event
type till maximum number is reached for the event type. This facilitates rebooking or
replaces attendee as well.
Version: 1.0
Page:
Page 40 of 86
Version: 1.0
Page:
Page 41 of 86
Object
Relationship
Version: 1.0
Page:
Page 42 of 86
Master Data
Business event
group
and
business event
types are finally
to be created
by HR core
team as per the
requirement.
Infotype
Number
Description
1002
1063
Field Name
Master Data
Priority
Subtype
Language
Description
Subject Area
Object
1000
Relationship
1001
Description
1002
Price
1021
Capacity
1024
Depreciation meter
1025
1029
Procedure
1030
Validity
Object Abbreviation
Object Name
Language Key
Validity
Relation Type/Relationship
Type Of Object Related
ID Of Object Related
Abbreviation
Name
Priority
Subtype
Language
Description
Validity
Internal Price
External Price
Validity
Optimum
Maximum
Minimum
Validity
Year
Month
Validity
Include In Business Event
Brochure
Convention
Attendee Type
Bookt
Prebt
Version: 1.0
Page:
Page 43 of 86
Business event
group
and
business event
types are finally
to be created
by HR core
team as per the
requirement.
Infotype
Number
Delivery method
5008
Object
Resource
1000
Relationship
1001
Description
1002
Capacity
1024
Address
1028
Cost
1036
Field Name
Chpre
Checkq
Quals
Delivery Method
Planning Status
Validity
Object Abbreviation
Object Name
Language Key
Validity
Relation Type/Relationship
Type Of Object Related
ID Of Object Related
Abbreviation
Name
Priority
Subtype
Language
Description
Validity
Optimum
Maximum
Minimum
Building
Address Supl
House No Street No
Street
Pcode/City
Room No
Tele No
Cost Item
1.33.1 Purpose
Maintenance of business events
Maintenance of business events types
Recording attendance
Last changed on:
Last saved by: xxx
1/20/2014 1/20/2014 Draft for discussion purposes only
Master Data
Version: 1.0
Page:
Page 44 of 86
All
resources
are dependent
on the event
type.
Resources data
will be finalized
depending on
the
event
types.
Cancellation of attendance
Appraisals
Follow up activity
Begin
Finalization
of catalog by
Functional
Expert Team
Updating
of Catalog
Booking Resources by
Trg. Agencies
Pre-booking by
Officers / approval by
superior
Booking attendees to
events by Trg.
Agencies.
Acknowledge pre-booking
and send format to collect
expectation from the officer.
End
Figure 1: Planning & Creation of Business Event Type & Day to Day Activities
Version: 1.0
Page:
Page 45 of 86
Begin
Conducting the event by Trg.
Agencies
Program Feedback
Immediate Attendee
Feedback Analysis for
improvement
Attendee Feedback after
three months
Feedback analysis for
improvements
End
Training Catalogue is prepared according to the need and organizational need by a panel of
expert, which can be chosen by the attendee.
Event Type is evaluated by attendee and its implication in work area is evaluated by supervisor.
So, realistic worth of the event type is established
1.33.4 Prerequisites
None
Report required
1
2
3
4
Gap report
Training Need record
List of participants
Effectiveness of training
5
6
1.33.6 Improvements
Last changed on:
1/20/2014 1/20/2014
Version: 1.0
Page:
Page 46 of 86
Description
PD
Profile match up
Career planning
Succession planning
PA
OM
Description
PD
Report on PD compliance
PA
The
event
type
linked
qualification is updated.
with
Object
Training feedback appraisal form as per Inlogistics format
Object Type
New appraisal
template
Version: 1.0
Page:
Page 48 of 86
9.
The Time Management component offers support in performing all human resources processes for
recording employees work performed and absence times.
Time Management has user-oriented interfaces that support centralized and decentralized entry and
administration of time data. Data can be maintained and processed centrally by administrators in the
human resources department or else in individual departments by time administrators such as
supervisors, secretaries, and employees themselves.
Employees can use self service applications to request leave, record working times for orders or projects,
for example, and display their key time accounts.
Version: 1.0
Page:
Page 49 of 86
Earned Leave
Maternity Leave
Casual Leave
Paternity Leave
Leave without Pay (LWP)
Earned Leaves
EL Rules:
An employee shall be entitled for 18 EL per calendar year.
1.5 EL per month will be credited to each employee absence quota.
Maximum limit of EL quota will be 45 for each employee.
All leave types for less than a day / fraction of a day is permissible.
Casual Leaves
CL Rules:
An employee shall be granted for 12 CL in a calendar year.
If an employee joins during a calendar year, he/she shall be entitled to CL for remaining part of
Year on a Pro-rata basis.
Maximum 3 CL can be availed at one time.
Leaves Approval
Leave rules: In exceptional circumstances, where an employee has no leave accumulation standing to his credit
and his need is genuine, the Sanctioning Authority may grant advance Leave subject to a maximum
of 7 days. The sanctioning authority for such leave will be Unit Head / Corporate Functional Head.
AS-IS Business Process
Leave Generation
If the any employee joins between the years then
the leave credit in the account of the employee
will be on Pro-rata basis.
Make the leave card in which leave details are to
be mentioned.
Maintain the leave register.
Last changed on:
1/20/2014 1/20/2014
Version: 1.0
Page:
Page 50 of 86
Version: 1.0
Page:
Page 51 of 86
General Explanations
The Public Holiday Calendar is to be maintained in Inlogistics as per the Annual Public Holiday List
released by respective Inlogistics HR department, Corporate Office and other allied divisions.
There are two types of Holidays, National Holidays (Fixed Holidays) which fall on the exact date of every
year and Movable Holidays (Festival Holidays) which keep changing every year. For e.g. Independence
Day (15th August) would be a fixed holiday whereas festivals like Maha Shivarathri are movable which
may fall on a different date.
Holidays, which have fallen on a working day during the current year, may fall on a weekly off day
in the subsequent year, there by necessitating the recreation or change of the holiday list every
year.
This changed list of holidays is assigned to the Public Holiday Calendar every year.
Separate Holiday Calendar would be created for each and every location and corporate office.
Creation of paid holidays would be done every year according to the calendar adopted by
Inlogistics and would be updated into the system by the concerned HR administrator.
The created paid holidays would be then be assigned to the Public Holiday calendar.
Work Schedule
Creation and maintenance of Enterprise specific Works Schedules to store the working timings (Shift
Timings) and the corresponding break times for the different Inlogistics Officers/Employees
General Explanations
To create and maintain the records of different work timings and scheduled break timing followed
by the employees of Inlogistics.
Generation of weekly off day of each and every employee needs to be tracked.
Shift wise present details should be made available.
Shift wise absent details of employees.
The Shift Details and the break timings are maintained for each employee at the respective
departments.
Any deviation from the normal shift timings get recorded as a discrepancy and are processed
subsequently after approval
Last changed on:
Last saved by: xxx
Version: 1.0
Page:
1/20/2014 1/20/2014 Draft for discussion purposes only
Page 52 of 86
The Infotype Planned Working Time (IT 0007) in Personnel Administration facilitates to store work
schedule for each employee and consequently the working hours and days for the employee is
inherited from the Work Schedule specifications.
By assigning a work schedule rule to an employee, the entire work schedule (the working time
including the shift patterns) including holiday calendar can be viewed and reported for the period
specified.
The Planned Working Time (Infotype 0007) captures Time Management Status, which will be
defaulted as 7 Time Evaluation without Payroll Integration for Managerial Staff and 0 No Time
Evaluation. The Time Management Status is of vital importance as it determines how the
employees are processed in Time Evaluation(Time Evaluation calculates planned times and
overtime, administrates time accounts and forms wage types, updates time quotas, and is used to
check working time specifications.)
The change in the work schedule as a result of transfer or reassignment has to be updated in the
Planned Working Time (Infotype 0007) so that the time data is processed as per the updated
timings.
Inlogistics need to update the Holiday Calendars every year and this requires the generation of
the respective Work Schedules for the changes to take effect.
Generally the Personnel Areas and Personnel Subareas, Employee Groups and Employee
Subgroups get grouped for the different work schedules. This allows the generation and the
subsequent assignment of the work schedules to various groups of employees.
Work Schedules define the working pattern together with the paid and unpaid break timings for
different groups of employees and are based on the public holiday calendar. The various
locations of Inlogistics have separate Holiday Calendars and separate Shift and Break Timings.
Break Schedules define the rule governing breaks (a period of time when employees are not at
work) in a workday.
By assigning a Work Schedule Rule in the Planned Working Time (Infotype 0007) the employee
personal planned working time gets determined.
The Planned Working Time (Infotype 0007) determines employees working time within an
organization on a daily basis.
1.41.1 Purpose
To ensure the availability of General (Public) Holidays to the various offices of Inlogistics & its Employees
For all units and corporate office, Public Holidays are finalized and fixed at the year beginning itself. All
Holidays are Full day Paid Holidays
Version: 1.0
Page:
Page 53 of 86
Name of the
Info type
Planned
working time
Absence
Quotas
Absence
02
03
Info type
Number
0007
2006
2001
Field Name
Start and end date, Work
schedule rule
Validity period, Quota sub type
Quota number
Start and end, Type of leave,
Absence hours, Absence days
The holiday calendar for a Calendar Year is released by Inlogistics in advance in the month of
December.
This Holiday Calendar is the reference for providing Public Holidays to the employees of
Inlogistics
1.41.4 Prerequisites
Appropriate work schedule in infotype 0007 have to maintained to the time status.
Transaction Code
PT03
PT64
PT90
PT63
SAP Query
SQ01
Version: 1.0
Page:
Page 54 of 86
Description
Master data of the employee
Organizational Management
1.44 Authorization
Specific authorization will be maintained as per the data provided by the core team during the realization
phase.
1.46 Improvements
Version: 1.0
Page:
Page 55 of 86
Version: 1.0
Page:
Page 56 of 86
Manpower Plan
Approval on manpower specification sheet
Job description
Source of Recruitment
Database of CVs
Interview Assessment
Finalize the date of interview and Invite all the shortlisted candidate for interview.
Page:
Page 57 of 86
Version: 1.0
Page:
Page 58 of 86
Version: 1.0
Page:
Page 59 of 86
Ap Cl
(Char/ 02)
P
AP
AP
AP
AP
AP
In case the vacancy is to be filled through internal data base, then the individual basic data maintained in
SAP in the category Unsolicited Applicant will be used.
In case the vacancy is to be filled from existing officers, then consideration set will be generated from the
employee data base maintained in SAP.
Employee referral cases will be identified from the applicants data. The format will contain a field to
capture Employee Personnel Number and Name in case of direct recommendation from any officer of
Inlogistics..
Recruitment Instrument
Recruitment instruments are the modes through which the vacancy is advertised. Every job advertisement
is published in the recruitment instrument. Recruitment instruments are classified according to the media
used.
A contact name and address key can be stored for each recruitment instrument. The following recruitment
instruments shall be maintained for Inlogistics.
ID
Name of Recruitment
Medium
Last changed on:
Last saved by: xxx
Version: 1.0
1/20/2014 1/20/2014 Draft for discussion purposes only
Address
Page:
Page 60 of 86
National dailies
Press
000000002
Local Dailies
Press
000000003
Regional dailies
Press
000000004
Business Magazines
Press
000000005
000000006
INLOGISTICS Mailer
Job Portals
000000007
000000008
B-Schools
Engineering Colleges
Lotus Notes
Internet (job
portals)
Campus
Campus
instrument
Through
Corporate Communication
INLOGISTICS
Dept,
The list of institutes for campus recruitment is to be revisited every year on the basis of ranking
done for B-Schools / Engineering Colleges.
The lists of mediums & instrument are to be configured.
Recruitment Administrator shall decide the appropriate recruitment instrument for each vacancy
and then create the advertisement in the system and assign vacancies to each.
Applicant Group
An applicant group is used to group together applicants on the basis of the type of work relationship for
which they have applied. 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 groups to be used in INLOGISTICS are tabulated as below:
APPLICANT GROUP CODE
(CHAR/1)
1.
2.
3.
4.
5.
6.
7.
8.
9.
A.
APPL.GROUPTEXT (CHAR/20)
Non Officers
Employee Referral
Campus
Employee Ward
Through Consultant
Through Group HR
Internal Employee
External reference
General Applicant
Unsolicited Applicant
APPLICANT CLASS
AP
AP
AP
AP
AP
AP
P
AP
AP
AP
HRM HR/IR
HRM HRI
HRM LEGAL
HRM ESTABLISEMENT
RH
Applicant Status:
In the recruitment process, an application is received by the organization. On receipt of the application,
the recruitment officer evaluates it for the suitability at two levels,
Whether the applicant is of interest to the company at all.
If yes, then for which particular vacancy or position he / she are to be processed.
The above situation is reflected in the SAP system by assigning an application status to the application.
All applications received are assigned an application status, for the various stages of processing. There
are two kinds of application status.
Overall Status:
This is the overall status of the application. This overall status reflects the nature of the companys
interest in the application at the global level.
For example, if the status is In Process, the application can be assigned to one or more vacancies,
depending on the suitability of the candidate. If this status is Rejected, the applicant is not suitable for
any vacant position. Only one overall status is maintained in the system per applicant.
Vacancy Status:
The vacancy status monitors the status of the application with respect to each vacancy assignment. This
is the status of the applicant with respect to each vacancy assignment. The applicant may be suitable for
several vacancies in the organization and hence several vacancy statuses may be maintained. The value
of vacancy status depends on Overall status.
For example, If the overall status is Rejected, the vacancy status cannot be In Process
The following status shall be maintained in the system:
Code (1A/N)
1.
2.
3.
4.
5.
6.
7.
8.
Version: 1.0
Page:
Page 62 of 86
Applicant status
In process
In Process
In process
In process
In process
In process
In process
In process
In process
In process
In process
In process
On Hold
On Hold
On Hold
On Hold
On Hold
On Hold
On Hold
On Hold
Rejected
Rejected
Rejected
Rejected
Rejected
Rejected
Rejected
Rejected
Rejected
Selected
Offer letter issued
Offer declined
Offer declined
Appt. letter issued
To be Hired
SR
01
02
03
04
05
06
07
08
09
11
12
10
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
Status Reason
Under Scrutiny (For internal application)
Initial Data Entry
Finalization of Panel / Schedule of interview
Under Written Test
Under Telephonic Interview
Called for Interview
Entry of assessment form
Medical Test Awaited
Salary negotiation Stage
To offer LOI
To offer appointment letter
To prepare Office Order / Circular
Waitlisted
Not willing to relocate
Freeze on employment
Awaiting business / growth plan
Credentials to be explored
Cancel Written Test
Cancel Telephonic Interview
Cancel Functional Interview
Insufficient skills
Overqualified
Under Qualified
Less Experience
Medically unfit
Not willing to relocate
Unsatisfactory reference check
Salary Mismatch
Offer Rejected by applicant
Selected
Suitable for the position
Less salary
Personal reasons
Offer letter accepted
To be Hired
Applicant Action
The Applicant Action serves as a record of all applicant actions carried out for an applicant.
Last changed on:
1/20/2014 1/20/2014
Version: 1.0
Page:
Page 63 of 86
Admissible combination of Applicant status to reason shall be maintained. These are as follows:
Code
Applicant Actions
Code
Applicant status
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
1
1
1
2
1
1
2
1
1
2
1
4
1
3
5
7
In process
In process
In process
On Hold
In process
In process
On Hold
In process
In process
On Hold
In process
Selected
In process
Rejected
Offer letter issued
Appt. letter issued
Version: 1.0
Page:
Page 64 of 86
Applicant Actions
Prepare for hiring
Offer rejected by the applicant
Code
8
6
Applicant status
To be hired
Offer rejected
Remarks
4002
Applicant Info type: Serves as a record of all applicant actions carried out for an applicant
Application Infotype: Store information on whether an application was made in response
to an advertisement, or is an unsolicited application
Assign the applicant to a vacancy
4003
4004
Applicant Activities
Applicant Activities can be used to enter the activities that have been created for an applicant.
Activities carried out for an applicant within a selection procedure are entered, logged and planned in the
Recruitment system by means of applicant activities.
Action
ACTION
ACTIVIT ACTIVITY
ACTIVITY (LONG)
ID 2
Y CODE (SHORT)
char
01
Initial data entry
001
Initiated
Initiated
02
Call for written test
002
Invite Applicant-WT
Invite applicant for Written
Test
03
Reschedule written test
003
Intimate
reschedule- Intimate
applicants
WT
regarding reschedule
04
Cancel written test
004
Intimate cancellation- Intimate
applicants
WT
regarding cancellation
05
Call for telephonic interview
005
Invite Applicant-TI
Invite
applicant
for
Telephonic Interview
06
Reschedule
telephonic
006
Intimate reschedule-TI Intimate
applicants
interview
regarding reschedule
07
Cancel telephonic interview
007
Intimate cancellation- Intimate
applicants
TI
regarding cancellation
08
Call for functional interview
008
Invite Applicant-FI
Invite
applicant
for
Telephonic Interview
09
Reschedule
functional
009
Intimate reschedule-FI Intimate
applicants
interview
regarding reschedule
10
Cancel functional interview
010
Intimate cancellation- Intimate
applicants
FI
regarding cancellation
11
Applicant appraisal
011
Fill applicant appraisal Filling applicant appraisal
form
12
Select applicant
012
App selected
Applicant selected
13
Put applicant in Panel
013
App in panel
Applicant in panel
14
Reject applicant
014
App Rejected
Applicant Rejected
15
Initiate offer letter
015
Prepare Offer
Prepare offer letter
Last changed on:
1/20/2014 1/20/2014
Version: 1.0
Page:
Page 65 of 86
ACTION
ACTIVIT
Y CODE
ACTIVITY
(SHORT)
ACTIVITY (LONG)
016
Prepare App.
17
017
To hire
Prepare
letter
To hire
18
018
Offer rejected
Offer rejected
19
Offer rejected
applicant
Letter of Intent
019
Letter of Intent
Letter of Intent
20
020
Medical Check up
21
Surety Bond
021
Surety Bond
22
Trainee Bond
022
Trainee Bond
Trainee Bond
23
Appointment letter
023
Appointment letter
Appointment letter
24
024
by
the
appointment
1.49.1 Purpose
1.49.2 Process Flow Chart
None
Report required
1
2
3
4
5
Vacancies
Organization Chart (Department, Unit and
BG wise)
Version: 1.0
Page:
Page 66 of 86
Object
Object Type
Upload program for uploading specifications details for each position in info
type 1002 against each new subtype created
Letter of intent as per INLOGISTICS format
Appointment letter along with code of conduct as per INLOGISTICS format
LSMW
Script/Smart Form
Script/Smart Form
Version: 1.0
Page:
Page 67 of 86
Version: 1.0
Page:
Page 68 of 86
Employee initiates the Travel Request with full details of itinerary (Date of travel, Source /
Destination, Preferred time, Accommodation request, Vehicle request, Travel advance request &
respective Cost Center. Employee can edit / delete the travel requests also.
Travel request is subject to the defined approval-cycle, based on the Business process.
Employees are entitled for per-diem allowance based on the defined trip schema.
Ticket Cost-booking shall be done directly in appropriate GL accounts through the Finance
module.
Ticket Rescheduling / Cancellation process shall be kept outside the preview of SAP Travel
Management.
Some of these functions are addressed by SAP Travel Management and rest, since they are not
addressed by SAP Travel Management are outside the scope of Travel Management implementation.
Precise distribution of the same is described below.
The following processes are considered:
Booking of guest house / hotel room, air / train tickets and other services by Travel-desk.
Posting of vendor-invoices. Manual posting to SAP FI would be done.
Posting of travel advance amount. Manual postings to SAP FI would be done.
Travel advance-balance recovery. Manual postings to SAP FI would be done.
Version: 1.0
Page:
Page 69 of 86
Travel request
Travel request
By employee
By employee
On rejection
Time, date & destination of travel
Notification to Employee
Trigger
Prerequisites
Version: 1.0
Page:
Page 70 of 86
Approved
Approved
(Superior)
(Superior)
Y/N
Y/N
Settled
Settled
Posting to FI/CO
Posting to FI/CO
Trigger
When the employee raises trip expenses after coming from the trip through ESS
Prerequisites
Expenses incurred during travel to have been captured as expense types.
Version: 1.0
Page:
Page 71 of 86
Travel Request
advance
Advance
Advance
Advance
paid
Balance
paid
Travel Expenses
Travel Expenses
Incurred
Incurred
Approval
Approval
Approval
Approval
Settlement
Settlement
Posting to
Posting to
FI / CO
FI / CO
Trigger
After settlement the travel expense are then posted to accounts.
Prerequisites
Settled travel expense report.
Employee
Groupings
All
employee
groups
Activity Types
Reasons
Meetings
Transfer
Domestic
Local (With-in City-Own Car)
Local (With-in City-Company
Car)
Deputation
Training
Others
Last changed on:
1/20/2014 1/20/2014
Trip Schema
Version: 1.0
Page:
Page 72 of 86
Expenses
All
employee
groups
Business Process
S.
No
Scenario
1
Performed By
R/3
HR
Enterprise Portal
Further Processing
Infotype 17 contains the eligibility
Mandatory Fields
Transport Services
Accommodation Services
Submit to Approval
Advance
Approves/Rejects
Mail to Reporting
Employee
Supervisor
Version: 1.0
Page:
Page 73 of 86
Employee
Approves/Rejects
Trip Settlement
Supervisor
Employee
Reporting Boss
Approves/Rejects
Finance
Posts to Finance
Finance
Mail to Reporting
1.54.1 Purpose
Online submission of claims and their reimbursement & settlement.
Travel
request
Traveler
Approval
Superior
Completion
of Expense
Report
Traveler
Approval
&settlement of
expenses
Approver
FI/CO
Posting
TRAVEL MANAGEMENT
Payment/ Deduction
Last changed on:
1/20/2014 1/20/2014
Version: 1.0
Page:
Page 74 of 86
Travel request is an entry scenario of travel management that accompanies the whole process of
company business. It handles the request electronically that can be sent from the SAP system to
the respective superior for approval. Following details are taken care:
o
o
o
o
o
Destination
Date and time of departure
Air Tickets
Rail Tickets
Advance required
Other information
On approval from the superior, the details raised by the employees are sent to the Travel desk for
providing the required services. This travel request in turn generates a unique number called the
Trip Number.
The travel desk gets the bookings done for travel-tickets / accommodation / other travel services
etc, through travel agents. Travel desk to provide unique trip numbers to the travel agents.
The employee collects advance from cash office. Advance requested by the employee is paid
through SAP FI / CO. [This process takes place by posting the advance amount to SAP FI/CO.]
The Travel Expenses function allows the employee to settle the travel expenses incurred during the
business trips efficiently. The expense receipts are entered, checked, and settled centrally by the
Expenses department.
The travelers enter the data themselves with a central monitoring of the trip facts and information.
After the trip has been taken, the traveler completes his or her travel expense report, including all
necessary data and documents.
The travel expense report is sent to the superior for approval, after which the same reaches the
expenses department for settlement with financial accounting.
The expenses department then checks the travel expense report, the original documents and
receipts. The trip is then settled and Travel expense results are then posted and amount is
transferred to financial accounting for final payment.
The amount incurred during the trip and the advances raised through travel request are captured in
financial accounting.
Last changed on:
1/20/2014 1/20/2014
Version: 1.0
Page:
Page 75 of 86
Once the advances are raised through travel request on approval are manually
posted in financial accounting.
The payment of reimbursement amounts to employee can take place through FI.
If a planned trip, for which an advance has been paid, does not take place, or if the
travel expense report for a trip, for which an advance has been paid, is rejected, then
the trip advance has to be cancelled. The trip advance is to be submitted to cash
office by the employee and reversal-entries to be done in FI manually.
To the Travel expense types, wage types are assigned which in turn are linked with
symbolic accounts.
Finally these symbolic accounts are assigned to expense accounts/clearing accounts in financial
accounting.
Any expense which is to be claimed from the employee can be taken care in FI.
1.54.3 Prerequisites
Travel Privileges infotype 0017 should be maintained.
Description
Overview of Planned Trips
Cost Assignment for Trip
Trip Receipts
Travel Expense Reporting by Period
Transaction Code
S_AHR_61016288
S_AHR_61016404
S_AHR_61016402
S_AHR_61016408
S. No
Object
Object Type
1.
2.
BADI
Enhancement/User
Exit based on the feasibility
checked in Realization.
BADI
Enhancement/User
Exit based on the feasibility
checked in Realization.
1.57 Authorization
Specific and Customized authorization required that will be finalized in the realization phase as the data is
been prepared by Inlogistics core team as applicable.
Version: 1.0
Page:
Page 77 of 86
ESS Process
Employee Self Service (ESS) Applications allow employees to view benefits, update personal information,
submit time cards, make vacation requests, and request travel expense reimbursement from their Web
browsers. The ESS Applications free human resources staff to deal with more complex tasks.
ESS is an effective means for providing real-time access and data maintenance capabilities to the source
or owner of the data. It has the ability to offload much of the data entry and related customer service
activities that may be typically performed in an organization's human resources, payroll, benefits and
purchasing departments.
Employees would be able to access the ESS portal from any computer with Internet access and within
Inlogistics through the Inlogistics Intranet.
ESS has to be a single window for employees to get an access to and manage their data in the HR
systems.
General Explanations:
ESS is a user friendly tool to make data access to all the employees based on the level of employees.
The tool reduces some of the cumbersome activities which are to be followed by the Human Resource
Department of an organization, like filling of employee details, maintaining of leave taken and updating
leave balances, sending of pay slip to each and individual employee etc.
Process:
Corporate Information
Management (OM)
Personal Information
Management (PA)
Version: 1.0
Page:
Page 78 of 86
Performance Management
System (PD)
Description of Improvements:
Employees can take care of their own day to day transactional work by themselves. The HR departments
are freed up from many of the routine, day-to-day processing functions. Overall, service levels and
efficiency increase and costs per transaction are drastically reduced.
Solution in SAP
All the ESS functionalities required at Inlogistics will be met through the standard Business Package for
Employee Self-Service.
Last changed on:
Last saved by: xxx
Version: 1.0
Page:
1/20/2014 1/20/2014 Draft for discussion purposes only
Page 79 of 86
Employees can use the Leave Request service to request both absences (infotype 2001) and
attendances (infotype 2002). This means that employees can also process records of the Attendances
infotype (2002) that have the quality of an absence in your company, such as Comp off etc.
Features
Leave Request:
This Web application provides your employees with many functions to simplify planning and recording
their absences. All functions can be accessed from the homepage of the Web application.
Employees can request leave and other absences and enter notifications of sickness and other
absences that do not require approval.
The Team Calendar enables employees to check their desired periods of leave against other
team members' leave.
The Calendar gives employees a practical three-month overview of their booked and requested
absences.
The Absences Overview enables employees to view their absences and track the status of their
requests.
Version: 1.0
Page:
Page 80 of 86
Employees can cancel, shorten or lengthen absences. To do this, they select the relevant
absence from the Absences Overview in the Team Calendar or Calendar.
The Time Accounts function provides employees with an overview of their absence entitlements
and attendance approvals. This means that you can check your remaining entitlement before
entering a leave request.
The information displayed in the Team Calendar, Absences Overview, and Time Accounts is only
updated after an employee has submitted a leave request.
Leave Approve/Reject:
This Web application provides HR managers or other authorized persons with all the functions they
require to check and approve leave requests.
This Web application is part of the Business Package for Employee Self-Service since it uses the same
functions as the Employee Self-Service application, Leave Request and cannot be implemented on its
own. However, it is for use in Manager Self-Service.
The worklist provides the approver with a list of all the absences he or she needs to approve. By
selecting an absence, he or she can approve or reject it.
The manager can use the different functions to help him or her determine whether or not the
leave request can be approved.
The Team Calendar enables the manager to check whether the employees absence would
create a bottleneck in his or her team.
The Time Account function provides the manager with an overview of an employee's leave
entitlements and attendance approvals.
After an employee has made changes to an absence, the approver can track the changes made.
The approver can enter a note stating the reason for approving or rejecting a request.
Business Process/Requirements:
Sr.
No.
Business Process
SAP Process
Standard Process
Standard Process
Version: 1.0
Page:
Page 81 of 86
Standard Process
Standard Process
Standard Process
Standard Process
Standard Process
10
IMG Customization
11
IMG Customization
12
Report required
Report for the leave
application status
Version: 1.0
Page:
Page 82 of 86
During the Planning Phase, goals are established for the company, team and employee
(employee goals: individual and competency and development goals).
The Review Phase consists of reviewing and updating goals.
The Appraisal Phase consists of appraising the individual performance and calibrating the team
performance ratings.
Online Objective setting and weightage for each objective in the appraisal form.
Self Assessment - Online self review of set objectives by rating each one of them in appraisal
form.
Appraiser Assessment - Online review and modification of objectives by the appraiser.
Reviewer Assessment - Online final review of objectives by the reviewer in appraisal form.
Description of Function:
Each appraisal is created using an appraisal model.
Version: 1.0
Page:
Page 83 of 86
Integration: Usage of already existing data in SAP to enable integrated management processes.
Removal of paper & excel via an integrated system.
Simplification: User friendly, intuitive user interfaces enable access to the data for employees and
managers.
HR Process / Area
Time and Attendance
Description
Allow
managers
to
display
attendance
information
for
the
Manager in their area of
responsibilities
Employee Review
Allow
managers
to
display
different
employee data
Page:
Page 84 of 86
Description
Allow
managers
to
display
Travel request related
information
in
their
areas of responsibility
Online viewing of Managers own data and other Managers data based on the employee level
Online application of Leaves and online approval by supervisor and auto updating of Quota
Online appraisal
Online viewing of organizational information
Online approval/cancellation of travel request
Description of Improvements:
Manager can take care of their own day to day transactional work by themselves. The HR departments
are freed up from many of the routine, day-to-day processing functions. Overall, service levels and
efficiency increase and costs per transaction are drastically reduced.
Solution in SAP
All the MSS functionalities required at Inlogistics will be met through the standard Business Package for
Managers Self-Service.
The Business Package for Managers Self-Service enables Manager to create, display and change their
own HR-related data in the Enterprise Portal. It covers data from various business areas: Working Time,
Employee Search, Personal Information, Travel and Expenses and Corporate Information.
This business package is intended for all company Manager. By giving your Manager access to their own
data, you simplify and standardize human resource processes and free up your HR department for
strategically important tasks.
Version: 1.0
Page:
Page 85 of 86
Version: 1.0
Page:
Page 86 of 86