End-To-End Solution for Configuration of ESS mySAP ERP 2005

Applies to:
SAP NW 2004s SP9 and SAP ECC 6.0. For more information, visit the Enterprise Resource Planning homepage.

Summary
This article supply the detail step to configure the Webdynpro based SAP business package for Employee Self Service for mySAP ERP 2005 on SAP WAS 2004s SP9.It also highlights all the hurdle faced and identified solution during that step. Author: Amitav Ghose

Company: HCLAXON Created on: 21 April 2011

Author Bio
Amitav Ghose is working in HCL AXON as Sr. SAP NetWeaver Consultant.He has wide range of experience in SAP EP, SAP Java Webdynpro, SAP MDM, Adobe Interactive Form and Java/J2ee.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1

End-To-End Solution for Configuration of ESS mySAP ERP 2005

Table of Content
Introduction ......................................................................................................................................................... 3 System Landscape.......................................................................................................................................... 3 Pre-requisites .................................................................................................................................................. 4 Configuration of SLD ....................................................................................................................................... 4
Preparation .................................................................................................................................................................. 5

Step. .............................................................................................................................................. 6
Step 1: Deploy the Business Package,Webdynpro Component and PCUI_GP ........................................................... 6 Step 2: JCO Connector setup in Webdynpro Content Administrator ............................................................................ 6 Step 3:Creating and Configuring System in Enterprise Portal...................................................................................... 8 Step 4: Creating a User in Enterprise Portal ................................................................................................................ 9 Step 5: Setting up Single Sign On between EP and ECC 6.0 using User Id and Password with User Mapping ........ 10 Step 6: Creating a User in SAP ECC 6.0 ................................................................................................................... 10 Step 7: Assign an Employee to an Existing User ....................................................................................................... 12 Step 8: Log on to Enterprise Portal with User Id ESS_USER1 to view the ESS screen ............................................ 14 Step 9: Test Employee Search for the Employee Assign to User .............................................................................. 14

Related Content ................................................................................................................................................ 16 Disclaimer and Liability Notice .......................................................................................................................... 17

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 2

End-To-End Solution for Configuration of ESS mySAP ERP 2005

Introduction
The Business Package for Employee Self-Service (mySAP ERP 2005) enables employees to create, display, and change their own HR-related data in the Enterprise Portal. It covers data from various business areas:

Benefits and Payment Working Time Career and Job Employee Search Personal Information Travel Management Corporate Information Life and Work Events

System Landscape

Employee(HR USER)

SAP ECC 6.0

SAP WAS 2004s SP9

Employee(HR USER)

The backend system SAP ECC 6.0 (mySAP 2005) and SAP WAS 2004s SP9 (Java Stack) was maintained in two separate server with in same domain. The business package would be deployed on SAP WAS 2004s SP9 and SAP WAS 2004s 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.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 3

End-To-End Solution for Configuration of ESS mySAP ERP 2005

Pre-requisites Installed SAP ECC 6.0 with Human Resource and financial extension. Installed SAP WAS 2004s SP9 (WAS 7.0, EP 7.0).

Configuration of SLD 1) Check the SLD of SAP WAS 2004s via URL http ://< server name> :< port>/sld. 2) SAP WAS 2004s J2ee Stack Technical System is already configured during the installation of server.

3) Configure the Technical system of SAP ECC 6.0 ABAP Stack using the path Landscape->Technical System

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 4

End-To-End Solution for Configuration of ESS mySAP ERP 2005

Note: Question: How to configure message server while configuring ABAP Technical System? Answer: To configure message server for ABAP Technical System you need to provide message server port and Logon Group.

How to get message server port? Message server port will be 36<2 digit instance number of SAP ECC 6.0 ABAP System> How to get Logon Group? Use SAP Transaction code SMLG, there you will get all the configured Logon Group and make sure that Ext. RFC-enabled attribute is checked for used logon group in SLD Technical system.

Please find the screen shot details mention below:

Preparation Download the Business Package and Application component for Employee Self Service from Service Market Place using your SAP Market Place User Id and Password. Go to the address http://service.sap.com/swdc.

1.BP for ESS : Click on Download -> Support Packages and Patches -> Entry by Application Group -> SAP Application Components -> SAP ERP -> SAP ERP 6.0 -> Entry by Component -> Portal Content -> BP ERP05 ESS 1.0 -> Click it and select #OS independent --> Select the SCA file depending on your SP Level 2.BP for MSS : Click on Download -> Support Packages and Patches -> Entry by Application Group -> SAP Application Components -> SAP ERP -> SAP ERP 6.0 -> Entry by Component -> Portal Content -> BP ERP05 MSS 1.0 -> Click it and select #OS independent -> Select the SCA file depending on your SP Level

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 5

End-To-End Solution for Configuration of ESS mySAP ERP 2005

For actual Web Dynpro applications Click on Download ->Support Packages and Patches -> Entry by Application Group -> SAP Application Components -> SAP ERP -> SAP ERP 6.0 -> Entry by Component -> SAP XSS (Self Services)-> Click it and select #OS independent -> Select the SCA file depending on your SP Level Then download the following files: 3. SAP ESS 600 4. SAP MSS 600 5. SAP PCUI_GP 600 It is very important that all the files you download have the same Support Package level. For detail information on Business Package SP level please refer the link mention below: http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOW+TO+GET+RID+OF+SP+STACK+MISMATCH+ISSUES

Step Step 1: Deploy the Business Package,Webdynpro Component and PCUI_GP Deploy all the files in SDM.As such there is no order to deploy the file but its recommended first to deploy the SAP PCUI_GP 600 then you can deploy the rest in any order you want. After that login to portal check for the content in PCD.

Step 2: JCO Connector setup in Webdynpro Content Administrator Log on to the Web Dynpro Content Administrator using the administration user for the J2EE server via the URL: http://<host>:<port>/webdynpro/dispatcher/sap.com/tc~wd~tools/Explorer Choose maintain JCO Destinations. A list of the JCO connection 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 JCO connections are required and displays them with status as RED which means that they need to be created. The JCo destinations can be created separately/individually, if required.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 6

End-To-End Solution for Configuration of ESS mySAP ERP 2005

Create the required JCO 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

Configure the JCO connection for the metadata and Application data In the Connection Type step, choose the Dictionary Meta Data or Application data option as per the need. Choose Security. In the Used Method field, enter the User/Password. Enter the username/password for a user in ECC 6.0 system with sufficient rights (Use the user with SAP_ALL authorization and the user must be map with employee which we will cover in later stage of this document. Check the connection.
Note: Question: What needs to be done if JCO connection failed and throws Exception? Answer: Please find the link mention below for Trouble shooting of JCO Connection.This link is quite helpful.

http://wiki.sdn.sap.com/wiki/display/EP/Troubleshooting+SAP+Java+Connector+(JCo) One Important entry needs to be done before JCO Connection to overcome come from common error which is mention below: If Java stack and ABAP stack is on same server On the portal server in services file add the entry %WINDIR%\system32\drivers\etc\ sapms<ABAP System SID Name> 36<ABAP System Instance Number>/tcp Service Port If Java stack and ABAP stack is on different server Please do the same entry mention above on both the server. Its always recommended once this changes are done please restart the server. Once the required JCO destinations are created, their status changes from red to green.

# SAP System Messaging

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 7

End-To-End Solution for Configuration of ESS mySAP ERP 2005

Step 3:Creating and Configuring System in Enterprise Portal a) Set up the first system on the Portal J2EE 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: <J2EE Name>:<Port> WAS path: /webdynpro/dispatcher/ WAS protocol: http or https Set up a system for an internal ITS or a separate ITS, and assign the system the alias SAP_ITS_EBU. Maintain the ITS properties for this system. In particular: ITS host name: <ITS Name>:<Port> ITS path: /sap/bc/gui/sap/its ITS protocol: http or https b) For the Career and Job 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 c) 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

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 8

End-To-End Solution for Configuration of ESS mySAP ERP 2005

Step 4: Creating a User in Enterprise Portal We create a User with the user-id ESS_USER1 and assign it the role for ESS which would be same for the user in our SAP system.

Also ensure that user has atleast Read Permission for the systems we have created in the Enterprise Portal. It will be done through System Administration->Permission->Portal Permission

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 9

End-To-End Solution for Configuration of ESS mySAP ERP 2005

Step 5: Setting up Single Sign On between EP and ECC 6.0 using User Id and Password with User Mapping a) Property Logon Method is set to UIDPW in the system object defining the SAP System in the portal.

b) Users user ID and Password must be mapped to their user ID and Password in each of the SAP system either by user themselves or Portal Administrator.

Step 6: Creating a User in SAP ECC 6.0 To be able to use the ESS applications (services), your employees require particular authorizations. Log on to the SAP ECC system. Go to the PFCG transaction (Role Maintenance). 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

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 10

End-To-End Solution for Configuration of ESS mySAP ERP 2005

Go to the transaction SU01 and create a user with User-id ESS_USER1 and assign it the copied composite role ZSAP_EMPLOYEE_ERP. 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.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 11

End-To-End Solution for Configuration of ESS mySAP ERP 2005

Step 7: Assign an Employee to an Existing User Go the transaction code HRUSER. Assignment of Employee to existing user.

Select the employee and press assign employee

Search for employee will be done by employee code. To get the information of employee you need to follow the following step mention below: Go to Transaction code SE11 Provide the table name as PA0002 then click display after that table content then execute.You will find all the employee information with Personal code.The employee personal code is mapped to table field PERNR.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 12

End-To-End Solution for Configuration of ESS mySAP ERP 2005

Use this employee code for assignation when you click Assign Employee after selecting user.

After entering employee code when you click enter the Create relationship Dialog box appear which creates a relationship between an employee and user. Then click create.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 13

End-To-End Solution for Configuration of ESS mySAP ERP 2005

Step 8: Log on to Enterprise Portal with User Id ESS_USER1 to view the ESS screen

Step 9: Test Employee Search for the Employee Assign to User Click Employee Search after that click Who's Who then search screen will display.Provide the search information then go for search.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 14

End-To-End Solution for Configuration of ESS mySAP ERP 2005

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 15

End-To-End Solution for Configuration of ESS mySAP ERP 2005

Related Content
Trouble Shooting JCO Downloading and deploy ESS & MSS HOW TO GET RID OF SP STACK MISMATCH ISSUES For more information, visit the Enterprise Resource Planning homepage.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 16

End-To-End Solution for Configuration of ESS mySAP ERP 2005

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.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 17