Exploring Architecture and Roles

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.

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.

The following steps on the FES are necessary for work with Fiori apps:

• Install backend component

• Install product-specific UI component on the backend

• Install frontend component on the frontend server

• Implement necessary SAP Notes

• Activate OData services on the frontend server

• Activate SAPUI5 apps on the frontend server

• Check/create roles containing Fiori catalogs and Fiori tile groups

• Assign roles to users

• Assign OData service authorizations (backend / frontend)

The following steps on the BES are necessary for work with Fiori apps:

• Install the required software components/products

• Implement app on the back end (additional steps might be required, for example, create selection variants, activate workflow tasks, assign responsible employees, link SAP user and personnel number, etc.)

• Check/create roles containing transactions, WDA (Web Dynpro ABAP) apps, and their authorizations

• Assign roles to users

• Activate business functions for WDA apps

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_ ...

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.

Fiori catalogs, Fiori tile groups, and individual tiles can be viewed and modified using the SAP Fiori launchpad designer.

A catalog contains the complete set of tiles that is available for a given area.

A group contains a set of tiles to be displayed for a certain user. You can add tiles to groups from catalogs. You can also edit the properties of a group. You can specify that a group cannot be personalized by the end user.

A tile contains a so-called target mapping in which the application type and the application to be used are specified.

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.

SAP GUI can be personalized and adapted as follows:

• The user can personalize SAP GUI.

  (f.ex. adapt the visual design (theme, font settings etc.) or set default values (user profile, transaction EAM_USER)

• The administrator or key user can customize SAP GUI on client level (IMG).

  (f.ex. define view profiles for business objects, define the field selection etc.)