SAP CLOUD PLATFORM | EXTERNAL

Blueprint
Modernize the Employee User Experience
with SAP Fiori Cloud
© 20xx SAP SE or an SAP affiliate company. All rights reserved.

1
Table of Contents
Table of Contents ......................................................................................................................................................... 2

OVERVIEW .................................................................................................................................................................... 3
Project Phases .................................................................................................................................................................3

IDEATION PHASE .........................................................................................................................................................4

Business Scenario ...........................................................................................................................................................4
Solution ............................................................................................................................................................................4
Value Proposition ............................................................................................................................................................5
Reference Solution Diagram ..........................................................................................................................................5
Reference Solution Components ...................................................................................................................................6
SAP Cloud Platform Components for Licensing Considerations .............................................................................................. 6
Other Components Required in this Use Case ............................................................................................................................ 7
Recommendations for Consideration ...........................................................................................................................8
References .......................................................................................................................................................................9

PLANNING PHASE ...................................................................................................................................................... 11

Back-end .........................................................................................................................................................................11
SAP Fiori App Selection .................................................................................................................................................11
SAP Gateway Consumption Options ........................................................................................................................... 12
Access Point Options .................................................................................................................................................... 13
Security .......................................................................................................................................................................... 13

IMPLEMENTATION PHASE ........................................................................................................................................ 16

Back-End System Setup & Configuration ................................................................................................................... 16
SAP Cloud Platform Account Setup ............................................................................................................................ 16
Administration ............................................................................................................................................................... 17
Theming ......................................................................................................................................................................... 18
Optional Development .................................................................................................................................................. 19

OPERATION PHASE ................................................................................................................................................... 21

Lifecycle Management .................................................................................................................................................. 21
Continuous Integration for SAPUI5 Applications ...................................................................................................... 22
Monitoring ..................................................................................................................................................................... 22
Troubleshooting ........................................................................................................................................................... 23

SUMMARY ................................................................................................................................................................. 26
Follow SAP .................................................................................................................................................................... 26

2
OVERVIEW
Digital user experience (UX) services delivered on SAP Cloud Platform bring together strong UX,
mobile collaboration and portal expertise to optimize business processes. Design and Build rich
mobile, web, portal and collaboration apps to optimize digital experience. Services include build,
SAP Cloud Platform Portal and SAP Fiori cloud apps, dev tools like SAP Web IDE and SAP mobile
services for development and operations, and more. This blueprint provides co mmon
information, guidance, and direction to be used during the Ideation, Planning, Implementation,
and Operation phases of SAP Fiori Cloud apps to increase employee productivity and satisfaction
by modernizing the user experience.

Project Phases

To modernize the employee user experience with the SAP Fiori Cloud solution, the steps outlined
below will be described in detail in this blueprint. Note that the information and guidance in this
blueprint is intended to be complementary to the existing information already available, and not
in replacement of it.

IDEATION Discover an SAP 1. Understand business value

solution that
Target Roles: 2. Visualize solution
overcomes a specific
• Line of Business
business challenge 3. Estimate investment
• Leaders/Users

1. Landscape setup
PLANNING Make technical 2. How does SAP Fiori Cloud fit to your
decisions in terms of existing setup
Target Roles: landscape and
• Enterprise architects 3. Landscape deployment options
deployment options
• Project leads
4. Security considerations

1. Back-end system setup

IMPLEMENTATION
2. SAP Cloud Platform account setup
Act, and start
Target Roles: completing the steps 3. Security configuration
• Developers necessary to go-live
• Administrators 4. App development
• Technical consultants
5. Administrative work

OPERATION Understand, what is

1. Lifecycle management
required to run the
Target Roles: solution, and, where 2. Troubleshooting
• Technical consultants relevant the tools
3. Monitoring
• Administrators provided by SAP

3
IDEATION PHASE

Business Scenario
Companies are embracing digital transformation and
creating strategies to adapt to the digital age. Leading the
way for digital transformation is a delightful user experience.
Companies understand now more than ever how important a
simple and intuitive user experience is for increasing
productivity, staying competitive, and fostering employee
satisfaction. SAP is offering the tools to streamline a
company’s journey towards digital transformation.

Solution
Regardless of industry, an intuitive user experience has
quickly become standard. Below is a table detailing examples
of different employee roles and the types of commonly-used
SAP Fiori Cloud apps to streamline productivity. Note that
this is a subset of the available SAP Fiori cloud apps, for a full
list please visit the SAP Fiori apps reference library.

Employee Tasks
Field Sales Various CRM apps to complete tasks in the field
Representative including My Accounts, My Leads, My
Opportunities, My Tasks and Customer Invoices
HR Manager Approve Leave Requests, Approve Timesheets,
My Inbox
Asset Accountant* Asset Balance, Asset History Sheet, Asset
Manager Worklist
Purchaser Approve Purchase Contracts, Approve Purchase
Orders, Track Purchase Order
Employee HR Info Employee Lookup, My Benefits, My Leave
Requests, My Paystubs, My Team Calendar, My
Time Events, My Timesheet, and People Profile
Employee Master Request Cost Center, Request Customer
Data Request* Change, Request Material, Request Profit
Center, Request Supplier, Track My Requests
*only available with SAP S/4HANA back-end system

4
Value Proposition
SAP Fiori Cloud provides SAP S/4HANA and SAP Business Suite customers a simple approach to
adopt the SAP Fiori user experience by leveraging pre-packaged content and services in the cloud,
while keeping business data on-premise. By doing this, SAP offers customers the opportunity to
save money while simplifying how they operate their daily business. Past customer success has
shown us*:

An Increase in Productivity by 20-50%

An Increase in Solution Adoption by 20-70%
Reduced Training Costs by 30-80%
A decrease in Support Costs by 30-80%
A Reduction in change requests by 30-60%

*SAP Design Services, Value of Design (https://experience.sap.com/designservices/value)

SAP User Experience Value calculator tool (http://www.sapcampaigns.de/us/UX_Calculator/)

Reference Solution Diagram

The SAP Fiori (user experience) is SAP’s modern design language for enterprise applications. SAP
Fiori in the Cloud is a scenario where you can develop and run SAP Fiori or custom SAPUI5 apps on
the SAP Cloud Platform. SAP Fiori Cloud is a hybrid solution consisting of SAP Fiori apps and
content for SAP S/4HANA & SAP Business Suite, plus selected SAP Cloud Platform services and
resources to develop, extend, and run the SAP Fiori user experience in the cloud.
In this blueprint, we focus on SAP Fiori Cloud, in which the frontend UI components are run and
maintained by SAP in the SAP Cloud Platform on a subscription basis. To run SAP Fiori Cloud,
customers should already have either a back-end SAP S/4HANA or SAP Business Suite system
with the respective SAP Gateway components installed. The back-end system is the primary data
source where the business processes are defined and transactional data is stored daily.
The following diagram of the solution illustrates a combined architectural pattern of the runtime
and design-time environments for implementing SAP Fiori Cloud with an on-premise SAP
S/4HANA or SAP Business Suite system.

5
This blueprint assumes you already have either a back-end SAP S/4HANA or an SAP Business Suite system installed and configured
with the appropriate SAP Gateway version.
* OData services via SAP Cloud Platform OData provisioning or SAP Gateway (see details about deployment options in SAP Enterprise
Architecture Explorer (#11115) and in SAP Note 1830712)

Reference Solution Components

SAP Cloud Platform Components for Licensing Considerations

Please note that the following Bill of Material is for reference purposes only. The following table is
only an example of the SAP Cloud Platform services and components required for this use case.
Please consult your SAP Account Executive regarding your specific licensing needs.

SALES ITEM FUNCTION LICENSING METRICS EXAMPLE

SAP Fiori Cloud Standard This base license includes SAP Per 100 named 100 users
Package Fiori content and apps, SAP users/month
Web IDE, OData Provisioning,
UI Theme Designer, Cloud
Connector and more
Additional Standard User A named user accessing SAP Named users 1900 users
Fiori apps

Use the SAP Cloud Platform pricing estimator to calculate the required investment.
Scale up or down as required.

Customers can use the SAP Cloud Platform pricing estimator to calculate the required investment
for a particular project. Scale up or down on services as required.

6
Members and partners of SAP PartnerEdge 1 can evaluate the development of an application for this
use case – most development licensing is covered by the packs offered by SAP’s partner licensing
services. Click here for details.
A license for SAP Fiori Cloud provides customers with both the required and the optional services
as a package. Each package comes with a defined number of users per service and customers have
the option to increase that number based on business requirements. For details on the packages
offered for SAP Fiori Cloud, please visit the SAP Fiori Cloud Packages page.

Other Components Required in this Use Case

COMPONENTS FUNCTION

Subscription and corresponding content for SAP Business Suite

SAP Fiori Apps and SAP S/4HANA back-end systems. Automated updates and
maintenance activities are included in the subscription.

SAP Cloud Platform Allows to create and publish freestyle and SAP Fiori launchpad
Portal style business sites.

SAP Cloud Platform Enables you to use SAP Gateway OData Services to extract data
OData Provisioning from SAP Business Suite systems so this data can be consumed
service freely in the cloud.

To establish connections between cloud applications and on -

Cloud Connector
premise systems.

To securely access remote services that run on the internet or on -

Connectivity
premise.

Identity Provides a tenant to secure authentication and single sign-on for

Authentication users in the cloud.

SAP Fiori launchpad

A tool used by administrators to create new and maintain existing
configuration cockpit
content for SAP Fiori launchpad sites.
(FCC)

To apply your corporate branding to applications based on SAPUI5

UI Theme Designer
technology.

SAP Web IDE To create and extend applications for browser and mobile devices.

SAP Build To create interactive prototypes without writing any code.

1
Excluding open ecosystem basic

7
Recommendations for Consideration
SAP Customers who have purchased and successfully implemented SAP Fiori Cloud have also
purchased additional users for included services and/or additional services to enhance their user
experience journey. Note that this is a subset of recommendations; for a comprehensive list please
contact an SAP Sales Associate.

• SAP Fiori Cloud, Enterprise Edition: includes all resources of SAP Fiori Cloud, plus SAP Cloud
Platform, Mobile Services for Development & Operations, a service designed to support the
creation and operation of enterprise mobile apps. You also receive additional SAP Cloud
Platform Build users.
• SAP API Management: provides one experience for managing and monitoring all APIs across
various data platforms and is enriched with real-time analytics. It enables consumers to
access relevant data directly in a secure manner. Selective data can be exposed while
reducing the risk of security breaches. Rather than app developers consuming services
directly, they access APIs created using SAP Cloud Platform API Management handling the
security and authorizations required to protect, analyze, and monitor your services.
• SAP Documents Center: to provide access to documents and unstructured content in your
launchpad you can add the SAP Documents center and easily integrate it into the launchpad.
• Launchpad/portal Visits: additional standard users are available for purchase per user
• Launchpad/portal Admins: the base package includes # admin users. Should you require
more than # admins you may purchase additional licenses.
• SAP Fiori Client: a native mobile application that easily consumes SAP Fiori-based
applications like the SAP Fiori launchpad. It provides additional supportability features, SAP
Fiori- specific caching, access to device features, an integrated attachment viewer, and a
better user experience than a mobile browser for this specific use case. Available as a free
download from the public app stores for iOS, Android, and Windows devices.

The diagram below depicts at a high level how Mobile Services for Development & Operations and
SAP API Management could fit into an overall SAP Cloud Platform solution.

8
References
SAP has deep knowledge and expertise in developing solutions that help businesses organize and
run their enterprise in the most efficient way possible. For a long time, the back-end expertise
rooted in SAP’s DNA took center stage and it was often commented about how little attention was
paid to user experience. With the quick emergence of mobile devices around 2010 and the world
suddenly demanding simple delivery and consumption of all information, SAP quickly reprioritized
and made UX a focus by developing and releasing SAP Fiori as the user experience for SAP
software. Since the release in 2013, SAP Fiori has been recognized and awarded the prestigious
Red Dot award for the SAP Fiori design concept. With 76% of the world’s transactions touching an
SAP system, customers quickly turned to SAP for best practices on how they could adopt the new
user experience to their business. Since its release to the on-premise world in 2013 and up to the
most recent cloud version offering a hybrid model with the SAP Cloud Platform , customers have
been adopting and sharing their success with the ecosystem.

Below you’ll find a small subset of SAP Fiori Cloud customer success stories, highlighting the
implementation time from idea to go live and the top benefit received. The BTS link listed under
each customer’s name will take you to the full Business Transformation Study for you to read and
learn more details. For a full list of references please visit the SAP Cloud Platform Success Stories
Site.

CUSTOMER INDUSTRY TOP BENEFIT

Ruralco Retail 2 hours to perform stocktaking down from >1 day
Sika Corporation Chemicals >80% of all US pricing offers directly validated through
accounting using SAP Fiori Cloud apps.
Convergent IS Professional 1-step login to comprehensive expense dashboards.
Services

9
More Information about the Ideation Phase:
• SAP Fiori Cloud Demo: https://www.sapfioritrial.com/
• SAP Fiori apps reference library
• SAP Design Services – Value of Design
• SAP User Experience Value Calculator
• SAP Enterprise Architecture Explorer (#11115)
• SAP Note 1830712
• SAP Cloud Platform Official terms and agreement
• SAP Fiori Cloud | Pricing Estimator
• SAP Fiori Cloud Packages page
• SAP Cloud Platform Success Stories

10
PLANNING PHASE
SAP Fiori is the user experience for SAP solutions and
therefore fits nicely to your existing SAP setup. However,
before implementing SAP Fiori Cloud, there are some
landscape decisions that need to be made on the back-end
landscape and subsequently which specific SAP Fiori Cloud
apps you want to implement.

Back-end
What back-end SAP system is your business currently
running? Is it an SAP S/4HANA system or an SAP Business
Suite back-end? It is imperative that you know this
information up front as there are certain SAP Fiori Cloud apps
created for each respective system. Additionally, depending
on the version of your back-end, there may be additional
upgrade steps to ensure validity when you move to the
implementation phase.

SAP Fiori App Selection

Based on your company’s business requirements and
corresponding back-end system, a decision of which specific
SAP Fiori apps to implement is the second decision in the
planning phase. A license to SAP Fiori Cloud provides you
access to all included SAP Fiori Cloud apps. However, each
app has its own set of prerequisites and corresponding
implementation steps to consider. The SAP Fiori Apps
Reference Library details all the SAP Fiori apps and has built-
in filters specific to SAP Fiori Cloud and back-end systems.

• SAP Fiori Cloud for SAP Business Suite

• SAP Fiori Cloud for SAP S/4HANA (version
dependent)
Whatever app(s) you decide to implement, you should
aggregate the data in the apps reference library so that when
you enter the implementation phase you have all the required
information. You will need to note for each app(s) the
important SAP notes, the back-end software component
version, the back-end authorization role, and the OData
service and corresponding version.

At this point in the planning phase, you could determine that

11
none of the out-of-the-box SAP Fiori Cloud apps fit all your business needs. In that case, SAP has a
few suggestions. Start by reaching out to the SAP Account team to inquire if your scenario is
already included in a future roadmap. If there are no future plans for your scenario, then you could
submit your use case for consideration to be added to the standard offering. In the meantime, you
could decide to design and develop a custom SAPUI5 Fiori like app. For more information on a
custom app scenario reference the Build a Custom SAP Fiori-like App for SAP S/4HANA blueprint.
Additionally, it is technically possible for you to manually deploy an SAP Fiori app to your SAP Cloud
Platform account. For more information please reference ‘Deploy transactional SAP Fiori Apps for
SAP Business Suite to SAP Cloud Platform blog*.

*Deploying transactional apps to SAP Cloud Platform is treated as custom development and therefore
maintenance and issues are not supported by SAP.

SAP Gateway Consumption Options

Depending on your back-end system setup and your SAP NetWeaver release, there are several
deployment options for SAP Gateway that are either already in use or can be setup for use with SAP
Fiori Cloud. Below is a high-level overview of the options and SAP’s recommendation based on your
back-end system.

• SAP Gateway Hub Deployment (central hub for SAP S/4HANA & SAP Business Suite
scenarios): service implementation and registration takes place in the back-end system and
the services are activated on the SAP Gateway server. The back-end system either needs
the IW_BEP add-on or has it pre-installed with SAP NW 7.40 version or higher with
component SAP_GWFND.
• SAP Gateway Embedded Deployment (SAP S/4HANA focus): OData services are developed,
registered, and published in the back-end system. In case of multiple back-end systems, this
needs to be done for each one.
• OData Provisioning (SAP Business Suite focus): service implementation is done on the back -
end system but the components that used to be in the SAP Gateway hub are now running in
SAP Cloud Platform through the OData Provisioning service. OData services and SAP Fiori
apps are securely connected to the back-end SAP Business Suite via the cloud connector.

12
For more information on the SAP Gateway deployment options please refer to SAP Gateway deployment options in a nutshell blog.

Access Point Options

SAP Fiori Cloud supports both internal and external access point scenarios. As pa rt of the planning
phase, you need to decide which option better complies with the company standards of your
business.
• Internal access point: prevents sensitive OData requests to the back-end system from being
routed through the cloud. Data stays within the customer’s network, whereas all UI
applications/components stay in the SAP Cloud Platform. [Implementation Quick Guide]
• External access point: exposes business data for the SAP Fiori apps to the Internet. OData
is provisioned on the SAP Cloud Platform directly from back-end systems and all front-end
server components are deployed on the SAP Cloud Platform. [Implementation Quick Guide]
The implementation steps for both scenarios are similar but deciding which scenario to use at this
phase will help you to better prepare the required resources for the implementation phase.

Security
Security can be broken up into three topics:
1. Authentication – proving users are who they say they are.
2. Authorization – providing permissions to the user
3. Single Sign-On (SSO) – allowing the user to use one set of credentials to access multiple
applications.
The diagram below depicts at a high level where the Authentication, Authorization and Identity
Propagation topics fit in an overall SAP Cloud Platform solution.

13
When implementing the solution just described, keep in mind that each of the three security topics
described above have several options for how they are implemented with the SAP Cloud Platform.
For the SAP Fiori Cloud solution, the following deployment methods are practical options:
• Authentication: SAP Cloud Platform Identity Authentication Service will allow you to use
a common source of identities for all your cloud-based application. It provides a
standard, internationally adopted method for authentication using SAML assertions. For
More information, visit SAP Cloud Platform Identity Authentication service | SAP Cloud
Platform Blueprint
• Authorization: SAP Cloud Platform offers possibilities to manage the authorizations of
users authenticated by an identity provider. Authorization is based on a role -based
authorizations concept. The role-based authorization allows administrators to easily
manage user access, and permissions for services on the platform and for applications
deployed on the platform. For more information, visit Authorization | SAP Cloud Platform
Blueprint
• Single Sign-On: Principal propagation with an X.509 certificate can be implemented from
SAP Cloud Platform to the backend system that is running on-premise. It allows the
consumer to use this method for any endpoint service that accepts X.509 certificate -
based authentication. For more information, visit Principal Propagation | SAP Cloud
Platform Blueprint

14
More Information about the Planning Phase:
– The SAP Fiori Apps Reference Library
– Deploy Transactional SAP Fiori Apps for SAP Business Suite to SAP Cloud Platform blog
– SAP Gateway deployment options in a nutshell blog
– Implementation Quick Guide – Internal Access Point
– Implementation Quick Guide – External Access Point
– SAP Cloud Platform Identity Service Blueprint
– Authorization Blueprint
– Principal Propagation Blueprint

15
IMPLEMENTATION PHASE

Back-End System Setup & Configuration

1 In the planning phase, an app consultant would typically work with business
leaders to understand business challenges and decide which SAP Fiori Cloud
apps can best mitigate those challenges. The app consultant would aggregate
the specific SAP Fiori Cloud app information from the SAP Fiori Apps reference
library and would share it with the system admin who can then get to work on
the following development tasks:

1. Verify the back-end system meets the minimum requirements specified

for the apps
2. Install the back-end software component
3. Install the OData component
– If you selected the SAP Gateway Hub consumption option in the
planning phase, then you will have additional configuration tasks
here to connect your SAP Gateway and back-end system,
including creating RFC connections, creating trust connections,
and importing certificates. For more information see the SAP
Gateway configuration guide.
4. Register the OData service in the back-end system
5. Assign back-end authorization role
6. Test back-end scenarios to ensure data is coming through. Doing this
step now will significantly reduce potential troubleshooting time later.

Please refer to the SAP Fiori Cloud Landscape Configuration Guide for SAP
Business Suite or SAP S/4HANA.

SAP Cloud Platform Account Setup

2 If SAP Fiori Cloud is your company’s first SAP Cloud Platform project, then a
system admin will need to spend time setting up the platform and onboarding
your company. Tasks include, but are not limited to, setting up subaccounts to
match your landscape in the back-end system, typically dev, test, prod
accounts, adding at least 2 additional administrators and assigning other roles
to members in your organization. For more information on the specifics for
onboarding and getting started with your SAP Cloud Platform account please

16
 reference the SAP Cloud Platform Planning Guide.

For an SAP Fiori Cloud project, a system admin would need to complete the
following tasks in the SAP Cloud platform:
1. Set up SAP Cloud Platform cloud connector (if implementing the external
access point option). You would need to install and then setup the cloud
connector to establish a secure tunnel between the SAP Cloud Platform
and the on-premise back-end system. Download the Cloud Connector
2. Configure trust in the SAP Cloud Platform cloud connector Set up Trust
3. Configure initial security depending on what options you selected in the
planning phase.
4. Setup destinations to the back-end system using the destinations section
in the SAP Cloud Platform
– If you are using the OData Provisioning SAP Gateway consumption
option, you would need to create a destination to the back-end
system within the OData Provisioning service and a destination to
the OData Provisioning service in the destinations section of your
SAP Cloud Platform account. OData Provisioning | Manage
Destinations
5. Activate subscriptions and content for SAP Fiori Cloud by navigating to
the SAP Cloud Platform Portal, which with a license comes activated for
you by default. Within the SAP Cloud Platform Portal, you’ll need to create
an SAP Fiori launchpad site. Going into the site to configure the apps and
content will navigate you to the SAP Fiori launchpad configuration cockpit.
You will be greeted with a popup asking you to select your back-end
system, either SAP Business Suite or SAP S/4HANA. Selecting the
appropriate back-end system for your business will automatically add the
relevant SAP Fiori apps and content to the SAP Cloud Platform as
subscribed HTML5 applications and in the SAP Fiori launchpad
configuration cockpit for you to further group and categorize.
– Note, you will need to do this step for every subaccount you create
and intend to use with SAP Fiori Cloud.

Administration

3 Before end users can work in the SAP Fiori launchpad, administrators need to
first set it up by configuring content such as app tiles, groups, catalogs, and
roles. By default, SAP provides you with “SAP” content to get you started,
including a catalog, a group and a role. You are not required to use any of these
defaults, but note that they cannot be deleted. When SAP updates content, the
content in your launchpad configuration cockpit is automatically updated and
the administrator will receive a notification asking to publish these updates.

17
 An administrator would take care of the following tasks in the SAP Fiori
launchpad configuration cockpit:
1. Configure site settings, including the name of your launchpad, a site
alias, defining the SAPUI5 version (either the innovation version,
(default), updated per SAPUI5 release, or the maintenance version
that uses the same SAPUI5 release for a predefined period, and
enabling or disabling user capabilities such as user personalization,
theme selection, search, etc.
2. All the apps that correspond to your chosen back-end SAP system are
available to you in the SAP Fiori launchpad configuration cockpit
under Content Management > Apps. From there you have the option
to add apps and administrators can customize the tile to their needs.
3. Catalogs are authorization objects to which both roles and apps are
assigned. Administrators can create new catalogs to organize SAP
Fiori apps per their business needs.
4. Administrators can create groups to ensure related apps are
organized and visible to users in the SAP Fiori launchpad. Only
members who are assigned to the group will see those apps in their
launchpad.
5. Set up authorization flow by means of users, roles, and user groups
which you assign to application roles and catalogs. You define
business roles and groups to assign users to in the SAP Cloud
Platform Portal > Configure Portal Service Roles. The
TENANT_ADMIN role is a predefined administrator role that you can
assign to additional administrators so they can have access to the SAP
Fiori launchpad configuration cockpit. In the SAP Fiori launchpad
configuration cockpit you would assign subscribed SAP Fiori Cloud
apps to roles and then add those apps to groups and catalogs that you
would then assign to end users. For more information, see SAP Help |
About Roles.

Theming

4 SAP provides you with a preconfigured launchpad using the Blue Crystal theme
designed and widely used by SAP. In most cases, you would want to apply your
own corporate branding to your launchpad and/or SAP Fiori apps. Your license
for SAP Fiori Cloud includes the UI theme designer, SAP’s browser-based tool
for cross theming scenarios. Using UI theme designer, you can easily and
intuitively apply your own corporate brand by customizing one of the templates
provided by SAP.
An administrator would take care of the following tasks in the SAP Cloud
Platform:

18
 1. Create and assign the UI theme designer role to the person(s)
responsible for creating the corporate theming
2. Access UI theme designer through the service under the User Experience
category in the SAP Cloud Platform cockpit

Theming SAP Fiori Apps and SAP Fiori launchpad

UI Theme Designer

Optional Development

5 For an out of the box SAP Fiori Cloud implementation, additional development
is not required. However, a customer may decide in the planning phase that all
business needs are not met with the available SAP Fiori Cloud apps. In that
case, as mentioned, a customer could choose to customize an existing SAP
Fiori Cloud app and/or develop their own custom SAPUI5 app. The information
in this section details the optional tools and processes included in your SAP
Fiori Cloud license for this purpose.

Extending Apps
A license for SAP Fiori Cloud provides a rich set of the most commonly -used
business processes as SAP Fiori app content. Also, included in a license for
SAP Fiori cloud is a subscription to SAP Web IDE, the powerful, web-based,
integrated development tool that simplifies end-to-end application
development. It allows you to build, debug, test, extend, and deploy apps by
using wizards, templates, samples, code, graphic modelers, and more.

SAP Web IDE offers a vast array of flexibility in terms of customizat ions for
SAP Fiori apps. Customers have the option to either adapt or enhance an
existing SAP Fiori out-of-the-box app by exposing or hiding additional
views/controllers or they can create entirely new apps designed to overcome
a specific business need by following the SAP Fiori Design guidelines.

Extending SAPUI5 Applications

Extend and Develop Apps Best Practice Guide
Build a Custom SAP Fiori-like App for SAP S/4HANA Blueprint

19
 SAP Build
SAP Build allows you to collaboratively develop prototypes with your project
team and engage end users for feedback. A license for SAP Build is included
with your SAP Fiori Cloud license and can be a valuable tool for learning design
concepts by leveraging best practice method cards, prototyping custom SAP
Fiori like apps without writing any code, and/or leveraging sample apps to
accelerate your design and development journey. For more information on SAP
Build and how you can use it to help accelerate your company’s digital
transformation strategy visit the product page.

More Information about the Implementation Phase:

• SAP Gateway configuration guide
• Landscape configuration guide for SAP Business Suite
• Landscape configuration guide for SAP S/4HANA
• Download the Cloud Connector
• Set up Trust
• OData Provisioning Manage Destinations
• SAP Help | About Roles
• Theming SAP Fiori Apps and SAP Fiori launchpad
• UI Theme Designer
• SAP Fiori Design Guidelines
• Extending SAPUI5 Applications
• Extend and Develop Apps Best Practice Guide
• SAP Cloud Platform Blueprint | Build a Custom Fiori-like App for SAP S/4HANA
• SAP build product page 20
OPERATION PHASE
In this phase, your SAP Fiori Cloud implementation is now productive and thus operations and
maintenance support are critical in ensuring success. This phase of running your application(s) is
where you need to understand topics such as lifecycle management, monitoring and what tools
SAP has available to support you.

Lifecycle Management
SAP recommends you create additional accounts for testing, quality assurance, and production so
that you have distinctive separation of data and authorizations. Ideally, this separation follows the
same separation on the backend system setup and it minimizes external exposure of productive
data. As you add additional subaccounts to your global account, it is important to note that these
new subaccounts will not be preconfigured and you’ll need to setup the SAP Cloud Platform
accordingly.

With a license for SAP Fiori Cloud you’ll receive the benefit of automatic updates to your SAP Fiori content;
Fiori apps are patched on a bi-weekly basis, the content, including roles, groups and catalog are updated in
the context of an SAP S/4HANA release (e.g. SP1, SP2 etc.) Updates include additional apps and bug
fixes and the content is applied in the SAP Cloud Platform customer account. Planned and unplanned
downtimes are announced via email & directly in the cockpit, though usually patches are achieved without
downtime (SLA for Cloud Solutions)
Two weeks prior to official delivery customers have the option to review and explore the new capabilities of
the SAP Cloud Platform Portal through the ‘Portal Preview’ option under the UX category of the SAP Cloud
Platform. The steps required for setting up the portal preview environment can be found in the SAP Help |
Preview Environment – Best Practices.

21
Below is an image detailing the subscription concept for SAP Fiori Cloud.

Continuous Integration for SAPUI5 Applications

SAP provides a best practice guide for continuous integration (CI) for development of SAP Fiori or
SAPUI5 applications running on the SAP Cloud Platform. For more information, see Part 4.5 of the
CI Best Practices Guide.

Monitoring
Administrators will want to monitor SAP Fiori Cloud apps for both performance and usage. SAP
recommends that you use a website-monitoring tool such as Google Analytics (see Tracking SAP
Cloud Portal Sites Usage Data with Google Analytics blog) or Pingdom to monitor your SAP Fiori
Cloud apps.
For an additional license, SAP Cloud Platform API Management provides one experience for
managing and monitoring all APIs across various data platforms and is enriched with real -time
analytics. This service enables consumers to access relevant data directly in a secure manner.
Selective data can be exposed while reducing the risk of security breaches. Rather than app

22
developers consuming services directly, they access APIs created using SAP Cloud Platform API
Management handling the security and authorizations required to protect, analyze, and monitor
your services. SAP Cloud Platform API Management offers many out of the box API security policies
based on the OWASP API security best practices which can be customized for your enterprise
requirements.
For hybrid scenarios spanning both on-premise and cloud environments, SAP Solution Manager
7.2 has several hybrid supportability offerings that ease the operation of corresponding
applications and use cases. For example, if your SAP Fiori app should be facing performance issues,
you can analyze where most of the time is spent for a certain action inside the app with end-to-end
Trace Analysis of SAP Solution Manager. In addition, you get insights about the request path that
the processing of the triggered action takes in your hybrid environment, including inbound and
outbound request points. With this information, you can start further investigations on the
identified hot spots of the operation. For more information about hybrid supportability offerings of
SAP Solution Manager for SAP Cloud Platform use cases, see this blog in SAP Community.

Troubleshooting
With biweekly updates to applications there is a chance you may experience issues therefore, SAP
offers tips on how to identify and mitigate application issues.

1. Restore previous patch level (n-1)

2. Test the upcoming patch level (n+1) in the preview landscape (if available)
3. Check support guides
4. Report incident
a. EP-CPP-SFC for Fiori Technology
b. For application specific components, reference the SAP Fiori Apps Reference Library

23
Common points for SAP Fiori Cloud issues include:
1. Checking OData Calls to the Back-End system
2. Broken connectivity between SAP Cloud Platform and the cloud connector
3. Access to OData resources not allowed in the cloud connector
4. Wrong passwords
5. Wrong configuration of OData service in SAP Gateway
6. Navigation between SAP Fiori launchpad and SAP Fiori apps not working properly
More information on how to troubleshoot these issues can be found in the troubleshooting guides.

Release Note Information:

2451380: SAP Fiori Cloud for Business Suite
2425345: SAP Fiori Cloud for SAP S/4HANA 1610
2520329: SAP Fiori Cloud for SAP S/4HANA 1709

24
More Information about the Operation Phase:

• Lifecycle Management for SAP Fiori Cloud

• SLA for Cloud Solutions
• SAP Help | Preview Environment – Best Practices
• Visit Part 4.5 of the CI Best Practices Guide
• Analyzing launchpad site statistics
• Monitoring SAP Fiori Cloud
• API Security Best Practices
• Brief Overview of Hybrid Supportability Options for SAP Cloud Platform
• SAP Fiori Cloud Support Guide
• SAP Fiori Apps Reference Library
• Troubleshooting 25
SUMMARY
For companies to truly digitally transform their business, a Submit Feedback:
delightful user experience for business applications is Help improve SAP Cloud Platform
imperative. SAP Fiori Cloud provides you with the most Blueprints.
commonly-used transactions tailored to provide end users
with only the most relevant data needed to drive their • Go to the SAP Cloud Platform
business task. The contents within this blueprint have Enablement Assets influence
detailed the most important steps for 4 definitive phases; session
ideation, planning, implementation, and operation. Before http://influence.sap.com/sapc
implementing SAP Fiori apps be sure to reference the links p-enablement-assets
within this blueprint.
• Click on Submit Improvement to
send your feedback or report an
error
For more information, please
visit
SAP Cloud Platform Scenarios

Follow SAP
www.sap.com/contactsap
© 2018 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 platforms, 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/corporate-en/legal/copyright/index.epx for additional
trademark information and notic

26