Business Package For Ess (Wda) 1.50

PRINT FROM SAP HELP PORTAL
Document:
Business Package for Employee Self-Service (WDA) 1.50
URL:
http://help.sap.com/erp2005_ehp_05/helpdata/en/25/340b0507434193adbfe3f8fc8896c7/frameset.htm
Date created:
August 19, 2013
2013 SAP AG or an SAP affiliate company. 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. Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors. National product specifications may vary. 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 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 other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information
and notices.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure.
Subtopics from other structures are not included.
The selected structure has more than 150 subtopics. This download contains only the first 150 subtopics. You
can manually download the missing subtopics.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Page 1 of 85

The Business Package for Employee Self-Service (WDA) 1.50 allows employees in your company to create, display, and change all employee-relevant data
themselves via the SAP NetWeaver Portal.
Technical Data
Availability
SAP ECC 6.0, SAP enhancement package 5 for SAP ERP 6.0
SAP NetWeaver 7.0
Data Source
SAP ERP Central Component (SAP ECC)
Browser Recommendation
For information about system prerequisites for these components, see the
Product Availability Matrix on SAP Service Marketplace at
service.sap.com/pam.
Languages Available
All languages available for SAP ERP 6.0.
Note that the individual country-specific services included in this business
package do not exist in all languages but rather in the language native to the
particular country.
Support
ESS Web Dynpro (CA-ESS-WD)
ESS based on Web Dynpro ABAP (PA-ESS-XX-WDA)
Prerequisites
You have determined your implementation strategy.
For more information, see the Master Guide for SAP ERP 6.0, SAP enhancement package 5. The Master Guide is located on SAP Service Marketplace at
www.service.sap.com/erp-inst Installation & Upgrade Guides SAP Business Suite Applications SAP ERP SAP ERP 6.0 SAP enhancement
packages for SAP ERP 6.0 SAP enhancement package 5 for SAP ERP 6.0 .
This business package uses objects from the Business Package for Common Parts therefore you need this business package. These shared objects are
listed in the Shared Objects in This Business Package section.
To use the Business Package for Employee Self-Service (WDA), you must have activated the following business function:
HCM, ESS on Web Dynpro ABAP
If you need the business package to enable Concurrent Employment (CE), you must additionally activate the following business function:
HCM, Time and Labor Management for Concurrent Employment (HCM_CE_PT)
The Employee Self-Service (WDA) role contains services from different functional areas, including services from non-EA-HR systems. These services will only
work if you have activated the required business functions for these services. The following business functions are a prerequisite if you want to have the full
functional scope of the services shipped in the standard ESS (WDA) role:
For services from HCM Processes and Forms (PA-AS): HCM, Administrative Services 03 (HCM_ASR_CI_3)
For services from Performance Management (PA-PD-PM):
CA, Appraisals, Evaluations, and Surveys 01 (CA_HAP_CI_1)
HCM, Performance Management 01 (HCM_OSA_CI_1)
HCM, Performance Management 02 (HCM_OSA_CI_2)
For services from Travel Management (FI-TV):
Travel Management 3(FIN_TRAVEL_3)
Travel Management, Third-Party Travel Planning 2(FIN_TRAVEL_PLANNING_EXTERNAL_2)
Travel Management, Enablement for Shared Services (FIN_SSC_TIC_1)
For services from Talent Management (PA-TM): HCM, Core Processes in Talent Management (HCM_TMC_CI_1)
For services from SAP E-Recruiting (PA-ER): HCM, SAP E-Recruiting 4 (HCM_ERC_CI_4)
For services from Self-Service Procurement (SRM-EBP-SHP): SRM, Self-Service Procurement (SRM_SELF_SERVICE_1)
For services from the E-Separation Solution for India: HCM, Localization Topics for India (HCM_LOC_CI_21)
Configuration
For information about configuration, see Configuration: Business Package for Employee Self-Service (WDA).
More Information
Release Note for the BP for Employee Self-Service (WDA) 1.50
Release Note for the BP for Employee Self-Service (WDA) 1.50
(New)
Technical Data
PUBLIC
Page 2 of 85
Product Version
SAP enhancement package 5 for SAP ERP 6.0
Area
EA-HR
Country Relevance
Valid for all countries

As of SAP ECC Enterprise Extension Human Capital Management 6.0 (EA-HR 600), SAP enhancement package 5 for SAP ERP 6.0, the Business Package for
Employee Self-Service (WDA) 1.50 is available for customers. This Business Package is based completely on the Web Dynpro for ABAP technology.
More Information
See the documentation for Employee Self-Service (WDA) in the SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com/erp SAP ERP
Enhancement Packages ERP Central Component Shared Services Employee Self-Service Employee Self-Service (WDA) .
Configuration: Business Package for Employee Self-Service
(WDA)

You use this function to make the required settings for integrating the Business Package for Employee Self-Service (WDA) into your portal and for its configuration.
Prerequisites
You have an overview of the required software components and the implementation strategy. For this, use the Master Guides and Installation Guides on SAP
Service Marketplace at service.sap.com/instguides.
To use the full range of functions of the Business Package for Employee Self-Service (WDA) 1.50, you must have installed the following:
SAP NetWeaver 7.0 with:
SAP NetWeaver Portal
Application Server ABAP
Adobe Document Services (ADS) (for HCM Processes and Forms)
Business packages:
Business Package for Common Parts
For more information, see Shared Objects in This Business Package.
SAP ERP Central Component (SAP ECC) 6.0 with SAP enhancement package 5 and Enterprise Extension Human Capital Management (EA-HR)
For information about the system prerequisites for these components, see the Product Availability Matrix (PAM) on SAP Service Marketplace at
service.sap.com/pam.
For information about the security settings for these components, see the appropriate Security Guide on SAP Service Marketplace at
service.sap.com/securityguide. In particular, note the Employee Self-Service chapter of the SAP ERP Central Component Security Guide under
Cross-Application Components Self-Services .
Activities
1. You set up the system landscape in the portal (see Setting Up the System Landscape).
2. In the configuration section of this documentation, make yourself familiar with the information given and perform all required settings and configuration steps
required for the Business Package for Employee Self-Service (WDA):
Roles in Employee Self-Service (WDA)
Single Roles for Employee Self-Service (WDA)
Assigning Roles for ESS (WDA) in SAP Portal
Configuration of the Role Menu for ESS (WDA) in SAP Portal
For this step, take also note of the following information:
Dynamic Rendering of the Menu (BAdI HRESS_MENU)
Application-to-Application Navigation Concept in Employee Self-Service
Object-Based Navigation for ESS (WDA) in the SAP Portal
Business Objects Used for OBN in the SAP Portal
For adjusting the delivered services for recording working time (CATS), requesting leave and the corresponding approval services, read the documentation
of the following sections carefully:
Leave Request
Services for CATS regular (Web Dynpro ABAP)
For adjusting the Personal Profile service, read the documentation of the following section carefully:
Configuration of Personal Profile Services
For creating your own reporting services, read the documentation of the following section carefully:
Note
Note
PUBLIC
Page 3 of 85
Configuration of Reporting Services
Make the Customizing settings that are required for the services that you intend to use in your customer-specific role. For more information, see the
documentation on the individual services under International Services and Country-Specific Services and Localizations.
The Customizing settings for Employee Self-Service (WDA) are only visible after you have activated the business function HCM, ESS on Web Dynpro ABAP.
You can find them in the SAP Customizing Implementation Guide under Personnel Management Employee Self-Service (WDA) .
Setting Up the System Landscape
Procedure
1. In the portal, create a Systems folder, if it does not already exist. Proceed as follows:
1. Choose System Administration System Configuration System Landscape .
2. Position your cursor on Portal Content and use the context menu (right mouse button) to create the new Systems folder.
2. Under the Systems directory, create an entry for the system, on which the software component SAP ECC Human Capital Management is installed. Proceed
as follows:
1. Using the context menu for the Systems folder, create a portal system (choose New System from Template ).
2. Use an SAP system with load balancing as a template.
3. Enter the name of the physical system (for example, XYZ000 for the system XYZ, client 000) as the name and ID.
4. Make your company-specific settings for the fields, using the following property categories:
Connector
Internet Transaction Server (ITS)
The relevant ITS path is: /sap/bc/gui/sap/its/webgui
Web Application Server (WAS)
5. Assign the system alias SAP_ECC_HumanResources.
6. If you also want to use services form SAP SRM Procurement or SAP E-Recruiting, also create the following system aliases in the same way:
Alias for SRM: SAP_SRM
Alias for E-Recruiting: SAP_EREC_TalentManagement
More Information
See System Landscape
Shared Objects in This Business Package

This business package uses objects from the Business Package of Common Parts. This business package is a prerequisite for using the Business Package
for Employee Self-Service (WDA).
Objects from the Business Package for Common Parts
Shared iViews
Title of the iView Technical Name Notes
iViews that are referenced from the launchpad
(ABAP)
In the same way as the Launchpad (ABAP) iView
from the Business Package for Common Parts, the
Overview iView in the Business Package for
Employee Self-Service (WDA)calls further iViews
from the Business Package for Common Parts
when the user chooses a link. For more information,
see Launchpad (ABAP).
Shared Business Objects
Title of Business Object Technical Name Use
Employee SAP_ERP_HumanResources.employee iView Appraisal Document
iView Appraisal Document
Display Form
More Information
Note
PUBLIC
Page 4 of 85
See the documentation for the relevant business package or packages on the SAP Developer Network (SDN) Web site at
www.sdn.sap.com/irj/sdn/developerareas/contentportfolio.

Roles are used in Employee Self-Service for different purposes:
Composite Role Employee Self-Service (WDA)
This role enables you to use the Employee Self-Service (WDA) role in SAP NetWeaver Business Client for HTML. It comprises single roles for ESS (WDA)
with the menu structure of all services available with ESS (WDA)
For more information see Composite Role Employee Self-Service (WDA)
Single Roles for Authorizations
Most of the single roles that are part of the composite role are used only for granting authorization rights for the services contained in these roles.
For more information, see Single Roles in Employee Self-Service (WDA)
Portal Role Employee Self-Service (WDA)
The Portal role enables you to use the Employee Self-Service (WDA) in the SAP NetWeaver Portal.
For more information, see Portal Role Employee Self-Service (WDA).
Composite Role Employee Self-Service (WDA)
Role: SAP_EMPLOYEE_ESS_WDA_1

The composite role contains the menu with all international and country-specific standard services for Employee Self-Service (WDA). Employees can use this role
to perform their tasks in SAP NetWeaver Business Client for HTML.
The composite role consists of a series of single roles that are primarily used for authorizations of the services contained therein. They also contain the menu
structure with the individual services since these services are not integrated directly into the composite role. The delivered composite role contains the following
single roles:
PUBLIC
Page 5 of 85
Role Name Use
SAP_EMPLOYEE_XX_ESS_WDA_1 ESS International Single Role Authorizations + menu for international ESS
services
SAP_EMPLOYEE_AU_ESS_WDA_1 ESS Single Role for Australia Authorizations + menu for country-specific ESS
services for Australia
SAP_EMPLOYEE_CA_ESS_WDA_1 ESS Single Role for Canada Authorizations + menu for country-specific ESS
services for Canada
SAP_EMPLOYEE_CH_ESS_WDA_1 ESS Single Role for Switzerland Authorizations + menu for country-specific ESS
services for Switzerland
SAP_EMPLOYEE_CN_ESS_WDA_1 ESS Single Role for China Authorizations + menu for country-specific ESS
services for China
SAP_EMPLOYEE_DE_ESS_WDA_1 ESS Single Role for Germany Authorizations + menu for country-specific ESS
services for Germany
SAP_EMPLOYEE_HK_ESS_WDA_1 ESS Single Role for Hong Kong Authorizations + menu for country-specific ESS
services for Hong Kong
SAP_EMPLOYEE_IN_ESS_WDA_1 ESS Single Role for India Authorizations + menu for country-specific ESS
services for India
SAP_EMPLOYEE_JP_ESS_WDA_1 ESS Single Role for Japan Authorizations + menu for country-specific ESS
services for Japan
SAP_EMPLOYEE_MY_ESS_WDA_1 ESS Single Role for Malaysia Authorizations + menu for country-specific ESS
services for Malaysia
SAP_EMPLOYEE_PT_ESS_WDA_1 ESS Single Role for Portugal Authorizations + menu for country-specific ESS
services for Portugal
SAP_EMPLOYEE_SG_ESS_WDA_1 ESS Single Role for Singapore Authorizations + menu for country-specific ESS
services for Singapore
SAP_EMPLOYEE_TH_ESS_WDA_1 ESS Single Role for Thailand Authorizations + menu for country-specific ESS
services for Thailand
SAP_EMPLOYEE_US_ESS_WDA_1 ESS Single Role for the United States Authorizations + menu for country-specific ESS
services for the USA
SAP_FI_TV_WEB_ESS_TRAVELER ESS Single Role for the Traveler Authorizations + menu for ESS services for the
traveler role
SAP_ASR_EMPLOYEE_SR_HCM_CI_3 ESS Single Role for HCM P&F Services Authorizations + menu for international ESS
services in the HCM Processes and Forms
application
SAP_PM_EMPLOYEE_HCM_CI_1 ESS Single Role for HCM PM Services Authorizations + menu for ESS services from the
Performance Management application
SAP_TMC_EMPLOYEE Employee in Talent Management Authorizations + menu for ESS services from the
Talent Management and Talent Development
application
SAP_EMPLOYEE_OTH_ESS_WDA_1 ESS Single Role Containing Non-EA-HR Services Menu structure for all services belonging to other
software components (SRM and SAP E-Recruiting).
The authorizations for these services are located in
the respective target system. This means that
employees that are to have access to these
systems must also be assigned to the single role
for authorizations necessary in the relevant system.
Also see: Single Roles for Employee Self-Service
(WDA)

The single roles are primarily used for authorizations for the services contained therein. They also contain the menu structure with the individual services since
these services are not integrated directly into the composite role.
PUBLIC
Page 6 of 85
Role Name Use
SAP_EMPLOYEE_XX_ESS_WDA_1 ESS International Single Role Authorizations + menu for international ESS
services
SAP_EMPLOYEE_AU_ESS_WDA_1 ESS Single Role for Australia Authorizations + menu for country-specific ESS
services for Australia
SAP_EMPLOYEE_CA_ESS_WDA_1 ESS Single Role for Canada Authorizations + menu for country-specific ESS
services for Canada
SAP_EMPLOYEE_CH_ESS_WDA_1 ESS Single Role for Switzerland Authorizations + menu for country-specific ESS
services for Switzerland
SAP_EMPLOYEE_CN_ESS_WDA_1 ESS Single Role for China Authorizations + menu for country-specific ESS
services for China
SAP_EMPLOYEE_DE_ESS_WDA_1 ESS Single Role for Germany Authorizations + menu for country-specific ESS
services for Germany
SAP_EMPLOYEE_HK_ESS_WDA_1 ESS Single Role for Hong Kong Authorizations + menu for country-specific ESS
services for Hong Kong
SAP_EMPLOYEE_IN_ESS_WDA_1 ESS Single Role for India Authorizations + menu for country-specific ESS
services for India
SAP_EMPLOYEE_JP_ESS_WDA_1 ESS Single Role for Japan Authorizations + menu for country-specific ESS
services for Japan
SAP_EMPLOYEE_MY_ESS_WDA_1 ESS Single Role for Malaysia Authorizations + menu for country-specific ESS
services for Malaysia
SAP_EMPLOYEE_PT_ESS_WDA_1 ESS Single Role for Portugal Authorizations + menu for country-specific ESS
services for Portugal
SAP_EMPLOYEE_SG_ESS_WDA_1 ESS Single Role for Singapore Authorizations + menu for country-specific ESS
services for Singapore
SAP_EMPLOYEE_TH_ESS_WDA_1 ESS Single Role for Thailand Authorizations + menu for country-specific ESS
services for Thailand
SAP_EMPLOYEE_US_ESS_WDA_1 ESS Single Role for the United States Authorizations + menu for country-specific ESS
services for the USA
SAP_FI_TV_WEB_ESS_TRAVELER ESS Single Role for the Traveler Authorizations + menu for ESS services for the
traveler role
SAP_ASR_EMPLOYEE_SR_HCM_CI_3 ESS Single Role for HCM P&F Services Authorizations + menu for international ESS
services from the HR Process and Forms
application
SAP_PM_EMPLOYEE_HCM_CI_1 ESS Single Role for HCM PM Services Authorizations + menu for ESS services from the
Performance Management application
SAP_TMC_EMPLOYEE Employee in Talent Management Authorizations + menu for ESS services from the
Talent Management and Talent Development
application
SAP_EMPLOYEE_OTH_ESS_WDA_1 ESS Single Role Containing Non-EA-HR Services Menu structure for all services belonging to other
software components (SRM and E-Recruiting). The
authorizations for these services are located in the
respective target system (see also the last two
table entries).
SAP_TIME_MGR_XX_ESS_WDA_1 Time Approval Role for ESS Authorizations for line managers in Manager Self-
Service for services used to approve leave
requests and working times from Employee Self-
Service (WDA).
SAP_RCF_ESS_SR_ERC_CI_4 E-Recruiting services for ESS (WDA) Authorizations in SAP E-Recruiting for employees
that use SAP E-Recruiting services in ESS (WDA).
/SAPSRM/EMPLOYEE_ESS SAP SRM Employee for ESS Authorizations in SAP SRM for employees that use
services from Purchasing in ESS (WDA).
Apart from the last three single roles in the table, all authorization relevant single roles are part of the composite role Employee Self-Service (WDA)
(SAP_EMPLOYEE_ESS_WDA_1).
The Time Approval Role for Leave requests and Time Sheet changes from ESS has to be assigned to Managers in Manager Self-Service (it is part of the
composite role SAP_Manager_MSS_NWBC).
The single roles for SAP E-Recruiting and SAP SRM Procurement services are in the SAP E-Recruiting and SAP SRM systems respectively. This means
that employees that are to have access to these systems and services must also be assigned to the single role for authorizations necessary in the relevant
system.
Note
PUBLIC
Page 7 of 85
Assigning Roles for ESS (WDA) in SAP Portal
Prerequisites
The following prerequisites have to be met:
You have created the users in the portal.
An assignment exists between users in the portal and the back-end system (for example, ERP system). For more information, see User Mapping.
Procedure
1. For using the Business Package ESS (WDA) role, assign the following roles to each portal user:
Employee Self-Service (com.sap.pct.erp.ess.wda.Employee_Self_Service_WDA)
Additionally, if you use SRM and would like the ESS users to access SRM applications in SAP Portal, assign the SRM role Employee Self Services
(EhP1 -ESS) (com.sap.pct.srm.core.ro_employeeselfservice)
2. In the backend system, assign to the corresponding backend user the single roles required for authorizations, also see Single Roles for Employee Self-Service
(WDA).
If you assign the ESS composite role, all authorizations that are in the authorization profiles of the single roles can be assigned in one step.
More Information

In this section you find information about how the role menu in the FPM Launchpad Configuration Repository (transaction LPD_CUST) is configured for the SAP
NetWeaver Portal role Employee Self-Service (WDA).
Features
For the Launchpad menu, the following technical objects are relevant:
Application HRESS_A_MENU with Overview Pattern Configuration (OVP) HRESS_AC_MENU
Component Configuration HRESS_CC_MENU_AREA_GROUP which has been created for the FPM Launchpad component FPM_LAUNCHPAD_UIBB.
Component Configuration HRESS_CC_MENU_AREA_GROUP which points to the following:
Launchpad configuration Role: ESS and Instance: MENU for menu rendering.
Launchpad configuration Role: ESS and Instance: RELATED_LINKS for the Related Links section in the Business Package for Employee Self-Service
(WDA).
Feeder Class CL_HRESS_LPD_MENU which is used to modify the menu at runtime based on BAdI implementations of HRESS_MENU.
Also see Dynamic Rendering of the Menu (BAdI HRESS_MENU).
Activities
In Customizing for Employee Self-Service (Web Dynpro ABAP), make the required settings under General Settings ESS Menu for Services Menu for SAP
Portal Role .
This Customizing activity calls up transaction LPD_CUST, where you can find the delivered Launchpad configurations Role: ESS and Instance: MENU and
Instance: RELATED_LINKS.
As soon as you access the delivered configurations in editing mode, the system automatically creates a copy of the launchpad configuration that you can change
according to your requirements:
You can create your own applications directly under the copied folders as required. Or you can subdivide the launchpad further by creating additional folders.
In the portal, the folders are used as headers for the links to the applications.
You can create an additional folder by selecting the folder under which you want to create the new one. Choose New Folder and enter a text for the new folder.
When you choose Enter, the new folder is inserted under the selected folder.
You can create applications by selecting the folder under which you want to create them. Choose New Application. and select the Application Category.
Depending on this selection, other input fields are displayed with which you can define or select the parameters of the application.
Note
Note
Note
PUBLIC
Page 8 of 85
If the field System Alias is displayed when you choose the application category, you have to enter a system alias. The folder Inactive Applications is used
to collect the applications that should be available in the SAP NetWeaver Portal, but not directly visible in the role menu. These applications are displayed
in the Portal in a table that the user can view when changing the launchpad settings.
You can enter (or change an existing) a description to be displayed in the SAP NetWeaver Portal under the link to the application. To do so, choose for the
folder or the application in your launchpad menu, once you have selected it with your cursor, on the right hand side Editor for the Description.
More Information
Launchpad
Create a Launchpad with Applications
Include a Launchpad in the User Interface
Change Launchpad
Employee Self-Services Menu (Application HRESS_A_MENU)

Technical Data
Web Dynpro Application HRESS_A_MENU
Web Dynpro Application Package PAOC_ESS_CENTRAL_SERVICES
Application Configuration HRESS_AC_MENU
Web Dynpro Components FPM_OVP_COMPONENT
Component Configurations HRESS_CC_MENU_OVP,
HRESS_CC_MENU_AREA_GROUP
Application Component Controller FPM_LAUNCHPAD_UIBB
Software Component for Web Dynpro Application EA-HRRXX
Support PA-ESS-XX-WDA
Availability SAP enhancement package 5 for SAP ERP 6.0
Required Business Function HCM_ESS_WDA_1
This technical application is used to display the menu created for Employee Self-Service (WDA) in the FPM launchpad repository (transaction LPD_CUST as the
role menu displayed for role com.sap.pct.erp.ess.wda.Employee_Self_Service_WDA in the Business Package for Employee Self-Service (WDA).
This application allows a much easier and quicker configuration of the SAP Portal role menu in the backend system. Apart from that, there is also the option to
dynamically change the services at runtime:
With BAdI HRESS_MENU, you can hide particular folders for employees for example based on their role, job, and country.
For more information, see Dynamic Rendering of the Menu (BAdI HRESS_MENU).
Integration
This application makes use of the FPM Launchpad Framework for Web Dynpro ABAP to display the menu structure. The Launchpad allows you to organize
applications, thereby providing your employees easy access to Web applications (services) that run in the SAP NetWeaver Portal.
OBN Navigation in the Menu:
Launchpad offers the flexibility to configure the first level navigation as an application or as an OBN.
For applications that are not a part of the EA-HR software component like applications from SRM and SAP E-Recruiting, the applications are launched via OBN
navigation in the standard delivery.
For these applications, the following setting is required for the launchpad menu:
1. In Edit mode, choose Extras General Settings .
2. Under OBN Navigation Mode, select User Set of Roles.
In the standard delivery this is set to active. This means that when an OBN is launched it searches for all the roles that are assigned to the Portal user before the
OBN Navigation is resolved. So when an application for example from SRM is launched, it checks for all the assigned roles of the user in the Portal and resolves
the OBN target. The SRM application is only resolved if the ESS-specific SRM single role has been assigned to the user in the SAP NetWeaver Portal.
For more information see Object-Based Navigation for ESS (WDA) in the SAP Portal.
Features
In the standard shipment, Launchpad Role: ESS and Instance: MENU is used to render the ESS menu. It has the following three views:
1. Map View with all Folders /Subfolders and all applications within it
2. Directory - View with all Folders /Subfolders
3. Index View where users can search for a specific service or obtain a specific list of services in alphabetical order.
Apart from these views, the application HRESS_A_MENU also has the following features:
The Most Frequently Used application which is populated based on the users hits to applications.
Both the administrator and the end user have the option to hide this section. When an administrator hides this section via configuring the OVP application, this
setting is applicable to the entire organization.
The Related Links menu: The administrator can configure a specific Role and Instance in the Launchpad repository in order to list applications here. In the
standard shipment this is blank and is configured to point to Role: ESS and Instance: RELATED_LINKS
PUBLIC
Page 9 of 85
Launchpad also offers the following basic functions:
Add short descriptions for the individual services that will appear on the user interface
Edit the link texts of the hyperlinks that the employees use to start the services
Emphasize certain services (for example, because there is an urgent deadline)
Deactivate services
Prerequisites
The Launchpad customizing Role = ESS and Instance = MENU needs to be available in the client from where the ESS menu is being displayed.
The Launchpad customizing Role = ESS and Instance = RELATED_LINKS needs to be available in the client from where the ESS menu is being displayed for
the section Related Links to work in the Business Package for Employee Self-Service (WDA).
Configuration
You can access the Launchpad transaction in the SAP Customizing Implementation Guide under Personnel Management Employee Self-Service (Web
Dynpro ABAP) General Settings ESS Menu for Services Menu for SAP Portal Role Setup Launchpad (Employee Services) .
The structure of a launchpad pages group and describe the different services and contain hyperlinks with which they can be started. In the standard ESS Menu
shipment the Role ESS and Instance MENU is what is configured to be displayed.
Administrators can change the Role and Instance that should be used by changing the Menu UIBB (User Interface Building Block)
HRESS_CC_MENU_AREA_GROUP configuration specified in the ESS menu application.
Role Configuration
A role that is displayed via the Service Map View or Directory View can also be described as an area group. From a technical point of view, it has a
hierarchical/tree structure, see also the following example:
Area Group Folder
Area Folder 1
Subarea Folder 1
Service 1
Service 2
Service 3
Subarea Folder 2
Service 4
Service 5
Area Folder 2
Subarea Folder 3
Service 6
Subarea Folder 4
Service 7
Service 8
Subarea Folder 5
Service 9
Area Folder 3
Subarea Folder 6
Service 10
Service 11
Service 12
Service 13
Area Group Folders
Area group folders contain descriptions of areas, hyperlinks to access the areas, and hyperlinks to start services directly.
Area Folders
Area folders contain services that are related to each other. Employees access an area folder from an area group folder.
Subarea Folders
Areas and subareas can be compared to headings and subheadings in a document. You use subareas to group the services that belong to an area on the
screen.
Services
Inside the subarea folder, you define the services that are to appear on the area folders. For each service you define a hyperlink and a short description that will
appear in the related area folder.
Employees use this link to start the service. You can make numerous settings to define where and how the hyperlink to the service will appear.
You can define several area group folders under one header. You can define this header in the launchpad framework.
Activities
We recommend you make a graphical design of the areas and services you want to implement. This way, the hierarchical relations between these elements will
become apparent.
If you have copied the Menu applications configurations to your own namespace, ensure that the Application Component Controller's (AppCC) component and
configuration name are the same as the copied UIBBs Component Configuration.
Example
Note
PUBLIC
Page 10 of 85
More Information
Launchpad
Create a Launchpad with Applications
Include a Launchpad in the User Interface
Change Launchpad
Dynamic Rendering of the Menu (BAdI HRESS_MENU)

The HRESS_MENU Business Add-In allows you to dynamically change the properties of the services in the ESS menu (enabled/disabled, visible/invisible,
application parameters etc.) based on your business requirements.
Features
Figure 1: BAdI HRESS_MENU Adapting the Menus of Both Role Repositories
The HRESS_MENU BAdI is used to dynamically adapt the menus from both role repositories for ESS (WDA):
1. The Report Launchpad for the SAP Portal Role ESS (WDA):
When the launchpad-based menu is rendered, it calls the associated feeder class. In the standard delivery, the feeder class CL_HRESS_LPD_MENU is called
by default.
Feeder class CL_HRESS_LPD_MENU calls the BAdI implementations of HRESS_MENU with filter value 'COUNTRY_FILTER'.
Feeder class CL_HRESS_LPD_MENU calls the BAdI implementations of HRESS_MENU with filter value 'Application Alias' that can be maintained for each
application in the menu maintenance (transaction LPD_CUST under Advanced Parameters Application-Related Parameters .
2. SAP NetWeaver Role Maintenance for ESS (WDA) in NWBC:
When the PFCG based menu is rendered, it checks for the implementations of HRESS_NWBC_MENU_EXT. In the standard delivery, the BAdI implementation
HRESS_NWBC_MENU_EXT exists. This implementation has Role Name as a filter value. When a role that has been specified in the filter is launched, the BAdI
implementation proceeds as follows:
The BAdI implementation HRESS_NWBC_MENU_EXT calls the BAdI implementations of HRESS_MENU with the COUNTRY_FILTER filter value.
The BAdI implementation HRESS_NWBC_MENU_EXT calls the BAdI implementations of HRESS_MENU with the Application Alias filter value that can
be maintained for each application in the menu maintenance (transaction PFCG under Other Node Details.
In the standard delivery, the HRESS_COUNTRY_FILTER implementation is active and is called by default in both the exits. This implementation checks the
COUNTRYGROUPING parameter in the application and if the user accessing the menu belongs to a different country (has a different MOLGA), it sets the application
to invisible. With this standard implementation, country-specific services are only visible to employees belonging to the respective countries.
More Information
Also see the documentation of the HRESS_MENU BAdI in the backend system (by calling up the BAdI in the BAdI Builder (transaction SE18) or in the SAP
Customizing Implementation Guide under Personnel Management Employee Self-Service (Web Dynpro ABAP) General Settings ESS Menu for Services
and then either under Menu for SAP Portal Role or Menu for SAP NetWeaver Business Client for HTML BAdI: Specify Dynamic Rendering of Services .
PUBLIC
Page 11 of 85
Application-to-Application Navigation Concept in Employee Self-
Service (WDA)

There are three basic types of application-to-application navigation in Employee Self-Service (WDA):
1. Direct call of a Web Dynpro ABAP application in a new Window
2. Launchpad-defined call of a Web Dynpro ABAP application
3. Launchpad-defined call based on Object Based Navigation (OBN)
Launchpad-defined means that you define this navigation via transaction LPD_CUST for the services contained in the Launchpad for your Portal role.
Which of these navigation types is used is internally handled within each application. For more information, see the individual service documentation for
Employee Self-Service (WDA).
Prerequisites
In the case of OBN-based call (type 3), the Business Objects used in the call have to be present in the different Business Object repositories, the Business
Object Repository (BOR) in the backend system and the business objects and methods in the SAP NetWeaver Portal Catalog in case of NWBC and SAP Portal.
More Information
Object-Based Navigation for ESS (WDA) in SAP NWBC

Object-Based Navigation (OBN) is used for the navigation within the Employee Self-Service role in the SAP NetWeaver Portal, also see Object-Based Navigation:
Overview.
Integration
The Business Package for Employee Self-Services (WDA) uses business objects from the Business Package for Common Parts for navigation, also see
Business Objects Used for OBN in the SAP Portal.
Prerequisites
The required Business Objects for OBN have to exist in the Business Objects repository.
Features
Figure 1: OBN Elements for ESS (WDA) in SAP NetWeaver Portal
Note
PUBLIC
Page 12 of 85
The SAP NetWeaver Portal Role Employee Self-Service (com.sap.pct.erp.ess.wda.Employee_Self_Service_WDA) also contains the target application (called
application) that needs to be launched in case of an OBN call by a specific application (calling application). These OBN-based applications (called applications)
are iViews contained in the Navigation Services folder.
These iViews are associated to the method call of the Employee Business Object. The calling application generally defines OBN-based settings via a
Launchpad Role/Instance where settings such as the System Alias (i.e. the target system) and where to search for the OBN object (User Set of Roles or Source
Role) can be defined.
The OBN targets are associated with iViews in the Portal Employee Self-Service role. The Business Package for Employee Self-Service (WDA) uses the
following iViews for navigation:
Appraisal Document (com.sap.pct.erp.ess.wda.Appraisal_Document)
Appraisal Document (com.sap.pct.erp.ess.wda.Appraisal_Document_PMP)
Display Form com.sap.pct.erp.ess.wda.Display_Form
More Information

In this section you can find the business objects that are necessary for the Object-Based Navigation (OBN) for Employee Self-Service (WDA) role in the SAP
NetWeaver Portal.
Features
The Business Package for Employee Self-Services (WDA) uses business objects from the Business Package for Common Parts for navigation, see also the
following table.
OBN Objects for ESS (WDA) Portal Role
Name Technical Name Object Type
Employee SAP_ERP_HumanResources.employee Business Object
Appraisal Document (PMP) appraisal_document_pmp Operation
Appraisal Document (WD UI) appraisal_document_wd_ui Operation
Appraisal Document Overview (PMP) appraisal_doc_overview_pmp Operation
assess assess Operation
compare compare Operation
Display display Operation
Display Attachment display_attachment Operation
Display Compensation Approval compensation_approval Operation
Display Compensation Comparison compensation_comparison Operation
Display Compensation Planning compensation_planning Operation
Display Compensation Profile compensation_profile Operation
Display Form display_form Operation
Display Form for Manager display_form_manager Operation
Display Long Profile display_long_profile Operation
Edit Development Plan edit_dev_plan Operation
Edit ESS Profile edit_ess_profile Operation
Leave Request

This function enables you to control the processing of leave requests and other absences. The function comprises the entire leave request process. The process
starts with the creation of a leave request and the processing of it, before it is finally posted to the backend system.
The interfaces used by employees and managers when they process leave requests are Web Dynpro applications that belong to Employee Self-Service (ESS)
and Manager Self-Service (MSS).
Prerequisites
You have integrated the Web applications with the relevant portal pages. For more information, see the Business Package for Manager Self-Service (MSS).
PUBLIC
Page 13 of 85
You have set up the Web application in Customizing. For more information, see Customizing under Personnel Management Employee Self-Service (Web
Dynpro ABAP) Service-Specific Settings Working Time Leave Request.
You have made the following settings in the Communication infotype (0105) for all employees:
You have specified the system user name in subtype 0001 (System User Name SAP System (SY-UNAME)).
You have stored the e-mail address in the subtype 0010 (E-Mail).
Features
The Leave Request function comprises the following areas:
Creation of leave request by employee
Forwarding of request to manager for approval
Controlling the deletion and cancellation processes
Status tracking and monitoring
Posting of absences to the backend system
Running reports and test applications to control processes and the database
The Leave Request application comprises the following services that are tailored to the needs of employees and managers and provide practical contextual
information:
Create Leave Request: The service for employees who want to request, change, or cancel leave.
You can use this function only if your employees enter their own leave requests in Employee Self-Service (Web Dynpro ABAP). It is not suitable if you have
time administrators who record absences.
Leave Overview: The service for employees who want to display their leave requests, and review, change, or cancel existing leave or other types of
absences.
Approve Leave Request: The service for managers who want to approve the leave requests.
You do not have to implement this Web Dynpro application. Alternatively, you can use a simple backend report.
Your employees can use the Leave Request service to request both absences (infotype 2001) and attendances (infotype 2002). This means that you can also
process records of the Attendances infotype (2002) that have the quality of an absence in your company, such as training courses.
The Leave Request application has automatic control of the processing process. You can make Customizing settings for groups of employees to control
aspects such as:
Which absence and attendance types employees are permitted to request.
The periods before and after an absence during which employees are permitted to request leave in advance or retroactively. You can define different periods
for different absence/attendance types.
The actions an employee is permitted to carry out. For example, you can specify whether an employee is permitted to change or delete an absence that has
already been approved.
Several reports are available in the backend system to control the processing. The reports send e-mails to employees to notify them of the status of their leave
request. Approvers and time administrators are notified of leave requests that they have to process.
You can schedule the reports as a periodic background process. If you want to use SAP Business Workflow, the same reports are processed with the
corresponding workflow tasks. For more information about the workflow, see General Workflow for Documents.
You can use Business Add-Ins (BAdIs) to customize the application to suit your requirements. For example, they enable you to adjust the processing process
to suit your needs, or import and change data.
Processing Leave Requests

You use this process to process leave requests.
Prerequisites
You have scheduled background processing for the required reports or have provided suitable variants of the reports for your time administrators and approvers.
For more information, see Customizing under Personnel Management Employee Self-Service (Web Dynpro ABAP) Service-Specific Settings Working Time
Leave Request Processing Processes Define Report Variants and Background Processing .
Process
Below is an example of the process when an employee requests leave. Processes involving changing and canceling leave or deleting a request that has not
been approved are largely similar.
1. An employee wants to take two weeks of leave. He or she accesses the Leave Request Web application. He or she sees in the Team Calendar that other
team members also have leave at the same time.
Nonetheless, he or she requests leave for the planned period. The leave requires approval. The system automatically determines the approver responsible
and lists the name in the Web application. If required, the employee can overwrite the name of the approver.
Note
Note
Note
PUBLIC
Page 14 of 85
The following process steps can, but do not have to be integrated with SAP Business Workflow. The reports and functions are available for both procedures.
For more information about the workflow, see General Workflow for Documents.
2. The employees request is stored in the database of leave requests with the status Sent.
Once a day, the Leave Requests: Send E-Mailsreport (RPTARQEMAIL) is run in the background. The system sends an e-mail to the appropriate approver for
the requests with status Sent that require approval. The e-mail notifies the approver of the steps required.
3. The approver accesses the Approve Leave Requests service from the personal object worklist (POWL). The application provides the approver with a list of all
the leave requests that require his or her approval.
4. The approver selects the employees leave request. After checking the Team Calendar, the approver realizes that the employees leave request cannot be
approved since it would mean there would not be enough team members at work for the period in question.
The approver writes a note in which he or she states why the request has been rejected. He or she then rejects the request.
5. The RPTARQEMAIL report sends an e-mail to the employee notifying him or her that the request was rejected. The employee accesses the Leave Request
service. He or she selects the request in the Absence Overview. He or she sees in the note the reason why the request was rejected.
6. The employee looks at the Team Calendar and finds a period in which no other team members are on vacation. He or she changes the period of the request.
The employee specifies the change in period in the note.
7. The RPTARQEMAIL notifies the approver of the request by e-mail. This time the approver can approve the request.
8. The request receives the status Approved in the database. The RPTARQEMAIL report sends an e-mail to the employee notifying him or her that the request
was approved.
9. The system processes the requests further according to their status:
1. The RPTARQPOST report (Leave Requests: Post) writes all requests in the database that have the status Approved to the Absences (2001) or
Attendances (2002) infotype.
2. The system may not be able to post the requests to the infotypes if, for example, they collide with other infotype records. These requests are given the
status With Errors.
The RPTARQEMAIL report sends an e-mail to the relevant time administrator to notify him or her that the requests were unable to be posted.
3. The time administrator accesses the RPTARQERR report (Leave Request: Process Posting Errors). It lists the requests with errors.
4. The time administrator analyzes the error situation in the backend system.
If he or she can solve the cause of the problem and save the data record in the infotype, he or she uses the RPTARQERR report to set the request to
Posted.
If the problem cannot be solved, because the employee has other commitments at the time, for example, the time administrator rejects the request.
10. The RPTARQEMAIL report sends an e-mail to the employee notifying him or her of the change in status of the request.
Evaluating Authorizations

In an absence request, employees personal data is protected using a special function.
Features
In an absence request, the system ensures that personal data is protected before displaying it by first querying whether it is the requester or approver of an
absence request asking to display the data. However, in certain conditions, other employees are also able to see this data.
Generally, the data is read for internal processing without an authorization check. If someone wants to display the data, the system checks whether that person is
the requester or approver, both of whom are allowed to see the entered data. If neither the requester nor the approver are trying to display the data, an authorization
check is performed. Data is displayed depending on the following factors:
If the employee does not have proper authorization, such as read authorization, no data is displayed.
If you have deactivated authorization checks in Customizing for this rule group, the data is displayed in an anonymized form.
If the employee has at least read authorization, the data is displayed.
Maintaining the Database and Testing

Various reports are available to give you a complete overview of the relevant data so that you can process and manage requests easily. These reports thereby
provide you with support during the implementation and test phase.
You can access the reports and tables listed below in transaction PTARQ (Test Environment for Leave Request). This transaction enables you to access
quickly the tools you need during the implementation and test phase. Note that the transaction is primarily intended for SAP-internal use and is not officially
part of the standard system offering.
Features
You can use the following reports, tools, and system tables. For more information about the reports, see the corresponding report documentation.
Reports for Controlling Processing
RPTARQEMAIL (Send E-Mails)
RPTARQPOST (Leave Requests: Post)
Note
PUBLIC
Page 15 of 85
RPTARQSTOPWF (Leave Requests: Complete Current Workflows)
RPTARQLIST (Leave Requests: Check)
RPTARQAPP (Leave Requests: Approve Documents)
RPTARQMASS_APPROVAL (Leave Requests: Mass Approval)
RPTARQERR (Leave Requests: Process Posting Errors)
Reports for Testing Customizing Settings
RPTREQWEBMO (Determine Rule Group). You can use this report to determine the most important organizational assignments for individual employees or
organizational units that are to be evaluated in the Web application.
RPTREQAPPRCHK (Determine Approver). You can use this report to check whether the system determines an employee's supervisor correctly.
Reports for Displaying and Maintaining the Database
RPTARQDBVIEW (Display Leave Requests (Database of Requests) You can use this report to view all information relating to the leave requests that have
been entered.
RPTARQDBVIEW (Delete Leave Requests (Database of Requests) You can use this report to remove out-of-date requests from the database.
System Tables
The following tables are SAP tables. You must not make any changes to them. If you do, the process of leave requests may no longer function as it is
supposed to.
PTREQ_STATUS_CHK (Check Methods for Status Transitions)
PTREQ_STATUS_TRA (Status Transitions)
V_PTREQ_TYPE (Document Type)
Test Programs
The test programs RPTARQUIATEST (Test Report for the UIA Interface for Leave Requests) and RPTARQAPTEST (Test Report for the UIA Area Pages for
Leave Requests) enable you to test processing in the backend system. You can use it to simulate the entry of leave requests in the Web application.
The test program should be used only in test systems; you must not use it in your production system.
Data Origin of Time Accounts
Use
Depending on the business processes you use to manage your employee's time data, you can display information from time accounts of various different data
sources.
Features
The Web application enables you to output time accounts from the following sources:
The Attendance Quotas infotype (2007)
The Absence Quotasinfotype (2006)
Absence quotas and time types as time evaluation results from cluster B2.
The transparent table PTQUODED (Deduction of Time Quotas)
Data from the request database: depending on the Customizing settings, you can include leave requests that have not yet been approved when you calculate
the remaining absence entitlement.
Data from the Leave Entitlement infotype (0005)
The BAdI uses the function module HR_GET_QUOTA_DATA to determine the time accounts. The BAdI PT_ABS_REQ (Enhancements for Leave Requests)
enables you to read this function module with particular parameters. In the standard implementation of the BAdI, the system determines time accounts as follows:
It reads attendance quotas from the Attendance Quotas infotype (2007).
Absence quotas
For employees who do participate in Time Evaluation (Time Management Status unequal to 0 in the Planned Working Time infotype (0007).
Up to the Retroactive Accounting Date BDE (Payroll Status infotype (0003)): absence quota data from cluster B2 if the key date is later than this date.
For times after the Retroactive Accounting Date BDE: data from the Absence Quotas infotype (2006) if the key date is later than the retroactive accounting
date.
If the cluster table has not been filled because you have not implemented the QUOTA function: absence quota data from the Absence Quotas infotype (2006).
For employees who do not participate in Time Evaluation (Time Management Status equal to 0 in the Planned Working Time infotpye (0007)), the system
reads absence quota data from the Absence Quotas infotype (2006).
If you want to display Time Types from the cluster or data from the Leave Entitlement infotype (0005), you can use other methods of the BAdI PT_ABS_REQ
(Enhancements for Leave Requests)to provide data for this Web application. For more information, see the documentation on the BAdI.
If you use Time Evaluation, employees can also check the leave entitlement they can expect in the future. To do this, employees enter a key date in the future.
Time Evaluation simulates the entitlement that can be expected on this key date. This function is particularly useful if at your company you periodically accrue
Caution
Caution
PUBLIC
Page 16 of 85
leave entitlement according to the time that employees have worked.
For more information, see Simulation and Projection of Time Evaluation Results.

Services for CATS regular (Web Dynpro ABAP)

Employees can use the Record Working Time service to access the CATS regular (Web Dynpro ABAP) application. The explanatory text displayed on the
Working Time screen is dynamically created, and provides information and the status for recorded working times.
This function enables employees to determine whether they have recorded sufficient working times. Consequently, employees often do not need to access the
application itself to check the status of the working time they have recorded.
There is also a service in Manager Self-Service for the approval of working times. For more information, see Approve Time Sheet.
Example: Recording Working Times

Record working times
Peter Miller is a field service employee who wants to record his working times. He accesses the company intranet and selects the Web application Record
Working Time. He then enters the attendance or absence type, the sender and receiver cost centers, and the number of hours he worked. To assist him with
entering this information, he can use either the default values proposed or the search function.
Saving working times
He saves the recorded working times. At the end of the week, Peter wants to check the working times he has recorded before he releases them to be checked by
his personnel officer.
Saving and releasing working times for approval
At the end of the week, Peter wants to release his data for approval. He first checks the working times he has already recorded and completes any data that may
be missing. He then releases the working times.
Approval rejected
Peter has entered an incorrect cost center. Therefore, Peter's personnel officer does not approve his working times. The next time Peter accesses the Web
application for the Time Sheet, he will see that the rejected hours are highlighted in color. He corrects the cost center and releases the working times again for
approval.
Approval granted
Peters personnel officer approves the corrected data. The data is written to the interface tables ready for transfer to the target components.
Default Values for Sender Cost Center and Activity Type

In certain Time Sheet user interfaces, you can fill the working time attributes SKOSTL (Sender Cost Center) and LSTAR (Activity Type) with default values from
different sources.
If in Customizing the option Assignment of personnel costs to receiver object is selected in the Cost Assignment Variant group box for the data entry profile
used, you cannot use default values for the sender cost center and activity type.
Integration
You can use default values in the following user interfaces of the Cross-Application Time Sheet:
CATS classic
CATS regular (ITS)
CATS regular (Web-Dynpro)
Record Working Time
The Time Sheet Defaults infotype (0315) is optional. However, if you transfer data from the Time Sheet to the External Services component (MM-SRV), you must
create the Time Sheet Defaults infotype (0315).
Note
Caution
PUBLIC
Page 17 of 85
Features
In contrast to personal templates, which enable you to prefill the data entry area when you start time recording, the system first displays default values when you
create a new account assignment row with one receiver object and at least one working time:
To display the default values in CATS classic, select after you have created an account assignment row.
To display the default values in CATS regular, check your entries after you have created the account assignment row.
This is correct, because it does not make sense to provide default values for the sender cost center and activity type if you are only entering an attendance
or absence type.
The system only proposes default values when you create a new account assignment row. If you want default values to be proposed when you change an account
assignment row, or if you copy data from the worklist, use the SAP enhancement CATS0002 (
Supplement Recorded Data).The system can take the default values from sources with different priorities. If default values exist that are from different sources, the
system uses the following order:
1. Time Sheet Defaults infotype (0315)
2. Organizational Assignment (0001)
3. Work Center or Activity
4. SAP enhancement CATS0002 (Supplement Recorded Data)
Activities
If required, create the Time Sheet Defaults infotype (0315) for your employees.
Make the following settings in Customizing for the data entry profiles you need in the default values group box.
To take the default values for sender cost center and activity type from the Time Sheet Defaults infotype (0315), set the Cost Center and Activity Type
indicators.
To take the default value for the sender cost center from the Organizational Assignment infotype (0001), select Master cost center instead of Cost center. If
you select both indicators, the system uses the cost center stored in the Time Sheet Defaults infotype (0315) for the default values.
More Information
In Customizing, you can store derivation values for specific working time attributes (for example, activity type or wage type) for each task level that you define for a
combination of task type and task component. You can make this setting in the Implementation Guide (IMG), under Cross-Application Components Time
Sheet Settings for All User Interfaces Time Recording Specify Task Types, Components, and Levels.
The Business Add-In (BAdI) CATS_DERIVATIVES enables you to make changes to these derivation values. You can find this BAdI in the Implementation Guide
(IMG), under Cross-Application Components Time Sheet Settings for All User Interfaces SAP Enhancements and Business Add-Ins BAdI: Change
Derived Values .
Worklist
Definition
Screen area in the data entry view of the time sheet. In the worklist you can display data, which the user can copy to simplify data entry.
Use
You can display a worklist in a separate section of the single entry screen if you have created the relevant
data entry profiles in Customizing. The worklist contains employee-specific and object-related information. This information is only available if you are
maintaining the time sheet for one employee using single entry.
Structure
The worklist can contain the following information:
Data that the employee has already entered in the time sheet
Data from SAP Logistics:
Resource planning (capacity splits)
Confirmation pools
Activities assigned to the employee based on his or her work center assignment
Data created using the SAP enhancement CATS0001 (Set Up Worklist) or using the Business Add-In (BAdI) CATS_WORKLIST_ADDIN, which is displayed
in the form of a customer-specific worklist.
You define the content of the worklist and fields displayed in it when you maintain profiles in Customizing.
Using the copy function, the user can copy data from the worklist to the data entry section, and overwrite it if required.
Depending on the type of data (from planning, for example), hours can also be copied. You can deactivate this function by deselecting Copy without hours when
you maintain your profiles.

Note
PUBLIC
Page 18 of 85
Creation of Personal Templates

You can save account assignment rows entered in the data entry area as a personal template. Each time you start the application and when you go to a different
data entry period, the account assignment rows are displayed in the data entry period. Therefore, you only need to enter your working times. This means that you
do not have to reenter the same working time attributes in every data entry period.
This function is not available for working time attributes that are objects from the cProjects application.
This function is not available when time recordings are displayed using the vertical list view.
Integration
This function is available in the following user interfaces of the Cross-Application Time Sheet:
CATS classic
CATS regular
A similar function is available in the Mobile Time Sheet..
You can use the standard Template for the Time Sheet program (RCATSTMP) to define any personal template that was already saved for a user, as the standard
template. You can create a separate standard template for each data entry profile. The system uses the standard templates for users who have not saved a
personal template or who have deleted their saved template.
For more information, see the report documentation.
Features
You can create a personal template for each combination of user and data entry profile, and you can delete it at any time. The system does not save personal
templates in relation to a personnel number, which means that users who record working times for several personnel numbers can use their personal
templates for all personnel numbers. Therefore you cannot use this function for data entry profiles intended for time recording for multiple personnel numbers.
You can decide for each data entry profile whether you want to enable users to create personal templates.
The system saves all visible working time attributes of rows in which at least one field is ready for input as part of the personal template.
This function is linked with the user maintenance function:
- When you copy a user, any existing personal templates are also copied.
- When you delete a user, the personal templates are also deleted.
The system can merge account assignment rows belonging to a personal template with other account assignment rows. For more information, see Sorting and
Merging of Account Assignment Rows.
Activities
Choose the Save as template button on the data entry screen to save the displayed account assignment rows as a personal template.
Choose Delete template on the data entry screen to delete an existing personal template.
For CATS regular (Web Dynpro), choose the Delete button to delete an existing personal template. Alternatively, you can navigate to an empty data screen and
choose the Save as template button-this action deletes the existing personal template and overwrites it with a new one.
Creation of Personal Favorites

Employees can use this function to manage their timesheet data in the CATS regular (Web Dynpro ABAP) user interface.
Features
You can create a personal favorite for each combination of user and data entry profile, which is valid for users who can record data for multiple data entry profiles.
Employees can use this function to do the following:
Save a favorite with or without times
Mark a favorite without times as their default favorite, which works like a personal template
Import one or more favorites at the same time to their timesheet. Even if an employee imports a combination of favorites both with and without times, the system
first imports those with times, performs a consistency check, and then imports those without times. When employees import a favorite, the time period
displayed in the table is automatically filled.
Organize their favorites by changing the name, changing the default favorite, or deleting a favorite at any time. Employees cannot change the content of a
favorite, and can have one default favorite at any point in time.
Note
Note
PUBLIC
Page 19 of 85
Sorting and Merging of Account Assignment Rows

When you call up a data entry period for which you have already entered working time, the system sorts the existing account assignment rows. Furthermore, the
system merges account assignment rows containing identical working time attributes, providing that the working times entered permit it.
Features
Data is displayed in a vertical list view or a horizontal list view, depending on your Customizing settings
The system sorts the account assignment rows in ascending order according to the date and time for which they were entered.
The system checks whether there are rows containing identical account assignment information that could be merged (see the example).
If you have saved a personal template and then call up a data entry period for which you have already entered working times, the system acts as follows:
- It merges the account assignment rows entered and the rows of the personal template if the account assignment information in them is identical.
- It displays the account assignment rows that belong to the personal template in a block in the upper part of the data entry area. The sequence of these
account assignment rows corresponds to the original sequence in which you saved the account assignment rows in your personal template.
- Underneath the account assignment rows that belong to your personal template, the system displays the account assignment rows that cannot be merged with
those in your personal template, and sorts them in ascending order by the date and time for which they were entered.
Copy and Insert into Timesheet

Employees use this function to copy their clock times from the previous time recording period to their current timesheet, and to perform the following activities:
Copy Line-copy a complete line and paste it to a new location in the timesheet
Copy from Previous Period-copy clock times from a previous period to the current timesheet
Copy from Target Hours-copy their planned hours to the timesheet
Insert Row-insert additional rows in the timesheet by selecting a row and choosing the Insert Row button. A new row is inserted below the selected row, and
employees must choose the Check button to validate their entries.
Import from Work Schedule

Employees use this function in HR-Enabled CATS to copy their weekly, bi-weekly, and daily work schedules to the timesheet, which overwrites existing data.
Features
If an employees work and break schedules are fixed, they can use this function to copy information directly to their timesheet, by choosing the Work Schedule
button. The Work Schedule button is visible only if employees use HR-Enabled CATS and if there are clock times in the timesheet. Employees cannot import a
work schedule if the timesheet does not include clock times.
The following information is copied from the work schedule:
Date
Daily Schedule
Planned Working Hours
Start Time
End Time
Break Duration
Break Start Time
Break End Time
Unpaid/paid break
Breaks are shown as a gap between two blocks of planned working time. For example, if a planned working time from 08:00 to 17:00 includes a break from
12:00 to 13:00, the timesheet shows two entries-one from 08:00 to 12:00, and the second from 13:00 to 17:00. Displaying the work schedule in the timesheet
does not affect the calculation of the employees target hours.
Example: Merging of Account Assignment Rows
The following graphic illustrates how the system merges account assignment rows:
PUBLIC
Page 20 of 85

The example illustrates the weekly data entry period from October 14 through October 20. It is assumed that October 19 and 20 (Saturday and Sunday) are
days off. Therefore, they are not shown in the example.
Scenario 1: Rows can be merged
1. You enter three account assignment rows for the data entry period October 14 through 20. The account assignment information is identical in the first and third
rows.
2. In the first account assignment row, you enter three hours for October 14 and five hours for October 16.
3. In the third account assignment row, you enter four hours for October 15.
4. You exit time recording and call up the data entry period again.
5. The system sorts the account assignment rows in ascending order according to the date and time for which they were entered.
6. The system checks whether the account assignment rows can be merged:
a. It determines that the account assignment information is identical in the first and third rows.
b. It checks whether the fields that are filled with working times in the first account assignment row are blank in the third row. This is the case.
c. It checks whether the fields that are filled with working times in the third account assignment row are blank in the first row. This is the case.
The system merges the first and third account assignment rows into one.
Scenario 2: Rows cannot be merged
1. You enter three account assignment rows for the data entry period October 14 through 20. The account assignment information is identical in the first and third
rows.
2. In the first account assignment row, you enter three hours for October 14, two hours for October 15, and five hours for October 16.
3. In the third account assignment row, you enter four hours for October 15.
4. You exit time recording and call up the data entry period again.
5. The system sorts the account assignment rows in ascending order according to the date and time for which they were entered.
6. The system checks whether the account assignment rows can be merged:
a. It determines that the account assignment information is identical in the first and third rows.
b. It checks whether the fields that are filled with working times in the first account assignment row are blank in the third row. This is not the case.
You have entered working times for October 15 in both account assignment rows. The system does not add the two values because there may be different
cell information (such as the processing status or follow-on documents) linked to them, which would be lost if the rows were merged. For more information, see
Follow-On Documents and Outstanding Postings.
The system cannot merge the account assignment rows.

Customizing Settings for Data Entry Profiles

This function enables you to provide your employees with a data entry view that is tailored to their area of activity and that fulfils your business requirements. When
employees record working times, they call the time sheet by specifying a data entry profile. The profile determines the data entry process and the layout of the
time sheet.
To create a data entry profile, you must make the following settings in Customizing:
Set Up Data Entry Profiles
The Customizing activities you use for setting up data entry profiles depends on the user interface you use. You can make the necessary settings for the
appropriate user interface in Customizing, under Cross-Application Components Time Sheet .
Select Fields
In Customizing, using transaction code CAC2, you can determine which fields are displayed for each data entry profile .
PUBLIC
Page 21 of 85
Features
Profile maintenance
The views that are visible in the CATS application depend on the periods selected during Customizing. The following settings for data entry profiles are
available in Customizing, using transaction code CAC1:
Display Option
Enables the horizontal or vertical view of the timesheet.
HR Enabled CATS
Enables HR features in the CATS application.
Public Holiday Type
Configures the public holiday default type.
Time-Recording Cut-off Date
This parameter is applicable only for the HR-Enabled CATS application. You use it to set the cut-off date for time recording, which is set to payroll period end
date by default. You can use BAdI: Calendar Display for Recording Working Times (HRESS_CATS_CAL_DISPLAY) to change the default time-recording
cut-off date.
For more information, see Customizing for HR-Enabled CATS under Employee Self-Service (Web Dynpro ABAP) Service-Specific Settings Working
Time Record Working Time Record Working Time .
Before you define a data entry profile, you must consider the following:
Do you want the data entry profile to provide a daily, weekly, or monthly data entry view?
Do your employees record their own working times or are they recorded centrally, for example in a data entry office?
Do you want to set up a separate release and approval procedure for the recorded data? If you choose to use an approval procedure, do you want to use
SAP Business Workflow?
Which profile authorization group do you want the data entry profile to belong to?
Profile authorization groups enable you to set up authorizations for the Time Sheet. You use authorizations to determine which data entry profiles a user
can use for which personnel numbers. For more information, see: Assignment of Authorizations for the Time Sheet
If you implement HR Payroll, which receiver object do you want to post the personnel costs to?
Do you want to simplify data entry for the user by providing default values and a worklist?
For more information about default values for CATS classic, CATS regular, and CATS for service providers see: Default Values for Sender Cost Center
and Activity Type.
Once you have answered these questions, you can create the data entry profiles you require. In addition to the options described above, other options are
available that enable you to modify the time sheet layout to suit your requirements, and increase ease of use for users.
For example, you can choose whether users record their working times as a number of hours or with start and end times.
If you enter your working times with clock times, the system calculates the exact number of hours for you. You can only change the clock times on which
the calculation was based, and not the actual calculated hours. This is also the case if you change a data record that you entered with clock times in a
different data entry profile in which no fields are available for clock times. In this case, the system does not allow you to change the number of hours
calculated because it administrates the clock times in a background task. If necessary, change the clock times on which the calculation is based.
Field selection
Users enter different information when recording their working times according to their area of activity. For this reason, you should provide your various employee
groups with different fields on the data entry screen.
An employee who confirms a maintenance order requires different fields on the data entry screen to an employee who only records attendances and
absences for Human Resources. You control which fields appear for a particular user using the data entry profile he or she uses to call the time sheet,
because you define an individual field selection for each data entry profile.
Recording Working Times for Concurrent Employment

If you implement the concurrent employment functions, you can greatly simplify time recording for your employees with multiple personnel assignments. To do
this, several time sheet functions are available to you for each personnel assignment, as opposed to each user.
Prerequisites
You have implemented the functions for concurrent employment for your Employee Self-Service applications.
You have activated the HCM, ESS for Concurrent Employment/Global Employment (HCM_ESS_CE) business function.
Note
Note
Note
Example
PUBLIC
Page 22 of 85
Features
When calling up the application, concurrently employed persons can now select the personnel assignment for which they would like to record working times.
For more information, see the description of functions for concurrently employed persons in the business packages for Employee Self-Service.
You can use the HRCATS_PROFILE_BY_PERNR Business Add-In to generate data entry profiles on the personnel assignment level. In the standard system,
the system can only assign profiles for a particular user.
You can use the HRCATS_TEMPLATE_BY_PERNR Business Add-In to enable your concurrently employed persons save personal templates for each
personnel assignment and data entry profile.
For more information on the BAdIs, see Customizing under Personnel Management Employee Self-Service (Web Dynpro ABAP) Service-Specific
Settings Working Time Record Working Time Record Working Time Record Working Time for Concurrent Employment.
Configuration of Personal Profile Services

The configuration information for Personal Profile services within the Web Dynpro for ABAP version of Employee Self-Service is divided into the following sections:
Application Composition
This section gives you an overview of the main elements of a Personal Profile service.
Concept Introduction
This section contains information about the Business Object Layer (BOL) model, Generic User Interface Building Blocks (GUIBBs), feeder classes, and
application component configurations.
Configuration
This section contains specific information about the individual configuration options for the Personal Profile application.
Process
The standard Personal Profile services delivered by SAP can be modified by customers to suit their business needs.
To do this, proceed as follows:
1. Familiarize yourself with the UI technology Web Dynpro ABAP.
2. Build up your knowledge of the SAP Floorplan Manager. For more information, see Floorplan Manager for Web Dynpro ABAP.
3. Build up your knowledge of the Business Object Layer model (see Concept Introduction).
4. Execute the necessary configuration steps.
Application Composition of Personal Profile Services

This section informs you about the main elements which a Personal Profile service in Employee Self-Service (and based on Web Dynpro ABAP) consists of.
Structure
Note
PUBLIC
Page 23 of 85
Figure 1: Component Encapsulation with GUIBBs
Figure 1 shows the encapsulation of several Web Dynpro components within one Web Dynpro Application Personal Profile service. The OVP component
configuration that the Personal Profile application configuration uses is HRESS_CC_PER_OVP. It consists of the following configurations:
1. The initial screen contains the WD component HRESS_C_PERNR_SELECTION and its interface view PERNR_SELECTION_MAIN.
2. The main screen summarizes the employees information in the form of business cards (biz cards). The GUIBB for the biz cards is implemented using the
feeder class CL_HRESS_PER_OVERVIEW.
3. Each of the main screens has a corresponding edit page. Edit pages are implemented using the feeder class CL_HRESS_PER_DETAIL.
Concept Introduction
Business Object Layer (BOL)

The Business Object Layer (BOL) model is a programming concept that allows for uniform application development, decoupled from interface changes in the
underlying business-object-specific Application Programming Interfaces (APIs).
HRPAD BOL Model
The Personal Profile application uses the HRPAD BOL model. You can view the BOL model via transaction GENIL_MODEL_BROWSER.
Structure
The root object is PERNR. This contains the dependent object(s) from a 0..n relationship.
The BOL model follows a three level hierarchy: PERNR > ITNNNN_REL > ITNNNN_NN_REL.
IT_NNNN_REL represents HCMT_BSP_PA_XX_R<NNNN>(international structures).
ITNNNN_NN_REL represents HCMT_BSP_PA_R<NNNN> (country-specific structure).
If you add a new relation, you must follow this hierarchy.
It is not mandatory for an infotype to have the relation ITNNNN_NN_REL.
Each infotype is identified via the HRPAD_S_MAIN_RECORD_KEY key structure and the HCMT_BSP_PA_XX_R_NNNN attribute structure if it has an international
view. For infotypes that have only one single country-specific structure, it would follow the HCMT_BSP_PA_NN_R_<NNNN> structure. Each infotype contains the
country-specific infotype as its dependent object through a 0..n relationship if it has country-specific structures.
PERNR
Note
Example
PUBLIC
Page 24 of 85
IT0004_REL 0..n
IT0006_REL 0..n
All infotypes are represented as dependent objects (for example IT0006) with relation names in the IT0006_REL format. Each dependent object has
an international XX structure (for example HCM_BSP_PA_XX_R0006) to provide an overview of the data stored in the infotype.
IT0006_NN
The dependent object has an abstract child, such as IT0006_NN.
IT0006_43
IT0006_41
IT0006_37
The abstract object has country-specific child objects that use the country-specific attribute structures.
Use the HRPAD_R_EDIT_MODEL report to add infotypes to the HRPAD model. For more information, see Customizing for Employee Self-Services (WDA) under
Service-Specific Settings Personal Information Personal Profile Adjust Infotypes in HRPAD Model .
Generic Interaction Layer (GenIL)

The Generic Interaction Layer (GenIL) is a layer connecting the Business Object Layer (BOL) model HRPAD to the HCM database table.

The GenIL class used in the Personal Profile application is CL_HRPAD_IL. This class implements the BOL component model HRPAD. It uses the Application
Programming Interfaces (APIs) of the ESS adapter CL_HRPA_PERNR_INFTY_XSS to perform all Create/Read/Update/Delete (CRUD) operations on the Human
Capital Management (HCM) data objects in the database.
For more information, see Adapter.
Do not make modifications to the GenIL class provided in the standard delivery
XSS Adapter

The Employee Self-Service or XSS adapter is accessed by the Generic Interaction Layer (GenIL) class CL_HRPAD_IL.

The XSS adapter used in the Personal Profile application is CL_HRPA_PERNR_INFTY_XSS. The class performs Create/Read/Update/Delete (CRUD) operations
on the Human Capital Management (HCM) data objects in the database. A single instance of this class is maintained for a specific PERNR and infotype.
For more information, see Generic Interaction Layer (GenIL).
The adapter returns data only for those infotypes and subtypes that have been maintained in table V_T7XSSPERSUBTY. For more information, see
Customizing for Employee Self-Service (WDA) under Service-specific Settings Personal Information Personal Profile Determine Active Subtypes and
Make Settings .
Generic User Interface Building Block (GUIBB)

Generic User Interface Building Blocks (GUIBBs) are design templates, for which the application, at design time, defines the data to be displayed along with a
configuration. The concrete display of the data on the user interface is not determined and generated by the GUIBB until runtime. Thus, GUIBBs enable a form and
list rendering mechanism.

The GUIBBs are provided by the Floorplan Manager (FPM) framework and used in the Personal Profile application for overview screens or business cards (biz
cards) and detail screens. Each biz card and detail screen consists of at least one GUIBB. A GUIBB is a reusable Web Dynpro component.
In order to facilitate the consumption of the Business Object Layer (BOL) through GUIBBs, FPM framework provides standard interfaces such as
IF_FPM_FEEDER_MODEL, IF_FPM_GUIBB_LIST and IF_FPM_GUIBB_FORM. For information on how to implement the feeder classes that can be used in
form and list GUIBBs, see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver SAP NetWeaver by Key
Capability Application Platform by Key Capability ABAP Technology UI Technology WEB UI Technology Floorplan Manager for Web Dynpro ABAP
The SAP standard delivery contains CL_HRESS_PER_OVERVIEW and CL_HRESS_PER_DETAIL feeder classes for overview and detail screen implementations
Note
Note
Note
PUBLIC
Page 25 of 85
of the Personal Profile application. For more information, see Feeder Class.
In the documentation for the configuration of Personal Profile Services, the GUIBB is generically referred to as a User Interface Building Block (UIBB).
Feeder Class

A feeder class is a class which supplies data to the User Interface Building Block (UIBB), handles its actions, and provides it with a screen structure.

There are primarily two feeder classes that are used by the Personal Profile application:
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. The usage of this
feeder class ensures the following:
Biz cards have the correct Create, Edit and Delete buttons based on the use case maintained in table V_T7XSSPERSUBTYP.
Data Sharing Information is displayed on the biz cards. For more information, see Data Sharing Information.
The grouping text in the biz card is displayed.
Grouping texts are based on infotype and subtype texts. In the case of concurrent employment, the grouping text additionally contains the Data Sharing
Information.
The appropriate header is transferred to be displayed on the detail screen.
For more information, see class documentation for CL_HRESS_PER_OVERVIEW.
CL_HRESS_PER_DETAIL
This feeder class is used to configure detail screens of the Personal Profile application. Using this feeder class ensures the following:
The dropdown list for the Foreign Address scenario is available.
Data Sharing Information is displayed on the detail screen. For more information, see Data Sharing Information.
F4 help, dropdown lists and dependent value helps are available.
For more information, see class documentation for CL_HRESS_PER_DETAIL.
Further feeder classes
There are other standard feeder classes available. These are found under the package PAOC_ESS_PER_WDA.
Overview Pattern (OVP)

The Overview Pattern (OVP) is a floorplan from the Floorplan Manager (FPM) framework. It consists of a main screen and an edit page.
Structure
A main screen or edit page contains User Interface Building Blocks (UIBBs). There can be only one page of type Main Screen. Each UIBB in the Main Screen is
a biz card and will have a corresponding edit page or detail screen. The detail screen is contained in an Edit Page. The main screen, in the case of thePersonal
Profile application, is also called the overview screen or business card (biz card). The navigation from the main screen to the edit page is the result of the
destination content area, which is specified in the Main Screen UIBB configuration.
Wiring

A wire is created in an Overview Pattern (OVP) configuration to specify the data transfer mechanism. It primarily contains the following:
The transaction class
The destination screen where data needs to be transferred.
The source screen from where the data is transferred.
The connector class used to transfer the data.
The parameters to be used by the connector class.
The way a data record is to be identified (for example LEAD SELECTION).
Transaction Class
The transaction behavior for the Personal Profile application is the result of the CL_HRESS_TRANSACTION transaction class. This class is called by the
Overview Pattern (OVP) configuration on execution of any of the standard Create/Read/Update/Delete (CRUD) FPM events.
Connector Class
A connector class is responsible for transferring data across User Interface Building Blocks (UIBBs) in the FPM OVP. In the Personal Profile application, the
Note
PUBLIC
Page 26 of 85
following connector classes are used to communicate between the different UIBBs:
CL_HRESS_CONNECTOR_PER_OVR
This connector is used to transfer data from the initial screen to an overview screen or biz card UIBB.
CL_HRESS_CONNECTOR_IDENTITY
This connector is used to transfer data from the overview screen UIBBs to the detail screen UIBBs in the case that both, overview screen and detail screen use
objects from Business Object Layer (BOL) model nodes at the same level. This connector is also used to transfer data from the detail screen UIBB to the
validity section UIBB. For more information, see Validity Section in Detail Screens.
CL_HRESS_CONNECTOR_RELATION
This connector is used to transfer data from the overview screen UIBBs to detail screen UIBBs in the case the detail screen uses the object from the BOL
model which is one level lower to the object used by the overview screen.
For more information, see class documentation.
More Information
Dynamic Wiring
Application Configuration Controller (AppCC)

An Application Configuration Controller (AppCC) is a Web Dynpro component which is used to perform dynamic operations on an application; there are occasions
when static configuration of an application is not sufficient to achieve the desired application behavior.

In case of Personal Profile application, the AppCC is primarily used to configure and control which User Interface Building Blocks (UIBBs) or Edit screens are to
be hidden or replaced for the particular target users. The application loads appropriate screens at runtime, based on the settings in the AppCC. For example, the
way an application behaves for employees in different countries is determined by the AppCC.
More Information
Maintaining the Application Configuration Controller (AppCC)
Application Exit via AppCC BAdI
AppCC Component HRESS_C_PERSINFO_CONFIG

This Web Dynpro component is an Application Configuration Controller (AppCC) component for the Employee Self-Service (ESS) Personal Profile application.
The Personal Profile application calls this Web Dynpro component before rendering. This component performs the following modifications to the Personal Profile
application depending on the maintained configuration.
Dynamic Screen Modification Based on Action Configuration
The different actions which could be performed on a particular User Interface Building Block (UIBB) are the following:
Hide
Do Not Hide
Replace
Replace Tabbed Overview
For the description of the actions see Maintaining the Application Configuration Controller (AppCC).
Application Title Handling
Overview Screen Title Handling
In systems where Concurrent Employment (CE) is not activated, the overview screen title would be the same as the title maintained in the content area property
TITLE. In a CE system the current accessed assignment is appended with the title maintained as content area property for the overview screen. This helps
ESS users to know which assignment is being processed.
Detail Screen Title Handling
The detail screen title is entirely controlled by the AppCC. The title maintained as content area property in the detail UIBB is completely ignored. The standard
customizing for the infotype or subtype text maintenance forms a part of this title which could be maintained to achieve a specific title.
For more information, see Application Title Handling.
Dynamic Wire Creation
The component performs dynamic wire maintenance in the following ways:
Overview navigation wires
Detail navigation wires
Level zero wires
Composite overview UIBB wires
For the description of the options for dynamic wire creation, see Dynamic Wiring.
PUBLIC
Page 27 of 85
Relationships
The component delegates its configuration maintenance view to the HRESS_C_PERSINFO_CONFIG_C component.
The component implements the IF_FPM_OVP_CONF_EXIT interface to make changes to the FPM OVP Personal Profile application.
Component Configuration HRESS_CC_PER_OVP

The Personal Profile application is HRESS_A_PERSINFO. The corresponding application configuration is HRESS_AC_PERSINFO. For the Overview Pattern
(OVP) configuration, this application configuration uses HRESS_CC_PER_OVP.
Structure
This OVP application contains the following configurations:
Initial Screen with INITIAL_SCREEN Id
It contains the User Interface Building Block (UIBB) that uses Component HRESS_C_PERNR_SELECTION and View PERNR_SELECTION_MAIN.
Main screen content area OVERVIEW_SCREEN
It contains the international screen UIBBs for the services Personal Data (Infotype 0002), Addresses (Infotype 0006), Bank Details (Infotype 0009), Family
Members /Dependents (Infotype 0021), Offica Data (Infotype 0032) and Communication (Infotype 0105).
Edit screen content area
Each of the Main screens has a corresponding Edit screen content area which contains the detail screen UIBBs for the above mentioned services.
For transferring the data across the UIBBs, wires are created. For more information, see Wiring.
When introducing a new infotype to the OVP configuration, refer one of the infotype UIBBs in the OVP Configuration HRESS_CC_PER_OVP.
Configuration

You can configure which configuration blocks or edit screens to be displayed, hidden or replaced for the particular target users by maintaining the Application
Configuration Controller (AppCC) configuration. Based on the (AppCC) configuration the application will load the appropriate screens at runtime.
An application exit can be maintained in the application configuration via Application Configuration Global Settings. The Personal Profile application implements
AppCC using the HRESS_C_PERSINFO_CONFIG component and its standard configuration HRESS_CC_PER_CONFIG.
For more information, see AppCC Component HRESS_C_PERSINFO_CONFIG.
The AppCC performs dynamic operation on UIBBs based on the keys configured.
Via 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 Russia (country version 33).
Key Configuration
Key maintenance is divided into two groups:
Mandatory Key Group
Country Version
This is the country grouping or MOLGA for which the dynamic operation on the user interface building block (UIBB) is expected.
Configuration Key
The availability of the configuration key depends on the implementation of the Business Add-In (BAdI) HRESS_PER_CONFIG_KEY. Configuration requesting
to use this key must implement this BAdI and set its filter as Web Dynpro component configuration ID values in advance. This will automatically activate the
usage of the configuration key as soon as the configuration is started. For more information, see Application Exit via AppCC BAdI.
By default, the configuration key is disabled.
Possible value set:
Note
Note
Note
PUBLIC
Page 28 of 85
The configuration must contain any of the two keys or both. Possible values for this are:
Country Version
Configuration Key
Country Version and Configuration Key
Optional Key Group
Optional Keys are configured by selecting the checkbox UIBBs Based on Infotype/Subtype. This feature is needed when some dynamic UIBB activity is
expected at particular infotype or subtype access. The use of the keys Infotype and Subtype is completely optional.
Possible value set:
Infotype
Infotype and Subtype
All possible combination from value sets of both groups could form a key
UIBB Configuration
The action configuration is available as a part of the UIBB configuration placed as child node for the key configuration. The following action configurations are
available:
Hide
You use this option to hide a UIBB for a particular key or key combination.
The infotype Bank Information (0009) should not be shown in the case of Russia. An entry has to be made in the AppCC with value 33 for the country
version and infotype 0009 with option Hide to hide the standard UIBB in the overview pattern (OVP).
Unhide
You use this option to show a UIBB for a particular key or key combination. This option is used for business cases where a standard UIBB in the OVP needs to
be hidden in all key or key combinations except a few.
The infotype 0182 needs to be shown only for Singapore (country version 25). In such a case the standard UIBB in the OVP has to be specified as Hide
for country version 99 and for country version 25 this UIBB has to be specified as Unhide.
Replace
You use this option to replace a UIBB for a particular key or key combination. This is the most common scenario.
Replace Tabbed Overview
You use this option in combination with the Replace option in case of Tabbed Overview replacement. The composite UIBB content is maintained separately in
this option for correct wiring maintenance within tabbed UIBB.
More Information
Application Configuration Controller (AppCC)
Dynamic Wiring

The Application Configuration Controller (AppCC) allows you to configure the replacement of user interface building blocks (UIBB). Replacing a UIBB also involves
creating relevant wires to be in place for proper data transfer. For more information, see Wiring.
The AppCC framework does this automatically for the maintained replacement entry.
Features
Automatic Dynamic Wire creation happens for the following use cases:
Overview Navigation Wires
If an overview screen replacement is requested in the AppCC configuration, then a fresh wire with a new UIBB destination is created based on the existing
source UIBB wiring.
Detail Navigation Wires
If a detail screen replacement is requested in the AppCC configuration, then a fresh wire with a new UIBB destination is created based on the existing source
UIBB wiring.
Level Zero Wires
The AppCC framework also checks for wires which could be connecting UIBBs belonging to the same page. In case of both - overview and detail UIBB
replacement request - a fresh wire with a new UIBB source or destination is created.
Composite Overview UIBB Wires
In case of a composite overview UIBB replacement, the AppCC framework also handles wiring for the content of composite UIBBs. This is achieved in the
AppCC by a special entry called Replace Tabbed Overview. This entry refers to the new UIBB content which is valid with the new Tabbed Overview
replacement maintained as a general replacement entry. This kind of entry is required for proper wire creation within the composite UIBB content.
Example
Example
PUBLIC
Page 29 of 85
Application Exit via AppCC BAdI

For every Application Configuration Controller (AppCC) component configuration you can create an associated Business Add-In (BAdI) implementation. The filter
key for the BAdI is the AppCC component configuration name. The implementation informs the configurator what the generic key is going to be and how it has to
be interpreted.
Features
The BADI interface IF_HRESS_EX_PER_CONFIG_KEY contains the following methods:
READ_TEXT_FOR_IMPLE
This method returns the text that the configurator displays for generic key.
GET_CONFIG_KEY
This method returns the appropriate key value for a particular PERNR.
For more information, see BAdI documentation.
Activities
To implement the BAdI, execute the activity in Customizing for Employee Self-Service under Service-Specific Settings Personal Information Personal
Profile Customizing of Personal Profile Screens BAdI: Determine Customer-Specific Key Screen Replacement .
Personalization

For Personal Profile application the following personalization options are available:
Implicit Personalization
All the implicit personalization options supported by Web Dynpro ABAP such as hiding fields, setting default values to the input fields are available to the end
user.
These personalization changes are stored in the system until the administrator or the employee clears the personalization.
Additionally, the following personalization options are also available to the end user of the application:
Drag and drop the information blocks (business cards or biz cards) in the Personal Profile page
Employees can drag an information block to drop it to the desired location in the Personal Profile Page.
Re-arranging the information blocks (biz cards) in the Personal Profile page
Employees can choose the Edit button in the toolbar to personalize the information blocks. Employees can hide and change the location and layout of the
information blocks.
For more information, see also Changing the Layout of the Personal Profile Page.
Changing the Layout of the Personal Profile Page

The Personal Profile Page layout can be changed as follows:
Configuration change
This allows for changing the arrangement of UIBBs in the Overview Pattern (OVP) configuration. This layout change is applicable to all users of the system and
all the clients.
Customization
The administrator of the application can run the application in administration mode and change the arrangement of the biz cards, hide the fields, and so on.
These changes are applicable to all users at client level.
In the application, the user can change the arrangement of the business cards (biz cards), hide the fields, and so on. This is applicable only at the user level. For
more information, see Personalization.
Customizing the Fields in Overview Screens

Every overview screen or business card (biz card) in the Personal Profile page exists as a configuration of the CL_HRESS_PER_OVERVIEW feeder class.
There are two ways to change the layout of a biz card:
Note
PUBLIC
Page 30 of 85
Creating a new configuration using the CL_HRESS_PER_OVERVIEW feeder class
Copying and later changing an existing configuration
Activities
In order to customize the biz cards, you have to execute the following steps:
1. Create a new configuration using the CL_HRESS_PER_OVERVIEW feeder class, or copy an existing configuration and change the layout as required.
2. In the configurator, the edit and delete buttons need to be added by default. You may refer to HRESS_CC_PER_OVR_BANK_XX configuration as an example.
You should not add any of the create buttons that appear in the configurator.
3. In order to make the newly created configuration available as a part of the application, specify in the Application Configuration Controller (AppCC) configuration
the new User Interface Building Block (UIBB) as a replacement to the existing UIBB present in the overview pattern (OVP) application configuration.
More Information
Customizing the Detail Screen

Each detail screen in the Edit Page Content Area exists as a configuration of the CL_HRESS_PER_DETAIL feeder class along with the validity User Interface
Building Block (UIBB).
Activities
In order to customize the detail screen, you have to execute the following steps:
1. Create a new configuration using the CL_HRESS_PER_DETAIL feeder class or copy an existing configuration and change the layout.
2. In order to make the newly created configuration available as a part of the application, specify in the Application Configuration Controller (AppCC) the new User
Interface Building Block (UIBB) as a replacement to the existing UIBB present in the Overview Pattern (OVP) application configuration.
The SAP-specific view V_T7XSSPERBIZFLD and the customer-specific view V_T7XSSPERBIZFLC are no longer used to customize business cards.
Do not replace the Addresses business card (biz card) by a country-specific biz card. This would result in loss of data on the screen, specifically in
cases where a foreign address is maintained by an employee. Using the international biz card ensures that all the applicable address data is available
in the overview screen.
Introducing a New Infotype

If an infotype is not part of the Personal Profile application, you have to create new User Interface Building Block (UIBB) configurations for the overview screen and
the detail screen. These have to be included in the HRESS_CC_PER_OVP component configuration. This component configuration exists within the standard
application configuration HRESS_AC_PERSINFO.
Introducing a new infotype comprises the following activities:
Adopt the Business Object Layer (BOL) model HRPAD
Add the new infotype to the overview pattern (OVP)
Adopting the BOL Model
Execute the following steps:
1. If the BOL model HRPAD does not include a specific infotype, enhance it by using the HRPAD_R_EDIT_MODEL program. You execute this step in
Customizing for Employee Self-Services under Service-Specific Settings Personal Information Personal Profile Adjust Infotypes in HRPAD Model .
2. You may have to lock the changes done via the report and release them to the other systems in your landscape.
For more information on the BOL model see Business Object Layer (BOL).
Add a new Infotype to the OVP
Execute the following steps:
1. Create appropriate Floorplan Manager (FPM) Generic User Interface Building Block (GUIBB) configurations. Use the following standard feeder classes and
components:
For the overview screen, use the CL_HRESS_PER_OVERVIEW feeder class
For the detail screen, use the CL_HRESS_PER_DETAIL feeder class
For the validity section, use the HRESS_C_VALIDITY component
The standard classes and components are available in the PAOC_ESS_PER_WDA package.
2. Change the FPM Overview Pattern (OVP) configuration to include the biz card in the main page and include the detail screen in a new edit page.
3. Add the validity UIBB in the edit page.
4. Specify the target page in the overview UIBB as the newly created page for the detail screen.
Caution
PUBLIC
Page 31 of 85
5. Add a wire with the overview screen UIBB as the destination using the CL_HRESS_CONNECTOR_PER_OVR connector class.
6. Add a wire with the detail screen UIBB as the destination, and the overview screen UIBB as the source using one of the following connector classes:
CL_FPM_CONNECTOR_BOL_IDENTITY
CL_FPM_CONNECTOR_BOL_RELATION
7. Add a wire with the validity section UIBB as the destination and the detail screen UIBB as the source using the CL_FPM_CONNECTOR_BOL_IDENTITY
connector class. Refer one of the infotype UIBBs in the OVP configuration HRESS_CC_PER_OVP as an example to do steps 2 through 7.
8. Change the AppCC configuration in case you want newly introduced infotypes to appear for specific countries only. For more information, see Application
Configuration Controller (AppCC).
More Information
Wiring
Enabling Specific Features
Concurrent Employment Scenario

If an employee who has multiple personnel assignments, accesses a service from the Personal Profile application, he is prompted to select an assignment for
which he wants to view or maintain his personal data. As per the selection, the employee can view or maintain his data for the specific assignment.
In case of Concurrent Employment, some of the personal data stored in infotypes may be valid for a specific assignment. Once the user has selected a personnel
assignment, on the Personal Profile page and edit screen, the validity of the information with respect to the assignment is shown in both, the overview and detail
screen. For more information, see Validity Section in Detail Screen.
Concurrent Employment Dialog Box
An Initial screen is the first screen to be loaded when the application is started. A central Web Dynpro component, HRESS_C_PERNR_SELECTION, is available
to handle the Concurrent Employment related dialog box. This central component provides an interface view, PERNR_SELECTION_MAIN, which you can include
as the initial screen user interface building block (UIBB) in your applications.
In order to use this service, include the PERNR_SELECTION_MAIN interface view of the HRESS_C_PERNR_SELECTION component n the applications
configuration (component configuration) as initial screen UIBB.
The Web Dynpro component provides the dialog box view, which is raised in case of Concurrent Employment. The initial screen launches the dialog box for an
employee with multiple assignments.
In the standard delivery of the Personal Profile application the initial screen has been included by default.
Countryfilter
This parameter is used in the Concurrent Employment scenario to filter out assignments belonging to a specific country. Setting this parameter to a specific
country ensures that in the Concurrent Employment dialog box, only assignments are shown.
Prerequisites
Concurrent Employment is enabled for the system which runs your application. For more information, see Enabling Concurrent Employment (CE).
The application is registered as a Concurrent Employment application via the V_T7XSSCE_GRP table view in Customizing for Employee Self-Service (WDA)
under General Settings Assign CE / GE Group Definition Settings to ESS Applications .
Enabling Concurrent Employment (CE)

In the Concurrent Employment scenario an employee has multiple personnel assignments within one organization. The enabling of Concurrent Employment
influences the system behavior of payroll, master data, and other components of Human Capital Management.
Activities
To enable Concurrent Employment, the following customizing settings are required:
1. An entry CCURE MAINS (Concurrent Employment Main Switch) = X and CCURE GSVAL = X in table V_T77S0 should exist.
Check the entry in Customizing for Personnel Management under Personnel Administration Basic Settings Basic Settings for Concurrent Employment
Activate Concurrent Employment .
2. If Concurrent Employment is activated, the application has to be registered as a Concurrent Employment application via the V_T7XSSCE_GRP table view.
To do so, execute the settings in Customizing for Personnel Management under Employee Self Service General Settings Concurrent Employment (CE)
/Global Employment (GE) Assign CE/GE Group Definition Settings to ESS Applications .
PUBLIC
Page 32 of 85
In the standard delivery, the Personal Profile application is, by default, CE enabled.
Application Title Handling

The title of the application is configured in the HRESS_CC_PER_OVP overview pattern (OVP) configuration.
The Personal Profile application can have different titles depending on whether Concurrent Employment (CE) is enabled:
Overview screen title in the Non-CE scenario
Example: Personal Profile
Overview screen title in the CE scenario
Example: Personal Profile + grouping text selected by the user on the CE dialog box
If the grouping text selected by the users on the CE dialog box is Ides US Inc. Philadelphia and they select Continue, the application title is Personal
Information, Ides US Inc. Philadelphia.
Detail screen title in the Non-CE scenario
In the detail screen, the application title is a mixture of subtype text from the T7XSSPERSUBTY subtype table, and the CRUD (Create/Read/Update/Delete)
operation performed.
Example: If the user is editing a mailing address record, then the application title would be Edit Mailing Address.
Detail screen title where data is not shared by all assignments in the CE scenario
Example: Edit Mailing Address + grouping text selected by the user on the CE dialog box would be Edit Mailing Address, Ides US Inc. - Philadelphia
The grouping text in the business cards (biz cards) is based on the Infotype or subtype. In the CE scenario it additionally contains the Data Sharing Info. For
more information, see Data Sharing Information
Foreign Address Screen Replacement

Employees can maintain their foreign addresses using the correct country-specific format, if available. In the detail screen for the biz card Addresses, the
dropdown list for the selection of the country allows maintaining foreign addresses in the relevant format. To enable the Foreign Address screen replacement, the
country dropdown should be associated with the _ON_COUNTRY_SELECT_ Floorplan Manager (FPM) event.
The detail screen, which is replaced on the selection of a different country, is based on the screen replacement configuration maintained in the Application
Configuration Controller (AppCC) for the country selected.
In case the AppCC is not maintained for the particular country selected, then the default international (XX) based user interface screen, which is the default
overview pattern (OVP) for the user interface building block (UIBB), is displayed to the user.
In the default shipment, the country dropdown is already associated with the _ON_COUNTRY_SELECT_ FPM event and appropriate screen configurations
are also maintained in AppCC.
Activities
The values that are included in the country dropdown list are based on the Customizing. To maintain the values you have to perform the following activities in
Customizing for Employee Self-Service (WDA) under Service-Specific Settings Personal Information Personal Profile Customizing of Personal Profile
Screens :
Determine Countries for Foreign Address and Make Settings
BAdI: Specify Countries for Foreign Address Entry
More Information
Application Configuration Controller
Data Sharing Information

The Data Sharing Information is applicable in the Concurrent Employment scenario. It indicates that the infotype data being displayed is also valid for other work
Note
Note
Note
PUBLIC
Page 33 of 85
agreements of the employee. This is a customer-specific setting which you can enable or disable via the application parameter HIDE_CE_DATA_SHARING.
In the standard delivery of the Personal Profile application, Data Sharing Information is enabled. Data Sharing Information is visible in the overview screen
alongside the subtype grouping text and in the detail screen as title of the page.
Activities
To hide the field, you must set the value X for the HIDE_CE_DATA_SHARING application parameter.
More Information
Concurrent Employment Scenario
Validity Section in Detail Screen

In the standard Personal Profile overview pattern (OVP) configuration, every edit page content area contains a validity user interface building block (UIBB). An
empty validity configuration is created for every edit page content area. This configuration is created out of the HRESS_C_VALIDITY component.
Features
To display appropriate validity information and radio button options, the HRESS_C_VALIDITY component makes use of the following:
The use case for the infotype or subtype being edited as maintained in the V_T7XSSPERSUBTYP table view
The begin date of the record being edited
Is it the last record of the list of records of the subtype being edited
Is the record being edited after or before the current system date
Data transmission from the validity UIBB to the detail screen UIBB takes place via the identity connector. This includes the validity UIBB in the OVP edit page
content area, and adding wires (CL_FPM_CONNECTOR_BOL_IDENTITY connector) that connect the validity UIBB to the detail screen UIBB in the same content
area, ensure that the validity information is automatically handled for the detail screen.
More Information
Wiring
BTracking

Data Tracking, also referred to as BTracking, is a process where applications can be tracked for their usage. Appropriate reports can also be gathered from SAP
NetWeaver Business Warehouse (BI) based on this data collected.
In the SAP standard delivery, the BTracking function (V_T5SSCTRACKXSS table view) is switched off.
Once tracking is active each time the application is launched by a user, it is recorded in the T5SSCXSSSERVICES table. This data is used in BI extraction for
further analysis.
Activities
1. In order to enable the tracking for all self-services, you set the TRACKING_ON field of table V_T5SSCSWITCHON to true. To do so, perform the steps in
Customizing for Personnel Management under Data Tracking for Self-Services -> Activate Data Tracking All Self-Services.
2. In order to enable the tracking for an application, additionally you have to make an entry for the application in the V_T5SSCTRACKXSS table view. To do so,
perform the steps in Customizing for Personnel Management under Data Tracking for Self-Services -> Set Data Tracking for Individual Self-Services.
3. Apart from the application-specific fields this view has a TRACKING_ID column. This allows for the same application to be tracked differently for different
configurations. When different TRACKING_IDs are maintained, the TRACKING_ID application parameter in the Personal Profile application has to be set to
the appropriate value, to which it has to be tracked against.
Configuration of Reporting Services

The configuration information for reporting services within the WebDynpro for ABAP version of Employee Self-Service is divided into three broad sections:
Architecture of Reporting Services
This section gives you an overview of the architecture of how the reporting scenarios are to be implemented.
Implementation of a Simple Customer-Specific Reporting Service
This section contains information about how to do an implementation of a simple reporting service with the seven steps that are essential to get your scenario up
and running.
PUBLIC
Page 34 of 85
Detailed Configuration
This section contains specialized information by topic which help you build more complex reporting services.
Prerequisites
To fully understand the information given in this section, you need to be familiar with the Floorplan Manager (FPM), a framework which allows you to build ABAP
Web Dynpro applications which are SAP UI guideline compliant. For more information see SAP Library for SAP NetWeaver on SAP Help Portal at
http://help.sap.com/netweaver SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology UI Technology
WEB UI Technology Floorplan Manager for Web Dynpro ABAP .
Process
In order to build your own customer-specific reporting services, proceed as follows:
1. Build your knowledge of the SAP Floorplan Manager for Web Dynpro ABAP (FPM) by reading the documentation in the SAP NetWeaver Library (you will find
the complete documentation under the navigation path given above).
2. Read the sections on Architecture and Implementation of a Simple Reporting Service.
3. Create your own configuration based on the information you gathered in steps 1 and 2.
4. If required, refine your configuration by making yourself familiar with the specialized information in section Detailed Configuration.
5. Fill Method GET_DATA of your implementation with life, based on the information that you can find under Refining Method GET_DATA.
6. Test your new application.
Steps 1 3 are the basic steps for creating a service and getting an output list. But the Detailed Configuration section provides you with information that you
will also need when building your own application, especially the section on Refining Method GET_DATA, where you define the processing of the whole
application. So do not skip these sections.
More Information
Floorplan Manager for Web Dynpro ABAP
Architecture of Reporting Services

This section informs you about the main elements of which a reporting service in Employee Self-Service based on Web Dynpro ABAP consists of.
Structure
The basic set up for all reporting scenarios includes several main elements, see also An Application and its Components.
Apart from these elements, every HCM Reporting scenario needs a feeder class to process the implementation and a Document Container class. See also
Feeder and Document Container Classes.
An Application and its Components
Structure
The following figure illustrates the basic set up for all reporting scenarios:
Note
PUBLIC
Page 35 of 85
Figure 1: Component Encapsulation with (G)UIBBs
Figure 1 shows the encapsulation of several Web Dynpro (WD) components within one Web Dynpro Application. Per reporting scenario, you have to create one
WD application, and then pull in the various FPM and HR reporting re-use components. (Apart from the encapsulating WD application in this figure, all the
rectangles are technically speaking WD components).
All of the Web Dynpro components mentioned in this section are for re-use. You will not be required to create any new components when you create your own
reporting service.
You can re-use these components by creating your own component configurations. Depending on your reporting scenario, you will use some of the following
elements:
the Document Display UIBB for the output of your report
the FORM GUIBB to configure any input fields for the end user
the LIST GUIBB if the user is to choose an entry from a table
A list or a form is the usual case. In some less common cases where the employee needs to make some entries, which generates a list, and then makes a
selection from the list which only then creates a form, you will need to use both FORM and LIST GUIBBS.
Feeder and Document Container Classes
Structure
In every HR Reporting scenario, there must be a feeder class and a Document Container class. The feeder class is the processing workhorse of your
implementation. The Document Container class is just a container, and also a singleton, principally to hold the document, once your feeder class has produced it.
Note
PUBLIC
Page 36 of 85
Figure 2: Interaction of Feeder and Document Container Classes with Application
Features
Figure 2 shows how the Feeder and Document Container classes interact with the WD Application.
At runtime, the end user makes entries in the fields provided by your FORM GUIBB configuration, or selects an entry from the table defined in your LIST GUIBB
configuration (depending on your scenario). This information is available at runtime in your feeder class. The feeder class processes the user selection information,
generates a form, and puts the finished form into the Document Container class.
During the FPM event loop, when the Document Display UIBB is built, the component controller of the Document Display UIBB reads this container and displays
the form in the Document Display UIBB.
Whenever you use one of the FPM GUIBBs, the component configuration requires you to provide a feeder class for it. This is your class, and works a little bit like
a Business Add-In (BAdI), in that you can partake of the FPM event loop in the FPM OVP component.
You can implement your own code in the interface methods in your class, so that you can influence the processing at various given points (for example
INITIALIZE for things needed at screen build, GET_DATA to run your report in the backend, etc.).
SAP provides two super classes which provide services you can use in your feeder class and your feeder class must inherit from one of these, depending on the
FPM GUIBB you intend to use:
For LIST GUIBB: AC_HRGRT_REPORTING_LIST_FEEDER
For FORM GUIBB: AC_HRGRT_REPORTING_FORM_FEEDER
These super classes have the super class AC_HRGRT_REPORTING for services generic to both. You must not use AC_HRGRT_REPORTING as your
feeders direct super class!
The Document Container CL_HRGRT_DOCUMENT_CONTAINER class is a reuse service class provided by SAP.
Currently the only document types supported are Acrobat PDF and Microsoft Office.
Implementation of a Simple Customer-Specific Reporting Service

This section explains the essential steps for creating a simple example reporting service with either a list or a form GUIBB as input for the backend report, and
one document (PDF, office document, url) display.
You can find information on how to implement more complex scenarios in section Detailed Configuration.
Process
1. Analyze the reporting scenario that you want to implement. You need to be familiar with what you are trying to achieve. This step is especially of importance if
Caution
Note
Note
PUBLIC
Page 37 of 85
you want to reuse a report based on Web Dynpro for Java that you used in the Business Package for Employee Self-Service (up to and including 1.41).
2. Create a feeder class for your application and implement the 2 essential methods, GET_DEFINITION and GET_DATA.
3. Complete the Methods of Your Feeder Class to bring it to life, in particular the GET_DATA method where you add the code for calling your report.
4. Create your Web Dynpro application and determine it as an Overview Page Floorplan (OVP).
5. Create the OVP configuration, into which you insert the screen elements in the next steps.
6. Create the initial screen, into which you embed a reuse component for PERNR selection.
7. Create the main screen, into which you embed a form GUIBB or list GUIBB for the user to make selections. You also embed here the reuse UIBB which takes
care of outputting the document result (PDF, XLS, etc.) of your backend report.
After you have completed the implementation steps, test your application.
Step 1: Analyze Your Reporting Scenario

In this step, define what kind of report service you want to implement and all the functions it should comprise.
If you want to implement a reporting scenario that you already used as an iView based on Web Dynpro for JAVA in the Business Package for Employee Self-
Service (up to and including 1.41), proceed as follows:
Procedure
1. Find all classes with the naming convention CL_HRXSS_* (for country-specific services, with naming convention CL_HRXSS_xx* (where xx is your country
identifier, e.g. DE for Germany):
These services implement an interface with the method PROCESS_ACTION from which all functionality in the service is executed.
2. Familiarize yourself with the functionality called by the different stages in this method, according to action type:
Generally speaking, the functionality will fetch data, run a report, and produce a form. Knowing what your service is trying to achieve will help you in the next
steps, as you reproduce this functionality in your FPM Application.
Step 2: Create Your Feeder Class

In this step you create your own feeder class, based on one of the following super classes provided by FPM:
AC_HRGRT_REPORTING_FORM_FEEDER
Use this super class if your reporting scenario requires the end user to make entries in a set of fields.
AC_HRGRT_REPORTING_LIST_FEEDER
Use this super class if your scenario requires the end user to choose an entry from a list or table (e.g. payroll results, tax form).
These super classes already contain the FPM interfaces and implement the generic international code, so you do not need to implement each method provided
by the interfaces. You must only redefine those interface methods that you need to implement. You do this in the following step, Step 3: Complete the Methods of
Your Feeder Class.
For some country-specific reports, you may find the international implementation of an FPM interface method is entirely sufficient, so that you need do nothing.
In many reporting scenarios, you will need only to redefine the bare minimum GET_DEFINITON and GET_DATA methods.
In this example implementation of a simple reporting service to be able to configure the UI, you need only to redefine the method GET_DEFINITION and
ensure the two exporting parameters ET_FIELD_CATALOG and ET_FIELD_DESCRIPTION are filled (see also the description under Create the Field
Catalogue (Method GET_DEFINITION). This is the essential part, because it provides the fields that you need when you arrange them on the screen. You can
come back and do the other parts of this method and any other methods later.
Procedure
Proceed as follows:
1. Create your feeder class in your appropriate package.
2. Inherit from one of the following super classes:
AC_HRGRT_REPORTING_FORM_FEEDER or AC_HRGRT_REPORTING_LIST_FEEDER
3. Save and activate your new class.
Step 3: Complete the Methods of Your Feeder Class

After creating you feeder class in step 2, in this step you complete the methods of your feeder class:
Note
PUBLIC
Page 38 of 85
Method GET_DEFINITION
Method GET_DATA
Method INITIALIZE
In this sample process of implementing a simple reporting scenario, only the basic steps in the code that you have to carry out are pointed out for each
method. For a normal reporting scenario, especially method GET_DATA, which is the core method of your feeder class, needs to be refined by making use of
events. To find out more, see Refining Method GET_DATA in the Detailed Configuration section of this documentation.
Procedure
Follow the instructions for completing the methods in the following sections:
1. Create the Field Catalogue (Method GET_DEFINITION)
2. Run the Report (Method GET_DATA)
3. Get the Global Data (Method INITIALIZE)
Create the Field Catalogue (Method GET_DEFINITION)

The field catalogue is the structure of fields that are to be visible to the end user, either as entry fields in your form, or as the fields in the table in the case of a list.
When you try to implement a former Web Dynpro for Java application, take a note of the input fields that were there. You should find something you can re-
use, or at least append to a new structure you can create especially for your new application. In the following code examples for a FORM and a LIST, existing
DDIC structures have been used.
In this method you not only determine DDIC fields (in your structure), but you can also override the fields properties, such as length, mandatory or not, read only,
etc.
Also here, you can give fixed value lists for each fields input help.
Activities
You must carry out following basic steps in your code. This is principally the same, regardless if it is a LIST or FORM implementation:
1. Call super method GET_DEFINITION.
2. Declare application specific events (so that they are visible in your configuration).
3. Convert your structure to field catalogue format
4. Read data for fixed values.
In the following code example for forms, some global tables for the value helps are filled and to aid this, some text variables will be created, for example:
a) V01 Compulsory/Voluntarily Insured
b) V02 Privately Insured
5. Field by field, adjust properties, set fixed values etc., if necessary.
Example
Also see the following examples for creating the field catalogue:
Code Example for a FORM Implementation
Code Example for a LIST Implementation
Code Example for a FORM Implementation
This is an example for a FORM implementation (the tables starting GT_* are attributes of the class):
01. METHOD if_fpm_guibb_form~get_definition.
02. DATA lo_guibb_definit TYPE REF TO cl_hress_fpm_guibb_services.
03. DATA ls_fixed_values TYPE wdr_context_attr_value.
04. DATA ls_action TYPE fpmgb_s_actiondef.
05. FIELD-SYMBOLS <ls_t516t> TYPE t516t.
06. FIELD-SYMBOLS <ls_t5d2l> TYPE t5d2l.
07. FIELD-SYMBOLS <ls_field_descr> TYPE fpmgb_s_formfield_descr.
08. **Step 1 ********************************************
09. * call super method, because it is the done thing.
Note
Note
Syntax
PUBLIC
Page 39 of 85
10. super->if_fpm_guibb_form~get_definition(
11. IMPORTING
12. es_message = es_message
13. eo_field_catalog = eo_field_catalog
14. et_field_description = et_field_description
15. et_action_definition = et_action_definition
16. et_special_groups = et_special_groups
17. ev_additional_error_info = ev_additional_error_info ).
18. **Step 2 *********************************************
19. * Expose supermethod standard 'display' event to configuration
20. expose_action_display_output( changing ct_action_definition =
21. et_action_definition ).
22. * Action on Radio buttons Privat- or Freiwillig-/Gesetzlichversichert
23. ls_action-id = GC_EVENT_RBHEALTH."'RBHEALTH'.
24. ls_action-text = text-e02.
25. ls_action-enabled = abap_true.
26. ls_action-exposable = abap_true.
27. APPEND ls_action TO et_action_definition.
28. **Step 3 **********************************************
29. * Get field catalogue for Screen fields. (If a customer extends
30. * structure HRESS_S_REP_DE_GHR for the screen parameters,
31. * this method will automatically get the DDIC information for the
32. * extended fields too. No modification necessary. )
33. CREATE OBJECT lo_guibb_definit.
34. TRY.
35. lo_guibb_definit->get_guibbf_definition_dstruc(
36. EXPORTING
37. iv_langu = sy-langu
38. is_data = gs_screen_parameters
39. IMPORTING
42. ).
43. CATCH cx_hress.
44. * create a dump here ...
45. MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
46. WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
47. ENDTRY.
48. **Step 4 ***********************************************
49. * Fill F4 values for ....
50. * Religion
51. SELECT * FROM t516t INTO TABLE gt_t516t
52. WHERE sprsl = 'D'.
53. * Bundesland (State)
54. SELECT * FROM t5d2l INTO TABLE gt_t5d2l.
55. * Insurance types for radio buttons
56. CLEAR ls_in_type_values.
57. ls_in_type_values-value = '01'.
58. ls_in_type_values-text = text-v01." 'Freiwilling/Pflichtversichert' .
59. APPEND ls_in_type_values TO gt_ins_type_values.
60. ls_in_type_values-value = '02'.
61. ls_in_type_values-text = text-v02."'Privatversichert' .
62. APPEND ls_in_type_values TO gt_ins_type_values.
63. **Step 5 ***********************************************
64. LOOP AT et_field_description ASSIGNING <ls_field_descr>.
65. CASE <ls_field_descr>-name.
66. * set currency for Gross Remuneration field
67. WHEN 'BRUTT'.
68. <ls_field_descr>-cq = 'C'.
69. <ls_field_descr>-mandatory = abap_true.
70. <ls_field_descr>-cq_ref = gv_currency.
71. WHEN 'DATUM'.
72. <ls_field_descr>-mandatory = abap_true.
73. * set F4 helps
74. * Church tax area
75. WHEN 'KISTG'.
76. LOOP AT gt_t5d2l ASSIGNING <ls_t5d2l>.
77. CLEAR ls_fixed_values.
78. ls_fixed_values-value = <ls_t5d2l>-brdld.
79. ls_fixed_values-text = <ls_t5d2l>-ksttx.
80. APPEND ls_fixed_values TO <ls_field_descr>-fixed_values.
81. ENDLOOP.
82. * Church tax
83. WHEN 'KONFE'.
84. LOOP AT gt_t516t ASSIGNING <ls_t516t>.
85. CLEAR ls_fixed_values.
86. ls_fixed_values-value = <ls_t516t>-konfe.
87. ls_fixed_values-text = <ls_t516t>-ktext.-ktext.
PUBLIC
Page 40 of 85
88. APPEND ls_fixed_values TO <ls_field_descr>-fixed_values.
89. ENDLOOP.
90. * no currency conversions..
91. WHEN 'WAERS'.
92. <ls_field_descr>-read_only = abap_true.
93. * fixed values for Privat/Gesetzlich/Freiw.Gesetzlich
94. WHEN 'INS_TYPE'.
95. <ls_field_descr>-fixed_values = gt_ins_type_values.
96. WHEN OTHERS.
97. ENDCASE.
98. ENDLOOP.
99. ENDMETHOD.
Code Example for a LIST Implementation
This is an example for the implementation of a LIST for payroll results, where the RGDIR structure is also extended manually with the fields P0002-NACHN and -
MAXBT.
If you have no need of such extensions of an existing structure, use the example of the form implementation, where the service
CL_HRESS_FPM_GUIBB_SERVICES- > get_guibbf_definition_dstruc does a lot of the work for you.
01. METHOD if_fpm_guibb_list~get_definition.
02. DATA: lo_table_descr TYPE REF TO cl_abap_tabledescr,
03. lo_struc_descr TYPE REF TO cl_abap_structdescr,
04. lt_component_tab TYPE cl_abap_structdescr=>component_table,
05. lt_rgdir TYPE h99_clst_t_rgdir,
06. ls_component_wa TYPE abap_componentdescr.
07. * call super method, because it is the done thing.
08. super->if_fpm_guibb_form~get_definition(
09. IMPORTING
10. es_message = es_message
13. et_action_definition = et_action_definition
14. et_special_groups = et_special_groups
15. ev_additional_error_info = ev_additional_error_info ).
16. * getting the field catalog for remuneration statement***
17. * 1 Get the line type from the table
18. * 2 Get the table of components from the line type
19. * 3 Add a component to the table of components
20. * 4 Create a new (expanded) structure
21. * 5 Create a new table typed with the new (expanded) structure
22. lo_table_descr ?= cl_abap_tabledescr=>describe_by_name(
23. 'H99_CLST_T_RGDIR' ).
24. lo_struc_descr ?= lo_table_descr->get_table_line_type( ).
25. lt_component_tab = lo_struc_descr->get_components( ).
26. ls_component_wa-name = 'NAME'.
27. ls_component_wa-type ?= cl_abap_datadescr=>describe_by_name( 'P0002-
28. NACHN' ).
29. ls_component_wa-as_include = abap_false.
30. APPEND ls_component_wa TO lt_component_tab.
31. ls_component_wa-name = 'BETRG'.
32. ls_component_wa-type ?= cl_abap_datadescr=>describe_by_name( 'MAXBT'
33. ).
34. ls_component_wa-as_include = abap_false.
35. APPEND ls_component_wa TO lt_component_tab.
36. CLEAR: lo_struc_descr.
37. lo_struc_descr ?= cl_abap_structdescr=>get( lt_component_tab ).
38. eo_field_catalog ?= cl_abap_tabledescr=>get( lo_struc_descr ).
39. Endmethod.
Run the Report (Method GET_DATA)
Note
Syntax
PUBLIC
Page 41 of 85

This is the method which is very much the heart of the application, and the incoming parameter IV_EVENTID allows you to react in your code according to, for
example, the events you declared for your configuration in GET_DEFINITION and will assign in your configuration in the Detailed Configuration section under
Refining Method GET_DATA.
In this sample procedure of implementing a simple reporting scenario, the method will remain empty to be filled with code in the process of the detailed
configuration.
The feeder classes for the reporting scenarios should always inherit from one of the super classes AC_HRGRT_REPORTING_FORM_FEEDER or
AC_HRGRT_REPORTING_LIST_FEEDER. These super classes handle certain functionality that is common to either the list or form reporting scenarios. In
most cases, you must redefine the methods GET_DEFINITION and GET_DATA. Further redefinitions will depend on what the scenario requires. It is important
that whenever you redefine, you must firstly call the super class method, then do your additional coding.
Activities
In order to get the FPM application aspects of the reporting service running, perform the following basic steps:
1. Call super method GET_DATA.
2. Get any further data specific to the employee, or the selections he or she has made.
3. a) In the case of a Form GUIBB, if necessary carry out consistency checks on the data selections the end user has made.
b) In the case of a List GUIBB, process the list specific events, e.g. the employee has selected a line in the table (either via a button or by selecting the
appropriate line in the table, which then determines other behaviour on the screen, for example if it is the first payroll period, the Previous button should be
deactivated etc. (See 6.8 The Application Component Controller and its Events for the instructions on how to implement this re-use behaviour.)
4. Call your report.
5. Send the result of your report to the container class.
Get the Global Data (Method INITIALIZE)

This method can be used for various purposes to do things right at the start of the application. Amongst other things, this method performs the following activities:
It instantiates the HR Reporting re-use Document Container CL_HRGRT_DOCUMENT_CONTAINER, by calling its method get_instance.
It Instantiates CL_FPM by calling the factory class method CL_FPM_FACTORY~get_instance.
It reads and sets the header of the application for later use, where you can dynamically modify the header later from your feeder class (e.g. with the payroll
period selected by the user, or date selection, etc.).
Activities
In order to define this method, call super class INITIALIZE, see also the following code example.
01. METHOD if_fpm_guibb~initialize.
02. DATA ls_in_type_values TYPE wdr_context_attr_value.
03. *call super method
04. super->if_fpm_guibb~initialize(
05. it_parameter = it_parameter
06. io_app_parameter = io_app_parameter
07. iv_component_name = iv_component_name
08. is_config_key = is_config_key
09. ).
10. ENDMETHOD.
Step 4: Create Your Web Dynpro Application

In this section you find information about how to create the application and several component configurations. The component configurations are all created with
forward navigation.
In the process of creating the configuration, you may be confronted with messages informing you that the component configurations do not yet exist. You can
ignore theses messages.
Note
Syntax
Note
PUBLIC
Page 42 of 85
Procedure
In order to create your application, proceed as follows:
1. Call up transaction SE80 and right-click your package and choose Create Web Dynpro Web Application .
2. Enter the application name (your choice) and description in the dialog box.
3. Fill in the application's attributes as follows:
Component: FPM_OVP_COMPONENT
Interface View: FPM_WINDOW
Plug Name: DEFAULT
Already at this early stage, while creating your FPM application, you define the Floor Plan Type, OVP.
4. Save the application.
5. Locate your newly created application in the structure for the objects of your package to the left and select it with right-mouse click.
6. Choose Create/Change Configuration. A brower is started.
7. Enter a name for the new application configuration (your choice, as with your application, but with the suffix AC to distinguish it from your application) that you
are about to create, and choose Create.
In the dialog box that is displayed now, enter description and package.
8. In the next screen, chose Save.
Step 5: Create the OVP Configuration
Procedure
After you have saved your application configuration in Step 4, you are now on the next screen, where you now have to enter a name for the component
configuration.
In this step, you are in fact creating the component configuration with forward navigation, although in the header <Application Configuration <your application>
is displayed.
1. Enter a name for the new Component configuration in the table field Configuration.
2. Choose Save.
You can see here in the table columns, going from left to right, the Component Usage is your application and this is where the OVP component is being
used. The Component and its Implementation is the OVP component itself, and the last column is the Configuration of the OVP that you are about to
create.
3. Choose Go to Component Configuration.
4. Choose Create.
5. In the dialog box that is displayed now, enter description and package.
6. In the next screen choose Save.
Result
Now you have created the application, the application configuration, and the main component configuration. For the component configuration, you will now add the
details by creating the screens.
More Information
Step 6: Create the Initial Screen
Step 7: Create the Main Screen
Step 6: Create the Initial Screen

In this step you create an initial screen and add the UIBB provided by the Personal Information framework called HRESS_C_PERNR_SELECTION.
Note
Note
Note
Note
PUBLIC
Page 43 of 85
This reuse UIBB handles the concurrent employment (CE) aspects, so that your reporting scenario will work in both CE and non-CE circumstances.
The HRESS_C_PERNR_SELECTION component checks if CE is active in the system and if the current user is a CE employee (which means has more than one
PERNR). If that is the case, the INITIAL_SCREEN generates a dialog box, allowing the user to enter one or other of his or her personnel numbers, and then to
proceed to the next screen.
For employees with only one PERNR, the INITIAL_SCREEN is automatically hidden and the component merely reads the PERNR based on the user data.
When redefining your feeder class method GET_DATA, at event LEAVE_INITIAL_SCREEN you should read the PERNR using the service class
CL_HRESS_EMPLOYEE_SERVICES. This service provides the correct PERNR according to what the user selected (if CE) or simply as per the user data (for
non-CE). See also code example in section Event LEAVE_INITIAL_SCREEN for Method GET_DATA).
Procedure
Whether you use concurrent employment or not, you must create the initial screen so that you handle PERNR correctly. To do so, proceed as follows:
1. Place your cursor on ContentArea in the hierarchy on the left.
2. Enter the ID and a title for the Initial Screen.
SAP recommends you to use INITIAL_SCREEN as the ID for this content area.
3. Set the Content Area Type to Initial Screen.
4. Place your cursor on ContentArea in the hierarchy on the left, then choose Add UIBB.
5. Choose the Attributes button of the UIBB inside the new content area for the initial screen.
6. Enter the component HRESS_C_PERNR_SELECTION.
7. Enter the view PERNR_SELECTION_MAIN.
8. Choose Save.
Result
You have successfully created the initial screen.
This initial screen will not be seen by the user, unless the user has CE, since there is nothing for the end user to select or do. Without concurrent employment,
this screen is automatically suppressed, you need not do anything to suppress it. This is taken care of automatically in this reuse component.
Step 7: Create the Main Screen

After you have created the initial screen in Step 6, you can directly proceed to create you main screen:
Procedure
1. In the Hierarchy on the left, in the element list, choose the OvpApplication, then select Add Content Area.
2. Enter the ID and a title for the main screen, which will contain all your visible screen elements.
SAP recommends that you use MAIN_SCREEN as the ID for this content area.
3. In the Hierarchy on the left, in the element list, open the ContentArea, then choose UIBB below it.
The system will not allow you to save at this moment, because the tool adds the UIBB automatically, but you have not yet configured it. To do so, proceed to
add the Document Display UIBB in the following steps.
4. Choose the ContentArea MAIN_SCREEN, then choose UIBB below it.
5. In field Component, enter the reuse UIBB HRGRT_FC_DOCUMENT_DISPLAY and its view FVS_OUTPUT.
6. In the Title field, enter a text for your Document Display window, e.g. Result.
7. Choose Save.
In this simple case it is not required to create a configuration of this component because we use the component as it is and need no adaptation. However, if
Note
Recommendation
Note
Recommendation
Note
Note
PUBLIC
Page 44 of 85
you have a case where you have two or more concurrent outputs for one reporting scenario, configuration would be necessary for each output this is not the
same as whether you have either a PDF or an office document, which may depend on the Customizing you have in the backend processing of your reporting
scenario. The Salary Statement is such an example. In such either-or cases, the reuse component displays the one output, as it can deal with whatever
format it was given by your feeder class.
In section Add Buttons to (G)UIBB 'Open in New Window' you can find information on how to implement the Display in New Window button for the form output.
This is not described here, as it is not essential to getting your application running.
Up to this point, the configuration steps have been the same, regardless of whether your reporting scenario has a list or a form GUIBB. Of the following two
sections, you need only carry out one, according to your example:
Add and Configure the Form GUIBB
Add and Configure the List GUIBB
Add and Configure the Form GUIBB
Procedure
In order to add the Form GUIBB to your OVP configuration, proceed as follows:
1. In the Hierarchy on the left, in the element list, choose the ContentArea MAIN_SCREEN, then select Add UIBB Add Form Component .
The system adds a new Form UIBB.
2. Enter a new configuration name, for example ZYEC_CC_FORM_REPORTING.
3. Choose the View type, General.
4. Enter 1 in the sequence index, so that the Document Display is located below the form GUIBB in this example).
5. Choose Save.
6. Choose Configure UIBB.
With forward navigation, you are now creating your own component configuration for the Form UIBB.
7. On the next screen, the system will point out the configuration does not yet exist, therefore choose Create.
A dialog box is displayed.
8. In this dialog box, enter description and package.
A new dialog box is displayed.
9. In this new dialog box, choose Cancel.
This is because our feeder class has no parameters.
10. In the next dialog box that is displayed, enter your feeder class.
If you cannot find your class, check that it is active and that it inherits the correct super class, for example the super class
AC_HRGRT_REPORTING_FORM_FEEDER in the case of a Form GUIBB.
11. Once you have entered the class, choose Edit parameters (although you do not have parameters in this example).
12. In this dialog box, confirm with OK.
13. Choose Save.
At this stage, you can see how your screen will finally look. In the following steps, see how to configure the Form GUIBB by arranging the fields on the
screen (from the field catalogue provided by the feeder class).
14. Choose Add Group.
15. Enter a name, for example General Data in the Text field, and choose Configure Group.
16. In this dialog box, choose the fields BRUTT and DATUM to go in this group, and then choose OK.
17. Select the element (1) in the hierarchy, enter an appropriate name for the field in Text field, for example, Gross Remuneration for BRUTT and Date for
DATUM.
18. Choose Save.
The fields you select come from the field catalogue you defined in Method GET_DEFINITION. The texts you can enter here are override texts for the DDIC
texts. Depending on the status of texts in your back end system, and if you set the attributes of your field catalogue (in GET_DEFINITION) to use DDIC
labels, the system will give the DDIC default values. Try to use the DDIC default values as it makes for easier content recognition by the user.
Note
Note
Note
Note
Note
PUBLIC
Page 45 of 85
Add and Configure the List GUIBB
Procedure
In order to add the List GUIBB to your OVP configuration, proceed as follows:
1. In the Hierarchy on the left, in the element list, choose the ContentArea MAIN_SCREEN, then select Add UIBB Add List Component .
The system adds a new UIBB.
2. Enter a new configuration name, for example ZYEC_CC_LIST_REPORTING and choose Save.
3. Enter 1 in the sequence index, so that the Document Display is located below the form GUIBB in this example).
4. Enter the newly created configuration name and choose Save.
5. Choose Configure UIBB.
With forward navigation, you are now creating your own component configuration for the List UIBB.
6. On the next screen, the system will point out the configuration does not yet exist, therefore choose Create.
7. In this dialog box, enter description and package.
8. In this new dialog box, choose Cancel.
This is because our feeder class has no parameters.
9. In the next dialog box that is displayed, enter your feeder class.
If you cannot find your class, check that it is active and that it inherits the correct super class, for example the super class
AC_HRGRT_REPORTING_LIST_FEEDER in the case of a List GUIBB.
10. Once you have entered the class, choose Edit parameters (although you do not have parameters in this example).
11. In this dialog box, confirm with OK.
12. Choose Save. You are now on the component configuration screen for the List GUIBB.
At this stage, you can see how your screen will finally look. In the following steps, see how to configure the Form GUIBB by arranging the fields on the
screen (from the field catalogue provided by the feeder class).
13. Select Configure Columns.
14. In this dialog box, you can choose fields to display. The fields at left are from your field catalog.
15. If necessary, change the texts for the column headers.
16. Choose OK.
17. Choose Assign Action.
A new dialog boy is displayed.
18. In the dialog box, choose the FPM Event ID, HRGRT_LINESELECT.
You should handle this event in your feeder class. When the end user chooses a line in the table, this is the event (or for the user, also known as an
Action) that is triggered. In method GET_DATA, your code should react to this event and the HRGRT_NEXT and HRGRT_PREVIOUS events by producing
the output to go into the Data Container
19. Choose Settings in the hierarchy, and make the following attribute settings
Selection Event = only lead selection produces an FPM event
Row Count = 0 (This is a standard default setting, that means that 5 rows are shown)
Selection Mode = Single (This means that the event is triggered only when the end user selects a single row. Indeed the user is only able to select a single
row)
20. Choose Save.
Test Your Application
Note
Note
Note
Note
PUBLIC
Page 46 of 85

There are two possibilities for you to test your application.
Procedure
1. Call up transaction SE80, right click your application, and choose Test.
2. Call up transaction SE80, select your application configuration and start the configurator. On the next screen, first choose Display, then Test.
Detailed Configuration

This section contains specialized information by topic which help you build more complex reporting services.
Process
Read and follow the instructions contained in the following sections as required:
Refining Method GET_DATA
The Document Container
Adding Buttons
Melting Group
Radio Buttons
The Application Component Controller and its Events
Modifying Titles
Error Handling
Concurrent Employment (CE)
Refining Method GET_DATA

In this section you find information about what processing you can add for method GET_DATA, which is the heart (processing part) of your feeder class. It manages
events from the Floorplan Manager (FPM), any you might raise in your code, and most importantly for you, the events triggered by the user (line selection,
pressing a button, etc.):
Depending on the event, this method goes to work, getting personnel numbers, running the report in the back end and putting the final output into the Document
Container, then modifying headers and raising its own events (setting the previous and next buttons to in/active) if necessary.
If you want to re-implement an Java application, you should be able to reuse the code that calls the back end report and returns a document output here,
either by cut and paste, or better still, by encapsulating it for both applications. This code is different for every report, so no example is added here. However,
the following steps should give you an idea.
Before you start, have a look at the attributes starting GC_EVENT* of your super class. These are the standard reporting events that you can react to in your feeder
class.
Then see in key block Process to find out what processing you can add for which events. Depending on your scenario, and thus depending on the buttons you
have on your screen, youll need varying event processing.
If you have Previous and Next buttons, see Event GC_EVENT_NEXT and GC_EVENT_PREVIOUS for LIST GUIBBs
If you have a form with a Show button or an application specific button, for example a Calculate button in a salary calculator report, see Event
GC_EVENT_NEXT_VALUE and GC_EVENT_PREVIOUS_VALUE for FORM GUIBBs
Prerequisites
As with all your redefinitions, call the super method GET_DATA at the start of your code.
In all cases add processing to the FPM event LEAVE_INITIAL_SCREEN.
Process
See the following sections to find out what processing you can add to method GET_DATA:
1. Event LEAVE_INITIAL_SCREEN
2. Event GC_EVENT_NEXT and GC_EVENT_PREVIOUS for LIST GUIBBs
3. Event GC_EVENT_NEXT_VALUE and GC_EVENT_PREVIOUS_VALUE for FORM GUIBBs
4. Event GC_EVENT_DISLAY for FORM GUIBBs
5. Get any Further Data and Produce the Form for LIST GUIBBs
6. Put the Output into the Document Container
7. Handle Visible Row and Buttons Active/Not Active for LIST UIBBs
Note
PUBLIC
Page 47 of 85
Event LEAVE_INITIAL_SCREEN

This is a generic FPM event (cl_fpm_event=>gc_event_leave_initial_screen), that runs as you leave the initial screen. At this point you can fetch
data that you need to build the main screen. Here, before you process the input data from the user, you get the PERNR.
Then you should do the processing that fetches the data for filling the list UIBB.
If you have a form UIBB; at this point you can set general or PERNR specific defaults for the fields in your form.
Code example for fetching PERNR:
01. TRY.
02. mv_pernr = cl_hress_employee_services=>get_instance( )->get_pernr( ).
03. CATCH cx_hress.
04. * <Errorhandling: Not necessary here, since this is handled earlier by
05. * component HRESS_C_PERNR_SELECTION>
06. ENDTRY.
Event GC_EVENT_NEXT and GC_EVENT_PREVIOUS for List
GUIBBs

If you use buttons to toggle along the entries in a List UIBB, you should use these standard HR reporting events (see super class attributes
AC_HRGRT_REPORTING_LIST_FEEDER), and call the super class method HANDLE_PREV_NEXT_EVENT, each time passing the appropriate event. This
method ensures that the correct entry in your list is selected, based on whether the user has selected previous or next.
Code example for handling previous and next buttons/events:
01. field-symbols : <lt_data> type standard table.
02. assign ct_data to <lt_data>.
03. CASE iv_eventid->mv_event_id.
04. WHEN gc_event_next or gc_event_previous.
05. call method me->handle_prev_next_event
06. exporting
07. iv_eventid = iv_eventid
08. iv_max_index = lines( <lt data> )
09. IMPORTING
10. ev_selected_lines_changed = ev_selected_lines_changed
11. changing
12. ct_selected_lines = ct_selected_lines
13. cv_lead_index = cv_lead_index
14. ENDCASE.
Event GC_EVENT_NEXT_VALUE and
GC_EVENT_PREVIOUS_VALUE for Form GUIBBs

This is very similar to the toggling in a List UIBB, but is intended for the value list of a drop down field in a Form UIBB. You should use these standard HR
reporting events (see super class attributes in AC_HRGRT_REPORTING_FROM_FEEDER), and call the super class method
HANDLE_PREV_NEXT_VALUE_EVENT, each time passing the appropriate event and the value list. This method ensures that the correct entry in your value list is
visually selected on the UI, based on whether the user has selected previous or next.
Note
Syntax
Example
Syntax
PUBLIC
Page 48 of 85
In this code example for handling previous and next buttons/ events, there is one field in a form GUIBB that contains the year. This allows the user to toggle
through year entries in that one field, just using the previous and next buttons:
01. field-symbols:
02. <ls_report_data> type hrxss_report_data,
03. <ls_field_usage> type fpmgb_s_fieldusage,
04. <lv_year> type any.
05. assign cs_data to <ls_report_data> casting.
06. case io_event->mv_event_id.
07. when gc_event_next_value "buttons pressed
08. or gc_event_prev_value.
09. read table ct_field_usage assigning <ls_field_usage>
10. with key name = 'YEAR'. "#EC WARNOK
11. if sy-subrc eq 0.
12. * get next/previous value relative to actual value
13. * before: field <ls_report_data>-year contains actual value
14. lv_year = <ls_report_data>-year.
15. * after: field <ls_report_data>-year contains prev/next value -> new
16. actual value
17. me->handle_prev_next_value_event(
18. exporting
19. iv_eventid = io_event
20. it_value_list = <ls_field_usage>-fixed_values
21. changing
22. * ct_messages = ct_messages
23. cv_value = <ls_report_data>-year
24. ).
25. if lv_year ne <ls_report_data>-year. "year have been changed!
26. lv_form = abap_true.
27. ev_data_changed = abap_true.
28. endif.
29. endif.
30. endcase.
Event GC_EVENT_DISLAY for Form GUIBBs

This is a standard event for form GUIBBs, that is triggered from a button on the screen. The name of this button can be freely defined in your application, and the
way your code reacts to the event is also up to you. So this is basically a very generic event that can be reused by many applications.
Code example for standard event for forms:
01. CASE iv_eventid->mv_event_id.
02. WHEN gc_event_display.
03. * 1. code to run your report/call function module etc,
04. * that generates e.g pdf.
05. CALL METHOD me->produce_form
06. IMPORTING
07. ev_pdf_content = lv_output_content
08. et_messages = et_messages
09. CHANGING
10. cs_screen_parameters = <ls_screen_parameters>.
11. * 2 .code to put e.g. pdf into the document container:
12. mo_document_container->set_document(
13. iv_content = lv_output_content
14. iv_content_type = cl_hrgrt_document_container=>gc_doc_type-pdf
15. iv_header_text = lv_header_text ).
16. ENDCASE.
Example
Syntax
Example
Syntax
PUBLIC
Page 49 of 85
Fetch any Further Data and Produce the Form for List GUIBBs

After the event handling for previous and next (where you naturally know if the user has requested a different output), you should then produce the form according
to the selection made by the user.
Activities
1. Check if a new selection has been made.
2. Fetch any PERNR-specific data you need for generating the form, for instance, infotype data.
3. Generate the output form, which means call your report, ready to put in into the Document Container (that will happen in the next step).
4. Handle any errors coming from the report, or from the reading of the infotype data and so on.
If you re-implement a Java scenario, refer to the Java implementation of your scenario on what exactly you must do, as it will be different for every scenario.
Code example for checking if the user has changed the list selection or if a Previous or Next event has been processed (this is all evident from the
comparison of the incoming CV_LEAD_INDEX and the class own GV_PREV_LEAD_INDEX:
01. IF cv_lead_index NE gv_prev_lead_index.
02. ME->PRODUCE_FORM(
03. EXPORTING
04. IV_ACTUAL_LINE = cv_lead_index
05. IMPORTING
06. EV_PDF_CONTENT = lv_output_content ).
Put the Output into the Document Container

At the event handling for previous and next (where you naturally know if the user has requested a different output) and after having produced the form, you need to
put that output into the Document Container. Likewise, as we saw for event GC_EVENT_DISPLAY, all you have to do is just putting your output from the report into
the Document Container, and the Web Dypro component HRGRT_FC_DOCUMENT_DISPLAY fetches it automatically without you having to tell it.
Code example for sending your form output to the Document Container:
01. data: lv_output_content TYPE xstring.
02. data: lv_header_text TYPE string.
03. GO_OUTPUT_CONTAINER->SET_DOCUMENT
04. (IV_CONTENT = lv_output_content
05. IV_CONTENT_TYPE = cl_hrgrt_document_container=>gc_doc_type-pdf
06. IV_HEADER_TEXT = lv_header_text). " set dynamically in code as/req
07. * set the global index variable for comparison at subsequent event processing
08. gv_prev_lead_index = cv_lead_index. for LIST UIBBs only!!!
09.
Handle Visible Row and Buttons Active/Not Active for List UIBBs

You should call these super class methods towards the end of the processing in method GET_DATA, so that:
1. In method ADJUST_FIRST_VISIBLE_ROW the selected entry in the list is visible in the LIST UIBB.
It can sometimes occur that if the list is longer than the viewing pane allows and the user must scroll through it, the user selects the Next button, and the line
selected is off the bottom of the part of the list currently shown. The correct pay slip is shown, but the user cannot see the selected period in the list.
The method adjusts the list so that the selected period is visible in the viewing pane.
2. In Method HANDLE_PREVIOUS_NEXT_ACTIVATION the buttons Previous and Next on the screen are set to inactive or active. This depends on if after the
current event has finished processing there actually is a previous or next entry in the List.
Note
Example
Syntax
Example
Syntax
PUBLIC
Page 50 of 85
If not, the buttons are greyed out.
Just call these super methods to get this handling.
Code example for handling button activation:
01. IF mv_prev_lead_index NE cv_lead_index
02. OR lv_prev_tab_lines NE lines( lt_data> ).
03. cv_first_visible_row = me->adjust_first_visible_row(
04. iv_lead_index = cv_lead_index
05. iv_first_visible_row = cv_first_visible_row
06. iv_visible_rows = iv_visible_rows
07. iv_max_index = lines( lt_data> )
08. if visible_row should be set according on max. shown entries use:
09. iv_max_index = lines( mt_filtered_rgdir )
10. ).
11. me->handle_prev_next_activation(
12. iv_lead_index = cv_lead_index
13. prev/next only on actual shown entries possible
14. iv_max_index = lines( lt_data> )
15. if prev/next should be set according on max. shown entries use:
16. iv_max_index = lines( mt_filtered_rgdir )
17. mv_prev_lead_index = cv_lead_index
18. ENDIF.
Handle Buttons Active/Not Active for FORM UIBBs

You should call the super class method towards the end of the processing in method GET_DATA, so that the buttons Previous and Next on the screen are set to
inactive or active. This depends on if after the current event has finished processing there actually is a previous or next entry in the set of values, if not, the
buttons are greyed out. You must simply pass the currently selected value and the list of values, the rest is done for you.
Code example for handling button activation:
01. me->handle_prev_next_activation(
02. iv_value = <ls_report_data>-year
03. it_value_list = <ls_field_usage>-fixed_values ).
The Document Container

The HR Reporting reuse class CL_HRGRT_DOCUMENT_CONTAINER, aka the Document Container, is the singleton instance into which you place the output from
your report. This output is then automatically fetched by the Document Display UIBB.
The singleton state is ensured because the constructor is a private method, so it cannot be called externally, but is called internally by method GET_INSTANCE
.At INITIALIZE in your feeder class, you call the super class INITIALIZE method which calls the GET_INSTANCE method of the Document Container. The
attribute GO_INSTANCE on this class is a reference to the class itself, so the method GET_INSTANCE checks if the reference is bound, and only creates the
instance if the reference is still initial.
Activities
Since the Document Display UIBB HRGRT_FC_DOCUMENT_DISPLAY fetches the data from the Document Container, there are only two steps for you to carry out
in your feeder class:
1. At INITIALIZE, ensure the class is instantiated. If you have not redefined this method, this is done for you already in the super method. If you must redefine
for other reasons, all you need do is call the super method, also see Get the Global Data (Method INITIALIZE).
2. At GET_DATA, move the output from your reporting scenario to the Document Container using its method SET_DOCUMENT.
Example
Syntax
Example
Syntax
Note
PUBLIC
Page 51 of 85
See the class constants in GC_DOC_TYPE to know what to use when filling the method parameter IV_CONTENT_TYPE. The method needs to know
whether it is a PDF, spreadsheet and so on.
Currently the only document types supported are PDF and Office types.
Adding Buttons

You can add buttons to your application, either by adding them to the Content Area of the OVP configuration, so they appear at the top of the screen, or you can
add them to a particular UIBB by adding them to the UIBB configuration.
In either case, you assign a Web Dynpro event to the button in the configuration, which you then catch and process during the event loop in GET_DATA of your
feeder class, see also Refining Method GET_DATA.
An example for buttons outside your GUIBB configuration (at the top of the screen) is the Salary Statement reporting application. Here, there is a list of payroll
periods and two buttons at the top of the screen (in the OVP configuration) entitled Previous Statement and Next Statement. You wish to toggle along the
sequence of periods, and at each click, the output for the correct period should be displayed in the lower window (Document Display UIBB).
An example for a button inside your GUIBB is in the Salary Calculator, where once the end user has made the appropriate entries for salary, tax class and so
on, he or she chooses the Calculate button inside the form. Then the output should be displayed in the lower window (Document Display UIBB)
A further example for a button in a UIBB is the Open in New Window button in the Document Display UIBB. Once the end user has chosen the pay slip he or
she wants to see, he or she chooses this button to get a separate and larger output of only the Document Display output.
Add Generic Button

You can add a button in your application configuration, and use the reuse event GC_EVENT_DISPLAY (HRGRT_DISPLAY in the configuration).
SAP recommends to use the generic event HRGRT_DISPLAY but if you need an own event that is very distinct from the idea of producing a form, see Add
Own Button.
At GET_DEFINITION you must call the super method EXPOSE_ACTION_DISPLAY_OUTPUT to expose the event to the configuration for you.
Then all you need to do is create a button in your application configuration and assign event HRGRT_DISPLAY to the button in the configuration, and in your code
at GET_DATA react to the event by producing the form.
Procedure
1. Add the following code (or similar) to your method GET_DEFINITION:
1. expose_action_display_output( changing ct_action_definition = et_action_definition ).
2. Choose Content Area: MAIN_SCREEN in the hierarchy on the left.
3. Choose Add Toolbar Element followed by menu point to content area.
4. In this dialog box, choose Button (without pressing OK).
5. In the field Text, enter the text for your button, for instance Calculate.
6. In the FPM Event ID field, enter the name of the event HRGRT_DISPLAY.
7. Choose Save.
8. Add the following code (or similar) to your method GET_DATA:
Caution
Example
Example
Example
Recommendation
Syntax
Syntax
PUBLIC
Page 52 of 85
2. when gc_event_display.
3. <your handling of event, e.g take results of input, generate output>
4. when others.
5. endcase.
6.
9. Activate your feeder class, place an external break point at this point in the code and test your application: Use the link at the top of this window to go to the
application configuration and choose Test. Choose your new button and the debugger should stop at your code.
Add Own Button

Adding your own button is slightly more effort, but there may be situations where you need further application-specific buttons, or your button cannot really be
described as Display.
Procedure
1. Go to your OVP component configuration in change mode.
2. In your feeder class, create a global constant GC_EVENT_RESET_DEFAULTS (type STRING) and give it the initial value RESET_DEFAULTS.
To make this available to use in the configuration (but it works without this step) you can declare your event (also known as actions) in your method
GET_DEFINITION:
1. DATA ls_action TYPE fpmgb_s_actiondef.
2. * supply actions as available for configuration
3. * Button 'Reset Defaults'
4. ls_action-id = GC_EVENT_ RESET_DEFAULTS.
5. ls_action-text = text-e01.
6. ls_action-enabled = abap_true.
7. ls_action-exposable = abap_true.
8. APPEND ls_action TO et_action_definition.
3. Choose Content Area: MAIN_SCREEN in the hierarchy on the left.
4. Choose Add Toolbar Element followed by menu point to content area.
5. In this dialog box, choose Button (don't press OK instead).
6. In the field Text, enter the text for your button, for example, Reset Defaults.
7. In filed FPM Event ID, enter the name of the event you will program for the event in your feeder class, for example RESET_DEFAULTS.
8. Choose Save.
9. Add the following code (or similar) to your method GET_DATA:
2. when gc_event_reset_defaults.
3. <your handling of event, e.g retrieve default values>
4. when others.
5. endcase.
10. Activate your feeder class, place an external break point at this point in the code and test your application. Use the link at the top of the same screen to go to
the application configuration and choose Test. Choose your new button and the debugger should stop at your code.
Add Previous/ Next Button to List GUIBB

You can add previous and next buttons to your application configuration, and use the reuse events GC_EVENT_NEXT and GC_EVENT_PREVIOUS (HRGRT_NEXT
and HRGRT_PREVIOUS in the configuration).
Procedure
1. At GET_DEFINITION you must call the super method GET_DEFINITION which exposes these event to the configuration for you.
2. Then you create previous and next buttons in your application configuration and assign the events to them.
3. In your code at GET_DATA you must react to these buttons by producing the form.
For precise detail of how to code out GET_DATA, see Refining Method GET_DATA.
Syntax
Syntax
PUBLIC
Page 53 of 85
If you use the words Previous xyz and Next xyz for toggling through a list, we recommend that in your OVP component configuration you assign the icons (in
field Image) ICON_COLUMN_LEFT and ICON_COLUMN_RIGHT respectively to the buttons in the UI.
You should also assign the reuse event GC_EVENT_LINE_SELECT (HRGRT_LINESELECT in the configuration) in the list GUIBB configuration. This reuse
event, as well as the previous and next events, signify that the user wants a new output, thus in GET_DATA your code should at all 3 of these events react by
producing a new form.
Add Previous/ Next Button to Form GUIBB

You can add Previous and Next buttons to your application configuration where you want to toggle up and down the values in a particular field in your form, and
produce a form if the user selects a value directly in the field.
Procedure
1. Find the three reuse events GC_EVENT_NEXT_VALUE, GC_EVENT_NEXT and GC_EVENT_VALUESELECT (HRGRT_NEXT_VALUE, HRGRT_PREV_VALUE
and HRGRT_VALUESELECT in the configuration) in the attributes of your form super class.
2. Since these are optional events, your feeder class must call the three relevant super methods to expose the events to the configuration for you. Add the
following code (or similar) to your method GET_DEFINITION:
1. expose_action_prev_next_value_( changing ct_action_definition = et_action_definition ).
2. expose_action_valueselect( changing ct_action_definition = et_action_definition ).
3. Then you create Previous and Next buttons in your application configuration and assign the events to them.
4. Assign the HRGRT_VALUESELECT directly to the field where the values are held.
5. In your code at GET_DATA you must react to these three events by producing the form. For precise detail of how to code out GET_DATA, see Refining Method
GET_DATA.
Add Buttons to (G)UIBB 'Open in New Window'

When you use the Document display UIBB, it is necessary that you add the following button in your configuration of it. Of course it is possible to add buttons to
other (G)UIBBs in exactly the same fashion as described here.
Procedure
1. Go to your OVP component configuration in change mode.
2. Open Content Area: MAIN_SCREEN in the hierarchy on the left
3. Choose the UIBB FVS_OUTPUT (Document Display UIBB).
4. Choose Add Toolbar Element, followed by menu point Add to UIBB.
5. In this dialog box, ghoose Button (not OK).
A new button appears inside the UIBB.
6. In the Text field, enter the text for your button, for example Open in New Window.
7. In the FPM Event ID field, enter the name of the reuse HRGRT_OPEN_POPUP (you must type this in by hand, unlike for the other events).
The processing is taken care of for you as this is an event already available to as part of the Document Display UIBB component controller.
8. Choose Save.
9. Use the link at the top of this window to go to the application configuration and choose Test. Then choose your new button on the Result screen.
Result
The system generates a dialog box.
Recommendation
Recommendation
Syntax
Note
PUBLIC
Page 54 of 85
Melting Group

In the Floorplan Manager (FPM), melting groups are a way of presenting fields next to each other. This is useful where a field only has meaning when qualified by
another field. A typical example is amount and currency; neither one on its own is particularly meaningful, so we can put them together in a melting group.
Activities
1. Go to your Form UIBB configuration in change mode.
2. Choose Group: General Data in the hierarchy on the left.
3. Choose Add Melting Group and then Configure melting group in succession.
A dialog box with your field catalogue is displayed.
4. In this dialog box, choose the fields BRUTT and WAERS from the available fields and move them over to the displayed fields.
5. Choose OK.
6. In the hierarchy on the left, choose the WAERS field in the melting group.
7. For WAERS, set the Display Type to Text view.
8. Set the label Visibility to None.
9. For BRUTT set the Text to Gross Remuneration.
10. If necessary, delete other usages of the field BRUTT (select field in hierarchy, then Delete button in the attribute maintenance to the right).
11. If necessary, to change the sequence of fields within a group, select the group in the hierarchy, then button Configure Group. A dialog box is displayed.
12. In the dialog box use the Change Sequence buttons to move the fields or field groups up or down.
13. Modify the method GET_DATA in your feeder class, so that the currency is always output as EUR.
1. field-symbols <ls_data> type 'HRXSS_DE_GHR_VC_VCDATA. as field cat.
assign cs_data to ls_data> casting.
2. * set currency 'EUR' as default
3. <ls_data>-waers = 'EUR'.
4. ev_data_changed = abap_true.
14. Test your application in the usual way, see Test Your Application.
Radio Buttons

Radio buttons are fairly easy to implement. In the configuration of your (G)UIBB you can set the Display Type of the element to Radio Button Group. Providing the
values for the field in question are provided by domain values or you have appended the values as fixed values to ET_FIELD_DESCRIPTION-FIXED_VALUES
in method GET_DEFINITION, instead of a drop down list, you can present all values as radio buttons.
The Application Component Controller and its Events

You could regard the Application Component Controller (APPCC) as a helpmeet that is able to do things for you outside your feeder class.
HR Reporting provides the reuse APPCC, HRGRT_C_REPORTING_CONFIG which we recommend you use, but you can also build and assign your own.
The purpose of this reuse component is to hold the processing of what is referred to in this documentation as 'internal events' (that is, internal to the application,
and triggered by super class code, not the user) that you might want to trigger from your feeder class.
You might want to do this because inside your feeder class you have the information to trigger the event, but you must catch and handle them outside the class,
because some of the events make changes to elements of the UI that are not part of your configured Form or List GUIBB. Further, this processing is deliberately
held outside the feeder class, because it is FPM-specific (in this case OVP), whereas the feeder class could feasibly be reused in other floor plans.
While, the feeder class can trigger internal events, the APPCC can catch and process them in the event loop.
An example for using the reuse APPCC is the Salary Statement scenario. There are a list of payroll periods and two buttons at the top of the screen called
Previous Statement and Next Statement. You wish to toggle along the sequence of periods, and once you have reached the last period in the sequence, you
want to deactivate the Next button.
Likewise you want to deactivate the Previous button when you have chosen the first period in the list. This is an example of having the information to trigger an
internal event (activation/deactivation of button) inside the GUIBB (for example, what line has the user selected?) but the internal event itself must be handled
outside, in the application, because the buttons are in the OVP application.
Syntax
Example
PUBLIC
Page 55 of 85
The internal events handled by the APPCC are different and not to be confused with the events that are triggered by the end user, who chooses the buttons
Previous and Next in the UI.
These buttons in the UI have different events to choose the next or previous entry in the list assigned to them, and these events are handled in your feeder
class.
Features
The reuse classes and interfaces provide all the building blocks for you:
The super class of your feeder class has in its attributes all the user events (for example, AC_HRGRT_REPORTING_LIST_FEEDER=>gc_event_next) that
you assign to your buttons in your configuration. You react to these user events in your redefinition GET_DATA by fetching data and producing the form.
Also in GET_DATA you call super methods, which raise internal events (for example, IF_HRGRT_REPORTING_C=>gc_event_enable_event) which are
then caught by the APPCC and processed.
These internal events are stored in interface IF_HRGRT_REPORTING_C and are used only by the super feeder classes and the APPCC.
You should not address them directly in your feeder class!
Activities
Decide if you need such processing of internal events that should be outside your feeder class, and if so, there are two steps: Firstly you must assign HR
Reporting APPCC HRGRT_C_REPORTING_CONFIG to your application in the global settings. Secondly, you must call the super methods from your feeder class
code in method GET_DATA:
1. At the end of GET_DATA in your feeder class, call service method AC_HRGRT_REPORTING_LIST_FEEDER-> HANDLE_PREV_NEXT_ACTIVATION.
In the case of LIST GUIBB you must pass the index of the table, and the number of lines in the table. For FORM GUIBB similarly, you must pass the table of
values and the current value. The super method raises the internal event and takes care of the active/ not active settings. In the APPCC method
OVERRIDE_EVENT_OVP, these events are caught and processed.
2. Go to your OVP component configuration, in change mode.
3. Above the hierarchy (on the left side of the screen), choose Change Global settings .
The dialog box Global Settings is displayed.
4. In the field Web Dynpro Component, enter the reuse component HRGRT_C_REPORTING_CONFIG.
5. Choose OK.
6. Choose Save.
Modifying Titles

There are several titles in your application, and this can be confusing. It is possible to have static or dynamically changing title texts. For example, depending on
the period selection the employee has made, you want to insert that period into the title of the application.
Static Titles
If you want static titles, all you need is to set the texts for the OVP, LIST/FORM GUIBBs and Document Container components in the configuration, as you
normally would. Since the dialog box title is not configurable as a static text, the system defaults the application title as the text for the dialog box. If this is enough
for your application, you do not need to call any of the following methods.
Dynamic Titles
You can only set two titles dynamically:
1. the application title
2. the title for the dialog box (triggered from the button Open in New Window inside the reuse component HRGRT_FC_DOCUMENT_DISPLAY).
You can set the application title either statically in the application configuration, or you can do it dynamically with the super class method SET_APPL_TITLE.
The system defaults the dialog box text either statically from the application title configuration, or you can set it dynamically with the super class method
SET_POPUP_TITLE. If you do not call SET_POPUP_TITLE, then the application title (dynamic if it is there, otherwise static) is duplicated for the dialog box title.
Or in table format:
SET_APPL_TITLE Called? SET_POPUP_TITLE Called? Pop-Up Title Taken from:
No No application configuration title
Yes Yes dynamic pop-up title
Yes No dynamic application title
No Yes dynamic pop-up title
MAIN_SCREEN Text, Method GET_DEFAULT_APPL_TITLE
As a preliminary step, you can at GET_DATA read the text of the main screen configuration with the super class method GET_DEFAULT_APPL_TITLE. This
returns the text from the application configuration MAIN_SCREEN, which you may want as a building block for one of the following titles.
OVP Title, Method SET_APPL_TITLE
Caution
Caution
PUBLIC
Page 56 of 85
You can dynamically modify the OVP title with data you have in one of the components (for example, List UIBB).
For example, you want to add the payroll period to the title, once the user has chosen the payroll period results to be shown from the list of periods. You can do
this in GET_DATA in your feeder class by calling the super class (AC_HRGRT_REPORTING) method SET_APPL_TITLE.
Pop-up Title, Method SET_POPUP_TITLE
The dialog box which is called with the event HRGRT_OPEN_POPUP has a title which you can dynamically modify in GET_DATA in your feeder class by calling
the super class (AC_HRGRT_REPORTING) method SET_POPUP_TITLE.
Restrictions
There is currently in the Document Containers method SET_DOCUMENT a parameter IV_HEADER_TEXT. This parameter is currently not used for anything.
It is not possible (allowed) to change the title in the Document Display UIBB, because the information in the LIST above should be sufficient. Also, dynamic
changing of the title would make the button to the right jump back and forth in the screen, if the dynamic titles were of different lengths, which could be irritating
to the user.
Error Handling

There are basically two ways in which you can produce messages from your feeder class:
1. Firstly you can put messages into the interface parameter ET_MESSAGES of the interface methods GET_DATA, PROCESS_EVENT and CHECK_CONFIG in
your feeder class.
There is the HR assistance class CL_HRESS_FPM_MSG_SERVICES whose methods you can use if you want to convert a table of messages of type
BAPIRET2 or T100 to the format required by ET_MESSAGES.
2. Secondly you can write messages directly (and albeit individually) to the FPM message manager. Inside the FPM class (IF_FPM) that you instantiated at
INITIALIZE, there is an attribute MO_MESSAGE_MANAGER of type IF_FPM_MESSAGE_MANAGER. You can use these methods of this FPM class attribute
(e.g. method report_T100_messages) to write messages to the message handler (there are different methods for different message formats).
Concurrent Employment (CE)

The handling of PERNR, regardless of CE and non-CE scenarios, is taken care of by
the reuse Web Dynpro component HRESS_C_PERNR_SELECTION
the service class CL_HRESS_EMPLOYEE_SERVICES.
More Information
See Step 6: Create the Initial Screen and Event LEAVE_INITIAL_SCREEN on how you can reuse them to ensure your application is CE-compatible.
Troubleshooting

The procedures described in this section are designed to help you analyze problems that arise when configuring reporting services.
Problem 1: The FMP configurator dumps
This can happen for a number of reasons:
1. Session may have timed out. Press F5 to refresh.
2. Check if you have correctly created all methods in your feeder class. Empty is sufficient for all bar the GET_DEFINITION method, where you must at least
have filled the exporting parameters ET_FIELD_CATALOG and the ET_FIELD_DESCRIPTION.
3. If in your feeder class you have calls to methods in the FPM factory class (that your class instantiates at INITIALIZE via the super method) you must
remember that the methods INITIALIZE, GET_PARAMETER_LIST and GET_DEFINITION are called not only at run time, but also at design time by the
FPM configurator. However, this FPM factory class cannot be instantiated except at run time. Thus in these 3 methods, you must encapsulate any actual calls
to the methods of this class, see also the following example.
1. if go_fpm is bound.
2. <your code>
3. endif.
Example
Syntax
PUBLIC
Page 57 of 85
4. See also Problem 4: User variants can cause dumps. You can delete these settings by running Web Dynpro Application WD_ANALYZE_CONFIG_USER in
test mode. Enter your user and the application gives you a list of your user variants. Delete these from the list and retest.
Problem 2: Form and List are Displayed in One Selection Screen
Canadian Tax Form Reprint service is an example of this: The recommendation from FPM is to implement one feeder class, which you assign to both FORM and
LIST GUIBB configurations in your application, so that the class has all data for the form input and list output available locally together.
Your class should inherit from the super class AC_HRGRT_REPORTING_LIST_FEEDER. This super class has services which are more extensive than those in
the FORM super class, In addition you should add the FPM interface IF_FPM_GUIBB_FORM directly to your feeder class, so that you can assign this class to
your FORM configuration. If you need services from the other super class AC_HRGRT_REPORTING_FORM_FEEDER, you can call these methods statically from
your feeder class.
Problem 3: The Fields in the Form are Showing Values Instead of Texts
If you use a search help, this appears to be what the output is. If you use fixed values and set the type of field in the configuration to input field the text appears
instead.
Problem 4: UI Changes are Not Visible in Test Mode
It may happen that you make changes to the configuration of a list or form UIBB, and these changes are not visible when you test your application.
During testing of your scenario in the development system, sometimes user variants are saved automatically by the system. To prevent this, you can add a
parameter to your application:
WDDISABLEUSERPERSONALIZATION, value X.
Make sure you remove this parameter before you release it to the test systems. It should not be part of standard delivery.
You may find that despite setting this parameter, a user variant is created, and you still cannot see changes you have made to your configuration. This even
applies to Event IDs that you might change in the configuration and in the code, and are not correctly recognized at run time, because the old name is stored in the
user configuration and is expected. Obviously a user will never encounter this, but during development you need to see your changes. The solution is to delete
your user configuration by running the application configuration for WD component WD_ANALYZE_CONFIG_USER.
1. Call up transaction SE80 and select WD component WD_ANALYZE_CONFIG_USER.
2. In the tree, select the WD Application Application Configuration Test .
3. Enter your user as parameter, and select Display.
4. Delete the user configuration for the component configuration you are developing.
Alternatively you can delete user variants inside your application by running it in test, then choosing Edit at the top right part of the screen, then choosing
Reset to Defaults.
Problem 5: My UIBBs have no headers
When you test your application, it may be that the headers of your form or list UIBB or the Document Container do not display, so you are unable to see if your title
is correctly showing in the header, or indeed buttons in the header are appearing. Check that the Rendering Type of the UIBBs is always Tray.
Portal Role Employee Self-Service (WDA)
Role: com.sap.pct.erp.ess.wda.Employee_Self_Service_WDA

With this Portal role your employees can access all applications that have been inserted in the role menu assigned to this role in the backend system. This menu
assignment is handled via Application HRESS_A_MENU.
Technically, the Portal role consists of the following objects:
Workset: Employee Self-Service
iView: Overview
Folder Navigation Services with the following navigation iViews:
Appraisal Document
Appraisal Document
Display Form
Configuration
For more information on how the menu that is launched for the Portal role is configured in the backend, see:
Caution
Recommendation
PUBLIC
Page 58 of 85
Workset: Employee Self-Service
Technical Data
Technical Name
com.sap.pct.erp.ess.wda.Employee_Self_Service

This is the only workset in the Business Package for Employee Self-Service (WDA).
Features
The workset contains the Overview page (com.sap.pct.erp.ess.wda.Overview).
From this page, the Overview iView can be started which is used to launch the role menu maintained in the backend in the Launchpad Customizing (transaction
LPD_CUST.
More Information
iView: Overview
Technical Data
Technical Name of the iView
com.sap.pct.erp.ess.wda.Overview
Runtime Technology
Web Dynpro ABAP
Data Source or Data Store
SAP ESS 6.0

This iView in the Portal role Employee Self-Service (WDA) is used to launch the role menu for the Portal role which has been maintained in the backend system.
Users assigned to the Portal role can access all services in the role menu through this iView.
More Information
iViews for Navigation

In the following section you can find the iViews in the Business Package for Employee Self-Service (WDA) that are used as navigation targets for Object Based
Navigation (OBN):
Appraisal Document
Appraisal Document
Display Form
More Information
Appraisal Document
Technical Data
com.sap.pct.erp.ess.wda.Appraisal_Document_PMP
Runtime Technology
Web Dynpro ABAP
SAP ECC 6.0
PUBLIC
Page 59 of 85

This iView is used as a navigation target in the Business Package for Employee Self-Service (WDA). It is used to enable the employee to display or change the
appraisal document used in the predefined Performance Management process.
Integration
This iView is called using Object-Based Navigation (OBN) by the Appraisal Document (PMP) appraisal_document_pmp operation of the Employee
(SAP_ERP_HumanResources.employee) business object .
It is called when the employee calls up the appraisal document from other iViews.
Appraisal Document
Technical Data
com.sap.pct.erp.ess.wda.Appraisal_Document
Runtime Technology
Web Dynpro ABAP
SAP ECC 6.0

This iView is used as a navigation target in the Business Package for Employee Self-Service (WDA). It is used to enable the employee to display or change the
appraisal document used in the flexible appraisal process.
Integration
This iView is called using Object-Based Navigation (OBN) by the Appraisal Document (WD UI) appraisal_document_wd_ui operation of the Employee
(SAP_ERP_HumanResources.employee) business object.
It is called when the employee calls up the appraisal document from other iViews.
Display Form
Technical Data
com.sap.pct.erp.ess.wda.Display_Form
Runtime Technology
Web Dynpro ABAP
SAP ECC 6.0

This HCM Processes and Forms iView is used as a navigation target in the Business Package for Employee Self-Service (WDA).
This service is accessed using Object-Based Navigation (OBN) by the Display Form (display_form) operation of the Employee
(SAP_ERP_HumanResources.employee) business object.
This iView is accessed when the employee displays a form used for HCM Prosesses and Forms from another iView.
More Information
Employee
Services Available for Employee Self-Service (WDA)

In this section, you can find the services that are available for Employee Self-Service (WDA).
Features
For ESS (WDA), international and country-specific services are available.
In the standard delivery, the services provided with the role menu are grouped in the following areas:
My Processes
Working Time
Benefits and Payment
Personal Information
PUBLIC
Page 60 of 85
Career and Development
Purchasing
Work Events
Travel and Expenses
In these areas, you can find both international and country-specific services. The only area that contains exclusively country-specific services is the Work
Events area, with services from the E-Separation Solution for India.
All services available are described under the following sections:
International Services
Country-Specific Services and Localizations
International Services

This section provides information about the international applications (services) that are available in the Employee Self-Service (WDA) component. The individual
applications are assigned to the following areas:
My Processes
Working Time
Purchasing
Travel and Expenses
My Processes

In this area, you can use the Status Overview service.
Status Overview

An employee uses this service to view the status of his or her processes.
For detailed information, see the documentation for the Sample Processes.
Technical Data
Web Dynpro Application ASR_PROCESSES_DISPLAY
Web Dynpro Application Package PAOC_ASR_WD_PROCESS_BROWSER
Application Configuration HR_ASR_LIST
Web Dynpro Components HRASR00_PROCESS_BROWSER, POBJ__BROWSER
Component Configurations HR_ASR_LIST
Application Component Controller Not relevant
Software Component EA-HRGXX
Support PA-AS
Available in the Composite Role From SAP enhancement package 5 for SAP ERP 6.0
Required Business Function HCM_ASR_CI_3
Configuration
In the standard system, this service uses the WD configuration HR_ASR_LIST for the Web Dynpro application ASR_PROCESSES_DISPLAY.
In the standard system, the following application parameters are passed to the service:
BROWSER_CONTEXT = AFFECTED_EE_OVERVIEW
WDCONFIGURATIONID = HR_ASR_LIST
PERNR_MEM_ID = ESS01
Note
PUBLIC
Page 61 of 85
Working Time
Record Working Time

Technical Data
Web Dynpro Application HRESS_A_CATS_1
Web Dynpro Application Package PAOC_CATS_ESS_WDA
Application Configuration HRESS_AC_CATS_1
Web Dynpro Components HRESS_C_CATS
Component Configurations HRESS_CC_CATS_1
Data Origin HRESS_CAT_WDA_RECORD
Software Component EA-HR
This service enables your employees to record their working times and assign these to a project, order, or other SAP application objects. You can also connect an
optional approval procedure.
Prerequisites
You do the following:
Use SAP Cross-Application Time Sheet (CATS).
Set up the Time Sheet. For the service, you can use the model data entry profile ESS, which meets the requirements of Employee Self-Service (ESS).
You can make the necessary Customizing settings for the Cross-Application Time Sheet under Personnel Management Employee Self-Service (Web
Dynpro ABAP) Service-Specific Settings Working Time Record Working Time Record Working Time .
Create personnel numbers in the SAP system for all employees who are to record data. The personnel number must be related to the employees system user
name in the Communication (0105) infotype. For more information, see Assigning an SAP User ID to a Personnel Number.
Use the user CATS variant (CVR) parameter to assign each employee a specific data entry profile, which they use to enter their working times. This profile
determines the data entry process and the layout of the time sheet.
If this user parameter has not been stored, the system uses the ESS data entry profile as standard.
Assign the required authorizations to all users.
Configuration
The application configuration HRESS_AC_CATS_1 is provided by default and allows you to provide default values for the application parameters. It also allows
you to specify the layout and appearance of the application.
The following application parameters are provided:
HIDE_CLOCK_TIMES_IN_WEEKLY
Hides the clock times in the weekly view.
MULTIPLE_PROFILE
Enables the selection of multiple data entry profiles from the dropdown list.
Features
This service is available in the Business Package for Employee Self-Service (mySAP ERP). For more information, see Employee Self-Service.
This application has been developed for the software component EA-HR. Subsequent enhancements and corrections to the software are available in HR
Support Packages.
HR-Enabled CATS integrates the HR and CATS systems. The following enhancements are available:
The Time Accounts tab displays an employees leave request data from the Leave Request application.
The Work Schedule button enables an employee to see their weekly or bi-weekly work schedule. If an employee has an approved leave request on a
specific day, it shows in their timesheet as a non editable line. An employee can import the times from their work schedule to their timesheet.
Approved leave requests display in an employees time sheet. In Customizing, you must select the Subtract HR hours checkbox if the user wants to see
their approved leave requests in their timesheet.
Holidays are marked in the calendar as Holiday. You can use BAdI: CATS Partial Day Public Holiday Display (HRESS_CATS_PUB_HOLIDAY_ENH) to
Note
PUBLIC
Page 62 of 85
define the number of hours for a half day public holiday.
You can make the relevant Customizing settings for Record Working Time under Employee Self-Service (Web Dynpro ABAP) Service-Specific Settings
Working Time Record Working Time .
The Summary display gives details of how many days an employee has recorded in the last three months, with time recordings greater or less than 100%.
This calculation is done when the application is loaded. Changes to the timesheet are not visible until they are saved.
The color status in the calendar changes when the employee releases their time recordings. Employees can also display the payroll period end date and the
last date for time recording. You can use BAdI: Calendar Legend for Recording Working Times (HRESS_CATS_CAL_LEGEND_ENH) to set the calendar
legend display. You can change the color of the items in the calendar legend, the display, and text. You cannot add additional legend items to the list.
The Working Time homepage includes dynamic links to the individual services, to provide employees with as much information as possible, as simply as
possible. For more information, see Services for CATS regular (Web Dynpro ABAP).
Multiple views are available for recording working times:
Weekly View: The weekly view always displays one week. It provides employees with a quick overview of their working time recorded for the week. In
Customizing, you can select either a vertical list view or a horizontal list view, using transaction code CAC1. The weekly view is ideal for employees who
record few activities or working time attributes on a particular day.
Bi-weekly View: The bi-weekly view provides employees with a quick overview of all the data they have recorded for two weeks. If you select a vertical list
view in Customizing using transaction code CAC1, employees can view all clock times without having to scroll horizontally. Employees can enter clock times
for bi-weekly periods but they cannot use the template functionality.
Daily View: The daily view provides employees with a quick overview of all the data they have recorded for a particular day. In addition to the fields available
in the weekly view, the daily view enables employees to record their activities with clock times (depending on the profile settings) and add a short text.
Employees can provide additional information about any given data record by opening its detail screen. For example, employees can enter confirmation
information for a network or enter further information about a data record in the form of a long text.
A calendar is integrated on the data entry screen. This calendar provides employees with a quick overview of the days on which they have recorded too many
or too few working hours, over a period of several months. It also displays the days for which unreleased or rejected data records exist. If there are multiple
status information texts for one day, the most important one is displayed.
You can use BAdI: Calendar Display for Recording Working Times (HRESS_CATS_CAL_DISPL) to display the summary information in the Calendar area. The
default implementation of the BAdI returns a line of text and the time recording cutoff date according to Customizing settings in the data entry profile. If CATS is
integrated with HR, the payroll period end date is read-only.
Employees can change the data entry period. They can do this by entering a date in the desired week and choosing Go, by choosing a particular day in the
calendar to display the appropriate week and data entry section, or by choosing the arrow keys to display the previous and next period.
Employees can use a worklist if the profile settings permit this. The worklist makes it easier to record their working times as it allows employees to copy
information about planned activities to the data entry section quickly.
Employees can save the working time attributes recorded for a particular week or day as a personal template or favorite.
Employees can use a search function to display a list of possible values for most working time attributes. The system can automatically determine important
working time attributes, such as the sender cost center, the controlling area, or the activity type from the employees HR master record.
If the working time attributes displayed are identical, the rows in the data entry section are merged. Note that in the merged rows the working time attributes that
are not displayed in the service may vary.
If you want to have the data approved, you can use the approval workflow.
Employees can print the timesheet data by selecting the Print icon in the timesheet. In the selection options, they can select the timesheet layout and period.
You can use BAdI: PDF Print Form for CATS (HRESS_CATS_PRINT_FROM) to provide the layout form names and the PDF data to the print form.
You can restrict the employees navigation in the timesheet by configuring the profile accordingly.
You can personalize the appearance of the timesheet by hiding columns or by changing the order in which some columns appear. You cannot change the
order in which the day and details columns appear. If you change the order of these columns, for example, move Wednesday before Tuesday, the system
reverses your change.
You can enable employees select from multiple data entry profiles on the Record Working Time screen, by setting the MULTIPLE_PROFILE parameter to X.
You can use BAdI: Data Entry Profile Filter (HRESS_CATS_PROFILE_FILTER_ENH) to control the list of profiles that appears to the employee.
Employees can directly release their timesheet data by using the Release Directly button. The modified data in the timesheet is automatically saved, and the
data in the current period is automatically released. You can use BAdI: Direct Release Confirmation Text Change (HRESS_CATS_DIRECT_RELEASE_ENH) to
redefine the confirmation text the employee sees after releasing their data.
Create Leave Request

PUBLIC
Page 63 of 85
Technical Data
Web Dynpro Application HRESS_A_PTARQ_LEAVREQ_APPL
Web Dynpro Application Package PAOC_TIM_ESS_WDA
Application Configuration HRESS_AC_PTARQ_LEAVREQ
Web Dynpro Components FPM_OVP_COMPONENT,
HRESS_C_PTARQ_LEA_APP_CC,
HRESS_C_LEA_EMP_CALENDAR
Component Configurations HRESS_CC_PTARQ_LEAVREQ,
HRESS_CC_LEA_CONFIG,
HRESS_CC_GUIBBF_LEAVREQ,
HRESS_CC_GUIBBF_LEAVREQDIALOG,
HRESS_CC_GUIBBF_LEAVREQFOCUS,
HRESS_CC_GUIBBL_PTARQ_LEAVREQ,
HRESS_CC_GUIBBT_PTARQ_LEAVREQ
Application Component Controller HRESS_C_PTARQ_LEA_APP_CC
Data Origin SAP ECC 5.0 and higher
RFC function modules called:
PT_ARQ_ACCOUNTS_GET,
PT_ARQ_CUSTOMIZING_GET,
PT_ARQ_EECALE_GET,
PT_ARQ_REQLIST_GET,
PT_ARQ_REQUEST_CHECK,
PT_ARQ_REQUEST_EXECUTE,
PT_ARQ_REQUEST_PREPARE,
PT_ARQ_SEARCH_NEXT_PROCESSOR,
PT_ARQ_TEAMCALE_GET,
PT_ARQ_ACCOUNTS_GET_CE,
PT_ARQ_REQLIST_GET_CE
Software Component for Web Dynpro Application EA-HR
Required Business Function HCM_ESS_WDA
Employees can use this service to request leave, or other absences or attendances. They can also use this service for absences that do not require approval, for
example, sick leave, to inform their manager that they will be absent for a certain time period. Employees can change or delete submitted leave requests or
absences that have already been stored in the database, if necessary.
If the concurrent employment functionality has been activated, employees can record or edit a leave for the relevant personnel assignment when they start the
application.
Integration
The Leave Request application includes the following tasks:
Creation of leave request by employee
Forwarding leave request to manager for approval
The interfaces used by employees and managers when they process leave requests are WebDynpro ABAP applications that belong to Employee Self-Service
(ESS) and Manager Self-Service (MSS).
The Leave Request application includes the following services that are tailored to the needs of employees and managers, and provide practical contextual
information:
Create Leave Request: The service for employees who want to request, change, or cancel leave.
You can use this function only if your employees enter their own leave requests in Employee Self-Service. It is not suitable if you have time administrators
record absences.
Approve Leave Request : The service for managers who want to approve the leave requests.
You do not have to implement this service. Alternatively, you can use a simple backend report.
Your employees can use the Create Leave Request service to request both absences (infotype 2001) and attendances (infotype 2002). You can also process
records of the Attendances infotype (2002) that have the quality of an absence in your company, such as training courses.
The Leave Request application has automatic control of the processing process. You can make Customizing settings for groups of employees to control
aspects such as:
Which absence and attendance types employees are permitted to request.
The periods before and after an absence during which employees are permitted to request leave in advance or retroactively. You can define different periods
for different absence and attendance types.
Note
Note
PUBLIC
Page 64 of 85
The actions an employee is permitted to carry out. For example, you can specify whether an employee is permitted to change or delete an absence that has
already been approved.
Several reports are available in the backend system to control the processing. The reports send e-mails to employees to notify them of the status of their leave
request. Approvers and time administrators are notified of leave requests that they have to process. You can schedule the reports as a periodic background
process. If you want to useSAP Business Workflow, the same reports are processed with the corresponding workflow tasks. For more information about the
workflow, see General Workflow for Documents.
You can use Business Add-Ins (BAdIs) to customize the service to suit your requirements. For example, you can adjust the processing process to suit your
needs, or import and change data.
For more information, see Customizing for Personnel Management under Employee Self-Service (Web Dynpro ABAP) Service-Specific Settings Working
Time Leave Request Business Add-Ins (BAdIs)
Prerequisites
You have integrated the services with the relevant portal pages. For more information, see the documentation for ESS and MSS:
Business Package for Manager Self-Service (MSS).
You have set up the service in Customizing. For more information, see Customizing under Personnel Management Employee Self-Service (Web Dynpro
ABAP) Service-Specific Settings Working Time Leave Request
You use SAP Time Management to manage your employees' time data.
Features
This service provides the following features to enable employees plan and record their absences:
Employees can request leave and other absences, and enter notifications of sickness and other absences that do not require approval.
The Team Calendar enables employees to check their desired periods of leave against other team members' leave.
This function also exists as a standalone Service in Manager Self-Service. For more information, see Team Calendar.
The Calendar gives employees a three-month overview of their booked and requested absences.
The Leave Overview enables employees to view their absences and track the status of their requests.
Employees can cancel, shorten, or lengthen absences. To do this, they select the relevant absence from the Leave Overview in the Team Calendar or
Calendar.
The Time Accounts function provides employees with an overview of their absence entitlements and attendance approvals. Employees can check their
remaining entitlement before requesting a new leave. This feature also exists as a standalone service, View Time Account Balances.
For information about the data sources and possible settings for this function, see Data Origin of Time Accounts and Customizing for Employee Self-Service
(Web Dynpro ABAP) under Service-Specifc Settings Working Time Time Accounts .
The information displayed in the Team Calendar, Leave Overview, and Time Accounts is only updated after an employee has submitted a leave request.
Leave Overview

Note
PUBLIC
Page 65 of 85
Technical Data
Web Dynpro Application HRESS_A_PTARQ_LEAVREQ_APPL
Application Configuration HRESS_AC_PTARQ_LEAVREQ_APPL
HRESS_C_PTARQ_LEA_APP_CC
Component Configurations HRESS_CC_PTARQ_LEAVREQ,
HRESS_CC_LEA_CONFIG,
HRESS_CC_GUIBBF_LEAVREQ,
HRESS_CC_GUIBBF_LEAVREQDIALOG,
HRESS_CC_GUIBBF_LEAVREQFOCUS,
HRESS_CC_GUIBBL_PTARQ_LEAVREQ,
HRESS_CC_GUIBBT_PTARQ_LEAVREQ,
HRESS_CC_GUIBBT_PTARQ_LEAVREQ_AC
Application Component Controller HRESS_C_PTARQ_LEA_APP_CC
Data Origin SAP ECC 5.0 and higher RFC function modules called:
PT_ARQ_ACCOUNTS_GET,
PT_ARQ_CUSTOMIZING_GET,
PT_ARQ_REQLIST_GET,
PT_ARQ_REQLIST_GET_CE,
PT_ARQ_ACCOUNTS_GET_CE
You can use this service to display and track the status of leave requests you have requested. Existing leave or other types of absences can be reviewed,
changed, or cancelled.
Prerequisites
You have integrated the Web applications with the relevant portal pages. For more information, see the Business Package for Manager Self-Service (MSS).
You have set up the Web application in Customizing. For more information, see Customizing under Personnel Management Employee Self-Service (Web
Dynpro ABAP) Service-Specific Settings Working Time Leave Request .
You have made the Customizing settings for the Leave Request, Time Accounts, and Team Calendar. For more information, see Customizing for Personnel
Management under Employee Self-Service (Web Dynpro ABAP) Service-Specific Settings Working Time .
Features
The Leave Overview application comprises the following tasks:
Status tracking and monitoring
The Time Accounts function provides employees with an overview of their absence entitlements and attendance approvals. Employees can check their
remaining entitlement before requesting a new leave. This feature also exists as a standalone service, View Time Account Balances.
Employees can request leave and other absences, and enter notifications of sickness and other absences that do not require approval.
View Time Account Balances

PUBLIC
Page 66 of 85
Technical Data
Web Dynpro Application HRESS_A_PTARQ_TIMEACC
Application Configuration HRESS_AC_PTARQ_TIMEACC
Component Configurations HRESS_CC_OVP_PTARQ_TIMEACC
Data Origin SAP ECC 6.00 and higher
RFC function modules called: PT_ARQ_ACCOUNTS_GET
PT_ARQ_ACCOUNTS_CE
This service enables employees to check their time credits, such as leave and time-off entitlements. It provides them with the necessary information they need to
plan their leave. It also provides information about the deduction periods in their time accounts. Depending on the business processes you use to manage your
employee's time data, you can display information from time accounts of various different data sources.
Prerequisites
You use SAP Time Management to manage your employees time data.
You have made the necessary Customizing settings for these services. For more information, see Customizing for Personnel Management under Employee
Self-Service (Web Dynpro ABAP) Service-Specific Settings Working Time Time Accounts .
Features
This service enables you to output time accounts from the following sources:
The Attendance Quotas infotype (2007)
The Absence Quotas infotype (2006)
Absence quotas and time types as time evaluation results from cluster B2.
The transparent table PTQUODED (Deduction of Time Quotas)
Data from the request database: depending on the Customizing settings, you can include leave requests that have not yet been approved when you calculate
the remaining absence entitlement.
Data from the Leave Entitlement infotype (0005)
The BAdI, BAdI:Enhancements for Leave Requests (PT_ABS_REQ) uses the function module HR_GET_QUOTA_DATA to determine the time accounts. The
BAdI enables you to read this function module with particular parameters. In the standard implementation of the BAdI, the system determines time accounts as
follows:
It reads attendance quotas from the Attendance Quotas infotype (2007).
Absence quotas:
For employees who participate in Time Evaluation, (Time Management Status is unequal to 0 in the Planned Working Time infotype (0007))
Up to the Retroactive Accounting Date BDE (Payroll Status infotype (0003)): absence quota data from cluster B2 if the key date is later than this date.
For times after the Retroactive Accounting Date BDE: data from the Absence Quotas infotype (2006) if the key date is later than the retroactive
accounting date.
If the cluster table has not been filled because you have not implemented the QUOTA function: absence quota data from the Absence Quotas infotype
(2006).
For employees who do not participate in Time Evaluation, (Time Management Status is equal to 0 in the Planned Working Time infotpye (0007)), the
system reads absence quota data from the Absence Quotas infotype (2006).
If you want to display Time Types from the cluster or data from the Leave Entitlement infotype (0005), you can use other methods of the BAdI,
BAdI:Enhancements for Leave Requests (PT_ABS_REQ) to provide data for this service. For more information, see the BAdI documentation using
transaction SE18.
If you use Time Evaluation, employees can also check their expected future leave entitlement. To do this, employees enter a key date in the future. Time
Evaluation simulates the entitlement that is expected on this key date. This is particularly useful if at your company you periodically accrue leave entitlement
according to the time that employees have worked.
For more information, see Simulation and Projection of Time Evaluation Results.
You can use this application in various services:
As a standalone service, View Time Account Balances. You can use it in the following situations:
In addition to the time accounts in the Leave Request application, you want to provide a separate service for displaying time accounts.
You do not use the Leave Request application but you want to provide your employees with a service that gives them information about their current time
accounts.
As part of the Leave Request application. Employees can expand the application as and when they need to use it.
As part of the Leave Request Approval application. Time accounts can be used to evaluate a leave request.
Note
Note
PUBLIC
Page 67 of 85
View Time Account Balances enables employees to check not only their current entitlement, but also past or future entitlements.
In the standalone application, time accounts are displayed in relation to a particular key date and for a specific quota. Employees can select the key date and
the quota that is to be displayed in the service. Alternatively, they can obtain an overview of all their time accounts. Quotas are displayed for each deduction
period.
In the Leave Request application, all time accounts are displayed that can be deducted on the current date.
The standard system provides employees with the following information from quota management:
Existing attendance and absence quotas
Deduction period
Total entitlement
Remaining entitlement
If required, you can show additional fields by making the relevant settings in Customizing for Web Dynpro interfaces. To determine which additional fields exist,
see the Test Report for UIA Interface for Leave Requests report (RPTARQUIATEST).
1. If the system is enabled for processing Concurrent Employment:
In the standalone service, View Time Account Balances the employee can see the quota details of all personnel assignments.
Additionally, the standard system provides employees with the following information from quota management:
Multiple assignment (Shared Quota): this indicates whether an absence quota is shared across a persons assignments.
Request a Change in Employment Percentage

Technical Data
Web Dynpro Application ASR_PROCESS_EXECUTE_FPM
Web Dynpro Application Package PAOC_ASR_WD_PROCESS_EXECUTE
Application Configuration ASR_EXECUTE_4_STEP_PA_CE
Web Dynpro Components FPM_GAF_COMPONENT
FPM_IDR_COMPONENT
Component Configurations ASR_EXECUTE_4_STEP_PA_CE_GAF
ASR_PROCESS_EXECUTE_IDR
Application Component Controller HRASR00_PROCESS_EXECUTE_1
Support PA-AS
An employee can use this service to request a change to his or her employment percentage here.
The service is provided as a model in the standard system. You can, however, create and implement customer-specific services at any time.
The Request a Change in Employment Percentage service in ESS is assigned to the Change Working Time (International) process in HR Administrative
Services. For detailed information, see the documentation for the Sample Processes.
Prerequisites
To use the service, take note of the following:
Validity of the service
Employee can access the service through a link only if the process, and therefore the service, are valid. If they are not valid, the link is grayed out and cannot
be used.
Authorization for the service
The service is displayed only if the employee has the required authorization. For detailed information, see Customizing for HR Administrative Services (PA-AS).
For detailed information, see Customizing for HR Administrative Services (PA-AS).
You have made the necessary Customizing settings for the service. Choose:
HR Administrative Services Configuration of Forms/Processes Process Configuration Set Up Processes Validity for Process Start
Carry out all the required Customizing activities.
HR Administrative Services Authorizations
HR Administrative Services HR Administrator Start Application for Processes
Configuration
The following parameters (and their values) are passed to the WD application ASR_PROCESS_EXECUTE_FPM:
PROCESS (HR_PA_XX_CHANGE_WORKINGTIME_1)
WDCONFIGURATIONID (ASR_EXECUTE_4_STEP_PA_CE)
INITIATOR_ROLE (HRASRD)
Caution
PUBLIC
Page 68 of 85
Clock-In/Out Corrections (Web Dynpro ABAP)

Technical Data
Web Dynpro Application HRESS_A_CORRECTIONS
Application Configuration HRESS_AC_CORRECTIONS
Web Dynpro Components HRESS_C_CORRECTIONS
Component Configurations HRESS_CC_OVP_CORRECTIONS
Employees can use this Web application, with the help of a weekly overview graphical interface, to correct errors that originated at the time recording terminal. For
example, they can correct duplicate clock in entries, enter missing time recordings, and enter account assignment data. An optional monitoring function validates
entries that employees change, delete, or create manually. An optional approval procedure approves entries that employees change, delete, or create manually.
Employees should continue to use the time recording terminal to record working times. This application enables employees to clock in and clock out using the
Enterprise Portal and to correct incorrect time recording data.
Prerequisites
You have done the following:
Implemented Time Evaluation for SAP Time Management.
Implemented the HR-PDC interface to transfer employees clock in and clock out entries from an external time recording system to the SAP system.
You can make the relevant Customizing settings for Personnel Time Management under Personnel Time Events Personnel Time Events .
Configured the Clock-In/Out Corrections Web application.
You can make the relevant Customizing settings for Personnel Management under Employee Self-Service (Web Dynpro ABAP) Service-Specific Settings
Working Time Clock-In/Out Corrections .
Made the following settings in the Communication infotype (0105) for all employees:
Specified the system user name in subtype 0001 (System User Name SAP System (SY-UNAME)).
Stored the e-mail address in the subtype 0010 (E-Mail)
.
Features
The following features are available:
Employees can use this Web application to correct errors that occur when they post time events at external time recording terminals. For example, they may
clock in twice instead of once, or they may forget to clock in or clock out. These errors are detected by time evaluations, but employees using this Web
application ensure time administrators only correct errors that employees cannot correct.
You can Customize time evaluation messages if employees must correct errors in their time events. Employees are notified by email to make their corrections.
If necessary, you can connect time evaluation to the Web application so employees can confirm immediately if their corrections are successful.
Employees can use this Web application to correct errors that time evaluation cannot detect. For example, incorrect account assignment information, or missing
entries on a day on which the employee was not scheduled to work and worked overtime. In Customizing, you can define which corrections an employee is
allowed to make.
We recommend you authorize employees to edit only time event types that they are permitted to use at the time recording terminal.
We recommend you do not authorize employees to overwrite corrections entered by the time administrator in the Time Events infotype (2011). These entries
are locked for processing with the Web application.
The Web application automatically controls the way in which time recordings are processed:
In Customizing you can specify which groups of employees are permitted to carry out which actions. For example, you can specify that a group of
employees is permitted to make corrections only if the time evaluation issues a message, or that the group is not permitted to create any new clock in or
clock out entries.
The clock in and clock out corrections are not saved directly in the TEVEN table. Instead, they are buffered in other tables so you can integrate checking and
approval processes to avoid incorrect entries, and to confirm employees' entries.
Note
Recommendation
Recommendation
PUBLIC
Page 69 of 85
Several reports are available to notify employees, managers, and HR administrators that they have clock in and clock out corrections they must edit, confirm,
or approve.
You can integrate an approval procedure with the Web application. You can incorporate the field for selecting an approver in your field selection for the Web
application. You can schedule the reports as a periodic background process. If you want to use SAP Business Workflow, the same reports are processed
with the corresponding workflow templates.
For more information, see General Workflow for Documents.
Employees can use the Web application to view their time balances. These are the same balances that are downloaded at the terminals.
Employees can view the time and date of their time events at a glance in a weekly overview.
The weekly overview is always related to one week. You can set the first day of the week and the portion of the day that is displayed for groups of employees.
In the header row of the data entry area, employees can check the work schedules that apply on that day. If there is more important information for a
particular day, such as vacation, it overwrites the work schedule information.
Partial-day absences without clock times, full day public holidays, and partial-day public holidays are displayed in a separate line in the header of the data
entry area. The display of an off-day takes precedence over the display of a public holiday.
When employees enter clock in and clock out times, the system provides dynamic default values which are determined according to the cursor position in
the application and in relation to the work schedule.
If you have not connected to an approval procedure, you can define in Customizing that the time evaluation for the employee starts after the data is saved.
Employees starting the application can confirm immediately whether their corrections have been made.
If you use this function, the response times might be slower when the system is saving data.
You can use Business Add-Ins (BAdIs) to customize the Web application to suit your requirements.
For more information, see Customizing for Clock-In/Out Corrections under Employee Self-Service (Web Dynpro ABAP) Service-Specific Settings
Working Time .
Time Statement with Date Selection

Technical Data
Web Dynpro Application HRESS_A_TIME_DATESEL
Web Dynpro Application Package PAOC_ESS_TIME_STATEMENT_
Application Configuration HRESS_AC_TIM_DATESEL_OVP
FPM_FORM_UIBB
Component Configurations HRESS_CC_TIM_DATESEL,
HRESS_CC_TIM_DATESEL_OVP
Application Component Controller HRGRT_C_REPORTING_CONFIG
Data Origin Cluster B2
Employees can use this service to view their time statements for a chosen interval. The employee selects the desired interval by selecting the start date and end
date.
Features
The service is based on the Time Statement Using the HR Forms Workplace and SAP Smart Forms.
For more information, see Time Statement Using the HR Forms Workplace.
Your employees may print the time statement from the Web application or save it on their PC.
Prerequisites
You implement Time Evaluation for SAP Time Management.
You have configured the Time Statement Using the HR Forms Workplace.
You have stored the name of the required print report for the services in the HRFOR feature (HR Forms Decision Feature).
For more information, see Customizing for Personnel Managementunder Employee Self-Service (Web Dynpro ABAP) Service-Specific Settings Working
Time Time Statement .
The time statement is output as a PDF-based form. Your employees can print the time statement from the Web application or save it on their PC.
Note
PUBLIC
Page 70 of 85
Time Statement with Period Selection

Technical Data
Web Dynpro Application HRESS_A_TIME_PERSEL
Web Dynpro Application Package PAOC_ESS_TIME_STATEMENT_WDA
Application Configuration HRESS_AC_TIM_PERIODSEL_OVP
FPM_LIST_UIBB
Component Configurations HRESS_CC_TIM_PERIODSEL,
HRESS_CC_TIM_PERIODSEL_OVP
Data Origin Cluster B2
Employees can use this service to display their time statements for any period they require.The employee selects the desired period in the overview selection
table. The table provides the begin date and end date of the period, and additional information such as wage types and time types is also displayed.
Features
This service is based on the Time Statement Using the HR Forms Workplace and SAP Smart Forms. For more information, see Time Statement Using the HR
Forms Workplace.
The time statement is output as a PDF-based form. Your employees can print the time statement from the Web application or save it on their PC.
Prerequisites
You implement Time Evaluation for SAP Time Management.
You have configured Time Statement Using the HR Forms Workplace.
You have stored the name of the required print report for the services in the HRFOR feature (HR Forms Decision Feature).
For more information, see Customizing for Personnel Management under Employee Self-Service (Web Dynpro ABAP) Service-Specific Settings Working
Time Time Statement .
Your employees have a program for displaying PDF-based forms installed on their PCs.
Salary Statement

Technical Data
Web Dynpro Application HRESS_A_PAYSLIP
Package of Web Dynpro Application PAOC_ESS_PAYSLIP
Application Configuration HRESS_AC_PAYSLIP
Web Dynpro Components FPM_LIST_UIBB, FPM_OVP_COMPONENT
Component Configuration HRESS_CC_LIST_PAYSLIP, HRESS_CC_OVP_PAYSLIP
Data Source Not applicable
Software Component of Web Dynpro Application HRGRT_C_REPORTING_CONFIG
Prerequisite Business Function HCM_ESS_WDA_1
PUBLIC
Page 71 of 85
This service gives employees a detailed list of monetary amounts and information for a selected time period. The statement consists of the following:
Gross amount (for example: incoming payments)
Net amount (for example: deductions)
Outgoing payments (example: bank transfers)
Additional information (for example: organizational assignment, vacation, notifications to the employee)
You receive one or more salary statements for a selected period. This service is based on the salary statement created with the HR Forms Workplace
(HRFORMS) or the salary statement created with the HR Form Editor (PE51). The salary statement is output as a PDF form. Your employees can print the salary
statements from the Web application or save them as files.
For more information about the tools, see SAP Library under Human Resources HR Tools HR Forms Workplace or HR Form Editor .
Configuration
You make the required settings for the service in Customizing for the salary statement. To do this, choose Personnel Management Employee Self-Service
(Web Dynpro ABAP) Service-Specific Settings Benefits and Payment Salary Statement .
You make the required settings for the salary statement of a selected country in Customizing for the relevant country version.
For more information about configuring this service, see Floorplan Manager for Web Dynpro ABAP. If you want to replace the standard system message texts with
customer-specific message texts, see Message Mapping for more details.
Total Compensation Statement

Technical Data
Web Dynpro Application HRESS_A_TCS
Package of Web Dynpro Application PAOC_ESS_TCS_WDA
Application Configuration HRESS_AC_TCS_OVP
Web Dynpro Components FPM_OVP_COMPONENT, HRESS_C_PERNR_SELECTION, FPM_FORM_UIBB,
HRGRT_FC_DOCUMENT_DISPLAY
Component Configuration HRESS_CC_TCS_FORM, HRESS_CC_TCS_OVP
Data Source Infotypes and payroll results
Software Component of Web Dynpro Application EA-HRRXX
Prerequisite Business Function HCM_ESS_WDA_1
Employees can use this service to display their total compensation statement. The total compensation statement is an online PDF statement that contains a list of
all compensation elements and benefits paid to an employee by the company in a certain time period (typically one year).
Configuration
Form for the Total Compensation Statement
The standard form delivered with the SAP system (HR_CMP_TCS) consists of various categories and subcategories that you can adjust to suit your company's
requirements.
PAY Payment
Salary and bonus
CMP - Other compensation
Various compensation elements including long-term incentives
BEN - Benefits
Benefits plans in which the employee takes part or has taken part
PDV - Personnel development
Individual development plans, education, and training
You can add your own categories and subcategories in Customizing for Enterprise Compensation Management under Compensation Statements Determine
Structure of Total Compensation Statement .
You can specify which wage types are used for the Bonus and Salary subcategories of the Payment category. This enables the system to calculate a total
amount from the payroll results for the relevant category.
HR master data
Edit the following infotypes for calling the header data (personnel number, personnel area, personnel subarea, personnel group, personnel subgroup, and so on):
Organizational Assignment (0001)
Personal Data (0002)
Feature ADDR
Edit this feature to determine the employee addresses displayed in the header of the total compensation statement. In the standard system, the employee's
Note
PUBLIC
Page 72 of 85
permanent residence (subtype 1) from the Addresses infotype (0006) is used.
Sports Club Fees

Technical Data
FPM_IDR_COMPONENT
Support PA-AS
An employee can use this service to request a deduction of sports club membership fees directly from his or her salary.
The service is provided as a model in the standard system, you can, however, create and implement customer-specific services at any time.
The Sports Club Fees service in Employee Self-Service (ESS) is assigned to the Membership Fees Sports Club (International) process in HR Administrative
Services. For detailed information, see the documentation for the Sample Processes.
Prerequisites
be used.
The service is displayed only if the employee has the required authorization. For detailed information, see Customizing for HR Administrative Services (PA-
AS).
Configuration
PROCESS (HR_PA_XX_MEMBERSHIP_FEES)
Request Car Loan

Caution
PUBLIC
Page 73 of 85
Technical Data
FPM_IDR_COMPONENT
Support PA-AS
An employee can use this service to request a car loan from his or her company.
The service is provided as a model in the standard system, you can, however, create and implement customer-specific services at any time.
The Company Loans service in Employee Self-Service (ESS) is assigned to the Company Loan (International) process in HR Administrative Services. For
detailed information, see the documentation for the Sample Processes.
Prerequisites
be used.
AS).
Configuration
PROCESS (HR_PA_XX_COMPANY_LOANS)
Personal Profile

Caution
PUBLIC
Page 74 of 85
Technical Data
Web Dynpro Application HRESS_A_PERSINFO
Web Dynpro Application Package PAOC_ESS_PER_WDA
Application Configuration HRESS_AC_PERSINFO
HRESS_C_PERNR_SELECTION
HRESS_C_PERSINFO_CONFIG
Component Configurations HRESS_CC_PER_OVP
HRESS_CC_PER_CONFIG
Application Component Controller HRESS_C_PERSINFO_CONFIG
Software Component for Web Dynpro Application EA-HRGXX
Employees can use this service to display and maintain their personal information such as their address, bank information, personal data, family members and
dependents, and office, and communication data.
Features
The Personal Profile service consists of several business cards (biz cards). These biz cards enable employees from different countries to display and maintain
their personal information. The following biz cards are available:
International biz cards
Communication
Internal Data
In the Personal Profile service, you can customize the availability of subtypes for the Communication and Internal Data biz cards. You can do this by
maintaining the view V_T7XSSPERSUBTYP.
For more information, see Customizing for Employee Self-Service (Web Dynpro ABAP) under Service-Specific Settings Personal Information
Determine Active Subtypes and Make Settings .
While customizing the Communication and Internal Data biz cards for countries, you must create an entry for all requested subtypes in the view, including
for the ones already available on the screen.
For example, on the Communication biz card, consider that the Cell Number, Fax, and Telephone Number subtypes already exist. If you want an additional
subtype such as E-Mail, you must maintain country-specific entries for all four subtypes.
If you maintain only the E-mail subtype for any country, the system overwrites the existing international subtype entries for Cell Number, Fax and
Telephone Number and will display only the E-Mail subtype.
International biz cards with localizations
Personal Data
Addresses
Bank Information
Family Members/Dependents
Country-specific biz cards
Benefits Medical Information
Personal ID
Alternative Name
Prerequisites
You have made the settings in Customizing for Employee Self-Service (Web Dynpro ABAP) under Service-Specific Settings Personal Information .
Personal Data

Note
Caution
PUBLIC
Page 75 of 85
Technical Data
Package PAOC_ESS_PER_XX
Component Configurations for Overview Screen HRESS_CC_PER_OVR_PERSDATA_XX
HRESS_CC_OVR_PERSDATA_PHOTO_XX
Component Configurations for Detail Screen HRESS_CC_PER_DTL_PERSDATA_XX
HRESS_CC_PER_DTL_PERSDATA_VAL
Feeder Class for Overview Screen CL_HRESS_PER_OVERVIEW
Feeder Class for Detail Screen CL_HRESS_PER_DETAIL
This business card (biz card) of the Personal Profile service enables employees to display and maintain their data from the Personal Data infotype (0002).
In the overview screen, employees can display an overview of their current personal data. In the detail screen, they can change data relating to their name,
marital status, nationality, and birth.
The Employees can also upload a photo in JPEG or JPG format that is always displayed in the business card.
The following localizations are available for Personal Data:
AR Personal Data (Argentina)
AT Personal Data (Austria)
AU Personal Data (Australia)
BE Personal Data (Belgium)
BR Personal Data (Brazil)
CA Personal Data (Canada)
CH Personal Data (Switzerland)
CL Personal Data (Chile)
CN Personal Data (China)
DE Personal Data (Germany)
DK Personal Data (Denmark)
ES Personal Data (Spain)
FI Personal Data (Finland)
FR Personal Data (France)
GB Personal Data (Great Britain)
HK Personal Data (Hong Kong)
ID Personal Data (Indonesia)
IE Personal Data (Ireland)
IN Personal Data (India)
IT Personal Data (Italy)
JP Personal Data (Japan)
KR Personal Data (South Korea)
MX Personal Data (Mexico)
MY Personal Data (Malaysia)
NL Personal Data (Netherlands)
NO Personal Data (Norway)
NZ Personal Data (New Zealand)
PH Personal Data (Philippines)
PT Personal Data (Portugal)
RU Personal Data (Russia)
SE Personal Data (Sweden)
SG Personal Data (Singapore)
TH Personal Data (Thailand)
TW Personal Data (Taiwan)
US Personal Data (USA)
VE Personal Data (Venezuela)
ZA Personal Data (South Africa)
For employees that are employed in countries where no localization is available, the international overview screen and detail screen are displayed. The
international overview screen and detail screen are maintained as a part of component configuration HRESS_CC_PER_OVP. For more information, see
HRESS_CC_PER_OVP.
Prerequisites
Addresses

Note
PUBLIC
Page 76 of 85
Technical Data
Component Configuration for Overview Screen HRESS_CC_PER_OVR_ADDRESS_XX
Component Configurations for Detail Screen HRESS_CC_PER_DTL_ADDRESS_XX
HRESS_CC_PER_DTL_ADDRESS_VAL
This business card (biz card) of the Personal Profile service enables employees to display and maintain their data from the Addresses infotype (0006).
The Addresses biz card comprises the address types Permanent Residence, Emergency Address, and Mailing Address. In the overview screen, employees
can display an overview of their current address data. In the detail screen, they can enter or change the address of their primary residence, a contact address for
emergencies, and a correspondence address.
The following localizations are available for Addresses:
AR Addresses (Argentina)
AT Addresses (Austria)
AU Addresses (Australia)
BE Addresses (Belgium)
BR Addresses (Brazil)
CA Addresses (Canada)
CH Addresses (Switzerland)
CL Addresses (Chile)
CN Addresses (China)
DE Addresses (Germany)
DK Addresses (Denmark)
ES Addresses (Spain)
FI Addresses (Finland)
FR Addresses (France)
GB Addresses (Great Britain)
HK Addresses (Hong Kong)
ID Addresses (Indonesia)
IE Addresses (Ireland)
IN Addresses (India)
IT Addresses (Italy)
JP Addresses (Japan)
KR Addresses (South Korea)
MX Addresses (Mexico)
MY Addresses (Malaysia)
NL Addresses (Netherlands)
NO Addresses (Norway)
NZ Addresses (New Zealand)
PH Addresses (Philippines)
PT Addresses (Portugal)
RU Addresses (Russia)
SE Addresses (Sweden)
SG Addresses (Singapore)
TH Addresses (Thailand)
TW Addresses (Taiwan)
US Addresses (USA)
VE Addresses (Venezuela)
ZA Addresses (South Africa)
HRESS_CC_PER_OVP.
Prerequisites
Bank Information

Note
PUBLIC
Page 77 of 85
Technical Data
Component Configuration for Overview Screen HRESS_CC_PER_OVR_BANK_XX
Component Configurations for Detail Screen HRESS_CC_PER_DTL_BANK_XX
HRESS_CC_PER_DTL_BANK_VAL
This business card (biz card) of the Personal Profile service enables employees to display and maintain their data from the Bank Details infotype (0009).
Employees bank details are used for bank transfers from payroll and to reimburse travel expenses. The Bank Information biz card comprises the bank
information types Main Bank, Travel Expenses, and Other Bank.
In the overview screen, employees can display an overview of their current bank data. In the detail screen, they can enter or change bank information for the bank
transfer from payroll, for travel expenses from travel expense management, and for special purposes such as transfer of a part of their salary to an account other
than their main bank account. This amount can be specified either as an absolute amount or as a percentage of the salary.
The following localizations are available for Bank Information:
AR Bank Information (Argentina)
AT Bank Information (Austria)
AU Bank Information (Australia)
BE Bank Information (Belgium)
BR Bank Information (Brazil)
CA Bank Information (Canada)
CH Bank Information (Switzerland)
CL Bank Information (Chile)
CN Bank Information (China)
DE Bank Information (Germany)
DK Bank Information (Denmark)
ES Bank Information (Spain)
FI Bank Information (Finland)
FR Bank Information (France)
GB Bank Information (Great Britain)
HK Bank Information (Hong Kong)
ID Bank Information (Indonesia)
IE Bank Information (Ireland)
IN Bank Information (India)
IT Bank Information (Italy)
JP Bank Information (Japan)
KR Bank Information (South Korea)
MX Bank Information (Mexico)
MY Bank Information (Malaysia)
NL Bank Information (Netherlands)
NO Bank Information (Norway)
NZ Bank Information (New Zealand)
PH Bank Information (Philippines)
PT Bank Information (Portugal)
RU Bank Information (Russia)
SE Bank Information (Sweden)
SG Bank Information (Singapore)
TH Bank Information (Thailand)
TW Bank Information (Taiwan)
US Bank Information (USA)
VE Bank Information (Venezuela)
ZA Bank Information (South Africa)
HRESS_CC_PER_OVP.
Prerequisites
Family Members/Dependents
Note
PUBLIC
Page 78 of 85

Technical Data
Component Configuration for Overview Screen HRESS_CC_PER_OVR_FAMILY_XX
Component Configurations for Detail Screen HRESS_CC_PER_DTL_FAMILY_XX
HRESS_CC_PER_DTL_FAMILY_VAL
This business card (biz card) of the Personal Profile service enables employees to display and maintain their data from the Family Member/Dependents infotype
(0021).
In the overview screen, employees can display an overview of their current family data such as their spouse, domestic partner, child, or child of their domestic
partner. In the detail screen, they can enter or change the name or birth date of their spouse, domestic partner, child, or child of their domestic partner.
The following localizations are available for Family Members/Dependents:
AR Family Members/Dependents (Argentina)
AT Family Members/Dependents (Austria)
AU Family Members/Dependents (Australia)
BE Family Members/Dependents (Belgium)
BR Family Members/Dependents (Brazil)
CA Family Members/Dependents (Canada)
CH Family Members/Dependents (Switzerland)
CL Family Members/Dependents (Chile)
CN Family Members/Dependents (China)
DE Family Members/Dependents (Germany)
DK Family Members/Dependents (Denmark)
ES Family Members/Dependents (Spain)
FI Family Members/Dependents (Finland)
FR Family Members/Dependents (France)
GB Family Members/Dependents (Great Britain)
HK Family Members/Dependents (Hong Kong)
ID Family Members/Dependents (Indonesia)
IE Family Members/Dependents (Ireland)
IN Family Members/Dependents (India)
IT Family Members/Dependents (Italy)
JP Family Members/Dependents (Japan)
KR Family Members/Dependents (South Korea)
MX Family Members/Dependents (Mexico)
MY Family Members/Dependents (Malaysia)
NL Family Members/Dependents (Netherlands)
NO Family Members/Dependents (Norway)
NZ Family Members/Dependents (New Zealand)
PH Family Members/Dependents (Philippines)
PT Family Members/Dependents (Portugal)
RU Family Members/Dependents (Russia)
SE Family Members/Dependents (Sweden)
SG Family Members/Dependents (Singapore)
TH Family Members/Dependents (Thailand)
TW Family Members/Dependents (Taiwan)
US Family Members/Dependents (USA)
VE Family Members/Dependents (Venezuela)
ZA Family Members/Dependents (South Africa)
HRESS_CC_PER_OVP.
Prerequisites
Communication

Note
PUBLIC
Page 79 of 85
Technical Data
Component Configuration for Overview Screen HRESS_CC_PER_OVR_COMM_DATA_XX
Component Configurations for Detail Screen HRESS_CC_PER_DTL_COMM_DATA_XX
HRESS_CC_PER_DTL_COMM_DATA_VAL
This business card (biz card) of the Personal Profile service enables employees to display and maintain their contact data from the Communication infotype
(0105).
The Communication biz card comprises the following communication types:
First Telephone Number at Work
Fax
Cell Phone
E-Mail
Pager
In the overview screen, employees can display an overview of their current contact data. In the detail screen, they can enter or change their communication data.
Prerequisites
Internal Data

Technical Data
Component Configuration for Overview Screen HRESS_CC_PER_OVR_OFFICE_DATA_XX
Component Configurations for Detail Screen HRESS_CC_PER_DTL_OFFICE_DATA_XX
HRESS_CC_PER_DTL_OFFICE_DATA_VAL
This business card (biz card) of the Personal Profile service enables employees to display and maintain their data from the Internal Control infotype (0032).
The Internal Data biz card comprises information relating to the employee's work center such as the Building Number and Room Number. It also contains the
Licence Plate Number of the employee's company car. In the overview screen, employees can display an overview of their current internal data. In the detail
screen, they can enter or change their internal data.
Prerequisites
Personnel File

Technical Data
Web Dynpro Application ASR_PERSONNEL_FILE
Web Dynpro Application Package PAOC_ASR_PERSONNEL_FILE
Application Configuration ASR_PERSONNEL_FILE
Web Dynpro Components HRASR0_PERSONNEL_FILE
Component Configurations Not relevant
Support PA-AS
PUBLIC
Page 80 of 85
An employee can use this service to display his or her personnel file.
This service is provided as a model in the standard system, you can, however, create and implement customer-specific services at any time.
For detailed information, see the documentation for the Sample Processes.
Prerequisites
be used.
AS).
For detailed information, see Customizing for HR Administrative Services (PA-AS).
Configuration
The following parameters (and their values) are passed to the WD application ASR_PERSONNEL_FILE:
PERNR_MEM_ID (ESS01)
EIC Authentication

Technical Data
Web Dynpro Application HRESS_A_EICAUTH
Web Dynpro Application Package PAOC_EIC_AUTHENTICATION
Application Configuration HRESS_AC_EICAUTH
Web Dynpro Component FPM_OVP_COMPONENT
Component Configurations HRESS_CC_EICAUTH_OVP, HRESS_CC_PER_DTL_EICAUTH_XX
Software Component for Web Dynpro Application EA-HRGXX
Support PA-EIC
Availability SAP enhancement package 5 for SAP ECC 6.0
You can use the authentication service when you implement an Employee Interaction Center (EIC) and you want to enable employees to contact the EIC by
telephone. In this case, EIC agents must be able to uniquely identify the caller. The authentication questions defined in this application make this possible.
Features
This service enables all employees at your company to define authentication questions and the corresponding answers. All employees can use this application to
select a maximum of five different authentication questions and enter the corresponding answers. The relevant data (in particular the questions and answers) are
stored in the Authentication infotype (0816). In the standard ESS role delivery, the EIC Authentication service is assigned to the Personal Information area.
Caution
PUBLIC
Page 81 of 85
Appraisal Documents
Services for the Predefined Performance Management Process
Appraisal Documents

Technical Data
Web Dynpro Application HAP_A_PMP_EMPLOYEE
Package of Web Dynpro Application PAOC_HAP_PA_PMP_UI
Application Configuration HAP_AC_PMP_EMPLOYEE
Web Dynpro Component HAP_PMP_EMPLOYEE
Component Configuration HAP_OIF_PMP_EMPLOYEE, HAP_IDR_PMP_EMPLOYEE
Application Component Controller HAP_PMP_EMPLOYEE
Data Source
Software Component of Web Dynpro Application EA-HRGXX
Support PA-PD-PM
Prerequisite Business Function HCM_NWBC_ROLES
With this service, you can provide appraisal documents to employees in the Career & Job area in the predefined Performance Management process. Employees
can perform the tasks necessary for their appraisal documents. The following are examples of what is available to you depending on your selected settings:
Graphical and temporal display of the individual phases of the appraisal process (planning, review, appraisal)
Entries: Examples of entries: Administrative data, event overview, status
Individual goals
Competency and development goals
Team goals
Corporate goals
Core values
Obsolete goals
Document overview
This service is assigned to the role visibly. The Appraisal Document service is called from this service.
If you use the flexible appraisal process, an alternative service is available to you. It is assigned to the role invisibly in the standard system. For more
information, see Appraisal Documents.
Prerequisites
You have made all the necessary settings in Customizing for the Objective Setting and Appraisals (Performance Management) application component.
Configuration
Appraisal Document

Note
PUBLIC
Page 82 of 85
Technical Data
Web Dynpro Application HAP_A_PMP_MAIN
Package of Web Dynpro Application PAOC_HAP_PA_PMP_UI
Application Configuration HAP_AC_PMP_MAIN
Web Dynpro Component HAP_PMP_MAIN
Component Configuration HAP_OIF_PMP_MAIN, HAP_IDR_PMP_MAIN
Application Component Controller HAP_PMP_MAIN
Data Source
Software Component of Web Dynpro Application EA-HRGXX
Support PA-PD-PM
Employees can use this service to display or change the appraisal document used in the predefined Performance Management process.
Integration
In the standard system, this service is accessed from the Performance Management service.
The service is called using the appraisal_document_pmp method of the employee business object. For more information about the business object, see
Employee.
Prerequisites
Configuration
Services for the Flexible Appraisal Process
Appraisal Documents

Technical Data
Web Dynpro Application HAP_START_PAGE_POWL_UI_ESS
Package of Web Dynpro Application PAOC_HAP_DOCUMENT_WD_UI
Application Configuration HAP_START_PG_POW_ESS_AC
Web Dynpro Components HAP_START_PAGE_POWL_UI
Component Configuration HAP_OIF_POWL_CONF_ESS, HAP_IDR_POWL_CONF
Application Component Controller AHAP_START_PAGE_POWL_UI
Data Source
Software Component of Web Dynpro Application SAP_ABA
Support PA-PD-PM
Required Business Function HCM_NWBC_ROLES
You can use this service to provide employees with a single point-of-entry in Web Dynpro technology for ABAP, thus making the required appraisal documents
available in their worklists in the flexible appraisal process. The appraisal documents also include those documents for which the employees have the role of part
appraisers. Employees can process the required documents from the worklist.
During the execution of the part-appraisal process, managers acting as part appraisers access their part-appraisal documents in Employee Self-Services
(WDA).
Note
PUBLIC
Page 83 of 85
A manager acting simultaneously as an appraser can access the main document in Manager Self-Services (WDA). (See also the Performance Management
(Flexible) service.)
For more information about the main document and part-appraisal document, see Element Access Tab.
Integration
The Appraisal Document service is available to call an appraisal document from the worklist.
This service is assigned to the role invisibly. However, the appraisal document service (HAP_A_PMP_EMPLOYEE) is assigned to the role visibly. If you want to
use the service for the flexible appraisal process, you must assign it to the employee role visibly. The Appraisal Document service is called from this service.
Prerequisites
Configuration
Appraisal Document

Technical Data
Web Dynpro Application HAP_MAIN_DOCUMENT
Package of Web Dynpro Application PAOC_HAP_DOCUMENT_WD_UI
Application Configuration HAP_AC_MAIN_DOC
Web Dynpro Component HAP_MAIN_DOCUMENT
Component Configuration FPM_OIF_COMPONENT, FPM_IDR_COMPONENT
Application Component Controller HAP_MAIN_DOCUMENT
Data Source -
Software Component of Web Dynpro Application SAP_ABA
Support PA-PD-PM
Employees can use this service to display or change the appraisal document used in the flexible appraisal process.
Integration
In the standard system, this service is accessed from the Performance Management service.
The service is called using the appraisal_document_wd_ui method of the employee business object. For more information about the business object, see
Employee.
Prerequisites
Configuration
Talent Profile

PUBLIC
Page 84 of 85
Technical Data
Web Dynpro Application HRTMC_EMPLOYEE_PROFILE
Package of Web Dynpro Application HCM_TMC
Application Configuration HRTMC_EMPLOYEE_PROFILE_ESS
Web Dynpro Components FPM_OIF_COMPONENT, HRTMC_TP_HEADER, HRTMC_TP_SHARED_DATA,
HRTMC_TP_WORKEXP_INTERNAL, HRTMC_TP_WORKEXP_EXTERNAL,
HRTMC_TP_EDUCATION, HRTMC_TP_ACCOMPLISHMENTS,
HRTMC_TP_CAREER_GOAL, HRTMC_TP_MOBILITY
Component Configuration HRTMC_EP_OIF
Application Component Controller HRTMC_TP_CONFIG_CONTROL
Software Component of Web Dynpro Application SAP_BS_FND
Support PA-TM
Required Business Function HCM_TMC_CI_1
The employee can use this service to enter information relevant to Talent Management, which is then saved as a talent profile.
For more information, see Talent Profile for Employees.
Integration
In the standard SAP system, the following persons can edit an employee's talent profile:
The employee can enter data in his or her talent profile.
The employee's manager can edit the employee's talent profile instead of or in addition to the employee. The Employee's Self Description service is available
in the role Manager Self-Service for SAP NetWeaver Business Client for HTML for this purpose.
For more information, see Employee's Self Description.
The talent management specialist responsible for the employee can edit the talent profile instead of or in addition to the employee or manager. The Talent's Self
Description service in the role Talent Management Specialist: NWBC is available for this purpose.
For more information, see Talent's Self Description.
Prerequisites
In Customizing for Talent Management and Talent Development, you have made the settings under Talent Profile.
PUBLIC
Page 85 of 85

Business Package For Ess (Wda) 1.50

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Business Package For Ess (Wda) 1.50

Transféré par

Droits d'auteur :

Formats disponibles

PRINT FROM SAP HELP PORTAL

Vous aimerez peut-être aussi