UI and UX

Objective

After completing this lesson, you will be able to check Architecture and Roles

UI Clients

SAP S/4HANA supports different UI client types:

  • SAP Fiori Launchpad

  • SAP GUI for Windows (On Premise only)

  • SAP GUI for HTML

  • SAP Business Client (for Desktop / for HTML)

Four examples of the SAP S/4HANA UI client types.

SAP Fiori Launchpad

SAP Fiori Launchpad (FLP) is designed to be the central entry point for all deployment models (Cloud and On Premise). SAP Fiori Launchpad supports SAPUI5 technology (HTML5), SAP GUI for HTML and Web Dynpro.

SAP Fiori Launchpad is a role-based, personalized UI client which can be deployed on different device types and platforms. The client is browser-based and works with Tile Groups or Spaces which can be flexibly put together based on Tile Catalogs. Which tile catalogs are available for which user is determined via the assignment of so-called Frontend Roles.

Architecture

The details shown in the diagram of the SAP S/4HANA and UX architecture is described in the following video.

SAP S/4HANA is available for deployment options cloud and on premise.

Cloud

In this context, the client type SAP Fiori Launchpad (FLP) is the first choice.

Within SAP Fiori Launchpad different UI technologies can be used: SAPUI5, Web Dynpro ABAP and SAP GUI for HTML.

On premise

For the on premise deployment model, the client type SAP Fiori Launchpad (FLP) also is the first choice. However, it is also possible to run SAP S/4HANA On Premise together with the traditional SAP GUI for Windows.

As an alternative to SAP Fiori Launchpad and SAP GUI for Windows the SAP Business Client can also be used.

SAP Fiori Launchpad (FLP) - Architecture

The details of the FLP Architecture diagram is described in the following text.

SAP Fiori Launchpad (FLP) runs in almost all browsers that are available on the market. Please check the SAP documentation for supported versions.

When logging on to FLP, the user first connects to the frontend server (FES). The FES acts as sort of hub for one or several backend systems and contains the Fiori-specific apps, roles, and services. Communication between the FLP and the FES is based on the HTTPS protocol, as well as on a set of OData services. Therefore the required OData services must be activated on the FES.

Open Data Protocol (OData) is a Web protocol for querying and updating data, applying and building on Web technologies, for example, HTTP, to provide access to information from a variety of applications and services. Because OData services are easily utilized on different platforms, you can use this service to build cross-platform Web and mobile applications.

Note

SAP only supports installations, where FES and BES run on the same server.

When clicking on a tile in the FLP, the user executes an application. The code of these applications in many cases is located on the backend system (BES). Therefore the user must be able to log on to the backend system and must be authorized to run the application. Communication between the FES and the BES is based on Remote Function Call (RFC). Therefore, the user needs certain RFC authorizations.

Application Types

Each tile has a specific application type with a specific UI technology:

  • Transactional apps: Usage of ABAP to provide the classic approach for functions of a business system

  • Analytical apps: Usage of analytical capabilities of SAP HANA to provide insights in business data

  • Fact Sheet apps: Usage of enterprise search capabilities of SAP HANA to provide search results

All tiles are delivered via SAP Fiori catalogs located on the FES. Which tiles are actually displayed in FLP is determined via Fiori tile groups.

Fiori catalogs and Fiori tile groups need to be assigned to PFCG roles on the FES. These roles will then be assigned to the user.

Most applications in SAP S/4HANA Asset Management are transactional apps. However, there is a variety of transactional apps using different UI technologies:

  • Transactional/SAPUI5: These are the new apps relying on SAPUI5 apps and OData services located on the FES.

  • Transactional/WDA: WDA stands for Web Dynpro ABAP and relies on Web applications that must be activated via business functions (BF) on the BES.

  • Transactional/SAP GUI: These apps execute a traditional transaction on the BES – displayed in FLP via SAP GUI for HTML.

Fiori / SAPUI5

The Fiori / SAPUI5 interface can be personalized and adapted as follows:

  • The user can personalize the SAP Fiori Launchpad.

  • The user can personalize individual SAP Fiori Apps.

  • The administrator or key user can adapt SAPUI5 at runtime (RTA).

  • The UI Theme Designer can be used to adapt theming and branding.

Web Dynpro ABAP (WDA)

WDA apps can be personalized and adapted as follows:

  • The user can personalize a WDA app.

  • The administrator or key user can customize a WDA app on client level (WDA Customizing).

  • The developer can configure a WDA app on system level.

  • The UI Theme Designer can be used to adapt theming and branding.

Note

For further info regarding customizing and configuration of Web Dynpro check the SAP Help Portal under SAP S/4HANA → Enterprise Technology → ABAP Platform → UI Technologies → Web Dynpro ABAP and Floorplan Manager or under the following link regarding Web Dynpro ABAP:

https://help.sap.com/viewer/fc79a39b30fe4d9aa983bad6787ab9ad/202009.000/en-US/4e161363b81a20cce10000000a42189c.html

Note

In the app that you are currently using : How can you find out which UI technology is used?

Simply use the i About option within your user profile (top right in the FLP).

In the Application section, the parameter Framework ID shows:

  • UI5 for Fiori / SAPUI5 apps

  • WDA for Web Dynpro ABAP apps

  • GUI for SAP GUI transactions

Roles, Catalogs and Groups (FES)

The details shown in the Frontend Roles diagram is explained in the following video and text.

Fiori catalogs contain all the apps that a certain user or group of users should have access to. These apps are not necessarily displayed in the FLP from the start, but they are available for personalization by the user.

Fiori tile groups consist of a headline and a set of tiles. The actual FLP interface for a given user at a given time is made up of a sequence of tile groups. Each tile group represents a kind of a menu and is displayed automatically in FLP if it is assigned to a role. In addition, the user can create his or her own tile groups during personalization. Tile groups can either be organized in a separate role (separate from catalogs) or they can be part of the roles containing the catalogs, as is the case in the standard roles.

Fiori catalogs and Fiori tile groups are assigned to PFCG roles on the FES. You can copy the standard roles to create your own role.

Standard roles in SAP S/4HANA Asset Management are:

  • SAP_BR_EMPLOYEE_MAINTENANCE – Employee

  • SAP_BR_MAINTENANCE_PLANNER – Maintenance Planner

  • SAP_BR_MAINTENANCE_PLANNER_RSH – Maintenance Planner - Resource Scheduling

  • SAP_BR_MAINTENANCE_TECHNICIAN – Maintenance Technician

Once your roles are defined, they are assigned to the user on the FES.

Note

For further info regarding Fiori Apps see the SAP Fiori apps reference library, via: https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/

Roles (BES)

The details of the Backend Roles diagram is described in the following video.

The same user who is configured on the FES must also be configured on the BES. First, you need to create PFCG roles on the BES that contain the necessary transactions, Web Dynpro ABAP (WDA) apps, and other app types if necessary – as well as the necessary authorizations.

As on the FES, you can copy the available standard roles to create your own roles and modify them as needed. The standard roles starting with SAP_PM_ contain the traditional transactions.

The following standard roles provide all WDA apps for SAP S/4HANA Asset Management:

  • SAP_COCKPIT_EAMS_GENERIC_FUNC2 – Generic EAM Functions

  • SAP_COCKPIT_EAMS_MAINT_WORKER2 – Maintenance Worker

Bear in mind that the WDA apps and their roles need to be activated via the business functions starting with LOG_EAM_SIMPLICITY – as explained earlier in this unit. This is not necessary for the traditional transactions.

Note

Further details regarding Business Functions in SAP S/4HANA can be found in the Help Portal, via:

https://help.sap.com/viewer/7113856e409647838af7891e1429b807/2020.000/de-DE/cc899f57e30f8a1be10000000a44147b.html

Business functions

The functionality of SAP EAM WDA is shipped with the following business functions:

  • LOG_EAM_SIMPLICITY

  • LOG_EAM_SIMPLICITY_2

  • LOG_EAM_SIMPLICITY_3

  • LOG_EAM_SIMPLICITY_ ...

Learning

SAP FacebookSAP YoutubeSAP LinkedIn