SDN Cont ri but i on

Configuring the Business Package for Employee Self-

Service (ESS) mySAP ERP 2004

Applies to:
SAP NetWeaver Portal 6.0, SAP ECC 5.0
Summary
SAP business packages deliver an intuitive user interface that brings together all the resources needed for
specific tasks, including internal and external information, access to services, and access to transactions,
basically predefined, role-specific content that you can use right out of the box. This article provides detailed
steps to quickly configure the Web Dynpro-based business package for Employee Self Service for mySAP
ERP 2004 on Sneak Preview J ava.
Created on: 4 April 2006
Author Bio
Siddhartha J ain is working in HCL Technologies as an SAP NetWeaver consultant and is an
SAP-certified Technology Consultant in Enterprise Portal and Knowledge Management
Collaboration.



2006 SAP AG 1

Table of Contents
INTRODUCTION............................................................................................................................. 2
THE SCENARIO.......................................................................................................................... 3
PRE-REQUISITES....................................................................................................................... 3
PREPRATION.............................................................................................................................. 4
STEPS.......................................................................................................................................... 5
A) IMPORTING THE BUSINESS PACKAGE........................................................................... 5
B) Deploying the Web Dynpro Development Components-ESS and PCUI_GP............................. 6
C) Setting up the SAP J AVA Connector (J Co) Connections in the Web Dynpro Content Administrator 6
D) Creating/Configuring the Systems used in Enterprise Portal .............................................. 7
E) Creating a User in Enterprise Portal.................................................................................... 9
F) Setting up Single Sign On between Enterprise Portal and mySAP ERP(ECC) Server..... 10
G) Creating a User in mySAP ERP 2004............................................................................... 12
H) Assign an Employee to an Existing User........................................................................... 14
I) Log into the Enterprise Portal using the portal user (ESS_USER1) to see the User Interface for ESS!!!
................................................................................................................................................ 16
J ) Time for Some Customization!!!!........................................................................................ 16
1) Changing the standard text In the Overview page............................................................. 16
2) Changing the Long Area Description................................................................................. 18
Related Content............................................................................................................................. 21
Disclaimer and Liability Notice....................................................................................................... 21
INTRODUCTION
SAP develops predefined, preconfigured content objects, packages it according to job and industry-specific
roles and makes it available in business packages that can be plugged into the SAP NetWeaver Portal.
SAP business packages deliver an intuitive user interface that brings together all the resources needed for
specific tasks, including internal and external information, access to services, and access to transactions
facilitating an increase in employee efficiency, reduce costs, speed portal deployments, and maximize the
value of your IT infrastructure thus helping companies get the most out of their IT investments.
The business package for Employee Self-Services helps streamline administrative tasks common to large
numbers of employees within the organization such as creating, displaying, and changing their own HR-
related data in the Enterprise Portal. It covers data from various business areas:
Benefits and Payment
Working Time
Career and J ob

2006 SAP AG 2

Employee Search
Personal Information
Travel Management
Corporate Information
Life and Work Events
This business package does not contain any business applications. Instead, it contains iViews that enable
you to call Web Dynpro applications and display these applications in the SAP Enterprise Portal.
These Web Dynpro applications are delivered with the SAP ECC 5.0 Human Resources Extension (EA-HR
500) component as opposed to with the business package

THE SCENARIO

The backend system is SAP E.C.C. 5.0 SP6 ( mySAP ERP 2004), WAS ABAP stack, while Sneak Preview
J AVA SP11 (WAS 6.4 , E.P. 6 SP11) has been installed separately.
The business package would be installed on Sneak Preview J avas Portal which would be the access point
for the users of ESS and the corresponding users would be available in the backend ECC system where they
would be assigned to employees of the Organization.

PRE-REQUISITES
1. Installed SAP ERP core components (SAP ECC 5.0) with Human Resource Extension (EA_HR) and
financial extension (EA_FIN).
2. Installed Sneak Preview J ava(WAS 6.4, EP 6.0)
3. Configured the System Landscape Directory(SLD)
Check the SLD of Sneak Preview J ava via URL
http://<server>.<domain>:<port>/sld
In System LandscapeTechnical Landscape
The J ava system (WAS 6.4) and the ABAP system (ECC server) must be configured.

2006 SAP AG 3





PREPRATION
1) Download the Business Package for Employee Self Service (mySAP ERP 2004) from SDN using your
SAP Service Marketplace ID.
(SDNPortal Content PortfolioBrowse Content PortfolioEvery UserSelf ServiceBusiness Package
for Employee Self Service (mySAP ERP 2004) 60.2)
2) Check the J 2EE Version and Download the following Web Dynpro Development Components (patches)
from service marketplace (Refer SAP Note 761266Self Service Patches to know the version to be
downloaded):
ESS
PCUI_GP
(service.sap.com/downloadSupport patches and packagesEntry By application GroupSAP
Application ComponentsSAP ERPSAP ERP 2004Entry By ComponentSAP XSS (SAP ESS 100
and SAP PCUI_GP 100))
For the current Scenario, I downloaded PCUI_GP07_0.sca; ESS07P_2.sca .

2006 SAP AG 4


STEPS
A) IMPORTING THE BUSINESS PACKAGE
The Business Package for ESS mySAP ERP2004 is ZIP file containing the archive of type Software
Component Archive (SCA) (BPERP4ESS0_0.sca) which has to be deployed using the Software Deployment
Manager (SDM) .
The deployment of new software components is divided into several steps....
1. Choose Add SCA/SDA to Deployment List. Choose Next.
2. The SDM determines the Deployment Action from the manifest data and displays the data in the
archive list. The Repository Preview shows us how the SDAs are distributed in the SDM Repository.
Choose Next.
3. The SDM tells us that it is ready for deployment. Choose Start. If an error occurs and you have to
perform the deployment again, deployments that were successfully performed are not repeated.
4. A success message appears at the end of the deployment process. Choose Confirm to confirm the
deployment.
5. Login into the Portal and check for the content in the Portal Content Directory.


2006 SAP AG 5



B) Deploying the Web Dynpro Development Components-ESS and PCUI_GP
The Development Components (Patches) for Employee Self service are archives of type Software
Deployment Archive (.sda).
Extract the ZIP files-- ESS07P_4-10002965.sca.zip and PCUIGP007_0-20000568.sca.zip. Each
extract consists of the folders -BUILDARCHIVES, DEPLOYARCHIVES, META_INF and
SOURCEARCHIVES.
Using the SDM GUI, add all the deployment archives from the folder DEPLOYARCHIVES, for ESS
and deploy.
Do the same for archives for PCUI_GP.
There is no order for deploying these Components but there are dependencies between the various SDAs
within each component, so all the archives within each component need to be added and deployed all
together, separately for each component.



C) Setting up the SAP J AVA Connector (J Co) Connections in the Web Dynpro Content Administrator
1) Log on to the Web Dynpro Content Administrator using the administration user for the J 2EE server
(admin in sneak preview) via the URL :
http://<host>:<port>/webdynpro/dispatcher/sap.com/tc~wd~tools/Explorer
2) Choose maintain J Co Destinations. A list of the J Co connetions for the metadata and those for the
application data is displayed. Connections for various areas exist. The names of the connections start with
SAP_R3_*. As we have deployed the web Dynpro Software components, the Web Dynpro Content
Administrator automatically recognizes which J Co connections are required and displays them with status as
RED which means that they need to be created. The J Co destinations can be created separately/individually,
if required.
3) Create the required J Co connections
SAP_R3_HumanResources
SAP_R3_HumanResources_MetaData
SAP_R3_Financials
SAP_R3_Financials_MetaData
SAP_R3_SelfServiceGenerics
SAP_R3_SelfServiceGenerics_MetaData
SAP_R3_Travel
SAP_R3_Travel_MetaData

2006 SAP AG 6


a. Configure the J Co connection for the metadata:
i. In the Connection Type step, choose the Dictionary Meta Data option.
ii. Choose Security.
iii. In the Used Method field, enter the User/Password.
iv. Enter the username/password for a user in mySAP ERP system for the metadata connection with
sufficient rights (I used user with SAP_ALL authorization)
v. Check the connection.

b. Configure the J Co connection for the application data:
i. In the Connection Type step, choose the Application Data option.
ii. Choose Security.
iii. In the Used Method field, enter Ticket.
iv. Check the connection.
Note: We use logon user for Meta data in J CO destination while for Application J Co destination, we use
either logon tickets or user mapping as the metadata calls are asynchronous and do not happen every time
we call an RFC.
Once metadata is obtained it is cached. With the metadata connection, the Web Dynpro application receives
the metadata that is not user-specific and that is therefore the same for all users. It must be available to all
users.
With the application data connection, the Web Dynpro application receives the application data, which is
normally user-specific.
Once the required J Co destinations are created, their status changes from red to green.



D) Creating/Configuring the Systems used in Enterprise Portal

2006 SAP AG 7

1) Set up the first system on the Portal J 2EE server in which the business package has been implemented
and assign the system the alias SAP_WebDynpro_XSS.
Maintain the WAS properties for this system. In particular:
WAS host name: <J 2EE Name>:<Port>
WAS path: /webdynpro/dispatcher/
WAS protocol: http or https

2) Set up a system for an internal ITS or a separate ITS, and assign the system the alias SAP_ITS_EBU.
WAS 6.4 comes with an integrated ITS, here mySAP ERP 2004,so we use the values for that. (see SAP
Note 745404):
Maintain the ITS properties for this system. In particular:
ITS host name: <ITS 6.40 Name>:<Port>
ITS path: /sap/bc/gui/sap/its
ITS protocol: http or https

3) For the Career and J ob work set, set up a system with the alias SAP_BSP_EREC for the BSP
applications from the E-Recruiting work set.

For the Properties for Connector, provide appropriate values for
SAP Client
System Type
Server Port
SAP System ID


2006 SAP AG 8

3) Set up a system with the alias SAP_R3_Financials that refers to the SAP Web AS for ABAP server and
acts as a BSP server. For this system, maintain the WAS properties (required for executing BSP
applications) and the SAP system properties (for the Financials functions):
Logical system name
SAP client
SAP system OD (SID)
SAP system number
Server port
WAS host name: <ECC Backend Name>:<Port>
WAS protocol: http or https


E) Creating a User in Enterprise Portal
In the scenario taken, the UME store for EP is database only, so we create a User with the user-id which
would be same for the user in our mySAP ERP system.
We create a User with the user-id ESS_USER1 and assign it the role for ESS

Also, ensure that the user has at least Read permissions for the systems we have created in the Enterprise
Portal.

2006 SAP AG 9


We can create a folder under which we can create all the systems required for the business package and
assign permissions to the user/group via the permission editor.
(System AdministrationPermissionPortal Permissions)


F) Setting up Single Sign On between Enterprise Portal and mySAP ERP(ECC) Server
1) Exporting the Portal Certificate.
a) Start the SAP J 2EE Administrator.
b) Connect to appropriate server .
c) Choose portal_sid/Server<>/Services/Key storage.
d) Select the TicketKeystore under Views .
e) Select SAPLogonTicketKeypair-cert under Entries .
f) Choose Export.
g) Change the name of certificate to portal_sid_certificate.crt .


2) Configuration of Instance Profile.
In the mySAP ERP server, go to transaction RZ10 and select the instance profile for editing.

2006 SAP AG 10


Set the following parameter values

icm/host_name_full points to the fully qualified domain name of the server (refer SAP Note 434918 and
517484 for details) and is of the form <server>.<domain>
Now restart the Application server for the changes in profile parameter to take effect.


3) Importing the Portal Certificate.
a) Start Transaction STRUSTSSO2.

2006 SAP AG 11


b) Import <portal_sid>_certificate.crt file in binary format
c) Add certificate to list of certificates
d) Add certificate to ACL, give portal system ID and Client as 000


G) Creating a User in mySAP ERP 2004
To be able to use the ESS applications (services), your employees require particular authorizations.
1. Log on to the SAP ECC system.
2. Go to the PFCG transaction (Role Maintenance).
3. Create copies of the composite role SAP_EMPLOYEE_ERP and all the single roles contained in it.
Work with the copies only.
Here I have copied the composite role SAP_EMPLOYEE_ERP and the single roles it contains, to
corresponding Z-Roles

2006 SAP AG 12



4. Go to the transaction SU01 and create a user with User-id ESS_USER1 and assign It the copied
composite role ZSAP_EMPLOYEE_ERP.
5. For the user, set the CVR parameter to the companies default Cross Application Time Sheets
Application (CATS) profile ESS.
The user Parameter CVR assigns a predefined data entry profile to a user, required when we access the
time sheet.


If the default profile does not exists, add the ESS profile in table TCATS.

2006 SAP AG 13

(IMG activity ->CAT regular ITS )






H) Assign an Employee to an Existing User
Go to Transaction HRUSER.
Assignment of Employee to existing Users

2006 SAP AG 14



Select the Employee and press Assign employees.


We search for the employee using his Personnel No. and assign it.
I have used employee 32 in this scenario.
The Create Relationship dialog box appears. This assignment creates a relationship between an employee
and a user


We can view the employees relationship in the Communication info type (0105) via transaction PA20.

2006 SAP AG 15



I) Log into the Enterprise Portal using the portal user (ESS_USER1) to see the User Interface for ESS!!!

J ) Time for Some Customization!!!!
Now that the business package has been implemented, its time for some change/customization to the User
Interface
In the ECC system, navigate to
IMG activity: Cross-Application Components Homepage Framework
1) Changing the standard text In the Overview page.
Say, we want to change the default description of the ESS application in the overview Page.


2006 SAP AG 16

a) Navigate to Define Area Group pages as:

b) Define Area Group Pages (Add Entries) and open the area group page SAPDEFAULTESS and change
the text as required and save.


2006 SAP AG 17



c) Log in to the Portal with ESS_USER1 and see the changes:


2) Changing the Long Area Description
An Area Page is a portal page that groups all applications that belong to a particular business area.
The page comprises a pictogram that represents the area and a short description for each application
(service). Hyperlinks on this page enable your employees to call the relevant applications
If we want to change the description of (Additional Information as shown in the screenshot)


2006 SAP AG 18


a) Create the area description as an HTML file.
I created an HTML file as a Document in KM of the Enterprise Portal.


b) In the Implementation Guide under Homepage Framework, create a new Resource that
points to the HTML document that is to be displayed.


c) In the Implementation Guide under Homepage Framework, select Define Areas and
open the area Employee Search for Editing and add the Resource just defined in the Area
Description(External) and give the height of the External Description Frame

2006 SAP AG 19





Now Login into the Portal with the User ESS_USER1 and see the changes.



Similarly, there are many other customizations that can be carried out depending upon the requirement.
This article was aimed at providing a step by step approach to setting up the Web Dynpro based business
package for Employee Self Service and share some quick Customizations.
I hope it comes in handy for the SDN community!!



2006 SAP AG 20

Related Content
1) Documentation On help.sap.com--Employee Self Service mySAP ERP2004
2) SDN - Portal Content Portfolio

Disclaimer and Liability Notice
This document may discuss sample coding or other information that does not include SAP official interfaces
and therefore is not supported by SAP. Changes made based on this information are not supported and can
be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods
suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of
this technical article or code sample, including any liability resulting from incompatibility between the content
within this document and the materials and services offered by SAP. You agree that you will not hold, or
seek to hold, SAP responsible or liable with respect to the content of this document.




2006 SAP AG 21