Configuration of SAP Fiori Infrastructure

PDF download from SAP Help Portal:

http://help.sap.com/fiori_bs2013/helpdata/en/25/4a4c52eea9c871e10000000a44176d/frameset.htm

Created on October 15, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC Page 1 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.
 Table of content
1 Configuration of SAP Fiori Infrastructure
1.1 Setup of SAP Fiori Launchpad
1.1.1 Activate OData Services for SAP Fiori Launchpad
1.1.2 Activate SICF Services for SAP Fiori Launchpad
1.1.3 Assign Administrator Role for SAP Fiori Launchpad to Administrat
1.1.4 Assign Role with Launchpad Start Authorization to End Users
1.1.5 Configure a Logout Screen for the SAP Fiori Launchpad (Optional)
1.1.6 Create RFC Connection for Back-End Transactions (Fact Sheets)
1.2 Setup of SAP Fiori Search
1.2.1 Enable SAP Fiori Search for Multiple Systems (Optional)
1.3 Enable SAP Fiori Fact Sheets for Multiple Systems (Optional)
1.4 Setup of SAP Smart Business Modeler (Analytical Apps)
1.5 Integrating SAP Lumira (Optional)
1.6 Integrating SAP Jam (Optional)
1.7 Long Material Number in SAP Fiori Apps (Transactional Apps)
1.8 Running Apps in Standalone Mode (Transactional Apps)
1.9 Preparing SAP Fiori Apps for Offline Use
1.9.1 Configuring SAP Fiori Apps for Offline Use
1.10 Configuration Using Task Lists

PUBLIC Page 2 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.
 1 Configuration of SAP Fiori Infrastructure

In this section, you set up the central SAP Fiori infrastructure before installing individual apps in your SAP Fiori system landscape.

1.1 Setup of SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to the apps, from desktop and mobile devices. You need to configure the SAP Fiori launchpad so that users can
access those apps that have been assigned to their respective role.
For detailed information about the configuration tasks for the SAP Fiori launchpad, see the following documentation:

For SAP NetWeaver 7.31, see SAP Library for User Interface Add-On 1.0 on SAP Help Portal at http://help.sap.com/nw-uiaddon Application
Help SAP Library SAP Fiori Launchpad Setting Up the Launchpad .
For SAP NetWeaver 7.4, see SAP Help Portal at http://help.sap.com/nw74 Application Help UI Technologies in SAP NetWeaver SAP Fiori
Launchpad Setting Up the Launchpad .

Note
From SAP NetWeaver 7.4 Support Package 6, you can perform setup tasks for SAP Fiori by using task lists that SAP delivers. A task list groups
configuration tasks logically and guides you through the necessary tasks.
For an overview of all task lists and tasks for SAP Fiori, see Configuration Using Task Lists.

The following task list applies to this step:

SAP_FIORI_LAUNCHPAD_INIT_SETUP

1.1.1 Activate OData Services for SAP Fiori Launchpad

The activation of the OData services and of the ICF services are required to initially set up the SAP Fiori launchpad and the SAP Fiori launchpad designer.
SAP Gateway provides the infrastructure for the OData services used by the SAP Fiori launchpad, and the SAP Fiori apps. An OData service has to be
enabled in SAP Gateway which establishes a mapping between the technical OData service name and the corresponding back-end service.

Note
From SAP NetWeaver 7.4 Support Package 6, you can perform setup tasks for SAP Fiori by using task lists that SAP delivers. A task list groups
configuration tasks logically and guides you through the necessary tasks.
For an overview of all task lists and tasks for SAP Fiori, see Configuration Using Task Lists.

The following task list applies to this step:

SAP_FIORI_LAUNCHPAD_INIT_SETUP

Prerequisites
When activating the OData services, the system alias must be the local system.
To configure that a local connection to SAP Gateway is used, proceed as follows:
1. In Customizing (transaction SPRO), choose SAP NetWeaver Gateway OData Channel Configuration Connection Settings SAP Gateway
to SAP System Manage SAP System Aliases .
2. Provide the following:

Field Value

SAP System Alias Name of the system alias (for example, LOCAL ).

Description Descriptive text for the system alias.

RFC Destination none

Local GW Make sure the checkbox is marked to specify that the system alias points to a
local SAP Gateway instance.

Procedure
1. Run transaction Activate and maintain services (/IWFND/MAINT_SERVICE) on the front-end server.
2. Use the system alias of your local system when activating the following services:

Note
Do not activate the /UI2/LAUNCHPAD service. This service is not relevant for SAP Fiori.
The service names listed below are concatenations of the namespace /UI2/ and the technical names of the individual services. Enter these
concatenations when adding new services in transaction /IWFND/MAINT_SERVICE. When searching for services, you need to search either
by namespace or by technical name.

PUBLIC Page 3 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.
 /UI2/PAGE_BUILDER_CONF
/UI2/PAGE_BUILDER_PERS
/UI2/PAGE_BUILDER_CUST
/UI2/INTEROP
/UI2/TRANSPORT
The services are activated in your customer namespace, with the following technical names, for example:
ZINTEROP
ZPAGE_BUILDER_CONF
ZPAGE_BUILDER_CUST
ZPAGE_BUILDER_PERS
ZTRANSPORT
3. Call each service once by selecting it in transaction Activate and maintain services (/IWFND/MAINT_SERVICE), then choosing Call Browser in the
screen area ICF Nodes . Select the OData node, not the SDATA node.
You have called a service successfully when an XML document is displayed without any error messages.

Note
When you call a service, a hash key is generated in the background. The hash key is required for the generation of authorization profiles under
Assign Administrator Role for SAP Fiori Launchpad to Administrator User.
You can verify the hash key generation in table USOBHASH in transaction Data Browser (SE16). In the selection screen, specify the following:
R3TR in the PGMID field
IWSG in the Object field
The technical service name in the OBJ_NAME field
The hash key should be displayed in the NAME column of the results table.

1.1.2 Activate SICF Services for SAP Fiori Launchpad

In addition to the ICF services that correspond to the OData services you have to activate the following ICF services manually.

Note
From SAP NetWeaver 7.4 Support Package 6, you can perform setup tasks for SAP Fiori by using task lists that SAP delivers. A task list groups
configuration tasks logically and guides you through the necessary tasks.
For an overview of all task lists and tasks for SAP Fiori, see Configuration Using Task Lists.

The following task list applies for this step:

SAP_FIORI_LAUNCHPAD_INIT_SETUP

Procedure
1. Run transaction Maintain Services (SICF) on the front-end server.
2. In the menu under Service/host Activate , activate the services under the following subtrees:

Note
In the Activation of ICF Services dialog box, choose Yes with the hierarchy icon to activate all child nodes under a service.

/default host/sap/bc/ui2/nwbc/
/default_host/sap/bc/ui2/start_up
/default_host/sap/bc/ui5_ui5/sap/ar_srvc_launch
/default_host/sap/bc/ui5_ui5/sap/ar_srvc_news
/default_host/sap/bc/ui5_ui5/sap/arsrvc_upb_admn
/default_host/sap/bc/ui5_ui5/ui2/ushell
/default_host/sap/public/bc/ui2
/default_host/sap/public/bc/ui5_ui5

1.1.3 Assign Administrator Role for SAP Fiori Launchpad to

Administrator User

You copy the administrator role for the SAP Fiori launchpad delivered by SAP and assign it to your administrator user. The administrator is then authorized to
use the SAP Fiori launchpad designer.

Prerequisites
You have created an administrator user who needs extensive authorizations, such as S_SERVICE, S_DEVELOP, /UI2/CHIP, S_RFC_ACL, and
S_CTS_SADM. If applicable, create the user with the ID the user already has in the back end.

For more information about required SAP Gateway authorizations, see the following documentation:
For SAP NetWeaver 7.31, see SAP Help Portal at http://help.sap.com/nwgateway Configuration and Deployment Information Configuration

PUBLIC Page 4 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.
 Guide SAP Gateway Configuration Guide SAP Gateway Configuration User, Developer, and Administrator Roles .
For SAP NetWeaver 7.4, see SAP Help Portal at http://help.sap.com/nw74 Application Help Function-Oriented View SAP Gateway
Foundation (SAP_GWFND) SAP Gateway Foundation Configuration Guide SAP Gateway Configuration User, Developer, and Administrator
Roles .

Procedure
1. Run transaction Role Maintenance (PFCG) to copy the role SAP_UI2_ADMIN_700 to your customer namespace.
2. On the Menu tab, open the menu of the pushbutton for adding objects (+ button). Select the object type Authorization Default .
3. Choose TADIR Service from the menu for the Authorization Default . Specify the following values:
Program ID: R3TR
Object Type: IWSG
4. In the table, enter the names of your activated services in the form <technical name>_<four-digit version number with leading
zeros>, for example ZINTEROP_0001 and ZPAGE_BUILDER_CONF_0001. For the list of the activated services, see Activate OData Services for
SAP Fiori Launchpad.
5. On the Authorizations tab, choose Propose Profile Name next to the Profile Name field.
6. Choose Change Authorization Data and then Generate .
You have generated a role with five IWSG authorizations and five IWSV authorizations. The IWSV authorizations are included in the role delivered by
SAP, so they are not in your customer namespace.
7. Assign the new role to your administrator user.

1.1.4 Assign Role with Launchpad Start Authorization to End

Users

SAP delivers a predefined role with start authorizations for the SAP Fiori launchpad.

Prerequisites
You have created a user in transaction SU01, using the same user ID as on the back-end server.

Procedure
1. Run transaction Role Maintenance (PFCG) to copy the role SAP_UI2_USER_700 to your customer namespace.
2. On the Menu tab, open the menu of the button for adding objects (+ button). Choose the object type Authorization Default .
3. Choose TADIR Service from the menu for the Authorization Default . Specify the following values:
Program ID: R3TR
Object Type: IWSG
4. In the table, enter the following services:
ZINTEROP_0001
ZPAGE_BUILDER_PERS_0001
5. On the Authorizations tab, choose Propose Profile Name next to the Profile Name field.
6. Choose Change Authorization Data and then Generate .
7. Assign the new role to your test user.

1.1.5 Configure a Logout Screen for the SAP Fiori Launchpad

(Optional)

After users log out from the SAP Fiori launchpad, the browser displays a generic logout screen.
You can configure a custom HTML page that is displayed as logout screen.

Procedure
1. On the SAP Fiori front-end server that runs the SAP Fiori launchpad, start transaction Maintain Services (transaction sicf).
2. On the start screen, choose External Aliases .
3. Select a host in the hierarchy that you want to be the root node of the alias, and choose Create New External Alias .
4. Enter the following data:
External Alias : /sap/public/bc/icf/logoff
Trg Element : /sap/public/bc/icf/logoff
On the Error Pages Logoff Page tab page: In Redirect , enter the URL of the logout page in HTML format.
5. Save your entries.

More Information
For SAP NetWeaver 7.31, see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw731 Application Help Function-Oriented
View Application Server Application Server Infrastructure Connectivity Components of SAP Communication Technology Communication Between
ABAP and Non-ABAP Technologies Internet Communication Framework Development Server-Side Development Creating and Configuring ICF

PUBLIC Page 5 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.
 Services External Aliases .

For SAP NetWeaver 7.4, see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw74 Application Help Function-Oriented
View Application Server Application Server Infrastructure Functions and Tools of SAP NetWeaver Application Server Connectivity Components of
SAP Communication Technology Communication Between ABAP and Non-ABAP Technologies Internet Communication Framework Development
Server-Side Development Creating and Configuring ICF Services External Aliases .

1.1.6 Create RFC Connection for Back-End Transactions (Fact

Sheets)

From fact sheets, you can access the back-end server and start transactions there (in SAP GUI or Web Dynpro). To enable this, you need to establish a
connection between the SAP Fiori launchpad and the back-end system. Perform the following steps on the front-end server:

Note
From mobile devices or tablets, you cannot access SAP GUI or Web Dynpro transactions through the SAP Fiori launchpad.

Procedure
1. Identify the system alias for the back-end transactions as follows:
1. Run transaction Overview of Launchpads (LPD_CUST) on the front-end server.
2. Select the relevant role with Instance TRANSACTIONAL and double-click it.

Note
There is a role for each front-end application. Select the front-end application that corresponds to the back end for which you want to define the
RFC connection. Example: You want to establish an RFC connection that enables users to run the transaction Display Purchase Order in the
SAP SRM back-end system. In this case, you need to select the role corresponding to the SAP SRM front-end application.

3. In the left-hand screen area, select a row where Transaction is displayed as the Application Description . The system alias is displayed in the
right-hand screen area.
2. Create an RFC connection of type H (HTTP connection) in transaction Configuration of RFC Connections (sm59).
Use the system alias identified under 1. as the RFC Destination .
3. Enter the Target Host under Technical Settings in transaction Configuration of RFC Connections (sm59).

1.2 Setup of SAP Fiori Search

You can use the SAP Fiori Search to find apps and central business objects. To enable the SAP Fiori search in the SAP Fiori launchpad, perform the steps
described below.
The search for business objects is enabled through corresponding search models. You can find an up-to-date list of the search models delivered for SAP
Business Suite in SAP Note 1999463 .

SAP Fiori Search and SAP Fiori Fact Sheets

SAP Fiori fact sheets are based on search models, and the results list of SAP Fiori search is the main entry point to fact sheets.

Note
The setup of SAP Fiori search is a prerequisite for the use of fact sheets.

SAP Fiori fact sheets for business objects provide information on top of what is displayed in the search results. Furthermore, they enable you to navigate to
fact sheets of related business objects and to transactional apps, or to access back-end transactions, and you can drill down into a business object's details.

Note
From SAP NetWeaver 7.4 Support Package 6, you can perform setup tasks for SAP Fiori by using task lists that SAP delivers. A task list groups
configuration tasks logically and guides you through the necessary tasks.
For an overview of all task lists and tasks for SAP Fiori, see Configuration Using Task Lists.

The following task lists apply for this step:

SAP_ESH_INITIAL_SETUP_000_CLIENT
SAP_ESH_INITIAL_SETUP_WRK_CLIENT

Activities

Setup of SAP Fiori Search in the Front End

You must have set up the communication between SAP Web Dispatcher and the ABAP servers. For more information, see:
ABAP Servers: Setup of Communication

PUBLIC Page 6 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.
 SAP Web Dispatcher: Setup of Communication

Setup of SAP Fiori Search in the Back End

You must have set up the Embedded Search technology. The setup process consists of the following main steps:
1. Implement SAP Notes
Implement the SAP Notes listed in the Release Information Notes (RINs) for SAP NetWeaver Enterprise Search and for SAP Fiori Fact Sheets:
SAP NetWeaver Embedded Search (SAP Notes to be implemented on back-end server): SAP NetWeaver 7.4 Support Package Stack 6: RIN
1976027
SAP Fiori Fact Sheets (SAP Notes to be implemented on back-end and front-end server): RIN 1998490
2. Activate business functions
Activate the following business functions in Customizing for your SAP Business Suite back-end system under Activate Business Functions :
To enable SAP Fiori search and fact sheets: SAP HANA-Based Search for SAP Business Suite (BSESH_HANA_SEARCH)
For more information, see SAP Library for SAP Enhancement Package 7 for SAP ERP 6.0 on SAP Help Portal at http://help.sap.com/erp607
under Business Functions Business Functions in SAP Business Suite Foundation General Business Functions for SAP Business Suite
SAP HANA-Based Search for SAP Business Suite .
To enable fact sheets: SAP HANA-Based Navigation for SAP Business Suite (BSCBN_HANA_NAV)
For more information, see SAP Library for SAP Enhancement Package 7 for SAP ERP 6.0 on SAP Help Portal at http://help.sap.com/erp607
under Business Functions Business Functions in SAP Business Suite Foundation General Business Functions for SAP Business Suite
SAP HANA-Based Navigation for SAP Business Suite .
Furthermore, the activities under Cross-Application Components General Application Functions HANA-Based Search for SAP Business Suite
are relevant in Customizing for your SAP Business Suite application.
3. Set secondary database connection for search to SAP HANA database
Make this setting in Customizing for your back-end system under Cross-Application Components General Application Functions HANA-Based
Search for SAP Business Suite Configure Indexing Set TREX/BWA Destination or SAP HANA DB Connection .
Alternatively, you can use report ESH_ADM_SET_TREX_DESTINATION to set the database connection.
Prerequisites:
You have created a second database connection in transaction DBCO.
A database user not equal to SAP<SID> is available. Database users must have the following authorizations:
Object authorizations TREXVIADBSL and TREXVIADBSLWITHPARAMETERS
Scheme authorization SELECT for the _SYS_REPO scheme.
Scheme authorizations SELECT, ALTER, and INDEX for the SAP<SID> scheme.
For more information, see SAP Help Portal at http://help.sap.com/nw_platform under <release> Application Help Function-Oriented View
Search and Operational Analytics Embedded Search Setting Up Embedded Search Creating a Connection Between Embedded Search and SAP
HANA or TREX/BWA .
4. Activate connector-based authorization checks
To restrict the search results to the business object instances a user is authorized to see, embedded search supports authorizations based on business
object instances. In addition, authorization checks based on search connectors are supported mainly for performance reasons. For more information,
see SAP Help Portal at http://help.sap.com/nw_platform under SAP NetWeaver Enterprise Search Security Information Security Guide
Authorizations Restricting Authorizations for Searching .
Activate the connector-based authorization checks in Customizing for your back-end system under Cross-Application Components General
Application Functions HANA-Based Search for SAP Business Suite Search Configuration Set Parameters for Federated Search . Under Model
Authorization , select Check from the dropdown menu.
5. Activate UI services
Activate the following services for the Embedded Search in transaction Activate Service (SICF) in your back-end system.:
default_host sap bc webdynpro sap ESH_ADMIN_UI_COMPONENT
default_host sap bc webdynpro sap esh_eng_modeling
default_host sap bc webdynpro sap esh_eng_wizard
default_host sap bc webdynpro sap esh_search_results_ui
default_host sap bc webdynpro sap wdhc_help_center
default_host sap es cockpit
default_host sap es saplink
default_host sap es search
default_host sap es ina GetResponse
default_host sap es ina GetServerInfo
default_host sap es ina Loader
6. Create connectors
Prerequisite: You need the following authorizations:
SAP_ESH_SEARCH
SAP_ESH_LOCAL_ADMIN
Create connectors in the Connector Administration Cockpit (transaction ESH_COCKPIT).
The connectors required for each fact sheet and the relevant search software components are documented in the implementation documentation for the
single fact sheets.

Note
Note the following system behavior:
Search software components build a stack: On top of the basis component, different layers can be installed.
Search models can be available in different components: In their original component, but also in higher layer components (extension components).
Once you create a search connector in an extension component, all search models from the original component are transferred into the extension
component. You will therefore no longer find the search models in the original component.
Example:
You have created a connector for a search model originating in search component SAPAPPLH. You have created the connector via component
EAAPPLH, not via its original component SAPAPPLH.
From that moment on, all search models originating in component SAPAPPLH can only be found under the EAAPPLH node in transaction
ESH_COCKPIT.

PUBLIC Page 7 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.
 For more information about connector creation, see SAP Help Portal at http://help.sap.com/nw_platform under <release> Application Help
Function-Oriented View Search and Operational Analytics Embedded Search Setting Up Embedded Search Creating Connectors .

Note
When search models are transported, for example in the event of a system upgrade, manual steps can be required. For more information, see SAP
Help Portal at http://help.sap.com/nw_platform under <release> Application Help Function-Oriented View Search and Operational
Analytics Managing Search and Operational Analytics Search-Specific Administration Tasks and Information Transporting Search Models .

7. Start indexing of Connectors

For more information, see SAP Help Portal at http://help.sap.com/nw_platform under <release> Application Help Function-Oriented View
Search and Operational Analytics Embedded Search Setting Up Embedded Search Starting Indexing of Connectors .

More Information
Enable SAP Fiori Search for Multiple Systems

1.2.1 Enable SAP Fiori Search for Multiple Systems (Optional)

In the SAP Fiori landscape, you can connect multiple ABAP back-end servers to have the installed systems browsed by SAP Fiori search. Each back-end
server must run on an SAP HANA database and must have SAP Fiori search installed and configured.
One back-end server acts as a proxy to which the other back-end servers are connected.
The connected back-end servers act as clients. Their content can be browsed using the SAP Fiori search on the proxy.

Enable SAP Fiori Fact Sheets for Multiple Systems

The results list of SAP Fiori search is the main entry point to fact sheets.
For information about how to enable fact sheets for multiple systems, see Enable SAP Fiori Fact Sheets for Multiple Systems (Optional).

Activities
To enable SAP Fiori search for multiple systems, proceed as follows:
1. Set up SAP Fiori search on each of the back-end servers. For more information, see Setup of SAP Fiori Search.
2. Connect the search systems on the different back-end servers. For more information, see http://help.sap.com under Technology SAP
NetWeaver Platform <release> Application Help Function-Oriented View Search and Operational Analytics Embedded Search Setting Up
Embedded Search Optional: Establishing Connection to Back-End Systems .

1.3 Enable SAP Fiori Fact Sheets for Multiple Systems (Optional)

If you have configured SAP Fiori search to browse the systems installed on multiple back-end servers, you can also configure fact sheets for multiple back
ends. This enables you to call up the fact sheet of a business object listed in the search results, regardless of the system the business object resides in.
While it is possible to search across multiple systems, the data displayed in a fact sheet always comes from one system.
For more information about SAP Fiori search for multiple back ends, see Enable SAP Fiori Search for Multiple Systems.

Activities
Create system aliases in SAP Gateway.

Note
You require at least SAP Gateway 2.0, support package stack 9. For more information about how to manage system aliases in a landscape with several
back-end systems to retrieve data from, see http://help.sap.com/nwgateway under Configuration and Deployment Information Configuration Guide
SAP Gateway Configuration Guide SAP Gateway Configuration Connection Settings for SAP Gateway Hub System Connection Settings: SAP
Gateway to SAP Systems System ID in Origin Segment Parameter .

1.4 Setup of SAP Smart Business Modeler (Analytical Apps)

Prerequisites
The SAP Smart Business modeler is installed.

Activities
Configure the SAP Smart Business modeler on the front-end server.

PUBLIC Page 8 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.
 More Information
For information about how to configure the SAP Smart Business modeler, see SAP Help Portal at http://help.sap.com/ssb Tools SAP Smart
Business 1.0 Foundation Component SAP Smart Business Modeler Apps Setting up the SAP Smart Business Modeler Apps Framework .

1.5 Integrating SAP Lumira (Optional)

You use SAP Lumira to prepare and visualize data.

SAP Lumira and SAP Fiori are integrated as follows:
The SAP Lumira and All Stories apps are available for the SAP Fiori launchpad to display your SAP Lumira contents.
You can use SAP Lumira to visualize SAP Smart Business KPIs, by using the Configure KPI Tiles app that is part of the SAP Smart Business
modeler apps.

Prerequisites
SAP Fiori launchpad is running
SAP Lumira Server 1.20 or higher is running
For using the All Stories app: Stories are available on SAP Lumira Server
For visualizing SAP Smart Business KPIs: SAP Fiori analytical apps using SAP Smart Business modeler apps

More Information
For information about installing and configuring SAP Fiori, see the Administration Guide for SAP Smart Business Cockpit at http://help.sap.com/ssb
Installation, Security, Configuration, and Operations Information .
For information about the Configure KPI Tiles app, see the following documentation:
For SAP NetWeaver 7.31, see SAP Library for User Interface Add-On 1.0 on SAP Help Portal at http://help.sap.com/nw-uiaddon
Application Help SAPUI5 Application Frameworks SAP Smart Business SAP Smart Business Modeler Apps Configure KPI Tiles .
For SAP NetWeaver 7.4, see SAP Help Portal at http://help.sap.com/nw74 Application Help UI Technologies in SAP NetWeaver UI
Development Toolkit for HTML5 (SAPUI5) SAPUI5 Application Frameworks SAP Smart Business SAP Smart Business Modeler Apps
Configure KPI Tiles .
For information about setting up SAP Lumira for integration with SAP Fiori, see the SAP Lumira Server Installation Guide at
http://help.sap.com/boall_en , especially the following sections:
In version 1.20: To add the Configuration tile to SAP Fiori
In version 1.21 and higher: To prepare SAP Lumira Server for configuration
To add the Manage Lumira Extensions tile to SAP Fiori
Working with SAP Fiori

1.6 Integrating SAP Jam (Optional)

Some SAP Fiori apps contain features based on an integration with SAP Jam. SAP Jam is a collaborative environment that brings together people,
information, applications, and processes to solve business-critical problems and drive rapid results.
SAP Jam is part of the ABAP social media integration (SMI), which allows you to integrate the SAP Jam social collaboration platform across SAP
technologies such as SAP UI5.
You can configure ABAP SMI to allow the SAP Fiori launchpad and apps to use the ABAP SMI functions developed for SAP Fiori.

More Information
For information about integrating SAP Jam with SAP Fiori and the prerequisites therefore, see the SAP Library as follows:

For SAP NetWeaver 7.31, see SAP Library for User Interface Add-On 1.0 on SAP Help Portal at http://help.sap.com/nw-uiaddon Application
Help SAP Library Social Media Integration Information for Administrators Configuration Configuring ABAP SMI for SAP Fiori Apps .
For SAP NetWeaver 7.4, see SAP Help Portal at http://help.sap.com/nw74 Application Help UI Technologies in SAP NetWeaver Social
Media Integration Information for Administrators Configuration Configuring ABAP SMI for SAP Fiori Apps .

For fact sheets, also see SAP Note 2103065 for limitations regarding the integration with SAP Jam.

1.7 Long Material Number in SAP Fiori Apps (Transactional Apps)

The standard material number allows a maximum length of 18 characters. If this length is not sufficient, the long material number can be activated in the back-
end system to allow a maximum length of 40 characters.
Some SAP Fiori apps are enabled to display the long material number (MATNR_EXTERNAL) instead of the standard material number (MATRN). If the long
material number has been activated in the back-end system, the enabled SAP Fiori apps automatically display the long material number.

Prerequisites
To display the long material in your SAP Fiori apps, you have made the following settings in your back-end system:

PUBLIC Page 9 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.
 You have activated one of the following business functions:
DIMP_SDUD: Discrete Industries Mill Products
MGV_LAMA: Long Material Number
IS_AD_MPN: A&D Manufacturer Part Number
You have run the ENLM ( Enable Long Material Number ) report.

Note
The length of the long material number is set in Customizing for SAP ERP under Material Master Basic Settings Define Output Format of Material
Numbers .

1.8 Running Apps in Standalone Mode (Transactional Apps)

Several SAP Fiori apps support standalone mode. If you implement this feature, users can directly access an app without the SAP Fiori launchpad being
visible to them either by calling a URL or by launching the app in the SAP Enterprise Portal content area.
You typically use one of these options to give users direct access to selected apps that do not require contextual navigation.

More Information
For information about which SAP Fiori apps support standalone mode and how to implement it, see the following documentation:

SAP Note 2103156

For SAP NetWeaver 7.31, see SAP Library for User Interface Add-On 1.0 on SAP Help Portal at http://help.sap.com/nw-uiaddon Application
Help SAP Fiori Launchpad Configuring Navigation Running an Application Standalone .
For SAP NetWeaver 7.4, see SAP Help Portal at http://help.sap.com/nw74 Application Help UI Technologies in SAP NetWeaver SAP Fiori
Launchpad Configuring Navigation Running an Application Standalone .

1.9 Preparing SAP Fiori Apps for Offline Use

SAP Fiori apps are normally used in online mode, in which client requests are sent over a network to the back end where the business data resides. SAP has
enabled some SAP Fiori apps to run offline, when prepackaged as hybrid apps hosted inside a native container for iOS or Android. The apps are presented
as tiles within a local launchpad.
Offline-enabled apps access a local offline store containing business data that synchronizes periodically with the back end when the network connection is
restored. Registration with SAP Mobile Platform Server or SAP HANA Cloud Platform mobile services is required to initialize the creation of the offline store,
and to provide the offline OData service that moves data between the back end and the client offline store.
The following apps support offline mode:
My Accounts
My Contacts

Packager
The packager is a Node.js application that is delivered with the SAP Mobile Platform SDK for hybrid apps. You can use it to download existing SAP Fiori web
apps from the Fiori front end server and create a project that includes the web assets, list of plugins, and additional metadata for the apps. The packager uses
the SAP Mobile Secure cloud build service API to build the application binary files for iOS and Android, which can be deployed to users though SAP Mobile
Place or a third party product.

Note
This topic gives an overview of packaging for offline use, and provides configuration information that is specific to the offline-enabled SAP Fiori apps
(listed above).

For detailed, generic instructions on how to use the packager, see http://help.sap.com/mobile-platform SAP Mobile Platform SDK <3.0 SP09 or
higher> Development Information Mobilizing SAP Fiori Apps: Developer Guide Creating a Prepackaged Fiori App Using the Packager

Prerequisites
SAP Mobile Platform SDK 3.0 SP 9 PL 4 or higher is installed.
You have a current SAP Mobile Secure account.
Registration with SAP Mobile Platform is required for offline-enabled apps.
You can use SAP Mobile Platform Server SP08 PL01 or higher, or SAP HANA Cloud Platform mobile services.
See the packager documentation for a complete list of prerequisites.

Process
1. Implement the offline-enabled SAP Fiori web apps on the Fiori front end server in the usual way.
2. Define the package properties in an appConfig.js configuration file. Provide the following information:

Property Value

PUBLIC Page 10 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.
 appId Application identifier for SAP Mobile Platform registration.
Example: com.acme.fiori.app

Caution
The hybrid application must be defined in the SAP Mobile Platform
Server/HCPms admin cockpit before the app is launched on the client
device.

appName Defines the app name displayed on the device.

Example: CRM

bundleID Globally unique application identifier. Select the bundle ID carefully to ensure
that different applications do not overwrite each other, and to ensure that an
updated application will correctly replace an existing application. It is strongly
recommended to use dot notation.
Example: com.acme.crm.app

fioriURL The runtime URL to connect to the SAP Mobile Platform server
The format is <protocol>://<host>:<port>

fioriURLIsSMP true

passcodePolicy Because SAP Mobile Platform is used: Do not change this property.

prepackaged true

offline true

singleApp Not supported in SAP CRM. Do not change this property.

In the applications property array of the appConfig.js file, provide at least the following properties:

Note
To provide common UI elements, you have to include the reuse library in each package that contains SAP CRM apps.

Property My Accounts My Contacts Reuse Library

id cus.crm.myaccounts cus.crm.mycontacts sap.cus.crm.lib.reuse

title My Accounts My Contacts -

url /sap/bc/ui5_ui5/sap/crm_myacco /sap/bc/ui5_ui5/sap/crm_mycont /sap/bc/ui5_ui5/sap/crm_lib_re

unts use/sap/cus/crm/lib/reuse

intent Account-MyAccounts ContactPerson-MyContacts -

reuse - - true

scenario - - true

3. Using the packager, you start assembling the data, using the downloadfromfes command.
Result: For each package, the packager creates a set of folders and files in the target directory.
4. Using the packager, you build the package, by using the createpackage, uploadpackage, and startbuild commands.
The packager transfers the relevant information to SAP Mobile Secure to build the package.
Result: On SAP Mobile Place, the following files are provided:
IPA file (for devices running the iOS operating system)
Android application package (APK) file (for devices running the Android operating system)
5. You make the offline apps available for the users to download them.
To distribute the offline apps, you can use SAP Mobile Secure or another mobile device management (MDM) solution that provides the same
functionality.
If you use another MDM solution, download the IPA and APK files from SAP Mobile Secure, by using the downloadapp command of the packager.
6. The users install the offline apps on their devices using SAP Mobile Place or any other MDM solution.

More Information
For detailed packager instructions, see http://help.sap.com/mobile-platform SAP Mobile Platform SDK <3.0 SP09 or higher> Development
Information Mobilizing SAP Fiori Apps: Developer Guide Creating a Prepackaged Fiori App Using the Packager .

For information about implementing the SAP Fiori apps, see http://help.sap.com/fiori SAP Fiori Apps .
For information about integrating SAP Mobile Platform Server into the SAP Fiori system landscape, see http://help.sap.com/fiori System Landscape
Required for SAP Fiori Integration of SAP Mobile Platform into the SAP Fiori Landscape .
For information about SAP Mobile Platform Server, SAP Mobile Platform SDK, and SAP HANA Cloud Platform Mobile Services, see
http://help.sap.com/mobile-platform .

For information about making and managing builds using SAP Mobile Place, see http://help.sap.com/mobilesecure Mobile Place User and
Administrator Guides Mobile Secure Administration Guide .

For information about downloading and installing apps from SAP Mobile Place as an end user, see http://help.sap.com/mobilesecure Mobile Place
User and Administrator Guides Mobile Place User Guide .

1.9.1 Configuring SAP Fiori Apps for Offline Use

Activities

PUBLIC Page 11 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.
 While preparing an SAP Fiori app for offline use, you can configure, for example, the following:

Bundling SAP Fiori Apps in Different Packages

There are user groups that need different offline apps. For example, some users only need the My Contacts app in offline mode, some need the My Contacts
and the My Accounts app.
For each package of offline apps that you want to create, in Preparing SAP Fiori Apps for Offline Use, in step 2, do the following:
1. In appConfig.js , in the bundleID property, enter a unique bundle ID.
2. In the applications property array, only enter the values for the reuse library and the apps that are part of this package.

Displaying a Custom Name for the Offline App

On the mobile device of the user, a custom name for the offline app shall be displayed.
In Preparing SAP Fiori Apps for Offline Use, in step 2, do the following:
In appConfig.js , in the appName property, enter the name that the offline app will display.

Displaying a Custom Icon for the Offline App

On the mobile device of the user, a custom icon for the offline app shall be displayed.
In Preparing SAP Fiori Apps for Offline Use, after step 3, do the following:
1. After the packager successfully downloaded the required assets from the front-end server, access the target directory where the packager assembled
the data.
2. For each operating system, in the /res/<OS>/icons folder, replace the icons with custom icons.
Make sure that you provide matching icon names and resolutions.

Preparing Extended SAP Fiori Apps for Offline Use

You have extended an app and then want to make it available in offline mode.

Prerequisites
You have extended an app that is enabled to be available in offline mode.
The extended app contains the delta information compared to the original app. Therefore, you have to package the original and the extended app, but can
decide which ones to display on the users' mobile devices.
For more information, see the app-specific documentation.

Procedure
1. Make sure that the extended app contains a manifest.json file.
If the manifest.json file is missing, copy it from the target folder of the app that you extended.
Update the id and in sap.platform.abap, enter the path where the extended app is stored.
2. Only if you redefined the back-end OData service:
1. From cus.crm.lib.reuse, copy the sap.mobile section and paste it into manifest.json.
2. Change serviceRoot so that it points to the redefined OData service, for example:
serviceRoot: /sap/opu/odata/sap/ZCRM_BUPA_ODATA
3. Only if you want to change definingRequests to define which data is synchronized with the back end:
1. From cus.crm.lib.reuse, copy the sap.mobile section and paste it into manifest.json.
2. Change definingRequests as required.
4. Make sure that the extended app contains a resources.json file.
resources.json lists all files of the extended app.
If the resources.json file is missing, copy it from the target folder of the app that you extended and change it as required.
5. Prepare the extended app for offline use.
In the applications property array of the appConfig.js file, provide the following properties:
If you do not want to make the original app available on the launchpad, do not specify the intent property. That is, do not enter or delete the
intent property.
For example, for test purposes, you might want to make both the original app and extended app available.
For the original app: Set reuse to true.
For the app that contains definingRequests in the manifest.json file: Set scenario to false.
By default, this is sap.cus.crm.lib.reuse.
In title, enter the name that the extended app should display.
Set scenario to true.
For the extended app, enter the following properties:
Enter the values for the id, intent and url that you defined for the extended app.
The following example shows an applications property array with an extended app:

Syntax
01. "applications": [
{
"id": "cus.crm.mycontacts",
"title": "My Contacts",
"url": "/sap/bc/ui5_ui5/sap/crm_mycont",
"reuse": true
},
{

PUBLIC Page 12 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.
 "id": "cus.crm.myaccounts",
"intent": "Account-MyAccounts",
"title": "My Accounts",
"url": "/sap/bc/ui5_ui5/sap/crm_myaccounts"
},
{
"id": "sap.cus.crm.lib.reuse",
"url": "/sap/bc/ui5_ui5/sap/crm_lib_reuse/sap/cus/crm/lib/reuse",
"reuse": true
},
{
"id": "poc.fiori.contacts",
"intent": "ContactPerson-ZMyContactsExt",
"title": "My Contacts Ext",
"url": "/sap/bc/ui5_ui5/sap/zcrm_mycontacts",
"scenario": true
}
]

6. In Preparing SAP Fiori Apps for Offline Use, after step 3, do the following:
After running the downloadfromfes command, in the Component.js file, comment out the following sections:
The values of the sap.ca.serviceConfigs array. For example:

Syntax
01. metadata: {
config: {
"sap.ca.serviceConfigs": [
//{
//name: CRM_BUPA_ODATA",
//serviceUrl: "/sap/opu/odata/sap/Z_CRM_BUPA_ODATA/",
//isDefault: true,
//useBatch: true,
//countSupported: true,
//mockedDataSource: jQuery.sap.getModulePath("cus.crm.mycontacts")+"/model/metadata.xml"
//},

The module registration for the original app. For example:

Syntax
01. //jQuery.sap.registerModulePath("cus.crm.mycontacts","/sap/bc/ui5_ui5/sap/crm_mycont");

7. Continue with building the package.

1.10 Configuration Using Task Lists

You can perform ABAP system configuration tasks in an automated way by using predefined task lists.
For SAP Fiori, task lists support you in setting up and configuring the communication channels between the client, the front-end, and the back-end servers.

Prerequisites
SAP NetWeaver 7.4 SPS 6 or later
To get all predefined task lists that are available for your support package stack level, you must implement the following SAP Notes:

SAP NetWeaver 7.4 SPS SAP Note

SPS 6 2017302

SPS 7 2017302

SPS 8 2088777
2120509

SPS 9 2088777
2120509

SPS 10 2120509

Note
You must have at least SAP NetWeaver 7.4 SPS 8, to use all available task lists for an SAP Fiori front-end configuration.

For task lists regarding embedded search: SAP NetWeaver 7.4 SPS 9 or later
You are assigned the necessary roles to execute task lists.
For more information, see SAP Help Portal at http://help.sap.com/nw_platform Application Help Function-Oriented View Solution Life Cycle
Management SAP NetWeaver Configuration Configuration using ABAP Task Manager for Lifecycle Management Automation Standard Roles and
Permissions .

PUBLIC Page 13 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.
 Features
The following table lists the predefined task lists that are available for SAP Fiori. When you execute a task list, the system guides you through the
configuration of the tasks that are included in the task list. In addition, the task list contains documentation that describes the tasks in the task list in more
detail. After executing a task list, you do not have to execute the corresponding tasks manually.
Task
SAP Gateway Basic Configuration
SAP Fiori Launchpad Initial Setup
Create Trusted Connection from SAP
System to SAP Gateway
Enable Embedded Search
SAP Gateway Add Backend System
SAP Gateway Maintain System Alias
SAP Gateway Activate OData Services SAP_GATEWAY_ACTIVATE_ODATA_SERV
SAP Basis Activate HTTP Services
(SICF)
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Task List
SAP_GATEWAY_BASIC_CONFIG
SAP_FIORI_LAUNCHPAD_INIT_SETUP
SAP_SAP2GATEWAY_TRUSTED_CONFIG
SAP_ESH_INITIAL_SETUP_000_CLIEN
T initial setup of Embedded Search in
SAP_GATEWAY_ADD_SYSTEM
SAP_GATEWAY_ADD_SYSTEM_ALIAS
SAP_BASIS_ACTIVATE_ICF_NODES
Description Related Information
You use this task list on the front-end Activating SAP Gateway
server to perform basic configuration
steps for SAP Gateway.
You use this task list on the front-end Setup of SAP Fiori Launchpad
server to activate launchpad OData and
HTTP services on an SAP Gateway
system (front end).
You use this task list on the back-end Connect SAP Gateway to SAP Business
server to create a trusted connection Suite (Trusted RFC)
from an SAP system to SAP Gateway. Logon Tickets
For SAP Fiori system landscape with
Note ABAP environment:
You have to execute this task list in
ABAP Servers: Setup of
dialog.
Communication
Setting Up SSO for SAP Fiori
Landscapes with ABAP
Environments
For SAP Fiori system landscape with
SAP HANA:
ABAP Servers: Setup of
Communication
Setting Up SSO for SAP Fiori
Landscapes with SAP HANA
Databases
Setting Up SSO for SAP Fiori
Landscapes with SAP HANA XS
You use this task list for the automatic Setup of SAP Fiori Search
client 000. This task list executes the
obligatory preparation steps for the
implementation of Embedded Search.
This can take a very long time, so start
the task list in the background.
You use this task list on the front-end Creating System Alias for Applications
server to connect an SAP system (back
end) to an SAP Gateway system (front
end). The task list creates or uses an
existing trusted remote function call
(RFC) destination, checks the single
sign-on (SSO) profile parameters,
configures the SSO ticket and creates a
system alias. Changes are recorded on a
customizing request that you have to
create or select at the beginning of the
task list.
Note
The task list uses a trusted RFC
destination with the current user.
Maintain the authorization object
S_RFCACL in the back-end system
and assign the corresponding role or
profile to the current user.
You use this task list on the front-end Creating System Alias for Applications
server to create a system alias for an
existing remote function call destination.
Configure the remote function call
destination as trusted. Changes are
recorded on a customizing request that
you have to create or select at the
beginning of the task list.
You use this task list on the front-end Activate OData Services for Several SAP
server to activate OData services for the Fiori Apps
SAP Fiori apps. OData services provide
information about the app tiles to be
displayed.
You use this task list on the front-end Front-End Server: Activate ICF Services
server to activate HTTP services (SICF) of SAP UI5 Application
according to transaction SICF. ICF nodes
Page 14 of 15
 provide access to web resources.

Enable Embedded Search on work SAP_ESH_INITIAL_SETUP_WRK_CLIEN You use this task list for the automatic Setup of SAP Fiori Search
clients T initial setup of Embedded Search in work
clients. This can take a very long time, so
start the task list in the background.

On one server in same client:
SAP Gateway Basic
Configuration
SAP Fiori Launchpad Initial Setup
SAP Gateway Activate OData
Services
SAP Basis Activate HTTP
Services (SICF)
SAP_GW_FIORI_ERP_ONE_CLNT_SETUP You use this task list to configure SAP
Gateway and SAP Fiori on the same
client where the ERP system is located.
The task list consists of tasks that are
available with the following task lists:
SAP_GATEWAY_BASIC_CONFIG
SAP_FIORI_LAUNCHPAD_INIT_S
ETUP
Activating SAP Gateway
Setup of SAP Fiori Launchpad
Activate OData Services for SAP Fiori
Launchpad
Activate SICF Services for SAP Fiori
Launchpad
Activate OData Services for Several SAP
Fiori Apps

SAP_GATEWAY_ACTIVATE_ODATA Front-End Server: Activate ICF Services

of SAP UI5 Application
_SERV
SAP_BASIS_ACTIVATE_ICF_NOD
ES

Procedure
1. Decide which task list you want to execute. Refer to the table above.
2. Execute the task lists with the ABAP Task Manager for Lifecycle Management Automation, transaction STC01.
3. Display the documentation that is available in the selected task list.

More Information
For more information about working with task lists in general and the required authorizations, see the Technical Configuration Automation ABAP configuration
guide at http://service.sap.com/sltoolset Software Logistics Toolset 1.0 Documentation System Provisioning Installation: Technical
Configuration Automation ABAP .
For more information about the task lists for SAP Fiori, see the Technical Configuration Automation SAP Fiori Frontend configuration guide at
http://service.sap.com/sltoolset Software Logistics Toolset 1.0 Documentation System Provisioning Installation: Technical Configuration
Automation ABAP Fiori .
For more information about task lists for setting up Embedded Search, see Automatic Configuration Using Task Manager Task Lists in the SAP Library for
SAP Net Weaver platform at http://help.sap.com/nw_platform Function-Oriented View Search and Operational Analytics Embedded Search
Setting Up Embedded Search .

PUBLIC Page 15 of 15
2014 SAP SE or an SAP affiliate company. All rights reserved.