You are on page 1of 220

5/14/2023

SAP Fiori 2.0 for SAP HCM


Generated on: 2023-05-14 20:23:59 GMT+0000

SAP Fiori for Business Suite | 2.0 2022-12

PUBLIC

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


US&state=PRODUCTION&version=2.0 2022-12

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/14/2023

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 20

Delivery Date 12/2022

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 SPS 12

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

This is custom documentation. For more information, please visit the SAP Help Portal 2
5/14/2023
Approve or reject requests (with optional note to the requester)

Allows manager to view leave overlaps for an employee over a speci c period

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)

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

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:

This is custom documentation. For more information, please visit the SAP Help Portal 3
5/14/2023

SAP Fiori for SAP ERP HCM 2.0 SPS 0 (Delivery Date 07/2017)
Initial delivery.

App Implementation: Approve Leave Requests (Version 3)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

This is custom documentation. For more information, please visit the SAP Help Portal 4
5/14/2023

App Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

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

Component Technical Name

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.

This is custom documentation. For more information, please visit the SAP Help Portal 5
5/14/2023
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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_LEAVE_REQUEST_APR_SRV In addition, this role contains authorizations OData service authorization must be
(0001 ) to display 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.

This is custom documentation. For more information, please visit the SAP Help Portal 6
5/14/2023
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.

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 TS12300097 and double-click on Visualization Parameter in the dialog structure on the left
pane.

Con gure the parameters as below

Values for Visualization parameter

Visualization Parameter Value for approval

ACTION approve

QUERY_PARAM00 -

QUERY_PARAM01 -

SEMANTIC_OBJECT LeaveRequest

Perform the two previous steps for Task TS21500003 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

This is custom documentation. For more information, please visit the SAP Help Portal 7
5/14/2023

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.

 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.

Customer Work ow

This con guration task is only relevant when you are using your own customer work ow for approvals.

In this case, you need to perform the above-mentioned steps Classifying the Work ow Template, Con guring SWFVISU for
Intent-based Navigation, and Maintaining Task Names and Decision Options as well.

In addition, execute the following actions to make the implementation of BAdI /IWWRK/ES_WF_WI_BEFORE_UPD_IB created for
SAP Fiori App Approve Leave Request (Version 3) be called for your customer work ow:

1. Open BAdI /IWWRK/ES_WF_WI_BEFORE_UPD_IB in transaction SE18.

2. Go to Enhancement Implementations and open BAdI Implementation HCMFAB_LEAVE_APPROVAL_INBOX (Leave


Approval from My Inbox - Fab Fiori)

3. In Filter Values, add OR STEP_ID = XX AND WORKFLOW_ID = WS9XXXXXXX

Con guring the Target Mapping

As a last step in the process you have to create a Target Mapping in the SAP Fiori Designtime. 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:

This is custom documentation. For more information, please visit the SAP Help Portal 8
5/14/2023

Semantic Application
Object Action Type Title URL ID Paramete

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


Fiori App Leave
Request Mandatory

Value:
embedIn

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:

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 add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

You can check whether an employee is a manager.

Settings for Team Calendar (HCMFAB_B_TEAMCALENDAR_SETTINGS)

This is custom documentation. For more information, please visit the SAP Help Portal 9
5/14/2023
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
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.

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
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

This is custom documentation. For more information, please visit the SAP Help Portal 10
5/14/2023
If there are additional UI controller hooks available in the controller code, you can add own code. For more information, 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 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 Overtime Requests (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app Approve Overtime Requests, you can enable managers to approve or reject overtime requests for
their direct reports or other employees, easily and exibly from their SAP Fiori My Inbox app. Key information for the approval
decision is available.

Key Features
Browse all requests submitted for approval in a personalized inbox.

View details for speci c requests, including information on the overtime requested, as well as additional information
based on the type of the requested overtime.

Approve or reject requests. Depending on the settings, approvers can optionally create a note to the requester.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

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 Overtime Requests

Component for Customer Incidents


PA-FIO-OVT

This is custom documentation. For more information, please visit the SAP Help Portal 11
5/14/2023

App History: Approve Overtime Requests (Fiori 2.0)


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 SPS18 (Delivery Date 06/2022)
Initial delivery.

App Implementation: Approve Overtime Requests (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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:

This is custom documentation. For more information, please visit the SAP Help Portal 12
5/14/2023

App Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

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=F4937

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYOVERTIMEQUOTA_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

Component Technical Name

This is custom documentation. For more information, please visit the SAP Help Portal 13
5/14/2023

Component Technical Name

SAPUI5 Application HCMFAB_OTQ_APR

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYOVERTIMEQUOTA_SRV In addition, this role contains authorizations OData service authorization must be
(0001 ) to display the related business data. assigned.

n/a

 Note
In addition, this role contains
authorizations to display the related
business data.

Con guration Tasks


To be able to implement the app, you must perform the following con guration tasks in the back-end system:

Maintain the activities in Customizing for Personnel Management under Employee Self-Service (Web Dynpro ABAP)
Service-Speci c Settings Working Time My Overtime Requests .

Classifying the Work ow Template

1. Execute transaction PFTC.

This is custom documentation. For more information, please visit the SAP Help Portal 14
5/14/2023
2. On the Task: Maintain screen, enter Workflow Template as Task Type, and 02400057 as Task.

3. Choose Display (F7), then choose Additional Data Classi cation Create .

4. On the Create Classi cation/Lock Ind. screen, in section Classi cation, classify the work ow as General Task using the
radio button.

5. Save the con guration.

Con guring SWFVISU for Intent-Based Navigation

1. Execute transaction SWFVISU and make sure that the following objects and settings are available in the system.

2. Set the Visualization Type of task TS02400044 to Intent-Based Navigation.

3. Choose the task TS02400044 and double-click Visualization Parameter in the dialog pane on the left. Use the following
values for the visualization parameters:

Visualization Parameter Value for Approval

ACTION approveOvertimeQuota

QUERY_PARAM00 -

QUERY_PARAM01 -

SEMANTIC_OBJECT TimeEntry

Maintaining Task Names and Decision Options

For the Approve and Reject buttons to appear in the SAP Fiori My Inbox app of the approver, carry out the following
con guration steps:

1. In Customizing under ABAP Platform SAP Gateway Service Enablement Content Work ow Settings Maintain
Task Names and Decision Options , con gure the approve and reject actions for the work ow template with Work ow
ID WS02400057 and Step ID 0000000038.

2. Create or choose the entry for the work ow template.

3. Double-click Decision Keys in the dialog on the left pane. Add the following entries for the decision keys:

Key Decision Text Nature

1 Approve POSITIVE

4 Reject NEGATIVE

4. Save the record.

 Tip
You can use the standard BAdI Implementation HCMFAB_MYOTQ_APPROVAL_INBOX to in uence the logic of the Approve
and Reject buttons.

Con guring the Target Mapping

This is custom documentation. For more information, please visit the SAP Help Portal 15
5/14/2023
As last step in the con guration process, you must create a target mapping in SAP Fiori Designtime. 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
of Approve Overtime Requests:

Semantic Object TimeEntry

Action approveOvertimeQuota

Application Type SAPUI5 Fiori App

Title Approve Overtime Requests

URL /sap/bc/ui5_ui5/sap/HCMFAB_OTQ_APR

ID hcm.fab.myovertimequotaapproval

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: Approve Overtime Requests (Fiori 2.0)


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 adding additional elds to the header in the overtime request details page.

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.

Further Extensibility Entities

Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

UI Descriptions for My Overtime Requests (HRPT_B_OVT_UI_DESCRIPTIONS)

You can use this BAdI to de ne the compensation types that employees can select when creating an overtime request.
You can also create your individual texts for the attendance quota types you use. In case you do not implement this BAdI,
the app uses the overtime quota types as well as the descriptions that you have maintained in the database tables.

Common BAdI for all HCM SAP Fiori Apps (HCMFAB_B_COMMONS)

You can use this BAdI to enhance HCM SAP Fiori apps delivered with software component UIHR002.

You can add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.

This is custom documentation. For more information, please visit the SAP Help Portal 16
5/14/2023
You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

You can check whether an employee is a manager.

Extension Points

View Extension Point Use

RequestItemsDisplay.view.xml approvalAboveItemsExtension Allows you to add elements to the


Overtime Items section.

RequestNotesDisplay.view.xml approvalAboveNotesExtension Allows you to add elements to the


Note section.

RequestApproval.view.xml approvalObjectHeaderHorizontalExtension Allows you to add elements to the


header of the Approve Request
screen.

RequestApproval.view.xml approvalSectionsExtension Allows you to add sections to the


Approve Request screen.

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
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 .

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)


Abstract for SAP Fiori apps.

With the transactional app Approve Time Events (Fiori 2.0), as a manager, you can approve or reject the time events of your
direct reports from your 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)

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

This is custom documentation. For more information, please visit the SAP Help Portal 17
5/14/2023
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 ( 17 (03/2022) )

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 Time Events (Version 2/Fiori 2.0)

Component for Customer Incidents


PA-FIO-CIO

App History: Approve Time Events (Fiori 2.0)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 01 (Delivery Date 01/2018)
Initial delivery.

App Implementation: Approve Time Events (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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:

This is custom documentation. For more information, please visit the SAP Help Portal 18
5/14/2023
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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

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=F3099

Front-End Server : Activate OData Services

This is custom documentation. For more information, please visit the SAP Help Portal 19
5/14/2023

Component Technical Name

OData Service (Version Number) HCMFAB_TIMEEVENTS_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

Component Technical Name

SAPUI5 Application HCMFAB_TEAPR_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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_TIMEEVENTS_APR_SRV (0001 In addition, this role contains authorizations OData service authorization must be
) to display the related business data. assigned.

n/a

 Note
In addition, this role contains
authorizations to display the related
business data.

Prerequisites for Implementation

This is custom documentation. For more information, please visit the SAP Help Portal 20
5/14/2023
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:

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

This is custom documentation. For more information, please visit the SAP Help Portal 21
5/14/2023

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:

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

This is custom documentation. For more information, please visit the SAP Help Portal 22
5/14/2023

Visualization Parameter Visualization Parameter Value

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:

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:

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.

This is custom documentation. For more information, please visit the SAP Help Portal 23
5/14/2023
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
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
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: Approve Time Events (Fiori 2.0)


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 adding additional elds to the Header section.

You can extend the app by displaying additional information in the Information section.

Extensibility Entities
Business Add-Ins (BAdIs)

The following Business Add-In is available for extensibility purposes:

oData BAdI (HCMFAB_B_TIME_EVENT_APPROVAL)

This is custom documentation. For more information, please visit the SAP Help Portal 24
5/14/2023
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

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 add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

You can check whether an employee is a manager.

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.

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
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 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.

If there are additional UI controller hooks available in the controller code, you can add own code. For more information, 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 UI Controller Hooks .

More Information

This is custom documentation. For more information, please visit the SAP Help Portal 25
5/14/2023
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 Timesheets (Version 3/Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app Approve Timesheets (Version 3/Fiori 2.0) managers can quickly see all pending approvals for their
direct reports, enabling them to easily approve timesheets, using their desktop or mobile device.

Key Features
Review timesheets for all your employees and view time entry compliance at a glance

View all the For Approval, and Already Approved time entries

View details of time entries per employee

View image, designation and contact information of each employee

View details of each time entry for approval

Attributes of the time records for approval are displayed in the Assignment column. For more information, see 2656478
.

Approve or reject records of multiple employees (Mass Approval). When selecting multiple employees, the records of an
employee are displayed as grouped according to the assignment type of the record.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

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 Timesheet (Version 3/Fiori 2.0)

Component for Customer Incidents


PA-FIO-TS

This is custom documentation. For more information, please visit the SAP Help Portal 26
5/14/2023

App History: Approve Timesheets (Version 3/Fiori 2.0)


App history for SAP Fiori app.

Approve Timesheets (Version 3/Fiori 2.0) (Delivery Date 06/2018)


Initial delivery.

App Implementation: Approve Timesheets (Version 3/Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

This is custom documentation. For more information, please visit the SAP Help Portal 27
5/14/2023

App Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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

2710686 Approve Timesheet V3: App Completeness and Translation File


Uploads

On the front-end server, the following SAP notes must be implemented for this app:

SAP Note Number Description

2710686 Approve Timesheet V3: App Completeness and Translation File


Uploads

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=F2585

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_APR_TIMESHEET_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

This is custom documentation. For more information, please visit the SAP Help Portal 28
5/14/2023

Component Technical Name

SAPUI5 Application HCMFAB_APR_TIME

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_APR_TIMESHEET_SRV (0001 In addition, this role contains authorizations OData service authorization must be
) to display the related business data. assigned.

SAP_HCMFAB_APR_TIME_APP

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: Approve Timesheets (Version 3/Fiori 2.0)


Extensibility information for SAP Fiori app.

This is custom documentation. For more information, please visit the SAP Help Portal 29
5/14/2023
You can extend the app according to your business needs for different aspects. For this purpose, the following extensibility
options are available:

Extensibility Entities
Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

BAdI de nition for Approve Timesheet V3 app (HCMFAB_B_APPROVE_TIMESHEET)

You can use this BAdI to do the following:

Get target hours for the period speci ed

Alter time records for approval

Read reportees for the approver

Fetch description text for the eld provided

Fetch Dynamic Tile Info

BAdI for enriching entities of Approve Timesheet (HCMFAB_B_APPR_TIME_ENRICH)

You can use this BAdI to extend the following entities:

Approvaldetails

Approvallist

Employeedetails

MassApproval

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 direct report of a manager.

You can add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

You can check whether an employee is a manager.

Extension Points

To enhance the app, the following extension points are available:

Extension Point Use

ApprovalMaster.view.MasterViewFooterExtension Allows you to add buttons to the footer of Master View

ApprovalDetail.view.DetailViewFooterExtension Allows you to add buttons to the footer of Detail View

ApprovalDetail.view.DetailViewHeaderContentExtension Allows you to add elements to the Detail View header

ApprovalDetail.view.DetailViewIndTableColumnExtension Allows you to add columns to the Individual Approval Table

ApprovalDetail.view.DetailViewIndTableCellExtension Allows you to add cells to the Individual Approval Table

This is custom documentation. For more information, please visit the SAP Help Portal 30
5/14/2023

Extension Point Use

ApprovalDetail.view.DetailViewIndTableActionsExtension Allows you to add action buttons to the Individual Approval Table

ApprovalDetail.view.DetailViewMassTableColumnExtension Allows you to add columns to the Mass Approval Table

ApprovalDetail.view.DetailViewMassTableCellExtension Allows you to add cells to the Mass Approval Table

ApprovalDetail.view.DetailViewMassTableActionsExtension Allows you to add action buttons to the Mass Approval Table

Customize elds displayed in assignment


In the SAP Customizing Implementation Guide go to Cross-Application Components Time Sheet Settings for All User
Interfaces Approval Procedure Approve Working Times De ne Field Selection for Individual Approval View . The Field
Selection Attribute, Field Customizing allows you to select the elds to be displayed in the Assignment quick view (a pop-over
displayed when clicking the assignment name hyperlink in detail view).

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 .

Employee Lookup (Version 2/Fiori 2.0)


Abstract for SAP Fiori apps.

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.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

This is custom documentation. For more information, please visit the SAP Help Portal 31
5/14/2023
For more information, see the app implementation document of this app.

Component for Customer Incidents


PA-FIO-LKP

App History: Employee Lookup (Version 2)


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.

App Implementation: Employee Lookup (Version 2)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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.

This is custom documentation. For more information, please visit the SAP Help Portal 32
5/14/2023
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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

2103156 Launching Fiori apps in standalone mode

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=F1383A

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_EMPLOYEELOOKUP_SRV (0001 )

This is custom documentation. For more information, please visit the SAP Help Portal 33
5/14/2023
For more information about how to activate the OData service, see Front-End Server: Activate OData Services .

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application HCMFAB_EMP_LKP

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_EMPLOYEELOOKUP_SRV (0001 In addition, this role contains authorizations OData service authorization must be
) to display the related business data. assigned.

SAP_HCMFAB_EMP_LKP_APP

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

This is custom documentation. For more information, please visit the SAP Help Portal 34
5/14/2023

App Extensibility: Employee Lookup (Version 2)


Extensibility information for SAP Fiori app.

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.

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:

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 an employee.

You can de ne who is a direct report of a manager.

You can de ne who is the manager of an employee.

You can add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

You can check whether an employee is a manager.

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

This is custom documentation. For more information, please visit the SAP Help Portal 35
5/14/2023

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

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

This is custom documentation. For more information, please visit the SAP Help Portal 36
5/14/2023
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
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 hooks are available in the controller code:

Controller Hook Use

PaystubsList.controller.js hcm.fab.employeelookup.controller.EmployeeDetails~extHookAdjustObjectPageHeader Allows you to


adjust the
EmployeeDetails
object header

If there are additional UI controller hooks available in the controller code, you can add own code. For more information, 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 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 .

My Addresses (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Addresses (Fiori 2.0) you can create, display, edit and delete your address data, such as
addresses of the Permanent Residence, Temporary Residence, Home Address, and Emergency Address. The app helps you to
keep your address data up to date.

Key Features
Display an overview of current address data

Create or edit address data

Set a validity date for data record

Delete address data

Maintain data for another employee on-behalf

An employee who is concurrently employed can use the app for a chosen personnel assignment.

Localization
The following localizations (country speci c screens for editing data) are available:

International Version Sweden Croatia

This is custom documentation. For more information, please visit the SAP Help Portal 37
5/14/2023
Germany Saudi Arabia Romania

Switzerland Singapore Slovenia

Austria Thailand Public Sector Germany

Spain Hong Kong Public Sector France

Netherlands China Public Sector USA

France Argentina Public Sector Belgium

Canada Slovakia United Arab Emirates

United Kingdom Mexico Bulgaria

Denmark Russia Egypt

USA Indonesia Kuwait

Ireland Ukraine Oman

Belgium Brazil Qatar

Australia Colombia United Nations

Malaysia Chile

Italy India

South Africa South Korea

Venezuela Taiwan

Thailand New Zealand

Czech Republic Finland

Portugal Poland

Hungary Philippines

Norway

Japan

Sweden

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

For more information, see the app implementation document of this app.

Related Apps

This is custom documentation. For more information, please visit the SAP Help Portal 38
5/14/2023
From a business perspective, the following apps are related to this app:

My Internal Data (Fiori 2.0)

My Bank Details (Fiori 2.0)

My Communication Data (Fiori 2.0)

My Family Members (Fiori 2.0)

My Personal Data (Fiori 2.0)

My Pro le (Fiori 2.0)

Component for Customer Incidents


PA-FIO-PER

App History: My Addresses (Fiori 2.0)


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 7 (Delivery Date 7/2019)

New Key Features New localization (country speci c screen for editing data)
is available

Allows you to use the app in the following new country


version:

Russia

An employee is allowed to maintain data for another


employee on-behalf.

New Extensibility Options New Extension Points to add additional elds to the forms
(Display and Edit) of the new localization.

You can use the BAdI HCMFAB_B_PERSINFO_SETTINGS


to disable the function to change the employee picture. You
can also set the MIME types of the employee picture that
an employee can upload.

You can use the BAdI HCMFAB_B_COMMON to con gure the


on-behalf scenario.

SAP Fiori for SAP ERP HCM 2.0 SPS 4 (Delivery Date 10/2018)

New Key Feature New localization (country speci c screen for editing data) is
This is custom documentation. For more information, please visit the SAP Help Portal 39
5/14/2023
available

Allows you to use the app in the following new country version:

Norway

New Extensibility Options Extension Points to add additional elds to the forms (Display and
Edit) of the new localization.

SAP Fiori for SAP ERP HCM 2.0 SPS 3 (Delivery Date 06/2018)

New Key Feature New localizations ((country speci c screens for editing data) are
available

Allows you to use the app in the following new country versions:

Public Sector Germany

Public Sector France

Public Sector USA

Public Sector Belgium

Switzerland

Spain

Italy

South Africa

Venezuela

Czech Republic

Portugal

Hungary

Sweden

Saudi Arabia

Singapore

Thailand

China

Slovakia

Mexico

Ukraine

Brazil

Colombia

Chile

India

Taiwan

Finland

Poland

This is custom documentation. For more information, please visit the SAP Help Portal 40
5/14/2023
Philippines

Croatia

Romania

Slovenia

United Arab Emirates

Bulgaria

Egypt

Kuwait

Oman

Quatar

United Nations

New Extensibility Options


Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

SAP Fiori for SAP ERP HCM 2.0 SPS 0 (Delivery Date 04/2018)
Initial delivery.

App Implementation: My Addresses (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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.

This is custom documentation. For more information, please visit the SAP Help Portal 41
5/14/2023
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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

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=F3004

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYADDRESSES_SRV (0001 )

This is custom documentation. For more information, please visit the SAP Help Portal 42
5/14/2023
For more information about how to activate the OData service, see Front-End Server: Activate OData Services .

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application HCMFAB_ADRS_MAN

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYADDRESSES_SRV (0001 ) In addition, this role contains authorizations OData service authorization must be
to display the related business data. assigned.

SAP_HCMFAB_MYADDRESSES_APP

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

This is custom documentation. For more information, please visit the SAP Help Portal 43
5/14/2023

App Extensibility: My Addresses (Fiori 2.0)


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 con gure your own country speci c entities.

You can ll your customer speci c extension includes.

You can add additional elds to the country speci c forms used to display/edit the data.

You can adapt the behavior of elds delivered in the standard UI con guration.

You can in uence the behavior of the app with regards to the employee picture.

Extensibility Entities
Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

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 specify for which employees a person (personnel number) is allowed to maintain data on-behalf.

You can specify how the system checks if a given employee number is allowed/relevant to be used in an on-behalf
scenario for the current user.

You can de ne who is the manager of an employee.

You can add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button. You can also enable the on-behalf functionality.

You can check whether an employee is a manager.

BAdI: HR FIori: PersInfo Con gurations (HCMFAB_B_PERSINFO_CONFIG)

You can use this BAdI to con gure your own country speci c entities to the My Addresses OData Service
HCMFAB_MYADDRESSES.

 Note
This BAdi is also relevant for the OData services of the other Personal Information SAP Fiori Apps.

In the standard system, SAP provides country-speci c BAdI implementations for a number of countries. For more
information see documentation of BAdI HCMFAB_B_PERSINFO_CONFIG.

BAdI for Enhancement of SAP Fiori App My Addresses (HCMFAB_B_MYADDRESSES)

You can use this BAdI to ll your customer speci c extension includes used in the My Addresses SAP Fiori App.

HR Fiori: PersInfo Settings (UI-relevant) (HCMFAB_B_PERSINFO_SETTINGS)

You can use this BAdI to disable the function to change the employee picture.

This is custom documentation. For more information, please visit the SAP Help Portal 44
5/14/2023
You can also set the MIME types of the employee picture that an employee can upload.

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: Gateway Entity Design Time: Extens

99_Display_Default_V001.view.xml view.extensionFormContent HCMFAB_S_PERS_A


Address
Allows you to add additional elds
to the international form (Display) AddressDefault

99_Edit_Default_V001.view.xml view.extensionFormContent Address HCMFAB_S_PERS_A

Allows you to add additional elds AddressDefault


to the international form (Edit)

++_Edit_Default_V001.view.xml view.extensionFormContent Address++ HCMFAB_S_PERS_A

++ = Number of county version Allows you to add additional elds Address++Default ++ = Number of coun
to the country version form (Edit)
The following localizations are available ++ = Number of county
version
(01) Germany

(02) Switzerland

(03) Austria

(04) Spain

(05)Netherlands

(06) France

(07) Canada

(08) Great Britain

(09) Denmark

(10) USA

(11) Ireland

(12) Belgium

(13) Australia

(14) Malaysia

(15) Italy

(16) South Africa

(17) Venezuela

(18) Czech Republic

This is custom documentation. For more information, please visit the SAP Help Portal 45
5/14/2023

UI Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time: Extens

(19) Portugal

(20) Norway

(21) Hungary

(22) Japan

(23) Schweden

(24) Saudi Arabia

(25) Singapore

(26) Thailand

(27) Hong Kong

(28) China

(29) Argentina

(31) Slovakia

(32) Mexico

(33) Russia

(34) Indonesia

(36) Ukraine

(37) Brazil

(38) Colombia

(39) Chile

(40) India

(41) South Korea

(42) Taiwan

(43) New Zealand

(44) Finland

(46) Poland

(48) Philippines

(58) Croatia

(61) Romania

(62) Slovenia

(OE) Public Sector Germany

(FP) Public Sector France

(UP) Public Sector USA

(BP) Public Sector Belgium

(AE) United Arab Emirates

This is custom documentation. For more information, please visit the SAP Help Portal 46
5/14/2023

UI Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time: Extens

(BG) Bulgaria

(EG) Egypt

(KW) Kuwait

(OM)Oman

(QA) Qatar

(UN) United Nations

++_Display_Default_V001.view.xml view.extensionFormContent HCMFAB_S_PERS_A


Address++
++ = Number of country version Allows you to add additional elds ++ = Number of coun
to the international form (Display) Address++Default

++ = Number of county
version

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
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 .

Adapt Fields of the Standard UI Con guration

You can adapt the behavior of the elds delivered with the standard UI con guration of the app in following way:

Set editable (Field property Can be edited)

Set invisible (Field property Invisible)

Set read-only (Field property Output Only)

Set mandatory (Field Property Required Entry)

To do so, use the view VT588MUIFPROPC (Customer: Field Properties of UI Fields) as described blow.

1. Open view VT588MUIFPROPC in transaction SM31 and choose the relevant Work Area. In this case this is Infotype
0006.

2. Choose New Entries and enter the following data:

a. Context: ESSWDAPERS

b. IT Version: Select the relevant country.

c. Subtype: Choose the relevant subtype.

d. UI Structure Name/Field Name: Choose relevant structure and eld.

e. Field Property: Choose the property you want to assign to the eld.

3. Repeat step 2 for each eld where you want to change the standard behavior.

4. Save your entries.

More Information
This is custom documentation. For more information, please visit the SAP Help Portal 47
5/14/2023
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 .

My Bank Details (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Bank Details (Fiori 2.0) you can create, disiplay and change your bank information, such as Main
Bank, Travel Expenses or Other Bank. The app helps you to keep your bank information for the bank transfer from payroll, for
travel expenses from travel expense management, and for special purposes up to date.

Key Features
Display an overview of the current bank information

Create or edit bank information

Set a validity date for data record

Delete bank information

Maintain data for another employee on-behalf

An employee who is concurrently employed can use the app for a chosen personnel assignment.

Localization
The following localizations (country and region speci c screens for editing data) are available:

Country/Region Code Country/Region Country/Region Code Country/Region

99 International Version 31 Slovakia

01 Germany 32 Mexico

02 Switzerland 33 Russia

03 Austria 34 Indonesia

04 Spain 36 Ukraine

05 Netherlands 37 Brazil

06 France 38 Colombia

07 Canada 39 Chile

08 Great Britain 40 India

10 USA 41 South Korea

11 Ireland 42 Taiwan

12 Belgium 43 New Zealand

13 Australia 44 Finland

14 Malaysia 45 Greece

15 Italy 46 Poland

This is custom documentation. For more information, please visit the SAP Help Portal 48
5/14/2023

Country/Region Code Country/Region Country/Region Code Country/Region

16 South Africa 48 Philippines

17 Venezuela 58 Croatia

18 Czech Republic 61 Romania

19 Portugal 62 Slovenia

20 Norway AE United Arabic Emirates

21 Hungary BG Bulgaria

22 Japan EG Egypt

23 Sweden KW Kuwait

24 Saudi Arabia OM Oman

25 Singapore QA Qata

26 Thailand UN Nonpro t Organization

27 Hong Kong

28 China

29 Argentina

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

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 Addresses (Fiori 2.0)

My Communication Data (Fiori 2.0)

My Personal Data (Fiori 2.0)

My Family Members (Fiori 2.0)

My Internal Data (Fiori 2.0)

My Pro le (Fiori 2.0)

This is custom documentation. For more information, please visit the SAP Help Portal 49
5/14/2023

Component for Customer Incidents


PA-FIO-PER

App History: My Bank Details (Fiori 2.0)


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 8 (Delivery Date 10/2019)

New Key Features


New localizations (country/region speci c screens for
editing data) are available

Allows you to use the app in the following new


country/region versions:

Sweden

Thailand

Slovakia

Ukraine

South Korea

Finland

Philippines

Croatia

Romania

Slovenia

Bulgaria

Greece

New Extensibility Options New Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

SAP Fiori for SAP ERP HCM 2.0 SPS 7 (Delivery Date 07/2019)

New Key Feature An employee is allowed to maintain data for another employee on-
behalf.

New Key Feature New localizations (country/region speci c screens for editing data)
are available

This is custom documentation. For more information, please visit the SAP Help Portal 50
5/14/2023
Allows you to use the app in the following new country/region
versions:

Argentina

Chile

Columbia

Egypt

Hong Kong

Hungary

Indonesia

Ireland

Kuwait

Malaysia

New Zealand

Oman

Portugal

Qatar

Singapore

South Africa

Taiwan

Venezuela

Nonpro t Organization (NPO)

New Extensibility Options You can use the BAdI HCMFAB_B_COMMON to con gure the on-
behalf scenario.

New Extensibility Options


Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

New Extensibility Options You can use the BAdI HCMFAB_B_PERSINFO_SETTINGS to


disable the function to change the employee picture. You can also
set the MIME types of the employee picture that an employee can
upload.

SAP Fiori for SAP ERP HCM 2.0 SPS 6 (Delivery Date 04/2019)

New Key Feature New localizations (country speci c screens for editing data) are
available

Allows you to use the app in the following new country versions:

Belgium

Italy

Czech Republic

Japan

This is custom documentation. For more information, please visit the SAP Help Portal 51
5/14/2023
Russia

Poland

New Extensibility Options


Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

SAP Fiori for SAP ERP HCM 2.0 SPS 5 (Delivery Date 01/2019)

New Key Feature New localizations (country speci c screens for editing data) are
available

Allows you to use the app in the following new country versions:

Austria

Netherlands

Norway

Spain

Switzerland

Canada

Mexico

Australia

United Arabic Emirates

Saudi Arabia

New Extensibility Options


Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

SAP Fiori for SAP ERP HCM 2.0 SPS 4 (Delivery Date 10/2018)

New Key Feature New localizations (country speci c screens for editing data) are
available

Allows you to use the app in the following new country versions:

Brazil

India

France

China

New Extensibility Options


Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

SAP Fiori for SAP ERP HCM 2.0 SPS 2 (Delivery Date 04/2018)
Initial delivery.

This is custom documentation. For more information, please visit the SAP Help Portal 52
5/14/2023

App Implementation: My Bank Details (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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


This is custom documentation. For more information, please visit the SAP Help Portal 53
5/14/2023
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:

SAP Note Number Description

not available not available

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=F3112

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYBANKDETAILS_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

Component Technical Name

SAPUI5 Application HCMFAB_BANK_MAN

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.

This is custom documentation. For more information, please visit the SAP Help Portal 54
5/14/2023
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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYBANKDETAILS_SRV (0001 In addition, this role contains authorizations to OData service authorization must be
) display the related business data. assigned.

SAP_HCMFAB_MYBANKDETAILS_APP

 Note
In addition, this role contains authorizations
to display the related business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Bank Details (Fiori 2.0)


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 con gure your own country speci c entities.

You can ll your customer speci c extension includes.

You can add additional elds to the country speci c forms used to display/edit the data.

You can adapt the behavior of elds delivered in the standard UI con guration.

You can in uence the behavior of the app with regards to the employee picture.

Extensibility Entities
Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

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 specify for which employees a person (personnel number) is allowed to maintain data on-behalf.

You can specify how the system checks if a given employee number is allowed/relevant to be used in an on-behalf
scenario for the current user.

This is custom documentation. For more information, please visit the SAP Help Portal 55
5/14/2023
You can de ne who is the manager of an employee.

You can add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button. You can also enable the on-behalf functionality.

You can check whether an employee is a manager.

BAdI: HR FIori: PersInfo Con gurations (HCMFAB_B_PERSINFO_CONFIG)

You can use this BAdI to con gure your own country speci c entities to the My Bank Data OData Service
HCMFAB_MYBANKDETAILS.

 Note
This BAdi is also relevant for the OData services of the other Personal Information SAP Fiori Apps.

In the standard system, SAP provides country-speci c BAdI implementations for a number of countries. For more
information see documentation of BAdI HCMFAB_B_PERSINFO_CONFIG.

BAdI for Enhancement of SAP Fiori App My Bank Data (HCMFAB_B_MYBANKDETAILS)

You can use this BAdI to ll your customer speci c extension includes used in the My Bank Data SAP Fiori App.

HR Fiori: PersInfo Settings (UI-relevant) (HCMFAB_B_PERSINFO_SETTINGS)

You can use this BAdI to disable the function to change the employee picture.

You can also set the MIME types of the employee picture that an employee can upload.

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: Gateway Entity Design Time: Ex

99_Display_Default_V001.view.xml view.extensionFormContent HCMFAB_S_PER


BankDetail
Allows you to add additional elds
to the international form (Display) BankDetailDefault

99_Edit_Default_V001.view.xml view.extensionFormContent BankDetail HCMFAB_S_PER

Allows you to add additional elds BankDetailDefault


to the international form (Edit)

++_Display_Default_V001.view.xml view.extensionFormContent BankDetail++ HCMFAB_S_PER

++ = number of country version Allows you to add additional elds BankDetail++Default


to the country version form
The following localizations are available:
(Display)

(01) (31) Slovakia


Germany
(32) Mexico

This is custom documentation. For more information, please visit the SAP Help Portal 56
5/14/2023

UI Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time: Ex

(02) (33) Russia


Switzerland
(34)
(03) Austria Indonesia

(04) Spain (36) Ukraine

(05) (37) Brazil


Netherlands
(38)
(06) France Colombia

(07) Canada (39) Chile

(08) Great (40) India


Britain
(41) South
(10) USA Korea

(11) Ireland (42) Taiwan

(12) (43) New


Belgium Zealand

(13) (44) Finland


Australia
(45) Greece
(14)
(46) Poland
Malaysia
(48)
(15) Italy
Philippines
(16) South
Africa (58) Croatia

(61)
(17)
Romania
Venezuela

(18) Czech (62)

Republic Slovenia

(AE) United
(19)
Arabic
Portugal
Emirates
(20) Norway
(BG)
(21) Bulgaria
Hungary
(EG) Egypt
(22) Japan
(KW) Kuwait
(23)
(OM) Oman
Sweden

(24) Saudi (QA) Qatar

Arabia (UN)
Nonpro t
(25)
Organization
Singapore
(NPO)
(26)
Thailand

(27) Hong
Kong

(28) China

(29)
Argentina

This is custom documentation. For more information, please visit the SAP Help Portal 57
5/14/2023

UI Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time: Ex

++_Edit_Default_V001.view.xml view.extensionFormContent HCMFAB_S_PER


BankDetail++
++ = number of country version Allows you to add additional elds
to the country version form (Edit) BankDetail++Default

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
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 .

Adapt Fields of the Standard UI Con guration

You can adapt the behavior of the elds delivered with the standard UI con guration of the app in following way:

Set editable (Field property Can be edited)

Set invisible (Field property Invisible)

Set read-only (Field property Output Only)

Set mandatory (Field Property Required Entry)

To do so, use the view VT588MUIFPROPC (Customer: Field Properties of UI Fields) as described blow.

1. Open view VT588MUIFPROPC in transaction SM31 and choose the relevant Work Area. In this case this is Infotype
0009.

2. Choose New Entries and enter the following data:

a. Context: ESSWDAPERS

b. IT Version: Select the relevant country.

c. Subtype: Choose the relevant subtype.

d. UI Structure Name/Field Name: Choose relevant structure and eld.

e. Field Property: Choose the property you want to assign to the eld.

3. Repeat step 2 for each eld where you want to change the standard behavior.

4. Save your entries.

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 .

My Bene ts (Version 3/Fiori 2.0)


Abstract for SAP Fiori apps.

This is custom documentation. For more information, please visit the SAP Help Portal 58
5/14/2023
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.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

For more information, see the app implementation document of this app.

Component for Customer Incidents


PA-FIO-BN

App History: My Bene ts (Version 3/Fiori 2.0)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 01 (Delivery Date 01/2018)
Initial delivery.

This is custom documentation. For more information, please visit the SAP Help Portal 59
5/14/2023

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


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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


This is custom documentation. For more information, please visit the SAP Help Portal 60
5/14/2023
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:

SAP Note Number Description

not available not available

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=F1316A

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYBENEFITS_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

Component Technical Name

SAPUI5 Application HCMFAB_BENF_MON

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.

This is custom documentation. For more information, please visit the SAP Help Portal 61
5/14/2023
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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYBENEFITS_SRV (0001 ) In addition, this role contains authorizations OData service authorization must be
to display the related business data. assigned.

n/a

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Bene ts (Version 3/Fiori 2.0)


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:

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


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_

This is custom documentation. For more information, please visit the SAP Help Portal 62
5/14/2023

UI Back End/ABAP

blockPlanDetail.view.xml extPlanDetailGeninfoContent HCMFAB_MYBENEFITS_SRV HCMFAB_S_BEN_BENEFIT Superclass:


CL_HCMFAB_MYB

Method: ENRICH_

Further Extensibility Entities


Business Add-Ins (BAdIs)

The following Business Add-In is available for extensibility purposes:

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 set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

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
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 .

My Bene ts Enrollment (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Bene ts Enrollment (Fiori 2.0) you can enroll in bene t plans, edit existing plans, and stop
participating in plans.

Key Features
Select enrollment event, and choose from the available bene t plans

View details of the bene t plan including status, start date, coverage, and frequency. You can choose the columns to be
displayed.

This is custom documentation. For more information, please visit the SAP Help Portal 63
5/14/2023
Choose the bene t plan by opting in to the plan

Stop participating in the bene t plan by opting out of the plan

Simulate a payslip prior to completing enrollment to see the effect of plan selections on gross pay

Review your selections prior to enrollment

Print or email a con rmation statement after enrollment

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 enables you to upload documents. For security reasons, we strongly recommend that you install a virus scanner
in your system landscape. For more information, see Virus Scanning.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

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 Bene ts(version 3/Fiori 2.0)

Component for Customer Incidents


PA-FIO-BN

App History: My Bene ts Enrollment (Fiori 2.0)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 7 (Delivery Date 7/2019)
Initial delivery.

This is custom documentation. For more information, please visit the SAP Help Portal 64
5/14/2023

App Implementation: My Bene ts Enrollment (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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


This is custom documentation. For more information, please visit the SAP Help Portal 65
5/14/2023
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:

SAP Note Number Description

not available not available

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=F3718

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_BEN_ENROLLMENT_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

Component Technical Name

SAPUI5 Application HCMFAB_BEN_ENRL

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.

This is custom documentation. For more information, please visit the SAP Help Portal 66
5/14/2023
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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_BEN_ENROLLMENT_SRV (0001 In addition, this role contains authorizations OData service authorization must be
) to display the related business data. assigned.

SAP_HCMFAB_BEN_ENRL_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 created the required Terms and Conditions Agreement using the Business Add-In BAdI: Save Terms and
Conditions Agreement part of Personnel Management Bene ts Bene ts (Fiori) .

Using the Customizing activity De ne Enrollment Events and T&C Doc Object part of Personnel Management
Bene ts Bene ts (Fiori) , you have done the following:

Added the required enrollment events.

Speic ed the documentation object containing the Terms and Conditions for each event.

You have implemented the following SAP Notes:

2041156

If you are using EHP5 (EA-HR 605) release, implement the 2749663 .

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Bene ts Enrollment (Fiori 2.0)


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:

Extensibility Entities

This is custom documentation. For more information, please visit the SAP Help Portal 67
5/14/2023

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

PlanDetail.view ExtPlanDetailHeaderContent Allows you to add content in


the Header area in the
bene t detail page

PlanDetail.view ExtPlanDetailCommonToolBarItm Allows you to add buttons to


footer toolbar in the plan
detail page

Enrollment.view ExtEnrollmentPageToolBar Allows you to add buttons in


page header toolbar
common to Select Events,
Select Bene ts and Review
Bene ts pages

CreditPlanDetail.fragment ExtCreditPlanDetailObjPageSection Allows you to add object


page section in the detail
page for credit

FSAPlanDetail.fragment ExtCreditPlanDetailObjPageSection Allows you to add object


page section in the detail
page for FSA

HealthPlanDetail.fragment ExtCreditPlanDetailObjPageSection Allows you to add object


page section in the detail
page for health

InsurancePlanDetail.fragment ExtCreditPlanDetailObjPageSection Allows you to add object


page section in the detail
page for insurance

MiscPlanDetail.fragment ExtCreditPlanDetailObjPageSection Allows you to add object


page section in the detail
page for miscellaneous
topics

SavingPlanDetail.fragment ExtCreditPlanDetailObjPageSection Allows you to add object


page section in the detail
page for saving

StockPlanDetail.fragment ExtCreditPlanDetailObjPageSection Allows you to add object


page section in the detail
page for stock

BenefitEvent.fragment ExtSelectEventTblColumn Allows you to add columns


in the event list table part of
the Select Event page

BenefitEvent.fragment ExtSelectEventTblColumnListItemCell Allows you to add cells in


the event list table part of
Select Event page

BenefitEvent.fragment ExtSelectEventBottomOfPage Allows you to add content at


the bottom of the Select
Event page

This is custom documentation. For more information, please visit the SAP Help Portal 68
5/14/2023

View Extension Point Use

EOIDialog.fragment ExtEOIDialogContent Allows you to add content in


the Evidence of Insurability
pop up dialog

OfferSortViewSettingDialog.fragment ExtSelectBenefitTblSortItem Allows you add columns for


sorting in the view setting
dialog of the plan list table
part of Select Bene ts page

ReviewBenefits.fragment ExtReviewBenefitTopOfPage Allows you to add content at


the top of the Review
Bene ts page

ReviewBenefits.fragment ExtReviewBenefitOptedOutPlanFormElement Allows you to add content in


the opted-out panel in the
Review Selections and
Enroll page

ReviewBenefits.fragment ExtReviewBenefitNewPlanFormElement Allows you to add content in


the opted-in panel in the
Review Selections and
Enroll page

ReviewBenefits.fragment ExtReviewBenefitChangedPlanFormElement Allows you to add content in


the changed-plans panel in
the Review Selections and
Enroll page

ReviewBenefits.fragment ExtReviewBenefitExistingPlanFormElement Allows you to add content in


existing-plans panel in the
Review Selections and
Enroll page

ReviewBenefits.fragment ExtReviewBenefitBottomOfPage Allows you to add content at


the bottom of the Review
Bene ts page

SelectBenefits.fragment ExtSelectBenefitTblToolBarItm Allows you to add buttons in


the bene t list table part of
Select Bene ts page

SelectBenefits.fragment ExtSelectBenefitTblColumn Allows you to add columns


in the bene ts list table part
of Select Bene ts page

SelectBenefits.fragment ExtSelectBenefitTblColumnListItemCell Allows you to add cells in


the bene ts list table part
of Select Bene ts page

SelectBenefits.fragment ExtSelectBenefitBottomOfPage Allows you to add content at


the bottom of the Select
Bene ts 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
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 .

More Information

This is custom documentation. For more information, please visit the SAP Help Portal 69
5/14/2023
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 .

My Career (Registered Candidate)


Abstract for SAP Fiori apps.

With the transactional app My Career (Registered Candidate) you can store your pro le, search for employment opportunities,
submit applications, and track the processing status of your applications.

Key Features
View available jobs

Search for required jobs using free-text search, and using lters

Apply for jobs

Track your applications

Save jobs as favorites, and apply later

Maintain your pro le, including attachments

Delete applications

Display or hide your pro le from recruiters

Create job agents that will notify you when a job is posted with the speci ed job criteria

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 enables you to upload documents. For security reasons, we strongly recommend that you install a virus scanner
in your system landscape. For more information, see Virus Scanning.

System Landscape Requirements


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 enhancement package 7 for SAP E-
Recruiting 6.0 (18 (03/2019))

 SAP enhancement package 7 for SAP


ERP 6.0 ( 18 (03/2019))

SAP enhancement package 8 for SAP E-


Recruiting 6.0 (12 (04/2019))

SAP enhancement package 8 for SAP ERP 6.0


(12 (04/2019))

This is custom documentation. For more information, please visit the SAP Help Portal 70
5/14/2023
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 for SAP ERP HCM add-ons 1.0 ( Initial
Shipment Stack )

For more information, see the app implementation document of this app.

Component for Customer Incidents


PA-ER

App History: My Career (Registered Candidate)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 06 (Delivery Date 04/2019)
Initial delivery.

App Implementation: My Career (Registered Candidate)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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) SAP NETWEAVER 7.4 - SPS 21 (01/2019)

 

SAP NETWEAVER 7.5 - SPS 14 (03/2019)

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.

This is custom documentation. For more information, please visit the SAP Help Portal 71
5/14/2023
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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori for SAP ERP UI FOR ERP HCM ADDON UIHRADD 100 (0000 )
HCM add-ons 1.0 (
Initial Shipment Stack
)

Back-End Components SAP enhancement E-Recruiting ERECRUIT 617


package 7 for SAP (0016 )
 E-
E-Recruiting 6.0
Recruiting ERECRUIT 617
(18 (03/2019))
(0016 )
E-Recruiting
 SAP
enhancement E-Recruiting
package 7 for SAP Standalone
ERP 6.0 ( 18
(03/2019))

SAP enhancement
package 8 for SAP
E-Recruiting 6.0
(12 (04/2019))

SAP enhancement
package 8 for SAP
ERP 6.0 (12
(04/2019))

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:

SAP Note Number Description

not available not available

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=F3613


This is custom documentation. For more information, please visit the SAP Help Portal 72
5/14/2023

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) RCF_CANDIDATE_SRV (0001 )

RCF_URM_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

Component Technical Name

SAPUI5 Application RCF_CANDIDATE

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

RCF_CANDIDATE_SRV (0001 ) In addition, this role contains authorizations OData service authorization must be
to display the related business data. assigned.
RCF_URM_SRV (0001 )
n/a

 Note
In addition, this role contains
authorizations to display the related
business data.

This is custom documentation. For more information, please visit the SAP Help Portal 73
5/14/2023

Prerequisites for Implementation


Before implementing the app, you must ensure the following:

You are using release ERECRUIT 617 SP16 or above.

You have set the value of RECFA FIOUI to X in the Customizing Set System Parameters, that is part of SAP E-
Recruiting Technical Settings .

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Career (Registered Candidate)


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:

Business Add-Ins (BAdIs)


The following Business Add-In is available for extensibility purposes:

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 set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

BADI_RCF_FIO_POSTING_IMAGE

You can use this BAdI to display an image for a Job Posting. To use this BAdI, excecute the Customizing BAdI: Specify
Image for Job in My Careers app part of SAP E-Recruiting Technical Settings User Interfaces Fiori UI .

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 using the BAdI BADI_RCF_FIO_ENRICH according to your speci c business needs:

UI Back End/ABAP

View Extension Point / Design Time: Methods to be Implemented for BAdI


Gateway Entity BADI_RCF_FIO_ENRICH
Purpose

CandProfile.view.xml CandProfileViewSectionExtension RCF_CANDIDATE ENRICH_CAND_EDUCATION

Allows ou to add a section in the candidate ENRICH_CAND_WORKEXPERIENCE


pro le view.

Application.view.xml ApplicationViewListItemExtension RCF_CANDIDATE Not applicable. Only front-end changes

Allows you to change list item in the


application view

This is custom documentation. For more information, please visit the SAP Help Portal 74
5/14/2023

UI Back End/ABAP

View Extension Point / Design Time: Methods to be Implemented for BAdI


Gateway Entity BADI_RCF_FIO_ENRICH
Purpose

Application.view.xml FavouriteViewListItemExtension RCF_CANDIDATE Not applicable. Only front-end changes

Allows you to change the list item in the


favourites view

JobSearch.view.xml SearchResultListExtension RCF_CANDIDATE ENRICH_JOB_HITLIST

Allows you to edit the search result list on


Job search View

JobDetails.view.xml JobDetailsHdrExtension RCF_CANDIDATE ENRICH_JOB_DETAILS

Allows you to enhance the header details of


the view JobDetails

JobDetails.view.xml JobDetailsContentExtension RCF_CANDIDATE ENRICH_JOB_DECRIPTIONSENRICH_

Allows you to enhance the content details of


the view JobDetails

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 .

My Career (Unregistered Candidate)


Abstract for SAP Fiori apps.

With the transactional app My Career (Unregistered Candidate) you can browse through the available jobs, view job details, and
share the jobs. To apply for a job, register and continue using the transactional app My Career (Registered Candidate).

Key Features
View available jobs

Search for required jobs using free-text search, and using lters

Share jobs

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 Career (Registered Candidate)

This is custom documentation. For more information, please visit the SAP Help Portal 75
5/14/2023

System Landscape Requirements


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) ()

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) ( )

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 Career (Registered Candidate)

Component for Customer Incidents

App History: My Career (Unregistered Candidate)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 11 (Delivery Date 09/2020)
Initial delivery.

App Implementation: My Career (Unregistered Candidate)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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)

Each SAP Fiori app consists of front-end components and back-end components:
This is custom documentation. For more information, please visit the SAP Help Portal 76
5/14/2023
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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components ( ) ()

Back-End Components () ()

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

On the front-end server, the following SAP notes must be implemented for this app:

SAP Note Number Description

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:

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) ()

For more information about how to activate the OData service, see Front-End Server: Activate OData Services .

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application

For more information about how to activate the SAPUI5 application (ICF service), see Front-End Server: Activate ICF Services.

This is custom documentation. For more information, please visit the SAP Help Portal 77
5/14/2023

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

() In addition, this role contains authorizations OData service authorization must be


to display the related business data. assigned.

 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 are using release ERECRUIT 617 SP16 or above.

You have set the value of RECFA FIOUI to X in the Customizing Set System Parameters, that is part of SAP E-
Recruiting Technical Settings .

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Career (Unregistered Candidate)

This is custom documentation. For more information, please visit the SAP Help Portal 78
5/14/2023
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:

Business Add-Ins (BAdIs)


The following Business Add-In is available for extensibility purposes:

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 set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

BADI_RCF_FIO_POSTING_IMAGE

You can use this BAdI to display an image for a Job Posting. To use this BAdI, excecute the Customizing BAdI: Specify
Image for Job in My Careers app part of SAP E-Recruiting Technical Settings User Interfaces Fiori UI .

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 using the BAdI BADI_RCF_FIO_ENRICH according to your speci c business needs:

UI Back End/ABAP

View Extension Point / Design Time: Methods to be Implemented for BAdI


Gateway Entity BADI_RCF_FIO_ENRICH
Purpose

CandProfile.view.xml CandProfileViewSectionExtension RCF_CANDIDATE ENRICH_CAND_EDUCATION

Allows ou to add a section in the candidate ENRICH_CAND_WORKEXPERIENCE


pro le view.

Application.view.xml ApplicationViewListItemExtension RCF_CANDIDATE Not applicable. Only front-end changes

Allows you to change list item in the


application view

Application.view.xml FavouriteViewListItemExtension RCF_CANDIDATE Not applicable. Only front-end changes

Allows you to change the list item in the


favourites view

JobSearch.view.xml SearchResultListExtension RCF_CANDIDATE ENRICH_JOB_HITLIST

Allows you to edit the search result list on


Job search View

JobDetails.view.xml JobDetailsHdrExtension RCF_CANDIDATE ENRICH_JOB_DETAILS

Allows you to enhance the header details of


the view JobDetails

JobDetails.view.xml JobDetailsContentExtension RCF_CANDIDATE ENRICH_JOB_DECRIPTIONSENRICH_

Allows you to enhance the content details of


the view JobDetails

This is custom documentation. For more information, please visit the SAP Help Portal 79
5/14/2023

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 .

My Communication Data (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Communication Data (Fiori 2.0) you can create, display and edit your communication data at
work, such as your Telephone Number, Fax and E-mail. The app helps you to keep your communication data up to date.

Key Features
Display an overview of current communication data

Create or edit communication data

Set a validity date for data record

Delete communication data

Maintain data for another employee on-behalf

An employee who is concurrently employed can use the app for a chosen personnel assignment.

Localization
Independently of the country of the employee the international screen is available for editing.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

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 Addresses (Fiori 2.0)

My Bank Details (Fiori 2.0)

My Personal Data (Fiori 2.0)

This is custom documentation. For more information, please visit the SAP Help Portal 80
5/14/2023
My Family Members (Fiori 2.0)

My Internal Data (Fiori 2.0)

My Pro le (Fiori 2.0)

Component for Customer Incidents


PA-FIO-PER

App History: My Communication Data (Fiori 2.0)


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 7 (Delivery Date 7/2019)

New Key Feature An employee is allowed to maintain data for another employee on-
behalf.

New Extensibility Options You can use the BAdI HCMFAB_B_COMMON to con gure the
on-behalf scenario.

You can use the BAdI HCMFAB_B_PERSINFO_SETTINGS


to disable the function to change the employee picture. You
can also set the MIME types of the employee picture that
an employee can upload.

SAP Fiori for SAP ERP HCM 2.0 SPS 4 (Delivery Date 10/2018)

New Key Feature Localizations (country speci c screens for editing data):
Data can be edited independently of the country of the employee
by using the international con guration.

SAP Fiori for SAP ERP HCM 2.0 SPS 2 (Delivery Date 04/2018)
Initial delivery.

App Implementation: My Communication Data (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements

This is custom documentation. For more information, please visit the SAP Help Portal 81
5/14/2023
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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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

This is custom documentation. For more information, please visit the SAP Help Portal 82
5/14/2023
On the front-end server, the following SAP notes must be implemented for this app:

SAP Note Number Description

not available not available

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=F3113

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYCOMMUNICATION_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

Component Technical Name

SAPUI5 Application HCMFAB_COMM_MAN

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.

This is custom documentation. For more information, please visit the SAP Help Portal 83
5/14/2023
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.

OData Service (Version Number) Back-End Server: Delivered Authorization Role Front-End Server : Assignment to
(PFCG Role) Authorization Role

HCMFAB_MYCOMMUNICATION_SRV In addition, this role contains authorizations to OData service authorization must be
(0001 ) display the related business data. assigned.

SAP_HCMFAB_MYCOMMUNICATION_APP

 Note
In addition, this role contains authorizations to
display the related business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Communication Data (Fiori 2.0)


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 con gure your own country speci c entities.

You can ll your customer speci c extension includes.

You can add additional elds to the country speci c forms used to display/edit the data.

You can adapt the behavior of elds delivered in the standard UI con guration.

You can in uence the behavior of the app with regards to the employee picture.

Extensibility Entities

Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

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 specify for which employees a person (personnel number) is allowed to maintain data on-behalf.

You can specify how the system checks if a given employee number is allowed/relevant to be used in an on-behalf
scenario for the current user.

You can de ne who is the manager of an employee.

You can add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.


This is custom documentation. For more information, please visit the SAP Help Portal 84
5/14/2023
You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button. You can also enable the on-behalf functionality.

You can check whether an employee is a manager.

BAdI: HR FIori: PersInfo Con gurations (HCMFAB_B_PERSINFO_CONFIG)

You can use this BAdI to con gure your own country speci c entities to the My Communication Data OData
Service HCMFAB_MYCOMMUNICATION.

 Note
This BAdi is also relevant for the OData services of the other Personal Information SAP Fiori Apps.

In the standard system, SAP provides country-speci c BAdI implementations for a number of countries. For more
information see documentation of BAdI HCMFAB_B_PERSINFO_CONFIG.

BAdI for Enhancement of SAP Fiori App My Communication Data (HCMFAB_B_MYCOMMUNICATION)

You can use this BAdI to ll your customer speci c extension includes used in the My Communication Data SAP Fiori
App.

HR Fiori: PersInfo Settings (UI-relevant) (HCMFAB_B_PERSINFO_SETTINGS)

You can use this BAdI to disable the function to change the employee picture.

You can also set the MIME types of the employee picture that an employee can upload.

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: Gateway Entity Design Time: Extension Inc

99_Display_Default_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form (Display)

99_Edit_Default_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form (Edit)

99_Display_0001_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0001 (Display)

99_Edit_0001_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0001 (Edit)

This is custom documentation. For more information, please visit the SAP Help Portal 85
5/14/2023

UI Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time: Extension Inc

99_Display_0002_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0002 (Display)

99_Edit_0002_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0002 (Edit)

99_Display_0001_V003.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0003 (Display)

99_Edit_0001_V003.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0003 (Edit)

99_Display_0004_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0004 (Display)

99_Edit_0004_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0004 (Edit)

99_Display_0005_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0005 (Display)

99_Edit_0005_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0005 (Edit)

This is custom documentation. For more information, please visit the SAP Help Portal 86
5/14/2023

UI Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time: Extension Inc

99_Display_0006_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0006 (Display)

99_Edit_0006_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0006 (Edit)

99_Display_0010_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0010 (Display)

99_Edit_0010_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0010 (Edit)

99_Display_0011_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0011 (Display)

99_Edit_0011_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0011 (Edit)

99_Display_0020_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0020 (Display)

99_Edit_0020_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0020 (Edit)

This is custom documentation. For more information, please visit the SAP Help Portal 87
5/14/2023

UI Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time: Extension Inc

99_Display_0030_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0030 (Display)

99_Edit_0030_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
0030 (Edit)

99_Display_CELL_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
CELL (Display)

99_Edit_CELL_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
CELL (Edit)

99_Display_FR01_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
FR01 (Display)

99_Edit_FR01_V001.view.xm extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
FR01 (Edit)

99_Display_FRMA_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
FRMA (Display)

99_Edit_FRMA_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
FRMA (Edit)

This is custom documentation. For more information, please visit the SAP Help Portal 88
5/14/2023

UI Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time: Extension Inc

99_Display_MAIL_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
MAIL (Display)

99_Edit_MAIL_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
MAIL (Edit)

99_Display_MPHN_V001.view.xml extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
MPHN (Display)

99_Edit_MPHN_V001.view extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
MPHN (Edit)

99_Display_PAGR_V001.view extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
PAGR (Display)

99_Edit_PAGR_V001.view extensionFormContent HCMFAB_S_PERS_COMMUN


Communication
Allows you to add
additional elds to the CommunicationDefault
international form subtype
PAGR (Edit)

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
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 .

Adapt Fields of the Standard UI Con guration

You can adapt the behavior of the elds delivered with the standard UI con guration of the app in following way:

Set editable (Field property Can be edited)

Set invisible (Field property Invisible)

Set read-only (Field property Output Only)

Set mandatory (Field Property Required Entry)

To do so, use the view VT588MUIFPROPC (Customer: Field Properties of UI Fields) as described blow.

This is custom documentation. For more information, please visit the SAP Help Portal 89
5/14/2023
1. Open view VT588MUIFPROPC in transaction SM31 and choose the relevant Work Area. In this case this is Infotype
0105.

2. Choose New Entries and enter the following data:

a. Context: ESSWDAPERS

b. IT Version: Select the relevant country.

c. Subtype: Choose the relevant subtype.

d. UI Structure Name/Field Name: Choose relevant structure and eld.

e. Field Property: Choose the property you want to assign to the eld.

3. Repeat step 2 for each eld where you want to change the standard behavior.

4. Save your entries.

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 .

My External Organizations (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My External Organizations (Fiori 2.0), as an employee, you can maintain the details of the external
organizations you are associated with. For example, you can specify the details of Charity Organizations and Trust Funds you
wish to contribute to. This information can be used by bene ts enrollment applications.

Key Features
An employee who is concurrently employed can use the app for a chosen personnel assignment.

View details of the employee such as name, organizational unit, and picture.

Add external organizations by specifying the organization’s name and details.

Edit existing external organizations.

Maintain data for another employee on-behalf

Delete existing external organizations.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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:

This is custom documentation. For more information, please visit the SAP Help Portal 90
5/14/2023
Front-End Components Delivered with (Product Version Stack) SAP Fiori 2.0 for SAP ERP HCM ( 17 (03/2022) )

For more information, see the app implementation document of this app.

Component for Customer Incidents


PA-FIO-BN

App History: My External Organizations (Fiori 2.0)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 7 (Delivery Date 7/2019)

New Key Feature An employee is allowed to maintain data for another employee on-
behalf.

New Extensibility Options You can use the BAdI HCMFAB_B_COMMON to con gure the on-
behalf scenario.

SAP Fiori for SAP ERP HCM 2.0 SPS 5 (Delivery Date 01/2019)
Initial Delivery.

App Implementation: My External Organizations (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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:

This is custom documentation. For more information, please visit the SAP Help Portal 91
5/14/2023
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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

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=F3114

Front-End Server : Activate OData Services

This is custom documentation. For more information, please visit the SAP Help Portal 92
5/14/2023

Component Technical Name

OData Service (Version Number) HCMFAB_MY_EXT_ORG_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

Component Technical Name

SAPUI5 Application HCMFAB_EORG_MAN

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MY_EXT_ORG_SRV (0001 ) In addition, this role contains authorizations OData service authorization must be
to display the related business data. assigned.

n/a

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information

This is custom documentation. For more information, please visit the SAP Help Portal 93
5/14/2023
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My External Organizations (Fiori 2.0)


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 con gure your own country speci c entities.

You can ll your customer speci c extension includes.

You can add additional elds to the country speci c forms used to display/edit the data.

You can adapt the behavior of elds delivered in the standard UI con guration.

Extensibility Entities
Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

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 specify for which employees a person (personnel number) is allowed to maintain data on-behalf.

You can specify how the system checks if a given employee number is allowed/relevant to be used in an on-behalf
scenario for the current user.

You can de ne who is the manager of an employee.

You can add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button. You can also enable the on-behalf functionality.

You can check whether an employee is a manager.

BAdI for con guring personal information (HCMFAB_B_PERSINFO_CONFIG)

You can use this BAdI to con gure your own country speci c entities to the My External Organizations OData Service
HCMFAB_MY_EXT_ORG.

 Note
This BAdI is also relevant for the OData services of the other Personal Information SAP Fiori Apps.

In the standard system, SAP provides country-speci c BAdI implementations for a number of countries. For more
information see documentation of BAdI HCMFAB_B_PERSINFO_CONFIG.

BAdI for Enhancement of SAP Fiori App My External Organizations (HCMFAB_B_MY_EXT_ORG)

You can use this BAdI to ll your customer speci c extension includes used in the My External Organizations SAP Fiori
App.

This is custom documentation. For more information, please visit the SAP Help Portal 94
5/14/2023

Extension Points

To enhance the app, the following extension points are available:

UI Back End/ABAP

View Extension Point/Purpose Design Time: Gateway Entity Design Tim

99_Display_Default_V001.view.xml extensionFormContent HCMFAB_S


ExternalOrganizations
Allows you to add content
to the Display Form ExternalOrganizationsDefault

99_Edit_Default_V001.view.xml extensionFormContent HCMFAB_S


ExternalOrganizations
Allows you to add content
to the Edit Form ExternalOrganizationsDefault

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
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 .

Adapt Fields in the Standard UI Con guration


You can adapt the behavior of the elds delivered with the standard UI con guration of the app in following way:

Set editable (Field property Can be edited)

Set invisible (Field property Invisible)

Set read-only (Field property Output Only)

Set mandatory (Field property Required Entry)

To do so, use the view VT588MUIFPROPC (Customer: Field Properties of UI Fields) as described below.

1. Open view VT588MUIFPROPC in transaction SM31 and choose the relevant Work Area. In this case, the relevant work
area is Infotype 0219.

2. Choose New Entries and enter the following data:

a. Context: ESSWDAPERS

b. IT Version: Select the relevant country.

c. Subtype: Choose the relevant subtype.

d. UI Structure Name/Field Name: Choose relevant structure and eld.

e. Field Property: Choose the property you want to assign to the eld.

3. Repeat step 2 for each eld where you want to change the standard behavior.

4. Save your entries.

More Information
This is custom documentation. For more information, please visit the SAP Help Portal 95
5/14/2023
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 .

My Family Members (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Family Members (Fiori 2.0) you can create, display, edit and delete your family data, such as your
spouse, domestic partner, child, or child of your domestic partner. The app helps you to keep your information about family
members up to date.

Key Features
Display an overview of the current family data

Create or edit family data

Delete family data

Maintain data for another employee on-behalf

An employee who is concurrently employed can use the app for a chosen personnel assignment.

Localization
The following localizations (country and region speci c screens for editing data) are available:

Country/Region Code Country/Region Country/Region Code Country/Region

99 International Version 31 Slovakia

01 Germany 32 Mexico

02 Switzerland 33 Russia

03 Austria 34 Indonesia

04 Spain 36 Ukraine

05 Netherlands 37 Brazil

06 France 38 Colombia

07 Canada 39 Chile

08 Great Britain 40 India

10 USA 42 Taiwan

11 Ireland 43 New Zealand

12 Belgium 44 Finland

13 Australia 45 Greece

14 Malaysia 46 Poland

15 Italy 48 Philippines

16 South Africa 58 Croatia

This is custom documentation. For more information, please visit the SAP Help Portal 96
5/14/2023

Country/Region Code Country/Region Country/Region Code Country/Region

17 Venezuela 61 Romania

18 Czech Republic 62 Slovenia

19 Portugal AE United Arabic Emirates

20 Norway BG Bulgaria

21 Hungary EG Egypt

22 Japan KW Kuwait

23 Sweden OM Oman

24 Saudi Arabia QA Qata

25 Singapore UN Nonpro t Organization

26 Thailand

27 Hong Kong

28 China

29 Argentina

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

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 Addresses (Fiori 2.0)

My Bank Details (Fiori 2.0)

My Communication Data (Fiori 2.0)

My Personal Data (Fiori 2.0)

My Internal Data (Fiori 2.0)

My Pro le (Fiori 2.0)

This is custom documentation. For more information, please visit the SAP Help Portal 97
5/14/2023

Component for Customer Incidents


PA-FIO-PER

App History: My Family Members (Fiori 2.0)


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 8 (Delivery Date 10/2019)

New Key Features


New localizations (country/region speci c screens for
editing data) are available

Allows you to use the app in the following new


country/region versions:

Sweden

Thailand

Slovakia

Ukraine

Finland

Philippines

Croatia

Romania

Slovenia

Bulgaria

Greece

New Extensibility Options New Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

SAP Fiori for SAP ERP HCM 2.0 SPS 7 (Delivery Date 07/2019)

New Key Features New localizations (country/region speci c screens for


editing data) are available

Allows you to use the app in the following new


country/region versions:

Argentina

This is custom documentation. For more information, please visit the SAP Help Portal 98
5/14/2023
Chile

Columbia

Egypt

Hong Kong

Hungary

Indonesia

Ireland

Kuwait

Malaysia

New Zealand

Oman

Portugal

Qatar

Singapore

South Africa

Taiwan

Venezuela

Nonpro t Organization (NPO)

An employee is allowed to maintain data for another


employee on-behalf.

New Extensibility Options


New Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

You can use the BAdI HCMFAB_B_COMMON to con gure the


on-behalf scenario.

You can use the BAdI HCMFAB_B_PERSINFO_SETTINGS


to disable the function to change the employee picture. You
can also set the MIME types of the employee picture that
an employee can upload.

SAP Fiori for SAP ERP HCM 2.0 SPS 6 (Delivery Date 04/2019)

New Key Feature New localizations (country speci c screens for editing data) are
available

Allows you to use the app in the following new country versions:

Belgium

Italy

Czech Republic

Japan

Russia

This is custom documentation. For more information, please visit the SAP Help Portal 99
5/14/2023
Poland

New Extensibility Options


Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

SAP Fiori for SAP ERP HCM 2.0 SPS 5 (Delivery Date 01/2019)

New Key Feature New localizations (country speci c screens for editing data) are
available

Allows you to use the app in the following new country versions:

Austria

Netherlands

Norway

Spain

Switzerland

Canada

Mexico

Australia

United Arabic Emirates

Saudi Arabia

New Extensibility Options


Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

SAP Fiori for SAP ERP HCM 2.0 SPS 4 (Delivery Date 10/2018)

New Key Feature New localizations (country speci c screens for editing data) are
available

Allows you to use the app in the following new country versions:

Brazil

India

France

China

New Extensibility Options


Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

SAP Fiori for SAP ERP HCM 2.0 SPS 2 (Delivery Date 04/2018)
Initial delivery

This is custom documentation. For more information, please visit the SAP Help Portal 100
5/14/2023

App Implementation: My Family Members (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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


This is custom documentation. For more information, please visit the SAP Help Portal 101
5/14/2023
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:

SAP Note Number Description

not available not available

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=F3115

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYFAMILYMEMBERS_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

Component Technical Name

SAPUI5 Application HCMFAB_FMLY_MAN

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.

This is custom documentation. For more information, please visit the SAP Help Portal 102
5/14/2023
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.

OData Service (Version Number) Back-End Server: Delivered Authorization Role Front-End Server : Assignment to
(PFCG Role) Authorization Role

HCMFAB_MYFAMILYMEMBERS_SRV In addition, this role contains authorizations to OData service authorization must be
(0001 ) display the related business data. assigned.

SAP_HCMFAB_MYFAMILYMEMBERS_APP

 Note
In addition, this role contains authorizations to
display the related business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Family Members (Fiori 2.0)


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 con gure your own country speci c entities.

You can ll your customer speci c extension includes.

You can add additional elds to the country speci c forms used to display/edit the data.

You can adapt the behavior of elds delivered in the standard UI con guration.

You can in uence the behavior of the app with regards to the employee picture.

Extensibility Entities
Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

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 specify for which employees a person (personnel number) is allowed to maintain data on-behalf.

You can specify how the system checks if a given employee number is allowed/relevant to be used in an on-behalf
scenario for the current user.

This is custom documentation. For more information, please visit the SAP Help Portal 103
5/14/2023
You can de ne who is the manager of an employee.

You can add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button. You can also enable the on-behalf functionality.

You can check whether an employee is a manager.

BAdI: HR FIori: PersInfo Con gurations (HCMFAB_B_PERSINFO_CONFIG)

You can use this BAdI to con gure your own country speci c entites to the My Family Members/Dependents OData
Service HCMFAB_MYFAMILYMEMBERS.

 Note
This BAdi is also relevant for the OData services of the other Personal Information SAP Fiori Apps.

In the standard system, SAP provides country-speci c BAdI implementations for a number of countries. For more
information see documentation of BAdI HCMFAB_B_PERSINFO_CONFIG.

BAdI for Enhancement of SAP Fiori App My Family Members/Dependents (HCMFAB_B_MYFAMILYMEMBERS)

You can use this BAdI to ll your customer speci c extension includes used in the My Familiy Members/Dependents SAP
Fiori App.

HR Fiori: PersInfo Settings (UI-relevant) (HCMFAB_B_PERSINFO_SETTINGS)

You can use this BAdI to disable the function to change the employee picture.

You can also set the MIME types of the employee picture that an employee can upload.

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: Gateway Entity Design Time:

99_Display_Default_V001.view.xml view.extensionFormContent HCMFAB_S_P


FamilyMember
Allows you to add additional elds
to the international form (Display) FamilyMemberDefault

99_Edit_Default_V001.view.xml view.extensionFormContent HCMFAB_S_P


FamilyMember
Allows you to add additional elds
to the international form (Edit) FamilyMemberDefault

++_Display_Default_V001.view.xml view.extensionFormContent HCMFAB_S_P


FamilyMember++
++ = number of country version Allows you to add additional elds
to the form for country ++, FamilyMember++Default
The following localizations are available:
Subtype 1 (Display)

(01) (31) Slovakia


Germany

This is custom documentation. For more information, please visit the SAP Help Portal 104
5/14/2023

UI Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time:

(02) (32) Mexico


Switzerland
(33) Russia
(03) Austria
(34)
(04) Spain Indonesia

(05) (36) Ukraine


Netherlands
(37) Brazil
(06) France
(38)
(07) Canada Colombia

(08) Great (39) Chile


Britain
(40) India
(10) USA
(42) Taiwan
(11) Ireland
(43) New
(12) Zealand
Belgium
(44) Finland
(13)
Australia (45) Greece

(46) Poland
(14)
Malaysia (48)
Philippines
(15) Italy

(16) South (58) Croatia

Africa (61)
Romania
(17)
Venezuela (62)

(18) Czech Slovenia

Republic (AE) United


Arabic
(19)
Emirates
Portugal
(BG)
(20) Norway
Bulgaria
(21)
Hungary (EG) Egypt

(KW) Kuwait
(22) Japan
(OM) Oman
(23)
Sweden (QA) Qatar

(24) Saudi (UN)


Arabia Nonpro t
Organization
(25)
(NPO)
Singapore

(26)
Thailand

(27) Hong
Kong

(28) China

(29)
Argentina

This is custom documentation. For more information, please visit the SAP Help Portal 105
5/14/2023

UI Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time:

++_Edit_0001_V001.view.xml view.extensionFormContent HCMFAB_S_P


FamilyMember++
++ = number of country version Allows you to add additional elds
to the form for country ++, FamilyMember++Default
Subtype 1 (Edit)

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
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 .

Adapt Fields of the Standard UI Con guration

You can adapt the behavior of the elds delivered with the standard UI con guration of the app in following way:

Set editable (Field property Can be edited)

Set invisible (Field property Invisible)

Set read-only (Field property Output Only)

Set mandatory (Field Property Required Entry)

To do so, use the view VT588MUIFPROPC (Customer: Field Properties of UI Fields) as described blow.

1. Open view VT588MUIFPROPC in transaction SM31 and choose the relevant Work Area. In this case this is Infotype
0021.

2. Choose New Entries and enter the following data:

a. Context: ESSWDAPERS

b. IT Version: Select the relevant country.

c. Subtype: Choose the relevant subtype.

d. UI Structure Name/Field Name: Choose relevant structure and eld.

e. Field Property: Choose the property you want to assign to the eld.

3. Repeat step 2 for each eld where you want to change the standard behavior.

4. Save your entries.

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 .

My Forms (Fiori 2.0)


Abstract for SAP Fiori apps.

This is custom documentation. For more information, please visit the SAP Help Portal 106
5/14/2023
With the transactional app My Forms (Fiori 2.0), you can display different HR-related form types relevant for you and your
country/region of employment, including remuneration statement and time statement. These form types may either be
provided by SAP or individually de ned by your employer. For more information regarding the de nition of own form types, see
App Extensibility: My Forms (Fiori 2.0).

Key Features
By default:

Display of an overview of the different form types available for you

Searching in as well as sorting, ltering and grouping of the overview list

Display of a detailed view of a speci c form in PDF format (based on the functions of the PDF Viewer) as well as
download and printing of the selected PDF form

Depending on settings:

Transfer of speci c form data into a le

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

For more information, see the app implementation document of this app.

Component for Customer Incidents


PA-FIO-FO

App History: My Forms (Fiori 2.0)


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.

SAP Fiori for SAP ERP HCM 2.0 SPS 15 (Delivery Date 09/2021)

This is custom documentation. For more information, please visit the SAP Help Portal 107
5/14/2023
With the release of SAP Fiori for SAP ERP HCM 2.0 SPS 15, the following enhancements to My Forms are available for certain
localizations:

Localization Enhancement SAP Note

Netherlands The Annual Tax Statement forms can be 2973571


accessed from the localized Annual Tax
2921833
Statement tile. The implementation steps
for the My Forms (Fiori 2.0) app did not
change.

SAP Fiori for SAP ERP HCM 2.0 SPS 14 (Delivery Date 06/2021)
With the release of SAP Fiori for SAP ERP HCM 2.0 SPS 14, the following enhancements to My Forms are available for certain
localizations:

Localization Enhancement SAP Note

United States of America Online W-2 View & Print is enabled. 3048028

Singapore The IR8A Form is included in the standard 3027282


forms.

The Key Employment Term is included in 3019351


the standard forms.

Malaysia The EA Form and the PCB2(II) Form are 3019828


included in the standard forms.

Portugal The Individual Income Declaration is 3017166


included in the standard forms.

Netherlands The Annual Tax Statement is included in 2973571


the standard forms.

SAP Fiori for SAP ERP HCM 2.0 SPS 12 (Delivery Date 12/2020)
Initial delivery.

App Implementation: My Forms (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

The SAP product version in the back-end system serving as the basis for the app must be the following:

This is custom documentation. For more information, please visit the SAP Help Portal 108
5/14/2023

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

Implementation Tasks

This is custom documentation. For more information, please visit the SAP Help Portal 109
5/14/2023
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=F4938

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYFORMS_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

Component Technical Name

SAPUI5 Application HCMFAB_MYFORMS

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

This is custom documentation. For more information, please visit the SAP Help Portal 110
5/14/2023

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYFORMS_SRV (0001 ) In addition, this role contains authorizations OData service authorization must be
to display the related business data. assigned.

SAP_HCMFAB_MYFORMS_APP

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Forms (Fiori 2.0)


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:

Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

Settings for the My Forms App (HCMFAB_B_MYFORMS)

You can use this BAdI to de ne the different form types to be displayed in the Fiori My Forms app and the related form
type columns. Furthermore, you can use it to de ne certain elds both for the master detail view and the view above the
corresponding PDF form. Moreover, you can use it to enable the data transfer function, allowing for the transfer of
speci c form data into a le, as well as to hide the form types provided by SAP. For more information, see the related
BAdI documentation.

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, to de ne who is a
colleague of an employee, to de ne who is a direct report of a manager, to de ne who is the manager of an employee, to
de ne how the system determines the employee picture, to set the visibility of certain UI elements, such as employee
picture, employee number and the concurrent employment (CE) functionality, and to check whether an employee is a
manager.

Extension Points

View Extension Point Use

Master.view.xml myformsToolbarExtension Allows you to add additional information to


the toolbar of the table

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

This is custom documentation. For more information, please visit the SAP Help Portal 111
5/14/2023
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

Controller Hook Use

Master.controller.js hcm.fab.myforms.view.Master ~ Allows you to adjust the display of the table


extHookAdjustViewModel control in the master view

If there are additional UI controller hooks available in the controller code, you can add own code. For more information, 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 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 .

My Internal Data (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Internal Data (Fiori 2.0) you can create, display, edit and delete your internal data, such as your
Building Number and Room Number. It also contains the Licence Plate Number of your company car. The app helps you to keep
your internal data up to date.

Key Features
Display an overview of current internal data.

Create or edit internal data

Set a validity date for data record

Delete internal data

Maintain data for another employee on-behalf

An employee who is concurrently employed can use the app for a chosen personnel assignment.

Localization
Independently of the country of the employee the international screen is available for editing.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

This is custom documentation. For more information, please visit the SAP Help Portal 112
5/14/2023
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 ( 17 (03/2022) )

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 Addresses (Fiori 2.0)

My Bank Details (Fiori 2.0)

My Communication Data (Fiori 2.0)

My Family Members (Fiori 2.0)

My Personal Data (Fiori 2.0)

My Pro le (Fiori 2.0)

Component for Customer Incidents


PA-FIO-PER

App History: My Internal Data (Fiori 2.0)


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 7 (Delivery Date 7/2019)

New Key Feature An employee is allowed to maintain data for another employee on-
behalf.

New Extensibility Options You can use the BAdI HCMFAB_B_COMMON to con gure the on-
behalf scenario.

New Extensibility Options You can use the BAdI HCMFAB_B_PERSINFO_SETTINGS to


disable the function to change the employee picture. You can also
set the MIME types of the employee picture that an employee can
upload.

SAP Fiori for SAP ERP HCM 2.0 SPS 4 (Delivery Date 10/2018)
This is custom documentation. For more information, please visit the SAP Help Portal 113
5/14/2023

New Key Feature Localizations (country speci c screens for editing data):
Data can be edited independently of the country of the employee
by using the international con guration.

SAP Fiori for SAP ERP HCM 2.0 SPS 2 (Delivery Date 04/2018)
Initial delivery.

App Implementation: My Internal Data (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

This is custom documentation. For more information, please visit the SAP Help Portal 114
5/14/2023

App Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

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=F3116

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYINTERNALDATA_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

Component Technical Name

This is custom documentation. For more information, please visit the SAP Help Portal 115
5/14/2023

Component Technical Name

SAPUI5 Application HCMFAB_INDT_MAN

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYINTERNALDATA_SRV In addition, this role contains authorizations to OData service authorization must be
(0001 ) display the related business data. assigned.

SAP_HCMFAB_MYINTERNALDATA_APP

 Note
In addition, this role contains authorizations
to display the related business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Internal Data (Fiori 2.0)


Extensibility information for SAP Fiori app.

This is custom documentation. For more information, please visit the SAP Help Portal 116
5/14/2023
You can extend the app according to your business needs for different aspects. For this purpose, the following extensibility
options are available:

You can con gure your own country speci c entities.

You can ll your customer speci c extension includes.

You can add additional elds to the country speci c forms used to display/edit the data.

You can adapt the behavior of elds delivered in the standard UI con guration.

You can in uence the behavior of the app with regards to the employee picture.

Extensibility Entities
Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

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 specify for which employees a person (personnel number) is allowed to maintain data on-behalf.

You can specify how the system checks if a given employee number is allowed/relevant to be used in an on-behalf
scenario for the current user.

You can de ne who is the manager of an employee.

You can add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button. You can also enable the on-behalf functionality.

You can check whether an employee is a manager.

BAdI: HR FIori: PersInfo Con gurations (HCMFAB_B_PERSINFO_CONFIG)

You can use this BAdI to con gure your own country speci c entities to the My Internal Data OData Service
HCMFAB_MYINTERNALDATA.

 Note
This BAdi is also relevant for the OData services of the other Personal Information SAP Fiori Apps.

In the standard system, SAP provides country-speci c BAdI implementations for a number of countries. For more
information see documentation of BAdI HCMFAB_B_PERSINFO_CONFIG.

BAdI for Enhancement of SAP Fiori App My Internal Data (HCMFAB_B_MYINTERNALDATA)

You can use this BAdI to ll your customer speci c extension includes used in the My Internal Data SAP Fiori App.

HR Fiori: PersInfo Settings (UI-relevant) (HCMFAB_B_PERSINFO_SETTINGS)

You can use this BAdI to disable the function to change the employee picture.

You can also set the MIME types of the employee picture that an employee can upload.

Extension Points

To enhance the app, the following extension points are available:


This is custom documentation. For more information, please visit the SAP Help Portal 117
5/14/2023

Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time: Extension

99_Display_Default_V001.view.xml extensionFormContent InternalData HCMFAB_S_PERS_INT

Allows you to add content InternalDataDefault


to the Display Form

99_Edit_Default_V001.view.xml extensionFormContent InternalData HCMFAB_S_PERS_INT

Allows you to add content InternalDataDefault


to the Edit Form

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
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 .

Adapt Fields of the Standard UI Con guration

You can adapt the behavior of the elds delivered with the standard UI con guration of the app in following way:

Set editable (Field property Can be edited)

Set invisible (Field property Invisible)

Set read-only (Field property Output Only)

Set mandatory (Field Property Required Entry)

To do so, use the view VT588MUIFPROPC (Customer: Field Properties of UI Fields) as described blow.

1. Open view VT588MUIFPROPC in transaction SM31 and choose the relevant Work Area. In this case this is Infotype
0032.

2. Choose New Entries and enter the following data:

a. Context: ESSWDAPERS

b. IT Version: Select the relevant country.

c. Subtype: Choose the relevant subtype.

d. UI Structure Name/Field Name: Choose relevant structure and eld.

e. Field Property: Choose the property you want to assign to the eld.

3. Repeat step 2 for each eld where you want to change the standard behavior.

4. Save your entries.

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 .

This is custom documentation. For more information, please visit the SAP Help Portal 118
5/14/2023

My Leave Requests (Version 3/Fiori 2.0)


Abstract for SAP Fiori apps.

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
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

Maintain data for another employee on-behalf

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.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

This is custom documentation. For more information, please visit the SAP Help Portal 119
5/14/2023
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:

Approve Leave Requests (Version 3)

Component for Customer Incidents


PA-FIO-LEA

App History: My 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 18 (Delivery Date 06/2022)

New Extensibility Options You can use new UI Controller Hooks to extend the app with custom
code.

SAP Fiori for SAP ERP HCM 2.0 SPS 7 (Delivery Date 7/2019)

New Key Feature An employee is allowed to maintain data for another employee on-
behalf.

New Extensibility Options You can use the BAdI HCMFAB_B_COMMON to con gure the on-
behalf scenario.

SAP Fiori for SAP ERP HCM 2.0 SPS 0 (Delivery Date 07/2017)
Initial delivery.

App Implementation: My Leave Requests (Version 3)


Implementation information for SAP Fiori app.

System Landscape Requirements


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
This is custom documentation. For more information, please visit the SAP Help Portal 120
5/14/2023
prerequisites:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

This is custom documentation. For more information, please visit the SAP Help Portal 121
5/14/2023

SAP Note Number Description

2103156 Launching Fiori apps in standalone mode

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=F1311A

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_LEAVE_REQUEST_CR_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

Component Technical Name

SAPUI5 Application HCMFAB_LEAV_MAN

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.

This is custom documentation. For more information, please visit the SAP Help Portal 122
5/14/2023

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_LEAVE_REQUEST_CR_SRV In addition, this role contains authorizations OData service authorization must be
(0001 ) to display 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
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Leave Requests (Version 3)


Extensibility information for SAP Fiori app.

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.

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:

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 specify for which employees a person (personnel number) is allowed to maintain data on-behalf.

You can specify how the system checks if a given employee number is allowed/relevant to be used in an on-behalf
scenario for the current user.

You can add additional employee information shown in the employee data.

You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button. You can also enable the on-behalf functionality.

You can check whether an employee is a manager.

BAdI for My Leave Requests App (HCMFAB_B_MYLEAVEREQUESTS)

This is custom documentation. For more information, please visit the SAP Help Portal 123
5/14/2023
You can use this BAdI to con gure the format of the input and display of absence hours. You can switch the format from
standard industrial hours (e.g., 7.5 hours) to hours and minutes (e.g., 7:30 hours).

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
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.

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

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

This is custom documentation. For more information, please visit the SAP Help Portal 124
5/14/2023

UI Back End/ABAP

View Extension Point Design Time: Design Time: Extension Include


Gateway Entity

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

Overview.view.xml overviewPageExtension LeaveRequest HCMFAB_S_LRQ_REQUEST_LIST_INCL

Allows you to add further elements to the


overview screen

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
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 .

This is custom documentation. For more information, please visit the SAP Help Portal 125
5/14/2023

UI Controller Hooks

To plug in and execute custom code, the following hooks are available in the controller code:

Controller Hook Use

Overview.controller.js hcm.fab.myleaverequest.controller.Overview~extHookAdjustOverviewCalendar Allows you to adjust


the calendar on the
overview page

App.controller.js hcm.fab.myleaverequest.controller.App~extHookAdjustCalendarLegend Allows to adjust the


legend of the calendar

App.controller.js hcm.fab.myleaverequest.controller.App~extHookAdjustCalendarEvent Allows to adjust the


events in the calendar

If there are additional UI controller hooks available in the controller code, you can add own code. For more information, 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 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 .

My Medical Information (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Medical Information (Fiori 2.0) you can specify the details of your physicians, and smoking status.
This information can be used by bene ts enrollment applications.

Key Features
An employee who is concurrently employed can use the app for a chosen personnel assignment.

Display and manage details of the employee such as name, organizational unit, picture

Manage physician details, including name and ID

 Note
You can specify the details of up to 3 physicians.

Maintain data for another employee on-behalf

Specify whether you are a smoker

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))
This is custom documentation. For more information, please visit the SAP Help Portal 126
5/14/2023

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 ( 17 (03/2022) )

For more information, see the app implementation document of this app.

Component for Customer Incidents


PA-FIO-BN

App History: My Medical Information (Fiori 2.0)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 7 (Delivery Date 7/2019)

New Key Feature An employee is allowed to maintain data for another employee on-
behalf.

New Extensibility Options You can use the BAdI HCMFAB_B_COMMON to con gure the on-
behalf scenario.

SAP Fiori for SAP ERP HCM 2.0 SPS 5 (Delivery Date 01/2019)
Initial delivery.

App Implementation: My Medical Information (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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

This is custom documentation. For more information, please visit the SAP Help Portal 127
5/14/2023
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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

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=F3729

Front-End Server : Activate OData Services

This is custom documentation. For more information, please visit the SAP Help Portal 128
5/14/2023

Component Technical Name

OData Service (Version Number) HCMFAB_MY_MEDICAL_INFO_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

Component Technical Name

SAPUI5 Application HCMFAB_MEDI_MAN

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MY_MEDICAL_INFO_SRV In addition, this role contains authorizations OData service authorization must be
(0001 ) to display the related business data. assigned.

SAP_HCMFAB_MEDI_MAN_APP

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information

This is custom documentation. For more information, please visit the SAP Help Portal 129
5/14/2023
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Medical Information (Fiori 2.0)


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 con gure your own country speci c entities.

You can ll your customer speci c extension includes.

You can add additional elds to the country speci c forms used to display/edit the data.

You can adapt the behavior of elds delivered in the standard UI con guration.

Extensibility Entities
Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

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 specify for which employees a person (personnel number) is allowed to maintain data on-behalf.

You can specify how the system checks if a given employee number is allowed/relevant to be used in an on-behalf
scenario for the current user.

You can de ne who is the manager of an employee.

You can add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button. You can also enable the on-behalf functionality.

You can check whether an employee is a manager.

BAdI for con guring personal information (HCMFAB_B_PERSINFO_CONFIG)

You can use this BAdI to con gure your own country speci c entities to the My Medical Information OData Service
HCMFAB_MY_MEDICAL_INFO.

 Note
This BAdI is also relevant for the OData services of the other Personal Information SAP Fiori Apps.

In the standard system, SAP provides country-speci c BAdI implementations for a number of countries. For more
information see documentation of BAdI HCMFAB_B_PERSINFO_CONFIG.

BAdI for Enhancement of SAP Fiori App My Medical Information (HCMFAB_B_MY_MED_INFO)

You can use this BAdI to ll your customer speci c extension includes used in the My Medical Information SAP Fiori App.

This is custom documentation. For more information, please visit the SAP Help Portal 130
5/14/2023

Extension Points

To enhance the app, the following extension points are available:

UI Back End/ABAP

View Extension Point/Purpose Design Time: Gateway Entity Design Time

99_Display_Default_V001.view.xml extensionFormContent HCMFAB_S_


MedicalInformation
Allows you to add content
to the Display Form MedicalInformationDefault

99_Edit_Default_V001.view.xml extensionFormContent HCMFAB_S_


MedicalInformation
Allows you to add content
to the Edit Form MedicalInformationDefault

10_Display_Default_V001.view.xml extensionFormContent HCMFAB_S_


MedicalInformation10
Allows you to add content
to the Display Form MedicalInformation10Default

10_Edit_Default_V001.view.xml extensionFormContent HCMFAB_S_


MedicalInformation10
Allows you to add content
to the Edit Form MedicalInformation10Default

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
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 .

Adapt Fields in the Standard UI Con guration


You can adapt the behavior of the elds delivered with the standard UI con guration of the app in following way:

Set editable (Field property Can be edited)

Set invisible (Field property Invisible)

Set read-only (Field property Output Only)

Set mandatory (Field property Required Entry)

To do so, use the view VT588MUIFPROPC (Customer: Field Properties of UI Fields) as described below.

1. Open view VT588MUIFPROPC in transaction SM31 and choose the relevant Work Area. In this case, the relevant work
area is Infotype 0376.

2. Choose New Entries and enter the following data:

a. Context: ESSWDAPERS

b. IT Version: Select the relevant country.

This is custom documentation. For more information, please visit the SAP Help Portal 131
5/14/2023
c. Subtype: Choose the relevant subtype.

d. UI Structure Name/Field Name: Choose relevant structure and eld.

e. Field Property: Choose the property you want to assign to the eld.

3. Repeat step 2 for each eld where you want to change the standard behavior.

4. Save your entries.

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 .

My Overtime Requests (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Overtime Requests, you can enable employees to create and submit overtime requests using
their desktop, tablet, or mobile device. The app also allows users to display the status of their requests.

Key Features
Create, save, and edit overtime requests. An overtime request can include multiple overtime items of a selected
overtime type. On request creation, users select the compensation types as well as the requested overtime based on a
date in conjunction with a start and end time, based on a start date in conjunction with a selected number of hours, or
based on a start and end date in conjunction with a selected number of hours.

Send overtime requests. Depending on the settings, the submitted request are either processed automatically without
manual approval or are sent for approval to an approver or to multiple approvers. In case of rejection, users can edit and
resend the request. Depending on the settings, users can also add a note for the approver.

Display the user's overtime requests including the approval status on the overview screen.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

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:

This is custom documentation. For more information, please visit the SAP Help Portal 132
5/14/2023
Approve Overtime Requests

My Inbox

Component for Customer Incidents


PA-FIO-OVT

App History: My Overtime Requests (Fiori 2.0)


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 SPS18 (Delivery Date 06/2022)
Initial delivery.

App Implementation: My Overtime Requests (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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.

This is custom documentation. For more information, please visit the SAP Help Portal 133
5/14/2023
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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

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=F4939

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYOVERTIMEQUOTA_SRV (0001 )

This is custom documentation. For more information, please visit the SAP Help Portal 134
5/14/2023
For more information about how to activate the OData service, see Front-End Server: Activate OData Services .

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application HCMFAB_OTQ_MAN

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYOVERTIMEQUOTA_SRV In addition, this role contains authorizations OData service authorization must be
(0001 ) to display the related business data. assigned.

n/a

 Note
In addition, this role contains
authorizations to display the related
business data.

Con guration Tasks


To be able to implement the app, you must perform the following con guration tasks in the back-end system:

Maintain the activities in Customizing for Personnel Management under Employee Self-Service (Web Dynpro ABAP)
Service-Speci c Settings Working Time My Overtime Requests .

This is custom documentation. For more information, please visit the SAP Help Portal 135
5/14/2023

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Overtime Requests (Fiori 2.0)


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:

De ne custom types of attendance quota your employees can choose from.

Adjust the elds displayed in the app for different attendance quota types.

De ne custom request processes for each attendance quota type.

De ne custom approval processes for each attendance quota type. You can also use multi-level approval.

Generate custom noti cation emails to the different stakeholders of an overtime request.

Further Extensibility Entities


Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

Custom Input Checks for Time Data Requests (HRPT_B_TMD_INPUT_CHECKS)

You can use this BAdI to check whether the employee creating a time data request is permitted to select a certain
approver. The system prevents the submission of requests with an approver that is not permitted for selection for the
employee. You can also create custom messages for those cases.

Multi-Level Approval for Time Data Requests (HRPT_B_TMD_MULTI_APPROVERS)

You can use this BAdI to retrieve the default approvers for time data requests based on the employee creating the
request. You can also save approvers to the database and use them as default for further requests.

Actor Substitutes for Time Data Requests (HRPT_B_TMD_SUBSTITUTES)

You can use this BAdI to examine a substitute approver for time data requests. In case an approver is absent, the time
data request is forwarded to the substitute approver.

Custom Input Checks for My Overtime Requests (HRPT_B_OVT_INPUT_CHECKS)

You can use this BAdI to perform checks on the input data of the request items of an overtime request. The system
prevents the submission of requests that do not pass the input checks. You can also create custom messages for those
cases.

UI Descriptions for My Overtime Requests (HRPT_B_OVT_UI_DESCRIPTIONS)

You can use this BAdI to de ne the compensation types that employees can select when creating an overtime request.
You can also create your individual texts for the attendance quota types you use. In case you do not implement this BAdI,
the app uses the overtime quota types as well as the descriptions that you have maintained in the database tables.

Common BAdI for all HCM SAP Fiori Apps (HCMFAB_B_COMMONS)

You can use this BAdI to enhance HCM SAP Fiori apps delivered with software component UIHR002.
This is custom documentation. For more information, please visit the SAP Help Portal 136
5/14/2023
You can add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

You can check whether an employee is a manager.

Extension Points

View Extension Point Use

RequestAdditionalDataEdit.view.xml displayAboveAddtlDataExtension Allows you to add elements to


the Additional Data section in
display mode.

RequestApproverDisplay.view.xml displayApproverBusinessCardExtension Allows you to add elements to


the approver’s business card
view.

RequestItemsDisplay.view.xml displayAboveItemsExtension Allows you to add elements to


the Overtime Items section in
display mode.

RequestItemsEdit.view.xml editAboveItemsExtension Allows you to add elements to


the Overtime Items section in
edit mode.

RequestNotesDisplay.view.xml displayAboveNotesExtension Allows you to add elements to


the Note section in display
mode.

RequestNotesEdit.view.xml editAboveNotesExtension Allows you to add elements to


the Note section in edit mode.

Overview.view.xml overviewAboveRequestsExtension Allows you to add elements to


the Request Overview screen.

RequestDisplay.view.xml displayObjectHeaderHorizontalExtension Allows you to add elements to


the page header of the
Request Detail screen in
display mode.

RequestDisplay.view.xml displaySectionsExtension Allows you to add sections to


the Request Detail screen in
display mode.

RequestEdit.view.xml editObjectHeaderHorizontalExte nsion Allows you to add elements to


the header of the Request
Detail screen in edit mode.

RequestEdit.view.xml editSectionsExtension Allows you to add sections to


the Request Detail screen in
edit mode.

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
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 .

This is custom documentation. For more information, please visit the SAP Help Portal 137
5/14/2023

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 .

My Paystubs (Version 3/Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Paystubs (Version 3), you can enable employees to check and manage a digital version of all their
paystubs issued by the company for each payroll period, easily and exibly using their desktop or mobile device.

Key Features
View a list of your paystubs issued by the company

Sort and group the entries in the paystubs list

Con gure the columns of the paystubs list

Export list of paystubs with all visible columns to Excel (not available on mobile devices)

Check the details of a paystub by displaying the PDF version of the paystub

Download and store a PDF version of a paystub locally on a device or using a Cloud-based storage solution (not available
on mobile devices)

Print a paystub (not available on mobile devices)

Maintain data for another employee on-behalf

An employee who is concurrently employed can use the app for a chosen personnel assignment.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

For more information, see the app implementation document of this app.

Component for Customer Incidents


PA-FIO-PST

App History: My Paystubs (Version 3)


This is custom documentation. For more information, please visit the SAP Help Portal 138
5/14/2023
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 7 (Delivery Date 7/2019)

New Key Features An employee is allowed to maintain data for another


employee on-behalf.

New Extensibility Options You can use the BAdI HCMFAB_B_COMMON to con gure the
on-behalf scenario.

SAP Fiori for SAP ERP HCM 2.0 SPS 0 (Delivery Date 07/2017)
Initial delivery.

App Implementation: My Paystubs (Version 3)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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.

This is custom documentation. For more information, please visit the SAP Help Portal 139
5/14/2023
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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

2103156 Launching Fiori apps in standalone mode

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=F1313A

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYPAYSTUBS_SRV (0001 )

For more information about how to activate the OData service, see Front-End Server: Activate OData Services .

This is custom documentation. For more information, please visit the SAP Help Portal 140
5/14/2023

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application HCMFAB_PAY_MON

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYPAYSTUBS_SRV (0001 ) In addition, this role contains authorizations OData service authorization must be
to display the related business data. assigned.

SAP_HCMFAB_PAY_MON_APP

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Paystubs (Version 3)


This is custom documentation. For more information, please visit the SAP Help Portal 141
5/14/2023
Extensibility information for SAP Fiori app.

You can extend the My Paystubs (Version 3) app according to your business needs for different aspects. For this purpose, the
following extensibility options are available:

You can extend the app by adding additional buttons to the toolbar.

You can extend the app by adding additional columns to the list of paystubs.

You can extend the app by adding additional cells to the list of paystubs.

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.

You can disable certain app functionality (e.g. Print, Download, Export to Excel)

Extensibility Entities
Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

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 specify for which employees a person (personnel number) is allowed to maintain data on-behalf.

You can specify how the system checks if a given employee number is allowed/relevant to be used in an on-behalf
scenario for the current user.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

BAdI for My Paystubs (Version 3) SAP Fiori App (HCMFAB_B_MYPAYSTUBS)

You can use this BAdI to add additional data to cells within the list of paystubs. You can also use this BAdI to display
additional information for a user while printing, downloading, or displaying a paystub as PDF document.

Extension Points

To enhance the app, the following extension points are available:

Back End/ABAP

View Extension Point / Purpose Design Design Time: Extension Run Time: Superclass an
Time: Include Be Rede ned
Gateway
Entity

PaystubsList.view.xml paystubsToolbarExtension - - -

Allows you to add additional


buttons to toolbar

PaystubsList.view.xml paystubsColumnsExtension - - -

Allows you to add additional


columns to the list of paystubs

This is custom documentation. For more information, please visit the SAP Help Portal 142
5/14/2023

Back End/ABAP

View Extension Point / Purpose Design Design Time: Extension Run Time: Superclass an
Time: Include Be Rede ned
Gateway
Entity

PaystubsList.view.xml paystubsCellsExtension Paystub HCMFAB_S_PAYSTUB_INCL Superclass:


CL_HCMFAB_MYPAYSTUB
Allows you to add additional cells
to the list of paystub Method:
PAYSTUBSET_GET_ENTI

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
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 hooks are available in the controller code:

Controller Hook Use

PaystubsList.controller.js hcm.fab.mypaystubs.controller.PaystubsList~extHookAdjustViewModel Allows


to adju
the
ViewM
after t
contro
was
initiali

If there are additional UI controller hooks available in the controller code, you can add own code. For more information, 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 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 .

My Personal Data (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Personal Data (Fiori 2.0) you can display and edit your personal data, such as your name and
birth date. The app helps you to keep your personal data up to date.

Key Features
Display an overview of current personal data

This is custom documentation. For more information, please visit the SAP Help Portal 143
5/14/2023
Edit personal data and

Set a validity date for data record

Upload a photo

Maintain data for another employee on-behalf

An employee who is concurrently employed can use the app for a chosen personnel assignment.

Localization
The following localizations (country and region speci c screens for editing data) are available:

Country/Region Code Country/Region Country/Region Code Country/Region

99 International Version 31 Slovakia

01 Germany 32 Mexico

02 Switzerland 33 Russia

03 Austria 34 Indonesia

04 Spain 36 Ukraine

05 Netherlands 37 Brazil

06 France 38 Colombia

07 Canada 39 Chile

08 Great Britain 40 India

10 USA 41 South Korea

11 Ireland 42 Taiwan

12 Belgium 43 New Zealand

13 Australia 44 Finland

14 Malaysia 45 Greece

15 Italy 46 Poland

16 South Africa 48 Philippines

17 Venezuela 58 Croatia

18 Czech Republic 61 Romania

19 Portugal 62 Slovenia

20 Norway AE United Arabic Emirates

21 Hungary BG Bulgaria

22 Japan EG Egypt

23 Sweden KW Kuwait

24 Saudi Arabia OM Oman

25 Singapore QA Qata

This is custom documentation. For more information, please visit the SAP Help Portal 144
5/14/2023

Country/Region Code Country/Region Country/Region Code Country/Region

26 Thailand UN Nonpro t Organization

27 Hong Kong

28 China

29 Argentina

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

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 Addresses (Fiori 2.0)

My Bank Details (Fiori 2.0)

My Communication Data (Fiori 2.0)

My Family Members (Fiori 2.0)

My Internal Data (Fiori 2.0)

My Pro le (Fiori 2.0)

Component for Customer Incidents


PA-FIO-PER

App History: My Personal Data (Fiori 2.0)


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.

This is custom documentation. For more information, please visit the SAP Help Portal 145
5/14/2023
The app has been enhanced as follows:

SAP Fiori for SAP ERP HCM 2.0 SPS 8 (Delivery Date 10/2019)

New Key Features


New localizations (country/region speci c screens for
editing data) are available

Allows you to use the app in the following new


country/region versions:

Sweden

Thailand

Slovakia

Ukraine

South Korea

Finland

Philippines

Croatia

Romania

Slovenia

Bulgaria

Greece

New Extensibility Options New Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

SAP Fiori for SAP ERP HCM 2.0 SPS 7 (Delivery Date 07/2019)

New Key Features


New localizations (country/region speci c screens for
editing data) are available

Allows you to use the app in the following new


country/region versions:

Argentina

Chile

Columbia

Egypt

Hong Kong

Hungary

Indonesia

Ireland

Kuwait

Malaysia

This is custom documentation. For more information, please visit the SAP Help Portal 146
5/14/2023
New Zealand

Oman

Portugal

Qatar

Singapore

South Africa

Taiwan

Venezuela

Nonpro t Organization (NPO)

An employee is allowed to maintain data for another


employee on-behalf.

New Extensibility Options New Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

You can use the BAdI HCMFAB_B_COMMON to con gure the


on-behalf scenario.

You can use the BAdI HCMFAB_B_PERSINFO_SETTINGS


to disable the function to change the employee picture. You
can also set the MIME types of the employee picture that
an employee can upload.

SAP Fiori for SAP ERP HCM 2.0 SPS 6 (Delivery Date 04/2019)

New Key Feature New localizations (country speci c screens for editing data) are
available

Allows you to use the app in the following new country versions:

Belgium

Italy

Czech Republic

Japan

Russia

Poland

New Extensibility Options


Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

SAP Fiori for SAP ERP HCM 2.0 SPS 5 (Delivery Date 01/2019)

New Key Feature New localizations (country speci c screens for editing data) are
available

Allows you to use the app in the following new country versions:

Austria

Netherlands

This is custom documentation. For more information, please visit the SAP Help Portal 147
5/14/2023
Norway

Spain

Switzerland

Canada

Mexico

Australia

United Arabic Emirates

Saudi Arabia

New Extensibility Options


Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

SAP Fiori for SAP ERP HCM 2.0 SPS 4 (Delivery Date 10/2018)

New Key Feature New localizations (country speci c screens for editing data) are
available

Allows you to use the app in the following new country versions:

Brazil

India

France

China

New Extensibility Options


Extension Points to add additional elds to the forms
(Display and Edit) of the new localizations.

SAP Fiori for SAP ERP HCM 2.0 SPS 2 (Delivery Date 04/2018)
Initial delivery.

App Implementation: My Personal Data (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

The SAP product version in the back-end system serving as the basis for the app must be the following:

This is custom documentation. For more information, please visit the SAP Help Portal 148
5/14/2023

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

Implementation Tasks

This is custom documentation. For more information, please visit the SAP Help Portal 149
5/14/2023
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=F3117

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYPERSONALDATA_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

Component Technical Name

SAPUI5 Application HCMFAB_PERS_MAN

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

This is custom documentation. For more information, please visit the SAP Help Portal 150
5/14/2023

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYPERSONALDATA_SRV In addition, this role contains authorizations to OData service authorization must be
(0001 ) display the related business data. assigned.

SAP_HCMFAB_MYPERSONALDATA_APP

 Note
In addition, this role contains authorizations
to display the related business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Personal Data (Fiori 2.0)


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 con gure your own country speci c entities.

You can ll your customer speci c extension includes.

You can add additional elds to the country speci c forms used to display/edit the data.

You can adapt the behavior of elds delivered in the standard UI con guration.

You can in uence the behavior of the app with regards to the employee picture.

Extensibility Entities
Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

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 specify for which employees a person (personnel number) is allowed to maintain data on-behalf.

You can specify how the system checks if a given employee number is allowed/relevant to be used in an on-behalf
scenario for the current user.

You can de ne who is the manager of an employee.

You can add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button. You can also enable the on-behalf functionality.

This is custom documentation. For more information, please visit the SAP Help Portal 151
5/14/2023
You can check whether an employee is a manager.

BAdI: HR FIori: PersInfo Con gurations (HCMFAB_B_PERSINFO_CONFIG)

You can use this BAdI to con gure your own country speci c entity to the My Personal Data OData
Service HCMFAB_MYPERSONALDATA.

 Note
This BAdi is also relevant for the OData services of the other Personal Information SAP Fiori Apps.

In the standard system, SAP provides country-speci c BAdI implementations for a number of countries. For more
information see documentation of BAdI HCMFAB_B_PERSINFO_CONFIG.

BAdI for Enhancement of SAP Fiori App My Personal Data (HCMFAB_B_MYPERSONALDATA)

You can use this BAdI to ll your customer speci c extension includes used in the My Personal Data SAP Fiori App.

HR Fiori: PersInfo Settings (UI-relevant) (HCMFAB_B_PERSINFO_SETTINGS)

You can use this BAdI to disable the function to change the employee picture.

You can also set the MIME types of the employee picture that an employee can upload.

Extension Points

To enhance the app, the following extension points are available:

Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time: Extens

99_Display_Default_V001.view.xml extensionFormContent PersonalData HCMFAB_S_PERS_P

Allows you to add PersonalDataDefault


additional elds to the
international form (Display)

99_Edit_Default_V001.view.xml extensionFormContent PersonalData HCMFAB_S_PERS_P

Allows you to add PersonalDataDefault


additional elds to the
international form (Edit)

++_Display_Default_V001.view.xml extensionFormContent PersonalData++ HCMFAB_S_PERS_P

++ = number of country version Allows you to add PersonalData++Default


additional elds to the
The following localizations are available:
country version form
(Display)
(01) (31) Slovakia
Germany
(32) Mexico
(02)
(33) Russia
Switzerland

(03) Austria (34)


Indonesia
(04) Spain
(36) Ukraine
(05)
(37) Brazil
Netherlands

(06) France (38)


Colombia

This is custom documentation. For more information, please visit the SAP Help Portal 152
5/14/2023

Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time: Extens

(07) Canada (39) Chile

(08) Great (40) India


Britain
(41) South
(10) USA Korea

(11) Ireland (42) Taiwan

(12) (43) New


Belgium Zealand

(13) (44) Finland


Australia
(45) Greece
(14)
(46) Poland
Malaysia

(15) Italy (48)


Philippines
(16) South
(58) Croatia
Africa
(61)
(17)
Romania
Venezuela

(18) Czech (62)

Republic Slovenia

(AE) United
(19)
Arabic
Portugal
Emirates
(20) Norway
(BG)
(21) Bulgaria
Hungary
(EG) Egypt
(22) Japan
(KW) Kuwait
(23)
Sweden (OM) Oman

(QA) Qatar
(24) Saudi
Arabia (UN)
Nonpro t
(25)
Organization
Singapore
(NPO)
(26)
Thailand

(27) Hong
Kong

(28) China

(29)
Argentina

++_Edit_Default_V001.view.xml extensionFormContent PersonalData++ HCMFAB_S_PERS_P

++ = number of country version Allows you to add PersonalData++Default


additional elds to the
country version form (Edit)

This is custom documentation. For more information, please visit the SAP Help Portal 153
5/14/2023
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
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 .

Adapt Fields of the Standard UI Con guration

You can adapt the behavior of the elds delivered with the standard UI con guration of the app in following way:

Set editable (Field property Can be edited)

Set invisible (Field property Invisible)

Set read-only (Field property Output Only)

Set mandatory (Field Property Required Entry)

To do so, use the view VT588MUIFPROPC (Customer: Field Properties of UI Fields) as described blow.

1. Open view VT588MUIFPROPC in transaction SM31 and choose the relevant Work Area. In this case this is Infotype
0002.

2. Choose New Entries and enter the following data:

a. Context: ESSWDAPERS

b. IT Version: Select the relevant country.

c. Subtype: Choose the relevant subtype.

d. UI Structure Name/Field Name: Choose relevant structure and eld.

e. Field Property: Choose the property you want to assign to the eld.

3. Repeat step 2 for each eld where you want to change the standard behavior.

4. Save your entries.

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 .

My Pro le (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Pro le you can enable employees to display an overview of his own information like incomplete
time recording, upcoming leave, upcoming courses. You can also view your company pro le, organizational and communication
details as well as navigate to the employee hierarchy.

Key Features
The following information can be displayed based on con guration settings:

An employee who is concurrently employed can use the app for a chosen personnel assignment

View time balances

This is custom documentation. For more information, please visit the SAP Help Portal 154
5/14/2023
View missing/incomplete time recording and the next upcoming leave

View upcoming courses

View your quali cations and skills information

View your performance information

View your progression in the company

View your payslips

View your salary and bonus information

View your personal information

Allows you to create, update, and delete time events for a speci c date ( via a connected app)

Allows you to create, update, and delete your personal information (via connected apps), such as:

Addresses

Bank Details

Communication Data

Family Members

Internal Data

Personal Data

Allows you to specify the details of your physicians, and smoking status

 Note
By default, this feature is only available in Canada and the USA.

Allows you to maintain the details of the external organizations you are associated with

 Note
By default, this feature is only available in Canada and the USA.

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.

Access to linked apps is provided via push buttons. Only those buttons are visible where the linked app is assigned to the user's
catalog.

Employee Lookup (Version 2/Fiori 2.0)

My Paystubs (Version 3/Fiori 2.0)

My Time Events (Version 2/Fiori 2.0)

My Timesheet (Version 3/Fiori 2.0)

My Leave Requests (Version 3/Fiori 2.0)


This is custom documentation. For more information, please visit the SAP Help Portal 155
5/14/2023
My Addresses (Fiori 2.0)

My Bank Details (Fiori 2.0)

My Communication Data (Fiori 2.0)

My Personal Data (Fiori 2.0)

My Family Members (Fiori 2.0)

My Internal Data (Fiori 2.0)

My External Organizations (Fiori 2.0)

 Note
Only relevant for Canada and USA.

My Medical Information (Fiori 2.0)

 Note
Only relevant for Canada and USA.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

For more information, see the app implementation document of this app.

Component for Customer Incidents


PA-FIO-PRO

App History: My Pro le (Fiori 2.0)


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 2 (Delivery Date 04/2018)

This is custom documentation. For more information, please visit the SAP Help Portal 156
5/14/2023
New Key Feature View your personal information

Allows you to create, update, and delete personal information (via


connected apps) such as:

Addresses

Bank Details

Communication Data

Family Members

Internal Data

Personal Data

New Extensibility Options


Enhancement Spot to add additional elements to the
Addresses form: extensionAddressForm

Enhancement Spot to add additional elements to the Bank


Details form: extensionBankDetailForm

Enhancement Spot to add additional elements to the


Communication Data form:
extensionCommunicationDataForm

Enhancement Spot to add additional elements to the Family


Members form: extensionFamilyMembersForm

Enhancement Spot to add additional elements to the


Internal Data form: extensionInternalDataForm

Enhancement Spot to add additional elements to the


Personal Data form: extensionPersonalDataForm

SAP Fiori for SAP ERP HCM 2.0 SPS 1 (Delivery Date 01/2018)
Initial delivery.

App Implementation: My Pro le (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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)

This is custom documentation. For more information, please visit the SAP Help Portal 157
5/14/2023
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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

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.

This is custom documentation. For more information, please visit the SAP Help Portal 158
5/14/2023
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=F3129

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYPROFILE_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

Component Technical Name

SAPUI5 Application HCMFAB_PRFL_MON

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

This is custom documentation. For more information, please visit the SAP Help Portal 159
5/14/2023

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYPROFILE_SRV (0001 ) In addition, this role contains authorizations OData service authorization must be
to display the related business data. assigned.

SAP_HCMFAB_PRFL_MON_APP

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Pro le (Fiori 2.0)


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 control the visibility of the delivered user interface sections.

You can de ne your own mechanisms to fetch the information for an employee and the periods for which the information
is provided.

You can extend the information displayed in the app on your customer needs.

You can extend the app by adding additional elds and actions.

You can adjust the object page header of the app.

You can add additional elements to forms.

Extensibility Entities

Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

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 an employee.

You can de ne who is a direct report of a manager.

You can de ne who is the manager of an employee.

You can add additional employee information shown in the employee data.

You can de ne how the system determines the employee picture.

This is custom documentation. For more information, please visit the SAP Help Portal 160
5/14/2023
You can de ne how the system determines the office address.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

You can check whether an employee is a manager.

BAdI for My Pro le Fiori App (HCMFAB_B_MYPROFILE)

You can use this BAdI to provide your own implementation to fetch the information for the employee in My Pro le app. In
addition, you can de ne the periods for which the information is provided. The BAdI implementation also provides
exibility to control the visibility (hide/show) of the user interface sections in the SAP Fiori app.

You can implement the logic that provides the information of the employee about salary, absence data, time balance,
time recording, trainings, career process, compensation, performance rating and quali cation.

BAdI for Customer Enhancements in My Pro le Fiori App (HCMFAB_B_MYPROFILE_ENRICH)

You can use this BAdI to provide additional information in My Pro le app depending on your customer needs. You can
enrich the following entities:

Con guration

For example you can add an additional section to the user interface.

Paystub

Absences

Time Balance

Training

Time Recording

Carrer Progress

Compensation

Performance Rating

Quali cation

Colleagues

Extension Points

To enhance the app, the following extension points are available:

UI Back End/ABAP

View Extension Point/Purpose Design Time: Design Time: Extens


Gateway Entity

ProfileOverview.view.xml extensionProfileHeaderActions - -

Allows you to add actions to the My


Pro le app header

This is custom documentation. For more information, please visit the SAP Help Portal 161
5/14/2023

UI Back End/ABAP

View Extension Point/Purpose Design Time: Design Time: Extens


Gateway Entity

ProfileOverview.view.xml extensionProfileHeaderContent EmployeeDetail HCMFAB_S_EMPLOY

Allows you to add elds to the My Pro le


app header

ManagerQuickview.fragment.xml extensionManagerQuickview EmployeeDetail HCMFAB_S_EMPLOY

Allows you to add additional elements to


the Manager quickview

ObjectPageSections.fragment.xml extensionProfileSections - -

Allows you to add additional sections to


the My Pro le app

OfficeInfoQuickview.fragment.xml extensionOfficeInfoQuickview EmployeeDetail HCMFAB_S_EMPLOY

Allows you to add additional elements to


the Office Info quickview

PersInfoAddressBlock.view.xml extensionAddressForm Address HCMFAB_S_PERS_A

Allows you to add additional elements to


the Addresses form

PersInfoBankBlock.view.xml extensionBankDetailForm BankDetail HCMFAB_S_PERS_B

Allows you to add additional elements to


the Bank Details form

PersInfoCommunicationDataBlock.view.xml extensionCommunicationDataForm Communication HCMFAB_S_PERS_C

Allows you to add additional elements to


the Communication Data form

PersInfoFamilyMembersBlock.view.xml extensionFamilyMembersForm FamilyMember HCMFAB_S_PERS_F

Allows you to add additional elements to


the Family Members form

PersInfoInternalDataBlock.view.xml extensionInternalDataForm InternalData HCMFAB_S_PERS_I

Allows you to add additional elements to


the Internal Data form

PersInfoPersonalDataBlock.view.xml extensionPersonalDataForm PersonalData HCMFAB_S_PERS_P

Allows you to add additional elements to


the Personal Data form

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
This is custom documentation. For more information, please visit the SAP Help Portal 162
5/14/2023
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 hooks are available in the controller code:

Controller Hook Use

ProfileOverview.controller.js extHookAdjustObjectPageHeader Allows you to adjust the My Pro le app


header

If there are additional UI controller hooks available in the controller code, you can add own code. For more information, 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 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 .

My Reporting (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Reporting (Fiori 2.0), you can launch and display different kinds of reports related to employees,
organizational units and other organizational objects according to individual selection views and selection periods.

Key Features
Launch and display of employee-speci c reports and other reports related to assigned orgnaizational objects

Adaptation of selection periods and selection views of report results lists

Creation of report variants as well as setting of default report variants

Sorting of report results by column

Display of totals and subtotals

Download of report results

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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:

This is custom documentation. For more information, please visit the SAP Help Portal 163
5/14/2023
Front-End Components Delivered with (Product Version Stack) SAP Fiori 2.0 for SAP ERP HCM ( 17 (03/2022) )

For more information, see the app implementation document of this app.

Component for Customer Incidents


PA-FIO-REP

App History: My Reporting (Fiori 2.0)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 11 (Delivery Date 09/2020)
Initial delivery.

App Implementation: My Reporting (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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:

This is custom documentation. For more information, please visit the SAP Help Portal 164
5/14/2023

App Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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

2896044
Fiori MSS: My Reporting
2957006
HCMFAB_REP_MON - Automatic Maint Upload

On the front-end server, the following SAP notes must be implemented for this app:

SAP Note Number Description

2957006 HCMFAB_REP_MON - Automatic Maint Upload

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=F4940

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYREPORTING_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


This is custom documentation. For more information, please visit the SAP Help Portal 165
5/14/2023

Component Technical Name

SAPUI5 Application HCMFAB_REP_MON

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYREPORTING_SRV (0001 ) In addition, this role contains authorizations OData service authorization must be
to display the related business data. assigned.

SAP_HCMFAB_REP_MON_APP

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Reporting (Fiori 2.0)


Extensibility information for SAP Fiori app.

This is custom documentation. For more information, please visit the SAP Help Portal 166
5/14/2023
You can extend the app according to your business needs for different aspects. For this purpose, the following extensibility
options are available:

Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

Settings for the My Reporting App (HCMFAB_B_MYREPORTING)

You can use this BAdI to de ne and group the reports offered in the app, de ne the related selection views and selection
periods, and to adapt the settings for the sorting, column headers, totals and subtotals of the corresponding results
lists. For more information, see the related BAdI documentation.

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, to de ne who is a
colleague of an employee, to de ne who is a direct report of a manager, to de ne who is the manager of an employee, to
de ne how the system determines the employee picture, to set the visibility of certain UI elements, such as employee
picture, employee number and CE functionality button, and to check whether an employee is a manager.

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 .

My Team (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Team (Fiori 2.0) you can display an overview of your team, tailored to your speci c needs. You can
choose from three options: a list view, a grid view and an organizational chart. The elds in the list and in the grid view are
customizable and provide general information about your employees. By clicking on a tile or a row, you will be redirected to the
employee's pro le. From the list view and the organizational chart, you can display a quick view by clicking on the name of the
employee. From within the grid view, you can open the quick view via a separate button.

Another important feature allows you to execute apps on behalf of your employees. This can be triggered via a distinct button
from within all views or the employee's pro le.

Key Features
Overview of the manager's team, available as a list view, a grid view or an organizational chart

Direct access to the employee's pro le

Usage of apps on behalf of your employees

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.

This is custom documentation. For more information, please visit the SAP Help Portal 167
5/14/2023
A key feature of the app My Team is that you can execute apps on behalf of your team members and thus on behalf of another
personnel number.

The app also allows you to navigate from one app to another. You can choose the target apps for this feature from a list of HCM
apps for the employee role. Which of these apps can technically be added as navigation targets is described in SAP Note
2990502 . In the standard delivery, the following apps are de ned as navigation targets that can be carried out on behalf of
another employee:

My Addresses

My Bank Details

My Communication Data

My Familiy Members

My Internal Data

My Leave Requests

My Personal Data

If you want to de ne your own Fiori apps as navigation targets, please see App Extensibility: My Team (Fiori 2.0) for further
details.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

For more information, see the app implementation document of this app.

Component for Customer Incidents


PA-FIO-MT

App History: My Team (Fiori 2.0)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 12 (Delivery Date 12/2020)
Initial delivery.

App Implementation: My Team (Fiori 2.0)


This is custom documentation. For more information, please visit the SAP Help Portal 168
5/14/2023
Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

This is custom documentation. For more information, please visit the SAP Help Portal 169
5/14/2023

SAP Note Number Description

not available not available

On the front-end server, the following SAP notes must be implemented for this app:

SAP Note Number Description

not available not available

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=F4941

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYTEAM_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

Component Technical Name

SAPUI5 Application HCMFAB_TEAM_MAN

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 :

This is custom documentation. For more information, please visit the SAP Help Portal 170
5/14/2023
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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYTEAM_SRV (0001 ) In addition, this role contains authorizations OData service authorization must be
to display the related business data. assigned.

SAP_HCMFAB_TEAM_MAN_APP

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Team (Fiori 2.0)


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:

Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

BAdI for My Team (Fiori) (HCMFAB_B_MYTEAM)

You can use this BAdI to con gure the screens of the My Team app in a way that suits your needs. You can choose which
data is provided on the overview screen or in the employee's pro le, and you can decide which apps can be executed on
behalf of your team members. Moreover, you can allow or disallow the following features:

drilldowns, thus displaying the direct reports of your direct reports

executing apps on behalf of your team members or on behalf of the direct reports of your team members

displaying the organizational chart

Common BAdI for all HCM Fiori Apps (HCMFAB_B_COMMON)

You can use this BAdI to enhance HCM SAP Fiori apps delivered with software component UIHR002, to

de ne who is a colleague of an employee

de ne who is a direct report of a manager

de ne who is the manager of an employee

de ne how the system determines the employee picture


This is custom documentation. For more information, please visit the SAP Help Portal 171
5/14/2023
set the visibility of certain UI elements, such as employee picture, employee number, and the concurrent
employment (CE) functionality

check whether an employee is a manager.

Extension Points

View Extension Point Use

EmployeeQuickview.fragment.xml extensionEmployeeQuickview Allows you to add additional


elements to the employee quick
view

EmployeeDetailsHeader.fragment.xml extensionEmployeeDetailsHeaderContent Allows you to add additional


elds to the employee details
header

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
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

Controller Hook Use

MyTeamOverview.controller.js extHookAdjustTeamOverviewConfigModel Allows you to enable


personalization and/or to
disable the employee quick
view

MyTeamOverview.controller.js extHookAdjustTeamOverviewHeader Allows you to adjust the


content of the team
overview page, such as
header, title, actions

EmployeeDetails.controller.js extHookAdjustEmployeeDetailsConfigModel Allows you to show/hide


empty data views via the
model parameter
bShowEmptyDataViews

EmployeeDetails.controller.js extHookAdjustEmployeeDetailsHeader Allows you to adjust the


content of the employee
details page, such as
header, title, actions

EmployeeDetails.controller.js extHookAdjustEmployeeDetailsSimpleForm Allows you to adjust the


layout of the simple form
showing the employee
details

App.controller.js extHookGetCustomerOwnCrossAppNavigationHash Allows you to de ne the


routing hash for customer-
speci c cross-app
navigation

App.controller.js extHookGetCustomerOwnCrossAppNavigationInfo Allows you to de ne an icon


and a text for a customer-
speci c cross-app
navigation target

This is custom documentation. For more information, please visit the SAP Help Portal 172
5/14/2023

Controller Hook Use

App.controller.js extHookGetCustomerOwnEmployeeQuickview Allows you to de ne your


own employee quick view

App.controller.js extHookGetCustomerOwnCrossAppNavigationIntent Allows you to de ne a


customer-speci c
semantic object/action
combination (intent)

 Note
If you want to de ne the routing hash, an icon or a text for your own navigation target, the following hooks need to be
implemented:

extHookGetCustomerOwnCrossAppNavigationHash

 Sample Code

extHookGetCustomerOwnCrossAppNavigationHash: function (sApplicationId, sEmployeeNumber) {


// Place your hook implementation code here
var sHash = "",
sSemanticObject = "",
sAction = "",
oCrossAppNavigator = sap.ushell && sap.ushell.Container && sap.ushe

//define own semantic object/action


switch (sApplicationId) {
case "ZZCUSTOMER_OWN":
sSemanticObject = "ZZCUSTOM";
sAction = "manageCustomerOwn";
break;
default:
}

if (sSemanticObject && sAction) {


sHash = oCrossAppNavigator && oCrossAppNavigator.hrefForExternal({
target: {
semanticObject: sSemanticObject,
action: sAction
},
params: {
"zzEmployeeNumber": [sEmployeeNumber]
}
});
}
return sHash;
}

extHookGetCustomerOwnCrossAppNavigationInfo

 Sample Code

extHookGetCustomerOwnCrossAppNavigationInfo: function (sApplicationId, oCustomerOwnOnBehalfTask)


// Place your hook implementation code here

This is custom documentation. For more information, please visit the SAP Help Portal 173
5/14/2023
switch (sApplicationId) {
case "ZZCUSTOMER_OWN":
//define own icon
oCustomerOwnOnBehalfTask.icon = "sap-icon://customer";
//define own text
oCustomerOwnOnBehalfTask.text = "My customer own app text";
break;
default:
}
}

If you want to de ne your own semantic object/action combination (intent), the following hook needs to be implemented:

extHookGetCustomerOwnCrossAppNavigationIntent

 Sample Code

extHookGetCustomerOwnCrossAppNavigationIntent: function (sApplicationId) {


// Place your hook implementation code here
switch (sApplicationId) {
case "MYPERSONALDATA":
return {
semanticObject: "ZEmployee",
action: "zzCustManagePersonalData"
};
default:
return null;
}
}

If there are additional UI controller hooks available in the controller code, you can add own code. For more information, 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 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 .

My Team Calendar (Version 2/Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Team Calendar (Version 2) you can view the upcoming events, trainings, leaves, and work
schedule of your colleagues or direct reports.

Key Features

This is custom documentation. For more information, please visit the SAP Help Portal 174
5/14/2023
View the upcoming absences and training courses for your colleagues or direct reports (only available if employees
report to you).

 Note
If you choose to display one of the weekly calendar views, the start date of the calendar depends on the Customizing
settings that have been made for the working week.

Choose the start date for your calendar using one of the available calendar views.

View the work schedule of your colleagues or direct reports.

Add your own views or enhance standard views.

Add employees to the standard view or to your own views (no approval required).

Ask colleagues to share their calendars to add them to one of the views (approval required).

Accept or reject sharing requests from other employees in the team calendar directly or by using a work ow.

Display all employees in the respective view. You can also choose to only display employees with events along with the
details of these events, or all absent employees.

 Note
You can display the details of the events by choosing the event in the calendar.

Hide employees by removing them temporarily from the standard view or your own views.

View an employee picture and (by default) the job description (can be changed to any other text).

An employee who is concurrently employed can use the app for a speci c personnel assignment.

Download an Excel le containing your team calendar data for a certain time period. You can choose between different
events (absences, non-working days, and so on) and different levels of detail shown in the le.

Display a customizable quick view of the selected employee, which allows you to see additional employee data, such as
their email address or office location.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

For more information, see the app implementation document of this app.

Component for Customer Incidents


PA-FIO-CAL

This is custom documentation. For more information, please visit the SAP Help Portal 175
5/14/2023

App History: My Team Calendar (Version 2)


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 16 (Delivery Date 12/2021)

New Key Features


You can now download an Excel le of calendar data for a
certain time period displaying certain events such as
absences, non-working day, and so on.

Customizable quick views for employees are now available


in your calendar providing additional employee information,
such as their office location or email address.

You can choose the start date for your calendar from even
more calendar views.

You can now choose to share your calendar and ask your
colleagues to share theirs.

Sharing requests can be accepted or rejected either in the


team calendar directly orby using a work ow.

SAP Fiori for SAP ERP HCM 2.0 SPS 0 (Delivery Date 07/2017)
Initial delivery.

App Implementation: My Team Calendar (Version 2)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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)

This is custom documentation. For more information, please visit the SAP Help Portal 176
5/14/2023
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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

2103156 Launching Fiori apps in standalone mode

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.

This is custom documentation. For more information, please visit the SAP Help Portal 177
5/14/2023
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=F1309A

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_COMMON_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

Component Technical Name

SAPUI5 Application HCMFAB_TCAL_MON

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

This is custom documentation. For more information, please visit the SAP Help Portal 178
5/14/2023

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_COMMON_SRV (0001 ) In addition, this role contains authorizations OData service authorization must be
to display the related business data. assigned.

SAP_HCMFAB_TCAL_MON_APP

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Team Calendar (Version 2)


Extensibility information for SAP Fiori app.

You can extend the app My Team Calendar (Version 2) according to your business needs for different aspects. For this purpose,
the following extensibility options are available to extend the team calendar control:

You can remove UI elements (for example employee foto, lter function, search function, CE button, legend button) from
the user interface of the team calendar control.

You can de ne which event types are displayed and in which color.

You can de ne which views are displayed on the user interface. In the standard delivery, the team calendar control
always displays the colleagues view for employees and the directs report view when the current user is a manager.

You can de ne whether employees can create their own views.

You can de ne on which views an employee can add additional employees to the list.

You can de ne which text is displayed in the employee description below the employee's name.

You can add additional information by extending the entities of the team calendar control.

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-In are available for extensibility purposes:

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 an employee.

You can de ne who is a direct report of a manager.

This is custom documentation. For more information, please visit the SAP Help Portal 179
5/14/2023
You can de ne who is the manager of an employee

You can de ne how the system determines the employee picture.

You can set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

You can check whether an employee is a manager.

Settings for Team Calendar (HCMFAB_B_TEAMCALENDAR_SETTINGS)

You can use this BAdI to customize the team calendar control.

 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.

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.

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 .

My Time Events (Version 2/Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Time Events (Version 2) you can enable employees to create, update, and delete time events for
a speci c date. In addition, the app noti es employees of missing or incorrect time entries.

Key Features
Create time events for a speci c date

Update time events for a speci c date

Delete time events for a speci c date

Select time event types as favorites for quick entries

Receive messages that indicates missing or incorrect time entries

This is custom documentation. For more information, please visit the SAP Help Portal 180
5/14/2023
Download time statement for a speci c period

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.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

For more information, see the app implementation document of this app.

Component for Customer Incidents


PA-FIO-CIO

App History: My Time Events (Version 2)


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.

App Implementation: My Time Events (Version 2)


Implementation information for SAP Fiori app.

This is custom documentation. For more information, please visit the SAP Help Portal 181
5/14/2023

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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

This is custom documentation. For more information, please visit the SAP Help Portal 182
5/14/2023

SAP Note Number Description

not available not available

On the front-end server, the following SAP notes must be implemented for this app:

SAP Note Number Description

not available not available

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=F1506A

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYTIMEEVENTS_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

Component Technical Name

SAPUI5 Application HCMFAB_TIME_EVT

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 :

This is custom documentation. For more information, please visit the SAP Help Portal 183
5/14/2023
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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYTIMEEVENTS_SRV (0001 ) In addition, this role contains authorizations OData service authorization must be
to display the related business data. assigned.

SAP_HCMFAB_TIME_EVT_APP

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Time Events (Version 2)


Extensibility information for SAP Fiori app.

You can extend the My Time Events (Version 2) app according to your business needs for different aspects. For this purpose, the
following extensibility options are available:

You can add buttons to the footer of the change and in the overview view.

You can add cells to the table of time events list.

You can add controls to the overview view.

You can control the visibility of UI elds in the overview view.

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:

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 set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

BAdI for My Time Events (Version 2) SAP Fiori App (HCMFAB_B_CICO_CREATE_CUST)

This is custom documentation. For more information, please visit the SAP Help Portal 184
5/14/2023
You can use this BAdI to control the visibility of UI elds such as Event Time, and Approver Note for Approver in the
overview view of the app.

Extension Points

To enhance the app, the following extension points are available:

View Extension Point Use

ChangeView.view.xml ChangeViewFooterExtension Allows you to add buttons to the footer of


change view

Overview.view.xml OverviewCellExtension Allows you to add cells to the table of time


events list

Overview.view.xml OverviewControlExtension Allows you to add controls to the overview


view

Overview.view.xml OverviewFooterExtension Allows you to add buttons to the footer of


overview view

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
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 hooks are available in the controller code:

Controller Hook Use

ChangeView.controller.js hcm.fab.mytimeevents.controller.Overview~extHookOnUpdate Allows you


to change
business
logic on cli
Update

ChangeView.controller.js hcm.fab.mytimeevents.controller.Overview~extHookCreatePostObject Allows you


to modify
the object
sent for
update.

The hook
method is
called whe
the decisio
options for
the detail
item are
fetched
successfu

This is custom documentation. For more information, please visit the SAP Help Portal 185
5/14/2023

Controller Hook Use

Overview.controller.js hcm.fab.mytimeevents.controller.Overview~extHookOnChangeOfDate Allows you


to change
the busine
logic on
change of
the selecte
date in the
calendar

Overview.controller.js hcm.cico.view.S1~extHookOnCreate Allows you


to change
the busine
logic on cli
Create

Overview.controller.js hcm.cico.view.S1~extHookCreatePostObject Allows you


to modify
the object
sent to
create or
delete.

The hook
method is
called whe
the decisio
options for
the detail
item are
fetched
successfu

Overview.controller.js hcm.cico.view.S1~extHookOnDelete Allows you


to change
business
logic on cli
Delete

If there are additional UI controller hooks available in the controller code, you can add own code. For more information, 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 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 .

My Timesheet (Version 3/Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Timesheet (Version 3/Fiori 2.0), as an employee, you can manage your time entries quickly and
efficiently using your desktop or mobile device.

This is custom documentation. For more information, please visit the SAP Help Portal 186
5/14/2023

Key Features
An employee who is concurrently employed can use the app to enter time records for the chosen personnel assignment
by selecting Enter Records.

Create or import assignments using the Assignment tab.

Select + to create an assignment. Specify the assignment name, and the duration of the assignment.

 Note
When you select the eld Validity Period, the rst selection allows you to specify the starting date, and the
second selection allows you to specify the ending date. You can also enter the dates without using the
calendar.

Specify the working time attribute, such as absence type of your assignment.

To import assignments, select Import and specify the worklist or admin assignment to import from.

Import assignments from worklist.

The assignment name is populated using the text from the worklist, if text is available. The BAdI used is
HCMFAB_B_TSH_ENRICH. The Interface method ENRICH_WORKLIST is used to pre- ll the default assignment
name from the following worklist elds - Project Description (CATSW-CPR_TEXT), Project Subobject (CATSW-
CPR_OBJTEXT), Name (CATSFIELDS-DISPTEXTW1) and Name (CATSFIELDS-DISPTEXTW2). You can also
change the default name of the assignment in the BAdI.

Specify the elds to be selected in the worklist using the Customizing activity De ne Field Selection, by
navigating to Cross-Application Components Time Sheet CATS Regular Record Working Time .

View calendar for two months on desktop, and one week on mobile. You can specify the starting day of the week to be
displayed in the calendar.

 Note
When you select a day in the calendar, the corresponding week is selected.

Enter time records

View weekly time entry details at a glance, and release or delete the entries with one-step.

 Note
In a desktop and tablet, the system displays records of one week time period. On a mobile device it displays
the records for the selected day.

Create time entry for a single day or multiple days in a single step.

Mark your entry as draft.

Add, edit or delete comments for your entry.

Duplicate assignment or week

Select Duplicate Assignment to copy one or more existing assignments to the required dates. If the duplicated
dates are for a different week than the current week, the new dates are displayed with the assignments below
the current week’s time entries. The additional entries remain on the screen until the next input.

Select Duplicate Week to copy the week’s assignments to one or more weeks. The new week(s) are displayed with
the assignments below the current week.

This is custom documentation. For more information, please visit the SAP Help Portal 187
5/14/2023
Specify columns to be displayed in the week.

Select Settings icon and choose the columns to be displayed. You can also change the order of the columns to be
displayed.

Easily access the to-do list.

Select To-Do List tab to view the missing or incomplete entries.

Select Enter Records to complete the entries.

 Note
Recorded entries include those in submitted or draft status.

Create and manage assignment groups

Assignment groups enable you to easily add multiple assignments for adding time entries.

In the Assignments tab, select the required assignments and select Create Group. Specify the name of the group
and save.

In the Overview tab, when entering records, you can select the created assignment group from the Assignment
list.

Select Assignment Groups tab to edit or delete assignment groups.

Easily lter time records according to the status of the record. Select the drop-down list in Overview tab to lter records
according to Draft, Submitted, Approved or Rejected status.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

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:

Approve Timesheets (Version 3/Fiori 2.0)

Component for Customer Incidents


PA-FIO-TS

App History: My Timesheet (Version 3/Fiori 2.0)


This is custom documentation. For more information, please visit the SAP Help Portal 188
5/14/2023
App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 04 (Delivery Date 10/2018)
Initial delivery.

App Implementation: My Timesheet (Version 3/Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

This is custom documentation. For more information, please visit the SAP Help Portal 189
5/14/2023

App Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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

2691220
My Timesheet application based on Fiori 2.0
2725894
My Timesheet V3 (Fiori 2.0): Software Component and
Support package information

On the front-end server, the following SAP notes must be implemented for this app:

SAP Note Number Description

2691220
My Timesheet application based on Fiori 2.0
2725894
My Timesheet V3 (Fiori 2.0): Software Component and
Support package information

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=F3074

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_TIMESHEET_MAINT_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

Component Technical Name

SAPUI5 Application HCMFAB_MY_TIME

This is custom documentation. For more information, please visit the SAP Help Portal 190
5/14/2023
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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_TIMESHEET_MAINT_SRV In addition, this role contains authorizations OData service authorization must be
(0001 ) to display the related business data. assigned.

SAP_HCMFAB_MY_TIME_APP

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Timesheet (Version 3/Fiori 2.0)


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:

This is custom documentation. For more information, please visit the SAP Help Portal 191
5/14/2023

Front End Extension Points


The following front-end extension points are available on the different layers. You have to extend each of these entities
according to your speci c business needs:

UI

View Extension Point

Worklist Worklist.view.worklistPageActionsExtension

Worklist Worklist.view.overviewTableToolbarExtension

Worklist Worklist.view.overviewTableRowsExtension

Worklist Worklist.view.todolistTableColumnsExtension

Worklist Worklist.view.todolistTableToolbarExtension

Worklist Worklist.view.todolistTableRowsExtension

Worklist Worklist.view.assignmentsTableToolbarExtension

Worklist Worklist.view.assignmentGroupsTableToolbarExtension

Worklist Worklist.view.worklistFooterExtension

Worklist Worklist.view.worklistPageHeaderExtension

Worklist Worklist.view.worklistTabSectionExtension

EditAssignment EditAssignment.view.editAssignmentActionsExtension

EditAssignment EditAssignment.view.editAssignmentTabSectionsExtension

EditAssignment EditAssignment.view.editAssignmentFooterExtension

createGroup createGroup.view.createGroupActionsExtension

createGroup createGroup.view.createGroupTabSectionsExtension

createGroup createGroup.view.createGroupFooterExtension

Further Extensibility Entities


Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

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 set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

BAdI de nition for lling admin assignments (HCMFAB_B_TSH_ADMIN_ASSIGNMENTS)

You can use this BAdI to provide a set of assignments for the users. For example, generic assignments may be stored by
the administrator in the HCMFAB_ASSIGNMNT (CATS Assignments) table. You can use this BAdI to implement a
customized logic to lter the required assignments suitable for speci c users. From the My Timesheet (Version 3/ Fiori
2.0) app, the user can import this set of assignments using the Import Admin Assignments functionality.

BAdI de nition for enriching entities (HCMFAB_B_TSH_ENRICH)

This is custom documentation. For more information, please visit the SAP Help Portal 192
5/14/2023
You can use this BAdI to enrich the entities provided by the ODATA service for the application. The default
implementation for the BADI method ENRICH_WORKLIST populates name for the entries from the worklist. The text
elds, if any, in the worklist entries will be used as name for the worklist entry. The order of priority in selecting the text
eld is given below:

1. cProject Text (cpr_text)

2. cProject Object Text(cpr_objtext)

3. Display Field1 (disptextw1)

4. Display Field2 (disptextw2)

You can override this priority by creating a custom implementation for the BAdI method.

BAdI to invoke custom value help (HCMFAB_B_TSH_PICKLIST_TXTFLTR)

You can use this BAdI to invoke custom value help for the search string, instead of the standard value help.

BAdI to determine elds for which value texts are displayed (HCMFAB_B_TSH_TEXTFIELDS)

You can use this BAdI to display custom text for the elds, instead of the standard text.

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 .

My Time Statements (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Time Statements (Fiori 2.0), as an employee, you can display your time statements for any
period. By default, the app displays the time periods for one year. You can select the required period, and also view additional
information.

Key Features
View information about the work hours planned, hours worked, overtime, deviation hours and absence hours.

Specify the time periods to be displayed, by selecting the dates in the date-range selector. The rst selection allows you
to specify the starting date, and the second selection allows you to specify the ending date. You can also enter the dates
without using the calendar.

Create customized time statement by selecting Custom Time Statement.

Download detailed time statement.

Select the columns to be displayed.

Sort and group the rows to be displayed.

System Landscape Requirements


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:

This is custom documentation. For more information, please visit the SAP Help Portal 193
5/14/2023
Required Back-End Product (Product Version Stack) SAP Fiori 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

For more information, see the app implementation document of this app.

Component for Customer Incidents


PT-EV-FO

App History: My Time Statements (Fiori 2.0)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 04 (Delivery Date 10/2018)
Initial delivery.

App Implementation: My Time Statements (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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.
This is custom documentation. For more information, please visit the SAP Help Portal 194
5/14/2023
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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

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=F3430

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_MYTIMESTATEMENTS_SRV (0001 )

For more information about how to activate the OData service, see Front-End Server: Activate OData Services .

This is custom documentation. For more information, please visit the SAP Help Portal 195
5/14/2023

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application HCMFAB_MYTIM_ST

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_MYTIMESTATEMENTS_SRV In addition, this role contains authorizations to OData service authorization must be
(0001 ) display the related business data. assigned.

SAP_HCMFAB_MY_TIME_STATEMENT

 Note
In addition, this role contains authorizations
to display the related business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Time Statements (Fiori 2.0)

This is custom documentation. For more information, please visit the SAP Help Portal 196
5/14/2023
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:

UI Extension Points
You can extend each of these entities according to your speci c business needs:

UI

View Extension Point Description

TimeStatementList.view.xml timestatementsToolbarExtension Allows you to add additional information to


the toolbar of the table.

TimeStatementList.view.xml timestatementsColumnsExtension Allows you to add additional columns to the


table.

Further Extensibility Entities


Business Add-Ins (BAdIs)

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 set the visibility of some UI elements, such as employee picture, employee number and CE functionality
button.

oData BAdI (HCMFAB_B_MYTIMESTATEMENTS)

You can use this BAdI to enhance the information displayed in the Time Statement, by implementing the following
methods:

ENRICH_TIMESTATEMENT – Additional information about the Time Statement can be included and displayed in
the screen.

ENRICH_TIMESTATEMENT_DISPLAY– Additional key elds ca be included and passed to generate the time
statement.

UI Controller Hooks

The following hook is available in the controller code:

Controller Hook Use

TimeStatementList.controller.js hcm.fab.timeevstatements.view.TimeStatementList Allows you to adjust


~ extHookAdjustViewModel the display of the time
statement

If there are additional UI controller hooks available in the controller code, you can add own code. For more information, 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 UI Controller Hooks .

More Information
This is custom documentation. For more information, please visit the SAP Help Portal 197
5/14/2023
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 .

Process Inbox (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app Process Inbox (Fiori 2.0), as a manager or HR administrator, you can view the list of work items for
approval and process them further.

Key Features
View the list of work items

Approve, reject, or withdraw work items

Save work items as drafts

Add comments to work items

Add attachments to work items

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 enables you to upload documents. For security reasons, we strongly recommend that you install a virus scanner
in your system landscape. For more information, see Virus Scanning.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

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:

Start Process

Component for Customer Incidents

This is custom documentation. For more information, please visit the SAP Help Portal 198
5/14/2023
PA-FIO-PNF

App History: Process Inbox (Fiori 2.0)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 07 (Delivery Date 07/2019)
Initial delivery.

App Implementation: Process Inbox (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

This is custom documentation. For more information, please visit the SAP Help Portal 199
5/14/2023

App Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

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=F3646

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_PROCESS_INBOX_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

Component Technical Name

This is custom documentation. For more information, please visit the SAP Help Portal 200
5/14/2023

Component Technical Name

SAPUI5 Application HCMFAB_PRO_INB

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_PROCESS_INBOX_SRV (0001 In addition, this role contains authorizations OData service authorization must be
) to display the related business data. assigned.

SAP_HCMFAB_PROCESSINBOX_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 installed My Inbox app.

You have integrated Process Inbox app with My Inbox app.

Con guration Tasks

This is custom documentation. For more information, please visit the SAP Help Portal 201
5/14/2023
To be able to implement the app, you must perform the following con guration tasks in the back-end system:

Con guring SWFVISU for Intent-based Navigation

To map a task in Process Inbox to the target SAPUI5 Fiori app, do the following for the Process and Forms custom Fiori tasks:

Execute transaction code SWFVISU.

Choose the Process and Forms custom Fiori tasks and set the Visualization Type as Intent-Based Navigation.

For example, if TS13600232 is a Process and Forms custom task, choose task TS13600232 and select Visualization
Parameter in the dialog structure on the left pane.

Con gure the parameters as below:

Visualization Parameter Value for approval

SEMANTIC_OBJECT BusinessProcess

ACTION manage

QUERY_PARAM00

QUERY_PARAM01

QUERY_PARAM09

The above example creates a mapping between a task with the Task De nition ID TS13600232 to an application with
the action manage and semantic object BusinessProcess.

Con gure the Visualization Parameters as explained above, for all the Process and Forms custom Fiori tasks.

Remove work items in Draft status from My Inbox

The work items in Draft status, created via the Start Process app must not be visible in My Inbox app.

To ensure that workitems in Draft status are not displayed in My Inbox app, do the following:

Navigate to SPRO and follow the path SAP Gateway Service Enablement Content Work ow Settings Enable Task
Filter

Activate the lter settings by executing Enable Task Filter.

Execute Maintain Task Names and Decision Options

Specify the work ows along with step ID for all the processes in the system which should be visible in My Inbox. Add all
the work ows except standard Save Draft (WS13600356).

An example to add work ow and step ID is shown below.

Work ow ID Step ID Icon MIME Repository Path Step Description

WS90500003 0000000030 Approve Form

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 technical catalog SAP_FND_BC_MANAGER_T of My Inbox Tile.

This is custom documentation. For more information, please visit the SAP Help Portal 202
5/14/2023

Semantic Action Application Title URL ID Parameters


Object Type

Business manage SAPUI5 Fiori Process /sap/bc/ui5_ui5/sap/hcmfab_pro_inb hcm.fab.process.inbox Name:


Process App Inbox openMode

Mandatory: X

Value:
replaceDetail

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: Process Inbox (Fiori 2.0)


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 to enhance the value help functionality.

You can extend the app to enhance the standard behavior after the user selects a process to execute.

Further Extensibility Entities


Business Add-Ins (BAdIs)

The following Business Add-In is available for extensibility purposes:

BAdI for Process Inbox (HCMFAB_B_ PROCESS_INBOX_ENRICH )

You can use this BAdI to enhance the OData services for the Process Inbox Fiori app. The following methods are available
in this BAdI:

ENRICH_FIELDVALUEHELP - Enables you to enhance the value help functionality.

ENRICH_PROCESSRECORD_METADATA - Enables you to enhance the functionality after the user selects a
process to execute.

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 .

Start Process (Fiori 2.0)


Abstract for SAP Fiori apps.

This is custom documentation. For more information, please visit the SAP Help Portal 203
5/14/2023
With the transactional app Start Process (Fiori 2.0) you can start any precon gured process, according to the roles assigned to
you.

Key Features
Start a precon gured process.

View the list of available processes

View details of each process, including status of the process

Add comments to the process

Add attachments to the process

Send the process for further action to the Process Inbox app, accessible via My Inbox app.

Users with the role of an employee, manager or HR administrator, can execute the processes according to the back-end
con gurations

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 enables you to upload documents. For security reasons, we strongly recommend that you install a virus scanner
in your system landscape. For more information, see Virus Scanning.

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

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:

Process Inbox, accessed via My Inbox

Component for Customer Incidents


PA-FIO-PNF

This is custom documentation. For more information, please visit the SAP Help Portal 204
5/14/2023

App History: Start Process (Fiori 2.0)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 07 (Delivery Date 07/2019)
Initial delivery.

App Implementation: Start Process (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

This is custom documentation. For more information, please visit the SAP Help Portal 205
5/14/2023

App Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
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:

SAP Note Number Description

not available not available

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=F3596

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFAB_START_PROCESS_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

Component Technical Name

This is custom documentation. For more information, please visit the SAP Help Portal 206
5/14/2023

Component Technical Name

SAPUI5 Application HCMFAB_PROCESS

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFAB_START_PROCESS_SRV (0001 In addition, this role contains authorizations OData service authorization must be
) to display the related business data. assigned.

SAP_HCMFAB_STARTPROCESS_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:

Con guration Tasks


To be able to implement the app, you must perform the following con guration tasks in the back-end system:

This is custom documentation. For more information, please visit the SAP Help Portal 207
5/14/2023
The Design Time Tool for SAP HCM Processes and Forms (transaction code HRASR_DT) is used to create processes and their
related objects such as work ow templates, form scenarios, and forms. You can also use this tool to specify the required
settings for the processes and objects. To use Start Process app, you must rst create the Fiori forms and con gure the
metadata for the elds in the forms.

Create Fiori form

In the transaction HRASR_DT , use the Form Type Fiori Form to create a new Fiori form. Add the elds required in the Fiori form
from the Field node and save the form.

You can also convert an existing Form Scenario to Fiori Form types. You can choose Copy or Copy with Dependent Objects for
an existing form, and convert it to a Fiori form.

Con gure metdata for the elds

The elds added are displayed as part of Field Metadata. In Field Metadata, specify the properties for each eld. These
properties determine how the elds are rendered on the Fiori Form.

You can con gure the following column values for specifying the metadata:

 Note
Do not change the pre- lled values ( eld container, control type) for rows HRASR_CURRENT_NOTE and
HRASR_PREVIOUS_NOTES.

Name of the eld Value required Mandatory(M)/


Optional(O)

Field Name All the elds part of Fields node are Pre- lled
displayed here.

Field Label All the eld names under Fields node are Pre- lled
displayed here

Field Container Specify one the following values: M

FORM – maintain this value if the


corresponding eld is part of a
form.

TABLE - maintain this value if the


corresponding eld is part of a
table.

COMMENTS - maintain this value if


you are using custom comments.
Standard comments are pre- lled –
HRASR_CURRENT_NOTE and
HRASR_PREVIOUS_NOTES.

This is custom documentation. For more information, please visit the SAP Help Portal 208
5/14/2023

Name of the eld Value required Mandatory(M)/


Optional(O)

Control Type Choose one of the following values: M

DROPDOWN

CHECKBOX

TEXT

INPUT

RADIO

COMMENT – use only when Field


Container value is COMMENTS

DATEPICKER

TEXTAREA

NONE

Field Container ID Enter an ID for the corresponding container M

Field Container Sequence Enter the sequence in which the containers M


are to displayed in the UI. For example,
1,2,3 and so on.

Container Title Enter the container title here. O

Type Kind Specify the type of the eld. You can choose O
one of the following values:

STRING

CHARACTER

INTEGER

DECIMAL

BOOLEAN

DATE

Field Length Enter the length of eld if the Control Type O


is INPUT.

Field Precision Enter the precision of the eld if the Control O


Type is INPUT.

Field Scale Enter the length of eld if the Control Type O


is INPUT.

Field Sequence Enter the sequence in which the elds are to M


displayed in the UI.

Group Name Group Name corresponds to a Section title M


in the UI. A group of elds can be viewed
under one section. Enter the group name
here.

Group ID Enter an ID for the corresponding group M


here.

This is custom documentation. For more information, please visit the SAP Help Portal 209
5/14/2023

Name of the eld Value required Mandatory(M)/


Optional(O)

Group Sequence Enter the sequence in which the groups are M


to displayed in the UI.

Has Value Help Check the box if the eld has value help. O

F4 Parent Field Enter the Field Name if the corresponding O


eld has a dependent eld.

Operation Enter any user events here. O

Verify the con gured metadata using the CHECK icon.

Work ow con guration

With Fiori forms, the following tasks can be used to con gure the work ow:

13600231 Process Form-Fiori

13600232 Approve Form- Fiori

13600233 Draft: Fiori

13600234 Forward to expert: Fiori

WS13600359 Save Form with Error Handling : Fiori

WS13600356 Draft for Process Start: Fiori(event to be maintained is


DRAFT_CREATED_FIORI)

WS13600357 Work ow for forward to expert ( event to be maintained is


DRAFT_TO_ERROR_AGENT_FI)

13600235 Check Form Data - Fiori

13600236 Save Form Data Fiori

13600237 Form Edited Again by Author-Fiori

Release Information

For release information and cookbook, see 2673872 .

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: Start Process (Fiori 2.0)


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 to enhance the list of processes displayed for an employee.

This is custom documentation. For more information, please visit the SAP Help Portal 210
5/14/2023
You can extend the app to enhance the value help functionality.

You can extend the app to enhance the list of processes displayed on the overview screen of the Start Process app with
status as ʻIncomplete’, ʻCompleted’ or ʻIn Process’.

You can extend the app to enhance the direct reports functionality.

You can extend the app to enhance what happens after the user selects a process to execute.

You can extend the app to enhance what happens after the user selects a process in status Incomplete from the initial
screen of the Start Process app.

Extensibility Entities
Business Add-Ins (BAdIs)

The following Business Add-In is available for extensibility purposes:

BAdI for Start Process(HCMFAB_B_START_PROCESS_ENRICH)

You can use this BAdI to enhance the Start Process app functionalities. The following methods are available in this BAdI:

ENRICH_PROCESSLIST

ENRICH_FIELDVALUEHELP

ENRICH_DRAFTLIST

ENRICH_DIRECT_REPORTS

ENRICH_PROCESSRECORD_METADATA

ENRICH_DRAFTRECORD_METADATA

HCMFAB_ASR_PROCESS

You can use this BAdI to enhance the OData services for the Start Process app. The following methods are available in
this BAdI:

CHANGE_PROCESS_ATTRIBUTES- Enables to lter the process list.

GET_ADMIN_EMPLOYEES

- Enables to specify the administrator.

GET_ADMIN_PERNR

- Enables to specify reporting employee for the administrator.

SET_FIO_BUTTONS

- Enables to de ne custom buttons for a user event.

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 .

Country/Region-Speci c Services and Localizations


This is custom documentation. For more information, please visit the SAP Help Portal 211
5/14/2023
The following apps are country speci c:

My Online Selections

My Online Selections (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Online Selections (Fiori 2.0) you can select, view, and change your online selections, such as
receiving your Online W-2 instead of paper.

Key Features
Display and/or change your online selections

System Landscape Requirements


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) ()

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) ( )

For more information, see the app implementation document of this app.

Component for Customer Incidents

App History: My Online Selections (Fiori 2.0)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 14 (Delivery Date 06/2021)
Initial delivery.

App Implementation: My Online Selections (Fiori 2.0)


Implementation information for SAP Fiori app.

System Landscape Requirements


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

This is custom documentation. For more information, please visit the SAP Help Portal 212
5/14/2023
prerequisites:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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)

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 Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components ( ) ()

Back-End Components () ()

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

On the front-end server, the following SAP notes must be implemented for this app:

SAP Note Number Description

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:

Front-End Server : Activate OData Services

Component Technical Name

This is custom documentation. For more information, please visit the SAP Help Portal 213
5/14/2023

Component Technical Name

OData Service (Version Number) ()

For more information about how to activate the OData service, see Front-End Server: Activate OData Services .

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application

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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

() In addition, this role contains authorizations OData service authorization must be


to display the related business data. assigned.

 Note
In addition, this role contains
authorizations to display the related
business data.

More Information

This is custom documentation. For more information, please visit the SAP Help Portal 214
5/14/2023
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Online Selections (Fiori 2.0)


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:

Extensibility Entities
Business Add-Ins (BAdIs)

The following Business Add-Ins are available for extensibility purposes:

BAdI: HR FIori: PersInfo Con gurations (HCMFAB_B_PERSINFO_CONFIG)

You can use this BAdI to con gure your own country speci c entity to the My Personal Data OData Service
HCMFAB_MYPERSONALDATA.

 Note
This BAdI is also relevant for the OData services of the other Personal Information SAP Fiori Apps.

In the standard system, SAP provides country-speci c BAdI implementations for a number of countries. For more
information see documentation of BAdI HCMFAB_B_PERSINFO_CONFIG.

BAdI: BAdI for enhancement of SAP Fiori App My Election (HCMFAB_B_MYSELECTION)

You can use this BAdI to con gure your own country speci c entity to the My Online Selections OData Service
HCMFAB_LOC_MYSELECTION.

BAdI: HR Fiori: PersInfo Settings (UI-relevant) (HCMFAB_B_PERSINFO_SETTINGS)

You can use this BAdI to disable the function to change the employee picture.

You can also set the MIME types of the employee picture that an employee can upload.

Extension Points

To enhance the app, the following extension points are available:

UI Back End/ABAP

View Extension Point / Purpose Design Time: Gateway Entity Design Time: Extension
Include

10_Edit_Default_V001.view.xml extensionFormContent OnlineSelections10Default HCMFAB_B_MYSELECTION

Allows you to add OnlineSelections10


additional elds to the
international form (Edit)

More Information

This is custom documentation. For more information, please visit the SAP Help Portal 215
5/14/2023
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 .

My Employee Withholding Certi cates (Fiori 2.0)


Abstract for SAP Fiori apps.

With the transactional app My Employee Withholding Certi cates (Fiori 2.0) employees can easily check and change their
withholding information when necessary from their desktop and/or mobile devices. The app helps you to display your
withholding certi cates.

Key Features
Update or change withholding information

Display withholding information

System Landscape Requirements


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 2.0 for SAP ERP HCM (17 (03/2022))

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 ( 17 (03/2022) )

For more information, see the app implementation document of this app.

Component for Customer Incidents


PY-LOC-XF

App History: My Employee Withholding Certi cates (Fiori 2.0)


App history for SAP Fiori app.

SAP Fiori for SAP ERP HCM 2.0 SPS 16 (Delivery Date 12/2021)
Initial delivery.

App Implementation: My Employee Withholding Certi cates


(Fiori 2.0)
Implementation information for SAP Fiori app.

This is custom documentation. For more information, please visit the SAP Help Portal 216
5/14/2023

System Landscape Requirements


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:

SAP Fiori System Landscape Setup Prerequisites

Setup of SAP Fiori System Landscape for SAP Business Suite Installation Requirements

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:

 Note
The SAP product version in the back-end system serving as the basis for the app of the Feature Database is only available as
of EHP8 Stack 18.

App Component Required SAP Product Version Available Instances Containing Software Component
(Support Package Stack) Software Component Required for App (Support
Package)

Front-End Components SAP Fiori 2.0 for SAP UI for ERP HCM UIHR002 100 (0017 )
ERP HCM ( 17 (03/2022) )
UI for ERP HCM >
FES 4.0

UI for ERP HCM >


FES 4.0/7.50

UI for ERP HCM >


NW750

Back-End Components SAP Fiori 2.0 for SAP HCM ERP 605 INT GBX01HR5 605 (0021 )
ERP HCM (17 (03/2022))
HCM ERP 605 INT
NW740

For more information about the installation of front-end components, see http://help.sap.com/ ori_implementation.

This is custom documentation. For more information, please visit the SAP Help Portal 217
5/14/2023

Required SAP Notes


On the back-end server, the following SAP notes must be implemented for this app:

SAP Note Number Description

3090828
SAP Fiori Backend
3098182
SAP_HR Prerequisite

On the front-end server, the following SAP notes must be implemented for this app:

SAP Note Number Description

3090867
SAP Fiori Frontend
3098182
SAP_HR Prerequisite

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=F6080

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) HCMFABUS_MYEMPLOYEEW4_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

Component Technical Name

SAPUI5 Application HCMFABUS_EMPLOYEEW4_MAN

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

This is custom documentation. For more information, please visit the SAP Help Portal 218
5/14/2023
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.

OData Service (Version Number) Back-End Server: Delivered Authorization Front-End Server : Assignment to
Role (PFCG Role) Authorization Role

HCMFABUS_MYEMPLOYEEW4_SRV In addition, this role contains authorizations to OData service authorization must be
(0001 ) display the related business data. assigned.

SAP_HCMFABUS_MYEMPLOYEEW4_APP

 Note
In addition, this role contains authorizations
to display the related business data.

More Information
For more information about app implementation, see http://help.sap.com/ ori_implementation App Implementation
Information for SAP Fiori .

App Extensibility: My Employee Withholding Certi cates (Fiori


2.0)
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:

Further Extensibility Entities

Business Add-Ins (BAdIs)

The following Business Add-Ins is available for extensibility purposes:

BAdI: BAdI for enhancement of SAP Fiori App My Employee Withholding Certi cates
(HCMFAB_LOCUS_MYEMPL_OYEEW4_SRV)

You can use this BAdI to con gure your own country speci c entity to the OData Service for My Employee Withholding
Certi cates.

Extension Points

This is custom documentation. For more information, please visit the SAP Help Portal 219
5/14/2023
To enhance the app, the following extension points are available:

View Extension Point Use

10_Edit_Default_V001.view.xml extensionFormContent Allows you to add additional elds to the


form for USA (Edit)

10_Display_Default_V001.view.xml extensionFormContent Allows you to add additional elds to the


form for USA (Display)

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
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 hooks are available in the controller code:

Controller Hook Use

Main.controller.js extHookGetCustomEntityNameForVersionId Allows you to return a different EntityName


for an already existing country screen and
also lets you de ne a new
VersionId/EntityName pair for a newly
created country.

Main.controller.js extHookAdjustObjectPageHeaderTitle Allows to adjust the object page header title

Main.controller.js extHookAdjustObjectPageHeaderContent Allows to adjust the object page header


content

CommonCountryController.controller.js extHookDoSpeci cFieldValidation Allows to do customer-speci c eld


validation

If there are additional UI controller hooks available in the controller code, you can add own code. For more information, 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 UI Controller Hooks .

For more information about hiding UI controls, 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 Hiding UI Controls .

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 .

This is custom documentation. For more information, please visit the SAP Help Portal 220

You might also like