HCM Q3-delivery (EA-HR 607 SP14) is based on the following stack:
— NW 731 SP7
— NW UI SPO1
— SAP NW UI EXT. 1.0 FOR NW 7.03 — Integration Services: Libs Gateway:
— SAP NW UI EXT. 1.0 FOR NW 7.03 - Integration Services: Provider + Gateway Server Core NW 703/731 SPO4
— SAP NETWEAVER GATEWAY 2.0 - Gateway BEP So END seo
= SAP NW UI EXT INFRA V1.0 + SAP WEB UIF 731
— SAP UI2 FOUNDATION V1.0
— SAP UI2 IMPL. FOR NW 7.00 V1.0
— SAP UI2 IMPL. FOR NW 7.01 V1.0
— SAP UI2 IMPL. FOR NW 7.02V1.0
— SAP UI2 IMPL. FOR NW 7.31 V1.0
— IW_PGWSP4
- LSOFE 607
— SAP_HR 604
- XICONTENT EA-HR 607
Note: In NW 740, Ul services and Gateway components objects are part of NW 740 (i.e. SAP_UI,
SAP_GWFND components are part of NW 7.4). The number of components need to install in NW 740
are less.
For more information refer:
Release Information Note: 1701634 and ADMINISTRATORS GUIDE
In case of Extemal Gateway scenario, it is mandatory to have web dispatcher(WD). We recommend to use latest WD like 740... In
WD configure the redirection based on the path like odata and sdata calls should goto Gateway system & /sap/bc and other calls
should be redirected to backend system. You can use the WD URL to launch the landing page. Example of the WD profile is as
follows:
wdisp/system_conflict_resoluti:
wdisp/adé_clientprotocol header = 1
udiep/handle_webdisp ap Reader
wdisp/add_xf
waisp/allow multiple matching systems = true
wdisp/EITP/esid_suppo: false R
PREFIX=/, FROM
for Gateway Serv
STD Te , VSEORT=@, SECURL:
libs/jqueryui/;/sap/public/bc/;/sap/public/;/sap/bc/ui5_ui5/sap/HR
ORGVIS_CHART/;/sap/public/businesssuice/;/sap/bc/uiS_ui/sap/ARSRVC_SUITE_PB/,CLIENT=002
SIDE, MSPORT=8@B0, SRCURL=/sap/opu/gdata/:/sap/opu/sdata/, CLIENT:
Note: In NW 740, Ul services and Gateway components objects are part of NW 740 (i.e.
SAP_UI, SAP_GWFND components are part of NW 7.4). The number of components need
to install in NW 740 are less.
Landing Page: Page Administration — Add CHIP to the catalog
To Add CHIP to the catalogs:
> Search or locate for a the CHIP
> Click on Add button in the CHIP
> Popup appears where Catalogs available to
the users are listed (based on the assinged
roles and newly created one). Select the
Catalog(s) where the CHIP need to be added
> Select the CHIP
Configuration Section appears in right
side
> Change Title
To change title for all users. Click
Edit button next to the title in
configuration section to edit the
CHIP title
> Change Additional Data
Configure additional data (if
configurable; or functionality
provided by CHIP to configure the
content)
Landing Page: Page Administration
Transporting the changes
Pre-requisite:
> Create Transport Requests
> In Own Data maintain the following parameters with values
> /UI2/WDC_DEVCLASS
> /UI2/WD_TRKORR_CONF
> /UI2/WD_TRKORR_CUST
If user performs any creation or updation in page administration, this contentis
assigned to the corresponding transport request.
For more information refer the documentation link
x
“spicy ling prat in aru pr isha Esa sat yat > Use Pale Our Oats Parma).
uns
Re-Arrangement of the CHIPs to be displayed
» Click on the header of the CHIP you would like to move
» Drag it to the place where the lane should be displayed in future and drop it
Content is being displayed as Tile in a condensed version and in a detailed/ complete version in the
expanded CHIP. There are several options to expand/minimize a CHIP:
A page administrator with access to CUST and/or CONF scopes can upload company-specific or
client-specific background images by starting the end user page in the CONF/CUST mode. The
page administrator can choose to upload company branding images here. Images uploaded here
are automatically available to end users in the PERS scope.
URL format for Landing Page to upload background image:
https://<server>:<port>/sap/bc/ui5_ui5/sap/arsrvc_suite_pb/main.html?page=<Pageld>&scope=CUST
+ Æ move Poston [Web Dynp.. 2. Create new folders & Actions: You can insert
+ [E delimit Postion |Web Dynp..
» LE voista Postion, er Folders with New Folder Button and insert Actions
> [1 View Position Details Folder with New Application Button.
> Ci View Orgunit Detais Folder
dite be : | 3. Rename Action Text & Description
> Employee Data Ching Folder
> Cl Employee Data India| Folder
> Cl Employee Data USA [Folder
1. Rearrange existing actions: You can re-arrange
actions with Drag&Drop.
Actions displayed in landing pages
8 menus are same.
To achieve this, actions are
configured centrally in launch pad
and the launch pad is assigned to
user's role.
Only one launch pad assignment is
supported for a user.
Follow the steps indicated, to
assign custom launch pad for a
user.
Technical essentials
Dynamic content for Actions
o With the help of a feeder class, launch pad contents can be modified at runtime.
You can filter, change (or) add information at runtime.
o SAP delivers standard feeder class e.g., CL_HRPAO_ACTIONS_LPD_FEEDER
for Actions lane in HR Professional role. This Feeder class is assigned to the
launch pad (maintained in view /Ul2/LPD_FEEDERV).
o Standard feeder class adds texts to application parameter ACTION_TEXT and
additional information parameter COUNTRYNAME for each link.
Employee Manager Card Organizational Position Chief Position
Card with Gray Unit Card Card Card
background
Architect Manager
20012584 50012532
COTE Bee 5
Predefined actions in the The body area is used for
footer area displaying important data.
Supported configuration options
- Order predefined fields,
= Add (or) Remove fields in cards without exceeding the maximum no. of fields
supported in the cards (Employee - 3 (including photo), Position - 2, Org. unit - 3 ).
- Additional fields can be configured in quick views
‘Si hae
SAP Customang Implementation Gude Tr
B ® actoate Business Functions:
SAP Netwveaver
a Gateway Herder
a Gateway Service Enablement > nacos Das for PO Process Sur web 9
e. Data Channel sas oo 000000724 Das Set Process
ment. hs: «| Le
eave Reauest
‘Workfiow Settngs [Dat fr mas processo
BD Task Provider Custom
A user who is also assigned the ,HR Professional role will find all search categories in his search lane. By
means of configuration, customers can decide which categories are to be searched through when starting
the search on the small Search chip within the landing page. Results of category „Employee“ can include
data that is relevant for an HR Professional user.
= Filters show users the number
of hits matching the filter value.
— Clicking on a filter value marks
this as selected filter; more
than one are possible (except
Category" filter).
Selected filter values can be
deselected again.
- Filters are configurable by
customers within standard
IMG activities.
+ Value Suggest:
= Up to 10 possible search hits are show
below the input field.
— Suggestions are
retrieved based on the fields tied to
the search term field
(e.9. ID, long text, abbreviation, description; configu
— Suggest list is already checked for
user's authorizations.
Search for Employees and Organizational Objects in Field
Search Helps for HR Professionals
— Search concept with a simple search term field is also used in some F4 field helps in
single-infotype screens. By default, this checks on fields ID, name and abbreviation.
— Same configuration options apply here as for the Integrated Search in the master data
application.
— Used in, e.g.,:
— Position attribute „Job Assignment": Search for Job
— Position attribute „Managed OrgUnits“: Search for Organizational Unit
+) Managed Org. Units
Search: ID
ane sueño war Wenges0r Un
LE Search Criteria
Language lie
=> (Sean | one [oser Dent
va
rene (aa D Les 3
a A
E73 m
Value Suggest List: — Up to 10 possible hits from — If you cannot find what you
— As you type into NWBC the ate
you typ A . HCM Search Provider show looking for, add more
Search Field, possible hits
and recent search terms are up characters 2
3 at the top of the suggested to the Search string or rua
shown in a box below the
: values. full
Ehrch by clicking Enter or
+ Choosing a
suggested
value will open
the Profile
Page of this
employee,
position, or
organizational
unit.
, Search Engines” that can be connected per Search Category in backend:
— SAPQuery
— Embedded Search (TREX)
Settings can be found here:
— IMG of Personnel & Organization > Search
— IMG of Employee Self-Service (SAP UI5) > Search
+ By Personnel Management
» By Global Settngs n Persomel Management
> Employee Seb-Service (SAP US)_
Personal Organen » Landing Page
See > Employee Profle
etm » Salary Statement
E ER » Workng Time
» as : Search
> Neate va popkaton + EQ define Search Categories
+ andng Pose + By @ Group Search Categories
+ [2-0 confgure SAP Query
+ Configure Embedded Search
| confgure Embedded Search
+ E Ó Asson notes to Modes
+ B O Manage indexng
- E O ntantan Parameters for Auhorzaten Change Ponte Report
‘dl Iplementatons fr Infotpe Updates
‘dl Iplementatons for Structural Authoreatons
tt > sevanad Search
Step 1: Define Search Categories
Here, you define search categories which show up in the Drop-down listboxes of
the search screens (Integrated Search and Expanded Search Lane).
a
‘Show Advanced Search
Usage: Orpantatens Unt
— Tie one or more object types to the search category
— Restrict category to a country grouping for object type P (Employee) if you want to offer an
employee search category each for different country groupings.
— Define whether the category is to be used only as value help for input fields.
— Specify the search engine you want to use for this search category (SAPQuery or Embedded
Search).
This IMG Activity allows you to easily define fields
behind the simple Search Term field
in Search Result List as additional information for search hit
for Advanced Search Criteria (Search in Master Data Application only)
to be used as Facet Filter Fields (Full Search Page = Search Lane only)
to be shown in the Value Suggest list
Change View "Maintain Query Information"; Overview.
YA me MEA
Op Mantan Information. =
> ann rl sed els loci =
2 Catan Rest els pu sa
2 Conan advances Seach Ctra me rove 0
+ Cnontan Fer Felts sap EARLOYEE mm Emvloyee (m)
+ Conan Vaue Suges Fais AS Envio (US)
[loas ess armor Bogrorer
“ae SANTI, UT Oganartenalune
fe rome eae
ar posos Posten
|SaP_smLe_c ‘Search Help for Jobs.
Een Seach Ha fo Organico Uat
‘na sus Such eb for Ptos
— Enter the Query InfoSets which should be used for the Search content
— Define field names in this view for each of the purposes listed on the previous slide.
The SAPQuery will then be generated based on the entries you have made in this view.
New: Creates a new record, default
values can be pulled from the
previous record, so it can act as
implicit copy
Edit: Allows to edit start and end
date as well as content of a record.
Depending on ist time constraint key,
editing a value would also delimit a
previous record automatically. l.e.
editing Personal Data, giving a new
start date and changing content will
result in the old value being
delimited and a new value being
created.
„Edit“ incorporates „Change“, „Copy“
(implicitly), and ,Delimit*
Delete: deletes a record from the
database
View all: shows all records per
infotype (similar to History/Overview
feature in Gui applications)
Authorizations:
all existing authorizations objects still
apply
Integrated Search Within Master Data Application
Quick access to Search for Employees, Organizational Units and Positions within
the Master Data Application
pp Simple Search
Simple Search: searchforObeet
— Search term will be looked up in various Gr
database fields for each object (configurable) m
Results immediately
actionable: Advanced
— Open profile page of the search res
- Directly access a view or change a
for the search result
+ Further features:
— Value Suggest Lists
— Advanced Search
— Date Selection
+ Configuration:
= Same config options as for Search Lane in Landing Page
= see chapter on Search Lane
Actionable Search
Results
le pee
Mame Testen” Moo DONCEL 220-0-uniried
Deroga
Embedded organizational chart visualization in
Personnel & Organization application offers:
‘Organizational Unit Profile: Human Resources
[en ]) & EJ sere onen metas + Dt [mecs v
v Graphical & attractive user interface based on Adobe
— Flash
y Node display in organizational chart displays
information in text & image (photo, icons) and
contextual menus with actions to maintain
organizational structure
+ Switch to different views (Staffing Structure,
Organizational Structure and any other custom-
defined)
v Various options to display organizational structure by
time period (single date and date range)
y Flexible options to personalize & configure
organizational tree display
Test Mode:
FPM Application Configuration HRPAO_PAOM_MASTERDATA (Personnel &
Organization) with Parameter DUMMY_SELECTOR = ,X'
— > Allows you to manually call a specific Infotype configuration or Process configuration
by entering its technical key and without the configurations being part of the actions
menu yet.
+ By O customer: Define Field Properties ser meca gal System
+ B O sap: Text Felds for Screen Structures DE
+ B® customer: Configure Text Fields for Screen Structures
+ Ez O configure Screen structures for Repeat Fals E)
+ BO edr Infotyoe Attrbutes
+ By ® Define Reasons for Changing Infotypes
+ Ey O Defne Fields Relevant for Retroactive Accounting
+ Bi @ adjust Infotypes in HRPAD Model
> Enhancements to Business Logic and Updating
, Enhancements to UI Log
Intemational Infotypes
5 ose
Infotypes for Organtational Objects
Infotypes in Decoupled Infotyp Ca
+ B® create or Edit Infotype Ifotype Name ns |
+ Be @ Assign check css Namespace E
+ By O sap: Feld Properties
+ By O customer: Define Field Properties | Characteretics
+ B® aaa: Busness Logic Enhancements of Standard Infotypes = SS
+ EY O Assign Screen Structure and Conversion Cass restesowb. |
+ [By O sa»: Text Feld for Screen Structures Orga Lang. O
+ Es Q customer: Configure Text Fields for Screen Structures
Configuration Step 3 (3):
Create List (2): Enter Feeder Class, BOL-Model and Object
1. Navigate to relevant FPM
eee: [CHARO GUBE PAST rei ae ort Ln UBB nei ol Component
parameters
* Component [Hapa CCA 2. Enter
+ Object ame: [TOS CO
— + Feeder Class for List
ere)
J [som stuctre | Reiten. | "Component. |: Assigned... [suite | Pot enter + Component (BOL-Model)
Configuration Step 3 (3):
Create List (3): Design the List
A a o 1. Navigate to relevant FPM
Component
[pren 2. Enter Feeder Class, ...
Be
‘Actone | js. | oran. Change. | Change... | Leck | Locka. | | vest From | vaio 3.
Design the List
+ By selecting the
relevant Infotype Fields
stun senems Tone | wens Setena | Oucivauscnems | = + By defining the Actions
alee re = = in the Action Column
+ [D Column: FPU_ROW_A.... LitkTo Action Determines by Feeder Cass .. =|
EI: Demmonserser et ot terms y Fede Ca. |
+ Dom pares ‘ners y Fc cs |
+ E cou: acom Input Fi Determined by Feeder ss... ~|
+ Demmin pares ‘ten y Fee Can. >|
+ Dose apa Ft herd by Feder om. ~|
te = Ostras rec | |
+ DDcoumemao nari = mere Fee cas =
+ Gleave: se008 pares + vat om ‘tered y Fede Css. |
¡A > ve ones Fee Ca. |
The Biz-Card Configuration is
equivalent to the Dataset
Configuration based on the FPM-
Form Repeater.
sss...
Configuration Step 3 (5):
Test your UI Configurations: Application (Parameter:
TEST_MODE=X)
Benefit of Test Application
Embedding UI configurations into the Master Data Application means adding this instance to the
Action Menu. To be able to test your infotype Ul configuration without this step, you can use the
Test version of the Master Data Application by running the application with Parameter
TEST_MODE =X.
We only can keep one active IT-Configuration in our Configuration Table as the call must be
unique for the Action Menu, thus it's not possible to test a new configuration in the Main
Application (as this runs only through the Action Menu) _
Configuration Step 3 (5):
Test Configurations: Set Up Test Application and execute test
Se ee al Set Up Test Application
! rn
| TE ere eee | + Enter your Configurations in the
| me left area
| um Conmes es Ca Gun virer | |
| a ee | + Call Configurations of other
| Mees ern users in the left area
| ar ee ee
| Ce Execute Test
| sn = eae
ewe Lanse te Vain ed re
| Sr mus + Use the icon in the column “Data
| Core Records” to test the List, Dataset
e = ia Raus and Detail Configuration
Lo tame T =
E | + Use the icon in the column “Biz-
[tora Card” ” to test the Biz-Card
Assign Infotype WDA Configurations into Master Data
Application
E [Infotypes| After successful test of the UI
+ Infotypes for Employees configurations, you add them into the
= Master Data Application in IMG of
Infotype UI Configurations for Master Data Application
B® customer: Overrde Ul Configurations
Personnel & Organization in node
"Infotype Ul Configuration for Master
Data Application"
Note:
This adds the screens into the master
data application and connects the
different views into the overall framework
to connect the different views per
infotype.
To make the Ul configurations available
in the Actions Menu, you later on need to
add the Infotype Configuration in the
Launchpad Customizing (Transaction
LPD_CUST).
The Biz-Cards will show up on the
Object Profile Page, the factsheet
per employee and organizational
object on the right hand side of the
master data application.
You have to enter them in the
Customizing Activities/Configuration
Tables as shown on the left.
Usage of HCM P&F for Multi-Infotype Scenarios
Multi-Infotype scenarios for HR Renewal content are
configured by means of HCM Processes &
Forms. The individual forms run embedded into
the Actions Menu, Master Data Application and
Lanes.
Each process can be executed directly for a selected
organizational object or employee that the user
picks from worklists, search results or
organizational structure / workforce viewer.
The following Webdynpro ABAP based form types are
available within HCM P&F:
Configuration of HCM P&F Content for Embedded Usage
HCM Processes & Forms for HR Professional Users:
— The Design Time for Processes and Forms is also used for the processes that run
embedded in the different applications for ESS, MSS, and HR Professional.
— All sample processes shipped by SAP for the HR Professional user role are configured as
1-Step processes, i.e. no other role is involved.
— The HR Professional fills in the data and can - [3 peisonneitianagement
choose Save or Save as Draft. LB Gobal Settngsin Personnel Management
| Ñ Y Personnel Organization
— Customers can add workflows if required. +B Hot on Customieng
Bas Settings
Integradon
Secury
Role
Infotypes
+ By deine Attachment Types
+ B® define inks for Additional information
» Generic Senices
7 huthorzations fr Processes and Forms
> Content Groups fr Authoreaten Check
+ Ez Q Deine Authorzation Method for Activtes (AI Processes)
+ By @ padi: implement own Logic for Authorzatin Check
+ [8% @ Define Authorization Methods for Active (for Each Process Group)
Enhancement Options:
— customer-specific ITs can be added
— Configuration of single-step / single-user or multi-step / multi-user scenarios, including
Workflow integration
= Decoupling of infotypes is required
= Benefits Classical One-Pager forms (,FPM Form“)
= Non-technical representation of infotype content, mix of infotypes and fields possible
" Easy web forms for casual users
= Benefits Roadmap-Forms:
" Simple user guidance through larger content
* Combine web enabled infotypes to define forms
= allow for quick re-use of existing infotype configurations (FPM configs) > low TCO
— Users will find the drafts of the HCM P&F process they saved as draft in their inbox
(Tasks by Draft lane) or the Open Tasks tab in the master data application.
— Prerequisite: you need to configure a dummy workflow so that the drafts show up in the
described way.
— See the SAP Library chapter ,Workflow Template WS33700033: Draft for Process Start
(Web Dynpro)” at
http://help.sap.com/erp_hcm_ias_2013_01/helpdata/en/bc/ba415499d84bd68917c3990
99d82aa/frameset.htm
Compare and Reconcile Objects
— You can use this function to compare processes or form scenarios using systems or
clients. You can also copy the settings that you made in a different system or client for a
process, validity period of a process, a form scenario, or a form scenario version, into
the current system.
— When reconciling, you overwrite the settings that you made in the current system for the
object to reconcile, with the settings for the object as they are in the remote system.
— See the SAP Library chapter ,Compare and Reconcile Objects” at
http://help.sap.com/erp hcm ias 2013 01/helpdata/en/71 10e 7aai91#4968ae9d56a4d68
Further Reading:
Check out existing HCM P&F Rollout Material
The HCM P&F framework was introduced in
earlier releases as overall framework to handle
processes across multiple users / roles,
connected with workflows.
+ Media Library of HCMPF on
SMP:
https://service.sap.com/hcm
For more information on existing configuration
options for HCM P&F check out the
comprehensive material at SAP Service
Marketplace.
Personal Data
Personal Data
Personal Data
Personal Data
Personal Data
Personal Data
Personal Data
Personal Data
Personal Data
Payro statu
Chalenge
‘Addresses
‘Addresses
‘Addresses
Addresses
Addresses
Addresses
Addresses
‘Addresses
Addresses
Addresses
Define the country version (Infotype 2 O SC UE SAA
version) you would like to create ee ET
the Form Scenario for. (Please Si [== =e
check availability first) Renata Tamla) vom
sera
Please note: Infotype version is
an optional entry field. If no
version has been defined the
process can be started for
employees of any country. If so,
customers have to ensure that the
process contains only infotypes
that can be maintained for all
countries.
Impacts of Personnel Actions Types and Reasons for
Personnel Actions:
The definition of Personnel Actions and Reasons for
Actions is required to use this in the Roadmap Form
configuration. This can be done in the
Implementation Guide.
Please note:
Based on the customizing settings for a certain Action
Type the input fields for the first step in the Roadmap
Form ‘General Process Data’ is being defined.
Additionally it can be defined, for example whether the
‘Effective Date’ (specified date) is the start date for
new records that will be maintained in the Roadmap
Form. For a Termination, however the Date control is
than set to ‘Specified date is end date for old
records’.
Example: Action Type ‘Organizational Reassignment is
defined as Action Type in the Roadmap Form ‘Transfer’.
This means Position, Personnel Area, Employee Group
and Subgroup will be displayed in the first step ‘General
Process Data’ of the corresponding Transfer Roadmap
Form.
(+ Change View "Personnel Action Types": Details
e 718/0080 CHR SESS BD OB
Change View "Personnel Action Types": Details
Y wo: OHO 8B
‘con Type (8
heck fate
[spa Poston
Da Pes. rea
(Depa Employee group
lDepy EnployesSubgroo.
Deep Dive: Roadmap Forms
Create Form Scenario V
Form Scenario Roadmap means:
1. Selection of the Infotypes and Infotype
Versions (Countries) to be maintained in the
Roadmap form. Depending on the Country
Version defined for the Form Scenario the
corresponding Infotype Versions are beeing
displayed e.g. for Canada IT Version 07 and —>
99.
2. Sequence of the infotype selection defines
the sequence of the infotypes to be displayed
as steps in the Roadmap Form. Change is
possible after infotype selection and using
the corresponding features for moving up
and down or adding/ deleting the
corresponding infotypes/ subtypes.
3. Definition of the Subtypes of an infotype to
be maintained in the Roadmap Form
4. Definition of the Operation to be performed
per Infotype (Create, Change, Copy, Delimit)
5. Definition of the indicator whether a step/
infotype in the Roadmap Form is mandatory
(Required Entry) or not.
+ The Infotypes you include here are the Floorplan
Manager based Webdynpro ABAP Configurations of the
infotypes. Thus, all configurations and field attributes of
the “individual” Infotype screens also apply within the
Roadmap Form.
2. You can change field attributes by creating a copy of the
FPM WDA Configurations and adjusting the copy in FPM.
The classical field attributes table T588M is not valid for
the WDA configurations. A successor table to T588M is
available, T588MFPROPC. However, settings in this table
apply to Infotypes in the Decoupled Infotype Framework in
general, i.e. to all Uls consuming the decoupled infotypes,
e.g. HCM P&F, ESS, Master Data Application, Roadmap
Form...
Deep Dive: Roadmap Forms
Create Form Scenario VI
Œ fomscenaro fée Goto Lies System Heb
Scenario Step Definition 97181008 LH 9009 Bm 08
For single-step processes the default | = = = ne
settings are fine. Thus nothing m
Eas Form Scenaro [ERC Zs carrer
needs to be adapted. Estan —— [wala Versen RB]
ES) HS)
‘Object Name y
Create Process (similar procedure Design Time for Processes and Forms
like for Form Scenario creation)
+ 8
4 , [ross]
Select ‘Process’ from drop-down
listbox os) aa a O rss soto
Enter the Name of the Process = zur a
to be created and press ENTER
(System ensures thatthe
Process does not exist)
You can easily create the object
(Process) when confirming the
pop-up message.
In the pop-up Create Process the
following entries have to be
defined:
Process description, e.g.
‘Transfer Employee CA’
Form Scenario (created
previously)
Initiator Role (=HR
Professional)
Change Process
Process Definition pan ES
Prec =} me (Sm men PLONE ca
1. Process Name is pre-defined by the miss mm ed
Process Description entered in the nenne On —
pop-up previously, e.g. ‘Transfer D vir Fert |]
Employee CA. This Process Name is papal wensevale oes . :
than being displayed in the Roadmap — <& zt" 0 hae ICO
Form.
2. Select Validity Period via double TT
click. APE) :
Fa res rre ara jan mow ono 0
+ Send Variant is pre-defined. Per default
this is ‘Write Data to Application
Database’. Thus nothing needs to be
done.
Ps eR NON wala)
a
+ Process Type: most processes are
started after the user has selected the
employee. E.g. user starts a transfer for
employee 'Steven Smith'. Butfor some
processes, like hiring, no ‘start object like — rome
employee exists. Thus Process Type aie Bee
‘Process without Start Object needs to be Se At ‘at Chay at
selected.
1. You can assign any of the standard workflow templates that work with FPM Form type also to the
Roadmap form type, such as e.g. WS33700017. No dedicated new workflow templates have been
created for Roadmap forms.
Note that some workflow templates read out specific form fields which is not supported in
Roadmap Forms at this stage.
2. To launch a Roadmap form from a Workflow item, the roadmap form is to be called in the HCM
P&F Standalone application (ASR_PROCESS_EXECUTE_OVP_CFG), not in the HCM P&F
application which runs embedded within the Master Data Application.
You use a form scenario with ‘Infotype Version’ = ‘blank’
All infotypes in Roadmap Form will be maintained without
specifying the IT Version
Process can be conducted for all employees (=>displayed as
action in every employee menu icon; Prerequisite: launchpad
customizing is done)
After process start, the country specific Ul Configuration of the
corresponding infotypes is being shown in the roadmap form.
Please note: If the UI configuration is not available, the UI
configuration for IT Version 99 (all countries) is being taken into
account.
Special case HIRE: After maintaining the first step in the Roadmap
Form (General Process Data) the corresponding IT Version (that
applies for the employee to be hired) will automatically be pulled
for the subsequent infotype steps. The same logic as described
above applies then.
Please note: There are no options to ‘override’ this with a ‘variable key (ie.
option to pull a special infotype UI configuration when the IT is called in this
specific process)
If a business process requires different infotypes per
country to be maintained, you should configure one
form / process per same set of ITs.
+ Example:
= Transfer NL requires IT0001, IT0007, IT0008, IT0059
whereas
» Transfer CA requires only [T0001 , IT0007, IT0008,
+ You use a form scenario with ‘Infotype Version’ = ‘Country-
/industry-Code' (e.g. 01, OE)
Please note:
Ifyou use Infotype Version '99' on Form Scenario level, this means that
the form can only be used for employees with MOLGA 99 (i.e. employees
working for international organizations)
Within the form scenario, you can now include all infotypes of the Infotype
Version defined for the Form Scenario plus those with version "99,
The corresponding Infotype Version of the UI configuration needs to be
available. The Infotype Version is derived dynamically, itis not stored in this
table.
tan IT you want to include does not have national Infotype Version and you
add this, the system will automatically retrieve version = ‘99 when the
process is run in the master data application. IT Version ‘99' means in this
context the international infotype version (not “employees working in
international organizations’).
Example:
When configuring a Roadmap Form for Netherlands, you can add all
configuration for which either version ‘05 or '99' exist, Whenever an infotype
is available with version '05, this will be pulled during runtime in the master
data application. Whenever there is no ‘05' version for an infotype,
automatically version '99' is pulled during runtime in the master data
application.
Consequences:
+ Process can only be performed for employees of the corresponding
country (MOLGA = IT Version of the Form Scenario).
+ Each infotype defined for the Roadmap Form will be displayed with the Ul
‘configuration that corresponds to the IT-Version you defined in the
Roadmap Form config.
Special Case ‘HIRE’:
In the first step ‘General Process Data’ of the Roadmap Form only those
values can be selected (as user input of via F4-help) that correspond with IT
Version defined for the Form Scenario.
Remove the field Marital Status from Employee Profile
5 Employee Self-Service (SAP UIS) Perform the following steps:
” Landing Page .
+B Landing Page overview 1. Go to transaction SPRO.
» Work Feeds
u My Info 2. Personnel Management >
Y EmployeeProfie Employee Self-Service (SAP UI5)
-E a Profie Bids > Employee Profile
no Rens a Data Se Configurations for Data Retrieval
: E = ane with Field Groups Create Configuration with Field
+ E O create Configuration for Fiker Dialog Box Groups.
+ BO Assign Configuration to User Interface
+ By O Assign Configuration for Header Area with Talent Data
» Extend Field Selection
» Calibration Grid
, Search
= rare Follow the steps mentioned
SEMESTRE 1. Go to transaction SPRO.
_ en Profile 2. Personnel Management >
E B Employee Profie Overview Employee Self-Service (SAP UI5)
Ai ee > Employee Profile >
+ E & create Configuration with Field Groups Configurations for Data Retrieval
: I E ee >Create Configuration with Field
+ Bi O Assign Configuration for Header Area with Talent Data Groups.
> Extend Field Selection
1 Calibration Grid
Choose Add Fields to a
Configuration (as indicated
in the screenshot)
121
Configuring Employee Profile (3/3)
Remove the card Trainings from Employee Profile
Change View "Add Fields to a Configuration": Overview
ROBE
so.
Es cp
AO |g aa at
et ae óseo Su Sanda et abel (abat weil Gow atl Gun Tee
psx pes coMPA RATIO Compare Ratio. (29 Compare Ratio Compare Ratio. O
ES Pecanagenfrge Specenzoen ange Pecanagen ange O
rem re al sis payee! (
Lars are Porte pm vid Feine a
or Paco nao Por Giese o
ares var ser ver ot
fap uss cost Total os of Trans SéTra Cont ‘cot [a]
sar pss ramos Upcommg Tenngs 237 Upcomng Trans ‘scoring Tanngs [a]
(serrer enone Talent Group 58 Tant Group Talent ou a at and Succsson
sus pearenauce Accompshment Sspeormance Petomance [a]
jasper Portal so Potental potent la]
(ares caen TYEE (Greene a ‘ree Te [a]
Jaap vss posan Moby a) Moby [a]
‘sap socersstou ‘uccesion 5 Succaor F … Succesor [a]
MEE Competency Matchup “ Competency Match a Competency Matchup
Is ss_can ner parcs Mssng Competences ss hssogCorgetences a
Joxe ss na seo Tant Gé “ ‘an Grd i
mur ss motions Paromance Hstory a a
5. Select the row which has Trainings in the Field Group Title column .
6. Delete the row (as indicated in the screenshot) and other fields belonging to
the group Trainings.
1.Add the new card and Field Group to SAP_ESS_UI5_EMP_OVERVIEW.
2.Select the Field Group Title checkbox. Add all the necessary fields under it.
3.In SPRO go to the node Personnel Management->Employee Self Service(SAP
UI5)-> Landing Page->Employee Profile-> BAdl: Modification of Card Visibility.
4.Create a new BADI Implementation to enable the display of the card in the
required View (Overview or Talent) and for the required role (Manager, Employee,
or Other Employee).
1.Create BADI implementation under Personnel Management > Employee
Self-Service(SAP Ul5)> Landing Page > My Info> BAdl: Defining the My Info
Icons and Text.
2.Implement the method PROVIDE_INFO_LINE_ITEMS for displaying the basic a
information relevant for an employee, for example, 90% CATS incomplete 8
and16 Sick leaves remaining. s]
Services in My Info Chip
«To display services in the My Info chip, go to Personnel Management >
Employee Self-Service (SAP Ul5) >Landing Page > My Info> Configure
Launchpad for My Info Services and refer documentation for this node.
Personnel Management
Global Settings n Personnel Management
Personnel & Organization
Organizational Management
Personnel Development
Personnel Administration
HR Administrative Services
Recrutment
Banefts
Compensation Management
Personnel Cost Planning and Simulation
Enterprise Compensation Management
Management of Global Employees
Company Pension Scheme
Pension Fund
Position Budgeting and Control
Managers Desktop
Expert Finder
Human Resources Information System
Manager Self-Service (Web Dynpro ABAP)
[Manager Sei-Senvce (SAP UI) |
Add a new monthly Work Feed for all employees named ‘Unused Leaves’
Step 1: Create OData
You can use the existing service HRESS_EMP_WORK_FEEDS_SERVICE as
template.
Service
Display IMG
Za formation
FE Eenoscse nical Service Name ‘HRESS_EME_WORK_FEEDS_SERVICE 1
ı
Structure ‚Service Version -
> [B,_ _ SAP Customizing Implementation Guide Description Work Feeds for Employee and Manager
+ By O activate Business Functions External Service Name [ERES EMP WORK FEEDS SERVICE ]
y SAP NetWeaver Namespace CI
= — Seema Data Provider Class CL HRESS GH KI EMPLOYEE FEEDS
= Bac ‘ODate Chan = m
User Sel Service Setup Soaked By. AE J
» Connection Settings to SAP NetWeaver Gat Cha = RATES
y Service Development for Backenc [PAOC_ESS_UIS
+ B O [Maintain Modes
+ By Y maintain Services —
+ By O Display Models and Services -
+ By O OData Channel Generation Tool Technical Model Name IHRESS_EMP_WORK_FEEDS
E Backend Event Publisher Administration Model Version 1
» Logging Settings Description [Work Feeds for Employee and Manager
» ‘Support Utities Model Provider Class [CL ERESS GH MD EMPLOYEE FEEDS |
Created By RAINAS
Changed By RAINAS
Package PAOC_ESS DIS
_ Display Service
Example OData
Sete Informeion . + Service created for
Technical Service Name ZHRESS_CUST_EMP_WORK_FEEDS SERVICE Y: A
Service Version 1 this example
Description [Runtime for custom employee work feeds
‚External Service Name ‘ZHRESS_CUST_EMP_WORK_FEEDS SERVICE
Namespace
Data Provider Class [ZCL_HRESS GH RI CUST EMP FEEDS)
Created By MERTASAS
Changed By MEBTASAG
Package (573
{ Model infomation
Technical Model Name ZHRESS_CUST_EMP_WORK_FEEDS
Model Version can
Description [Model for custom employee work feeds
Model Provider Cass [2CL_BRESS GH MD CUST EMP FEEDS
Created By
Changed By
Package
_ Create Model | Mode
Configuring Work Feeds (3/11)
Step 2: Configuring Work Feeds
| Display IMG
TG Ed | Besingscsets Sec sets for acivey dracivated BC Sets for Activty [EBRelease Notes | Change Log Where Ese Used
Structure
7B Personnel Management
> Global Settings n Personnel Management
Personnel & Organzaton
Organizational Management
Personnel Development
Personnel Adminstration
HR Administrative Services
Recutment
Benefits
Compensaton Management
Personnel Cost Planning and Simulation
Enterprse Compensation Management
Management of Global Employees
Company Pension Scheme
Pension Fund
Postion Budgeting and Control
Managers Desktop
Expert Fnder
Human Resources Information System
HRESS_EMP_WORK_FEEDS_SERVICE
HRESS_EMP_HORK FEEDS SERVICE
HRESS_EMP_HORK FEEDS SERVICE
HRESS_EMP_WORK_FEEDS_SERVICE
HRESS_EMP_WORK_FEEDS_SERVICE
HRESS_EMP_WORK_FEEDS_SERVICE
HRESS_EMP_HORK FEEDS SERVICE
HRESS_EMP_HORK FEEDS SERVICE
HRESS_EMP_NORK FEEDS SERVICE
Define a new subscription key using
the OData service and the collection
you just created. Here you can also
define the OTR alias for the text to
be displayed for the employee work
feed Subscribe/Unsubscribe option.
Collection Version [Ai
EMP_ANIV_TODAY 1
EMP_ANIV_UPCOMING 1
EMP_8DAY_TODAY fb
EMP_BDAY_UPCOMING a
EMP_CATS_COMPLIANCE a
EMP_EXPIRING_QUALIF 1
EMP_MISSING_QUALIF 1
EMP_PAYSLIP 1
EMP_PRM 1
PUBLIC_HOLIDAY a
MGR_CATS_COMPLIANCE 1 pa
MGR_COMPENSATION 1 EN
Configuring Work Feeds (5/11)
Step 2b: Assign attributes to the subscription key
= Manager Self-Service (SAP UIS)
AA Here you define the OTR alias that is
= lite used to fetch the text for the work feed
notification. You can also set the
options - priority, unsubscribe — for
your feed.
Info": Overview
? newentes BREA
‘View for Subscription Info,
| | Subscription Key Pers. subarea Alas Name for OTR Unsubserbable
|HRESS_EXPIRNG_QUALIF PAOC_ESS_UIS/HRESS_WORK_FEED_EXPIRNG_QUALIF True
| |HRESS_MISSNG_QUALIF PAOC_ESS_UIS/HRESS_WORK FEED MISSNG_QUALIF True
|HRESS_PAYSLIP PAOC_ESS_UIS/HRESS WORK FEED PAYSLIP True
| |HRESS_PRM FAOC_ESS_UIS/HRESS_WORK_FEED FRM True
|HRESS_PUBLIC_HOL PAOC_ESS_UIS/HRESS_WORK FEED PUSLIC_HOL True
|HRMSS_CATS PAOC_ESS_UIS/HRMSS_WORK_FEED_CATS False
|HRMSS_COMPENSATION PAOC_ESS_UIS/HRUSS_WORK FEED COMP rue
_HRMSS_EXPIRNG_QUALIF PROC_ESS_UIS/HRMSS_WORK_FEED EXPIRNG_QUALIF True
|HRMSS_LEAVE PROC_ESS_UIS/HRMSS_WORK_FEED LEAVE True
IHRMSS_MISSNG_QUALIF PAOC_ESS_UIS/HRMSS_WORK_FEED_MISSNG_QUALIF True
IHanss_prm PROC_ESS_UI5/ARMSS_WORK_FEED_PRM =
Configuring Work Feeds (6/11)
Step 3a: Create a BAdl for fetching the data
2 Manager Self-Service (SAP UIS)
N Landing Page
Sr Create a new BAdl
HE implementation for fetching the
LR econ oc een work feed notification text.
(9 BAdI: Defining the Text for Work Feeds|
E
[Descrpton 2222 |
Work Feed implementation for Comper =
HRESS_WORK_FEED_EMP_B AND A Implementation for Employee Birthdi ”
HRESS_WORK_FEED EMP CATS Implemenation for Employee Cats Wt
HRESS, WORK_FEED_PAYSLIP Tupienenation for Paysiip Work Fee
HRESS WORK FEED_ PUBLIC HOLIDAY HRSSS_WORK FEED PUBLIC HOLIDAY Implimentation for Public Holiday
HRESS_WORX_FEED_LEAVE HRESS_WORK_FEED_LEAVE Implementation for the leave work !
HRMSS_WORK_FEED_QUALIFICATIONS HRESS_8_WORK_FEED Implementation for Qualifications
Configuring Work Feeds (7/11)
Step 3b: Add filter to BAdl implementation
Assign the filter value with the subscription key that you
have just created. This is important because it will enable
the BAdl to be called for the correct work feed scenario.
Enhancement Implementation ZHRESS_WORK_FEED_UNUSED_LEAVES Change
arm A200 XoRs
eo Puma i
‘ZHRESS_WORK FEED UNUSED_LEAVES
Enhancement Implementation A, E,
Properties 14 History + Technical Details Eh. Implementation Elements |
O Filter Values
Ela contratos] corras [vl |e va en Jr)
Fier Combinations | Fit... | Value 1
—
+ À ZHRESS_WORK_FEED | Implementation: BAGI: Defining the Text
qu Implementing = = Ic gro e
[HRESS_UNUSED_LEAVE - IV SUBSCRIPTION KEY | ;_UNUSED_LEAVE IV_SUBSCRIPTION_KEY
Configuring Work Feeds (11/11)
Step 5: Add the subscription key to the Role personalization
a DE By adding the subscription key
= to the role, all users of this role
= na can subscribe/unsubscribe to
the work feed notification.
(eviews «| (EIN) (__show Documentation | EE
Role (SRE EMPLOYE Ess 015 1
Employee Self-Service Composte Role consi
Overview of Launchpads
Die Lancopat | Den Repostary
MEILE
am me
eo oenc are Test 2 Dans
Be — ee u.
er nis rag
a wen
ES HRS LO. role Sefsenca Lame Pu
Es EU Epis Sef Seve
ES FEU Envie sefseves
ES En Ei set Sever
ES wae Eph Sef era Ny o Line
ANIGETION Ely ferez Nanton tens
Es NAS Enya Safe Nation tens
ELATED KS SS Mena Rebtel ls
ES FELIS ES Nenu Rete ns
Es EL Dus ES Menu Rebtel ns
FAG_REORS —FAG_REORG
FON N YOU CAN ALSO CO You Car Ao Lk
Fou UO Franc Hate: Cata rane
CCA Franc OW (ete Seres)
Po RUN Fran WOW (etd Li)
me am Sol Rothe
A Rega o estables Bae Rs.
AN YOUR An "You anal Deben Lt
mm FPMLDEFAULT Debt gato
mn SAD SHAS METEO
Ed) OEM Fr Worten
UNS FU 6 MESSE UP se per
E
m
PVG VSG VS SVS GV SVS VS ESS NS ESS S
SS PSSSSSSSSSLS SSS SST SSS SLSES
El
2a
th
5
8
ji
ä
ae
E
ii
i
i
E
é
TA
GER NES
i
5
1609200
207201
16422
EL
20202
TEE)
21523
15223
24523
231203
2203
a3
20722
2.5203
2.203
wa
nam
2.2200
0602209
62.209
297201
3162010
zus
1.2200
Coen
3203
168200
Das
DD
042013,
2020
204208
aaa
5122010
1605203
7205208
0.012007
050208
(205.203
001200
050200
1042012
2105203
A
50620
10202
91200
1042012
4042012
202002
DI
71202
06112009
Perform the following
steps:
1. Goto transaction
SPRO.
2. Personnel
Management>
Manager Self-Service
(UI5) >Landing Page
> My Services >
Configure Launchpad
for My Team Services.
The Launchpad for My
Team Services is Role:
MSS Instance:
TEAM_MENU.
142
Configuring Approvals
Adding new Workflow-based Items in Approval
— Under SAP NetWeaver> Gateway Service Enablement> Content> Workflow
Settings> Maintain Task Names and Decision Options, create entries for new workflow
item and also decision options, if you need custom actions for the work item.
— If you have custom actions for work item, then you also must implement the BAdI
/IWWRK/ES_WF_WI_BEFORE_UPD_IB with appropriate filter parameters to handle
decision option.
— For launching task specific application from inbox, an entry must be maintained in
transaction SWFVISU.
Nonworkflow-based Item (Other Approvals)
— Launchpad Role/Instance must be configured for this.
— Refer documentation Under Personnel Administration> Manager Self-Service (SAP
UI5)> Landing Page> Approvals> Approvals Overview for more details.
Perform the following steps:
1. Go to transaction SPRO.
a E ® ee Be Displayed 2. Personnel Management >
+ > O specify Color Display of Absences Employee Self-Service (SAP
en UI5) >Working Time > Team
- 2 Q Badt: Control Processing of Leave Requests Calendar.
- [2 O Bad: Team Calendar Enhancement with Additional Information
The HCM Processes and Forms framework previously used the Adobe interactive forms
solution integrated with Web Dynpro ABAP for its user interface (UI). A new UI based on the
Floor Plan Manager (FPM) framework has been created as an alternative to this.
More information
HCM Process and Form in Web Dynpro ABAP
The following new form scenarios are introduced:
Roadmap: To define the roadmap processes and form scenario, roadmap form scenario can
be used. You can find more information at: Roadmap Form
FPM: To define the Floor Plan Manager (FPM) based processes and form scenario, the FPM
form scenario can be used. You can find more information at : FPM Form
Mass: To define the mass process and form scenario, mass form scenario can be used. You
can find more information in Mass Form and in Mass Processes and Fast Data Entry
+ The slim client Netweaver Business Client for Desktop does not require additional
licenses. It is a good alternative to Portal usage for professional users.
+ HR Renewal 1.0 is fully released with NWBC 4.0 for Desktop.
+ Software, operating system and browser requirements as well as restrictions are listed in
SAP Note 1754946.
+ For more information about the SAP NWBC 4.0 for Desktop please visit also the SAP
NWBCs space on SAP Community Network at http://scn.sap.com/community/netweaver-
business-client and the SAP User Experience Community
https://experience.sap.com/post/show/51 .
+ See also the Software Download Center at http://service.sap.com/swdc
>> A- Z Index >> NWBC NW Business Client 4.0
+ Available as of HR Renewal 1.0 SP18 plus any of the following minimal recommended
versions:
— 7.00 SP027 and up
— 7.01 SPO11 and up
— 7.02 SPO11 and up
+ Required Notes
— 1685257 - Upload of SAP delivered NWBC Roles to SAP Netweaver Portal
— 1708020 - Support of UI5 based on ABAP applications in the
— 1737445 - Internet Explorer standards mode rendering for EP portal
— 1895989 - UI5 ¡View style sheet rendering issues
— 1935713 - Unified Shell support for Navigation Mode 10 in Enterprise Portal
— 1956146 - Shell API support for navigation with system alias in Enterprise Portal
+ Blog with links to SAP Help Portal
http://scn.sap.com/community/erp/hcm/blog/2014/01/16/portal-available-in-hr-renewal-10
+ Supported Browser Versions
— see Product Availability Matrix http://service.sap.com/pam
Landing pages and Webdynpro for ABAP applications can also be accessed directly
via Browser URL. This is an option for testing phases. For productive usage, this
has the following restrictions:
— no log-off feature, sessions would be kept until automated log-out;
— no accessibility options in shell dialogue;
— no language settings in shell dialogue;
— no automated theming by client application;
Thus, we only recommend this environment for project implementation and testing
phases. Theoretically, it could be deployed also for productive usage for endusers,
but customers would have to solve the named restrictions themselves.
‘Install HR Renewal
For more information refer the Administrator's Guide in HR Renewal documentation
2 Configure the Suite Page Builder (SPB)
Like activate/configure required OData and SICF services required for SPB. For more
information, refer the Prerequisites in Suite Page Builder documentation
@ After configuring SPB, test the Administration Page
3.Configure the HR Renewal content
For example: activate/configure required OData and SICF services required for ESS
CHIPs/lanes to work. For information refer the ESS Landing Page documentation. Similarly
to configure MSS HR Renewal content refer the documentation. To configure HR
Professional HR Renewal content refer the documentation.
Configuration overview is also mentioned in the HR Renewal Administrator's Guide.
Batter configuring HR Renewal content, test the landing page (with roles
assigned to the user)
TIPS
List of OData and SICF services required for the SPB and HR Renewal are listed in the documentation
FAQs Documentation
Different content for users in Action Lane in HR Renewal
http://scn.sap.com/community/erp/hcm/blog/201 4/01/09/different-content-for-users-in-action-lane-in-hr-renewal
Different Action Menu for different objects in HR Renewal
http://sen.sap.com/community/erp/hcm/blog/2014/01/09/different-action-menu-for-different-objects-in-hr-renewal