© SAP AG 2006

HR260 Manager Self-Service
HR260 Manager Self Service
THE BEST-RUN BUSI NESSES RUN SAP
© SAP AG 2005
HR260
Manager Sel f -Ser vi c e



Þ SAP ERP Central Component 5.0
Þ 2006/Q2
Þ 50074209
© SAP AG 2006
Copyright 2006 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in
any form or for any purpose without the express written
permission of SAP AG. The information contained in this
publication may be changed without prior notice.
Copyright
© SAP AG 2006



Trademarks:
Þ Some software products marketed by SAP AG and its distributors may contain proprietary
software components of other software vendors.
Þ Microsoft, Windows, Outlook and PowerPoint are registered trademarks of Microsoft
Corporation.
Þ IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390,
AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,
WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM
Corporation in the USA and/or other countries.
Þ Oracle is a registered trademark of Oracle Corporation.
Þ UNIX, X/Open, OSF/1 and Motif are registered trademarks of Open Group.
Þ Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
Þ HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World
Wide Web Consortium, Massachusetts Institute of Technology.
Þ Java is a registered trademark of Sun Microsystems, Inc.
Þ JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for
technology developed and implemented by Netscape.
Þ MaxDB is a trademark of MySQL AB, Sweden.
Þ …
Þ …
Þ SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and
services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All other
product and service names mentioned here are the trademarks of their respective owners. The
information provided here is not binding and is solely for information purposes. Product
specifications may vary from country to country.
Þ The information contained in this publication is proprietary to SAP. No part of this publication
may be reproduced or transmitted in any form or for any purpose without the express written
permission of SAP AG.
Þ This publication is a preliminary version and it is not subject to your license agreement or any
other agreement with SAP. This publication only contains intended strategies, developments
and functions of the SAP
®
product. It is not intended to be binding upon SAP to any particular
course of business, product strategy and/or development. SAP can change this publication any
time without prior notice.
Þ SAP assumes no responsibility for errors or omissions in this publication. Furthermore, SAP
does not accept liability for the accuracy or completeness of the information, texts, graphics,
links or other items contained within this publication. This publication is provided without a
warranty of any kind, either express or implied, including but not limited to the warranties of
marketability, suitability for a particular purposes, or non-infringement.
Þ SAP shall have no liability for damages of any kind, including without limitation, direct,
special, indirect, or consequential damages that may result from the use of these materials.
These limitations shall not apply in cases of intent or gross negligence.
Þ The statutory liability for personal injury and defective products is not affected. SAP has no
control over the information that you may access through the use of hot links contained in
these materials. SAP does not endorse your use of third-party Web pages nor provide any
warranty whatsoever relating to third-party Web pages.
© SAP AG 2003
Target Groups
Target Audience:
Þ Members of the Human Resources department
Þ MSS implementation teams
Þ Consultants
Duration:
Þ 3 days



Notes to the user
Þ The training materials are not teach-yourself programs. They complement the course
instructor's explanations. On the sheets, there is space for you to write down additional
information.
Þ There may not be enough time to do all the exercises during the course. The exercises are
intended to be additional examples that are dealt with during the course. Participants can also
use them to deepen their knowledge after the course.
© SAP AG 2006
Course Prerequisites
Required:
Þ SAPHR (mySAP Human Resources Solution Overview)
Þ HR505 (Organizational Management)
Recommended:
Þ HR305 (Configuration Master Data)
Þ HR130 (Essentials of SAP Enterpri se Portal in HCM)
Þ HR050 (Business Processes in Human Capital Management)



© SAP AG 2006
Course Goals
Þ Understand the portal system landscape
Þ Configure and explain special technical aspects
of MSS
Þ Describe the interaction of MSS and the SAP system
Þ Describe and use MSS services within HR
(My Staff)
Þ Customize the central element team viewer;
understand PCR and workflow within MSS;
build up pages and load iViews
Þ Explain special iViews of the MSS package,
their customizing and their background
This course will prepare you to:



© SAP AG 2006
Contents
Unit 1 MSS Overview
Unit 2 Manager Self-Service Fundamentals in the Enterprise Portal
Unit 3 The Employee Review Workset
Unit 4 The Compensation Workset
Unit 5 The ESS Workset in MSS
Unit 6 The Team Calendar Workset
Unit 7 The Personnel Change Requests (PCR) Workset
Unit 8 The Recruitment Workset
Unit 9 The Reporting Workset
Unit 10 The Headcount Workset
Unit 11 Team Viewer
Preface
Appendix Homepage Framework





© SAP AG HR260 1-9
© SAP AG 2006
MSS Overview:
Unit 1 MSS Overview
Unit 2 Manager Self-Service Fundamentals in the Enterprise Portal
Unit 3 The Employee Review Workset
Unit 4 The Compensation Workset
Unit 5 The ESS Workset in MSS
Unit 6 The Team Calendar Workset
Unit 7 The Personnel Change Requests (PCR) Workset
Unit 8 The Recruitment Workset
Unit 9 The Reporting Workset
Unit 10 The Headcount Workset
Unit 11 Team Viewer
Appendix Homepage Framework




© SAP AG HR260 1-10
© SAP AG 2006
MSS Overview
Þ Manager’s needs
Þ MSS concept
Þ MSS components
Content:




© SAP AG HR260 1-11
© SAP AG 2006
MSS Overview: Goals
Þ Explain Manager’s needs
Þ Explain the MSS concept
Þ Explain the MSS components
Þ Describe the opportunities MSS offers
your company
At the end of this unit you will be able to:




© SAP AG HR260 1-12
© SAP AG 2003
Question and Answer
Question:
What is the current situation for managers?
Answer:
Þ Managers have a heavy work load and are continuously under
pressure
Þ Managers have to make decisions based on the information available
Þ Managers have to analyze too much information that is distributed
between too many different systems
Þ Managers do not have a suitable tool that supports them in their
administrative tasks







© SAP AG HR260 1-13
© SAP AG 2006
What Situation Are Managers Currently in? I
Peter F.
Motivate Employees
Motivate Employees
Perform Certain Tasks
Perform Certain Tasks
Control and Reduce Costs
Control and Reduce Costs
Manage Budgets
Manage Budgets



Þ In a world where conditions are constantly changing, it is extremely important that superiors
make the right decisions at the right time. To do this, they need sufficient information.
However, they often spend a lot of time searching for the right information. Even completing
management tasks demands far too much time because superiors do not have the appropriate
tools that would facilitate their work.

© SAP AG HR260 1-14
© SAP AG 2006
What Situation Are Managers Currently in? II
Motivate Employees
Motivate Employees
Perform Certain Tasks
Perform Certain Tasks
Control and Reduce Costs
Control and Reduce Costs
Manage Budgets
Manage Budgets
Hire the Right
People
Recognize and Reward
High-Performance Employees
Distribute Tasks
Peter F.



Þ Success in today's economy is a difficult undertaking full of challenges. Companies are
competing in global markets that are unpredictable and dynamic, and where mistakes are
quickly punished. Quality products or services must often be launched faster than before and
this must frequently be accomplished with fewer resources. Productivity and cost efficiency
must be maximized in view of the wide-spread company reorganization.
Þ This situation mainly affects superiors because companies are increasingly decentralizing
management tasks. This means: Superiors are under a great deal of stress to fulfill
requirements and make the right decisions.
Þ Let us examine a few tasks superiors are responsible for in more detail.
Þ They must:
º Motivate employees
º Complete certain tasks, such as buying and selling
º Control and reduce costs
º Manage the company's budget

© SAP AG HR260 1-15
© SAP AG 2006
What Situation Are Managers Currently in? III
Motivate Employees
Motivate Employees
Perform Certain Tasks
Perform Certain Tasks
Control and Reduce Costs
Control and Reduce Costs
Manage Budgets
Manage Budgets
Hire the Right
People
Hire the Right
People
Recognize and Reward
High-Performance Employees
Recognize and Reward
High-Performance Employees
Distribute Tasks
Distribute Tasks
Plan Budget
and Quota
Trigger
Processes
Authorize
Personnel Change
Requests
Peter F.



Þ But this is not enough. They must also:
º Appraise their employees
º Recognize and reward high-performance employees appropriately
º Distribute tasks
º Assign personnel to projects, and
º Hire people best suited for future tasks

© SAP AG HR260 1-16
© SAP AG 2006
Systems
What Situation Are Managers Currently in? IV
Hire the Right
People
Hire the Right
People
Recognize and
Reward High-
Performance
Employees
Recognize and
Reward High-
Performance
Employees
Distribute
Tasks
Distribute
Tasks Motivate
Employees
Motivate
Employees
Perform
Certain
Tasks
Perform
Certain
Tasks
Control and
Reduce
Costs
Control and
Reduce
Costs
Manage
Budgets
Manage
Budgets
Trigger
Processes
Trigger
Processes
Authorize
Personnel Change
Requests
Authorize
Personnel Change
Requests
Plan Budget
and Quota
Plan Budget
and Quota
Reporting
Peter F.



Þ In most companies, superiors must perform planning tasks such as budget and headcount
planning once a year. As part of their tasks they also have to trigger processes.
Þ This is in addition to management tasks such as authorizing personnel change requests or
correcting cost center postings. In addition, they also authorize transfers of employees to other
departments. This is often very time-consuming and requires a great deal of organizational
effort.
Þ To complete all of these tasks, superiors need information, tools and reports. The information
is often distributed between various systems in a company and access may be restricted.
Where access to systems is available, they still have to log on multiple times and search for
the necessary information and reports. Where no direct access is available the superior must
also communicate by telephone with the relevant departments.
Þ Today, detailed employee data and cost center reports are still printed on paper, therefore it is
difficult to find the right report. Departments create these reports on a monthly basis. As a
result of this there is no "real-time" data. Performing these processes on-line would
considerably reduce costs.


© SAP AG HR260 1-17
© SAP AG 2003
Problem: Limited Access to Systems and
Information
HR
BW
FI
SRM
Internet
Legacy
Systems
Employee
Project
lead
Manager
Roles
Peter F.
Intranet
CRM
Departments



Þ A manager has only limited access to the systems that contain the information he needs. A lot
of time is spent on forms and written messages to the HR department in order to conduct
routine tasks.
Þ A manager must read through excel sheets and other screens in order to find key figures he
needs (e.g. headcount)

© SAP AG HR260 1-18
© SAP AG 2006
Manager’s Self-Service Is the Answer
Manager’s
Self-Service
Manager’s
Self-Service
Gain a Competitive
Advantage Through
Knowledge and
Keep it
· Customers
· Products
· Competitors
· Market Trends
SAP Business Package Manager Self-Service
Get the
Right
Business
Information
· Main Task
· Indicator
· E- Mail/Calendar
· Applications
Manage
Your
Employees
· Skills & Talents
· Career Goals
· Availability
· Reviews
· Recruiting
Manage Your
Budgets
· Cost Centers
· Orders &
Purchases
· Budgeting
· Monitori ng
· Predictions



Þ Manager’s Self-Service is the answer to the challenges described on the previous slide:
º Superiors have extensive access to all information where they can complete all personnel
management tasks.
º They have a user interface that is as easy to use as other established websites on the
Internet (for example, a bookstore).

© SAP AG HR260 1-19
© SAP AG 2006
MSS: My Staff and My Budget



Þ Manager Self-Service comprises two parts:
º My Budget supports managers in fulfilling their cost and budget responsibilities. This
includes annual budget planning, budget monitoring, cost analysis and the correction of
postings.
º My Staff supports superiors with personnel planning and management.

© SAP AG HR260 1-20
© SAP AG 2006
What Does MSS Offer? Information



Þ MSS provides information from different sources. This includes SAP reports, infotype
information, Business Warehouse and SAP queries. When using Portal content, information
from other sources (for example, salary overviews) may also be included.

© SAP AG HR260 1-21
© SAP AG 2006
What does MSS offer? Web-Enabled SAP
Processes



Þ MSS Web-enables SAP processes. Before MSS was introduced, secretaries, HR
Administrators and other people were involved, from an administrative point of view, in
processes such as compensation planning and employee reviews. Now superiors and HR
personnel can complete these activities. Consequently, the personnel department can be more
of a business partner than a purely administrative department.

© SAP AG HR260 1-22
© SAP AG 2006
What Does MSS Offer? New Process Opportunities



Þ With the flexible framework for handling processes triggered by superiors, MSS offers new
possibilities for structuring your personnel administration activities more efficiently. You can
use this framework to implement time-consuming and form-based processes, for example
applying for a loan. MSS provides 11 forms as standard.

© SAP AG HR260 1-23
© SAP AG 2006
Worksets and Functions in MSS



Þ The My Staff part of MSS offers 9 worksets:
º Overview
º Attendance
º Employee Review
º Personnel Change Request
º Recruitment
º ESS in MSS
º Reporting
º Compensation
º Headcount Planning

© SAP AG HR260 1-24
© SAP AG 2006
MDT vs. MSS: Integration Is the Answer



Þ MDT (Manager's Desktop) was the predecessor of MSS functions, based exclusively on
mySAP ERP.
Þ MSS Reporting was enhanced so that you can create additional reports for customers, this was
not previously possible in MDT.

© SAP AG HR260 1-25
© SAP AG 2006
Documentation and Implementation Documents
See the following websites for detailed
information for your implementation.
https://www.sdn.sap.com
http://service.sap.com/MSS



Þ SAP provides you with extensive documentation to support your implementation of MSS.
Þ For various configuration guides for the Manager Self-Service worksets, amongst other things,
see http://service.sap.com/mss.

© SAP AG HR260 1-26
© SAP AG 2003
MSS Overview: Summary
Þ Explain Managers’ needs
Þ Explain the MSS concept
Þ Explain the MSS components
Þ Describe the opportunities MSS offers
your company
You are now able to:




© SAP AG HR260 1-27
Exercises


Unit: MSS Overview

I n this exercise:
• Rethink the MSS general concept.
• Develop first proposals of the needs for MSS in your company.

1 List the two parts of MSS and explain their purpose.

2 MSS offers three different kinds of functions. List them.

3 My Staff consists of which components?

4 What is the relationship between the Manager’s Desktop and Manager Self Service
(MSS)?

5 If you think of the daily work of the manager in your company: Which functions
does he/she need? List them. (During the course we will try to find suitable
solutions for the needs you listed, based on the MSS functionalities)




© SAP AG HR260 1-28

© SAP AG HR260 1-29
Solutions


Unit: MSS Overview

1 List the two parts of MSS and explain their purpose.
a. My Budget supports a manager in fulfilling their cost and budget
responsibilities. This includes annual budget planning, budget monitoring, cost
analysis and the correction of postings.
b. My Staff supports a manager in fulfilling his/her administrative and planning
tasks in Human Resources.

2 MSS offers three different kinds of functions. List them.
Information (e.g. Attendance Overview), Web-enabled mySAP ERP processes (e.g.
Edit Appraisals in the Employee Review workset), New process opportunities
(PCR).

3 My Staff consists of what components?
The My Staff part of MSS offers 9 worksets:
• Overview
• Attendance
• Employee Review
• Personnel Change Request
• Recruitment
• ESS in MSS
• Reporting
• Compensation
• Headcount/Quota Planning

4 What is the relationship between the Manager’s Desktop and Manager Self Service
(MSS)?
MDT and MSS serve a similar process but as the predecessor of MSS, MDT was
not web enabled and was based exclusively on functionality from the mySAP ERP
system.


© SAP AG HR260 1-30
5 If you think of the daily work of the manager in your company. Which functions do
they need? List them. (During the course we will try to find suitable solutions for
the needs you listed, based on the MSS functionalities)






© SAP AG HR260 2-31
© SAP AG 2006
Manager Self-Service Fundamentals in the Enterprise
Portal: Overview Diagram
Unit 1 MSS Overview
Unit 2 Manager Self-Service Fundamentals in the Enterprise Portal
Unit 3 The Employee Review Workset
Unit 4 The Compensation Workset
Unit 5 The ESS Workset in MSS
Unit 6 The Team Calendar Workset
Unit 7 The Personnel Change Requests (PCR) Workset
Unit 8 The Recruitment Workset
Unit 9 The Reporting Workset
Unit 10 The Headcount Workset
Unit 11 Team Viewer
Appendix Homepage Framework




© SAP AG HR260 2-32
© SAP AG 2006
¤ Portal Infrastructure
¤ Portal Appli cation
¤ Portal Content
¤ User Administration
¤ Business Package for
Manager Self-Service
Contents:
Manager Self-Service Fundamentals




© SAP AG HR260 2-33
© SAP AG 2006
¤ Explain the purpose of an enterprise portal
¤ Name the aims of portals in a company
¤ Describe the advantages of using an enterprise
portal
¤ Name the advantages of Business Packages
¤ Name the development tools for the portal
¤ Create users and user groups
¤ Assign roles to user groups
After completing this unit, you will be able to:
Manager Self-Service Fundamentals: Objectives




© SAP AG HR260 2-34
© SAP AG 2006
¤ You are part of a project team that is going to
introduce the Manager Self-Service portal
component. Therefore you want an overview of the
main functions of the SAP Enterprise Portal
Manager Self-Service Fundamentals: Business Scenario




© SAP AG HR260 2-35
© SAP AG 2006
Challenge: Too many End-User Interfaces
SAP R/3
SAP SCM
Other
SAP Systems
SAP CRM Tradi ng
e-Sales
Other
Systems
(non-SAP)
ERP Systems
(non-SAP)
Technical
Systems
...
E
n
t
e
r
p
r
i
s
e

A
p
p
l
i
c
a
t
i
o
n
s
E
n
d
-
U
s
e
r

D
e
s
k
t
o
p ERP
B2B
Workfl ow
CRM
Legacy
Internet
Groupware



Þ End users must frequently combine applications in interconnected business views and business
processes. This means that end users find information and must react to it; for example, about
a missing delivery of a single customer, independently of where this information is in the IT
landscape, and where reactions are required.
Þ Many different user interfaces are necessary to execute a variety of different applications. This
means that opportunites for an improved customer service, increased process flow efficiency
and higher employee productivity frequently cannot be used.

© SAP AG HR260 2-36
© SAP AG 2006
Single Sign-On in the Enterprise Portal
...
SAP R/3
SAP SCM
Other
SAP Systems
SAP CRM Tradi ng
e-Sales
Other
Systems
(non-SAP)
ERP Systems
(non-SAP)
Technical
Systems
E
n
t
e
r
p
r
i
s
e

A
p
p
l
i
c
a
t
i
o
n
s
E
n
d
-
U
s
e
r

P
o
r
t
a
l



Þ An enterprise portal can establish a connection between the applications and the required
information necessary for completing a task. The portal gives the end user a complete view of
the company at a glance. This is based on multiple data sources and is integrated into multiple
operational applications in the back office


© SAP AG HR260 2-37
© SAP AG 2006
Enterprise Portal – The Solution

P
e
o
p
l
e

P
l
a
t
f
o
r
m

C
o
n
t
e
n
t



Þ SAP Enterprise Portal is designed to empower people to collaborate effectively across the
Internet on any given task – at any time and from anywhere. As the leading enterprise portal
offering on the market today, SAP Enterprise Portal incorporates both platform technology
and content in its unique offering. It provides employees and external stakeholders, such as
customers, suppliers, business partners, and investors with a role-based, central access point to
personalized information, applications, and services.
Þ As with any platform, it is only useful when there are applications that run on it. SAP provides
customers with a jump start in creating such applications by providing business packages with
targeted content for various roles within the organization, or external to it.
Þ SAP Enterprise Portal 6.0 supports a wide range of standards:
º iView development: Java, .Net
º User management & security: LDAP, X.509, JAAS
º Connector: JCA
º Information / content exchange: ICE, XML, WebDAV
º APIs: Java, JNDI (PCD API)
Þ SAP Enterprise Portal 6.0 supports Web services (UDDI, SOAP)
º iViews can use Web services
º Portal services (such as user management) can be called as Web services

© SAP AG HR260 2-38
º Connectors can be called as Web services
Þ SAP Enterprise Portal 6.0 is Unicode-compliant
Þ SAP participates in standardization groups such as the Java Specification Request 168 Portlet
Specification (JSR 168) and the Web Services for Remote Portals (WSRP)

© SAP AG HR260 2-39
© SAP AG 2006
SAP Enterprise Portal: Service Characteristics
SAP NetWeaver™
C
o
m
p
o
s
i
t
e

A
p
p
l
i
c
a
t
i
o
n

F
r
a
m
e
w
o
r
k
PROCESS INTEGRATION
PEOPLE INTEGRATION
Multi-Channel Access
Portal Collaboration
INFORMATION INTEGRATION
APPLICATION PLATFORM
L
i
f
e
c
y
c
l
e

M
a
n
a
g
e
m
e
n
t
Knowledge
Management
Business
Intelligence
Master Data Management
Business Process
Management
Integration
Broker
J2EE ABAP
DB and OS Abstraction
SAP Enterprise Portal (SAP EP)
Has the Following
Core Functions :
People Integration
Þ Portal Infrastructure
Þ Team-Based & Real -Time Coll aborati on
Information Integration
Þ Knowledge Management
Examples for Integrating with
Other SAP NetWeaver Components:
Þ SAP EP Uses the SAP Web
Appli cati on Server As a Runtime Environment
Þ SAP EP All ows a “ One-Step” Integration
with SAP BW (Business Intell igence)
Þ SAP Master Data Management Uses SAP EP



Þ SAP Enterprise Portal provides the following core functions:
º Portal infrastructure: The SAP Enterprise Portal provides a personalized, secure user
interface, that you can access using many different instruments. It connects applications,
information, and processes from SAP and non-SAP sources, in an interconnected role-
based Portal. It supports UNIX and Microsoft Windows Servers, and is provided in over 20
languages.
º Collaboration: SAP Enterprise Portal provides Collaboration Rooms and tools for real-
time Collaboration, so that teams and work groups can efficiently share information, ideas
and their work. Administrators manage shared e-mails, calendars, threaded discussions and
document storage, and can update memberships and authorization rights for them.
º Knowledge Management: As a central point of access, the SAP Enterprise Portal gives
you access to unstructured content that is stored in SAP Content Management systems and
repositories by third party administrators. It facilitates the user-friendly and flexible
creation and publishing of documents, intelligent classification and subscription, stable
version management as well as powerful searching and navigating. Additionally, it
provides an open framework for creating and managing document and file-based
applications as well as Content and user services.


© SAP AG HR260 2-40
© SAP AG 2006
Core Functions of the SAP Enterprise Portal
User
Manager
Speci ali sts
Business
Packages
SAP
Enterprise
Portal
UNIX



Þ The SAP Enterprise Portal contributes greatly to reducing the total cost of ownership
(TCO). This is achieved by the many different Portal levels. From administration to the end
user, SAP provides you with the appropriate tools. For example, Business Packages provide
you with one of the most extensive Business Content libraries that reflects on SAPs
development experience in various industries, which spans over 30 years. This guarantees you
that the SAP Enterprise Portal will be quickly implemented in your company. By using the
SAP Web Application Server as the runtime environment for the SAP Enterprise Portal you
also have extensive platform support available. Various UNIX derivatives and the Microsoft
Windows Server in combination with differing databases are supported.
Þ To allow global companies to implement the Portal in different languages, the SAP Enterprise
Portal is provided in over 20 languages, along with the appropriate local support at an
operating system level. You can of course modify any aspects of the SAP Enterprise Portal to
suit the requirements of your company. In addition to the numerous configuration possibilities
of the Portal, you can enhance your SAP Enterprise Portal through your own developments.
Þ I nteroperability allows you to write your applications in the Microsoft.NET development
environment or in the SAP NetWeaver Developer Studio.
Þ Unification allows you to provide your end users with a seamless integration of information
from differing sources through the patented Drag&Relate technology. This increases
employee efficiency.

© SAP AG HR260 2-41
© SAP AG 2006
Steps for Logging on to the Portal
Open a
Web Browser
Enter the URL for
the SAP Enterprise Portal
Enter User ID
and Password
Portal Client
Portal Client
SAP Enterpri se Portal 6.0 – Microsoft Internet Expl SAP Enterpri se Portal 6.0 – Microsoft Internet Expl
Fil e Edi t Vi ew Favorites Tools
http://twdf0000.wdf.sap.corp:50000/i rj/
User
Password



Þ You can configure the portal so that it uses the same user names and passwords that are used
for logging on to the business network. SAP supports access to the SAP Enterprise Portal
using a dial-up connection. To do this you need the appropriate URL for logging on.
Þ The URL is composed as follows:
º http://<Host name of Portal server>.<Domain>:<Default Port of J2EE Engine>/irj (IRJ =
iView Runtime for Java).


© SAP AG HR260 2-42
© SAP AG 2006
Masthead
Tool Area
Top-Level Navigation
Page Title Bar
Screen Elements of the Portal Desktop
Collaboration Search
Home CorporateServices Business Area Business Area My Staff My Budget BI Analyst BI Consumer
Overview| Attendance| EmployeeReview| Personnel ChangeRequest | Recruitment | Reporting| Compensation| QuotaPlanning
EmployeeProfile
DetailedNavigation
Þ CompensationInformation
Þ Personnel Development
Þ EmployeeDocuments
Þ Appraisal Overview
Þ Edit Appraisals
Þ ObjectiveSettingandAppraisals
Þ EmployeeProfile
Dynamic Navigation
DirectlyReporting Employees
Employee Personnel Number
JuliaGrimm
AndreaKlein
Felicitas Bauer
DonnaHerz
Daniel Leitner
00001444
00001450
00001451
00001452
00001453
Drag&RelateTargets
Þ Retailers Customer Complaints
Þ Retailers Address Book
Þ Display Material
Þ Display Customer
Þ Sales Analysis
Þ TopCustomer
Þ TopMaterial
Þ TopSales Organization
RelatedLinks
Þ Customer by Country
Þ Display Customer
Þ TopCustomer
Þ TopMaterial
Þ TopSales Organization
Back Forward
Photo General Data
JuliaGrimm(000011444)
ContractData
Work Contract
HiringDate
Cap. Util.Level
Organizational AssignmentOMore...
Org. Unit
Position
Cost Center
Payroll Area
Communications Data
E-Mail Julia.Grimm@ides.com
Office BAC/Au.22
Telephone 56565
Personnel Structure
Personnel Area Frankfurt
Personnel Subarea HeadOffice
EEGroup Active
EESubgroup Salariedstaff
Personnel Data
BirthDate 6/21/1965
Mar.Status Single
Address Ms.
JuliaGrimm
Bismarckplatz 22
69117Heidelberg
EmergencyContact
Address
Ms.
JuliaGrimm
JohnGrimm
Walldorf
WelcomeChristianS. Help Personalize LogOff
AbsenceDays
DefineFilter Filter not active
Period2/11/2003– 2/11/2005
Period
2/16/2004–2/16/2004
Days
0.38
Description
Doctor‘s appointment
<<
February2004 March2004
>>
Content Area
Navigation
Panel
Header Area
iView Functions
iView Functions
Personalize Portal
Personalize Portal
History



Þ When displayed in the Web browser, the SAP Enterprise Portal output window, the Portal
Desktop, is divided into the following areas:
º Header area
º Page title bar
º Navigation panel
º Content area
Þ The header area is in the upper part of the browser window. This area does not change when
you navigate from one page to another. The header area includes a masthead, tool area and
top-level navigation.
Þ The masthead consists of:
º Branding image (usually company name and logo)
º Welcome text (usually welcome message and user ID)
º Function links (for personalizing the portal, help and logging off)
Þ The tool area is an area of the masthead that allows access to key applications, such as the
Collaboration Launchpad or a search component. Applications may differ, depending on the
company and the user.
Þ Top-level navigation is directly under the masthead, or when it is activated, under the tool
area. This represents the entry point for navigation using the Content that was assigned to you.

© SAP AG HR260 2-43
In the standard system, the entries in top-level navigation are organized in two tab levels (tab
for the first level and subtab for the second level) and are predefined by your administrator.
Þ …

© SAP AG HR260 2-44
Þ …
Þ The navigation panel is on the left-hand side of your browser window. You can use the arrow
symbols to compress the navigation panel to give you more space within the window. You can
also expand it, or modify it to the size required, to access tools and folders.
Þ According to the Content area (see below), the navigation panel can include the following
navigation iViews:
Þ Detailed navigation is the hierarchical continuation of top-level navigation. It includes all
Content underneath the second navigation level.
Þ A dynamic navigation iView includes controls for user interfaces, for example dropdown
lists and links, which you use to call the content displayed in the Content area. The iView can
consist of a list of customers, orders, regions, employees, or data which accesses a database.
Each time you choose an option in a dynamic navigation iView, you only update the data
currently displayed in the Portal Content area.
Þ The iView Related Links contains a list of links whose target topics are relevant for the
iView or Portal page that you are currently working on. The links are predefined at iView and
page levels (Portal Content Studio).
Þ Clicking on an object under Related Links opens its Content in a new browser window.
Þ For each user, the iView Portal Favorites provides a freely composable list of links for
directly accessing Portal objects, for example, Portal pages, full-page iViews, KM objects and
external objects, such as Web pages. This allows you to organize favorites in a folder
structure. Contrary to browser favorites, Portal favorites are client-independent and are
therefore available on every computer after you log on to the Portal.
Þ Knowledge Management must be installed as it provides the functions of the Portal favorites.
Equally, you must activate the Add to Portal Favorites option in the page title bar.
Þ The Drag&Relate iView provides you with a selection of Drag&Relate targets that link to
iViews, which were accordingly configured as Drag&Relate-enabled. The iView is displayed,
if the displayed page in the Content area contains iViews with corresponding Drag&Relate
operations.
Þ Drag&Relate is a powerful navigation technology, which accesses structured data and can link
it with structured data from other systems.
Þ Drag&Relate-enabled data in an iView are indicated by a small symbol on the data record.
You can use the mouse to drag the data hidden behind this symbol to a link in the
Drag&Relate iView. There you can trigger a navigation in the iView by releasing the mouse
button. This gives data, which would, for example, expect an entry screen, to the navigation
call and thus fills the entry screen and starts the data retrieval process.
Þ The actual content that you access is displayed in the Content area of the Portal Desktop. The
Content area is filled with data that you call from sources of information from your company
and from the Internet using small applications called iViews. The Content area shows a page
with multiple iViews or only one iView in full-page mode. iViews can access document files,
e-mails, websites and data in business applications. They compose a personalized screen of all
elements that are important for your task area. You can use iViews to expand the coverage of
your Portal to any available sources of information, for example, ERP systems (Enterprise
Resource Planning), productivity tools, custom-built applications, the World Wide Web and
others. iViews are not just static links that display words and numbers, they can return current
real-time information.


© SAP AG HR260 2-45
© SAP AG 2006
Page Title Bar
Welcome
Roles
Create Users
Documents
Overview
Portal Content
Page Options
Page Options
Navigate backwards and
forwards in the history
Navigate backwards and
forwards in the history
Current Page
Current Page
Personalize
Refresh
Open in new window
Details
Add to Browser Favorites
Add to Portal Favorites
BackForward History



Þ The page title bar is below the top-level navigation and provides you with functions for
personalizing pages in the Content area and efficient navigation possibilities on the Content
page currently displayed.
Þ As part of the page title bar, the history provides a selection of the Portal pages most recently
visited and allows you to quickly navigate to them. Pages that you visit more than once are
only included in the history once. The current page is displayed in bold font.
Þ You can use the Back and Forward links to navigate through the history of pages that you
have visited, similar to the Back and Forward functions of your Web browser.
Þ In the Page Options menu, you have additional functions, such as refreshing the page, opening
the current page in a new window, or adding the current page to your Web browser favorites.
If the Content administrator allows you to, you can personalize the current page, you can
determine the assigned Content that is displayed on the page and the layout of the page.

© SAP AG HR260 2-46
© SAP AG 2006
The Breadcrumb Path



Þ A further, configurable page title bar option is the breadcrumb path, which displays the
history of the pages last visited in a path format. Each object in the path is a link to the page
with that name. The currently displayed page is the last element of the path. You can click on
pages in the path to navigate to them.





© SAP AG HR260 2-47
© SAP AG 2006
Personalizing the Portal
Personalizing the SAP Enterprise Portal
¤ Portal Theme
Selection of predefined themes to change the appearance of the Portal
¤ Portal Language
Allows you to change the logon language
¤ User Assignment
Assigning users and password to systems without SSO functions
¤ User Assignment (Remote iViews)
Assigning users and password to remote Content providers
¤ User Password
Changing your user password
¤ User Profile
Maintaining your user profile (for example, address, tel. no., accessibility)
¤ WorkProtect Mode
Determines how the Portal handles unsaved data when navigating
Log Off Personalize Help



Þ You can use the Personalizelink in the header area of the Portal client to access various
options for modifying the SAP Enterprise Portal to suit your requirements. In addition to
selecting the portal theme or your preferred language, you can also change your user settings,
for example, your address.
Þ Personalization settings are user-specific and therefore are only valid for your user.
Þ In the Portal themearea of Portal personalization, define the portal appearance for your user.
You can select from the themes that your Content administrator has predefined. Themes
determine, for example, the fonts, colors and background of Portal elements. SAP provides
multiple themes.
Þ You use the Portal languagepersonalization option to determine the language of the Portal
for your user. The language settings influence, for example, menu texts and button texts (if
available in the language) of the Portal.
Þ If you have not selected a Portal language and the administrator has not selected a language
for you, the Portal considers the language setting of the Web browser. This setting also affects
the language of the SAP Enterprise Portal logon screen.
Þ User Assignment: iViews can access data from secure data sources and make it available, that
is from an application that requires logon information. Assigning users and passwords to a
data source facilitates a rudimentary Single-Sign-On (SSO). This means that you do not have

© SAP AG HR260 2-48
to repeatedly enter your logon data when an iView calls data from a secure source. The data
sources and systems must be set up by your administrator in advance.
Þ User Assignment (Remote iViews): This allows you to provide logon information for iViews
that include Content from a remote Content provider. This option is only relevant if your
organization has a global Portal environment with syndicated Content. Global Portal
environment: Within a company there is more than one SAP Enterprise Portal worldwide.
They each provide Content for the other Portals and in this case are remote Content providers.
Þ User Password: This allows you to change your password for the SAP Enterprise Portal. You
should regularly change the standard password assigned to you, to improve Portal security.
The administrator can influence the quality and validity of a password.
Þ Your user profiledetermines your identity, provides information about you, details about
your position within the company and your contact information. With a user profile, other
Portal users can find you and communicate with you, and the Portal user administrator can
manage Portal users better. You can use the Activate Accessibility checkbox to activate the
functions for working accessibly in the Portal.
Þ WorkProtect Mode: iViews and their applications can include forms with fields in which you
can enter data. If when working in the Portal, you exit the active window of such an
application to go to another page, all data that you entered in this iView, or changes to these
iViews, are lost. The WorkProtect mode prevents unsaved data from being lost when
navigating. When you activate this function, all navigation links are started in a new window.
The active window with the unsaved data is retained.

© SAP AG HR260 2-49
© SAP AG 2006
Enterprise Portal – Personalization
My Sales Figures
My Weather
Content Personalization of
3. Level: My iViews
Content Personalization of
3. Level: My iViews
Content Personalization of
2. Level: My Page
Content Personalization of
2. Level: My Page
Content Personalization of
1. Level: My Role
Content Personalization of
1. Level: My Role
Company
Branding
Company
Branding



Þ You can completely modify the user interface (UI). You can position navigation iViews
anywhere within the interface. This slide shows the design of a standard SAP Enterprise Portal
page before customer-specific branding. Both the company and individual users can
personalize the page. For this personalization, the user must be assigned a particular role,
eu_role. (eu = every user)
Þ Portal theme: The company modifies the appearance.
In the "portal theme" area, companies can easily modify the page design to achieve a
standardized company image. Company personalization usually includes the company logo,
as well as colors that define the branding of the company, images to arouse interest, and so on.
Þ Level 1: The company determines Content for various roles.
By assigning roles to individual users, companies determine which worksets users can access.
Users can access individual worksets using the tab pages at the top of the page.
Þ Level 2: Users determine the page layout
Depending on their work preferences, users can change the way in which the iViews displayed
for their role are arranged on the page. For example, they might want to move the iView they
use the most, to the top left-hand area.
Þ Level 3: Users determine the displayed iViews
Users can also determine which iViews are displayed. However, a company can determine
iViews that are always displayed.

© SAP AG HR260 2-50
© SAP AG 2006
Personalize Pages
iView 1
Personali zed Page
iView 2
iView 3
iView 4
i View 7
iView 6
Page B
iView 5
Portal
Content
Folder
Subfolder
Save Close
Display Layout: 2 Col umns (Equal Width)
Column1 Column2
iView 1 iView 3
iView 4
Add iView/Page
to Page
Remove
Page
1. Select Layout
1. Select Layout
3. Save Changes
3. Save Changes
2. Arrange
iView
2. Arrange
iView
iView 5
iView 2
Drag&Drop
BackForward History
Personalize
Refresh
Open in new window
Details
Add to Browser Favorites
Add to Portal Favorites



Þ You can use the Personalizeoption from the option menu of the page title bar to determine the
layout and content of a page. Your Content administrator must have allowed this page to be
personalized.
Þ You use the page layout to determine how the Content is arranged. The administrator
predefines possible page layouts (for example, single column, double column) that you can
select from. You can use Drag&Drop to move the iViews into the required order, or into a
different column.
Þ In the Personalized Pagearea, you can see which iViews are assigned to the page and which
iViews from this supply you can still assign. To be able to add iViews from the Portal Content
area to the page, the administrator must have assigned the relevant authorizations in the
underlying tree structure.

© SAP AG HR260 2-51
© SAP AG 2006
Personalize iViews
Available Properties Depending
on iView Type and Content
Transfer Cancel
| Caching
false
| SERIES
50
| Time Scale for Calendar
1 Hr.
iView
1/2 Hr.
1 Hr.
1 Hr.
2 Hrs.
Compress /
Expand
Personalize
Refresh
Open in new window
Remove from Page
Details
Reset All Properties



Þ Personalizing iViews is a further possibility to modify the Portal to suit your requirements.
This personalization also depends on whether the Content administrator allows it. The
properties of an iView that you can modify is heavily dependent on the iView itself and its
content. To do this, select the Personalizeentry from the iView option menu. A new window
with personalization options appears.
Þ The Reset All Properties pushbutton restores all settings to the default values. When you have
made your changes, choose Transfer to save this entry. This automatically closes the
personalization window and independently refreshes the iView on the page.


© SAP AG HR260 2-52
© SAP AG 2006
Modules of SAP Enterprise Portal
SAP Enterprise Portal
SAP Enterprise Portal
Collaboration
Collaboration Launch Pad, Collaboration Rooms Collaboration Launch Pad, Collaboration Rooms … …
Knowledge Management
Content Management Content Management
Portal Platform
Portal Framework
(Portal Runtime with Services and Components)
Java Dispatcher Java Dispatcher
Java Java
Server Server
Java Java
Server Server

Java Dispatcher Java Dispatcher
Java Java
Server Server
Java Java
Server Server


SAP Web AS Java
SAP Enterprise Portal
Database
TREX TREX



Þ The SAP Enterprise Portal comprises three large modules: the Portal platform, Knowledge
Management and collaboration. These modules are completely integrated with each other.
This means that Knowledge Management needs the Portal platform as an integration and
runtime environment. Equally, Knowledge Management (KM) functions are a prerequisite of
collaboration, and KM in turn uses collaboration functions.
Þ The SAP Enterprise Portal is a Java application that is deployed in the J 2EE Engine of the
SAP Web Application Server. Therefore, the Portal integrates the J2EE architecture
implemented in the SAP Web Application Server.


© SAP AG HR260 2-53
© SAP AG 2006
Software Architecture of SAP Enterprise Portal
Browser
Browser
Data Sources
Data Sources
SAP Enterprise Portal
SAP Enterprise Portal
Portal Framework
Collaboration
Knowledge Management
TREX TREX CM CM
Portal Runtime Portal Runtime
Portal Components Portal Components
Page Buil der
Portal Services Portal Services
User
Management
Portal Content
Directory
Connectivity Framework Connectivity Framework
Connectors
System
Database
User User
Management Management
Engine Engine
Unificati on
Admin. Tools
User
Persistence
Store



Þ As part of the Portal Framework, Portal Runtime (PRT) represents the core of the Portal
environment. From a technical point of view, Portal Runtime, as a J2EE Engine application,
provides the runtime environment for portal components, portal services and the connector
framework.
Þ A Portal component is Java code that is executed according to user queries and generates
HTML output for Web browser display. For example, the Page Builder is a portal component
that builds portal pages and provides them to the Web browser. Portal components can be the
basis for creating an iView.
Þ Portal services are interfaces that exchange procedures and data. They provide portal
components and other service functions. For example, the service Portal Content Directory
(PCD) is an interface for the Portal system databasein which all Portal data exists. User
management is an additional service. This is an interface between Portal Runtime (and
related applications) and the User Management Engine (UME). The UME is a separate
software component that manages user and group data stored in the User Persistence Store.
Individual Portal applications are not assigned to their own user management and
administrators can manage user data centrally, using the UME.


© SAP AG HR260 2-54
© SAP AG 2006
Process Flow of Requests
Portal User
Portal User
1 URL Query
4
HTML
Portal Runtime Portal Runtime Portal Runtime
2
Portal Services Portal Services Portal Components Portal Components
Page Buil der
Admin. Tools
User
Management
Portal Content
Directory
3
Portal System
Database
User
Persistence
Store
User User
Management Management
Engine Engine



Þ The general process flow of a client request in the Portal can be represented as follows:
Þ When a user starts an iView, the client sends an HTTP or HTTPS request.
Þ The PRT is responsible for parsing the request and determines the following:
º the request object of the PCD
º user data, for example personalization data,
º log-on language, page personalization, iView personalization
Þ If the user who created the request has authorization for the requested object, the following
information is given:
º the Portal components to be executed, for example Page Builder
º a range of properties to be transferred to the Portal components; this can be a range of
properties for an iView or a page
Þ The PRT receives an instance of the Portal components to be executed and makes it available,
together with other information from the PCD. If the request is for a page, the Page Builder is
the activated Portal component. The Page Builder is responsible for parsing the information,
builds the page and generates the HTML. If the request refers to the Content of an iView, the
PRT activates the relevant components, which can, in turn, use Portal services to generate
HTML.
Þ The HTML is returned to the browser.

© SAP AG HR260 2-55
© SAP AG 2006
Object Assignments
User
Role
iView
Workset
Group
Page
Workset
User
Role
iView
Workset
Group
Page
iView
Page
iView
Page
iView
Role
Typical
Object Assignments
Possible
Object Assignments



Þ SAP Enterprise Portal is a scaleable portal with an open architecture, which you can use,
without restriction, to integrate Content. Portal Content calls information from various sources
of information such as websites, Groupware applications, legacy systems, ERP applications,
databases and document directories. The portal provides a complete set of tools for managing,
handling and monitoring the portal in a standard environment. These management tools are
conceived as modular portal pages or iViews, which you can use to delegate management
tasks according to your business scenario.
Þ Portal Content Directory (PCD)
º iView - Program that retrieves data from content sources in your enterprise and from the
Internet, and displays the data in the Portal Content area.
º Page - Consists of layout and assigned Content (for example, iViews)
º Workset - Collection of tasks, services and information that belong to a particular area of
activity (Content with navigation structure)
º Role - Collection of tasks, services and information available to groups of users; the role
determines which services can be accessed, additionally it displays the Content and the
navigation structure.

© SAP AG HR260 2-56
© SAP AG 2006
Portal Content Directory (PCD)
Portal Content Directory
Workset 1
i View 1
Role 1
Page 1
Folder A
Folder B1
Folder B2
Folder B3
Folder C1
Folder C2
Folder C3
...
Folder D1
Folder D2
Folder D3
...
Workset 2
i View 2
Page 2
iView 3
Page 3
...



Þ The Portal Content Studio is a central environment for developing and managing the Portal
Content described above. The tools for creating Portal Content available in the Portal Content
Studio allow both inexperienced and experienced Content developers to create all possible
Portal Content types, based on data resources, systems and applications of a company.
Þ The Portal Content Studio covers a wide range of possible portal users. By maintaining the
required iView properties, beginners can use the available iView templates to create their own
Portal Content. Furthermore, they can use existing Portal Content and Portal Content that they
created themselves to create simple portal pages. Advanced users, such as Content experts,
can use the extensive tools of the Portal Content Studio to create complex portal pages and
iViews.

© SAP AG HR260 2-57
© SAP AG 2006
Interfaces of the Portal Content Studio
Header Area
Navig.
Panel
Portal Desktop
Content
Area
Portal Catalog Portal Catalog
Editing Area Editing Area
Object Register and Path
Tools for Editing Objects
Object Editor
Tools for Subordinate Objects
Property
Editor
Register
Quick-Info
Portal Content
Tree
Portal Content Studio



Þ To access the Portal Content Studio, you must be assigned the Content administrator role (if
your Portal is based on standard roles provided by SAP). In top-level navigation, choose
Content Administration -> Portal Content, to start the Portal Content Studio. The following
two areas are displayed in the Content area:
Þ The Portal Catalog is on the left-hand side of the Portal Content Studio and displays Content
stored in the Portal Content Directory (PCD). The interface of the the Portal catalog comprises
the following areas:

© SAP AG HR260 2-58
© SAP AG 2006
Business Packages Provide Predefined Portal Content
User
Manager
Speci alists
SAP NetWeaver
Application and Integration Platform
Business Packages
I
n
t
e
g
r
a
t
i
o
n
P
o
r
t
a
l

C
o
n
t
e
n
t
People Information Processes



Þ With Business Packages, SAP provides predefined Portal content that fulfills task and
industry-specific requirements. Business Packages contain a multitude of iViews, that in turn
provide transactions, reports and documents and so on, from your various IT systems in the
enterprise portal. Business Packages accelerate the introduction of your enterprise portal,
increase productivity and provide a fast return on investment.
Þ To better fulfill the respective requirements of users, managers and specialists, Business
Packages are divided into three categories:
Þ Business Packages for Users cover all tasks that all users of the enterprise portal perform,
independently of their role in the company. They help beginners to get quickly acquainted
with the enterprise portal environment, thereby increasing user acceptance. The contents of
this Business Package include, amongst other things, e-mails, task lists, calendar, travel
expenses, managing benefits, Employee Self-Service, E-learning and searches in employee
directories.
Þ With Business Packages for Managers, decision makers can efficiently perform analyses and
get decision-relevant information. In addition, they provide extensive tools for planning and
managing workforce planning and budgets. This enables line managers, team managers and
project leaders to dramatically reduce the time they spend on administrative tasks and they can
concentrate on strategic tasks instead.
Þ Business Packages for Specialists are tailored to the requirements of experts from financial
accounting, sales, marketing and production. They provide operational tools, analytical

© SAP AG HR260 2-59
evaluations and time-critical warning messages, that enable quick actions based on the right
information. Consequently, experts receive consistent, precise and up-to-date information
from a wide range of sources.


© SAP AG HR260 2-60
© SAP AG 2006
Downloading Business Packages
SAP Developer Network (SDN),
Portal Content Portfolio (PCP) Area
SAP Service Marketplace (SMP),
Software Distribution Center Area
Download
•Open to Everyone •Onl y for Licensed Users



Þ Business Packages allow you to structure Portals out-of-the-box, without additional
development effort. After downloading Business Packages from the SDC, you can easily
incorporate them into an SAP Enterprise Portal. They comprise Portal content that is
preconfigured and geared to certain user profiles: Role-based functions and processes that are
available to all users in the entire value-added chain. Business Packages cover a large part of
the content required for a particular task.



© SAP AG HR260 2-61
© SAP AG 2006
Available BPs for Manager Self-Service I



Þ Source: https://www.sdn.sap.com
Remove available Business Packages from the Portal Content Studio (these pages are only
available in English):
Þ Business Package for Manager Self-Service (mySAP ERP 2004)
“The Business Package for Manager Self-Service (mySAP ERP) (MSS) provides your
managers with a personalized solution that supports decentralized decision-making processes
and thereby meets today’s market requirements. It serves as a single point of access to data
and information that help managers make the right decisions at the right time.”
Þ Version 60.1.1 Restricted Shipment
Þ To download a Business Package for Manager Self-Service, use the link above. The SAP
Developer Network appears. From here you can call the current Business Packages.
Additonally, you can gather information that affects the Portal technology.

© SAP AG HR260 2-62
© SAP AG 2006
Available BPs for Manager Self-Service II



Þ The selection of available Business Packages appears.
Þ After selecting the required Business Package, the relevant version is made available with the
button Add to Download Basket.

© SAP AG HR260 2-63
© SAP AG 2006
Available BPs for Manager Self-Service III



Þ The Download Manager supports you when downloading business packages.
Þ The Download Manager and the relevant documentation are available at:
http://service.sap.com/swdc.
Then choose "Download Basket" in the "Downloads -> SAP Software Distribution Center"
area.
Þ You can then import the business package within the Enterprise Portal.

© SAP AG HR260 2-64
© SAP AG 2006
Installing a Business Package
1.
2.
4. 3.
6.
5.



Þ To install a Business Package in the Portal, note the following steps:
º Log on as the Portal administrator (authorization) in EP
º The path: System Administration -> Transport -> Select Import
º Specify the location of the Business Package (on the Portal server or client file system)
º Find the Business Package file using the Search button.
º Decide whether the new objects overwrite existing objects in EP.
º Choose the Import button.
Þ This loads the Business Package (extension *.pkg) to the Portal.
Þ Then you find the individual parts of this package (role, workset, page, iView) in the Portal.
Þ All that is left to do is assign the new role to the prepared user group.

© SAP AG HR260 2-65
© SAP AG 2006
Create User



Þ To create a new user, choose the following path: User Administration -> Users -> Create User.
Þ At the very least, you must complete those fields indicated by a red star:
º User ID
º Define Password and Confirm Password
º Last Name
º First Name
º E-Mail Address
Þ Then drag the vertical scroll bar to the bottom and choose Create.

© SAP AG HR260 2-66
© SAP AG 2006
Create User Groups
2.
4.
3.
1.
5.
6.



Þ To create a new user group, choose the following path: User Administration -> Groups ->
Groups.
Þ Choose "Create".
Þ Enter the name of the user group.
Þ Save your entries.

© SAP AG HR260 2-67
© SAP AG 2006
Assigning User Groups I



Þ After you have created the user group, assign a user to it. To do this, choose Assign User to.

© SAP AG HR260 2-68
© SAP AG 2006
Assigning User Groups II



Þ You must choose the '+' button to search for the users that you want to assign to this group.

© SAP AG HR260 2-69
© SAP AG 2006
Assigning User Groups Ill



Þ In the user ID field, specify the user name that you want to assign to this group. Then, drag the
vertical scroll bar to the bottom and choose Search.

© SAP AG HR260 2-70
© SAP AG 2006
Assigning User Groups IV



Þ Select the found users and choose Select.

© SAP AG HR260 2-71
© SAP AG 2006
Assigning User Groups V



Þ The result: You have assigned a user group to a user.

© SAP AG HR260 2-72
© SAP AG 2006
Role Assignment I
1. 2.
3.



Þ You must assign a role to the user group. To do this, choose the following path: User
Administration -> Roles -> Roles
Þ In the Search field, enter the name of the role that you want to assign to the group. You can
also work with wildcards. Choose the Start button. The search results are displayed in the list.
Þ To now make the further assignments, choose the Edit link.

© SAP AG HR260 2-73
© SAP AG 2006
Role Assignment II
1.
2.
4.
3.



Þ You assign roles on this screen. Proceed as follows:
º In the search field, specify the group name.
º Choose the Start button
º The required group appears at the bottom-right of the window
º To assign the role to the group, and thereby to the assigned users, choose the Add button. In
doing so, you transfer the selected user group to the list of assigned users and groups
(upper right)
º Finally, save the assignment

© SAP AG HR260 2-74
© SAP AG 2006
Development Tools for the Enterprise Portal
Portal Content Studio
Tool s for
End Users
Visual Composer
SAP NetWeaver Developer Studi o (Web Dynpro)
(incl udes the Portal Devel opment Kit)(
Required Knowledge
User Devel oper Process Special ists
Process Owner
Admini strator
Complexity
Personalization
iViews Created
From Templ ates
iViews with
Help from
t-RFCs
Tailored
Devel opment
MSS Standard Implementation



Þ With the SAP Enterprise Portal, SAP provides various tools that require different capabilities.
Þ For MSS, it is recommended to use the standard tools and options, to contain iView
development.

© SAP AG HR260 2-75
© SAP AG 2006
SAP Enterprise Portal Content Studio
Technology
Focus
Business
Focus
¤ Integrated into SAP EP
¤ Based on assistants
¤ Create iViews quickl y
¤ SAP provides templates;
customers can create
templates
¤ Integrated into SAP EP
¤ Based on assistants
¤ Create iViews quickl y
¤ SAP provides templates;
customers can create
templates
Content
Expert
Content
Expert
Business
User
Business
User
Business
Application
Developer
Business
Application
Developer
J 2EE
Developer
J 2EE
Developer



Þ The Portal Content Studio is a central environment for developing and managing Portal
Content. This Content includes iViews, pages, worksets, roles and transport packages. The
tools for creating Content available in the Portal Content Studio allow Content experts to
create all possible Content types, based on data resources, systems and applications of a
company.
Þ Content administrators can start the Portal Content Studio from the standard Portal user
interface (additional front-end software is not necessary). Assistants guide you through the
process of creating Content. New iViews are based on templates provided by SAP and
partners.


© SAP AG HR260 2-76
© SAP AG 2006
SAP NetWeaver Visual Composer
Technology
Focus
Business
Focus
Content
Expert
Content
Expert
Business
User
Business
User
Business
Application
Developer
Business
Application
Developer
J 2EE
Developer
J 2EE
Developer
¤ Browser-based
¤ Intuitive modeling and design
¤ Rapid application development
¤ Prototyping
¤ Code-Free development
¤ Supports JSP and HTMLB
as well as Web Dynpro metadata
¤ Browser-based
¤ Intuitive modeling and design
¤ Rapid application development
¤ Prototyping
¤ Code-Free development
¤ Supports JSP and HTMLB
as well as Web Dynpro metadata



Þ SAP NetWeaver Visual Composer is a visual modeling tool that enables demanding Content
development for SAP Enterprise Portal, by moving related objects using Drag&Drop, and
through relationships between objects. There is no programming effort. Visual Composer is
entirely Web-based.
Þ Business experts can sit next to business users and can access the Visual Composer from any
computer, to create or modify Content, to convert business requirements into queries. The
target groups are Content developers (people who know what a user interface does, but are not
actually programmers). A Controller could, for example, use the Visual Composer to create
iViews, without code, that process data from an SAP system.
Þ The aim of the Visual Composer is to provide a visual tool that makes Content development
quick and easy, as well as:
º to minimize time and work effort required for creating Content
º to facilitate quick production decisions
º to reduce the total cost of ownership (TCO)
º to increase Return on Investment (ROI)
Þ For up-to-date information on the Visual Composer, see the /nw-vc quick link on the SAP
Service Marketplace.

© SAP AG HR260 2-77
© SAP AG 2006
SAP NetWeaver Developer Studio (Web Dynpro for
Java Perspective)
Technology
Focus
Business
Focus
Content
Expert
Content
Expert
Business
User
Business
User
Business
Application
Developer
Business
Application
Developer
J 2EE
Developer
J 2EE
Developer
¤ Eclipse-based
¤ Java expertise required
¤ Scalable MVC architecture
¤ Model-driven
¤ Device-independent
¤ Access to source code
¤ Eclipse-based
¤ Java expertise required
¤ Scalable MVC architecture
¤ Model-driven
¤ Device-independent
¤ Access to source code



Þ Web Dynpro is SAP's development environment for building professional Web user
interfaces for business applications. Its model-based approach minimizes the manual
programming effort and uses visual tools for designing and reusing interface components.
Web Dynpro is based on a high-performance and flexible Model View Controller (MVC)
architecture that facilitates a clear separation of user interfaces and application logic.
Developers for Business Applications have complete control of the generated code at all
times throughout the development process.
Þ The Web Dynpro tools support application developers in the implementation and design
phases. When you develop a Web Dynpro application, you create a platform-independent
meta model. For Web Dynpro for Java, Java classes are generated from this meta model and
used in a Servlet. Web Dynpro combines the strengths of the GUI/Dynpro approach from
mySAP ERP, including functions such as dictionary-based field validation and
troubleshooting, seamless integration into a software lifecycle, a distribution infrastructure for
performing all installation, upgrade, administrative and monitoring tasks, with Internet
innovations, for example, worldwide access and integration of random Content, using
hyperlinks.
Þ Advantages for developers are:
º As many designs as possible and as little programming as possible, higher productivity
through a declarative modeling approach instead of programming, layout, screen use,
navigation and data binding

© SAP AG HR260 2-78
º Reduced development effort through Web Dynpro patterns; user interfaces are configured,
not programmed
º …

© SAP AG HR260 2-79
º …
º Generic UI services, for example, automatic input help (F4), automatic conversion, checks
and troubleshooting for basic types
º Increased efficiency for Java development through complete integration into the Java
Development Infrastructure (JDI); this avoids error-prone tasks such as creating,
distributing and installing components
Þ For up-to-date information about Web Dynpros, see the /webdynpro quick link on SAP
Service Marketplace.

© SAP AG HR260 2-80
© SAP AG 2006
SAP NetWeaver Developer Studio (Java/PDK
Perspective)
Technology
Focus
Business
Focus
Content
Expert
Content
Expert
Business
User
Business
User
Business
Application
Developer
Business
Application
Developer
J2EE
Developer
J2EE
Developer
¤ Eclipse-based
¤ Complete J2EE support
¤ Expertise in object-oriented
programming and J2EE required
¤ PDK Business Package with
programming examples
¤ Supports JSP and HTMLB
for Java
¤ Eclipse-based
¤ Complete J2EE support
¤ Expertise in object-oriented
programming and J2EE required
¤ PDK Business Package with
programming examples
¤ Supports JSP and HTMLB
for Java



Þ J 2EE developers (with knowledge of object-orientated J2EE programming) receive full J2EE
support with SAP NetWeaver Developer Studio (J ava/PDK perspective). PDK stands for
Portal Development Kit and, from a technical point of view, is a Business Package. When it is
uploaded to the SAP Enterprise Portal, it provides documentation, tutorials, templates and
assistants for creating new portal applications.

© SAP AG HR260 2-81
© SAP AG 2003
MSS and the Enterprise Portal (EP) 6.0
Þ SAP EP is mandatory for MSS
Þ Technical reasons, especially portal-based eventing
Þ EP offers you additional
features for successful
MSS implementation
(KM; Personalization)



Þ The SAP Enterprise Portal is mandatory for MSS.
Þ MSS is deeply rooted and connected with the EP infrastructure (Eventing, URL-generation
for the reporting framework, session management).

© SAP AG HR260 2-82
© SAP AG 2006
Eventing Overview I
Eventing in MSS is a navigation paradigm that can be used differentl y
Þ Communication between iViews on the same page
These pages include:
¤ An event sender
¤ An event receiver




© SAP AG HR260 2-83
© SAP AG 2006
Eventing - Overview II
Eventing in MSS is a navigation paradigm that is used differentl y.
Þ Retaining selected
object as context
when navigating
through the
Business Package




© SAP AG HR260 2-84
© SAP AG 2006
¤ Explain the purpose of an enterprise portal
¤ Name the aims of portals in a company
¤ Describe the advantages of using an enterprise portal
¤ Name the advantages of Business Packages
¤ Name the development tools for the portal
¤ Create users and user groups
¤ Assign rol es to user groups
You should now be able to:
Manager Self-Service in the Enterprise Portal
Fundamentals: Conclusion




© SAP AG HR260 2-85
Exercise 1


Unit: Manager Self-Service Technology Fundamentals

I n this exercise:
• Describe the MSS technology fundamentals
• Check whether you are able to discuss the MSS technology
fundamentals with your team colleagues

1 What components are needed for MSS?

2 What technology is used for the MSS front end?

3 Which application components establish the connection from the SAP Enterprise
Portal to the mySAP ERP back end?

4 What is the difference between a portal role and the role in the mySAP ERP
system, and how do they interact in MSS?

5 A manager requests additional developments in order to tailor MSS to his/her
requirements. What is your approach?



© SAP AG HR260 2-86

© SAP AG HR260 2-87
Solutions 1


Unit: Manager Self-Service Technology Fundamentals

1 What components are needed for MSS?
The SAP Enterprise Portal and a mySAP ERP system >= 4.0B are mandatory for
MSS.

2 What technology is used for the MSS front end?
JSPs

3 Which application components establish the connection from the SAP Enterprise
Portal to the mySAP ERP back end?
JavaConnector (JCO) and RFC.

4 What is the difference between a portal role and the role in the mySAP ERP
system, and how do they interact in MSS?
The portal role determines which iViews are displayed in a portal page. Whether it
is filled with data is determined by the mySAP ERP authorization.

5 A manager requests additional developments in order to meet his/her requirements
in the MSS area. What is your approach?
Check Customizing possibilities in detail (keep the BAdIs in mind). Check the
Portal Content Studio tools (for example, inserting SAP transactions using
assistants). Check the Visual Composer. If the options prove to be infeasible,
consider a customized development using the NetWeaver Developer Studio.
Careful screen design for the iViews is needed (keep it simple, keep in line with the
principles of MSS you learn in this course). Use function modules already in your
SAP system.



© SAP AG HR260 2-88

© SAP AG HR260 2-89
Exercise 2


Unit: Manager Self-Service Fundamentals in the
Enterprise Portal
Topic: Creating a user

At the conclusion of this exercise, you will be able to:
• Create a user in the Enterprise Portal
• Assign roles to a user

Create a user in the Portal for your superiors so that your superior
can log on to the Enterprise Portal. The superior should also be
able to use the worksets for the “My Staff” role. Therefore you
need to assign various roles to the superior.

1 Log on to the Enterprise Portal. Enter the URL that your instructor gave you for
the Enterprise Portal. Your user is “HR260.a-XX” and the password is “init”.

2 Create a new user. The new user is HR260-XX
(XX = group number). The password is init.

3 Role assignment
3-1 Assign the necessary roles to the newly created user so that he or she can
use the manager worksets
3-2 Log on to the portal using user HR260-XX and change the password to
“welcome”

4 Check the worksets for the role “My Staff”. What do you notice? What do you
need to do to be able to see the data?

5 Link personnel number 26099XX (XX= group number) in the back-end system
with user HR260-XX and check whether the position of the personnel number is
indicated as the chief position.


© SAP AG HR260 2-90

© SAP AG HR260 2-91
Solutions 2


Unit: Manager Self-Service Fundamentals in the
Enterprise Portal
Topic: Creating a user

1 Logging on to the Portal
Log on to the Portal. Start the Internet Explorer. Enter the URL that your
instructor gave you for the Enterprise Portal.
Enter the user “HR260.A-XX” (XX = group number) in the “User ID” field. The
password is “INIT”. You are then asked to change the password. To do this, enter
“INIT” in the “Old Password” field. Enter your new password in the fields “New
Password” and “Confirm Password”. You can choose any password.
You are now logged on as the Portal administrator.

2 Creating a new user
In the first level navigation, select “User Administration” and in the second level
navigation, select “User”. In detailed navigation, choose “Create User”.
Fill the following fields in the “Create User” iView:
Field Name or Data Type Values
User ID* : HR260-XX (XX = group number)
Define Password: init
Confirme Password: init
Last Name Any
First Name: Any
E-Mail Address Any
Choose “Create”
You have now created a user in the Portal.

© SAP AG HR260 2-92
3 Role assignment
3-1 In the first level navigation, select “User Administration” and in the
second level navigation, select “Roles”.
In the “Search” field, enter “eu_role”. Select “in Roles” and choose Start.
The Every User role appears. In the roles rows, choose “Edit” to the right.
Now you assign users to roles.
In the “Search” field (lower-right area of the screen), enter the user
HR260-XX (XX = group number), select “in Users” and choose “Start”.
The user you searched for appears in the selection. Select the left
checkbox next to the user and choose the “Add” button, in the bottom-left
of the selection.
The selected user is transferred to the upper display of user/group
assignment. After you choose the “Save” button on the left-hand side of
the screen, the “eu_role” role is assigned to the user.
In the same way, assign the role “com.sap.pct.hcm.manager” to your user.
3-2 Logging on to the Portal using the new user
Log on to the Portal using the new user. You are asked to change the
password. IMPORTANT: Change the password to “WELCOME”

4 Check the worksets for the role “My Staff”. What do you notice? What do you
need to do to be able to see the data?
I cannot see any employees in the worksets because I have not yet linked the user
with the personnel number of the line manager in the back-end system.

5 In the back-end system, call transaction PA30 – Maintain HR Data, enter the
manager’s personnel number: 260991XX (XX = group number) Select infotype
0105 communication, subtype 0001 – System User Name. In the ID field, enter
the user HR260-XX (XX = group number) and save your entries.
Call transaction PPOME – Organization and Staff Assignment and check whether
the position of the manager is indicated as the chief position. If necessary, select
the position as the chief position.



© SAP AG HR260 3-93
© SAP AG 2006
Employee Review Workset: Course Overview Diagram
Unit 1 MSS Overview
Unit 2 Manager Self-Service Fundamentals in the Enterprise Portal
Unit 3 Employee Review Workset
Unit 4 Compensation Workset
Unit 5 ESS Workset ESS in MSS
Unit 6 Team Calendar Workset
Unit 7 Personnel Change Requests (PCR) Workset
Unit 8 Recruitment Workset
Unit 9 Reporting Workset
Unit 10 Headcount Workset
Unit 11 Team Viewer
Unit 12 Homepage Framework




© SAP AG HR260 3-94
© SAP AG 2006
Employee Review
Þ Working with the MSS workset “ Employee review”
Þ Customizing of the MSS workset “ Employee review”
Þ Business scenario examples
Content:




© SAP AG HR260 3-95
© SAP AG 2006
Employee Review: Goals
Þ Understand the content of the MSS workset
“ Employee review”
Þ Describe the functionality of this workset
Þ Customize this workset
At the end of this unit you will be able to:




© SAP AG HR260 3-96
© SAP AG 2006
Employee Review: Integration with SAP
Components
Compensation
Management (PA-CM)
Compensation
Management (PA-CM)
Organizational
Management (PA-OM)
Organizational
Management (PA-OM)
Training and Event
Management (PE)
Training and Event
Management (PE)
Time Management
(PA-PT)
Time Management
(PA-PT)
Enterprise
Compensation
Management (ECM)
Enterprise
Compensation
Management (ECM)
Personnel Development
(PA-PD)
Personnel Development
(PA-PD)
Personnel
Administration
(PA-PA)
Personnel
Administration
(PA-PA)
Objective Setting and
Appraisals
(PA-PD-PM)
Objective Setting and
Appraisals
(PA-PD-PM)




© SAP AG HR260 3-97
© SAP AG 2006
Employee Review: Portal View



Þ The Employee Review workset includes functions for managers for displaying and editing
various employee data.
Þ Managers can use this workset for the following tasks:
º Displaying important employee data when preparing for an employee review
º Planning new salaries taking the previous salary development of the employee into account
º Recruiting employees for a new project within their department based on the qualifications
of the employees
Þ This workset uses examples to illustrate how to use the MSS tools. Only a small amount of
customizing is necessary as MSS utilises functions already implemented in mySAP ERP.

© SAP AG HR260 3-98
© SAP AG 2006
Employee Review: Team Viewer iView



Þ To be able to use this iView you must:
º Implement the mySAP ERP components Personnel Administration (PA-PA) and
Organizational Management (PA-OM)
º Integrate the PA-PA and PA-OM components
Þ You need to make the required Customizing settings for the TeamViewer iView for the Object
and Data Provider.

© SAP AG HR260 3-99
© SAP AG 2006
Employee Review: General Data iView
Þ General Data
¤ Managers can use this iViewto display general data about employees in
their area of responsibility (for example, contact data such as office,
telephone number, or e-mail address).



Þ The iView also displays the following data:
º Personnel number
º Hiring date
º Organizational assignment
Þ The system determines the contact data in the following way:
º The system reads office and telephone data from infotype Internal Data (0032)
º The system reads infotype Communication (0105)
º The system reads the e-mail address (subtype 0010)
º If the Internal Data (0032) infotype does not contain a telephone number, the system reads
the telephone number from subtype 0020.
º If the system cannot find any data when reading the infotypes and subtypes, it reads user
data.
Þ The system reads the remaining data from the Organizational Assignment (0001) and Basic
Pay (0008) infotypes.

© SAP AG HR260 3-100
© SAP AG 2006
Employee Review: Organizational Assignments iView
Þ Organizational Assignments
¤ This iViewshows managers the organizational assignments for
employees in their area of responsibility. Managers get an
overview of the past organizational assignments of their employees and can
use this information to gain an overview of the career development of
employees in their company. Managers
can personalize the period for which they display organizational
assignments. The data displayed is
based on mySAP ERP data from Organizational Management.



Þ The system displays the position history in a list together with staff assignment period and
staff assignment percentage, if required. For each of the positions, the system displays the
corresponding jobs and organizational units together with the relationship period
(Relationships infotype (1001)).
Þ The system displays, for each organizational unit, the last manager responsible in the
relationship period together with his or her e-mail address, telephone number, and room
number.
Þ The system only displays this data and the relevant indicator, if the data is stored in the
system. If no job is created for the position, the J ob indicator is not displayed at all.

© SAP AG HR260 3-101
© SAP AG 2006
Employee Review: Absence Days iView
Þ Absence Days
¤ This iViewshows managers the absence data during a given period
for employees in their area of responsibility.
The manager can personalize the display. The system reads the
mySAP ERP Time Management data from the Absences (2001) infotype.



Þ Features:
º The system displays the data as a table of intervals, or as a calendar. You can browse
through the calendar. The table entries are in the form of links that the manager can use to
call the intervals in the calendar view directly.
If managers only want to display certain absence types in the current list, they can filter the
list. If you only want to deliver certain absence types from mySAP ERP, use the
enhancement HRWPCABS (see Optional Settings). This enhancement enables you, for
example, to display only absence types related to leave. Using an ID, this absence type is
included in the iView parameters as a customer-defined absence type (ABSENCE_TYPE).
You can use the iView more than once, to display different, self-defined absence types
(leave, sickness, and so on).
º You can use the optional settings for the Absence Days iView, as part of the SAP
enhancement HRWPCABS, to determine whether only a particular absence type is
displayed.

© SAP AG HR260 3-102
© SAP AG 2006
Employee Review: Monitoring of Tasks iView
Þ Monitoring of Tasks
¤ You can use this iViewto display data for selected employees
from infotype Monitoring of Tasks (0019). You can display the
following data: Status, date, reminder, task.



Þ I ntegration
Þ This iView is used both in the Employee Profilepage (technical name:
com.sap.pct.hcm.eeprofile.pag) and the Task Reminder iView.
Þ The following applies to the employee profile:
º The TeamViewer iView transfers the employee's personnel number to the iView using
event handling.
º The tabular display of an employee's task types corresponds to personalization settings.
º The data selection period is displayed below the table.
Þ The following applies to the Task Reminder iView:
º The Task Reminder iView transfers the personnel number, start and end date, as well as the
selected task type.
º The iView is displayed in a separate window.
º The selected tasks are displayed in a table.
º The employee's name is displayed above the table.
º The Closepushbutton for the window is located below the table.
Þ In addition to the general prerequisites for the system, you need the mySAP ERP component
Personnel Administration to use the Monitoring of Tasks iView.

© SAP AG HR260 3-103
© SAP AG 2006
Employee Review: Company Properties iView
Þ Company Properties
¤ This iViewshows managers possessions of employees in their
area of responsibility. The system reads the data from the Company
Properties (0040) infotype. The system displays the data as a tabular
overview for the current time. In a text area below the table, the system
displays three lines of a note relating to an object, that the manager
selects in the table. If company property is related to a cost center,
the system also displays the cost center in the table.




© SAP AG HR260 3-104
© SAP AG 2006
Employee Review: Archived Documents iView
Þ Archived Documents
¤ This iViewdisplays all of the documents stored for an employee or
applicant in SAP ArchiveLink.
¤ With Release 4.5 of SAP R/3, the log for archiving SAP documents
was converted from RFC to HTTP.



Þ For the Archived Documents iView, the interface of your archive system must have an HTTP
4.5 certification.

© SAP AG HR260 3-105
© SAP AG 2006
Employee Review: Photo iView
Þ Photo
¤ This iViewshows the photo(s) that are stored in the mySAP ERP component
ArchiveLink for employees and applicants in the manager’s area of
responsibility.



Þ For the iView Photo, the interface of your archive system must have an HTTP 4.5
certification.

© SAP AG HR260 3-106
© SAP AG 2006
Employee Review: Personal Data iView
Þ Personal Data
¤ You can use this iViewto display personal data for employees assigned
to a manager's area of responsibility. The following
data is displayed: Date of birth, marital status and private address.
The system reads this data from the Personal Data (0002) and
Addresses (0006) infotypes.



Þ The addresses in the Personal Data iView are formatted in the function module
HR_MAKE_ADDRESS.

© SAP AG HR260 3-107
© SAP AG 2006
Þ Emergency Contact
¤ This iViewdisplays the emergency contact (address and/or telephone number)
for the selected employee.
The emergency contact data originates
from the Addresses (0006) infotype.
The subtype Address Type is
evaluated for this purpose. You can
either specify this directly using
the property ADDRESSTYPE
or indirectly using the
characteristics RCLAS and
VARKY (see below). The latter are used
to evaluate feature
ADDRS (Set Subtype Sequence for
Address Formatting).
Employee Review: Emergency Contact iView



Þ In addition to the general prerequisites for the Emergency Contact iView, you must use the
mySAP ERP component Personnel Administration. If you want to implement version 4.5B as
an R/3 back-end system, you also need Support Package 04 for PI 2003.1. For more
information, see SAP Note 647048.

© SAP AG HR260 3-108
© SAP AG 2006
Þ Compensation Adjustments
¤ This iViewshows managers the compensation adjustments from the
Compensation History infotype (0380) during a particular period, for
the employees in their area of responsibility. Managers can change
the period to suit their requirements.
Employee Review: Compensation Adjustments
iView



Þ The iView shows the data for each compensation adjustment as a tabular overview: Effective
date (EFFDA), adjustment reason (CPROC), adjustment type (CPLAN), status of
compensation adjustment (CSTAT), calculation base for compensation adjustment (BSSAL),
total of adjustment amounts (total of all wage types), currency, overall adjustment percentage.
Þ The Compensation Adjustments iView must fulfill the following prerequisites: You must
implement the mySAP ERP component Compensation Management, and the Compensation
History (0380) infotype for employees in a managers area of responsibility must be
maintained.

© SAP AG HR260 3-109
© SAP AG 2006
Þ Exercising Employee Options
¤ This iViewshows managers the exercising employee options
from the Exercising Employee Options (0382) infotype for each employee in
their area of responsibility for a specific period.
Employee Review: Exercising Employee Options
iView



Þ The following additional settings are required for the Exercising Employee Options iView: As
with the Compensation Adjustments iView, you must implement the mySAP ERP component
Compensation Management. Additionally, the Exercising Employee Options infotype (0382)
must be maintained for the employees in the manager's area of responsibility.

© SAP AG HR260 3-110
© SAP AG 2006
Employee Review: Salary Development iView
Þ Salary Development
¤ Managers can use this iViewto display salary development data for
employees in their area of responsibility. The
data is displayed for a specified period, for example, clustered
annual values for salaries, bonus payments, and so on.



Þ The iView can determine annual values based on payroll results or based on the infotypes
Basic Pay (0008), Recurring Payments and Deductions (0014), and Additional Payment
(0015). The data is displayed in the iView in tabular form. In addition, users can choose the
property DisplayChart (see above) to display a diagram.
Þ In addition to the general prerequisites, one of the following SAP R/3 system prerequisites
must be fulfilled for the salary iView:
º SAP R/3 Release 45B + HR Support Package 82 or higher
º SAP R/3 Release 46B + HR Support Package 64 or higher
º SAP R/3 Release 46C + HR Support Package 55 or higher
º SAP R/3 Release 470 + HR Support Package 01 or higher
Additionally, you must have defined which annual values you want to display and the wage
types to evaluate. Make these settings in the Implementation Guide (IMG) for the Business
Package for Manager Self-Service(transaction SIMG_SPORT), under Manager Self-Service >
Employee Review >Define Wage Types for Annual Salary.
Þ Optionally, you can use the enhancement HRWPCEP1 under Manager Self-Service ->
Employee Review -> Modify Periods for Annual Salary, to modify the periods used to
determine the annual salary to suit customer requirements.

© SAP AG HR260 3-111
© SAP AG 2006
Employee Review: Customizing I
Customizing points for the
Employee Review workset



Þ Here you can see the three Customizing points for the Employee Review workset:
º Define wage types for annual salary
º Modify periods for annual salary
º Filter absence records

© SAP AG HR260 3-112
© SAP AG 2006
Employee Review: Customizing II
View: V_596A_B
Parameter in iView



Þ In this IMG activity, you can define wage types for salaries and bonuses, and so on. The
system uses these to determine the annual salary and displays the annual values determined for
the wage types in the Employee Review workset, in the Salary Development
(com.sap.pct.hcm.salaryhistory.ivu) iView.
Þ The iView can determine annual values for payroll results or for the infotypes Basic Pay
(0008), Recurring Payments and Deductions (0014), and Additional Payment (0015). In either
case, you must perform this IMG activity.
Þ When creating wage types, we recommend you use subapplication MSSH because the
technical key of the subapplication must be stored as the value of the PCD parameter Wage
Type Application fromVC_596A_C (Salary Application) for the Salary Development
(com.sap.pct.hcm.salaryhistory.ivu) iView in portal administration (content administration).
The value MSSH is stored in the standard delivery of the Business Package for Manager Self-
Service. This means that when you use this technical key, you no longer need to process the
PCD parameter.

© SAP AG HR260 3-113
© SAP AG 2006
Employee Review: Customizing III
View: V_596G_A
View: V_596I_A



Þ 1. Create a subapplication (for example, MSSH).
Þ 2. For this subapplication, define the cumulation wage types for the system to display in the
Salary Development iView (for example, the technical key 1SAL and the cumulation wage-
type text salary, and the technical key 2BON and the cumulation wage-type text Bonus).
Þ Note that the system displays the cumulated wage types sorted according to your technical
keys.
Þ 3. For each cumulation wage type, define the relevant wage types.
Þ Note
Þ If you want the system to determine the annual salary based on the infotypes Basic Pay
(0008), Recurring Payments and Deductions (0014), and Additional Payments (0015) as
opposed to payroll results, you must use a wage type in this process step that refers to a
module in view V_T511 (Wage Type Characteristics). You must have defined this module in
view V_T539J (Basic Wage Type Valuation).

© SAP AG HR260 3-114
© SAP AG 2006
Employee Review: Customizing IV
SAP enhancement for employee profile



Þ Modify periods for annual salary
º In this IMG activity, you can use the enhancement HRWPCEP1 (SAP Enhancement for
Employee Profile) to modify the periods used to determine the annual salary on a
customer-specific basis.
º When determining the annual salary in the Salary Development iView in the Employee
Review workset, the system includes the periods to be used.
º You can use a Function Exit to modify the standard SAP procedure.
º To use this function exit, proceed as follows:
- Create an enhancement project and assign the enhancement HRWPCEP1 to it.
- The only component of HRWPCEP1 is function exit
EXI T_SAPLHRWPC_EXI TS_001. Adapt this function exit to suit your requirements.
Þ Filter absence records
º In this IMG activity, you can use enhancement HRWPCABS (Filtering Absence Records)
to control whether the system only displays certain absence records for a particular type of
absence in the Employee Review workset.
º The only component is function module exit EXI T_SAPLHRWPC_ABSENCES_001.

© SAP AG HR260 3-115
© SAP AG 2006
Employee Review: Compensation Adjustments
iView
Þ Compensation Adjustments (ECM)
¤ This iViewshows managers the compensation adjustments from
infotype 0759 (Compensation Process) during a particular period
for employees in their area of responsibility .
Managers can change the period to suit their requirements.



Þ For the iViews Compensation Adjustments (ECM), Long-TermIncentives and Salary Data
(ECM), you must use the mySAP ERP component Enterprise Compensation Management
(ECM).

© SAP AG HR260 3-116
© SAP AG 2006
Employee Review: Long-Term Incentives iView
Þ Long-Term Incentives
¤ This iViewshows managers the long-term incentives (LTI) from
infotypes 0761 (LTI Granting) and 0762 (LTI Exercising) for each
employee in their area of responsibility during a particular period.
Managers can change the period to suit their requirements.




© SAP AG HR260 3-117
© SAP AG 2006
Employee Review: Salary Data (ECM) iView
Þ Salary Data (ECM)
¤ In this iView, managers can display the current salary of all of their
employees in comparison to the internal specifications for their
salary group, reference salary and percentage position in the
salary range. The data comparison is displayed graphically
so that managers can tell at a glance whether an employee's
salary is above or below the reference salary.




© SAP AG HR260 3-118
© SAP AG 2006
Employee Review: Salary Survey Results (ECM) iView
Þ Salary Survey Results (ECM)
¤ This iViewdisplays external data and results from salary surveys from
infotype 1271 (Combined Result). The iViewdisplays data
for the following areas:
º Employee salary data
º J ob/position survey data
º A graphical comparison of survey data with the current employee
salary
The administrator can set up which percentile is displayed for the salary
and results data, and which average values are displayed (see
Characteristics). The administrator can also specify whether
the percentage and the absolute difference between the survey resuts
and the employee salary is displayed.



Þ For the Salary Survey Results (ECM) iView, you must use the mySAP ERP component
Enterprise Compensation Management (ECM).

© SAP AG HR260 3-119
© SAP AG 2006
Employee Review: Appraisals iView
Þ Appraisals
¤ This iViewshows managers
appraisals for a particular period
that employees within their area
of responsibility have already
received.
The following data is
displayed for each appraisal:
Appraisal text and period,
appraiser, overall appraisal
result, appraisal scale,
status and date of creation,
list of individual appraisals.



Þ The TeamViewer iView transfers the employee's personnel number to the iView using event
handling.
Þ If you want to use the iView for appraisals, you must implement the mySAP ERP component
Personnel Development.

© SAP AG HR260 3-120
© SAP AG 2006
Þ Business events
¤ This iViewshows managers business events that have been booked or
attended within a given period by employees in their area of responsibility.
The following data can be provided for each business event; Name
of business event, period, fees and status (booked, cancelled,
attended). Managers can call a detailed view using the links saved in the
name of the business event.
Employee Review: Business Events iView



Þ The TeamViewer iView transfers the employee's personnel number to the iView using event
handling.
Þ If you also implement the Business Event Details iView, the manager can display detailed
information about business events.

© SAP AG HR260 3-121
© SAP AG 2006
Þ Business Event Details
¤ This iViewdisplays detailed information about the following
object types:
Business event, business event type, development plan. The following data is
given for the object types Business Event and Business Event Type:
Description, prerequisites, determined qualifications, target groups.
Employee Review: Details of Business Events
iView



Þ For the object type Development Plan, the system displays the description and selected data
from the development plan in tabular form.
Þ Managers can call this iView from the Profile Matchup and Business Events iViews.

© SAP AG HR260 3-122
© SAP AG 2006
Þ Qualifications
¤ This iViewshows superiors the qualifications and the respective proficiency
of employees in their area of responsibility.
Employee Review: iView Qualifications




© SAP AG HR260 3-123
© SAP AG 2006
Þ Employee Documents
¤ This iViewallows managers to manage documents for all their employees
in Content Management, that only they can access.
Employee Review: Employee Documents iView



Þ Master iView EmployeeDocumentsDispatcher comprises two additional master iViews that
are called automatically: EmployeeDocumentsHeader and EmployeeDocuments.
EmployeeDocumentsHeader only includes the heading and is always the same size.
EmployeeDocuments however, includes the actual documents and its size therefore depends
on the number of folders and documents. Therefore, it is recommended to limit the size of this
document iView.
You can restrict the size of the parameter HEIGHTPERCENTAGE in the Java iView
com.sap.pct.hcm.employeedocuments. The system administrator specifies the percentage share
of the documents iView in relation to the overall height of the Java iView. Specifying 80% for
a fixed height of a Java iView with 500 pixels has the most optimal results.
Þ To use the iView Employee Documents, in addition to the general system settings, the
following prerequisites must be met: Content Management must be intergated in the SAP
Enterprise Portal; SAP Note 640634.
Þ Managers can also personalize the folder structure. They can enter various paths that start in
the root folder. The different paths must be separated by commas.
Example: Notes,Notes/Work,Documents,Documents/Design,Miscellaneous
Þ The system administrator determines the root path that is used within Own Documents,
whereas the manager can personalize the higher-level file structure. This file structure is then
automatically generated for each employee.

© SAP AG HR260 3-124
© SAP AG 2006
Þ Appraisal Overview
¤ This iViewgives managers an overview of appraisals they need to
process. The iViewdisplays both new appraisals that need to be
processed and appraisals that are already in process.
Employee Review: Appraisals Overview iView



Þ The manager can use the following selection criteria to limit which appraisals are displayed:
º View (view ID)
º Appraisal template used
º Appraisal period
º Appraisal status
º Filter according to subordinate managers
Þ Managers can create and edit appraisals directly from the overview screen (by going to the
Edit Appraisals iView). Furthermore, managers can also display information on employees
and their superiors (Employee Profile page), on employees' positions (Position Profile page),
as well as previous employee appraisals. Managers can store additional documents on
employees by changing to the Employee Documents iView.
Þ You can only use the Appraisals Overview iView if you have made the settings for the Object
and Data Provider.

© SAP AG HR260 3-125
© SAP AG 2006
Þ Edit Appraisals
¤ Managers can use this iViewto create appraisals for employees in their
area of responsibility and display an overview of all appraisals that
still need to be edited, that is, appraisals that do not yet have a completed
status.
Employee Review: Editing Appraisals iView



Þ The functions of the iView correspond to the transactions for creating and editing appraisals in
the mySAP ERP component Personnel Development.
Þ Managers can edit appraisals by switching to the Appraisal Templates iView (technical name:
com.sap.pct.hcm.editappraisalformular.par[.tpl]). This iView includes the appraisal template
defined in mySAP ERP Customizing for the Human Resources department. It is not necessary
or possible to make any additional settings for this iView, which is only called indirectly.
Þ To use the Edit Appraisals iView, the following prerequisites must be met:
You must first import the following support packages into your HR System:
º 46B: HR R/3 Support Package 39, R/3 Support Package 32
º 46B: HR R/3 Support Package 33, R/3 Support Package 23
You must create the corresponding appraisal model (transaction OOAM) in mySAP ERP
Customizing. For more information, see the Implementation Guide (IMG) for the mySAP
ERP Personnel Development component, under Appraisal Systems >Edit Appraisals
Catalog.

© SAP AG HR260 3-126
© SAP AG 2006
Employee Review: Profile Matchup iView
Þ Profile Matchup
¤ This iViewshows managers the profile matchup between the
qualifications that an employee in their area of responsibility has,
and the qualifications required for their position.



Þ The system compares the qualifications currently held by the employee with the requirements
stored for the position. If the system detects qualification deficits, it proposes business events
that can provide the missing qualifications. The system displays the proposed business events
in a list. The manager can click on a business event in the list and display information about it
in a separate window. The functions of the iView correspond to those of the mySAP ERP
transaction for the profile matchup in Personnel Development.
Þ To use the Profile Matchup iView, you must also implement the mySAP ERP Personnel
Development and Training and Event Management components and have entered the
following data in mySAP ERP:
º Qualifications of the employee
º Requirements of the position
º Business events
Optional: You can specify that the system considers the depreciation meters of the employee's
qualifications by selecting the user parameter PEH = X. Additionally, by selecting user
parameter PES = X, you can specify that alternative qualifications are searched for if the
employee does not have the required qualifications.

© SAP AG HR260 3-127
© SAP AG 2006
Þ Status Overview
¤ In this iViewfor the status overview of Objective Setting and
Appraisals, managers can display the degree of processing of
documents for a particular form within a particular period.
Employee Review: Status Overview iView



Þ To use the Status Overview iView, the following prerequisites must be met: To evaluate,
create or edit the appropriate appraisals, at least one defined appraisal template must be
released in the mySAP ERP system. You define appraisal forms in the Implementation Guide
(IMG) for the Personal Development component, under Objective Setting and Appraisals >
Edit Template.
All nine status columns must be defined in the properties of the iView (see SAP Note
497777). The view groups of the Object and Data Provider determine the number of objects
and columns:
º View Group: HAP_STATUS
º Column Name: HAP_STATUS_1 (…9) (Document Status) and HAP_PEROCO
(Percentage of Processed Documents)
Þ Optional Settings:
º You can specify that the system considers the depreciation meters of the employee's
qualifications by selecting the user parameter PEH = X.
º You can specify that the system searches for alternative qualifications if the employee does
not have the required qualifications by selecting the user parameter PES = X.

© SAP AG HR260 3-128
© SAP AG 2006
Employee Review: Portal View



Þ Generally you cannot use all of the iViews included as standard because your company
usually only implements either mySAP Compensation Management (PA-CM) or Enterprise
Compensation Management (ECM).
Þ If you use Enterprise Compensation Management (ECM), you can use all iViews with the title
"ECM", for example Compensation Adjustments or Salary Data.

© SAP AG HR260 3-129
© SAP AG 2006
Employee Review: Conclusion
Þ Describe the content of the Employee Review
MSS workset
Þ Describe the functions of this workset
Þ Modify this workset
You should now be able to:




© SAP AG HR260 3-130

© SAP AG HR260 3-131
Exercise 1


Unit: Employee Review

I n this exercise:
• Familiarize yourself with the Employee Review workset.
• Familiarize yourself with employee review Customizing.


Log on to the Portal server and the mySAP ERP back-end system. Use
the log-on information provided.

1 Which applications are integrated with the Employee Review workset?

2 You are preparing a feedback meeting with one of your subordinate employees.
Where can you find the necessary information?

3 Update the appraisal of one of your employees and change from grade 2 to the
highest level available.

4 Why are the iViews of the Employee Review workset also useful for other
processes?



© SAP AG HR260 3-132

© SAP AG HR260 3-133
Solutions 1


Unit: Employee Review


1 Which applications are integrated with the Employee Review workset?
Organizational Management, Time Management, Training and Event Management,
Enterprise Compensation Management, Compensation, Objective Setting and
Appraisals, Personnel Development, Personnel Administration.

2 You are preparing a feedback meeting with one of your subordinate employees.
Where can you find the necessary information?
Click on the Employee Review tab page in the top-level navigation of the portal.
The information concerning the general data is in the middle of the page. Select
Compensation from the detailed navigation.

3 Update the appraisal of one of your employees and change from grade 2 to the
highest level available.
Click on the Employee Review tab page in the top-level navigation of the Portal.
The information concerning the general data is in the middle of the page. Select
Edit Appraisals from the Detailed Navigation iView.

4 Why are the iViews of the Employee Review workset also useful for other
processes?
The General Information iViews can be used in many other processes.



© SAP AG HR260 3-134

© SAP AG HR260 3-135
ReportinExercises 2


Unit: Employee Review
Topic: Generic iView List

At the conclusion of this exercise, you will be able to:
• List exercise objectives related to unit objectives. These can be
more specific than the unit objectives.


After careful analysis of the workset employee review, the
implementation team decides to add more information to the page
„Employee profile“. You want to implement communication data
which are based on the infoset query MSS_IT0105. This infoset
delivers the following data: Mobile phone, Telefax, eMail, Pager,
Systemusername, Telephone and Phone extension.

1-1 Before applying your infoset query it is necessary to create a customer specific
java iView which is based on the appropriate master iView for generic lists.

1-2 Define the properties of the customer specific java iView. You will be using the
global workarea (G), the user group /SAPQUERY/MS and the query named
MSS_IT0105.

1-3 Define specific properties for the list that will be used in the iView. The list
should contain just 1 column and should be filled from top to bottom. No
grouping needs to be defined. A fixed height of 250 pixels needs to be defined.

1-4 Apply your iView to the content of the portal page “Employee Profile”.

1-5 Log on to the portal as manager, go to the workset “Employee Review” and check
on the page “Employee Profile”, if communication data of your selected
employed are displayed in your customer specific iView.

1-6 OPTIONAL EXERCISE:
You want to change the alignment/ appearance of the communication data in your
customer specific iView. You would like to display the data in 4 columns, each
column containing 2 rows of information.

© SAP AG HR260 3-136


© SAP AG HR260 3-137

© SAP AG HR260 3-138
Solutions 2


Unit: Employee Review
Topic: Generic iView List


1 Log on to the portal as an administrator. (Use the logon data your instructor gives
you.)
Go to the Content Administration tab and choose Portal Content.
In the detailed navigation area, you need to use the Browse tab.
Choose the class_HR260 folder.
Right-click and choose New fromarchive ¬ iView.
The iView data (templates) are displayed in a list. In this list, choose the master
iView com.sap.pct.hcm.eeprofilegenericiviewlist.
At the bottom of this selection screen, choose Next.
Choose the Default option for the Portal Component Selection and then choose
Next.
In this step, you need to maintain the general properties of the iView. Enter the
following data:
iView Name: HR260_XX_Communication (XX = group number)
iView ID: HR260XX (XX = group number)
iView ID Prefix: com.sap.HR260XX (XX = group number)
Choose Save as iView.
If you wish, you can enter a description.
Choose Next.
On the Overview page, you can check your data, mark the checkbox Open for
editing when wizard completes and then choose Finish.


© SAP AG HR260 3-139
2 When you create the iView, you must define specific properties accordingly, so
that the query is called. To edit the properties, first select Show All from the
dropdown list. All of the properties of your iView are then listed on the screen.
a) If the query is to deliver data from the past or future, you require “Reporting
in Past (in years)” (PROP_YearsPast) or “Reporting in Future (in years)”
(PROP_YearsFuture) to be able to set up a time span in years.
(*Note for other activities: If iViews are displayed in a list, the query only
returns the first data record it finds. This may not necessarily be the relevant
data record.)
Enter the value 0 for both properties.
b) To identify the query on which the iView is based, you need to maintain the
following properties:
Query work area (PROP_Workarea): G
Query user group (PROP_Usergroup): /SAPQUERY/MS
Query name (PROP_Queryname): MSS_IT0105
In the Isolation Method parameter, enter the value “URL”.

3 Note: After you maintain one property, we recommend that you save the data in
order to prevent a loss of data. After you save the data, choose Refresh and then
choose Show All in the dropdown list. You can then continue to enter data.
a) Number of Columns (PROP_NumberOfColumns)
specifies the number of main columns displayed in the iView.
Enter 1.
b) Fixed Height (Pixels): 250
Save your data. Then close the edit screen for this iView.
You have created a customer-specific list iView and defined the required
properties.

4 Note: This part of the exercise can only be completed by one user, because the
“Employee Profile” page will be locked for others if one administrator opens it
for editing.
In the Browsetab in the detailed navigation of the Portal Content, choose the
following path: Portal Content ¬ Migrated Content ¬ EP 5.0 ¬ Pages. Select
the “Employee Profile” page and right-click ¬ Edit ¬ Object. The properties of
the page appear on the right-hand side of the screen.
Select Edit Page Content from the dropdown list. The iViews from the page are
listed.
Now go back to the detailed navigation in the left-hand area of the screen and
select your customer-specific iView HR260_XX_Communication.
It is available under the following path: Portal Content ¬ Class_HR260
Right-click this object and choose Add iView to Page ¬ Delta Link.
Your iView is now added to the list of iViews on the “Employee Profile” page.
Now save the data on the “Employee profile” page and refresh the data.

© SAP AG HR260 3-140


© SAP AG HR260 3-141
5 Log on to the portal as a manager. Go to the “Employee Review” workset and
select the “Employee Profile” page in the detailed navigation. Check whether
your customer-specific iView appears on the screen.

6 OPTIONAL EXERCISE:
Change the following properties of your customer-specific iView to see how the
data displayed in the portal changes. Log on as a portal administrator. In the
Portal Content Directory, choose the iView that you created in the previous
exercises. Choose Edit ¬ Object and maintain the following data:
¬ PROP_NumberOfColumns: 4
¬ PROP_Groupings: 2,2,2,2
Save your entries. Go back to the portal application as a manager and refresh your
customer-specific iView. Check how the data displayed in your iView has
changed.


© SAP AG HR260 4-142
© SAP AG 2006
The Compensation Workset: Overview Diagram
Unit 1 MSS Overview
Unit 2 Manager Self-Service Fundamentals in the Enterprise Portal
Unit 3 The Employee Review Workset
Unit 4 The Compensation Workset
Unit 5 The ESS Workset in MSS
Unit 6 The Team Calendar Workset
Unit 7 The Personnel Change Requests (PCR) Workset
Unit 8 The Recruitment Workset
Unit 9 The Reporting Workset
Unit 10 The Headcount Workset
Unit 11 Team Viewer
Appendix Homepage Framework




© SAP AG HR260 4-143
© SAP AG 2006
Compensation
Þ Compensation planning
Þ Using Team Viewer in the Compensation workset
Þ mySAP ERP compared with Web compensation planning
Contents:




© SAP AG HR260 4-144
© SAP AG 2006
Compensation: Aims
Þ Describe the compensati on planning
process
Þ Describe the use of the Team Vi ewer in
the Compensation Workset
Þ Compare the mySAP ERP functions and
the Web compensation planning
After completing this unit, you will be able to:




© SAP AG HR260 4-145
© SAP AG 2006
Compensation: Scenario
Þ The Web activation of mySAP ERP processes for
managers represents a key function of MSS. You must
decide six months before the start of your
compensation planning process whether you want to
use the MSS functions or the mySAP ERP functions.




© SAP AG HR260 4-146
© SAP AG 2006
Overview



Þ Compensation planning supports managers with planning compensation adjustments, for
example planning the annual salary.
Þ The Compensation workset is a good example of the Web enabling of mySAP ERP
transactions using MSS.
Þ Additional functions, such as graphical comparison or survey results, are available.
Þ The MSS functions are available for mySAP ERP releases >= 4.6C.

© SAP AG HR260 4-147
© SAP AG 2006
iViews for Compensation Planning



Þ You can use the Compensation workset to:
º choose the type of planning to be performed, and the organizational units for which you
want to perform planning
º display a tabular overview of employees and their planning-relevant data
º display an overview of all relevant compensation adjustment types
º apply company-specific guidelines for a few selected employees
º apply a percentage change for multiple selected employees
º enter direct and employee-specific change amounts, change percentages and effective dates
for planning
º display a graphical summary of planning for an employee
º display a graphical comparison of the adjustments for several employees
º change the display currency
º trace the action status
º monitor budgets
º submit compensation planning

© SAP AG HR260 4-148
© SAP AG 2006
Compensation Planning – Functions I



Þ You use this iView if you need to select planning.
Þ You can use the Personalization iView to predefine the compensation parameter.
º Adjustment reason – CPROC
º Planning period – CYEAR
Þ If both parameters are predefined, you can skip the selection.

© SAP AG HR260 4-149
© SAP AG 2006
Compensation Planning – Functions II



Þ This iView is based on the evaluation paths in the Object and Data Provider.
Þ If the parameter SKIPORGUNIT = trueis set in the iView personalization, you cannot choose
organizational units.

© SAP AG HR260 4-150
© SAP AG 2006
Compensation Planning – Functions III



Þ Managers use this iView to perform salary planning for employees assigned to their
organizational unit. Managers can display the actual planning data in addition to the employee
data that is relevant for planning.

© SAP AG HR260 4-151
© SAP AG 2006
Additional Information on a Portal Page



Þ In addition to the employee data displayed in the actual planning table, there are other iViews
that support managers in the planning process. You can make them available on an employee-
specific portal page via the employee name.
Þ This portal page can contain as many iViews as you want that display employee data. The
iViews that can be included on this page must fulfill the technical prerequisite to be able to
determine the selected employees using the MSS eventing model. All iViews from the
Employee Profileworkset and the Compensation Planning workset fulfill this prerequisite.
Þ In particular, three additional iViews from the Compensation Planning workset
(Compensation Guidelines, Compensation Eligibility and Salary Survey Data) should be on
this page. Additional enhancements could also include the individual iViews from the
Employee Profileworkset.
Þ We provide the portal page com.sap.pct.hcm.compensationinfo as an example. It includes the
following iViews:
º Compensation Eligibility (WCPEligibility)
º Salary Survey Results (WCPSurvey)
º Compensation Guidelines (WCPGuidelines)
º General personal data (EEProfileGeneralData)
º Photo (EEProfilePhoto)

© SAP AG HR260 4-152
© SAP AG 2006
Possible Pushbuttons



Þ Four iView properties are available, which you can use to influence which pushbuttons should
be displayed for each compensation category. For this, six different parameters are available.
Þ ACTI ONS…
Þ These properties determine which actions in the individual views (tabstrips) are available for a
compensation plan according to the plan category. When you enter the action ID in one of the
action properties (ACTI ON_SAL, ACTI ONS_BONREG, ACTI ONS_BONOFF,
ACTI ONS_LTI ), the action is added to the view for the relevant plans. The actions have the
following IDs:
º GDL – Use guidelines
º PCT – Use percentage
º CLR – Delete entries
º MI N – Increase to minimum in salary range
º CMP – Graphical comparison
º CUR – Currency change


© SAP AG HR260 4-153
© SAP AG 2006
Pushbutton Control



Þ Not all actions are available for all plan categories. The allowed actions that are available for
the various plan categories are:
º Salary Adjustment (ACTIONS_SAL) - GDL, PCT, CLR, MIN, CMP, CUR
º Regular Bonus (ACTIONS_BONREG) - GDL, PCT, CLR, CMP, CUR
º Off-cycle Bonus (ACTIONS_BONOFF) - GDL, PCT, CLR, CMP, CUR
º LTI (ACTIONS_LTI) - GDL, CLR, CMP


© SAP AG HR260 4-154
© SAP AG 2006
Additional iView Parameters I
Salary Adjustmt.
Plans
Off-Cycle
Bonus Plans
LTI Plans
Regular Bonus Plans



Þ VI EWI D, NAVTYPE: These properties determine which Object and Data Provider you
want to use. The view determines in which way the system should determine employees and
which columns are contained in the planning table. The view defined for the VI EWI DSAL
property is always used to determine employees.
Þ However, you can set up column configuration differently for each compensation plan. The
column group of the individual view is used, that is, the 'salary adjustment plan' view defined
for the VI EWI DSAL property, the 'regular bonus plan' view defined for the
VI EWI DBONREG property, the 'off-cycle bonus plan' view (US-specific) defined for the
VI EWI DBONOFF property, and the 'LTI plan' view defined for the VI EWI DLTI property.
In addition, you can also select a specific view for individual plans. To do this, you enter the
relevant plan key and view in the VI EWI DADD property in the following format:
Þ <Plan1>=<ViewId1>,<Plan2>=<ViewId2>, and so on
Þ Example:
Þ The ECMSAL view is to be used for the MRTA plan and the ECMBON view is to be used for
the BONU plan. In this case, the entry for VIEWIDADD must be as follows:
Þ MRTA=ECMSAL,BONU=ECMBON


© SAP AG HR260 4-155
© SAP AG 2006
Additional iView Parameters II
Þ WaitingScreen
Þ CREVI
Þ SKIPOBJECTSELECTION
Þ CURRENCY
Þ SkipReviewPage
Þ Rows
Þ ShowBudgetTotals
Þ InitialSortingColumn
Þ RefreshAl lColumns



Þ WaitingScreen: This property defines whether an intermediate screen is displayed for actions
that may be time-consuming. The intermediate screen requests the user to wait until the step
has been completed, to prevent the user from making additional entries in the meantime.
Otherwise, some inconsistencies would arise.
Þ CREVI , SKI POBJ ECTSELECTI ON: These properties determine the behavior of the initial
screen of the iView. Normally, that is, if neither of these two properties have been predefined,
users must first specify the compensation review to be approved and then select the
organizational units for which he or she wants to approve the compensation review.
Þ If you only predefine the CREVI (Compensation Review) property for the scenario, the user
can no longer select the compensation review when he or she accesses the scenario. That is,
the selection is switched to inactive.
Þ If you only set the SKIPOBJECTSELECTION property to true, the user can no longer select
the organizational units. That is, the selection is switched to inactive. The system
automatically selects all organizational units delivered by the evaluation path.
Þ If you predefine the CREVI property and set the SKIPOBJECTSELECTION property to true,
the user arrives directly at the planning view of the iView.
Þ …

© SAP AG HR260 4-156
Þ …
Þ CURRENCY
Þ The user can display all of the planning data in one currency or in employee-specific
currencies (depending on the country grouping of the employee). All currencies from the
budget or compensation adjustments are available to the user. If you require additional
currencies, you can define the appropriate technical key from the SAP R/3 system (for
example, EUR, USD) in the CURRENCY property. However, you must ensure that the
currencies exist in the SAP R/3 system and that it is possible to convert them to the other
relevant currencies here. The currencies are then also available to the user.
Þ SkipReviewPage: This property dictates whether the review screen is displayed before the
compensation plan is approved or rejected. The review screen allows you to check all data that
is to be approved or rejected in the subsequent step. If the property has the value true, the
review page is displayed. If the property has the value false, the review page is not displayed.
Þ Rows
Þ This property dictates the number of lines displayed in the planning table.
Þ ShowBudgetTotals
Þ This property determines whether the budget table includes a line that displays the total of all
budgets.
Þ I nitialSortingColumn: This property determines which table column is used to sort
employees at the start of the compensation scenario. Here you can enter the technical name of
the table column you would like to use. By default, the characteristic has the value
CP_NAME. Therefore, the list of employees is initially sorted according to their names, in the
format <Last Name, First Name>.
Þ RefreshAllColumns
Þ If you want to display dynamic table data in your compensation scenario, that is, data that
depends on the current planning data, you must set this property to true . The column contents
are then updated in SAP R/3 after each user action.

© SAP AG HR260 4-157
© SAP AG 2006
Workset and mySAP ERP Functions Compared I



Þ The Web scenario has some restrictions:
º You can only use one adjustment amount and adjustment percentage.
º Rounding rules are always applied automatically.
º You can only change the currency for display purposes.

© SAP AG HR260 4-158
© SAP AG 2006
Workset and mySAP ERP Functions Compared II




© SAP AG HR260 4-159
© SAP AG 2006
Use Process Parameters I



Þ mySAP ERP System
º If you want to perform compensation planning in the mySAP ERP system, the following
three parameters are essential:
º Compensation Planning Period: This parameter defines the period in which the
compensation adjustments are planned and in which they can become effective.
º Compensation Adjustment Reason: The settings for this parameter represent the
compensation program of your company (for example, annual salary review). They have a
time unit as a basis for planning, and incorporate one or more compensation adjustment
types, that is, different types of monetary compensation that employees can receive in your
company (such as salary, bonus).
º Compensation Adjustment Type: The settings for this parameter represent the different
types of monetary compensation.
º You can only plan compensation adjustments if you have chosen the process parameters
mentioned above in the application.

© SAP AG HR260 4-160
© SAP AG 2006
Use Process Parameters II
Þ Web Compensation Planning:
¤ Managers must manually choose parameters.
¤ You can predefine parameters (planning period, adjustment reason).



Þ Web Scenario
º In the Web application you can start compensation planning in two different ways:
º Your managers select the process parameters manually in the application, in the same way
as in the mySAP ERP standard system.
º You use the PCD parameters to predefine the compensation planning period and/or the
adjustment reason for your managers.
º Your managers can no longer change the parameters in the application.
º Unlike the mySAP ERP application, you always edit all of the compensation adjustment
types for a compensation adjustment reason. Therefore it is not essential to predefine the
compensation adjustment type.
º As in the mySAP ERP application, you cannot edit more than one compensation planning
period or compensation adjustment reason at the same time.

© SAP AG HR260 4-161
© SAP AG 2006
Data Lock I
Þ mySAP ERP system:
¤ From the time at which you start the actual compensation planning, the
system locks employees and budgets.



Þ mySAP ERP system
º From the time at which you start the actual compensation planning, the system locks
employees and budgets. Neither can you edit employees and budgets that the system could
not lock. The system displays a message to tell you this. If you choose Refresh, you can
also lock employees and budgets later, during planning.

© SAP AG HR260 4-162
© SAP AG 2006
Data Lock II
Þ Web Compensation Planning:
¤ The system only locks the relevant employees and budgets when the
manager saves or submits the planning data.



Þ Web Scenario
º Initially, the system does not lock any data in the Web scenario. Only when the manager
saves or submits planning data does the system lock the relevant employees and budgets
for the short period of the database change.
º This lock logic considers the fact that during compensation planning another user could
change employee data, and therefore invalidate planning. This ensures data consistency
upon saving. The system checks the current data in the database once again when you save.
º If the system cannot save planned data, it informs the manager by displaying a message.


© SAP AG HR260 4-163
© SAP AG 2006
Use Eligibility Rules I
Þ mySAP ERP system:
¤ Eligibility rules determine which compensation adjustment is permitted
for which employees in your company.



Þ mySAP ERP system
º You can use eligibility rules to specify which employees in your company are eligible for
which compensation adjustments (such as, salary adjustment, bonus payment and so on).
º Eligibility rules consist of one or more eligibility criteria.
º For example, an eligibility rule can state that an employee must have worked in the
company for at least one year, and must have at least an average appraisal in order to be
considered for a salary adjustment. Different eligibility criteria can be applicable for
different employee groupings.

© SAP AG HR260 4-164
© SAP AG 2006
Use Eligibility Rules II
Þ Web Compensation Planning:
¤ The Web scenario uses the effective date in the same way as the
mySAP ERP standard system.
¤ The eligibility rules and the corresponding results for each employee
and each adjustment type can be displayed in a separate iView.



Þ Web Scenario
º The Web scenario uses eligibility rules in the same way as the mySAP ERP application and
checks them automatically for each employee and compensation adjustment type.
º Unlike in the mySAP ERP application, in the iView you can display the eligibility rules
and their results for each employee and adjustment type (see Compensation Eligibility
iView).
º For each employee and adjustment type the system displays the texts of the eligibility
criteria, but not their value ranges.
º We recommend that you use meaningful texts for the eligibility criteria you use.

© SAP AG HR260 4-165
© SAP AG 2006
Use Calculation Base I
Þ mySAP ERP system:
¤ The calculation of percentage adjustments depends on the settings in
Compensation Management Customizing.
¤ A different calculation base can be relevant for each compensation
adjustment type.



Þ mySAP ERP system
º The system uses the calculation base as the basis for percentage compensation adjustments.
The calculation of percentage adjustments depends on the settings in Compensation
Management Customizing.
º A different calculation base can be applicable for each compensation adjustment type.
º Note that the calculation base can, but does not have to, correspond to the annual salary of
your employees.

© SAP AG HR260 4-166
© SAP AG 2006
Use Calculation Base II
Þ Web Compensation Planning:
¤ The Web scenario uses the calculation base in the same way as the
mySAP ERP standard system.



Þ Web Scenario
º The Web scenario uses the calculation base in the same way as the mySAP ERP standard
system.

© SAP AG HR260 4-167
© SAP AG 2006
Use Effective Date I
Þ mySAP ERP system:
¤ The system suggests the effective date according to the settings in
Compensation Management Customizing.
¤ Managers can overwrite the effective date for each compensation
adjustment.



Þ mySAP ERP system
º The effective date specifies the day as of which a compensation adjustment and its
activation are effective. The system suggests the effective date according to the settings in
Compensation Management Customizing.
º You can individually overwrite the effective date of each compensation adjustment in the
mySAP ERP application.

© SAP AG HR260 4-168
© SAP AG 2006
Use Effective Date II
Þ Web Compensation Planning:
¤ The Web scenario uses the effective date in the same way as the mySAP
ERP standard system.
¤ You can completely hide the effective date in the Web application by
removing the column from the column group.



Þ Web Scenario
º The Web scenario uses the effective date in the same way as the mySAP ERP standard
system.
º However, by making the appropriate settings in the Object and Data Provider you can also
completely hide the effective date in the Web application. To do this you remove the
CP_EFFDA column from the column group used.
º If, in your company, all compensation adjustments of a compensation adjustment type
become effective on a fixed date, it can be useful to hide the effective date.

© SAP AG HR260 4-169
© SAP AG 2006
Edit Compensation Adjustments I
Þ mySAP ERP system:
¤ You can plan a compensation adjustment by:
º entering an adjustment amount or percentage manually
º generating an automatic percentage adjustment
º applying (optional) enterprise-internal guidelines
¤ A compensation adjustment can consist of up to ten different amounts or
percentages (compensation wage types). Upon activating a compensation
adjustment, only the total amount is relevant.
¤ You cannot delete compensation adjustments from the database.



Þ mySAP ERP system
º In the mySAP ERP standard system, you can plan a compensation adjustment by:
- entering an adjustment amount or percentage manually (individual processing)
- generating an automatic percentage adjustment (individual or mass processing)
- applying (optional) enterprise-internal guidelines (individual or mass processing)
º A compensation adjustment can consist of up to ten different amounts or percentages
(compensation wage types). The number of these compensation wage types depends on the
settings in Compensation Management Customizing, and can be different for employees
from different compensation areas. When you activate a compensation adjustment, only the
overall amount is relevant, and not the individual adjustment amounts.
º In the mySAP ERP application you can delete compensation adjustments, regardless of
their status. The system then removes the data records from the database.

© SAP AG HR260 4-170
© SAP AG 2006
Edit Compensation Adjustments II
Þ Web Compensation Planning:
¤ For usability reasons, you can only process one adjustment
amount or percentage per compensation adjustment for the first
available compensation wage type.
¤ You cannot delete compensation adjustments from the database.
¤ However, you can set planned amounts for one or more
employees to zero.



Þ Web Scenario
º In the Web application, for usability reasons, you can only process one adjustment amount
or percentage per compensation adjustment for the first available compensation wage type.
If Compensation Management Customizing allows several compensation wage types, the
system displays a message to let you know. However, you can still continue with the
planning process. In this case, the system does not take the additional compensation wage
types into account. This ensures intuitive use of the Web scenario.
º In the Web scenario, you cannot delete compensation adjustments from the database.
However, you can set planned adjustment amounts for one or more employees to zero.
º If you have performed planning for test purposes only, and then want to begin planning
again, it can be useful to set the amounts to zero. The data records (with zero values for
amounts and percentages) remain in the database.

© SAP AG HR260 4-171
© SAP AG 2006
Data Check and Recalculation I
Þ mySAP ERP system:
¤ If you edit compensation adjustments and choose Enter, the system
checks all data on the basis of mySAP ERP Dynpro flow logic, and
recalculates it.
¤ If you perform functions such as Apply Guidelines, Percentage Increase,
or Change Currency, the system also performs the checks and
recalculation.



Þ mySAP ERP system
º If you edit compensation adjustments and choose Enter, the system checks all data on the
basis of mySAP ERP Dynpro flow logic, and recalculates it.
º If you perform functions such as Apply Guidelines, Percentage Increase, or Change
Currency, the system also performs the checks and recalculation. It performs the following
checks and recalculations in detail:
º Calculation of adjustment amounts from adjustment percentages, or the other way around
º Calculation of total increase or total percentage
º Check of guideline limits
º Calculation of total increase or total percentage
º Calculation of budget data

© SAP AG HR260 4-172
© SAP AG 2006
Data Check and Recalculation II
Þ Web Compensation Planning:
¤ Data checks are usually only performed when the user triggers a
particular event, for example, by choosing a push button.
¤ All data checks and recalculations refer to amounts in their original
currency.



Þ Web Scenario
º In Web applications, data checks are usually only performed when the user triggers a
particular event, for example, by choosing a push button. Following this approach, the
system only performs the checks and recalculation in the Web scenario when the following
functions are triggered:
- Refresh
- Apply Guidelines
- Apply Percentage
- Change Display Currency
- Save and Submit
º Note that unlike in the mySAP ERP application, all data checks and recalculations relate to
amounts in their original currency. In the Web scenario, you only change the currency for
display purposes.
º If you have saved rounding rules in Compensation Management Customizing, the Web
scenario takes them into account automatically when recalculating data.

© SAP AG HR260 4-173
© SAP AG 2006
Percentage Changes I
Þ mySAP ERP system:
¤ You can choose the employees for whom you want to perform
a percentage change.
¤ Percentage changes always affect the first compensation wage type of an
adjustment.



Þ mySAP ERP system
º You can use percentage changes to adjust compensation for multiple employees
automatically. In the mySAP ERP standard system, you can choose the employees who
you want to apply a percentage change to. Percentage changes always affect the first
compensation wage type of an adjustment.

© SAP AG HR260 4-174
© SAP AG 2006
Percentage Changes II
Þ Web Compensation Planning:
¤ This function is available in the same way as in the mySAP ERP standard
system.



Þ Web Scenario
º In the Web scenario, this function is available in the same way as in the mySAP ERP
standard system.
º Unlike the mySAP ERP standard system, the Web scenario always takes rounding rules
into account.

© SAP AG HR260 4-175
© SAP AG 2006
Use Guidelines I
Þ mySAP ERP System:
¤ You can set up guidelines for compensation management for
each compensation wage type.
¤ When checking an adjustment, each individual compensation
wage type is synchronized with these guidelines.
¤ Guideline types:
º Fixed guidelines
º Matrix-based guidelines
º User-defined guidelines



Þ mySAP ERP System
º Guidelines enable you to automatically determine and assign default values for
compensation adjustments and to check your planned adjustment amounts or percentages
automatically against specified limits.
º You can set up guidelines for compensation management for each compensation wage
type. When checking an adjustment, each individual compensation wage type is checked
against the guidelines, and not the total amount for the adjustment. Different guidelines can
be relevant for different employee groupings. There are three different types of guidelines:
- Fixed guidelines comprise solely a fixed adjustment amount or percentage. When using
a fixed guideline, each selected employee receives the same adjustment amount or
percentage. There are no minimum or maximum levels for fixed guidelines.
- Matrix-based guidelines can include a maximum of three guideline criteria (matrix
dimensions), for example, appraisal results or length of service. Based on the criteria,
the system determines a default value or percentage for each employee and uses this.
º You do not necessarily have to use the guidelines we provide. You can also create your
own guidelines to suit your requirements. Depending on the specification of the guideline
criteria (dimension segments), you can define different minimum and/or maximum levels
in Compensation Management Customizing. The system considers these guideline levels
when checking data.

© SAP AG HR260 4-176
- With user-defined guidelines, you can flexibly define how the system determines
adjustment amounts or percentages for your employees. Similar to fixed guidelines,
there are no guideline levels for monitoring planned adjustment amounts.
º In the mySAP ERP application, you can display the guideline information for individual or
multiple employees. In addition to the default value and guideline levels, this view also
contains individual relevant guideline criteria, and their value for an employee.

© SAP AG HR260 4-177
© SAP AG 2006
Use Guidelines II
Þ Web Compensation Planning:
¤ All of the previously listed guideline types are available.
¤ For usability reasons, only the first compensation wage
type per compensation adjustment is available for
editing compensation adjustments.
¤ The guideline information view only includes data for
individual employees.



Þ Web Scenario
º All of the previously mentioned guideline types are available in the Web scenario. Unlike
the mySAP ERP standard, the Web scenario always takes rounding rules into account.
Unlike the mySAP ERP standard, there are the following restrictions: As described under
"Processing Compensation Adjustments", only the first compensation wage type per
compensation adjustment is available to you for processing your employees' compensation
adjustments (only one adjustment amount and one adjustment percentage). Consequently
for the Web scenario, guidelines for additional compensation wage types are pointless.
These guidelines cannot be used and usually no guideline levels are checked. Only if the
adjustment amounts or percentages of the additional compensation wage types change, is it
necessary to check the guideline levels to guarantee data consistency. However, this is only
the case if a different calculation base arises from the change to the effective date.
º As with the mySAP ERP application, the Web scenario can also display this information.
Unlike the mySAP ERP standard system, this view only includes data for individual
employees. However, it includes all compensation adjustment types for the edited
adjustment reason.

© SAP AG HR260 4-178
© SAP AG 2006
Use Rounding Rules I
Þ mySAP ERP system:
¤ You must manually trigger the application of rounding rules.



Þ mySAP ERP system
º You can set up Compensation Management Customizing per compensation wage type
rounding rule. According to the degree of exactness for rounding that you specified,
rounding rules enable you to round adjustment amounts up or down to the nearest whole
number. In the mySAP ERP application you must trigger the rounding rules manually.

© SAP AG HR260 4-179
© SAP AG 2006
Use Rounding Rules II
Þ Web Compensation Planning:
¤ The system automatically uses rounding rules when checking and
recalculating data.
¤ In the Web scenario, the system applies the rounding rules to the
adjustment amounts in the original currency. This is also the case if the
manager has selected an alternative display currency.



Þ Web Scenario
º You can also use rounding rules in the Web scenario. For usability reasons, the system
always automatically uses the rounding rules when checking and recalculating data. In
addition to the first compensation wage type, this also applies to additional compensation
wage types insofar as the adjustment amount or percentages have changed due to a change
to the effective date.
º Unlike the mySAP ERP standard system, the system uses rounding rules in the Web
scenario for adjustment amounts in the original currency. This is also the case if the
manager has selected an alternative display currency.

© SAP AG HR260 4-180
© SAP AG 2006
Monitoring Compensation Adjustments Using
Budgets I
Þ mySAP ERP system:
¤ Budgets enable you to control the total of all compensation adjustments
for the employees of an organizational unit.
¤ Depending on the organizational assignment, different budgets with
alternative currencies can be relevant for different employees.
¤ The system checks the budgets when saving data. If you often plan up
to the limit of a budget, this avoids repeated error messages regarding
budget deficits. The system updates budget data each time data is
checked.
¤ Using a separate menu function, you can access an overview of all
budget data that is relevant for planning.



Þ mySAP ERP system
º Whereas you can use matrix guidelines, for example, to check the upper limit of an
employee's compensation adjustment amount, budgets allow you to monitor the sum of all
compensation adjustments for employees from an organizational unit. Depending on the
organizational assignment, different budgets with alternative currencies can be relevant for
different employees. In extreme cases, multiple budgets can exist for an employee within
the compensation planning period (however only one budget can exist at a given time). The
effective date for the individual compensation adjustments determines which of these
budgets is allocated for compensation planning.
º In the mySAP ERP application, the system first checks budgets when backing up data and
not each time a data check for excesses is either explicitly or implicitly triggered.
º If you often plan up to the limit of a budget this avoids repeated error messages regarding
budget deficits. The system updates budget data each time data is checked.
º In the mySAP ERP standard system, the system directly displays the relevant budget
information for the compensation adjustment being processed. Using a separate menu
function, you can access an overview of all budget data that is relevant for planning.
Þ Web Scenario
º In the Web scenario, the same functions are available as in the mySAP ERP standard
system.

© SAP AG HR260 4-181
º In the Web scenario, you also always have an overview of all planning-relevant budgets.

© SAP AG HR260 4-182
© SAP AG 2006
Monitoring Compensation Adjustments Using
Budgets II
Þ Web Compensation Planning:
¤ In the Web scenario, the same functions are available as in the mySAP
ERP standard system.
¤ Additionally, in the Web scenario you always have an overview of all
planning-relevant budgets (in an iView).



Þ mySAP ERP system
º Whereas you can use matrix guidelines, for example, to check the upper limit of an
employee's compensation adjustment amount, budgets allow you to monitor the sum of all
compensation adjustments for employees from an organizational unit. Depending on the
organizational assignment, different budgets with alternative currencies can be relevant for
different employees. In extreme cases, multiple budgets can exist for an employee within
the compensation planning period (however only one budget can exist at a given time). The
effective date for the individual compensation adjustments determines which of these
budgets is allocated for compensation planning.
º In the mySAP ERP application, the system first checks budgets when backing up data and
not each time a data check for excesses is either explicitly or implicitly triggered.
º If you often plan up to the limit of a budget this avoids repeated error messages regarding
budget deficits. The system updates budget data each time data is checked.
º In the mySAP ERP standard system, the system directly displays the relevant budget
information for the compensation adjustment being processed. Using a separate menu
function, you can access an overview of all budget data that is relevant for planning.

© SAP AG HR260 4-183
© SAP AG 2006
Currency Change I
Þ mySAP ERP system:
¤ You can perform compensation adjustments for different employees
in different currencies.
¤ If the currency changes, the system translates all amounts of a
compensation adjustment in the mySAP ERP application.
The amounts in the original currency are lost.



Þ mySAP ERP system
º In principle, you can perform compensation adjustments for different employees in
different currencies, particularly if employees are assigned to alternative country
groupings.
º In the case of a currency change, invariably associated with rounding errors, the system
translates all compensation adjustment amounts in the mySAP ERP application. The
amounts in the original currency are lost. When you save data, the system saves the
adjustment amounts in the new currency.
º You can only change the currency individually for one compensation adjustment. We do
not currently support a mass function.
º For comparability reasons the system also translates each of the corresponding budgets into
the new currency. However, they are not translated in the database.

© SAP AG HR260 4-184
© SAP AG 2006
Currency Change II
Þ Web Compensation Planning:
¤ The currency change is only for display purposes. The amounts are
saved in the original currency in the database.
¤ Within a planning session, you can only change the display currency
simultaneously for all employees.



Þ Web Scenario
º A currency translation is also possible in the Web scenario. However, the following two
basic differences exist compared to the mySAP ERP standard system:
- The currency translation is only for display purposes. The amounts in the database
retain their original currency. You can reset the display to the employee-specific
currency at any time.
- You can only change the display currency for all employees within one planning
session. In this way, all employees have adjustment amounts that you can compare.

© SAP AG HR260 4-185
© SAP AG 2006
Data Backup I
Þ mySAP ERP system:
¤ The system always saves all compensation adjustments of
planning session together.
¤ The system does not usually save adjustments to the database if all
increase amounts and percentages are zero.
¤ You cannot only save a part of the changed compensation adjustments.



Þ mySAP ERP system
º In the mySAP ERP standard system, the system always saves all compensation adjustments
from one planning session together. You cannot only save a part of the changed
compensation adjustments. The system does not usually save adjustments to the database if
all increase amounts and percentages are zero. An exception occurs if the system has
already saved these adjustments with an increase amount or percentage in the database.
º A data check for compensation adjustments is performed within the Dynpro flow logic.
The system only checks budgets when backing up data and triggers error handling if
necessary.

© SAP AG HR260 4-186
© SAP AG 2006
Data Backup II
Þ Web Compensation Planning:
¤ The system saves all compensation adjustments whose increase
amounts and percentages are zero. This procedure enables you to submit
such data records.
¤ Upon saving the data in the Web scenario, the system must check all
adjustment and budget data.
¤ Due to the special treatment of data locks in the Web scenario, the
system must perform an additional data consistency check for
compensation adjustments and budgets.



Þ Web Scenario
º In the Web scenario, the system also saves all compensation adjustments from the current
planning session together. Unlike the mySAP ERP standard system, the system also saves
all compensation adjustments for which the increase amounts and percentages are zero.
This procedure enables you to submit such data records.
º Because users may have changed data that they want to save directly without having to first
explicitly trigger the data check, the system must check all adjustment and budget data
when saving in the Web scenario.
º Due to the special treatment of data locks in the Web scenario, the system must perform an
additional data consistency check for compensation adjustments and budgets. This takes
place when saving data.

© SAP AG HR260 4-187
© SAP AG 2006
Status Changes and SAP Business Workflow I
Þ mySAP ERP system:
¤ Supported statuses:
º planned
º submitted
º approved
º rejected
º active



Þ mySAP ERP system
º In the mySAP ERP standard system, we support the following statuses for compensation
adjustments:
- planned
- submitted
- approved
- rejected
º This status corresponds to the planned status:
- active
º When you submit compensation adjustments and have set up the Approval Process for
Compensation Adjustments workflow in Customizing for Compensation Management, the
system generates a worklist and sends this to your superior. The superior receives the
worklist in their workflow inbox and can approve or reject the submitted compensation
adjustments.
º If the superior rejects the compensation adjustments, they receive the status planned once
more and you can process them again.

© SAP AG HR260 4-188
º If the superior approves the compensation adjustments, the system generates a new
worklist and sends this to the responsible administrator in the HR department, who
activates this worklist.
º For more information on the Approval Process for Compensation Adjustments workflow,
see the Implementation Guide (IMG) for Compensation Management under Planning and
Administration -> Adjustments -> Set Up Workflow Approval Process for Compensation
Adjustments.

© SAP AG HR260 4-189
© SAP AG 2006
Status Changes and SAP Business Workflow II
Þ Web Compensation Planning:
¤ supports the planning process
¤ the submission is included



Þ Web Scenario
º In the Web scenario we only support the planning process. The submission of
compensation adjustments is included. In the Web scenario, compensation adjustments
cannot (yet) be approved. This takes place using SAP Business Workflow in the mySAP
ERP standard system.

© SAP AG HR260 4-190
© SAP AG 2006
Error Handling I
Þ mySAP ERP system:
¤ An error log provides information about all errors that occurred during
the planning process.



Þ mySAP ERP system
º If errors occur during compensation planning, the system indicates this by displaying
appropriate messages. An error log provides information about all errors that occurred
during the planning process.

© SAP AG HR260 4-191
© SAP AG 2006
Error Handling II
Þ Web Compensation Planning:
¤ simplified error handling
¤ messages always directly relate to the activity last performed by the user



Þ Web Scenario
º In contrast to mySAP ERP standard system, the Web scenario demonstrates simplified
error handling. Clear, comprehensible, and concise messages help users to recognize the
cause of the error without prior knowledge, and enable them to react suitably.
º The messages displayed by the system always directly relate to the activity last performed
by the user. For usability reasons, an error log that relates to all activities cannot be
displayed

© SAP AG HR260 4-192
© SAP AG 2006
ECM Entry Screen in MSS



Þ As of SAP MSS 50.4, new functions are available that are based on the new ECM
compensation function. This new workset provides managers with functions from the
Enterprise Compensation Management (ECM) component.
Þ Prerequisites
º SAP R/3 Enterprise (4.70) HR Extension 2.0
Þ Additional functions (compared with the compensation functions available in SAP MSS):
º Integration of LTI plans
º New columns (guidelines, notes, and so on) in the planning and approval iViews
º Available column configuration (increase in benefits, LTI granting) for all plan categories
º Function for setting the minimum (set an employees salary to the minimum)
º Review Screen for checking planning data before it is submitted for approval
º Function for creating and maintaining notes in the Approve Compensation Planning (ECM)
iView

© SAP AG HR260 4-193
© SAP AG 2006
Long-Term Incentive (LTI) Granting in MSS
If necessary, you can di splay or
hide functi ons by plan.
If necessary, you can di splay or
hide functi ons by plan.
You can sort all
columns.
You can sort all
columns.




© SAP AG HR260 4-194
© SAP AG 2006
Compensation Planning Approval in MSS




© SAP AG HR260 4-195
© SAP AG 2006
Compensation: Conclusion
Þ Describe the compensati on planning process
Þ Describe the use of the Team Viewer in the
Compensation Workset
Þ Compare the mySAP ERP functions and
the Web compensation planning
You should now be able to:




© SAP AG HR260 4-196

© SAP AG HR260 4-197
Exercises


Unit: Compensation

I n this exercise:
• Familiarize yourself with the Compensation workset.
• Examine the requirements for MSS Compensation.
• Familiarize yourself with MSS Compensation Customizing.


Log on to the portal server and the mySAP ERP back-end system.
Use the logon information provided.


1 Which general options do you have in mySAP ERP Customizing (on which the
MSS Compensation workset is based)?

2 List some of the differences between the Web scenario and the mySAP ERP
scenario.

3 Create compensation planning for your employees.
3-1 For all your employees, create “infotype 0758 – Compensation Program” for
01.01. of the current year. Accept the default values.
3-2 Create compensation planning for your employees in the Enterprise Portal.
For this, use the compensation review “MSS – Compensation Review”.
Adjust the compensation as follows:
• Apply the guidelines for Jose Granados.
• Give Iffat Keitel a fixed amount of €50.00.
• Increase compensation for Seamus O’Brian by 3%.
Observe how the budget is reduced.
Which amount and percentage is displayed for the employee Jose Granados?
Amount: ________________
Percentage: ________________
Which percentage is displayed for the employee Iffat Keitel?
Percentage: ________________

© SAP AG HR260 4-198
What is the compensation adjustment for Seamus O’Brian?
Amount: ________________
Display the compensation adjustment in graphical form. Then save your
changes. Check the status of your change request. Exit your planning.
3-3 Go to the ERP system and display infotype “0759 – Compensation Process”
for the three employees.
3-3-1 Compare the status of the compensation process in IT 0759 with
compensation planning in the Enterprise Portal.
______________________________________________________
______________________________________________________
3-4 Check and send your planning.
3-4-1 Go to the ERP system and display infotype “0759 – Compensation
Process” for the three employees.
Compare the status of the compensation process in IT 0759 with
compensation planning in the Enterprise Portal.
______________________________________________________
______________________________________________________
3-5 Then approve your compensation planning. Display infotype 0759 for the
employees for whom you have approved compensation planning. What is the
status of the compensation adjustment?
______________________________________________________
3-6 Activate compensation planning. First activate the “Test Run” switch. Start
the program and check the result. If no error messages are issued, deactivate
the “Test Run” switch and restart the program.
3-7 Display the status of the “adjusted” employee in infotype 0759 and check
infotype 0015 – Additional Payments and Deductions.
3-7-1 What is the status of infotype 0759?
______________________________________________________
3-7-2 What is the content of infotype 0015 (amount)?
______________________________________________________
3-8 Now check the Compensation Adjustments iView (ECM).


© SAP AG HR260 4-199
Solutions


Unit: Compensation

1 Which general options do you have in mySAP ERP Customizing (on which the
MSS Compensation workset is based)?
Compensation Management, Enterprise Compensation Management (based on R/3
Enterprise Extension Set 2.0)

2 List some of the differences between the Web scenario and the mySAP ERP
scenario.

3 Create compensation planning for your employees.
3-1 For all your employees, create “infotype 0758 – Compensation Program” for
01.01. of the previous year. Accept the default values.
SAP Easy Access Menu
Human Resources → Personnel Management → Administration →HR
Master Data → Maintain
Field Name Contents
Infotype 0758 – Compensation Program
Start date 01.01. of the current year
The proposals for the compensation area and the compensation program
grouping come from three features.
(CARGP compensation area, CP1GP first compensation program grouping,
CP2GP second compensation program grouping)
Save your entries.
3-2 Create compensation planning for your employees in the Enterprise Portal.
For this, use the compensation review “MSS – Compensation Review”.
Adjust the compensation as follows:
• Apply the guidelines for Jose Granados.
• Give Iffat Keitel a fixed amount of €50.00.
• Increase compensation for Seamus O’Brian by 3%.
Observe how the budget is reduced.

© SAP AG HR260 4-200
For this, go to the Enterprise Portal and choose the “Compensation” workset
and the “Compensation Planning (ECM)” page.

© SAP AG HR260 4-201

Field Name Contents
Compensation Review MSS – Compensation Review
Choose “Select All” and “Perform Planning”.
First deselect the employee selection. To do this, choose “Deselect”.
Then select the employee Jose Granados and choose “Apply Guidelines”.
Which amount and percentage is displayed for the employee Jose Granados?
Amount: EUR 3,000.00
Percentage: 4.84 %
Which percentage is displayed for the employee Iffat Keitel?
Percentage: 0.16 %
What is the compensation adjustment for Seamus O’Brian?
Amount: EUR 2,736.00
Display the compensation adjustment in graphical form. Then save your
changes. Check the status of your change request. Exit your planning.
Select the three employees for whom you are planning a compensation
adjustment and choose “Graphic Comparison”.
Choose “Save”. The three employees now have the status “In Planning”.
Choose “Exit”.
3-3 Go to the ERP system and display infotype “0759 – Compensation Process”
for the three employees.
3-3-1 Compare the status of the compensation process in IT 0759 with
compensation planning in the Enterprise Portal.
SAP Easy Access Menu
Human Resources → Personnel Management → Administration →
HR Master Data → Display
Field Name Contents
Infotype 0759 – Compensation Process
The process status is “I n Planning”. All of the infotype fields have
been transferred from the planning process in the portal.

© SAP AG HR260 4-202
3-4 Check and send your planning.
For this, go to the Enterprise Portal and choose the “Compensation” workset
and the “Compensation Planning (ECM)” page.
Field Name Contents
Compensation Review MSS – Compensation Review
Choose “Select All” and “Perform Planning”. In the next screen, select your
three employees and choose “Check Plan”. After the check, choose “Send
Planning”.
3-4-1 Go to the ERP system and display infotype “0759 – Compensation
Process” for the three employees.
Compare the status of the compensation process in IT 0759 with
compensation planning in the Enterprise Portal.
SAP Easy Access Menu
Human Resources → Personnel Management → Administration →
HR Master Data → Display
Field Name Contents
Infotype 0759 – Compensation Process
The process status is “Submitted”. The adjustments submitted for
the employees can no longer be changed in the Enterprise Portal.

3-5 Then approve your compensation planning. Display infotype 0759 for the
employees for whom you have approved compensation planning. What is the
status of the compensation adjustment?
For this, go to the Enterprise Portal and choose the “Compensation” workset
and the “Compensation Approval (ECM)” page.
Field Name Contents
Compensation Review MSS – Compensation Review
Choose “Select All” and “Approve/Reject Plan”. In the next screen, select
your three employees and choose “Check Approval/Rejection”. After the
check, choose “Send Approval/Rejection”.
SAP Easy Access Menu
Human Resources → Personnel Management → Administration → HR
Master Data → Display
Field Name Contents
Infotype 0759 – Compensation Process
The process status is “Approved”.

© SAP AG HR260 4-203
3-6 Activate compensation planning. First activate the “Test Run” switch. Start
the program and check the result. If no error messages are issued, deactivate
the “Test Run” switch and restart the program.
SAP Easy Access Menu
Human Resources → Personnel Management → Compensation
Management→ Enterprise Compensation Management → Compensation
Administration → Change Compensation Process Status
Field Name Contents
Personnel Number Your three employees
Compensation Plan MSS0
Compensation Review MSS0
Process Status from Approved
Process Status to Active
First activate the “Test Run” switch. Start the program and check the result.
If no error messages are issued, deactivate the “Test Run” switch and restart
the program.
3-7 Display the status of the “adjusted” employee in infotype 0759 and check
infotype 0015 – Additional Payments and Deductions.
3-7-1 What is the status of infotype 0759?
SAP Easy Access Menu
Human Resources → Personnel Management → Administration →
HR Master Data → Display
Field Name Contents
Infotype 0759 – Compensation Process
The process status is “Active”. All other fields are no longer ready
for input.
3-7-2 What is the content of infotype 0015 (amount)?
SAP Easy Access Menu
Human Resources → Personnel Management → Administration →
HR Master Data → Display
Field Name Contents
Infotype 0015 – Additional Payments
I nfotype 0015 now has amounts that were transferred from
infotype 0759 to infotype 0015.
3-8 Now check the Compensation Adjustments iView (ECM).
For this, go to the Enterprise Portal and choose the “Compensation” workset
and the “Compensation Overview (ECM)” page. In the Compensation
Adjustments iView (ECM), you can see the current compensation adjustment.

© SAP AG HR260 4-204



© SAP AG HR260 5-205
© SAP AG 2006
The ESS Workset in MSS: Overview Diagram
Unit 1 MSS Overview
Unit 2 Manager Self-Service Fundamentals in the Enterprise Portal
Unit 3 The Employee Review Workset
Unit 4 The Compensation Workset
Unit 5 The ESS Workset in MSS
Unit 6 The Team Calendar Workset
Unit 7 The Personnel Change Requests (PCR) Workset
Unit 8 The Recruitment Workset
Unit 9 The Reporting Workset
Unit 10 The Headcount Workset
Unit 11 Team Viewer
Appendix Homepage Framework




© SAP AG HR260 5-206
© SAP AG 2003
ESS in MSS
Þ ESS in MSS concept
Þ ESS in MSS limitations
Þ Technical concept of ESS in MSS
Þ Custom developed ESS scenarios
in the MSS functionality
Content:




© SAP AG HR260 5-207
© SAP AG 2003
ESS in MSS: Goals
Þ Understand the concept and the limitations of the
ESS in MSS workset
Þ Describe the principles the iViews are based upon
Þ Include your own custom-developed ESS services
in the MSS workset
At the end of this unit you will be able to:




© SAP AG HR260 5-208
© SAP AG 2003
ESS in MSS: Business Scenario
Þ In one of your production departments there are
no user terminal s availabl e. Nevertheless, the
team leads in these groups are able to maintain the
employees´ data because your company wants to
decentralize administrative work.




© SAP AG HR260 5-209
© SAP AG 2006
ESS in MSS: Business Background
Þ In some industries, specificall y in some departments like
production, decentralized team leads are responsible for
their employees. These employees do not have access to
a PC and user terminal solutions are not installed.
However, these companies want to decentralize their
administrative work. In their organizations, delegation of
the tasks to others than the team is not possible.
Þ Companies want their managers to ensure data quality is high.




© SAP AG HR260 5-210
© SAP AG 2003
Manager Self-Service
The Answer: ESS in MSS
Employees without PC access
Provided information about changes
Systems
HR
BW
IS-PS
FI
CO
other
Intranet
Internet
Peter F.



Þ The process starts on the Enterprise Portal where managers have access to the ESS in MSS
workset, encompassing several business functions.
Þ A manager/supervisor can select an ESS scenario for an employee who does not have access
to a computer as part of their daily tasks. In this way, the manager can enter or change
personal data on behalf of the employee.

© SAP AG HR260 5-211
© SAP AG 2003
Recap: ESS and MSS in the Enterprise Portal
Portal
Server
SAP
iViews
SAP
iViews
SAP
iViews
iView Server Page Buil der
Integration
Platform
Middleware
SAP Connector
(Jco, Business
Connector)
Internet
Transacti on
Server
Internet
Transacti on
Server
Internet
Transacti on
Server
Backend
Systems
SAP
HR
SAP
FI
SAP

SAP

SAP R/3 Systems
(>3.1H)
ESS
(< ERP2004)
SAP Web
Appli cati on
Server
SAP Web
Appli cati on
Server
SAP Web
Appli cati on
Server
Web Applications
Web Applications
MSS
URL Integration
(External Service)
URL Integration
(External Service)




© SAP AG HR260 5-212
© SAP AG 2006
ESS in MSS
Team
Viewer
Detailed
Navigation

Example
Delivery
SAP ESS Service
Application ITS
1
2
3



Þ Prerequisites
º SAP R/3 Release 4.6C:
- Plug-In 2003_1, Support Package 5
- HR Support Package 75
º SAP R/3 Enterprise (4.70):
- Plug-In 2003, Support Package 5
- HR Support Package 20
Þ The standard delivery includes eleven standard scenarios that are supported from a business
process point of view.



© SAP AG HR260 5-213
© SAP AG 2003
ESS in MSS: Example Delivery
Þ The standard delivery consists of the following services:
¤ Record Working Time (CATW)
¤ Book Training Course (PV71)
¤ Edit Skills (PZ31)
¤ Total Compensation Statement (HRCMP0080ESS)
¤ Change Own Data (PZ50)
¤ Emergency Address (PZ05)
¤ Emergency Contact (PZ18)
¤ Address Change (PZ02)
¤ Bank Information (PZ03)
¤ Personal Data (PZ13)
¤ Famil y / Related Persons (PZ12)




© SAP AG HR260 5-214
© SAP AG 2003
ESS in MSS: Technically Enabled Services I
Þ From a technical perspective, the following services
are available:
Þ Personnel Administration
¤ Who’s Who (PZ01)
¤ My Assets (ASEM)
¤ Previous Employer (PZ28)
Þ Time Management
¤ Create Leave Request (WS20000081)
¤ Request Leave of Absence (WS01000060)
¤ Display Time Statement (PZ04)
¤ Display Work Schedule (PZ17)



Þ Only the services that are part of the example delivery or part of the above list describing the
technically enabled services will be supported by SAP.
Þ Only those ESS scenarios that allow managers to quickly execute the data changes are
released in the standard business package.
Þ It is not intended to extend the ESS in MSS functionality.
Þ Country-specific services are not part of the example delivery (see above table).
Þ Services that are regarded as private services (for example, tax-related services) are not
included in the example delivery. Private services are also those which require that the
employee receives a copy of the information, either online or per mail (for example, tax
forms).

© SAP AG HR260 5-215
© SAP AG 2003
ESS in MSS: Technically Enabled Services II
Þ From a technical perspective, the following services
are released:
Þ Benefits
¤ Benefits – Enrollment (PZ14)
¤ Benefits – Participation Overview (PZ07)
¤ Retirement Benefits (PZ43)
¤ Exercising Employee Options (HRCMP0061ESS)




© SAP AG HR260 5-216
© SAP AG 2006
ESS in MSS: Record Working Time



Þ This iView enables managers to record working time data for employees in their area of
responsibility.
Þ This refers to the CATS application in the Portal (Cross Application Time Sheet)

© SAP AG HR260 5-217
© SAP AG 2006
ESS in MSS: Book Training



Þ This iView enables managers to display course offerings and book training courses for
employees in their area of responsibility.
Þ This iView calls the Employee Self-Service Course Offering.

© SAP AG HR260 5-218
© SAP AG 2006
ESS in MSS: Edit Qualifications



Þ This iView enables managers to edit the qualifications profile for employees in their area of
responsibility.
Þ This iView calls the Employee Self-Service Qualifications Profile.

© SAP AG HR260 5-219
© SAP AG 2006
ESS in MSS: Total Compensation Statement



Þ This iView enables managers to call the Compensation Management service, which they can
use to obtain the total compensation statement for a selected employee.

© SAP AG HR260 5-220
© SAP AG 2006
ESS in MSS: Change Own Data



Þ This iView enables managers to access the Change Own Data service which they can use to
maintain the name, e-mail address, and similar data for a selected employee.

© SAP AG HR260 5-221
© SAP AG 2006
ESS in MSS: Emergency Address



Þ This iView enables managers to display or change the emergency address for a selected
employee.

© SAP AG HR260 5-222
© SAP AG 2006
ESS in MSS: Overview of Personal Data



Þ This iView enables managers to display or change personal data for a selected employee.

© SAP AG HR260 5-223
© SAP AG 2006
ESS in MSS: Family Member/Dependents



Þ This iView enables managers to display or change family members or dependents for a
selected employee.

© SAP AG HR260 5-224
© SAP AG 2003
Customizing ESS in MSS
Þ No specific customizing for ESS in MSS




© SAP AG HR260 5-225
© SAP AG 2003
Including Your Own ESS Scenarios In Your Manager
Portal




© SAP AG HR260 5-226
© SAP AG 2003
ESS in MSS: Summary
Þ Understand the concept and the limitations of the
ESS in MSS workset
Þ Describe the principles the iViews are based upon
Þ Include your own custom-developed ESS services
in the MSS workset
You are now able to:




© SAP AG HR260 5-227
Exercises


Unit: ESS in MSS

I n this exercise:
• Familiarize yourself with the ESS in MSS workset.
• Familiarize yourself with ESS in MSS Customizing.


Log on to the Portal server and the mySAP ERP back-end
system. Use the log-on information provided.


1 Have you implemented the complete range of ESS services within your systems?
How much additional work can you expect if you want to use the ESS in MSS
function? How much Customizing?

2 Enter a CATS report for one of your employees.

3 Which systems and technologies are involved in using ESS in MSS?



© SAP AG HR260 5-228

© SAP AG HR260 5-229
Solutions


Unit: ESS in MSS

1 You have implemented the complete ESS services within your system. How much
additional work can you expect if you want to use the ESS in MSS function? How
much Customizing?
• None. All listed services are available for use in the workset without additional
Customizing.

2 Enter a CATS report for one of your employees.
• Log on to the portal as manager
• Go to My Staff in the top level navigation
• Choose the ESS in MSS workset
• Select any employee in the Team Viewer
• Choose the CATS application
• Fill out the appropriate fields and save the report

3 Which systems and technologies are involved in using ESS in MSS?
• Enterprise Portal and iViews for the navigation and the Team Viewer
• ITS server and Internet Application Component technology for the ESS
applications
• mySAP ERP back end for executing business logic; RFCs for the iViews and
transactions of the ITS services.




© SAP AG HR260 6-230
© SAP AG 2006
The Team Calendar Workset: Overview Diagram
Unit 1 MSS Overview
Unit 2 Manager Self-Service Fundamentals in the Enterprise Portal
Unit 3 The Employee Review Workset
Unit 4 The Compensation Workset
Unit 5 The ESS Workset in MSS
Unit 6 The Team Calendar Workset
Unit 7 The Personnel Change Requests (PCR) Workset
Unit 8 The Recruitment Workset
Unit 9 The Reporting Workset
Unit 10 The Headcount Workset
Unit 11 Team Viewer
Appendix Homepage Framework




© SAP AG HR260 6-231
© SAP AG 2006
¤ Working with the attendance workset
¤ Attendance principles
¤ Team calendar Customizing
Contents:
Team Calendar: Contents




© SAP AG HR260 6-232
© SAP AG 2006
¤ Explain the advantages of the Team Viewer for your
superiors
¤ Describe the principles on which the attendance
workset is based
¤ Name the differences between the leave request,
approving the leave request and the stand-alone
team calendar scenario
¤ Explain team calendar Customizing
After completing this unit, you will be able to:
Team Calendar: Objectives




© SAP AG HR260 6-233
© SAP AG 2006
¤ Your superior needs precise and rapid information on
the attendance of their employees. Provide the
necessary information within the team calendar.
Team Calendar: Business Scenario




© SAP AG HR260 6-234
© SAP AG 2006
Team Calendar
¤ Integration with time management
¤ Display absences
¤ Display leave requests from mySAP ERP ESS



Þ The Attendancearea provides managers with a team calendar that shows them at a glance the
attendances and absences of their employees. In addition, the Attendancearea comprises the
Leave Request service with which employees can submit Employee Self-Service leave
requests. Managers can display and approve submitted leave requests in their worklist (UWL).
Þ The Attendancearea is integrated with Time Management.
Þ The system reads the displayed absences from the Absences infotype (2001) and the
Attendances infotype (2002).
Þ Leave requests from mySAP ERP ESS are stored in a separate document database from where
they are transported to the manager's worklist.


© SAP AG HR260 6-235
© SAP AG 2006
In mySAP ERP 2004, the team calendar is required in the
following business scenarios:
Scenario 1:
Team Calendar -1. Scenario
¤ In SAP Employee Self-Service an employee creates a leave
request. In SAP Manager Self-Service the line manager can
approve or reject the leave request. Absences are approved
using the SAP Enterprise Portal function of the worklist
iView (Universal Worklist - UWL), which is a central point of
entry for all SAP Business Workflows. Within this UWL line
managers can approve or reject the individual positions of
the leave requests.



Þ In this integrated scenario you use the team calendar control in a context-oriented assistant
area/pattern (CAP) of the screen. This means that both the employee creating the request and
the approving line manager can look at the leave requests. They are supported in deciding on
the leave request, as well as in approving or rejecting the request. You can call the team
calendar using a link. In addition to calling the team calendar, line managers can get an
overview of the required absence types.

© SAP AG HR260 6-236
© SAP AG 2006
Team Calendar – 2. Scenario
Scenario 2:
¤ You can also use the team calendar in a " stand-al one"
scenario. It is part of the Business Package for Manager
Self-Service (mySAP ERP) 60.1
It is offered as part of the attendance workset in the standard
delivery.




© SAP AG HR260 6-237
© SAP AG 2006
Participation - Area Group Page
Access to Attendance Area



Þ You can start the team calendar from the area group page. If you select the "My Staff" tab in
first level navigation, the area group page appears. In the standard delivery, the area group
page has the description "Overview". The overview page provides line managers with
information on the worksets available in SAP Manager Self-Service (SAP MSS).
Þ Here you can click on the "Attendance" or "Team Calendar" quick link. If you choose
"Attendance", the "Attendance" area appears, which contains the link to the Team Calendar
service.
Þ If you click on the "Team Calendar" quick link within the area group page, you can execute
the Team Calendar service directly.
Þ In Customizing, you can modify the area group page and areas to suit your requirements. You
can determine which links are available. For detailed information about configuring the
homepage, see Customizing, under: Cross-Application Components -> Homepage
Framework.

© SAP AG HR260 6-238
© SAP AG 2006
Attendance - Area Page
Access to Team Calendar Service



Þ After the line manager selects the Attendancelink, the corresponding subarea is displayed.
Þ You can show customer-specific additional information on this page, which can help line
managers (see the Homepage Framework unit)
Þ To call the TeamCalendar service, click on the TeamCalendar link.
Þ The Attendancearea provides managers with a team calendar that shows them at a glance the
attendances and absences of their employees. In addition, the Attendancearea comprises the
Leave Request service with which employees can submit Employee Self-Service leave
requests. Managers can display and approve submitted leave requests in their worklist (UWL
– Universal Work List).
Þ The Attendancearea is integrated with Time Management.
Þ The system reads the displayed absences from the Absences infotype (2001) and the
Attendances infotype (2002).
Þ Leave requests from mySAP ERP ESS are stored in a separate document database from where
they are transported to the manager's worklist. The corresponding tables have the prefix
PTREQ*.
Þ Restrictions: Requests from the ITS-based leave request service cannot be displayed.

© SAP AG HR260 6-239
© SAP AG 2006
Team Calendar
Information from
infotypes 2001/2002



Þ The Team Calendar service gives you an overview of information on attendances and
absences of employees.
Þ The TeamCalendar comprises a colored calendar display of employees' attendances and
absences. In the standard system the colors have the following meanings:
º Blue: There is an absence on the day.
º Green: There is more than one entry for a day.
º Yellow: An employee has requested an absence that has not yet been approved.
º Red: An employee wants to cancel an absence.
Þ The manager can display details on attendance and absence types in a detail area. Note that in
the case of overlapping entries (colored green) no selection list can be displayed at this time;
only the first attendance or absence is displayed.
Þ Note:
º In the mySAP ERP 2004 standard delivery you cannot define any other status information.

© SAP AG HR260 6-240
© SAP AG 2006
Team Calendar - Details
02.05.2005 14:00 - 16:00 Doctor's appointment, partial day
informed
02.05.2005 08:00:00 -12:00 Doctor's appoi ntment, parti al day
informed
Absence details



Þ To get detailed information on absences:
º You can position the mouse pointer on an absence day. The data is then displayed in a
window
º You can display the absence by double-clicking on an absence field at the bottom left of
the team calendar

© SAP AG HR260 6-241
© SAP AG 2006
Team Calendar - Customizing
Team Calendar Customizing



Þ To use the team calendar, you have to perform the following activities in Customizing, in the
Attendance section of the IMG, under Integration with Other SAP Components -> Business
Packages / Functional Packages -> Manager Self-Service (mySAP ERP):
º Create Rule Groups
- Maintain rule groups (V_HRWEB_RULE_GRP)
- Maintain WEBMO feature
º Specify Types of Leave and Set Parameters (V_T554S_WEB)
º Define Layout of TeamCalendar (V_PTARQ_TCALE)
º Select Employees for the TeamCalendar (V_PTREQ_TEAM)



© SAP AG HR260 6-242
© SAP AG 2006
Create Rule Groups I
View V_HRWEB_RULE_GRP



Þ Rule groups help you to differentiate the various business rules that are valid for different
employees in your company.
Þ To determine the number of required rule groups, analyze how many groups of employees
there are in your company for which you want to define different Customizing settings for the
applications mentioned. It is also possible that you only need one individual rule group.
Þ For the rule group point, see the SAP IMG under Integration with Other SAP Components ->
Business Packages/Functional Packages -> Manager Self-Service (mySAP ERP) ->
Attendance-> Create Rule Groups.
Þ This IMG activity consists of two steps:
º Defining the rule group
If you need additional rule groups, you can define them in the view
V_HRWEB_RULE_GRP. You need at least one rule group. SAP provides the rule group
SAP Standard (00000001) as standard.
º Maintaining the WEBMO feature.
In this step, define the rule assignment to your employees
Þ Example:
º Some employees may be ill without a medical certificate. For other employees, the
personnel department must be informed directly and line managers must approve the
absence.

© SAP AG HR260 6-243
In this case they must create additional rule groups. The example shows them the rule
group information HR Department (00000002) and the rule group Manager Approval
(00000003)
Þ The rule groups include workflow templates for the absence types

© SAP AG HR260 6-244
© SAP AG 2006
Create Rule Groups II
WEBMO Feature



Þ In feature WEBMO, assign the rule groups defined in the previous step to your employees.
Employees are assigned in the feature based on their organizational assignment, for example,
personnel area, personnel subarea, employee group, employee subgroup, cost center and so on.
Þ This feature is used in Web applications Customizing to define different rules for groups of
employees, for example, for:
º displaying data
º selecting data
º the processing processes to run
Þ The illustration shows you how you can assign employees from rule group 00000002 and
00000003 on the basis of cost center assignment.

© SAP AG HR260 6-245
© SAP AG 2006
Set Parameters for Absence Types
View V_T554S_WEB



Þ In this IMG activity, you determine the following specifications for processing absences in the
Web application:
º You specify which absence types are displayed in the Leave Request Web application, and
which you can edit. (Scenario for Business Package for Employee Self-Service mySAP
ERP 60.1)
º If required, you can determine specific time limits for editing an absence.
Þ The absence types that you define here are also displayed in the stand-alone scenario of the
line manager's team calendar.
Þ In the standard delivery, the following attendance and absence types are defined for the rule
group SAP Standard (00000001) and the personnel subarea 01:
º Leave (absence type 0100)
º ½ day leave (absence type 0110)
º Educational leave (absence type 0190)
º Illness with medical certificate (absence type 0200)
º Illness without medical certificate (absence type 0210)
Þ The Employee Self-Service course explains the Customizing of this table. For more detailed
information, see the IMG documentation for this table.

© SAP AG HR260 6-246
© SAP AG 2006
Layout of the Team Calendar
V_PTARQ_TCALE



Þ In the view V_PTARQ_TCALE - Determine Layout of Team Calendar, you can define how
many rows are displayed in the TeamCalendar for each rule group.
Þ Note: The Cache Validity function is only available for the team calendar as of the next
release.

© SAP AG HR260 6-247
© SAP AG 2006
Selection of Employees for the Team Calendar I
Standard views based on the organizational structure:
- All employees (A_ALL)
- Directl y reporting employees (A_DIR)
These views are summarized in the ATTEND view group.



Þ This service displays information about the manager's team. You can determine how the
system identifies a team. It is possible to use the group IDs that you know from the Time
Manager's Workplace (TMW) application, or the iViews that are defined in SAP Manager
Self-Service (SAP MSS).
Þ In the standard system, you use the Object and Data Provider (OADP) view ID concept in the
team calendar (standalone scenario).
º Directly reporting employees (A_DIR)
º All employees (A_ALL)
º These two views are based on the organizational structure and are summarized in the
ATTEND view group.
Þ The Team Viewer unit explains the Object and Data Provider.

© SAP AG HR260 6-248
© SAP AG 2006
Selection of Employees for the Team Calendar II
From view V_TWPC_VG
From view HRSEL_GROUPIDS –
Customizing of TMW
View
V_PTREQ_TEAM



Þ In the view V_V_PTREQ_TEAM - Select Employees for the TeamCalendar, the next of kin
of one of the team are assigned per rule group.
Þ You must define a validity period for each rule group.
Þ Furthermore, you can define a mode for the team calendar. This means that you can use the
team calendar function in various roles:
º Application mode
You need this mode so that users can create applications.
º Approval mode
Managers/those responsible for personnel need this mode for approving applications.
º Administrator mode
You can use this mode to assign the employees that administrators need for their work to
them, using view groups/grouping IDs.
º Batch mode
Certain actions can run in the background with this mode, for example Send E-Mails or
Post Documents.
º Team view mode
In this mode a project manager, for example, can display the team calendar.

© SAP AG HR260 6-249
© SAP AG 2006
Link to Homepage Customizing



Þ Note that you can either assign the view groups in the IMG activity Select Employees for the
TeamCalendar (V_PTREQ_TEAM) as described previously, or you can use homepage
framework Customizing for assigning view groups. (See the Homepage Customizing unit)
Þ If you define the view groups in the homepage framework, these overwrite the settings in the
Customizing step Select Employees for the TeamCalendar. Note that the URL parameter of
the ATTEND view group is provided in the standard system. If you define other view groups
and want to define them using the URL parameters, you must maintain these entries in the
IMG activity Select Employees for the TeamCalendar.
Þ Note that you can also define static Portal Content Directory (PCD) pages. To do this, select
the Static PCD Pages field and enter the URL of the static page in the URL of PCD Page
field. The Static PCD Pages setting overwrites the settings created using the URL parameters
and the Select Employees for the Team Calendar view (V_PTREQ_TEAM).

© SAP AG HR260 6-250
© SAP AG 2006
¤ Explain the advantages of the Team Viewer for your
superiors
¤ Describe the principles on which the participation
workset is based
¤ Name the differences between the leave request,
approving the leave request and the stand-alone team
calendar scenario
¤ Explain Team Calendar Customizing
You should now be able to:
Team Calendar: Conclusion




© SAP AG HR260 6-251
Exercises


Unit: Team Calendar
Topic: Creating an Absence

At the conclusion of this exercise, you will be able to:
• Understand the association between the team calendar and the
attendances and absences.
• Provide the team calendar with additional
attendances/absences.

Your manager wants to use the team calendar to see which
employees are present or absent from his/her team. Provide
him/her with particular attendances/absences for this purpose.
Also create a new absence type “special leave” and make the
team calendar available.

1 Create an Absence
1-1 Create a new absence type MSXX with the description XX – special leave
(XX = group number) by copying absence type 0100 – leave for the
personnel subarea 01 grouping.
1-2 For your personnel number 260992XX (XX = group number), enter five
days’ leave for the following month.
For personnel number 260994XX, enter the MSXX absence type for three
days.
For personnel number 260994XX, enter a half day’s leave for a workday
in the following month from 8:00 – 12:00 as well as the off-site work
attendance from 13:00 to 15:00 for the same day.
1-3 Display the absences and details for the following month in your team
calendar.
Why do you not see any absences for personnel number 260993XX
(Sharon Strong)?

2 Specify Processing Processes for Types of Leave
2-1 Your manager wants to see the MSXX absence type in the team calendar.
Provide him/her with this function.


© SAP AG HR260 6-252

© SAP AG HR260 6-253
Solutions


Unit: Team Calendar
Topic: Creating an Absence

1 Create an Absence
Customizing:
Personnel Time Management → Time Data Recording and Administration →
Absences → Absence Catalog → Define Absence Types
1-1 Start transaction SM31.
Create a new absence type MSXX with the description XX – special leave
(XX = group number) by copying absence type 0100 – leave for the
personnel subarea 01 grouping.
Select the entry in the table (V_T554S) and choose “Copy As…”.
Alternatively, you can choose the F6 function key.
Field Name Contents
A/AType MSXX (XX = group number)
Text XX – Special Leave (XX = group number)
Save your entries.
1-2 SAP Easy Access Menu
Human Resources → Personnel Time Management → Administration
→ Time Data → Maintain
For your personnel number 260992XX (XX = group number), enter five
days leave for the following month.
For personnel number 260994XX, enter the MSXX absence type for three
days.
For personnel number 260994XX, enter a half day’s leave for a workday
in the following month from 8:00 – 12:00 as well as the off-site work
attendance from 13:00 to 15:00 for the same day.
Log on to the back-end system with your user HR260-XX (XX = group
number).
Field Name Contents
Personnel Number 260992XX (XX = group number)
Information Type 2001– Absence
Type 0100 – Leave

© SAP AG HR260 6-254
Period from – to Time span of five days
Choose “Create”. Confirm any system messages with “Enter”, or correct
your entries according to the system message. Then save your entries.
Repeat your entries for personnel number 260993XX with absence type
MSXX – “Special Leave” (XX = group number).
Field Name Contents
Personnel Number 260993XX (XX = group number)
Information Type 2001– Absence
Type MSXX – Special Leave
(XX = group number)
Period from – to Time span of three days
Enter the following data for personnel number 260994XX:
Field Name Contents
Personnel Number 260994XX (XX = group number)
Information Type 2001– Absence
Type 0110 – “1/2 Day Leave”
Period from – to Any workday from following month
Choose “Create”.
In the next screen, enter the following data:
Field Name Contents
Time 8:00 – 12:00
Save your entries.
Now enter the attendance “off-site work” for the same person and same
day.
Field Name Contents
Personnel Number 260994XX (XX = group number)
Information Type 2002– Attendance
Type 0410 – “Off-Site Work”
Period from – to The same day as absence type 0110
Choose “Create”.
In the next screen, enter the following data:
Field Name Contents
Time 13:00 – 15:00
Save your entries.

© SAP AG HR260 6-255


© SAP AG HR260 6-256
1-3 Display the absences and details for the following month in your team
calendar.
To do this, choose the following path in the Enterprise Portal:
My Staff → Attendance → Team Calendar
In the team calendar, select the following month, and choose “Start” to
update the calendar.
Why do you not see any absences for personnel number 260993XX
(Sharon Strong)?
Answer: Absence MSXX is not permitted for the team calendar.

2 Specify Processing Processes for Types of Leave
Customizing:
Integration with Other my.SAP.com Components → Business
Packages/Functional Packages → Manager Self-Service (mySAP ERP) →
Attendance → Specify Processing Processes for Types of Leave
2-1 Your manager wants to see the MSXX absence type in the team calendar.
Provide him/her with this function.
In the Specify Processing Processes for Absences table, maintain the
following entries:
Field Name Contents
Rule Group 00000003 – Manager’s Approval
PS G 01
A/A Type MSXX
Sort Number 001
Start Date First day of the year
End Date 31.12.9999
Processing Process Without workflow, no approval necessary
Save your entries.
Now check whether your manager can see the absence types in the team
calendar. You may have to call the team calendar again so that the
Customizing changes are updated.



© SAP AG HR260 7-257
© SAP AG 2006
Personnel Change Requests (PCR) Workset: Overview
Diagram
Unit 1 MSS Overview
Unit 2 Manager Self-Service Fundamentals in the Enterprise Portal
Unit 3 The Employee Review Workset
Unit 4 The Compensation Workset
Unit 5 The ESS Workset in MSS
Unit 6 The Team Calendar Workset
Unit 7 The Personnel Change Requests (PCR) Workset
Unit 8 The Recruitment Workset
Unit 9 The Reporting Workset
Unit 10 The Headcount Workset
Unit 11 Team Viewer
Appendix Homepage Framework




© SAP AG HR260 7-258
© SAP AG 2006
¤ PCR overview
¤ PCR concept
¤ Forms
¤ PCR Customizing
¤ ISR Customizing for PCR
¤ Workflow connection
¤ PCR status tracking
Contents:
Personnel Change Requests (PCR)




© SAP AG HR260 7-259
© SAP AG 2006
¤ Explain the general concept of PCRs
¤ Describe the components of PCRs
¤ Explain the status tracking of PCRs
¤ Adjust PCRs
¤ Explain ISR Customizing for PCRs
After completing this unit, you will be able to:
Personnel Change Requests (PCR): Objectives




© SAP AG HR260 7-260
© SAP AG 2006
¤ Your company wants to replace the paper-based
personnel administration processes that are triggered
by superiors with a Portal solution. Your team has
been assigned this task.
Personnel Change Requests (PCR): Business Scenario




© SAP AG HR260 7-261
© SAP AG 2006
Introduction - What are PCRs?
HR Department
HR Expert
HR Admi nistrator
(Admi nistration Payroll, Time)
Secretary
Telephone
Form
Telephone
Form
Telephone
Form
Superi or
Thomas
Approver
Line Manager
Communication Line Management - HR Department
Automatically Using PCR



Þ By implementing personnel change requests (PCRs) you can handle the typical processes that
are usually paper-based. The system supports managers by ensuring that the current version of
the form is always displayed for their personnel change request. The master data of the
employee for whom a change is to be requested is transferred to the header data of the request
where the data is displayed according to the current status of the HR system. This prevents a
manager from making any errors when transferring data from lists to requests.
Þ The system automatically enters information regarding the area of responsibility and forwards
the request. Particularly in the case of requests that are used infrequently, many questions arise
regarding the actual process and area of responsibility in a paper-based process. This often
means that more people than actually required are involved in the process.
Þ The time required for processing a paper-based request is often much longer than that required
for an electronic request as paper-based requests must be forwarded by internal mail, which
also makes it more difficult for those involved in the process to ask questions.

© SAP AG HR260 7-262
© SAP AG 2006
Introduction - PCR Business Process
Superi or
Tom
Approver
HR Admi nistrator
Selects the PCR form,
maintains the request
data and starts a
workfl ow usi ng the
PCR form template
Approves the
compl eted PCR form
using hi s/her
workfl ow i nbox
Fills the PCR form using
the workfl ow inbox by
calling the attached HR
transacti on



Þ This figure illustrates the flow of a typical request scenario, which you can optimize using a
personnel change request (PCR). The support that the system offers means that fewer people
participate in the flow. In the Portal you can store an FAQ document for the individual
processes. This enables users to find answers to their questions directly in the system.
Þ As the system automatically enters data concerning responsibilities, those involved in the
process no longer need to determine this data. Therefore, managers can create and submit their
requests without having to know which higher-level manager needs to approve the data, or
which HR administrator maintains the data in the system.
Þ At any time during the process, the manager requesting the change can view this information
in his or her PCR overview in the portal. In the PCR overview, managers can display the other
participants and the status of the request.
Þ There is no need to forward any documents on paper as this is replaced with an electronic
signature in the system. Therefore, in-house mail is no longer necessary.

© SAP AG HR260 7-263
© SAP AG 2003
SAP delivers examples, each customer can create forms
without modification
Introduction - SAP Standard PCRs
Þ Change employee group/subgroup (in Organizational Assignment IT 0001)
Þ Change personnel area/subarea (in Organizational Assignment IT 0001)
Þ Request promotion (changing pay scale group and pay scale level, or pay
grade and pay grade level, or a change of salary in IT0008)
Þ Change position (transferring an employee from one position to another
within the managers’ area of responsibility)
Þ Request separation (applying for the employer- or employee-initiated
termination of a contract by selecting a suitable personnel action reason)
Þ Request special payment (creating an additional payment in IT0015)
Þ Request transfer (transferring an employee to the area of responsibility
of a another manager)
Þ Change working time (changing work schedule rule and employment
percentage in IT0007)



Þ The SAP standard system already comprises a variety of PCRs. However, SAP accepts no
responsibility for the completeness of these forms with regard to the business content or their
suitability for all branches. Since processes differ greatly between enterprises, SAP provides
only a toolbox in the form of a framework in the system and example implementations.
Þ The PCR concept enables you to replace individual PCR forms without the need for making
additional modifications or allows you to use customer-specific workflows to depict
processes.
Þ You can find out about the framework that is used, under Internal Service Request (ISR) or the
term Q Notifications. The SAP Service Marketplace includes a cookbook that explains how to
implement certain scenarios using different technology and you can find this cookbook under
the alias /isr.

© SAP AG HR260 7-264
© SAP AG 2006
Personnel Change Requests



Þ You can start the Personnel Change Requests application by selecting either the Personnel
Change Requests area page, or the quick link New Personnel Change Request.

© SAP AG HR260 7-265
© SAP AG 2006
Employee Selection I
Roadmap
Team Viewer
Navigation Buttons



Þ A roadmap comprising five steps supports the visual process flow Personnel Change
Requests:
º Select employees
º Select forms
º Process forms
º Check forms
º Confirmation
Þ In the "select employees" step, line managers select the employee for whom they want to
create a change request. They use the Team Viewer to select the employee (see the Team
Viewer unit). Line managers can choose whether to display all of the directly reporting
employees for the selection.
Þ After selecting the employee, choose the Next Step button and the form selection appears.

© SAP AG HR260 7-266
© SAP AG 2006
Employee Selection II
Send E-Mail



Þ Within the Team Viewer line managers can send an e-mail to the appropriate employee.

© SAP AG HR260 7-267
© SAP AG 2006
Form Selection
PCR Scenarios
According to
Employee Grouping
Context-Dependent Support



Þ You select the change request on this page. There are 11 change requests:
º SPEG - Change Employee Group and Subgroup
º SPPA - Change Personnel Area and Subarea
º SPPD - Change Position (Enhanced)
º SPPM - Request Promotion
º SPPS - Change Position
º SPSD - Request Separation (Enhanced)
º SPSE - Request Separation
º SPSP - Request Special Payment
º SPTD - Request Transfer (Enhanced)
º SPTR - Request Transfer
º SPWT - Change Working Time
Þ For the system to handle change requests, it assigns them a technical name in Customizing, for
example, SPEG. Customizing is addressed later on in the unit.

© SAP AG HR260 7-268
© SAP AG 2006
Context-Dependent Support
Context-Dependent Support
Content Selection Column Selection



Þ In the upper area of the page, you can show the last change requests (context-dependent
support). Line managers can get an overview of their last change requests as well as their
processing status here.
Þ They can use the Personalize button to show or hide additional columns.
Þ The Filter On button enables them to restrict the display according to various criteria. They
can set the filter function for each column.
Þ They use the Continuebutton to display the Adobe form.

© SAP AG HR260 7-269
© SAP AG 2006
Edit Form
Adobe Form
Object
Entries Check



Þ You enter change data using an Adobe form. The number of input fields depends on the type
of the change request.
Þ You check all entries for validity using the Go To FormCheck button.

© SAP AG HR260 7-270
© SAP AG 2006
Check Forms
Send Form
Back to Input



Þ Before you send the change request to the responsible administrator you can check whether
the entered request data is correct.
Þ If line managers want to revise their changes they can use the Back button to go back to the
form entry page.
Þ Choosing the Submit button completes the editing of the form and sends the request to the
responsible processor (administrator or approver).

© SAP AG HR260 7-271
© SAP AG 2006
Confirmation
Navigation Area
Request Number



Þ After you have sent the change request a confirmation message with a request number appears
on the page. Each change request is assigned a unique number. This number makes the change
request available to the further processor of the change request. The change number also
appears in the status overview of change requests.
Þ Subsequently, the following links are available:
º Display and print form
º Goto personnel change request home page
º Goto Manager Self-Service home page

© SAP AG HR260 7-272
© SAP AG 2003
HR Administrator’s Business Workplace
Þ Transaction: iqs22
Þ Predefined follow-up functions for the action box
Þ Called by the personnel clerk via workflow inbox



Þ HR administrators process PCRs via the quality notification inbox IQS22.
Þ Administrators are able to branch to the transaction automatically when the received work
item with the correct notification number is started.
Þ This is advantageous since it enables tasks that are not executed in the system to be
documented. Such tasks might include the printing of the PCR for the personnel file or other
tasks related to the change that are not executed in the HR system.

© SAP AG HR260 7-273
© SAP AG 2003
Use follow-up
functions to process
request
Use follow-up
functions to process
request
HR Administrator’s Business Workplace
Setting the
notification
status to complete
Setting the
notification
status to complete
Putting the
notification in
process
Putting the
notification in
process
HR Admi nistrator
1 1
2 2
3 3



Þ After a request with status "In Process" has been received, processing can begin in the
standard system using the defined activities.
Þ Questions can be sent directly from the system to the manager (provided that Business
Workplace has been set up, the R/3 system has been connected to an SMTP server or, more
simply, an external mail system is called via a link in the frontend).
Þ HR master data can be checked and, if necessary, corrected before the personnel action is
performed.
Þ The personnel action is then performed.
Þ After all tasks have been performed, the status of the request is set to “Completed".

© SAP AG HR260 7-274
© SAP AG 2003
Follow Up Functions Available for all PCRs
HR Admi nistrator
Available for all scenarios



Þ The form can be called in display mode in all PCR scenarios. The form is displayed in a
browser window.

© SAP AG HR260 7-275
© SAP AG 2003
Follow Up Functions Available for all PCRs
HR Admi nistrator
Available for all scenarios
Requested data changes are
automaticall y populated
to the body of the mail
Requested data changes are
automaticall y populated
to the body of the mail



Þ Similar to in the Team Viewer, the frontend link enables you to call an external mail system to
communicate with the person who created the request.
Þ However, in contast to the Team Viewer in which only the recipient is entered automatically, a
subject line and the content of the request is also transferred as the mail text.

© SAP AG HR260 7-276
© SAP AG 2003
Follow Up Functions Available for all PCRs
HR Admi nistrator
Available for all scenarios
Personnel number is pre-filled
Personnel number is pre-filled



Þ To display HR master data, the personnel number is transferred from the request to the
personnel number field in PA20.

© SAP AG HR260 7-277
© SAP AG 2003
Follow Up Functions for Special PCRs
HR Admi nistrator
Available for scenarios:
SPEG IT0001
SPPA IT0001
SPWT IT0007
SPPM IT0008
SPSP IT0015
Requested data changes are
populated from the form into
the infotype screen
Requested data changes are
populated from the form into
the infotype screen



Þ In some scenarios, individual infotypes need to be maintained. However, dynamic actions
means that even if you want to change just one of these infotypes, a screen sequence for
several infotypes might be displayed.
Þ When you maintain HR master data, you can branch directly to the relevant infotypes and
transfer the data from the request to the relevant fields.

© SAP AG HR260 7-278
© SAP AG 2003
Follow Up Functions for Special PCRs
HR Admi nistrator
Available for scenarios:
SPEG, SPPA, SPWT, SPSE
Assign personnel action using
scenario attributes customizing



Þ In other scenarios, the request is processed using a personnel action. This means that the
change is also documented in IT 0000 and the employee's status might change.
Þ The values from the request are transferred to the personnel action reason and the action is
started using the relevant request data.

© SAP AG HR260 7-279
© SAP AG 2006
Processing Functions for Special PCRs III
HR Admi nistrator
Available for the scenarios:
SPPS, SPTR
Change org. management data
Execute a personnel action in order
to update the employee master
data
Change org. management data
Execute a personnel action in order
to update the employee master
data
Delete entry from table T77INT
Delete entry from table T77INT



Þ Transfer requests that involve an employee being transferred from one manager's area of
responsibility to another are an exception.
Þ Since such reassignments are very complex and both managers are involved in the process, a
"bookmark" is used at this level to indicate that such a request has already been created for
this employee and this thereby prevents further transfer requests from being created.
Þ As a result, the organizational model remains consistent, because the processor makes the
organizational reassignment first and the manager only removes the bookmark when the
reassignment is completed.

© SAP AG HR260 7-280
© SAP AG 2003
Recap: PCR in a Nutshell
Þ PCR (Personnel Change Request)
¤ Designed for managers
¤ Manager can request HR data changes for their employees on
web based forms within a portal
¤ PCRs can trigger any SAP Business Workflow
¤ Personnel clerk controls and updates data in the R/3 system
¤ PCRs depends on ISR
¤ SAP delivers examples
¤ Each customer can create forms without modification



Þ A short summary of the advantages:
Þ Tailoring the requests to suit the needs of end users, namely managers, has enabled
complicated processes to be simplified greatly – something that was previously not thought
possible. In most cases, just a few fields enable a manager to request a complex business
process.
Þ Managers have access to current data (almost in real time) from the HR system. This means
that managers are no longer reliant on regular printouts of employee data that are quickly out-
of-date and difficult to search through.
Þ The connection of requests to the SAP Business Workflow enables any processing or approval
processes to be depicted in the system. Different participants can perform different activities
in the process.
Þ PCRs are based on a framework that has already proved to be a success in quality
management. When used on a large scale, the framework ensures the stability and clarity of
processes.
Þ SAP delivers a number of examples as Quick Win.
Þ Customers can make changes to scenarios or integrate their own developments in this
framework without having to make any modifications.

© SAP AG HR260 7-281
© SAP AG 2006
PCR Overview
11 Request Scenarios



Þ SAP currently provides eleven request scenarios that you can use productively, or also as
templates when creating your own change requests. For the request scenarios provided, see the
Manager Self-Service (mySAP ERP) component Implementation Guide (IMG), under
Integration with Other SAP Components -> Business Packages / Functional Packages ->
Manager Self-Service (mySAP ERP) -> Personnel Change Requests -> Define Change
Request Types. The Manager Self-Service Business Package contains the following request
scenarios for employee data:

© SAP AG HR260 7-282
© SAP AG 2006
Change Employee Group and Subgroup (SPEG)



Þ Change Employee Group and Subgroup (SPEG)
Managers can use this change request to trigger a change of employee group and employee
subgroup for an employee (Organizational Assignment infotype (0001)). Our example
Business Workflow is not intended to be used with an approval step. HR administrators can
use the transactions PA30 (Maintain HR Master Data) and PA40 (Personnel Actions) to post
the changes to the system.

© SAP AG HR260 7-283
© SAP AG 2006
Change Personnel Area and Subarea (SPPA)



Þ Change Personnel Area and Subarea (SPPA)
This change request enables managers to apply for a change of personnel area and personnel
subarea for an employee (Organizational Assignment infotype (0001)). Our example Business
Workflow is not intended to be used with an approval step. HR administrators can use the
transactions PA30 (Maintain HR Master Data) and PA40 (Personnel Actions) to post the
changes to the system.

© SAP AG HR260 7-284
© SAP AG 2006
Change Working Time (SPWT)



Þ Change Working Time (SPWT)
This change request enables managers to ask for a change to an employee's work schedule
rule and employment percentage (Planned Working Time infotype (0007)). Our example
Business Workflow is not intended to be used with an approval step. HR administrators can
use the transactions PA30 (Maintain HR Master Data) and PA40 (Personnel Actions) to post
the changes to the system.

© SAP AG HR260 7-285
© SAP AG 2006
Request Special Payment (SPSP)



Þ Request Special Payment (SPSP)
This change request enables managers to request a special payment for an employee. Our
example Business Workflow includes an approval step, in which the superior manager must
approve the manager's request. The HR Administrator can use transaction PA30 (Maintain HR
Master Data) in the system to create a record for the Additional Payments infotype (0015).

© SAP AG HR260 7-286
© SAP AG 2006
Request Promotion (SPPM)



Þ Request Promotion (SPPM)
This change request enables managers to ask for a change of pay scale group and pay scale
level, or pay grade and pay grade level, or a change of salary. Our example Business
Workflow includes an approval step, in which the superior manager must approve the
manager's request. The HR administrator can copy a record of the Basic Pay infotype (0008),
using transaction PA30 (Maintain HR Master Data).

© SAP AG HR260 7-287
© SAP AG 2006
Change Position (SPPS)



Þ Change Position (SPPS)
This change request enables managers to transfer employees from one position to another
within their area of responsibility. Our example Business Workflow includes an approval step,
in which the superior manager must approve the manager's request. The HR Administrator can
execute the transfer in the system or delete the designation generated by the transfer request.




© SAP AG HR260 7-288
© SAP AG 2006
Request Transfer (SPTR)
Available as of mySAP ERP 2005



Þ Request Transfer (SPTR) – available for Interactive Forms as of mySAP ERP 2005
Managers can use this request to submit the transfer of an employee from their area of
responsibility to the area of responsibility of a new manager. The new manager receives the
transfer request via the SAP Business Workflow, and adds the employee's new position to the
form. In the standard procedure the superior manager of the manager who sent the request is
the approver. As with the position change, the HR administrator can execute the transfer in
the system or delete the designation.

© SAP AG HR260 7-289
© SAP AG 2006
Request Separation (SPSE)



Þ Request Separation (SPSE)
This change request enables managers to apply for the employer- or employee-initiated
termination of a contract by selecting a suitable personnel action reason. The responsible HR
Administrator then performs the administrative steps. Our example Business Workflow
includes an approval step, in which the superior manager must approve the manager's request.
The HR Administrator can perform the corresponding personnel action in the system.

© SAP AG HR260 7-290
© SAP AG 2006
Change Position (Enhanced) (SPPD)



Þ Change Position (Enhanced) (SPPD)
This change request enables managers to transfer employees from one position to another
within their area of responsibility. At the same time – as an enhancement to the standard
scenario Change Position (SPPS) – managers can also propose the action reason, employee
subgroup, time data, and salary changes. The Business Workflow provided as an example and
the follow-up actions correspond to the standard scenario SPPS.




© SAP AG HR260 7-291
© SAP AG 2006
Request Transfer (Enhanced) - SPTD
Available as of mySAP ERP 2005



Þ Request Transfer (Enhanced) (SPTD) – available for Interactive Forms as of mySAP ERP
2005
Managers can use this change request to apply to transfer an employee from their area of
responsibility to the area of responsibility of a new manager. The new manager receives the
transfer request via the SAP Business Workflow, and adds the employee's new position to the
form. At the same time, as an enhancement to the standard scenario Request Transfer (SPTR),
managers can also propose the action reason, employee subgroup, time data, and salary
changes. The Business Workflow provided as an example and the follow-up actions
correspond to the standard scenario SPTR.

© SAP AG HR260 7-292
© SAP AG 2006
Request Separation (Enhanced) - SPSD



Þ Request Separation (Enhanced) (SPSD) – available for Interactive Forms as of mySAP ERP
2005
In contrast to the standard scenario, Request Separation (SPSE), this change request includes
an additional field that specifies the last working day. All other processes are identical.

© SAP AG HR260 7-293
© SAP AG 2006
Change Requests Under ERP2004 – Objectives
¤ Intuitive use and navigation
¤ Standardized user interface design
Roadmap
Navigation buttons
¤ Context-dependent help within forms



Þ As of Version ERP2004, Adobe forms replace JSP forms in MSS. This makes it easy to adjust
forms and to develop new forms.
Þ The user-friendly interfaces and standardized design within the Personnel Change Request
workset make it possible for users to switch to this technology without requiring much
training.

© SAP AG HR260 7-294
© SAP AG 2006
Status Overview I



Þ In addition to personnel change requests, line managers can call a status overview of their
change requests.

© SAP AG HR260 7-295
© SAP AG 2006
Status Overview II
Display Form
Show Additional Columns
Filter Display



Þ Line managers can see a status overview of the processing status of the change requests here.
Þ They can use the Personalizebutton to show or hide additional columns.
Þ The Filter On button enables you to restrict the display according to various criteria. You can
set the filter function for each column.

© SAP AG HR260 7-296
© SAP AG 2006
Status Overview III



Þ In the status overview line managers can call the created forms for control purposes.

© SAP AG HR260 7-297
© SAP AG 2006
Technical Levels
¤ MSS
Þ Manager Self-Service
¤ PCR (HCM)
Þ Pers. Change Request
¤ ISR (CA)
Þ Internet Service Request
¤ Solution until Release 4.7 (EP 5.0/ EP 6.0)
Þ Java iViews with forms implemented by Java Server Pages (JSPs)
¤ ERP Solution (ERP 2004/5)
Þ WebDynpro with ADOBE forms (PCR is pilot in ISR @ ADOBE)
MSS
PCR
ISR
Form
...



Þ The internal service request (Internet Service Request, ISR) allows occasional users, without
specific knowledge of the mySAP ERP system, to submit and develop versatile service
requests on the intranet, Extranet or Internet, using Request Forms.
Þ When you fill in and send the request form, the mySAP ERP system generates a Message.
SAP Business Workflow finds the processor of this message. From the message, the processor
can execute Activities directly (for example, send e-mails, automatically generate and send
Microsoft Word documents, trigger indents, or perform any mySAP ERP transactions). You
can individually reconcile the request forms and the subsequent workflow with the service
request to be implemented and situations in the company. You can quickly and easily structure
your own ISR Scenarios. Close integration with controlling and Easy Cost Planning (ECP)
allows you to structure complex, cost-incurring scenarios, which automatically calculate the
costs and directly charges them to the cost unit.
Þ The Internal Service Request (ISR) provides a definition environment (framework) for Web-
based forms and is the basis for forms that use the Personnel Change Requests business area.
Þ ISR belongs to the cross-application components (CA). Therefore it is not exclusively used in
HR.
Þ For example, an Internal Service Request can be:
º looking for a solution to a problem
º requesting a change to a budget (subject to approval)

© SAP AG HR260 7-298
º requesting an office change (cost-incurring)
Þ For general information about Internal Service Requests, see SAP Service Marketplaceat
service.sap.com/isr.

© SAP AG HR260 7-299
© SAP AG 2006
ISR Customizing
Customer Enhancement of ISR Scenarios
ISR Scenario Definition



Þ You use the SAP Implementation Guide to set up the Internal Service Request (ISR) by
choosing Cross-Application Components → Internet/Intranet Services → Internal Service
Request → Scenario Definition.
Þ Customers can use BAdIs to influence the ISR scenarios:
º QISR1 - You can use this BAdI to control the flow logic of the request form on the mySAP
ERP page in detail.
º QISR2 - You can use this BAdI to freely determine the account assignment object for cost-
incurring scenarios.
º QISR3 - You can use this BAdI to influence the container determined for a workflow
standard role used to find the processor .
º QISR4 - You can use this BAdI to program any action from the action box, if you have
stored one of the following generic function modules in ISR Customizing for determining
the action box:
- ISR_ACTIVITY_EXECUTE_TASKDOC
- SR_ACTIVITY_EXECUTE_ACTIONDOC
- ISR_ACTIVITY_EXECUTE.
º QISR5 - You can use this BAdI to influence which processor you determine for the
Internal Service Request.

© SAP AG HR260 7-300
Þ For more information about the use and methods of BAdIs, see the ISR Cookbook on SAP
Service Marketplace at http://service.sap.com/isr.

© SAP AG HR260 7-301
© SAP AG 2006
ISR Scenario Definition I
View V_SCENARIO



Þ In this IMG activity you define scenarios for Internal Service Requests.
Þ By defining a scenario you standardize the submission and implementation of the appropriate
service request.

© SAP AG HR260 7-302
© SAP AG 2006
ISR Scenario Definition II
V_TQ85 View
V_SCENARIO View



Þ To be able to define scenarios, you require notification types. In the notification type, you
have defined if, and from whom, the service request requires approval. Numerous notification
types are provided. To be able to use them, you must use transaction QI SR_SM29 to adopt
the settings from client 000. You then need to process the number ranges of the notification
types. If the notification types from client 000 are not sufficient, you can create your own
notification types.
Note that you can use a notification type for multiple scenarios.
Þ All of the scenarios that SAP provides are in the namespace S.
Þ Two notification types are available for personnel change requests:
º 56 - PCR with approval
º 57 - PCR without approval
Þ You can only enter new requests within the validity period. You can also subsequently process
existing requests. If you do not specify a period and the Activeindicator is set, you can use the
scenario without restriction.
Þ The ISR BAdIs are in the SAP Implementation Guide under Cross-Application Components -
> Internet/Intranet Services -> Internal Service Request -> Scenario Definition -> Business
Add-Ins
.

© SAP AG HR260 7-303
© SAP AG 2006
ISR Scenario Definition III
View V_TQ85



Þ The functions that you can execute within the action box in transaction IQS22 - Process
Messages are defined here.
Þ You define the assignment of the function to the type of message (56 - with approval, 57 -
without approval) and the scenario of the Internal Service Request.
Þ Further important settings for MSS:
º Sort sequence within the action box
º Assigning the function module processed when the action is called. Several example
function modules are provided. You can use the following generic key to find the affected
function modules: QM06_FA*
º Icons that display the function on the screen

© SAP AG HR260 7-304
© SAP AG 2006
ISR Scenario Definition (Action Box I)



Þ Using the PCR change employee group and subgroup as an example, the system displays the
necessary steps for defining the action box.
Þ 1. Define the Display Formaction.

© SAP AG HR260 7-305
© SAP AG 2006
ISR Scenario Definition (Action Box II)



Þ 2. Define the Change Formaction.

© SAP AG HR260 7-306
© SAP AG 2006
ISR Scenario Definition (Action Box III)



Þ 3. Define the action "send e-mail to manager".

© SAP AG HR260 7-307
© SAP AG 2006
ISR Scenario Definition (Action Box IV)



Þ 4. Define the Display Master Data activity (PA20).

© SAP AG HR260 7-308
© SAP AG 2006
ISR Scenario Definition (Action Box V)



Þ 5. Define the Change Master Data activity (PA30).

© SAP AG HR260 7-309
© SAP AG 2006
ISR Scenario Definition (Action Box VI)



Þ 6. Define the personnel action activity (PA40).

© SAP AG HR260 7-310
© SAP AG 2006
Personnel Action
V_WPC_PCRGENERAL View
V_TQ85 View



Þ An action is called using a "HRWPC*TRANSACTION_PA40" function module. The
V_WPC_PCRGENERAL view contains the corresponding action type.
Þ The standard system contains the following function modules:
º HRWPC_PCR_EG_TRANSACTION_PA40 - Change Employee Group, Employee
Subgroup: Transaction PA40
º HRWPC_PCR_PA_TRANSACTION_PA40 - PCR Change Personnel (Sub)Area:
Transaction PA40
º HRWPC_PCR_SE_TRANSACTION_PA40 - Request Separation: Transaction PA40
º HRWPC_PCR_WT_TRANSACTION_PA40 Change Working Time: Transaction PA40
Þ A detailed description of the V_WPC_PCRGENERAL view will be provided later.





© SAP AG HR260 7-311
© SAP AG 2006
ISR Scenario Definition
V_SCENARIO View
Server Details
V_SCENARIOXMPO View



Þ If you decide to use the Adobe PDF or the JSP iView, you must specify Additional Data for
Scenario. For both types of data entry, you must specify the server that you need to call the
form from the back-end system. You can enter a server for each input type; this is valid for all
scenarios.
All other settings are only necessary if you use JSP iViews to enter data. These are the same
settings that you can make in Customizing for the Manager Self-Servicebusiness package. For
more information, see the Manager Self-Service Implementation Guide under Integration with
Other mySAP.comComponents -> Business Packages / Functional Packages -> Manager
Self-Service -> Internal Service Request -> Maintain Additional Data for Scenarios for
Internal Service Request.

© SAP AG HR260 7-312
© SAP AG 2006
ISR Scenario Definition (Status Overview)
View V_SCENARIOXMPO



Þ You can define up to 5 additional features for the status overview. These fields are maintained
for each scenario in the features point (see the next slide). Within the status overview you can
show these fields (columns) using the Personalize button.

© SAP AG HR260 7-313
© SAP AG 2006
ISR Scenario Definition (Features)
View V_SCENARIOFLD



Þ In Features you define which fields are called in the Internal Service Request form.
Þ In the Features area you specify the fields to be available in the form for the scenario.
Þ You can choose between:
º Untyped Features
º Features with up to 250 characters
º Dictionary Type Features
º Available features from the Dictionary
º For data elements, the system adopts the type and name of the feature from the Dictionary.
For structures, all data elements within the structure are drawn.
º Note: The following restrictions apply to the definition of scenario features:
- Feature names or structure field names must be unique within a scenario
- Feature names or structure field names must not start with ISR_
- Feature names or structure field names should not be named using HTML business
names, for example LABEL, NAME, VALUE, DIM, MAXSIZE, TYPE, EXISTS,
ENABLED or VISSIZE
- Feature names or structure names may only contain a maximum of 28 characters
- The data length of the feature or structure field is limited to 250 characters

© SAP AG HR260 7-314
Þ To also use the BAdI QISR1 programmed input help for Adobe forms, you must store the
technical key values of this input help in the feature. The fields Place Holder for Key Values
and Place Holder for Default Values are available for this purpose.
For each feature that you want to use as a field for a multirow long text (continuous text), you
must set the Long Text Field indicator.
© SAP AG 2006
ISR Scenario Definition (Additional Settings)
Create a Long Text for
Scenario
Definition of BADI
for Your Flow Logic



Þ Use the option of storing a long text for the scenario. This name is displayed as an explanation
when you call the form. You can also use this name to search for an appropriate form on the
intranet. When you enter text, you are not restricted to entering keywords. The search engine
does not just filter the text according to its words, it also takes their conjugation and
declination into account. The search also includes word families.
For more information on search engines, see SAP Library under Accounting -> Controlling ->
Cost Center Accounting -> Information System-> Interactive Information Systemin the text
Search Documentation on Reports, under Document Search Using the Retrieval System.
Þ To add your own processing logic to the forms, choose Business Add-In. You can change the
implementation (create, change, delete and so on).
If you need specific initializations or checks of a request for a scenario, you can use a
Business Add-In (BADI QISR1) for this purpose. For more information about BAdIs, see SAP
Library under Basis -> Change and Transport System- Overview -> Transactions and Tools -
> BC Changes in SAP Standard System-> Business Add-Ins.

© SAP AG HR260 7-315
Þ By default, each scenario is assigned its own BAdI implementation from BAdI definition
QISR1. However, if required it is possible to use oneBAdI implementation for multiple
scenarios:
º Assigning a BAdI implementation to multiple scenarios
º Referencing a scenario to the BAdI of another scenario. This option is particulary
recommended as this does not require you to modify existing BAdI implementations.

© SAP AG HR260 7-316
© SAP AG 2006
ISR Scenario Definition (Workflow)
View V_SCENARIOXMPO
View V_SCENARIO



Þ Scenario-Specific Workflow Template
Þ Create message
º You can use the "create message" workflow template to control the workflow for the
message specific to each scenario.
º Enter the workflow template that starts when you create the message for this scenario.
º If you do not want a workflow to start for this scenario when you create the message, enter
NOWORKFLOW as the workflow template.
º If you want workflow template WS03100019 that is not scenario-specific to start for this
scenario when you create the message, do not enter a workflow template here.
Þ Message in process
º You can use the "message in process again" workflow template to control the workflow for
the message specific to each scenario.
º Enter a workflow template to start for this scenario when the message is in process again.
º If you do not want a workflow to start for this scenario when the message is in process,
enter NOWORKFLOW as the workflow template.
º If you want workflow template WS03100019 that is not scenario-specific to start for this
scenario when the message is in process again, do not enter a workflow template here.

© SAP AG HR260 7-317
© SAP AG 2003
Workflow – Assignment of Workflow Templates
Þ You can assign a workflow template to each ISR scenario
(V_SCENARIOXMPO)
Workflow template
assigned to
PCR
form
Assign a workflow, which is
triggered when the manager
sends a form
Assign a workflow, which is
triggered when the manager
sends a form



Þ A separate workflow can be stored for each request type. The start of the workflow is
dependent on the event performed on a business object. If a workflow is entered in the Create
Notification field, the start event is the CREATED event performed on object BUS7051.
Þ If a workflow is entered in the Notif. in Process field, the start event is INPROCESS on
BUS7051.
Þ Since most PCRs must be approved before any changes are made to HR master data, the
CREATED event usually has to be used. Only if this event is used, is a workflow started when
the request is created. The INPROCESS event can be used if follow-on processes are to be
started as soon as processing commences for the request in the HR department.

© SAP AG HR260 7-318
© SAP AG 2006
Workflow – Templates Delivered by SAP
Return to Author
Administrator
Manager
ProcessPCR_2 (WS 50000031): 2 Approval Steps
Complete Workflow
PCR
Form
Approver
Yes
Approver
Yes
No No
Administrator
Manager
ProcessPCR_0 (WS 50000042): No Approval Step
PCR
Form
Without Approval
Return to Author
Administrator Manager
ProcessPCR_1 (WS 50000041): 1 Approval Step
Complete Workflow
PCR
Form
Approver
Yes
Complete Workflow
No



Þ SAP delivers three standard workflows for PCRs. These can be replaced with customer-
specific workflows or they can be copied and modified.
Þ There is one workflow that transfers processing directly to the HR department. No approval is
required for the request.
Þ In the standard systems, a one-step approval workflow exists whereby the next higher-level
manager, above the person who created the request, must approve the request.
Þ There is also a two-step approval workflow whereby the next two higher-level managers,
above the person who created the request, must approve the request.
Þ Such multi-step approval processes can be enhanced if work scheduling and the works council
have to be involved in a compensation adjustment. In this example, a four-step approval
process would be required. In the case of such complex approval processes, it is worth
considering whether the procedure can run simultaneously to reduce the overall runtime.

© SAP AG HR260 7-319
© SAP AG 2003
Workflow – Assignment to SAP scenarios
Þ Change employee group/subgroup: ProcessPCR_0
Þ Change personnel area/subarea: ProcessPCR_0
Þ Request promotion: ProcessPCR_1
Þ Change position: ProcessPCR_1
Þ Request separation: ProcessPCR_1
Þ Request special payment: ProcessPCR_1
Þ Request transfer: ProcessPCR_2
Þ Change working time: ProcessPCR_0
All workflows are triggered if a PCR is created



Þ In the standard system, a workflow template is assigned to each request template. You can
change this assignment at any time in Customizing.
Þ The check function module, which is required in event linkage, is essential for creating your
own workflows. The function module is called QGN01_EVENT_NOTIF_CREATED_ISR
and the assignment to event linkage can be seen in the detail view in transaction SWETYPV.
Þ If you do not maintain this entry, each workflow is started with an active event linkage
regardless of whether it is to be used for this request or not.

© SAP AG HR260 7-320
© SAP AG 2003
Workflow – Roles Delivered by SAP
Þ ApproverNext (50000133):
Determines user of the next level manager
Þ ApproverForm (50000134):
Reads user name of the approver directly from the form
(corresponding characteristic: APPROVER_UNAME)
Þ PersClerkPCR (50000137):
Determines user of the personnel clerk
Þ AuthorPCR (50000142):
Determines user of the author of a PCR



Þ Together with the standard workflows, various roles are also delivered in the workflow for
determining the processor.
Þ These roles are stored for the individual step tasks of the workflow and, after they have been
copied, can easily be replaced with user-defined roles.
Þ In role definition, you can select different methods for determining processors. The most
common methods entail specifying the areas of responsibility and processors (such as
administrator Miller is responsible for all employees whose surnames begin with the letter A-
K, administrator Thomas is responsible for L-Z) or using a function module.
Þ A suitable function module would be one that determines the next higher-level manager. The
function module uses the relationships in Organizational Management and the next
organizational unit(s) to read the next higher-level position and the user of the person who
holds this position. You can easily reprogram this logic to suit the requirements of a particular
enterprise.

© SAP AG HR260 7-321
© SAP AG 2006
Interactive Forms I
Parameters for Adobe
Forms
Call Form Builder
View V_SCENARIO



Þ In the input type field on the Web, specify how to create the internal request.
You can choose between:
º Pure text entry
º Entry using notification transaction
º Entry using Adobe PDF (see step 5 for detailed information)
º Entry using ITS service (see step 6 for detailed information)
º Entry using BSP (If you choose this entry type you must define a BSP application.
ISR_DEMO1 is an example application)
º Entry using JSP iView (The scenario is used as an iView in the Enterprise Portal. You can
generate a JSP iView. To do this, choose Additional Data for Scenario. Enter an existing
Portal component or generate a component)
Þ You only need to specify an Adobe PDF form if you chose the entry type Create with Adobe
PDF.
Þ You can generate a form. If you do not specify a name for the form, this is created
automatically upon generation as ISR_FORM_XXXX (XXXX = technical name of scenario).
You can generate the form using a template: either using the SAP standard form, or using the
form of a different scenario.
Upon generation, the features of the scenario are automatically transferred to the interface and
context of the form. You go to the FormBuilder where you can change the layout. If you

© SAP AG HR260 7-322
define new fields in the layout, you can automatically transfer them to scenario Customizing
as features when you leave the Form Builder. This also automatically stores the data binding
of the new fields in the layout.
For information about the Form Builder, in the Form Builder choose Help -> Application
Help.
For more information about using Adobe PDF forms in ISR scenarios, see the ISR Cookbook
on SAP Service Marketplace at service.sap.com/isr.

© SAP AG HR260 7-323
© SAP AG 2006
Interactive Forms II



Þ You can use the Form Builder to design the Adobe forms. The integrated Software Adobe
Designer supports you and it must be installed on your front end so that you can create the
layout. To see a print preview, you also need to install Adobe Reader 6.0, or a complete
version of Adobe Acrobat 6.0.
Þ In the Form Builder, you have various tools available for editing the form. You can also call
the Form Builder using transaction SFP. For extensive documentation on the Form Builder,
see Help -> Application Help within this transaction.
Þ For additional technical information, see the ISR Cookbook on SAP Service Marketplaceat
http://service.sap.com/I SR.

© SAP AG HR260 7-324
© SAP AG 2006
Interactive Forms III
Header
Data Entry
Context Information
Data Entry
Context Information



Þ The forms are structured as follows:
º Header area
º Context information
º Data entry
º Context information
º Data entry
º ....and so on

© SAP AG HR260 7-325
© SAP AG 2006
Internal Service Request Runtime Technology
Business
Logic Layer
Visualization
Layer
ITS
BSP
JSP
ADOBE
ISR
R/3 Back End
New
RFC



Þ You can create Internal Service Requests using different form technology:
º ITS form (in SAP@ Web Studio designed form for ITS – Internet Transaction Server)
º BSP form (Business Server Pages)
º JSP form (Java Server Pages)
º ADOBE form
Þ As of ERP 2004, forms for personnel change requests in MSS are based on Adobe technology.
Up to Release 4.7, JSP technology was used in MSS.

© SAP AG HR260 7-326
© SAP AG 2006
PCR – Customizing Employee Groupings I
View V_TWPC_PCR_EEGRP
Definition Name:
HRWPC_PCR_EEGRP
SAP Standard Grouping:
Scenarios Are Available for All
Employees in Your Company



Þ In this IMG activity, you determine employee groupings for change requests. Within the
Personnel Change Request iView, you can use employee groupings to create employee-
specific assignments of request types for request scenarios.
Þ You group employees generally, meaning independently of scenarios.
Þ In Business Add-In HRWPC_PCR_EEGRP (Adjustment: Employee and Employee Grouping
Assignment), you can create customer-specific employee groupings for change requests.
Þ If all request scenarios apply to all employees without restriction, you do not need to create
any further employee groupings. In this case, you use the employee grouping SDEF that is
provided.
Þ Request types bundle the scenarios time-dependently, depending on employee groupings. This
allows a request type to merge various country-dependent change requests, or to take
restricted validities of individual scenarios into account.
Þ The system shows managers the request types in the iView Personnel Change Request.
Þ You can implement BAdIs, for example, to:
º define country-specific scenarios
º use different forms for a scenario
º only allow the scenario Early Retirement Request for employees above a certain age

© SAP AG HR260 7-327
© SAP AG 2006
PCR – Customizing Employee Groupings II
Request Special Payment
Restrict Form Selection



Þ The figure above shows you how you can use Business Add-In HRWPC_PCR_EEGRP to
restrict the selection of forms according to certain rules.

© SAP AG HR260 7-328
© SAP AG 2003
Customizing PCRs: Example Employee Groupings
Exampl e
Þ Retirement regulations onl y for employees who are older than 55.
Þ Special Payment (Germany onl y) for employees who work in Germany.
PCR types Employee groupings PCR Scenarios
Retirement
regulations
Retirement
regulations
Special Payment
Special Payment
Special
Payment Germany
Special
Payment Germany
DE55+, R55+
ALL
DE55+, DE55-
Retirement
regulations
Special Payment



Þ You must then determine the employee groupings for which a particular request can be
created.
Þ Depending on the various employee groupings, different scenarios can be allowed for a
request type.

© SAP AG HR260 7-329
© SAP AG 2006
PCR – Customizing Change Request Types
View V_TWPC_PCR_TYPES



Þ In this IMG activity you define the data that is necessary for change requests, meaning you
define the request types.

© SAP AG HR260 7-330
© SAP AG 2006
PCR – Group Customizing Change Request Scenarios
V_WPC_PCR_GROUPS View



Þ In this IMG activity, you assign request types and employee groupings to your request
scenario. The scenarios bundled by request types are time-dependent and depend on the
employee groupings.
Þ You can use employee groupings to control the employee-specific assignment of request
scenarios to request types.

© SAP AG HR260 7-331
© SAP AG 2006
Relationship Between PCR and ISR Customizing
View V_SCENARIO
from ISR Customizing
View V_TWPC_PCR_EEGRP
from PCR Customizing
View V_TWPC_PCR_TYPES
from PCR Customizing
Grouping of Change Request Scenarios
in View V_WPC_PCR_GROUPS from
PCR Customizing
Selection Using BAdI HRWPC_PCR_EEGRP



Þ Within the Personnel Change Request iView, you can use employee grouping to create
employee-specific assignments of request scenarios for request types.
Þ You group employees generally, that is, independently of scenarios. Therefore this is valid for
all scenarios.
Þ In Business Add-In HRWPC_PCR_EEGRP (Adjustment: Employee and Employee Grouping
Assignment), you can create customer-specific employee groupings for change requests. If all
request scenarios apply to all employees without restriction, you do not need to create any
further employee groupings. In this case, you use the employee grouping SDEF that is
provided.
Þ Request types bundle the scenarios time-dependently, depending on employee groupings. This
allows a request type to merge various country-dependent change requests, or to take
restricted validities of individual scenarios into account.
Þ The system shows managers the request types in the iView Personnel Change Request.
Þ Example:
º You want to use different forms for the Special Payment scenario, for example, one form
for Germany and one form for the remaining countries. In this case, define an employee
grouping (for example GER0) and two scenarios that mirror the various forms. You define
the Special Payment request type that you can assign to employee grouping GER0,
scenario Special Payment Germany and to employee grouping SDEF, scenario Special

© SAP AG HR260 7-332
Payment Remaining. This assignment is still valid even if there are other employee
groupings. If, as described in the first example, you need an additional employee grouping
(for example, USCA for USA and Canada) for a different request type, Transport, you can
use employee grouping SDEF. In this example, American and Canadian employees are
automatically included in employee grouping SDEF.

© SAP AG HR260 7-333
© SAP AG 2006
Define PCR Customizing Attributes of Scenarios
View V_TWPC_PCR_GENERAL



Þ In this IMG activity you assign specific Human Resources Management attributes to your
request scenarios. You can assign a type of personnel administrator to your scenarios, for
example, you can specify that a scenario is processed further by an HR Administrator for
payroll. In addition, you can specify the personnel actions affected so that an HR
Administrator can postprocess changes in the system.
Þ Note that in each case you must create the personnel actions for the request scenarios Position
Changeand Internal Change.

© SAP AG HR260 7-334
© SAP AG 2006
Define PCR Customizing Reasons for Special
Payment
View V_TWPC_PCR_PAYM



Þ In this IMG activity you define the reasons for special payment that you want to use in the
Personnel Change Request iView in the Special Payment request scenario.
Þ The system shows managers the possible reasons for special payment in the request for special
payment form and they can select these as appropriate.

© SAP AG HR260 7-335
© SAP AG 2006
View V_TWPC_PCR_PAYMWT
PCR Customizing - Assign Wage Types to Speci al
Payment Reasons



Þ In this IMG activity you assign the wage types for the Special Payment request scenario to the
special payment reasons. In addition, you determine whether managers are allowed to enter
the special payment amount themselves.
Þ You can use the amount indicator to control whether the submitting manager can enter data for
the special payment amount within the Personnel Change Request iView in the Special
Payment scenario.
Þ Note: You should only set the indicator if there are no fixed calculation rules or fixed amounts
for that particular type of special payment.
Þ The special payment takes effect in infotype 0015 - additional payments.

© SAP AG HR260 7-336
© SAP AG 2006
PCR Customizing - Set Up Workflows for Change
Requests
Select Processor
1
2
3



Þ In this process step, you can set up workflows for the approval processes that are needed for
employees' change requests. This includes the following workflow templates:
Þ Submit Change Request (no approver) (WS50000042)
Þ Submit Change Request (1 approver) (WS50000041)
Þ Submit Change Request (2 approver) (WS50000031)
Þ To implement these workflows, you must assign agents to the relevant tasks contained in each
of the workflow templates and activate event linkage, that is the events that trigger the
workflow.
Þ First perform activity Assign Agents to Tasks. The screen Task Group: Maintain Agent
Assignment appears. The workflow templates to be implemented are also displayed in a tree
structure for selection.
Þ Assign agents sequentially for each of the workflow templates:
Þ 1. Expand the tree structure for one of the workflow templates. This displays all tasks that
belong to this workflow and, if necessary, any additional workflow templates that can be
called within this workflow.
Þ 2. To assign the agent, place the cursor on a task and choose Create Agent Assignment from
the function bar or menu.

© SAP AG HR260 7-337
Þ Note: Behind each task is displayed whether it is a background task. If it is a background task,
you do not need to / cannot assign an agent. If the task is not a background task, the dialog
screen Choose Agent Typeis displayed after you choose a function.
Þ 3. Select an Agent Type(for example, object type Position).
Þ 4. Then select the relevant agent (the concrete position).
Þ 5. Perform all agent assignments for the displayed tasks in this way and choose Back to leave
agent assigning.
Þ Activating Event Linkage
Þ Perform activity Activate Event Linkage. The screen Event Linkage: Triggering Events
appears. The workflow templates are again displayed in a tree structure for selection. For each
of the workflow templates, activate the events that trigger the individual workflows:
Þ 1. Expand the tree structure for one of the workflow templates. All triggering events are
displayed for the appropriate workflow template. Behind each event is displayed whether it is
activated or deactivated.
Þ 2. Activate the events of the workflows you want to use. To do this, position the cursor on the
event and choose Activate/Deactivate Event Linkagefrom the function bar or menu, or
double-click on the event.

© SAP AG HR260 7-338
© SAP AG 2006
PCR – Customizing Business Add-Ins
Definition Name:
HRWPC_PCR_EEGRP
Definition Name:
HRWPC_PCR_INIT
Definition Name:
HRWPC_PCR_ADD_VALUES
Definition Name:
HRWPC_PCR_EFF_DATE
Definition Name:
HRWPC_PCR_CHECKDATE
Definition Name:
HRWPC_PCR_APPR_FORM
Definition Name:
HRWPC_PCR_APPR_NEXT



Þ You can use the "Modify Employee Grouping" Business Add-In (BAdI) (definition name
HRWPC_PCR_PCR_EEGRP) to assign customer-specific employee groupings to employees,
in the context of change requests.
Þ You can use the "Modify Header Data in Change Forms" Business Add-In (BAdI) (definition
name HRWPC_PCR_INIT) to format the data in the form header of personnel change requests
to suit customers' requirements.
For example, you can: format employee names on a customer-specific basis. This is
recommended when the display using I0001-ENAME is not satisfactory. You can compose
employee names any way you choose, from title, first name, last name and so on. For an
example of coding, see the documentation for the method MANIPULATE_INIT_DATA.
Þ You can use the "Modify Input Help for Change Forms" Business Add-In (BAdI) (definition
name HRWPC_PCR_ADD_VALUES) to modify the input help for forms for personnel
change requests to suit customers' requirements.
Þ You can use the Modify Effective Date for Change Forms Business Add-In (BAdI) (definition
name HRWPC_PCR_EFF_DATE) to set the effective date in the form header of personnel
change requests on a customer-specific basis. For an example of coding, see the
documentation for the method MANIPULATE_EFF_DATE.
Þ You can use the Modify Check of Effective DateBusiness Add-In (BAdI) (definition name
HRWPC_PCR_CHECK_DATE) to implement a customer-specific check for the effective
date. The effective date refers to the date as of which changes to employee data are valid.

© SAP AG HR260 7-339
Þ You can use the Modify Rule Resolution for Receiving Manager Business Add-In (BadI)
(definition name HRWPC_PCR_APPR_FORM) to modify the rule resolution of the rule
ApproverForm(50000132) to suit customer requirements. The entire rule container is
available for this purpose.
Þ You can use the Modify Rule Resolution for Higher-Level Manager Business Add-In (BadI)
(definition name HRWPC_PCR_APPR_NEXT) to modify the rule resolution of the rule
ApproverNext (50000133) to suit customer requirements. The entire rule container is
available for this purpose.
Þ For more information, see the BAdI documentation in the IMG.

© SAP AG HR260 7-340
© SAP AG 2003
Customizing PCRs – Adjust Employee Groupings



Þ The SAP standard system comprises one grouping that contains all the employees at the
enterprise.
Þ Business Add-Ins are used to determine and assign customer-specific groupings.
Þ To do this, you create an implementation of the definition HRWPC_PCR_EEGRP, which is
delivered by SAP. In ABAP OO, the personnel number and the date of change for the request
is transferred. This data can be used to read all the relevant employee data required for
determining the grouping.
Þ Return values include RETURN, whether or not the grouping could be determined, and the
grouping that was determined.

© SAP AG HR260 7-341
© SAP AG 2006
Adobe/WebDynpro Concept
PCR Runtime (WebDynpro)
Select
Person /
Object
Select
Form*
Edit
Form
ISR Runtime (WebDynpro)
Adobe Form
Integration
ISR Runtime (R/3)
PBO PAI
Process Event
BAdI Implementation
Data Storage
Start Workflow
Submit
Form
*Optional at Runtime



Þ In this figure, the technical process flow of a change request is represented by ISR.

© SAP AG HR260 7-342
© SAP AG 2006
Runtime: Approving a Request I



Þ This is the Universal Worklist (UWL). From here line managers or administrators can process
change requests.

© SAP AG HR260 7-343
© SAP AG 2006
Runtime: Approving a Request II



Þ An e-mail informs the employee about the processing of a change request.

© SAP AG HR260 7-344
© SAP AG 2006
Adobe/WebDynpro – Approval Procedure (Technical View)
Portal Runtime EP 6.0
ISR Runtime (WebDynpro)
Adobe Form
Integration
ISR Runtime (R/3)
PBO PAI
Process Event
BAdI Implementation
Data Storage
Start Workflow
Submit
Form
Select
Request
from UWL



Þ In this figure the technical process flow of an approval procedure is represented by ISR.

© SAP AG HR260 7-345
© SAP AG 2006
Architectural Sketch – Basic Components
R/3
RFC
ADS
Design
Time
R/3
ISR Customizing
Net Data
CITY
COUNTRY
...
ADOBE Designer
DATA
CITY
COUNTRY
...
| City
| Country
...
XFT
User Entry
Data
Bindi ng
Runtime
Web
Dynpro
ISR Application
DATA
CITY
Walldorf
COUNTRY
Germany
...
Dynami call y
Generated!
ISR Application
ADOBE Runtime
| City
| Country
...
Walldorf
Germany
PDF




© SAP AG HR260 7-346
© SAP AG 2006
Types of PCRs
Þ No Approval Step
Þ SPEG – Change Employee Group and Subgroup
Þ SPPA – Change Personnel Area and Subarea
Þ SPWT- Change Working Time
Þ One Approval Step
Þ SPPM – Request Promotion
Þ SPPS – Change Position
Þ SPPD – Position Change Enhanced
Þ SPSD – Change Position (Enhanced)
Þ SPSE – Request Separation
Þ SPSP – Request Special Payment
Þ Two Approval Steps
Þ SPTR – Request Transfer
Þ SPTD – Request Transfer (Enhanced)




© SAP AG HR260 7-347
© SAP AG 2006
Diagram of Approval Process
Workfl ow Started-
Status: Outstanding
Noti fi cati on
Status: In Process
Fi rst Approver Gets Work Item in Inbox
Approver Executes Work Item
Requi sition Form Is Displ ayed in
Portal
Approver
Deci des
Approve
Rej ect
Yes
Personnel Offi cer
Gets Work Item
No
Next Approver Gets
Work Item in Inbox
Status of
Requi sition:
Approval : OK
Process PCR Inform Mgr
Back for
Correcti on
Manager Gets Work Item
i n Inbox
Status: Not
Approved
Status: In Process
Manager Executes Work
Item
Form Is Di spl ayed
i n Pop-Up
Withdraw
Submit
End
Workflow Ended-
Status of Requi si ti on:
Noti fication Compl eted
Hi ring Manager
Fil ls and Submi ts PCR Form
Approval Workfl ow
Templ ate
During the Approval
step, three outcomes
are possi ble:
Rejection – an e-mail
noti fication is sent out
to the Hiri ng Manager
and the Busi ness
Workfl ow i s completed
Send Back for
Correcti on – the Hiri ng
Manager recei ves the
workfl ow i tem that
allows him/her to l ook
up the approver’ s
comments and make
the consequent
adjustments
Approval – this
compl etes the approval
and the next step i n the
main workfl ow template
is executed
Last Approval Step?
Hiri ng Manager
Decides




© SAP AG HR260 7-348
© SAP AG 2006
Authorizations
Authorizations
Þ The person submitting the request needs to have authorization for the
following authorization objects:
¤ Activities for General Notifications (B_NOTIF)
¤ Relevant authorization fields:
4 Notification Type (QMART)
4 Activity Type for Notification Maintenance (NOTIF_ACT) = Notification Creation
Þ PM/QM: Notification Types (I_QMEL)
Þ Relevant authorization fields:
¤ Notification Type (QMART)
¤ Transaction Code (TCD) = IQS1
Þ User Master Maintenance: User Groups (S_USER_GRP)
¤ Activity (ACTVT) = Display (03)
Þ BC-SRV-KPR-BDS: Authorizations for Document Set (S_BDS_DS)
Þ Relevant authorization fields:
¤ Business Document Service: Class Name (CLASSNAME) = *
¤ Business Document Service: Class Type (CLASSTYPE) = *




© SAP AG HR260 7-349
© SAP AG 2006
ISR Information I



Þ For detailed information about setting up an ISR scenario, use the quick link
http://service.sap.com/isr on SAP Service Marketplace. The ISR Cookbook takes you step-by-
step through ISR Customizing.

© SAP AG HR260 7-350
© SAP AG 2006
ISR - Information II



Þ SAP online documentation also includes extensive documentation on ISR scenarios.

© SAP AG HR260 7-351
© SAP AG 2003
What about a new PCR?
HR Department
HR Expert
Manager
Tom
HR Admi nistrator
(Admi nistration,
Payroll, Time)
Secretary
Phone
Form
Phone
Form
Phone
Form
Approver
Line Management
Communication Line Management - HR Department
automatically via PCR



Þ Are you interested in learning more about the PCR concept?
If you have not already done so, calculate the Return On Investment (ROI) for one of your
paper-based processes. This will enable you to determine the costs you can save as a result of
being able to process PCRs much quicker. The advantages of system-based PCRs are
apparent.

© SAP AG HR260 7-352
© SAP AG 2006
PCR Information I



Þ For detailed information about setting up a PCR scenario, use the quick link
http://service.sap.com/mss on SAP Service Marketplace. The Configuration Guide for the
personnel change requests area provides you with information on creating a PCR scenario.

© SAP AG HR260 7-353
© SAP AG 2006
PCR - Information II



Þ For technical documentation on the MSS business package, use the quick link
http://service.sap.com/mss on SAP Service Marketplace. Among other things, the Workset
unit includes: Personnel Change Requests, which offer help within the Portal on this topic.

© SAP AG HR260 7-354
© SAP AG 2006
You should now be able to:
Personnel Change Requests (PCR): Conclusion
¤ Explain the general concept of PCRs
¤ Describe the components of PCRs
¤ Explain the status tracking of PCRs
¤ Adjust PCRs
¤ Explain ISR Customizing for PCRs




© SAP AG HR260 7-355

© SAP AG HR260 7-356
Exercise 1


Unit: Personnel Change Requests (PCR)

I n this exercise:
• Familiarize yourself with the PCR workset.
• Familiarize yourself with PCR customizing.


Log on to the Portal server and the mySAP ERP back-end system. Use
the log-on information provided.

1 Initiate a special payment for one of your employees.

2 Where do you use paper based processes in your company? How many of those
processes take place within one year? Are there processes where you would
recommend using a PCR? If so … why?

3 Which steps are necessary to create your own PCR?



© SAP AG HR260 7-357

© SAP AG HR260 7-358
Solutions 1


Unit: Personnel Change Requests (PCR)

1 Initiate a special payment for one of your employees
• Log on to the portal as manager
• In top-level navigation, change to My Staff
• Choose workset PCR
• Select any employee who does not have a “bookmark”
• Choose the form for special payment
• Fill out the appropriate field and send the change request

2 Where do you use paper based processes in your company? Think about how many
of those processes take place within one year. Are there processes you would
recommend for a … and if so, why?
• No solution. Discussion.

3 Which steps do you need to create your own PCR?
• Read the ISR “cookbook”
• Choose a similar example PCR from SAP
• Copy the existing Portal archive from this PCR and create your own JSP pages
within this copy. Upload the archive to the portal
• Copy the standard request Customizing and adjust it to the logic of your
process. If necessary, create your own workflow for the request



© SAP AG HR260 7-359

© SAP AG HR260 7-360
Exercises 2


Unit: Personnel Change Requests (PCR)
Topic: Creating a Special Payment Request

At the conclusion of this exercise, you will be able to:
• Understand the connection between creating a change request
in the portal and editing the request in the back end.
• Create additional reasons for special payment for a special
payment request.

Assign different wage types to the reasons for special payments
in the change form. Link additional reasons for special payment
with wage types in Customizing.
The HR administrator can edit the change request, supported by
the workflow.

1 Administrator Customizing
1-1 Administrator Customizing
Create a new administrator MXX with the name administrator XX for the
administrator group CABB. Assign the user name HR260.A-XX to the
administrator (XX = group number).
1-2 Assign the Administrator
Assign the administrator that you have just created as a payroll
administrator to personnel number 260993XX (Sharon Strong).

2 Create a reason for special payment
2-1 In Customizing, create a new reason for special payment XXMS with the
description XX-Special Payment (XX = group number).
Subsequently, assign wage type 50XX to the reason for special payment
XXMS (XX = group number).
2-2 For personnel number 260993XX (Sharon Strong), create a request for a
special payment for €100.00, for the 15
th
of the following month. In the
“New Comments” field, enter any reason for the request.
Go to the form check and check your entries. Send your request. Note the
number of the change request: _____________________
Check the status of your change request.


© SAP AG HR260 7-361
3 Edit the change request
3-1 Edit the change request in your inbox.
Log on to the back end as the user HR260.A-XX. Enter the password
“init”. You can choose any new password.
Select your work item.
Set the status to “Give Approval”.
Check the status change in the Enterprise Portal. Refresh your portal page
so that you can see the current status. The status should now be changed to
“Editing/Approved”.
Maintain the special payment.
Check the validity date and the wage type amount.
Check the status change in the Enterprise Portal. Refresh your portal page
so that you can see the current status. The status should now be changed to
“Completed/Approved”.


© SAP AG HR260 7-362
Solutions 2


Unit: Personnel Change Requests (PCR)
Topic: Creating New Special Payment Reasons

1 Administrator Customizing
1-1 Administrator Customizing
Customizing:
Personnel Management → Personnel Administration → Organizational
Data → Organizational Assignment → Define Administrator
Create a new administrator MXX with the name administrator XX for the
administrator group CABB. Assign the user name HR260.A-XX to the
administrator (XX = group number).
Field Name Contents
Group CABB
Administrator MXX (XX = group number)
Administrator Name Administrator-XX
SAP Name HR260.A-XX (XX = group number)

1-2 Assign the Administrator
Assign the administrator that you have just created as a payroll
administrator to personnel number 260993XX (Sharon Strong).
Human Resources → Personnel Management → Administration → HR
Master Data → Maintain
Field Name Contents
Personnel Number 260993XX (XX = group number)
Information Type 0001– Organizational Assignment
Choose “Change”.
In the “PayrAdmin” field, enter your administrator.
Field Name Contents
PayrAdmin MXX (XX = group number)
Save your entries.

© SAP AG HR260 7-363
2 Create a reason for special payment
2-1 In Customizing, create a new reason for special payment XXMS with the
description XX-Special Payment (XX = group number).
Customizing:
Integration with Other mySAP.com Components → Business
Packages/Functional Packages → Manager Self-Service (mySAP ERP)
→ Personnel Change Requests → Define Reasons for Special Payment
Field Name Contents
Spec. Paym. XXMS
Name of Reason for Special
Payment
XX Special Payment
Subsequently, assign wage type 50XX to the reason for special payment
XXMS.
Customizing:
Integration with Other mySAP.com Components → Business Packages
/Functional Packages → Manager Self-Service (mySAP ERP) →
Personnel Change Requests→ Assign Wage Types to Special Payment
Reasons
Field Name Contents
Country Grouping 99
Spec. Paym. XXMS
Start – End 01.01.2005 – 31.12.9999
Wage Type 50XX
Amount X
Save your entries.
2-2 For personnel number 260993XX (Sharon Strong), create a request for a
special payment for €100.00, for the 15
th
of the following month. In the
“New Comments” field, enter any reason for the request.
To do this, choose the following path in the Enterprise Portal:
My Staff → Personnel Change Request → New Personnel Change
Request
Select the personnel number 260993XX and choose “Next Step”.
Select the following request: “Request Special Payment” and choose
“Next Step”.
Field Name Contents
Change Date 15. of the following month
Special Payment Reason XXMS (XX = group number)

© SAP AG HR260 7-364
New Comments Any Reason
Go to the form check and check your entries. Send your request. Note the
number of the change request: _____________________
Check the status of your change request.
Go to the “Personnel Change Request” home page, and then to the status
overview.
3 Edit the change request
3-1 Edit the change request.
Log on to the back end as the user HR260.A-XX. Enter the password
“init”.
SAP Easy Access:
Office → Workplace
Select your work item.
Choose “Display”.
Set the status to “Give Approval”.
Menu:
Message → Functions → Give Approval
Alternatively, you can use the shortcut “Shift + F4”, or choose the
approval button. Save your entries.
Check the status change in the Enterprise Portal. Refresh your portal page
so that you can see the current status. The status should now be changed to
“Editing/Approved”.
Maintain the special payment. To do this, reopen your message. Now go
to the action box and choose "Change Master Data (PA30)".
Check the validity date and the wage type amount.
Save your entries and close the message.
Menu:
Message → Functions → Complete…
Alternatively, you can use the shortcut “Shift + F9”, or choose the button
with the black and white flag. To confirm the dialog box that appears,
choose Enter.
Check the status change in the Enterprise Portal. Refresh your portal page
so that you can see the current status. The status should now be changed to
“Completed/Approved”.



© SAP AG HR260 8-365
© SAP AG 2006
Recruitment Workset: Overview Diagram
Unit 1 MSS Overview
Unit 2 Manager Self-Service Fundamentals in the Enterprise Portal
Unit 3 The Employee Review Workset
Unit 4 The Compensation Workset
Unit 5 The ESS Workset in MSS
Unit 6 The Team Calendar Workset
Unit 7 The Personnel Change Requests (PCR) Workset
Unit 8 The Recruitment Workset
Unit 9 The Reporting Workset
Unit 10 The Headcount Workset
Unit 11 Team Viewer
Appendix Homepage Framework




© SAP AG HR260 8-366
© SAP AG 2003
MSS Recruitment
Þ MSS Recruitment process
Þ Integration of R/3 functionalities and ISR
Þ Customizing
Content:




© SAP AG HR260 8-367
© SAP AG 2003
MSS Recruitment: Goals
Þ Describe the MSS-based recruitment process
Þ Describe the integration of R/3-functionalities
and ISR in the recruitment workset
Þ Customize the MSS recruitment workset.
At the end of this unit you will be able to:




© SAP AG HR260 8-368
© SAP AG 2006
Recruitment Workset - Overview



Þ The MSS workset Recruitment provides a seamless integration with mySAP ERP functions.
Furthermore, the functions available in mySAP ERP were enhanced by integrating new MSS
functions within the workset in the forms based on the ISR framework.
Þ Before mySAP ERP, the MSS Business Package does not offer any integration with SAP's e-
recruiting solution.

© SAP AG HR260 8-369
© SAP AG 2003
MSS Requisition – Purpose
Þ The requisition process is convened in a Requisition service
for the Recruitment workset of the Business Package for
Manager Self-Service.
Þ The requisition process is presented as a web-based application
for Line Managers to manage and track the recruitment process
for candidates and applicants. It covers the entire recruitment
cycle - from discovering the need to hire through to filling a
vacant position.




© SAP AG HR260 8-370
© SAP AG 2003
MSS Requisition - Characteristics
Þ The requisition scenario is designed with the following
characteristics:
¤ Flexible requisition creation by utilizing easy-to-use Requisition
Request Forms that can be customized to fit various business
practices.
¤ Efficient workflow-supported process, involving roles such as
Hiring Manager, Approver(s), HR Recruiter and other members
of the Recruitment Team.
¤ Streamlined recruiting process by integrating SAP’s applicant
tracking system with the company‘s choice of web-based
application for Talent Relationship Management.
¤ Effective requisition management of SAP objects, such as requisition,
position, job and applicants with highly visible and timesaving
overviews intended for the Hiring Managers.




© SAP AG HR260 8-371
© SAP AG 2006
MSS Requisition Flow
Þ The requisition process starts in the Enterpri se Portal, where
managers can access the Recruitment workset and can perform
several business functions:
¤ Create requisition request
¤ Business workflow



Þ Create requisition request
º Managers can choose between multiple (pre or user-defined) templates to create requisition
requests. Forms for requisition requests are either started new, or by selecting a position
with position-dependent data. If the form was initialized with the correct information, the
hiring manager can fill the remaining mandatory or optional fields of the form in the
individual sections (for example, Header Data, Position Data, Posting Data and so on).
Managers can also search the SAP Repository for users, positions, or jobs to be able to
complete the form. When the requisition request form is complete and has been sent, the
form data is verified and checked against the my SAP ERP system. If data conflicts, or if
there are errors, error messages inform the manager. These are displayed at the top of the
form. Otherwise the form data from the requisition request is saved in the SAP Repository.
Þ Business Workflow
º As soon as the requisition request has been sent and saved in the SAP Repository, the
mySAP ERP system initiates the Business Workflow linked with the request form. In the
workflow template provided, the workflow work item is forwarded to the first approver,
the superior of the hiring manager, for approval.

© SAP AG HR260 8-372
© SAP AG 2006
Business Flow I
Þ Within the Business Package
Manager Self-Service, the
recruitment workset contains
the R/3 component functions
for recruitment, and integrates
new functionalities that are
relevant for managers.
Positi on overview / set positi on
to vacant wi th posi tion detail s
Form: Set posi tion to vacant
HR department approves request
and sets the positi on to vacant
Vacant positi on appears in
the vacancy overview
Assignment of appli cants to the
vacant posi tion; the appli cants for a
posi tion appear in the applicant
overvi ew for a vacancy



Þ In the Position Overview / Designate Vacant Position iView, managers can display an
overview for the part of the organizational structure for which they are responsible. They can
obtain the following information from the overview:
º Which organizational units am I responsible for?
º Which employees fill which positions?
º Has a position already been designated as vacant?
Þ Furthermore, managers can also access additional functions (for example, detail view of
positions) by further navigation.
Þ If an organizational change becomes apparent — for instance, if an employee changes
department — the overview allows managers to send a request to the personnel department to
designate the position as vacant. Form: Staff Requisition/Designate Vacant Position is
available for this purpose. SAP Business Workflow ensures that the form reaches the
responsible administrator, who then processes the request.



© SAP AG HR260 8-373
© SAP AG 2006
Business Flow II
Appli cant anal ysis based on archi ved
appli cati on documents
Hire applicant
¬ Position is occupi ed
Forms:
¤ Invite Applicant
¤ Offer Appl icant a Contract
¤ Reject Applicant
¤ Send to HR department



Þ After the approval process has been completed and the administrator has designated the
position as vacant, the system displays the vacant position in the iView Vacancies Overview .
As soon as an applicant has been assigned to the vacancy, the system displays this in the
iView Applicant Overview for Vacancy. In this overview, the manager can display data on an
applicant (applicant documents, photo) and arrange applicants in a personal ranking list.
Þ When the manager has completed the applicant analysis, he or she can send various requests
to the personnel department. Managers can use the following form-based iViews for this
purpose:
º Form: Invite Applicant
º Form: Job Offer
º Form: Reject Applicant
Þ SAP Business Workflow ensures that the request is sent to the responsible personnel
administrator who then processes it
Þ When an applicant is hired the corresponding position receives the status filled.

© SAP AG HR260 8-374
© SAP AG 2003
Recruitment – iViews Technical Basis
Object and Data Provider
Object and Data Provider
Form
Form
Þ Vacancy Request Overview X
¤ Create vacancies X
¤ Link to position description
Þ Vacancy Overview X
(link to applicant overview)
Þ Appli cant Overview X
¤ Short Profile
¤ Archived Documents
¤ Photo
¤ Administration
º Invite X
º Reject X
º Offer job X
º Ranking
Þ Send Recruitment Forms
Þ Position Description



Þ The Recruitment iViews are closely integrated with the Object and Data provider, which is
described in detail in the team viewer unit.
Þ In addition, it is integrated with the ISR-framework, upon which the PCRs are based.
Þ This workset illustrates that by using powerful tools (OADP, ISR), SAP has created a
consistent framework for different purposes. The advantages for implementation teams are
clear. If they understand the basics of MSS, they can easily adjust all the functionalities to
their needs.

© SAP AG HR260 8-375
© SAP AG 2003
Requisition Creation – Position/Job Viewer
Position/Job Viewer
(com.sap.pct.hcm.rq_positionjob
viewer.default)
Þ Tab strip-based iView,
displaying infot ype data
(1002, 1005, 1008, 10011,
1013) about a position or job.
Link to Position Viewer
Link to Position Viewer



Þ Managers can easily create a requisition directly from the portal.
Þ By using the portal to launch another iView, the manager receives useful information about
the position from different infotypes.

© SAP AG HR260 8-376
© SAP AG 2003
Requisition Creation – Create Requisition Form
Same iVi ew –
two states:
Initial and Detail
Same iVi ew –
two states:
Initial and Detail
Select a position
and click on
“ Create Requisi tion”
Select a position
and click on
“ Create Requisi tion”




© SAP AG HR260 8-377
© SAP AG 2006
Applicant Tracking As The Next Step Of The
Recruitment Process




© SAP AG HR260 8-378
© SAP AG 2006
Short Profile Linked to Previous iView
Change Short Profile:
SIMG_SPORT -> Manager Self-
Service -> Vacancies and
Applicants -> BAdI: HTML Format
iView: com.sap.pct.hcm.rc_shortprofile.default iView: iView: com.sap.pct.hcm.rc_shortprofile.default com.sap.pct.hcm.rc_shortprofile.default



Þ This iView displays the short profile defined in the mySAP ERP system.
Þ You set up the short profile in Recruitment Customizing, under Applicant Administration ->
Short Profile. In this IMG activity you can define a short profile and assign it to particular
groups of persons using a function.
Þ As the short profile is formatted in SAPScript, the system depicts indentations as spaces in the
mySAP ERP system.
Þ To display these indentations in HTML format in the Portal environment, we provide the
Business Add-In (BAdI) HRWPC_RC_SHORTPROFIL.
Þ After importing the plug-in system, set up the BAdI by making the settings in the Manager
Self-ServiceBusiness Package (transaction SIMG_SPORT). Choose Recruitment -> BAdI:
Adjust HTML Format for Short Profile.

© SAP AG HR260 8-379
© SAP AG 2006
Archived Documents and Photos
iView: com.sap.pct.hcm.eeprofilephoto.applicant iView: iView: com.sap.pct.hcm.eeprofilephoto.applicant com.sap.pct.hcm.eeprofilephoto.applicant



Þ Archived Documents
º This iView displays applicant documents that have been saved in the mySAP ERP system
using SAP ArchiveLink.
º You can create a document in the mySAP ERP System using transaction OAAD. For an
applicant, you must use the business object PAPL.
Þ Photo
º This iView displays the photograph of an applicant that has been saved in the mySAP ERP
system using SAP ArchiveLink.
º You can attach the photo in the mySAP ERP System using transaction OAAD. You must
use the business object PAPL and the document type HRICOLFOTO for an applicant.

© SAP AG HR260 8-380
© SAP AG 2006
Applicant Administration
Calls Recruitment Forms. Use
Table V_TWPC_RC_VACSTA to
Determine the Status Displayed in this iView
Defined in Table
V_TWPC_RC_RANK_C




© SAP AG HR260 8-381
© SAP AG 2003
Sent Recruitment Forms
iView: com.sap.pct.fin. com.sap.pct.fin.isrstatusoverview.rcwide iView: com.sap.pct.fin. com.sap.pct.fin.isrstatusoverview.rcwide iView: com.sap.pct.fin. com.sap.pct.fin.isrstatusoverview.rcwide
iView: com.sap.pct.fin.isrstatusoverview.rcnarrow iView: com.sap.pct.fin.isrstatusoverview.rcnarrow iView: com.sap.pct.fin.isrstatusoverview.rcnarrow




© SAP AG HR260 8-382
© SAP AG 2003
¬ ISR-Scenario: SRVR Staff requisition / designate vacant position
Vacancy Request - Form and Workflow
Customizing Behind It
¬
Notification type: 5A RC with approval
5B RC without approval
¬
Number ranges: Ensure that notification types 5A/5B are assigned
to number ranges
¬ BAdI: QISR1 / HRWPC_RC_VACREQ
¬ Workflow: WS50000034 vacancy request
¬
Prerequisites: Personnel officer must be entered in table T526
Assign agents (officer) to workflow tasks



Þ In the standard system, SAP delivers the SRVR form.
Þ The form uses Business Add-In (BAdI) QISR1 (Internal Service Request: Program-Interface
Forms)
within ISR form technology. The BAdI has the following functions:
Þ Fills form fields
Þ Checks ready-for-input fields for correctness after an entry has been made
Þ Selects and displays text for a specified value
Þ For this form we deliver implementation HRWPC_RC_VACREQ for BAdI QISR1. The
implementation uses the following methods:
Þ INT_SERVICE_REQUEST_CHECK
º You need this method to check the correctness of ready-for-input fields after data has been
entered.
Þ INT_SERVICE_REQUEST_INIT
º This method pre-assigns values to form fields.
Þ SCENARIO_SET_ADDITIONAL_VALUES
º If you want to fill a dropdown list box with values, you can use this method to help you.

© SAP AG HR260 8-383
© SAP AG 2006
Invite Applicant – Underlying Customizing for
Forms and Workflow
¬ ISR Scenario: SRIV invite applicant
¬
Notification Type: 5A RC with approval
5B RC without approval
¬
Number Ranges: Ensure that number ranges are assigned notification
types 5A/5B
¬ BAdI: QISR1 / HRWPC_RC_INVITE
¬ Workflow: WS50000038 Invite applicant for an interview
¬
Prerequisites: Personnel officer must be entered in table T526
Processor (officer) is assigned workflow tasks
Personnel officer must be assigned a vacancy ->
Field V_T750X



Þ The system proposes an administrator that you assigned in the position view V_T750X
(Vacancy).
Þ If there is no assignment, the system proposes the first administrator listed in the combo box.
Þ In input help, the system displays all administrators from table T526 (Administrator) for group
APPL as administrators.
Þ These administrators must also be maintained during user assignment for the started
workflow.
Þ After the administrator has performed the necessary steps for changing the vacancy status in
the mySAP ERP system, the system displays the changed vacancy status in the Portal. To
enable the administrator to set an applicant from vacancy status Invited (7) to vacancy status
Offer J ob (5), you may need to change the feature STATU (Consistency of Overall Status with
Vacancy Assignment Status).
Þ Make these settings in Recruitment Customizing, under Applicant Selection -> Applicant
Status -> Set Permissible Vacancy Assignment Statuses.

© SAP AG HR260 8-384
© SAP AG 2006
Reject Applicant – Underlying Customizing for
Forms and Workflow
¬ ISR Scenario: SRVR Reject applicant
¬
Notification Type: 5A RC with approval
5B RC without approval
¬
Number Ranges: Ensure that number ranges are assigned notification
types 5A/5B
¬ BAdI: QISR1 / HRWPC_RC_REJECT
¬ Workflow: WS50000040 Reject applicant
¬
Prerequisites: Personnel officer must be entered in table T526
Processor (officer) is assigned workflow tasks
Personnel officer must be assigned a vacancy ->
Field V_T750X
Maintain table V_T751D for reason for rejection



Þ The system proposes an administrator that you assigned in the position view V_T750X
(Vacancy).
Þ If there is no assignment, the system proposes the first administrator listed in the combo box.
Þ In input help, the system displays all administrators from table T526 (Administrator) for group
APPL as administrators.
Þ These administrators must also be maintained during user assignment for the started
workflow.
Þ In input help for the Reason for Rejection field, the system displays the values from view
V_T751D.
Þ You can change this is in the Recruitment Implementation Guide (IMG), under Applicant
Selection -> Applicant Status.
Þ After the administrator has performed the necessary steps for changing the vacancy status in
the mySAP ERP system, the system displays the changed vacancy status in the Portal.

© SAP AG HR260 8-385
© SAP AG 2006
Prerequisites: Personnel officer must be entered in table T526
Processor (officer) is assigned workflow tasks
Personnel officer must be assigned a vacancy ->
Field V_T750X
Methods: INT_SERVICE_REQUEST_CHECK
INT_SERVICE_REQUEST_INIT
SCENARIO_SET_ADDITIONAL_VALUES
Offer Job – Underlying Customizing for Forms and
Workflow
¬ ISR Scenario: SRJO Offer job
¬
Notification Type: 5A RC with approval
5B RC without approval
¬
Number Ranges: Ensure that number ranges are assigned notification
types 5A/5B
¬ BAdI: QISR1 / HRWPC_RC_JOBOFFER
¬ Workflow: WS50000039 Offer applicant job
¬
¬



Þ The system reads information on the position from the following infotypes:
º Planned Compensation (1005)
º Account Assignment Features (1008)
º Employee Group/Subgroup (1013)
Þ The system proposes an administrator that you assigned in the position view V_T750X
(Vacancy).
Þ If there is no assignment, the system proposes the first administrator listed in the combo box.
Þ In input help, the system displays all administrators from table T526 (Administrator) for group
APPL as administrators.
Þ These administrators must also be stored during user assignment for the started workflow.
Þ After the administrator has performed the necessary steps for changing the vacancy status in
the mySAP ERP system, the system displays the changed vacancy status in the Portal.

© SAP AG HR260 8-386
© SAP AG 2003
Workflow For Vacancy Assignment And The
Customizing Behind It
Personnel officer
creates an assignment
vacant
AP
Workflow RCVacAssign
(WS 50000036) starts
Manager receives a message:
“ New Applicant”
Þ Prerequisites:
¤ Assign manager to workflow task
¤ Activate event linking
¤ Manager must be assigned to vacancy ¬V_T750X field :‘manager‘
¤ T77S0: PPVAC PPVAC, value =1



Þ When an administrator assigns an applicant to a vacancy, either during the initial entry of
applicant data (PB10) or whilst processing the Vacancy Assignment (4002) infotype, the
system triggers the events VACASSIGN.CREATED or VACASSIGN.INPROCESSING.
These events trigger Workflow WS50000036 (RCVacAssign). This Workflow informs the
manager that an applicant has been assigned to him or her.
Þ If you want to use this workflow, you must perform the processor assignment for each
Workflow task and activate the event linkage for the events that trigger events in workflow.
Þ Workflow ensures that the manager you stored as the line manager for vacancy in view
V_T750X is informed.
Þ To enable you to process view V_T750X, while creating a vacancy in Organizational
Management, you must set the PPVAC / PPVAC switch to 1 in table T77S0.
Þ You process this setting in the Implementation Guide (IMG) for Organizational Management
under Infotype Settings ¬ Activate/Deactivate “Vacancy” Infotype.

© SAP AG HR260 8-387
© SAP AG 2003
MSS Recruitment: Summary
Þ Describe the MSS-based recruitment process
Þ Describe the integration of R/3-functionalities
and ISR in the Recruitment workset
Þ Customize the MSS Recruitment workset.
You are now able to:




© SAP AG HR260 8-388

© SAP AG HR260 8-389
Exercises


Unit: MSS Recruitment

I n this exercise:
• Familiarize yourself with the Recruitment workset.
• Familiarize yourself with Employee Review Customizing.


Log on to the Portal server and the mySAP ERP back-end
system. Use the log-on information provided.

1 Create a vacancy for one of your positions.

2 You need information about applicants. Where can you get it?

3 How can you change the objects displayed in the checkboxes in the Recruitment
workset?

4 How can you adjust the format of the short profile of applicants?



© SAP AG HR260 8-390

© SAP AG HR260 8-391
Solutions


Unit: MSS Recruitment

1 Create a vacancy for one of your positions.
Select the Recruitment tab page. Select Position Overview in the Detailed
Navigation iView. Select the Create formicon in the line assigned to the position
that is to be changed to vacant.

2 You need information about applicants. Where can you get it?
Select the Recruitment tab page. Select Applicant Tracking in the Detailed
Navigation iView on the left side. Choose the Applicant Overview iView and then
the applicant whose data you want to see.

3 How can you change the objects displayed in the checkboxes in the Recruitment
workset?
Use the table V_TWPC_OTYPES.

4 How can you adjust the format of the short profile of applicants?
Manager Self-Service (transaction SIMG_SPORT). Do this under Recruitment ->
BAdI: Adjust HTML Format for Short Profile.




© SAP AG HR260 9-392
© SAP AG 2006
Reporting Workset: Overview Diagram
Unit 1 MSS Overview
Unit 2 Manager Self-Service Fundamentals in the Enterprise Portal
Unit 3 The Employee Review Workset
Unit 4 The Compensation Workset
Unit 5 The ESS Workset in MSS
Unit 6 The Team Calendar Workset
Unit 7 The Personnel Change Requests (PCR) Workset
Unit 8 The Recruitment Workset
Unit 9 The Reporting Workset
Unit 10 The Headcount Workset
Unit 11 Team Viewer
Appendix Homepage Framework




© SAP AG HR260 9-393
© SAP AG 2006
¤ Reporting – concept
¤ MDT and MSS
¤ Reporting Customizing
Contents:
Reporting




© SAP AG HR260 9-394
© SAP AG 2006
¤ Explain the concept of reporting in MSS
¤ Explain the relationship between MSS and MDT
¤ Adjust the reporting workset and incorporate new
elements in the workset
After completing this unit, you will be able to:
Reporting: Objectives




© SAP AG HR260 9-395
© SAP AG 2006
¤ Instant access to information is one of your
manager' s main requirements.
Your task is to incorporate user-defined developed
reports in your manager Portal.
Reporting: Business Scenario




© SAP AG HR260 9-396
© SAP AG 2003
Manager Require information
Peter F.
Birthday list
Birthday list
Headcount
Headcount
Success of recruiting
channels
Success of recruiting
channels
Attendance
Attendance
Qualification
OrgUnit
Qualification
OrgUnit
Top performers
Top performers
Maternity
Maternity
Employee Overview
Service
anniversaries
Attendance
Costs



Þ As we have seen before, a manager has to fulfill a lot of tasks like:
º Appraise his employees,
º Identify the top performers, and reward them appropriately.
º Delegate tasks,
º Staff projects, and
º Recruit the people best suited for future tasks.

© SAP AG HR260 9-397
© SAP AG 2006
MSS Provides Access to Al l Reporting Information
ABAP Reports
SAP Queries
BW Reports
HIS Reports
Crystal Reports
Transactions
Cost Center Reports
Peter F.



Þ These reports can be based on the following technologies:
º ABAP Report
º Query Report
º BW Web Report Release 2.x
º BW Web Report Release 3.x
º RW Report
º mySAP ERP Transaction
º Function Modules
Þ The report selection is based on Manager's Desktop Customizing. This gives users who have
previously used Manager's Desktop and now want to change to Manager Self-Service a great
advantage. The majority of MDT Customizing can be reused for MSS. For example, you can
reuse reports, information and transactions that customers developed especially for their line
managers that were not provided by the standard SAP system. You can easily incorporate
these functions into MSS.
Þ The Combined Analysis service enables line managers to directly access BW reporting and
BW Cockpits.

© SAP AG HR260 9-398
© SAP AG 2006
Manager’s Desktop (MDT) and MSS



Þ The figure above shows you extracts from the Manager’s Desktop and Manager Self-Service
applications.

© SAP AG HR260 9-399
© SAP AG 2006
Reporting Workset



Þ You use the reporting workset to access the report selection within the My Staff role.

© SAP AG HR260 9-400
© SAP AG 2006
Reporting - Overview Page I
Start of Report Selection



Þ Line managers can use the Report Selection service to select a report that, as a selection basis,
contains organizational objects (for example, organizational units, positions and employees)
for which they are responsible. When line managers click on the Report Selection service they
get a list of reports that they can execute in Manager Self-Service.

© SAP AG HR260 9-401
© SAP AG 2006
Report Selection I



Þ In the first step line managers can select a report from the list, or restrict the report selection to
certain categories.

© SAP AG HR260 9-402
© SAP AG 2006
Report Selection II
Select Report Category



Þ The report tree that you know from MDT and earlier versions of MSS is now represented as a
list of report categories. You can select the report categories using a dropdown list box.
Þ To select a report, choose the left radio button next to the name of the report. Then choose the
Select Objects button to navigate to the next page.
Þ At the top of the page the road map helps you follow the steps for selecting reports and
objects.

© SAP AG HR260 9-403
© SAP AG 2006
Report Selection III
Select Period
Select Objects



Þ Depending on Customizing settings (see the Team Viewer unit), line managers can select the
employees for whom they want to start a report. For example:
º All organizational units
º All cost centers
º Directly reporting employees
º Directly subordinate organizational units
º Directly subordinate employees
º And so on

© SAP AG HR260 9-404
© SAP AG 2006
Selection Criteria Definition
Depending on the Selected View, the
Appropriate Objects Appear
Selected Objects



Þ After you select the report, object selection appears
Þ Line managers can make the following selection criteria:
º Report period in which evaluations are performed
º Organizational view for selecting objects in the table below the dropdown list box
º Select objects (organizational units, positions, employees) for which the report is started
Þ Choosing the Report Results button opens a window with the contents of the report

© SAP AG HR260 9-405
© SAP AG 2006
Report Results
The result of the report is displayed in a
separate popup window. This allows you to
execute multiple reports and compare
results.



Þ In the last step of the road map line managers see the results of the report in a separate
window.
Þ This enables you to execute multiple reports in parallel.
Þ The following links are below the road map:
º Change selection criteria
º Select next report
º Call reporting homepage
º Back to My Staff homepage
º Line managers can print the report.

© SAP AG HR260 9-406
© SAP AG 2006
Reporting - Overview Page II
BW Cockpit Selection



Þ The reporting workset includes the services:
º Report selection
º Combined analysis
Þ You can use the Combined Analysis services to start Business Warehouse reports.
Þ This page enables you to select BW analysis reports.
Þ The standard delivery includes the BW report areas:
º Headcount
º Illness and Overtime
º Qualifications



© SAP AG HR260 9-407
© SAP AG 2006
Combined Anal ysis - Headcount



Þ A BW Cockpit with four BW reports is displayed in the headcount area. The BW Cockpit is
displayed in a separate window.
Þ You can use the dropdown list to adjust the data period:
º Current month
º Last quarter
º Last 12 months
Þ The headcount is graphically displayed for each of these four reports. For more detailed
information, double-click on the graphic.
Þ Headcount details:
Line managers choose the "Detail" icon to display a new view with details on the selected
group.

© SAP AG HR260 9-408
© SAP AG 2006
Combined Anal ysis - Illness and Overtime



Þ You can use the Illness and Overtime area to get an overview of the illness and overtime status
as well as the costs thus incurred.
Þ This BW Cockpit includes four queries:
º Illness Rate: This query displays the relationship between illness hours and planned
working hours within the selected period.
º Overtime Rate: This query displays the relationship between overtime and planned
working hours within the selected period.
º Illness Costs: This query displays the number of illness hours and the resulting illness costs
within the selected period.
º Overtime Costs: This query displays the amount of overtime and the resulting overtime
costs within the selected period.

© SAP AG HR260 9-409
© SAP AG 2006
Combined Anal ysis - Qualifications



Þ The qualifications area gives you an overview of qualifications, their average valuation, and
postings for training tasks.
Þ Qualifications: This query shows you all qualifications for the active employee. (Status
employment = 3, employee group = 1)
Þ Course participation and cancellations: This query shows an evaluation of course
participations and cancellations with all cost factors in two different time views.


© SAP AG HR260 9-410
© SAP AG 2006
MSS Report Selection Based on MDT Customizing
Many customers that implement the Manager‘s Desktop (MDT)
application offer line managers their own reports within MDT
If you want to implement Manager Self-Service (MSS), the following
question is often asked: Is it possible to continue using the reporting
available for line managers in MDT in MSS?
SAP does not provide a migration tool, but you do not lose your work
from MDT
In the reports service SAP makes it possible to continue using the user-
defined reports made available for line managers for MDT
Within the SAP standard system there is an example scenario that can
be used in MSS and that customers can easil y adjust. You can, of
course, create your own MDT scenarios with your own reports
It is also possible to use reporting for MSS from MDT Customizing, even
if you did not previousl y use MDT




© SAP AG HR260 9-411
© SAP AG 2006
Report Selection in MSS
Categories
(Subcategories in MDT
Customizing)
Executable Functions



Þ The following pages explain MSS Customizing:
º Creating a new subcategory
º Including a report within the reporting workset

© SAP AG HR260 9-412
© SAP AG 2006
Example
Þ MDT Customizing is relevant for creating new subcategories and
assigning new reports.
Þ Assume that you want to add the organization category to the standard
report selection list and you want to assign reports that evaluate
organizational management to this category.
Þ RHFILLPOS: The report cumulates the attrition periods of positions that
are assigned to a particular organizational unit.
Þ RHSBESS00: The report generates a staffing assignment plan.
Þ You must:
¤ Create a new function code in the T77MWBFCD table. This function
code specifies the new subcategory and contains two additional
codes that include the reports to be linked.
¤ Assign the function codes to the existing scenario (RPT0) already
used in Manager Self-Service.




© SAP AG HR260 9-413
© SAP AG 2006
Create Function Codes for Enhancing the Report List
Table T77MWBFCD
Table T77MWBFCD



Þ You want to enhance the overview tree for reports with a new report folder.
Þ Switch to IMG, and choose the path Personnel Management -> Manager’s Desktop ->
Enhancements of Function Codes -> Determine Function Codes.
Þ In this table (T77MWBFCD) you enter a new function code for the new subcategory
Organization, and for each report you want to add.
Þ Choose New Entries, or copy an existing entry to create a new function code.

© SAP AG HR260 9-414
© SAP AG 2003
Create a Function Code for New Subcategory
Table T77MWBFCD
Table T77MWBFCD
Name of function code
Name of function code
Text will be displayed
in MSS
Text will be displayed
in MSS
Determines that this is
not an executable
function, but a
subcategory to group
executable functions
Determines that this is
not an executable
function, but a
subcategory to group
executable functions



Þ To create the new subcategory Organization, make the entries shown in the screen.
Þ Note: function code name must be created in the customer name space.
Þ Save your entries.



© SAP AG HR260 9-415
© SAP AG 2006
Create Function Code for Report RHFILLPOS
Table T77MWBFCD
Table T77MWBFCD
Determine a new
function code for report
RHFILLPOS
Determine a new
function code for report
RHFILLPOS
Determines that this
function code is a
report
Determines that this
function code is a
report
The Based on
Organizational Structure
indicator is set for all
function codes that are
applied to organizational
objects.
The Based on
Organizational Structure
indicator is set for all
function codes that are
applied to organizational
objects.
The report is object type-
specific and can only be
called using a certain
object type.
The report is object type-
specific and can only be
called using a certain
object type.
RHFILLPOS



Þ An organizational structure forms the basis of the RHFILLPOS report. Certain object types
(organizational units and positions) can start the report. On the basis of this structure, the
system collects all objects, organizational units and positions, and displays the appropriate
data for the positions found.
Þ Object type-specific:
º Set this indicator if you want the function to only be available for certain object types. You
can specify the corresponding object types in the section Enhancement of Function
Codes in the Customizing activity Define Object Type-Specific Function Codes.
Þ Choose New Entries to create a new function code, or to copy an existing entry.
Þ Note: You must enter the name of the function code in the customer namespace.
Þ Save your entries.

© SAP AG HR260 9-416
© SAP AG 2006
Create a Function Code for Report RHSBES00
Table T77MWBFCD
Table T77MWBFCD
Create a new function
code for the report
RHSBES00
Create a new function
code for the report
RHSBES00
Determines that this
function code is a
report
Determines that this
function code is a
report
The Based on
Organizational
Structure indicator is
set for all function
codes that are applied
to organizational
objects
The Based on
Organizational
Structure indicator is
set for all function
codes that are applied
to organizational
objects
The report is object
type-specific and can
onl y be started with a
certain object type
The report is object
type-specific and can
onl y be started with a
certain object type



Þ This report is based on the organizational structure. The report can only be started with object
type org unit. Along the structure the system collects all objects (org units and positions) and
displays the appropriate data.
Þ Object type specific:
º Set this indicator if you want the function only to be available for certain object types. You
can specify the corresponding object types in the customizing activity Define Object-
Specific Function Codes in the Enhancement of Function Codes section.
Þ The report RHSBES00 can only be started with org units.
Þ To create a new function code for a report choose New Entries or copy an existing entry.
Þ Note: function code name must be created in the customer name space.
Þ Save your entries

© SAP AG HR260 9-417
© SAP AG 2003
Entries in Table T77MWBFCD
Table T77MWBFCD
Table T77MWBFCD
Results
Results




© SAP AG HR260 9-418
© SAP AG 2003
Define Object Types for Object Type-Specific
Function Codes
Table T77MWBFCO
Table T77MWBFCO
Results
Results



Þ For some functions, only special types of organizational objects (persons, positions etc.) may
be appropriate. It also may be useful that a function stands for different function modules or
reports depending on the type of the argument. These restrictions are stored in T77MWBFCO.
Þ Enter the function code that you previously flagged as object type-specific.
Þ Enter the object type that the function code is to apply to. If there is more than one object type
per function code, you must make separate entries.
Þ In the FUNCTION MODULE and PROGRAM NAME fields, enter the function module or
the report that is called up by the corresponding function code.


© SAP AG HR260 9-419
© SAP AG 2006
Assigning Function Codes to a Scenario Used in
MSS
Table T77MWBFCH
Table T77MWBFCH
MDT Scenario RPT0 Is Used
In the MSS Standard
Delivery
MDT Scenario RPT0 Is Used
In the MSS Standard
Delivery




© SAP AG HR260 9-420
© SAP AG 2006
Assign Executable Functions and Subcategories
Table T77MWBFCH
Table T77MWBFCH
Theme Categories
Theme Categories
Subcategories All Assigned
to the Same Theme Category
MSS_HOME
Subcategories All Assigned
to the Same Theme Category
MSS_HOME
Executable Functions All
Assigned to Same Subcategory
TRAIN
Executable Functions All
Assigned to Same Subcategory
TRAIN



Þ In table T77MWBFCH, define the hierarchy for the report tree. The report tree structure is
based on the function codes defined in table T77MWBFC. The functions that cannot be
executed (categories and subcategories) structure the report tree.
Þ The hierarchy is structured as follows:
Þ A function code of type Start Page(theme category) functions as a node on the highest level
(root) of the report tree. Only one theme category is used in MSS.
Þ Subcategories, function codes of type Node, or executable functions are arranged on the
second level.
Þ In MDT, a subcategory can include further subcategories or executable functions. In MSS,
subcategories are always assigned to the same theme category and can only include executable
functions.
Þ In the example above, the subcategory Train includes 6 reports.
Þ The name of the scenario is entered in the first field.
Þ The name of the theme category (enter STARTPAGE), or subcategory - function that cannot
be executed - (enter NODE) is displayed in the Higher-Level Function Codecolumn. As the
category corresponds to the entry on the highest level of the report tree, there is no entry for
this category in the Higher-Level Function Codefield.
Þ Using the entry in the Number column, you can specify the order in which the theme
categories are displayed on the initial screen. Furthermore, you can specify the order in which

© SAP AG HR260 9-421
subcategories and executable functions are displayed on a hierarchy level of the function tree
in the left-hand area of the screen.
Þ Enter the name of the individual function codes in the Function Codecolumn.

© SAP AG HR260 9-422
© SAP AG 2006
Enhance Scenario RPT0 Used in MSS I
Scenario Used in MSS
Theme Category to Which You
Want to Assign the New
Subcategory
Determine the Order in Which
the Subcategories Are
Displayed in the Dropdown Box
Enter the Function Code for the
New Report



Þ To enhance the scenario used in MSS with two reports and the new category "Organization",
choose New Entry, or copy an existing entry.
Þ To assign the new subcategory to the scenario used in MSS, enter RPT0 as the application
scenario.
Þ In the Function Code field, enter the theme categories that you want to assign the new
category to. As only one theme category is permitted in the MSS scenario, you must specify
the theme category MSS_HOME.
Þ By entering a number in the sequence field, you determine the order in which the categories in
the Report Selection dropdown box are displayed in MSS.

© SAP AG HR260 9-423
© SAP AG 2006
Enhance Scenario RPT0 Used in MSS II
Scenario Used in MSS
New Subcategory the Report Is
Assigned to
Determine the Order in Which
the Reports Are Listed in the
Report List
Enter the Function Code for the
New Report



Þ The function codes of reports are assigned to subcategories in the figure above. The order of
reports within the subcategory is also determined.

© SAP AG HR260 9-424
© SAP AG 2006
Entries Created in Table T77MWBFCH
T77MWBFCH



Þ The figure above shows the hierarchical representation of the entries.

© SAP AG HR260 9-425
© SAP AG 2006
New Subcategories in the MSS Report Selection I
New Subcategory
Organization



Þ You can see the newly created subcategory in the Enterprise Portal.

© SAP AG HR260 9-426
© SAP AG 2006
New Subcategories in the MSS Report Selection II
New Reports in the
Organization Subcategory



Þ Here you can see the new reports within the organization subcategory.

© SAP AG HR260 9-427
© SAP AG 2006
Incorporating an SAP Query
A query is identified using these
three parameters. If you want to
use the query PHONE_LIST from
the user group /SAPQUERY/H2,
which belongs to the global work
area (X), you should enter the
value
X*/SAPQUERY/H2/PHONE_LIST
in the URL field.
<Work Area>*
<User Group>*
<Query Name>
Web Address
(URL)
This enables the system to
identify that it is a query.
*SAPQUERY* Program Name
REPO Type of
Function Code
Type
Note Value Description Field Name



Þ In addition to the function code types supported by Manager’s Desktop, you can also include
SAP queries by defining a function code in the detail screen (see above). For this, refer to the
Manager’s Desktop IMG under Enhancement of Function Codes → Define Function Codes
→ Define Function Codes for Manager's Desktop (table T77MWBFCD).

© SAP AG HR260 9-428
© SAP AG 2003
Easy Customizing using the Wizard (I)
Þ Using the Customizing wizard, you can enhance the range
of functions in the Manager’s Desktop.



Þ You can use the Customizing wizard to enhance the functions that are arranged in a function
tree on the left side of the Manager’s Desktop screen. You can only enhance functions based
on an existing Manager's Desktop scenario.
Þ You can enhance structural functions (subject categories and subcategories) and functions
executed by the user (reports, transactions, URLs).

© SAP AG HR260 9-429
© SAP AG 2003
Easy Customizing using the Wizard (III)
Working area
Progress &
navigation area
Information area
Information
link
Progress
indicator
Navigation
link



Þ The wizard is divided into the following three screen areas:
Þ Progress and navigation area: the system displays the steps you must take to create functions.
The current step in the list is always highlighted. Navigation links help you to navigate
directly to a particular step.
Þ The information area contains instructions regarding the current step and links to further
information.
Þ You make the entries proposed by the wizard in the working area.

© SAP AG HR260 9-430
© SAP AG 2003
Easy Customizing of Subcategory - Wizard (IV)
MSS0



Þ Add a subcategory:
Þ In the first step, you specify the function type (theme category, subcategory or executable
function) you want to create. The example here shows a subcategory (directory in the function
tree).
Þ In the second step, you enter an existing scenario in which you want the function to appear. In
addition, you enter a technical name and a descriptive text for the new function. The
descriptive text appears later in the Manager Self-Service function tree.
Þ In the third step, you choose the theme category (the MSS standard delivery is based on theme
category MSS_HOME) or, if you wish a subcategory in which you want to position the new
subcategory.
Þ In the fourth step, you either save your entries, which ends the program, or continue by
creating another function.

© SAP AG HR260 9-431
© SAP AG 2003
Easy Customizing of Exec. Function - Wizard (V)
MSS0



Þ Add an executable function:
Þ In the first step, you specify the function type (theme category, subcategory or executable
function) you want to create. The example here shows an executable function.
Þ In the second step, you enter an existing scenario in which you want the function to appear. In
addition, you enter a technical name and a descriptive text for the new function. The
descriptive text appears later in the Manager Self-Service function tree.
Þ In the third step, you choose the theme category (and, if you wish, a subcategory) in which
you want to position the new executable function.
Þ In the fourth step, you enter the type of executable function you want to create (transaction,
report, URL, and so on) and the technical name of the function. For example, if you want to
add a report, choose the function type Report and enter the existing technical name of the
report (for example, RHSBES00).
Þ Some functions can be object type-specific, in other words they can only be applied to certain
object types (for example Change Position). If you want to add such a function, you must also
set the indicator Function is Object Type-Specific.

© SAP AG HR260 9-432
© SAP AG 2003
Easy Customizing of Exec. Function - Wizard (VI)
Þ Customizing an object type-specific function



Þ If the new function is object type-specific, you must carry out a further step, where you enter
the object type(s) for which the function is valid. You make one entry for each object type.
Þ In the final step, you either save your entries, which ends the program, or continue by creating
another function.

© SAP AG HR260 9-433
© SAP AG 2006
Technical iView Information I
sap.xss.rpt.scenario=RPT0&
sap.xss.rpt.viewgroup=REPORTING&
sap.xss.rpt.visiblerowcount=0
Select Entry in View V_T7XSSSERRES
MSS Scenario
In homepage framework Customizing,
determine the parameters which call
the reporting workset.
The associated iView is:
com.sap.pct.mss.hcm.serv_reporting



Þ Parameter: sap.xss.rpt.scenario
º Define the scenario that creates a list of available reports. In the standard delivery, the
standard scenario is RPT0. The value of the sap.xss.rpt.scenario parameter is the MDT
scenario. If, for example, you want to use the standard scenario, set the parameter:
sap.xss.rpt.scenario=RPT0.
Þ Parameter: sap.xss.rpt.viewgroup
º Parameter sap.xss.rpt.viewgroup defines the OADP view group. This view group contains
at least one Organizational Management view ID. Organizational Management view IDs
determine the list of Organizational Management objects, such as employees and
organizational units. For more information, see Configuring the Object and Data Provider.
Þ sap.xss.rpt.visiblerowcount: (optional)
º In this parameter you determine the number of rows displayed in the object selection table.
If you do not enter a value here, the default value for the parameter is displayed.
Þ sap.xss.rpt.emptyselforbidden: (optional)
º If at least one object has to be selected to run the report, set the value of the parameter to
true. The default value for the parameter is false.

© SAP AG HR260 9-434
© SAP AG 2006
Technical iView Information II
Links to BW Reports
com.sap.pct.mss.hcm.bw.headcount
com.sap.pct.mss.hcm.bw.illness_overt
ime
com.sap.pct.mss.hcm.bw.skills



Þ The Reporting area provides line managers with the following SAP Business Information
Warehouse(SAP BW) Content in the MSS Business Package on separate pages:
Þ The Headcount page (com.sap.pct.mss.hcm.bw.headcount) includes the following
applications:
Þ Headcount (com.sap.pct.mss.hcm.bw.wt_hdc)
Þ Headcount FTE (com.sap.pct.mss.hcm.bw.wt_hdcfte)
Þ Entries (com.sap.pct.mss.hcm.bw.wt_ent)
Þ Leavers (com.sap.pct.mss.hcm.bw.wt_leav)
Þ The I llness and Overtime page (com.sap.pct.mss.hcm.bw.illness_overtime) contains the
following applications:
Þ Illness Rate (com.sap.pct.mss.hcm.bw.wt_illra)
Þ Illness Costs (com.sap.pct.mss.hcm.bw.wt_illcst)
Þ Overtime Rate (com.sap.pct.mss.hcm.bw.wt_ovr)
Þ Overtime Costs (com.sap.pct.mss.hcm.bw.wt_ovc)
Þ The Skills page (com.sap.pct.mss.hcm.bw.illness_skills) includes the following applications:
Þ Number of Qualifications (com.sap.pct.mss.hcm.bw.wt_qual)
Þ Average Proficiency of Qualifications (com.sap.pct.mss.hcm.bw.wt_avqu)

© SAP AG HR260 9-435
Þ Business Event Attendance and Costs (com.sap.pct.mss.hcm.bw.wt_trp)
Þ Business Event Cancellations and Costs (com.sap.pct.mss.hcm.bw.wt_trc)

© SAP AG HR260 9-436
© SAP AG 2006
Technical iView Information III
Illness and Overtime Page
IViews for Illness and Overtime Page



Þ In this figure you can see how the appropriate iViews for BW reports are assigned in the PCD
(Portal content directory) of the illness and overtime page.
Þ For more information about SAP BW Web templates and SAP BW queries on which the BW
Web applications listed above are based, see the documentation for SAP BW. See the SAP
Help Portal (Internet address help.sap.com), under Documentation -> SAP NetWeaver -> SAP
Business Information Warehouse -> SAP BI Content 3.5.1 -> Business Content -> Human
Resources Management -> Personnel Administration, or Personnel Development, or Time
Management, or Payroll or Training and Event Management -> Web Templates.

© SAP AG HR260 9-437
© SAP AG 2006
Technical iView Information IV
Name of BW Query
System
Alias



Þ This iView graphically displays the illness costs of employees when using the Information
Consumer Pattern (ICP) in the first view, and enables further detailed analyses. The following
time views are available: current month, previous month / current month, last 4 quarters, and
last 12 months. The report is run according to organizational units.
Þ This iView is based on a Web template from the component SAP BW. For more information,
see help.sap.com -> SAP NetWeaver -> Release '04,and after selecting a language, under SAP
NetWeaver -> Information Integration -> SAP Business Information Warehouse-> BI Content
-> Personnel Management -> Payroll -> Web Templates -> Illness Costs (Charts).
Þ The technical prerequisites for this iView are:
Þ SAP BW 3.5/BI Content 3.5.2 Add-On
Þ In the SAP BW system, the content of the BW roles SAP_BW_0ROLE_0162 and
SAP_BW_BCT_GENERI C_TEMPLATES has been activated.

© SAP AG HR260 9-438
© SAP AG 2006
Information on Setting Up Reporting in MSS



Þ For detailed information about setting up reporting in MSS, use the quick link
http://service.sap.com/mss on SAP Service Marketplace. Start the Business Package
documentation.

© SAP AG HR260 9-439
© SAP AG 2006
¤ Explain the concept of reporting in MSS
¤ Explain the relationship between MSS and MDT
¤ Adjust the reporting workset and incorporate new
elements in the workset
You should now be able to:
Reporting: Conclusion




© SAP AG HR260 9-440
Exercise 1


Unit: Reporting

I n this exercise:
Familiarize yourself with the Reporting workset.
Examine the technical requirements for MSS Reporting
Describe the technical settings in order to include a custom-
developed report


Log on to the Portal server and the mySAP ERP back-end
system. Use the log-on information provided.


1 Use the Reporting workset to determine the birthdays of your directly subordinate
employees.

2 What infrastructure component do you need if you want to display mySAP ERP
reports with the MSS Reporting workset?

3 Do you need to develop a new iView if you want to include a custom-developed
mySAP ERP report in the Reporting workset?

4 What kind of information can the Reporting workset display?

5 If you already use Manager’s Desktop what do you have to do to migrate this
content to MSS?


© SAP AG HR260 9-441

© SAP AG HR260 9-442
Solutions 1


Unit: Reporting

1 Use the Reporting workset to determine the birthdays of your directly subordinate
employees.
Select the Reporting tab page in the detailed navigation. Choose Birthday List
under the entry SAP Queries in the Report Selection. Choose all employees in the
integrated Team Viewer in the Selection Criteria iView. Select two employees in
the list created. Select Start Report.

2 What infrastructure component do you need if you want to display mySAP ERP
reports with the MSS Reporting workset?
ITS

3 Do you need to develop a new iView if you want to include a custom-developed
mySAP ERP report in the Reporting workset?
No. You can customize the MDT to include a report in the MSS workset.

4 What kind of information can the Reporting workset display?
mySAP ERP reports, BW queries, mySAP ERP queries, HIS information, mySAP
ERP transactions.

5 If you already use Manager’s Desktop what do you have to do to migrate this
content to MSS?
You can reuse this Customizing for MSS.


© SAP AG HR260 9-443

© SAP AG HR260 9-444
Exercise 2


Unit: Reporting
Topic: Reporting Enhancement

At the conclusion of this exercise, you will be able to:
• Include a report in the reporting workset


Your manager wants to start the RHVOPOS0 and RHSBES00
reports in the Enterprise Portal. These reports are not yet
permitted for the Enterprise Portal. Provide your manager with
these reports in the reporting workset.

1 Enhance your manager’s report selection in the Enterprise Portal.
Use the RHVOPOS0 and RHSBES00 reports.
The RHVOPOS0 report displays the vacant positions assigned to a particular
organizational unit.
The RHSBES00 report generates a staffing assignment plan.
1-1 First, create a new subcategory.
You must enter the name of the function code in the customer namespace
(Z*, Y*).
1-2 Create two function codes of the type “REPO” for the reports mentioned
above.
The RHVOPOS0 report forms the basis of an organizational structure.
Certain object types (organizational units and positions) can start the
report. On the basis of this structure, the system collects all objects,
organizational units and positions, and displays the appropriate data for
the positions found.
Do the same for the RHSBES00 report.

2 The programs mentioned above are only relevant for object types S and O. Mark
the function codes of the type REPO as object-type specific.
2-1 Define your previously created function codes according to an object type
(O, S) – Table T77MWBFCO.


© SAP AG HR260 9-445
3 In table T77MWBFCH, define the hierarchy for the report tree. The report tree
structure is based on the function codes defined in the T77MWBFCD table.
3-1 Now store your structure in the RPT0 scenario.

4 Check your function codes in the Enterprise Portal.
Call the reporting workset in the Enterprise Portal and execute the reports.





© SAP AG HR260 9-446
Solutions 2


Unit: Reporting
Topic: Reporting Enhancement

1 Enhance your manager’s report selection in the Enterprise Portal.
Use the RHVOPOS0 and RHSBES00 reports.
The RHVOPOS0 report displays the vacant positions assigned to a particular
organizational unit.
The RHSBES00 report generates a staffing assignment plan.
Customizing:
Personnel Management → Manager’s Desktop → Enhancement of Function
Codes → Define Function Codes → Define Function Codes for Managers'
Desktop
1-1 First, create a new subcategory.
In the table (T77MWBFCD), enter a new function code for the new
subcategory XX Organization (XX = group number) and for each report
you want to add. Choose New Entries, or copy an existing entry to create a
new function code.
You must enter the name of the function code in the customer namespace
(Z*, Y*).
Field Name Contents
Function Code ZXX_ORGANISATION (XX = group number)
Text XX – Organization (XX = group number)
Type NODE
Save your entries.
If you are asked for a transport request number, create a transport request.

© SAP AG HR260 9-447
1-2 Create two function codes of the type “REPO” for the reports mentioned
above.
The RHVOPOS0 report forms the basis of an organizational structure.
Certain object types (organizational units and positions) can start the
report. On the basis of this structure, the system collects all objects,
organizational units and positions, and displays the appropriate data for
the positions found.
Choose New Entries to create a new function code, or to copy an existing
entry.
Field Name Contents
Function Code ZXX_ RHVOPOS0
(XX = group number)
Text XX – Organization
(XX = group number)
Type REPO
Organization Structure-Based Select
Object Type-Specific Select
ProgramName RHVOPOS0
Save your entries.
If you are asked for a transport request number, create a transport request.
Do the same for the RHSBES00 report.

2 The programs mentioned above are only relevant for object types O and S. Mark
the function codes of the type REPO as object-type specific.
Customizing:
Personnel Management → Manager’s Desktop → Enhancement of Function
Codes → Define Object Type-Specific Function Codes
2-1 Define your previously created function codes according to an object type
(O, S) – Table T77MWBFCO.
Field Name Contents
Function Code ZXX_RHVOPOS0
(XX = group number)
Object Type O
ProgramName RHVOPOS0
Save your entries.
Repeat the entries for function code ZXX_ RHSBES00. Also make the
changes for object type S.
If you are asked for a transport request number, create a transport request.

© SAP AG HR260 9-448
3 In the T77MWBFCH table, define the hierarchy for the report tree. The report
tree structure is based on the function codes defined in the T77MWBFCD table.
Customizing:
Personnel Management → Manager’s Desktop → Enhancement of Function
Codes → Define Structure of Function Codes → Define Function Code
Hierarchies
3-1 Now store your structure in the RPT0 scenario.
Field Name Contents
Application Scenario RPT0
Function Code MSS_HOME
Sequence 10 + group number
Function Code ZXX_Organization –
(XX = group number)

Application Scenario RPT0
Function Code ZXX_Organization –
(XX = group number)
Sequence 1
Child Nodes Function Code ZXX_ RHVOPOS0
(XX = group number)

Application Scenario RPT0
Function Code ZXX_Organization –
(XX = group number)
Sequence 2
Child Nodes Function Code ZXX_ RHSBES00
(XX = group number)
Save your entries.
If you are asked for a transport request number, create a transport request.

4 Check your function codes in the Enterprise Portal.
Call the reporting workset in the Enterprise Portal and execute the reports.




© SAP AG HR260 10-449
© SAP AG 2006
The Headcount Workset: Overview Diagram
Unit 1 MSS Overview
Unit 2 Manager Self-Service Fundamentals in the Enterprise Portal
Unit 3 The Employee Review Workset
Unit 4 The Compensation Workset
Unit 5 The ESS Workset in MSS
Unit 6 The Team Calendar Workset
Unit 7 The Personnel Change Requests (PCR) Workset
Unit 8 The Recruitment Workset
Unit 9 The Reporting Workset
Unit 10 The Headcount Workset
Unit 11 Team Viewer
Appendix Homepage Framework




© SAP AG HR260 10-450
© SAP AG 2006
¤ Quota planning – process
¤ Quota planning
¤ Transfer headcount
¤ Customizing for quota planning
¤ Follow-up activities
Contents:
Quota Planning (Also Headcount Planning)




© SAP AG HR260 10-451
© SAP AG 2006
¤ Describe the quota planni ng process
¤ Describe the headcount transfer process
¤ Adjust the follow-up activities
After completing this unit, you will be able to:
Quota Planning: Objectives




© SAP AG HR260 10-452
© SAP AG 2006
¤ Web-enabled processes are fundamentall y important
to the successful implementation of MSS. Therefore,
implement the scenario for quota planning in the
manager Portal.
Headcount: Business Scenario




© SAP AG HR260 10-453
© SAP AG 2003
Headcount Planning - Process
Headcount Planning
Process
¤ Line manager determines the positions required for the planning
period (first plan for the year 2004)
¤ Managers transfer the planning data from the HR system to the key
statistical figures in the FI-CO system.
¤ Consolidation of enterprise-wide planning: first plan can no longer
be changed
¤ Planned position requirements /costs are too high. A second planning
cycle takes place
¤ Second planning cycle: manager determines the required positions
in the second plan
¤ Managers transfer the planning data from the HR system to the key
statistical figures in the FI-CO system. Consolidation of the second
round of enterprise-wide planning: second plan can no longer be
changed.
¤ Requirements in second plan are approved
¤ Positions are created or reduced using a report



Þ Using this function, managers can plan required positions per job centrally for the
organizational units for which he or she is directly responsible.
Þ With the Headcount/Quota transfer functionality, managers can transfer the results of the
headcount planning in the form of statistical key figures to Accounting.
Þ The system transfers to Accounting (AC) the planning results for the selected cost center of the
current or of a previous headcount planning per fiscal year. In this way, the job-related
headcount planning is summarized in one statistical key figure for each cost center.
Þ After reviewing, the board decided to lower the number of required positions. As a result,
managers have to perform a second round of planning; the first round is stored in the history).

© SAP AG HR260 10-454
© SAP AG 2006
Headcount - Overview Page
Select Headcount Planning



Þ The system returns the current number of positions linked with a job for which the relevant
line manager within an organizational unit is responsible.
Þ The quota planning process can include one or more runs.
º Example:
º In the first run, line managers plan the number of positions available for a particular
organizational unit for which they are responsible. After the first planning run is complete,
the plan is consolidated on a company-wide basis. Superiors can no longer change the first
planning.
º If the number of planned positions is too high there is a second planning round.
º In the second planning phase line managers must modify their planning to fit requirements.
º Then the second planning can be approved. Quota planning is now complete.
Þ In the back-end system, you can now:
º generate additional positions
º restrict superfluous positions, or
º indicate a position as obsolete if it is still occupied by an employee
Þ The overview page includes quota planning and transfer to CO.
Þ Headcount transfer allows line managers to release quota plans for transferring to CO. In CO
quota planning is necessary for statistical key figures.

© SAP AG HR260 10-455
© SAP AG 2006
Headcount Planning - Select Organizational Units
Select Organizational Unit



Þ In this step all organizational units that a line manager is responsible for are displayed in a list.
Þ The relevant cost center and name of the cost center are also shown
Þ Quota planning is created by organizational unit
Þ To select an organizational unit, highlight it and choose the Select Planning button

© SAP AG HR260 10-456
© SAP AG 2006
Headcount Planning - Select Planning Data
Select Planning Type and
Time Interval



Þ In this step, line managers choose the planning type and associated planning interval (for
example, monthly, quarterly, yearly).
Þ Planning type: A planning type is chosen for each planning run. In other words, it determines
which of the plans (first, second, or if required other planning) defined in Customizing is to be
used as a basis. Therefore, line managers can only plan those planning types indicated as
Current in Customizing.
Þ Time interval: You enter the time unit (for example, weeks, months, years) to be scheduled
for the required positions in the appropriate planning period (for example 01.01.2006-
31.12.2006). The periods and time units are defined in Customizing.
Þ Planning period: Is predefined in Customizing and displays the validity of the planning
period.
Þ After you enter the planning parameters, choose the Edit button and quota planning appears.

© SAP AG HR260 10-457
© SAP AG 2006
Headcount Planning - Enter Planning Data
You Can Enter the
Number of Required
Positions for each
Listed Job



Þ In this step you perform quota planning. The selected organizational unit and the planning
parameters are displayed under the road map.
Þ The planning table displays all jobs for the selected organizational unit.
Þ There are two rows available for each job:
º The first row (current) displays the number of positions assigned to the respective job
within the selected organizational unit.
º In the second row (new) line managers can plan, based on the respective job, how many
positions are required for the corresponding organizational unit in the predefined planning
period.
Þ If positions need to be planned for which there are no jobs within the selected organizational
unit, you can choose the Insert J ob button. Then you get a selection field which you can use to
search for additional jobs.
Þ It is also possible to completely delete positions by choosing the Delete J ob button.
Þ Planning often takes place on a monthly basis. To avoid entering the same number of required
positions in all cells (if the increase in all the cells in a row stays the same) line managers can
enter the number of positions in a cell and choose the Apply button. Using the changed cell as
a basis, all the other cells in this row are adjusted to fit the changed value.
Þ You can also change the number of positions by positioning the cursor in a cell and choosing
the Increaseor Decreasebutton. This increases or decreases the number of positions by 1.

© SAP AG HR260 10-458
Þ Choosing the Review button takes you to the next processing step.

© SAP AG HR260 10-459
© SAP AG 2006
Headcount Planning - Further Possibilities I
Enter Search Term



Þ If positions need to be planned for which there are no jobs within the selected organizational
unit, you can choose the Insert J ob button. Then you get a selection field which you can use to
search for additional jobs.
Þ It is also possible to completely delete positions by choosing the Delete J ob button.
Þ Planning often takes place on a monthly basis. To avoid entering the same number of required
positions in all cells (if the increase in all the cells in a row stays the same), line managers can
enter the number of positions in a cell and choose the Apply button. Using the changed cell as
a basis, all the other cells in this row are adjusted to fit the changed value.
Þ You can also change the number of positions by positioning the cursor in a cell and choosing
the Increaseor Decreasebutton. This increases or decreases the number of positions by 1.
Þ Choosing the Review button takes you to the next processing step.

© SAP AG HR260 10-460
© SAP AG 2006
Headcount Planning - Other Options II
Change to
Number of
Positions



Þ Planning often takes place on a monthly basis. To avoid entering the same number of required
positions in all cells (if the increase in all the cells in a row stays the same), line managers can
enter the number of positions in a cell and choose "Apply". If you use the changed cell as a
basis, all the other cells in this row are adjusted to fit the changed value.
Þ You can also change the number of positions by placing the cursor in a cell and choosing
"Increase" or "Reduce". This increases or decreases the number of positions by 1.
Þ To move to the next processing step, choose “Review".

© SAP AG HR260 10-461
© SAP AG 2006
Headcount Planning - Check Entries



Þ Before saving the planning, line managers can check their changes in this step.
Þ If everything is correct managers can save the plan by choosing the Savebutton.

© SAP AG HR260 10-462
© SAP AG 2006
Headcount Planning - Complete Planning
Navigate to a
Different Page



Þ After saving quota planning, the system informs the line manager whether the changes were
successful.
Þ If saving was successful, a success message appears under the road map, if it was not
successful an appropriate error message is displayed.
Þ There are also other links on the page:
º Go to New Headcount Planning: Takes line managers to the selection of further
organizational units to introduce additional planning processes
º Go to Planning Transfer: Here line managers can forward quota planning transfer to CO
º Go to Headcount Homepage: This link takes line managers to the initial screen for quota
planning
º Go to My Staff Homepage: This link takes line managers to the overview page of the My
Staff role

© SAP AG HR260 10-463
© SAP AG 2006
Quota Planning Reports
Quota Planning Reports



Þ The following reports are available for quota planning:
º In report RH_GEN_AND_RED_FROM_BUDGET, depending on the scheduled job
budget, new positions are generated, or superfluous jobs are indicated as outdated.
º In report RH_COPY_BUDGET_PLANNING, position data is copied from one type of
planning to another.
º In report RH_COPY_ACTUAL_TO_BUDGET, current job budget data is copied to a
planning type.
º In report RH_FREEZE_BUDGET, job budget data planned for a particular period up to a
certain key date is frozen.
º In report RH_DELETE_FREE_POSITIONS, positions generated in quota planning, but
that remain unoccupied up to a certain key date, are deleted.

© SAP AG HR260 10-464
© SAP AG 2003
Generate Positions
Generate new positions
for org unit IT Computer,
first plan (Documentation)
Generate new positions
for org unit IT Computer,
first plan (Documentation)



Þ Using this report you can generate positions based on executed headcount headcount planning.
Þ Using the Planning typeparameter you can specify the planning type in which positions
should be generated.
Þ Using the Automatic reduction parameter you can specify that the system should not offer the
user a dialog box for selecting which positions should be reduced.

© SAP AG HR260 10-465
© SAP AG 2003
Generate Positions
Generate positions
Generate positions
Reduction required for one
position -> set position to
obsolete
Reduction required for one
position -> set position to
obsolete



Þ Using the Display list before generation parameter you can specify that the system should
show a list of those organizational units which have headcount planning.
Þ The user can then decide for which organizational units, positions should be generated. If the
parameter is not set, the number of positions is generated immediately.
Þ For those organizational units where a reduction is required, all the positions are listed. Via
List -> Reduction, you reach a dialog box in which you can make a position-specific entry
regarding reductions.

© SAP AG HR260 10-466
© SAP AG 2003
Reduce Positions



Þ Unoccupied positions marked as obsolete are immediately delimited.
Þ Occupied positions and those marked as obsolete are counted in full in the existing required
positions.

© SAP AG HR260 10-467
© SAP AG 2003
Headcount Planning - FTE
Þ A full-time equivalent (FTE) expresses planned capacity
in terms of full-time positions.
Þ This is calculated from the working time of the position
in relation to the working time valid for the superior
organizational unit.




© SAP AG HR260 10-468
© SAP AG 2006
Calculation in Positions/Full-Time Equivalents (FTE)
Positi on Positi on Positi on
Positi on Positi on Positi on
Working time
40 hrs/week
Working time
40 hrs/week
Positi on Positi on Positi on
Positi on Positi on Positi on
Working time
20 hrs/week
Working time
20 hrs/week
1.11 FTE 1.11 FTE 1.11 FTE
1 FTE 1 FTE 1 FTE
O.5 FTE O.5 FTE O.5 FTE
1 FTE 1 FTE 1 FTE
Org.Unit Org.Unit Org.Unit
Working time
36 hrs/week
Working time
36 hrs/week
Working time
40 hrs/week
Working time
40 hrs/week
Headcount Planning in FTEs
WORKT FTEQ X



Þ An FTE is the target capacity (expressed in full-time positions) and corresponds to the
relationship between the working time defined for a position and the working time defined for
the organizational unit to which the position is assigned.
Þ If you set the WORKT FTEQ switch to ‘X’, you specify that you want to perform headcount
planning using FTEs rather than positions. In that case you can use FTEs with up to two
places after the decimal point.
Þ If a position has a weekly working time of 20 hours, and the position’s superior organizational
unit has a weekly working time of 40 hours (saved in infotype 1011, Working Time), the
calculation is as follows: the working time of the position (20) is divided by the working time
of the organizational unit (40), giving an FTE value of 0.5.
Þ If, on the other hand, the position has a weekly working time of 40 hours, and the superior
organizational unit has a working time of 36 hours, the FTE has a value of 40/36 = 1.11.

© SAP AG HR260 10-469
© SAP AG 2006
Calculation in Positions/Full-Time Equivalents
(FTE)
WORKT
WORKT
FTEP
FTEQ
X
X
Calculation of value for FTE
Headcount planni ng i n FTEs
IT 0008 Capacity Utilizati on IT 0008 Capacity Utilizati on
Level 50% Level 50%
IT 0008 Capacity Utilizati on IT 0008 Capacity Utilizati on
Level 50% Level 50%
Positi on Positi on Positi on
Positi on Positi on Positi on
Positi on Positi on Positi on
50%
100%
Not staffed Not staffed
0.5 FTE 0.5 FTE 0.5 FTE
0.25 FTE 0.25 FTE 0.25 FTE
0 FTE 0 FTE 0 FTE



Þ Using the WORKT FTEP switch, you can specify that the value of an FTE should either be
determined solely on the basis of the the planned working time of the position (switch = ‘ ’),
or on the basis of the staffing percentage of the position in conjunction with the capacity
utilization level of the employee (person) (switch = 'X').
Þ Examples:
º If you have set WORKT FTEP - switch to ‘X’, there are also two possible scenarios:
Þ The position is not staffed, or staffed by a user.
º In this case, the value of the FTE is 0.
Þ The position is staffed by an employee (person).
º In that case, the value of the FTE is the product of the staffing percentage (A/B 008
relationship between S and P) and the capacity utilization level (stored in infotype 0008 of
Personnel Administration), where 100% corresponds to the value 1.
Þ Example:
º The staffing percentage is 100%, the capacity utilization level 50%. Following on from
this, the value for an FTE is 1 x 0.5 = 0.5. If the staffing percentage and capacity utilization
level were both 50%, the value of the FTE would be 0.5 x 0.5 = 0.25.

© SAP AG HR260 10-470
© SAP AG 2003
Headcount Planning – R/3 Customizing
Þ The key customizing steps include:
¤ View T77POSBUD (Position Budget) that allows for creation and
activation of the different Headcount planning types/rounds;
¤ Infotype 1019 (Headcount Data) has to be set up with appropriate
subtypes that are prerequisite for the T77POSBUD customizing;
¤ In addition, Headcount planning can be defined for calculations in FTE
equivalents. This feature of the 4.70 release allows managers to
enter decimal values for the headcount planning; e.g. Manager
has a 50% part-time job holder that can be represented as 0.5.



Þ R/3 Customizing
º For the Headcount Planning MDT Customizing use the following path: Personnel
Management ¼ Organizational Management ¼ Infotype Settings ¼ Quota Planning.
º To set up subtypes of infotype 1019 use the following path: Personnel Management ¼
Organizational Management ¼ Basic Settings ¼ Data Module Enhancement ¼ Infotype
Maintenance ¼ Maintain Subtypes
Þ Plug-In Customizing
º If you use Organizational Management and Accounting in two separate systems you must
set up the ALE scenario AC-HR.
º The Business Add-In adjusts the time-specific planning results to the corresponding
periods in CO and transfers the number of required positions per org units to FI-CO.
º This Business Add-In allows you to realize customer-specific requirements when
transferring required positions planning to CO.
º Example: For statistical key figures planning you want to distinguish between manager,
secretaries and administrators. Therefore you have to change the Business Add-In in a way
that data transfer not only includes number of required positions per org unit but also
number of required managers, secretaries and administrators.

© SAP AG HR260 10-471
© SAP AG 2006
Quota Planning Customizing in OM
Quota planning
Customizing is in
Organizational
Management.
There is no specific quota
planning Customizing for
MSS.



Þ There is no specific quota planning Customizing for MSS.
Þ You use ERP2004 Organizational Management Customizing for quota planning.

© SAP AG HR260 10-472
© SAP AG 2006
Create Planning Periods
Table T77POSBUD



Þ In this work step you define customer-specific subtypes of the quota planning (1019) infotype
and use them to define further planning types in addition to the existing planning types (First
Planning, Second Planning).
Þ In this work step you make the settings that refer to the definition of the type of planning and
planning period within quota planning.
Þ You choose a type of planning for each planning round, (you determine whether it is First
Planning or Second Planning and so on). The respective user can then only plan the type of
planning indicated as Current in this work step in their application scenario.
Þ The time interval is also entered (weeks, months, quarter, year) for which each of the required
positions need to be planned.
Þ Finally, the total planning period is predefined for which the user has to specify the respective
planning numbers for each planning session. Note that for performance reasons planning
periods should not be longer than three years.

© SAP AG HR260 10-473
© SAP AG 2006
FTE Switch Customizing
Table T77S0



Þ In this activity you make the settings that relate to calculating the required positions in full-
time equivalents (FTE).
Þ Furthermore, in this activity you can determine that the value for an FTE is determined related
to the staffing percentage of positions, taking the employment fraction of the employee
(person) into account.

© SAP AG HR260 10-474
© SAP AG 2006
Headcount - Planning Transfer
Transfer to CO Selection



Þ As soon as quota planning is released line managers can transfer their planning to cost
accounting (CO). CO needs this data to form statistical key figures. To start the Transfer line
managers choose Planning Transfer.

© SAP AG HR260 10-475
© SAP AG 2006
Planning Transfer - Select Planning
Selection of Planning Type to Transfer
to CO that Includes Corresponding Key
Figures



Þ You use this entry screen to fill the appropriate parameters for transferring to CO:
º Planning type
º Controlling area
º Fiscal year
Þ When you choose Select Cost Center, the page for selecting the cost center appears.

© SAP AG HR260 10-476
© SAP AG 2006
Planning Transfer - Select Cost Center
Select One or More Cost Centers
for Transferring Quota Planning to
CO



Þ Line managers have previously created the number of required future positions, or FTEs, for
the respective organizational unit and triggered the transfer for the statistical key figures to
CO.
Þ In the back-end system cost centers are assigned to organizational units or positions.
Assigning to a cost center can be passed on from one organizational unit to the next, and from
an organizational unit to a position. If a cost center is directly assigned an organizational unit
or position using relationship A011, the inheritance chain is broken. This means that object
types are assigned to the relevant cost centers and then pass on these assignments.
Þ On this screen you can see all cost centers for which the line manager is responsible. Line
managers can decide for which cost center the transfer to CO should take place. The released
quota planning data is then transferred to the module CO.
Þ Choosing the Review button takes you to the next data transfer step.

© SAP AG HR260 10-477
© SAP AG 2006
Planning Transfer - Check Data
Line Managers Can Check Whether the
Correct Parameters Were
Predetermined, Before the Data Is
Transferred



Þ The data transfer information is displayed here to be checked. If all data is correct you can
transfer the data to CO by choosing the Savebutton.
Þ This function is only an enhanced user interface for the report ABAP
(RHWPC_HDCN2SKF), which you use to transfer headcount. You can start this report in the
mySAP ERP system and it is similar to the user interface for transferring headcount.

© SAP AG HR260 10-478
© SAP AG 2006
Planning Transfer - Completion of Transfer
Navigate to a Different Page



Þ A notification on the screen confirms the successful release of data for the transfer. If errors
occur a qualified error message is displayed on the screen.
Þ After the data transfer, line managers can use the following links:
º Go to Next Data Transfer: create another data transfer for CO
º Go to Headcount Planning Homepage: this link takes line managers to the initial screen for
quota planning
º Go to My Staff Homepage: this link takes line managers to the overview page of the "My
Staff" role

© SAP AG HR260 10-479
© SAP AG 2006
Transfer to CO
Report RHWPC_HDCNT2SKF:
Data Transfer of Quota Planning Results to Accounting



Þ You use this report to post the planning results of the current quota planning by controlling
area and fiscal year to Accounting (AC). Job-related quota planning is aggregated into one
statistical key figure for each cost center. A second statistical key figure describes the
difference between quota planning and the current positions required.

© SAP AG HR260 10-480
© SAP AG 2006
Transfer Quota Planning
Þ When you transfer the quota planning results to CO the
system adjusts the time-specific planning results to fit
the relevant periods in CO.
The results are updated in CO.
Þ If the planning data is edited for the periods, the system reads
the relevant data in the CO system using a BAPI.
Þ As soon as the planning data is posted:
¤ the system reconciles posting data with CO data, using a synchronous
BAPI
¤ the system transfers the data asynchronousl y to the receiving
system using ALE
¤ the receiving system posts the data to the CO system




© SAP AG HR260 10-481
© SAP AG 2006
Planning Transfer Customizing
Table T77S0
Customizing of Quota
Planning



Þ You must set up the following switches in your HR system in table T77S0 (System
Table):
º SKFCO / COPLS (Planning source for CO data transfer) - You use this entry to
determine which accounting planning source to use for transferring data. You must
create the planning source in Customizing for accounting. In CO Customizing, the
planning source used must have a standardized setting (either 'X' or ' ') for each controlling
area at all times for the Add Values setting.
º SKFCO / KFACNT (Statistical Key Figure: Number of Positions (Change)) - This
statistical key figure describes the difference between quota planning and the
current positions required.
º SKFCO / KFBCNT (Statistical Key Figure: Number of Positions (Budget)) - This
statistical key figure describes quota planning (planned number of positions).
Þ The SAP standard system provides two key figures for transferring quota planning
results data to accounting using report RHWPC_HDCNT2SKF. They can be posted to
statistical key figures in accounting. You must enter the names of the statistical key
figures in accounting under the semantic abbreviations KACNT and KBCNT.

© SAP AG HR260 10-482
Þ The Business-Add-In enables you to implement customer-specific requirements when
transferring position quota planning to CO. For an example implementation, see the
class CL_IM_HRWPC00_HEADCNT2CO.
Þ For more information, see the documentation on the Manager Self-Service Business
Package, under Technical Description -> iView Pool -> Quota Planning.

© SAP AG HR260 10-483
© SAP AG 2006
Transfer Quota Planning - mySAP ERP
Customizing
Þ Plan Source for CO Data Transfer
¤ Maintain in view cluster VC_COPLNCTRL.
Þ Statistical key figures are master data in the Cost
Center Accounting module that you can maintain using
transaction KK02 or KAK2.



Þ Cost Planning: Plan Source for CO Data Transfer
Þ For transactions KK02 and KAK2, see the SAP Easy Access Menu, under: Accounting ->
Controlling -> Cost Center Accounting -> Master Data -> Statistical Key Figures -> Single
Processing or Accounting -> Controlling -> Cost Center Accounting
-> Master Data -> Statistical Key Figures -> Collective Processing.
Þ This entry specifies the accounting planning source to use for transferring data. The planning
source must first be defined in Customizing. In CO Customizing, the planning source must
always have the value ' ' in the Add Values setting for each controlling area.
Þ Statistical Key Figure: For transferring quota planning to CO using report
RHWPC_HDCNT2SKF, SAP provides two key figures that you can use for statistical key
figure planning in CO. The first statistical key figure is the planned headcount and the second
describes the difference between the actual and the planned headcount.
Þ You must record the name of the statistical key figure in T77S0, groups SKFCO KACNT and
SKFCO KBCNT.

© SAP AG HR260 10-484
© SAP AG 2006
¤ Describe the quota planning process
¤ Describe the headcount transfer process
¤ Adjust the follow-up activities
You should now be able to:
Headcount Workset: Conclusion




© SAP AG HR260 10-485
Exercises


Unit: Headcount/Quota Planning

I n this exercise:
• Familiarize yourself with the handling of the headcount/quota
planning workset.
• Familiarize yourself with MSS headcount/quota planning
Customizing.


Log on to the Portal server and the mySAP ERP back-end
system. Use the log-on information provided.


1 Where can you find the headcount/quota planning Customizing in
mySAP ERP?

2 What do you have to set up if you run Organizational Management and Accounting
in two different systems.

3 What is the key table for the mySAP ERP Customizing?

4 Conduct the headcount/quota planning process for your organizational unit and
increase the headcount of your first position to 2.



© SAP AG HR260 10-486

© SAP AG HR260 10-487
Solutions


Unit: Headcount/Quota Planning

1 Where can you find the headcount/quota planning Customizing in
mySAP ERP?
Personnel Management ¬ Organizational Management ¬ Infotype Settings ¬
Quota Planning

2 What do you have to set up if you run Organizational Management and Accounting
in two different systems.
ALE scenario AC-HR

3 What is the key table for the mySAP ERP Customizing?
T77POSBUD

4 Conduct the headcount/quota planning process for your organizational unit and
increase the headcount of your first position to 2.
Select the Quota Planning tab page. Select Quota Planning in the Detailed
Navigation iView on the left side. Choose the iView Quota Planning. Select your
organizational unit.
Insert a 2 in the line of the position in order to increase the planning. Save your
planning.





© SAP AG HR260 11-488
© SAP AG 2006
Team Viewer: Course Overview Diagram
Unit 1 MSS Overview
Unit 2 Manager Self-Service Fundamentals in the Enterprise Portal
Unit 3 Employee Review Workset
Unit 4 Compensation Workset
Unit 5 ESS Workset in MSS
Unit 6 Team Calendar Workset
Unit 7 Personnel Change Requests (PCR) Workset
Unit 8 Recruitment Workset
Unit 9 Reporting Workset
Unit 10 Headcount Workset
Unit 11 Team Viewer
Unit 12 Homepage Framework




© SAP AG HR260 11-489
© SAP AG 2006
Team Viewer
Þ Object and Data Provider
Þ Team viewer principles
Þ Team viewer customizing
Content:




© SAP AG HR260 11-490
© SAP AG 2006
Team Viewer: Goals
Þ Explain the benefit of the team viewer for your
managers
Þ Describe the principles of the Object and Data
Provider the team viewer is based upon
Þ Customize the team viewer
At the end of this unit you will be able to:




© SAP AG HR260 11-491
© SAP AG 2006
Team Viewer: Business Scenario
Þ Your MSS implementation should be easy to use for
your manager. Therefore, the group of employees
displayed should be adapted to their needs.
You have the task to determine their needs and to
customize the team viewer in order to fulfill them.




© SAP AG HR260 11-492
© SAP AG 2006
Team Viewer Based on Object and Data Provider
Eventing



Þ The Team Viewer provides managers with a list of employees who belong to their area of
responsibility. The basic prerequisite for the Team Viewer is HR Organizational Management.
All directly and indirectly reporting employees are determined along the organizational
structure. These employees are then displayed in the portal using the Team Viewer.
Þ The Team Viewer can be implemented with other iViews from the Business Package for
Manager Self-Service. When a manager selects a person in the Team Viewer, information
about this person is displayed in related iViews such as the Employee Profile. Some iViews,
including the Employee Profile iView, do not include a function for selecting personnel
numbers. Such iViews obtain the personnel number for which information is to be displayed,
using client eventing with the Team Viewer.
Þ That is, eventing takes place between the Team Viewer and other iViews. Eventing comprises
the following three mechanisms:
Þ When an employee is selected in the Team Viewer, other iViews (such as General Data,
Photo, and Skills) are loaded that display data on the selected employee.
Þ The first time the portal page is called with the Team Viewer (after the manager has logged
onto the portal), the first employee in the person list is displayed.
Þ The last employee to be selected is saved. When a manager navigates to a different portal page
and then returns to the original page, the last employee he or she selected and the relevant
information is displayed automatically in the related iViews.

© SAP AG HR260 11-493


© SAP AG HR260 11-494
© SAP AG 2006
Chief Posi tion
Org. Unit
Employee/
Person
The Employee Has
A Chief Positi on
IT 105 (Communication)
Assign an
SAP System ID
Start Evaluation Path
Start Evaluation Path
Manager Self-Service - Prerequisites
Start Object(s)
Start Object(s)
Area of Responsibility
Area of Responsibility



Þ To use all the functions of the Object and Data Provider in Manager Self-Service you must
have created the organizational plan of your enterprise in the Organizational Management
component, which includes displaying the organizational structure and staff assignments (the
assignment of persons or users to positions).
Þ A start evaluation path and a subsequent evaluation path are required for defining views. The
start evaluation path determines the start objects for the view. Starting from these start objects,
a subsequent evaluation path is used to determine a number of organizational objects.
Þ When managers log on to the system, their start evaluation path (user-person-chief position-
organizational unit) is used to determine all the organizational units for which they are
responsible. The organizational unit is used as the start object for the subsequent evaluation
path. Starting from the start object, a second evaluation path is used to determine along the
structure the organizational objects (organizational units, jobs, positions, persons, cost centers)
for which a manager is responsible.
Þ The relevant organizational objects (such as persons) are displayed in a list in the Team
Viewer.


© SAP AG HR260 11-495
© SAP AG 2006
Different Views of the Area of Responsibility
Exampl e: Two different views
from a manager' s area of
responsibility
+ Evaluation Path
SBESX
View: V_TWPC_V
+ Evaluation Path
SBESX
View: V_TWPC_V
Start Object(s)
Start Object(s)
Start Object(s)
Start Object(s)
+ Evaluation Path
MSSDIREC
View: V_TWPC_V
+ Evaluation Path
MSSDIREC
View: V_TWPC_V



Þ The Team Viewer enables managers to display different views of their area of responsibility,
for example:
º All Reports
º Direct Reports

© SAP AG HR260 11-496
© SAP AG 2006
Defining a View
Evaluation Paths
¤ Start Objects
¤ Structure
View (V_TWPC_V) View (V_TWPC_V) View (V_TWPC_V)
Technical Name
Column Framework
Use V_TWPC_V_C to Overwrite the SAP
Entries in V_TWPC_V
Use V_TWPC_V_C to Overwrite the SAP Use V_TWPC_V_C to Overwrite the SAP
Entries in V_TWPC_V Entries in V_TWPC_V



Þ In Object and Data Provider Customizing (Transaction SIMG_SPORT, Manager Self-
Service-> Object and Data Provider), you can overwrite the different views of the
area of responsibility that are provided for the user, or define new views.
Þ If you want to define a new view, choose New Entries and enter a technical name for
the new view.
Þ Enter a name for the view and the start evaluation path that determines the root object
for the second evaluation path.
Þ Alternatively, you can determine the root object(s) using a function module instead of
the start evaluation path. If you want to use a function module, enter the appropriate
function module in the Function Modules for Root Objects field and leave the
Evaluation Path for Root Objects field empty.
Þ Under Evaluation Path Objects, enter the second evaluation path that determines
along the structure the objects that are displayed in the Team Viewer.
Þ Table V_TWPC_V contains the views delivered by SAP. If you want to change the
delivered views, use the customer table, table V_TWPC_V_C.
Þ In the Column Group field, enter the column group under which a view is to be
displayed.

© SAP AG HR260 11-497
Þ In the Header Typefield you can specify a specific header type for your view (see
Column Framework).
Þ You can use the Delete Duplicatedisplay to determine that each object in the output
list is only output once. If, for example, one person is related to two positions in an
organizational unit, this person is displayed twice in the list.
Þ Exclude Manager: If you set this indicator, the system deletes the logged-on user and
the person assigned to this user (Communication infotype (0105)) from the output list.
Þ The system also deletes all users/persons from the output list who, together with the
logged on user (or the assigned person), are assigned to a chief position.

© SAP AG HR260 11-498
© SAP AG 2006
Grouping the Views: Define a View Group
View (V_TWPC_VG) View (V_TWPC_VG) View (V_TWPC_VG)
Views in
this Group
Use V_TWPC_VG_C to Overwrite the SAP
Entries in V_TWPC_VG
Use V_TWPC_VG_C to Overwrite the SAP Use V_TWPC_VG_C to Overwrite the SAP
Entries in V_TWPC_VG Entries in V_TWPC_VG
View Group
Appraisal
(Technical Name)
1
2



Þ The function for grouping organizational structure views allows you to group views and
determine the positions of the view within the group. The grouped views are available in the
Team Viewer and you can select them from a selection list.
Þ SAP provides you with a customer view in which you can define customer-specific
assignments of views to object types. You can find entries of the standard delivery in view
V_TWPC_VG (Grouping the Views).
Þ If you want to overwrite the standard entries, you must use the same key as in the standard for
each of your entries in the customer view, and change the remaining entries.
Þ Note that the sequence of the views may not be correct. This would be the case if you include
an additional view in the view group and give it a position number that has already been
assigned to a view in the standard delivery.

© SAP AG HR260 11-499
© SAP AG 2006
Object Types to Display in the List
View (V_TWPC_OTYPES) View (V_TWPC_OTYPES) View (V_TWPC_OTYPES)
View (V_TWPC_OTYPES_C) View (V_TWPC_OTYPES_C) View (V_TWPC_OTYPES_C)
Overwrite Entries in Table V_TWPC_OTYPES
Determine Object Type(s) per View



Þ Table V_TWPC_OTYPES defines the object types (persons, organizational units, positions,
and so on) that were determined using the second evaluation path and are listed in the Team
Viewer.
Þ You can use the IMG activity Define Display of Object Types (Manager Self-Service ->
Object and Data Provider -> Define Display of Object Types) to overwrite the SAP entries
from table V_TWPC_OTYPES. Furthermore, for your customer-specific views, you can
determine the object types that are displayed in the Team Viewer in the Portal.

© SAP AG HR260 11-500
© SAP AG 2006
IMG: Adjust Views and View Groups on a
Customer-Specific Basis
IMG: Transaction simg_sport IMG: IMG: Transaction simg_sport Transaction simg_sport
Views (Transaction sm30) Views (Transaction sm30)
SAP Customer
V_TWPC_V V_TWPC_V_C
V_TWPC_OTYPES V_TWPC_OTYPES_C
V_TWPC_VG V_TWPC_VG_C
SAP Tables (Delivery Class E) SAP Tables (Delivery Class E)
with Customer Namespace with Customer Namespace
Z* and Y* Z* and Y*
Use Customer Tables for Over Use Customer Tables for Over- -
writing Entries in writing Entries in
SAP Tables SAP Tables




© SAP AG HR260 11-501
© SAP AG 2006
Column Framework
The columns of
the Team Viewer iView
are based on column
framework
You can create your
own columns and
merge them into a
column group
Columns of View
All Reports (A_ALL)
Column framework
View (V_TWPC_V) View (V_TWPC_V) View (V_TWPC_V)
A column group is
then assigned to a
view



Þ In the same way as Organizational Management views and view groups, the Object and Data
Provider allows you to define columns and put them together in column groups. These, in
turn, can then be assigned to an Organizational Management view. Column groups specify the
number of columns and the information that is displayed in them.

© SAP AG HR260 11-502
© SAP AG 2006
Column Framework: How Do You Define a Column
Group?
Form Column Groups
(V_TWPC_ACOL )
View (V_TWPC_V) View (V_TWPC_V) View (V_TWPC_V)
Define Columns
(V_TWPC_COL_ERP )
Define Column Groups
Basis Definition
(V_TWPC_ARRAYTP )
Add Column Group to
View



Þ The column framework includes a generic concept for filling columns in a structured or list
display. The foundations for this are: column definitions, how columns are merged into
column groups and a function modules with a standard interface, or a query that is defined
using transaction ARRAY_CREATE set up for this purpose, to find and copy the column
content. Users are able to interactively define and modify their individual column view
(visibility, order). The system manages this user-specific view in the column framework so
that users see exactly the same changed view the next time they look at the view they changed.

© SAP AG HR260 11-503
© SAP AG 2006
Column Framework: Define a Column Group
Form Column Groups
(V_TWPC_ACOL )
View V_TWPC_ARRAYTP View V_TWPC_ARRAYTP View V_TWPC_ARRAYTP
Define Columns
(V_TWPC_COL_ERP )
Define:
¤ Technical Name
¤ Short Description
Define Column Groups
Basis Definition
(V_TWPC_ARRAYTP )




© SAP AG HR260 11-504
© SAP AG 2006
Column Framework: Define a Column
Form Column
Groups
(V_TWPC_ACOL )
View V_TWPC_COL View V_TWPC_COL View V_TWPC_COL
Define Column Groups
Basis Definition
(V_TWPC_ARRAYTP )
Define
Columns
(V_TWPC_COL_ERP )
Service Key



Þ Field Alignment: Controls whether the system aligns the entries in a column to the left,
centrally, to the right, or automatically.
Þ In the FM for Column Contents field, specify a function module that provides the column
content.
Þ If the text or icon displayed in a column is to include a link, store an entry in the Service field.
You define services in view V_T77XSSSERSRV.

© SAP AG HR260 11-505
© SAP AG 2006
Column Framework: Form a Column Group
View V_TWPC_ACOL View V_TWPC_ACOL View V_TWPC_ACOL
Define Columns
(V_TWPC_COL_ERP )
Define Column Groups
Basis Definition
(V_TWPC_ARRAYTP )
¤ Group Columns
¤ Define Attributes Such
As Position and
Visibility
Form Column Groups
(V_TWPC_ACOL )



Þ You can group individual columns in groups. You can make the following additional settings:
º Assign the positions of individual columns within a column group
º Set visibility attribute
º Define coherence relationships between individual columns (see defining coherence
relationships [Page 21])
Þ For the system to display these column groups on the user interface you must ensure that the
column group you defined is assigned to an Organizational Management view that is, in turn,
assigned to a Web Dynpro application.
Þ The individual columns of a column group are displayed in the individual Organizational
Management views in the sequence of the position numbers you assigned for columns within
the column group. Only columns that are not set as Do Not Display or Invisibleare displayed.
Þ Managers can show or hide individual columns by using one of the buttons stored in the
Organizational Management view to access the dialog box to configure columns. Managers
can show or hide any columns that are not set as Do Not Display or Invisible.

© SAP AG HR260 11-506
© SAP AG 2006
Column Framework: Form Column Groups
View V_TWPC_ACOL
Column Group
Columns of Column Group
Positions of Columns in Column Group
Column Always Shown
Manuall y Show Column
Column Always Hidden



Þ Meaning of view V_TWPC_ACOL:
º Position:
You use this value to determine the order of views to the organizational structure or the
order of columns in various listings.
º Indicator: Visible
Specifies that the system always displays the column within the application and that the
user cannot hide the column.
º Indicator: Do not display
If you set this indicator, the system does not display this column when you call the column
group. The user cannot show this column.
º Indicator: Hidden
If you set this indicator, the system does not display this column when you call the column
group.
º Coherence Relationship:
Relationship between columns in a column group that enables you to collectively show and
hide columns. Such a relationship is useful, for example, for columns in which there is a
start and end date of a link.
Þ …

© SAP AG HR260 11-507
Þ …
Þ Caution: The following applies to entries in the Always Visible, Do Not Display, and Invisible
fields:
º You do not select any of these fields. In this case, the column is displayed for managers
and they can set the user-specific settings to hide the column.
º If the Do Not Display field is selected, the system ignores the Always Visibleand Invisible
fields. The column is not displayed for managers and they cannot set the user-specific
settings to show the column.
º If the Always Visiblefield is selected, the system ignores the Invisible field. The column is
displayed for managers and they cannot set the user-specific settings to hide the column.


© SAP AG HR260 11-508
© SAP AG 2006
Column Framework: Change Column Header
Columns of View
All Reports (AP_ALL)
View (V_TWPC_V) View (V_TWPC_V) View (V_TWPC_V)
View V_TWPC_COLHEAD View V_TWPC_COLHEAD View V_TWPC_COLHEAD



Þ In this IMG activity you can overwrite column headers. This enables you to store column
headers that depend on the context or the type of object displayed. For example, if the objects
displayed represent cost centers, you can label the column Cost Center, or you can label the
column Personnel Number if the displayed objects are people or employees.

© SAP AG HR260 11-509
© SAP AG 2006
View Group Parameter on Rel. 4.7 Enterprise
V_TWPC_VG View



Þ The above slide shows the view group assignment on Rel. 4.7 Enterprise.
Þ The view groups and the standard views (default setting) are stored in the iView as
parameters:
º Parameter: Selected View ID by First Call – name of view that is the default setting
º Parameter: View Group Used for Attendance Overview – the name of the view group that is
valid for this scenario is entered here.
Þ Note that the parameter name for the view group may differ in each iView.

© SAP AG HR260 11-510
© SAP AG 2006
Incorporating View Group ERP2004
View V_TWPC_VG
View V_T7XSSSERRES



Þ ERP2004 enables you to assign the view group in the backend. You can find the Customizing
in Defining Resources in the Homepage Framework Customizing (see Appendix).

© SAP AG HR260 11-511
© SAP AG 2006
Team Viewer Integration: Create Requisition Request –
Column Content
Views V_TWPC_COL Views V_TWPC_COL Views V_TWPC_COL
Column Name
Determines the Next
iView
Function Module
Determines
Window Layout
Function Module for
Column Content
Function Module for
External Link
1
2
3
4



Þ A column can contain a link or a symbol with a link to another iView.
Þ A function module (1) defines the content displayed in the column. If users choose the link, a
new browser window with another iView opens. This iView is determined depending on the
PCD service entry (2).
Þ A second function module (3) determines the layout of the browser window (large, without
toolbar, and so on) and transfers certain parameters to the iView, such as system ID, object ID,
object name, date, and so on. The active iView uses these parameters to call the data to be
displayed from the mySAP ERP system.

© SAP AG HR260 11-512
© SAP AG 2006
Column Framework: Tables
SAP Tables
V_TWPC_COL_ERP Column Definition as of <ERP2004
V_TWPC_COL Column Definition >ERP2004
V_TWPC_ARRAYTP Define Column Groups
V_TWPC_ACOL Compose Columns in Column Groups
V_TWPC_COLHEAD Redefine Column Headers
V_TWPC_COLHTYP V Define Column Header Types
V_TWPC_COLMERGE Group Columns
V_TWPC_FRIEND Define Coherence Relationships
V_TWPC_HIERATP Hierarchical Column Groups
V_TWPC_ACOL_C Compose Columns in Column Groups
– Customer
V_TWPC_COLHEAD Redefine Column Headers – Customer
V_TWPC_HIERATP_C Hierarchical Column Groups - Customer




© SAP AG HR260 11-513
© SAP AG 2006
Column Framework: Table Interaction
V_TWPC_COL
Define Columns
V_TWPC_COL
Define Columns
V_TWPC_ARRAYTP
Define Column
Groups
V_TWPC_ARRAYTP
Define Column
Groups
V_TWPC_ACOL
Form Column
Groups
V_TWPC_ACOL
Form Column
Groups
V_TWPC_COLHTYP
Define Header
Types
V_TWPC_COLHTYP
Define Header
Types
V_TWPC_COLHEAD
Redefine Column
Headers
V_TWPC_COLHEAD
Redefine Column
Headers
V_TWPC_V
Define Views
V_TWPC_V
Define Views



Þ In table V_TWPC_V, assign a column group to a view that is displayed in the table view of
the iView.
Þ Table V_TWPC_ARRAYTP defines table groups.
Þ Table V_TWPC_COL defines columns.
Þ Table V_TWPC_ACOL combines columns into column groups.
Þ You can use table V_TWPC_COLHEAD to redefine the column headings and define a
language-dependent heading. Column headers must be assigned a header type that was defined
in table V_TWPC_COLHTYP. The header type is then transferred to the view.
Þ If no header type is transferred to the view, the headers are take from table V_TWPC_COL .

© SAP AG HR260 11-514
© SAP AG 2006
IMG: Customizing the Column Framework
IMG: Transaction simg_sport IMG: Transaction simg_sport




© SAP AG HR260 11-515
© SAP AG 2006
Navigation Types – I
Organizational units for which the
manager is responsible
Along the structure, the
system finds all
organizational units for
which the manager is
responsible.
Each organizational unit
is displayed as an entry in
the iView.
Go to next page ...



Þ In some Team Viewer iViews, navigation objects (such as organizational units) as opposed to
views are offered for selection in the list box. This has the advantage that you can restrict
which objects (in this case, positions) are displayed and thereby obtain a better overview.
Þ Example:
The Designate Vacant Position iView is based on the Object and Data Provider. The list box
displays a list of organizational units for which a manager is directly or indirectly responsible.
When a manager selects an organizational unit, all the positions for the organizational unit are
displayed in a list in the iView. That is, the organizational unit selected determines the objects
that are displayed in the iView.
Þ If views as opposed to navigation objects are to be used, all positions for which a manager is
directly and indirectly responsible are displayed.
Þ The navigation objects that are offered for selection in the list box are determined along the
structure using the evaluation path stored in the Object and Data Provider.

© SAP AG HR260 11-516
© SAP AG 2006
Navigation Types II
Display all
employees
belonging to
selected
organizational
unit




© SAP AG HR260 11-517
© SAP AG 2006
Navigation Types III
Chief Posi tion
Employee/
Person Org. Unit
Start Evaluation Path
Start Evaluation Path
Start Object
Start Object
Employee Has a
Chief Posi tion
Org. Unit
Start Object
Start Object
+ Eval. Path (O-O)
Eval. Path (O-O)
Selected
Nav. Object
Selected
Nav. Object
+
Second
Eval. Path
O-O-S-P
Second
Eval. Path
O-O-S-P



Þ Starting from the user, the start evaluation path uses person and chief position to determine the
start object, in this case an organizational unit.
Þ Starting from this start object, along the structure, a second evaluation path determines the
navigation objects (in this case, organizational units) that are displayed in the list box.
Þ When one of the organizational units is selected from the list box, the objects to be displayed
(in this case, positions) are determined using a further evaluation path.

© SAP AG HR260 11-518
© SAP AG 2006
Navigation Types IV
View for compensation
The start evaluation path
(US-P-S-O) determines the
start objects
The second evaluation path
(O-O-S-P) determines the
objects for which the
superior is responsible
The evaluation path (O-O)
determines the objects
for navigation
View (V_TWPC_V) View (V_TWPC_V) View (V_TWPC_V)
View V_TWPC_NAV View V_TWPC_NAV View V_TWPC_NAV



Þ In table V_TWPC_NAV, the view CPALL is assigned a navigation ID. An evaluation path
that determines the navigation objects, starting with the start object (using the start evaluation
path in table V_TWPC_V), is part of the navigation ID.


© SAP AG HR260 11-519
© SAP AG 2006
Navigation Types: Permitted Object Types
Evaluation path that
determines the objects for
navigation (O-O)
Structure depth for
navigation display
The depth describes the
number of levels evaluated
along the structure.
Determine the object types
displayed in the Team
Viewer
V_TWPC_NAV View V_TWPC_NAV View V_TWPC_NAV View
V_TWPC_NAVOTYPE View V_TWPC_NAVOTYPE View V_TWPC_NAVOTYPE View



Þ If necessary, in the "Depth" field, enter the level of the organizational structure up to which
the system is to determine objects using the evaluation path. If a manager is responsible for the
entire area of the organizational structure, but only wants to see the first three hierarchy levels
of their own structure in the portal, this is possible by entering a depth in the V_TWPC_NAV
table.
Þ Table V_TWPC_NAVOTYPE defines the object types displayed on the selection page.
Þ Customer Tables:
º If you want to change or redefine navigation object types, use the V_TWPC_NAVTP_C
table.

© SAP AG HR260 11-520
© SAP AG 2006
Navigation Parameters
View V_TWPC_NAV



Þ The entry from view V_TWPC_NAV is entered in the iView parameter Navtype.

© SAP AG HR260 11-521
© SAP AG 2006
IMG: Navigation Types Customizing
IMG: IMG: Transaction simg_sport Transaction simg_sport
Views (Transaction sm30) Views (Transaction sm30)
SAP Customer
V_TWPC_NAV
V_TWPC_NAVTYPE V_TWPC_NAVTP_C
SAP Tables (Delivery Class E) with SAP Tables (Delivery Class E) with
Customer Namespace Z* and Y* Customer Namespace Z* and Y*
Use Customer Tables for Overwriting Use Customer Tables for Overwriting
Entries in SAP Tables Entries in SAP Tables




© SAP AG HR260 11-522
© SAP AG 2006
Navigation Types – Tables Interaction
V_TWPC_V
Define Views
V_TWPC_V
Define Views
V_TWPC_VG
Define View Groups
V_TWPC_VG
Define View Groups
V_TWPC_NAVOTYPE
Object types for
Navigation
V_TWPC_NAVOTYPE
Object types for
Navigation
V_TWPC_ACOL
Form Column Groups
V_TWPC_ACOL
Form Column Groups
Assign view
group to
iView
Assign view
to iView
V_TWPC_NAV
Define navigation
types & eval. path
V_TWPC_NAV
Define navigation
types & eval. path




© SAP AG HR260 11-523
© SAP AG 2006
Hierarchical Column Groups I
Two Column Groups



Þ You can enhance existing column groups that are displayed in several Organizational
Management views, so that the enhancements are only valid for some Organizational
Management views while other Organizational Management views, or the original column
group, remain unaffected. Enhancements of this type are based on the definition of
hierarchical column groups and denote a grouping of existing columns and column groups.
Þ If you group columns and column groups hierarchically, the system not only displays columns
that are directly assigned to this column group, but also the columns and column groups that
are below them in the hierarchy - it displays all of these columns on the user interface in the
Organizational Management views to which this column group is assigned.

© SAP AG HR260 11-524
© SAP AG 2006
Hierarchical Column Groups II
V_TWPC_ARRAYTP View
V_TWPC_ACOL View
V_TWPC_HIERATP View
V_TWPC_V View



Þ Example:
º You assign the ATTEND and ZATTEND column groups to the ZHI ERARCHI E_1
column group.
º When the ZHI ERARCHI E_1 column group is displayed in an Organizational
Management view within a Web Dynpro application, the system automatically displays the
columns belonging to the ATTEND and ZATTEND column groups. The sequence in
which columns are displayed for the ZHI ERARCHI E_1 column group is determined as
follows: the columns that are directly assigned to the ZHI ERARCHI E_1 column group
are displayed first (you can assign columns in the V_TWPC_ACOL view (Put Columns
Together in a Column Group) or in the V_TWPC_ACOL_C customer view). The system
then displays the direct columns of the ATTEND and ZATTEND column groups
assigned to the ZHI ERARCHI E_1 column group. These columns are displayed in the
sequence defined in the V_TWPC_ACOL or V_TWPC_ACOL_C views. If the
ATTEND or ZATTEND column group is hierarchical again, the columns and column
groups of ATTEND and ZATTEND , which are assigned in a hierarchy, are then
evaluated. In other words, the evaluation algorithm for hierarchical column groups follows
a breadth-first search.

© SAP AG HR260 11-525
© SAP AG 2006
Defining Coherence Relationships
V_TWPC_FRIEND View
V_TWPC_ACOL View



Þ The content of some columns is so closely related that it only makes sense to show or hide
these columns together within a column group. You can link together columns that contain
similar content by defining coherence relationships.
Þ You can define coherence relationships in the view V_TWPC_FRI END (Definition of
Coherence Relationships). Customer-specific entries must begin with Y or Z.
Þ If there are two or more columns in a column group, you can store each of the coherence
relationships defined in the above view in the Coherence field in the customer view
V_TWPC_ACOL_C (Put Columns Together in a Column Group – Customer). This ensures
that these columns, to which the same coherence relationship is assigned, are always shown
together for a manager and can similarly be hidden together by the manager.
Þ In the dialog box for configuring columns, columns with the same coherence relationship are
grouped together under the name of the coherence relationship that is stored in the view
V_TWPC_FRI END.

© SAP AG HR260 11-526
© SAP AG 2006
Transfer Table Settings from Column Framework
(Manager's Desktop)
TWPC_HIERATP_C (Hierarchical Column Groups -
Customer)
T77HIERATC (Column Framework: Hierarchical
Column Groups) (as of Release 4.6C)
TWPC_HIERATP (Hierarchical Column Groups) T77HIERATP (Column Framework: Hierarchical
Column Groups) (as of Release 4.6C)
TWPC_FRIEND_T (Text for Definition of Coherence
Relationships)
T77FRIENDT (HR-OM: Text for Column Grouping)
TWPC_FRIEND (Definition of Coherence Relationships) T77FRIEND (HR-OM:Type of Column Groupings)
TWPC_COLHEAD_C (Redefining Column Headers -
Customer)
T77COLH_C (HR-OM: Customer-Specific Redefinition
of Column Headers)
TWPC_COLHEAD (Redefining Column Headers) T77COLHTYP (HR-OM: Redefined Definition of the
Column Headers)
TWPC_COLHTYP (Definition of the Column Header
Types)
T77COLHTYP (HR-OM: Definition of the Column
Header Types)
TWPC_ACOL_C (Columns of Column Group - Customer) T77ACOLC (HR-OM: Columns of a Structure)
TWPC_ACOL (Columns of a Column Group) T77ACOLINI (Initial Settings for Columns of an Array
Type)
TWPC_ACOL (Columns of a Column Group) T77ACOL (HR-OM: Columns of a Structure)
TWPC_ARRAYTP_T (Text Table for Column Group
Definition)
T77ARRAYTT (Text Table for T77ARAYTP)
TWPC_ARRAYTP (Column Group Definition) T77ARRAYTP (Structure Type)
TWPC_COL_T (Texts for Column Definition) T77COLT (HR-OM: Texts for Column Defini tion for
Structures)
TWPC_COL Column Definition T77COL (HR-OM: Column Definition for Structures)
The system converts the following tables:



Þ For the Object and Data Provider within the Manager Self-Service business package, new
tables were created to provide flexibility when setting up this scenario.
Þ These tables are similar to the Column Framework used in the Manager's Desktop, for
example.
Þ If you are using the Column Framework and if you want to continue to use table settings in
the Manager Self-Service business package, you can use this conversion report to integrate
entries from the tables in the Column Framework into the new tables.
Þ A report allows you to convert the table settings for the Column Framework into the table
settings for the Object and Data Provider.
Þ You can use the PWPC_TO_CONVERT_TABLES conversion report to integrate entries
from the tables of the Column Framework into the tables of the Object and Data Provider.
This allows you to reuse columns and column groups that have already been defined.

© SAP AG HR260 11-527
© SAP AG 2006
Team Explorer I
Team Viewer – not suitable for more than 70 employees!



Þ The MSS business package was designed for the middle management of a company with a
typical span of control of up to 70 employees.
Þ There are no plans to implement these functions for all employees if there is a span of control
of several hundred employees. However, it may make sense to view certain data for all
employees assigned to a manager, even if the span of control is greater than the span of
control intended by SAP for the business package. As of Business Package MSS 60.1.3
(EP6.0) and MSS 50.4.3 (EP5.0), the Team Explorer is provided and it can replace the Team
View in the "Employee Review" workset.
Þ The Team Explorer's area of operation is limited to the workset that is delivered ("Employee
Review") and the "Employee iViews" contained in this workset. You cannot use the Team
Explorer for other worksets (for example, worksets that contain iViews that enable you to
maintain employee data, such as 'Employee Appraisals' or 'Compensation Management').
Þ One difference between the Team Explorer and the Team Viewer is that the Team Explorer
has a navigation area on the left-hand side of the page. For example, the manager can first
select an organizational unit on the left-hand side of the page and then obtain a list of all
employees assigned to this organizational unit on the right-hand side of the page.

© SAP AG HR260 11-528
© SAP AG 2006
Team Explorer II
Team Explorer
V_TWPC_NAV View
V_TWPC_V View
V_TWPC_OTYPES View



Þ To improve performance in the Team Viewer, you must make the following settings:
º Assign a structure that only comprises one type of organizational object (for example,
organizational units) to the navigation tree (screen area on the left) of the Team Explorer.
For this, use the ORGEH evaluation path (organizational structure) in the relevant
navigation ID.
Þ The advantage associated with this is that the system does not need to initially determine and
import additional data from other hierarchical levels (positions and employees).
º Use Customizing for the view that was maintained in the navigation ID to fill the object list
(screen area on the right) of the Team Explorer in such a way that the system only displays
a flat list of employees.
Þ When you select an organizational unit, the system uses the evaluation path for the object set
of the view ID to determine the employees. Here, it makes sense to use the MSSREPS
(directly reporting employees) or SBES (staffing assignment for each organizational unit)
evaluation path.

© SAP AG HR260 11-529
© SAP AG 2006
Team Explorer III
PAR File for the Team Explorer



Þ The Team Explorer is delivered as of the business packages listed above. Note that the Team
Explorer is not delivered as an iView in the business package, nor is it available on any portal
page in the business package. The PAR file of the iView is contained in the business package.
To be able to use the Team Explorer, you must create a portal iView on the basis of the PAR
file com.sap.pct.hcmteamexplorer. After you create the PAR file, you can replace the Team
Explorer iView on the relevant portal pages with the Team Viewer.

© SAP AG HR260 11-530
© SAP AG 2006
Team Explorer IV
Initial Expand Level
Keep Level
Navigation IDs
Default Value



Þ The 'Keep Level' iView parameter is usually set to the same value as the depth in the
V_TWPC_NAV table; it is also possible to set the value to depth -1. This value ensures that
the expanded levels in the structure do not exceed the level set in the memory.
Þ The 'Initial Expand Level' iView property is used to define up to how many levels the
structure in the navigation tree should automatically be expanded when you first display the
iView. Do not exceed an initial expand level of 2. Otherwise, the structure display will be too
complex the first time you call the structure. This also limits the volume of data initially
imported by the system.
Þ The 'Nav Group' iView property is used to determine which navigation IDs are displayed for
selection in the pulldown field of the Team Explorer.
Þ The 'NavID' iView property is used to determine which navigation ID is displayed as the
default value in the Team Explorer.

© SAP AG HR260 11-531
© SAP AG 2006
Team Explorer V
2. V_TWPC_NAV View
1. V_TWPC_V View
3. V_TWPC_OTYPES View



Þ The following tables in the back-end system are relevant for adjusting the Team Explorer:
º V_TWPC_NAV for defining the navigation ID
º V_TWPC_V for defining the view ID
º V_TWPC_OTYPES for restricting the object type display
Þ In the first step, a view ID that fulfills two tasks is generated in the V_TWPC_V table:
º You use the evaluation path for the root object (or you use a function module) to determine
the organizational units for which a manager is responsible; for this, you usually use the
SAP_MANG evaluation path.
º You use the evaluation path for the object set (or you use a function module) to determine
the employees belonging to all organizational units for which our manager is responsible;
here, you can use either SBES or MSSDIREC.
Þ All the evaluation paths mentioned here are delivered in the standard SAP system and are
available in the T77AW table.
Þ Make sure that the 'Display as Tree Structure' attribute is not activated for the view ID in the
V_TWPC_V table; only 'Output as List' is permitted here.
Þ In the second step, a navigation ID is created in the V_TWPC_NAV table. This contains the
previously defined view ID and an evaluation path that determines all lower-level

© SAP AG HR260 11-532
organizational units based on the root objects that were determined. We recommend that you
use ORGEH as the evaluation path.
Þ In the third step, an entry is created in the V_TWPC_OTYPES table and this entry refers to
the view in the V_TWPC_V table. Here, only the output of object type 'P' (personnel number)
is permitted.
Þ For more information, see SAP Note 738006.

© SAP AG HR260 11-533
© SAP AG 2006
Standard Entries for the Attendance Workset
V_TWPC_VG V_TWPC_VG V_TWPC_VG
V_TWPC_ACOL V_TWPC_ACOL V_TWPC_ACOL
V_TWPC_V V_TWPC_V V_TWPC_V
V_TWPC_OTYPES V_TWPC_OTYPES V_TWPC_OTYPES



Þ There are entries for the Attendanceworkset provided by SAP in all views that are important
for the Team Viewer.

© SAP AG HR260 11-534
© SAP AG 2006
Team Viewer PCR – Object and Data Provider
V_TWPC_V: Defini tion of views
V_TWPC_V: Defini tion of views



Þ To make the various views available for selection in the dropdown list of the Team Viewer,
and the relevant objects to be selected, a name must be assigned in this Customizing step and
the evaluation path for determining objects must be maintained.
Þ The other settings determine how the objects are displayed and whether the person submitting
the request is removed from the list, for example.

© SAP AG HR260 11-535
© SAP AG 2006
Team Viewer PCR – Object and Data Provider
V_TWPC_OTYPES: Defini tion of object types for PCRALL and PCRDIR
V_TWPC_OTYPES: Defini tion of object types for PCRALL and PCRDIR
V_TWPC_VG: Grouping vi ews PCRALL and PCRDIR to viewgroup PCR
V_TWPC_VG: Grouping vi ews PCRALL and PCRDIR to viewgroup PCR
V_TWPC_ACOL: Assigning columns to column group
V_TWPC_ACOL: Assigning columns to column group



Þ The defined object types determine which organizational objects are displayed in the list. This
means that you can use the evaluation path to select an entire organizational structure but
display employees only.
Þ Using the generic Object and Data Provider means that you are not limited to the object type P
(person), but you can also create views for requests based on positions or cost centers. In this
way, you can create customer-specific PCRs that do not use the employee as the core object.
Þ The grouping of the individual views determines which selection options are to be available in
the dropdown list for the person submitting the PCR.
Þ The column group or the individual columns in the group do not only define which data is
later displayed in the Team Viewer, rather the interactive functions for each of the individual
columns are also stored here. The column is used to define the portal service with which the
employee profile is to be displayed or which frontend link is used to address the mail function.

© SAP AG HR260 11-536
© SAP AG 2006
Team Viewer PCR – Object and Data Provider
V_TWPC_COLHEAD: Defi ning column headers
V_TWPC_COLHEAD: Defi ning column headers



Þ For maximum flexibility, you can either overwrite individual column headers or you can do
this using an appropriate header group.
Þ This enables you to use terms specific to your enterprise without having to make alterations to
the logic of the individual columns or data retrieval.

© SAP AG HR260 11-537
© SAP AG 2006
Team Viewer Integration: Requisition Creation –
Example for OADP
Org units the manager is responsible
for. Eval. path SAP_MANG
Result of the first evaluation Path:
Start Object “Sales East”
1
Eval. path:
O_NACH_S
Eval. path:
O_NACH_S
Starting with the start
object and the eval. path
ORGEH_T, the system finds
all org units for which the
manager is responsible
within the structure.
Each Org Unit is then
displayed as an entry in the
list box
2
3



Þ In some team viewers the system offers navigation objects (for example, organizational units)
instead of views in the list box. The advantage of this is that you can restrict the display of
objects (here, Positions) and therefore obtain a better overview.
Þ Example: The iView My Position List is based on the Object and Data Provider. In a list box,
the system displays a list of organizational units for which the manager is directly or indirectly
responsible. If the manager selects an organizational unit, the system displays a list of all the
positions in that organizational unit in the iView. In other words, the selected organizational
unit determines the objects that are displayed in the iView.
Þ If there were views instead of navigation objects here, the system would display all positions
for which the manager is directly or indirectly responsible.
Þ The navigation objects that are offered for selection in the list box are determined according to
the structure by evaluation paths stored in the object and data provider.

© SAP AG HR260 11-538
© SAP AG 2006
Team Viewer Integration: Requisition Creation –
Navigation Types in OADP
Views V_TWPC_V Views V_TWPC_V Views V_TWPC_V
Navigation types V_TWPC_NAV Navigation types V_TWPC_NAV Navigation types V_TWPC_NAV
View for Vacancy request
Start eval. path determines
the Start Objects (US-P-S-O)
Evaluation path determines
the objects the manager is
responsible for (O-S)
Eval. path that determines
the objects for navigation
(O-O)
Structure depth for navigation
display
1
3
2



Þ In table V_TWPC_NAV, a navigation ID is assigned to the view RCPOS. For this navigation
ID you enter an evaluation path (2), which determines the navigation objects based on the start
object (determined using the start evaluation path (1) in table V_TWPC_V).
Þ If you now select an organizational unit from the list box, a subsequent evaluation path (3)
uses the organizational unit to determine the objects for display in table V_TWPC_V, and
displays the objects in the iView.
Þ Customer tables:
º If you want to overwrite SAP views or define new views, use the customer tables
V_TWPC_V_C.

© SAP AG HR260 11-539
© SAP AG 2006
Team Viewer Integration: Object Types for
Navigation
Navigation types V_TWPC_NAVOTYPE
Navigation types V_TWPC_NAVOTYPE
Determine the
Object Types
that are
displayed in
the list box
Navigation types V_TWPC_NAV
Navigation types V_TWPC_NAV
Eval. Path that determines
the objects for navigation
(O-O)



Þ If required, specify in the Depth field the level of the organizational structure to which you
want the system to evaluate objects, according to the evaluation path. If one manager is
responsible for the whole area of the organizational structure, but only wants to see the first
three hierarchical levels of his or her structure in the portal, he or she can specify this by
entering a depth in table V_TWPC_NAV.
Þ In table V_TWPC_NAVOTYPE the object types are defined that are displayed in the list box.
Þ Customer tables:
º If you want to change navigation object types or define new ones, use table
V_TWPC_NAVTP_C.

© SAP AG HR260 11-540
© SAP AG 2006
Team Viewer Integration: Requisition Creation –
Displayed Object Types
Views V_TWPC_V Views V_TWPC_V Views V_TWPC_V
Displayed Object Types V_TWPC_OTYPES Displayed Object Types V_TWPC_OTYPES Displayed Object Types V_TWPC_OTYPES
Evaluation Path determines
the objects the manager is
responsible for (O-S)
3
Determine the Object
Types that are
displayed in the table
view



Þ Starting from the organizational unit that the manager chooses in the list box, another
evaluation path (3) determines the objects that may be displayed in the iView.
Þ In table V_TWPC_OTYPES the object type is determined that is displayed in the table view.

© SAP AG HR260 11-541
© SAP AG 2006
Team Viewer Integration: Requisition Creation –
Column Groups
Views V_TWPC_ACOL Views V_TWPC_ACOL Views V_TWPC_ACOL
Views V_TWPC_V Views V_TWPC_V Views V_TWPC_V
Assign Column Groups
Views V_TWPC_ARRAYTP Views V_TWPC_ARRAYTP Views V_TWPC_ARRAYTP
Column Name Column Description Function Module for Content
RQ_S_NAME Position Name HRWPC_RQ_REQ_NAME
ORG_OBJ ID Object ID HRWPC_FILL_STANDARD_COLUMNS
RQ_O_BEGDA Valid From HRWPC_RQ_BEGDA_ENDDA
RQ_O_ENDDA Valid To HRWPC_RQ_BEGDA_ENDDA
RC_HOLDER Holder of Position HRWPC_RC_VACREQ_HOLDER
RC_VACDA Vacant From HRWPC_RC_VACREQ_VACDATA
See example on next page




© SAP AG HR260 11-542
© SAP AG 2006
Navigation Types in Compensation Workset I
Organizational units for which the
manager is responsible
Starting with the start object and
evaluation path ORGEH_T, the
system searches all organizational
units in the structure for which the
manager is responsible
Each organizational unit is displayed
as an entry of the list field
Result of first evaluation path:
Start object " Sales EAST"



Þ In some Team Viewers the system provides navigation objects (for example, organizational
units) instead of views in the list field. The advantage is that you can restrict the display of
objects (in this case employees) to gain a better overview.
Þ Example: The Find Vacant Positions iView is based on the Object and Data Provider. In a
selection view, the system displays a list with organizational units for which the manager is
directly or indirectly responsible. If the manager chooses one or more organizational units, the
system displays a list of all employees in the selected organizational units in the iView. The
organizational units determine the objects displayed in the iView.
Þ The navigation objects that you can select in the list field are determined along the structure
using the evaluation paths saved in the Object and Data Provider.

© SAP AG HR260 11-543
© SAP AG 2006
Navigation Types in Compensation Workset II
Views V_TWPC_V Views V_TWPC_V Views V_TWPC_V
Navigation Types V_TWPC_NAV Navigation Types V_TWPC_NAV Navigation Types V_TWPC_NAV
Evaluation path that
determines the
objects for navigation (O-O)
2
View for compensation
Start evaluation path
determines
start objects (US-P-S-O)
Evaluation path determines
the objects for which the
manager is responsible
(O-S)
1
3
Structure depth for
navigation display



Þ In table V_TWPC_NAV, the view CPALL is assigned a navigation ID. Enter an evaluation
path (2) for this navigation ID that determines the navigation objects according to the start
object (determined using the start evaluation path (1) in table V_TWPC_V).
Þ If you now choose an organizational unit, a subsequent evaluation path (3) uses the
organizational unit to determine the objects to be displayed in table V_TWPC_V and displays
the objects in the iView.
Þ Customer Tables:
º If you want to overwrite SAP views, or define new views, use customer table
V_TWPC_V_C.

© SAP AG HR260 11-544
© SAP AG 2003
Object Types Eligible for Navigation
Navigation types V_TWPC_NAVOTYPE Navigation Navigation types types V_TWPC_NAVOTYPE V_TWPC_NAVOTYPE
Determine the
object types
that are
displayed on the
selection page
Navigation types V_TWPC_NAV Navigation Navigation types types V_TWPC_NAV V_TWPC_NAV
Eval. Path that determines
the objects for navigation
(O-O)



Þ If required, in the Depth field, specify the level of the organizational structure to which you
want the system to evaluate objects according to the evaluation path. If one manager is
responsible for the whole area of the organizational structure, but only wants to see the first
three hierarchical levels of his or her structure in the portal, he or she can specify this by
entering a depth in table V_TWPC_NAV.
Þ In table V_TWPC_NAVOTYPE the object types are defined that are displayed on the
selection page.
Þ Customer tables:
º If you want to change navigation object types or define new ones, use table
V_TWPC_NAVTP_C.

© SAP AG HR260 11-545
© SAP AG 2003
Object types to be displayed in the List
Views V_TWPC_V Views V_TWPC_V Views V_TWPC_V
Displayed Object Types V_TWPC_OTYPES Displayed Object Types V_TWPC_OTYPES Displayed Object Types V_TWPC_OTYPES
Determine the object types
that are displayed in the
table view
Evaluation Path determines
the objects the manager is
responsible for (O-S-P)
3



Þ Starting from the organizational units that the manager chooses on the selection page, another
evaluation path (3) determines the objects that may be displayed in the iView.
Þ In table V_TWPC_OTYPES the object type is determined that is displayed in the table view

© SAP AG HR260 11-546
© SAP AG 2006
Assign Column Groups to Views
Assign Column Groups
V_TWPC_ARRAYTP Column Group: COMPPLAN
Views V_TWPC_V Views V_TWPC_V Views V_TWPC_V




© SAP AG HR260 11-547
© SAP AG 2006
Compensation Planning – Columns
Define Columns: V_TWPC_COL Define Columns: Define Columns: V_TWPC_COL V_TWPC_COL
CP_APPRAISAL
CP_AMOUNT
CP_BSSAL
CP_BUDGET
CP_COMPRATIO
CP_CURRENCY
CP_EFFDA
CP_HIRE_DATE
CP_JOB
CP_CP_NAME
CP_NEWSAL
CP_PERCENT
CP_POSITION
CP_STATE
CP_SUMMARY
Performance
Amount
Basic Salary
Budget
Compa-Ratio
Currency
Effective on
Entry Date
Job
Employee
Total
Percent
Position
Status
Summary



Þ Columns with data relevant for planning that you fill using Java front-end
Þ Columns with additional data (display only) that you fill using mySAP ERP function modules

© SAP AG HR260 11-548
© SAP AG 2003
Default Properties – Compensation Planning
Views V_TWPC_V Views V_TWPC_V Views V_TWPC_V
Assign the Navigation Type
Assign the
View ID




© SAP AG HR260 11-549
© SAP AG 2006
Team Viewer: Summary
Þ Explain the benefit of the team viewer for your
managers
Þ Describe the principles of the Object and Data
Provider the team viewer is based upon
Þ Customize the team viewer
You are now able to:




© SAP AG HR260 11-550

© SAP AG HR260 11-551
Exercise 1


Unit: Team Viewer

I n this exercise:
• Familiarize yourself with the key feature of MSS, the Team
Viewer.
• Familiarize yourself with Team Viewer Customizing.


Log on to the Portal server and the mySAP ERP back-end
system. Use the log-on information provided.

1 The Team Viewer is used in different worksets. Compare the use of the Team
Viewer in the worksets Reporting, Headcount/Quota Planning and Employee
Review.

2 Explain the differences.

3 How do you add an additional column?

4 Managers in your company are not only responsible for one organizational unit, but
also for virtual teams. How can you support such managers with MSS?



© SAP AG HR260 11-552

© SAP AG HR260 11-553
Solutions 1


Unit: Team Viewer

1 The Team Viewer is used in different worksets. Compare the use of the Team
Viewer in the worksets Reporting, Headcount/Quota Planning and Employee
Review.
In the Reporting workset, the Team Viewer is used in an own iView, which is
integrated into the Reporting application. For a Team Viewer fully integrated into
the application, see the Quota Planning workset. In the Employee Review workset,
the Team Viewer is an own iView that communicates with other iViews.

2 Explain the differences.
The different use of the Team Viewer iView is a result of the different use of the
individual worksets. Therefore the Team Viewer must be available in different
ways.

3 How do you add an additional column to the Team Viewer (e.g. date of birth)?
You create an additional column in the Team Viewer by defining column groups in
the table V_TWPC_COL and creating this additional column group in table
V_TWPC_ACOL.

4 Managers in your company are not only responsible for one organizational unit, but
also for virtual teams. How can you support such managers with MSS?
Managers who are also responsible for virtual teams can be supported by using the
appropriate evaluation paths provided by organizational management. Additionally,
you can use your own views in table T_TWPC_V.




© SAP AG HR260 11-554

© SAP AG HR260 11-555
Exercises 2


Unit: Team Viewer

I n this exercise:
• Familiarize yourself with the key feature of MSS, the Team
Viewer.
• Familiarize yourself with Team Viewer Customizing.


Log on to the portal server and the mySAP ERP back-end system.
Use the logon information provided.


Exercise 1:
Business Scenario – After careful analysis of the standard team calendar iView, the
company has decided to keep both the views Directly Reporting Employeeand All
Employees, but add a view that restricts the employee display to an organizational unit
within a manager’s area of responsibility. Employees from deeper organizational units
are not displayed.
*Hint - the team calendar iView that SAP provides uses the view group ‘ATTEND’ – this
view group in turn uses the views A_ALL and A_DIR.
1 Should this change be made in the customer configuration tables? Discuss.
2 Using the naming standard ZXX_L2, create a new view that will display
employees within the organizational unit of the manager. Restrict your view to
object type “P”.
*Hint - explore other views within the table to get a better understanding of them.
3 After you create your new view, you need to assign it to a view group. Discuss the
reasons.
4 Use the view group ATTEND and assign the new view ZXX_L2 to this group.

© SAP AG HR260 11-556
Exercise 2:
Business Scenario – After careful analysis of the standard Team Viewer iView in the
Employee Review workset, the company has decided to keep the view Directly Reporting
Employees, but change the ZXX_L2 view to a reporting tree.
*Hint - the TeamViewer iView provided by SAP uses the view group ATTEND – this
view group in turn uses the views A_ALL and A_DIR.
1 Should this change be made in the customer configuration tables? Discuss.

2 You can use the view ZXX_L2 to change the appearance of your customer-
specific view so that it will display employees in a hierarchy display.

*Hint - explore all view configuration options.

3 After changing your customer-specific view, do you now need to create a new
view group? Discuss why this is not the case?

4 What are the advantages and disadvantages associated with a hierarchy display?
Discuss.

5 The company wants to use the All Employees view on the Employee Profilepage
as a hierarchy display, but wants to display a column view for All Employees on
the Personnel Development page. What does this require? Discuss.

Exercise 3:
Business Scenario – After further analysis of the new TeamViewer iView in the
Employee Review workset, the company wishes to reduce the width of the columns in the
view ZXX_L2 to avoid displaying a horizontal scroll bar in the iView. For this reason,
the column name Personnel Number is to be renamed Per No.XX.
1 Can these requirements be met fully in the customer configuration tables?
Discuss.

2 This requirement demands a change to the standard configuration, provided by
SAP, in the column table. How would these direct changes affect the
configuration provided by SAP? Discuss. What are the alternatives?
*Hint - consider the entire column configuration tables covered in the Object and
Data Provider course notes.

3 Using the naming standard ZXX_HEADTYP, create a new header type to display
the Per No.XX in the header for the Employee Number column.

© SAP AG HR260 11-557
Exercise 4:
Business Scenario – After further analysis of the new TeamViewer iView in the
Employee Review workset, the company wishes to remove the Attendancecolumn from
the customer-specific view ZXX_L2. The column is to be removed entirely, meaning the
column does not remain as an option for the user to select in the Team Viewer.
*Hint – consider the entire column configuration tables covered in the Team Viewer
course notes.
1 Can these requirements be met fully in the customer configuration tables?
Discuss.

2 This requirement demands a change to the standard configuration, provided by
SAP, in the column table. How would these direct changes affect the
configuration provided by SAP? Discuss.

3 Using the naming standard ZXX_COLGRP, create a new column group. Insert
your column configuration into the appropriate table to meet the new
requirements.

4 You must then assign the columns to the new column group. Note the standard
configuration provided by SAP for ATTEND. Use the standard configuration as
the template for the new column configuration.

5 Make the appropriate changes to the ZXX_L2 view in order to incorporate the new
column group.




© SAP AG HR260 11-558

© SAP AG HR260 11-559
Solutions 2


Unit: Team Viewer


Solution 1:
Business Scenario – After careful analysis of the standard team calendar iView, the
company has decided to keep both the views Directly Reporting Employeeand All
Employees, but add a view that restricts the display of employees to an organizational
unit within a manager’s area of responsibility. Employees from deeper organizational
units are not displayed.
*Hint - the team calendar iView that SAP provides uses the view group ‘ATTEND’ – this
view group in turn uses the views A_ALL and A_DIR.
1 Should this change be made in the customer configuration tables? Discuss.
The change should only be made in the customer configuration tables if you want
to override existing definitions. New definitions should be made in the default
SAP tables.
2 Using the naming standard ZXX_L2, create a new view that will display
employees within the organizational unit of the manager.
*Hint - explore other views within the table to get a better understanding of them.
Restrict your view to object type “P”.
Start transaction SM31 and maintain the V_TWPC_V table.
Copy the entry “A_ALL” to name range ZXX_L2 and make the following
changes:
Field Name Contents
View: ZXX_L2 (XX = group number)
View Name: Assignments XX (e.g.)
Eval. Path for Root Objects: SAP_MANG
Evaluation Path Objects: OSP
Initial Evaluation Depth:
Column Group: ATTEND
Header Type: EMPLOYEE_1
Save your entries.
*Hint – also explore other views within the table to get a better understanding of
them.

© SAP AG HR260 11-560
Start transaction SM31 and maintain the V_TWPC_OTYPES table, so that you
can restrict the object selection in the list display to persons.
Field Name Contents
View: Z##_L2
Object Type: P
Save your entries.
3 After you create your new view, you need to assign it to a view group. Discuss the
reasons.
Here, you use an existing ATTEND view group that contains two views. An
additional ZXX_L2 view should be added to the view group. Therefore, you must
maintain the V_TWPC_VG_C customer view in order to define the customer-
specific assignment of views to view groups.
4 Use the view group ATTEND and assign the new view ZXX_L2 to this group.
Customizing:
Transaction simg_sport
Business Packages/Functional Packages ¬ Manager Self-Service ¬ Object and
Data Provider ¬ Group Views of Organizational Structure
Alternatively:
Start transaction SM31 and maintain the V_TWPC_VG_C table.
Choose New Entries.
Add or enter the following data:
Field Name Contents
View Group: ATTEND
View: ZXX_L2
Position: Add number XX+2 (XX = group number) without a
leading zero


© SAP AG HR260 11-561
Solution 2:
Business Scenario – After careful analysis of the standard Team Viewer iView in the
Employee Review workset, the company has decided to keep the view Directly Reporting
Employees, but to display the view ZXX_L2 as a reporting tree.
*Hint - the TeamViewer iView provided by SAP uses the view group ATTEND – this
view group in turn uses the views A_ALL and A_DIR.
1 Should this change be made in the customer configuration tables? Discuss.
No. You can make the change directly in the V_TWPC_V view because we want
to change the view defined in task 1.

2 You can use the view ZXX_L2 to change the appearance of your customer-
specific view so that it will display returned employees in a hierarchy display.
*Hint - explore all view configuration options.
Start transaction SM31 and maintain the V_TWPC_V table.
Select the view ZXX_L2 to change the appearance of your customer-specific view.
Set the Hierarchy Display indicator, so that it will display employees in a
hierarchy.
Field Name Contents
Display Tree: Select

3 After changing your customer-specific view, do you now need to create a new
view group? Discuss why this is not the case?
It is not necessary to create a new view group. The existing view is already
assigned to a view group. The changes to the properties of the existing view do
not affect the assignment to the view group.

4 What are the advantages and disadvantages associated with a hierarchy display?
Discuss.
Advantage: The system recognizes the assignment to the organizational unit or
position.
Disadvantage: You are unable to sort according to name or according to the other
columns.

5 The company wants to use the All Employees view on the Employee Profilepage
as a hierarchy display, but wants to display a column view for All Employees on
the Personnel Development page. What does this require? – Discuss.
You have to reconfigure the Team Viewer iView on the Personal Development
page. To do this, you must assign a new view group to the “ViewGroup” property
of the Team Viewer iView. This view group must contain a view in which the
display is a list display.
You must assign the view group to the iView within dynamic navigation on the
Personal Development page.

© SAP AG HR260 11-562
Solution 3:
Business Scenario – After further analysis of the new TeamViewer iView in the
Employee Review workset, the company wishes to reduce the width of the columns in the
view ZXX_L2 to avoid displaying a horizontal scroll bar in the iView. For this reason, the
column name Personnel Number is to be renamed Per No.XX.
1 Can these requirements be met fully in the customer configuration tables?
Discuss.
The changes could be made in the V_TWPC_COLHEAD_C view for the
EMPLOYEE_1 header type. However, the EMPLOYEE_1 header type is used in
a couple of views. Therefore, you must define a new header type
Z00_HEADTYPE in the V_TWPC_COLHEAD view and assign it to the
customer view.

2 This requirement demands a change to the standard configuration, provided by
SAP, in the column table. How would these direct changes affect the
configuration provided by SAP? Discuss. What are the alternatives?
*Hint - consider the entire column configuration tables covered in the Object and
Data Provider course notes.
If you change the standard configuration provided by SAP, this will affect all of
the views that contain columns. Furthermore, you must maintain the customer
table if you want to override entries. Therefore, you must define a separate header
type.

3 Using the naming standard ZXX_HEADTYP, create a new header type to display
the Per No.XX in the header for the Employee Number column.
Start transaction SM31 and maintain the header type in the V_TWPC_COLHTYP
table.
Choose New Entries.
Field Name Contents
Column Header Type: ZXX_HEADTYPE (XX = group number)
Save your entries.
Start transaction SM31. In the V_TWPC_COLHEAD table, maintain the
assignment of the ORG_OBJID_2 column to the ZXX_HEADTYPE header types
(XX = group number).
Choose New Entries.
Field Name Contents
Lang.: EN
Header Type: ZXX_HEADTYPE
Column Name: ORG_OBJID_2
Name: PerNo. XX (XX = group number)
Save your entries.

© SAP AG HR260 11-563
Solution 4:
Business Scenario – After further analysis of the new TeamViewer iView in the
Employee Review workset, the company wishes to remove the Attendancecolumn from
the customer-specific view ZXX_L2. The column is to be removed entirely, meaning the
column does not remain as an option for the user to select in the Team Viewer.
*Hint – consider the entire column configuration tables covered in the Team Viewer
course notes.
1 Can these requirements be met fully in the customer configuration tables?
Discuss.
Hiding the column in the V_TWPC_ACOL_C view affects this column in all
views. You must therefore define a new column group that contains the columns
that you require.

2 This requirement demands a change to the standard configuration, provided by
SAP, in the column table. How would these direct changes affect the
configuration provided by SAP? Discuss.
The direct change in the configuration provided my SAP will affect all views that
contain the column group.

3 Using the naming standard ZXX_COLGRP, create a new column group. Insert
your column configuration into the appropriate table to meet the new
requirements.
Start transaction SM31 and maintain the column group in the
V_TWPC_ARRAYTP table.
Choose New Entries.
Field Name Contents
Column Group: ZXX_COLGRP (XX = group number)
Name: Attendance GR. XX (XX = group number)
Save your entries.

4 You must then assign the columns to the new column group. Note the standard
configuration provided by SAP for ATTEND. Use the standard configuration as
the template for the new column configuration.
Start transaction SM31 and maintain the column group in the V_TWPC_ACOL
table.
Select the first three entries in the ATTEND column group and choose “Copy”.
Field Name Contents
Column Group: ZXX_COLGRP (XX = group number)
Column Name: ORG_OBJID_2
Column Group: ZXX_COLGRP (XX = group number)

© SAP AG HR260 11-564
Column Name: ORG_STEXT_JS
Column Group: ZXX_COLGRP (XX = group number)
Column Name: SAP_LEAD_POS
Save your entries.
5 Make the appropriate changes to the ZXX_L2 view in order to incorporate the new
column group.
Start transaction SM31 and maintain the ZXX_L2 view in the V_TWPC_V table.
Select the customer-specific view ZXX_L2 and change the entry for the column
group to ZXX_COLGRP.
Field Name Contents
Column Group: ZXX_COLGRP (XX = group number)
Save your entries.


© SAP AG HR260 11-565
Exercises 3


Unit: Team Viewer
Topic: Team Explorer

At the conclusion of this exercise, you will be able to:
• Include the Team Explorer in your own page

You are using the MSS business package. The span of control
within your company has increased. As a result, you want to
replace the Team Viewer with the Team Explorer.

1-1 Create your own portal page with the iViews “Emergency Contact” (technical
name: eeprofilepersonaldata) and “Personal Data” (technical name:
eeprofilepersonaldata). Then assign the Team Explorer to your page as “dynamic
navigation”.
Finally, include the new page in the Employee Review workset.
1-1-1 Enter the following information:
Name Contents
Page Name: XX Page with Team Explorer
(XX = group number)
Page ID: hr260-XX (XX = group number)
Page ID Prefix: com.hr260
1-1-2 Define any page layout and save your entries (for example, 2 columns).

1-2 Your page should contain the following iViews:
“Emergency Contact” (technical name: eeprofilepersonaldata) and “Personal Data”
(technical name: eeprofilepersonaldata).
Add the iViews “Emergency Contact” (technical name: eeprofilepersonaldata) and
“Personal Data” (technical name: eeprofilepersonaldata) to your page.

1-3 Use the Team Explorer to assign dynamic navigation to the page.

© SAP AG HR260 11-566
1-4 Add the page that you have created to the “Employee Review” workset.
NOTE: To ensure that you do not lock the “Employee Review” workset for
editing, thus preventing other participants from accessing the workset, wait until the
instructor tells you that you can edit the workset.

1-5 Check your new page.



© SAP AG HR260 11-567
Solutions 3


Unit: Team Viewer
Topic: Team Explorer

1-1 Create your own portal page with the iViews “Emergency Contact” (technical
name: eeprofilepersonaldata) and “Personal Data” (technical name:
eeprofilepersonaldata). Then assign the Team Explorer to your page as “dynamic
navigation”.
Finally, include the new page in the Employee Review workset.
Content Administration-> Portal Content-> Portal Content folder -> class HR260
-> Group XX -> right-click -> New -> Page -> Default Page Template -> choose
“Next”
1-1-1 Enter the following information:
Name Contents
Page Name: XX Page with Team Explorer
(XX = group number)
Page ID: hr260-XX (XX = group number)
Page ID Prefix: com.hr260
1-1-2 Define any page layout and save your entries.
Example: 2 Columns -> choose “Add” -> choose “Finish”
Choose: Open the object for editing -> choose OK

1-2 Your page should contain the following iViews:
“Emergency Contact” (technical name: eeprofilepersonaldata) and “Personal Data”
(technical name: eeprofilepersonaldata).
Leave the page open and, in the Portal Content, choose the following folder: Portal
Content -> Migrated Content-> EP 5.0-> iViews -> Manager%20Self-
Service%3a%20My%20Staff
Add the iViews “Emergency Contact” (technical name: eeprofilepersonaldata) and
“Personal Data” (technical name: eeprofilepersonaldata) to your page. To do this,
right-click the relevant iView. A context menu is displayed. Choose Add iView to
Page-> Delta Link. Save your data.

1-3 Use the Team Explorer to assign dynamic navigation to the page.

© SAP AG HR260 11-568
Go to the “Display” field and choose “Dynamic Navigation”. Leave the page open
and, in the Portal Content, choose the following folder: Portal Content -> class
HR260-> Trainer Demo
Add the Team Explorer iView to dynamic navigation. To do this, right-click the
iView and choose “Add to Dynamic Navigation”. Save the page.

1-4 Add the page that you have created to the “Employee Review” workset.
NOTE: To ensure that you do not lock the “Employee Review” workset for
editing, thus preventing other participants from accessing the workset, wait until the
instructor tells you that you can edit the workset.
To do this, choose the following folder in the Portal Content: Portal Content ->
Migrated Content-> EP 5.0-> Worksets -> Employee Review. Right-click the
workset and choose “Open” -> “Object”.
Search for the page that you have just created (“XX Page with Team Explorer”) in
the Portal Content. Right-click the page and choose “Add Page to Workset” ->
“Delta Link”. Choose “Refresh” and close the workset.

1-5 Check your new page.
Choose “My Staff” (role on the right) -> Employee Review -> XX Page with Team
Explorer.



© SAP AG HR260 12-569
© SAP AG 2006
Appendix: Homepage Framework: Overview Diagram
Unit 1 MSS Overview
Unit 2 Manager Self-Service Fundamentals in the Enterprise Portal
Unit 3 The Employee Review Workset
Unit 4 The Compensation Workset
Unit 5 The ESS Workset in MSS
Unit 6 The Team Calendar Workset
Unit 7 The Personnel Change Requests (PCR) Workset
Unit 8 The Recruitment Workset
Unit 9 The Reporting Workset
Unit 10 The Headcount Workset
Unit 11 Team Viewer
Appendix Homepage Framework




© SAP AG HR260 12-570
© SAP AG 2006
¤ Homepage framework structure
Þ Area group
Þ Area group page
Þ Area page
Þ Subarea
Þ Resources
Þ Services
¤ Homepage framework
Customizing
Contents:
Homepage Framework




© SAP AG HR260 12-571
© SAP AG 2006
¤ Explain the homepage framework structure
¤ Name the elements of the homepage framework
¤ Describe homepage framework Customizing
¤ Develop your own scenario
After completing this appendix, you will be able to:
Appendix: Homepage Framework: Objectives




© SAP AG HR260 12-572
© SAP AG 2006
¤ You are part of a project group that wants to
implement MSS. Your task is to examine how to
define the homepage framework in order
to incorporate your own areas into the homepage.
Appendix: Homepage Framework: Business Scenario




© SAP AG HR260 12-573
© SAP AG 2006
Homepage Framework - Features
¤ Replace pictograms (images) on area group pages and area
pages
¤ Define long area description
¤ Create customer-specific area with services
¤ Do not display areas from the standard delivery
¤ Add services to an area of the standard delivery
¤ Do not display services from the standard delivery
The homepage for Manger Self-Service offers the following
functions for modifying overview pages for your Self-Service
applications or for creating your own overview pages:



Þ The Homepage for Manager Self-Servicegenerates overview pages that facilitate manager's
access to Self-Service applications (services). These overview pages are displayed in the SAP
Enterprise Portal. They group and describe the services and contain hyperlinks with which
your line managers can start services.
Þ The Homepage for Self-Services has two types of overview pages:
º Area group pages - area group pages are often called homepages
º Area pages
Þ You can make numerous settings to modify the overview pages in the standard delivery to suit
your requirements, or to create your own overview pages.

© SAP AG HR260 12-574
© SAP AG 2006
Homepage Framework I
Subarea
Quick Links to
Service
Area Group Page
Areas



Þ When they select the "My Staff" role, line managers get an overview of the possible services
in a homepage that they can execute. In the standard delivery, the homepage is divided into
five areas that correspond to the worksets:
º Attendance
º Personnel Change Requests
º Recruitment
º Reporting
º Headcount
Þ The individual areas consist of subareas, which in turn contain the actual services that can be
executed.
Þ Area pages include services (Web applications) that are related to each other. Line managers
access an area page from an area group page.

© SAP AG HR260 12-575
© SAP AG 2006
Homepage Framework II
Service
Subarea
Area Page



Þ You can compare subareas with headers and subheaders in a document. With subareas you
group the services that belong to an area on the screen. You must define at least one subarea
for each area.
Þ A service is a Web application that appears on area pages or subareas. For each service that
you define, a hyperlink and a short description appear on the appropriate area page.
Þ Line managers use this link to start the service. You can make a multitude of settings to define
where and how the hyperlink to the service appears.


© SAP AG HR260 12-576
© SAP AG 2006
Homepage Framework III
Area Group Text
Area Link Text
Area Short Description
Quick Links
Graphic



Þ The definition of the area group page is extremely flexible. You can easily add text elements,
graphics and so on.
Þ The figure above displays the individual elements of an area group page.

© SAP AG HR260 12-577
© SAP AG 2006
Homepage Framework IV
Area Link Text
Subarea Name
Service Link Text
Service Description
Graphic



Þ It is also easy to modify the area page.
Þ You can change the following text elements:
º Area Link Text
º Subarea Name
º Service Link Text
º Service Description
Þ You can also modify the subarea graphic.


© SAP AG HR260 12-578
© SAP AG 2006
Homepage Framework V
Long Text
of Area Description
Header
of Area Description



Þ You can also define individual information on the area pages. On the right-hand side you can
define your own descriptions or links to descriptions, such as leave ruling.

© SAP AG HR260 12-579
© SAP AG 2006
Before You Start
¤ Create a graphical draft of the areas and services you
want to implement
¤ This clarifies the hierarchical relationship between
the individual elements
¤ Create a list of the necessary resources



Þ Before you start Customizing you should create a graphical draft of the homepage framework.
This highlights the dependencies of the individual elements. This simplifies Customizing.
Þ Also create a list of the necessary resources.

© SAP AG HR260 12-580
© SAP AG 2006
Structure of Area Group Page
Resource R1...Rr
Service Group SVG1...SVGg
Server SV1...SVs
Subarea UB1
Subarea UBm
...
Header Area Ki
Header Area K1
...
Area Group BGi
Area Group BG1
...
Area B1
Area Bn
...
Service S1
Service Sk
...



Þ An area page may have the structure depicted in the graphic.
Þ A homepage can also be described as an area group page.
Þ Technically, it is composed of a hierarchical structure. Consequently, an area page consists of
areas, an area of subareas, and finally, a subarea contains the Web services that you can
execute.

© SAP AG HR260 12-581
© SAP AG 2006
Example of an Area Group Page
Resource R1...Rr
Servi ce Group SVG1...SVGg
Server SV1...SVs
Subarea UB1 =
New Change Request
Subarea UBm
Header Area H1
Area Group BG1 =
Manager Self-Servi ce
Area B1 = Personnel Change
Request
Area Bn
...
Servi ce Sm
Service Sk
...
Subarea UB2 =
Status Overview
Servi ce S2 =
nnn
Servi ce S1 =
Create Change Request
Servi ce S5 =
xxx
Servi ce S4 =
nnn
Service S3 =
Di splay Status Overvi ew



Þ This is an example of the structure of the area group page within Manager Self-Service.

© SAP AG HR260 12-582
© SAP AG 2006
Define a Homepage Framework
Step-by-Step
1. Define header area (optional)
2. Define area group
3. Define area group page
4. Define services (with country-specific service)
5. Define resources



Þ The figure above outlines the necessary steps for defining a homepage framework in the
correct order.

© SAP AG HR260 12-583
© SAP AG 2006
Homepage Framework Customizing



Þ For homepage framework Customizing, see the IMG, under:
º Cross-Application Components -> Homepage Framework
Þ Here you can position the required area group pages, areas, subareas and services on the
homepage.

© SAP AG HR260 12-584
© SAP AG 2006
Definition of Header Area
View V_T7XSSSERRES
View V_T7XSSSERHEB



Þ In view V_T7XSSSERHEB - Define Headers (Add Entries) you define the header areas of
your homepage. A header area consists of a screen and a welcome text for line managers.
Þ You must define at least one header area.

© SAP AG HR260 12-585
© SAP AG 2006
Area Group Page
View V_T7XSSSERARGB



Þ In view V_T7XSSSERARGB - Define Area Group Pages (Add Entries) you define area group
pages. Area group pages contain descriptions of areas, hyperlinks for accessing area pages,
and hyperlinks for directly starting services.
Þ You must define at least one area group page.
Þ If you define an area group page for each role, you can also call the different area group pages
homepages.

© SAP AG HR260 12-586
© SAP AG 2006
Assigning Areas to an Area Group Page
1 2
3
4
5
View V_T7XSSSERARG



Þ In view V_T7XSSSERARG - Assign Areas to Area Group Pages (Search for Entries) assign
an area group page to each area and define its position.
Þ You can also hide an area on an area group page. Goto customer view V_T7XSSSERARGC
and copy the entry from SAP view V_T7XSSSERARG. Assign position 0 to it.
Þ If you want to add your own areas to an area group page, enter the area group page in
customer view V_T7XSSSERARGC and assign your areas to it. This applies both to area
group pages provided by SAP as well as your own.


© SAP AG HR260 12-587
© SAP AG 2006
Define Area Page I
View V_T7XSSSERARB
Definition in View
V_T7XSSSERRES



Þ In view V_T7XSSSERARB - Define Area Page (Add Entries) you define area pages. Area
pages include services (Web applications) that are related to each other. Line managers access
an area page from an area group page.
Þ In this view you also maintain the image resource and the link to the resource.
Þ You must define at least one area page.

© SAP AG HR260 12-588
© SAP AG 2006
Define Area Page II
View V_T7XSSSERARB
Options for Describing the Area:
1) Text from Area Description
or
2) External HTML Page



Þ In view V_T7XSSSERARB - Define Area Page (Add Entries) you define both the header and
associated long text for the area description.
Þ Alternatively you can specify an HTML page that contains the long text, using the technical
name of the resource object.

© SAP AG HR260 12-589
© SAP AG 2006
Define Resources
View V_T7XSSSERRES
Resource: Screen File Resource: Page in Portal



Þ In view V_T7XSSSERRES - Define Resources (Add Entries) you define the images that
appear on a page, or the URL of the page in the Portal Content Directory (PCD).
Þ You can reuse resources on the pages that you define. If you define a URL as a resource, you
must also provide the relevant content where the URL links to.
Þ Note that some fields in this view only apply to particular types of resources. If, for example,
the resource object is a service, it is useful to enter a URL parameter. If the resource object is
an image, entering URL parameters is not useful. For the possible input combinations, see the
documentation on defining resources in the IMG.

© SAP AG HR260 12-590
© SAP AG 2006
Define Subareas
View V_T7XSSSERSARB
View V_T7XSSSERAR



Þ In view V_T7XSSSERSARB - Define Subareas (Add Entries) you define subareas. You can
compare subareas with headers and subheaders in a document. With subareas you group the
services that belong to an area on the screen.
Þ You must define at least one subarea for each area.
Þ In view V_T7XSSSERAR - Assign Subareas to Areas (Search for Entries) assign an area
page to each subarea and define its position.
Þ You can hide a subarea on an area page. Goto customer view V_T7XSSSERARC and copy
the entry from SAP view V_T7XSSSERAR. Assign position 0 to it.
Þ If you want to add your own subareas to an area page, enter the area page in customer view
V_T7XSSSERARC and assign your subareas to it. This applies both to area pages provided
by SAP as well as your own.


© SAP AG HR260 12-591
© SAP AG 2006
Define Services
View V_T7XSSSERSRV



Þ In view V_T7XSSSERSRV - Define Services (Add Entries) you define the services (Web
applications) that appear on the area pages. For each service that you define, a hyperlink and a
short description appear on the appropriate area page.

© SAP AG HR260 12-592
© SAP AG 2006
Quick Link
View V_T7XSSSERSRV



Þ Line managers use this link to start the service. You can make a multitude of settings to define
where and how the hyperlink to the service appears.
Þ If you regularly use a service, you can show an additional hyperlink on the area group page
that directly calls the services. Select the Quick Link indicator in view V_T7XSSSERSRV.
Line managers then have faster access.

© SAP AG HR260 12-593
© SAP AG 2006
Assign Services to Subareas
View V_T7XSSSERSRV
View V_T7XSSSERSAR



Þ If you want to temporarily deactivate the hyperlink to a service, you can set the indicator in
view V_T7XSSSERSRV. The link text still appears to be normal on the screen, but the system
removes the hyperlink.
Þ In addition, you can define an extensive service description that is displayed in the subarea for
the service.
Þ In view V_T7XSSSERSAR - Assign Services to Subareas (Search for Entries) assign a
service to each subarea and define its position.
Þ You can hide a service in a subarea. Goto customer view V_T7XSSSERSARC and copy the
entry from SAP view V_T7XSSSERSAR. Assign position 0 to it.
Þ If you want to assign your own services to a subarea, enter the subarea in customer view
V_T7XSSSERSARC and assign your services to it. This applies both to subareas provided by
SAP and your own subareas.

© SAP AG HR260 12-594
© SAP AG 2006
<No Entri es Here>
Define Country-Specific Services
View V_T7XSSSERSRVCG
View V_T7XSSSERSRV



Þ In this IMG activity you define country-specific services. When an employee calls a service,
the system determines the country grouping of the employee and checks whether there is a
country-specific service description in views V_T7XSSSERSRVCG and
V_T7XSSSERSRVCGC.
Þ If there is a country-specific service description the system uses it.
Þ If there is not a country-specific service description the system uses the general service
description in views V_T7XSSSERSRV and V_T7XSSSERSRVC.
Þ This enables you to define country-specific variations of some services for certain countries
and simultaneously use a general service description for all other countries.

© SAP AG HR260 12-595
© SAP AG 2006
Dependencies of Customizing Views
V_T7XSSSERARB – Define Area Page
V_T7XSSSERARGB –
Define Area Group Pages
V_T7XSSSERARG – Area Group Pages
Assign Areas
V_T7XSSSERSARB –
Define Subareas
V_T7XSSSERAR –
Assign Subareas to Areas
V_T7XSSSERSRV - Define Services
V_T7XSSSERSAR –
Assign Services to Subareas
V_T7XSSSERRES - Define Resources



Þ This overview shows you the dependencies of the homepage framework.

© SAP AG HR260 12-596
© SAP AG 2006
Overview of Homepage Framework Views
Define service groups (change
entries)
V_T7XSSSERSRVG Define service groups (add
entries)
V_T7XSSSERSRVG
Define country-specific services
(change entries)
V_T7XSSSERSRVCGC Define country-specific services
(add entries)
V_T7XSSSERSRVCG
Define services (change entries) V_T7XSSSERSRVC Define services (add entries) V_T7XSSSERSRV
No customer table Define server V_T7XSSSERSDB
Define subareas (change entries) V_T7XSSSERSARBC Define subareas (add entries) V_T7XSSSERSARB
Assign services to subareas (add
and change entries)
V_T7XSSSERSARC Assign services to subareas
(search for entries)
V_T7XSSSERSAR
Define resources (change entries) V_T7XSSSERRESC Define resources (add entries) V_T7XSSSERRES
Define headers (change entries) V_T7XSSSERHEBC Define headers (add entries) V_T7XSSSERHEB
Assign areas to area group pages
(add and change entries)
V_T7XSSSERARGBC Define area group pages (add
entries)
V_T7XSSSERARGB
Define area group pages (change
entries)
V_T7XSSSERARGC Assign areas to area group
pages (search for entries)
V_T7XSSSERARG
Define area pages (change entries) V_T7XSSSERARBC Define area page (add entries) V_T7XSSSERARB
Assign subareas to areas (add and
change entries)
V_T7XSSSERARC Assign subareas to areas (search
for entries)
V_T7XSSSERAR
Name Customer View Name SAP View



Þ This gives you an overview of the views that are necessary for homepage framework
Customizing. The SAP views are on the left-hand side and they include the preset entries. If
you want to add or change entries, maintain the customer views that end with the letter "C"
(customer).
Þ For extensive documentation on configuring the homepage framework, see:
º http://help.sap.com -> Documentation -> mySAP ERP -> Language English or German ->
SAP Library -> SAP ERP Central Component -> Cross-Application Components ->
Manager Self-Service -> General Settings -> Self-Services Homepage

© SAP AG HR260 12-597
© SAP AG 2006
Table Assignment Overview
Resource R1...Rr
Service Group SVG1...SVGg
Server SV1...SVs
Header Ki
Header K1
...
Area Group BGi
Area Group BG1
...
Area B1
Area Bn
...
Subarea UB1
Subarea UBm
...
Service S1
Service Sk
...
VI EW V_T7XSSSERARG
VI EW VV_T7XSSSERAR
VI EW V_T7XSSSERSAR
VI EW V_T7XSSSERSRVCG
VI EW V_T7XSSSERHEB
VI EW V_T7XSSSERARGB
VI EW V_T7XSSSERARB
VI EW V_T7XSSSERSARB
VI EW VV_T7XSSSERSRV
VI EW VV_T7XSSSERSRVG
VI EW V_T7XSSSERRES
VI EW V_T7XSSSERSDB



Þ In this view you can see in exactly which tables the individual objects and their assignments
are defined.

© SAP AG HR260 12-598
© SAP AG 2006
Homepage Framework Application Parameter
View V_T7XSSSERHEB
View V_T7XSSSERARGB



Þ On this page you can see the Content Administration for the overview pages in the Enterprise
Portal. In the Application Parameters property you can see the assignment of the parameters
sap.xss.menuhdr and sap.xss.menuargrp.
Þ Parameter sap.xss.menuhdr determines which area group is displayed in the menu (from view
V_T7XSSSERARGB)
Þ Parameter sap.xss.menuargrp determines which header area is displayed (from view
V_T7XSSSERHEB)
Þ For additional parameters for the Overview iView, see the end of the unit.

© SAP AG HR260 12-599
© SAP AG 2006
Parameters for XssMenu and XssMenuArea
This parameter does not have any
values.
Determines that extensive error
messages are displayed
sap.xss.debug
This parameter is recommended during
Customizing as in this case changes in
system Customizing affect the menu
applications immediately.
You must not use this parameter in
production operation as this has a
considerable adverse affect on
performance and resources.
Switches Caching/buffering of the data
read from the SAP system off.
sap.xss.menunobuffer
This parameter does not have any
values. If it is available, Caching is
switched off and the system does not
display the header area.
Determines that the header area is not
displayed
sap.xss.disablehdr
Entries in the IMG activity Areas →
Define Areas
Determines the area displayed in the
menu
sap.xss.menuarea
Entries in the IMG activity Header Area
and Area Group Pages →Define Area
Group Pages
Determines the area group displayed in
the menu
sap.xss.menuargrp
Entries in the IMG activity Header
Area and Area Group Pages →Define
Header Areas
Determines the displayed header area sap.xss.menuhdr
Possi ble Values Meaning Parameter



Þ In the overview above you can see the possible parameters for the overview iView, and their
meaning.
Þ The IMG paths in the "Possible Values" column are always relative to the following path:
Cross-Application Components -> Homepage Framework

© SAP AG HR260 12-600
© SAP AG 2006
¤ Explain the homepage framework structure
¤ Name the el ements of the homepage framework
¤ Describe homepage framework Customizing
¤ Develop your own scenario
You are now able to:
Appendix: Homepage Framework: Summary