-
PRINT FROM SAP HELP PORTALDocument:Business Package for Employee
Self-Service (WDA)
1.50URL:http://help.sap.com/erp2005_ehp_05/helpdata/en/25/340b0507434193adbfe3f8fc8896c7/frameset.htmDate
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 expresspermission of SAP AG.
The information contained herein may be changed without prior
notice. Some software products marketed by SAP AG and its
distributors contain proprietarysoftware components of other
software vendors. National product specifications may vary. These
materials are provided by SAP AG and its affiliated companies ("SAP
Group") forinformational 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 onlywarranties 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 hereinshould be construed as constituting
an additional warranty. SAP and other SAP products and services
mentioned herein as well as their respective logos are trademarks
orregistered trademarks of SAP AG in Germany and other countries.
Please see
www.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark informationand notices.
NoteThis 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.
Youcan manually download the missing subtopics.
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 1 of 85
-
Business Package for Employee Self-Service (WDA) 1.50 The
Business Package for Employee Self-Service (WDA) 1.50 allows
employees in your company to create, display, and change all
employee-relevant datathemselves via the SAP NetWeaver
Portal.Technical Data
Availability SAP ECC 6.0, SAP enhancement package 5 for SAP ERP
6.0SAP NetWeaver 7.0
Data Source SAP ERP Central Component (SAP ECC)
Browser Recommendation For information about system
prerequisites for these components, see theProduct Availability
Matrix on SAP Service Marketplace atservice.sap.com/pam.
Languages Available All languages available for SAP ERP 6.0.Note
that the individual country-specific services included in this
businesspackage do not exist in all languages but rather in the
language native to theparticular country.
Support ESS Web Dynpro (CA-ESS-WD)ESS based on Web Dynpro ABAP
(PA-ESS-XX-WDA)
PrerequisitesYou 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 enhancementpackages 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 arelisted 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 ABAPIf 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 onlywork if you have activated the required business
functions for these services. The following business functions are
a prerequisite if you want to have the fullfunctional 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)
ConfigurationFor information about configuration, see
Configuration: Business Package for Employee Self-Service
(WDA).
More InformationRelease 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 2013 SAP AG or an SAP affiliate company. All rights
reserved.
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 forEmployee Self-Service (WDA) 1.50 is available
for customers. This Business Package is based completely on the Web
Dynpro for ABAP technology.
More InformationSee 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 ERPEnhancement 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.
PrerequisitesYou have an overview of the required software
components and the implementation strategy. For this, use the
Master Guides and Installation Guides on SAPService 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 PortalApplication Server
ABAPAdobe Document Services (ADS) (for HCM Processes and Forms)
Business packages:Business Package for Employee Self-Service
(WDA) 1.50Business Package for Common PartsFor 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 atservice.sap.com/pam.For information about the
security settings for these components, see the appropriate
Security Guide on SAP Service Marketplace
atservice.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 .
Activities1. 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 PortalConfiguration 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 PortalBusiness
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 documentationof the following sections carefully:
Leave RequestServices 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 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 3 of 85
-
Configuration of Reporting ServicesMake the Customizing settings
that are required for the services that you intend to use in your
customer-specific role. For more information, see thedocumentation
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 LandscapeProcedure1. 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. Proceedas 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:
ConnectorInternet Transaction Server (ITS)The relevant ITS path
is: /sap/bc/gui/sap/its/webguiWeb 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_SRMAlias for E-Recruiting:
SAP_EREC_TalentManagement
More InformationSee 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
Packagefor Employee Self-Service (WDA).
Objects from the Business Package for Common Parts
Shared iViews
Title of the iView Technical Name NotesiViews that are
referenced from the launchpad(ABAP)
In the same way as the Launchpad (ABAP) iViewfrom the Business
Package for Common Parts, theOverview iView in the Business Package
forEmployee Self-Service (WDA)calls further iViewsfrom the Business
Package for Common Partswhen the user chooses a link. For more
information,see Launchpad (ABAP).
Shared Business Objects
Title of Business Object Technical Name UseEmployee
SAP_ERP_HumanResources.employee iView Appraisal Document
iView Appraisal DocumentDisplay Form
More Information
Note
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 4 of 85
-
See the documentation for the relevant business package or
packages on the SAP Developer Network (SDN) Web site
atwww.sdn.sap.com/irj/sdn/developerareas/contentportfolio.
Roles in Employee Self-Service (WDA) 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 AuthorizationsMost 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 roleto 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 menustructure
with the individual services since these services are not
integrated directly into the composite role. The delivered
composite role contains the followingsingle roles:
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 5 of 85
-
Role Name UseSAP_EMPLOYEE_XX_ESS_WDA_1 ESS International Single
Role Authorizations + menu for international ESS
servicesSAP_EMPLOYEE_AU_ESS_WDA_1 ESS Single Role for Australia
Authorizations + menu for country-specific ESS
services for AustraliaSAP_EMPLOYEE_CA_ESS_WDA_1 ESS Single Role
for Canada Authorizations + menu for country-specific ESS
services for CanadaSAP_EMPLOYEE_CH_ESS_WDA_1 ESS Single Role for
Switzerland Authorizations + menu for country-specific ESS
services for SwitzerlandSAP_EMPLOYEE_CN_ESS_WDA_1 ESS Single
Role for China Authorizations + menu for country-specific ESS
services for ChinaSAP_EMPLOYEE_DE_ESS_WDA_1 ESS Single Role for
Germany Authorizations + menu for country-specific ESS
services for GermanySAP_EMPLOYEE_HK_ESS_WDA_1 ESS Single Role
for Hong Kong Authorizations + menu for country-specific ESS
services for Hong KongSAP_EMPLOYEE_IN_ESS_WDA_1 ESS Single Role
for India Authorizations + menu for country-specific ESS
services for IndiaSAP_EMPLOYEE_JP_ESS_WDA_1 ESS Single Role for
Japan Authorizations + menu for country-specific ESS
services for JapanSAP_EMPLOYEE_MY_ESS_WDA_1 ESS Single Role for
Malaysia Authorizations + menu for country-specific ESS
services for MalaysiaSAP_EMPLOYEE_PT_ESS_WDA_1 ESS Single Role
for Portugal Authorizations + menu for country-specific ESS
services for PortugalSAP_EMPLOYEE_SG_ESS_WDA_1 ESS Single Role
for Singapore Authorizations + menu for country-specific ESS
services for SingaporeSAP_EMPLOYEE_TH_ESS_WDA_1 ESS Single Role
for Thailand Authorizations + menu for country-specific ESS
services for ThailandSAP_EMPLOYEE_US_ESS_WDA_1 ESS Single Role
for the United States Authorizations + menu for country-specific
ESS
services for the USASAP_FI_TV_WEB_ESS_TRAVELER ESS Single Role
for the Traveler Authorizations + menu for ESS services for the
traveler roleSAP_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 Formsapplication
SAP_PM_EMPLOYEE_HCM_CI_1 ESS Single Role for HCM PM Services
Authorizations + menu for ESS services from thePerformance
Management application
SAP_TMC_EMPLOYEE Employee in Talent Management Authorizations +
menu for ESS services from theTalent Management and Talent
Developmentapplication
SAP_EMPLOYEE_OTH_ESS_WDA_1 ESS Single Role Containing Non-EA-HR
Services Menu structure for all services belonging to othersoftware
components (SRM and SAP E-Recruiting).The authorizations for these
services are located inthe respective target system. This means
thatemployees that are to have access to thesesystems must also be
assigned to the single rolefor authorizations necessary in the
relevant system.Also see: Single Roles for Employee
Self-Service(WDA)
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 sincethese services are not integrated directly into the
composite role.
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 6 of 85
-
Single Roles for Employee Self-Service (WDA)
Role Name UseSAP_EMPLOYEE_XX_ESS_WDA_1 ESS International Single
Role Authorizations + menu for international ESS
servicesSAP_EMPLOYEE_AU_ESS_WDA_1 ESS Single Role for Australia
Authorizations + menu for country-specific ESS
services for AustraliaSAP_EMPLOYEE_CA_ESS_WDA_1 ESS Single Role
for Canada Authorizations + menu for country-specific ESS
services for CanadaSAP_EMPLOYEE_CH_ESS_WDA_1 ESS Single Role for
Switzerland Authorizations + menu for country-specific ESS
services for SwitzerlandSAP_EMPLOYEE_CN_ESS_WDA_1 ESS Single
Role for China Authorizations + menu for country-specific ESS
services for ChinaSAP_EMPLOYEE_DE_ESS_WDA_1 ESS Single Role for
Germany Authorizations + menu for country-specific ESS
services for GermanySAP_EMPLOYEE_HK_ESS_WDA_1 ESS Single Role
for Hong Kong Authorizations + menu for country-specific ESS
services for Hong KongSAP_EMPLOYEE_IN_ESS_WDA_1 ESS Single Role
for India Authorizations + menu for country-specific ESS
services for IndiaSAP_EMPLOYEE_JP_ESS_WDA_1 ESS Single Role for
Japan Authorizations + menu for country-specific ESS
services for JapanSAP_EMPLOYEE_MY_ESS_WDA_1 ESS Single Role for
Malaysia Authorizations + menu for country-specific ESS
services for MalaysiaSAP_EMPLOYEE_PT_ESS_WDA_1 ESS Single Role
for Portugal Authorizations + menu for country-specific ESS
services for PortugalSAP_EMPLOYEE_SG_ESS_WDA_1 ESS Single Role
for Singapore Authorizations + menu for country-specific ESS
services for SingaporeSAP_EMPLOYEE_TH_ESS_WDA_1 ESS Single Role
for Thailand Authorizations + menu for country-specific ESS
services for ThailandSAP_EMPLOYEE_US_ESS_WDA_1 ESS Single Role
for the United States Authorizations + menu for country-specific
ESS
services for the USASAP_FI_TV_WEB_ESS_TRAVELER ESS Single Role
for the Traveler Authorizations + menu for ESS services for the
traveler roleSAP_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 Formsapplication
SAP_PM_EMPLOYEE_HCM_CI_1 ESS Single Role for HCM PM Services
Authorizations + menu for ESS services from thePerformance
Management application
SAP_TMC_EMPLOYEE Employee in Talent Management Authorizations +
menu for ESS services from theTalent Management and Talent
Developmentapplication
SAP_EMPLOYEE_OTH_ESS_WDA_1 ESS Single Role Containing Non-EA-HR
Services Menu structure for all services belonging to othersoftware
components (SRM and E-Recruiting). Theauthorizations for these
services are located in therespective target system (see also the
last twotable 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 leaverequests 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 employeesthat use SAP
E-Recruiting services in ESS (WDA).
/SAPSRM/EMPLOYEE_ESS SAP SRM Employee for ESS Authorizations in
SAP SRM for employees that useservices 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 thecomposite 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 meansthat
employees that are to have access to these systems and services
must also be assigned to the single role for authorizations
necessary in the relevantsystem.
Note
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 7 of 85
-
Assigning Roles for ESS (WDA) in SAP PortalPrerequisitesThe
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.
Procedure1. 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 InformationRoles in Employee Self-Service (WDA)
Configuration of the Role Menu for ESS (WDA) in SAP Portal In
this section you find information about how the role menu in the
FPM Launchpad Configuration Repository (transaction LPD_CUST) is
configured for the SAPNetWeaver Portal role Employee Self-Service
(WDA).
FeaturesFor the Launchpad menu, the following technical objects
are relevant:
Application HRESS_A_MENU with Overview Pattern Configuration
(OVP) HRESS_AC_MENUComponent 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).
ActivitiesIn Customizing for Employee Self-Service (Web Dynpro
ABAP), make the required settings under General Settings ESS Menu
for Services Menu for SAPPortal Role .This Customizing activity
calls up transaction LPD_CUST, where you can find the delivered
Launchpad configurations Role: ESS and Instance: MENU andInstance:
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 changeaccording 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 2013 SAP AG or an SAP affiliate company. All rights
reserved.
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 usedto collect the applications that
should be available in the SAP NetWeaver Portal, but not directly
visible in the role menu. These applications are displayedin 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 thefolder 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 InformationLaunchpad
Create a Launchpad with ApplicationsInclude a Launchpad in the
User InterfaceChange Launchpad
Employee Self-Services Menu (Application HRESS_A_MENU) Technical
Data
Web Dynpro Application HRESS_A_MENUWeb Dynpro Application
Package PAOC_ESS_CENTRAL_SERVICESApplication Configuration
HRESS_AC_MENUWeb Dynpro Components FPM_OVP_COMPONENTComponent
Configurations HRESS_CC_MENU_OVP,
HRESS_CC_MENU_AREA_GROUP
Application Component Controller FPM_LAUNCHPAD_UIBBSoftware
Component for Web Dynpro Application EA-HRRXXSupport
PA-ESS-XX-WDAAvailability SAP enhancement package 5 for SAP ERP
6.0Required 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 therole 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
todynamically 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).
IntegrationThis application makes use of the FPM Launchpad
Framework for Web Dynpro ABAP to display the menu structure. The
Launchpad allows you to organizeapplications, 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 OBNnavigation 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 theOBN 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
resolvesthe 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.
FeaturesIn 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 it2. Directory - View with all Folders
/Subfolders3. 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, thissetting
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
thestandard shipment this is blank and is configured to point to
Role: ESS and Instance: RELATED_LINKS
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 9 of 85
-
Launchpad also offers the following basic functions:Add short
descriptions for the individual services that will appear on the
user interfaceEdit the link texts of the hyperlinks that the
employees use to start the servicesEmphasize certain services (for
example, because there is an urgent deadline)Deactivate
services
PrerequisitesThe 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 forthe section Related Links to work in
the Business Package for Employee Self-Service (WDA).
ConfigurationYou can access the Launchpad transaction in the SAP
Customizing Implementation Guide under Personnel Management
Employee Self-Service (WebDynpro 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 Menushipment 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 ConfigurationA 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 ahierarchical/tree
structure, see also the following example:
Area Group FolderArea Folder 1
Subarea Folder 1Service 1Service 2Service 3Subarea Folder
2Service 4Service 5
Area Folder 2Subarea Folder 3Service 6Subarea Folder 4Service
7Service 8Subarea Folder 5Service 9
Area Folder 3Subarea Folder 6Service 10Service 11Service
12Service 13
Area Group FoldersArea group folders contain descriptions of
areas, hyperlinks to access the areas, and hyperlinks to start
services directly.Area FoldersArea folders contain services that
are related to each other. Employees access an area folder from an
area group folder.Subarea FoldersAreas 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
thescreen.ServicesInside 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 willappear 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.
ActivitiesWe recommend you make a graphical design of the areas
and services you want to implement. This way, the hierarchical
relations between these elements willbecome apparent.
If you have copied the Menu applications configurations to your
own namespace, ensure that the Application Component Controller's
(AppCC) component andconfiguration name are the same as the copied
UIBBs Component Configuration.
Example
Note
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 10 of 85
-
More InformationLaunchpad
Create a Launchpad with ApplicationsInclude a Launchpad in the
User InterfaceChange 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
RepositoriesThe 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 calledby 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
eachapplication 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
implementationHRESS_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 BAdIimplementation 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 canbe 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 theCOUNTRYGROUPING parameter in
the application and if the user accessing the menu belongs to a
different country (has a different MOLGA), it sets the
applicationto invisible. With this standard implementation,
country-specific services are only visible to employees belonging
to the respective countries.
More InformationAlso 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 SAPCustomizing 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 2013 SAP AG or an SAP affiliate company. All rights
reserved.
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
Window2. Launchpad-defined call of a Web Dynpro ABAP application3.
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 forEmployee Self-Service
(WDA).
PrerequisitesIn 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 BusinessObject
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 InformationObject-Based Navigation for ESS (WDA) in SAP
NWBCObject-Based Navigation for ESS (WDA) in the SAP Portal
Object-Based Navigation for ESS (WDA) in the SAP Portal
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.
IntegrationThe Business Package for Employee Self-Services (WDA)
uses business objects from the Business Package for Common Parts
for navigation, also seeBusiness Objects Used for OBN in the SAP
Portal.
PrerequisitesThe 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 2013 SAP AG or an SAP affiliate company. All rights
reserved.
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 (calledapplication) 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
aLaunchpad 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 SourceRole) 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
thefollowing 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 InformationBusiness Objects Used for OBN in the SAP
Portal
Business Objects Used for OBN in the SAP Portal 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 SAPNetWeaver Portal.
FeaturesThe Business Package for Employee Self-Services (WDA)
uses business objects from the Business Package for Common Parts
for navigation, see also thefollowing table.OBN Objects for ESS
(WDA) Portal Role
Name Technical Name Object TypeEmployee
SAP_ERP_HumanResources.employee Business ObjectAppraisal Document
(PMP) appraisal_document_pmp OperationAppraisal Document (WD UI)
appraisal_document_wd_ui OperationAppraisal Document Overview (PMP)
appraisal_doc_overview_pmp Operationassess assess Operationcompare
compare OperationDisplay display OperationDisplay Attachment
display_attachment OperationDisplay Compensation Approval
compensation_approval OperationDisplay Compensation Comparison
compensation_comparison OperationDisplay Compensation Planning
compensation_planning OperationDisplay Compensation Profile
compensation_profile OperationDisplay Form display_form
OperationDisplay Form for Manager display_form_manager
OperationDisplay Long Profile display_long_profile OperationEdit
Development Plan edit_dev_plan OperationEdit 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 processstarts 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).
PrerequisitesYou have integrated the Web applications with the
relevant portal pages. For more information, see the Business
Package for Manager Self-Service (MSS).
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 13 of 85
-
You have set up the Web application in Customizing. For more
information, see Customizing under Personnel Management Employee
Self-Service (WebDynpro 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).
FeaturesThe Leave Request function comprises the following
areas:
Creation of leave request by employeeForwarding of request to
manager for approvalControlling the deletion and cancellation
processesStatus tracking and monitoringPosting of absences to the
backend systemRunning 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 contextualinformation:
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 havetime 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 ofabsences.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 alsoprocess 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 controlaspects 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 periodsfor 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 hasalready 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 leaverequest. 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 thecorresponding 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 processto suit your needs, or import and
change data.
Processing Leave Requests You use this process to process leave
requests.
PrerequisitesYou 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 TimeLeave
Request Processing Processes Define Report Variants and Background
Processing .
ProcessBelow is an example of the process when an employee
requests leave. Processes involving changing and canceling leave or
deleting a request that has notbeen 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
responsibleand lists the name in the Web application. If required,
the employee can overwrite the name of the approver.
Note
Note
Note
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
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 forthe 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 allthe 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 beapproved 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 Requestservice. 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) orAttendances (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 thestatus 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 toPosted.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.
FeaturesIn 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 anabsence 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 isthe
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 authorizationcheck 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
therebyprovide 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 accessquickly the tools you need during
the implementation and test phase. Note that the transaction is
primarily intended for SAP-internal use and is not officiallypart
of the standard system offering.
FeaturesYou 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 2013 SAP AG or an SAP affiliate company. All rights
reserved.
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 SettingsRPTREQWEBMO (Determine
Rule Group). You can use this report to determine the most
important organizational assignments for individual employees
ororganizational 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 DatabaseRPTARQDBVIEW
(Display Leave Requests (Database of Requests) You can use this
report to view all information relating to the leave requests that
havebeen 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 issupposed to.
PTREQ_STATUS_CHK (Check Methods for Status
Transitions)PTREQ_STATUS_TRA (Status Transitions)V_PTREQ_TYPE
(Document Type)
Test ProgramsThe test programs RPTARQUIATEST (Test Report for
the UIA Interface for Leave Requests) and RPTARQAPTEST (Test Report
for the UIA Area Pages forLeave 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 UseDepending on the business
processes you use to manage your employee's time data, you can
display information from time accounts of various different
datasources.
FeaturesThe 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 accountingdate. 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 systemreads 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 2013 SAP AG or an SAP affiliate company. All rights
reserved.
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
theWorking 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 theapplication 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 timesPeter
Miller is a field service employee who wants to record his working
times. He accesses the company intranet and selects the Web
application RecordWorking 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 withentering this information, he
can use either the default values proposed or the search
function.Saving working timesHe 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 byhis personnel
officer.Saving and releasing working times for approvalAt 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 maybe missing. He then releases the working
times.Approval rejectedPeter has entered an incorrect cost center.
Therefore, Peter's personnel officer does not approve his working
times. The next time Peter accesses the Webapplication 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 forapproval.Approval grantedPeters 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 fromdifferent 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 profileused, you cannot use default values
for the sender cost center and activity type.
IntegrationYou can use default values in the following user
interfaces of the Cross-Application Time Sheet:
CATS classicCATS 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 mustcreate the Time Sheet Defaults infotype
(0315).
Note
Caution
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 17 of 85
-
FeaturesIn 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 youcreate 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 attendanceor 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 accountassignment 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, thesystem uses the following order:1. Time Sheet
Defaults infotype (0315)2. Organizational Assignment (0001)3. Work
Center or Activity4. SAP enhancement CATS0002 (Supplement Recorded
Data)
ActivitiesIf 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 Typeindicators.To take the default value for
the sender cost center from the Organizational Assignment infotype
(0001), select Master cost center instead of Cost center. Ifyou
select both indicators, the system uses the cost center stored in
the Time Sheet Defaults infotype (0315) for the default values.
More InformationIn 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 acombination of
task type and task component. You can make this setting in the
Implementation Guide (IMG), under Cross-Application Components
TimeSheet 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:
ChangeDerived Values .
Worklist DefinitionScreen 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.
UseYou 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 aremaintaining the time sheet for one
employee using single entry.
StructureThe worklist can contain the following information:
Data that the employee has already entered in the time sheetData
from SAP Logistics:Resource planning (capacity splits)Confirmation
poolsActivities assigned to the employee based on his or her work
center assignmentData created using the SAP enhancement CATS0001
(Set Up Worklist) or using the Business Add-In (BAdI)
CATS_WORKLIST_ADDIN, which is displayedin 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
whenyou maintain your profiles.
Note
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
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 differentdata
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 youdo 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.
IntegrationThis function is available in the following user
interfaces of the Cross-Application Time Sheet:
CATS classicCATS regularA 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 standardtemplate. You can create a separate
standard template for each data entry profile. The system uses the
standard templates for users who have not saved apersonal template
or who have deleted their saved template.For more information, see
the report documentation.
FeaturesYou 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 personaltemplates in relation to a
personnel number, which means that users who record working times
for several personnel numbers can use their personaltemplates 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 andMerging of Account
Assignment Rows.
ActivitiesChoose 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 andchoose
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.
FeaturesYou 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 timesMark a favorite without
times as their default favorite, which works like a personal
templateImport 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 systemfirst imports those with
times, performs a consistency check, and then imports those without
times. When employees import a favorite, the time perioddisplayed
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
afavorite, and can have one default favorite at any point in
time.
Note
Note
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
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, thesystem merges account assignment rows containing
identical working time attributes, providing that the working times
entered permit it.
FeaturesData is displayed in a vertical list view or a
horizontal list view, depending on your Customizing settingsThe
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 theseaccount
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 withthose 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 timesheetCopy from Previous Period-copy clock times from a
previous period to the current timesheetCopy from Target Hours-copy
their planned hours to the timesheetInsert 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,
andemployees 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.
FeaturesIf an employees work and break schedules are fixed, they
can use this function to copy information directly to their
timesheet, by choosing the Work Schedulebutton. 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
awork schedule if the timesheet does not include clock times.The
following information is copied from the work schedule:
DateDaily SchedulePlanned Working HoursStart TimeEnd TimeBreak
DurationBreak Start TimeBreak End TimeUnpaid/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 from12: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 timesheetdoes 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 2013 SAP AG or an SAP affiliate company. All rights
reserved.
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) aredays 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
thirdrows. 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
thirdrows. 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 differentcell 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. Whenemployees 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 thetime
sheet.To create a data entry profile, you must make the following
settings in Customizing:
Set Up Data Entry ProfilesThe Customizing activities you use for
setting up data entry profiles depends on the user interface you
use. You can make the necessary settings for theappropriate user
interface in Customizing, under Cross-Application Components Time
Sheet .Select FieldsIn Customizing, using transaction code CAC2,
you can determine which fields are displayed for each data entry
profile .
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 21 of 85
-
FeaturesProfile maintenanceThe views that are visible in the
CATS application depend on the periods selected during Customizing.
The following settings for data entry profiles areavailable in
Customizing, using transaction code CAC1:
Display OptionEnables the horizontal or vertical view of the
timesheet.HR Enabled CATSEnables HR features in the CATS
application.Public Holiday TypeConfigures the public holiday
default type.Time-Recording Cut-off DateThis 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 enddate by default. You can use BAdI: Calendar Display for
Recording Working Times (HRESS_CATS_CAL_DISPLAY) to change the
default time-recordingcut-off date.For more information, see
Customizing for HR-Enabled CATS under Employee Self-Service (Web
Dynpro ABAP) Service-Specific Settings WorkingTime 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 useSAP 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 usercan 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 Centerand 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 areavailable 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 whichthe 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 adifferent 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
hourscalculated because it administrates the clock times in a
background task. If necessary, change the clock times on which the
calculation is based.
Field selectionUsers enter different information when recording
their working times according to their area of activity. For this
reason, you should provide your various employeegroups 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 andabsences 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 dothis, several time sheet functions are available
to you for each personnel assignment, as opposed to each user.
PrerequisitesYou 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 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 22 of 85
-
FeaturesWhen 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 eachpersonnel assignment and data entry profile.
For more information on the BAdIs, see Customizing under
Personnel Management Employee Self-Service (Web Dynpro ABAP)
Service-SpecificSettings 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 CompositionThis section gives you an overview of the
main elements of a Personal Profile service.Concept
IntroductionThis section contains information about the Business
Object Layer (BOL) model, Generic User Interface Building Blocks
(GUIBBs), feeder classes, andapplication component
configurations.ConfigurationThis section contains specific
information about the individual configuration options for the
Personal Profile application.
ProcessThe 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 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 23 of 85
-
Figure 1: Component Encapsulation with GUIBBsFigure 1 shows the
encapsulation of several Web Dynpro components within one Web
Dynpro Application Personal Profile service. The OVP
componentconfiguration 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 theunderlying
business-object-specific Application Programming Interfaces
(APIs).
HRPAD BOL ModelThe Personal Profile application uses the HRPAD
BOL model. You can view the BOL model via transaction
GENIL_MODEL_BROWSER.
StructureThe 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(international
structures).ITNNNN_NN_REL represents HCMT_BSP_PA_R
(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 internationalview. For infotypes that have only one single
country-specific structure, it would follow the HCMT_BSP_PA_NN_R_
structure. Each infotype contains thecountry-specific infotype as
its dependent object through a 0..n relationship if it has
country-specific structures.
PERNR
Note
Example
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights
reserved.
Page 24 of 85
-
IT0004_REL 0..nIT0006_REL 0..nAll infotypes are represented as
dependent objects (for example IT0006) with relation names in the
IT0006_REL format. Each dependent object hasan international XX
structure (for example HCM_BSP_PA_XX_R0006) to provide an overview
of the data stored in the infotype.IT0006_NNThe dependent object
has an abstract child, such as
IT0006_NN.IT0006_43IT0006_41IT0006_37The 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 ApplicationProgramming
Interfaces (APIs) of the ESS adapter CL_HRPA_PERNR_INFTY_XSS to
perform all Create/Read/Update/Delete (CRUD) operations on the
HumanCapital 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) operationson 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, seeCustomizing for Employee Self-Service (WDA) under
Service-specific Settings Personal Information Personal Profile
Determine Active Subtypes andMake 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 aconfiguration. 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 andlist 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 (bizcards) 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 asIF_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 inform and list GUIBBs, see SAP
Library for SAP NetWeaver on SAP Help Portal at
http://help.sap.com/netweaver SAP NetWeaver by KeyCapability
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 2013 SAP AG or an SAP affiliate company. All rights
reserved.
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_OVERVIEWThis feeder class is used to configure
overview screens, also referred to as business cards (biz cards),
of the Personnel Profile application. The usage of thisfeeder 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 SharingInformation.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_DETAILThis 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 classesThere 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.
StructureA 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 isa 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
thePersonalProfile 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 thedestination 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 classThe 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