Leave System Sap Fiori

5/21/2022
SAP Fiori 2.0 for SAP HCM

Generated on: 2022-05-21 09:59:59 GMT+0000
SAP Fiori for SAP Business Suite | 2.0 2018-01
PUBLIC
Original content: https://help.sap.com/docs/SAP_FIORI/d59d9f81f4884bf9b115936b92c27202?locale=en-

US&state=PRODUCTION&version=2.0 2018-01
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/docs/disclaimer.
This is custom documentation. For more information, please visit the SAP Help Portal 1
5/21/2022
SAP Fiori 2.0 for SAP ERP HCM
Use
This SAP Fiori product contains the front-end components of a bundle of transactional apps for Human Capital Management
(HCM) that run on the SAP Fiori launchpad.
Information Type Product Data
SAP Product (Official Name) SAP Fiori 2.0 for SAP ERP HCM
Release 2.0
Support Package Stack SPS 01
Delivery Date 01/2018
System Landscape Requirements

Before you start to install this SAP Fiori product and implement the contained apps, ensure that your system landscape has
been set up to enable SAP Fiori. Since the back-end components of the apps are delivered with separate products, the
respective back-end product has to be in place in your system landscape as well.
SAP Fiori System Landscape Setup Prerequisites
Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements
The back-end components of the apps are delivered with the following SAP product:
Information Type Product Data
SAP Product (Official Name) SAP Fiori 2.0 for SAP ERP HCM
Support Package Stack SP00
Approve Leave Requests (Version 3/Fiori 2.0)

Abstract for SAP Fiori apps.
With the transactional app Approve Leave Requests (Version 3) you enable managers to approve or reject leave requests for
their direct reports, easily and exibly from their SAP Fiori My Inbox app . Key information for the approval decision is
available at a glance, including a team calendar that shows overlapping leave requests.
Key Features
Browse all requests submitted for approval in a personalized inbox
View details for speci c requests, including the leave requested, the available balance and any comments relating to the
request
View a team calendar that shows overlapping leave requests if there are leave con icts
Approve or reject requests (with optional note to the requester)
Allows manager to view leave overlaps for an employee over a speci c period
5/21/2022
View attachments
Navigation Targets
This app enables users to access other apps directly (for example to display detailed information).
 Note
Linked apps have to be already available in your system landscape or you have to implement them along with this app.
My Team Calendar (Version 2)

In order to be able to implement this app, your system landscape has to be enabled for SAP Fiori. One of the requirements for
your system landscape is that your back-end product meets the required product version stack:
Required Back-End Product (Product Version Stack) SAP Fiori 1.0 for SAP ERP HCM (07 (07/2017))
The front-end components of this app (such as the user interface) are delivered together with the components of other apps as
part of this SAP Fiori product:
Front-End Components Delivered with (Product Version Stack) SAP Fiori 2.0 for SAP ERP HCM ( Initial State )
For more information, see the app implementation document of this app.
Related Apps
From a business perspective, the following apps are related to this app:
My Leave Requests (Version 3)
Component for Customer Incidents

PA-FIO-LEA
App History: Approve Leave Requests (Version 3)

App history for SAP Fiori app.
 Note
Starting with the initial delivery date, the app is delivered with each support package stack of the respective SAP Fiori
product. This document only lists support package stacks in which the app has been enhanced or changed. If the app was not
changed in a particular support package stack, then this support package stack is not mentioned in this document.
The app has been enhanced as follows:
SAP Fiori for SAP ERP HCM 2.0 SPS 0 (Delivery Date 07/2017)
Initial delivery.
5/21/2022
App Implementation: Approve Leave Requests (Version 3)

Implementation information for SAP Fiori app.

In order to be able to implement this app, your system landscape has to be enabled for SAP Fiori. Depending on the database
type serving as the basis in your system landscape, it has to be set up for SAP Fiori and has to meet the respective
prerequisites:
The SAP product version in the back-end system serving as the basis for the app must be the following:
Required Back-End Product (Product Version Stack) EHP7 FOR SAP ERP 6.0 - SPS 01 (08/2013)
EHP8 FOR SAP ERP 6.0 - SPS 01 (01/2016)
MSS ADD-ON 1.0 - SPS Initial Shipment Stack
Each SAP Fiori app consists of front-end components and back-end components:
The front-end components of the app consist of the user interfaces and content required for launching the app on the
SAP Fiori launchpad. These components have to be installed on your front-end server.
The back-end components of the app mainly consist of the OData services required for the app. These components have
to be installed in your back-end system.
The front-end and back-end components of the app are delivered with the following SAP product versions as part of the listed
software components. The required software components for the app are contained in the listed product instances:
App Required SAP Product Version Available Instances Containing Software Component Required for
Component (Support Package Stack) Software Component App (Support Package)
Front-End SAP Fiori 2.0 for SAP ERP HCM UI for ERP HCM > NW750 UIHR002 100 (0005 )
Components ( Initial State )
Back-End SAP Fiori 1.0 for SAP ERP HCM HCM ERP 605 INT GBX01HR5 605 (n/a )
Components (07 (07/2017))
HCM ERP 605 INT
NW740
For more information about the installation of front-end components, see http://help.sap.com/ ori_implementation.
Required SAP Notes

On the back-end server, the following SAP notes must be implemented for this app:
SAP Note Number Description
not available not available
On the front-end server, the following SAP notes must be implemented for this app:
5/21/2022
Implementation Tasks
The following sections list tasks that have to be performed to implement the required components of the app. The tables
contain the app-speci c data required for these tasks.
You can nd the data required to perform these tasks in the SAP Fiori apps reference library at:
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F2584
Front-End Server : Activate OData Services
Component Technical Name
OData Service (Version Number) HCMFAB_LEAVE_REQUEST_APR_SRV (0001 )
For more information about how to activate the OData service, see Front-End Server: Activate OData Services .
Front-End Server: Activate SAPUI5 Application
SAPUI5 Application HCMFAB_LRAPR_IN
For more information about how to activate the SAPUI5 application (ICF service), see Front-End Server: Activate ICF Services.
Enable App for Access in SAP Fiori Launchpad
To de ne the access of single users to this app in the SAP Fiori launchpad, technical content is delivered, such as catalogs and
example roles.
You can nd an overview of the delivered technical content for this SAP Fiori app in the SAP Fiori apps reference library.
For more information about how to proceed with this content, see Enable App for Access in SAP Fiori Launchpad.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
You must assign OData service authorizations for the app to your users.
 Note
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server :
On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You
can copy this role and adjust it to your needs.
On the front-end server , you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs.
5/21/2022
OData Service (Version Number) Back-End Server: Delivered Authorization Role (PFCG Front-End Server : Assignment to
Role) Authorization Role
HCMFAB_LEAVE_REQUEST_APR_SRV In addition, this role contains authorizations to display OData service authorization must be
(0001 ) the related business data. assigned.
SAP_HCMFAB_LRAPR_IN_APP
 Note
In addition, this role contains authorizations to
display the related business data.
Prerequisites for Implementation

Before implementing the app, you must ensure the following:
You have implemented the SAP Fiori app My Inbox.
Con guration Tasks

To be able to implement the app, you must perform the following con guration tasks in the back-end system:
SAP Note 2434370
SAP Note: 2434370 is prerequisite for implementing Approve Leave Requests (Version 3) SAP Fiori app.
Switch to Activate Non -Work ow Leave Request
 Note
This con guration task is only relevant when you are using the request database for your leave request approvals.
In general, the SAP Fiori My Inbox app only receives the work items generated via the work ow. Historically, the customers
can choose to create the leave request based on work ow or request database via the Rule Group con guration in the back-
end system. To receive the non work ow based work items in the SAP Fiori My Inbox app, you have to activate in table T77S0
the switch PTMW FABFI. With the switch active (X), the Inbox shows the non work ow items.
Classifying the Work ow Template
Execute transaction code PFTC.
On the screen Task: Maintain enter the value Workflow Template for Task Type and 27000001 for Task.
Click the Display (F7) button.
In the following screen, choose the menu Additional data Classi cation Create
In the Create Classification/Lock Ind. screen, classify the work ow as a General Task by choosing the
radio button in the section Classification.
Save the con guration.
Con guring SWFVISU for Intent-based Navigation
Execute transaction code SWFVISU.
5/21/2022
Choose the tasks TS12300097 and TS21500003 and set the Visualization Type as Intent-Based
Navigation.
 Note
Do not use the Task TS21500003 as template for other work ows.
Choose the task TS12300003 and double-click on Visualization Parameter in the dialog structure on the left
pane.
Con gure the parameters as below
Table 1: Values for Visualization parameter
Visualization Parameter Value for approval
ACTION approve
QUERY_PARAM00 -
QUERYPARAM01 -
SEMANTIC_OBJECT LeaveRequest
Perform the two previous steps for Task TS21500097 as well.
Maintaining Task Names and Decision Options
For the APPROVAL / REJECT Button to appear in the SAP Fiori My Inbox, the following con guration steps has to be done:
In the SAP Customizing Implementation Guide go to SAP NetWeaver SAP Gateway Service
Enablement Content Work ow Settings Maintain Task Names and Decision Options
Con gure the Approve/Reject actions for the following work ow templates as shown below:
Work ow ID Step ID
WS33700137 0000000038
WS12300111 0000000038
WS21500001 0000000038
WS27000001 0000000010
Create/Choose the entry for the work ow template (for example Work ow ID: WS21500001, Step ID: 0000000038,
Step Description: Leave Request)
Double-click Decision Keys in the Dialog Structure on the left pane and add the following entries for the decision keys:
Key Decision Text Nature
1 Approve POSITIVE
4 Reject NEGATIVE
Save the record.
Repeat the previous 3 steps for all above-mentioned work ow templates.
5/21/2022
 Note
SAP delivered a standard BAdI Implementation HCMFAB_LEAVE_APPROVAL_INBOX to in uence the logic of
APPROVE/REJECT buttons. If Customers want in uence the behavior, consider implementing the BAdI:
/IWWRK/BADI_WF_BEFORE_UPD_IB. The BAdI implementation: /IWWRK/ES_WF_WI_BEFORE_UPD_IB has two
implementation for the same lter. Please deactivate the implementation delivered in the old release.
Con guring the Target Mapping
As a last step in the process you have to create a Target Mapping in the SAP Fiori Launchpad Designer. Create the target
mapping as shown below in the catalog of your Inbox Tile. For an instance, if you’re using the My Inbox for Manager app as
described in the SAP Fiori Library create the following target mapping in the technical catalog SAP_FND_BC_MANAGER_T for
the instances Approve Leave Request:
Semantic Action Application Title URL ID Parameters

Object Type
LeaveRequest Approve SAPUI5 Approve /sap/bc/ui5_ui5/sap/hcmfab_lrapr_in hcm.fab.leaveapproval.inbox Name: open

Fiori App Leave
Mandatory:
Request
Value:
embedIntoD
More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .
App Extensibility: Approve Leave Requests (Version 3)

Extensibility information for SAP Fiori app.
You can extend the app according to your business needs for different aspects. For this purpose, the following extensibility
options are available:
You can extend the app by customizing the team calendar for your business needs.
You can extend the app by displaying additional information about leave requests and employees who sent the leave
requests.
You can enhance the properties of the additional elds for a speci c leave type.
You can extend the app by adding additional elds to the header and the icon tab or to add a sections tab in the details
page.
You can adjust the object attributes of the header section.
You can de ne the relations between employees using this app and other employees (for example to determine direct
reports) and can extend the information displayed in the employee data.
Extensibility Entities
Business Add-Ins (BAdIs)
The following Business Add-Ins are available for extensibility purposes:
5/21/2022
Common BAdI for all HCM SAP Fiori Apps (HCMFAB_B_COMMON)
You can use this BAdI to enhance HCM SAP Fiori apps delivered with software component UIHR002. You can de ne who
is a colleague of the employee, who is a direct report of a manager, who is an employee reporting to a manager and who
is a manager of an employee. You can also extend the employee information shown in the employee data, the
determination of the employee picture and the office address. Besides, you can check whether an employee is a
manager.
 Note
Since the BAdI is also relevant for settings of team calendars used in other HCM SAP Fiori Apps, you have to specify
in the BAdI interface that the information is relevant to this app.
Settings for Team Calendar (HCMFAB_B_TEAMCALENDAR_SETTINGS)
You can use this BAdI to customize the team calendar. You can add or remove elements from the UI like the employee
photo or the lter button. You can de ne which event types, which calendar views and employee descriptions are
displayed in the team calendar.
 Note
BAdI: Extensions for Team Calendar ODATA Entities (HCMFAB_B_TEAMCALENDAR)
You can use this BAdI to extend the entities of the team calendar control:
SearchResult
TeamCalendarEmployee
TeamCalendarEvent
TeamCalendarEventType
TeamCalendarUISettings
TeamCalendarView
 Note
Note that the entries affect the team calendars in all apps that use the team calendar control.
BAdI: Enhancements for Approve Leave Requests (Version 3) App (HCMFAB_B_LEAVE_APPROVAL)
You can use this BAdI to display additional information about the leave request, the employee who sent the leave
request and to enhance the properties of the additional elds that are con gured for the speci c leave type.
Extension Points
To add additional UI elements to the app, the following extensibility entities are available on the different layers. You have to
extend each of these entities according to your speci c business needs:
View Extension Point Use
S3.view extS3Header Allows you to add additional elds in the

header
S3.view extS3SectionsTab Allows you to add sections tab in the

details page
If there are additional elds available in the OData service, you can display these elds on the UI. For more information, see the
extensibility documentation for the respective SAP NetWeaver release on your front-end server at
5/21/2022
http://help.sap.com/ ori_implementation Extensibility Information for SAP Fiori Extending the UI Layer UI Extensibility
Work ow Checking the SAP-Enabled Extension Options Extension Points .
UI Controller Hooks
To plug in and execute custom code, the following hook is available in the controller code:
Controller Hook Use
S3.controller.js hcm.fab.leaveapproval.inbox.view.S3~extHookHandleHeader Allows you to adjust

the object header
If there are additional UI controller hooks available in the controller code, you can add own code. For more information, see the
Work ow Checking the SAP-Enabled Extension Options UI Controller Hooks .
More Information
For a general description of the extensibility options and procedures of SAP Fiori apps, see
http://help.sap.com/ ori_implementation Extensibility Information for SAP Fiori .
Approve Time Events (Fiori 2.0)

With the transactional app Approve Time Events (Fiori 2.0), as a manager, you can manage the time events of your direct
reports from their SAP Fiori app My Inbox.
Key Features
Browse all requests submitted for approval in the inbox
View details for each request, including type of the event, date and time of request submission, comments from the
requester, and any additional information con gured for the event type
Approve or reject requests (with optional note to the requester)

Front-End Components Delivered with (Product Version Stack) SAP Fiori 2.0 for SAP ERP HCM ( 01 (01/2018) )
5/21/2022
Related Apps
My Time Events (Version 2/Fiori 2.0)

PA-FIO-CIO
App History: Approve Time Events (Fiori 2.0)

Initial delivery.
App Implementation: Approve Time Events (Fiori 2.0)


prerequisites:
5/21/2022
Front-End SAP Fiori 2.0 for SAP ERP UI for ERP HCM > NW750 UIHR002 100 (1 )
Components HCM ( 01 (01/2018) )
Back-End SAP Fiori 1.0 for SAP ERP HCM ERP 605 INT GBX01HR5 605 (n/a )
Components HCM (08 (12/2017))
HCM ERP 605 INT
NW740
Required SAP Notes

https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F3099
OData Service (Version Number) HCMFAB_TIMEEVENTS_APR_SRV (0001 )
SAPUI5 Application HCMFAB_TEAPR_IN
5/21/2022
example roles.
 Note
HCMFAB_TIMEEVENTS_APR_SRV In addition, this role contains authorizations to display the OData service authorization must be
(0001 ) related business data. assigned.
n/a
 Note
In addition, this role contains authorizations to display
the related business data.
Prerequisites for Implementation

Before implementing the app, you must ensure the following:
You have implemented the SAP Fiori app My Inbox and the SAP Note 2520847 .
Con guration Tasks

To be able to implement the app, you must perform the following con guration tasks in the back-end system:
Activate Non-Work ow Time Events
 Note
This con guration task is only relevant when you are using the request database for your time events.
SAP Fiori My Inbox app receives only those work items that are generated via the work ow. You can choose to create time
events based on work ow, or based on request database via the Rule-Group con guration in the back-end system. To receive
the non-work ow based work items in the My Inbox app, do the following:
5/21/2022
In the table T77S0, activate the switch PTMW FABFI. When the switch is active(X), the non-work ow based work items are
displayed in the My Inbox app.
Classify the Work ow Template
1. Execute the transaction code PFTC. On the Task:Maintain screen, enter the following values:
Task Type - Work ow Template
Task - 27000003
2. Choose Display button or press F7. On the screen, navigate to Additional data Classi cation Create .
3. On the Create Classi cation/Lock Ind. screen, classify the work ow as a General Task by choosing the radio button in
the section Classi cation.
4. Save the con guration.
5. Repeat the steps 1 to 4, for the following Task Types.
Task Type Task
Standard task 27000001
Work ow Template 13600347
Standard task 13600230
 Note
The Work ow 13600347 and Task 13600230 are available as of the following HRSPs.
Release HRSP
605 A3
606 88
607 77
608 54
These standard work ow and tasks are to be used exclusively for Time Events. If your system does not have the
mentioned HRSPs or higher, create a custom work ow and tasks, and use instead of 13600347 and 13600230.
Custom Task
You can copy the standard task 21500003 to create a custom task. You may wish to adjust the Workitem Text to
&_WI_OBJECT_ID.OWNER.NAME&'s Time Event.
Custom Work ow
You can copy the standard work ow 21500001, and make the following changes, to create a custom work ow.
1. On the Work ow Builder – Display ʻPT_TIMCORWDA’ screen, assign the created custom task as Task in the Step 38
(000038) Approval Process.
2. Choose the Binding(Exists) button, and ensure that the binding is as follows:
5/21/2022
Work ow Step ʻTime Events – Approval Process’
&REQ.REQ_ID& &REQUESTID&
&REQ& &_WI_OBJECT_ID&
3. c. Select Agent Assignment, and on the Standard Task: Maintain Agent Assignment screen, verify that the con guration
is as follows:
Name ID General
Time Events – Approval Process TS 13600230 General Task
If the assignment is different, on the same Standard Task: Maintain Agent Assignment screen, choose Attributes, and
select General Task in the Task popup.
The con gurations speci ed for the work ow 13600347 and task 13600230 should be performed for the custom work ow and
custom task respectively.
Con gure SWFVISU for Intents based navigation
1. Execute the transaction code SWFVISU.
2. Choose the following tasks and set the Visualization Type as Intent-Based Navigation.
TS27000001
TS13600230
3. Choose the task TS27000001 and double-click Visualization Parameters on the left pane.
4. Con gure the visualization parameters as below:
Visualization Parameter Visualization Parameter Value
ACTION approve
QUERY_PARAM00
QUERY_PARAM01
SEMANTIC_OBJECT TimeEntry
5. Repeat steps 3 and 4 for the Task TS13600230.
Maintain Task Names and Decision Options
To ensure that the APPROVAL / REJECT Button to appears in the Inbox, con gure the Approve/Reject actions through
Customizing activity.
1. Execute transaction code SPRO.
2. Navigate to the Customizing activity Maintain Task Names and Decision Options under SAP NetWeaver SAP Gateway
Service Enablement Content Work ow Settings .
3. Con gure for the following Work ow templates:
5/21/2022
Work ow ID Step ID
WS13600347 0000000038
WS27000003 0000000010
4. Create or choose the entry for the work ow template.
5. Double-click Decision Keys in the left pane and create the following entry in the Change View “Decision Keys”: Overview
screen:
Table 2: Decision Keys
Key Icon MIME Repository Decision Text Comment Nature

Path
1 Approve POSITIVE
4 Reject NEGATIVE
6. f. Save the record.
7. Repeat the steps 4, 5 and 6 for the Work ow templates WS27000003 and WS13600347.
 Note
SAP delivered a standard BADI Implementation HCMFAB_CICO_APPROVAL_INBOX to in uence the logic of
APPROVE/REJECT button. If you need to in uence the behavior, please consider implementing the following BADI:
/IWWRK/BADI_WF_BEFORE_UPD_IB.
Set up the Task Visualization Parameter
You must set up the task visualization parameter for the task TS27000001.
1. Execute transaction code SM30.
2. In the Edit Table Views: Initial Screen, specify Table/View as SWFVVTV.
3. Choose Display.
4. In the Determine Work Area: Entry popup, specify the following:
Task Visualization Type
TS27000001 WD_ABAP
5. Select the Edit button and enter the Task Visualization parameter as follows.
Visualization Parameter Visualization Parameter Value
APPLICATION LeaveRequestApprover
6. Save the record.
Con gure the Target Mapping
Create a target mapping in the FIORI Launchpad Designer. Create the target mapping as shown below in the catalog of your
Inbox Tile. For an instance, if you’re using the My Inbox for Manager app as described in the SAP Fiori Library, create the
5/21/2022
following target mapping in the technical catalog SAP_FND_BC_MANAGER_T for the instances Approve Time Events:
Semantic Action Application Title URL ID Paramet

Object Type
TimeEntry approve SAPUI5 Approve /sap/bc/ui5_ui5/sap/hcmfab_teapr_in hcm.fab.timeeventsapproval.inbox Name: op

Fiori App Time
Mandato
Events
Value:
embedIn
More Information
App Extensibility: Approve Time Events (Fiori 2.0)

You can extend the app by adding additional elds to the Header section.
You can extend the app by displaying additional information in the Information section.
The following Business Add-In is available for extensibility purposes:
oData BAdI (HCMFAB_B_TIME_EVENT_APPROVAL)
You can use this BAdI to enhance the Employee, Time Event, and Additional Fields information con gured for the speci c
event type. You can implement the following methods to enhance the standard information.
ENRICH_TIME_EVENT
ENRICH_EMPLOYEE
ENRICH_ADDITIONAL_FIELDS
Extension Points
To enhance the app, the following extension points are available:
View Extension Point Use
S3.view.xml extS3Header Allows you to add additional information to

the Header section.
extS3Information Allows you to add additional information to

the Information section.
5/21/2022
UI Controller Hooks
To plug in and execute custom code, the following hooks are available in the controller code:
Controller Hook Use
S3.controller.js hcm.fab.timeeventsapproval.inbox.view.S3~extHookHandleHeader Allows you to adjust

the Header section.
hcm.fab.timeeventsapproval.inbox.view.S3~ extHookHandleInfo Allows you to adjust

the Information
section.
More Information
Employee Lookup (Version 2/Fiori 2.0)

With the transactional app Employee Lookup (Version 2) you can search for an employee using the employee name and view
reporting line and communication data of the selected employee.
Key Features
Search for employees
View organizational and communication details of employees and get in contact with them
View the reporting line of the selected employee
View the direct reports and colleagues of employees
An employee who is concurrently employed can use the app for a chosen personnel assignment.

5/21/2022

PA-FIO-LKP
App History: Employee Lookup (Version 2)

 Note
Initial delivery.
App Implementation: Employee Lookup (Version 2)


prerequisites:
5/21/2022
HCM ERP 605 INT
NW740
Required SAP Notes

2103156 Launching Fiori apps in standalone mode
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F1383A
OData Service (Version Number) HCMFAB_EMPLOYEELOOKUP_SRV (0001 )
5/21/2022
SAPUI5 Application HCMFAB_EMP_LKP
example roles.
 Note
HCMFAB_EMPLOYEELOOKUP_SRV In addition, this role contains authorizations to display the OData service authorization must be
SAP_HCMFAB_EMP_LKP_APP
 Note
In addition, this role contains authorizations to display
the related business data.
More Information
App Extensibility: Employee Lookup (Version 2)

5/21/2022
You can extend the app Employee Lookup (Version 2) according to your business needs for different aspects. For this purpose,
the following extensibility options are available:
You can extend the app by adding columns and cells to the table of search results, to the table of colleagues, and to the
table of direct reports.
You can extend the app by adding actions and elds to the employee details object header.
You can extend the app by adding additional elements to the manager quick view and the office info quick view.
You can adjust the employee details object header.
manager.
 Note
BAdI for Employee Lookup (Version 2) SAP Fiori App (HCMFAB_B_EMPLOYEELOOKUP)
You can add additional information to the search suggestion list of the search eld.
You can add additional information to the colleagues and direct reports information shown in standard.
Extension Points
To add additional UI elements to the app, the following extensibility entities are available on the different layers. You can extend
each of these entities according to your speci c business needs:
UI Back End/ABAP
View Extension Point / Purpose Design Time: Design Time: E

Gateway Entity
ColleaguesBlock.view.xml colleaguesTableColumnsExtension - -
Allows you to add columns to the table of

colleagues
ColleaguesBlock.view.xml colleaguesTableRowsExtension Colleague HCMFAB_S_EM
Allows you to add cells to the table of colleagues
5/21/2022
UI Back End/ABAP
View Extension Point / Purpose Design Time: Design Time: E

Gateway Entity
DirectReportsBlock.view.xml directReportsTableColumnsExtension - -
Allows you to add columns to the table of direct

reports
DirectReportsBlock.view.xml directReportsTableRowsExtension DirectReport HCMFAB_S_EM
Allows you to add cells to the table of direct reports
EmployeeDetails.view.xml extensionEmployeeDetailsActions - -
Allows you to add actions to the EmployeeDetails

object header
EmployeeDetails.view.xml extensionEmployeeDetailsHeaderContent EmployeeDetail HCMFAB_S_EM
Allows you to add elds to the EmployeeDetails

object header
EmployeeDetails.view.xml extensionEmployeeDetailsSection EmployeeDetail HCMFAB_S_EM
Allows you to add sections to the EmployeeDetails

page
SearchResultList.view.xml searchResultTableColumnsExtension - -
Allows you to add columns to the table of search

results
SearchResultList.view.xml searchResultTableRowsExtension SearchResult HCMFAB_S_EM
Allows you to add cells to the table of search

results
ManagerQuickview.fragment.xml extensionManagerQuickview EmployeeDetail HCMFAB_S_EM
Allows you to add additional elements to the

Manager Quick view
OfficeInfoQuickview.fragment.xml extensionOfficeInfoQuickview EmployeeDetail HCMFAB_S_EM
Allows you to add additional elements to the Office

Info Quick view
UI Controller Hooks
To plug in and execute custom code, the following hooks are available in the controller code:
5/21/2022
Controller Hook Use
PaystubsList.controller.js hcm.fab.employeelookup.controller.EmployeeDetails~extHookAdjustObjectPageHeader Allows you to

adjust the
EmployeeDetails
object header
More Information
My Bene ts (Version 3/Fiori 2.0)

With the transactional app My Bene ts (Version 3/Fiori 2.0) you can provide a quick and easy overview of the bene t plans in
which an employee is enrolled, ensuring that the employee has all the details of the bene ts offered by their company at their
ngertips.
Key Features
An employee who is concurrently employed can use the app for a chosen personnel assignment
Display the bene t plans in which you are enrolled by plan categories
Display eligible bene t plans for which you have not yet enrolled
Display plan details of a selected bene t plan, for example, your coverage, pre-tax cost, and so on
View the bene t overview or detailed information for any given date
Access links to bene t plan documents to nd information on the de nition of bene t plans
Open the Bene ts Summary statement as a PDF that can be downloaded locally
Technical Features
In addition, this app supports the following technical features and options. Some of these features require additional
components or settings in your system landscape:
This app also runs in standalone mode. To use this feature, see Running Apps in Standalone Mode.

5/21/2022
Front-End Components Delivered with (Product Version Stack) SAP Fiori 2.0 for SAP ERP HCM ( 01 (01/2018) )

PA-FIO-BN
App History: My Bene ts (Version 3/Fiori 2.0)

Initial delivery.
App Implementation: My Bene ts (Version 3/Fiori 2.0)


prerequisites:
5/21/2022
Front-End SAP Fiori 2.0 for SAP ERP UI for ERP HCM > NW750 UIHR002 100 (1 )
Components HCM ( 01 (01/2018) )
Back-End SAP Fiori 1.0 for SAP ERP HCM ERP 605 INT GBX01HR5 605 (n/a )
Components HCM (08 (12/2017))
HCM ERP 605 INT
NW740
Required SAP Notes

OData Service (Version Number) HCMFAB_MYBENEFITS_SRV (0001 )
SAPUI5 Application HCMFAB_BENF_MON
5/21/2022
example roles.
 Note
OData Service (Version Back-End Server: Delivered Authorization Role (PFCG Role) Front-End Server : Assignment to
Number) Authorization Role
HCMFAB_MYBENEFITS_SRV In addition, this role contains authorizations to display the OData service authorization must be
n/a
 Note
In addition, this role contains authorizations to display the
related business data.
More Information
App Extensibility: My Bene ts (Version 3/Fiori 2.0)

Extending the Details view
You can add additional elds in the header section on Details screen
You can add additional elds under the General Information section on the Details screen
Extending the Details view

5/21/2022
To add a eld to the Details screen, the following extensibility entities are available on the different layers. You have to extend
each of these entities according to your speci c business needs:
UI Back End/ABAP
View Extension Point Design Time: Gateway Entity Design Time: Extension Run Time: Superc
Include Be Rede ned
DetailPlan.view.xml extDetPlanheaderContent HCMFAB_MYBENEFITS_SRV HCMFAB_S_BEN_BENEFIT Superclass:

CL_HCMFAB_MYB
Method: ENRICH_
blockPlanDetail.view.xml extPlanDetailGeninfoContent HCMFAB_MYBENEFITS_SRV HCMFAB_S_BEN_BENEFIT Superclass:

CL_HCMFAB_MYB
Method: ENRICH_
Further Extensibility Entities
The following Business Add-In is available for extensibility purposes:
BAdI for HCM Bene t Overview (HCMFAB_BENEFITPLAN_ENRICH)
You can use this BAdI to populate the data for the custom elds that are added to the Bene t Entity.
Extension Includes
In addition to the extension includes described above, the following extension includes are available:
DDIC Extension Include Use
HCMFAB_S_BEN_BENEFIT HCMFAB_S_BEN_BENEFIT_INCL Allows you to add custom elds to the

bene t entity.
For more information about extension includes, see the extensibility documentation for the respective SAP NetWeaver release
on your front-end server at http://help.sap.com/ ori_implementation Extensibility Information for SAP Fiori Extending the UI
Layer UI Extensibility Work ow Checking the SAP-Enabled Extension Options Extension Includes .
More Information
My Leave Requests (Version 3/Fiori 2.0)

With the transactional app My Leave Requests (Version 3) you can enable employees to create and submit leave requests
quickly and exibly, using their desktop or mobile device. The app lets users track the status of their requests and view their
current leave entitlements.
Key Features
5/21/2022
Create leave requests, including partial day leave
Use multi level approval
Create attendances like training, business trip
Select the leave period using an integrated calendar that shows non-working days, working days, public holidays,
approved leave, rejected leave, and leave pending approval
Add a note for the approver
Display a summary of employees leave entitlement, leave taken so far, and available balance
Display employees leave requests and check their approval status
Withdraw or change leave requests
Add and view attachments
An employee who is concurrently employed can use the app for a chosen personnel assignment.
Technical Features
In addition, this app supports the following technical features and options. Some of these features require additional
components or settings in your system landscape:
This app also runs in standalone mode. To use this feature, see Running Apps in Standalone Mode.
Key Features Available on Mobile Devices

You can capture and add a picture or image as an attachment instantly.

Related Apps
Approve Leave Requests (Version 3)

PA-FIO-LEA
5/21/2022
App History: My Leave Requests (Version 3)

 Note
Initial delivery.
App Implementation: My Leave Requests (Version 3)


prerequisites:
5/21/2022
HCM ERP 605 INT
NW740
Required SAP Notes

2103156 Launching Fiori apps in standalone mode
OData Service (Version Number) HCMFAB_LEAVE_REQUEST_CR_SRV (0001 )
SAPUI5 Application HCMFAB_LEAV_MAN
example roles.
5/21/2022
 Note
HCMFAB_LEAVE_REQUEST_CR_SRV In addition, this role contains authorizations to display OData service authorization must be
(0001 ) the related business data. assigned.
SAP_HCMFAB_LEAV_MAN_APP
 Note
In addition, this role contains authorizations to
display the related business data.
More Information
App Extensibility: My Leave Requests (Version 3)

You can extend the app My Leave Requests (Version 3) according to your business needs for different aspects. For this purpose,
the following extensibility options are available:
You can extend the UI of the app by adding elements to the different views.
You can add columns and cells to the entitlements table and the leave request overview table.
You can customize the team calendar control.
You can extend the entities of the app.
5/21/2022
manager.
 Note
Settings for Team Calendar (HCMFAB_B_TEAMCALENDAR_SETTINGS)
You can use this BAdI to customize the team calendar. You can add or remove elements from the UI like the employee
photo or the lter button. You can de ne which event types, which calendar views and employee descriptions are
displayed in the team calendar.
 Note
BAdI: Extensions for Team Calendar ODATA Entities (HCMFAB_B_TEAMCALENDAR)
You can use this BAdI to extend the entities of the team calendar control:
SearchResult
TeamCalendarEmployee
TeamCalendarEvent
TeamCalendarEventType
TeamCalendarUISettings
TeamCalendarView
 Note
Note that the entries affect the team calendars in all apps that use the team calendar control.
BAdI: Enrich Entities of My Leave Request (Version 3) SAP Fiori App (HCMFAB_LRQ_ENRICH)
You can use this BAdI to extend the following entries:
AbsenceType
LeaveRequest
TimeAccount
Extend AbsenceTypeAdditionalField
FileAttachment
AbsenceTypeApproverDefault
Extension Points
5/21/2022
To add additional UI elements to the app, the following extensibility entities are available on the different layers. You have to
extend each of these entities according to your speci c business needs:
UI Back End/ABAP
View Extension Point Design Time: Design Time: Extension Include

Gateway Entity
Creation.view.xml creationMainFieldsExtension LeaveRequest HCMFAB_S_LRQ_REQUEST_LIST_INCL
Allows you to add elements to the creation

view before additional elds section
Creation.view.xml creationPageExtension LeaveRequest HCMFAB_S_LRQ_REQUEST_LIST_INCL
Allows you to add elements at the end of the

creation view
Display.view.xml displayObjectHeaderExtension LeaveRequest HCMFAB_S_LRQ_REQUEST_LIST_INCL
Allows you to add elements to the object

header
Display.view.xml displaySectionsExtension - -
Allows you to add sections to the Display

Page
Overview.view.xml entitlementsToolbarExtension - -
Allows you to add elements to the entitlement

table toolbar
Overview.view.xml entitlementsTableColumnsExtension - -
Allows you to add columns to the entitlements

table
Overview.view.xml entitlementsTableRowsExtension TimeAccount <Name of extension include>
Allows you to add cells to the entitlements

table
Overview.view.xml overviewToolbarExtension - -
Allows you to add elements to the leave

request overview table toolbar
Overview.view.xml overviewTableColumnsExtension - -
Allows you to add columns to the leave

request overview table
Overview.view.xml overviewTableCellsExtension LeaveRequest HCMFAB_S_LRQ_REQUEST_LIST_INCL
Allows you to add cells to the leave request

overview table
Overview.view.xml overviewCalendarLegendExtension - -
Allows you to add further items to the

calendar legend
5/21/2022
UI Back End/ABAP
View Extension Point Design Time: Design Time: Extension Include

Gateway Entity
Overview.view.xml overviewPageExtension LeaveRequest HCMFAB_S_LRQ_REQUEST_LIST_INCL
Allows you to add further elements to the

overview screen
More Information

Leave System Sap Fiori

Uploaded by

Document Information

Original Title

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

Leave System Sap Fiori

Uploaded by

Copyright:

Available Formats

5/21/2022

SAP Fiori 2.0 for SAP HCM

SAP Fiori for SAP Business Suite | 2.0 2018-01

Original content: https://help.sap.com/docs/SAP_FIORI/d59d9f81f4884bf9b115936b92c27202?locale=en-

For more information, please visit the https://help.sap.com/docs/disclaimer.

SAP Fiori 2.0 for SAP ERP HCM

Information Type Product Data

Support Package Stack SPS 01

Delivery Date 01/2018

System Landscape Requirements

SAP Fiori System Landscape Setup Prerequisites

Information Type Product Data

Support Package Stack SP00

Approve Leave Requests (Version 3/Fiori 2.0)

Approve or reject requests (with optional note to the requester)

My Team Calendar (Version 2)

System Landscape Requirements

My Leave Requests (Version 3)

Component for Customer Incidents

App History: Approve Leave Requests (Version 3)

The app has been enhanced as follows:

App Implementation: Approve Leave Requests (Version 3)

System Landscape Requirements

SAP Fiori System Landscape Setup Prerequisites

EHP8 FOR SAP ERP 6.0 - SPS 01 (01/2016)

MSS ADD-ON 1.0 - SPS Initial Shipment Stack

Required SAP Notes

SAP Note Number Description

not available not available

SAP Note Number Description

not available not available

https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F2584

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_LEAVE_REQUEST_APR_SRV (0001 )

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application HCMFAB_LRAPR_IN

Enable App for Access in SAP Fiori Launchpad

Prerequisites for Implementation

You have implemented the SAP Fiori app My Inbox.

Con guration Tasks

SAP Note 2434370

Switch to Activate Non -Work ow Leave Request

Classifying the Work ow Template

Execute transaction code PFTC.

Click the Display (F7) button.

Save the con guration.

Con guring SWFVISU for Intent-based Navigation

Execute transaction code SWFVISU.

Con gure the parameters as below

Table 1: Values for Visualization parameter

Visualization Parameter Value for approval

Perform the two previous steps for Task TS21500097 as well.

Maintaining Task Names and Decision Options

Key Decision Text Nature

Save the record.

Repeat the previous 3 steps for all above-mentioned work ow templates.

Con guring the Target Mapping

Semantic Action Application Title URL ID Parameters

LeaveRequest Approve SAPUI5 Approve /sap/bc/ui5_ui5/sap/hcmfab_lrapr_in hcm.fab.leaveapproval.inbox Name: open

App Extensibility: Approve Leave Requests (Version 3)

You can adjust the object attributes of the header section.