Fiori Configurations

Configuring SAP Fiori Apps -Quick Guide

An example-based step-by-step guide to enable the usage oftransactional SAP Fiori apps and SAP Fiori fact sheets

Version 1.2

2014-07-08

Introduction

Configuring transactional SAP Fiori Apps - Quick Guide 2

© Copyright 2014 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. The information contained herein may be changed without priornotice. Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors. No part of this publication may be reproduced ortransmitted in any form or for any purpose without the express permission of SAP AG. Theinformation contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors. National product specifications may vary.SAP Landscape Transformation Replication Server installation SAP and other SAP products andservices mentioned herein as well as their respective logos are trademarks or registered trademarksof SAP AG in Germany and other countries.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additionaltrademark information and notices.

DisclaimerThe content of this document is not part of SAP product documentation. SAP does not guarantee thecorrectness of the information provided. You may not infer any product documentation claimsagainst SAP based on this information.

Introduction


Contents

Introduction .................................................................................................................................... 5

Prerequisites ...................................................................................................................................5

Out of Scope ...................................................................................................................................6

Configuration Overview ..................................................................................................................6

Process Steps ..................................................................................................................................8

1 Preparation.............................................................................................................................12

Install and Set up SAP Web Dispatcher (Fact Sheets Only) .................................................. 121.1

Create Administrator User on Front-End Server ................................................................. 121.2

Create Test User on Front-End Server ................................................................................ 121.3

2 Initial Configuration on Front-End Server (One-Time Activities) ....................................13

Activate OData Services for SAP Fiori Launchpad ............................................................... 132.1

Activate SICF Services for SAP Fiori Launchpad................................................................... 152.2

Assign Administrator Role for SAP Fiori Launchpad to Administration User ........................ 162.3

Assign Role with Launchpad Start Authorization for End Users........................................... 182.4

Set up SAP Fiori Search (Fact Sheets Only) ......................................................................... 182.5

Perform Check: ICF Service for Fact Sheets (Fact Sheets Only) ........................................... 182.6

Perform Checks: SAP Fiori Launchpad Designer and SAP Fiori Launchpad .......................... 182.7

Perform Check: SAP Web Dispatcher (Fact Sheets Only) .................................................... 192.8

Perform Check: Search UI (Fact Sheets Only) ..................................................................... 192.9

3 App-Specific Configuration ................................................................................................. 19

Open Product Documentation for My Leave Requests App/Customer Fact Sheet ............... 193.1

Activities on Front-End Server ............................................................................................ 203.2

3.2.1 Activate ICF Services of UI5 Application (SAP Fiori Administrator) .............................. 20

3.2.2 Activate OData Service for App (SAP Fiori Administrator) ........................................... 20

3.2.3 Copy Template Business Role to Create Role with Launchpad Catalog and Group ...... 21

3.2.4 Add Start Authorizations for OData Service of Apps to Business Role ......................... 22

3.2.5 Assign Business Role to Test User on Front-End Server ............................................... 23

3.2.6 Remove Apps Not Required from Catalog (Optional Step) .......................................... 23

3.2.7 Perform Check: SAP Fiori Launchpad with App Content.............................................. 24

Activities on Back-End Server ............................................................................................. 243.3

3.3.1 Assign RFC Authorization to Test User ........................................................................ 24

3.3.2 Assign PFCG Role with OData Service Authorization to Test User ............................... 24

3.3.3 Create Search Connectors (Fact Sheets Only) ............................................................. 25

Introduction


3.3.4 Start Indexing of Search Connectors (Fact Sheets Only) .............................................. 26

3.3.5 Perform Check: SAP Fiori Launchpad with Content and Authorizations ...................... 26

Introduction


Introduction

This document guides you through the steps required to enable users to accesstransactional SAP Fiori apps and SAP Fiori fact sheets in the SAP Fiori Launchpad.

The process is described using the examples of the My Leave Requests app – atransactional app – and the Customer fact sheet. You can use it as a reference process forthe setup of any transactional app or fact sheet.

The process follows a straight-forward path with several prerequisites already in place.

This documentation gives you an insight into the setup process for SAP Fiori apps. Theapproach does not necessarily correspond to the system setup in a productiveenvironment.

For SAP Fiori app implementation in a productive environment, see the AppImplementation Information for SAP Fiori1 on the SAP Help Portal.

Note:If you use SAP NetWeaver 740 SPS 6 or higher, you can use tasklists to do the steps 2.1and 2.2.For more information about the tasklists for the setup of SAP Fiori and how to use them,see http://service.sap.com/sltoolset Software Logistics Toolset 1.0 Documentation

System Provisioning Technical Configuration Automation Fiori Frontend.

Prerequisites

The following conditions must be met:All required components are installed.For more information, see the following documentation on SAP Help Portal:

o Implementation Overview2

o System Landscape Required for SAP Fiori3.Note:For fact sheets, you need to set up the system landscape with SAPHANA database.

Initial configuration of SAP NetWeaver Gateway is in place. For more information,see Basic Configuration Settings4

HTTPS connectivity is enabled between the front-end server (FES) running SAPNetWeaver Gateway and the back-end systems, including SAP HANA ExtendedApplication Services (SAP HANA XS).

1 http://help.sap.com/fiori App Implementation Information for SAP Fiori ImplementationInformation2 http://help.sap.com/fiori SAP Fiori Overview Implementation Overview3 http://help.sap.com/fiori System Landscape Required for SAP Fiori4 http://help.sap.com Technology SAP Gateway SAP NetWeaver Gateway 2.0Configuration and Deployment Information Basic Configuration Settings

http://help.sap.com/fiori_bs2013/helpdata/en/11/e168533271a548e10000000a423f68/frameset.htm

http://help.sap.com/fiori_bs2013/helpdata/en/11/e168533271a548e10000000a423f68/frameset.htm

http://service.sap.com/sltoolset

http://service.sap.com/~sapidb/012002523100008986102014E

http://help.sap.com/fiori_bs2013/helpdata/en/aa/aa41524a6b6760e10000000a423f68/content.htm?frameset=/en/84/154353a7ace547e10000000a441470/frameset.htm&current_toc=/en/84/154353a7ace547e10000000a441470/plain.htm&node_id=5

http://help.sap.com/fiori_bs2013/helpdata/en/40/1b675374bc6655e10000000a423f68/frameset.htm

http://help.sap.com/saphelp_gateway20sp08/helpdata/en/f8/ed8170ef8846e2b4a26bbfbcb65d90/content.htm?frameset=/en/4c/a670b0e36c4c01ae2b9a042056f9dc/frameset.htm

http://help.sap.com/fiori

http://help.sap.com/



Introduction


In the Internet Communication Manager (ICM), the fundamental ability ofconnecting to a system with HTTP(S) is activated.In the Internet Communication Framework (ICF), certain services can be activated,for example, the service /sap/public/ping for testing connections.

Out of Scope

Analytical appsSingle sign-onAuthorizations in complex system landscapesBack-end configuration to enable the business functionality, for example,configuration of the employee self-services in SAP Human Capital Management, ormapping of users to the corresponding entities in personal management.Back-end configuration required for the specific Fiori app.

Configuration Overview

The configuration of SAP Fiori apps requires steps on a front-end Server (FES) and on oneor multiple connected SAP Business Suite back-end systems.

On the front-end server resides an SAP NetWeaver Gateway system with the SAPNetWeaver UI Add-On.

On the back-end servers, the SAP ERP or SAP CRM systems are installed, for example.

The SAP NetWeaverNetWeaver UI Add-On includes the SAP Fiori LaunchpadLaunchpaddesigner, which is the administration tool to configure the content for the SAP FioriLaunchpadLaunchpad.

The SAP Fiori Launchpad is the entry point for end users. They access the Launchpad andthe Launchpad designer from a Web browser via secure requests to the FES.

To enable these requests, UI5 applications and their related OData services need to beactivated in SAP NetWeaver Gateway on FES. In addition, users need start authorizationsfor the services on the front-end and authorizations for related functions on the back-end.

The majority of configuration steps are activation steps (for applications and services) andauthorization steps on both the front-end server and in back-end systems.

Chapter 2 describes the initial configuration of the SAP Fiori Launchpad and of the SAPFiori Launchpad designer:

Activation of the ICF services of the SAP Fiori Launchpad to create the HTTP requesthandlers for the Launchpad URLsActivation of the OData services for the SAP NetWeaver UI Add-OnCreation of a PFCG role for administrators with authorizations for the SAP FioriLaunchpad designerCreation of a PFCG role for end users with authorizations for the SAP Fiori Launchpad

At the end of these one-time activities you can launch the SAP Fiori Launchpad designerand the SAP Fiori Launchpad.

Introduction


Chapter 3 describes how to configure individual SAP Fiori apps using the example of theMy Leave Requests app and the Customer fact sheet.

Each app is included in a business catalog of apps available for a sample business role, inour example: the role for the HCM employee or for the fields representative, respectively.

On the front-end Server (FES) you have to do the following:

Activate the OData services and ICF nodes for the SAP UI5 applications in SAPNetWeaver Gateway. This enables the corresponding HTTP request handlers.Create a PFCG role that provides access to the relevant catalog in the SAP FioriLaunchpad. In our example, we copy the sample business role delivered by SAP.Add start authorizations for the required OData service to the business role (weprovide an unsecure shortcut: use wildcard authorization).Assign the role to a user, which has to have the same user name as in the back-endsystemAdapt the business catalog to your needs in the SAP Fiori Launchpad designer

SAP Fiori fact sheets are based on search models, and the results list of SAP Fiori searchis the main entry point to fact sheets. For fact sheets, you must therefore create searchconnectors on the back-end server.

In addition, users for both, fact sheets and transactional apps, must be assigned theauthorizations required in the back-end to be able to run the apps. You have to do thefollowing:

Assign the RFC Authorization to the user to allow remote access from the front-endserver to the back-end serverAssign and generate the authorizations to call and perform the OData services onthe back-end

Introduction


Process Steps

Step Back-End Server/Front-End Server/Other

Transaction Data Required

PreparationInstall and set up SAP WebDispatcher (Fact SheetsOnly)

Separate Server Seedetaileddocumentation

See detailed documentation

Create administrator user Front-End Server SU01 User name as on the back-end serverCreate test user Front-End Server SU01 User name as on the back-end serverInitial Configuration on Front-End Server (One-Time Activities)

Activate OData services forSAP Fiori Launchpad

Front-End Server /IWFND/MAINT_SERVICE

/UI2/PAGE_BUILDER_CONF/UI2/PAGE_BUILDER_PERS/UI2/PAGE_BUILDER_CUST/UI2/INTEROP/UI2/TRANSPORT

Activate SICF services forSAP Fiori Launchpad

Front-End Server SICF Full list for both Launchpad anddesigner:

/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

Assign administrator rolefor SAP Fiori Launchpad toadminstration user

Front-End Server PFCG SAP role: SAP_UI2_Admin_700The activated gateway servicenames for:

o /UI2/PAGE_BUILDER_CONF

o /UI2/PAGE_BUILDER_PERS

o /UI2/PAGE_BUILDER_CUST

o /UI2/INTEROPo /UI2/TRANSPORT

Assign role with Launchpad Front-End Server PFCG SAP role: SAP_UI2_User_700

Introduction


start authorization for endusers

The activated gateway servicenames for:

o /UI2/PAGE_BUILDER_PERS

o /UI2/INTEROP

Set up SAP Fiori Search(Fact Sheets Only)

Back-End Server Seedetaileddocumentation

See detailed documentation

Perform Check: ICF Servicefor Fact Sheets (FactSheets Only)

Front-End Server SICF /sap/bc/ui5_ui5/ui2/ushell/resources/sap/ushell/components/factsheet

Perform checks:SAP FioriLaunchpad designer andSAP Fiori Launchpad

Front-End Server Webbrowser

URL of Launchpad designer, seeLaunching the LaunchpadDesigner5

URL of Launchpad, see Launchingthe Launchpad6

Perform Check: SAP WebDispatcher (Fact SheetsOnly)

Front-End Server Webbrowser

https://<server>/sap/es/ina/getserverinfo

Perform Check: Search UI(Fact Sheets Only)

Back-End Server ESH_SEARCH

5 http://help.sap.com Technology User Interface Add-On for SAP NetWeaver ApplicationHelp SAP Fiori Launchpad Using the Launchpad Designer Launching the LaunchpadDesigner6 http://help.sap.com Technology User Interface Add-On for SAP NetWeaver ApplicationHelp SAP Fiori Launchpad Initial Launchpad Configuration Launching the Launchpad

http://help.sap.com/saphelp_uiaddon10/helpdata/en/2d/98610a5bcf43dfad588e755459dc42/content.htm?frameset=/en/a7/fff23179874b34a8a5b995c3a55a63/frameset.htm


http://help.sap.com/saphelp_uiaddon10/helpdata/en/e0/8c9cfe07b8431b884048700067aa1a/content.htm?frameset=/en/a7/fff23179874b34a8a5b995c3a55a63/frameset.htm




Introduction


App-Specific Configuration

Open productdocumentation for MyLeave Requests app/Customer fact sheet

Public internet ImplementationInformation for MyLeaveRequests7

AppImplementation:Customer8

Activities on Front-End ServerActivate ICF services of UI5application (SAP Fioriadministrator)

Front-End Server SICF UI5 applications:My Leave Requests app:HCM_LR_CRECustomer fact sheet:

BSCBN_ANF_SDMDActivate OData services perapp (SAP Fioriadministrator)

Front-End Server /IWFND/MAINT_SERVICESAPFioriLaunchpaddesigner

OData servicesMy Leave Requests app:/GBHCM/LEAVEREQUEST (2)Customer fact sheet:CB_CUSTOMER_SRV

Business catalog:My Leave Requests app:SAP_HCM_BC_EMPLOYEE_X1Customer fact sheet:SAP_SD_BC_FIELDSALESREP

Copy template businessrole to create role withLaunchpad catalog andgroup

Front-End Server PFCG Business roleMy Leave Requests app:SAP_HCM_BCR_EMPLOYEE_X1Customer fact sheet:SAP_SD_BCR_FIELDSALESREP

Add start authorizations forOData services of apps tobusiness role

Front-End Server PFCG OData servicesMy Leave Requests app:/GBHCM/LEAVEREQUEST (2)Customer fact sheet:CB_CUSTOMER_SRV

Assign business role to testuser on front-end server

Front-End Server PFCG Test user on front-end server

Remove apps not requiredfrom catalog

Front-End Server SAP FioriLaunchpaddesigner

URL of Launchpad designer incustomization mode, see Launchingthe Launchpad Designer.

Perform check: SAP FioriLaunchpad with appcontent

Front-End Server SAP FioriLaunchpad

7 http://help.sap.com/fiori SAP Fiori Products SAP Fiori for SAP ERP SAP Fiori PrincipalApps for SAP ERP 1.0 SAP Fiori Apps for SAP ERP My Leave Requests ImplementationInformation for My Leave Requests.8 http://help.sap.com/fiori SAP Fiori Apps SAP Fiori Apps for SAP ERP Apps for Logistics

Sales and Distribution (SD) Customer App Implementation: Customer

http://help.sap.com/saphelp_fiorierpx1_100/helpdata/en/f1/9467524a916d2de10000000a44176d/content.htm?frameset=/en/a1/20655213f0ea5fe10000000a423f68/frameset.htm&current_toc=/en/c1/567952d690214fe10000000a445394/plain.htm&node_id=96






http://help.sap.com/fiori_bs2013/helpdata/en/84/d6e852b804eb2de10000000a423f68/content.htm?frameset=/en/e1/8369523c71725fe10000000a441470/frameset.htm&current_toc=/en/ba/954353a531e647e10000000a441470/plain.htm&node_id=252










Preparation


Activities on Back-End ServerAssign RFC authorization totest user

Back-End Server SU01 authorizations S_RFC andS_RFCACL

Assign PFCG Role withOData ServiceAuthorization to User

Back-End Server PFCBSU01

Back-end authorization role:My Leave Requests app:SAP_GBHCM_LEAVE_REQUEST_EMPLCustomer fact sheet:SAP_SD_CUSTOMER_APP

Create Search Connectors(Fact Sheets Only)

Back-End Server ESH_COCKPIT

See App Implementation: Customer9

Start Indexing of SearchConnectors (Fact SheetsOnly)

Back-End Server ESH_COCKPIT

Activity on Front-End ServerPerform check: SAP FioriLaunchpad with contentand authorizations

Front-End Server SAP FioriLaunchpad

9 http://help.sap.com/fiori SAP Fiori Apps SAP Fiori Apps for SAP ERP Apps for Logistics Sales and Distribution (SD) Customer App Implementation: Customer



Preparation


1 Preparation

Install and Set up SAP Web Dispatcher (Fact Sheets Only)1.1

To be able to use SAP Fiori fact sheets, you must install SAP Web Dispatcher and set upthe connections between SAP Web Dispatcher and the ABAP servers.

For more information, see:

Installation of SAP Web Dispatcher10

Communication Between SAP Web Dispatcher and ABAP Servers11

Note

You must configure both the HTTP port and the HTTPS port, even if you use the HTTPsconnection only, as strongly recommended by SAP.

Create Administrator User on Front-End Server1.2

If an administrator user is not yet available on the front-end server, you have to create one.

If you are using a trusted RFCC connection to the back-end server, the user IDs need to beidentical on the front-end and on the back-end server.

The administration user needs extensive authorizations, such as S_SERVICE,S_DEVELOP, /UI2/CHIP, and S_CTS_SADM.

1. Run transaction User Maintenance (SU01) on the front-end server.2. Create a user – if applicable, with the ID the user already has in the back-end (see

above).

Create Test User on Front-End Server1.3

Create a test user in transaction SU01, using the same user-ID as on the back-end server.

10 http://help.sap.com/fiori System Landscape Required for SAP Fiori Setup of SAP FioriSystem Landscape with SAP HANA Database Installation Installation of SAP Web Dispatcher.11 http://help.sap.com/fiori System Landscape Required for SAP Fiori Setup of SAP FioriSystem Landscape with SAP HANA Database Communication Channels CommunicationBetween SAP Web Dispatcher and ABAP Servers.

http://help.sap.com/fiori_bs2013/helpdata/en/37/7b4352b4e61b13e10000000a44176d/content.htm?frameset=/en/d9/ca1e53f7e59254e10000000a4450e5/frameset.htm&current_toc=/en/40/1b675374bc6655e10000000a423f68/plain.htm&node_id=33

http://help.sap.com/fiori_bs2013/helpdata/en/49/e243539b47e344e10000000a423f68/content.htm?frameset=/en/61/963e536f6a0050e10000000a44176d/frameset.htm&current_toc=/en/40/1b675374bc6655e10000000a423f68/plain.htm&node_id=49



Initial Configuration on Front-End Server (One-Time Activities)


2 Initial Configuration on Front-End Server (One-Time Activities)

Note:If you use SAP NetWeaver 740 SPS 6 or higher, you can use tasklists to do the steps 2.1and 2.2.For more information about the tasklists for the setup of SAP Fiori and how to use them,see http://service.sap.com/sltoolset Software Logistics Toolset 1.0 Documentation

System Provisioning Technical Configuration Automation Fiori Frontend.

The SAP Fiori Launchpad uses the User interface add-on for SAP NetWeaver. It requiresthe ICF nodes that provide access to the web resources, and the OData services whichprovide the information about the configured app tiles to be displayed.For more information, see the following documentation on SAP Help Portal underhttp://help.sap.com:

SAP NetWeaver User Interface Add-On for SAP NetWeaverEspecially: SAP NetWeaver User Interface Add-On for SAP NetWeaverApplication Help Administration Guide Content Administration SAP FioriLaunchpad

Activate OData Services for SAP Fiori Launchpad2.1

The activation of the OData services and of the ICF services (described in the next section)are required to initially set up the SAP Fiori Launchpad and the SAP Fiori Launchpaddesigner.

SAP NetWeaver Gateway provides the infrastructure for the OData services used by theSAP Fiori Launchpad and the SAP Fiori apps.

An OData service has to be enabled in Gateway. This basically establishes a mappingbetween the technical OData service name and the corresponding back-end service(identified by system alias, namespace, and the external service name).

1. Run transaction Activate and maintain services (/IWFND/MAINT_SERVICE) on thefront-end server.

2. Use the system alias of your local system when activating the following services:Note:

You do not need to activate the /UI2/LAUNCHPAD service. This service is notrelevant for SAP Fiori.The service names listed below are concatenations of the namespace /UI2/and the technical names of the individual services. Enter these concatenationswhen adding new services in transaction /IWFND/MAINT_SERVICE. Whensearching for services, you need to search either by namespace or by technicalname.

/UI2/PAGE_BUILDER_CONF

http://service.sap.com/sltoolset

http://service.sap.com/~sapidb/012002523100008986102014E

https://help.sap.com/nw-uiaddon

https://help.sap.com/saphelp_uiaddon10/helpdata/en/a7/fff23179874b34a8a5b995c3a55a63/frameset.htm

https://help.sap.com/saphelp_uiaddon10/helpdata/en/a7/fff23179874b34a8a5b995c3a55a63/frameset.htm



/UI2/PAGE_BUILDER_PERS/UI2/PAGE_BUILDER_CUST/UI2/INTEROP/UI2/TRANSPORT

Result:The services are activated in your customer namespace, with the followingtechnical names, for example:

ZINTEROPZPAGE_BUILDER_CONFZPAGE_BUILDER_CUSTZPAGE_BUILDER_PERSZTRANSPORT

3. Call each service once by selecting it in transaction Activate and maintain services(/IWFND/MAINT_SERVICE), then clicking Call Browser in the screen area ICFNodes. Always select the OData node, not the SDATA node.



Note:You have called a service successfully when an XML document is displayedwithout any error messages.When you call a service, a hash key is generated in the background. The hashkey is required for the generation of authorizations described under AssignAdministrator Role for SAP Fiori Launchpad to Administration User.You can verify the hash key generation in table USOBHASH in transactionData Browser (SE16). In the selection screen, specify the following:o R3TR in the PGMID fieldo IWSG in the Object fieldo The technical service name in the OBJ_NAME field. Use the technical

name of your generated service, typically starting with Z, and having theversion number appended in four-digit format with leading zeros

The hash key should be displayed in the NAME column of the results table.

Activate SICF Services for SAP Fiori Launchpad2.2

In addition to the ICF services that correspond to the OData services it is necessary toactivate the following ICF services manually:

1. Run transaction Maintain Services (SICF) on the front-end server.



2. Activate services under the following subtrees, either by right-clicking the mouse andselecting Activate Service, or selecting Service/host Activate from the menu:

/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

Note:To activate all child nodes under a service, choose the Yes button with the hierarchy iconin the Activation of ICF Services dialog box.

Assign Administrator Role for SAP Fiori Launchpad to2.3Administration User

In this step, you copy the SAP-delivered administrator role for the SAP Fiori Launchpadand assign it to your administrator user. The administrator is then authorized to use theSAP Fiori Launchpad designer.

1. Run transaction Role Maintenance (PFCG) to copy the role SAP_UI2_ADMIN_700 toyour customer namespace.

2. Edit the new role in transaction Role Maintenance (PFCG) as follows:1. On the Menu tab, open the dropdown menu of the button for adding objects (+

button). By default, the object type Transaction is selected. Change theselection to Authorization Default.

2. In the Service pop-up that opens, select TADIR Service from the dropdownmenu for the Authorization Default. Specify the following values:

Program ID: R3TRObject Type: IWSG

In the table, enter the names of your activated services (see Activate ODataServices for SAP Fiori Launchpad) in the form <technical name>_<four-digitversion number with leading zeros>, for example:

ZINTEROP_0001ZPAGE_BUILDER_CONF_0001ZPAGE_BUILDER_CUST_0001ZPAGE_BUILDER_PERS_0001ZTRANSPORT_0001



3. On the Authorizations tab, click Propose Profile Name next to the Profile Name field.4. Choose Change Authorization Data .

On the screen that opens up, click the Generate button.

Result:

You have a role with 5 IWSG authorizations and 5 IWSV authorizations. The IWSVauthorizations are included in the role from the start, so they are not in the customernamespace:

5. Assign the new role to the administrator user created under Create Administrator Useron Front-End Server.



Assign Role with Launchpad Start Authorization for End2.4Users

Proceed as described under Assign Role for SAP Fiori Launchpad Administration toAdministration User, but using the SAP_UI2_USER_700 role as a template and assigningonly a subset of services:

ZINTEROP_0001ZPAGE_BUILDER_PERS_0001

Assign this role to the test user you have created under Create Test User on Front-EndServer.

Set up SAP Fiori Search (Fact Sheets Only)2.5

To be able to use SAP Fiori fact sheets, you must set up the SAP Fiori search. At this stage,perform steps 1-5 as described under Setup of SAP Fiori Search12 on the SAP Help Portal.

To clean up your back-end system eliminating existing search connectors, run reportESH_ADM_INDEX_ALL_SC. Mark the checkbox Delete All Search Connectors.

Perform Check: ICF Service for Fact Sheets (Fact Sheets2.6Only)

Run transaction Maintain Services (SICF) on the front-end server and check that thefollowing service is active:/sap/bc/ui5_ui5/ui2/ushell/resources/sap/ushell/components/factsheet

Perform Checks: SAP Fiori Launchpad Designer and SAP Fiori2.7Launchpad

Note:

For productive usage with a system landscape including SAP Web Dispatcher, youneed the Web Dispatcher links to perform the checks.

1. Look up the composition of the URLs of the Launchpad designer and the Launchpad inthe following documentation:

Launching the Launchpad Designer13

Launching the Launchpad14

2. Adapt the URLs entering your landscape information, such as server and port.

12 http://help.sap.com/fiori Configuration of SAP Fiori Infrastructure Setup of SAP FioriSearch13 http://help.sap.com Technology User Interface Add-On for SAP NetWeaver ApplicationHelp SAP Fiori Launchpad Using the Launchpad Designer Launching the LaunchpadDesigner14 http://help.sap.com Technology User Interface Add-On for SAP NetWeaver ApplicationHelp SAP Fiori Launchpad Initial Launchpad Configuration Launching the Launchpad

http://help.sap.com/fiori_bs2013/helpdata/en/12/af5252b10d5a64e10000000a423f68/content.htm?frameset=/en/fc/4a4c52eea9c871e10000000a44176d/frameset.htm&current_toc=/en/fc/4a4c52eea9c871e10000000a44176d/plain.htm&node_id=10








Note:You can determine the server and port Launchpad as follows:Run transaction SICFDrill Down default host -> sap -> public -> pingRight mouse click on the ping service -> click Service test

3. Check that the Launchpad designer can be opened.4. Check that the Launchpad can be opened. At this stage, an empty Launchpad should

be displayed.

Perform Check: SAP Web Dispatcher (Fact Sheets Only)2.8

To check that SAP Web Dispatcher is operating, enter the following URL into your Webbrowser: https://<server>/sap/es/ina/getserverinfo. Fill the placeholder for the serverwith the address of your back-end server.

You should be able to view a description of the server.

Perform Check: Search UI (Fact Sheets Only)2.9

To check that SAP Fiori search has been installed correctly, run transaction ESH_SEARCHin the back-end system.

The WebDynpro UI for the search should appear in the back-end system.

3 App-Specific Configuration

Open Product Documentation for My Leave Requests3.1App/Customer Fact Sheet

For the following procedures, you need information from the product documentation,such as technical names of services, roles, and so on.

The information is included in the following sections.

However, to have the documentation with the required entities at hand, go tohttp://help.sap.com and open the following documents:

1. Implementation Information for My Leave Requests15.2. App Implementation: Customer16

15 http://help.sap.com/fiori SAP Fiori Products SAP Fiori for SAP ERP SAP Fiori PrincipalApps for SAP ERP 1.0 SAP Fiori Apps for SAP ERP My Leave Requests ImplementationInformation for My Leave Requests.16 http://help.sap.com/fiori SAP Fiori Apps SAP Fiori Apps for SAP ERP Apps for Logistics

Sales and Distribution (SD) Customer App Implementation: Customer







Activities on Front-End Server3.2

3.2.1 Activate ICF Services of UI5 Application (SAP Fiori Administrator)

To activate the apps, you must perform this procedure, as well as the activation of theOData services per app (next section).

My Leave Requests app

1. Run transaction Maintain Services (SICF) on the front-end server.2. Press F8.3. Navigate to the following path default_host sap bc ui5_ui5 sap .4. Under this node, navigate to the UI5 application for the My Leave Requests app:

hcm_lr_cre.5. To activate the service (UI5 application), choose Service/host Activate .

Customer fact sheetCheck if the ICF service is already active:

1. Retrieve the UI5 application relevant for the Customer fact sheet in the AppImplementation: Customer17. You find this information in the Extensibility sectionunder BSP application for annotation files.

2. Run transaction Maintain Services (SICF) on the front-end server.3. Press F8.4. Navigate to the following path default_host sap bc bsp sap .5. Under this node, navigate to the UI5 application for the Customer fact sheet:

BSCBN_ANF_SDMD.6. If it is not yet active, activate the ICF service for your app choosing Service/host

Activate .

3.2.2 Activate OData Service for App (SAP Fiori Administrator)

1. Run transaction Activate and maintain services (/IWFND/MAINT_SERVICE) on thefront-end server.

2. Click Add Service.3. Enter the system alias of your back-end system.

4. In the External Service Name field, enter the technical name of the OData servicewithout the version number:

17 http://help.sap.com/fiori SAP Fiori Apps SAP Fiori Apps for SAP ERP Apps for Logistics Sales and Distribution (SD) Customer App Implementation: Customer






/GBHCM/LEAVEREQUEST for the My Leave Requests appCB_CUSTOMER_SRV for the Customer fact sheet

5. Enter the version number – “2” for the My Leave Requests app – into the Version field.6. Click Get Services.7. Click Add Selected Services.

A popup opens up:

8. Give the service a technical name in your customer namespace.9. Assign a package or choose Local Object.10. Click Execute to save the service.11. In the Activate and maintain services screen, verify that the system alias is maintained

correctly. If not, change it as required by deleting the alias and adding the correct one.

3.2.3 Copy Template Business Role to Create Role with Launchpad Catalogand Group

You must perform this step and the following authorization- and-role-related tasks on thefront-end server to equip the test user with all rights needed for the app.

SAP delivers business roles for users of SAP Fiori apps. Business roles provide access to asample of apps relevant for specific business users.

The authorization for the My Leave Requests app is included in the business role for theHCM employees (SAP_HCM_BCR_EMPLOYEE_X1).

The authorization for the Customer fact sheet is included in the business role for thefields representative (SAP_SD_BCR_FIELDSALESREP).



Run transaction Role Maintenance (PFCG) to copy the business role to your customernamespace.

Note:A business catalog and a business catalog group containing apps relevant for businessrole are displayed under the Menu tab.

3.2.4 Add Start Authorizations for OData Service of Apps to Business Role

A user trying to consume an OData service needs the following types of authorizations:

Authorizations on the Gateway side: Role Menu entries for Authorization Defaultsof type TADIR Service with object type “IWSG – Gateway: Service GroupsMetadata”.Authorizations on the back-end side: Role Menu entries for Authorization Defaultsof type TADIR Service with Object Type IWSV – Gateway Business SuiteEnablement - Serv.

For the back-end entries, an example role is provided, from which the entries can becopied (see section Assign PFCG Role with OData Service Authorization to Test User).

For the Gateway-side entries, there are no such examples, as the technical names areentered during the activation of the service, and therefore not known in advance.

To create a role with OData start authorizations on the front-end server, proceed asfollows:

Caution:

Be aware that the check for OData service authorization can provide additionalsecurity, especially in case SAP NetWeaver Gateway is set up as separate hub. Byspecifying the services explicitly in the role menu, you control which requests onbehalf of a user can pass the Gateway.

If you use a wildcard, users can call all activated services. Unauthorized requestscan only be rejected on the back-end server, provided that the user’sauthorizations in the back-end are not sufficient.

We therefore recommend that you do not use wildcard authorizations in productiveenvironments.

Instead, add single services as follows:

Note

You must have called an OData service at least once before you can assign startauthorizations for it.

1. Edit the business role created under Copy Template Business Role to Create Rolewith Launchpad Catalog and Group in transaction Role Maintenance (PFCG).

2. On the Menu tab, open the dropdown menu of the button for adding objects (+button). By default, the object type Transaction is selected.Change the selection to Authorization Default.



3. In the Service pop-up that opens, select TADIR Service from the dropdown menufor the Authorization Default. Specify the following values:

Program ID: R3TRObject Type: IWSG

4. In the table, enter the name of the activated OData service (see Activate ODataService for App (SAP Fiori Administrator).

Note:You need to enter the name in the form <technical name>_<four-digit versionnumber with leading zeros>, for example, ZLEAVEREQUEST_0002.

5. Under the Authorization tab, click the button next to the Profile Name field togenerate the authorization profile for the role.

6. Choose Change Authorization Data .On the screen that opens up, click the Generate button.

3.2.5 Assign Business Role to Test User on Front-End Server

In transaction Role Maintenance (PFCG), assign the business role to the test user initiallycreated (see Create Test User on Front-End Server) by specifying the user ID under theUser tab.

3.2.6 Remove Apps Not Required from Catalog (Optional Step)

This is a clean-up step. You can narrow down the authorizations contained in the businessrole delivered (see Copy Template Business Role to Create Role with Launchpad Catalogand Group) to the apps that should actually be available for the test user. For thispurpose, remove apps that are not required from the business catalog.

1. Retrieve the name of the relevant business catalogImplementation Information for My Leave Requests:SAP_HCM_BC_EMPLOYEE_X1.

http://help.sap.com/saphelp_fiori_erp_100/helpdata/en/f1/9467524a916d2de10000000a44176d/content.htm?frameset=/en/fb/b34f52f10a5c64e10000000a423f68/frameset.htm



App Implementation: Customer:SAP_SD_BC_FIELDSALESREP

2. Enter the SAP Fiori Launchpad designer in customization mode (see PerformCheck: SAP Fiori Launchpad with App Content):https://<server>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?sap-client=<client>&scope = CUST

3. Search for the business catalog.4. Delete tiles not required.

Caution:

Do not delete target mapping tiles (blue) or app launcher tiles (white) of the appsyou want to keep.

To delete tiles, drag them to the lower right corner in the Launchpad designer.

3.2.7 Perform Check: SAP Fiori Launchpad with App Content

1. Open the SAP Fiori Launchpad with the test user credentials.2. Choose Open Catalog from the menu.

The business catalog with the My Leave Requests app/Customer fact sheet shouldbe visible.At this stage, however, starting the app will lead to an error, because back-endauthorizations are still missing.

Activities on Back-End Server3.3

3.3.1 Assign RFC Authorization to Test User

If the OData back-end service is located on a remote back-end, users need permission toperform the RFC call on the back-end system, that is, they require the authorizationsS_RFC and S_RFCACL for trusted RFC.

In this case, and if your user does not have these authorizations yet, assign a role includingthe RFC authorization objects to the back-end user that corresponds to the test userinitially created (see Create Test User on Front-End Server).

Note:

You can check whether the user has the RFC authorizations in the user informationsystem (by entering transaction User Maintenance (SU01) and choosingInformation Information System).

3.3.2 Assign PFCG Role with OData Service Authorization to Test User

Note:

The following procedure describes how you assign the OData service to a user forjust the one app (My Leave Requests app/Customer fact sheet).

For a productive usage of Fiori apps, you would most probably do the PFCG roleassignment differently: You would create a PFCG role that contains multiple OData




start authorizations. For example, you would include the start authorizations for allHR apps, based on the technical catalog for HR.

1. Run transaction Role Maintenance (PFCG) to copy the back-end authorization rolerequired for your app to your customer namespace:

Technical role name for the My Leave Requests app:SAP_GBHCM_LEAVE_REQUEST_EMPLTechnical role name for the Customer fact sheet:SAP_SD_CUSTOMER_APP

2. Edit the copied business role in transaction Role Maintenance (PFCG)3. On the Menu tab, open the dropdown menu of the button for adding objects (+

button). By default, the object type Transaction is selected. Change the selection toAuthorization Default.

4. In the Service pop-up that opens, select TADIR Service from the dropdown menufor the Authorization Default. Specify the following values:

Program ID: R3TRObject Type: IWSV

5. In the table, enter the name of the activated OData service (see Activate ODataService for App (SAP Fiori Administrator)

6. Under the Authorization tab, click the button next to the Profile Name field togenerate the authorization profile for the role.

7. Choose Change Authorization Data. On the screen that opens up, click Save andthen the Generate button.

8. Run transaction User Maintenance (SU01) and assign the role to the test user userinitially created (see Create Test User on Front-End Server).

Note:

The following steps are only necessary if the user does not yet have the businessauthorizations that are required to use the My Leave Requests app.

1. On the Authorization tab, click Generate Profile next to the profile name.2. Choose Maintain Authorization Data.3. On the Authorization Details screen, click the Generate icon in the toolbar.

3.3.3 Create Search Connectors (Fact Sheets Only)

Prerequisites:

To create search connectors, you need the following authorizations:

SAP_ESH_SEARCHSAP_ESH_LOCAL_ADMIN

SAP Fiori fact sheets are based on search models.

To enable the use of fact sheets, search connectors must be created for the underlyingsearch models.



Retrieve the search connectors required for the Customer fact sheet in the AppImplementation: Customer.

Create the search connectors as described on SAP Help Portal under Back-End Server:Create Search Connectors for Apps18.

3.3.4 Start Indexing of Search Connectors (Fact Sheets Only)

For more information, see Setup of SAP Fiori Search on SAP Help Portal19.

3.3.5 Perform Check: SAP Fiori Launchpad with Content and Authorizations

Open the SAP Fiori Launchpad with the test user credentials.

My Leave Requests app:

1. Choose Open Catalog from the menu.2. The business catalog with the your transactional app (My Leave Requests app)

should be visible.

Customer fact sheet

Fact sheets can be called from the results of the SAP Fiori search.To access the Customerfact sheet, proceed as follows:

1. Use the SAP Fiori search. To narrow down the search results to customer businessobjects, enter a customer name and then enter the term customer in the searchfield.

2. From the search results, you should be able to open the Customer fact sheet

When starting the apps, the actual app functions should be available.

Note

If you get an error message stating that configuration is missing when you start theapp, it means that your back-end system has not been configured correctly toenable the business functionality (see Out of Scope).

18 http://help.sap.com/fiori App Implementation Information for SAP Fiori ImplementationInformation App Implementation for Fact Sheets Back-End Server: Create Search Connectorsfor Apps.19 http://help.sap.com/fiori Configuration of SAP Fiori Infrastructure Setup of SASP FioriSearch



http://help.sap.com/fiori_bs2013/helpdata/en/a5/83425356817d77e10000000a441470/content.htm?frameset=/en/da/0f415370107d77e10000000a441470/frameset.htm&current_toc=/en/11/e168533271a548e10000000a423f68/plain.htm&node_id=22

http://help.sap.com/fiori_bs2013/helpdata/en/a5/83425356817d77e10000000a441470/content.htm?frameset=/en/da/0f415370107d77e10000000a441470/frameset.htm&current_toc=/en/11/e168533271a548e10000000a423f68/plain.htm&node_id=22

http://aiokeh.wdf.sap.corp:50000/SAPIKS2/contentShow.sap?IWB_INDUSTRY=FIORICROSS&RELEASE=100_SP02&_CLASS=BCO_COMMON&_LOIO=12AF5252B10D5A64E10000000A423F68&TMP_IWB_TASK=PREVIEW&_SLOIO=299A5652D8C3725FE10000000A441470&LANGUAGE=EN&_SEQNUM=1304&_SCLASS=XDP_STRUCT



Documents

Fiori Configurations