sap offline word template -...

Building Block Configuration GuideDocument Version: 1.4 – 2017-07-05

CUSTOMER

SAP S4HANA Fiori Launchpad Operation (MAG)

Typographic ConventionsType Style Description

Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.Textual cross-references to other documents.

Example Emphasized words or expressions.EXAMPLE Technical names of system objects. These include report names, program names,

transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .

2

CUSTOMER © 2016 SAP SE or an SAP affiliate company. All rights reserved.

SAP S4HANA Fiori SAP S4HANA Fiori Launchpad Operation (MAG)Purpose

Document HistoryVersion Date Change

1.0 2015-11-15 Version 1

1.1 2016-04-06 Technical update



1.4 2017-07-05 Update for SAP S/4 HANA 1709, on-premise edition


CUSTOMER© 2016 SAP SE or an SAP affiliate company. All rights

reserved. 3

Table of Contents1 Purpose

2 Preparation2.1 Prerequisites

3 Configuration3.1 Creating and Assigning Transport Requests3.2 Creating a Sample Catalog3.3 Creating a Sample Group3.4 PFCG Roles Management

3.4.1 Creating a Sample PFCG Role and Assigning to End-Users3.4.2 Copying SAP-delivered PFCG to Customer Namespace

3.5 (Optional) Creating a Target Mapping3.5.1 Creating a Target Mapping for a SAPUI5 Application3.5.2 Creating a Target Mapping for a Transaction3.5.3 Creating a Target Mapping for a URL3.5.4 Creating a Target Mapping for a Web Dynpro Application

3.6 Adding a Static Tile to the Sample Catalog and Group3.7 Adding a Transactional App to SAP Fiori Launchpad

3.7.1 Creating a Transactional App Target Mapping to Catalog3.7.2 Adding a Transactional App Tile to Catalog and Group

3.8 Adding an Analytical App to Fiori Launchpad3.8.1 Checking Analytical App in KPI Modeler3.8.2 Checking Analytical App in Catalog3.8.3 Adding a KPI App Tile into Group

3.9 Adding a Fact Sheet to Fiori Launchpad3.9.1 Display a Fact Sheet from Search3.9.2 Creating a Fact Sheet Target Mapping to Catalog3.9.3 Adding a Fact Sheet Tile into Catalog and Group

3.10 Adding a NWBC/SAP GUI for HTML (Web GUI) App to Fiori Launchpad3.10.1 Creating a NWBC/SAP GUI for HTML (Web GUI) Target Mapping to Catalog3.10.2 Adding a NWBC/SAP GUI for HTML (Web GUI) App Tile to Catalog and Group

3.11 Adding a Web Dynpro App to Fiori Launchpad3.11.1 Creating a Web Dynpro Target Mapping into Catalog3.11.2 Adding a Web Dynpro App Tile to Catalog and Group

3.12 SAP Jam Integration Enablement3.12.1 Create SAP Jam User and Group3.12.2 Change Front-End Server User to Map to SAP Jam User3.12.3 Configuring HTTP Proxy on Front-End Server3.12.4 Importing SAP Jam Root Certificate into Front-End Server3.12.5 Configuring SAML2 Authentication for SAP Jam3.12.6 Configuring OAuth Client for SAP Jam3.12.7 Configuring ABAP Social Media Integration in Front-End Server3.12.8 Configuring ABAP SMI for SAP Fiori Apps3.12.8.1 Activating ABAP SMI OData Services3.12.8.2 Creating the Social Media Catalog

4



3.12.8.3 Creating a Social Media Integration Role3.12.9 Verify Jam Integration Tiles3.12.10 Verify Jam Integration in Fiori Apps

4 Transportation



reserved. 5

1 PurposeThe SAP Fiori Launchpad is the entry point for Fiori apps on mobile or desktop devices, and the Launchpad Designer is the standard tool for configuring the SAP Fiori Launchpad. This configuration guide provides the information you need to set up the SAP Fiori Launchpad and the Launchpad Designer, as well as the SAP Jam integration in the SAP Fiori Launchpad. In addition to the SAP Fiori Launchpad setup for SAP standard apps of all types, the guide provides information on the configuration required if you want to integrate your custom apps to the SAP Fiori Launchpad.

6



2 Preparation

2.1 PrerequisitesBefore starting with the installation of this building block, please complete the configuration of the building blocks 'SAP S4HANA Foundation Configuration (MAA)', 'Basic Network Security Configuration (MAB)', 'Fiori Apps Deployment (MAD)' and 'Other App Types Deployment (MAL)'. For the specific apps that are used in the guide as examples you should also implement the corresponding configuration steps prior to their SAP Fiori Launchpad integration.

NoteIn case of ABAP Front-End Server based on SAP NetWeaver 7.50 and above the SAP Fiori Launchpad and Launchpad Designer are part of the software component SAP_UI, which is already included in the standard SAP NetWeaver 7.50.



reserved. 7

3 ConfigurationThe SAP Fiori Launchpad is the entry page to SAP Fiori apps on mobile or desktop devices. It can be configured via the Launchpad Designer. There are important concepts for the Launchpad Designer, which are described in this section:1. Scope: The Launchpad Designer has 3 scopes: Configuration, Customizing, Personalization:

Configuration is a system-wide setting. The content delivered by SAP is stored in the configuration scope. It can be accessed via the following link: http(s)://<FrontEndServer>:<Port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?scope=CONF.Changes should be attached to a Workbench Request.You can access the Launchpad Designer using the following SAP GUI transaction:

Transaction Code /UI2/FLPD_CONF

Customizing is a client-specific setting. Content changes are valid only for the current client. These settings override the configuration settings, but can be superseded by personalization settings. It can be accessed via the following link:http(s)://<FrontEndServer>:<Port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?sap-client=<Client>(&scope=CUST).This is also the default in case no "scope" parameter provided. Changes should be attached to a Customizing Request.You can access the Launchpad Designer using the following SAP GUI transaction:

Transaction Code /UI2/FLPD_CUST

Personalization is a user-specific setting. This setting overrides customizing and configuration settings. This functionality is already integrated in the SAP Fiori Launchpad, so that end users can configure it by themselves.

2. Catalog: It contains Tiles and Target Mappings. The SAP pre-delivered catalogs can usually be mapped to a combination of LoB and archetype, like Catalog of MM Transactional Apps, or Catalog of CRM Fact Sheets.

3. Group: Contains Tiles from Catalogs, more oriented to a business role like Sales Representative or Cost Manager. The end users can see the groups in the SAP Fiori Launchpad if the corresponding role is assigned to them.

4. Tile: Icon in the SAP Fiori Launchpad that provides a link to the Target Mapping via Intent.5. Target Mapping: Defines the navigation target, i.e. the application that is launched, when an Intent

is triggered.6. Intent: Semantic Object + Action + Semantic Object parameters.

Semantic Object Represents a business entity such as a customer, a sales order or a product. By using semantic objects you can bundle applications that reflect a specific scenario. They allow you to refer to objects in a standardized way, abstracting from concrete implementations of these objects.You can either use semantic objects shipped by SAP or create new ones.

Action Describes which operation (such as display or approvePurchaseOrders) is intended to be performed on a semantic

8



object (such as Purchase Order or Product). The name of the action can be defined arbitrarily.

Semantic Object parameters

Define the instance of the semantic object (e.g. by specifying the employee ID).

The intents have the following pattern:#<SemanticObject>-<Action>?<SemanticObjectParameter>=<Value>.Subsequently, the SAP Fiori Apps can be accessed via the Sap Fiori Launchpad URL + Intent, for example:http(s)://<FrontEndServer>:<Port>/sap/bc/ui2/flp#SalesOrder-change?SalesOrder=27.

3.1 Creating and Assigning Transport Requests

UseAll settings carried through in the Launchpad Designer can be recorded in the Front End Server using Transport Requests. A Workbench Request is needed for the Configuration scope and a Customizing Request is needed for Customizing scope.

Procedure1. Log in to the ABAP Front-End Server.2. Call the following transaction:

Transaction Code SE01

3. Choose Create.... The Create Request dialog box appears.4. Select Customizing Request and then Choose Copy (Enter ).5. Maintain the description and the Target parameter in the request details.6. Choose Save.7. Access the Launchpad Designer.8. Choose the Settings button in the top right corner.

9. In the Assign Transport Request dialog box, select the Workbench/Customizing Request (or choose None (Local Object) if you don't want to record changes), and then choose OK.



reserved. 9

3.2 Creating a Sample Catalog

UseIt is possible to make SAP standard catalogs available to users or create custom catalogs, i.e., custom collections of apps that are made available for specific roles. In this activity, a sample catalog will be created to contain the Fiori apps of different archetypes.

Procedure1. In the Launchpad Designer, choose the Catalogs tab. All catalogs are loaded.2. Choose the + button at the bottom left corner of the page.

3. In the Create Catalog dialog box, choose Standard, enter Title and ID as Z_RDS_BC, and then choose Save.

NoteThe Remote Catalog option is valid for HANA catalogs. It is used for the KPI Modeler.

4. (Optional) In case you want to copy or delete the catalog, drag the Catalog Z_RDS_BC to the bottom left or bottom right of the catalog list, respectively.

10



3.3 Creating a Sample Group

UseIn this activity, a sample group will be created to contain the Fiori apps of different archetypes.

Procedure1. In the Launchpad Designer, choose the Groups tab. All groups are loaded.2. Choose the + button at the bottom left corner of the page.3. Enter Title and ID as Z_RDS_BCG, and then choose Save. 4. (Optional) In case you want to delete the group Z_RDS_BCG, drag it to the bottom left of the page.



reserved. 11

3.4 PFCG Roles ManagementIn this section it is described how the apps, i.e. catalogs and groups, are assigned to the users using PFCG roles. In the first section it is described how to create your own PFCG role for the previously created catalog and group. In the second chapter it is described how to copy SAP-delivered PFCG roles to the customer namespace. Those roles can be adapted based on the customer needs.

3.4.1 Creating a Sample PFCG Role and Assigning to End-Users

UseThe access to catalogs and groups is controlled by PFCG roles in the ABAP Front-End server. This access is granted to the end users by assigning them the corresponding roles.

Procedure1. Log in to the ABAP Front-End server.2. Call the following transaction:

Transaction Code PFCG

3. On the Role Maintenance screen, enter Role as Z_RDS_BCR and choose Create Single Role.

12



4. On the Create Roles screen, choose the Menu tab.5. Choose + and select SAP Fiori Tile Catalog.

6. On the Assign Catalog dialog box, choose Catalog Provider as Fiori Launchpad Catalogs, enter Catalog ID as Z_RDS_BC and then choose Continue (Enter ).

7. Choose + again and select SAP Fiori Tile Group.8. On the Assign Group dialog box, enter Group ID as Z_RDS_BCG and then choose Continue (Enter ).9. Choose the User tab, enter User ID as end-user IDs like FIORI_USER and then choose User

Comparison.10. Close the Compare Role User Master Record dialog box and then choose Save (Ctrl+S ).

3.4.2 Copying SAP-delivered PFCG to Customer Namespace

UseOnce you want to use the SAP-delivered PFCG roles it is mandatory to copy these PFCG roles to your customer namespace. You can adapt those roles according to your needs, i.e. add or remove catalogs or groups.

Procedure1. Log in to the ABAP Front-End Server.2. Call the following transaction:


3. On the Role Maintenance screen, click in the role field and choose F4 to open the search window.4. Enter the name of the role you want to copy and choose the Start search button.5. Select the role from the list and choose Copy.6. You have now selected a role. Choose the Copy role button.



reserved. 13

7. Enter a name in the Role field that fits to your naming conventions and used customer namespace (for example: Z_<original name of SAP-delivered role>).

8. Choose Copy all button.9. Choose the User tab, enter User ID as end-user IDs like FIORI_USER and then choose User

Comparison.10. Close the Compare Role User Master Record dialog box and then choose Save (Ctrl+S ).

3.5 (Optional) Creating a Target Mapping

UseThe target mapping defines the navigation target when an intent (semantic object + action + parameters) is triggered. In case you implement SAP-delivered apps, the target mappings are already available in the corresponding catalogs and are delivered via the UI Add-On in the ABAP Front-End Server. In this case, it is not required to create any target mappings and you may proceed to the next section of this guide. However, in case you create your own app, you need to create a target mapping.

NoteStarting with SAP UI Add-on 2.0 SPS01, the SAP Fiori Launchpad configuration is done using the Launchpad Designer for all application types, including NWBC and Web Dynpro applications. It is recommended to use the Launchpad Designer instead of the transaction Overview of Launchpads (LPD_CUST) for the configuration of catalogs, tiles and target mappings for reasons of simplicity and performance during runtime.

3.5.1 Creating a Target Mapping for a SAPUI5 Application

ProcedureIn case the Target Mapping is a SAPUI5 application, the procedure is as follows:1. In the Launchpad Designer, choose a catalog and then choose the Target Mappings tab.2. Choose Create Target Mapping at the bottom of the Launchpad Designer.3. In the Configure: 'Target Mapping' screen, maintain the corresponding fields.

Parameter ValueSemantic Object Semantic object, as defined in the app launcher tile, e.g. Supplier

Action Action, as defined in the app launcher tile, e.g. displayBalanceApplication Type SAPUI5 Fiori App

Title Title of the SAPUI5 applicationURL Relative URL pointing to the SAPUI5 application, e.g.

/sap/bc/ui5_ui5/my_fin_vendor_bal

ID Enter one of the following:o Component name of the SAPUI5 application, e.g.

14



Parameter Valuecus.fin.ap.balances.display

o ID of the application descriptor of the SAPUI5 application

NoteIn case the SAPUI5 application is located in the SAPUI5 ABAP repository, it is sufficient to use the ID and leave the URL field empty.

4. Choose Add and check if the target mapping is added.

3.5.2 Creating a Target Mapping for a Transaction

ProcedureIn case the Target Mapping is a transaction, the procedure is as follows:1. In the Launchpad Designer, choose a catalog, and then choose the Target Mappings tab.2. Choose Create Target Mapping at the bottom of the Launchpad Designer.3. In the Configure: 'Target Mapping' screen, maintain the corresponding fields.

Parameter ValueSemantic Object Semantic object, as defined in the app launcher tile, e.g.

HTMLGUI_FIN

Action Action, as defined in the app launcher tile, e.g. postVendorDownPayment

Application Type Transaction

Title Title of the transactionTransaction Transaction code, e.g. F-48

System Alias Alias of the target system, e.g. S4FIN4. Choose Add and check if the target mapping is added.

3.5.3 Creating a Target Mapping for a URL

ProcedureIn case the Target Mapping is a URL, the procedure is as follows:1. In the Launchpad Designer, choose a catalog, and then choose the Target Mappings tab.2. Choose Create Target Mapping at the bottom of the Launchpad Designer.3. In the Configure: 'Target Mapping' screen, maintain the corresponding fields.

Parameter ValueSemantic Object Semantic object, as defined in the app launcher tile



reserved. 15

Parameter ValueAction Action, as defined in the app launcher tileApplication Type URL

Title Title of the URLURL Target URLSystem Alias Alias of the target system


3.5.4 Creating a Target Mapping for a Web Dynpro Application

Procedure1. In the Launchpad Designer, choose a catalog, and then choose the Target Mappings tab.2. Choose Create Target Mapping at the bottom of the Launchpad Designer.3. In the Configure: 'Target Mapping' screen, maintain the corresponding fields.

Parameter ValueSemantic Object Semantic object, as defined in the app launcher tile, e.g.

BankAccount

Action Action, as defined in the app launcher tile, e.g. maintainHierarchy

Application Type Web Dynpro

Title Title of the Web Dynpro applicationApplication ID of the Web Dynpro application, e.g. WDA_FCLM_BAM_HIERARCHYConfiguration ID of the Web Dynpro configuration file

APP_CFG_FCLM_BAM_HIERARCHY

System Alias Alias of the target system, e.g. S4FIN


3.6 Adding a Static Tile to the Sample Catalog and Group

UseThe configuration of a tile consists of a) a link to the target mapping and b) the tile configuration itself. Since most Fiori apps use static tiles, the step of adding a static tile to a catalog or group will be repeated several times in the following sections and it is described here for reference.

16



Procedure1. In the Launchpad Designer, choose a catalog to be used as a copy template for your purpose.2. Choose the tab Target Mappings.3. Choose a line, and then choose Create Reference.4. On the Select Catalog dialog box, choose Z_RDS_BC.5. In the Launchpad Designer, choose the Catalog Z_RDS_BC and check if the Target Mapping is

added.

6. On the right-side panel, choose Tiles, and then choose the + Add Tile.7. On the Select a tile template screen, choose App Launcher - Static.8. The Configure: 'App Launcher - Static' screen appears. Enter Title and Subtitle as the Fiori app's

name and description, and choose an Icon. It will be displayed on the Launchpad tile. Enter a Semantic Object and Action. They need to be related to the Semantic Object and Action of the Target Mapping. Choose Save, the screen will be automatically guide you back to the catalog Z_RDS_BC.

9. Choose the group Z_RDS_BCG and then choose the + Add Tile.10. On the Add Tile to 'Z_RDS_BCG' screen, choose the input help button.

11. In the Catalogs dialog box, choose the Z_RDS_BC catalog. All the tiles of this catalog will be displayed. Tiles with a green check are already added to the group, tiles with a grey plus are not yet part of the group.



reserved. 17

12. Choose the grey + below the tile; it will turn to a green check and the tile will be added. Choose the back arrow and check if the tile is added to the group.

3.7 Adding a Transactional App to SAP Fiori Launchpad

UseTransactional apps are the most typical and widely used Fiori apps. The transactional apps contain operations on semantic objects. For all SAP-delivered apps the target mapping is pre-delivered with the corresponding catalog.

PrerequisitesIn this walk through example the transactional app "Post Outgoing Payments" is being used. You should implement the app prior to the integration to the SAP Fiori Launchpad based on the 'SAP S/4 HANA Fiori Apps Deployment (MAD)' configuration guide.

3.7.1 Creating a Transactional App Target Mapping to Catalog

Procedure1. In the Launchpad Designer, choose the Catalog SAP_SFIN_BC_APAR_OPER, and then choose the

Target Mappings tab.2. Choose the Supplier postPayment line and then choose Create Reference.

18



NoteThis button was formerly called Copy.

3. In the Select Catalog dialog box, choose Z_RDS_BC.4. Check if the target mapping is added to the catalog Z_RDS_BC.

3.7.2 Adding a Transactional App Tile to Catalog and Group

ProcedurePlease refer to the section "Adding a Static Tile to the Sample Catalog and Group" on how to add a tile for the above target mapping.

3.8 Adding an Analytical App to Fiori Launchpad

UseAnalytical Apps use KPI tiles, which are generated by the KPI Modeler, and OData from CDS Views. In this section, an analytical app is being used to demonstrate how to get insights of analytical apps.

PrerequisitesIn this walk-through example the analytical app "Overdue Payables" is being used. You should implement the app prior to the integration to the SAP Fiori Launchpad based on the 'SAP S/4 HANA Fiori Apps Deployment (MAD)' configuration guide.

3.8.1 Checking Analytical App in KPI Modeler

Procedure1. In the ABAP Front-End Server, assign the role SAP_BR_ANALYTICS_SPECIALIST to your user using

the transaction PFCG (Display Roles).2. In SAP Fiori Launchpad, choose the tile KPI Workspace in group KPI Design.3. Search and choose the KPI Overdue Payables, and then choose the Evaluation Today. You can now

see detailed information of the Evaluation.4. In SAP Fiori Launchpad, choose the tile Create Tile in group KPI Design.5. Search and choose the Evaluation Today and then choose the Tile Overdue Payables.

NoteThere might be multiple Evaluations with description 'Today' available.



reserved. 19

6. In the Add Tile screen, you can see detail information of the tile

3.8.2 Checking Analytical App in Catalog

Procedure1. In the Launchpad Designer, choose the catalog SAP_SFIN_BC_AP_ANALYTICS.2. In the second Tile tab, you can see the tile configuration. Since it is generated by the KPI

Framework, you can only see that it is a Comparison Tile and it cannot be configured here.3. In the Target Mapping tab, there is only one line since all the Smart Business apps use the same

Semantic Object * and Action analyzeSBKPIDetailsS4HANA.

3.8.3 Adding a KPI App Tile into Group

Procedure1. In the Launchpad Designer, choose the Group Z_RDS_BCG and then choose the + Add Tile.2. On the Add Tile to 'Z_RDS_BCG' screen, choose the input help button.3. In the Catalogs dialog box, choose the SAP_SFIN_BC_AP_ANALYTICS catalog. All the tiles of this

catalog will be displayed.4. Add the KPI App tile and then choose the back arrow. Check if the KPI App Tile is added to the

group Z_RDS_BCG.

3.9 Adding a Fact Sheet to Fiori Launchpad

UseFact Sheets are read-only displays for an instance of a semantic object. A Fact Sheet can be accessed via Search or via navigation from another Fiori app. With the Launchpad Designer, the semantic object and displayFactSheet can be configured in the target mapping settings. Additionally, if some Fact Sheets are to be permanently used, e.g. some important customers’ Fact Sheets, they can be set as tiles.

PrerequisitesIn this walk-through example the Fact Sheet " Customer Accounting Document (S/4HANA)" is being used. You should implement the Fact Sheet prior to the integration to the SAP Fiori Launchpad based on the 'SAP S/4 HANA Fiori Apps Deployment (MAD)' configuration guide.

20



3.9.1 Display a Fact Sheet from Search

UseThis is the procedure to verify if a Fact Sheet can be searched and displayed correctly.

Procedure1. Access the SAP Fiori Launchpad from a browser.

URL https://<host>:<port>/sap/bc/ui2/flp2. Login via credentials, for example, Fiori_adm and the corresponding password, and then find the

search icon at the top right corner.

3. Click on it; a search field appears. Specify the search term, for example. Customer Accounting Documents, and press Enter .

4. The search result list will be shown. Choose a customer accounting document object, for example. 1010 90000000 001 2016.

5. The Customer Accounting Document Fact Sheet will be shown.



reserved. 21

3.9.2 Creating a Fact Sheet Target Mapping to Catalog

Procedure1. In the Launchpad Designer, choose the catalog SAP_TC_FIN_FO_COMMON and then choose the tab

Target Mappings in the right panel.2. Choose the CustomerAccountingDocument displayFactSheet line, and then choose Create

Reference.


3. In the Select Catalog dialog box, choose the custom catalog, for example: Z_RDS_BC.4. Check if the target mapping is added to the catalog Z_RDS_BC.

3.9.3 Adding a Fact Sheet Tile into Catalog and Group

ProcedureSince the Fact Sheet tile must refer to a dedicated instance of the semantic object, you must define a key parameter. Please refer to the section "Adding a Static Tile to the Sample Catalog and Group" for the above target mapping and enter Parameters, for example CompanyCode=1010.

3.10 Adding a NWBC/SAP GUI for HTML (Web GUI) App to Fiori Launchpad

UseNWBC apps and SAP GUI for HTML apps are links to pages of transaction codes in the SAP S/4 HANA system. They are not SAPUI5 apps. The tile and target mapping entries in the Launchpad Designer are pre-delivered for all SAP-delivered apps. In this section it is described how to add an SAP-delivered NWBC/Web GUI app to the SAP Fiori Launchpad.

PrerequisitesIn this walk-through example the NWBC app "Change Sales Order" is being used. You should implement the app prior to the integration to the SAP Fiori Launchpad based on the 'SAP S/4 HANA other app Types Deployment (MAL)' configuration guide.

22



3.10.1 Creating a NWBC/SAP GUI for HTML (Web GUI) Target Mapping to Catalog

Procedure1. In the Launchpad Designer, choose the catalog SAP_SD_BC_SO_PROC_OP and then choose the tab

Target Mappings in the right panel.2. Choose the SalesDocument change line, and then choose Create Reference.



3.10.2 Adding a NWBC/SAP GUI for HTML (Web GUI) App Tile to Catalog and Group


NoteYou can copy the SAP-delivered tile information to your catalog in the same way.

3.11 Adding a Web Dynpro App to Fiori Launchpad

UseWeb Dynpro for ABAP of Web Dynpro ABAP (WD4A, WDA) is an SAP UI technology for developing Web applications in the ABAP environment. Web Dynpro apps can also be accessed via the SAP Fiori Launchpad. The tile and target mapping entries in the Launchpad Designer are pre-delivered for all SAP-delivered apps.

PrerequisitesYou should have implemented the Web Dynpro App "Trial Balance Version 2". The implementation of Web Dynpro applications is described in the 'SAP S/4 HANA other app Types Deployment (MAL)' configuration guide.



reserved. 23

3.11.1 Creating a Web Dynpro Target Mapping into Catalog

PrerequisiteYou must apply the SAP Notes 2243529, 2256680 and 2269272 from the Software and Delivery Requirements documentation, especially for the S4SD system alias.

Procedure1. In the Launchpad Designer, click on the catalog SAP_TC_CEC_SD_BE_APPS:S4SD and then choose

the tab Target Mappings in the right panel.2. Choose the GLAccount analyzeTrialBalance line and then choose Create Reference.



3.11.2 Adding a Web Dynpro App Tile to Catalog and Group


NoteYou can copy the SAP-delivered tile information to your catalog in the same way.

3.12 SAP Jam Integration Enablement

PrerequisiteYou must have purchased a license for SAP Jam.

3.12.1 Create SAP Jam User and GroupFor SAP Jam integration, each Fiori user should have access to your SAP Jam site. Please have your SAP Jam administrator create user IDs and groups for Fiori users, who need to use the Jam integration functionality.

24



3.12.2 Change Front-End Server User to Map to SAP Jam User1. Log in to the ABAP Front-End Server.2. Call the following transaction:

Transaction Code SU01

3. Enter User as your Fiori user, like FIORI_ADM and then choose Change (Shift+F6 ).4. In the Maintain Users screen, enter the E-mail Address as your SAP Jam user.5. Choose Save (Ctrl+S ) to save the change.

3.12.3 Configuring HTTP Proxy on Front-End ServerSince Jam Integration requires the Intranet Front-End Server connecting to Internet SAP Jam, we need to set a HTTPS proxy for the Front-End Server.1. Log in to the ABAP Front-End server.2. Call the following transaction:

Transaction Code SICF

3. Choose Execute (F8 ).4. In the Maintain Service screen, choose the menu Client → Proxy Settings.5. In the Proxy Configuration for HTTP Client dialog box, choose the HTTPS Protocol tab, enter the

proxy values and choose Execute (F8 ).

3.12.4 Importing SAP Jam Root Certificate into Front-End Server

1. Access SAP Jam in a web browser and download its root certificate as sapjam.cer.2. Log in to the ABAP Front-End server.3. Call the following transaction:

Transaction Code STRUST

4. Choose Display →Change (Ctrl+F1 ).5. In Trust Manager: Change screen, choose the node under SSL client SSL Client (Anonymous) and

then choose menu Certificate → Import.6. In the Import Certificate dialog box, choose the sapjam.cer file and then choose Continue (Enter ).

The SAP Jam server certificate details will appear.7. Choose Add to Certificate List; the certificate will be added to the above table. Then choose Save

(Ctrl+S ).

3.12.5 Configuring SAML2 Authentication for SAP Jam1. Log in to the ABAP Front-End server.2. Call the following transaction:



reserved. 25

Transaction Code SAML2

3. In the SAML 2.0 Configuration of ABAP System page, enable Local Provider, enter Provider Name as <TrustedIDP> and choose Operation Mode as Service Provider.

4. Call the following transaction:


5. Choose the node under SSF SAML2 Service Provider – S and then double click on the Subject field. The certificate details will appear.

6. Choose menu Certificate → Export. In the Export Certificate dialog box, choose File format as Base64, save the certificate as SSFSPS.cer.

7. In SAP Jam, choose menu Admin → SAML Trusted IDPs and then choose Register your identity provider.

8. In the Register a new SAML Trusted Identity Provider page, enter IDP ID as <TrustedIDP>, choose Enabled, choose Administrative Area as Company, copy and paste the content of SSFSPS.cer as X509 Certificate (Base64), leave the default values for the rest of the fields and then choose Register.

9. Check if the newly created one appears in the SAML Trusted IDPs page.

3.12.6 Configuring OAuth Client for SAP Jam1. Log in to the ABAP Front-End server.2. Call the following transaction:


3. If there's no PSE under SSF Collaboration Integration choose Create in the context menu, choose Algorithm as RSA with SHA1 and then choose Continue (Enter ).

4. Choose the PSE under SSF Collaboration Integration, and then double click on the Subject field. The certificate details will appear.

5. Choose menu Certificate → Export. In the Export Certificate dialog box, choose File format as Base64 and save the certificate as SSFCI.cer.

6. In SAP Jam, choose menu Admin → OAuth Clients and then choose Add OAuth Client.7. In the Add your OAuth Client page, enter Name as <OAuthClient>, enter Integration URL to your

company's URL like http://www.sap.com, copy and paste the content of SSFCI.cer as X509 Certificate (Base64) and then choose Save.

8. Check if the newly created one appears in the OAuth Clients page, choose View for it and copy the Key value as <ConsumerKey> for later use.

3.12.7 Configuring ABAP Social Media Integration in Front-End Server

1. Log in to the ABAP Front-End server.2. Call the following transaction:

Transaction Code CLB2_PLATF

3. On the Change view "Server Communication": Overview screen choose New Entries.

26



http://www.sap.com/

4. On the New Entries: Details of Added Entries screen, enter the entry as in the table below:Field ValueServ. Provider

TypeJam, select via F4 help

Server Jam productive, select via F4 help

Service Provider cubetree.com

Server URL <Jam URL>, for example https://integration3.sapjam.comProxy HostProxy Port

Proxy information if your Front-End Server can't directly connect to SAP Jam

SSF Application ID ANONYM

5. Double click on Authentication Method in the left side Dialog Structure and then choose New Entries. Enter the entries as in the table below and then choose Save (Ctrl+S ).

Context Authentication MethodAPPLI OAUTH_10_SHA1

APPUSR OAUTH_10_SHA1_3

NONE NONE

USER SAML_20


Transaction Code CLB2_APPLI_PLATF

7. On the Change view "Application-Server Assignment": Overview screen choose New Entries.8. On the New Entries: Overview of Added Entries screen, enter Application ID as DEFAULT, Service

Provider Type as Jam via F4 Help and Server as Jam productive via F4 help.9. Double click on Server Settings in the left side Dialog Structure and then choose New Entries. Enter

Ext. Application ID as <OAuthClient>, Consumer Key as <ConsumerKey> and then choose Save (Ctrl+S ).


Transaction Code SICF

11. Activate the services below:o /sap/bc/ui2/smi/rest_tunnel/o /sap/bc/ui5_ui5/sap/arsrvc_sm/


Transaction Code CLB2_TUNNEL

13. Choose New on the New Entries: Details of Added Entries screen, enter the entries one by one as in the table below and then choose Save (Ctrl+S ).

Tunnel Destination

Service Provider Type

Application ID

Service Root Resource Path

Authentication Context

Jam Jam DEFAULT api/v1/OData $metadata NONE

Jam Jam DEFAULT api/v1/OData USER



reserved. 27

https://integration3.sapjam.com/

Tunnel Destination

Service Provider Type

Application ID

Service Root Resource Path

Authentication Context

Jam Jam DEFAULT api/v1/feed/post USER

Jam Jam DEFAULT /v1/single_use_tokens USER

3.12.8 Configuring ABAP SMI for SAP Fiori Apps

3.12.8.1 Activating ABAP SMI OData Services1. Log in to the ABAP Front-End server.2. Call the following transaction:

Transaction Code /IWFND/MAINT_SERVICE

3. Activate the services below for System Alias LOCAL:SM_INTEGRATION_V2_SRVSM_CATALOG_SRV

3.12.8.2 Creating the Social Media Catalog1. In the Launchpad Designer, choose the Catalogs tab, and then choose the +.2. In the Create Catalog dialog box, input the entry below and then choose Save.

Title ID Remote ID System alias

Base URL

Remote Social Media Catalog

Jam SMCatalog LOCAL /sap/opu/odata/sap/SM_CATALOG_SRV/

3.12.8.3 Creating a Social Media Integration Role1. Log in to the ABAP Front-End Server.2. Call the following transaction:


3. Create a role for Social Media Integration or change an existing role and assign your user to it.4. In the Change Roles screen, choose the Menu tab, choose the dropdown list for Transaction and

choose SAP Fiori Tile Catalog.5. In the Assign Tile Catalog screen, choose Catalog Provider as Remote Catalogs, Catalog ID as Jam

from the dropdown list and then choose Continue (Enter ).6. In the Change Roles screen, choose Save (Ctrl+S ).

28



3.12.9 Verify Jam Integration Tiles7. In the Launchpad Designer, choose the sample group that you created in the section "Creating a

Sample Group", for example Z_RDS_BCG and then choose Add Tile.8. In the Add Tile to Group 'Z_BCG_RDS' screen, filter the Catalog Social Media Catalog.9. Choose both the Notification Tile and Group Tile and then navigate back. The two tiles should

appear in your sample group.

10. In the SAP Fiori Launchpad, navigate to your custom group; you should see the two Jam Tiles like below:

3.12.10 Verify Jam Integration in Fiori Apps1. In the SAP Fiori Launchpad, use the Sales Order Fulfillment Issue app as an example and choose

any of the issues.



reserved. 29

2. In the Issue Details page, choose Share.

3. In the Share on SAP Jam dialog box, choose your Jam Group and then choose OK.

4. In SAP Jam, choose Feed Updates, check if your Share appears.

30



4 Transportation

UseWhen implementing and configuring the best practices in a multi-tier customer landscape, the applied configuration settings need to be transported from one system landscape to the next, i.e. from a development landscape to a quality landscape and to a productive landscape in case of a 3-tier landscape environment. This section describes additional aspects that need to be taken into consideration while configuring SAP S/4 HANA Fiori in a multi-tier landscape. As a prerequisite, the ABAP transport system between the systems needs to be configured properly. Configuration settings that can be transported using the ABAP transportation mechanisms and where no additional or subsequent steps are required are not mentioned in the following list.

ProcedureFind in the following table an overview on the steps where additional considerations are required.

Chapter name Comment/Additional informationCreating a sample PFCG Role and assign to End Users

The user assignment needs to be carried through in each system. Find additional information on transporting pfcg Roles here:http://help.sap.com/saphelp_nw70ehp2/helpdata/en/6d/7c8cfd410ea040aadf92e1f78107a4/content.htm

Creating a Target Mapping (Optional)

All settings carried through in the Launchpad Designer can be added to a transport request as described in chapter Creating and Assign Transport Request.



reserved. 31

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/6d/7c8cfd410ea040aadf92e1f78107a4/content.htm

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/6d/7c8cfd410ea040aadf92e1f78107a4/content.htm

www.sap.com/contactsap

© 2016 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 or an SAP affiliate company.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 or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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 (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Material Number:

http://www.sap.com/corporate-en/legal/copyright/index.epx