HCM Processes and Forms

Additional User Interface

May 2012
Objectives

At the end of this module, you will be able to:

• Understand the need to providing an additional user interface.
• Understand the positioning of the additional user interface.
• Understand how you can use the „Design Time Tool“ to create the
additional user Interface.
• Understand how to use the additional user interface from different
roles.
• Understand how to use the Service layer and how does this help
• Understand how to configure the additional user interface in the
„Design Time Tool“
• Understand consumption of the additional user interface from
ESS(Employee Self Services) and MSS(Manager Self Services).
• Service Layer details

© 2012 SAP AG. All rights reserved. RKT 2

Why Additional User Interface?

• “HCM Processes and Forms” is a

framework which can be used by
customers to create customer
business specific processes.

• The user Interface used by “HCM

Processes and Forms” is Interactive
Adobe by SAP.

• Due to market demands we are now

providing additional user interface
for “HCM Processes and Forms”
framework.

• The additional user interface is

based on web dynpro ABAP
technology .

© 2012 SAP AG. All rights reserved. RKT 3

Positioning of the new Additional User Interface

New alternative is based on Web Dynpro ABAP technology

 New Forms Design Tool
 New Presentation Layer

Existing investments in SAP Interactive Forms by Adobe are safe

 Project goal is to introduce an additional UI not a replacement. This is a side-by
–side approach .Customers can choose the technology according to their
needs.
 Most configuration, other than form layout, is meant to be reusable with Web
Dynpro UI version if you want to switch

© 2012 SAP AG. All rights reserved. RKT 4

Adobe UI vs. SAP Web Dynpro ABAP UI

SAP Web Dynpro ABAP SAP Interactive Forms by Adobe

Potential Advantages Potential Advantages

 Lower Total Cost of Infrastructure (TCI)  Printing – No additional effort/WSIWYG
 Leverage existing ABAP skills  Strong forms workbench
 Better translation support (i.e., 1 form for  Looks like the paper solution you are
multiple languages) already familiar with (i.e., no training)
 Improved UI element capabilities like more
robust help values (F4), table object
 Supported by traditional SAP mechanisms
(e.g., notes, support packages)

© 2012 SAP AG. All rights reserved. RKT 5

The Design Time now Supports the Additional User
Interface
 Web Dynpro ABAP Forms
1
 Forms, Lists

 At runtime these will

automatically be taken into
considerations by
1 application

© 2012 SAP AG. All rights reserved. RKT 6

Features of the Additional User Interface(1)

We now have an alternative to

Adobe LiveCycle Designer . 1

1 The alternative will be based on

web dynpro ABAP 2

© 2012 SAP AG. All rights reserved. RKT 7

Features of the Additional User Interface(2)

 Messages are linked to the

fields that invoked the
error. 1
 The information about the
field that is responsible for
the error should be
1 provided by the backend
 Adobe forms do not have
this feature

© 2012 SAP AG. All rights reserved. RKT 8

Features of the Additional User Interface(3)

 Drop downs and OVS both

are possible 1
 Customer defined F4‟s are
also possible
1

© 2012 SAP AG. All rights reserved. RKT 9

Features of the Additional User Interface(4)

 It is possible to use the translated

data elements in a form.For
example if you use fields on the
1 form which have translated data
elements then the form will
automatically get translated .
1

© 2012 SAP AG. All rights reserved. RKT 10

Features of the Additional User Interface(5)

 The form can use the

properties of fields defined
in the design Time Tool for
1 example if a field is defined
as „read only‟ , „output field‟
then the form inherits these
properties
1

© 2012 SAP AG. All rights reserved. RKT 11

Launch From ESS Role

 Webdynpro ABAP form is

listed in the ESS services
and can be launched and
executed. 1

© 2012 SAP AG. All rights reserved. RKT 12

Launch From MSS Role

 The web dynpro

ABAP form can
be launched
from
MSS.(starting
with MSS
1
ADDON 1.0)

© 2012 SAP AG. All rights reserved. RKT 13

Service Layer : What it is and how Does This Help?

 “HCM Processes and Forms” also opens up its framework via “service layer”.
 The “service layer” can be used if customer wants to consume “HCM Processes
and Forms” backend but a non SAP technology for the user interface.
 You can use all the functions including “check data” , “save”, “save draft”,
“forward to expert” etc. on the form
 You can also use attachments , link lists and history features.
 You can also launch workitems with the help of service layer.

© 2012 SAP AG. All rights reserved. RKT 14

Configure the Design Time for Additional User Interface
Configure the Web Dynpro ABAP Based Process(1)
Form Type 1
New option in create form
scenario where customer can
select the type of form.
1
Type Of Forms 2
2 Adobe Form – Existing option
to create form based upon
Adobe Interactive Forms
FPM Form – New option to
create form based upon FPM
Web Dynpro ABAP

© 2012 SAP AG. All rights reserved. RKT 15

Configure the Design Time for Additional User Interface
Configure the Web Dynpro ABAP Based Process(2)

Form Type 1
Customer can change the form scenario Form type from ” Change Form Scenario”
screen. Change of form type is only allowed if the form scenario is not used in any
process.

© 2012 SAP AG. All rights reserved. RKT 16

Configure the Design Time for Additional User Interface
Configure the Form for the Process(1)

Form 1
New tool for creating web dynpro ABAP forms. Here customer can create different
types of configurations which is explained in later slides.

© 2012 SAP AG. All rights reserved. RKT 17

 Configure the Design Time for additional user interface
Configure the Form for the Process(2)
2
3 Configuration Type
1
Customer can choose from
1 following configuration type to
design the layout.
Form – This configuration is use
to create form like layout
List – List configuration is use to
create table like layout
List Complex – Visually it appears
Buttons to manage configurations 2 like list but this is used to design
These buttons are use to create, change or display table in case of repeat field and
configurations. On click of the button user will Time Constraint 3 scenarios.
navigate to FPM configuration editor.
Composite – Composite
Reorder configurations 3 configuration is collection of
configuration. Customer can
Customer can use this button to reorder the
include up to three configuration
configurations as while rendering the ui configuration
of any type.
will© appear
2012 SAP AG. Allin same
rights reserved. order RKT 18
Configure the Design Time for Additional User Interface
Configure the Form for the Process(3)
Field Attribute 1
Customer can set the field
attribute for the fields of form
scenario. These attributes
1
will be taken care
automatically while designing
the form layout.

© 2012 SAP AG. All rights reserved. RKT 19

 Configure the Design Time for Additional User Interface
Configure the Form for the Process(4)

Create Configuration 1
This button can be use to create configuration. In first column user has to choose the
type of configuration which she would like to create. User can select the
configuration which she would like to create. On click of the button FPM
configuration will be launched to design the layout.

© 2012 SAP AG. All rights reserved. RKT 20

Configure the Design Time for Additional User Interface
Configure the Form for the Process(5)
Fields Repositories 1
4
All fields including some additional
fields from form scenario is
1 available automatically for design
Form Design 2
2 This area can be use to design the
layout. Customer can drag and
drop the fields. UI attribute set
while configuring form scenario is
taken automatically.
Attribute of field 3

3 Attribute of fields like display type,

position, label, tooltip etc can be
maintained
4
General Settings
Here layout type and other settings
© 2012 SAP AG. All rights reserved. RKT 21
can be done
 Configure the Design Time for Additional User Interface
Configure the Form for the Process(6)

1 Fields Repositories 1
All fields including some additional
fields from form scenario is
available automatically for design
2 List/Table Design 2
This area can be use to design the
layout. Customer can choose the
fields from repositories and add
these as column.

© 2012 SAP AG. All rights reserved. RKT 22

Configure the Design Time for Additional User Interface
Configure the Form for the Process(7)

Actions 1
1
Some actions like Add Row,
Delete Row, Check and Initialize is
available as standard actions for
list type

© 2012 SAP AG. All rights reserved. RKT 23

Configure the Design Time for Additional User Interface
Configure the Form for the Process(7)

Web Dynpro ABAP Value Help1

Customer can create their own value help when required. This
web dynpro component has to implement IWD_VALUE_HELP and
IF_FPM_GUIBB_VH

© 2012 SAP AG. All rights reserved. RKT 24

Copy a Form Scenario or a Process

Form Type selection in “Copy

Form Scenario” screen 1
New option is provided to
select form type while copying
form scenario. Customer can
change the form type in this
1 screen.

Form Type selection in “Copy

Process with Dependent
Objects” screen 2
2 Customer can select new
form type for copied form
scenario.

© 2012 SAP AG. All rights reserved. RKT 25

 POWL Inbox Customizing for MSS Role to Launch New
HCM P&F Application for Workitem(1)
1 Defining an action for the inbox:
Maintain view IBO_V_WF_ACC
1 to
create a new action as shown
below:
2 Application:
MANAGER_MSS_INBOX/MANAG
ER_MSS_INBOX_2
Action: EXECUTETASK
Action Type:
OBJECTNAVIGATIONLAUNCHER
Associating an action with an OBN target (Action properties): 2
For the workitem to be launched from the POWL inbox via OBN, action properties must
be maintained in the system. Maintain the action properties in the view
IBO_V_WF_APS.
The following properties must be maintained for the action EXECUTETASK:
Property Name Property Value
OBJECTNAME MSS_WL
OBJECTVALUE WI_ID=${ITEM.EXTERNALID}
OPERATION
© 2012 SAP AG. All rights reserved. NAVIGATE_FORM_WD RKT 26
 POWL Inbox Customizing for MSS Role to Launch New
HCM P&F Application for Workitem(2)
Associating workflow task
types with actions
1 1
Maintain view
IBO_V_WF_TTAC to assign
actions for task types:

For each workflow task

maintain the action to be
2 executed for the application.

PFCG changes to the role

2
In PFCG edit the role menu and add a new application node as shown below
Node Type : WD ABAP Application
Application Name : ASR_PROCESS_EXECUTE_OVP
Application configuration : ASR_PROCESS_EXECUTE_OVP_CFG.
Visibility : Invisible
© 2012 SAP AG. All rights reserved. RKT 27
POWL Inbox Customizing for MSS Role to Launch New
HCM P&F Application for Workitem(3)
This new node must
implement the method
NAVIGATE_FORM_WD of
the business object
MSS_WL . 1
Pass the following OBN
1 parameters:

WI_ID :{WI_ID}
Portal_bo_alias :
SAP_ERP_HumanResour
ces

© 2012 SAP AG. All rights reserved. RKT 28

Assignment of a Process to the Manager Self Service Role

Open Launchpad Customizing using the transaction LPD_CUST.

To add the process to the employee context menu in the MSS, select the following launchpad and click
Change:
Role – MSS
Instance – EMPLOYEE_MENU
Description – Employee Navigation Menu
Create a new application by entering the following details:
Application Type – Web Dynpro ABAP
Name Space – sap
Application – ASR_PROCESS_EXECUTE_OVP
System Alias – SAP_ECC_HumanResources
Click Show Advanced Parameters and enter the following details:
In Target App. Parameters, in addition to the parameters that are already there, enter the parameters as
shown below:
To pass the process enter the following parameters:
PERNR_MEM_ID
&SUBST_CLASSIFICATION=NO_CLASS&PROCESS=<Process_Name>&INITIATOR_ROLE=HRASRB
To pass the process group enter the following parameters:
PERNR_MEM_ID
&SUBST_CLASSIFICATION=NO_CLASS&PROCESS_GROUP=<Proc_Group>&INITIATOR_ROLE=HR
ASRB
Configuration – ASR_PROCESS_EXECUTE_OVP_CFG
Save the configuration.
© 2012 SAP AG. All rights reserved. RKT 29
Assignment of a Process to the Employee Self Service
Role
Assignment of Process to the ESS Scenario
Run transaction PFCG.
Select the single role for employee SAP_EMPLOYEE_XX_ESS_WDA_3 and edit it.
On the Menu tab, under the appropriate node insert the new HCM Process as a Web
Dynpro application.
Enter the following details for the application:
Web Dynpro Application – ASR_PROCESS_EXECUTE_OVP
Description – <Process_Description>
Application Configuration – ASR_PROCESS_EXECUTE_OVP_CFG
In the Parameters table, enter the following in Name and Value:
PROCESS – <Process_Name>
INITIATOR_ROLE – HRASRD
Save the role menu.

© 2012 SAP AG. All rights reserved. RKT 30

Service Layer Details(1)

RFC Name: HRASR_PROCESS_EXECUTE

Functionality
This function module can be used to execute the HR processes created with the HCM
Processes and Forms (HCM P&F) Design Time Tool (DTT). Processes can be started
programmatically without the aid of the Webdynpro ABAP (WD ABAP) based start
applications. This function module can be invoked from custom applications.
The importing parameter IV_EVENT is very important and must always be passed.
The function module reacts based on the event passed and invokes the
corresponding HCM P&F backend operations to operate on the form data. The
different values for the parameter IV_EVENT are as follows:
INITIALIZE - Initialize form data. The field values returned from the infotype framework
will be passed back.
CHECK - Check form data.
SAVE_DRAFT - Save the form as a draft for processing later. The form data is
submitted to the backend.
SEND - Submit the form data to the HCM P&F backend.
APPROVE - Approve a workitem. The workitem is submitted to the backend for further
processing based on the workflow.
REJECT - Reject a workitem. The workitem is submitted to the backend.
CONTINUE - reserved.
© 2012 SAP AG. All rights Submit the form inspite of errors. RKT 31
Service Layer Details(2)

FORWARD_TO_EXPERT - Forward the form to an expert for further processing in

case of form errors.
DELETE_DRAFT - Delete a draft workitem
BACK_TO_USER - Send the workitem back to the user.
BACK_TO_AUTHOR - Send the workitem back to the initiator
WITHDRAW - Withdraw a process
ADD_ATTACHMENT - Add an attachment.
DELETE_ATTACHMENT - Delete an attachment which as already been attached.
GET_ATTACHMENT - Get the list of attachments for a particular workitem.
GET_LINK_LISTS - Get the list of link lists.
GET_HISTORY - Get the previous processors of the process's workitems

The typical sequence of events that must be passed to the function module during the
execution of a process is as follows:
1. INITIALIZE
2. CHECK
3. User events
4. SEND

© 2012 SAP AG. All rights reserved. RKT 32

Summary

You should now be able to

 Understand why an additional user interface is required.
 The positioning of the web dynpro ABAP based forms and the
Adobe forms.
 Features possible on the webdynpro ABAP forms.
 How to configure a web dynpro ABAP based form.
 How to use the „Design Time Tool“ to configure the form.
 How to Launch the Form form Employee and Manager role.

© 2012 SAP AG. All rights reserved. RKT 33

© 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,
without the express permission of SAP AG. The information contained herein may be Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,
changed without prior notice. Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are
trademarks or registered trademarks of Google Inc.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors. INTERMEC is a registered trademark of Intermec Technologies Corporation.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are Wi-Fi is a registered trademark of Wi-Fi Alliance.
registered trademarks of Microsoft Corporation.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP,
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. StreamWork, SAP HANA, and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of SAP AG in Germany
Linux is the registered trademark of Linus Torvalds in the United States and other countries. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
trademarks of Adobe Systems Incorporated in the United States and other countries. Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
Oracle and Java are registered trademarks of Oracle and its affiliates. mentioned herein as well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP company.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin products and services mentioned herein as well as their respective logos are trademarks or
are trademarks or registered trademarks of Citrix Systems Inc. registered trademarks of Sybase Inc. Sybase is an SAP company.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks
World Wide Web Consortium, Massachusetts Institute of Technology. of Crossgate AG in Germany and other countries. Crossgate is an SAP company.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, All other product and service names mentioned are the trademarks of their respective
Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
IOS is a registered trademark of Cisco Systems Inc.
The information in this document is proprietary to SAP. No part of this document may be
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry reproduced, copied, or transmitted in any form or for any purpose without the express prior
Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App written permission of SAP AG.
World are trademarks or registered trademarks of Research in Motion Limited.

© 2012 SAP AG. All rights reserved. RKT 34