Skip to Content

 

User Interface technology at SAP has a long history. Starting with SAP GUI, Business Server Pages (BSP), Web Dynpro, Floorplan Manager (FPM), Enterprise Portal (as client for UI integration), we have now Fiori.

Fiori apps are web applications, which need an SAPUI5 library and a Fiori Launchpad and last but not least an “SAP Fiori Front-end Server” on which all runs on premise or need SAP Fiori Cloud for cloud deployment.

Classic SAP GUI and Web Dynpro applications using SAP Fiori theme need an AS ABAP in the backend, which supports SAP Fiori theme. This is only the case for AS ABAP 7.51 and higher for S/4HANA.

 

What is SAP Fiori Front-end Server?

First of all, it is just an Application Server ABAP.

 

Technically it is an Add-on to AS ABAP, delivering the right Service Pack Stack (SPS) definition (stack.xml) for AS ABAP, suitable for Fiori App deplyoment.

Each SAP Fiori Front-end Server (FES) supports multiple AS ABAP versions, basically starting from AS ABAP 7.40.

FES version AS ABAP 7.40 AS ABAP 7.50 AS ABAP 7.51 AS ABAP 7.52
FES 2.0 x x
FES 3.0 x x x
FES 4.0 x x x x

 

FES defines the initial shipment stack (ISS) and service pack stack (SPS) for 2 AS ABAP software components independent from the AS ABAP stack.

  • User Interface Technology (technical name “SAP_UI”) and
  • SAP Gateway Foundation (technical name “SAP_GWFND”, only up to AS ABAP 7.51).

Means these 2 component can be installed and updated independently from the underlying AS ABAP stack definition.

 

A SAP Fiori Front-end Server version always defines exactly one version of SAP_UI. SAP_UI contains the innovation version and one maintenance version of the SAPUI5 library.

For example:

FES version contains SCV contains
FES 2.0 SAP_UI 7.50 SAPUI5 1.38.x
FES 3.0 SAP_UI 7.51 SAPUI5 1.44.x
FES 4.0 SAP_UI 7.52 SAPUI5 1.50.x (Innovation, planned maintenance vers. 1.52.x)

(For more information about versioning, see versioning of SAPUI5, and available SAPUI5 versions)

 

FES defines also the SAP_GWFND up to AS ABAP 7.51. The SAP_GWFND software component version has always the same version as the underlying AS ABAP, but shares the Service Pack Stack definition with SAP_UI, which is defined in FES.

From AS ABAP 7.52 on, SAP_GWFND is not any more part of the FES stack defintion and can only be updated via the AS ABAP using the AS ABAP stack definition.

 

FES version SAP_GWFND 7.40 SAP_GWFND 7.50 SAP_GWFND 7.51 AS ABAP 7.52
FES 2.0 x x
FES 3.0 x x x
FES 4.0 x x x x

 

 

Maintenance and Update

Thes FES Add-on also provides the 2 software components “SAP_UI” and “SAP_GWFND” independent from AS ABAP. So these 2 component can be downloaded and implemented or updated independently from the AS ABAP stack definition.

The FES stack definition can run a higher SPS than the underlying AS ABAP SPS. E.g. if you update FES 3.0 to SPS09, typically SAP_UI and SAP_GWFND (until 7.51) will be SP09, while e.g. SAP NetWeaver 7.5 can – but need not – stay on SPS01.

 

 

Upgrade

As ABAP allows you to upgrade the SAP_UI version to a higher version. e.g. AS ABAP 7.50 allow  to upgrade SAP_UI 7.50 to SAP_7.51. FES does not. In this example you have to upgrade from FES 2.0 to FES 3.0.

If you want to “upgrade” your SAP_GWFND to a higher version, you hav eto upgrade the underlying AS ABAP to a higher instance. The highest possible SAP_GWFND and AS ABAP verison is the SAP_UI version.

 

 

Optional Components

FES contains additionally the SAP software component “UI for Basis Applications”, technical name “UIBAS”. In documentation it is named “SAP Fiori Apps for SAP NetWeaver”. Target group are “key user for SAP NetWeaver”. These apps are mainly required for some S/4HANA Fiori apps and are only available for FES on NW AS ABAP 7.5 or higher.

100-300 for S/4HANA.

FES version contains available for AS ABAP
FES 2.0 UIBAS 100 7.50
FES 3.0 UIBAS 200 7.50, 7.51
FES 4.0 UIBAS 300 7.50, 7.51, 7.52

 

 

 

Deployment Options for SAP Fiori Front-end Server

SAP Fiori Front-End Server allows various deployment options.

  • Embedded deployment: The front-end server is deployed into the (existing) AS ABAP of a Business Suite or S/4HANA backend system.
  • Hub single backend deployment: A dedicated AS ABAP based SAP Fiori Front-end Server is deployed “in front of” the backend system. These allows decoupling of the life cycle of the AS ABAP of the FES from the AS ABAP of the backend.
    Different backends run in different AS ABAP clients of the FES. Fiori apps for different backend versions do not interfere each other.
  • Hub multi backend deployment: Deployment in one FES client for multiple backends. Only possible, if the software components for the Fiori apps are different and do not interfere each other.

For detailed information, see Landscape Deployment Recommendations for SAP Fiori Front-End Server and Release Information Notes for the deployed Fiori Apps.

 

 

Additional Information

2219596 Central Note for SAP Fiori Front-End Server 2.0

2355644 Central Note for SAP Fiori Front-End Server 3.0 (incl. Fiori 2.0)

2484979 SAP-Fiori-Frontend-Server 4.0 – General Information

 

Related Blogs on SAP Fiori Front-end Server

Explore the SAP Fiori Implementation Options

Planning an SAP Fiori Implementation

SAP Fiori Front-end Server Installation Guide

Landscape Deployment Recommendations for SAP Fiori Front-End Server

 

Additional Readings 

SAP Fiori for S/4HANA – Wiki

All Things SAP Fiori – Wiki

Fiori in S/4HANA – Overview

Fiori for S/4HANA – Getting started with documentation

Fiori for S/4HANA – Fiori 2.0 Implementation Guidelines

 

 

 

 

 

 

 

 

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply