Unit 1: SAP Fiori Launchpad Architecture

Week 1: Understanding SAP Fiori Launchpad
Unit 1: SAP Fiori Launchpad Architecture

SAP Fiori Launchpad Architecture
Overview
SAP Fiori is designed to focus on the

most common and critical activities
▪ Role-based
▪ Responsive
▪ Simple
▪ Coherent
▪ Delightful
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

On-premise architecture
SAP Fiori launchpad architecture high level

▪ Client/browser or mobile devices
▪ Reverse proxy – SAP Mobile Platform On-Premise
▪ ABAP servers
▪ Back-end server
SAP Mobile Platform
for Mobile Devices
Note: It is also possible for FES from the cloud to
connect to an existing on-premise landscape.
Front-End Server
SAP Fiori Applications OData Services
SAP Business Suite

SAP S/4HANA …
(ERP, SRM,…)

SAP Fiori launchpad architecture with SAP Web Dispatcher
SAP Fiori launchpad architecture high level

▪ Client/browser or mobile devices
▪ Reverse proxy – SAP Web Dispatcher
▪ ABAP servers
▪ SAP HANA extended application services (XS)
▪ Back-end server

Deployment options
Gateway Central Hub Deployment Embedded System Development Gateway Central Hub
▪ Support for multiple system routing ▪ Less runtime overhead ▪ Similar advantages to Central Hub
▪ Deploying content without touching ▪ One less system to maintain ▪ The only difference between Central
the back end Hub and Development hub is the
▪ Single point of access to the back end services development does not need to
be deployed in the back end

Components – Central hub system
Components required for central hub deployment
SAP NetWeaver < SAP NetWeaver >=

7.40 7.40
NW Gateway ▪ GW_CORE SAP_GWFND
▪ IW_FND (Comes with it)
SAP Back End IW_BEP SAP_GWFND
(Comes with it)
SAPUI5 1.28 or Higher 1.28 or Higher

Components – Embedded system
Components required for embedded deployment
SAP NetWeaver < SAP NetWeaver >=

7.40 7.40
SAP Back End ▪ GW_CORE SAP_GWFND
▪ IW_BEP (Comes with it)
▪ IW_FND
SAPUI5 1.28 or Higher 1.28 or Higher

SAP Fiori launchpad building blocks
SAP Fiori launchpad –

Building blocks
▪ Based on the unified shell
architecture
▪ Client-side runtime
environment, which can be
hosted on different server
platforms
▪ Shell offers unified services
with platform-independent
interfaces to the hosted apps
and shell components

SAP Fiori launchpad – Building blocks architecture
SAP Fiori launchpad – Building blocks Web Browser
▪ Apps are embedded in application container FioriLaunchpad.html CustomLaunchpad.html
▪ Shell services and renderer are managed by Runtime

the central shell container Configuration
▪ Runtime configuration is fed by the following Shell Container

settings:
– Static configuration settings in the hosting
HTML page Shell Renderer Shell Services
– Dynamic configuration data read from the Home Page Platform- Platform-
front-end server during startup Specific Independent
Service Service
– Dynamic settings are passed as query
parameters in the URL Application Container
▪ FioriLaunchpad.html contains all JavaScript Service
Application Adapter
components

Summary
In this unit, we gave a brief overview of

▪ SAP Fiori launchpad architecture
▪ SAP Fiori launchpad deployment options
▪ SAP Fiori launchpad components needed
▪ SAP Fiori launchpad building blocks
architecture

Thank you.
Contact information:
open@sap.com
© 2017 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this docume nt or any related presentation, or to develop or release
any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products,
and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The
information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various
risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,
and they should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trade marks 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 companie s.
See http://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Unit 2: SAP Fiori Launchpad Troubleshooting
Tools
SAP Fiori Launchpad Troubleshooting Tools
Verifying system ID and client from Login screen
▪ Use Chrome developer tools (F12)

▪ Locate network request for "login.js"
▪ Examine cookies

Verifying system ID and client from the launchpad home
▪ Use "Sources" tab in Chrome

▪ Locate "oServerSideConfig" in
FioriLaunchpad.html
▪ Use breakpoints to pause processing
▪ From Console tab, evaluate
"console.table(oServerSideConfig)"

Analyzing missing tiles
PageSets OData call (Network tab)

▪ JSON Viewer Chrome extension is
needed to show JSON formatted in
browser
▪ Open in new tab
▪ Search name of tile
▪ "catalogId" contains catalog information
▪ Chip  configuration shows details of
tile without accessing launchpad
designer
▪ Tile won't display if target mapping
defined in tile doesn’t exist

Analyzing missing tiles (cont.)
Use the extended "start_up" call ("*")

▪ Search for intents (semobj-action) to find
all assigned target mappings / details
▪ Duplicate intents with different
configurations can cause unexpected
results
▪ Intents are case-sensitive

Examining system aliases
Invalid or missing system alias

results in app opening on SAP
Gateway system
Use extended start_up call again

▪ Copy JSON content of response
▪ "var startupobj = <paste content of JSON
response>" in Chrome console
▪ "console.table(startupobj.systemAliases)"
in Chrome console to display a table of the
system aliases
▪ "console.table(startupobj.targetMappings)"
available for target mappings

Examining system aliases (cont.)
SE24 to resolve the alias using the

standard class (KBA 2423115)
▪ /UI2/CL_SYS_ALIAS_MANAGER class, display
▪ Execute in Test Environment (F8)
▪ Continue on "Replace Generic Parameter
Types" screen, no changes
▪ Execute RESOLVE method
▪ Provide IV_ALIAS as derived from the start_up
request
▪ Review details of results using "Single Entry"
icon (Shift+F7)

Differences in business and technical catalogs
Business Catalogs
▪ Collection built for specific business roles
– Comprised of references from technical catalogs
– Can be assigned directly to end users
Technical Catalogs
▪ Collection of tiles and target mappings from related
technical areas and development teams
– Comprised of mostly original tiles/mappings
– Should not typically be assigned directly to end
users

Support tools
/UI2/FLC
▪ Used to analyze SAP Fiori launchpad content
status
▪ Filters for catalog, user, and adaptation layer
▪ Results table has status icons to highlight problem
areas
– "Message" column shows warning/error detail
/UI2/FLIA
▪ Used to analyze intent (target mapping) resolution
▪ Filter by intent and form factor
▪ Additional filters similar to those in /UI2/FLC

Caches
SAP Fiori content affected by multiple caches

▪ Browser cache
▪ Web Dispatcher cache (opt.)
▪ ICM cache
▪ UI2 cache
▪ UI5 index
▪ SAP Gateway OData caches
– IWFND
– IWBEP
Useful KBAs
▪ 2319491 – How to clean up the cache after applying changes that affect SAP Fiori apps
▪ 2116090 – UI Addon, SAP UI: Information for customers for efficient incident analysis

Summary
In this unit we discussed the following

▪ How to use Chrome development tools
▪ How to locate system ID of Fiori system
▪ How to debug PageSet
▪ How to debug target mapping using start_up
extended call
▪ We learned how to debug system aliases used by a
target mapping
▪ We introduced to you the troubleshooting tools that
are available to you to troubleshoot Fiori Launchpad
▪ Lastly we talked about how caching could impact
your content

Thank you.
open@sap.com
Unit 3: SAP Fiori Applications and Maintenance
SAP Fiori Applications and Maintenance
Overview
▪ The SAP Fiori apps reference library enables you to

explore, plan and implement SAP Fiori.
▪ Discover all the SAP Fiori apps available today.
▪ Find key information for each app, including all the
technical data you need for installation and
configuration.
▪ View the data for previous app versions.
▪ Navigate directly to related resources, such as app
documentation, Product Availability Matrix, and
Maintenance Planner.

Overview
To install an SAP Fiori app, the

recommended process is: Select App(s) in SAP
Plan Installation in Install and Update
Fiori Apps Reference
▪ Select the app in the SAP Fiori apps Library
Maintenance Planner System
reference library
▪ Plan installation in Maintenance Planner
1 Choose SAP Fiori Apps 1 In Maintenance Planner, 1 In case of new installation
▪ Install and update the system select existing system or start software provisioning
plan installation of new manager with stack.xml
system
2 View product version 2 Choose target product 2 Start SUM with stack.xml
requirements and navigate version and support to update the system to
to Maintenance Planner package stack for all the target support package
involved systems in a stack
single planning step
3 Generate and download
consolidated stack.xml and
archives for front-end,
back-end, and SAP HANA
components (if needed)
Maintenance Planner
Installation process with Maintenance Planner offers following advantages:

▪ Consolidated planning allows users to generate consolidated stack XML for all planned landscape changes
▪ Installation of new systems supported
▪ Required files for all involved systems can be pushed to download basket in a single planning step
▪ Multiple deployment options to choose from

Planning SAP Fiori apps installation with Maintenance Planner
▪ In SAP Fiori apps reference library, select

SAP Fiori apps to view product features
and implementation details
▪ Switching on the aggregate mode will let
you install multiple SAP Fiori apps with a
single transaction

Navigate to Maintenance Planner
▪ Once apps are grouped, navigate to Maintenance Planner directly from Installation
Details tab. In this scenario, all the apps selected can be installed in a single instance
of Maintenance Planner.

Maintenance Planner – Three step procedure
Maintenance Planner offers the installation

of an SAP Fiori app in three simple steps:
▪ Overview of available apps
▪ System selection
▪ Details of impacted systems

Maintenance Planner – Overview of Available Apps
▪ Check details about technical prerequisites for front-end, back-end, and SAP HANA servers.

Maintenance Planner – System Selection
Maintenance Planner provides

following details for back-end
server:
▪ Current software version
▪ Minimal required release
• Maintenance Planner provides options

to select existing system, install a new
system for front-end and SAP HANA
XS server.
• New installation of front-end and SAP
HANA system is supported. For
existing systems, current software state
is displayed and target version can be
selected.

Maintenance Planner – Details of Impacted systems
• Once you have made the system selection,

click Next to view the snapshot of all the
impacted systems.
• At this stage, you can proceed to select files
and download installation archives, or chose
Install Additional Software to iteratively install
additional software.

Maintenance Planner – Select and download
▪ To select and download installation media, select OS/DB files, select stack-dependent and independent files
▪ Select OS/DB files for back-end and front-end systems
▪ Select OS/DB files for both systems and click Confirm Selection
▪ Click Next and move to the next step
▪ Download all the relevant files by clicking Download Stack XML and click Push to Download Basket to
download the archives to download basket

SAP Fiori Launchpad Content Transport
Demo
DEMO

Summary
To install an SAP Fiori app, the recommended

process is:
▪ Select the app in the SAP Fiori apps reference library
▪ Plan installation in Maintenance Planner
▪ Install and update the system

Thank you.
open@sap.com
Unit 4: Translation
Translation
Translatable areas
The launchpad itself Application labels

▪ Search bar ▪ Fields
▪ Menu Application messages
Tile text elements ▪ Notifications
▪ Title
Back-end OData responses
▪ Subtitle
▪ Metadata
▪ Catalog title
▪ Group title

Translation
The launchpad itself
Includes:
▪ Logon language selector
▪ Search
▪ Menus

Translation
How to translate the launchpad itself
▪ Make sure that the required language pack is installed

via transaction SMLT
▪ To enable language selection at logon:

1. In transaction SICF, open and select service name “FLP” (path: /sap/bc/ui2/)
2. Enter Edit mode by choosing Display ↔ Change button
3. Choose Error Pages → Logon Errors → Configuration
4. Make sure that Language is selected under System Logon Settings → Select Display → Language
5. Select Input/green checkmark
6. Save the data by choosing Display ↔ Change button again and hitting Yes to save
Translation
Tile text elements
▪ Catalog and group titles are defined in the

launchpad designer.
▪ The tile title and subtitles are defined in the tile
catalog in the launchpad designer as well.
▪ Translations are defined through transaction
SE63 on SAP Gateway.

Translation
How to translate tile/group/catalog titles
1. Open transaction SE63 in the SAP

Gateway system hosting the launchpad
2. Choose Short Texts button or Translation
→ ABAP Objects → Short Texts
3. Expand 00 Meta Objects and select TABL
Tables (Meta)
4. Enter object name
*WDY_CONF_USERT2*
5. Set the source and target (translation)
languages and choose Edit

Translation
How to translate tile/group/catalog titles
6. Set User Scope to A and use the search help

(F4) on Configuration ID
7. Select configuration ID for desired catalog
and execute
8. Enter the translations for relevant texts and
save
9. Repeat for the other configuration ID for the
desired catalog and for the group
10. It may be necessary to run report
/UI2/INVALIDATE_GLOBAL_CACHES

Translation
Application labels
▪ Translated via i18n files

▪ Editable through SE80
▪ Standard applications may
be extended to include other
i18n files from Web IDE

Translation
How to translate application labels
1. Start transaction SE80 in your SAP Gateway system

2. Copy existing properties file to a new file for your
own language
▪ Enter the new name under Page. The format is:
i18n/i18n_<iso code for your language>.properties
▪ The system will now ask for an object key. Request
this via SSCR keys
Note: The following caches must be invalidated after

adding i18n file:
▪ /UI2/INVALIDATE_GLOBAL_CACHES
▪ Global ICM cache (SMICM → Invalidate Globally)
▪ Browser cache

Translation
Application messages
▪ These messages are located in a

message class on your back-end
system.
▪ These messages are the ones that pop
up automatically.

Translation
How to translate application messages
1. Start transaction SE91 and enter the message

class (a search help exists, so class can be
found via package, application component,
etc.)
2. Select the message and translate each
individual text via Goto → Translation
3. Enter the target language
4. Enter the translation and save
5. After the translation is done, refresh your
browser
6. It may be necessary to run report
/UI2/INVALIDATE_GLOBAL_CACHES

Translation
Back-end OData
▪ Information from certain OData sources may be

translated to reflect the local language settings
▪ Since OData sources rely on RFC destinations,
a unique RFC destination is required for each
supported language
▪ Example: Value Help values in apps

Translation
Setting the language for back-end OData
1. Go to transaction /n/iwfnd/maint_services in your

SAP Gateway system
2. Select the OData service your app is using and
double-click in the system alias
3. Choose the Edit button and click the Logon &
Security tab
4. Enter the desired language (If you leave it empty,
the language will be the one specified in the login).
Save the changes
5. Now you can see the back-end information in the
selected language despite the logon language

Translation
Logon language priority
▪ The logon language is determined by the following

mechanisms (higher priority first):
1. URL parameter (sap-language), if maintained
2. HTTP request accept-language header, which is
defined by the browser and provides a list of
languages with probabilities
3. The value maintained in SU01 for a particular
user
▪ More information available in KBA 2420212 and

KBA 2422021

Translation
Summary
The launchpad itself Application labels

▪ Search bar ▪ Fields
▪ Menu Application messages
Tile text elements ▪ Notifications

▪ Title Back-end OData responses
▪ Subtitle
▪ Metadata
▪ Catalog title
▪ Logon language priorities
▪ Group title

Thank you.
open@sap.com
Unit 5: Replication of Catalogs
Replication of Catalogs
Scenario
Newer SAP Fiori ships “legacy app” content FRONT-END SYSTEM

(e.g. Web Dynpro, Web GUI transactions) via
so-called “back-end catalogs”. (Typical naming
convention *_TC_*_BE_* Technical Catalog BUSINESS CATALOGS
BackEnd).
These are delivered in the back-end system.
On the front-end server (FES) “dangling

references” to these applications are delivered Web Dynpro
in business catalogs *_BC_* , which are only Web GUI Transactions
satisfied once the technical catalogs have been
*replicated* to the front-end server. BACK-END CATALOGS
(Table SUI_TM_MM_APP)
BACK-END SYSTEM
Technical catalogs, business catalogs and groups
▪ Technical catalogs, naming convention *_TC_ *

▪ Business catalogs, naming convention *_BC_*
▪ Business group, naming convention *_BCG_*
▪ Catalogs can be found in launchpad designer
▪ For a particular app, you can find the
corresponding catalogs in the SAP Fiori apps
reference library

Overview
FRONT-END SERVER BACK-END SERVER
When installing the SAP Fiori /UI2/V_ALIASCAT Table SUI_TM_MM_APPS

launchpad, catalogs must be Delivered mapping or *_TC_*_BE* definition list of
name of _TC_BE_ to Web Dynpro or Web GUI
retrieved from the back end. apps and mappings to
SYSTEMALIAS
SAP delivers some content to allow intents
this replication, but consultants must 1) Configure view 2) Run transaction

/UI2/SYSALIASMAP /UI2/APPDESC_GET
perform some manual tasks after create entry to map
installation. Alias above
Create <alias>_RFC
destination in
transaction SM59
SAP-delivered Fiori
business catalog *_BC_*
shipping dangling
references to content in
*_TC_*_BE_*
APPDESC_GET creates
_TC_*_BE_* as read-
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC only SAP Fiori catalogs 4
UI2 system alias (SAP-delivered)
The system aliases are stored in table

/UI2/SYSTEMALIAS. It can be maintained using
the maintenance view /UI2/V_SYSALIAS in
transaction SM30.
The front-end system needs to connect to the
back-end server during:
▪ SAP Fiori launchpad design time, when replicating
back-end catalogs to the front-end server: here we
need an RFC connection. Naming convention:
<sysalias>_RFC, e.g. FIORI_BE_RFC
▪ SAP Fiori launchpad runtime, when navigating to the
application: here we need an HTTP or an HTTPS
connection. Naming convention:
<sysalias>_HTTP or <sysalias>_HTTPS, e.g.
FIORI_BE_HTTP

Mapping catalogs and system alias (SAP-delivered)
▪ Map custom back-end catalog to front-end

system alias modifying the entries in table
/UI2/V_ALIASCAT using transaction SM30
▪ Make sure you enter the catalog name defined
in the back-end mass maintenance tool for app
descriptors
▪ You can define your own system alias and
assign it to your custom technical catalog

Mapping sources and system alias
▪ In the next step, each customer must fill view

/UI2/V_ALIASMAP
▪ In this view, you map the system alias with your
own system aliases
▪ Alternatively, you can directly create SM59
destination called NW_RFC, S4CMD_RFC etc.
and skip this step

Transaction /UI2/APPDESC_GET
▪ For SAP content replication via business catalog,

transaction /UI2/APPDESC_GET is strongly
recommended, which will attempt to replicate all
catalogs contained in /UI2/V_ALIASCAT
▪ Select the system alias and catalog ID you defined
in the previous step
▪ Report must be run in test mode prior to importing
the catalogs
▪ To perform the catalog replication, follow the
procedure explained in SAP Note 2269272

Further reports available
Additionally, the following reports are available

with more options for catalog replication:
▪ /UI2/DELETE_APP_DESCR_CATS Delete replicated
catalogs for a remote system alias
▪ /UI2/GET_APP_DESCR_REMOTE_ALL Replicate
back-end catalogs for all system aliases
▪ /UI2/GET_APP_DESCR_REMOTE_DEV Replicate
back-end technical catalog from remote system (DEV)
▪ These report are enclosed in package
/UI2/SERVICES_PB_CAT_PROV_703

Copying business catalogs and groups
▪ To copy a catalog with a reference, just drag and

drop it to “New Catalog with References”
▪ To delete a catalog, drag and drop it to “Delete”

Assigning catalogs to users
▪ The last step is assigning your created catalog to your

user. This assignment can be done in transaction PFCG
by choosing “SAP Fiori Tile Catalog”

Unit summary
▪ SAP provides Web Dynpros and HTML GUI catalogs

in SAP S/4HANA that must be replicated to the SAP
Gateway system
▪ To do so, SAP provides some system aliases
mapped with the catalogs
▪ Customers must map these system aliases with their
own RFCs
▪ A replication report must be executed in the SAP
Gateway system in order to perform the replication
▪ The replicated catalogs have to be copied in
launchpad designer so modifications can be carried
out

Thank you.
open@sap.com
Unit 6: SAP Fiori Launchpad Content Transport
Overview
Transport Management System

▪ Transport Management System (TMS) is used to
model and manage your system landscape
▪ Provides tools for configuring your system landscape,
as well as for organizing, carrying out, and monitoring
transports
▪ Enables SAP Fiori launchpad applications and
customizations to be transported throughout the
SAP ecosystem

Architecture: high-level overview – Cloud and on-premise options
Web
SAP Cloud Platform On-Premise Tools

Front-End Services SAP Web IDE
Mobile SAP Mobile Platform
Services SAP Fiori OData for Mobile Devices
Apps Services
SAP Fiori User
Interfaces
SAP S/4HANA Cloud Front-End Server
SAP Fiori Apps OData Services
SAP S/4HANA
ABAP in Eclipse
SAP S/4HANA Business Logic SAP Business Suite …
SAP S/4HANA Back-End Services
(ERP, SRM, …)

SAP Fiori transport
Repository objects Quality Gate Management (QGM)

▪ Gateway Service Development Quality Production
Assurance
▪ SAPUI5 app
Customizing Gateway Gateway Gateway
Server Server Server
▪ System aliases
Repository objects
Gateway Gateway Gateway
▪ Service implementation Back End Back End Back End
Customizing Requests
SAP Fiori scopes for adapting content
Adapting Content
▪ Administrator can adapt the content delivered by
SAP within SAP Fiori launchpad for the roles within
the company using the SAP Fiori launchpad
designer.
▪ SAP delivers predefined content like catalogs and
groups for the SAP Fiori launchpad.
▪ Administrators can use the launchpad designer to
copy and adapt the content in the configuration and
customizing scopes.
▪ The predefined SAP Fiori launchpad content uses
the Web Dynpro configuration as a persistence tool.
The content is stored in the following scopes:
Configuration, Customizing, and Personalization.

SAP Fiori Launchpad Designer Scope
Configuration Scope
▪ System-wide settings
▪ Content delivered by SAP is stored in configuration scope
▪ Administrators can copy a catalog and adapt the copy in
Customization scope
▪ Access launchpad designer using scope=CONF
https://<server>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html ?sap-client=<client>&scope=CONF
Customizing Scope
▪ Client-specific settings (sap-client)
▪ Content changes only valid for current client
▪ These settings take priority over configuration settings
▪ Administrators can use Customizing Scope to copy a catalog
and adapt it for client
▪ Access launchpad designer using scope=CUST
https://<server>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html ?sap-client=<client>&scope=CUST
Personalization Scope
▪ User-specific settings
▪ End users can adapt a group that contains
predefined content and has been assigned to their
user role
▪ Users can do actions like rearrange their tiles and
save these preferences
▪ These settings take priority over customizing and
configuration settings

Creating a transport – Configuration scope
▪ You have to create a workbench request

▪ The user actions such as creating or deleting catalogs or groups, adding tiles to or removing tiles from
catalogs or groups are captured under the workbench request
▪ Using scope=conf, you see the client information in red on the header

Creating a transport – Customizing scope
▪ You have to create a customizing request

▪ The user’s actions such as creating or deleting
catalogs or groups, adding tiles to or removing tiles
from catalogs or groups, are stored under the
customization request
▪ Using scope=cust, you see the client information in
blue on the header

Creating a transport – SE01, SE09, SE10
Transactions
▪ SE01 is the main screen of the Transport Organizer.
▪ SE09 is the workbench transport requests transaction.
▪ SE10 is the customizing request display transaction.

Creating a transport – Prerequisites
Create Transport Requests Procedure

1. Transaction SE01.
2. Choose Request from the Menu tab.
3. Choose Create from the submenu.
4. Choose OK.

Creating a transport – Setting default transport
Configuration Scope in Launchpad Designer

1. Launch the launchpad designer in configuration scope.
2. Choose the Settings button.
3. Select the workbench request.
4. Enter the default package name.
5. Choose OK.
You can create a local object in configuration scope by starting the name with Z, for example, ZServiceCatalog.
In that case, setting the workbench request and the package is not required.
Creating a transport – Setting default transport
Customization Scope in Launchpad Designer

1. Launch the launchpad designer in customization
scope.
2. Choose the Settings button.
3. You can choose either the Local Object or any
customizing request from the Customizing
Request dropdown list
4. If you choose customizing request, all the user
actions are saved under the selected request.
5. Choose OK.
6. You have saved the selected customizing request in
the target parameters as your default values.
The settings made in the launchpad designer are visible in the back-end user parameters.
Creating a transport – Setting default transport back end
1. Go to transaction SU02.
2. Choose the Parameters tab on the Maintain User
Profile screen.
3. Maintain the parameters below.
4. You have saved the selected customizing request
in the target parameters as your default values.
The transport request and package set in the user parameters are visible in the launchpad designer settings.
Parameters Description
/UI2/WDC_DEVCLASS Package name, which contains the page
/UI2/WD_TRKORR_CONF Workbench request to which the workbench transport for the page has to be submitted
/UI2/WD_TRKORR_CUST Customizing request to which the customizing transport for the page has to be submitted
Transport in action
DEMO

Transport – Common issues
Common Issues
▪ You make some changes on a catalog/group in SAP Fiori launchpad designer and they are captured in a
transport request. After transporting the changes to another system, you find the entire catalog/group has
been transported instead of a single tile/target mapping you just modified.
 Every time you make any change in a catalog/group it will record all the information of this catalog/group
in the transport request, which means the transport unit is a catalog/group, not a tile/target mapping. KBA
2498051.
▪ SAP Fiori catalogs and groups cannot be transported to other systems.
 No transport request was assigned in the launchpad designer when the catalogs and groups were
created. KBA 2406055.
▪ During the Hub registration of a Gateway service the ICF node is not captured to a transport request,
although according to the package assignment, it should be assigned to a corresponding transport request.
 The ICF node of the namespace part (for example /UI2/) is registered to the $TMP package (for example
SICF node "ui2" under /default_host/sap/opu/odata/). KBA 2430348.

Transport – Common issues
Common Issues
▪ No transport requests to select in launchpad designer.
 The /UI2/TRANSPORT OData service is not using the LOCAL system alias. KBA 2401506.
▪ Catalog changes update via transport copy takes a very long time before it is available in the system client.
 This is expected behavior since the cache is not invalidated. KBA 2463351.
▪ After transporting catalog/group changes for a new tile, the new tile does not appear for existing users in the
SAP Fiori launchpad of the target system for a while.
 The global cache is outdated, or there is a stored variant of the group in the personalization layer.
KBA 2476801.

Summary
Transport Management System

▪ Transport Management System (TMS) is used to
model and manage your system landscape.
▪ Provides tools for configuring your system
landscape, as well as for organizing, carrying out,
and monitoring transports.
▪ Enables SAP Fiori launchpad applications and
customizations to be transported throughout the
SAP ecosystem.

Thank you.
open@sap.com
Unit 7: SAP Fiori Launchpad Cache
SAP Fiori Launchpad Cache
Principle
▪ Versioned URLs for all resources which are

cached in the browser (injecting tokens)
▪ Cache-buster tokens returned by the server
▪ Software updates generate new cache-buster
tokens
▪ New generated URLs are not found in the
browser´s cache and resources are reloaded
from the server

Implementation
▪ By HTTP handler /UI2/CL_FLP_HTTP_HANDLER

 Before SAP_UI 750 SP03/UI add-on 2.0 SP03: only ICF service /sap/bc/ui2/flp
<<Browser>> <<Browser>>
https://<host>:<port>/sap https://<host>:<port>/sap/bc/ui5_ui5/ui2
/bc/ui2/flp/Index.html /ushell/shells/abap/FioriLaunchpad.html
<<ICF Node>>
<<ICF Node>>
/sap/bc/ui5_ui5/
Before SP03 /sap/bc/ui2/flp
ui2/ushell
<<ABAP Class>
<<ABAP Class>
/UI5/
/UI2/CL_FLP_HTTP_HANDLER
CL_FLP_HTTP_HANDLER
BSP Repository
/UI2/USHELL

Implementation
▪ By HTTP handler /UI2/CL_FLP_HTTP_HANDLER

 As of SAP_UI 750 SP03/UI add-on 2.0 SP03: also ICF service /sap/bc/ui5_ui5/ui2/ushell
<<Browser>>
<<Browser>>
https://<host>:<port>/sap/bc/ui5_ui5/ui2
https://<host>:<port>/sap/bc/ui2/flp/Index.html
/ushell/shells/abap/FioriLaunchpad.html
<<ICF Node>>
<<ICF Node>>
/sap/bc/ui5_ui5/
As of SP03 /sap/bc/ui2/flp
ui2/ushell
<<ABAP Class>
/UI2/CL_FLP_HTTP_HANDLER
<<ABAP Class> BSP Repository

/UI5/
CL_FLP_HTTP_HANDLER /UI2/USHELL

Types of cache-buster tokens
Four types
▪ For SAPUI5 library resources: /~20161108153600~/
▪ For SAPUI5 applications resources (fine-grained): /~7E0DB5259167BE2983A36342A1766544~5/
▪ For SAP Fiori application resources (single): /~BC4721AE212118A9F76BAD97A4A9C9B1~C/
▪ For UI2 services (SAP Fiori launchpad content): sap-cache-id=C0191EB9D99097171E78C8C86E6A5C4C

SAPUI5 resources token
▪ Used for SAPUI5 library resources located in the MIME repository

▪ Token: timestamp of the latest SAPUI5 library deployed in the MIME repository
▪ Sent as part of ServerSideConfig in FioriLaunchpad.html
▪ Invalidated automatically when SAPUI5 library is deployed in the MIME repository
▪ Resource types:
– ushell_abap
– core
– ushell lib
– standard UI5 themes

SAPUI5 applications resources (fine-grained) token
▪ Used for SAPUI5 applications

▪ Token: Ends with suffix (~5). Different for each SAPUI5 application (fine-grained)
▪ Sent as part of the start_up request
▪ Invalidated manually with report /UI5/APP_INDEX_CALCULATE
▪ Resource types:
– SAPUI5 application 1
–…

SAP Fiori application resources (single) token
▪ Used for SAP Fiori application resources and SAPUI5 apps excluded from fine-granular token mechanism
▪ Token: Ends with suffix (~C). Single/Global/Generic token
▪ Invalidated manually with report /UI2/INVALIDATE_CLIENT_CACHES
▪ Resource types:
– FLP tiles
–…

UI2 services token
▪ Used for UI2 OData and REST services

▪ Token: URL parameter sap-cache-id. Different for each UI2 service
▪ Invalidated when UI2 cache is invalidated (Note 2362875)
▪ Resource types:
– OData service /UI2/PAGE_BUIDER_PERS
– OData service /UI2/INTEROP
– REST service start_up

Evaluation (ServerSideConfig)
▪ Cache-buster tokens transported in the

FioriLaunchpad HTML file as part of the
ServerSideConfig and in the response
of the start_up request

Evaluation (start_up)
▪ Cache-buster tokens transported in the

FioriLaunchpad HTML file as part of the
ServerSideConfig and in the response
of the start_up request

Summary
In this unit we gave a brief overview of:

▪ Cachebusting principle
▪ Cache-buster implementation in the SAP Fiori
launchpad
▪ Types of cache-buster tokens
▪ Evaluation of the cache-buster token in the SAP Fiori
launchpad application

Thank you.
open@sap.com

Unit 1: SAP Fiori Launchpad Architecture

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Unit 1: SAP Fiori Launchpad Architecture

Hochgeladen von

Copyright:

Verfügbare Formate

Week 1: Understanding SAP Fiori Launchpad

Unit 1: SAP Fiori Launchpad Architecture

SAP Fiori is designed to focus on the

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

SAP Fiori launchpad architecture high level

SAP Business Suite

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

SAP Fiori launchpad architecture high level

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Components required for central hub deployment

SAP NetWeaver < SAP NetWeaver >=

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Components required for embedded deployment

SAP NetWeaver < SAP NetWeaver >=

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

SAP Fiori launchpad –

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

SAP Fiori launchpad – Building blocks Web Browser

▪ Apps are embedded in application container FioriLaunchpad.html CustomLaunchpad.html

▪ Shell services and renderer are managed by Runtime

▪ Runtime configuration is fed by the following Shell Container

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

In this unit, we gave a brief overview of

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

▪ Use Chrome developer tools (F12)

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

▪ Use "Sources" tab in Chrome

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

PageSets OData call (Network tab)

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Use the extended "start_up" call ("*")

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Invalid or missing system alias

Use extended start_up call again

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

SE24 to resolve the alias using the

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

SAP Fiori content affected by multiple caches

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

In this unit we discussed the following

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

▪ The SAP Fiori apps reference library enables you to

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

To install an SAP Fiori app, the

Installation process with Maintenance Planner offers following advantages:

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

▪ In SAP Fiori apps reference library, select

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Maintenance Planner offers the installation

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Maintenance Planner provides

• Maintenance Planner provides options

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

• Once you have made the system selection,

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

To install an SAP Fiori app, the recommended

▪ Technical catalogs, naming convention _TC_