SAP HCM PF Fiori Comprehensive Guide v3.1

CUSTOMER

SAP HCM Processes and Forms (P&F)

A comprehensive guide for configuring SAP P&F for Fiori
Version 3.1 | December 2023

Changes introduced in version 3.1
Section Title
3.5 New Mode in Process Inbox: genericEmbedIntoDetails
4.15.1 Enable functionality of setting default values of table fields on click of ADD
button through user event
4.18 Ability to perform Employee search with Position and Organization Unit
4.19 Display of additional Business Status column in Switch Process Step window
4.20 Ability to upload attachment directly through camera in mobile devices.
4.21 Enable hiding of Table toolbar buttons based on business rules
4.22 Enable Link control to the UI elements of the Fiori form
4.23 Ability to show value help description text instead of only key value
4.24 Enable functionality to show “Document Type” in the added attachments for UI
version 1.103 onwards.
5.4 Updated new methods for BAdi HCMFAB_ASR_B_PROCESS
6.9 Maintain Business Statuses corresponding to Processing Statuses
6.10 Process Configuration for Time Constraint 3 Infotypes
6.11 Metadata configuration for multiple tables
6.12 Ability to display error message during user event trigger
Navin P R and Team ( [email protected] )

Table of Contents
INTRODUCTION TO SAP HCM PROCESSES AND FORMS .................................................... 5
1. CONFIGURATION OF METADATA ..................................................................................... 5
1.1 Creating a Fiori Form........................................................................................................................... 6
1.2 Fields in the Fiori form ........................................................................................................................ 6
1.3 Business Example ................................................................................................................................ 7
1.4 Metadata Properties ........................................................................................................................... 9
1.5 Error Handling ................................................................................................................................... 13
1.6 Copying existing Form Scenario into Fiori form ................................................................................ 15
1.7 Workflow Configuration ................................................................................................................... 16
1.8 Copying existing Adobe or FPM workflow to Fiori workflow ..................................................... 16
1.9 Adaption of custom workflow and tasks .................................................................................... 21
2. START PROCESS APP..................................................................................................... 27
2.1 Gateway System Configuration......................................................................................................... 27
2.2 Backend System Configuration ........................................................................................................ 27
2.3 Integration between frontend and backend system for Fiori Apps.................................................. 29
2.4 Process Instances: Filters .................................................................................................................. 33
2.5 Configuration for custom role........................................................................................................... 39
2.6. Determining the HR Administrator for an Employee: ..................................................................... 42
2.7. Determining the Employees mapped to a HR Administrator: ......................................................... 42
2.8. Configuration to launch different type of processes for different initiator roles ............................ 42
2.9. Process Flow of Start Process App (PA & PT Process)...................................................................... 44
2.10. Process Flow of Start Process App (PD Process) ............................................................................ 46
2.11 Determining the Employees for a Manager.................................................................................... 48
3. CONFIGURATION OF PROCESS INBOX APP (INTEGRATION WITH MY INBOX APP) . 49
3.1 Disable Actions in My Inbox app ....................................................................................................... 49
3.2 Remove workitems in ‘Draft’ status from My Inbox ......................................................................... 50
3.3 Configuring P&F related custom tasks .............................................................................................. 52
3.4 Launching SAP HCM P&F processes from My Inbox ......................................................................... 53
3.5 New Mode in Process Inbox: genericEmbedIntoDetails ................................................................... 54
4. FEATURES IN START PROCESS AND PROCESS INBOX APP ......................................... 55
4.1. Download of form in PDF is possible from,...................................................................................... 55
4.2. Additional information links/URLs on the page header. ................................................................. 57
4.3. Display current Processor name in Start Process App. .................................................................... 58
SAP Note: 2673872 2|Page
4.4. Launch Fiori form for process instance with “In Process” status .................................................... 59
4.5 Display of additional status record in Start Process Fiori App .......................................................... 59
4.6 Ability to control Attachment Type visibility in a form ..................................................................... 60
4.7 Ability to Reserve and Release Work item from Process Inbox App ................................................ 62
4.8 Ability to Withdraw Process from Start Process Fiori App ............................................................... 62
4.9 Display Error Messages or Warning Message ................................................................................... 63
4.10 Ability to specify maximum file size of each attachment and total number of attachments ....... 64
4.11 Ability to mark mandatory fields .................................................................................................... 64
4.12 Ability to Hide/Unhide Tables and/or Forms based on User Event ................................................ 66
4.13 Continue button functionality for Start Process and Process Inbox App ....................................... 68
4.14 Process Browser .............................................................................................................................. 69
4.15 Ability to trigger user event on click of ADD button in Table. ........................................................ 77
4.15.1 Enable functionality of setting default values of table fields on click of ADD button through user
event. ...................................................................................................................................................... 81
4.16 Ability for substitute users to process workitems. ......................................................................... 82
4.17 Workflow template WS76600085: Save Form with Lock/Unlock Err Handling .............................. 83
4.18 Ability to perform Employee search with Position and Organization Unit ..................................... 84
4.19 Display of additional Business Status column in Switch Process Step window .............................. 85
4.20 Ability to upload attachment directly through camera in mobile devices. .................................... 86
4.21 Enable hiding of Table toolbar buttons based on business rules. .................................................. 87
4.22 Add HTML Link control as a form field to allow navigation to reference or mandatory links ........ 90
4.23 Ability to show value help description text instead of only key value. .......................................... 91
4.24 Enable functionality to show “Document Type” in the added attachments for UI version 1.103
onwards. ................................................................................................................................................. 92
5. REFERENCES ..................................................................................................................... 93
5.1. Prerequisite for configuration of Fiori Processes ............................................................................ 93
5.2. Business Function ............................................................................................................................ 93
5.3 Launching standalone Process without Start Process Fiori App ....................................................... 94
5.4. Extensibility Options for Backend: ................................................................................................... 95
5.5. Extension Hooks/Points for UI: ...................................................................................................... 102
5.5.1. Overview page extension hooks/points ..................................................................................... 102
5.5.2. Detail page extension hooks/points .......................................................................................... 103
5.5.3. Detail page : Extension hook/points for Dialog box................................................................... 104
5.5.4. Detail page: Extension hook/points for Form/Table labels ........................................................ 105

5.5.5. Detail page: Extension hook/point for Rich Text Editor ............................................................. 106
5.6. SAP Help Content ........................................................................................................................... 107
6. REFERENCE EXAMPLES .................................................................................................. 108
We are demonstrating example configurations to covers different business requirements............... 108
6.1. Implementation of dependent value help or F4 Help (in a popup format) .............................. 108
6.2. Implementation of dependent drop down (dropdown in a screen) ........................................ 111
6.3. User event to trigger the pre-population of a screen field. ...................................................... 114
6.4. Provision to display field description next to the input field in the form ................................. 116
6.5. Provision to show custom tooltip for all the fields ................................................................... 118
6.6. Control Type, FORMATTEDTEXT to display text with html tags ............................................... 119
6.7. Control Type, Timepicker for Time related Processes .............................................................. 120
6.8. Control Type, RICHTEXTEDITOR to maintain text with html tags ............................................. 121
6.9 Maintain Business Statuses corresponding to Processing Statuses. ........................................ 122
6.10 Process Configuration for Time Constraint 3 Infotypes ............................................................ 125
6.11 Metadata configuration for multiple tables: ............................................................................ 127
6.12 Ability to display error message during user event trigger. ..................................................... 130

Introduction to SAP HCM Processes and Forms

SAP HCM Processes and forms (SAP HCM P&F) solution provides a software which facilitate
execution of different human resource related business processes from start to finish.
SAP HCM P&F solution replaces the traditional paper forms and automates the movement of the
forms after approvals. This facilitates real time validation of data, supports integration with all
involved business roles saving the processing time for HR processes.
SAP has already provided options of Adobe interactive Forms & FPM based forms for UI.
To enrich the user experience, HCM P&F has been made available in Fiori which enables the end
user to access SAP HCM P&F on mobiles, tablets in addition to desktops.
PA (Personnel Administration), PD (Personnel Development) and PT (Personnel Time

Management) based Fiori processes are available. For further details, refer here.
We recommend customers to get acquainted with basic principles of HCM Processes and Forms
configuration. You may refer to documentation for base configuration of HCM Processes & Forms
@ HCM Processes & Forms.
1. Configuration of Metadata
The system provides flexibility to the customers, who have existing HCM P&F investments in the
form of mapped business processes and Adobe/FPM forms, to re-use the existing backend
configuration and generate Fiori UI at runtime. Customers who are new to HCM P&F have the
option to directly configure Fiori based forms.
The Design Time Tool (DTT) accessed from transaction code HRASR_DT can be used to copy
existing Adobe/FPM process with their related objects (e.g., workflow templates, form scenarios,
and backend services) and configure Fiori process.
HCM Process, backend service, rules and user events can be created from the beginning. If you
have already configured them for an earlier Adobe/ FPM process, you could reuse them for the
Fiori application configuration. In other words, Fiori forms might need to be created from the
beginning. But the existing workflows can be copied and adjusted using newly shipped Fiori
workflow tasks. For further details, refer to 1.7 Workflow Configuration

1.1 Creating a Fiori Form
DTT can be used to create Fiori form using Form Type “Fiori Form”.
1.2 Fields in the Fiori form
The node, ‘Field Metadata’ enables you to configure the metadata for the form fields. Configure
every field with the required properties (like field type, header title, section title etc), for rendering
it on the Fiori form.

1.3 Business Example
The following steps illustrates the end to end creation of Fiori Form Scenario
Navigate to Transaction: HRASR_DT
Steps:
a. Create a Form Scenario: select Form Type “Fiori Form” and click “Continue” button ( ).
b. Add the required infotype fields within the ‘Field’ node. For example, the following 4 fields
have been added:
• I0001_BEGDA
• I0001_BTRTL
• I0001_ENDDA
• I0001_WERKS
c. After adding the fields and saving the form, these fields are available as part of the Field
Metadata node.
In Field Metadata, you must specify the properties for each field.
These properties determine how the fields are rendered on the Fiori form.
d. Enter data for all the columns. For more information, refer to section Metadata
Properties.
e. Save the Form Scenario.

1.4 Metadata Properties
The following column values must be configured for the forms to be rendered in the UI:
Note: Do not change the pre-filled values (field container, control type) for rows
‘HRASR_CURRENT_NOTE’ and ‘HRASR_PREVIOUS_NOTES’.
Mandatory(M)/
Name of the field Value required
Optional(O)
Field Name All the fields under ‘Fields’ node will be displayed here. This is pre-filled
All the field names under ‘Fields’ node will be displayed This is pre-filled. If
here. needed, this can
Field Label
be changed from
“Fields” section in
DTT.
This can have any following values:
a. FORM – maintain this value if the corresponding field is
part of a form.
b. TABLE - maintain this value if the corresponding field is
Field Container part of a table.
M
c. COMMENTS - maintain this value if you are using
custom comments. Standard comments have already
been pre-filled – ‘HRASR_CURRENT_NOTE’ and
‘HRASR_PREVIOUS_NOTES’.
Enter an ID for the corresponding container here.

Field Container ID O
Enter the sequence (e.g.: 1, 2, 3, and so on) in which the
Field Container
containers are to be displayed in the UI. O
Sequence
Enter the container title here.
Container Title O
You can choose from any the following values:

a. STRING
Type Kind b. INTEGER O
c. DECIMAL

Mandatory(M)/
Optional(O)
You can choose from any the following values:
a. DROPDOWN
b. CHECKBOX
c. TEXT
d. INPUT
e. RADIO
f. COMMENT – to be used only if Field Container value
Control Type is ‘COMMENTS’ M
g. DATEPICKER
h. TEXTAREA
i. NONE
j. FORMATTEDTEXT
k. TIMEPICKER
l. RICH TEXT EDITOR
For an INPUT Control Type, enter the length of the field.

The Field Length specified can be used for input
Field Length validations.
O
Note: Rendering of the form is dynamic, field length
maintained does not change the visible output length.
For an INPUT Control Type, enter the precision of the

field.
E.g. if the input must allow a decimal number, the field
Field Precision precision specifies the maximum number of digits before O
and after the decimal.
10.234 as an input requires a Filed Precision of 5.
For an INPUT Control Type, enter the scale of the field.

Field Scale E.g. if input must allow a decimal number, the field scale
O
specifies the maximum number of decimals allowed
10.234 as an input requires a Field Scale of 3.
Enter the sequence (e.g.: 1, 2, 3 and so on) in which the
fields are to be displayed in the UI.
Field Sequence The dynamically rendered form considers the field
M
sequence to get the order in which the fields are to be
displayed
Group Name Group Name corresponds to a Section title in the UI. A

M
group of fields can be viewed under one section.
Enter an ID for the corresponding group here.
Group ID M
Enter the sequence (e.g.: 1, 2, 3 and so on) in which the

groups are to be displayed in the UI.
The dynamically rendered form considers the Group
Group Sequence M
sequence to get the order in which the Groups are to be
displayed
This field needs to be “Ticked” / “Checked” if the field has

a dependent value help.
Has Value Help O
SAP Note: 2673872 10 | P a g e

Mandatory(M)/
Optional(O)
Enter any user events here.
Operation O
It is possible to configure two fields linked to each other

displayed on same row. It is recommended to link TEXT
field with INPUT field.
Field description O
For e.g., You want to show currency along with amount.
(Refer business example in part 6 of config Guide)
The drop-down also known as value help or F4 help is

commonly used in several HCM processes and forms. In
many cases there might be a need for dependent value
helps as well.
For example, a user action to select from a "Country"
dropdown followed by user action to select from a
F4 Parent Field O
"Region" dropdown (which is dependent on the Country
dropdown).
While configuring the field “Region”,

the F4 Parent Field needs to contain “Country”.
By default, label text maintained for field is shown as

tooltip. Custom tooltip can be configured in Field metadata
Tooltip for each field. (Refer example maintained in Examples O
document)
The following example scenarios would explain metadata configuration to achieve some of the
common business requirements. And illustrates that it is easy to generate the Fiori form in a
simple way without any coding efforts for UI.
Example:
a. Implementation of a complex UI which contains infotype fields (Address for example)
with separate Groups called Permanent Address, Temporary Address along with Notes
and multiple attachments.
b. The configuration needed in DTT to achieve this
SAP Note: 2673872 11 | P a g e

a. Required UI
SAP Note: 2673872 12 | P a g e

b. Field Metadata configuration for the above required UI in DTT (Design time tool)
As mentioned above, Address Details and Notes are the Group names and Permanent Address
and Temporary Address are the “Container Titles”. One group can have multiple containers and
the sequence of the containers can be defined in “Field Container Sequence”.
1.5 Error Handling
Use the Check option to verify the metadata configuration.
Mainly two kinds of errors are shown by the check.

a. Errors generated due to missing mandatory values.
SAP Note: 2673872 13 | P a g e

b. Errors generated due to changes in values for rows ‘HRASR_CURRENT_NOTE’ and

‘HRASR_PREVIOUS_NOTES’.
These errors come when rows ‘HRASR_CURRENT_NOTE’ and ‘HRASR_PREVIOUS_NOTES’

in Metadata configuration are manually modified.
Revert the values in these rows as shown below:
SAP recommendation: Do not change the pre-filled values (field container, control type) for rows
‘HRASR_CURRENT_NOTE’ and ‘HRASR_PREVIOUS_NOTES’. Rest of the columns like
Group name, Field sequence can be changed.
SAP Note: 2673872 14 | P a g e

1.6 Copying existing Form Scenario into Fiori form
Copy an existing Form Scenario (Adobe form/FPM form) to Fiori form type using the ‘Copy with
Dependent Objects’.
Copy with Dependent Objects helps you to copy all the configured fields and their properties.
Metadata node configuration are to be done after using either of the “Copy” options in order to
render the form in Fiori UI.
Note: After copying a form from adobe/FPM to Fiori using ‘Copy with Dependent Objects’
functionality, fields which are required by other fields or are to be processed in next steps, should
be added in ‘Field Metadata’ tab even if those fields are not shown on UI.
For example: Some fields, which are not shown on UI, have default values configured in previous
Adobe/FPM form and are source of data for other fields. In such case, those fields should also be
added to ‘Field Metadata’ tab with no field container or control type assigned. This is done so that
SAP Note: 2673872 15 | P a g e

field metadata can be passed between frontend and backend in every step processing. Field
Metadata correctly configures default values or UI attributes for any field.
1.7 Workflow Configuration
The following workflows and workflow tasks have been delivered for Fiori based P&F
configuration
Workflow ID Description
WS13600359 Workflow for PA error handling - Fiori
WS13600356 Draft for Process Start-Fiori
WS13600357 Workflow for Forward to expert
Workflow Tasks Description

13600231 Process Form-Fiori
13600232 Approve Form-Fiori
13600233 Draft for Process Start-Fiori

13600234 Forward Because of Errors-Fiori
13600235 Check Form Data – Fiori

13600236 Save Form Data Fiori
13600237 Form Edited Again by Author-Fiori
13600238 Process PD Form-Fiori
13600239 Approve PD Form-Fiori

13600240 PD Form Edited Again Author-Fiori
13600241 Draft for PD Process Start-Fiori
1.8 Copying existing Adobe or FPM workflow to Fiori workflow
1. Open the workflow you want to copy using transaction code SWDD
2.To copy the workflow, click on More >> Workflow>> Save As and modify the new workflow.
For instance, let us consider ‘Special Payment’ WS61000073 Workflow
(i) Open the workflow using SWDD transaction code.
SAP Note: 2673872 16 | P a g e

(ii) Copy the workflow, click on More >> Workflow>> Save As, as shown in the screenshot
below.
Enter required workflow name and abbreviation.
SAP Note: 2673872 17 | P a g e

(iii) The copied workflow will be opened.

Replace all Adobe or FPM workflow task IDs with the equivalent fiori workflow task IDs referring
to section 1.7.
For example, fiori task equivalent to FPM ‘Process form’ task TS17900100 is TS13600231 and
is replaced as follows:
SAP Note: 2673872 18 | P a g e

(iv) Once workflow task is changed binding will be reset.

Maintain the binding for each task.
SAP Note: 2673872 19 | P a g e

(v) Maintain form scenario and form:

Form scenario and form can be maintained via Workflow container:
Click on workflow container,
Click on form_standard,
Maintain form scenario and form scenario version as shown in the screenshot below.
SAP Note: 2673872 20 | P a g e

(vi) For subsequent workflow tasks continue to replace with equivalent fiori workflow task ID.
For example, ‘Approve Form’ task ID is replaced with ‘Approve Form’ Fiori task ID TS13600232.
(vii) Similarly, continue until all the workflow task IDs are replaced to fiori equivalent task ID by
referring to section 1.7.
(viii) Save the workflow and activate it.
1.9 Adaption of custom workflow and tasks
If you have custom workflow which needs to be adapted to fiori process and forms workflow
following are the points to be noted.
Workflow task that have to be used in Fiori Process and forms, need to have a program exit
class and version INdependent configuration.
Workflow specific configuration:
(i) Version-INdependent configuration:
Maintain Process Object for workflow in start events,
Click on Basic Data
Click on Version-INdependent (Task) >> Start Events.

SAP Note: 2673872 21 | P a g e
Maintain binding so that you can use the data from the event in the workflow.
(ii) Version-Dependent Configuration:

Maintain Program Exit class.
Click on Version-Dependent >> Program Exits and add the program exit class as
shown in the screenshot below.
Workflow task specific configuration:
SAP Note: 2673872 22 | P a g e

(iii) Maintain Program exits for interactive step:

Click on any interactive step >> Program Exits and add the class.
For example, in the screenshot below for Step – Process Form, program exits Class
– CL_HRASR00_POBJ_WF_EXIT is maintained.
(iv) Maintain agent determination rules:

Agent determination rules specify how the system determines the agents
(processors) of each interactive workflow step at runtime.
Following are various agent types available:
SAP Note: 2673872 23 | P a g e

Following are various standard agent determination rules available for HCM Processes and
Forms and can be used based on requirement:
Identifier Name Function Module Description
17900012 ASRAgent HR_ASR_AGENTFINDER Agent determination with

authorization check
17900013 ASROrgObject HR_ASR_ORGANIZATIONAL_OBJECT Employees belonging to a

specified organizational object
type.
This rule delivers all users (object
type US ) that are assigned to an
object type from SAP
Organizational Management . The
rule processes all object types that
are used for agent determination
within the framework of the
workflow.
SAP Organizational
Management is used to determine
the users.
17900014 ASRManager HR_ASR_MANAGER Manager

This rule delivers the manager for
a person. The rule processes the
object types P (Person). S
(Position), O (Organizational Unit),
C (Job), and US (User).
SAP Organizational
the users.
17900015 ASRGrpAdmin HR_ASR_GROUP_ADMINS Administrator Group

This rule delivers the users (object
type US) for the administrator
group of the relevant person. The
rule processes the object types P
(Person) and US (User).
SAP Personnel
Administration objects are used to
determine the users.
SAP Note: 2673872 24 | P a g e

17900016 ASRPersAdmin HR_ASR_PERSONNEL_ADMIN Personnel Administrator

This rule delivers the user (object
type US) for the personnel
administrator of the relevant
person. The rule processes the
object types P (Person) and US
(User).
SAP Personnel
17900017 ASRTimeAdmin HR_ASR_TIME_ADMIN Time Recording Administrator

type US) for the time recording
(User).
SAP Personnel
17900018 ASRPayrAdmin HR_ASR_PAYROLL_ADMIN Payroll Administrator

type US) for the payroll
(User).
SAP Personnel
04000007 ASR_PD_Admin Responsibilities PD Administrator

The processes are determined
using the areas of responsibility.
The container element
PROCESS_GROUP is available
for this.
SAP Note: 2673872 25 | P a g e

SAP Organizational
the users.
In addition to standard rules, you can create custom rules to determine the next agent.
SAP Note: 2673872 26 | P a g e

2. Start Process App

A preconfigured SAP HCM P&F process can be initiated using Start Process app. A process can
be triggered by employee or manager or HR Administrator or any custom roles. This app can be
launched from SAP Fiori Launch pad and is available under ‘Employee Catalog’. The next section
describes how to configure the Start Process app.
2.1 Gateway System Configuration
1. PFCG role SAP_HCMFAB_BCR_EMPLOYEE_T needs to be assigned to the end user.

This would provide access to the Start Process app.
2. Go to Fiori Launch pad, edit the home page, add the start ‘Start Process Tile’ from the
employee catalog.
Current Info for the standard tile is as follows:
Semantic Object: Employee; Action: initiateProcess
3. Use IMG node “Access and Maintain Services” or use transaction: /n/iwfnd/maint_services –
to add and maintain the newly delivered service HCMFAB_START_PROCESS_SRV.
2.2 Backend System Configuration
Go to transaction SU01 and add the parameter id: PNF_FIOROLE_PROCGRP with any one of
the following possible values mentioned below.
In the parameter values, the initiator roles are separated by the delimiter symbol ‘#’. The process
groups are separated by the delimiter symbol ‘+’.
Parameter Value What it means

Here, the following initiator roles are added:
HRASRD - Employee
HRASRB - Manager
HRASRA - HR Administrator
o For a user with Employee role (HRASRD) alone,

only “My Processes” will be displayed in Add
Process menu.
o For a user with both Employee role (HRASRD)
HRASRA#HRASRB#HRASRD and Manager role (HRASRB), “My Processes”
and “My Team Processes” will be displayed in
Add Process menu.
o For a user who has all three roles, that is,
Employee role (HRASRD), Manager role
(HRASRB) and HR Administrator role
(HRASRA), “My Processes”, “My Team
Processes” and “HR Admin Processes” will be
displayed in Add Process menu.
For a user with role HRASRB+HIRE, all the
processes belonging to the process group HIRE for
HRASRB+HIRE
Manager role (HRASRB) will be displayed in “My
Team Processes”.
SAP Note: 2673872 27 | P a g e

Parameter Value What it means

For a user with role HRASR+HIRE, all the
processes maintained for the process group HIRE
HRASRA+HIRE for HR Administrator role (HRASRA) will be
displayed in “HR Admin Processes”.
• The processes maintained for the process group

HIRE for HR Administrator role (HRASRA) will be
displayed in “HR Admin Processes”.
• The processes maintained for a custom process
HRASRA+HIRE#HRASRB+ZMGR#HRASRD group ZMGR for HR Manager role (HRASRB) will
be displayed in “My Team Processes”.
• The processes for employee role (HRASRD) will
be displayed in “My Processes”.
At least one process should be assigned to a role, to get the menu options (My Processes, My
Team Processes, HR Admin Processes) under the ‘Add Process’ button.
Processes can be assigned to respective role using view ‘V_T5ASRPROCGRVAL’ as shown in
the screenshot below.
SAP Note: 2673872 28 | P a g e

The following screen illustrates the output for a user who has all the above-mentioned initiator
roles
2.3 Integration between frontend and backend system for Fiori Apps
Creating an RFC connection in Gateway System

Step 1: Open Transaction SM59: Enter transaction code "SM59" in the SAP command field and
press Enter.
Step 2 In the SM59 transaction screen, click the "Create" button to create a new RFC
destination.
Step 3:
• Specify RFC Destination Parameters: A dialog box will appear where you need to
provide the necessary information for the RFC destination:
• RFC Destination: Enter a unique name for your RFC destination. This is the name you
will use to refer to the destination in your programs.
• Connection Type: Select the appropriate connection type. Usually, it's "3 - Connection to
an External Server" for remote connections.
• Target Host: Enter the hostname or IP address of the target system you want to connect
to.
SAP Note: 2673872 29 | P a g e

Logon & Security:

• Language: Set the logon language for the target system.
• User: Enter the username for authentication on the target system.
• Password: Provide the password for the specified user.
• Client: Enter the client number of the target system.
• SNC Name: If Secure Network Communication (SNC) is enabled, enter the SNC name.
• SNC Partner Name: If SNC is enabled, enter the SNC partner name.
SAP Note: 2673872 30 | P a g e

• Test Connection: Once you've filled in all the necessary information, you can click the
"Connection Test" button to check if the destination can be reached successfully.
• Save the RFC Destination: After the connection test is successful, click the "Save"
button (floppy disk icon) to save the newly created RFC destination.
Step 4: Create System Alias
• Create System Alias for the RFC destinations in view /IWFND/V_DFSYAL as shown
below with given Software versions.
• With software version “default” for HCMFAB_PROCESS_INBOX_SRV and

HCMFAB_START_PROCESS_SRV
• Software version /IWPGW/BWF for TASKPROCESSING service.
The "TASKPROCESSING" service refers to the OData service that is responsible for
handling tasks and workflows in the SAP system. It is part of the SAP Business
Workflow functionality and allows users to manage their work items, such as approvals,
notifications, and other task-related activities.
SAP Note: 2673872 31 | P a g e

Step 5: Create PFCG Role.

• Using transaction PFCG to create a new role.
• Enter a unique name for the role in the "Role" field. The role name typically starts with
the letter "Z" to indicate a custom role and click on the "Single role" button to create a
new single role. This will open the Profile Generator screen.
• Enter the description for the role and select the created RFC connection from the F4
help in Target System. Save the role.
• We can add some authorization objects from authorization tab, and assign this role
directly to users from user tab.
• The newly created PFCG role is now available and can be assigned to users as
needed.
• Using transaction Su01 attach this role to your user in frontend system.
Step 6: We need to maintain below services for our Fiori App in IWFND/MAINT_SERVICE
transaction of Frontend System.
• HCMFAB_START_PROCESS_SRV maintain system alias, for example:
QK8CLNT569_T
• HCMFAB_PROCESS_INBOX_SRV maintain system alias, for example:
QK8CLNT569_T
• TASKPROCESSING maintain system alias, for example: QK8CLNT569_T1
SAP Note: 2673872 32 | P a g e

2.4 Process Instances: Filters
You can make use of search filters in start process overview page; it lets you to refine
process list in seconds.
Search Criteria Returns

Name All process with the matching name
selected
Affected All process with the matching affected
person selected
Processor All process with the matching Processor
selected
Started on All process started on the date passed in
filter
Reference Number All process with the matching reference
number
Current Step Status All process with the matching Current Step
Status
Status All process with the matching Status
SAP Note: 2673872 33 | P a g e

Date Range All process started between the chosen

date range
For instance, search such as “Name – Birth of a Child(DE)“ and “Date Range – Mar 10, 2021 -
Apr 9, 2021” this displays all process with the name Birth of a Child(DE) started on between
March 10th 2021 and April 9th 2021
In addition, to these search criteria a new search criteria ‘Browser Context’ is available from
SP18 ( GBX01HR5 605 ) or note 2954692 and SP13 ( UIHR002 100 ) or note 2966204, refer
section 4.14 for more details.
Adapt Filters:
You can find all the available filters in ‘Adapt filters’ option and choose the filters to get the
overview you require.
SAP Note: 2673872 34 | P a g e

Sorting
Sorting makes it easy for you to get a quick overview of your process. If you have many
processes, you can choose to sort them by name, affected, processor, started on, reference
number, current step status, and status to get the overview you require.
To sort a list, you can click on ‘sort’ button in overview page, then choose sort by option and
choose Ascending or Descending.
SAP Note: 2673872 35 | P a g e

For example, below screenshot shows that how we can sort process list based on name in
ascending order.
Grouping
Grouping makes it easy for you to get a quick overview of your process. If you have many
processes, you can choose to group them by name, affected, processor, started on, reference
number, current step status, and status to get the overview you require.
SAP Note: 2673872 36 | P a g e

To group a list, you can click on ‘group’ button in overview page, then choose group by option
and choose Ascending or Descending.
For example, below screenshot shows that how we can group process list based on name in
ascending order.
SAP Note: 2673872 37 | P a g e

Personalize Column
You can also personalize what columns to be displayed in start process overview screen by
using ‘Personalize’ button.
SAP Note: 2673872 38 | P a g e

2.5 Configuration for custom role
If you want to configure roles beyond Employee, Manager or Admin, this is also possible.
*Available from UIHR002 100 SP 09 and GBX01HR5 605 13.
SAP Note: 2673872 39 | P a g e

Below screenshot shows that how other custom role processes would be visible for user.
a) Maintain custom role in SPRO (IMG Node)
SAP Note: 2673872 40 | P a g e

Maintain custom processor role, for e.g., Company Secretary
b) Configuration in DTT: Maintain initiator role with custom role, in this case ZHRASRA.
c) Maintain the user parameter, add the custom role via transaction SU01 for the required
user. In this case, ZHRASRA needs to be added as the parameter value.
SAP Note: 2673872 41 | P a g e

2.6. Determining the HR Administrator for an Employee:
We can determine the HR Administrator by any of these two options:

1. HR Administrator of the employee is determined based on IT 0001 – PersAdmin field
(SACHP).
2. You have an option to overwrite this logic by implementing BAdi
HCMFAB_ASR_B_PROCESS. You need to implement method
IF_HCMFAB_ASR_PROCESS_CONFG~ GET_ADMIN_PERNR of Class
CL_HCMFAB_ASR_IM_PROCESS_CONFG in your implementation.
If you maintain both options, then BAdi will take higher priority.
2.7. Determining the Employees mapped to a HR Administrator:
We can determine the employees mapped to a HR Administrator by any of these two

options:
1. Employees mapped to the HR Administrator are determined by checking view T526.
2. You need to implement method IF_HCMFAB_ASR_PROCESS_CONFG~
GET_ADMIN_EMPLOYEES of Class CL_HCMFAB_ASR_IM_PROCESS_CONFG in
your implementation.
If you maintain both options, then BAdi will take higher priority.
2.8. Configuration to launch different type of processes for different initiator roles
Business Case Output
Launch of processes as an
employee
Required parameter: HRASRD
Business Case Output
SAP Note: 2673872 42 | P a g e

Launch Processes as a HR
Administrator with start object
Required parameter: HRASRA
Launch Processes as a HR
Administrator without start
object
Required parameter:
HRASRA+ZGROUP
HIRE process is part of

Process group ZGROUP.
Launch Process as a HR
Manager
Required parameter: HRASRB
SAP Note: 2673872 43 | P a g e

2.9. Process Flow of Start Process App (PA & PT Process)
1. On clicking “Add Process” button, based on the initiator roles, the user gets to select three
process types: My Processes / My Team Processes / HR Admin Processes.
User gets to see and initiate Employee specific processes on clicking “My Processes”.
For example: All processes like Change of Address, Maintain Availability, Change of Family
details can be initiated.
User gets to see and initiate Manager specific processes on clicking “My Team Processes”.
For example: Manager could initiate processes on behalf of an employee or decide to initiate any
process for the required team member.
User gets to see and initiate Administrator specific processes on clicking “HR Admin Processes”.
SAP Note: 2673872 44 | P a g e

2. The user chooses a process to open the Search Help to do the following:
Find an employee, chooses an employee for whom the selected process must be initiated:
For example, the user chooses the employee Mr. Will Smith.
3. User fills in the details and clicks on “Send”. In case the user is unsure about some entry,
then could use the “Save Draft” option to save the work done.
SAP Note: 2673872 45 | P a g e

The process is saved, and the latest process instance list can be viewed in the Start Process
app.
User can also use the filters available on this page, to filter the results in the process instances
table. For e.g., We can filter on the Name of the Process, Status, Affected etc.
2.10. Process Flow of Start Process App (PD Process)
On clicking “Add Process” button, based on the initiator roles, the user gets to select process.
PD processes can be configured for Object types: Organizational Unit, Position, Job.
In below example, HR Administrator can see the list of configured PA & PD processes. User
selects “Delete Position” process.
SAP Note: 2673872 46 | P a g e

1. User enters the required search strings like Object ID, Object Abbreviation, Object Name
and clicks on “Go”
User selects from the search output the desired position to be deleted.
For example, the position Plantest1 has been selected above.
2. User fills in the details, like “effective date” and clicks on “Send”.
Note: Steps used for Form creation & Metadata configuration for PA, PT & PD processes are
same.
SAP Note: 2673872 47 | P a g e

2.11 Determining the Employees for a Manager
A012 relationship defines the manager who is managing organization unit.

By default, all the positions which are part of organization unit are considered to be reporting to
the manager with A012 relationship.
Let us, say you have the requirement to determine all the employees reporting to a manager
using A002 relationship (Manager is not necessarily head of the same organization unit as
employee).
To get this behaviour, you need to implement method GET_DIRECT_REPORTS of BAdi

Definition HCMFAB_B_COMMON in your implementation. (Enhancement spot
HCMFAB_COMMON).
SAP Note: 2673872 48 | P a g e

3. Configuration of Process Inbox app (integration with My Inbox app)

A new Fiori app namely Process Inbox app has been released which enables managers / HR
Admins to approve/reject/perform other actions, on the workitems that have arrived in the Inbox.
Since “Process Inbox” application is integrated within My Inbox app, the workitems related to
P&F are also shown in My Inbox and can be processed further.
Customers need to follow the below steps to utilize Process inbox app.
End user roles assignment required for My Inbox: SAP_FND_BCR_MANAGER_T
Target Mapping for INBOX App need to be maintained as shown below:
3.1 Disable Actions in My Inbox app
While configuring Fiori P&F, My Inbox app configuration might need to be changed because the
buttons like “Show Log”, “Claim”, “Forward”, and “Suspend” are not supported for P&F (These
buttons are visible by default in My Inbox app).
If these buttons are used in other apps, or if you like to continue to show these, then suitable
training needs be imparted to the end users to only use ‘Open Task’ button from My Inbox app
for P&F workitems.
SAP Note: 2673872 49 | P a g e

To disable the above-mentioned buttons, in the footer section of My Inbox app, implement the
BAdI WF_TASK_SUPPORT. To know more information, see SAP Note 2321144.
3.2 Remove workitems in ‘Draft’ status from My Inbox
Start Process app is used to initiate a process. When a user is unsure about some entries and
creates a “Draft”, SAP recommendation is to use Start Process app to continue editing all draft
workitems related to P&F until it is submitted. After the P&F is completed and once “Send” button
is clicked, its status changes to “in process”.
However, by default, My Inbox app also shows the Draft workitems created via the P&F Start
Process app, which must be hidden for better usability and functional correctness. Below steps
can be performed to hide all P&F draft workitems from My Inbox app.
• Navigate to SPRO and follow the path: SPRO-> SAP Gateway Service Enablement->
Content-> Workflow Settings-> Enable Task Filter.
SAP Note: 2673872 50 | P a g e

• Activate the filter settings by executing Enable Task Filter.

• Execute Maintain Task Names and Decision Options.
• Specify all the workflows along with step ID for all the processes in the system which
should be visible in My Inbox. Add all the workflows except standard Save Draft
(WS13600356).
An example to add workflow and step ID is shown below.
Workflow ID Step ID Icon MIME Repository Path Step Description
WS90500003 0000000030 Approve Form
SAP Note: 2673872 51 | P a g e

3.3 Configuring P&F related custom tasks
When the user selects a P&F workitem from My Inbox app, it launches the Process Inbox app.
To enable the navigation from My Inbox to Process Inbox the following steps are required to be
performed and applicable only for custom P&F workflow tasks. No additional action is needed for
Standard workflow tasks since they are already delivered.
• Execute transaction SWFVISU.

• Choose the P&F custom Fiori task created and set the Visualization Type as Intent-
Based Navigation.
• For example, if TS13600232 is a P&F custom task, choose task TS13600232 and select
Visualization Parameter in the dialog structure on the left pane. Configure the parameters
as below:
Visualization Parameter Value for approval
SEMANTIC_OBJECT BusinessProcess
ACTION Manage
QUERY_PARAM00
QUERY_PARAM01
QUERY_PARAM09
This enables the mapping between a task with the TaskDefinitionID TS13600232 to an application
with the action ‘manage’ and semantic object ‘BusinessProcess’.
SAP Note: 2673872 52 | P a g e

3.4 Launching SAP HCM P&F processes from My Inbox
1. Open standard My Inbox app from Fiori Launchpad.
2. Select the required workitem title and click on Open Task on the detail page.
SAP Note: 2673872 53 | P a g e

3. Key in the required details and choose the necessary action to proceed.
Once the necessary action is performed, the workitem will be moved to the next step in the
workflow and cleared from My Inbox app.
3.5 New Mode in Process Inbox: genericEmbedIntoDetails
We have added a new mode - ‘genericEmbedIntoDetails’ in process inbox where the details of
the form will appear beside the workitem as shown below.
SAP Note: 2673872 54 | P a g e

Changes in this mode:

With this mode, the standard My Inbox App’s Claim and Release functionality will not be
available. Process Inbox has implemented inbuilt Claim and Release functionality.
A particular workitem is claimed when it is selected, and it's released when another workitem is
selected from the master page or when the app is closed.
For detailed information on the new mode or to apply new mode, please apply SAP note:
3288904 - Process Inbox (UI): Consolidated bug fixes and feature enhancements or upgrade to
SP 23 of UIHR002 100 component for frontend changes. For backend changes, please apply
SAP note: 3359002 - HCM Process and Forms: Workitem lock and release or upgrade to SP 28
of GBX01HR5 605 component.
Refer KBA 3397911 for further details in case any issue is faced in implementation of
‘genericEmbedIntoDetails’ mode.
4. Features in Start Process and Process Inbox App

4.1. Download of form in PDF is possible from,
I. Overview page of Start Process Fiori App

II. The detail page of Start Process & Process Inbox Fiori App.
Refer to SAP note 2894179 and 2894110 for more details.
A. Define PDF form

In Transaction HRASR_DT, configure “Print form”
B. Launch of PDF from Start Process & Process Inbox App

SAP Note: 2673872 55 | P a g e
Launch of PDF from Start Process App:
Note:
1. Personalize option: To hide/unhide column for Download PDF.
2. PDF will be shown for processes in progress. (With In Process & Draft Status)
Launch of PDF from Detail Page of Start Process & Process Inbox Fiori App:
C. Example of downloaded PDF form:

SAP Note: 2673872 56 | P a g e
4.2. Additional information links/URLs on the page header.
Links & URL can be configured to provide additional information to end users.
Refer to SAP note 2874669 & 2874496 for more details.
For e.g., below screenshot shows how an embedded URLs will look like.
DTT configuration:
Using transaction HRASR_DT, configure URLs in additional information section.
SAP Note: 2673872 57 | P a g e

4.3. Display current Processor name in Start Process App.
In Start Processes App, it is possible to view the current processor name for each process
with “In Process” status.
SAP Note: 2673872 58 | P a g e

4.4. Launch Fiori form for process instance with “In Process” status
Fiori form can be launched by the user to verify entered data for a Process with status “In
Process”.
Refer to SAP note 2894179 for more details.
Fiori Form will be launched in “read only” mode (as shown below), on click of a process
instance which is “In process”.
4.5 Display of additional status record in Start Process Fiori App
In Start Process App, it is possible to view forms belonging to process with status 'In Process',
'Completed' and 'Cancelled’.
Refer SAP Note 2909174 for more details.
SAP Note: 2673872 59 | P a g e

4.6 Ability to control Attachment Type visibility in a form
It is possible to control the visibility of attachment at runtime based on a user selected/entered

value.
For example, let us consider a business scenario where while creating special payment process
if the amount is more than 500 euros then an appreciation email from stake holders must be
attached, if the amount is less than or equal to 500 euros General Attachment would suffice.
If amount entered is less than 500 euros attachment type ‘Appreciation Mail’ is not displayed on
UI.
SAP Note: 2673872 60 | P a g e

Attachment type - 'Appreciation Mail' is visible only if the amount is greater than 500 euros.
Attachment types – General Attachment and Appreciation Mail are configured in process
configuration as shown in the below screenshot.
SAP Note: 2673872 61 | P a g e

The visibility of attachment types can be handled in the form by implementing BAdI method
HCMFAB_ASR_PROCESS-> SET_ATTACHMENT_TYPE_VISIBILITY.
Refer section 5.4 and SAP Note – 2909174 for more details.
4.7 Ability to Reserve and Release Work item from Process Inbox App
To prevent another user from accidentally changing a form while you are still editing, you need
to reserve workitem and release it once you make the changes. This can be used to prevent
overwriting problem when more than one user is trying to work on same workitem.
In Process Inbox app, you can reserve and release workitem using ‘claim’ and ‘release’ button.
In addition, reserve and release of workitem can be handled by implementing BAdI method
HCMFAB_ASR_PROCESS-> HANDLE_WORKITEM. This BAdi allows you to auto reserve the
workitem when user opens task and auto release workitem when user cancels.
For UI, new extension hook for Process Inbox is provided

Detail.controller.extHookHandleOnExitEvent
Refer section 5.4 for more details on BAdi Implementation or SAP Note 2909174.
Note: Ability to reserve and release work item from Process Inbox app is auto implemented for
new mode: ‘genericEmbedintodetails’ of Process Inbox app. Refer section 0 for more details on
new mode. Upgrade to SP 23 of UIHR001 100 & SP 28 of GBX01HR5 605 to implement new
mode.
4.8 Ability to Withdraw Process from Start Process Fiori App
Process initiator can always withdraw a process from Start Process Fiori App using ‘withdraw’
button.
By default, ‘Withdraw’ button is
a) available for Process Workflow task
b) not available for Approve task.
SAP Note: 2673872 62 | P a g e
To show the Withdraw Button in approval task

On any form, you can designate a Button control to be the 'Withdraw' Button. Such a button is
usually programmed to enable the user to quickly withdraw process without committing to any
action.
For example, let us consider 'Company Loan Process' an employee initiates the process and
sends to manager for approval. By default, withdraw button is not available since it is approval
task.
To enable withdraw button in this scenario implement BAdi HCMFAB_ASR_B_PROCESS with
method SET_FIO_BUTTONS. In SET_FIO_BUTTONS set visibility as 02 and enabled as X for
withdraw button.
For Process Workflow task, by default Withdraw button is available. If you don't want to show
withdraw button in Process Inbox app then change binding as ' '.
Refer section 5.4 for more details on BAdI Implementation or SAP Note 2909174.
4.9 Display Error Messages or Warning Message
In Start Process and Process Inbox app, when you click on send button the form will be
checked, and if you have errors or warning messages it will be displayed as shown in the
screenshot below.
SAP Note: 2673872 63 | P a g e

Refer SAP note 2909174 for more details.
4.10 Ability to specify maximum file size of each attachment and total number of
attachments
By default, maximum file size allowed is 5 MB and total number of attachments allowed is 5.
It is possible to specify maximum file size of each attachment and total number of attachments
allowed by implementing BAdI method HCMFAB_ASR_PROCESS-
>GET_ATTACHMENT_LIMITS .
Refer section 5.4 for more details on BAdI Implementation or SAP Note 2909174.
4.11 Ability to mark mandatory fields
When you enter data on forms or tables in Start Process App, certain fields are marked with a
red asterisk. The red asterisk means that the field must be filled to complete current process.
For example, on the ' Change of Address' form , the red asterisk appears in the 'Country Key'
field and in the 'City' field to indicate that it is a mandatory entry and you cannot send this form
unless the fields are filled.
SAP Note: 2673872 64 | P a g e

To mark any field with a red asterisk indicating mandatory field a user must set field attribute of
field as 'Required Entry' in Process Configuration as shown in the screenshot below.
SAP Note: 2673872 65 | P a g e

4.12 Ability to Hide/Unhide Tables and/or Forms based on User Event
In Process Inbox and Start process app, a user can set field attribute as Invisible for any fields
and following checks are performed.
1. If all the fields of any form or all the columns of any table within a section are set as
Invisible, then corresponding form or table is hidden.
For example, let us consider ‘Update Employee Details’ process it has 1 section – Personal
Details and 1 table as shown in the screenshot below.
If all the fields of address details table are set to Invisible for scenario step ‘Approve’ as shown
below, then entire address details table will be hidden for ‘Approve’ step.
SAP Note: 2673872 66 | P a g e

2. If all the forms or tables of any section are hidden, then corresponding section is hidden.
For example, let us consider ‘Update relationship’ process it contains 3 sections – Personal
Details, Address Details and Family Details as shown in the screenshot below.
If all the fields of address details are set to Invisible for scenario step ‘Approve’ as shown below,
then entire address details section will be hidden for ‘Approve’ step.
SAP Note: 2673872 67 | P a g e

4.13 Continue button functionality for Start Process and Process Inbox App
Let us consider an example where a user enters incomplete data and wants to send this form
with the errors to the next process step, in that case a User can use 'Continue' Button.
To enable 'Continue Button' in UI, set 'Send Variation' to ' Tolerate Error Messages' in Process
Configuration as shown in the screenshot below.
SAP Note: 2673872 68 | P a g e
This will allow User to send a form to next process steps even if it has errors. These errors will
need to be corrected in the later process step by the administrator or subsequent processor.
4.14 Process Browser
In start process fiori app, a new filter criterion is introduced called ‘Browser Context’. The
browser context allows you to list all processes based on predefined search criteria. This is
available from SP18 (GBX01HR5 605) or note 2954692 and SP13 ( UIHR002 100 ) or note
2966204.
SAP Note: 2673872 69 | P a g e

In general, we use the following browser contexts, which come under one of three roles:
Role Browser Context
• PA Processes Initiated by me as employee

HRASRD • PD Processes initiated by me as employee
• All Process initiated by me as employee
• PA Processes with my involvement

HRASRA • PD Processes with my involvement
• All Processes with my involvement
• PA Processes with me as manager

HRASRB • PD Processes with me as manager
• All Processes with me as manager
The system displays a list of process instances that match the search criteria. In the list you can
view the data for the relevant process – Name of the process, Affected, Start Date, Processor,
Reference number and Status. In addition, you can download form as PDF if download PDF
option is present.
SAP Note: 2673872 70 | P a g e

How to enable browser context?

You can enable browser context by setting value ‘X’ for ENABL_CTXT parameter in table
‘T5ASRSETTINGS’.
* Available in SAP Note EA-HRGXX - 3026239
Default Browser Context:

It is mandatory to maintain a default context for each role in view ‘HCMFAB_V_BRCNT_T’, this
context ID will be used while loading up of the form first time.
You need to maintain only one default context ID for each role, not maintaining default context
or maintaining more than one default context ID for a role will result in error.
SAP Note: 2673872 71 | P a g e
Note: Maintenance view ‘HCMFAB_V_BRCTXT’ is changed to ‘HCMFAB_V_BRCNT_T’.
Translation of Browser Context text:

Browser Context text can be translated based on user’s default language. This functionality is
available from SP 22 of GBX01HR5 component or implement SAP Note: 3149859 - Language
Table for browser context for FIORI application.
You need to maintain translation of selected browser context text by performing below steps:
SAP Note: 2673872 72 | P a g e

Maintain translation for any language as shown below:
SAP Note: 2673872 73 | P a g e

Creation of Custom Browser Context:

In addition, to standard browser context, you can create custom browser context using BAdI
HCMFAB_ASR_B_PROCESS-> FETCH_VALUES_FOR_CONTEXT.
You need to maintain Context ID and Context Name for Custom Browser context in view
‘HCMFAB_V_BRCNT_T’ as shown in the figure below.
SAP Note: 2673872 74 | P a g e

The logic for search criteria needs to be implemented in the BAdI

HCMFAB_ASR_B_PROCESS-> FETCH_VALUES_FOR_CONTEXT.
Refer section 5.4 for more details on BAdI Implementation.
Process Step Details:

Once you have opened a process from the search result, use the ‘Switch Process Step’ button
to display a list of all the previous process steps involved in that process. ‘Switch Process Step’
is available only when Browser Context is enabled.
SAP Note: 2673872 75 | P a g e

When you open a process step, it opens the associated form in the display mode. The form
contains all data and attachments that existed when the relevant process step was completed.
SAP Note: 2673872 76 | P a g e

4.15 Ability to trigger user event on click of ADD button in Table.
In Start Process and Process Inbox app, users can trigger user event on click of ADD button in
the header section of table. This user event can be used to set UI attributes of table fields based
on their requirement or assign default values to table fields when a new row is added.
The code to be executed on click of ADD button can be written in DO_OPERATIONS method of
Basic Generic Service: HRASR00GEN_SERVICE_BASIC.
The following steps need to be performed to link user event to ADD button.
Business case: To trigger user event on click of ADD button of Table.
Required configuration:
1. Define field TABLEADDBTN with type BOOLE_D. Please note that this field is case
sensitive.
SAP Note: 2673872 77 | P a g e

2. Maintain Field Metadata for the field.

Maintain field metadata as follows:
Field container: BUTTON
Group ID: Maintain Group ID of the table.
Operation: User event to be triggered on click of ADD button.
Ensure that User event is using fields(columns) of the same table.
3. Handling for multiple tables:

Incase multiple tables are configured for same form, maintain TABEADDBTN and its attributes
using code.
SAP Note: 2673872 78 | P a g e

A new method “UPDATE_TABLE_BUTTON” is introduced in interface

IF_HCMFAB_ASR_PROCESS_CONFG of BADI HCMFAB_ASR_B_PROCESS.
Multiple tables are configured within same Group: Specify same Group ID, same group
sequence and different field container ID to differentiate between two tables.
Multiple tables are configured in different Groups: Specify different Group ID and different
Group sequence. In this case, field container ID is optional.
You can add TABLEADDBTN in the field Metadata for other tables of the form by implementing
BADI method UPDATE_TABLE_BUTTON. Decision to specify button can be taken based on
form scenario, form scenario stage. In the metadata specify Field container, Group ID, Group
Sequence, Field container ID is optional.
Changing UI attributes of newly added row:

UI attribute can be set using generic service based on user event, field group, service operation
and form scenario stage.
SAP Note: 2673872 79 | P a g e

For existing rows, UI attribute can be set using generic service.

For newly added row, UI attributes can be set in ct_process_record for the selected columns.
Decision of specifying UI attribute can be taken based on form scenario, form scenario stage,
form scenario version and user event and record index for the selected column.
A new method “SET_TABLE_UI_ATTRIBUTE” is introduced in interface
IF_HCMFAB_ASR_PROCESS_CONFG of BADI HCMFAB_ASR_B_PROCESS.
To enable these features, kindly implement note: 3132691 - Fiori: Table button enhancements
or these changes are available in GBXHR5 component from SP 21.
SAP Note: 2673872 80 | P a g e

4.15.1 Enable functionality of setting default values of table fields on click of ADD
button through user event.
On click of ADD (+) button, user is now getting the flexibility to set default values of fields
appearing on table popup by triggering a user event. These default values for table fields can be
set by maintaining generic service.
Configure user event for ADD button in the process configuration by performing above
mentioned steps.
Add logic to set default values of table fields in the generic service. Implement INITIALIZE or
DO_OPERATIONS methods of your generic service. If you are maintaining Processing type as
"INITIALIZE" for user event configuration, then implement INITIALIZE method of generic service
and for processing type "CHECK" implement DO_OPERATIONS method.
Defaulting of field values for different form scenario and form scenario stage can be decided by
performing similar steps and writing code for user event for different form scenario and form
scenario stage.
For detailed information on setting up this functionality, refer attachment mentioned in note:
3358508.
SAP Note: 2673872 81 | P a g e
To enable this feature, kindly implement note: 3358508 - Start Process and Process Inbox Fiori
2.0 application (Backend): Consolidated feature enhancement or these changes are available in
GBX01HR5 605 component from SP 28.
4.16 Ability for substitute users to process workitems.
In your organization, structural authorization is configured dynamically based on user position.

User has maintained substitute for processing workitems for a specified time period.
Earlier, substitute user was launching workitem and was not able to see infotype data
maintained for the process due to lack of authorizations.
Apply note: 3341317 - Process and Forms: Substitution for process and missing infotype
authorization for GBX01HR5 component (or available from SP 27) and 3286793 - Process and
Forms: Substitution for process and missing infotype authorization for EA-HRGXX (or available
from SP 123 for 608) & S4HCMGXX (or available from SP 12) components, for handling
authorizations and functionalities by substitute users.
Implement BAdI method HCMFAB_ASR_PROCESS->HANDLE_SUBSTITUTION
In the standard delivered class CL_HCMFAB_ASR_IM_PROCESS_CONFG code is provided to
enable substitute user to perform action. You can uncomment the code to use it in your
implementation.
SAP Note: 2673872 82 | P a g e

4.17 Workflow template WS76600085: Save Form with Lock/Unlock Err Handling
Use
You can use this workflow template to have the data of a form automatically saved in the
infotypes in the backend system, without a human user initiating the save.
You can use the workflow template if you do not want to give the last person to process the form
data, the extensive authorizations required to save the data securely on the database. If error
messages arise in the backend system during automatic processing, you can have the data
processed by an authorized expert.
This workflow template comes with Lock/Unlock Error handling mechanism. The workflow tries
to lock/unlock a pernr before trying to save data to ensure availability of pernr as follows:
• Lock is performed over a pernr to check if the pernr is available for processing currently.
• If pernr is locked, unlock is performed to release the pernr and further processing is
continued.
• If pernr is not locked, workflow will wait and try to lock the pernr again until it is locked, or
maximum number of tries have been achieved.
• If maximum number of tries have been achieved, workflow executes further, thereby
throwing lock error on the pernr.
This workflow template is intended for use only within a surrounding workflow template as a
multistep task. You can use it without adjusting the standard version. If the standard version
does not meet your requirements, you can copy it and adjust the copy.
Workflow Template: WS76600085
Availability: Available from S4HCMGXX (SP 08) and EA-HRGXX (608 – SP 119, 607 – SP 142).
ID: SAVE_LOCK_WF
Name: Save Form with Lock/Unlock Err Handling
Standard Tasks Used
Standard Task TS17900107: Check Form Data
Standard Task TS04200011: Wait Step
Standard Task TS76600083: Lock Employee
Standard Task TS17900160: Forwarded Because of Errors
Standard Task TS17900108: Save Form Data
Standard Task TS17900110: Import Form Container to Workflow
Standard Task TS17900112: Instantiate BOR EMPLOYEET
Standard Task TS76600084: Unlock Employee
Standard Task TS17900106: Check Existence of PA Infotype
SAP Note: 2673872 83 | P a g e

New Standard tasks released:

Standard Task TS76600083: Lock Employee
You can use this standard task to lock an employee. The result of the check is available at
workflow level for further processing.
Standard task: 76600083
ID: LOCK_PERNR
Name: Lock Employee
Referenced Object Method, Properties:
Object Type: CL_HRASR00_WF_ERROR_HANDLING
Method: LOCK_PERNR
Standard Task TS76600084: Unlock Employee
You can use this standard task to unlock an employee. If an employee is not unlocked
successfully, then a true is returned from this task. The result of the check is available at
workflow level for further processing.
Standard task: 76600084
ID: UNLOCK_PERNR
Name: Unlock Employee
Referenced Object Method, Properties:
Object Type: CL_HRASR00_WF_ERROR_HANDLING
Method: UNLOCK_PERNR
New Standard Class released:
CL_HRASR00_WF_ERROR_HANDLING - Contains logic for locking/unlocking of an employee.
The rest of the functionality is similar to WORKFLOW TEMPLATE WS17900260: SAVE FORM
WITH ERROR HANDLING.
4.18 Ability to perform Employee search with Position and Organization Unit
The system has been enhanced to allow users to conduct searches and review search results
for employees based on the following fields: Employee name, Employee number, Position ID
and Organizational ID.
SAP Note: 2673872 84 | P a g e

The code logic has been updated to enable the search and display results for additional fields.
This update applies to the default implementation of BAdi HCMFAB_ASR_B_PROCESS for the
method IF_HCMFAB_ASR_PROCESS_CONFG~GET_ADMIN_EMPLOYEES.
If your system has a custom implementation of BAdi HCMFAB_ASR_B_PROCESS, you need
to modify the code of the method
IF_HCMFAB_ASR_PROCESS_CONFG~GET_ADMIN_EMPLOYEES. For guidance on how to
make these adjustments, please refer to the standard class
CL_HCMFAB_ASR_IM_PROCESS_CONFG.
To enable this feature, kindly implement note: 3358508 or upgrade to SP28 of GBX01HR5 605
component for backend changes. For frontend changes, implement note: 3369631 for Start
process and note: 3369797 for Process Inbox or upgrade to SP24 of UIHR002 100 component.
4.19 Display of additional Business Status column in Switch Process Step

window
The Switch Process Step window has been enhanced to display 'Business Status' data related
to processing statuses. This Business Status can be customized as per the user's preferences
and requirements (to set Business Status, refer section 6.9 Maintain Business Statuses
corresponding to Processing Statuses. )
SAP Note: 2673872 85 | P a g e

To enable this feature, kindly implement note: 3382077 or upgrade to SP 28 of GBX01HR5 605
component for backend changes and note: 3369631 for Start process or upgrade to SP24 of
UIHR002 100 component for frontend changes.
4.20 Ability to upload attachment directly through camera in mobile devices.
The user can upload any document/image directly through camera in a process as shown
below:
SAP Note: 2673872 86 | P a g e

4.21 Enable hiding of Table toolbar buttons based on business rules.
To enable handling of table buttons in the Start Process and Process Inbox Fiori App, the
following steps need to be performed:
i) Apply the code corrections and manual pre-implementation steps of SAP note 3358508 for
backend changes.
ii) Apply the code corrections and configuration steps of note 3386922 or relevant SP 28 of
GBX01HR5.
iii) Apply the code corrections of note 3369631 for Start Process and note 3369797 for Process
Inbox or upgrade to SP 24 of UIHR002 100 component for frontend changes.
These code corrections will enable:
• Hiding of Table toolbar ADD button based on business rules.

• Hiding of Edit or Delete buttons for Fiori table control dynamically based on business
rules.
Output: In below example:

- User is not allowed to ADD new address record.
- User is allowed to edit or delete Temporary residence Address but user is not allowed to edit
or delete Permanent Address.
Configuration steps to handle table button functionality:
• Open the transaction HRASR_DT and navigate to the Process section. Expand the
Fields section of the Form Scenario. Add the field "CUSTOM_TABLE" with the field label
"custom" and the type "boole_d".
SAP Note: 2673872 87 | P a g e

• In the Field Metadata section, set the field_container as "BUTTON".
• To handle the visibility of the Add button, you need to write an implementation for the
BAdi "HCMFAB_ASR_B_PROCESS" and implement the method
"IF_HCMFAB_ASR_PROCESS_CONFG~UPDATE_TABLE_BUTTON.
• To handle the visibility of the Edit, and Delete buttons of the table, you need to write an
implementation for the BAdi "HCMFAB_ASR_B_PROCESS" and implement the method
"IF_HCMFAB_ASR_PROCESS_CONFG~TABLE_BUTTON_HANDLING".
• This implementation will allow you to control the visibility based on the form_scenario,
form_scenario_stage, Group, and Field group level. If you will not write any
implementation then standard behaviour of ADD, EDIT and DELETE button will be
considered.
Sample code for handling table button visibility based on the form_scenario,
form_scenario_stage, Group, and Field group level is provided in commented form in
method IF_HCMFAB_ASR_PROCESS_CONFG~TABLE_BUTTON_HANDLING of
Class CL_HCMFAB_ASR_IM_PROCESS_CONFG.
SAP Note: 2673872 88 | P a g e

Please note that all tables of the form scenario can be either based on the "custom_table"
feature or as standard defined tables.
SAP Note: 2673872 89 | P a g e

4.22 Add HTML Link control as a form field to allow navigation to reference or
mandatory links
Links can now be attached to the UI elements/fields appearing on the Fiori forms.
Configuration steps to handle links:
• Open the transaction HRASR_DT and navigate to the Process section. Expand the Fields section
of the Form Scenario.
• Add a custom field to add the URL of the link – add the URL in the default value(manually) of the
field. If the link is mandatory in the form, select Required entry under the Field Attribute.
• Add a custom field to add the label of the link - add the label name in the default
value(manually) of the field. Select Invisible under the Field Attribute.
• Expand the Field Metadata section configure the custom field added for URL of link with the
new control type Link and maintain the rest of the fields based on the position of field in the
form.
• Configure the custom field for label of URL with the new control type Text and maintain the rest
of the fields.
SAP Note: 2673872 90 | P a g e

• Link the label field and the URL field of the link with field description (adding the label field for
URL field).
To enable this functionality, kindly implement note: 3386922 or upgrade to SP 28 of GBX01HR5

605 component and note: 3404455 for EA-HRGXX component (or upgrade to SP 128 for 608,
SP151 for 607, SP 17 for S4HCMGXX 100, SP 04 for S4HCMGXX 101) for backend changes.
Implement note: 3403689(Start Process) and 3403686(Process Inbox) or upgrade to SP 24 of
UIHR002 100 component for frontend changes.
4.23 Ability to show value help description text instead of only key value.
Earlier, on selecting any value from F4 help table, only key value was shown in corresponding field. Now,
the user is able to see description text of selected value instead of only key value.
For instance, Region field is having following F4 help:
SAP Note: 2673872 91 | P a g e

On selecting ’11 – Berlin’, description text (‘Berlin’) is shown in corresponding field:
To enable this functionality, kindly implement SAP note: 3382077 or upgrade to SP28 of GBX01HR5 605
component for backend changes. For frontend changes, implement note: 3369631 for Start process and
note: 3369797 for Process Inbox or upgrade to SP24 of UIHR002 100 component.
4.24 Enable functionality to show “Document Type” in the added attachments for
UI version 1.103 onwards.
A new control 'UploadSet' for handling attachments is introduced from SAP UI5 version 1.103 onwards
which lets you to show document type of the added attachment.
On versions lower than 1.103,
SAP Note: 2673872 92 | P a g e

1.103 onwards,
To enable this functionality, kindly implement note: 3369631 for Start process and note: 3369797 for
Process Inbox or upgrade to SP24 of UIHR002 100 component.
5. References
5.1. Prerequisite for configuration of Fiori Processes
We recommend customers to get acquainted with basic principles of HCM Processes and
Forms configuration. You may refer to documentation for base configuration of HCM Processes &
Forms at IMG Activity mentioned below.
Transaction SPRO -> IMG Activity ->Personnel Management -> HR Administrative services ->
Configuration of Forms/ Processes -> Design time for Processes and Forms.
5.2. Business Function
Activate business function HCM_ASR_CI_7 using transaction SFW5.
SAP Note: 2673872 93 | P a g e

5.3 Launching standalone Process without Start Process Fiori App
This could be achieved by either of the below:

Create URL for the process based on below template:
#Employee-initiateProcess&/ObjectId/<Process name>/RoleId/<Initiator role>
Eg1: For process BIRTH_OF_CHILD_10_FIO to be initiated by HR Administrator, the required

URL would be as shown below.
#Employee-initiateProcess&/ObjectId/BIRTH_OF_CHILD_10_FIO/RoleId/HRASRA
Eg2: For process BIRTH_OF_CHILD_10_FIO to be initiated by Manager, the required URL

would be as shown below.
#Employee-initiateProcess&/ObjectId/BIRTH_OF_CHILD_10_FIO/RoleId/HRASRB
Eg3: For process BIRTH_OF_CHILD_10_FIO to be initiated by Employee, the required URL

would be as shown below.
#Employee-initiateProcess&/ObjectId/BIRTH_OF_CHILD_10_FIO/RoleId/HRASRD
1) Create custom Fiori tile and embed URL.
SAP Note: 2673872 94 | P a g e

Maintain tile for process and role specific. Use semantic object navigation: Unchecked
Custom tile can be displayed in Launchpad as below;
2) Embed URL in your custom portal or SAP portal.
5.4. Extensibility Options for Backend:
The following BAdIs delivered to enhance SAP HCM Fiori P&F app and delivered with
software component GBX01HR5 605 SP 12 onwards.
BAdI: HCMFAB_B_START_PROCESS_ENRICH to enhance the OData services for the Start
Process Fiori app. The following methods are available in this BAdI:
• Method: ENRICH_PROCESSLIST – If you wish to have additional fields or filter some

fields showing up in the list of processes, this method can be used to get the desired
output. The modified list of processes is then available for the end user.
The entity ProcessList can be extended by this method.
Structure: HCMFAB_S_PROCESS_LIST
This structure would need to be enhanced to have additional or to filter fields coming up after
clicking “Add Process” button. The enhanced structure can then be consumed in method
ENRICH_PROCESSLIST.
SAP Note: 2673872 95 | P a g e

Impacted Screen Area:
• Method: ENRICH_FIELDVALUEHELP – If you are looking to enhance the value help

functionality, this method can be used to change any logic behind the standard offering.
The entity FieldValueHelp can be extended by this method.
Structure: HCMFAB_S_VALUEHELP
The structure HCMFAB_S_VALUEHELP can be enhanced and added fields can be
consumed in method ENRICH_FIELDVALUEHELP
For Example: In the above screen, a dependent F4 value help is taken in the Region field,
if the output screen that is shown needs enhancement, the above BAdI method and structure
are to be used.
• Method: ENRICH_DRAFTLIST – If you wish to enhance the list of processes displayed on

the overview screen of the Start Process app, this method is to be used.
For example, you can change the standard implementation where the statuses ‘Draft’,
‘Completed’ and ‘In Process’ that are shown and add columns in addition to the ones
shown in standard.
The entity DraftList can be extended by this method.
Structure: HCMFAB_S_DRAFT_LIST
Structure can be enhanced and added fields can be consumed in method
ENRICH_DRAFTLIST.
SAP Note: 2673872 96 | P a g e

• Method: ENRICH_DIRECT_REPORTS – If you have contingent workforce for instance

and want to change the logic enhance to get the list of direct reports, this method could be
used to do the same.
The entity DirectReports can be extended by this method.
Structure: HCMFAB_S_STARTPRC_DIRECTREPORT
This structure can be enhanced to add and consume fields in method
ENRICH_DIRECT_REPORTS to influence the list of direct reports.
BAdI: HCMFAB_B_PROCESS_INBOX_ENRICH
If you want to enhance the OData services for the Process inbox Fiori app the following
methods of the BAdI can be used.
• Method: ENRICH_FIELDVALUEHELP
If you are looking to enhance the value help functionality, this method can be used to
change any logic behind the standard offerring.
The entity FieldValueHelp can be extended by this method.
Structure: HCMFAB_S_VALUEHELP
The structure HCMFAB_S_VALUEHELP can be enhanced and added fields can be
consumed in method ENRICH_FIELDVALUEHELP
Impacted Screen Area: (in My Inbox)
SAP Note: 2673872 97 | P a g e

Note: The impact of method ENRICH_FIELDVALUEHELP of BAdI

HCMFAB_B_PROCESS_INBOX_ENRICH is very similar to the same method in BAdI
HCMFAB_B_START_PROCESS_ENRICH but it is used to change the output of My Inbox
application.
BAdI HCMFAB_ASR_B_PROCESS
This BAdI can be used to change the standard business logic for the following methods for the
Start Process Fiori App and Process Inbox Fiori App.
• CHANGE_PROCESS_ATTRIBUTES – Change Process attributes
This method is used to append process list for custom initiator role (role other than HR
Admin, Manager or Employee)
• GET_ADMIN_EMPLOYEES - Get PERNRS List falling under the current admin user
This method can be used to change default logic of finding pernr falling under a HR
Administrator.
• GET_ADMIN_PERNR–Get PERNR for the administrator
This method can be used to change default logic to determine pernr of HR Administrator for
any employee.
• SET_FIO_BUTTONS – To define custom button for user event.
Code snippet for reset values button:
SAP Note: 2673872 98 | P a g e

• SET_ATTACHMENT_TYPE_VISIBILITY
Let us consider a business scenario where while creating special payment process if the
amount is more than 500 euros then an appreciation email from stake holders must be
attached, if the amount is less than or equal to 500 euros General Attachment would
suffice.
If amount entered is less than 500 euros attachment type ‘Appreciation Mail’ is not
displayed on UI.
Visibility of any attachment type can be modified during user events.

Set the field Hidden = ‘X’ in order to hide any attachment type.
Refer section 4.6 for business case scenario.

• HANDLE_WORKITEM – To reserve or release work item, based on process event it
decides whether to reserve or release work item. Refer to code maintained in the method.
Refer section 4.7 for business case scenario.
• GET_ATTACHMENT_LIMITS – In Process and Forms, we have set file size as 5MB and
total number of attachments as 5. If you intend to change this to address your business
need refer to following code snippet where attachment size needs to be 10MB, attachments
needed are 6.
SAP Note: 2673872 99 | P a g e

Refer section 4.10 for business case scenario
• FETCH_VALUES_FOR_CONTEXT - In addition, to standard browser context, you can

create custom browser context using this BADI method. You need to also implement logic
for search criteria of custom browser context here.
• SET_TABLE_UI_ATTRIBUTE – User can set UI attributes for fields of the form

based on required business logic.
UI attribute can be set using generic service based on user event, field group,
service operation and form scenario stage.
For existing rows, UI attribute can be set using generic service.
For newly added row, UI attributes can be set in ct_process_record for the selected
columns. Decision of specifying UI attribute can be taken based on form scenario,
form scenario stage, form scenario version and user event and record index for the
selected column.
SAP Note: 2673872 100 |

Page
• UPDATE_TABLE_BUTTON –
a) Incase multiple tables are configured for same form, maintain TABEADDBTN and its
attributes by implementing method UPDATE_TABLE_BUTTON. Two tables can be
differentiated based on Group ID and field container id. Refer section 4.15 for further
details.
b) Implement this method to handle visibility of ADD button. Refer section 4.21 for further
details.
• HANDLE_SUBSTITUTION - In the standard delivered class

CL_HCMFAB_ASR_IM_PROCESS_CONFG code is provided to enable substitute
user to perform action. You can uncomment the code to use it in your
implementation.
• TABLE_BUTTON_HANDLING – By implementing this method, we can handle the

visibility of the Add, Edit, and Delete buttons of the table.This implementation will allow
you to control the visibility based on the form_scenario, form_scenario_stage, Group,
and Field group level. If you will not write any implementation then standard behavior of
ADD, EDIT and DELETE button will be considered.
SAP Note: 2673872 101 |

Page
5.5. Extension Hooks/Points for UI:
The following extension hooks are delivered to enhance SAP HCM Fiori P&F App. They
are available with software component UIHR002 100 SP 08 onwards.
Refer to SAP note 2894179, 2894110 and 2874669 for more details.
5.5.1. Overview page extension hooks/points
a) Overview.view.OverviewViewActionExtension = Allows to add action buttons to overview

dynamic page
.
b) Overview.view.OverviewViewToolbarExtension = Allows to add elements to the process
instance (draft table's) toolbar. (also known as overflow toolbar)
c) Overview.view.OverviewViewColumnExtension = Allows to add columns to the process

instance (draft) table.
d) Overview.view.OverviewViewItemExtension = Allows to add items to the process

instance (draft) table, cell data for custom columns.
e) FilterBar.fragment.OverviewViewFilterItemsExtension = Allows to add Filter Group Items

in Overview view.
SAP Note: 2673872 102 |
Page
f) Overview.controller.extHookChangeDateRange = Allows to change date range on

overview page. By default, App picks 30 days of data based on the current system date.
5.5.2. Detail page extension hooks/points
g) Detail.view.DetailViewHeaderExtension = Allows to add elements to the

ObjectPageHeader of the Detail view.
h) Detail.view.DetailViewHeaderVLExtension = Allows to add elements to the vertical layout

of headerContent of the Detail view.
i) Detail.view.DetailViewHeaderCntExtension = Allows to add layout to the headerContent

of the Detail view.
j) Detail.controller.extHookModifyKey = Allows to modify keys visibility in dropdown controls
SAP Note: 2673872 103 |

Page
5.5.3. Detail page : Extension hook/points for Dialog box
k) Detail.controller.extHookShowSuccessMsgDialog = Allows to show success messages in

a Dialog instead of a Message Toast. True: Dialog | False: MessageToast (Default)
l) SuccessMessageDialog.fragment.DetailViewSuccessMessageDialogExtension = Allows
to add content to the Success Message Dialog Box on the Detail Page (Displayed after
finalizing action like 'SEND' etc.) only if Detail.controller.extHookShowSuccessMsgDialog
is implemented to return the value 'true'.
m) Detail.controller.extHookSetConfirmationMessage = Allows to display a confirmation

dialog by setting the message for finalizing standard events.
SAP Note: 2673872 104 |

Page
n) ConfirmMessageDialog.fragment.DetailViewConfirmMessageDialogExtension = Allows to
add content to the Confirm Message Dialog Box on the Detail Page(Displayed if
extHookSetConfirmationMessage is implemented and confirmation message is returned).
o) Detail.controller.extHookHandleOnExitEvent = Allows you to handle custom operations

required during the init/exit events. The hook gets called at the end of the onInit lifecycle
method to perform custom operations. These custom events/operations need to be
carefully handled so that it does not break the SAP standard functionality.
5.5.4. Detail page: Extension hook/points for Form/Table labels
p) Detail.controller.extModifyPopinDisplayAndLabelDesign = Allows to modify the design

property of the Labels in all the Forms and Tables. It also allows to modify the Table
Column's popinDisplay property. (Default label design: "Standard" | Default popinDisplay:
"Inline")
q) Detail.controller.extHookSetColumnMinScreenWidth = Allows to handle the Table

Column's minScreenWidth property
r) Detail.controller.extHookInputFieldWidth = Allows to modify the field width of Input

control, when description property is filled
SAP Note: 2673872 105 |

Page
5.5.5. Detail page: Extension hook/point for Rich Text Editor
s) Detail.controller.extHookRichTextEditorSettings = Allows to use Rich Text Editor (RTE:

sap.ui.richtexteditor.RichTextEditor) control with custom settings
SAP Note: 2673872 106 |

Page
5.6. SAP Help Content
1. HCM Processes & Forms | Documentation for base configuration of HCM Processes & Forms
2. Process Inbox | Documentation for configuration of Process Inbox Fiori App
3. Start Process | Documentation for configuration of Start Process Fiori App
SAP Note: 2673872 - Release information of Fiori Apps for HCM Processes and Forms.
Fiori PA, PD & PT processes are available by applying Support Pack (SP) of below software
components:
Software component SP
GBX01HR5 605 SP 13
UIHR002 100 SP 09
EA-HRGXX EHP8 SP 76
Fiori PA & PD processes are available by applying Support Pack (SP) of below software
components along with note 2829082:
Software component SP
GBX01HR5 605 SP 12
UIHR002 100 SP 08
EA-HRGXX EHP8 SP 71
Fiori PA processes are available with below SP:
Software Component SP
GBX01HR5 605 SP 11
UIHR002 100 SP 07
EA-HRGXX EHP8 SP 69
SAP recommendation for customers is to upgrade their systems to the latest UIHR002,
GBX01HR5 and EA-HRGXX software components and then implement the latest released notes
for ‘Start Process’ and ‘Process Inbox’ Apps (PA-FIO-PNF) so that you do not miss any new
functionality and get latest bug fixes in Fiori apps.
Facing issues? Need more details? Contact SAP Support/create incident for PA-FIO-PNF
component.
SAP Note: 2673872 107 |

Page
6. REFERENCE EXAMPLES
We are demonstrating example configurations to covers different business
requirements.
6.1. Implementation of dependent value help or F4 Help (in a popup format)

The drop-down also known as value help or F4 help is commonly used in several HCM
processes and forms. In many cases there might be a need for dependent value helps as
well.
For example, a user action to select from a "Country" dropdown followed by user action to
select from a "Region" dropdown (which is dependent on the Country dropdown). The steps
to configure such a behavior are:
a) Define a generic service S_CH_ADD_FIO which link the two related fields.
b) Create a field group G1 with land1 & region which corresponds to Country & Region, the two
fields that are to be related in the dependent value help.
In addition to region & land1, five mandatory fields are to be added to the Field group for
creation of any user event.
These fields are:
• CENTRAL_PERSON
• EFFECTIVE_DATE
• MASSN
• MASSG
• PERNR
SAP Note: 2673872 108 |

Page
Under User Events maintain an operation called GET_STATES as shown below.

Attach Field Group G1 to the User Events operation GET_STATES.
There are two processing types which can be assigned a Field Group.
If the user event needs to be triggered during form initialization, maintain ‘Initialize’ as the
processing type of the Field Group.
If the user event needs to trigger validation / additional calculation based on another user entry,
maintain ‘Check’ as the processing type of the Field Group.
In the current example, since we are dealing with dependent search help, where the search help
of one field input should trigger the dropdown in a second field, we have maintained the
processing type of Field Group G1 as ‘Check’.
SAP Note: 2673872 109 |
Page
c) Configure the Fields. In “Country Key” row, “Input Help” column, select SAP_PA
(inputs help available can be SAP_PA, SAP_PD, SAP_PT, Generic services)
In “Region” row, “Input Help” column, select the newly created Generic service
S_CH_ADD_FIO.
d) Go to Field Metadata, maintain following entries for “Region” (I0006_STATE) field:

i) Has Value Help = checked / ticked
ii) F4 Parent Field = I0006_LAND1 (“Country Code”)
iii) Control type = Input
Output in UI based on above configuration steps:
Refer to standard delivered HCM Process HR_PA_XX_CHANGE_ADDRESS_FIO for

checking the configuration of dependent value help.
SAP Note: 2673872 110 |
Page
6.2. Implementation of dependent drop down (dropdown in a screen)
This section covers the configuration needed, if you want to populate a dropdown within a
screen.
For example, if “Region” field’s dropdown needs to be based on a user selected value of
“Country Code” following are the steps to be performed:
a) Create a Field group FG_GET_STATES:
SAP Note: 2673872 111 |

Page
b) Go to User Events, and create an Operation named GET_STATES and associate it with
newly created Field group FG_GET_STATES
c) Maintain the Field Metadata configuration as shown below to populate dependent dropdown
of “Region”. SH stands for search help event and it is used as the “keyword” for the system
to trigger the operation. For the current example, in order to trigger the GET_STATES
operation, we need to maintain the metadata configuration of “Region” field (I0006_STATE)
with the keyword SH=GET_STATES
SAP Note: 2673872 112 |

Page

At the launch of the Form, the list of countries will be displayed as a dropdown in the “Country
code” field.
On Initialize, Region field’s dropdown will be empty
(since the user operation is yet to be executed).
When the user selects a Country in the “Country Code” field using the drop down, the
“GET_STATES” User Event is triggered, and the search help event is triggered, and “Region” is
populated based on Country code.
E.g. when user selects India as the “Country Code”, list of States is populated in “Region”
SAP Note: 2673872 113 |

Page
6.3. User event to trigger the pre-population of a screen field.
If you want to initialize a field based on user selection of a different field, this option can be
used.
For example, if you want to default “Personal administrator” field for the employees based
on “Country Code” selected.
a) Create a Field group FG2:
b) We will read Field group FG2 values in generic service(ZHRASR_GS_4_NEW) and

populate personal administrator field with a fixed value based on country.
SAP Note: 2673872 114 |

Page
c) Under User Events create GET_VALUES user event and link it to the newly created field
group FG2
d) Maintain the Field Metadata configuration as shown below to trigger the operation.
FE stands for field event and it is used as the “keyword” for the system to trigger the
operation. For the current example, GET_VALUES is the operation. In order to trigger
GET_VALUES, we need to maintain the metadata configuration of “Country code” field
(I0006_LAND1) with the keyword FE=GET_VALUES
SAP Note: 2673872 115 |

Page

On Selecting “Country Code”, field event will be triggered which will populate the value in
the “Personal Administrator” field.
6.4. Provision to display field description next to the input field in the form
It is possible to configure two fields linked to each other displayed on same row.
It has been made available to link TEXT field with INPUT field.
For e.g., You want to show currency along with amount.
SAP Note: 2673872 116 |

Page
DTT Configuration:
SAP Note: 2673872 117 |

Page
6.5. Provision to show custom tooltip for all the fields
By default, label text maintained for field is shown as tooltip. Custom tooltip can be configured in
Field metadata for each field.
For e.g., “Place of birth” is custom tooltip configured for “Country of Birth” field.
DTT configuration:
In case you are using multiple logon languages then tooltip need to be maintained for
corresponding languages.
SAP Note: 2673872 118 |

Page
6.6. Control Type, FORMATTEDTEXT to display text with html tags
For fields in the forms where you want specific formatting for example font change / font
characteristics like bold / italics, bullet points, headings etc., you could use FORMATTEDTEXT
during the form configuration.
For example, below form shows the output of a formatted text describing a Technical Manager.
DTT configuration: Maintain field with Control type “FORMATTEDTEXT”.
SAP Note: 2673872 119 |

Page
6.7. Control Type, Timepicker for Time related Processes
If you have the need to use “Timepicker” field in your form to allow user to enter time in
HH:MM:SS format, this control could be used.
For example, below form shows the output of a form with “Timepicker” control.
DTT configuration:
SAP Note: 2673872 120 |

Page
6.8. Control Type, RICHTEXTEDITOR to maintain text with html tags
For fields in the forms where you want specific formatting for example font change / font
characteristics like bold / italics, bullet points, headings etc., you could use RICHTEXTEDITOR
during the form configuration.
For example, below form shows description describing a Manager 1 position.
DTT configuration: Maintain field with Control type “RICHTEXTEDITOR”.
SAP Note: 2673872 121 |

Page
6.9 Maintain Business Statuses corresponding to Processing Statuses.
Business Status is maintained depending on processing status.

There are two actions available with this activity:
• Provide the business status text for a specific step status.
• Assign the business status to the request step in a specific process.
Requirements:
You have created a process in Customizing for Personnel Management by choosing HR
Administrative Services -> Configuration of Forms/Processes -> Process Configuration -> Set
Up Processes and performing the activities there.
Activities:
1) To enter and change the business status for a particular step status:
1. Choose Maintain Business Status in the dialog box that appears when you start the
activity (view V_5ASRBSTATUS).
2. Specify Work Area.
The work area is the processing step status that you want to provide a custom business
status text for, such as Processed, or Forwarded.
3. Enter business status text for this processing status in the column Business Status,
such as Processed by Manager.
4. Choose Save.
The Business Status text you have specified here is available as an option when you are
specifying Business Status for a specific process.
For example, you are setting different Business Statuses to be used in different scenarios for
Work Area ‘Processed’ as shown below:
SAP Note: 2673872 122 |

Page
2) To edit the business status for the request step in a particular process:
1. Choose Maintain Business Status in Request Step in the dialog box that appears
when you start the activity (view V_5ASRREQBSTATUS).
2. Specify Work Area.
The work area is the process that you want to provide a custom business status text for.
3. You can create a new entry, selecting from the options provided under Step Status
After Action and then selecting an option from the BStatusID column, or change the text
of an existing entry, selecting from the options provided under BStatusID for the existing
step status.
4. The text in column Business Status appears in the Process Browser.
5. Choose Save.
For example, you are using one of the Business Statuses, specified for work area
‘PROCESSED’ in view V_5ASRBSTATUS, as Business Status Text for first step i.e., when form
is submitted by initiator.
You are setting Business Status ID for required step (‘PROCESSED’ in this case) for process
‘HR_PA_XX_SPECIAL_PAYMENT_1_FIO’ in view V_5ASRREQBSTATUS as shown below:
SAP Note: 2673872 123 |

Page
3) If there is a workflow involved, you must perform binding in the workflow builder to save the
business status.
To save the business status in workflow:
1. Open the Workflow Builder in transaction SWDD.
2. Enter the workflow that you want to set the business status for, for
example, Termination.
3. Double-click the workflow step that you want to set the business status for.
4. Choose the Binding button on the navigation pane.
5. Choose Business_Status and drag to workflow window.
a) Open the Enter Constant dialog box and choose the Edit button,
b) Choose the processing status you want to enter business status text for.
Alternatively, you can drag an individual status from under Business_Status into
workflow and specify a business status ID.
6. Choose Save.
For example, you want to show Business Status after the form has been approved by manager
for process ‘HR_PA_XX_SPECIAL_PAYMENT_1_FIO’.
• You set Business Status ID for work area ‘APPROVED’ in V_5SRBSTATUS view.
SAP Note: 2673872 124 |

Page
• You will use the same Business Status ID in Binding of Approve Step in the related
workflow as shown below:
6.10 Process Configuration for Time Constraint 3 Infotypes
Below configuration is required when multiple operations (Add, Edit and Delete) need to be performed
simultaneously for multiple records of same subtype of Infotype.
Form Scenario Configuration:
1. Config under Form Scenarios -> Fields section:
• Include field DELETE_DATASET with data binding to Data element “delete_dataset_flag “.

Maintain field attribute as “Invisible”.
Note: a) DELETE_DATASET is reserve field and need to be maintained as shown below.
b) Add DELETE_DATASET at form scenario level.
• Maintain Field HRASR_IS_MULT_PA with Manual default value as X.
SAP Note: 2673872 125 |

Page
2. Config under SAP_PA -> Fields section: Maintain subtype as ‘*’ in case multiple subtypes need to be
determined at runtime.
Maintain record index with value ‘*’ instead of 1.
3. Rule creation:
Create rule DELETE as shown below.
SAP Note: 2673872 126 |

Page
4. Config under SAP_PA -> Infotype and Operations section:

Maintain subtype as ‘*’ and Operation as ‘Change’. Maintain Rule DELETE.
6.11 Metadata configuration for multiple tables:
In case multiple tables are required to be shown on form, these are the configuration steps to be
followed to correctly format multiple tables on the form:
Multiple tables are added in same container:

• Each table should belong to distinct group.
• For each group, the numbering of the columns (included in the table) should begin from lowest
numbers of that group or 1(initial numbers) as shown in the below image:
SAP Note: 2673872 127 |
Page
On correctly numbering multiple tables, the formatting of the table is correctly set as shown below:
If tables in each group are not numbered starting from lowest numbers of the group, the formatting of
the table will be disturbed as shown below:
SAP Note: 2673872 128 |

Page
Single table is shown in the same group as other fields of the form:
• Numbering of the columns (displayed on the form) of the table should start from lowest
numbers or 1.
SAP Note: 2673872 129 |

Page
6.12 Ability to display error message during user event trigger.
While maintaining a user event in DTT (Design time tool), if user has not selected "Ignore
errors" then error messages generated in backend is also displayed when user event is
triggered.
For instance, following user event is maintained for a Birth of Child test process with ‘Ignore
Errors’ unchecked, as shown below:
User event is now linked to ‘Country of Birth’ field on form:
SAP Note: 2673872 130 |

Page
Since, Ignore Errors was not selected, error message generated for mandatory field ‘First
Name’ is sent to frontend when user event is triggered on selecting ‘Country of Birth’.
SAP Note: 2673872 131 |

Page

SAP HCM PF Fiori Comprehensive Guide v3.1

Uploaded by

Copyright:

Available Formats

SAP HCM PF Fiori Comprehensive Guide v3.1

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP HCM PF Fiori Comprehensive Guide v3.1

Uploaded by

Copyright:

Available Formats

CUSTOMER

SAP HCM Processes and Forms (P&F)

Version 3.1 | December 2023

Navin P R and Team ( [email protected] )

SAP Note: 2673872 3|Page

SAP Note: 2673872 4|Page

Introduction to SAP HCM Processes and Forms

PA (Personnel Administration), PD (Personnel Development) and PT (Personnel Time

SAP Note: 2673872 5|Page

1.1 Creating a Fiori Form

1.2 Fields in the Fiori form

SAP Note: 2673872 6|Page

1.3 Business Example

e. Save the Form Scenario.

SAP Note: 2673872 8|Page

1.4 Metadata Properties

Enter an ID for the corresponding container here.

You can choose from any the following values:

SAP Note: 2673872 9|Page

For an INPUT Control Type, enter the length of the field.

For an INPUT Control Type, enter the precision of the

For an INPUT Control Type, enter the scale of the field.

Group Name Group Name corresponds to a Section title in the UI. A

Enter the sequence (e.g.: 1, 2, 3 and so on) in which the

This field needs to be “Ticked” / “Checked” if the field has

SAP Note: 2673872 10 | P a g e

It is possible to configure two fields linked to each other

The drop-down also known as value help or F4 help is

While configuring the field “Region”,

By default, label text maintained for field is shown as

SAP Note: 2673872 11 | P a g e

SAP Note: 2673872 12 | P a g e

1.5 Error Handling

Use the Check option to verify the metadata configuration.

Mainly two kinds of errors are shown by the check.

SAP Note: 2673872 13 | P a g e

b. Errors generated due to changes in values for rows ‘HRASR_CURRENT_NOTE’ and

These errors come when rows ‘HRASR_CURRENT_NOTE’ and ‘HRASR_PREVIOUS_NOTES’

Revert the values in these rows as shown below:

SAP Note: 2673872 14 | P a g e

1.6 Copying existing Form Scenario into Fiori form

SAP Note: 2673872 15 | P a g e

1.7 Workflow Configuration

WS13600359 Workflow for PA error handling - Fiori

WS13600356 Draft for Process Start-Fiori

WS13600357 Workflow for Forward to expert

Workflow Tasks Description

13600232 Approve Form-Fiori

13600233 Draft for Process Start-Fiori

13600235 Check Form Data – Fiori

13600239 Approve PD Form-Fiori

13600241 Draft for PD Process Start-Fiori

1.8 Copying existing Adobe or FPM workflow to Fiori workflow

SAP Note: 2673872 16 | P a g e

Enter required workflow name and abbreviation.

SAP Note: 2673872 17 | P a g e

(iii) The copied workflow will be opened.

SAP Note: 2673872 18 | P a g e

(iv) Once workflow task is changed binding will be reset.