HR250 SAP Employee Self-Service HR250 · 2019. 4. 18. · ©SAP AG 1999 Target Group zAudience: HR and Intranet project team members responsible for implementing SAP Employee Self-Service

HR250 SAP Employee Self-Service HR250

Release 640 04/06/2006

© SAP AG 2002

HR250 SAP Employee Self-Service

THE BEST-RUN E-BUSINESSES RUN SAP

HR250Employee Self-Service

SAP R/3 4.6C, Workplace 2.11 2003/Q1 5004 3566

© SAP AG 2004

Copyright 2004 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 permission of SAP AG. The information contained herein may be changed without prior notice.

Copyright

Some software products marketed by SAP AG and its distributors 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 United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the 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 invented and

implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, 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 are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG 2002

Course Prerequisites

Required:HR051 Human Resources Essentials I

HR052 Human Resources Essentials II

Knowledge of the Human Resources application you want to Web enable

Highly Recommended:HR053 Human Resources Essentials III

HR305 Configuration of Master Data

HR940 Authorizations in HR

© SAP AG 1999

Target Group

Audience:HR and Intranet project team members responsible for implementing SAP Employee Self-Service

Duration: 2 days

Hints for the user

This training material is not a self-teaching program. The training material will only be complete in combination with the trainer's explanations. Your training material leaves room for writing down this additional information.

(C) SAP AG HR250 1-1

© SAP AG 1999

Course Goals

Course Objectives

Course Content

Course Overview Diagram

Main Business Scenario

Contents

Course Overview


© SAP AG 1999

The philosophy behind SAP Employee Self-Service (SAP ESS)

The SAP ESS services

Customizing SAP ESS

The mySAP Workplace and the Employee Self-Service role

The technical infrastructure of SAP ESS

SAP ESS user administration

Planning and implementing SAP ESS

Adapting and enhancing SAP ESS

Course Goals

This course teaches you about:


© SAP AG 2002

Explain the SAP ESS philosophy

Explain and use the SAP ESS services

Describe and perform the steps necessary to customize SAP ESS

Describe the mySAP Workplace and the Employee Self-Service role

Maintain SAP ESS users

Explain the necessary steps for a successful SAP ESS implementation

Describe the technical infrastructure of the mySAP Workplace and SAP ESS

Course Objectives

At the conclusion of this course, you will be able to


© SAP AG 1999

Unit 6 Customizing SAP ESS

Unit 7 Enhancing SAP ESS

Unit 8 Planning andImplementation

Unit 9 Conclusion

Unit 1 Course Overview

Unit 2 Introduction to SAP ESS

Unit 3 SAP ESS Services

Unit 4 mySAP Workplace: Architecture and Roles

Unit 5 User Management

Preface

Appendix

Course Content


© SAP AG 1999


Course Overview

Introduction to SAP ESS

SAP ESS Services

User Management

Customizing SAP ESS

Summary

Planning and Implementation

Enhancing SAP ESS

mySAP Workplace: Architecture and Roles


© SAP AG 1999

The Caliber A Bicycle Company is an international company that sells bicycles and bicycle accessories.

The Caliber A Bicycle Company has already implemented the SAP Human Resources applications and is now evaluating SAP Employee Self-Service (SAP ESS) to become the Intranet portal for their employees.

SAP ESS should support the employees in their daily work and serve as a tool for using e-mail to find information and to enter and maintain personal data. It should also be used to perform such tasks as entering travel expenses and recording working time.

Main Business Scenario


© SAP AG 1999

What is SAP Employee Self-Service (SAP ESS)?

The Philosophy

The Highlights

The Benefits

The SAP Internet Strategy: mySAP.com®

The Changes to Release 4.6C


Contents


© SAP AG 1999


Describe the features of SAP ESS

Discuss the benefits of SAP ESS

Describe the relationship between SAP ESS and mySAP.com®

Specify the most important new features of SAP ESS in Release 4.6C

At the conclusion of this unit, you will be able to:

Introduction to SAP ESS : Unit Objectives


© SAP AG 1999


Course Overview


SAP ESS Services

User Management


Summary

Enhancing SAP ESS

Customizing SAP ESS



© SAP AG 2002

The Caliber A Bicycle Company is implementing SAP Employee Self-Service.

SAP ESS provides employees with a powerful information and service portal accessible through their desktop computer.

This streamlines processes that are paper based and administratively intensive within the company.

Introduction to SAP ESS : Business Scenario


© SAP AG 1999


Basic Features of SAP ESS

SAP ESS in the mySAP.com® Context

11

22


© SAP AG 1999

The Personnel Department without ESS

Heavy work load caused by administrative and repetitive tasks in the personnel department

Enterprise processes are carried out using paper or informally

Data is entered more than once and is processed by:

Employees

Managers

Computer personnel

RESULT:

Poor data quality and data redundancy

Inefficiency

Overworked human resources department


© SAP AG 2002

SAP Employee Self-Service (SAP ESS) includes a number of easy-to-use Web applications with which every employee in an enterprise can create, display, and maintain data in the R/3 System using a browser.SAP ESS offers transactions for:

OfficeWorking timeBusiness tripsBenefitsJobsPaymentPersonal informationTrainingSkillsAppraisalsLife and work events

What is SAP Employee Self-Service?

SAP ESS is an efficient means of accessing and maintaining data in real-time. It permits the off-load of data entry activities and related tasks that are typically performed in a company's human resources, payroll, benefits and travel departments.

SAP Employee Self-Service (SAP ESS) empowers employees to view, create, and maintain data any time, anywhere through their Web browser.

SAP ESS has an intuitive user interface and is therefore ideal for casual users.

SAP ESS provides a number of services for a variety of areas.

ESS development is currently working on Life and Work Events, in which the application and information are combined in a way that supports employees in their decisions.


© SAP AG 2002

Employees maintain their own data

Employees are responsible for some of their personal data

Information is supplied for all employees

Simple and intuitive use

Let them do it themselves!

SAP ESS - The Philosophy

SAP ESS currently provdes more than 70 services. Using SAP ESS employees can

Search the Who's Who Look in their calendar Check workflow work items Submit travel expenses Enter their working times Enroll themselves for benefits

Employee information can be obtained using SAP ESS: Individual information (Payroll Result, Time Management, Travel Expenses, Skills...)

"Public information" (Who's Who, Calendar, Training Center, Employment Opportunities, ...)

SAP ESS is intuitive and easy to use.


© SAP AG 2002

SAP ESS - The Highlights

Wide scope of functions

Can be personalized

Intuitive use

No double customizing

Workflow-enabled

Country-specific, languages, and currencies

Access at any time from any place

SAP ESS leverages the power of SAP, taking full advantage of R/3 business logic and functionality, security, and audit functionality. SAP ESS primarily includes human resources capabilities, but also offers logistical, financial and office functionality. SAP ESS utilizes the same database as the R/3 System. As a result, no dual customizing or reconciliation is required.

All the SAP ESS services are workflow-enabled. They work with the same R/3 business objects as the R/3 System. If activities in the business objects trigger workflow events in R/3, then the same activities will trigger workflow events in SAP ESS.

SAP ESS inherits the international architecture of the R/3 System, with its unsurpassed language and currency management capabilities. It takes full advantage of the global capabilities of the R/3 System, including country localization.

SAP ESS requires the mySAP Workplace, which can be used with the Microsoft Internet Explorer (or with the Netscape Navigator Release 6.0) under the Windows, Mac OS and Unix operating systems.

The mySAP Workplace provides an intuitive and easy-to-use user interface that can be personalized. The screens for the ESS services only contain the R/3 information that is relevant for the enduser. Little to no training is required.

The SAP ESS menu and the individual SAP ESS services can be customized and enhanced. The appearance of the SAP ESS services can be adapated to match the look and feel of the company's Intranet and corporate identity.

(C) SAP AG HR250 2-10

© SAP AG 2002

SAP ESS - The Benefits

Various intuitive services

Greater employee satisfaction

Improved data quality and more efficient processes

Time savings for employees, managers, and human resources personnel

Cost savings:Personnel costs

Printing and shipment costs

Avoids double maintenance

Costs for error correction

Simple link between application and information using Life and Work Events

By enabling employees to maintain their own data and to have access to individual as well as public information, companies empower employees to take responsibility and ownership. This increases employee satisfaction and improves the accuracy of data.

Companies' human resources departments are freed from many of the data entry and related customer service activities.

Companies save money by reducing the costs of paper, postage and data entry. Time is saved by eliminating bureaucratic processes, thereby releasing those resources. SAP ESS does not require expensive, time-consuming training.

If the life or work environment of an employee changes, the employee is supported in his decisions by the application and by context-specific information.

SAP ESS is part of the R/3 core system as of Release 4.5

(C) SAP AG HR250 2-11

© SAP AG 1999


Basic Features of SAP ESS

SAP ESS in the mySAP.com® Context

11

22

(C) SAP AG HR250 2-12

© SAP AG 1999

INTEGRATEDPERSONALIZED

COLLABORATIVE

Platform for business collaborationIndustry-specificIntegrated, general business processes

Relationship building (communities)External services integration (content)

One-step business (collaboration)Application hosting

Internet business framework

CustomizableRole-specific

Single point of access to all internal and external

services

The SAP Internet Strategy: mySAP.com ®

mySAP.com® is the SAP strategy for providing customer solutions. The name mySAP.com® has the three components:

my

my stands for easy access to all the elements of mySAP.com®

The mySAP Workplace provides users with personalized, role-specific access to the system.

SAP ESS is completely integrated in the mySAP Workplace. The Workplace is responsible for access and navigation.

SAP

SAP stands for the powerful enterprise software provided using the Internet.

.com

.com stands for SAP's commitment to the Internet economy.

Business relationships and collaboration can be initiated and deepened using the Internet.

(C) SAP AG HR250 2-13

© SAP AG 1999

The Elements of mySAP.com®

Application Hosting Business Scenarios

Workplace Marketplace

Main elements of mySAP.com®

The mySAP Workplace is an enterprise portal providing easy access to all system functions. The user logs on once, after which access is possible to all mySAP applications.

The mySAP Marketplace is a portal for collaboration between multiple enterprises using the Internet. There are four main areas. Enterprises that are listed in the industry directory of the Marketplace can take advantage of one-step business and can participate in industry-specific trade and communication forums.

SAP has developed a number of business scenarios that simplify trade and communication. SAP customers can use their mySAP components with hardware and software that is provided externally by SAP and its partners. This procedure is called Application Hosting and can be selected after implementation.

(C) SAP AG HR250 2-14

© SAP AG 1999

The mySAP Workplace

Company boundary

WorkplaceIndustry-specific

Role-specificMatches needs

Drag&Relate

Market-place

3.1HR/3 4.6

FIFI LOLOHRHR

CRMCRMKWKW

BBPBBPSEMSEM

APOAPO

BWBW

CFMCFMmySAP.com components

OpenInternet

Standards

R/2R/2

OthersExternalSystems

Partner

SAPSAP

internal

external

mySAP.com Internet servicesOther Internet services

VariousERP Systems

SingleSign-On

ESSESS

With Release 4.6C SAP Employee Self-Service is an integral part of the mySAP Workplace.

The mySAP Workplace is a role-oriented portal giving employees unified access to all the necessary applications, information and services needed for their daily work at any time and at any place using the Web browser.

Only a single logon is required for access to the Workplace and the applications it provides (Single Sign-On).

SAP delivers a catalog of predefined role templates allowing companies to get up and running quickly with the mySAP Workplace. Customers are free to customize these roles or define new ones of their own. Roles are centrally maintained. When a role is updated, all assigned users can automatically take advantage of the new additions.

Users can configure the Workplace themselves. The Workplace is also delivered to suit the customer's needs in a number of industry-specific and role-specific versions. By inserting links and transactions that are frequently called, the Workplace can be configured to the requirements of the individual user. The Drag&Relate function is already implemented.

The Workplace provides access to a number of mySAP.com and external components. R/3 Systems are internet- and intranet-enabled with Release 3.1H.

(C) SAP AG HR250 2-15

© SAP AG 2002

The mySAP Marketplace

One-Step Business

CommunitiesCommunities CommerceCommerce

ContentContent CollaborationCollaboration

http://marketplace.mysap.com

The mySAP Marketplace is divided into four main areas. Companies can join a virtual industry community in the "Communities" area. The members of these communities exchange information in discussion forums. The "Communities" support and encourage inter-enterprise collaboration.

The Marketplace also offers contents that are constantly updated. This includes comments about industry-relevant events, industry news and trend information. The user can also display the current stock market prices in a portfolio that can be configured to his requirements.

There is a separate industry directory for the Commerce area. Enterprises entered in the Marketplace offer their products and services here. Unified processing of a transaction ("one-step business") is possible due to the integrated exchange of business documents. You can subscribe to a number of online services on the start page of the Marketplace.

The mySAP Marketplace also supports internet-supported collaboration between the enterprises. The Marketplace permits one-step business: Goods and services can be bought and sold in a single step in the Marketplace. Two processing systems ensure correct financial transactions in the background.

(C) SAP AG HR250 2-16

© SAP AG 1999

Application Hosting

Hosting by SAP & Partner

ProductionProductionCustomer Solution

Internet

......BWBW HRHR

......BWBW

Test phaseTest phase ConfigurationConfiguration ImplementationImplementation ProductionProduction

ImplementationImplementation

HRHR

Application Hosting is divided into four phases: Testing (the customer tests the suggested solution), configuration (definition of the solution), implementation and operation (internally or online by SAP & partners). In the test phase, those interested can test whether mySAP.com satisfies the company's requirements. A user account is set up for IDES, the SAP Internet demo system for the various industries.

During configuration, the customer can define his individual solution. You can configure SAP ESS using a special Solution Map or directly in the system by answering simple catalog questions.

Implementation takes place once the customer-specific SAP solution has been created. This can be done in two ways:

- The customer installs hardware and software locally and implements the project.

- SAP provides all the hardware and software needed by the customer in the implementation phase.

After implementation, the customer can either run his production system himself (internal solution) or have it run externally by SAP or one of its partners. SAP's Application Hosting reduces the costs for new hardware and software maintenance. The customer only needs a Web browser for accessing the Internet.

(C) SAP AG HR250 2-17

© SAP AG 1999

Business Scenarios

Business Partner

CustomerVendorVendor

Employee Employee SelfSelf--ServiceService

BusinessBusiness--toto--Business Business

ProcurementProcurement

CollaborativeCollaborativeApplicationsApplications

PurchasingPurchasing OnlineOnlineSalesSales

Invoice/Invoice/PaymentPaymentPaymentPayment

CollaborativeCollaborativePlanningPlanning

OnlineOnlineServicesServices

Employee

Business-to-Business Procurement (BBP) and Employee Self-Service (ESS) are examples of business scenarios. Vendors can use SAP BBP to offer their product catalogs in the Internet or in company Intranets. Sales and procurement use the World Wide Web.

With SAP ESS, employees can for example order their own office supplies or maintain their personal data. Purchase orders, requests and their modifications are passed to the SAP background system. The first ESS scenarios were presented in 1996 in Release 3.1G.

Collaboration between business partners primarily involves cross-site planning and forecasting. The parties involved hereby access the commonly used applications and the online services of external vendors as required.

(C) SAP AG HR250 2-18

© SAP AG 2002

SAP ESS 4.6C and mySAP.com®

New functions were added and existingfunctions were enhanced.

The mySAP Workplace replaces the earlier ESS menu.

SAP Employee Self-Service is now represented by the role Employee Self-Service.

What are the implications of mySAP.com®

and R/3 System Release 4.6C on SAP Employee Self-Service ?

With Release 4.6C, you can only call the SAP Employee Self-Service applications from the mySAP Workplace.

Your ESS licenses automatically authorize you to use the mySAP Workplace for the SAP Employee Self-Service. Note that these licenses do not authorize you to use the mySAP Workplace for other SAP components. You have to purchase these licenses separately.

As an ESS customer you are given the mySAP Workplace upon request.

(C) SAP AG HR250 2-19

© SAP AG 2002


Describe the features of SAP ESS

Discuss the benefits of SAP ESS

Describe the relationship between SAP ESS and mySAP.com®

Specify the most important new features of SAP ESS in Release 4.6C

You are now able to:

Introduction to SAP ESS : Unit Summary


© SAP AG 1999

Contents

Navigation in the mySAP Workplace

Employee Self-Service Role

SAP ESS Services

SAP ESS and Workflow

Life and Work Events

SAP ESS Services


© SAP AG 2002


The SAP ESS Services: Unit Objectives

Navigate in the mySAP Workplace

Describe the SAP ESS services

Describe the relationship between SAP ESS and Workflow

Briefly describe Life and Work Events


© SAP AG 1999

SAP ESS Services

Course Overview


User Management


Summary

Enhancing SAP ESS

Customizing SAP ESS




© SAP AG 2002

The Caliber A Bicycle Company wants to offer an Intranet service portal to its employees.

To reduce the expense, time, and resources required of a modified Intranet, the Caliber A Bicycle Company wants to review what is available in the standard delivery of SAP Employee Self-Service.

SAP ESS Services: Business Scenario


© SAP AG 1999

SAP ESS and Workflow44

Life and Work Events55

SAP ESS Services 33

Navigation in the mySAP Workplace11

Employee Self-Service Role22



© SAP AG 2002

Welcome Willi Workplace

mySAP.com Marketplace Update Adapt Info

FavoritesFinancial AccountingSales

Display Inquiries

Wonderland Enterprises

Display RequestCreate Request

Meyer, Inc.

InfosystemsGeneric Services

1

2

WorkSpace (MiniApps, Transactions, Websites)LaunchPad

ChannelBar

Drag&Relate

Inbox

Elements of the Workplace Browser Window

The Workplace is called by entering the corresponding URL (Internet address) in the Web browser. This usually is done by clicking on a link (and not manually). The syntax for the Workplace URL is typically <protocol>://<webserver>[:<port>]/scripts/wgate/sapwp/!, for example "https://workplace.wdf.sap-ag.de:1042/scripts/wgate/sapwp/!".

The Workplace browser window has three areas: Session Handling in the Workplace permits you to hold multiple applications in parallel in channels. The individual channels are displayed with icons in a vertical bar called the ChannelBar in the left part of the browser window. By clicking on the channel icons you can switch back and forth between the different applications.

When working with the Workplace you see your roles with the relevant entries in the LaunchPad. You can also add your own entries (favorites) to the LaunchPad.

When you log onto the Workplace, the list of MiniApps assigned to your role (such as stock ticker, news, overview lists, reports) as well as MiniApps that you added yourself are displayed in the WorkSpace to the right. If you start a certain transaction in the LaunchPad (such as the transaction for booking an invoice), this application is executed to the right in the WorkSpace.

With Drag&Relate you can link and execute objects of an application with another application by simply clicking them.


© SAP AG 1999

1

4

Favorites MiniApps General

LaunchPad Language Other

Display dialog for Drag&Relate

Use channels (requires restart)

Expand and collapseLaunchPad

Initial screen(for the MiniApps)

Channel busy

Current channel

Log off

Adapt

Channel free

ChannelBar Functions

The ChannelBar is at the left edge of the Workplace browser window. Only one channel is normally displayed the first time you log onto the Workplace. If you want to use all the channels, you have to adapt your ChannelBar. You go to a new window with Adapt. Mark Use channels on tab page Other of tab General.

You can show and hide the LaunchPad in the ChannelBar. By clicking on the channel icons you can go to different applications or navigate to the MiniApps. In this case you work with multiple browser windows that are all displayed directly in the Workplace (as frames). The lowermost button is used to log off.

You can assign an application to a channel. Channels that do not have a number are not assigned (free channels).

You can also assign a quickstart channel. This means that the channels are retained when you log off from the mySAP Workplace. You can start your application directly in the predefined channel the next time you log on.


© SAP AG 1999


Display Inquiries



Meyer Inc.

Information systemsGeneric Services

1

4


Web addresses Roles

http://www.mysap.com

SAP AG

Web address

Name

Test Replace Add

OK Terminate

New folder Delete Replace

Display in separate browser window

FavoritesWeb Addresses

YahooAlta VistaMetaGer

SalesCreate RequestDisplay RequestEvaluation

Adding transactionswith Drag&Drop

Testing and addingWeb addresses

Favorites in the LaunchPad

You can personalize the LaunchPad with favorites. You go to a new window with Adapt. You can create, rename, move and regroup your own folders in the left part of the Favorites tab page.

You can insert Web addresses (URLs) in the right part. These then appear in the LaunchPad in the Favorites. You should test your favorites with the "Test" button before adding them to the list of favorites. A favorite that needs the entire browser window for display is not suitable for the WorkSpace of the mySAP Workplace.

In the second tab page Roles on the right side you see the LaunchPad entries your system administrator assigned to you. They include for example transactions. If you use a transaction very frequently, you can define it as a favorite. Click on the relevant transaction and choose Add.

The favorites can also be enhanced and edited directly from the LaunchPad. With Drag&Drop you can insert frequently used transactions in the Favorites folder.


© SAP AG 1999


Display Inquiries



Meyer Inc.


1

4


Test Add

OK Terminate

Preview Delete

New MiniApps MiniApps Preview

Displayminimized

Web address

Name

Height 10 Lines

Display minimized

http://marketplace.mysap.com/General-Stocks

Stock Ticker

Search in WebReuters NewsCalculatorTerminated DeliveriesZSuperMini



Personalizing MiniApps

MiniApps are Web applications or documents that are easy and intuitive to use. When you start the Workplace, they give you a quick overview and access to your most important functions.

The MiniApps included in the WorkSpace are assigned to you by your system administrator, but you can also assign your own MiniApps.

You go to a new window with Adapt. You can add your own MiniApps to the right above New MiniApps on tab page MiniApps. Enter the Web address (URL), a name for the MiniApp and the height in lines. MiniApps should be tested before they are added. You can rename and move them afterwards with no difficulty.

The MiniApp display can be changed and adapted. For example the order in which the MiniApps are displayed in the Workplace can be changed or the display (expanded or collapsed) can be selected on the MiniApps tab page.

(C) SAP AG HR250 3-10

© SAP AG 1999

Easy to useRole-specific accessPersonalizedFlexible access

EfficientSingle Sign-On (SSO)Unified initializationDrag&Relate

OpenSingle Internet interfaceView on SAP and external componentsEnhanceable role specifications

Lower overall costsNo costs for installation at the PC workplaceStandardizationEasy maintenance

SecurityCentral administrationControlled access

Productivity

User Company

Workplace: Benefits

Both the user and the enterprise profit from the benefits provided by the Workplace.

(C) SAP AG HR250 3-11

© SAP AG 1999





SAP ESS Services 33

The Employee Self-Service Role

(C) SAP AG HR250 3-12

© SAP AG 2002

Role: Employee Self-Service

MiniApps

LaunchPad

mySAP Workplace: Employee Self-Service

A role menu is displayed at the left side of the screen when the user logs onto the mySAP Workplace. A number of MiniApps are displayed at the right.

The role menu contains all the employee's roles within the enterprise. One of these roles can be the Employee Self-Service role.

(C) SAP AG HR250 3-13

© SAP AG 2002

OfficeInboxCalendarWho's WhoChange Own Data 4.6CInternal Service Request 4.6CMy Assets 4.6C

Working TimeRecord Working Time (CATS)Create Leave RequestCancel Leave RequestDisplay Leave InformationDisplay Work ScheduleDisplay Time Statement

Business TripsTravel Management 4.6C

Life and Work EventsMy First Days 4.6CDivorce 4.6CBenefits 4.6CRole MenuRole Menu

The Employee Self-Service Role 1/3

(C) SAP AG HR250 3-14

© SAP AG 1999


BenefitsParticipation OverviewEnrollmentFSA Claims 4.6CRetirement Benefits 4.6C

JobsJob OpportunitiesApplication Status

PaymentPaycheck Inquiry

Employment and Salary VerificationExercising Employee Options 4.6CDisplay Total Compensation Statement 4.6C

Personal InformationAddressBank detailsPrevious EmployersEmergency AddressEmergency ContactFamily Member/DependentsNew Hire Data

(C) SAP AG HR250 3-15

© SAP AG 2002

MiniAppsWho's WhoDisplay PhotoWorkflow InboxMicrosoft Outlook InboxMicrosoft Outlook Calendar

Complete overview ofcountry-specific functionshttp://www.sap.com/ess


TrainingCourse Offering 4.6CMy Bookings 4.6C

SkillsEdit Skills ProfileDisplay Skills Profile 4.6CDisplay Requirements Profile 4.6CProfile Matchup with Own Position 4.6C

AppraisalsMy Appraisals 4.6C

(C) SAP AG HR250 3-16

© SAP AG 1999


Employee Self-Service Role

11

22

SAP ESS Services 33



SAP ESS Services

(C) SAP AG HR250 3-17

© SAP AG 1999

Inbox

Calendar

Who's Who

Change Own Data

Internal Service Request

My Assets

Office

Office

Employees can display e-mails and work items in their SAP office Inbox. They can display and process the work items to be executed as workflow steps. In this way all employees are involved in the workflow.

Employees can also maintain their own Calendar and display their colleagues' calendars.

They can look up data about other persons using the Who's Who.

With the Change Own Data service employees can maintain their own internal data such as telephone number and e-mail address. They can also include a photo if desired.

Employees can submit Internal Service Requests, such as ordering a shuttle to the airport or requesting support for computer problems. Possible solutions can be offered directly.

The My Assets service shows all the assets assigned to your personnel number. You can edit this data and report the removal of an asset if required.

(C) SAP AG HR250 3-18

© SAP AG 2002

Office - Who's Who

Calendar

Communication Who sent me this e-mail?

Is she available?

How will I recognize her?

Organizational Chart

Is he the right person?

Photo

Workflow

Who has to approve this?

Let's call him! Telephone

Who's Who supports internal communication. Employees can:

Look up the data of other persons

Find out their position in the company using the Organizational Chart

Use the Calendar to find out if they are available for a meeting Employees can maintain their internal data such as telephone number and e-mail address. Employees can add their own photo for display in the Who's Who.

(C) SAP AG HR250 3-19

© SAP AG 1999



Request service

Offer solution

Pass on

Cost control

Employees can submit Service Requests, such as ordering a shuttle to the airport or requesting support for computer problems.

Possible solutions can be offered directly. Employees can pass on the service requests for further processing using workflow integration. The service costs that ensue can be verified. Employees can check the status of their service requests.

(C) SAP AG HR250 3-20

© SAP AG 2002

Display assetsDisplay assets

Edit assetsEdit assets

Report asset removalReport asset removalReport asset removal

Asset accountingAsset accountingAsset accounting

EditEditEdit

Employee:My Assets

Employee:Employee:My AssetsMy Assets

My Assets

The My Assets service shows all the assets assigned to your personnel number. You can enhance the list with various selection criteria.

You can Display assets - You can display all the assets assigned to your personnel number in the asset master record.

Edit assets - You can edit the data for your assets (depending on your authorization profile).

Report asset removal - With a form you can report that an asset was removed and give an explanation. The person

responsible for processing the asset removal is informed by workflow.

(C) SAP AG HR250 3-21

© SAP AG 1999

Working Time

Working Time

Record Working Time

Create Leave Request

Display Leave Information

Display Work Schedule

Display Time Statement

Time Sheet (CATS) supports decentralized time recording.

Employees can enter their own work times and allocate the time to different accounting objects with the time sheet.

They can display a work list. They can also enter times or simplify data entry by copying existing time entries. They can save their time sheet and release the times for approval.

CATS provides an automatic calculation of hours worked based on clock times.

Employees can check how much leave they have available and request leave.

The request will be routed to the manager for approval or rejection.

Employees receive notification of their request (approved or rejected) in their integrated inboxes. (This service uses workflow and office inbox functionality).

Employees can also cancel an approved leave request.

Employees can display an overview of the current status of their time accounts. They can make various checks, such as for leave remaining and leave already approved.

Employees can display an overview of their calculated time balances. They can check how many hours they have worked in current or previous payroll periods.

Employees can view their current work schedules.

(C) SAP AG HR250 3-22

© SAP AG 1999

Workinghours

WorkingWorkinghourshours

PSPS

PMPM

CSCSCOCO

MMMM

CopyCopyCopyCATSCATS

COCOMMMM

HRPMPM

PSPSCSCS

Attend./AbsenceEmpl. Remun. Info.

Process Feedback

Internalactivityallocation Services

HR

DEU TS CHEM AR K

DEU TS CHEM AR K

DEU TS CHEM AR K

DEU TS CHEM AR K

Record Working Time (CATS)

CATS (Cross-Application Time Sheet) is a cross-component service for entering working times of individuals ina central time sheet.

You can define the layout of the time sheet yourself using an entry profile. Working times can be relevant for more than one target component at a time. Reports transfer the data to one or more target components.

The time sheet can be used to enter and transfer time data for the following target components: Controlling (CO): Internal activity allocation Human Resources (HR): Attendances, Absences, Employee remuneration statements Services (MM-SRV): Service entry for external services Plant Maintenance (PM), Customer Service (CS) and Project System (PS): Feedback for Orders or Networks

Important: Production Planning (PP) feedback is not supported by CATS because only time data and no machine or quantity data is entered in CATS.

(C) SAP AG HR250 3-23

© SAP AG 1999

Time Sheet

ApprovedApprovedRejectedRejected

Time Sheet (CATS)

Decentralized time recording

Automatic calculation of the working hours from clock times

The approval status of the times entered can be seen in the colored markings in the time sheet (Enter Working Time service).

Approved data has a green frame and rejected data has a red one.

(C) SAP AG HR250 3-24

© SAP AG 1999

Business TripsTravel Management

Travel Request

Travel Planning

Expense Reports

Business Trips

With SAP Travel Management you can efficiently and reliably carry out all the processes concerned with business trips, from the Travel Request to Travel Planning right up to submitting your Travel Expenses and transferring the travel expenses to other components.

Travel Request Enter general trip data, requested travel services and calculations Transfer to approving manager

Travel Planning Access non-vendor-specific information and book flights, hotels, rental cars and trains (e.g. Amadeus) Take internal travel rules into consideration in queries and bookings Possibly set up company-specific hotel catalog Take agreements with travel agencies into consideration Take personal preferences of the person traveling into consideration

Expense Reports Enter travel facts (centralized/decentralized) Invoice and book trips Pay travel expenses with Financial Accounting (FI), Payroll (HR) or by exchanging data carriers with banks Archive confirmation receipts optically Integrate with Financial Accounting (FI), Payroll (HR) and Controlling (CO) Possibly clear credit card

(C) SAP AG HR250 3-25

© SAP AG 1999

Benefits

Benefits

Participation Overview

Enrollment

FSA Claims

Retirement Benefits

Employees can check which benefit plans they are currently enrolled in. They can also set key dates and check their past benefit plans.

Employees can plan their enrollment options. They can select plans and choose options, coverage, contribution amounts, dependents and beneficiaries. They can check if their selections are consistent with company policy and find out if evidence of insurability is necessary.

Mid-year adjustment reasons can be customized in R/3 and are acknowledged within SAP ESS. They allow employees to make changes to enrolled plans outside the open enrollment period. An example for adjustment reason is the birth of a child.

Employees can display their expected retirement benefits and vested entitlements.

In the USA, employees can display their flexible spending accounts and enter claims.

They can also simulate their remuneration statements to see how the chosen plan will affect their gross salary.

(C) SAP AG HR250 3-26

© SAP AG 1999

Various Country-Specific ServicesW-2 Reprint (USA)Net Calculation of Monthly SalaryIR* Forms (Hong Kong, Singapore)

Payment

Paycheck Inquiry

Exercising Employee Options

Display Total Compensation Statement

Employment and Salary Verification

Employees can display their current or previous remuneration statements.

Users can display an overview of the employee options they chose and exercise these options. This triggers a workflow that informs the relevant person in the personnel department that an employee is exercising his options.

Employees can display their total compensation statements.

Employees can request a report verifying their employment and/or salary details. The user may choose between a fax or letter to be sent out. This request is routed to the Human Resources Administrator, who then fulfills the request. This is a US-specific service, but can be adapted to other countries.

There is also a number of country-specific services for Payment. You can find detailed information about it in the Appendix and under http://www.sap.com/ess

(C) SAP AG HR250 3-27

© SAP AG 1999

Navigation Menu

Intranet

CompanyEmployees

End ?

Employment Opportunities

Employment OpportunitiesEnd ?

Personal Data Skills Education Previous Employers

TitleFirst Na meLast NameBirth Na meDate of BirthNationalityStreetZip CodeTownCountryTelephone NumberE- mailAddress

Send

Mr.JohnMeier

30.05.1968German

DD.MM.YYYY

Washington Street 11565385Middletown, N.Y.USA06722-235692

[email protected]

Create Attach ment

Create Attach ment

Valid document formats:

You can send a document with your application.(e.g. CV and copies of certificates)

MS Word ApplicationJoint Photographic Experts Group Format

Select Docu mentC:\MyDocu ments\Application.doc

Apply Back

Browse

Employment OpportunitiesEnd ?

Employment OpportunitiesAlaska USAMid-USANorthwest USASouth USAWest USA

SalesHR Administrator

Admin. HRFinances

Apply

Administrator HR

Jobs

With the Internet/Intranet, employees can review the list of open positions in the company and apply for one by mouse-click without having to enter additional data.

The status of the job application can be checked just as easily. Since the Web application and the Jobs service are linked with the archiving tool SAP ArchiveLink®, applicants can link their application material with their online application and send it as an electronic attachment.

This means that the personnel department need not perform such administrative tasks as scanning in documents and archiving them manually. The departments that are to make the decisions have fast access to the application material.

Applications can use various formats in the standard system: - .doc as document format - .jpg as picture format - If you want to permit applicants to use other formats as well, you must install these formats when

you customize Recruitment.

(C) SAP AG HR250 3-28

© SAP AG 1999

Personal Data

Previous Employers

Various Country-Specific Services

New Hire Data

Personal Information

Address

Bank Information

Emergency Address

Emergency Contact

Family Member/Dependents

Employees can maintain their address information. This includes a number of address options, such as permanent, temporary and home address (Address Infotype (0006)). You can define the address types to be maintained with SAP ESS in Customizing.

Employees can maintain their bank information for the direct deposit of paychecks and expense reimbursements (Bank Details Infotype (0009)).

Employees can maintain a contact address for emergency situations (Address Infotype (0006) subtype Emergency Address (4)).

Employees can maintain the details of an emergency contact person (Family/Related Person Infotype (0021) subtype Emergency Contact (7)).

Employees can maintain information on their dependents and family members to be used in Benefits.

Employees can display and change their personal data (Personal Data Infotype (0002)).

Previous employers lets you create, display, change or delete the data concerning the employer or employers you worked for prior to starting work with your current employer. (Other/Previous Employers Infotype (0023)).

Various country-specific services contain functions for covering tax and other local information.

(C) SAP AG HR250 3-29

New Hire Data guides a new hire step-by-step through a chain of screens from within Personal Information. With 4.6C Support Package 8 this service is replaced with the Life and Work Event "My New Job".

(C) SAP AG HR250 3-30

© SAP AG 1999

My BookingsDisplay BookingsDisplay StatusParticipation HistoryCancel Booking (Workflow is triggered)Appraise Event

Training

Training Center

List of Events

Find Event

Book Event (Workflow is triggered)

Shopping Basket

Two new Employee Self-Services that are very easy-to-use were developed for event management. Training Center My Bookings

The two new services include all the functions of the four old services in Training (only exception: Book). A shopping basket can now be created and saved (for later editing) and bookings can be changed (from one date

to another for the same type of event). The employee can display booking information in the shopping basket and save it for later use. Employees can also book more than one event using the shopping basket.

The services can be used with specially developed approval workflows. The most important event data can be displayed with a hit list. There are also links to executable functions (such as

place in shopping basket), to the detail screen for events (from the name) and possibly to information about the location of the event (Web link).

All existing information can be displayed in the detail screen for the events. Further information can be displayed with a Web link.

Employees can display the booked events with the Book Event service. They can also display the total costs involved with booking this event.

The current data for all the employee's bookings can also be displayed (book, cancel, rebook) Employees can appraise the events they attended directly in the detail screen.

(C) SAP AG HR250 3-31

© SAP AG 1999

My BookingsInfotype Web Link

Infotype Info Event Type

New Infotypes

Web link for event in ESS detail screen

Web link for location from ESS My Bookings

Categorize event groups as Subject Areas

Subject Area

Web Link is a new infotype that can be created for event types, events and locations: You can create a link from these objects to URLs. This permits you to call relevant material that is stored in the Internet (such as information about events) for the particular objects.

You can create any number of links (infotype records). You can also display the links from ESS scenarios. - All the existing links for events are displayed in ESS - The first link created for locations is displayed in ESS

With the Info Event Group event type you can mark the event groups that should be offered in the ESS search under Subject Area.

You can mark the event types that should not be displayed in the Training Center and My Bookings services with the flag for displaying event types in Employee Self-Service that can be set in infotype Info Event Type (1029).

(C) SAP AG HR250 3-32

© SAP AG 1999

Job / Projects / Training RequirementsJob / Projects / Training Requirements

Skills Profile

?? ?

?

Profile Matchup

Requirements Profile

Skills

Employees enter their skills in SAP ESS by selecting the relevant skills and maintaining the associated proficiency level.

Managers can utilize the database to identify employees with the appropriate skills for project placement or job posting.

The skills profile can also be used to determine if an employee needs additional training. Display / Edit Skills Profile

These services permit the employee to display or maintain his or her skills. Each skill can be evaluated.

Display Requirements Profile This service allows the employee to display the requirements for his or her position. Each requirement can be evaluated.

Profile Matchup with Own Position This service permits employees to compare their skills profile with the requirements profile for their position. The service detects missing skills and suggests suitable training. A link takes you to the appropriate events.

(C) SAP AG HR250 3-33

© SAP AG 1999

Employees can display their appraisals.

My Appraisals

My Appraisals

End ?

User

Start

Meyer

01.01.1900 31.12.9999

Appraisals

Appraisal status Appraiser Appraisal Appraisal periodCompleteComplete

Henry MillerMichael Ludwig

Appr. of performanceAppr. of performance

01.01.200001.07.2000

01.07.200031.12.2000

To

Appraisals

This service allows the employee to display the appraisals that were made of his work. Benefits of this service:

Reduces the administrative load on the human resources department and the manager: Encourages participation and responsibility by the individual employee.

(C) SAP AG HR250 3-34

© SAP AG 2002

Availability of SAP ESS Services

............

4.0BInternationalTime Sheet

4.6BInternationalLeave RequestWorking Time

............

4.6CInternationalMy Assets

3.1HInternationalWho's Who

3.1HInternationalInbox

4.6AInternationalCalendarOffice

AvailableCountry-dependent

ESS Service

A detailed list of which SAP ESS services are available can be found in the Appendix: Availability of SAP ESS Services. The table also shows which services are country-specific.

(C) SAP AG HR250 3-35

© SAP AG 2002

Country-Specific ESS Services

Examples:

AddressBank DetailsFamily Member/DependentsEmergency ContactTax Withholding (w-4, US only)Tax Inquiry (Canada)Personal InformationEmployment and Salary Verification

SAP Employee Self-Service uses SAP R/3's global capabilities such as multi-language and currency capabilities and country localization.

SAP ESS supports localization of its different services in two ways:

Country-specific screens

- Example: Different country-specific input fields and plausibility checks are implemented in the Personal Information services (such as Address and Bank Information).

Country-Specific Services

- Example: US tax forms.

- The system ensures that only the employees working for a company within the relevant country see the country-specific services.

(C) SAP AG HR250 3-36

© SAP AG 2002

SAP ESS Support Countries

Examples:

Australia

Canada

Denmark

France

Germany

Great Britain

Ireland

Italy

Japan

Netherlands

Norway

Portugal

Spain

Switzerland

USA

SAP ESS is available in all languages installed in your R/3 runtime environment.

(C) SAP AG HR250 3-37

© SAP AG 2002




Display Inquiries



Meyer Inc.


1

2

WorkSpace (MiniApps, Transactions, Websites)LaunchPad

ChannelBar

Inbox

Show me list of employees

9 absent, not excused 0 at work 11 absent, excused 7 free

Name Work time frameNake Hourly wagesEsch Half-timeKurz Full-time

PersNo. Name Birth date Birthday Age Status

Job list for T70Job name Status Start AppServerARCHIVELINK ended 08.28.2000 16:17CLEAN-UP JOB planned 08.29.2000 09:00ARCHIVE_IDOC_SUB_19960312 planned 08.30.2000 06:00

Open Tasks

Attendance List

Empl. Birthdays

Background jobs

Inbox

Who's Who

Go

Find jobs

Photo

Browse...

Display Picture

Change Picture

Selection time range 18.08.2000 - 27.08.2000

Drag&Relate

WorkSpace (MiniApps, Transactions, Websites)

MiniApps

MiniApps are Internet applications that are intuitive in their use. When the mySAP Workplace is called, they give you a quick overview of and access to important data.

MiniApps are self-contained Web documents that are called with an URL from the Workplace server. You do not need to know where they are stored. The Workplace architecture supports various MiniApp techniques as well as the exchange of data with any number of servers, including the servers of other vendors.

Important information and services are available in the system immediately after logon. A number of useful MiniApps are delivered with Release 2.10. You can also write your own MiniApps and add them to your company's role specifications. The MiniApps are assigned to roles with URLs. For this reason it is very easy to obtain contents such as Internet services and internal company information. You can also directly access data in SAP and external components using MiniApps. With Release 2.0 of the Business Information Warehouse you can also create MiniApps with BW Web Reporting.

The MiniApps that are displayed in the mySAP Workplace depend on your user role. It is also very easy for the end user himself to link MiniApps into his Workplace (if they can be addressed with URLs).

(C) SAP AG HR250 3-38

© SAP AG 2002

MiniApps: Types

Stock market pricesStock market prices

Error reportedError reported

E-mail addressE-mail address Telephone directoryTelephone directory

ReportsReports

AgendaAgendaCalendarCalendarNewsNews

MiniApps

Search enginesSearch engines

MiniApps provide a wide selection of information. In addition to the options listed in the graphic, this includes Preview of transaction contents, such as system monitoring tools, lists of resubmitted documents, lists of defaulting debtors)

Frequently used functions in which only minimal data is entered, so that it is not necessary to call the entire application

Generally available directories Ad-hoc queries Wizards and navigation aids Interfaces to other vendors' applications

If you want to perform complex tasks, you should use Internet Application Components (IACs) instead of MiniApps. These were conceived specially for the casual user and are especially easy to use. Use them to run simple applications such as various SAP ESS services in the Internet.

(C) SAP AG HR250 3-39

© SAP AG 2002



FavoritesDirectory1

Subdirectory 1

Transaction BWeb LinkSubdirectory 2

Transaction CTransaction D

Transaction A

Directory 2

Directory 3

Transaction D

Show me list of employees

9 absent, not excused 0 at work 11 absent, excused 7 free

Name Work time frameNake Hourly wagesEsch Half-timeKurz Full-time

PersNo. Name Birth date Birthday Age Status

Job list for T70Job name Status Start AppServerARCHIVELINK ended 08.28.2000 16:17CLEAN-UP JOB planned 08.29.2000 09:00ARCHIVE_IDOC_SUB_19960312 planned 08.30.2000 06:00

Open Tasks

Attendance List

Empl. Birthdays

Background jobs

Inbox

Who's Who

Go

Find jobs

Photo

Browse...

Display Picture

Change Picture

Selection time range 08.18.2000 - 08.27.2000

MiniApps: Examples

With R/3 Release 4.6C, SAP delivers more than 50 different MiniApps. You can find these MiniApps together with a short description and screen shots under alias miniapps on the SAP Service Marketplace. Some examples are given in the above graphic.

You can use the following MiniApps for the Employee Self-Service role: Who's Who Display Photo Workflow Inbox Microsoft Outlook Inbox Microsoft Outlook Calendar

The mySAP Workplace also supports MiniApps from third party vendors. The only requirement that such applications have to satisfy in order to be used as a MiniApp is that they can be accessed with an URL. Each Website can therefore be used as a MiniApp. Of course you can also write your own MiniApps. This procedure will be described in detail later on.

You can find documentation about development techniques and examples for MiniApps that could be useful when you begin to develop MiniApps on the MiniApps Community Homepage (http://www.sap.com/miniapps).

(C) SAP AG HR250 3-40

© SAP AG 1999



SAP ESS Services 33




(C) SAP AG HR250 3-41

© SAP AG 1999

SAP ESS services that use Workflow:Approval procedure:

Leave requestCATSTravel request and travel planTravel expensesParticipation in an event

Employee New Hire Data and Change of Address notification

Use of workflow applications grows exponentially with the number of SAP ESS users in your company

Integration of the SAP Office Inbox in SAP ESS opens workflow to all employees


The use of SAP ESS in connection with the workflow result in synergy effects since both work with the same business objects. If activities for these objects trigger workflow events in the R/3 System, they will also trigger workflow events in SAP ESS.

The following Workflow templates are delivered with SAP ESS and can be used to set up your workflow-based processes.

Post hire activities (including creation of SAP ESS users)

User delimit

Leave request

Cancel leave request

Travel request and travel plan

W-2 Reprint


Approve booking/cancellation/rebooking of an employee for an event


My Assets

(C) SAP AG HR250 3-42

My Appraisals

Time Sheet


(C) SAP AG HR250 3-43

© SAP AG 2002

Example: Workflow for Leave Request

Employees Manager Administrator

Receivesnotification

Approves request

Checks,corrects, and

approves request

Checks andrejects request

Receives notificationof unsuccessful posting

Rejects request

SubmitsLeave Request ESS

Changes request ESS

ESS

ESS

ESS

ESS

The leave request form submitted by the SAP ESS user triggers the processes in this workflow. The procedure of this workflow is:

The employee triggers the workflow by entering leave request data in an HTML form.

The system selects the name of the line manager who should approve the request. He gets a work item asking him to review the employee's request. If he approves the leave request, the approval is logged in the R/3 System. If there is a problem here, a work item is sent to the Human Resources Administrator, who addresses the issue.

If the manager rejects the request, the employee receives a work item in his Web inbox. Depending on the manager's comment, the employee either withdraws the request or changes it. In the latter case, the workflow begins again.

(C) SAP AG HR250 3-44

© SAP AG 2002

Example: Workflow for Booking Approval

Start ofworkflow

Requestsbooking

Receivesnotificationof approval

Receivesnotificationof rejection

Receivesrequest

Rejectsbooking

Approvesbooking

Takes part in

training

System: Requested booking Booking

Employee EmployeeManager

Three new approval workflows were developed for the new Training Center and My Bookings services. Approve employee participation Cancel employee participation Approve rebooking of an employee

The workflows are started when employees who are not authorized to book, cancel or rebook events execute the corresponding functions in ESS. They are informed that the corresponding process was requested. The manager receives the request for approval in his workflow inbox as a work item. If the manager approves the request, the function is executed automatically. If he rejects the request, the process is deleted and the employee is informed about it in his workflow inbox.

(C) SAP AG HR250 3-45

© SAP AG 1999



SAP ESS Services 33




(C) SAP AG HR250 3-46

© SAP AG 2002

Employees are confronted with a number of changes in their life and work environment:

Begin a new jobBirth/adoption of a childMarriageDivorceChange in employment status

The user needs suitable:Applications

Information

If such life and work events occur, the employee and the employer must react appropriately and trigger the necessary activities.


When Life and Work Events occur, the corresponding changes must be displayed in the system. The employee must make certain decisions, such as claiming certain benefits. To do this he needs information from various areas.

This information is usually not included in the data for the application. To make well-founded decisions, more background information is required (e.g. from the Intranet or Internet).

The user therefore needs an expert system that provides the employee with the application and the necessary information.

(C) SAP AG HR250 3-47

© SAP AG 2002

InformationNew employees receivenecessary information:

Internal to the company

Benefits

Enterprise politics

Forms

External to the company

AuthoritiesApplicationNew employees enter necessary information:

Personal informationBank details

Example: My First Days

An enterprise that hires a new employee needs various information about the employee in order to be able to create the master data in the HR system (such as Address, Bank Information). The new employee can enter this information himself with the Life and Work Event "My New Job".

New hires also have to make a number of decisions, for which they need information from the most various sources. This includes suggestions about what an employee should take into consideration when newly hired, but also information about offers made within the company, about the benefits and the company policy, as well as information from external sources.

The Life and Work Event "My First Days" (Support Package 8) replaces the old service "New Hire Data".

(C) SAP AG HR250 3-48

© SAP AG 1999

Application

Information

Event Menu

Life and Work Events: Framework

The framework for life and work events is the basis used for modeling a series of activities in which suitable applications and information is accessed. Forms (such as HR master data sheet when newly hired) SAP ESS Services (such as Benefits) Background information (such as from Internet or Intranet)

This framework allows a combination of application and knowledge management. Employees are placed in a position to handle complex processes in which well-founded decisions requiring much information must be made.

(C) SAP AG HR250 3-49

© SAP AG 1999

Menu:

(a) Catalogs(b) Services

configurablecountry-specific

Start pageColor representation

Status

Functionality (I)

The menu for the Life and Work Events contains a number of catalogs, such as "Before you Start" and "Personal Data". Each catalog contains various services (e.g. address).

The menu structure can be completely adapted to your requirements. From the menu you can go to ESS Services or to External Services (non-SAP services). The menu is country-specific, i.e. you can define which specific services should appear in the menu in which countries.

Life and Work Events are time-dependent, that is you cannot access them once the time you defined for certain events has expired.

The employees can check which activities and services they already completed. (Status) The services are displayed in different colors reflecting the priority of the event and the number of days remaining.

(C) SAP AG HR250 3-50

© SAP AG 1999

ESS ServicesExternal Services:• URLs• Contents of a Web-based

knowledge base

You can go to ...

Functionality (II)

From the menu for Life and Work Events you can go to: ESS Services External (non-SAP) services

(C) SAP AG HR250 3-51

© SAP AG 1999

Adjustable Frame Size

Split Screen

Functionality (III)

The screen for the Life and Work Events is divided into two parts: the application area and the information area.

If no information is required for an application, the information part is automatically hidden. The frame size of the application and information areas can be defined specifically for the service. To adjust the frame size, place the mouse at the margin of a frame and change the frame size by dragging the mouse.

(C) SAP AG HR250 3-52

© SAP AG 1999

Personalized Contents

Printable Contents

Functionality (IV)

The content templates that are displayed for a Life or Work Event in the information area are not delivered by SAP. You can either create them yourself or get them from a Content Provider.

The content templates can contain various kinds of information: General information to support decision making Application help Form help

The content templates are stored outside of the SAP System, but are controlled dynamically by the data of ERP systems such as SAP R/3. In this way forms can be filled automatically with data from R/3, for example with the address of the employee.

All the contents can be printed. Note: The SAP ESS interface that is used to link a Web-based knowledge base is a generic interface.

(C) SAP AG HR250 3-53

© SAP AG 2002

http://

Transfer R/3 System parameters to fill HTML documents

Data Interface

HTML documentHTML document



ESS Service

ESS Service

ESS Service

Web-Based Knowledgebase R/3 System-SAP ESS

Within the framework for the life and work events, external services can be used to create links to all kinds of Web-based contents that can be provided by a Knowledgebase. External services permit all kinds of contents to be displayed.

The displayed contents can be personalized based on the R/3 data. The contents can come from various different sources.

(C) SAP AG HR250 3-54

© SAP AG 1999

Employees can make well-founded decisions with combined access to:

Company information, such as company benefits and company politicsServices and products outside the direct work environment

The Benefits

Employees enter their own data.Correct and prompt entry

Managers and HR departments need less time for administration and resubmissionOne-step shopping by combining the application and information

(C) SAP AG HR250 3-55

© SAP AG 2002

Requirements

R/3 System Release 4.6C

mySAP Workplace 2.1

Authoring Environment

SAP Knowledge Warehouse

ProAct Technologies Knowledgebase

Other certified Knowledgebase vendors

The SAP ESS interface that is used to link a Web-based Knowledgebase is a generic interface. ProAct Technologies Corp. offers Knowledge Base solutions for company Intranets and SAP partners in the United States.

(C) SAP AG HR250 3-56

© SAP AG 2002

Scope of Delivery

Delivered by...

Pre-configurationPredefined menu structure SAP

SAP ESS services

External services(SAP refers you to the page of examples)

Transfer of suggested R/3 System data to external services

Authoring environment SAP or Knowledgebase Providers

Templates Knowledgebase Provider

SAP provides preconfigured Life and Work Events. These include: Predefined menu structure with links to - ESS services - External (non-SAP) services

SAP refers you to a page of examples. You must create the concrete contents of the templates (=external services) yourself or have them created by a Knowledgebase Provider.

Transfer of suggested R/3 data to external services You can use the SAP Knowledge Warehouse or a Web-based Knowledgebase of another vendor as your authoring environment.

Note: External services are not SAP services

(C) SAP AG HR250 3-57

© SAP AG 2002

Availability

The following Life and Work Events are available:

My First Days R/3 4.6C SP 8

Divorce R/3 4.6C SP 10

Benefits R/3 4.6C SP 10

Birth/Adoption R/3 4.6C SP 15

Marriage R/3 4.6C SP 15

Change Employment Status R/3 4.6C SP 16

Terminate Employment R/3 4.6C SP 16

Life and Work Events are available as of R/3 4.6C SP8. Life and Work Events can be adapted or newly defined to suit your company's needs. Other Life and Work Events will be delivered successively in Support Packages.

(C) SAP AG HR250 3-58

© SAP AG 2002

You are now able to

Navigate in the mySAP Workplace

Describe the SAP ESS services

Describe the relationship between SAP ESS and Workflow

Briefly describe Life and Work Events

SAP ESS Services: Conclusion

(C) SAP AG HR250 3-59

Exercise Data Sheet Key to Icons in Exercises and Solutions

Exercises

Solutions

Course Objectives

Business scenario

Warning or Caution

Data Used in Exercises Type of Data Data in Training System

## Group number

User ID HR250-##/initpass

P250994##/init

Composite role Z_HR250_SAP_WP_EMPLOYEE

Personnel numbers International:

250991## Shavon Whitmer,

250992## Pierre Dunois,

250993## Kai Nishids,

250994## Ruth Cabrera,

250995## Elina Lopez

Organization unit ## - Customer Service within the Caliber A Bicycle Company as part of the HR250 Organizational units

Positions Manager, Service Technician (2)

(C) SAP AG HR250 3-60

URL for the mySAP Workplace http://<webserver>:[port]/scripts/wgate/sapwp/!

(Details are provided by the trainer)

(C) SAP AG HR250 3-61

SAP ESS Services-Exercises

(C) SAP AG HR250 3-62

(C) SAP AG HR250 3-63

Unit: SAP ESS Services

At the conclusion of this exercise, you will be able to:

• Describe the functionality provided with the SAP ESS services

• Navigate through SAP ESS

The Caliber A Bicycle Company wants to implement SAP ESS on its Intranet. Your job is to explain the options available in SAP ESS to the management team so they can decide which services should be implemented in the company.

1-1 Log onto SAP ESS with the following URL: http://<webserver>:[port]/scripts/wgate/sapwp/! Use ESS user P250994## and password init.

1-2 Use the Who’s Who service to answer the following questions:

1-2-1 What is the cost center of Johanna Smith?

_________________________________________________

1-2-2 Who does Alexander Rickes report to?

_________________________________________________

1-2-3 What is the e-mail address of Deborah Schmidt (New York)? _________________________________________________

1-3 You moved recently. Change your permanent address using your choice of data.

1-4 Define an emergency contact.

1-5 Display your remuneration statement for the current month.

1-6 Create a leave request for today. Use the leave type “vacation”.

(C) SAP AG HR250 3-64

(C) SAP AG HR250 3-65

SAP ESS Services-Solutions

(C) SAP AG HR250 3-66

(C) SAP AG HR250 3-67

Unit: SAP ESS Services

1-1 Enter the following URL in your browser: http://<webserver>:[port]/scripts/wgate/sapwp/! Enter P250994## in the Login field.

Enter init in the Password field.

Select the Logon button.

1-2 Use the Who’s Who service to locate the following information:

1-2-1 The cost center of Johanna Smith is 2200. You can find this information using the steps below:

In the LaunchPad, select the Who’s Who service in the Office menu.

Enter Smith in the Last name field.

Select Find.

In the Results field, click on Johanna Smith to display her detailed information and obtain her cost center.

1-2-2 Alexander Rickes reports to Anja Miller.

You can find this information using the steps below:


Enter Rickes in the Last name field.

Select Find.

In the Results field, click on Alexander Rickes to display his detailed information.

Select Organizational Chart to obtain his superior’s name.

(C) SAP AG HR250 3-68

1-2-3 You can reach Deborah Schmidt at the e-mail address [email protected].

You can find this information using the steps below:


Enter Schmidt in the Last name field.

Select Find.

In the Results field, click on Deborah Schmidt to display the detailed information including the e-mail address.

1-3 Change your permanent address.

In the LaunchPad, select the Address service in the Personal Information menu.

Make sure that Permanent address is selected.

Select the address from the list.

Select Change.

Change the relevant information.

Select Save.

1-4 Define an emergency address.

In the LaunchPad, select the Emergency Address service in the Personal Information menu.

Select OK to acknowledge the message “No valid data available for area selected”.

Select New.

Enter the relevant information.

Select Save.

The new entry is displayed in the Emergency Address list.

1-5 Create a leave request for today. Use the leave type “vacation”. In the LaunchPad, select the Leave Request service in the Working Time menu. Enter the relevant information. Choose Send.


© SAP AG 1999

Architecture of the mySAP Workplace

mySAP Workplace Frontend

mySAP Workplace Middleware

mySAP Workplace Backend Systems

Roles in the mySAP Workplace

Single and Composite Roles


Creation and Maintenance of Roles

Contents



© SAP AG 1999


Understand the Workplace architecture

Explain the functions of the elements involved

Explain the role definition

Describe the Employee Self-Service Role

Create and maintain single roles

Create and maintain composite roles

Swap roles between component systems and the Workplace Server

mySAP Workplace: Unit Objectives


© SAP AG 1999

Course Overview

SAP ESS Services

User Management


Summary

Enhancing SAP ESS

Customizing SAP ESS


mySAP Workplace: Architecture & Roles



© SAP AG 2002

SAP Employee Self-Service assumes that you have a suitable system infrastructure.

To be able to administer roles and users in the different systems you have to understand the relationship between the Workplace and the component systems.

mySAP Workplace: Business Scenario


© SAP AG 1999



11

22



© SAP AG 1999

Workplace Architecture: Overview

Web Browser and Web Server

SAP Internet Transaction Server

Contents

Architecture


© SAP AG 1999




Architecture: Objectives


© SAP AG 1999

DesktopDesktop BackendBackendSystemsSystems

Workplace MiddlewareWorkplace Middleware

R/3 APO

BW KW

BBP CRM

Examples:Examples:

Web Server ITS

Web Browser

Web server ITS WP

Web server

Web server

ITS 1

ITS n

WorkplaceServer

Comp.System 1

Comp.System n

Workplace Architecture

The Workplace architecture has three layers. To access the Workplace the user only needs a Web browser on his desktop. The Web browser uses a Web server belonging to the Workplace middleware for communications. Another important element is the SAP Internet Transaction Server (ITS), which connects the Web server with the backend systems.

A number of backend systems can be linked with the Workplace. One of the most important backend systems is the Workplace Server, which is used to handle the role specifications and central user administration if implemented. The other systems (such as R/3, APO, BW, KW, BBP, CRM) are called component systems.

Recommendation: When using SAP ESS you should install a physical ITS for the Workplace Server and for each component system (such as HR, BBP).


© SAP AG 1999

Web Server(HTTP Server)

Web Browser(HTTP Client)

<HTML><BODY>...</BODY></HTML>

• Client/Server Architecture• HTTP based on TCP/IP

HTTP Query

HTTP Reply

Web Browser Web Server PortalBuilder WP Server

Web Server ITS Component

Drag&Relate SAP DCOM

File Edit View Favorites

Back Forwards Cancel

Address http://www.mysap.com/

Web Browser and Web Server

The Internet was originally the data network of the US military. Its use was then extended to research institutes and universities, and later to the private and commercial sector.

The Internet is a "Network of networks". Every device connected to the Internet is assigned an address that is unique worldwide and that conforms to the "Internet Protocol" (IP). The "Transmission Control Protocol" (TCP) controls the exchange of data packages between the devices.

A number of services are provided with the Internet, such as e-mail, FTP and newsgroups. The World Wide Web (WWW) is such a service. Its immediate success is due to such features as a user-friendly interface and to its hypertext format.

The "Hypertext Transport Protocol" (HTTP) is used as communications protocol for the WWW. It defines methods for data objects. HTTP is oriented to the client/server model: A Web browser (the HTTP client) sends requests to a Web server (the HTTP server) and it in turn replies. The HTTP query contains the address of the required object, called an URL (Uniform Resource Locator). The corresponding syntax is <protocol>://<Server (Name or IP)>/<Path (optional)>", i.e. "http://www.mysap.com".

The HTTP reply contains the required data object. The Web browser displays the object in the correct format. If the Web browser does not recognize the format, it suggests that the user download the object to a local drive as a file.

The HTML (Hypertext Markup Language) format is of special importance in the WWW. HTML files consist of ASCII characters and describe the page layout using special instructions. Embedded objects such as graphics as well as links to other data objects are also taken into consideration.

(C) SAP AG HR250 4-10

© SAP AG 1999

Internet Transaction Server (ITS)

WebBrowser

WebServer

Comp.SystemWGateWGate AGateAGateHTTPHTTP CGICGI TCP/IPTCP/IP

DIAGDIAG

RFCRFC

• Link: Web Server / Component System• Log onto the Component System• Data Receipt, Conversion to HTML• Status Management




User Query Input

CSSFiles

ServiceFiles

HTMLTemplates

OutputHTML Page

ITS: Overview

The Web Server is linked with the component systems by the SAP Internet Transaction Server (ITS). The ITS is needed for the following tasks: Data exchange (for example by converting protocols) Logging onto the component system Transferring data to component systems, converting the output into HTML Status management

The ITS consists of two components: WGate is the interface to the Web server. WGate and the Web server must run on the same hardware. In addition to the CGI (Common Gateway Interface), SAP supports the external interfaces ISAPI (Microsoft) and SNAPI (Netscape). If you use the Microsoft IIS Web server, the WGate is stored as a DLL file in directory scripts.

Exchange with the component system uses the AGate. It can run either on the same hardware as the WGate (single host) or on a separate host (dual host). A number of files stored on the AGate configure the ITS. This includes: Service files: component system, logon data (client, user, password) HTMLBusiness Templates: HTML with additional instructions, placeholder for screen fields CSS files: Description of the optical design of the generated HTML pages

(C) SAP AG HR250 4-11

© SAP AG 2002

Component SystemAGateAGate (ITS)(ITS)

Not Based on SAP Dialog

Based on SAP Dialog

Where is the transactionorder defined?

Development Tools:SAP@Web Studio and Web Application Builder

DisplayDisplay

Display

Dialog Transactionor Function Module

Status Status

Status

Flow Logic &Representation

<HTML><BODY>

Result:F1 value

Representation

Business Object

BAPIBAPI

BAPI

ITS: Programming Models (I)

ITS supports two programming models. They differ in the location where the individual transaction flows are defined.

Flows for models that are based on SAP dialog are defined in the component system (normally in the dialog transaction). The ITS takes care of the visual representation. There is at least one template for each screen of the transaction in the AGate. HTML standard instructions are linked with HTMLBusiness instructions in these files. HTMLBusiness gives you access to all the screen fields and their features. HTMLBusiness also offers a wide spectrum of instructions for input fields, loops, conditions, arithmetic operations, etc.

In models that are not based on SAP dialog, the ITS controls the order of the transactions as well as the visual display. As in the above case, the display is defined by HTMLBusiness templates. The order is described in a separate layer called the ITS flow logic. The main features of this layer are the different statuses and the event-dependent transitions between these statuses. The specification uses flow logic files that are based on XML syntax.

Two tools are provided for developers for creating Internet applications. SAP@Web Studio is an independent program. The functionality of the SAP@Web Studio includes various wizards that support developers.

With Release 4.6C the SAP development environment (Transaction SE80) contains the Web Application Builder, which can also be used to create Internet applications.

(C) SAP AG HR250 4-12

© SAP AG 2002


Greater learning effort, more features

IACsIACs

ITSITSFlow LogicFlow Logic

HTML Templates

HTML Functions

HTML Templates

Flow Files

HTML Functions

SAP GUISAP GUIfor HTMLfor HTML

HTML Functions

R/3 System

HRCRMBBP

...

Web Browser

Flow Logic in R/3 SystemFlow Logic in R/3 System Flow Logic Flow Logic in the ITS in the ITS

ITS: Programming Models (II)

SAP ESS is based on Internet Application Components (IACs). It has a three-step procedure: SAP GUI for HTML - a one-to-one mapping of the R/3 screens. The SAP GUI for HTML provides a dynamic emulation of the R/3 dialogs in a Web browser. This mapping is implemented by HTMLBusiness functions (one for each screen element), which either reside in the ITS kernel or are called from those functions.

Internet Application Components (IAC) SAP ITS Flow Logic - BAPIs and Function Modules

A Web-enabled transaction has the following characteristics: It uses only "simple" screens that can be easily converted into HTML. It can be synchronized by the ITS. It uses a special technique to provide users with input help in HTML forms. It permits users to log onto the Internet while the transaction is being processed.

The past SAP ESS services are based on a SAP dialog and therefore either are executed with the SAP GUI for HTML or work with HTML templates (IACs). The Life and Work Events as well as the MiniApps, however, are not based on a SAP dialog (ITS flow logic).

(C) SAP AG HR250 4-13

© SAP AG 1999




Architecture: Summary

(C) SAP AG HR250 4-14

© SAP AG 1999



11

22

Workplace and Roles

(C) SAP AG HR250 4-15

© SAP AG 1999

Role Definition: Overview

Single and Composite Roles


Creation and Maintenance of Roles

Contents

Roles

(C) SAP AG HR250 4-16

© SAP AG 1999






Roles: Topic Objectives

(C) SAP AG HR250 4-17

© SAP AG 1999

Roles

From the business point of view, a role is the description of an activity in a company. Using the mySAP Workplace, employees of a company are assigned to roles in business scenarios. The roles and scenarios are ways of looking at processes in modern enterprises.

Technically speaking, a role is a collection of transactions, Internet links (URLs), reports, executable files, MiniApps, Knowledge Warehouse links and links to external systems. The role includes all the authorizations (not shown in the graphic) that are needed to perform the role-specific tasks.

The role defines the transactions, information and services that may be accessed at the mySAP Workplace. It also defines the appearance of the interface for the particular user (LaunchPad and MiniApps).

Roles can be maintained both on the Workplace Server and in the component systems. There are the following types of roles: Single roles: are created and maintained in the component systems and then transferred to the Workplace Server. If the component systems have Release 4.6A or higher, single roles can be initially created on the Workplace Server and then distributed to the component systems.

Composite roles: These can only be created and maintained on the Workplace Server. They define the appearance of the LaunchPad.

(C) SAP AG HR250 4-18

© SAP AG 1999

KW

LO

FI

SAP_WP_EMPLOYEESAP_WP_EMPLOYEE

SAP_ESSUSER

SAP_FI_EMPLOYEE

SAP_LO_EMPLOYEESAP_FI_TV_TRAVELLER

SAP_BC_ENDUSER

SAP_WPS_EMPLOYEESAP_WPS_EMPLOYEE

SAP_WPS_USERSAP_WPS_USER

SAP_KM_KW_ALL_AREAS_DISP_EMPL

SAP_HR_EMPLOYEE_XX

WorkplaceWorkplace ServerServer HR

WorkplaceWorkplace ServerServerComposite role

Single Roles

BBP

SAP_EC_BBP_EMPLOYEE

SAP_BC_EMPLOYEE

The Employee Self-Service Composite Role

The Employee Self-Service composite role replaces the navigation menu used in Releases 4.5 and 4.6B, which now can be found in the role in the mySAP Workplace LaunchPad.

The composite role Employee Self-Service (SAP_WP_EMPLOYEE) is delivered by SAP. It resides on the mySAP Workplace system and contains all the international and country-specific single roles (transactions, authorizations) provided for Employee Self-Service.

The single roles always reside in the relevant component systems with the exception of the single roles SAP_WPS_EMPLOYEE and SAP_WPS_USER, which contain the MiniApps and basic authorizations for the Workplace system and therefore reside in the Workplace system. The single role SAP_BC_ENDUSER contains the basic authorizations for the component systems and therefore must exist in all the component systems (HR, LO, FI...).

Although you can use any role to install SAP ESS authorizations, SAP strongly recommends that you use a copy of SAP_WP_EMPLOYEE. Copy the composite role to your customer namespace (Z* or 9*). Then, if necessary, you can adapt it to include transactions that are relevant to your company.

You can find a detailed description of the single roles in the SAP Employee Self-Service Release 4.6C Implementation Guide

(C) SAP AG HR250 4-19

© SAP AG 1999

Component SystemComponent System WorkplaceWorkplace ServerServer

GenerateGenerateauthorizationsauthorizations

CreateCreatecomposite rolecomposite role

DistributeDistributesingle rolessingle roles

CreateCreatesingle rolessingle roles

CopyCopysingle rolessingle roles

ChangeChangesingle rolessingle roles

ChangedChangedsingle rolessingle roles

CreateCreatesingle rolessingle roles

2

1

3

4

5

Role Definition: Overview

The graphic shows the recommended procedure for creating your own composite role for SAP ESS: Component system(s): Create single roles by copying the delivered single roles to the customer

namespace (Z* or 9*). If necessary, adapt it to include transactions that are relevant to your company. Component system(s): Generate authorizations for each single role. Workplace Server: Read the single roles from the component systems. Workplace Server: Create Workplace-specific single roles by copying the delivered single roles to the

customer namespace (Z* or 9*). Workplace Server: Create a composite role in the customer namespace. Add the single roles imported

from the component systems and the Workplace-specific single roles. If the component system has Release 4.6A or higher, you can maintain the single roles on the

Workplace Server after the import and then distribute them to the component systems.

(C) SAP AG HR250 4-20

© SAP AG 2002

Component System

TransaktionTA1

Role A

Z_SAP_LO_EMPLOYEE

TransaktionTA1

???Transaktion

TA2

TransactionTA1 Web

Link

ReportReportxyzxyz

ReportReportxyzxyz

ReportReportxyzxyz

ReportReportxyzxyz

ReportReportxyzxyz

WebLinkTransaction

TA1WebLinkTransaction

TA3

TransactionTA1

TransactionTA1

Weblink

MiniApp 1

Z_SAP_ESSUSER

Role B

Creation of Single Roles

Single roles are usually created in the component system, transferred to the Workplace Server and possibly maintained centrally on the Workplace Server. 'Creation' here means defining the activity of the role.

The authorization contents of the role are usually maintained in the component systems due to different Customizing.

Completely new roles can also be created. However, we recommend that you use the roles provided by SAP as a template, copy them to new roles and modify them as required. SAP delivers a wide selection of roles for a number of business activities.

(C) SAP AG HR250 4-21

© SAP AG 2002

Menu Design

TransactionTA3

Define functions

Reportzab

Reportxyz

WebLink

WebLink

Mini-App

Modify menu tree

Transaction TA2

TransactionTA1

Component System

Reportxxx

Role Z_HR250_SAP_ESSUSER Role Documentation Description Employee Self-Service (Copy)

Activity group menu

Description Menu Authorizations MiniApps Users

Transaction Report Other All

URL - www.mysap.comOffice

InboxCalendarWho's WhoChange Own DataInternal Service RequestMy Assets...

Business TripsWorking Time

Time SheetLeave Request

Information System

Copy Menus

From the SAP menuFrom other roleFrom area menuImport from file

Translate nodeDisplay documentationSearch documentation

Target system (trusting)

Additional Activities

Drag&Drop T70CLNT400Distribution OK

Distribute

You can go to role maintenance with Transaction PFCG or by choosing Tools ? Administration ? User Maintenance ? Roles. Role names should contain the names of the appropriate component systems. Enter the name of the role and click on Create or Change. Choose the Menu tab.

Change functions: The menu tree can be adapted to suit your individual roles. Transactions can be inserted in or deleted from the tree structure. Reports can be integrated by choosing Report. In this case the role maintenance creates transaction codes that are used to call these reports.

By choosing Other you can include Internet addresses and Links to files (such as tables or text files). When you integrate files, you have to specify the corresponding storage path instead of the URL. You can also specify BW WebReports, external mail system links and Knowledge Warehouse links.

MiniApps can also be linked. Change menus: Directories and subdirectories can be created, moved, deleted and renamed as required. You can use the Drag&Drop function for role maintenance.

When you change a single role within the role maintenance on the Workplace Server, the menu design is distributed to the corresponding component systems. The component system is addressed under its logical system name and is entered in the Target system field. Then choose Distribute. The modified menu definition is now also in the component system and its authorizations are maintained there.

(C) SAP AG HR250 4-22

© SAP AG 2002

Creation of Authorization Profiles

Role Z_HR250_SAP_ESSUSER Description Employee Self-Service (Copy)

Created Last change

Information about authorization profile

Maintain authorization data and generate profiles

User ErhardDate 16.10.2000Time 13:22:12

Profile nameProfile textStatus Profile adjustment required

Change authorization data

Expert mode for profile generation

User DERNDate 16.01.2000Time 13:22:12

Description Menu Authorizations Users

Z_HR250_SAP_ESSUSER Employee Self-Service (Copy)

Maintenance: 0 non-maintained organization levels 7 open fields, Status: changed

Standard old Cross-application authorization objectsmaintained old Human resources administrationmaintained new Basis: Administration

Standard old Basis: Development environmentmaintained new Basis: Central functionsStandard old Personnel development

ActivityPhysical file nameABAP program name

Standard new Authorization to access file


maintained old SAPscript: Standard text

Authorization

profile

Generate

Role Z_HR250_SAP_ESSUSER Description Employee Self-Service (Copy)

Created Last change

Information about authorization profile

Maintain authorization data and generate profiles

User ErhardDate 16.10.2000Time 13:22:12

Profile nameProfile textStatus Profile adjustment required

Change authorization data

Expert mode for profile generation

User DERNDate 16.01.2000Time 13:22:12

Description Menu Authorizations Users

Z_HR250_SAP_ESSUSER Employee Self-Service (Copy)

Maintenance: 0 non-maintained organization levels 7 open fields, Status: changed

Standard old Cross-application authorization objectsmaintained old Human resources administrationmaintained new Basis: Administration

Standard old Basis: Development environmentmaintained new Basis: Central functionsStandard old Personnel development

ActivityPhysical file nameABAP program name



maintained old SAPscript: Standard text

Authorization

profile

Generate

Component System

The role authorizations are normally maintained in the component systems. Role maintenance automatically creates the authorizations belonging to the transactions specified in the menu tree. You nevertheless have to manually check and possibly adapt all authorizations to your actual requirements and constraints. The system administrator is responsible for this task together with the relevant department. You can considerably simplify the authorization maintenance by using organization levels.

Choose tab page Authorizations and click on Change authorization data. Check the scope and contents of the authorizations.

The green traffic light in the authorization overview indicates that the role maintenance was able to generate an authorization automatically. A yellow traffic light indicates that you have to maintain it manually. The role maintenance does not propose a value for the authorization.

Once you have maintained all your authorizations, you can create the authorization profile by clicking on Generate. Important: The second letter of the profile name may not be an underscore (character "_") (see Note 16466). This name cannot be changed once it has been created.

If you use the standard authorization profiles delivered with SAP ESS based on the authorization object P_PERNR, you must enable the HR authorization checks. To enable the HR authorization checks, you must activate the ESS-specific P_PERNR authorization object in table T77S0 by setting the value to 1 for Group AUTSW and Semantice abbreviation PERNR. This setting controls the authorization check for the personnel numbers assigned to users in the Communication infotype (0105).

(C) SAP AG HR250 4-23

© SAP AG 2002

Workplace Server

Transfer of the Roles to the Workplace Server

Singlerole 6

Singlerole 3

Singlerole 5

Singlerole 2Single

role 1

Singlerole 3Single

role 4

Component Systems Workplace Server

For a role-specific LaunchPad implementation, you must reproduce the roles on the Workplace Server for later assignment to the users. The menu definitions of the single roles therefore have to reside on the Workplace Server. You can do this by copying them from the component systems to the Workplace Server.

One way to do this is by using a plug-in that is delivered together with the Workplace and installed in the component system. Menu definitions can then be copied to the component system from the Workplace Server using an RFC link. On the Workplace Server start role maintenance and choose Role à Read from other system with RFC.

Role definitions can also be downloaded as a file. One component of the plug-in is Transaction WPST, which combines the roles to form a file. You can load this transaction in the role maintenance by choosing Role à Upload on the Workplace Server. There are also special reports for uploading and downloading the roles (see Note 181368). User assignments to roles are not copied.

(C) SAP AG HR250 4-24

© SAP AG 2002

Creation of a Composite Role

Target system

Z_SAP_ESSUSER

Menu forZ_SAP_ESSUSER

Menu forZ_SAP_LO_EMPLOYEE

Z_SAP_LO_EMPLOYEE

Menu forZ_SAP_ESSUSER

Menu forZ_SAP_LO_EMPLOYEE

Z_SAP_WP_EMPLOYEEZ_SAP_WP_EMPLOYEE

Target system

Changes to the entire

Workplace menu

Single Role 1

T70CLN

Single Role 2

Composite Role

T71CLNT

Workplace Server

When a user starts a transaction in the Workplace from the LaunchPad, this transaction is executed in the corresponding component system. The single roles must therefore refer to the relevant component system on the Workplace Server. Single roles that were created on the Workplace Server in the central role maintenance and distributed to the component systems are already assigned to "their" component systems. Single roles that were copied to the Workplace Server with RFC are also assigned to "their" component systems. Manual assignment is only required for single roles that were copied by uploading or downloading. On the Workplace Server choose tab page Menu in the role maintenance transaction. Enter either the logical system name of the component system or an RFC variable in field Target system.

Composite roles bundle single roles. Composite roles can contain single roles that access different systems of the Workplace architecture. You cannot combine composite roles to form higher-level composite roles.

Composite roles define the appearance of the LaunchPad in the Workplace. The menu tree for a composite role normally consists of the role menus it contains. Tree components therefore can occur more than once. Menu entries for the single roles can appear in any order and may be deleted. If the single roles are changed at a later time, the dependent composite roles can be redefined.

Composite roles are only maintained on the Workplace Server and do not contain authorizations.

(C) SAP AG HR250 4-25

© SAP AG 2002

Workplace Server

Assignment of Composite Roles to Users


Z_SAP_ESSUSER

Z_SAP_FI_EMPLOYEE

Z_SAP_LO_EMPLOYEE

Z_SAP_FI_TV_TRAVELLER

Z_SAP_WPS_EMPLOYEEZ_SAP_WPS_USER

Z_SAP_HR_EMPLOYEE_XXZ_SAP_BC_EMPLOYEE

If the composite roles have the required menu structure, they are assigned to users on the Workplace Server.

If the central user administration is not used, the corresponding single roles must also be assigned tot he users in the relevant component systems.

If central user administration is used, the single role assignment is cancelled by the assignment of the composite roles on the Workplace Server. The system checks which single roles are contained in a composite role and which component systems these single roles are assigned to. The single roles are then automatically assigned to the users in the component systems. A user master check is carried out immediately.

The user can log onto the Workplace when the composite roles have been assigned to the user identifiers on the Workplace Server. The user can call all the transactions offered on the LaunchPad since they correspond to the single roles contained in the composite roles. The transactions are executed in the relevant component system.

(C) SAP AG HR250 4-26

© SAP AG 1999

AddressAddress

Bank detailsBank details

W2 ReprintW2 Reprint

Tax Withholding W4Tax Withholding W4

Capital FormationCapital Formation

Net Calculation of Monthly SalaryNet Calculation of Monthly Salary

MOLGA

VAGRATTS

SAP_HR_EMPLOYEE_DESAP_HR_EMPLOYEE_DESAP_HR_EMPLOYEE_USSAP_HR_EMPLOYEE_US

UCN = US UCN = DE

VAGRATTS


SAP Employee Self-Service uses SAP R/3's global capabilities such as multi-language and currency capabilities and country localization.

SAP ESS supports localization of its different services in two ways:

Country-specific screens

- Example: Different country-specific input fields and plausibility checks are implemented in the Personal Information services (such as Address and Bank Information).

- The country-specific screen views are controlled within the individual services by the employee's country assignment (MOLGA).


- Example: US tax forms and capital formation in Germany

- The system ensures that only the employees working for a company within the relevant country see the country-specific services.

- The availability of country-specific services is controlled by country attributes. These can be assigned to the single roles in table VAGRATTS (table maintenance with transaction SM30). This table also defines the country-specific single roles for which dynamic filtering is required.

(C) SAP AG HR250 4-27

- The country-specific services displayed for a particular user are defined by parameter UCN in the user master record used for dynamic filtering during the mySAP Workplace logon.

(C) SAP AG HR250 4-28

© SAP AG 2002






Roles: Unit Summary

(C) SAP AG HR250 4-29

mySAP Workplace Architektur & Rollen Exercises


At the end of this exercise you will be able to do the following within central role maintenance:

• Create single roles in the component system

• Copy single roles to the Workplace Server

• Centrally maintain single roles on the Workplace Server

• Distribute changed single roles to component systems

• Create and maintain composite roles

1 Create customer-specific single roles based on the standard roles delivered with SAP ESS.

R/3 component system (SAP GUI for Windows, User HR250-##):

1-1 Create the single role HR250_01_R3_## with the role maintenance transaction. Use single role SAP_ESSUSER as a template.

Create the single role HR250_02_R3_## with the role maintenance transaction. Use single role SAP_FI_Employee as a template.

Create the single role HR250_03_R3_## with the role maintenance transaction. Use single role SAP_LO_Employee as a template.

1-2 Using the role maintenance transaction, create the authorization profile for roles HR250_01_R3_## to HR250_03_R3_##.

Assign overall authorizations for all organization levels (character "*"). Assign overall authorization (“*”) to all the authorizations marked in yellow. Generate the authorization profile.

(C) SAP AG HR250 4-30

2 Read in single roles on the Workplace Server

Workplace Server (SAP GUI for Windows, User HR250-##):

2-1 Read in the single roles created in the component system on the Workplace Server. Your trainer will tell you which RFC link to use.

3 Change single roles on the Workplace Server


3-1 Change single role HR250_01_R3_##.

Create a new folder called My Links. Add the URL http://www.sap.com to this folder with the name Internet. Save your entries.

3-2 Distribute the changed single role from the Workplace Server to the R/3 component system.

Check the entry in the Target system field on tab page Menu for single role HR250_01_R3_##. Enter the logical system name of the component system here (your trainer will tell you this name).

Choose Distribute.

4 Create composite role on the Workplace Server


Use role maintenance to create the composite role HR250_COMP_WP_##.

4-1 Combine single roles HR250_01_R3_## to HR250_03_R3_## to create composite role HR250_COMP_WP_##.

4-2 Create the menu tree of the composite role by reading the menus of the bundled single roles. Note: Choose tab page Menu and click on Read menu.

(C) SAP AG HR250 4-31

4-3 Update the user master record for your Workplace user. Assign your user ID HR250-## composite role HR250_COMP_WP_## on the Workplace Server. Make the correct entries in tab pages Systems and Activity groups. Distribute the data to the R/3 component systems by choosing Save. Note: Do not remove single roles SAP_BC_Employee, SAP_BC_Enduser, SAP_WPS_Employee, SAP_WPS_Enduser from the user master record.

5 Web Browser: Log onto the Workplace with user ID HR250-## and check the appearance of the LaunchPad. Try out some of the transactions that are offered. What do you find?

(C) SAP AG HR250 4-32

mySAP Workplace Architektur & Rollen Solutions

Unit: mySAP Workplace Architecture & Roles

1 Create customer-specific single roles based on the standard roles delivered with SAP ESS.

R/3 component system (SAP GUI for Windows, User HR250-##):

1-1 Create the single role HR250_01_R3_## with the role maintenance transaction. Use single role SAP_ESSUSER as a template.

Create the single role HR250_02_R3_## with the role maintenance transaction. Use single role SAP_FI_Employee as a template.

Create the single role HR250_03_R3_## with the role maintenance transaction. Use single role SAP_LO_Employee as a template.

In the SAP Easy Access menu choose: Tools → Administration → User maintenance →Roles (or go directly to Transaction PFCG).

Select the specified single role and choose Copy. Give the copies the names specified above. Save your entries.

1-2 Using the role maintenance transaction, create the authorization profile for roles HR250_01_R3_## to HR250_03_R3_##.

Assign overall authorizations for all organization levels (character "*"). Assign overall authorization (“*”) to all the authorizations marked in yellow. Generate the authorization profile.


(C) SAP AG HR250 4-33

Choose Authorization. Choose Change authorization data.

Assign overall authorizations for all the fields that were not maintained: Click on the yellow traffic light and then the green checkmark.

Choose Generate. You have created the authorization profile for your role.

2 Read in single roles on the Workplace Server


2-1 Read in the single roles created in the component system on the Workplace Server. Your trainer will tell you which RFC link to use.


In the menu bar choose: Role → Read from other system with RFC In the next dialog box choose: Select an RFC destination Choose the RFC destination specified by your trainer. Confirm your entries with Enter. The single roles are read in from the component system.

3 Change single roles on the Workplace Server


3-1 Change single role HR250_01_R3_##.

Create a new folder called My Links. Add the URL http://www.sap.com to this folder with the name Internet. Save your entries.


On the Menu tab choose Create folder. Enter My Links as name. Choose Enter.

(C) SAP AG HR250 4-34

3-2 Now choose Other and in the next dialog box select URL. Confirm your entries with Enter. In the next window enter Internet in field Text and http://www.sap.com in field Web address. Choose Enter.

Save your entries.

3-3 Distribute the changed single role from the Workplace Server to the R/3 component system.

Check the entry in the Target system field on tab page Menu for single role HR250_01_R3_##. Enter the logical system name of the component system here (your trainer will tell you this name).

Choose Distribute.

4 Create composite role on the Workplace Server


Use role maintenance to create the composite role HR250_COMP_WP_##.

4-1 Combine single roles HR250_01_R3_## to HR250_03_R3_## to create composite role HR250_COMP_WP_##.


To create composite role HR250_COMP_WP_## choose Create composite role Select the Roles tab page. Enter the single roles for HR250_01_R3_## to HR250_03_R3_##. The system defines field Target system to correspond to your entries in the single role. Save your entries.

(C) SAP AG HR250 4-35

4-2 Create the menu tree of the composite role by reading the menus of the bundled single roles.

Choose tab page Menu and click on Read menu. You can now redesign the entire menu. You can change the position of the entries or delete the entries, but you cannot add new entries.

4-3 Update the user master record for your Workplace user. Assign your user ID HR250-## composite role HR250_COMP_WP_## on the Workplace Server. Make the correct entries in tab pages Systems and Activity groups. Distribute the data to the R/3 component systems by choosing Save. Note: Do not remove single roles SAP_BC_Employee, SAP_BC_Enduser, SAP_WPS_Employee, SAP_WPS_Enduser from the user master record.

In the SAP Easy Access menu choose: Tools → Administration → User maintenance →Users (or go directly to Transaction SU01).

You want to assign user HR250-## the composite role HR250_COMP_WP_##. In tab page Roles enter role HR250_COMP_WP_##. Choose Save and distribute the data to the R/3 component system.

5 Web Browser: Log onto the Workplace with user ID HR250-## and check the appearance of the LaunchPad. Try out some of the transactions that are offered. What do you find?

Not all of the services are available because the user is not yet assigned to an employee.


© SAP AG 2002

Contents

Authorizations in the R/3 System

Central User Administration

Migration of Existing Users

Maintenance of SAP ESS Users

User Management


© SAP AG 2002

At the conclusion of this unit, you will be able to

Outline the R/3 System authorization concept

Describe the concept of Central User Administration

Copy existing users to the mySAP Workplace Server

Create and maintain SAP ESS users

Authorize users for SAP ESS

User Management: Unit Objectives


© SAP AG 1999

Course Overview

SAP ESS Services



Summary

Enhancing SAP ESS

Customizing SAP ESS


User Management



© SAP AG 2002

Now that you have copied the SAP ESS roles to the customer namespace and adapted them, you want to provide these roles and the services they contain for the employees of Caliber A Bicycle.

To work as efficiently as possible, you should first familiarize yourself with the features of user management.

You want to implement ESS users for the employees in the component systems and provide both the newly created as well as the existing users on the Workplace Server.

User Management: Business Scenario


© SAP AG 1999

Central User Administration (CUA)

SAP ESS User Maintenance

11

22

User Management


© SAP AG 1999

Principles of Central User Administration (CUA)

CUA Configuration

ALE Distribution Model

Migration of Existing Users

Contents



© SAP AG 1999

Explain how the CUA works

Describe the ALE configuration

Explain how to create users on the Workplace Server and how to distribute them to the component systems

Describe how to copy existing users to the Workplace Server


Central User Administration: Unit Objectives


© SAP AG 1999

Backend Systems

WorkplaceServer

Comp.System 1

Comp.System 2

Comp.System n

...User

maint.

User maint.

User maint.

User maint.

User Management in the Backend Systems

The maintenance costs for keeping user master records up to date in complex system infrastructures with multiple systems and clients is very high. New employees are hired, leave the company or change their jobs internally. Usually employees have to access various systems and clients in order to perform their tasks and therefore they need multiple users.

Users are client-specific, and therefore need to be maintained separately for each client in the system infrastructure. A separate user master record must be created manually in each client and each system to which an employee has access.

The user master records can be maintained in a separate client. The existing user master records can be copied to a new client. The corresponding single roles and composite roles are also copied when the profiles are copied. You cannot select individual users when you use the copy functions - it is only possible to copy all the users. Furthermore, there is no mechanism for synchronizing the user master records for maintenance purposes between the clients.

The administrative costs for maintaining users in the component systems and on the Workplace Server can be reduced by using the Central User Administration (CUA).

The Central User Administration is recommended when using the Workplace and thus also when using SAP ESS, but is not mandatory.


© SAP AG 1999

ALE

Backend Systems

WorkplaceServer

Comp.System n

Comp.System 2

Comp.System 1

User maint.

Datadistribution

...

Central User Administration: Idea

All the users for the component systems on the Workplace Server must be declared when you use the Workplace. It is therefore ideal for central administration of all the users of the mySAP.com environment. The purpose of the CUA is to use a central client in its own system. It can be used to maintain the user master records of all other clients in the system infrastructure. You can specify which single or composite roles are assigned to which users in the particular clients. This considerably reduces the cost for maintaining user management.

You can define the client in which each user may log on. CUA therefore does not mean that all users can automatically be used in all clients of the system infrastructure.

You can also define what user data should be maintained centrally and what data locally. Sometimes it is advisable to have the user or an administrator maintain the data locally.

Authorization data is exchanged using ALE. ALE means "Application Link Enabling". This is a technique for implementing and running distributed SAP applications. ALE enables the process-controlled exchange of business news between loosely coupled SAP systems. Asynchronous communications ensure that the application can run smoothly and without disturbance.

The name "Workplace Server" below refers to those clients of the Workplace Server system for which a user is maintained. The term "component system" refers to clients that are linked to the CUA. Such component systems must have at least Release 4.5.

(C) SAP AG HR250 5-10

© SAP AG 1999

ALE

WorkplaceServer

Comp.System

User master dataFunction assignment

Single or composite role (system-dependent)Profile (system-dependent)Initial password

What Data can be Distributed?

The following data can be distributed with the CUA: User master records: address, logon data, user fixed values and parameters The corresponding single and composite roles and profiles are assigned to users for all component systems. The use of CUA has the advantage that you need not log onto the individual clients in order to maintain these assignments locally. You can do this centrally from the Workplace Server.

Initial password: An initial password is sent to the component systems when a new user is created. The user can change this password in the usual manner.

Lock status: In addition to the known reasons for locking (failed attempt to logon or lock by an administrator), there is a new "general lock". This lock takes effect in all component systems in which the particular user is authorized. It can be removed both centrally and in the particular component system.

Single and composite roles and authorization profiles can be passed on. However, they are usually maintained locally and not centrally. Other system settings and releases might require that you adapt the roles.

(C) SAP AG HR250 5-11

© SAP AG 1999

AddressLogon data

Fixed valuesParameters

ProfilesRolesLocks

Groups

AddressLogon data

Fixed valuesParameters

ProfilesRolesLocks

Groups

Global

Proposed

Redistributed

Local data

Everywhere

Workplace Server

CUA Configuration: Field Attributes

You can define whether each element of the user data should be maintained on the Workplace Server or locally in the component systems. You can do this with Transaction SCUM (from Transaction SALE: Model and implement business processes → Configure predefined ALE business processes → Cross-application business processes → Implement Central User Administration → Set distribution parameters for fields) on the Workplace Server.

You can assign one of the following field attributes for each field of Transaction SU01: Fields with attribute global can only be maintained on the Workplace Server. The data is distributed to the component systems after being saved. Global fields can only be displayed, but not changed, in the component systems.

Entries made on the Workplace Server are distributed to the component systems for fields with attribute Proposal. These fields are maintained locally there. They are not redistributed.

You can maintain data both locally and centrally for fields with attribute Redistribution. If data is changed in one component system, the changes are passed back to the Workplace Server and from there to the other component systems.

Fields with attribute local can only be maintained in the component systems. There is no distribution. The data of fields with attribute Everywhere can be maintained in all systems. There is no redistribution. This attribute only exists for the Lock tab.

(C) SAP AG HR250 5-12

© SAP AG 1999

WorkplaceServer

Comp.System n

Comp.System 1

User maint.

new

new

new

WorkplaceServer

Comp.System n

Comp.System 1

Integration in Existing User Environment

User maint.

old

old

new

Initial Configuration of a User Environment

User maint.... ...

Integration of Existing Systems

User maint.

Existing systems can be coupled with the CUA in two ways: Either the users are newly created or existing users are copied to the CUA.

When a user is newly created, CUA is used on the Workplace Server from the beginning and the user master records are distributed automatically. This ensures that the data is consistent in all systems.

If CUA is implemented when there are already existing users, these users must be copied to the Workplace Server. The copied user master records must be adapted and checked there.

The single and composite roles assigned to the users must also be stored on the Workplace Server. Such assignments can then be made centrally. Existing assignments can be reused.

The assignment of authorizations to single roles must still be maintained in the existing distributed component systems.

(C) SAP AG HR250 5-13

© SAP AG 2002

Workplace Server

Migration Tool

WorkplaceServer

Comp.System

Copyusers

New usersIdentical usersDifferent users

Existing user master records are copied from the component systems to the Workplace Server using the migration transaction SCUG. The migration is run once for each component system. The copied master records can then only be maintained on the Workplace Server.

User is the name under which the employee logs onto the SAP System. The user must be defined in all component systems of the CUA with the same first and last names.

On the Workplace Server start Transaction SCUG (from Transaction SALE: Model and implement business processes → Configure predefined ALE business processes → Cross-application business processes → Implement Central User Administration → Copy users from new systems) and select the component system from which the user master records should be copied. Choose Copy user.

(C) SAP AG HR250 5-14

© SAP AG 2002

Workplace Server

Copy User

Copy userCopy userCopy userMaintainuser and

restart

MaintainMaintainuser anduser and

restartrestart

Newuser

Identicaluser

Differentuser

Alreadycentral

user

Migration ToolMigration Tool

There are three different cases: The user in the component system does not exist on the Workplace Server. The corresponding user is displayed in the New users tab page. You can copy these users directly to the Workplace Server by selecting and clicking on Copy users. Composite roles are created on the Workplace Server The component system to which it belongs and the role and profile assignment are recorded.

The user in the component system already exists with the same first and last names on the Workplace Server. The corresponding user is displayed in the Identical users tab page. You can copy these users directly to the Workplace Server by selecting and clicking on Copy users. The component system to which it belongs and the role and profile assignment are created anew.

The user in the component system already exists on the Workplace Server, but with a different first and last name. The corresponding user is displayed in the Different users tab page. You first have to clear up the difference. If the name is correct on the Workplace Server, you can copy the user. On the other hand, if the name from the component system is correct, you have to change the name on the Workplace Server using Transaction SU01. The user account is displayed in tab page Identical users after after the correction. If the user account really has two different owners, an owner must be changed on either the Workplace Server or in the component system.

The user accounts that were copied and that are administered centrally are displayed on the Already central users tab page.

(C) SAP AG HR250 5-15

© SAP AG 2002

Workplace Server

User Maintenance

... Systems Roles Profiles Groups

PRDCLNT100

PRQCLNT200

PRDCLNT100

PRQCLNT200

Superuser

Staff

AdministratorT-...........

Workplace Server

The SU01 display changes after the CUA has been activated (Tools → Administration → User maintenance → User).

The Workplace Server also contains the Systems tab page. It lists the logical systems to which the user data should be distributed. The corresponding user can only be used for these systems. There is also a column for systems on the Roles and Profiles tab pages. You can thus assign single and composite roles as well as profiles separately for each component system. By choosing Save you distribute the data to the component systems.

Single and composite roles are maintained and created in the component systems. To assign single and composite roles as well as profiles that are only stored in certain component systems, choose Text comparison from subsystems on the Roles and Profiles tab pages. The names of the single and composite roles as well as the profiles (specified in the component systems) are copied to the Workplace Server together with their short descriptions. You can find out the names using F4. Since this data can be changed in the component systems, you should repeat the copy from time to time.

In the component systems you can only maintain those fields of Transaction SU01 whose global attribute is not set. New users cannot be created in the component systems.

(C) SAP AG HR250 5-16

© SAP AG 2002

Workplace Server

Log Display for CUA

... Systems Roles Profiles Groups

PRDCLNT100

PRQCLNT200

PRDCLNT100

PRQCLNT200

Superuser

Staff

AdministratorT-...........

Workplace Server

The SU01 display changes after the CUA has been activated (Tools → Administration → User maintenance → User).

The Workplace Server also contains the Systems tab page. It lists the logical systems to which the user data should be distributed. The corresponding user can only be used for these systems. There is also a column for systems on the Roles and Profiles tab pages. You can thus assign single and composite roles as well as profiles separately for each component system. By choosing Save you distribute the data to the component systems.

Single and composite roles are maintained and created in the component systems. To assign single and composite roles as well as profiles that are only stored in certain component systems, choose Text comparison from subsystems on the Roles and Profiles tab pages. The names of the single and composite roles as well as the profiles (specified in the component systems) are copied to the Workplace Server together with their short descriptions. You can find out the names using F4. Since this data can be changed in the component systems, you should repeat the copy from time to time.

In the component systems you can only maintain those fields of Transaction SU01 whose global attribute is not set. New users cannot be created in the component systems.

(C) SAP AG HR250 5-17

© SAP AG 2002


Explain how the CUA works

Describe the ALE configuration

Explain how to create users on the Workplace Server and how to distribute them to the component systems

Central User Administration: Unit Summary

(C) SAP AG HR250 5-18

© SAP AG 1999

Central User Administration (CUA)

SAP ESS User Maintenance

11

22

User Management

(C) SAP AG HR250 5-19

© SAP AG 2002

Define an ESS user



At the conclusion of this topic, you will be able to

SAP ESS User Maintenance: Topic Objectives

(C) SAP AG HR250 5-20

© SAP AG 2002

An SAP ESS user is a SAP system user who is enabled for SAP ESS.

Defining characteristics:Individualized; assigned to one employee only

Assigned to the customer-defined ESS role

Used exclusively by one employee

An SAP user who is not necessarily limited to using SAP ESS

Definition of an SAP ESS User

Technically an SAP ESS user is a SAP user with the following defining characteristics:

Individualized - assigned to and used exclusively by one employee

- This employee can only maintain his or her own data.

Assigned to a customer-specific role

- Not limited to SAP ESS use only, but can have additional authorization for tasks that can only be performed directly in R/3 and only using the SAPGUI

An Enterprise Human Resources (EHR) user is a pricing concept that defines a certain price for an SAP user that is then licensed for ESS use.

The Employee user is a component of the mySAP.com licensing concept in which there is a certain price for an SAP user who is licensed for the mySAP Workplace and for SAP ESS.

(C) SAP AG HR250 5-21

© SAP AG 2002

Basic Procedure

Component System

Workplace Server

Providing SAP ESS for Employees

If they do not yet exist, create users on the Workplace Server and in the HR component system.Assign an SAP system user to an employee with Infotype Communication (0105) in the HR component system.Assign the SAP system user to the composite role Employee Self-Service(copy of SAP_WP_EMPLOYEE) on the Workplace Server.Automatically distribute (with CUA) the SAP system user from the Workplace Server to the component systems.

(C) SAP AG HR250 5-22

© SAP AG 2002

SAP ESS User Installation Process

Employees with existing SAP system users

Select the employees who will use SAP ESS (component system)

Employees are authorizedfor SAP ESS

Copy composite role (SAP_WP_EMPLOYEE) to the customer namespace (Workplace Server)

New user attributes

2

3

3b3a

1

4b

Employees who do not have existing SAP system users

Copy user attributes4a

To install users, you must first copy composite role SAP_WP_EMPLOYEE, containing the single roles and system authorizations needed for SAP ESS, to the customer namespace on theWorkplace Server.

You must then decide which employees you intend to enable for SAP ESS (component system).

There are two groups:

Employees with existing SAP users who are not yet authorized to use SAP ESS. For these employees you must:

- Establish a link between the master records and the existing SAP users

- Authorize them to use SAP ESS

Employees who do not have SAP users. For these employees you must:

- Create SAP users


For new users, you can define how your employees can log onto SAP ESS in the User Attributes

SAP provides a tool to guide you through the installation. The tool is available using the transaction HRUSER.

(C) SAP AG HR250 5-23

© SAP AG 1999

Employee Selection for SAP ESS

You must decide which employees you intend to enable for SAP ESS. If you do not want to enable all employees, you may choose a certain department, or you may choose employees of a particular employee group.

The user installation tool (transaction HRUSER) offers you different selection criteria for choosing employees. You can pre-select employees by their organizational assignment, or by their employee data, such as the employee status.

The user selection process also enables you to exclude inactive or retired employees. You can define employee status to ensure that you do not include inactive employees in the group of employees to be authorized for SAP ESS.

(C) SAP AG HR250 5-24

© SAP AG 1999

Set Up and Maintain ESS Users (Start)

Preparation

Assign employees to existing users

Copy SAP role to customer namespace

Correction

Delete ESS users

Change user attributes/key date

Select employees using employee master

Preselect employees using org. assignment

User/Authorization Assignment

User attributes


Z_HR250_SAP_WP_EMPLOYEE

User group ESSUSER

Role


RFC destination W70CLNT400

CUA is active

Component System

Employee Selection Details

You can pre-select employees using their organizational assignment.

In the Set up and Maintain ESS Users (Start) screen, choose Preselect employees using org. assignment in the User/Authorization Assignment area. The Choose Personnel Numbers using Org. Assignment screen appears.

Enter the relevant search criteria and choose Execute.

The Choose Personnel Numbers using Employee Master screen appears. Enter relevant search criteria and choose Execute. Only the employees in the original organizational units will be displayed.

You can also select employees by employee data.

Select Select employees using employee master in the User/Authorization Assignment area of the Set Up and Maintain ESS Users screen. The Choose Personnel Numbers using Employee Master screen appears.

Enter the relevant search criteria and choose Execute.

The Set Up and Maintain ESS Users (List) screen appears.

You now have a selected group of employees that you can maintain for SAP ESS.

(C) SAP AG HR250 5-25

© SAP AG 2002

Employees with Existing SAP System Users (1)


Preparation



Correction

Delete ESS users





User attributes



User group ESSUSER

Role



CUA is active

Establish a link between the employee master records and the existing SAP system users

Component System

Some of your employees might already have SAP users, but not authorization for SAP ESS. You therefore have to assign the employee master records to existing SAP users. It is a one-to-one assignment and has to be done manually. While assigning your SAP ESS users ('employees') to existing SAP users, you can check the employee's master data and the user master record.

In the Set Up and Maintain ESS Users (Start) screen, select Assign employees to existing users in the Preparation area. The Compare User Master with HR Master screen appears. There are various methods for selecting users.

Select a method and choose Execute. The Assign Employees to Existing Users screen appears.

Select Assign employees. The Choose Person dialog box appears.

Select an employee. The Create Relationship dialog box appears. Change the validity date if necessary and select Create.

The users still need authorization for SAP ESS.

(C) SAP AG HR250 5-26

© SAP AG 2002



Preparation



Correction

Delete ESS users





User attributes



User group ESSUSER

Role



CUA is active


Component System

You can view the relationship in the Communication infotype (0105). The SAP user must be assigned to the employee with subtype 0001.

The assignment of the user to the SAP ESS role authorizes the SAP user to access SAP ESS.

(C) SAP AG HR250 5-27

© SAP AG 2002



Preparation



Correction

Delete ESS users





User attributes



User group ESSUSER

Role



CUA is active


Component System

You can now set up ESS authorization. In the Set Up and Maintain ESS Users (Overview) screen, select Employees with users without ESS role.

The Relate Users to Persons screen appears. Select the employee you are working with and choose Authorization Assignment.

The Attributes of Users to be Created screen appears. Choose Execute.

If a large number of employees is involved, you can generate the users for SAP ESS in background mode (Option Background).

(C) SAP AG HR250 5-28

© SAP AG 2002

Employees Without Existing SAP System Users (1)

Set Up and Maintain ESS Users (Overview)

Inactive employees without user assignment (ok)Total number of employees selected

Extended list

ESS Participants

Employees with users and ESS rolesESS role

Inactive employees with usersEmployees with deleted users

Employees with inconsistencies

Employees with users without ESS role

Employees without users

ESS Participants without users/authorization

Key date

0 Reconcile User

Z_SAP_EMPLOYEE

Background

Background

Background

Background

09.11.2000

0

1

0

0

00

Create SAP system users and authorize them to use SAP ESS.

Component System

If you have employees who do not have SAP users, first create SAP users for them and then authorize them to use SAP ESS.

In the Set Up and Maintain ESS Users (Overview) screen:

Choose Employees Without Users.

- If you select Background, the Attributes of Users to be Created screen appears.

- If you select Overview, the Create Users for Persons screen appears.

Select a person and choose Create User. The Attributes of Users to be Created screen appears. Choose Execute.

(C) SAP AG HR250 5-29

© SAP AG 2002

Employees Without Existing SAP System Users (2)

Personnel No. 250991001

EE Group 1 Active employee Pers. area

EE Subgroup X1 Hourly wage earn...From 01.01.2000 to 31.12.2000

Change Communication

Infotype Communication: Assign an SAP system user to an employee master record

Assign ESS role to user

Component System

Communication

Type 0001 System user name ID/number P25099101

You can view the relationship in the Communication infotype (0105). The SAP user must be assigned to the employee with subtype 0001.

Whereas you had to assign employees having SAP users ESS authorization manually, it is assigned automatically here. .

(C) SAP AG HR250 5-30

© SAP AG 1999

Password

Usergroup

Role

Authorization Assignment

Decimal Format

Data Format

Start Menu

Logon Data

User Attributes

You must decide how you would like your employees to log on to SAP ESS.

The user group ESSUSER is a fixed user attribute. It is used to distinguish between SAP ESS users and other system users, such as administrators.

You can change user attributes in the Set up and Maintain ESS User (Start) screen. In the Attributes of users, you can modify the Password field. The initial password is INIT. You cannot change the entry ESSUSER in the User group field because it is important to differentiate users authorized for SAP ESS from other users. In the Role field, the SAP role (which you have copied into your namespace) is the default.

SAP delivers a user exit, which you can use to determine your own password routine and user name. SAP delivers user exit Exit_saplehus_001 as part of the enhancement HRESSWWW. This user exit enables you to change the name and password that the user installation tool creates for each SAP ESS user that is generated.

Existing users keep their attributes, such as user group, password, date and decimal format and start menu. The existing setting are not overwritten.

(C) SAP AG HR250 5-31

© SAP AG 1999


Preparation



Correction

Delete ESS users





User attributes



User group ESSUSER

Role



CUA is active

Users on the Workplace Server and in the component systems

WorkplaceServer

ComponentSystem

HRUSER and CUA

If CUA is active, Transaction HRUSER access the Workplace Server and hereby permits direct assignment in the component system of the composite role (copy of SAP_WP_EMPLOYEE), which resides on the Workplace Server. The user is created locally in the HR component system and on the Workplace Server. The user is assigned to the employee in the component system with Infotype 105 and is assigned to the composite role on the Workplace Server. The CUA then distributes the user data to all the component systems.

(C) SAP AG HR250 5-32

© SAP AG 1999

Component System

User Maintenance in SAP ESS

Functions to support periodic user maintenance

in SAP ESS

Check inactive employees with users

Delete users

User exit

The system contains functions that support periodic user maintenance in SAP ESS. You should look for inconsistencies on a regular basis by selecting:

Inactive employees with users. These are employees who have retired or left the company and still have SAP users. You delimit their user assignment because you do not want them to be able to use SAP ESS.

Employees with deleted users.

New employees who need ESS users.

SAP delivers workflow support for SAP ESS user maintenance. Work items prompt system administrators to create SAP ESS users for new employees and to delimit the SAP ESS users of employees leaving the company.

(C) SAP AG HR250 5-33

© SAP AG 1999

Set Up and Maintain ESS Users (Overview)

Inactive employees without user assignment (ok)Total number of employees selected

Extended list

ESS Participants

Employees with users and ESS rolesESS role

Inactive employees with usersEmployees with deleted users


Employees with users without ESS role

Employees without users

ESS Participants without users/authorization

Key date

0 Reconcile User

Z_SAP_WP_EMPLOYEE

Background

Background

Background

Background

09.11.2000

0

0

0

1

00

Component System

User Maintenance: Employees with Inconsistencies


In the user installation tool (transaction HRUSER) there is an option for maintaining Employees with inconsistencies. The options are:

Inactive employees with users:

- In the Set Up and Maintain ESS Users (Overview) screen select Overview/List.

- The Delimit User Assignments to Inactive Persons screen appears. Select the employee you wish to delimit and choose Delimit.

Employees with deleted users. Users cost money and perhaps you have created too many. To delete users proceed as follows:

- In the Set Up and Maintain ESS Users (Start) screen, select Delete ESS Users.

- The Delete ESS Users (Selection) screen appears. Enter the name of the user you want to delete and choose Execute.

- The Delete ESS Users (Overview) screen appears. Select the users you want to delete and choose Delete users (online). The users are deleted from the user master in the system.

You can only delete SAP ESS users that are assigned to the user group ESSUSER here.

(C) SAP AG HR250 5-34

© SAP AG 2002

User Maintenance: User Exit

Exit_saplehus_001

Component System

SAP delivers user exit 'Exit_saplehus_001' as part of the enhancement HRESSWWW.

It enables you to change the name and password that the user installation tool creates for each generated SAP ESS user. As a default, the tool will create:

Name: P followed by the personnel number (for example P00000001)

Password: uses "init" as an initial password

To access and modify the user exit:

Tools → ABAP Workbench → Utilities→ Enhancements → Project Management.

(C) SAP AG HR250 5-35

© SAP AG 1999

SAP ESS Tools

Helpful tools for creating and authorizing usersin SAP ESS:

Log

Background processing

View data

Role maintenance

SAP Employee Self-Service provides a number of useful tools for creating and authorizing users:

Log: All the steps you perform are recorded in a log file. They are written to a log file and displayed as historical information. You can display the log at any time. To do so, select Log. To reset the log, select Delete log.

Background processing: You can perform most of the tasks in SAP ESS in the background. SAP recommends the use of background processing if your user group has more than 100 employees. To do so, select Background.

View data: Select HR master data to view or change the HR master of the employee you are working with. To do so, select User master record.

Role maintenance: You can access role maintenance with transaction PFCG or in the Attributes of Users screen by choosing Display.

(C) SAP AG HR250 5-36

© SAP AG 2002

You are now able to

Outline the R/3 System authorization concept

Describe the concept of Central User Administration

Copy existing users to the mySAP Workplace Server



User Management: Unit Summary

(C) SAP AG HR250 5-37

User Management-Exercises

(C) SAP AG HR250 5-38

(C) SAP AG HR250 5-39

Unit: User Management Topic: User Maintenance in SAP ESS


• Create SAP ESS users for employees with existing R/3 users and for employees that do not have R/3 users

• Link existing users with employees

• Assign SAP ESS users for employees who do not have SAP users

• Check whether newly created ESS users work properly

The CAB company has decided to implement SAP ESS for its Service department. You must set up existing and new users in the company for use in SAP ESS.

1-1 Find out which steps are necessary to create users for employees with and without R/3 users in transaction HRUSER and complete the records.

1-1-1 If the employee already has an R/3 user, you must

_________________________________________________

_________________________________________________

_________________________________________________

1-1-2 If the employee does not yet have an existing R/3 user, you must

_________________________________________________

_________________________________________________

_________________________________________________

1-2 Link an existing user (HR250-##) with an employee (250995##) using the option Assign employees to existing users. Use role Z_HR250_SAP_WP_EMPLOYEE.

(C) SAP AG HR250 5-40

1-3 Create users for the organizational unit ## Customer Service in the Caliber A Bicycle Company. Use the evaluation path Organization-Position-Job (O-S-P) and technical path 3 to pre-select the employee with the organizational unit in the current plan version.

1-4 Review the entries you made in the R/3 System when setting up the users. Look at the Communication infotype (0105) and the user master records for employee 250995## in the ## Customer Service organization unit. View the entries from transaction HRUSER.

1-5 Use the Web browser to make sure that the users you created work correctly. (Your trainer will tell you which URL to use for logging onto the Workplace System.)

(C) SAP AG HR250 5-41

User Management-Solutions

(C) SAP AG HR250 5-42

(C) SAP AG HR250 5-43

Unit: User Management Topic: User Maintenance in SAP ESS

1-1 Find out which steps are necessary to create users for employees with and without R/3 users in transaction HRUSER and complete the records.

1-1-1 If the employee has an R/3 user, you must create a relationship between the employee and user using the Communications infotype (0105, subtype 0001) and authorize the use for SAP ESS.

1-1-2 If the employee does not have a R/3 user, you must create a user and authorize the employee for ESS.

1-2 Link an existing user (HR250-##) with an employee (250995##) using the option Assign employees to existing users. Use role Z_HR250_SAP_WP_EMPLOYEE.

Transaction: HRUSER or IMG Path: Personnel Management → Employee Self - Service → General Setting for ESS → Create SAP Users for ESS

1-2-1 In the Set Up and Maintain ESS Users (Start) screen, select Assign employees to existing users in the Preparation area.

1-2-2 In the Reconcile User Master with HR Master screen, enter HR250-## in the User name field and select all other setting that are relevant to your company. Choose Execute.

1-2-3 Select user HR250-## in the Assign Employees to Existing Users screen.

1-2-4 Select Assign employees.

1-2-5 Enter employee number 250995## in the Choose person dialog box and choose Enter.

1-2-6 Select Create in the Create Relationships dialog up box.

1-2-7 Confirm the message “User HR250-## was related to employee 250995##” with Enter.

1-2-8 Return to the HRUSER screen and select Select employees using employee master data in the User/authorization assignment area.

1-2-9 Enter employee number 250995## in the Choose person numbers using employee master screen and choose Enter.

1-2-10 An entry appears in the Employees with users without ESS role. Select List/Overview.

(C) SAP AG HR250 5-44

1-2-11 In the Relate User with Persons screen, select the personnel number and choose Authorization assignment.

1-2-12 In the dialog box Attributes of Users make sure that the correct role Z_HR250_SAP_WP_EMPLOYEE is used and select Execute.

1-2-13 Choose Enter to confirm the message “Profile(s) for role Z_HR250_SAP_WP_EMPLOYEE assigned to user HR250-##”.

1-2-14 Choose Refresh to see the changes.

1-3 Create users for the organizational unit ## Customer Service in the Caliber A Bicycle Company. Use the evaluation path Organization-Position-Job (O-S-P) and technical path 3 to pre-select the employee with the organizational unit in the current plan version.

Transaction HRUSER or IMG Path: Personnel Management → Employee Self - Service → General Setting for ESS → Create SAP Users for ESS

1-3-1 Select Preselect employees using org. assignment in the User/Authorization assignment area of the Setup and Maintain ESS Users screen.

1-3-2 Enter 01 in the Plan version field, and O in the Object type field. Use the structure search function to locate customer service organizational unit ## in the Caliber A Bicycle company and choose Execute.

1-3-3 The personnel numbers for the employees in the selected organizational unit are displayed in the Choose Personnel Numbers Using Employee Master screen. Choose Execute.

1-3-4 In the Setup and Maintain ESS Users (Overview) screen, you see an entry for the number of employees without users in the Employees without users field in the User/authorization assignment area.

1-3-4 Choose List /Overview.

1-3-5 The Create Users for Persons screen appears with a list of all of the employees that exist in the preselected organizational unit that do not have users.

1-3-6 Choose Select All.

1-3-7 Choose Users with authorization.

1-3-8 Make your desired settings for the new users in the Attributes of users dialog box. You can change the logon data and the password that is assigned to the employees when their users are created. Choose Execute.

1-3-9 The new users are listed for the employees in the Create persons for users screen.

1-3-10 Select Refresh to see the changes.

(C) SAP AG HR250 5-45

1-4 Review the entries you made in the R/3 System when setting up the users. Look at the Communication infotype and the user master records for employee 250995## in the ## Customer Service organization unit. View the entries from transaction HRUSER.

Transaction: HRUSER or IMG Path: Personnel Management → Employee Self - Service → General Setting for ESS → Create SAP Users for ESS

1-4-1 Select Select employees using employee master in the User/Authorization assignment area of the Setup and Maintain ESS Users screen.

1-4-2 Enter the personnel numbers for the employees in your group (250991## to 250995##) in the Choose Personnel Numbers Using Employee Master screen. Choose Execute.

1-4-3 In the Setup and Maintain ESS Users (Overview) screen, select Display to get the Total number of employees selected.

1-4-4 Select employee 250995## and choose HR master data. Check the entry in infotype Communication (0105, subtype 0001).

1-4-5 Return to the overview, select User Master Data and check the role and profiles for the user.

1-5 Use the Web browser to make sure that the users you created work correctly. (Your trainer will tell you which URL to use for logging onto the Workplace System.)

1-5-1 Start the browser and enter the following URL:

1-5-2 http//:<webserver>:[port]/scripts/wgate/sapwp/!

1-5-3 Log on with one of the users you created.


© SAP AG 1999

Contents

Customizing the SAP ESS Services

Country-Specific Customizing Settings

Workflow in the Web Environment

Customizing Life and Work Events

Customizing SAP ESS

This chapter contains information about R/3 System customizing that you need to adjust SAP Employee Self-Service to meet your requirements.


© SAP AG 1999


Perform the necessary Customizing steps in the R/3 System to adapt SAP ESS to your company's requirements

Describe the SAP ESS country-specific settings

Describe how Workflow can be used within SAP ESS

Explain how to customize the Life and Work Events

Customizing SAP ESS: Unit Objectives


© SAP AG 1999

Customizing SAP ESS

Course Overview


User Management


Summary

Enhancing SAP ESS

SAP ESS Services




© SAP AG 2002

Users were created for the employees and they were assigned to the Employee Self-Service role

The SAP ESS services should now be configured to satisfy the requirements of the company and the employees. The options provided by the Workflow should also be taken into consideration.

The Life and Work Events should be adapted to the company requirements.

Customizing SAP ESS: Business Scenario


© SAP AG 1999



11

22

Customizing Life and Work Events33

Customizing SAP ESS


© SAP AG 2002

Who's Who

Time Management

Travel Management

Interfacing with Business-to-Business Procurement

Jobs

Payment


Skills

At the end of this unit you will be able to set up the following R/3 System customizing services:

Customizing the SAP ESS Services: Unit Objectives

For service-specific customizing, choose the following menu path in the Implementation Guide (IMG): Personnel Management → Employee Self-Service → ESS Settings for Specific Services.


© SAP AG 1999

Display/Change Picture

Throughout the company

Individual for each employee

Dear Mary Hansen,

I wish you a very happy birthday.

Birthday Greetings

MiniApp

General Settings

The Personal Picture MiniApp defines: Whether and how a picture should be displayed in the picture area of the MiniApp Whether to display birthday greetings in the MiniApp when the employee logs on on his own birthday

You go to the corresponding Customizing activity with: Personnel Management → Employee Self-Service → General Settings for ESS → MiniApp for Personal Picture

You can exclude the picture area entirely. You can define a picture or graphic to be displayed throughout the company. To do so, specify the required URL. Individual employee settings can be made for this area. Enter the URL of a default picture. The employee can replace this picture with one of his own. The default picture is displayed if an employee has not entered his own picture.

Define a text in every language required for the greeting. Save the text. You can formulate the text so that the name and title of the ESS user is displayed. To do so, use the following placeholders: &FNAME& for the first names &LNAME& for the last names &ENAME& for editing the name

If you want to display spaces before or after a placeholder, enter an underscore '_' in the corresponding position.

Example: If you enter "Happy Birthday_&FNAME&_&LNAME &!", for example "Happy Birthday Mary Hansen!" will be displayed.


© SAP AG 2002

Determine document type

Restrict search for employee

Change selection and output fields

User exits

Customizing Settings:

Customizing Who's Who

Employees can change their own data in the Who's Who service. This is true for all fields of infotype Communication (0105), with the exception of subtype 0001, and for all fields of infotype Internal Data (0032).


© SAP AG 1999

Who's Who: Determine Document Type

Employee photos are entered in the optical archive

SAP delivers the document type HRICOLFOTO for the photo storage

In this step, you define the document type for the Who's Who photo stored in the optical archive. You do not have to perform this step if you already defined the document type for the optical archive. In the SAP standard system, document type HRICOLFOTO was already set as a default value in Table T77S0.

The same document type is also used for entering photo formats in Personnel Administration (PA). You may not change the document type if you want to use a photo that already exists in SAP ESS.

SAP ESS supports photos in GIF and JPEG formats. It does not support bitmap (BMP) graphics. To define whether a photo should be displayed in SAP ESS, choose the following in the IMG: Personnel Management → Employee Self-Service → ESS Settings for Specific Services → Office →

Who's Who/User’s Own Data (ESS): Determine Functions In order to use the photo storage, you must have installed the optical archive for the R/3 System. Employees can link their own photo to the application with the Change Own Data service.

(C) SAP AG HR250 6-10

© SAP AG 1999

Who's Who: Restricting the Search for Employees

Possible restrictions:

Employee is not part of the company

Employee is not currently working (for example during maternity leave).

Employee is part of the company, but is retired

Employee is active in the company

You can restrict the search for employees in the Who's Who service. The default is that there is no restriction, so the system looks for all employees when you search.

The search is restricted by maintaining Table T77S0. Enter the following keys: Group name should be ESS and Semantic abbreviation STAT2. Select one or more of the following values in the Value field:

Value Restriction

0 Employee is not part of the company

1 Employee is part of the company, but is not working (for example, maternity leave).

2 Employee is part of the company, but is retired

3 Employee is active in the company

4 External employee

The most common setting is the value 3 to restrict the search to active employees only. The value you set will depend on your company's Customizing. This is not delivered by SAP.

(C) SAP AG HR250 6-11

© SAP AG 1999

Who's Who: Change Selection and Output Fields (1)

You can define fields for the:

Selection of an employee

"Hit list" (list of all employees who match the selection criteria )

Detail information for the selected employee

You can change the data selection and/or data output fields for the Who's Who service. The fields of the InfoSet of the underlying Ad Hoc Query should be used here.

The standard SAP system contains an InfoSet (SAP Query) for the Who's Who service. The SAP naming convention for the standard InfoSet is /SAPQUERY/HR_XX_PA_ESS. The country key 'XX' stands for international. The InfoSet itself resides in the global work area (cross-client). The selection and output fields are already defined.

You should check if the standard settings satisfy your requirements before making any changes.

All the selected fields are automatically copied to the service in the chosen order and are available there for selection or output.

Note that text fields cannot be marked for the data selection with the exception of the fields Organizational Unit, Position Name and Job Name.

You can define the sort sequence of the hit list in the Sort field on the Output fields list tab page in the query maintenance.

You should not select the Employee status field as a search field

(C) SAP AG HR250 6-12

© SAP AG 1999

If the standard settings do not meet your requirements, you can create your own InfoSets to:


Change the selection, output and detail fieldsDelete the default fields

Include fields which exist in the InfoSet

Include fields which do not exist in the InfoSet

If the standard settings do not meet your requirements, you can define your own InfoSets by copying existing functional areas and changing them. When doing this, you should take the customer namespaces into account and set the relevant country abbreviations.

Do not include the Personnel number field P0000-PERNR in the InfoSet. If you want to include the personnel number, select field P0001-PERNR.

The path for editing and creating InfoSets (Easy Access Menu) is Tools→ ABAP Workbench → Utilities → SAP Query → InfoSets.

To change the selection and output fields of Who's Who, start Transaction PZ01C or choose the following path in the IMG: Personnel Management → Employee Self-Service → ESS Settings for Specific Services → Office →

Who's Who (ESS): Selection and Output (PZ01) Remove the flag for Use default settings for. The list of fields within the tab pages is ready for input.

To change the selection fields, choose the Selection fields tab page.

To change the fields of the hit list, choose the Output field list tab page.

To change the fields of the detail screen choose the Detail output fields tab page.

To delete a pre-defined field, mark it on the appropriate tab page and choose Delete lines.

(C) SAP AG HR250 6-13

© SAP AG 1999



Change the selection, output and detail fieldsDelete the default fields



To include a further field of the InfoSet, mark the desired field in the area Fields in InfoSet. Then choose Copy entry from InfoSet table. You now have two options:

(1) Mark a field that already exists in the tab page and choose Insert entry in display table. The system copies the field of the InfoSet in front of the marked entry.

(2) Mark the empty field at the end of the tab page and choose Insert entry in display table. The system copies the InfoSet to the end of the tab page.

- The order of the fields on the tab page should match the structure of the fields in the services.

- The fields are structured with a maximum of four columns and a maximum of 20 fields (from top to bottom and left to right).

- The fields of the detail screen are structured vertically with a maximum of 20 digits, whereas the fields of the hit list are structured from left to right (maximum 20 fields).

(C) SAP AG HR250 6-14

© SAP AG 1999



Change the selection, output and detail fields

Delete the default fields



If you want to include a field that is not yet in the InfoSet, you must create a new InfoSet and assign the desired field to it. Include the field in the corresponding selection/output or detail output tab page.

The path for editing InfoSets is Tools → ABAP Workbench → Utilities → SAP Query → InfoSets.

(C) SAP AG HR250 6-15

© SAP AG 1999

The alternative to SAP Query:


The BAPI _EMPLOYEE_GETDATA method

Data selection

Hit list and detail screen

You can deactivate SAP Query and instead use the BAPI_EMPLOYEE_ GETDATA method. This increases the throughput and search speed in Who's Who.

Sometimes runtime problems can occur, especially in data selection. When this occurs, set the Selection fields indicator in the Use default settings for box. You can also set the hit list to BAPI_EMPLOYEE_GETDATA.

(C) SAP AG HR250 6-16

© SAP AG 2002

Who's Who: User Exit

Enhancement HRESSWWW: User exit (exit_saplrh65_001)

MillerMillhouseMillsMillstone...

Mill

SAP delivers a user exit to change the search pattern in Who's Who

Example:

To get a list of names beginning with 'Mill', enter 'Mill*'. You get Miller, Mill, Mills, and so on.

With the user exit, entering "Mill" gives you the same list.

The default setting for Who's Who is defined so that the user must either specify the full word or part of the word and wildcard (*).

In the enhancement HRESSWWW, SAP delivers a user exit (exit_saplrh65_001) to change the search pattern in Who's Who.

If you use the user exit, you do not need to enter the wildcard. The system automatically searches for words that begin with the specified string.

(C) SAP AG HR250 6-17

© SAP AG 1999

Leave

Attendance

Can the Attendance/Leave

type be used in SAP ESS?

Employee Self-Service

Time Management: Customizing Settings

?

You can define which Time Management subtypes are used for leave and attendance in SAP ESS.

In the IMG under ESS Settings for Specific Services → Time Management, you see a list of all the subtypes provided for recording attendance and leave. When you use the Leave Request, Leave Information or CATS service, some absence types might not be relevant to your SAP ESS users. You can deactivate them here.

(C) SAP AG HR250 6-18

© SAP AG 1999

Steps for setting up the Cross-Application Time Sheet (CATS) for SAP ESS:

Time Management: Customizing for CATS

Create data entry profiles for SAP ESS

Specify additional information for SAP ESS

Define field selection for SAP ESS

The Cross-Application Time Sheet (CATS) is available as an SAP Employee Self-Service application.

You can define the layout of this SAP ESS service in the same way as for the R/3 System. You can also make specific profile settings in a view designed especially for SAP ESS.

(C) SAP AG HR250 6-19

© SAP AG 1999

Target components

Data entry

Layout

FieldsEntry

Process

CATS: Creating Data Entry Profiles

You can set up your own data entry profiles in the Create Data Entry Profiles screen.

The ESS version of the time sheet does not support the following profile settings in the General settings area: With target hours, With totals line, With clock times, No deduction of breaks, Highlight rejected records, Workdays only, Display weekdays, Release future times, Release on saving, Approval required, No changes after approval, Immediate transfer to HR and Print program.

The following sections in the profile customizing are fully supported: Time settings, Cost accounting variant, Default values, Work list, Data entry checks (general), Checks for users of SAP HR and Workflow.

Person selection is not supported. The course CA500 will provide you with further information about configuring the Cross Application Time Sheet.

(C) SAP AG HR250 6-20

© SAP AG 1999

CATS: Additional Information

Initial lines

Web Settings

"Go to" function active

"Wkday/date" function active

"Copy prev period" function active

"Insert line" function active

"Delete line" function active

"Show/Hide all details" active

Display data entry profileHide help section

Extended

Copy including hours

Show all details now

Choose data entry profile

Initial lines at same time

Web settings for a CATS entry profile

You determine the layout of the ESS service in the same way that you customize the Time Sheet for R/3. You can also make specific profile settings in a view designed especially for the ESS service.

In the user parameter CVR, you must specify the data entry profile to be used for maintaining data for each employee. If you do not maintain this user parameter for an employee, the system uses the data entry profile ESS.

Alternatively, you can set up a data entry profile with the name ESS as the default value. The system uses this profile if you did not maintain user parameter CVR.

To enter additional specifications for the Web settings, access the Specify Additional Information for ESS Profile step.

(C) SAP AG HR250 6-21

© SAP AG 1999

CATS: Define Field Selection

Field settings available:Input

Required

Displayed

Hidden

To select the fields in which users should make entries using the standard profile ESS or your own profile, perform the IMG action Define Field Selection for ESS.

Within SAP ESS, you can only distinguish between Input and Hidden fields. The Required and Display fields are treated like Input fields. Highlighted fields are not supported.

To make a field Read only you need to modify the HTML template.

(C) SAP AG HR250 6-22

© SAP AG 1999

OvertimeOvertime

Time Management: Customizing for Leave/Attendance

Leave Requests

Leave Information

Attendance

Businesstrips, workperformed

Leave Request: You can specify the absence types that an employee may enter in the Leave Request service. In the ESS IMG, choose ESS Settings for Specific Services → Time Management → Time Management (ESS): Determine Subtypes and deactivate the subtypes that are not relevant using Deactivate.

Leave Information: You can specify the time evaluation variants used to simulate an account balance on the basis of time data that has not been evaluated by general time evaluation. Employees use this SAP ESS service to display the status of their leave balance for any date. The system checks whether the specified key date lies within a period that has already been evaluated.

If the date lies within a period that has already been evaluated, the system uses this data.

If the date is outside the last period evaluated, the system attempts to simulate time data for the specified key date

Time evaluation is run using the variant specified in the LLREP feature. To allow leave balances in SAP ESS, you must assign the required time evaluation variant using the LLREP attribute. If there are errors in the simulation, the system accesses the data from the Absence Quotas infotype (2006).

(C) SAP AG HR250 6-23

© SAP AG 1999

Early

Normal

Night

Work Schedule

Time Management: Customizing for Work Schedule and Time Statement

Work Schedule: In this service, Sunday is considered the last day of the week. If you do not want to display the days from Monday through Sunday, you can use the LDAYW attribute to specify a day other than Sunday as the last day of the week.

Time Statement: If you want to use a time statement form other than the one you are currently using in the Intranet, you can create your own form using the form editor. If you want to specify selection parameters other than those in the standard system, you can create a variant for your time statement form.

You can Web-enable functions with Tools → Web Development → Web Repository (Transaction SMW0).

(C) SAP AG HR250 6-24

© SAP AG 2002

Travel Management: Customizing Settings

Expense Reports:Online (R/3 System Release 4.6 and higher)

Offline (R/3 System Release 4.5 and higher)

If you use Travel Management in SAP ESS, you have the following options: The online Travel Management component delivered with Release 4.6B offers the new Travel Expense service with which you can enter your travel expenses online. This service does not require any ESS-specific customizing and is therefore recommended for implementing the Travel Management service in SAP ESS.

The offline Travel Management components delivered with Release 4.5+ using an Excel sheet. It requires ESS-specific customizing. You can do this in the ESS IMG in the section ESS Settings for Specific Services → Travel.

The offline service Expense Reports is not part of the standard SAP ESS menu, but can be easily added.

(C) SAP AG HR250 6-25

© SAP AG 1999

INTRANET

EMPLOYEEEMPLOYEE

COMPANYCOMPANY

Application Status

Jobs: Customizing Settings (1)

Employees can scan through open internal jobs, apply for these jobs and track the status of their application using the Intranet.

You do not have to define additional texts because you can create them in addition to the status texts. The status texts are read from the R/3 System and displayed for the applicant.

You can create additional texts for the processing status of the SAP ESS service Application Status.

Create these texts individually using the names recommended by SAP (Status-1, Status-2, Status-3, Status-4, Status-5, Status-6 and Status-7). Use PAWW as the text ID.

Enter the text you want and save it.

(C) SAP AG HR250 6-26

© SAP AG 1999

Job OpportunitiesJob Opportunities WillWill LemayLemay Navigation menuNavigation menu Start Page Log offStart Page Log off

Apply

Vice President HR & Finance (US)Vice President HR & Finance (US) You have extensive Human Resources experience, and have managed a

team of HR professionals. We operate on an international scale, and soyou must be fluent in English. We have long been the market leader inbusiness software development and sales, and can offer a challengingopportunity for an enthusiastic team-player.

Job OpportunitiesAll regions

ProductionHR-MANAGER

HR-DIRECTORSD-MANAGERSD-CLERK

Region CentralRegion NorthEastRegion SouthRegion West

Employment Opportunities

Jobs: Customizing Settings (2)

To implement Job Opportunities in the Intranet, you must set the following features: • INTDF (Default value for Internet). In the INTDF attribute, store the medium for Internet applications

and the default value for the address details to be transferred to the entry screen for the applications. • INTDY (Determines the organizational assignment of the applicant)

(C) SAP AG HR250 6-27

© SAP AG 1999

Paycheck Inquiry

Function module:

HR_CALC_SHEET_TO_HTML_PERIOD

Feature: EDTIN

Payment: Customizing Settings

To make the paycheck inquiry results available through the Intranet, you must:

Release function module HR_CALC_SHEET_TO_HTML_PERIOD for the Intranet by calling Transaction SMW0 in the R/3 System.

The standard system uses the remuneration statement program variant stored in the EDTIN feature to create the remuneration statement in the Intranet.

If you do not wish to use your standard remuneration statement in the Intranet, you can create a new form.

(C) SAP AG HR250 6-28

© SAP AG 1999

Maintain HR Master Data

Basic personal data Basic con.data

ActionsOrganizational assignmentPersonal DataAddressesBank detailsFamily Member/DependentsChallengeInternal Medical ServiceMaternity Protection/Parental LeaveMilitary Service

Direct selection

Create Family Member/Dependents

Basic personal data Basic contract data

Personnel No. Name Vera Sorokin

EE Group 1 Active employee Pers area CABB Caliber A Bicycle

EE Subgroup X0 Hourly wage earn.From To 31.12.9999

Family member Child

Last name Sorokin Birth name

First name Initials

Other title Name format

Name prefix Name prefix

Gender Female Male

Date of Birth

Birthplace

City of birth

Nationality 2./3. Nat.

Family Member/Dependents

Personnel No. 4599200

Name Vera Sorokin

EE Group 1 Active employee Per area

EE Subgroup X0 Hourly wage earn.

Infotype 0021Subtype 2

Styp 2STyp Name

1 Spouse2 Child

10 Divorced spouse11 Father12 Mother

Personal Information: Customizing Settings

Your HR administrators will probably need more subtypes than your SAP ESS users. You should limit the number of subtypes you use in SAP ESS to only the ones that are relevant for the users. For example, in the infotype Family Member/Dependents, the only subtypes relevant to your company's employees may be Spouse and Child. You should switch off any other family member subtypes.

Define the master data subtypes you need. This screen shows all the subtypes for the SAP ESS infotypes.

To define subtypes:

In the ESS IMG, choose ESS Settings for Specific Services → Personal Information → Personal Information (ESS): Determine Subtypes.

In the ESS Deactivation of Subtypes table, choose those subtypes you do not want to use and select the deactivate checkbox.

(C) SAP AG HR250 6-29

© SAP AG 1999

Emergency ContactFamily Member/Dependents

Emergency Address

Emergency Information

SAP ESS Employee Emergency Information

SAP ESS offers two ways to store the emergency address for an employee: in the Address infotype (0006) in the Family Member/Dependents infotype (0021).

Deactivate the infotype you do not want to use in both services Personal Information and New Hire.

(C) SAP AG HR250 6-30

© SAP AG 1999

Skills

- LanguagesSpanish

German

French

Portuguese

- Computer Skills

Microsoft Office

SAP R/3

HTML

XML

- Business Skills

Leadership

Creativity

Skills Profile - Parameter Settings (1)

Parameters:Catalog roots

Delimiter

Catalog text

Mode

Plan version

The Skills menu contains the following services:

Edit Skills Profile (PZ31)

Display Skills Profile (MY_QUALIS)

Display Requirements Profile (MY_REQUIREMENTS)

Profile Matchup with Own Position (MY_PROFILEMATCH)

You may change five parameters in service PZ31 (pz31.srv). These changes are not made directly in the R/3 System, but have an effect on the system. They also affect the Skills Profile display in the browser. You make the changes in SAP@Web Studio or a text editor, such as Notepad.

(C) SAP AG HR250 6-31

© SAP AG 1999

Parameters

Skills Profile - Parameter Settings (2)

Catalog roots

Delimiters

Catalog text

Mode

Plan version

In the service file of PZ31 (pz31.srv), you can change five parameters.

• Parameter 1: Catalog roots (~quali_id). This parameter limits the display of your skills to a certain area or sub-catalog. For the parameter ~quali_id, you can enter the eight-digit identifier for a certain sub-catalog of your skills catalog. This ensures that when your users call the Skills service, they see only the sub-catalog that is defined with the parameter ~quali_id.

• Parameter 2: Delimiter (~delimiter). The structure data of the skills catalog is stored using a string. The components of this string are delimited by default with the ASCII character '|'. If you want to use this character in the name of a skill, you must replace it with another one, such as a backslash, in this parameter.

• Parameter 3: Catalog text (~root_text). This parameter is initially empty. It means that the root text in the browser is 'Skills'. If you want to change this text, for example to 'Skills at My Company', you can override the default.

• Parameter 4: Mode (~display). This parameter is also initially empty. It means that the user can always modify the Skills Database service. If you would like the service to be for display only, you should set the parameter to 'X'.

• Parameter 5: Plan version (~plvar). This parameter overrides the default plan version 01.

• For further information see Note 184009.

(C) SAP AG HR250 6-32

© SAP AG 1999

External Bank Transfer Leave Request

Country-Specific IMG Settings

While SAP ESS delivers a number of country-specific services, many do not require any specific customizing.

Customizing is required for

Set Up Leave Request (SAP ESS Japan): You can specify the actions you want to use in the Leave Request (Japan) service. To deactivate action types that you do not want to use, select the action type concerned and choose Deactivate.

External Bank Transfer: Check Entry Permissibility (SAP ESS Australia): You can restrict the wage types that an employee is allowed to use for an external bank transfer in the SAP ESS service to prevent employees from making external payments using a certain wage type. External payments using this wage type must be maintained centrally by the HR administrator. In order to do so, you must have defined which wage types can be entered for the External Transfer infotype (0011) in the R/3 System. To deactivate a wage type for the SAP ESS service External Bank Transfer, choose Deactivate.

(C) SAP AG HR250 6-33

© SAP AG 2002


In the standard delivery, some services are already country-specific:

Address (including Emergency Address)

Bank details

W4 form for Family Member or Dependents (US only)

All the Personal Information services are country-specific. If more than one country version exists for a specific service, one of them serves as default. This service is specified in table T77WWW_SC. This table also contains the number of screens in an ESS service. All Personal Information services have two screens: an overview screen and a detail screen.

If you want to create new or modified country-specific program objects, make sure that you use customer namespaces instead of SAP namespaces. This ensures that these objects are not overwritten during a system upgrade.

Country-specific functionality can be implemented in two different ways: By making country-specific modifications using additional fields, different or additional plausibility and/or consistency checks (such as address, personal data, etc.).

By designing a new service for a particular country function (such as US Taxes)

(C) SAP AG HR250 6-34

© SAP AG 1999



11

22


Customizing SAP ESS

(C) SAP AG HR250 6-35

© SAP AG 1999

Explain how Workflow can be used within SAP ESS

Describe the Workflow templates delivered by SAP

At the conclusion of this topic, you will be able to

Workflow in the Web Environment: Topic Objectives

(C) SAP AG HR250 6-36

© SAP AG 1999


Processing of Workflow activities

Triggering of Workflow processes

Delivered Workflow templates

SAP ESS is an alternative user interface to the R/3 System. It therefore works with the same business objects. If activities using these objects trigger workflow events in R/3 (for example, a change of address), the same activities will trigger workflow events if they are executed using SAP ESS.

The delivered workflow templates include: post hire activities, user delimit, leave request, cancel leave request, employment and salary verification and W-2 reprint.

(C) SAP AG HR250 6-37

© SAP AG 1999

Processing Workflow Activities

Supported tasks in the Web inbox:Generic decision tasks

Executable HTML formats

Tasks NOT supported in Web inbox:

SAPGUI dialog methods

You can process SAP ESS workflow tasks from the Web inbox. The Web inbox only supports certain tasks. These are: • Generic decision tasks • Executable HTML forms

You cannot execute SAPGUI dialog methods in the Web inbox.

(C) SAP AG HR250 6-38

© SAP AG 1999

Employee Manager Administrator

Receivesnotification

Approves request

Checks,corrects and

approves request

Checks andrejects request

Receives notificationof unsuccessful posting

Rejects request

SubmitsLeave Request ESS

Changes request ESS

ESS

ESS

ESS

ESS

Triggering Workflow Processes

In order for an ESS object to trigger a workflow, the objects must be coupled to a workflow process in R3.

(C) SAP AG HR250 6-39

© SAP AG 1999

Post-Hire Activities

User Delimit

Workflow Templates in SAP ESS (1)

SAP ESS contains the following workflow templates:

Post-Hire Activities: Triggered by the events Employee.Hired and Employee.Rehired.

- Hiring triggers a workflow that sends a work item to the system administrator to create an ESS user.

- The HRUSER transaction is started in the SAPGUI inbox of the system administrator. The transaction preselects the new employee's data. A work item is sent to the Web inbox of the new employee, asking him or her to enter personal data in the SAP ESS service New Hire Event. The employee fills in the data and confirms that the data is complete. This sends a work item to the HR administrator, asking him or her to check the new employee's entries.

- The new employee receives a work item if his or her data needs to be corrected. Once corrected, the employee confirms in the Web inbox that the data is complete. A work item is sent again to the HR administrator. If there are no corrections, the workflow is complete.

User Delimit: Triggered by the events Employee.Retired and Employee.Company.Left

- This is a single-step task, rather than a workflow template. The workflow is triggered when an employee leaves the company. A work item is sent to the system administrator, asking him or her to delimit the departing employee's SAP ESS user. The role used here is System Administrator (delimits the user of the employee leaving the company).

(C) SAP AG HR250 6-40

© SAP AG 1999

Change Notify

Reject Approve

Employee Manager

Approve

ApproveApprovedRejected

Administrator

Workflow templates

• Leave Request(20000081)

• Cancel LeaveRequest(10000109)


Leave Request:

The employee triggers the workflow by entering leave request data in an HTML form. The system selects the manager who should approve the absence. He gets a work item asking him to review the employee's request.

If he approves the leave request, the approval is logged in the R/3 System. If there is a problem here, a work item is sent to the Human Resources Administrator, who addresses the issue.

If the manager rejects the request, the employee receives a work item in his Web inbox. Depending on the manager's comment, the employee either withdraws the request or changes it. In the latter case the workflow begins again.

Cancel Leave Request:

The employee triggers the workflow by selecting the leave to be cancelled. The system selects the manager who should approve the cancellation. The employee can overwrite this entry.

If the leave request to be cancelled is pending (approval has not yet been given), the system cancels the leave request workflow. The manager does not get a work item for approval.

If a leave request has already been approved, the manager receives a work item asking him or her to approve its cancellation.

(C) SAP AG HR250 6-41

© SAP AG 1999



W-2 Reprint

Employment and Salary Verification: Triggered when the employee submits a form asking an HR administrator to send an employment and salary verification to a third party:

- The employee fills out the form and decides which type of verification should be sent. He or she can also decide whether the form should be sent to an HR administrator to be printed, signed and posted, or whether if should be faxed directly to the address entered.

- If the employee chooses the first option, the HR administrator receives a work item in his or her inbox. Once it has been processed, a printer dialog appears in which the administrator can request that the document be printed.

W-2 Reprint: Triggered when the employee submits a form asking an HR administrator to provide a W-2 reprint.

- The employee submits the W-2 Reprint form from SAP ESS.

- The HR administrator receives a work item in his or her inbox. When the work item is executed, the print dialog box appears, prompting the administrator to send the document to the printer.

(C) SAP AG HR250 6-42

© SAP AG 1999



11

22


Customizing SAP ESS

(C) SAP AG HR250 6-43

© SAP AG 1999


Describe the framework for the Life and Work Events

Adapt Life and Work Events to the needs of your company

Create new Life and Work Events

Life and Work Events: Topic Objectives

(C) SAP AG HR250 6-44

© SAP AG 1999

Service type

Description

U URL for any contents in WWW

S ITS service name

X External serviceApplication

Information

Event menu

1

3

2

Overview: The Framework

The following pages give an overview of how Life and Work Events can be adapted or how new ones can be created to meet customer requirements. Those aspects of the system that should be taken into consideration when inserting additional or external contents are also discussed.

External service type X was introduced together with the framework for the Life and Work Events. This service type can be used to link to Web-based contents provided by knowledge base vendors. A service of type X can display any contents. The displayed contents can be personalized based on R/3 data.

Service types U and S were already used in SAP ESS Release 4.6B.

(C) SAP AG HR250 6-45

© SAP AG 1999

XXSXUXXSSSUSXUSUUU

emptyXemptySemptyU

Screen LayoutContent Area (3)Application Area (2)

1 2

1 2

3

Overview: Framework

Every service type in the application area (2) can be combined with every service type in the content area. The content area can also remain empty.

(C) SAP AG HR250 6-46

© SAP AG 2002

Overview: The Interface

Field name ValueP0002-PERID 999999999P0002-STATE CAP0002-NACHN TompkinsP0002-VORNA Andrea

SAP Standard Interface IF_DEFAULT

<input type=”hidden” name=”P0006-PERID”value=”999999999”><input type=”hidden” name=”P0006-STATE”value=”CA”><input type=”hidden” name=”P0002-NACHN”value=”Tompkins”><input type=”hidden” name=”P0002-VORNA”value=”Andrea”>

Example

You need a suitable interface to link from the R/3 System to a Web-based knowledge base. SAP provides you with the generic standard interface IF_DEFAULT.

Interface IF_DEFAULT creates an HTML form with a list of hidden input fields. The first table field (field name) is written in input field Name. The second table field (value) is written in input field Value. When all the data has been entered in the form, the form is sent to the external vendor.

The features of the input fields of the HTML form are set as follows: NAME = SAP_DATA ACTION = BASE_URL + KEY (The system fills in the variables) * METHOD = POST

* The following URL is an example of a typical way of accessing database contents using the Web: http://www.myserver.com/myDB?key=123 or http://www.myserver.com/myDB?key=abc There is always a static part (=Basis-URL) followed by a key (each form of identification for accessing a page)

Interface IF_DEFAULT can be used as a template to create a customer-specific interface. You need this template if the external service provider cannot communicate with the standard interface delivered by SAP.

(C) SAP AG HR250 6-47

© SAP AG 1999

Definition of the Customer Interface

IF_DEFAULT.HTMLIF_DEFAULT.FLOW

MY_NEW_INTERFACE.HTML (Copy and change the source code)MY_NEW_INTERFACE.FLOW (Copy, but do not change the source code)

Example

Overview: The Interface

To create a customer-specific interface, copy interface IF_DEFAULT. The files reside on the ITS in the template directory of service PZLE.

In our example, the new interface is called MY_NEW_INTERFACE. This name must be assigned to the corresponding service provider in table T77WWW_LE_EP.

(C) SAP AG HR250 6-48

© SAP AG 1999

Event menu

Catalogs

Services

Customizing the Framework (I)

The event catalog contains a number of catalogs such as 'Before you Start' and 'Personal Information'. Each catalog in turn contains various services such as Address. All subsequent Customizing steps are carried out by Transaction SM30.

(C) SAP AG HR250 6-49

© SAP AG 1999

Customizing the Framework (II): Menus

Tables for Customizing the MenuMenu creation: T77WWW_MNMenu description: T77WWW_MNTEvent-specific settings: T77WWW_LEDATA

The event name is defined in table T77WWW_MN. Event names are defined in further languages in table T77WWW_MNT. A new record is automatically created in table T77WWW_MN by adding a new event. The system uses the logon language as the country key.

Specific settings can be made in table T77WWW_LEDATA. For example, you can create a link to a start service (home page) for a certain service. You can also specify a function module that controls how long a user can access a certain event. SAP delivers function module ESS_NEW_HIRE_CHECK, which determines the time difference between the current date and the date a user joined a company. If this difference exceeds the value stored in field Duration, the function module returns the value 0, which closes the event. When a user wants to access an event, he or she therefore is informed that the event is no longer available for data maintenance. The function module can be used as a template for creating further function modules.

(C) SAP AG HR250 6-50

© SAP AG 1999

Customizing the Framework (III): Catalogs

Tables for Customizing the CatalogsCatalog creation: T77WWW_CTCatalog description: T77WWW_CTTCatalog position: T77WWW_MNPCountry-specific services: T77WWW_CD

The catalog name is defined in table T77WWW_CT. Table T77WWW_CTT is used to create catalog names in other languages. A new record is automatically created in table T77WWW_CT by adding a new catalog. The system uses the logon language as the country key.

An event is assigned to a catalog in table T//WWW_MNP. The position of the catalog within the event is also defined.

Table T77WWW_CD is used to assign an existing service to a country group. If a service is assigned to one or more country groups and it belongs to a user who has not logged onto one of these country groups, the service will not appear in the menu of this user.

(C) SAP AG HR250 6-51

© SAP AG 1999

Customizing the Framework (IV): Services

Tables for Customizing the ServicesService creation: T77WWW_SRVService description: T77WWW_SRVNService position: T77WWW_CTPMapping of application and contents (split screen): T77WWW_SMAP

All the services delivered by SAP with pre-configured Life and Work Events are listed in table T77WWW_SRV. Additional services can also be created.

Table T77WWW_CTT is used to create service names in other languages. A new record is automatically created in table T77WWW_SRV by adding a new service. The system uses the logon language as the country key.

The services are assigned to a catalog in table T77WWW_CTP. The position of each service within the catalog can also be determined.

To divide the screen into an applications and an information area, you have to link the content service with the application service. You can map it in table T77WWW_SMAP. All the services (application and content) first have to be maintained in table T77WWW_SRV. The height of the content area is specified in % (0-99). The default height is 30.

(C) SAP AG HR250 6-52

© SAP AG 1999

Customizing the Framework (V): Service Providers

Tables for Defining External Service ProvidersCreate external provider: T77WWW_LE_EP

Define required data: T77WWW_SDATA

External service providers are defined in table T77WWW_LE_EP. The interface and the Web server address of the external service provider are stored here. SAP delivers this table with a sample provider named SAP. IF_SAP: This interface is used automatically to display a sample page of an external provider. IF_DEFAULT: This is the generic interface that is delivered by SAP for linking external service providers.

If the external service provider can receive R/3 data, the data requirements are defined in table T77WWW_SDATA. There are two types of data requirements: I (Infotype): If the data is stored in SAP infotypes, you only have to specify the number of the infotype and the field name within this infotype.

F (Function module): R/3 data is not necessarily stored in infotypes. In this case a function module reads the data. SAP delivers function module ESS_NEW_HIRE_DATA_01, which can be used as a template for creating further function modules.

(C) SAP AG HR250 6-53

© SAP AG 1999

Customizing the Framework (VI): Color Codes

Tables for Setting the ColorsColor code definition: T77WWW_LECC

Color code description: T77WWW_LECCT

Color code assignment: T77WWW_LECCP

Table T77WWW_LECC is used to define individual color codes for the services within an event. These color codes represent the priorities and show which services are for example optional or required. The individual color codes are described sorted in increasing order of the unique ESS color ID. These codes are displayed in the Infobox below the event menu.

The color code descriptions are added in further languages in table T77WWW_LECCT. A new record is automatically created in table T77WWW_LECC by adding a new color code. The system uses the logon language as the country key.

The color codes are assigned to a certain service within an event in table T77WWW_LECCP.

(C) SAP AG HR250 6-54

© SAP AG 1999

Customizing the Framework (VII): Status Trace

Status Trace

The Status Trace function is optional. If the Status Trace function is active, a checkbox appears in front of each service in the menu. This function can be activated (value 'X') or deactivated (value " ") with parameter ~use_status in the service file (PZLE_01, PZLE_02, etc.) of the Life and Work Events. Do not change the PZLE service files. These files are integrated in all subordinate files and events. Changes to these service files would also affect all other services.

The status information for a service is stored in table T77WWW_LESTATUS. You can check the status information for a certain event with function module ESS_LE_STATUS_CHECK.

(C) SAP AG HR250 6-55

© SAP AG 2002

Creation of a Life and Work Event

Customize R/3 System as described in this unit

Create a new ITS service

Copy transaction in R/3 System

Add the Life and Work Event to the role in the Workplace system

Add the Life and Work Event to the usable single roles

SAP delivers service PZLE_01 (Life and Work Event 'My First Days @') from the template for creating further events. You can copy this service with SAP@Web Studio or with Transaction SE80. After copying, you should set service parameter ~ESS_LIFE_EVENT to the new menu key created in table T77WWW_MN (e.g. EM99). Make sure that the menu codes have the correct case and use uppercase when possible.

Since the Life and Work Events framework is not based on an existing R/3 transaction, you need to create a dummy transaction to link this service tot he mySAP Workplace. You can do this by copying transaction PZLE_01. Use transaction SE93 in the SAP HR System to make sure that the service name is identical to the transaction name.

After creating the transaction in the component system, you have to load the transaction information into the Workplace system. Use Transaction CS_WP_CACHE_RELOAD in the Workplace system to do this. This process can take a while if you are loading all the information from all linked component systems. You can reduce this time by selecting the following options: Logical system: Deactivate ALL and add the logical system that is used for the role.. Data transfer: Select Partial and load only the system and classification data.

Include the new transaction in the corresponding roles using the role maintenance transaction (PFCG).

(C) SAP AG HR250 6-56

© SAP AG 2002


Perform the necessary Customizing steps in the R/3 System to adapt SAP ESS to your company's requirements

Describe the SAP ESS country-specific settings

Describe how Workflow can be used within SAP ESS

Explain how to customize the Life and Work Events

Customizing SAP ESS: Unit Summary


© SAP AG 1999

Contents

General Design Changes for SAP ESS

Programming Models

Tools for Adapting the SAP ESS Services

Enhancing SAP ESS


© SAP AG 1999


Describe the programming models that are used in SAP ESS.

Explain how to change the appearance of SAP ESS.

Specify the tools for adapting the SAP ESS Services.

Enhancing SAP ESS: Unit Objectives


© SAP AG 1999

Enhancing SAP ESS

Course Overview


User Management


Summary

Customizing SAP ESS

SAP ESS Services




© SAP AG 1999

The Caliber a Bicycle Company wants to change the SAP ESS services to adapt them to internal company standards.

Enhancing SAP ESS: Business Scenario


© SAP AG 1999

What can be Changed?

Adapting Standard Services

Screen display for SAPGUI for HTML

Templates for SAPGUI for HTML

Field layout and flow logic

Visual design

The overall appearance as visualized by the end user with a browser is defined by the design elements of the mySAP Workplace on the one hand and the individual MiniApps and Internet Application Components on the other hand.

For your overall design to be successful you generally have to adapt the design of both the mySAP Workplace and the SAP Web applications. When doing, keep the following in mind: Different programming models are used when developing the mySAP Workplace, the MiniApps and the Internet Application Components. These programming models focus on the HTML generation.

The design is controlled by the Internet Transaction Server (ITS). Since there are usually multiple ITS involved in the overall architecture (one ITS for the mySAP Workplace system and one ITS for each component system), you generally have to change the design to suit multiple ITS.


© SAP AG 1999


WebBrowser

WebServer

Comp.SystemWGateWGate AGateAGateHTTPHTTP CGICGI TCP/IPTCP/IP

DIAGDIAG

RFCRFC

• Link: Web Server / Component System• Logging onto the component system• Data Receipt, Conversion to HTML• Status management




User Query Input

CSSFiles

ServiceFiles

HTMLTemplates

OutputHTML Page

ITS: Overview

The Web Server is linked with the component systems by the SAP Internet Transaction Server (ITS). The ITS is needed for the following tasks: Data exchange (for example by converting protocols) Logging onto the component system Transferring data to component systems, converting the output into HTML Status management

The ITS consists of two components: WGate is the interface to the Web server. WGate and the Web server must run on the same hardware. In addition to the CGI (Common Gateway Interface), SAP supports the external interfaces ISAPI (Microsoft) and SNAPI (Netscape). If you use the Microsoft IIS Web server, the WGate is stored as a DLL file in directory scripts.

Data is exchanged with the component system using the AGate. It can run either on the same hardware as the WGate (single host) or on a separate host (dual host). A number of files stored on the AGate configure the ITS. This includes: - Service files: Component system, logon data (client, user, password) - HTMLBusiness Templates: HTML with additional instructions, placeholder for screen fields - CSS files: Description of the optical design of the generated HTML pages


© SAP AG 2002

ITS: Programming Models (I)

Component SystemAGate (ITS)

Not Based on SAP Dialog

Based on SAP Dialog

Where is the transactionorder defined?

Development Tools:SAP@Web Studio and Web Application Builder

DisplayDisplay

Display

Dialog Transactionor Function Module

Status Status

Status

Flow Logic &Representation

<HTML><BODY>

Result:f1.value

Representation

Business Object

BAPIBAPI

BAPI

ITS supports two programming models. They differ in the location where the individual transaction flows are defined.

Flows for models that are based on SAP dialog are defined in the component system (normally in the dialog transaction). The ITS takes care of the visual representation. There is at least one template for each screen of the transaction in the AGate. HTML standard instructions are linked with HTMLBusiness instructions in these files. HTMLBusiness gives you access to all the screen fields and their features. HTMLBusiness also offers a wide spectrum of instructions for input fields, loops, conditions, arithmetic operations, etc.

In models that are not based on SAP dialog, the ITS controls the order of the transactions as well as the visual display. As in the above case, the display is defined by HTMLBusiness templates. The order is described in a separate layer called the ITS flow logic. The main features of this layer are the different statuses and the event-dependent transitions between these statuses. The specification uses flow logic files that are based on XML syntax.

Two tools are provided to help developers create or change Internet applications. SAP@Web Studio is an independent program. The functionality of the SAP@Web Studio includes various wizards that support developers.



© SAP AG 2002

ITS: Programming Models (II)



IACs

ITSFlow Logic

HTML Templates

HTML Functions

HTML Templates

Flow Files

HTML Functions

SAP GUIfor HTML

HTML Functions

R/3System

HRCRMBBP

...

Web Browser

Flow Logic in R/3 Flow Logic in the ITS

Each SAP Web application normally consists of multiple HTML pages. The layout of a single HTML page consists of various design elements (such as pushbuttons and fields), where there are the following types: Screen-based design elements are elements that are provided by an underlying screen of a transaction of the R/3 System.

Non-screen-based design elements are elements that are not provided by an underlying screen.

As with this page, the elements on which the layout of an HTML page are based depend on how the HTML is generated. You can proceed in the following ways: The HTML is generated automatically by the ITS. In this case the corresponding HTML page is based on a screen of a transaction of the R/3 System. The ITS converts the elements and layout of the screen into an HTML page at runtime.

The HTML is generated using templates. A template that is created manually can contain both screen-based and non-screen-based design elements.



© SAP AG 2002

SAPGUI for HTML: HTML Generation

System HelpSAP R/3

System HelpSAP R/3

R/3R/3 SystemSystem

Web Browser ITSHTTP

Server

Personnel no.: 1000

Personnel number: 1000Employee group: 1Employee subgroup: DS

......

200

100

HTTPHTTP

HTTPHTTP

CGICGI

CGICGI

DIAGDIAG

DIAGDIAG

One Screen =One HTML Page HTML

BusinessFunctions

ServiceFile

Automatic Conversion of DIAG to HTML

ABAP WorkbenchABAP Workbench

SAPGUI for HTML permits you to execute nearly every R/3 transaction in the Web browser. All the screen elements (and controls) are automatically converted into HTML pages.

The HTML is generated automatically by the ITS. In this case the corresponding HTML page is based on a screen of a transaction of the R/3 System. The ITS converts the elements and layout of the screen into an HTML page at runtime. The HTML layout you create nearly corresponds to the original screen layout. The screen-based HTMLBusiness functions generate the HTML for the relevant screen elements, taking the corresponding screen element attributes into consideration.

The contents of the HTML page solely depend on the definition of the R/3 screen it is based on. To change the screen display, you should use the ABAP Workbench in the R/3 System.

(C) SAP AG HR250 7-10

© SAP AG 2002

IAC: HTML Generation

(a) SAP@Web Studio(a) SAP@Web Studio(b) Web Application Builder(b) Web Application Builder

System HelpSAP R/3

System HelpSAP R/3

R/3R/3 SystemSystem

Web Browser ITSHTTP

Server200

100

HTTPHTTP

HTTPHTTP

CGICGI

CGICGI

DIAGDIAG

DIAGDIAG

One Screen =One Template =One HTML Page Service

File

HTMLBusinessTemplates

Conversion of DIAG into HTML with Templates

Personnel no.: 1000

Personnel number: 1000Employee group: 1Employee subgroup: DS

......

The HTML is generated using templates. A template that is created manually can contain both screen-based and non-screen-based design elements: You can access elements of an underlying screen with screen-based HTMLBusiness functions. With non-screen-based HTMLBusiness functions you can display design elements that cannot be provided by screen elements. When using a template, you are free to design the layout of the HTML page as you like, i.e. even if you use screen-based HTMLBusiness functions you are not dependent on an underlying screen layout.

Two tools are provided to help developers create or change IACs. SAP@Web Studio is an independent program. The functionality of the SAP@Web Studio includes various wizards that support developers.


(C) SAP AG HR250 7-11

© SAP AG 2002

ITS Flow Logic

R/3R/3 SystemSystem

Web Browser ITSHTTP

Server

HTTPHTTP

HTTPHTTP

CGICGI

CGICGI

RFCRFC

RFCRFC

One Template =One HTML Page

BAPIs and other(any) RFC-enabledfunction modules

ServiceFiles

HTMLBusinessTemplates

ITSFlowFiles

Dialog Logic and Templates on the ITS

(a) SAP@Web Studio(a) SAP@Web Studio(b) Web Application Builder(b) Web Application Builder

In models that are not based on SAP dialog, the ITS controls the order of the transactions as well as the visual display. The display is defined by HTMLBusiness templates. The order is described in a separate layer called the ITS flow logic. The main features of this layer are the different statuses and the event-dependent transitions between these statuses. The specification uses flow logic files that are based on XML syntax.

You can change the templates with the SAP@Web Studio or Web Application Builder.

(C) SAP AG HR250 7-12

© SAP AG 1999

Cascading Style Sheets

Style Sheet DesignerStyle Sheet Designer

Cascading Style Sheets

To change:

Font

Color

Images (Logo, Pictures, Graphics)

The actual design (colors, fonts, images, etc.) of the individual design elements is defined within the generated HTML page using Cascading Style Sheets (CSS).

Edit the Cascading Style Sheets (CSS) to change the font, color or image. Advantage: The coding normally does not have to be changed. Fonts and colors are defined with CSS classes and images (logos, pictures and graphics) are referenced with paths.

The easy-to-use Style Sheet Designer helps you to change the Style Sheets, enabling you to change the design in all applications of the mySAP Workplace and all SAP Web applications. The Style Sheet Designer offers you a set of attributes (such as font, color) based on the Style Sheet that can be changed for each design element. The changes are displayed (Preview) and the relevant Style Sheet is adapted automatically.

Changing the Cascading Style Sheets with the Style Sheet Designer offers you three advantages: The changes are made in all applications, i.e. you automatically ensure that the overall design of the mySAP Workplace and of all MiniApps and Internet Application Components is consistent

You make your changes in a copy of the delivered standard files and not in the originals. The files for your design can reside on any server. The standard design is not changed and your self-defined design is protected against overwriting in an ITS upgrade.

You can store multiple self-defined designs, whereby only one design at a time is used. The design changes are made with the Style Sheet Designer and the necessary directory structures are created manually.

(C) SAP AG HR250 7-13

© SAP AG 1999

Adapting the Optical Appearance

Copy the entire service to the customer namespace (Y* or Z*). Change templates.

If the templates work with CSS, you can make optical changes by changing the CSS file.

These changes affect all the services that use the CSS file.

The CSS file is a MIME object and is part of either the copied service or another service (also copy if necessary).

If the templates work with the SAP template library, you might have to change it too.

These changes affect all the services that use the SAP Template Library.

You can access the SAP Template Library with the template templateLibraryDHTML.html in theme pm of the service system.

(C) SAP AG HR250 7-14

© SAP AG 2002

Adapting the Flow Order

Internet Application Component

Screens and programs must be changed in the R/3 System

In some cases, templates also have to be changed

ITS Flow Logic

Changing specific flow files

In some cases, templates also have to be changed

If the changes are very large, you might have to change existing function modules or create new function modules in the R/3 System

(C) SAP AG HR250 7-15

© SAP AG 1999

You are now able to

Describe the programming models that are used in SAP ESS.

Explain how to change the appearance of SAP ESS.

Specify the tools for adapting the SAP ESS services.

Enhancing SAP ESS: Unit Summary


© SAP AG 1999

SAP ESS Implementation Guidelines

Sizing the SAP ESS Environment

Hardware and Software Requirements

Skills

Project Planning

Contents



© SAP AG 1999

Describe the various steps to consider when implementing SAP ESS

Determine the size of the SAP ESS environment

Determine the hardware and software requirements

Know which skills are necessary for SAP ESS

Set up a basic SAP ESS project plan


Planning and Implementation: Unit Objectives


© SAP AG 1999

Course Overview


SAP ESS Services

User Management

Enhancing SAP ESS

Summary


Customizing SAP ESS




© SAP AG 1999

Caliber A Bicycle needs an effective rollout strategy for implementing SAP ESS.

It is your responsibility to explain all of the factors that should be considered when creating the project plan.

Planning and Implementation: Enterprise Scenario


© SAP AG 2002

Overview: SAP ESS Implementation (1)

1 Size the ESS environment and order hardware

2

Install the Web server, ITS, and SAP@WebStudio

3

Install the mySAP Workplace Server

4

Determine which SAP ESS services you need5

6

7

8

Implement Central User Administration

Apply the necessary Support Packages

Publish the required services from R/3 System to the ITS

Inform the ESS users

9 Create test users

Before you begin planning your SAP ESS implementation, there is a quick guide of 15 steps you should take into consideration. The details on each of these steps are covered throughout this course and in the SAP ESS Implementation Guide.

Enabling employees to change their human resources information, and thus take ownership of their own data, means a shift in corporate culture. It is important to ensure that you take certain steps to inform, train and acclimatize your employees to the changes that lie before them.


© SAP AG 1999

Integrate SAP ESS into your company Intranet

10

Make changes to HTML templates if necessary

11

Create ESS users for the pilot users

12

Train the pilot users

13

Stress test the applications

14

Create the remaining ESS users

15

Start production

Test the applications

Perform additional customizing if necessary

16

17

18



© SAP AG 1999

General ConsiderationsIs it a single or dual host environment?

How many services will be enabled?

What is the maximum number of active users?

Additional Considerations Network configuration of the server components

Web server configuration

Sizing the SAP ESS Environment

The SAP ESS environment comprises one or more AGate and WGate servers.

A sizing table to determine the hardware requirements depending on the number of active users or hits per second is included in Sizing the ESS Environment in the SAP ESS Implementation Guide. This sizing information only applies to the Web environment, and not to the sizing of your R/3 environment.

Other considerations should include an examination of your network setup, as the network load between the ITS and the R/3 application server is basically the same as the network load between the SAPGUI and the R/3 application servers.


© SAP AG 1999

Services with Even Load

Services with Peak Load

Time Sheet

Expense Reports

e.g. Fridays after 1:00 p.m.

Address

Who's Who

e.g. The same all day

Sizing: SAP ESS Available Services

Users will execute transactions at different times, so you don't need to size your system for your total number of Employee Self-Service users. Instead, you should aim for the maximum number of users you expect to be on your system at any one point in time or during peak load phases.

Continuous load services have consistent requests during a given day. Applications that generate a continuous load on the system include the Address and Who's Who services.

Peak load services are used intensively at certain times and only sporadically at other times. For example, a peak load phase for Time Sheet would be Fridays between 1pm and 5pm.

Although there are no hard and fast rules to determine how many active users you may have, SAP recommends the following strategy. Keep in mind, however, that this is just one of many possible strategies and doesn't address the load on the R/3 environment generated by any additional SAPGUI users, batch jobs, reports, and so on. You should therefore examine this strategy and determine whether or not it meets your needs. In general, existing systems will experience a greater load when SAP ESS is used and therefore must be sized to cope this situation.


© SAP AG 1999

Example using the Cross Application Time Sheet (CATS)

15 min

1000 per week4 hrs (240 min)

63 = 1000/240 *15

Active users = Number of transactions/Time frame (min) * Average transaction time (min)

SAP ESS services that generate a loadPeak load

Number of transactions

Time frames

Estimated average transaction time

Number of active users

Sizing: Determining the Number of Active Users

The steps for calculating the number of active users are:

List all the ESS services from which you expect continuous or peak load.

Determine the average number of transactions per week (for continuous load) or crunch period (for peak loads) for each individual service.

Determine the time frame for simultaneously performing the transactions you just determined.

Estimate the average time it will take to perform a transactions.

Apply the values to the following formula: Active users=Number of transactions/Time frame (min) * Average transaction time (min)

Add the number of active users for each service to get the total number of active users that are required for SAP ESS.

The SAP ESS Implementation Guide contains a sizing table.

(C) SAP AG HR250 8-10

© SAP AG 2002

Sizing: Other Factors

Other factors that can affect the system load include:

ITS size

R/3 System sizing for the number of users

Network

Web server configuration

In general, SAP recommends using high-speed (100-megabit) links between the server components. You might also want to consider using a separate subnet between the Web server(s) and ITS server(s) to maximize throughput.

If you use Netscape Enterprise Server, configure the NSAPI extension rather than the CGI version. You should also set Maximum Simultaneous Requests within the Netscape Server Administration tool to at least the maximum number of active users. For more information on Web server settings, contact your Web server manufacturer.

If you use Microsoft IIS 4.0 and are running two instances of the ITS (one for administration, one for the applications), make sure that the IIS instance for the applications is running in-process whereas the administration instance is running out-of-process.

(C) SAP AG HR250 8-11

© SAP AG 1999

Pentium-compatibleprocessor

Backup system(optional)

ISO 9660-conformCD ROM

≥ 2 x min. 1 GBmirrored

per hard disk

RAM≥ 128 MB

HardwareWeb browser:

Microsoft Internet Explorer 5.0(Netscape Navigator 6.0)

Web server:Netscape Enterprise Server

Microsoft InternetInformation Server (IIS)

Operating system:Windows 2000 or NT 4.0,

NTFS file system,TCP/IP network,Virtual memory

Other software:SAP GUI

Software Skills

Installation,configuration

and administrationof ITS and

Web servers

Basic knowledge ofSAP@WebStudio

ITS Requirements

The ITS hardware requirements for the ITS depend on the type of environment you are implementing. The requirements for the processor and backup mechanism are the same for both a development or test system with a single host installation and a production environment with a dual host installation. However, the hard disk and memory sizes only need to be half as large for the test and development systems.

Additional hardware will be required to accommodate the system load if you are using HTTPS.

Additional software could include a SAPGU (for support purposes) and Microsoft Excel (for offline expense reporting purposes).

To install the required services, you need to be familiar with the installation, configuration and administration of ITS and Web servers as well as with the SAP@Web Studio. Additional training for the ITS is available in the BC440 Developing Internet Application Components and the BC350 ITS Administration courses.

SAP ESS can create considerable load on your R/3 system. You should therefore check the sizing of your R/3 environment and keep in mind that the number of ESS users you determine will be in addition to the number of existing standard R/3 users. For information about sizing the R/3 environment, see the Quicksizer (OSS note 0085524).

(C) SAP AG HR250 8-12

© SAP AG 1999

Pentium-compatibleprocessor

Backup system(optional)

ISO 9660-conformCD ROM

≥ 1 GBmirrored

per hard disk

≥ 64 MB RAM

Operating system:Windows 2000Windows NT

Web browser:Microsoft Internet Explorer 5.0

(for test purposes)

Virtual memoryset according to

Microsoft guidelines

NTFS file system

TCP/IP network

Install and use the

SAP@WebStudio

Manageservice-related

objects that are external to the

R/3 System

Publish files onthe ITS and use source control

in theR/3 System

HTML skills

Hardware Software Skills

SAP@Web Studio Requirements

You can obtain SAP@Web Studio skills in the BC440 Developing Internet Application Components and the BC350 ITS Administration courses or in the SAP@Web Studio documentation.

HTML skills include how to design templates in standard HTML and HTMLBusiness and a basic understanding of the HTMLBusiness functions.

(C) SAP AG HR250 8-13

© SAP AG 2002

R/3 System Requirements

QuicksizerR/3 System customized

configuredR/3 System applications

Depending on thetype of SAP ESS

installation

Hardware Software Skills

For information on R/3 System hardware requirements see the Quicksizer (OSS note 0085524).

SAP ESS is an additional, simplified user interface for existing R/3 applications. In most cases, once you have configured the relevant R/3 applications, no extra SAP ESS-specific customizing is required. A complete list of SAP ESS services and the corresponding R/3 applications is available in the unit Getting Started in the SAP ESS Installation Guide.

The R/3 skills you need in order to set up SAP ESS depend on your installation:

If you are setting up an application for SAP ESS use for the first time, you need a specialist for that particular application who can customize it in R/3 and then ensure that the settings for SAP ESS are correct.

If you want to make an existing R/3 application available for SAP ESS, you need an HR customizing generalist who understands the application as well as the implications of SAP ESS for your existing R/3 configuration.

(C) SAP AG HR250 8-14

© SAP AG 1999

Web browser:Microsoft IE 5.0

Operating system:Windows 95, 98,

NT or 2000

Workplace Server:SAP Basis System 4.6D

with Workplace 2.1

Workplace Middleware:Windows NT 4.0Windows 2000

No restrictions

Frontend WorkplaceComponent

Systems (R/3)

Requirements: mySAP Workplace

The end user only needs access to the Web browser and the ability to use the browser.

(C) SAP AG HR250 8-15

© SAP AG 1999

Project Phases

Phase 1: Project preparation

Phase 2: Business blueprint

Phase 3: Realization

Phase 4: Final preparation

Phase 5: Go live and support

Phase 6: Continuous optimization

Project Plan

The project plan was developed using the AcceleratedSAP (ASAP) method. It outlines steps to be taken when you implement SAP ESS in your company.

During the project preparation phase you create the project plan and define the project procedure. It ends with the project kick-off.

The business blueprint phase involves training the project team, developing an Intranet concept, determining the Web design and defining hardware and software requirements for the development, test and production environments.

The realization phase involves project execution: implementing the development and test systems, authorizing users, customizing the R/3 System, testing the SAP ESS services, implementing the production system, transporting objects between the different environments, integration in the existing Intranet, testing the production system and releasing the new system.

The final preparation phase involves informing your employees about upcoming changes and the training the support team.

In the go live and support phase, the system is used for production for the first time and support begins.

In the continuous optimization phase, the system is subject to continuous evaluation and optimization.

(C) SAP AG HR250 8-16

© SAP AG 1999

Start a pilot project and implement it in phases

Inform the employees

Set up a group of "power users"

Assign passwords

Set up a feedback channel

Train the participants

Create additional documentation

Define realistic deadlines

Project Notes: "Golden Rules"

By running a pilot project before actually implementing SAP ESS you can identify possible problems before they happen on a large scale. Make sure that your sample is not too small, as this should be a realistic test. Make sure that your pilot users are distributed throughout the entire company. This permits you to make them key users for the various departments later on.

An effective information policy means that employees are informed about SAP ESS long before rollout.

Your superusers should be available as soon as you implement SAP ESS. The superusers serve as experts for a group of ordinary users, making their expertise available to others and taking a load off your project team/HR department.

When you initially assign passwords, make sure that your employees know that they must keep their logon and password in a safe place. Then you will not have to reassign forgotten passwords.

It is especially important that your employees can provide you with feedback. Try to bundle the feedback using the superusers.

While SAP ESS is simple and intuitive to use, some of your employees may feel they still need training. Try to involve your superusers in providing training for their target groups.

Provide additional documentation that meets the needs of your company.

Make sure that SAP ESS is not implemented during peak periods, such as Benefits Open Enrollment.

(C) SAP AG HR250 8-17

© SAP AG 2002

You are now able to

Describe the various steps to consider when implementing SAP ESS

Determine the size of the SAP ESS environment

Determine the hardware and software requirements

Know which skills are necessary for SAP ESS

Set up a basic SAP ESS project plan

Planning and Implementation: Unit Summary

(C) SAP AG HR250 8-18

Planning and Implementation Exercises

(C) SAP AG HR250 8-19

(C) SAP AG HR250 8-20

Unit: Planning and Implementation Topic: Planning and Implementation


• List the various steps to consider when implementing SAP ESS

• Define the steps necessary to determine the number of active SAP ESS users

• Determine the number of active users necessary for an SAP ESS service

The Caliber A Bicycle Company has asked you to determine the number of active users they will need to implement SAP ESS at their company. You should provide guidelines for determining this number.

They have also asked you to provide some general implementation guidelines.

1-1 List the items to consider when implementing SAP ESS.

1. __________________________________________________

2. __________________________________________________

3. __________________________________________________

4. __________________________________________________

5. __________________________________________________

6. __________________________________________________

7. __________________________________________________

8. __________________________________________________

9. __________________________________________________

10. __________________________________________________

11. __________________________________________________

12. __________________________________________________

(C) SAP AG HR250 8-21

13. __________________________________________________

(C) SAP AG HR250 8-22

14. __________________________________________________

15. __________________________________________________

16. __________________________________________________

17. __________________________________________________

18. __________________________________________________

1-2 Determine the number of SAP ESS users necessary for a continuous load on the Who’s Who service if 10,000 transactions are executed daily with an average transaction time of 2 minutes.

Load type: ________________________________

Number of transactions: ________________________________

Time frame: ________________________________

Average transaction time: ________________________________

1-3 Evaluate the following statements with True or False

1-3-1 To determine the number of active users for SAP ESS, you must add the user numbers for the individual services.

___________________________________________________

1-3-2 The Cross Application Time Sheet (CATS) is primarily a peak load application. ___________________________________________________

1-3-3 The sizing of the R/3 System is not relevant when sizing the SAP ESS environment. ___________________________________________________

1-3-4 When you implement SAP ESS, you have to take certain hardware, software and skills requirements into consideration.

___________________________________________________

1-3-5 The project plan does not have to consider the realization phase.

___________________________________________________

(C) SAP AG HR250 8-23

Planning and ImplementationSolutions

(C) SAP AG HR250 8-24

(C) SAP AG HR250 8-25

Unit: Planning and Implementation Topic: Planning and Implementation

1-1 List the items to consider when implementing SAP ESS.

1. Size the ESS environment and order hardware

2. Install the mySAP Workplace Server

3. Implement Central User Administration

4. Install the Web server, ITS and SAP@WebStudio

5. Determine which SAP ESS services you need

6. Apply the necessary Support Packages

7. Publish the required services from R/3 to the ITS

8. Inform the ESS users

9. Create test users

10. Test the applications

11. Perform additional customizing if necessary

12. Integrate SAP ESS into your company Intranet

13. Make changes to HTML templates if necessary

14. Create ESS users for the pilot users

15. Train the pilot users

16. Stress test the applications

17. Create the remaining ESS users

18. Start production

(C) SAP AG HR250 8-26

1-2 Determine the number of SAP ESS users necessary for a continuous load on the Who’s Who service if 10,000 transactions are executed daily with an average transaction time of 2 minutes. 42 active users

Load type: Continuous load

Number of transactions: 10.000

Time frame: 480 minutes (for continuous load the time frame corresponds to a workday of 8 hours, which is equivalent to 480 minutes)

Average transaction time: 2 minutes Formula: Active users = Number of transactions/Time frame (min)

* Average transaction time (min)

Active users = 10000/480 * 2 = 41.67 – rounded up to 42

1-3 Evaluate the following statements with True or False

1-3-1 To determine the number of active users for SAP ESS, you must add the user numbers for the individual services. True

1-3-2 The Cross Application Time Sheet (CATS) is primarily a peak load application. True

1-3-3 The sizing of the R/3 System is not relevant when sizing the SAP ESS environment. False, you must consider the size of the R/3 System.

1-3-4 The requirements to consider include hardware, software and skills. True 1-3-5 The project plan does not have to consider the realization phase. False, the six

phases of the project plan are project preparation, the business blueprint, realization, final preparation, go live & support and continuous optimization.


© SAP AG 1999

Review

Wrap-up

Contents

Conclusion


© SAP AG 2002


Course Objectives


Explain and use the SAP ESS services

Describe and perform the steps necessary to customize SAP ESS

Describe the mySAP Workplace and the Employee Self-Service role

Maintain SAP ESS users

Explain the necessary steps for a successful SAP ESS implementation

Describe the technical infrastructure of the mySAP Workplace and SAP ESS


© SAP AG 1999

Course Overview


SAP ESS Services

User Management


Summary

Enhancing SAP ESS

Customizing SAP ESS




© SAP AG 2002

What is SAP Employee Self-Service?

SAP Employee Self-Service (SAP ESS) includes a number of easy-to-use Web applications with which every employee in an enterprise can create, display, and maintain data in the R/3 System using a browser.SAP ESS offers transactions for:

OfficeWorking TimeBusiness TripsBenefitsJobsPaymentPersonal InformationTrainingSkillsAppraisalsLife and Work Events

SAP ESS is an efficient means of accessing data in realtime and maintaining this data. It permits the off-load of data entry activities and related tasks that are typically performed in a company's human resources, payroll, benefits and travel departments.

SAP Employee Self-Service (SAP ESS) empowers employees to view, create, and maintain data any time, anywhere through their Web browser.

SAP ESS has an intuitive user interface and is therefore ideal for casual users.

SAP ESS provides a number of services for a variety of areas.

The ESS development is currently working on Life and Work Events, in which the application and information are combined in a way that supports employees in their decisions.


© SAP AG 1999

DesktopDesktop BackendBackendSystemsSystems

Workplace MiddlewareWorkplace Middleware

R/3 APO

BW KW

BBP CRM

Examples:

Web Server ITS

Web Browser

Web server ITS WP

Web server

Web server

ITS 1

ITS n

WorkplaceServer

Comp.System 1

Comp.system n

Workplace Architecture

The Workplace architecture has three layers. To access the Workplace the user only needs a Web browser on his desktop. The Web browser uses a Web server belonging to the Workplace middleware for communications. Another important element is the SAP Internet Transaction Server (ITS), which connects the Web server with the backend systems.

A number of backend systems can be linked with the Workplace. One of the most important backend systems is the Workplace Server, which is used to handle the role specifications and central user administration if implemented. The other systems (such as R/3, APO, BW, KW, BBP, CRM) are called component systems.

Recommendation: When using SAP ESS you should install a physical ITS for the Workplace Server and for each component system (such as HR, BBP).


© SAP AG 1999

KW

LO

FI


SAP_ESSUSER

SAP_FI_EMPLOYEE

SAP_LO_EMPLOYEESAP_FI_TV_TRAVELLER

SAP_BC_ENDUSER

SAP_WPS_EMPLOYEESAP_WPS_EMPLOYEE

SAP_WPS_USERSAP_WPS_USER

SAP_KM_KW_ALL_AREAS_DISP_EMPL

SAP_HR_EMPLOYEE_XX

Workplace ServerWorkplace Server HR

WorkplaceWorkplace ServerServerComposite role

Single roles

BBP

SAP_EC_BBP_EMPLOYEE

SAP_BC_EMPLOYEE

The Employee Self-Service Composite Role

The Employee Self-Service composite role replaces the navigation menu used in Releases 4.5 and 4.6B, which now can be found in the role in the mySAP Workplace LaunchPad.

The composite role Employee Self-Service (SAP_WP_EMPLOYEE) is delivered by SAP. It resides on the mySAP Workplace system and contains all the international and country-specific single roles (transactions, authorizations) provided for Employee Self-Service.

The single roles always reside in the relevant component systems with the exception of the single roles SAP_WPS_EMPLOYEE and SAP_WPS_USER, which contain the MiniApps and basic authorizations for the Workplace system and therefore reside in the Workplace system. The single role SAP_BC_ENDUSER contains the basic authorizations for the component systems and therefore must exist in all the component systems (HR, LO, FI...).

Although you can use any role to install SAP ESS authorizations, SAP strongly recommends that you use a copy of SAP_WP_EMPLOYEE. Copy the composite role to your customer namespace (Z* or 9*). Then, if necessary, you can adapt it to include transactions that are relevant to your company.

You can find a detailed description of the single roles in the SAP Employee Self-Service Release 4.6C Implementation Guide


© SAP AG 2002

Select the employees who will use SAP ESS (component system)

Employees are authorizedfor SAP ESS

Copy composite role (SAP_WP_EMPLOYEE) to the customer namespace (Workplace Server)

New user attributes

2

3

3b3a

1

4bCopy user attributes4a

SAP ESS User Installation Process

Employees with SAP R/3 system users

Employees without SAP R/3 system users

To install users, you must first copy composite role SAP_WP_EMPLOYEE, containing the single roles and system authorizations needed for SAP ESS, to the customer namespace on theWorkplace Server.

You must then decide which employees you intend to enable for SAP ESS (component system).

There are two groups:

Employees with existing SAP users who are not yet authorized to use SAP ESS. For these employees you must:

- Establish a link between the master records and the existing SAP users


Employees who do not have SAP users. For these employees you must:

- Create SAP users


For new users, you can define how your employees can log onto SAP ESS in the User Attributes

SAP provides a tool to guide you through the installation. The tool is available using the transaction HRUSER.


© SAP AG 1999

General IMG Settings

Applications-Specific IMG Settings

Country-Specific IMG Settings


Overview: Customizing SAP ESS


© SAP AG 2002

ITS: Programming Models



IACs

ITSFlow Logic

HTML Templates

HTML Functions

HTML Templates

Flow Files

HTML Functions

SAP GUIfor HTML

HTML Functions

R/3System

HRCRMBBP

...

Web Browser

Flow Logic in R/3 System Flow Logic in the ITS

SAP ESS is based on Internet Application Components (IACs). It has a three-step procedure: SAP GUI for HTML - a one-to-one mapping of the R/3 screens. The SAP GUI for HTML provides a dynamic emulation of the R/3 dialogs in a Web browser. This mapping is implemented by HTMLBusiness functions (one for each screen element), which either reside in the ITS kernel or are called from those functions.

Internet Application Components (IAC) SAP ITS Flow Logic - BAPIs and Function Modules

A web-enabled transaction should have the following characteristics: It uses only "simple" screens that can be easily converted into HTML. It can be synchronized by the ITS. It uses a special technique to provide users with input help in HTML forms. It permits users to log onto the Internet while the transaction is being processed.


(C) SAP AG HR250 9-10

© SAP AG 2002


1 Size the ESS environment and order hardware

2

Install the Web server, ITS, and SAP@WebStudio

3

Install the mySAP Workplace Server

4

Determine which SAP ESS services you need5

6

7

8

Implement Central User Administration

Apply the necessary Support Packages

Publish the required services from the R/3 System to the ITS

Inform the ESS users

9 Create test users

Before you begin planning your SAP ESS implementation, there is a quick guide of 15 steps you should take into consideration. The details on each of these steps are covered throughout this course and in the SAP ESS Implementation Guide.

Enabling employees to change their human resources information, and thus take ownership of their own data, means a shift in corporate culture. It is important to ensure that you take certain steps to inform, train and acclimatize your employees to the changes that lie before them.

(C) SAP AG HR250 9-11

© SAP AG 1999

Integrate SAP ESS into your company Intranet

10

Make changes to HTML templates if necessary

11

Create ESS users for the pilot users

12

Train the pilot users

13

Stress test the applications

14

Create the remaining ESS users

15

Start production

Test the applications

Perform additional customizing if necessary

16

17

18


(C) SAP AG HR250 10-1

© SAP AG 2002

Appendix: Enterprise Portal 5.0

This appendix briefly introduces the changes to expect when converting to Enterprise Portal 5.0 (EP5.0).

(C) SAP AG HR250 10-2

© SAP AG 2002

Enterprise Portal "Look and Feel"

ESS Services in the Enterprise Portal

Enterprise Portal Architecture and Technical Changes

Demo in EP5.0

Changes in Conversion from WP2.11 to EP5.0

Contents

The appendix addresses four main questions regarding conversion to EP 5.0: What differences are there in the usage of EP5.0 compared with WP2.11? What do ESS scenarios look like in EP5.0 and how are they included? What changes need to be made to the architecture and technical infrastructure? What does EP5.0 and its services look like?

(C) SAP AG HR250 10-3

© SAP AG 2002




Demo in EP5.0


Look and Feel (1)

The appendix addresses four main questions regarding conversion to EP 5.0: What differences are there in the usage of EP5.0 compared with WP2.11? What do the ESS scenarios look like in EP5.0 and, how are they included? What changes need to be made to the architecture and technical infrastructure? What does EP5.0 and its services look like?

(C) SAP AG HR250 10-4

© SAP AG 2002

Layout

Top-level navigation

iViews

Detail navigation or iPanel

The layout of the Enterprise Portal is composed of two main elements: Navigation area Work area

The navigation area is divided into a top-level navigation area, in the first two rows, and a detail navigation area called the iPanel, which can be found on the left of the screen.

The work area can include different iViews or be composed of just one iView. An iView is the smallest unit. You can define information that is to be displayed for each iView. An administrator can display the iViews as shown in the above example.

(C) SAP AG HR250 10-5

© SAP AG 2002

iPanel for Detail Navigation

Top-level navigation offers two levels. In this example, the first level is My Page and the second is Private.

If you need additional navigation options you can also use the iPanel. Additional selection options can be found in the category Private. A single mouse click in the iPanel enables you to load iViews in the work area.

(C) SAP AG HR250 10-6

© SAP AG 2002

Personalizing Layout and Design

Layout and DesignAdministrators determine how ESS users can personalize the pages displayed.Using a pre-defined profile, the entire portalcan be tailored to suit the corporate identityof an enterprise.

Changes to Layout and DesignBased on style sheetsColors and graphics can be included

Tool SupportVisual style sheet editorStandard Web-design tools

At the push of a button, ESS users can compile their own layout of pages and change the design of the entire portal.

Administrators can release the settings for layout and design enabling them to be used by the user group ESS User, or lock them.

(C) SAP AG HR250 10-7

© SAP AG 2002




Demo in EP5.0


Look and Feel (2)

The appendix addresses four main questions regarding conversion to EP 5.0: What differences are there in the usage of EP5.0 compared with WP2.11? What do the ESS scenarios look like in EP5.0 and how are they included? What changes need to be made to the architecture and technical infrastructure? What does EP5.0 and its services look like?

(C) SAP AG HR250 10-8

© SAP AG 2002

ESS in Enterprise Portal 5.0

SAP ESS services are:Transferred with all their functions to the Enterprise Portal. Tailored to suit the design of EP5.0.

The following ESS releases are available for EP5.0:Business Packages:

SAP ESS 4.6BSAP ESS 4.6C

No changes have been made to the service functions and they are still executed via the ITS. The HTML output from the ITS is displayed in the portal.

The design of services has been tailored to suit EP5.0. ESS services are included in business packages. Business packages are available for the current releases (4.6B, 4.6C, and later also 4.7) of the connected component system.

You can download business packages from the SAP Service Portal and import them to EP5.0. Service customizing remains unchanged in the component system.

(C) SAP AG HR250 10-9

© SAP AG 2002

ESS in SAP R/3 4.6C in Enterprise Portal 5.0

The above slide shows as an example Change Address Data from business package SAP ESS 4.6C. The layout and the functions of the service remain unchanged. Only the appearance of the services has been tailored to suit EP5.0.

Here you can see the selected navigation path highlighted in red. Top-level: Home and Self-Service. In the detail navigation area, Address was selected.

(C) SAP AG HR250 10-10

© SAP AG 2002

ESS in SAP R/3 4.6B in Enterprise Portal 5.0

Here you can see the same service for R/3 release 4.6B. The appropriate business package (SAP ESS 4.6B) was selected.

(C) SAP AG HR250 10-11

© SAP AG 2002




Demo in EP5.0


Look and Feel (3)


(C) SAP AG HR250 10-12

© SAP AG 2002

SAP WorldInternet Technology

Roles and User Administration

in WP

System Landscape with Workplace 2.11

Web Server

BWBWBWITS

ITS

ITS

ITS

KWKW

ITS

ITS

CRMCRM

IITTSS

BWR/3

System(HR)

R/3System

(HR)WP2.11WP2.11

ITS

ITS

BrowserBrowser

BrowserBrowser

BrowserBrowser

BrowserBrowser

NetNet

© SAP AG 2002

This slide shows the initial status of WP2.11 with which you are familiar from this course. WP2.11 uses its own individual ITS instance to communicate with a normal Web server. As we have seen in this course, the Workplace (WP) is responsible for role and user administration. It also creates connections to the component systems.

The implementation of EP5.0 changes the initial situation.

(C) SAP AG HR250 10-13

© SAP AG 2002© SAP AG 2002

SAP WorldInternet TechnologyWP.2.11 - EP5.0:- ITS remains in the backend- Services remain the same- Roles migrated - Users transferred from the

R/3 System

WP2.11WP2.11

ITS

ITS

BrowserBrowser

BrowserBrowser

BrowserBrowser

BrowserBrowser

System Landscape with Enterprise Portal 5.0

NetNet

Migration

Web Server

ITS

ITS

KWKW

BW

IITTSS

BWR/3

Enterprise(HR)

Basis 6.20

R/3Enterprise

(HR)Basis 6.20

EP5.0EP5.0

Page Builder

Page Builder

LDAP Dir.

Manage:- Uses- Roles

BWBWITS

ITS

CRMCRMITS

ITS

In the Enterprise Portal (EP), the EP5.0 server replaces the WP2.11 server. You no longer need an individual ITS instance for the Workplace (WP). This is replaced in the Enterprise Portal by the built-in page builder. However, the ITS is still needed to communicate with back-end systems. The ITS will not be replaced completely. Similarly to WP2.11, EP5.0 connects itself to the component system's ITS and displays in the browser the HTML pages formatted there.

The EP takes on the functions of the Workplace. Therefore, users and roles are administrated in the EP. A new component exists, namely the Directory Server. This component is not SAP-specific. You can use an existing directory server. This directory server is accessed via the usual, non SAP-specific LDAP log (LDAP = Lightweight Directory Access Protocol), and saves user data (user administration) and roles (role administration) together with their user assignment.

You can use a migration tool to transfer users and roles from the WP server to the directory server. The transfer process is displayed on the following two slides.

(C) SAP AG HR250 10-14

© SAP AG 2002

Role Migration: R/3 to Enterprise Portal

You can import roles from an existing R/3 system. This is performed as a one-off migration process to transfer data from the WP server to the Enterprise Portal server.

The menu structure and user allocation for the role is transferred and displayed appropriately in the EP. If you are using a business package for ESS, these menu structures are already included and you therefore do not need to import them. This tool only allows you to migrate existing roles to the WP server.

However, you can also create your own menu structures in the EP, independent of the R/3 system, or adapt the menu structures contained in the business package. These are called worksets.

If you want to migrate roles, we recommend you have Basis release 6.20 or higher.

(C) SAP AG HR250 10-15

© SAP AG 2002

User Migration: R/3 to Enterprise Portal

You can transfer users from an R/3 system to the Enterprise Portal. This is done by transferring the R/3 users to the directory server. The directory server is also referred to as the LDAP server because it uses the LDAP = Lightweight Directory Access Protocol.

In addition, you can use Central User Administration for R/3 systems. Central User Administration (ZBV) is used to reconcile the directory server. If you want to migrate users, we recommend you have Basis release 6.20 or higher.

(C) SAP AG HR250 10-16

© SAP AG 2002

Port

al C

onte

nt D

irec

tory

(LD

AP)

for R

oles

Unification

Session Mgmt

iView Server

User Management Personalization

Branding

PortalDir.

Cooperate Directory (LDAP) for Users

SSO

Technical Integration

SAP R/3 and other ABAP-based applications (such as CRM)

ITS

SAP GUIfor HTML

HTMLBMiniApp

Page Builder Interactivity and App. IntegrationInformation Access

InternetContent

JavaConnector

Browser ITS-based services in EP5.0

On closer inspection, you can recognize other details that have changed in EP5.0. MiniApps have been replaced by iViews. They are programmed using Java and are executed on the iView server.

In addition to using the ITS, you can also use a Java connector to connect to the R/3 System and read data.

The page builder compiles the pages and sends them to the Web server as a single HTML page. This improves system performance.

Roles and users can be saved in two directory services. The allocation of role to user is saved in a third directory service, namely the Portal Directory. Roles are stored in the Portal Content Directory whereas users are stored in the Cooperate Directory. There is no reason why you cannot save all three in the same place. The Portal Content Directory (PCD) contains roles, worksets, and personalization settings.

The Cooperate Directory contains EP users and user groups. Here you can use an existing user directory (must be LDAP-enabled).

The Portal Directory is used to save user assignments to roles. User mapping (R/3 user <> EP user) can be stored here.

The ITS remains an integral part of the ESS-service architecture.

(C) SAP AG HR250 10-17

© SAP AG 2002




Demo in EP5.0


Look and Feel (4)


(C) SAP AG HR250 10-18

© SAP AG 2002

ESS Demo in Enterprise Portal 5.0

Additional Information and Demo LandscapeInformation about the mySAP Enterprise Portal solution

http:// www.sap.com/ep

Information for customers and partners on the SAP Service Marketplace

http://service.sap.com/ep

Documentation in the SAP Help Portal (under Cross-Industry Solutions)

http://help.sap.com

Business packages and offers for developers and content partners

http://www.iViewStudio.com

Course offering for the mySAP Enterprise Portal solution http://www.sap.com/education

You can download business packages for ESS in the Enterprise Portal under http://www.iviewstudio.com.

You can find information on the Enterprise Portal for customers and partners on our Service Marketplace under http://service.sap.com/ep.

You can find information that is accessible to all under http://www.sap.com/ep. You can access the complete documentation for Enterprise Portal under http://help.sap.com. You can download the business packages for ESS using the URL http://www.iViewStudio.com. You can find our course offering as usual under http://www.sap.com/education. Here you can find our further training offering for the Enterprise Portal.

(C) SAP AG HR250 10-19

© SAP AG 2002

Questions

Any questions?

Thanks for your attention!

(C) SAP AG HR250 10-20

Enterprise Portal 5.0: Exercise

Optional Demo / Exercise Enterprise Portal 5.0

In this demo / exercise you will see:

• The “look and feel” of Enterprise Portal 5.0

• The navigation and personalization options in EP5.0

• The ESS services in EP5.0

Familiarize yourself with EP5.0. Experiment with the navigation options in EP5.0 and start an ESS service of your choice.

Log on to an IDES Portal Server. Your instructor will provide you with the necessary logon data.

1. Log on to the portal

Start your Internet browser. To log on to the Portal Server, enter the URL provided by your instructor. Enter in the dialog window the user and password data given to you by your instructor. Choose Confirm. You are now logged on to EP5.0. Your user name is displayed in the top right corner of the browser. The start page is displayed.

2. Personalize EP5.0

In the top right corner, immediately below your user ID, two links are displayed behind the heading Personalize. Choose the Portal link. Here you can determine the language and the design of the portal. Choose language English, and press Apply. Choose the design you want for the portal, and press Apply. The language and design you have chosen are now displayed. (Usually, the link Page is locked by an administrator).

(C) SAP AG HR250 10-21

3. Navigate in EP5.0

Click on Home in the top-level navigation area to return to the start page. In the top-level navigation area, choose Home and then Employee Self-Service to navigate in EP5.0. (The Business Package for ESS generates this entry automatically). A similar view is displayed to that with which you are already familiar from the Workplace (WP). Links in the detail navigation area, iPanel, display your services. iViews are used as opposed to MiniApps.

4. Start the service Change Address Data

Under the category Personal Information, choose the Address service. The service is displayed in the work area to the right of the screen. The service is the same as in the WP. The address data for your user is displayed. Choose any additional services. You will notice that the services are very similar to those of WP2.11.

(C) SAP AG HR250 11-1

© SAP AG 1999

Contents

Training Courses in the SAP ESS Environment

Further Sources of Information

Appendix

(C) SAP AG HR250 11-2

© SAP AG 1999

Workplace

MY301: mySAP Workplace

BC350: Technical Core Competence: Workplace

Internet Transaction Server

ITS050: ITS Foundation

ITS070: ITS Administration

ITS100: Developing Easy Web Transactions

ITS110: Developing Web Scenarios and MiniApps with ITS Flow Logic

ITS150: Corporate Identity Design

Authorizations

CA940: SAP Authorization Concept

HR307: Configuration of HR Systems Control

Training Courses in the SAP ESS Environment (I)

(C) SAP AG HR250 11-3

© SAP AG 1999

Training Courses in the SAP ESS Environment (II)

Workflow

BC600: SAP Business Workflow - Introduction

BC601: SAP Business Workflow - Definition and Use

Application Customizing

CA500: Cross Application Time Sheet (CATS)

HR305: Configuration of Master Data

HR306: Configuration of Time Recording

HR315: Recruitment

HR505: Organizational Management

HR510: Personnel Development

HR515: Event Management

HR580: Reporting in HR

AC270: Travel Management - Travel Expenses

AC275: Travel Management - Travel Planning

(C) SAP AG HR250 11-4

© SAP AG 1999

Further Sources of Information (I)

Online documentation

IMG documentation

Release information

SAP Employee Self-Service Release 4.6C Implementation Guide (SAP Material No.: 50041350 / ISBN 1-893570-97-5)

SAP ESS Newsletter

http://www.sap.com/ess SAP DesignGuild

http://www.sapdesignguild.org"Authorizations Made Easy"

Download from www.saplabs.com/auth

(C) SAP AG HR250 11-5

© SAP AG 1999

SAP Service Marketplace

Aliases

esssap-itssizinginternetadviser

Further Sources of Information (II)

(C) SAP AG HR250 11-6

© SAP AG 1999


Notes

Workplace

See components whose name begins with "WP"183914 (Release Strategy for the Workplace Server)193991 (Delivery of the Workplace 2.0)183998 (Workplace: Installation, Correction Software, Release Upgrade)215609 (Workplace Plug-In: Overview)178788 (SAP GUI for HTML)146505 (SAP GUI for Java)

Further Sources of Information (III)

(C) SAP AG HR250 11-7

© SAP AG 1999


Notes

RolesSee component BC-CCM-USR-PFC93769 (Documentation for Role Maintenance)

Central User AdministrationSee components whose name begins with "BC-CCM-USR"

159885 (Collective Note about Central User Administration)

161347 (Tables of the Central User Administration)

197728 (Complete Deletion of the CUA)

Further Sources of Information (IV)

(C) SAP AG HR250 11-8

© SAP AG 1999

SAP Employee Self-ServiceSee component CA-ESShttp://service.sap.com/essR/3 Security Guide (OSS Note 0039267)Quicksizer (OSS Note 0085524)

ITS and SAP@Web Studiohttp://www.saplabs.com/its (includes software downloads)SAP@Web Installation Guide (Material No. 51007160)R/3 Online DocumentationBasis Components -> Frontend Services (BC-FES) -> ITS/Web Server (BC-FES-ITS)

Further Sources of Information (V)

Documents

HR250 SAP Employee Self-Service HR250 · 2019. 4. 18. · ©SAP AG 1999 Target Group zAudience: HR and Intranet project team members responsible for implementing SAP Employee Self-Service