Professional Documents
Culture Documents
Welcome, Guest
Login
Register
Getting Started
Newsletters
Store
Top of Form
Search for:
true
Innovation
Home
Activity0
Communications
Actions0
BrowseMore
Content
People
Places
Recent Bookmarks
Top of Form
2
document.restore [placeholder]
Bottom of Form
Top of Form
document.publish
[placeholder]
DOC-30218
Bottom of Form
More documents in SAP ERP HCM Employee Self-ServiceWhere is place located?
All Places
Enterprise Resource Planning (SAP ERP)
SAP ERP Human Capital Management (SAP ERP HCM)
SAP ERP HCM Employee Self-Service
Currently Being Moderated
Customizing ESS in EHP5 ( Step by Step Guide)
created by Virag Shinde on Jul 20, 2012 3:28 PM, last modified by Julien Tuerlinckx
on Jan 2, 2013 1:25 PM
Version 2
Tweet
Table of Contents
1.1
1.2
1.3
Portal Objects 9
1.4
Prerequisite Configuration 10
2.
3.
4.
5.
6.
7.
Customize the Personal Information Application Configuration
(HRESS_AC_PERSINFO) 26
8.
Customize the Personal Information Component Configuration
(HRESS_CC_PER_OVP) 30
9.
10.
11.
12.
13.
14.
15.
16.
References 62
SAP has adapted its major release strategy to better fit an organizations adoption
cycle. To ensure that customers benefit from new developments and innovations
while minimizing the impact on core operational systems, SAP uses enhancement
packages to speed up the delivery of new functions.
With SAP enhancement packages, you can install and activate new functions
depending on your business needs without having to perform a system upgrade.
You can selectively implement the new functions and activate the software upon
business demand. As a result, you can isolate the impact of software updates and
make new functions available faster due to shortened test cycles.
The fifth release of such Enhancement Package by SAP is termed as SAP EHP5.
Implementation Overview
There are three different scenarios to implement an enhancement package:
Installation of an enhancement package on an existing SAP system
New installation of an SAP system including an enhancement package
Upgrade of an SAP system including an enhancement package
You have a choice on both levels installation and activation. You do not need to
install a full enhancement package. Instead, you can update the software
components that are related to the functional enhancements you want to use.
From a business point of view, functional enhancements are grouped into business
functions (BFs). The technical installation of the business functions does not change
the system behavior. The new functions are available in the system, but are not
active.
Switch Framework
After the installation, no user interface or process change takes place. You must
explicitly activate new functions so that they become visible in the system. As a
result, changes are predictable and there are no side effects as only the activated
areas change.
With the switch framework technology (transaction SFW5), it is possible to control
the activation of new SAP objects in ABAP-based SAP systems. The activation
process triggers a background job that automatically performs all changes in the
SAP system. It is recommended to test the installation and up gradation on a
sandbox system.
After you have activated a business function, you can see the changes and new
developments in the SAP system, for example
Menu entries
New screens
New fields on the application user interfaces
IMG activities required for the implementations
New table entries in Customizing tables and system tables
You can create a transport request with the current settings of the switch
framework. You can check functional changes and the impact of an activated
business function in advance in the business function documentation.
Support packs
SAP enhancement packages have Support Packages of their own that are equivalent
to the Support Package versions of the underlying SAP system. Install the
enhancement package in combination with the latest available Support Package
stack. This approach reduces installation, modification adjustment, and testing
effort. Using this strategy, you can install SAP enhancement packages as a normal
maintenance activity together with Support Package stacks.
An enhancement package requires a specific Support Package stack level in the
source release SAP system. If the SAP system is on a lower Support Package stack
level, all relevant Support Package stacks are automatically included into the
download queue, as well as the latest available Support Packages for the
enhancement package.
Please refer https://service.sap.com/sap/support/notes/1484460 for all EHP5 related
support packs
The following systems, business packages and XSS components need to be installed
to fully leverage ESS (and/or MSS) services in ECC6 EHP5.
a.
System Requirements
SAP Web AS ABAP 7.0+
SAP Portal 7.0+
b.
1.2
ESS UIs are based on WebDynpro applications. Customization can be done through
application configurations delivered by SAP for each application component.
The following table is a list of commonly used ESS packages and application
configurations:
Package
Application Configuration.
Service
PAOC_ESS_CENTRAL_SERVIC
ES
HRESS_AC_MENU
ESS Overview
PAOC_ESS_PER_WDA
HRESS_AC_PERSINFO
Personal Information
PAOC_ESS_PER_XX
HRESS_CC_PER_OVR_<subtype
> _XX
Personal Information
International overview
screen
PAOC_ESS_PER_XX
HRESS_CC_PER_DTL_<subtype
>_XX
Personal Information
International detail
screen
PAOC_CATS_ESS_WDA
HRESS_AC_CATS_1
Time Recording
PAOC_HAP_PA_PMP_UI
HRESS_AC_PMP_EMPLOYEE
Performance Appraisal
PMP
1.3
Portal Objects
b. Page:
Overview:
portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.wda.bp_folder/com.sap.
pct.erp.ess.wda.pages/com.sap.pct.erp.ess.wda.Overview
c. Workset:
Employee Self-Service:
portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.wda.bp_folder/com.sap.
pct.erp.ess.wda.worksets/com.sap.pct.erp.ess.wda.Employee_Self_Service
d. Role:
portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.wda.bp_folder/com.sap.
pct.erp.ess.wda.roles/com.sap.pct.erp.ess.wda.Employee_Self_Service_WDA
1.4
a.
Prerequisite Configuration
Business Function HCM_ESS_WDA_1
Activate this business function (SFW5) to enable ESS ABAP functionality. Use SFW2
to check its status.
b.
c.
Assign to all ESS users the standard portal role: Employee Self-Service
(com.sap.pct.erp.ess.wda.Employee_Self_Service_WDA). If customization is
required, make a copy of this role.
d.
Create a portal system connection to the ECC backend with the alias
SAP_ECC_HumanResources.
For detailed information about the Initial setup required, refer following link:
https://help.sap.com/erp2005_ehp_05/helpdata/en/4f/b9088db1034075a337c53708
3539da/frameset.htm
You use a launchpad to allow users to navigate to specific goals outside of the
current Floorplan Manager application. For example, this could mean navigating to
other Web Dynpro ABAP applications, external Web pages, transactions, reports, or
other business objects. The YouCanAlsoand RelatedLinks elements are available in
the toolbar of Object Instance Floor Plans and Guided Activity Floor Plans. You can
assign these elements to different launchpads. In the floor plan for an overview
page, you can integrate launchpads via the launchpad component.
The SAP Standard Menu for ESS looks like this on the portal
To change the Contents, like the processes seen above in each of the groups we
have to create a custom launchpad.
Go to transaction LPD_CUST. Select ESS (Role), Menu (instance) as shown below.
Once inside the ESS Menu, we will see the following applications under the ESS
Launch pad:
Enter following details on the next screen. In the namespace, enter the name of
your Z package. In this way, you will be able to transport your launchpad to other
systems.
Then you should see the SAP Standard ESS launchpad on the left and the blank
custom launchpad to the right.
Click on New Folder to create new nodes like Benefits & Payment Etc on the right
hand side in ZESS Launchpad.
Once the Folders are created, we can drag and drop applications from the SAP
standard launchpad to the custom one as shown below
Once the custom launchpad is ready, we need to ensure that we see the custom
launchpad on the portal instead of the standard one. For this we need to make some
modifications using the Component Configuration in Floor Plan Manager.
We can add various types of objects in the launchpad like WebDynpro ABAP or Java
Application , a SAP transaction , a URL page , a Portal Object etc . See screenshot
below :
Goto transaction SE80, in the Repository Browser & select WebDynpro Comp. / Intf.
. Enter the component name FPM_LAUNCHPAD_UIBB and press enter.
So far we have customized the ESS Launchpad to add / remove applications as per
our need and have assigned the custom launchpad to FPM. Now that we have the
launchpad customized, lets see how to make the Portal point to custom
applications instead of the standard one.
4. Locating the ESS Overview Portal iView.
There is only one iView for ESS in EHP5. It is called as the ESS Overview IView. It
displays the content from the Launchpad we have customized so far.
The ESS Overview iView can be found under Portal Content -> Content Provided by
SAP -> End User Content -> Employee Self-Service Web Dynpro ABAP -> iView ->
Overview
In Step 1, we saw how to change the content inside each of the groups above by
creating a custom launchpad. The layout of the groups and their appearance (not
their content) can be managed by making a copy of the HRESS_AC_MENU
Configuration.
Once you click on Start Configurator, new browser windows should open which will
display the Application configuration.
To make a copy of the Application config, click the Copy. Then we will have to enter
Configuration Name, Description, Package and Transport Request for the Copy
object as shown below.
This copy can now be seen in the Object navigator and can be used to make any
customizations required.
ESS contains various applications like Personal Information, Benefits and Payment,
Travel and Expenses etc. Lets see how to customize the Personal Information
Screen.
Personal Data
2.
Addresses
3.
Communication
4.
Bank Information
5.
6.
Internal Data
7.
A Web Dynpro application usually belongs to a main component, which - in turn uses a series of other components. You can use the application configuration to
assign all used components the component configuration required in the current
application.
SAP has used various configurations for its applications to deliver a seamless
business object for ESS.
To customize the Personal Information application do the following:
Once the Application Configuration is opened in a browser window, use the Copy
button to make a copy and name it ZHRESS_AC_PERSINFO
After creating a copy by giving the appropriate transport request. Go back to SE80
Goto, open WebDynpro component FPM_OVP_COMPONENT -> WebDynpro
Applications -> HRESS_A_PERSINFO ->ZHRESS_AC_PERSINFO. Click on Start
Configurator.
This means that we are still referring to the Standard SAP Screen. We need to
customize the Component Configuration for Personal Information
(HRESS_CC_PER_OVP) and assign it to our custom Application Configuration
(ZHRESS_AC_PERSINFO).
With the component configuration, you can control the behavior of each individual
component within a Web Dynpro application or the user interface of individual
views. For each component, several records of configuration data can be created.
This kind of data record contains different types of attribute, Web Dynpro built-in
attributes, component attributes, and administration data.
For more information about component configurations, refer the following link:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/47/b1693856293c5ce10000000
a421937/content.htm
Once you see the Component Configuration screen, click on Copy to make a Copy
and enter proper name, Package and transport request.
You will then see the below screen which Shows the FPM layout of the Personal
Information Overview page
The Component Configuration has two parts, Hierarchy on the Left hand side and
Preview on the right hand side.
1. The Overview screen ( as seen above) which has Business Cards to various
process
2. The Detail Screen which is shown upon clicking on a business card in overview
page and contains more details about the particular process
The Hierarchy sections show a list of all the Details screens as well as the overview
screen. Clicking on each page on the left side shows the FPM preview on the right
side. The Figure above shows a preview of the Overview page.
To hide unwanted sections from the overview screen, click on the Attributes button
of that UIBB. For e.g., to hide the Alternate Name Overview Screen, see below
screenshot
On the attributes screen use the Hidden Element Checkbox to hide that UIBB from
the overview screen.
b.
In case we need to use a different component configuration than the one provided
by SAP, we can change that in the Attributes window.
c.
We can also embed custom applications on the Overview Page. To do this the
custom WebDynpro Component needs to implement FPM interfaces as seen below:
Once the FPM interfaces are implemented the custom application can then be
added to the over view screen as follows:
Select the appropriate Section of the Overview page in the left pane
Then Click Add UIBB on the right, from the dropdown menu, selects Add UIBB
again.
Save the Overview Configuration and the custom application can be seen on the
overview screen along with other Standard SAP components as seen below:
10.
You can configure which configuration blocks or edit screens to be displayed, hidden
or replaced for the particular target users by using the HRESS_CC_PER_CONFIG
component controller under HRESS_C_PERSINFO_CONFIG. The AppCC performs
dynamic operation on UIBBs based on the keys configured a Key Configuration and
UIBB Configuration of the AppCC for example, you can replace the Bank Information
overview screen with a country-specific overview screen for US (country version 10).
Then click on Start Configurator and you will get the following screen in a new
browser window, Click on Display
Here you can which Country is using which screen. For example, if you need to see
which screen is used for US Address, do the following:
Scroll down and Select USA, you will see all the Infotype and subtypes configured
for USA
Then Click on Addresses, on the right side we can see the Country Version 10
(USA) & Infotype 0006 (Address)
To check which screen is used for US Address, select the UIBB under Addresses
This means that the component dynamically replaces the International Screen with
the US Screen during runtime.
This way, we can find out the Screen Configuration used by any Country for any
Infotype.
We will now see how to develop a custom screen for an Infotype and use it in ESS.
11.
12.
The Business Cards on the overview screen are configured in the FPM_LIST_UIBB
WebDynpro component while the Detailed screens are configured in
FPM_FORM_UIBB .You can get the appropriate configuration name for a particular
Country and Infotype by following link :
http://help.sap.com/erp2005_ehp_05/helpdata/en/5b/6bd62591bc42aab2aa155d03ff
f79c/content.htm
For the US, there is an international overview
screen(HRESS_CC_PER_OVR_ADDRESS_XX) and a localized detail screen
(HRESS_CC_PER_DTL_ADDRESS_US), which enable employees to display and
maintain their address data from the Addresses Infotype (0006) in a format specific
to the United States.
Click on Start Configurator, once the browser opens create a Copy of the
Configuration and give it the name ZHRESS_CC_PER_OVR_ADDRESS_US. Please note
the naming convention, custom object should start with Z, and replace the XX by
US. XX stands for international version.
You will then be able to see the Configuration with a list of fields as shown below.
13.
Here you can modify / remove any fields and save the configuration. Just select the
field you desire to delete and click on the delete button.
See screenshot below on how to remove valid to field.
In addition to removing unwanted fields, we also have the option to modify other
properties related to the screen field. Here are some of the properties:
UI Element Type ( Text view , input
field etc)
Design ( Bold ,
Italic etc )
Wrapping
Label text
Text Color
Width
Alignment
Tooltip
Layout
These fields can be modified/removed from the overview screen. Follow similar
process to modify/remove fields form the detail screen. Please note that detailed
screen uses the WebDynpro component FPM_FORM_UIBB . (Overview screen uses
FOM_LIST_UIBB)
14.
To add new fields to the Overview Screen, click on Configure Columns from the
toolbar
The left side of the above screen shows all Available Columns while the right side
displays the Displayed Columns. You can add new fields from left to right. Also
note that you can remove fields from this screen too in addition to the way
mentioned in step 2.10.1.1.
Please note that the available fields on the left are only filled with the corresponding
screen structure for that Country/Infotype combination. For more information on
Screen structures please visit following link:
http://help.sap.com/erp2005_ehp_05/helpdata/en/43/304ad229990b19e10000000a
1553f6/content.htm
In case custom fields need to be added to the screen, these fields need to be added
to the CI INCLUDE of the respective structure. The above screenshot shows custom
fields added the include CI_US_R0006 of the US screen structure
HCMT_BSP_PA_US_R0006.
The same custom screen fields can now be seen in the FPM configuration for US
address HRESS_CC_PER_DTL_ADDRESS_US.
Please note that adding fields to the structure only makes them available to be
added on the screen. We need to use HRPAD00INFTYUI BADI. For more information
on this BADI please see the following link:
http://help.sap.com/erp2005_ehp_05/helpdata/en/4f/d526cb575e11d189270000e83
22f96/content.htm
Following extract of the code from the OUTPUT CONVERSION method shows how to
move values from the Infotype to screen fields.
Similarly , data can be moved from the Screen to the Infotype using the INPUT
CONVERSION method.
15.
If there is any requirement which cannot be fulfilled by following the above steps,
we can go a level deeper in the SAP framework and modify the feeder class. A
feeder class provides a link between the application and the generic user interface
building block (GUIBB).
There are primarily two feeder classes that are used by the Personal
Profileapplication:
CL_HRESS_PER_OVERVIEW
This feeder class is used to configure overview screens, also referred to as business
cards (biz cards), of the Personnel Profile application.
CL_HRESS_PER_DETAIL
This feeder class is used to configure detail screens of the Personal
Profileapplication
Further feeder
classes
There are other standard feeder classes available. These are found under the
package PAOC_ESS_PER_WDA.
The feeder class for any UIBB can be modified in the Component configuration by
using the Edit Feeder button as shown below :
Once we click the Edit Feeder button it will show the name of the Feeder class as
seen below
We can either add a custom feeder class here or change the existing one in SE80
as shown:
The Feeder class has various methods which can be modified as required to
customize the output.
We have covered majority of the aspects of customizing ESS screens spanning the
pre-requisites to the customizations required in the code. Please see the references
section below for additional information links.
16.
References
http://help.sap.com/erp605/
http://help.sap.com/erp2005_ehp_05/helpdata/en/25/340b0507434193adbfe3f8fc88
96c7/content.htm
http://help.sap.com/erp2005_ehp_05/helpdata/en/77/804c18e1844944b7f8baf5315
9be78/frameset.htm
Configuration of services
http://help.sap.com/erp2005_ehp_05/helpdata/en/3a/fe6eac579d4a9ead651d77
9a2dbd23/content.htm
http://sapehp5.blogspot.com/
20490 Views
Average User Rating
5
(6 ratings)
Tweet
Comments
13 Comments
Virag Shinde Jul 20, 2012 7:22 PM (in response to Siddharth Rajora)
Thanks Siddharth. I will update the document in line with the other blogs to make
sure we have the best solution possible.
Like (0)
Anuj Sharma Jan 14, 2013 4:41 PM (in response to Siddharth Rajora)
Hi Virag,
Its really good documnet for ESS with EHP 5, May you please light on MSS part also.
All above done and end user can use ESS but whats we have to do for MSS
configuration ...
Like (0)
This is most useful document for who are going to implement ESS module on EHP5.
Like (0)
Excellent Blog!
We are having EHP 6 .. want to ask you whether thr is much difference b/w EHP5 &
6. I am unable to find a good explanatory blog on EHP6.
Regards
Sahil Kohli
Like (0)
This is an excellent blog, in one single blog you have explained end to end, starting
from how to activate the switches, how to configure, customize the ESS apps.
Regards,
Yugandhar Reddy
Like (0)
Email Address
Website Address
Add Comment
Bottom of Form
Top of Form
Name (Required)
Website Address
Save
Bottom of Form
Top of Form
document.delete.
[placeholder]
Bottom of Form
Delete Document
Are you sure you want to delete this document?
Delete
Cancel
Actions
Stop tracking
Track in Communications
Incoming Links
Re: How to add table Column beside to another column
Upgrading to NW Portal 7.3 what to do with ESS/MSS?
Upgrading to NW Portal 7.3 what to do with ESS/MSS?
Re: Requiement : partial time entries should not allowed through ESS.
Re: LPD_cust text transport
Re: Header text change in Personal data screen ( ESS-WDA)
Follow SCN
Site Index
Contact Us
SAP Help Portal
Privacy
Terms of Use
Legal Disclosure
Copyright
Jive Software Version: 5.0.1.1 , revision:
201110261520.2c99f0c.release_jive_sbs_5_0_1_1