Extending the Create Entry view
1.28 My Travel Requests
PUBLIC Page 110 of 138
With the transactional app My Travel Requests , you can manage your own travel requests in real time using your desktop or mobile device. The app allows you to create, edit, submit, and delete requests. You can also check the status of a particular request at any time.
Key Features
Create a new travel request
Submit travel requests to your organizational manager Browse existing travel requests in detail
Edit existing travel requests and resubmit Delete existing travel requests
System Landscape Requirements
The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori.
Product Version Containing Back-End and Front-End Components of the App
SAP Fiori principal apps for SAP ERP 1.0 SPS03
Back-End Product Versions Supporting the App (Minimum Product Version Stack)
SAP ERP 6.0 SP15 or higher
SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher
SAP Fiori System Landscape Options Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible:
Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS
Related Apps
Approve Travel Expenses Approve Travel Requests
Component for Customer Messages
MOB-UIA-FI-MTR: My Travel Requests
More Information
App History: My Travel Requests App Implementation: My Travel Requests App Extensibility: My Travel Requests
1.28.1 App History: My Travel Requests
The My Travel Requests app has been enhanced as follows:
SAP Fiori for SAP ERP Principal Apps 1.0 SPS 003 (Delivery Date 07/2014)
No changes.
SAP Fiori for SAP ERP Principal Apps 1.0 SPS 002 (Delivery Date 05/2014)
No changes.
SAP Fiori for SAP ERP Principal Apps 1.0 SPS 001 (Delivery Date 02/2014)
No changes.
SAP Fiori for SAP ERP Principal Apps 1.0 SPS 00 (Delivery Date 11/2013)
Initial delivery.
1.28.2 App Implementation: My Travel Requests
System Landscape Requirements
For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP :
Back-End/Front-End Server Back-End/Front-End Component Technical Name of Software Component Support Package Level
Back-end server Back-end component SRA004 1.0 04
Front-end server Front-end component UIX01TRV 100 02
Required SAP Notes
For My Travel Requests , the following SAP Notes must be available:
Back-End/Front-End Server SAP Note Number Description
For more information, see the collective SAP Note. 1980943 Collective SAP Note listing all relevant SAP Notes for this app.
Implementation Tasks
The following sections list tasks that have to be performed to implement the < My Travel Requests > app. The tables contain the app-specific data required for these tasks:
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) SRA004_SRV (1)
For more information about activating OData services, see Front-End Server: Activate OData Services.
Front-End Server: Activate UI5 Application
Component Technical Name
UI5 Application ui5_fi_trreq_cr
For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.
Front-End Server: Enable App for Access in SAP Fiori Launchpad
There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps.
Component Technical Name
Semantic Object
Business Role SAP_TRAVEL_BCR_EMPLOYEE_X1
Business Catalog SAP_TRAVEL_BC_EMPLOYEE_X1
Business Catalog Group SAP_TRAVEL_BCG_EMPLOYEE_X1
Technical Role Technical Catalog LPD_CUST Role
LPD_CUST Instance
Front-End and Back-End Server: Assign Role with OData Service Authorization to Users
To grant access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end 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 adjust this role according to your needs.
On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
PUBLIC Page 112 of 138
OData Service (Version Number) Back-End Server: Delivered Authorization Role (PFCG Role)
Front-End Server: Authorization Role
SRA004_SRV (1) SAP_FIN_TR_CRE_APP Use an existing role or create a new one.
For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.
More Information
For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.
1.28.3 App Extensibility: My Travel Requests
You can extend My Travel Requests according to your business needs for different aspects. For this purpose, the following extensibility options are available:
Extension Points
To extend My Travel Requests , you can use the following extension points:
Name: extInfoAdditionalData Location: detail.view.app.xml Purpose: Add data to the information tab Name: extTabs
Location: detail.view.app.xml Purpose: Add a new tab to the tab container Name: Additionalbuttons
Location: detail.controller.js Purpose: Add buttons to the footer toolbar
More Information
For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.
1.29 My Spend
With the transactional app My Spend , you can track the budget and spending status of your departments and projects, anywhere and anytime. This app consolidates budget and spending information and visualizes it in an easy-to-consume way.
Key Features
View budget and actual spending data of your departments and projects
Display the overview of a specific area, including the budgeted and actual spending Drill down by various dimensions and to the corresponding accounts
Note
This app runs on desktops and tablets, but not on smartphones.
System Landscape Requirements
The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the front-end components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori.
Product Version Containing Back-End and Front-End Components of the App
SAP Fiori principal apps for SAP ERP 1.0 SPS03
Back-End Product Versions Supporting the App (Minimum Product Version Stack)
SAP ERP 6.0 SP15 or higher
SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher
SAP Fiori System Landscape Options Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible:
Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS
Component for Customer Incidents
MOB-UIA-FI-MS
More Information
App History: My Spend App Implementation: My Spend App Extensibility: My Spend
1.29.1 App History: My Spend
The My Spend app has been enhanced as follows:
SAP Fiori principal apps for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014)
No changes.
SAP Fiori principal apps for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014)
No changes.
SAP Fiori principal apps for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014)
No changes.
SAP Fiori principal apps for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013)
Initial delivery.
1.29.2 App Implementation: My Spend
System Landscape Requirements
Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape:
SAP Fiori System Landscape Options Setup of SAP Fiori System Landscape with ABAP Environment Based on SAP enhancement package 7 of SAP ERP 6.0 also possible:
Setup of SAP Fiori System Landscape with SAP HANA Database Setup of SAP Fiori System Landscape with SAP HANA XS Configuration of Front-End Server Configuration of SAP Fiori Infrastructure
Back-End Product Versions Supporting the App (Minimum Product Version Stack)
SAP ERP 6.0 SP15 or higher
SAP enhancement package 2 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS05 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS03 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS01 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher
Product Version Containing Back-End and Front-End Components of the App
SAP Fiori principal apps for SAP ERP 1.0 SPS03
For more information on the installation of the back-end and front-end components of the app, see Installation of Back-End Components and Installation of Front-End Components.
For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori principal apps for SAP ERP :
Back-End/Front-End Server Back-End/Front-End Component Technical Name of Software Component Support Package Level
Back-end server Back-end component SRA012 1.0 03
Front-end server Front-end component UIX01EAP 100 03
PUBLIC Page 114 of 138
Required SAP Notes
For My Spend , the following SAP Notes must be available:
Back-End/Front-End Server SAP Note Number Description
Back-end server and front-end server 1940348 Collective SAP Note for the My Spend app
Implementation Tasks
The following sections list tasks that have to be performed to implement the My Spend app. The tables contain the app-specific data required for these tasks:
Front-End Server: Activate OData Services
Component Technical Name
OData Service (Version Number) SRA012_SPEND_SRV (0001)
For more information about activating OData services, see Front-End Server: Activate OData Services.
Front-End Server: Activate UI5 Application
Component Technical Name
UI5 Application FIN_SPE_MON
For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.
Front-End Server: Enable App for Access in SAP Fiori Launchpad
There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps.
For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad.
Component Technical Name
Semantic Object CostObjectVariance
Business Role SAP_FIN_BCR_CostManager_X1
Business Catalog SAP_FIN_BC_CostManager_X1
Business Catalog Group SAP_FIN_BCG_CostManager_X1
Technical Role SAP_FIN_SPE_MON_APP
Technical Catalog SAP_FIN_TC_T_X1
LPD_CUST Role UIX01FI
LPD_CUST Instance TRANSACTIONAL
Front-End and Back-End Server: Assign Role with OData Service Authorization to Users
To restrict access to OData services to specific users, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end 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 adjust this role according to your needs.
On the front-end server, you can 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: Authorization Role
SRA012_SPEND_SRV (1) SAP_FIN_SPE_MON_APP SAP_FIN_BCR_CostManager_X1
For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.
Configuration Tasks
To enable My Spend , you must perform the following configuration tasks:
User role configuration:
Front-end system (gateway system)
1. Run transaction SU01, specify a user and click Edit . 2. On the Roles tab, enter the following roles: