0% found this document useful (0 votes)
264 views11 pages

SAP Fiori Launchpad

The document discusses deployment options and recommendations for SAP Fiori launchpad. It can run on ABAP, SAP Business Technology Platform, or SAP Enterprise Portal. ABAP is recommended for on-premise usage while SAP BTP is recommended for cloud deployments. The document provides a comparison of features and capabilities of each option.

Uploaded by

saurabh.rai83
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
264 views11 pages

SAP Fiori Launchpad

The document discusses deployment options and recommendations for SAP Fiori launchpad. It can run on ABAP, SAP Business Technology Platform, or SAP Enterprise Portal. ABAP is recommended for on-premise usage while SAP BTP is recommended for cloud deployments. The document provides a comparison of features and capabilities of each option.

Uploaded by

saurabh.rai83
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

SAP Fiori launchpad

Deployment options and recommendations:


ABAP and SAP Launchpad service

March 2021
TABLE OF CONTENTS
INTRODUCTION ................................................................................................................................................ 3
OVERVIEW OF DEPLOYMENT AND CONSUMPTION OPTIONS .................................................................. 3
SAP Fiori launchpad on ABAP ........................................................................................................................ 4
SAP Fiori launchpad on SAP Business Technology Platform..................................................................... 4
SAP Fiori launchpad on SAP Enterprise Portal ............................................................................................ 5
DETAILED COMPARISON ................................................................................................................................ 6
Content Consumption ...................................................................................................................................... 6
Features and Functions ................................................................................................................................... 7
Platform and Additional Information .............................................................................................................. 8
RECOMMENDATIONS FOR CUSTOMERS ..................................................................................................... 9
ADDITIONAL RESOURCES ............................................................................................................................10

2
INTRODUCTION
SAP Fiori launchpad is a role-based entry point to business applications that provides additional services like
navigation, embedded help, notifications, and personalization. It is designed according to the intuitive and
coherent SAP Fiori user experience and runs on multiple devices (desktop, tablet, smartphone) using an
adaptive design paradigm.
The launchpad enables the business user to easily
access applications based on modern SAP Fiori /
SAPUI5 technology as well as established UI
technologies such as SAP GUI for HTML or Web
Dynpro ABAP.
For more information on user experience and design
aspects of SAP Fiori launchpad, see SAP Fiori
Launchpad - Overview

With the SAP Fiori 3 design system, SAP is applying


a common shell bar and the spaces and pages
concept across SAP solutions.

OVERVIEW OF DEPLOYMENT AND CONSUMPTION OPTIONS


SAP Fiori launchpad is based on modern web technologies and can be consumed via web browser or SAP
Business Client.
While the end user experience and capabilities are well aligned across different platforms, the design-time
environment is platform-specific. SAP Fiori launchpad (FLP) is available on the following main platforms:
- SAP Fiori front-end server (ABAP)
- SAP Business Technology Platform
- SAP Enterprise Portal (Java).
The content administrator uses different tools to set up, configure and manage the launchpad and its content
(such as tiles, catalogs, groups, spaces, pages, and roles):
- SAP Fiori front-end server: SAP Fiori launchpad content manager, SAP Fiori launchpad application
manager, SAP Fiori launchpad designer, Manage Launchpad Spaces and Manage Launchpad Pages
apps, and PFCG
- SAP Launchpad service (SAP BTP): Provider Manager / Content Manager / Site Manager (multi-cloud
environment) and SAP Fiori Configuration Cockpit (Neo environment)
- SAP Enterprise Portal: Portal Content Directory
SAP is enhancing the SAP Launchpad service to act as central entry point by integrating and consuming
apps from multiple SAP systems (cloud and on-premise). More detailed information is available in the SAP
Fiori Deployment Options and System Landscape Recommendations guide.

3
For recommendations regarding landscape setup read SAP Fiori Deployment Options & Recommendations

SAP Fiori launchpad on ABAP


SAP Fiori launchpad running on SAP Fiori front-end server or SAP Fiori front-end server for SAP S/4HANA
(FES)1 natively aggregates transactional, factsheet and analytical SAP Fiori applications with established UI
technologies (e.g. Web Dynpro ABAP, SAP GUI). It leverages existing users, authorization management and
role configuration in the ABAP environment.
In addition, SAP Fiori launchpad runs on ABAP Platform as part of SAP S/4HANA Cloud. To simplify
configuration and setup significantly in the cloud environment, administrator flexibility and capabilities are
reduced here.

SAP Fiori launchpad on ABAP can be consumed via web browser on all devices. The consumption of SAP
Fiori launchpad via SAP Business Client (SAP BC) is a recommended setup to combine SAP Fiori apps with
native SAP GUI transactions and Web Dynpro ABAP applications in a Windows desktop environment.

SAP Fiori launchpad on SAP Business Technology Platform


To create cloud-based launchpad sites content administrators work with SAP Launchpad service (new
projects) or SAP Cloud Portal service (for licensed customers). Both services provide the required tools to
manage and configure the launchpad (e.g. catalogs, groups, roles), translation, user management, branding,
and more. The launchpad can run as a full cloud solution or in a hybrid scenario, consuming business data
and applications from on-premise SAP systems2 and/or cloud solutions.
SAP Launchpad service on SAP BTP (Cloud Foundry runtime) is available in data centers of selected hyper-
scalers (multi-cloud / Cloud Foundry environment) like Amazon Web Services, Microsoft Azure, Google Cloud
Platform, and Alibaba Cloud. The SAP Launchpad service offers enhanced app integration capabilities to
contribute to SAP’s central entry point vision. This central launchpad leverages advanced integration
capabilities to act as UX integrator to various SAP and non-SAP solutions (on-premise and cloud) and across
multiple SAP S/4HANA systems. Furthermore, SAP has integrated central services such as Inbox/Task Center
and the SAP Workflow service into the Launchpad. Further integrations like Notifications, or Enterprise Search

1 See SAP Community Blog: SAP Fiori front-end server strategy


2 Check the SAP Fiori Apps reference library for apps and releases

4
are planned. To ensure a harmonized user experience across all products, SAP establishes a common SAP
Fiori look and feel, and UX integration guidelines.

For further information on planned enhancements, please refer to the relevant product road maps on SAP
Road Map Explorer: https://roadmaps.sap.com.

SAP Fiori launchpad on SAP Enterprise Portal


SAP Enterprise Portal (EP) is a widely adopted on-premise solution based on SAP NetWeaver Java platform.
Please note that the latest SAP Fiori 3 enhancements are not planned to be made available for SAP Enterprise
Portal. Furthermore, the product is in maintenance mode with planned end of mainstream maintenance of SAP
NetWeaver Java 7.5 on December 31, 2027.
Therefore, SAP Enterprise Portal is not recommended as platform for new SAP Fiori launchpad
implementation projects. For existing SAP EP installations, the Fiori framework page might be an intermediate
step to adopt the basic SAP Fiori design guidelines. The Fiori framework page is also recommended for
consuming SAP Enterprise Portal on mobile devices.

See also SAP Fiori on SAP Enterprise Portal - All you need to know on One Page (November 2019)

5
DETAILED COMPARISON
The following table describes major differences and points for consideration when evaluating the different
deployment options. It focuses on SAP Fiori front-end server and the SAP Launchpad service on SAP BTP
as main options for implementation projects.

Content Consumption
SAP Fiori front-end server SAP BTP
(ABAP) (Cloud Foundry)
Supported standard All SAP Fiori apps (on-premise) Federation of SAP Fiori apps from SAP
SAP Fiori Apps3 S/4HANA (as of SAP Fiori front-end server
Transactional apps, analytical apps as well 2020)
as factsheets and SAP Fiori Elements (object
page, overview page...) Manual integration of applications from
- SAP Business Suite
- SAP S/4HANA
- SAP S/4HANA Cloud

Tasks and Workflow My Inbox app and ABAP workflow My Inbox app, SAP Task Center service and
SAP Workflow service

Supported UI  SAPUI5 apps  SAPUI5 apps


Technologies  Web Dynpro ABAP  Web Dynpro ABAP
 SAP GUI for HTML  SAP GUI for HTML
 SAPUI5/HTML5 apps on SAP BTP (beta)  SAPUI5 / HTML5 apps on SAP BTP
 CRM Web Client UI  CRM Web Client UI
 SAP Screen Personas  SAP Screen Personas
 SAP Smart Business apps  URL
 Factsheets
 URL SAP Smart Business apps only as federated
content from SAP S/4HANA
SAP GUI for Windows in combination with
SAP Business Client SAP GUI for Windows in combination with
SAP Business Client

Consume custom ABAP deployment Managed SAPUI5/HTML5 apps on SAP


SAPUI5 apps Integration of extension apps on SAP BTP BTP, integration of custom apps running on
(Cloud Foundry) available as beta (not for ABAP
productive use)

Enrichment with News Tile,


Web Content Integration of SAP Jam

Browser Support Check SAPUI5 browser and platform support

3 Available SAP Fiori apps see SAP Fiori Apps Reference Library

6
Features and Functions

SAP Fiori front-end server SAP BTP


(ABAP) (Cloud Foundry)
SAP Fiori 3 Yes Yes
Design/Theme

Spaces and pages Yes Only as federated content from SAP S/4HANA
Local spaces and pages planned

Tile types Static, dynamic and custom tiles Static, dynamic and custom tiles
Links available in home page mode, planned Links planned
in spaces and pages mode
Tile size options: Responsive and Small
(selectable per site)

Notifications Yes Planned

SAP CoPilot / Yes, running on SAP BTP Planned


Conversational AI

Personalization
Supported persistency: ABAP Supported persistency: SAP BTP

Search SAP Enterprise Search across all content Search for applications
levels Planned: integration with search service

Authentication Certificates, SAML, Basic SAP Identity Authentication service, SAML2,


Basic, oAuth

Mobile Support Yes Yes

Theming/Branding UI theme designer UI theme designer

Shell Extensibility4 Via shell plug-ins and SAP Fiori launchpad Via shell plug-ins
APIs

Design Time Tool SAP Fiori launchpad content manager, SAP Site Manager incl. Provider Manager, Content
for FLP content Fiori launchpad application manager, Fiori Manager and Site Editor
launchpad designer (FLPD), SAP Fiori apps
Manage Launchpad Spaces and Manage
Launchpad Pages

SAP Fiori launchpad Configuration parameters in SAP Fiori Site settings


(shell) settings Customizing or via target mapping for role-
specific assignments

User defaults Yes Consumption of user defaults from SAP


S/4HANA systems planned

4 See SAP Help: Extending the Launchpad (ABAP)

7
About dialog Yes (providing detailed support information Yes (providing detailed support information like
like application and component IDs, versions application and component IDs, versions of
of application and framework etc.) application and framework etc.)

User Assistance Yes, Web Assistant by SAP Enable Now Web Assistant integration planned
integrated

SAP Fiori launchpad One launchpad instance per SAP Fiori front- Multiple launchpad sites possible
instances end server

Roles Repository PFCG | ABAP DB - Local roles on SAP BTP


- Remote role consumption from backend
systems via content federation
- Integration with SAP Identity Provisioning
Service/SAP Cloud Identity Access
Governance for advanced role management
and assignments

Platform and Additional Information

SAP Fiori front-end server SAP BTP


(ABAP) (Cloud Foundry)
Platform Technology ABAP Cloud

Deployment On-premise / Cloud5 Cloud

Release On-premise: SAP NetWeaver AS ABAP Cloud service with monthly releases
with quarterly support packages and
annual release
SAP S/4HANA Cloud: quarterly releases

Central Note SAP Note 2065235

Documentation Link Link

Software Licenses Included in SAP NetWeaver license Consumption based pricing or monthly
subscription for SAP BTP account and
relevant services
Licensing options

5 Using SAP HANA Enterprise Cloud

8
RECOMMENDATIONS FOR CUSTOMERS

For accessing content from single SAP S/4HANA system SAP recommends embedded deployment for SAP
Fiori launchpad, means SAP Fiori front-end server is co-deployed with your SAP S/4HANA and SAP S/4HANA
Cloud instance.

For SAP Business Suite landscapes, it is possible to set up the front-end server as dedicated box (hub
deployment) to access SAP Fiori apps and content from one or more SAP Business Suite systems. You can
learn more in the official SAP Fiori Deployment Options and Recommendations.

In addition, you can establish a central SAP Fiori launchpad using the SAP Launchpad or SAP Cloud Portal
service running on SAP BTP for accessing standard applications side-by-side custom apps deployed on SAP
BTP. The content can be consumed remotely from connects backend systems, providing central access to
SAP, custom-build and third-party applications and extensions.

The following table shows typical use cases for each of the SAP Fiori launchpad deployment options:

ABAP Platform
SAP Fiori front-end server SAP BTP
(SAP S/4HANA
(ABAP) (Cloud Foundry)
Cloud)
 SAP S/4HANA and SAP Business Suite  SAP S/4HANA Cloud  Customers developing and running their
customers customers custom applications deployed on SAP BTP
 SAP S/4HANA customers building cloud  Customers looking for a central launchpad
extensions solution to bring together applications from
 Customers who would like to have the option multiple backend systems
to implement all kind of SAP Fiori apps (on-  Integration scenarios across companies in
premise) an external-facing scenario
 ABAP-centric on-premise scenarios bringing  Customers following SAP’s strategic
together Fiori apps with established UI direction to the cloud
technologies

9
ADDITIONAL RESOURCES
- SAP Fiori Apps Reference Library
- SAP Fiori roadmap
- SAP Transformation Navigator
- SAP Fiori Deployment Options and System Recommendations

SAP Launchpad service


- SAP Business Technology Platform: overview and documentation
- SAP Launchpad service overview
- SAP BTP Trial account
- Community
- Documentation
- Limitations

SAP Cloud Portal service


- Community
- Documentation

SAP NetWeaver ABAP


- Documentation
- SAP Fiori launchpad on SAP NetWeaver ABAP
- SAP Fiori launchpad documentation
- SAP Fiori launchpad for SAP S/4HANA Cloud documentation
- SAP Fiori implementation information
- SAP Note 2262813

SAP Enterprise Portal on SAP NetWeaver


- Documentation
- Community
- SAP Fiori launchpad on Enterprise Portal Overview
- SAP Fiori Integration with SAP Enterprise Portal (SAP Note 2031108)
- Maintenance: SAP Note 1648480 - Maintenance for SAP Business Suite 7 Software

10
www.sap.com/contactsap
© 2021 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 document 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 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. See www.sap.com/copyright for additional trademark information and notices.

You might also like