Business Blueprint ESS
Business Blueprint ESS
Business Blueprint ESS
ASAP Business
Blueprint
Changed by:
Version:
Page 2 of 59
ESS Business Blueprint Document
Contents
1 HR Structure..................................................................................................10
1.1 Enterprise structure........................................................................................10
1.1.1 Company Code....................................................................................................... 10
1.1.2 Personnel Area....................................................................................................... 10
1.1.3 Personnel Subareas................................................................................................ 10
1.2 Personnel Structure........................................................................................11
1.2.1 Employee group...................................................................................................... 11
1.2.2 Employee subgroup................................................................................................ 12
1.3 Organization Structure...................................................................................13
1.3.1 Organization Unit.................................................................................................... 13
1.3.2 Jobs........................................................................................................................ 14
1.3.3 Position................................................................................................................... 14
2 ESS Applications..........................................................................................15
2.1 ESS Applications of Recruitment...................................................................15
2.1.1 Employment Opportunities Service(Intranet or Internet).........................................15
2.1.1.1 Scope..................................................................................................................................16
2.1.1.2 Expectations and Requirements.........................................................................................16
2.1.1.3 Explanation of Functions and Events.................................................................................16
2.1.1.4 Business Model..................................................................................................................17
2.1.1.5 Changes and its Implications..............................................................................................17
2.1.1.6 Description of Improvement...............................................................................................17
2.1.1.7 Gaps and Possible Approaches to bridge Gaps..................................................................18
2.1.1.8 System configuration considerations..................................................................................18
2.1.1.9 Data Migration Considerations...........................................................................................18
2.1.1.10 Interface considerations..................................................................................................18
2.1.1.11 Authorizations and User Roles.......................................................................................18
2.1.2 Application Status service.......................................................................................18
2.1.2.1 Scope..................................................................................................................................18
2.1.2.2 Expectations and Requirements.........................................................................................18
2.1.2.3 Explanation of Functions and Events.................................................................................18
2.1.2.4 Business Model..................................................................................................................19
2.1.2.5 Changes and its Implications..............................................................................................19
2.1.2.6 Description of Improvement...............................................................................................19
2.1.2.7 Gaps and Possible Approaches to bridge Gaps..................................................................19
2.1.2.8 System configuration considerations..................................................................................19
2.1.2.9 Data Migration Considerations...........................................................................................19
2.1.2.10 Interface considerations..................................................................................................19
2.1.2.11 Authorizations and User Roles.......................................................................................19
2.2 ESS Applications of Personnel Administration............................................19
2.2.1 Entering Hiring Data Service...................................................................................20
2.2.1.1 Scope..................................................................................................................................20
2.2.1.2 Expectations and Requirements.........................................................................................20
2.2.1.3 Explanation of Functions and Events.................................................................................20
2.2.1.4 Business Model..................................................................................................................20
2.2.1.5 Changes and its Implications..............................................................................................20
2.2.1.6 Description of Improvement...............................................................................................21
Page 3 of 59
ESS Business Blueprint Document
2.2.1.7 Gaps and Possible Approaches to bridge Gaps..................................................................21
2.2.1.8 System configuration considerations..................................................................................21
2.2.1.9 Data Migration Considerations...........................................................................................21
2.2.1.10 Interface considerations..................................................................................................21
2.2.1.11 Authorizations and User Roles.......................................................................................21
2.2.2 Who’s Who Service................................................................................................. 21
2.2.2.1 Scope..................................................................................................................................21
2.2.2.2 Expectations and Requirements.........................................................................................21
2.2.2.3 Explanation of Functions and Events.................................................................................21
2.2.2.4 Business Model..................................................................................................................22
2.2.2.5 Changes and its Implications..............................................................................................22
2.2.2.6 Description of Improvement...............................................................................................22
2.2.2.7 Gaps and Possible Approaches to bridge Gaps..................................................................23
2.2.2.8 System configuration considerations..................................................................................23
2.2.2.9 Data Migration Considerations...........................................................................................23
2.2.2.10 Interface considerations..................................................................................................23
2.2.3 Personal Data Service............................................................................................ 23
2.2.3.1 Scope..................................................................................................................................23
2.2.3.2 Expectations and Requirements.........................................................................................23
2.2.3.3 Explanation of Functions and Events.................................................................................23
2.2.3.4 Business Model..................................................................................................................23
2.2.3.5 Changes and its Implications..............................................................................................24
2.2.3.6 Description of Improvement...............................................................................................24
2.2.3.7 Gaps and Possible Approaches to bridge Gaps..................................................................24
2.2.3.8 System configuration considerations..................................................................................24
2.2.3.9 Data Migration Considerations...........................................................................................24
2.2.3.10 Interface considerations..................................................................................................24
2.2.3.11 Authorizations and User Roles.......................................................................................24
2.2.4 Address Service...................................................................................................... 24
2.2.4.1 Scope..................................................................................................................................24
2.2.4.2 Expectations and Requirements.........................................................................................24
2.2.4.3 Explanation of Functions and Events.................................................................................24
2.2.4.4 Business Model..................................................................................................................25
2.2.4.5 Changes and its Implications..............................................................................................25
2.2.4.6 Description of Improvement...............................................................................................25
2.2.4.7 Gaps and Possible Approaches to bridge Gaps..................................................................25
2.2.4.8 System configuration considerations..................................................................................25
2.2.4.9 Data Migration Considerations...........................................................................................25
2.2.4.10 Interface considerations..................................................................................................25
2.2.4.11 Authorizations and User Roles.......................................................................................25
2.2.5 Emergency Address................................................................................................ 25
2.2.5.1 Scope..................................................................................................................................25
2.2.5.2 Expectations and Requirements.........................................................................................25
2.2.5.3 Explanation of Functions and Events.................................................................................26
2.2.5.4 Business Model..................................................................................................................26
2.2.5.5 Changes and its Implications..............................................................................................26
2.2.5.6 Description of Improvement...............................................................................................26
2.2.5.7 Gaps and Possible Approaches to bridge Gaps..................................................................26
2.2.5.8 System configuration considerations..................................................................................26
2.2.5.9 Data Migration Considerations...........................................................................................26
2.2.5.10 Interface considerations..................................................................................................26
2.2.5.11 Authorizations and User Roles.......................................................................................26
2.2.6 Family Related Person service...............................................................................26
2.2.6.1 Scope..................................................................................................................................26
2.2.6.2 Expectations and Requirements.........................................................................................26
2.2.6.3 Explanation of Functions and Events.................................................................................27
Page 4 of 59
ESS Business Blueprint Document
2.2.6.4 Business Model..................................................................................................................27
2.2.6.5 Changes and its Implications..............................................................................................27
2.2.6.6 Description of Improvement...............................................................................................27
2.2.6.7 Gaps and Possible Approaches to bridge Gaps..................................................................27
2.2.6.8 System configuration considerations..................................................................................27
2.2.6.9 Data Migration Considerations...........................................................................................27
2.2.6.10 Interface considerations..................................................................................................27
2.2.6.11 Authorizations and User Roles.......................................................................................27
2.2.7 Emergency Contact Service....................................................................................28
2.2.7.1 Scope..................................................................................................................................28
2.2.7.2 Expectations and Requirements.........................................................................................28
2.2.7.3 Explanation of Functions and Events.................................................................................28
2.2.7.4 Business Model..................................................................................................................28
2.2.7.5 Changes and its Implications..............................................................................................28
2.2.7.6 Description of Improvement...............................................................................................28
2.2.7.7 Gaps and Possible Approaches to bridge Gaps..................................................................29
2.2.7.8 System configuration considerations..................................................................................29
2.2.7.9 Data Migration Considerations...........................................................................................29
2.2.7.10 Interface considerations..................................................................................................29
2.2.7.11 Authorizations and User Roles.......................................................................................29
2.2.8 Bank Details on Internet service.............................................................................29
2.2.8.1 Scope..................................................................................................................................29
2.2.8.2 Expectations and Requirements.........................................................................................29
2.2.8.3 Explanation of Functions and Events.................................................................................29
2.2.8.4 Business Model..................................................................................................................30
2.2.8.5 Changes and its Implications..............................................................................................30
2.2.8.6 Description of Improvement...............................................................................................30
2.2.8.7 Gaps and Possible Approaches to bridge Gaps..................................................................30
2.2.8.8 System configuration considerations..................................................................................30
2.2.8.9 Data Migration Considerations...........................................................................................30
2.2.8.10 Interface considerations..................................................................................................30
2.2.8.11 Authorizations and User Roles.......................................................................................30
2.2.9 Previous employer’s Service...................................................................................30
2.2.9.1 Scope..................................................................................................................................30
2.2.9.2 Expectations and Requirements.........................................................................................30
2.2.9.3 Explanation of Functions and Events.................................................................................31
2.2.9.4 Business Model..................................................................................................................31
2.2.9.5 Changes and its Implications..............................................................................................31
2.2.9.6 Description of Improvement...............................................................................................31
2.2.9.7 Gaps and Possible Approaches to bridge Gaps..................................................................31
2.2.9.8 System configuration considerations..................................................................................31
2.2.9.9 Data Migration Considerations...........................................................................................31
2.2.9.10 Interface considerations..................................................................................................31
2.2.9.11 Authorizations and User Roles.......................................................................................31
2.3 ESS Applications of Personnel Development...............................................32
2.3.1 Qualification Profile Service....................................................................................32
2.3.1.1 Scope..................................................................................................................................32
2.3.1.2 Expectations and Requirements.........................................................................................32
2.3.1.3 Explanation of Functions and Events.................................................................................32
2.3.1.4 Business Model..................................................................................................................33
2.3.1.5 Changes and its Implications..............................................................................................33
2.3.1.6 Description of Improvement...............................................................................................33
2.3.1.7 Gaps and Possible Approaches to bridge Gaps..................................................................33
2.3.1.8 System configuration considerations..................................................................................33
2.3.1.9 Data Migration Considerations...........................................................................................33
Page 5 of 59
ESS Business Blueprint Document
2.3.1.10 Interface considerations..................................................................................................33
2.3.1.11 Authorizations and User Roles.......................................................................................33
2.3.2 Display Qualifications Service.................................................................................33
2.3.2.1 Scope..................................................................................................................................34
2.3.2.2 Expectations and Requirements.........................................................................................34
2.3.2.3 Explanation of Functions and Events.................................................................................34
2.3.2.4 Business Model..................................................................................................................34
2.3.2.5 Changes and its Implications..............................................................................................34
2.3.2.6 Description of Improvement...............................................................................................34
2.3.2.7 Gaps and Possible Approaches to bridge Gaps..................................................................34
2.3.2.8 System configuration considerations..................................................................................34
2.3.2.9 Data Migration Considerations...........................................................................................34
2.3.2.10 Interface considerations..................................................................................................34
2.3.2.11 Authorizations and User Roles.......................................................................................34
2.3.3 My Appraisals Service............................................................................................. 35
2.3.3.1 Scope..................................................................................................................................35
2.3.3.2 Expectations and Requirements.........................................................................................35
2.3.3.3 Explanation of Functions and Events.................................................................................35
2.3.3.4 Business Model..................................................................................................................35
2.3.3.5 Changes and its Implications..............................................................................................35
2.3.3.6 Description of Improvement...............................................................................................35
2.3.3.7 Gaps and Possible Approaches to bridge Gaps..................................................................35
2.3.3.8 System configuration considerations..................................................................................35
2.3.3.9 Data Migration Considerations...........................................................................................36
2.3.3.10 Interface considerations..................................................................................................36
2.3.3.11 Authorizations and User Roles.......................................................................................36
2.3.4 Appraisal Overview service.....................................................................................36
2.3.4.1 Scope..................................................................................................................................36
2.3.4.2 Expectations and Requirements.........................................................................................36
2.3.4.3 Explanation of Functions and Events.................................................................................36
2.3.4.4 Business Model..................................................................................................................37
2.3.4.5 Changes and its Implications..............................................................................................37
2.3.4.6 Description of Improvement...............................................................................................37
2.3.4.7 Gaps and Possible Approaches to bridge Gaps..................................................................37
2.3.4.8 System configuration considerations..................................................................................37
2.3.4.9 Data Migration Considerations...........................................................................................37
2.3.4.10 Interface considerations..................................................................................................37
2.3.4.11 Authorizations and User Roles.......................................................................................37
2.4 ESS Applications of Training and Events......................................................37
2.4.1 My Service Training Center.....................................................................................37
2.4.1.1 Scope..................................................................................................................................38
2.4.1.2 Expectations and Requirements.........................................................................................38
2.4.1.3 Explanation of Functions and Events.................................................................................38
2.4.1.4 Business Model..................................................................................................................38
2.4.1.5 Changes and its Implications..............................................................................................38
2.4.1.6 Description of Improvement...............................................................................................38
2.4.1.7 Gaps and Possible Approaches to bridge Gaps..................................................................38
2.4.1.8 System configuration considerations..................................................................................38
2.4.1.9 Data Migration Considerations...........................................................................................38
2.4.1.10 Interface considerations..................................................................................................38
2.4.1.11 Authorizations and User Roles.......................................................................................39
2.4.2 Service My Bookings............................................................................................... 39
2.4.2.1 Scope..................................................................................................................................39
2.4.2.2 Expectations and Requirements.........................................................................................39
2.4.2.3 Explanation of Functions and Events.................................................................................39
Page 6 of 59
ESS Business Blueprint Document
2.4.2.4 Business Model..................................................................................................................40
2.4.2.5 Changes and its Implications..............................................................................................40
2.4.2.6 Description of Improvement...............................................................................................40
2.4.2.7 Gaps and Possible Approaches to bridge Gaps..................................................................40
2.4.2.8 System configuration considerations..................................................................................40
2.4.2.9 Data Migration Considerations...........................................................................................40
2.4.2.10 Interface considerations..................................................................................................40
2.4.2.11 Authorizations and User Roles.......................................................................................40
2.4.3 Calendar of Events or Service List of Events..........................................................40
2.4.3.1 Scope..................................................................................................................................40
2.4.3.2 Expectations and Requirements.........................................................................................40
2.4.3.3 Explanation of Functions and Events.................................................................................41
2.4.3.4 Business Model..................................................................................................................41
2.4.3.5 Changes and its Implications..............................................................................................41
2.4.3.6 Description of Improvement...............................................................................................41
2.4.3.7 Gaps and Possible Approaches to bridge Gaps..................................................................41
2.4.3.8 System configuration considerations..................................................................................41
2.4.3.9 Data Migration Considerations...........................................................................................41
2.4.3.10 Interface considerations..................................................................................................41
2.4.3.11 Authorizations and User Roles.......................................................................................42
2.4.4 Book/Prebook Attendance or Service book Attendance..........................................42
2.4.4.1 Scope..................................................................................................................................42
2.4.4.2 Expectations and Requirements.........................................................................................42
2.4.4.3 Explanation of Functions and Events.................................................................................42
2.4.4.4 Business Model..................................................................................................................43
2.4.4.5 Changes and its Implications..............................................................................................43
2.4.4.6 Description of Improvement...............................................................................................43
2.4.4.7 Gaps and Possible Approaches to bridge Gaps..................................................................43
2.4.4.8 System configuration considerations..................................................................................43
2.4.4.9 Data Migration Considerations...........................................................................................43
2.4.4.10 Interface considerations..................................................................................................43
2.4.4.11 Authorizations and User Roles.......................................................................................43
2.4.5 Service view Attendance or IAC Booked Events.....................................................43
2.4.5.1 Scope..................................................................................................................................44
2.4.5.2 Expectations and Requirements.........................................................................................44
2.4.5.3 Explanation of Functions and Events.................................................................................44
2.4.5.4 Business Model..................................................................................................................44
2.4.5.5 Changes and its Implications..............................................................................................44
2.4.5.6 Description of Improvement...............................................................................................44
2.4.5.7 Gaps and Possible Approaches to bridge Gaps..................................................................44
2.4.5.8 System configuration considerations..................................................................................45
2.4.5.9 Data Migration Considerations...........................................................................................45
2.4.5.10 Interface considerations..................................................................................................45
2.4.5.11 Authorizations and User Roles.......................................................................................45
2.4.6 Cancel Attendance or IAC Cancel Attendance........................................................45
2.4.6.1 Scope..................................................................................................................................45
2.4.6.2 Expectations and Requirements.........................................................................................45
2.4.6.3 Explanation of Functions and Events.................................................................................45
2.4.6.4 Business Model..................................................................................................................46
2.4.6.5 Changes and its Implications..............................................................................................46
2.4.6.6 Description of Improvement...............................................................................................46
2.4.6.7 Gaps and Possible Approaches to bridge Gaps..................................................................46
2.4.6.8 System configuration considerations..................................................................................46
2.4.6.9 Data Migration Considerations...........................................................................................46
2.4.6.10 Interface considerations..................................................................................................46
2.4.6.11 Authorizations and User Roles.......................................................................................46
Page 7 of 59
ESS Business Blueprint Document
2.5 ESS Applications of Time Management........................................................47
2.5.1 Display of Work schedule of employee...................................................................47
2.5.1.1 Scope..................................................................................................................................47
2.5.1.2 Expectations and Requirements.........................................................................................47
2.5.1.3 Explanation of Functions and Events.................................................................................47
2.5.1.4 Business Model..................................................................................................................47
2.5.1.5 Changes and its Implications..............................................................................................48
2.5.1.6 Description of Improvement...............................................................................................48
2.5.1.7 Gaps and Possible Approaches to bridge Gaps..................................................................48
2.5.1.8 System configuration considerations..................................................................................48
2.5.1.9 Data Migration Considerations...........................................................................................48
2.5.1.10 Interface considerations..................................................................................................48
2.5.1.11 Authorizations and User Roles.......................................................................................48
2.5.2 Leave Request........................................................................................................ 48
2.5.2.1 Scope..................................................................................................................................48
2.5.2.2 Expectations and Requirements.........................................................................................48
2.5.2.3 Explanation of Functions and Events.................................................................................48
2.5.2.4 Business Model..................................................................................................................49
2.5.2.5 Changes and its Implications..............................................................................................49
2.5.2.6 Description of Improvement...............................................................................................49
2.5.2.7 Gaps and Possible Approaches to bridge Gaps..................................................................49
2.5.2.8 System configuration considerations..................................................................................49
2.5.2.9 Data Migration Considerations...........................................................................................49
2.5.2.10 Interface considerations..................................................................................................49
2.5.2.11 Authorizations and User Roles.......................................................................................49
2.5.3 Leave Approval....................................................................................................... 49
2.5.3.1 Scope..................................................................................................................................49
2.5.3.2 Expectations and Requirements.........................................................................................50
2.5.3.3 Explanation of Functions and Events.................................................................................50
2.5.3.4 Business Model..................................................................................................................50
2.5.3.5 Changes and its Implications..............................................................................................51
2.5.3.6 Description of Improvement...............................................................................................51
2.5.3.7 Gaps and Possible Approaches to bridge Gaps..................................................................51
2.5.3.8 System configuration considerations..................................................................................51
2.5.3.9 Data Migration Considerations...........................................................................................52
2.5.3.10 Interface considerations..................................................................................................52
2.5.3.11 Authorizations and User Roles.......................................................................................52
2.5.4 Leave Cancellation and Approval ...........................................................................52
2.5.4.1 Scope..................................................................................................................................52
2.5.4.2 Expectations and Requirements.........................................................................................52
2.5.4.3 Explanation of Functions and Events.................................................................................52
2.5.4.4 Business Model..................................................................................................................53
2.5.4.5 Changes and its Implications..............................................................................................53
2.5.4.6 Description of Improvement...............................................................................................53
2.5.4.7 Gaps and Possible Approaches to bridge Gaps..................................................................53
2.5.4.8 System configuration considerations..................................................................................53
2.5.4.9 Data Migration Considerations...........................................................................................53
2.5.4.10 Interface considerations..................................................................................................53
2.5.4.11 Authorizations and User Roles.......................................................................................54
2.5.5 Time Accounts........................................................................................................ 54
2.5.5.1 Scope..................................................................................................................................54
2.5.5.2 Expectations and Requirements.........................................................................................54
2.5.5.3 Explanation of Functions and Events.................................................................................54
2.5.5.4 Business Model..................................................................................................................54
2.5.5.5 Changes and its Implications..............................................................................................54
Page 8 of 59
ESS Business Blueprint Document
2.5.5.6 Description of Improvement...............................................................................................54
2.5.5.7 Gaps and Possible Approaches to bridge Gaps..................................................................55
2.5.5.8 System configuration considerations..................................................................................55
2.5.5.9 Data Migration Considerations...........................................................................................55
2.5.5.10 Interface considerations..................................................................................................55
2.5.5.11 Authorizations and User Roles.......................................................................................55
2.5.6 Leave Requests Overview......................................................................................55
2.5.6.1 Scope..................................................................................................................................55
2.5.6.2 Expectations and Requirements.........................................................................................55
2.5.6.3 Explanation of Functions and Events.................................................................................55
2.5.6.4 Business Model..................................................................................................................56
2.5.6.5 Changes and its Implications..............................................................................................56
2.5.6.6 Description of Improvement...............................................................................................56
2.5.6.7 Gaps and Possible Approaches to bridge Gaps..................................................................56
2.5.6.8 System configuration considerations..................................................................................56
2.5.6.9 Data Migration Considerations...........................................................................................56
2.5.6.10 Interface considerations..................................................................................................56
2.5.6.11 Authorizations and User Roles.......................................................................................56
2.6 ESS Applications of Travel Management......................................................56
2.6.1 Submit Travel Request............................................................................................ 56
2.6.1.1 Scope..................................................................................................................................56
2.6.1.2 Expectations and Requirements.........................................................................................57
2.6.1.3 Explanation of Functions and Events.................................................................................57
2.6.1.4 Business Model..................................................................................................................57
2.6.1.5 Changes and its Implications..............................................................................................57
2.6.1.6 Description of Improvement...............................................................................................57
2.6.1.7 Gaps and Possible Approaches to bridge Gaps..................................................................57
2.6.1.8 System configuration considerations..................................................................................57
2.6.1.9 Data Migration Considerations...........................................................................................57
2.6.1.10 Interface considerations..................................................................................................57
2.6.1.11 Authorizations and User Roles.......................................................................................57
Page 9 of 59
ESS Business Blueprint Document
1 HR Structure
Page 10 of 59
ESS Business Blueprint Document
and work schedule planning, takes place at the personnel
subarea level. The personnel subarea is defined by a four-
character, alphanumeric code. The respective country-
specific control features are stored here.
Definitions at VIL
The definitions are covered under Personnel
Administration
Page 11 of 59
ESS Business Blueprint Document
employee group is defined with a one Character
identification.
Definitions at VIL.
The definitions are covered under Personnel Administration
Page 12 of 59
ESS Business Blueprint Document
scale groups are valid for specific employee
subgroups.
Will help in determining which work schedules are
permissible for which employee subgroups using the
employee subgroup grouping for the work schedule.
Will help in setting up appraisal criteria dependent on
employee subgroup using the employee subgroup
grouping.
The employee subgroup enables to define data entry
default values, for example, for the payroll area or an
employee’s basic pay.
The employee subgroup is a selection criterion for
evaluations.
Employee subgroups are an authorization check unit.
Definitions at VIL:
The definitions are covered under Personnel Administration
Page 13 of 59
ESS Business Blueprint Document
Inherited by subordinate positions
Definitions at VIL
The Organization structure is defined based on geographical
areas and business/Functional Requirements
The Organization structure and organizational unit
configuration is covered under Organization Management.
1.3.2 Jobs
Definition and Meaning
Jobs are classifications of functions in an enterprise
(administrator, for example), which are defined by the
assignment of characteristics. Jobs serve as job descriptions
that apply to several positions with similar tasks or
characteristics.
Definitions at VIL
The definitions are covered under Organization
Management.
1.3.3 Position
Definition and Meaning
Represents a post, which can be occupied by a person
(employee) in the staff assignments of an organizational unit.
(For example JOB = Manager and POSITION = Manager –
HR).
Page 14 of 59
ESS Business Blueprint Document
2 ESS Applications
SAP ESS Key Capabilities
SAP Employee Self-Service (ESS) offers all the functionality to empower users
and deliver the information, tools, and services they need to do their jobs. Giving
them the freedom to focus on business results.
ESS includes key capabilities for:
Office -- Manage items related to daily work activities, such as an inbox,
company directory, personal calendar, and internal service request.
Time management -- Submit leave requests, and receive approvals and Leave
Requests Overview.
Business travel -- Manage all aspects related to business travel, from trip
planning to Trip Completion and Financial Postings also
Payment -- Handle issues related to salary, such as salary verification and
compensation statements.
Skills and appraisals -- Access a qualifications profile, maintain a skills
database, and view recommendations for skills enhancement.
Training -- Display training schedules, sign up for training, and receive training
approval as well as.
Recruitment -- View job openings with the company, create application
materials, apply for a position, and check the status of pending applications.
Life and work events -- Receive guidance and background information pertinent
to life and work changes, such as getting married or starting a new job.
Personal information -- View, enter, and update personal information such as
address, dependents, and emergency contact and bank data.
Page 15 of 59
ESS Business Blueprint Document
The employment opportunities services will help the
organization in streamlining and structuring of recruitment
process where the applicants will apply directly in reference
to a position which is vacant or sometimes unsolicited
applications without reference to any vacant Job. The
Intranet and internet media is very cheap compared with
other Media such as Vendors and Mass media which is
News papers.
2.1.1.1Scope
The scope of the document is to cover the process of
Employment opportunities service of ESS.
Page 16 of 59
ESS Business Blueprint Document
employees can submit an online application with
minimal data entry.
Employees log on to the Employment Opportunities
service using their current user ID for Intranet.
Internet Web Services
Generally speaking, human resources are the highest
fixed costs that a company has. Consequently,
recruiting the best people possible has become a high
priority. Companies invest a lot of time and money
advertising employment opportunities, evaluating
applicants, and managing the entire recruitment and
hiring process.
This Web application allows external applicants to do
the following:
Display job advertisements from your company
Apply for vacant positions in your company
Submit unsolicited applications to your company
Create attachments (application documents with
passport photograph
Change application data as required
Job seekers can display a list of all job advertisements
in your company. The system displays a short
description of the vacant positions.
External applicants can submit applications in
response to specific job advertisements or make
unsolicited job applications. Applicants submit
applications via the Internet by entering the
information that is requested of them (personal details,
experience, qualifications, skills, and training).
Applicants are obligated to enter their personal details.
In the other areas, however, applicants are free to
decide how much information they want to provide.
Applicants can also create an attachment containing
their application documents and passport photograph
in their online application via the Internet.
2.1.1.4Business Model
None
2.1.1.6Description of Improvement
SAP implementation is a total improvement over the
existing practices. The SAP intranet and web
applications will help in speeding up of the recruitment
Page 17 of 59
ESS Business Blueprint Document
process and also reduce the burden of HR personnel
in manually entering Large Volumes of Data.
2.1.2.1Scope
The scope of the document is to cover the process of
ESS service applicant status through Intranet or
Internet.
Page 18 of 59
ESS Business Blueprint Document
Costs can be saved because applicants can track their
own applications on the Internet. This means that
companies have fewer telephone inquiries to answer,
and that they do not need to create and send letters of
confirmation.
Advantages for employees:
Employees can find out the status of their application
quickly and easily on the Internet. Another advantage
is that they are not restricted to normal company
opening hours.
2.1.2.4Business Model
None
2.1.2.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
Page 19 of 59
ESS Business Blueprint Document
- Address Service
- Emergency Address Service
- Family Related Person service
- Emergency Contact Service
- Bank Details on Internet Service
- Previous employer’s Service
2.2.1.1Scope
The scope of the document is to the cover the
business process of ESS service Entering Hiring Data
for VIL and VAL employees
2.2.1.4Business Model
None
Page 20 of 59
ESS Business Blueprint Document
2.2.1.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
2.2.2.1Scope
The scope of the document is to cover the ESS
service Who’s who in the Organization.
Page 21 of 59
ESS Business Blueprint Document
maintained in the SAP Personnel Administration
component.
2.2.2.4Business Model
None
2.2.2.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
Page 22 of 59
ESS Business Blueprint Document
2.2.2.7Gaps and Possible Approaches to bridge Gaps
None
2.2.3.1Scope
The scope of the document is to the cover the
business process of ESS service Personal Data
where employee personal information gets stored for
VIL and VAL employees
2.2.3.4Business Model
None
Page 23 of 59
ESS Business Blueprint Document
2.2.3.5Changes and its Implications
None
2.2.3.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
2.2.4.1Scope
The scope of the document is to the cover the
business process of ESS service Addresses of
employees at VIL and VAL.
Page 24 of 59
ESS Business Blueprint Document
An employee must have an SAP user that is directly
linked to his or her R/3 employee master data via the
Communication infotype (0105).
2.2.4.4Business Model
None
2.2.4.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
2.2.5.1Scope
The scope of the document is to the cover the
business process of ESS service Emergency Address
for VIL and VAL employees
Page 25 of 59
ESS Business Blueprint Document
2.2.5.3Explanation of Functions and Events
The Emergency Address service will enables the
employees at VIL and VAL to display and edit contact
addresses for emergency situations. In this way,
employees can keep their own data up-to-date.
2.2.5.4Business Model
None
2.2.5.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
2.2.6.1Scope
The scope of the document is to the cover the
business process of ESS service Family Related
Person for VIL and VAL employees
Page 26 of 59
ESS Business Blueprint Document
and enter all the details of the Family and related
persons in SAP.
2.2.6.4Business Model
None
2.2.6.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
Page 27 of 59
ESS Business Blueprint Document
2.2.7.1Scope
The scope of the document is to the cover the
business process of ESS service Emergency Contact
service for VIL and VAL employees
2.2.7.4Business Model
None
2.2.7.6Description of Improvement
Page 28 of 59
ESS Business Blueprint Document
SAP implementation is a total improvement over the
existing practices.
2.2.8.1Scope
The scope of the document is to the cover the
business process of ESS service Bank details service
for VIL and VAL employees
Page 29 of 59
ESS Business Blueprint Document
2.2.8.4Business Model
None
2.2.8.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
2.2.9.1Scope
The scope of the document is to the cover the
business process of ESS service Previous employer’s
service for VIL and VAL employees.
Page 30 of 59
ESS Business Blueprint Document
2.2.9.3Explanation of Functions and Events
The Previous employer service enables the
employees at your enterprise to display and edit data
on their own previous employers. In this way,
employees can keep their own data up-to-date, while
simultaneously reducing the number of time-
consuming and expensive activities performed by the
Human Resources Department.
If an employee uses this service to update his or her
previous employers, the old data is automatically
delimited. Old HR data is not lost. Instead, it is kept in
full so that historical evaluations are possible.
An employee must have an SAP user that is directly
linked to his or her R/3 employee master data via the
Communication Infotype (0105).
2.2.9.4Business Model
None
2.2.9.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
Page 31 of 59
ESS Business Blueprint Document
2.3.1.1Scope
The scope of the document is to explain the
Qualification profile service for VIL and VAL
employees where employees can add additional
qualifications which are acquired by them from time to
time.
Page 32 of 59
ESS Business Blueprint Document
Advantages of using this service:
Reduces the administrative workload of staff in the
personnel department and supervisors
Promotes employee involvement and responsibility
Prerequisites
You must have implemented the Personnel
Development component.
In Customizing for Personnel Development, you must
have worked through the following activities:
Edit Scales
Edit Qualifications Catalog
You must have created a mini master record for every
employee. You must also have created Infotype 105.
2.3.1.4Business Model
None
2.3.1.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
Page 33 of 59
ESS Business Blueprint Document
2.3.2.1Scope
The scope of the document is to cover the process of
display employee qualifications.
2.3.2.4Business Model
2.3.2.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
Page 34 of 59
ESS Business Blueprint Document
2.3.3 My Appraisals Service
My appraisal service will display and allow editing the
different phases of Appraisals.
2.3.3.1Scope
The scope of the document is to cover the appraisal
process where as an appraisee employee can edit his
KRA’s and reset the KRA’s in Co-ordination with
Appraiser and where as Appraiser can access his own
Appraisals and also can appraise the appraisee.
2.3.3.4Business Model
None
2.3.3.6Description of Improvement
SAP implementation is a total improvement over the
existing practices .
Page 35 of 59
ESS Business Blueprint Document
2.3.3.9Data Migration Considerations
None
2.3.4.1Scope
The scope of the document is to cover the process of
Appraisals overview service where the Managers can
view, Create or edit the appraisals of subordinates
Page 36 of 59
ESS Business Blueprint Document
Appraisal models must already be defined.
Authorizations/Security
The user also requires the following authorizations:
Authorization for display his/her own appraisals
Authorization for displaying and editing the appraisals
of the employees for whom he/she is responsible
No special security measures need to be
implemented.
2.3.4.4Business Model
None
2.3.4.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
Page 37 of 59
ESS Business Blueprint Document
2.4.1.1Scope
The scope of the document is to cover the ess service
My Service center.
2.4.1.4Business Model
This is a standard ESS service where employees can
enter or check the information with regard to the
Business Events at VIL and VAL.
2.4.1.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
Page 38 of 59
ESS Business Blueprint Document
2.4.1.11 Authorizations and User Roles
Roles: HR_ESS_user
2.4.2.1Scope
The scope of the document is to cover the ess service
Calendar of events.
Page 39 of 59
ESS Business Blueprint Document
2.4.2.4Business Model
This is a standard ESS service where employees can
enter or check and book, cancel and rebook the
business event and also the information with regard to
the Business Events at VIL and VAL.
2.4.2.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
2.4.3.1Scope
The scope of the document is to cover the ess service
Calendar of events.
Page 40 of 59
ESS Business Blueprint Document
Display of calendar of Training and events to
employees at various locations to enable them to
Book themselves for the Training programs
2.4.3.4Business Model
This is a standard ESS service where employees can
enter or check the information with regard to the
Business Events at VIL and VAL.
2.4.3.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
Page 41 of 59
ESS Business Blueprint Document
2.4.3.11 Authorizations and User Roles
Roles: HR_ESS_user
2.4.4.1Scope
The scope of the document is to cover the ESS/WEB
service Book/Prebook Attendance.
Page 42 of 59
ESS Business Blueprint Document
dates are fixed, the Prebookings will become a
Booking for Business Event
2.4.4.4Business Model
This is a standard ESS service where employees can
Book for a Business Event or Prebook for a Business
Event type with regard to the Business Events at VIL
and VAL.
2.4.4.6Description of Improvement
SAP ESS implementation is a total improvement over
the existing practices. At present there is no facility to
book or view or Cancel the Training Programs on line.
Page 43 of 59
ESS Business Blueprint Document
2.4.5.1Scope
The scope of the document is to cover the process of
ESS service View Attendance.
2.4.5.4Business Model
This is a standard ESS service where employees can
view the information with regard to the Business
Events at VIL and VAL.
2.4.5.6Description of Improvement
SAP ESS implementation is a total improvement over
the existing practices. At present there is no facility to
book or view or Cancel the Training Programs on line.
Page 44 of 59
ESS Business Blueprint Document
2.4.5.8System configuration considerations
None
2.4.6.1Scope
The scope of the document is to cover the ESS
service Application where employees can cancel their
attendances through Intranet or Internet.
Page 45 of 59
ESS Business Blueprint Document
editing the information themselves on the corporate
intranet.
The Web Application Components Cancel Attendance
enables Web users to cancel bookings they have
made via Internet for business events or Training
Programs offered by the company. To do so, they
access the calendar of events, find the relevant
business event date for which they are booked and
cancel the booking.
2.4.6.4Business Model
This is a standard ESS service where employees can
enter or check the information with regard to the
Business Events at VIL and VAL.
2.4.6.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
Page 46 of 59
ESS Business Blueprint Document
2.5.1.1Scope
The scope of the document to explain the service of
displaying the working times of employee through
work schedules Service.
2.5.1.4Business Model
None
Page 47 of 59
ESS Business Blueprint Document
2.5.1.5Changes and its Implications
None
2.5.1.6Description of Improvement
Displaying of working times will help the employee in
adhering to the working pattern and also will be useful
in any changes which takes palce at shop floor level
from time to time(Shift Changes).
2.5.2.1Scope
The scope of the document is to cover the process of
Leave request web application of VIL and VAL
employees.
Page 48 of 59
ESS Business Blueprint Document
for example. To assist users in entering data, the
system displays an overview of all existing information
on leave entitlements.
The leave request can be submitted to the employee's
superior for approval, depending on the workflow
template that is used. Employees can display the
status of their requests in an Overview. They can also
cancel leave requests on the overview screen.
2.5.2.4Business Model
None
2.5.2.6Description of Improvement
SAP implementation is a total improvement over the
existing practices .
2.5.3.1Scope
The scope of the document is to cover the process of
Leave approval and rejection.
Page 49 of 59
ESS Business Blueprint Document
2.5.3.2Expectations and Requirements
In VIL and VAL the practice is that as and when
employee applies for a leave the same has to go
through approval process. At present the approval will
be taken on a Paper Leave application form and
stored in a file. Need to have a Facility where the
approvals to happen in the system.
2.5.3.4Business Model
Page 50 of 59
ESS Business Blueprint Document
2.5.3.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
Page 51 of 59
ESS Business Blueprint Document
None
2.5.4.1Scope
The scope of the document is to cover the Ess service
Leave cancellation in VIL and VAL
Page 52 of 59
ESS Business Blueprint Document
The corresponding absence or cancellation is then
highlighted in color.
Choose Delete.
The message Request deleted appears. The request
is no longer displayed in the overview.
Canceling leave with the status Approved
Click on the trash can in the appropriate line.
Extra dialog boxes appear.
Enter the required information for the cancellation:
If you want to cancel the leave request partially, enter
the period you want to cancel, that is, the period in
which you will be at work.
If you want to cancel the leave request completely, do
not change the date.
If you want to choose a different approver, choose
Replace. Enter the new approver.
If required, enter a note to inform the approver of the
reason for the cancellation.
Choose Send cancellation.
The message the information was sent successfully
appears. The cancellation is forwarded to the specified
approver.
2.5.4.4Business Model
None
2.5.4.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
Page 53 of 59
ESS Business Blueprint Document
2.5.5.1Scope
The scope of the document is to cover the process of
employee Time accounts where employee Leave
Balances and availed will be shown.
2.5.5.4Business Model
None
2.5.5.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
Page 54 of 59
ESS Business Blueprint Document
2.5.5.7Gaps and Possible Approaches to bridge Gaps
None
2.5.6.1Scope
The scope of the document is to cover the ESS
service of Leave requests overview.
Page 55 of 59
ESS Business Blueprint Document
2.5.6.4Business Model
None
2.5.6.6Description of Improvement
SAP implementation is a total improvement over the
existing practices.
2.6.1.1Scope
The scope of the document is to cover the service of
create, Edit and change Travel requests of an
Page 56 of 59
ESS Business Blueprint Document
employee and also to submit the Travel expenses
also.
2.6.1.4Business Model
None
2.6.1.6Description of Improvement
SAP implementation is a total improvement over the
existing practices. The employee can send the travel
request to the superior for approval and also can
submit and settle the Travel expenses online through
ESS.
Page 57 of 59
ESS Business Blueprint Document
Roles: HR_ESS_User
HR_ESS_user with Approval Authorizations
2.6.2.1Scope
The scope of the document is to cover the service of
approve the Travel requests of subordinates and also
to approve the Travel expenses also.
2.6.2.4Business Model
None
2.6.2.6Description of Improvement
SAP implementation is a total improvement over the
existing practices. The employee can send the travel
request to the superior for approval and also can
submit and settle the Travel expenses online through
Page 58 of 59
ESS Business Blueprint Document
ESS which will help in reduction of Time in settling the
travel expenses.
Page 59 of 59