App Implementation: Approve Travel Requests
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:
| Database | SAP Fiori System Landscape Setup | Prerequisites |
|---|---|---|
ABAP environment |
Setup of SAP Fiori System Landscape for SAP Business Suite with ABAP Environment |
|
HANA database |
Setup of SAP Fiori System Landscape for SAP Business Suite with SAP HANA Database |
The SAP product version in the back-end system serving as the the basis for the app must be the following:
|
Required Back-End Product (Product Version Stack) |
|
-
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.
|
App Component |
Required SAP Product Version (Support Package Stack) |
Available Instances Containing Software Component |
Software Component Required for App (Support Package) |
|---|---|---|---|
|
Front-End Components |
SAP Fiori principal apps 1.0 for SAP ERP ( 09 (01/2016) ) |
|
UIX01TRV 100 (0007 ) |
|
Back-End Components |
SAP Fiori principal apps 1.0 for SAP ERP (09 (01/2016)) |
|
SRA009 600 (0008 ) |
For more information about the installation of front-end components, see http://help.sap.com/fiori_implementation.
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your respective back-end system and define sufficiently restrictive scan profiles to prevent the upload of malicious content. For more information about virus scanning and scan profiles for SAP Fiori apps, see Virus Scanning.
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:
The following sections list tasks that have to be performed to implement the required components of the app. The tables contain the app-specific data required for these tasks.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at:
https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F0411Front-End Server : Activate OData Services
|
Component |
Technical Name |
|---|---|
|
OData Service (Version Number) |
SRA009_SRV (001 ) |
For more information about how to activate the OData service, see Front-End Server: Activate OData Services .
Front-End Server: Activate SAP UI5 Application
|
Component |
Technical Name |
|---|---|
|
SAP UI5 Application |
FIN_TR_APV |
For more information about how to activate the SAP UI5 application (ICF service), see Front-End Server: Activate ICF Services.
Enable App for Access in SAP Fiori Launchpad
To define 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 find 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 procede 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.
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.
-
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 (PFCG Role) |
Front-End Server : Assignment to Authorization Role |
|---|---|---|
|
SRA009_SRV (001 ) |
In addition, this role contains authorizations to display the related business data.
Note
In addition, this role contains authorizations to display the related business data. |
OData service authorization must be assigned. |
To be able to implement the app, you must perform the following configuration tasks in the back-end system:
To be able to implement the app, you must perform the following configuration tasks in
Customizing for Travel Management under 
SAP Fiori 
Approve Travel Requests 
:
-
Define Task Types for Approval Workflow (tableSRA009_T_TASKTYP)
In this IMG activity, you define the workflow task that is used to approve travel requests.
-
Define Decision Keys for Approval Workflow (table SRA009_T_CONFIG)
In this IMG activity, you define the decision keys for approval and rejection. You need to define these keys if you are using a custom workflow to approve travel requests.
If the manager should be able to see the estimated costs by category during the approval
process, you must make the necessary settings in Customizing for Travel
Management under Travel Request Travel Request ESS Travel Mediums and Estimated Costs to Be Approved Define Travel Mediums and Estimated Costs to Be Approved .
For more information about
app implementation, see http://help.sap.com/fiori_implementation
App Implementation Information for SAP Fiori .