Using SAP Fiori

When talking about SAP Fiori deployment options, we differentiate mainly between the deployment location of SAP Fiori UI components and the back-end components. The following graph shows the main SAP Fiori deployment options with an on-premise SAP back end:

• On-premise: SAP Fiori front-end server embedded deployment.
• On-premise: SAP Fiori front-end server as a standalone server/hub deployment.
• Hybrid: SAP Fiori launchpad and (custom) SAP Fiori UIs on SAP BTP(Cloud Foundry).

All the mentioned deployment options consume business data from an on-premise SAP back-end system. The SAP Fiori launchpad, the SAP-delivered or custom-build SAP Fiori UIs and the launchpad content can be deployed on the same server (embedded deployment), or on a separate server (hub deployment). Furthermore, SAP Business Technology Platform offers tools to develop custom SAPUI5/Fiori applications and extensions.

Based on the technical deployment options described in the previous section, the following graph shows the deployment options when focusing on an SAP S/4HANA implementation.

The previous figure shows the main software components and versions in an embedded SAP Fiori front-end server deployment for the different SAP S/4HANA releases.

The system landscape for SAP Fiori mainly consists of an SAP front-end server and an SAP back-end server. These are system roles of an Application Server for ABAP (AS ABAP) in this landscape. The back-end server is an SAP Business Suite that contains applications and data for all areas based on AS ABAP 7.40 or higher. The front-end server is a basic AS ABAP 7.40 or higher with no installed business products. Both systems can be run on any database.

Although the SAP Fiori launchpad running on any client can communicate directly with the SAP front-end server, it is recommended that you use an SAP Web Dispatcher or another reverse proxy, not only in external scenarios, but also internally between the SAP Fiori launchpad and the SAP front-end server. The reason is that for some functions of the SAP Fiori launchpad, several systems have to be reached, which is for good reason prohibited in web communication. Therefore, a reverse proxy provides a single point of communication that contains routing rules for routing requests to the correct destination systems.

For guidance on SAP Fiori landscape architecture get the official document: SAP Fiori Deployment Options and System Landscape Recommendations.

See the document below the download-URL: https://www.sap.com/documents/2018/02/f0148939-f27c-0010-82c7-eda71af511fa.html with the title: SAP Fiori Deployment Options and System Landscape Recommendations.

The SAP Fiori system landscape for an SAP Business Suite on any database supports SAPUI5-based transactional and legacy apps based on Web Dynpro and ABAP transactions. Obligatory components of the SAP front-end server are the SAP Gateway for Open Data Protocol (OData) communication, the central UI for general SAP Fiori functions, and product UIs for the apps. Once again, the SAP Gateway and the ABAP code for the logic of the apps are located on the SAP back-end server.

To use an SAP Fiori app, you first need a running SAP Fiori launchpad. The SAP Fiori launchpad is part of the central UI, including all views, functions, and tools for personalization, customizing, and content configuration. The personalization is done by the user in the SAP Fiori launchpad being executed. Therefore, not only for personalization but also for other domains, the SAP Fiori launchpad needs to read and write data from the SAP front-end server using OData.

There is no communication with the SAP back-end server from the SAP Fiori launchpad. All general settings for SAP Fiori are saved on the SAP front-end server to be independent of the SAP back-end server. Although not shown in the diagram, it is common for many customers to have multiple back ends. Therefore, there is a big advantage if there is only one location (a system) for SAP Fiori settings.

Aside from the need to run an SAP Fiori launchpad, transactional apps consist of SAPUI5 apps and the SAP Gateway services. SAPUI5 apps are backed up as Business Server Pages (BSP) in the ABAP repository and deployed using product-specific UI add-ons. These will be installed on the SAP front-end server. The Gateway services are included with updates to the SAP back-end server solution and written in ABAP.

The registration of the gateway services is done by the customer on the SAP front-end server. If transactional apps require data, an OData request is executed via the SAP Web Dispatcher to register the gateway service on the SAP front-end server. From there, the SAP Gateway framework creates an RFC request to implement the gateway service on the SAP back-end server. The implementation uses ABAP code to access the data in the database.

In the second dimension, SAP Fiori provides a unified user experience for a variety of clients. Users should have a consistent, simple, intuitive, and engaging user experience across all devices, so they can work smarter and more efficiently. This role-based approach is the biggest change compared to classic user interfaces.

A role-based user experience means that end users get all the information and features they need to do their daily work, but no more. The classic SAP user interface (UI) often offers a single complex transaction for many user roles. The tasks of a single user then require the use of several of these transactions or even additional applications.

SAP Fiori breaks down these large transactions into multiple individual apps that match the user roles. All apps are connected to each other, so that all tasks of the transaction are still possible, but only be carried out if the user really wants this. The SAP Fiori launchpad then serves as the central entry point for all users' apps.

The SAP Fiori launchpad offers various functions for end users to simplify daily work. Depending on the role of the user, the SAP Fiori launchpad displays different groups of tiles. Every app is represented by a tile, which can be clicked or tapped to start it. Tiles can display a summary of the data available for the user in the tile. This information can be represented by a simple number or color coding of key performance indicators (KPIs) or is visually represented by diagrams containing comparisons or trends.

The SAP Fiori launchpad can be accessed in three ways:

Web browser

You can use any browser that supports HTML5.

SAP Business Client (BC)

As of SAP Business Client 6.0, it is possible to create system connections to the SAP Fiori launchpad.

SAP Fiori Client

The SAP Fiori Client is available for mobile devices from Apple, Google, and Microsoft.

You can integrate the SAP Fiori launchpad into other system areas to generate additional advantages, such as additional log-in functions, or to reach further users.

The figure shows a screenshot of the My Inbox app. In the SAP Fiori app reference library, you can find information about the technical implementation.

We have created a tile for a catalog, and it is accessible to the user.

The user can browse through the catalogs available to them and choose the tiles that they want to display on the entry page of the SAP Fiori launchpad.

To add a tile to the launchpad home screen:

1. Log in to SAP Fiori launchpad.
   Note

   The figure shows data of the user TRAIN-40.
2. Click to the user.
3. Select the App Finder.
4. Search the workflow apps and add them to My Home.
5. Choose Close.