Skip to Content

SAP Fiori Front-end Server Installation Guide


Related blogs of the series:

SAP Fiori Front-end Server in a Nutshell (very brief overview)

Explore the SAP Fiori Implementation Options (including SAP Fiori Cloud options)

Planning an SAP Fiori Implementation (what you need to run SAP Fiori)



Installation Guide SAP Fiori Front-end Server

In order to run SAP Fiori apps, you need to setup Your SAP Fiori system landscape. SAP Fiori apps require front-end components to host the web-based user interface and the connection to the back end and back-end components to provide the business data. The front-end components and the back-end components are delivered in separate products.  For a list of available Fiori apps please refer to

In an on-premise scenario, the front-end components run on a front-end server, such as SAP Fiori Front-end Server, which is based on a NetWeaver Applications Server ABAP. After the installation, the configuration of the SAP Fiori Front-end Server is required.


1  Plan the SAP Fiori System Landscape

SAP Fiori Front-End Server allows various deployment options. In general, you have two options to set up the SAP Fiori Front-end Server to deploy the front-end server into an (existing) SAP landscape:

  • 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 Fiori Front-end Server is deployed “in front of” one SAP Business Suite or S/4HANA backend system.
  • Hub multi-backend deployment: Deployment of one FES client for multiple backends. Only possible, if the software components for the Fiori apps are different and do not interfere each other.

Each option has both advantages and drawbacks. It is therefore up to the customers to decide, which deployment option for SAP Fiori Front-End Server suits best their IT and business needs.

For further information, including mobile and multi-backend scenarios, see Landscape Deployment Recommendations for SAP Fiori Front-End Server and the blog SAP Gateway deployment options in a nutshell.


Note: Fiori 2.0 landscape requirements

If you want to run Fiori 2.0 in your landscape you need to meet some minimum requirements for frontend server and optional backend server.

The full Fiori 2.0 feature set basically needs 3 technical components:

  • Fiori 2.0 theme Belize for web applications
  • Fiori 2.0 theme Belize for classic applications using SAP GUI
  • Fiori 2.0 feature “Notifications” in Fiori Launchpad

Fiori 2.0 theme Belize for web applications needs an SAP Fiori Front-end Server 3.0 or higher. It is part of the SAP_UI component 7.51 or higher and is available in any AS ABAP instance of the Fiori Front-end Server.
Fiori 2.0 theme Belize for SAP GUI for HTML and SAP GUI Windows is only available only for S/4HANA 1610 or higher. It needs an AS ABAP 7.51 or higher on the backend server.
Fiori 2.0 feature “Notifications” in Fiori Launchpad is only available with Fiori Frontend Server 3.0 and higher with minimum an AS ABAP 7.51 and higher in frontend server and in backend server.


2  SAP Fiori Front-end Server

SAP Fiori front-end server is an add-on product for NetWeaver AS ABAP. It contains all the infrastructure components needed to run SAP Fiori apps in the right stack definition for Fiori apps. These components are:

  • User Interface Technology – including the SAPUI5 library and SAP Fiori launchpad
  • SAP Gateway Foundation – for communication between front-end and back-end
  • SAP Fiori app implementation foundation (SAPUIFT) – administrative tools for configuration tasks
  • UI for Basis Applications – “SAP Fiori Apps for SAP NetWeaver” (only available with SAP NetWeaver 7.5 or higher).

The software component SAP_UI in Fiori Front-End Server 2.0 (and higher) or in NW AS ABAP 7.40 (and higher) contains the UI technologies SAPUI5 and Web Dynpro ABAP (WDA).

SAP Fiori Launchpad (FLP) is part of the SAP software component SAP_UI, the FLP user interface is part of the SAPUI5 library. FLP is the central entry hub for all SAP Fiori apps.

Software Component “SAP NW Gateway Foundation” SAP Gateway offers connectivity between SAPUI5 based web applications and the business logic in the backend systems (BES) leveraging REST services and OData/ATOM protocols. AS ABAP 7.40 and higher contains the corresponding Software Component Version (SCV) “SAP NW Gateway Foundation”.

For more information about User Interface Technology and SAP Gateway, see and choose your product version (direct link to version 7.51: SAPUI5 and Gateway Foundation).

SAP Fiori app implementation foundation provides automated services activation in AS ABAP. It activates OData services (/IWFND/MAINT_SERVICE) and ICF nodes (SICF). For more information about SAP Fiori app implementation foundation (SAPUIFT), see SAP Note 2219596.

For more information about Fiori Front-end Server, see

SAP Fiori apps are delivered separately as SAP Business Suite or S/4HANA product-specific UI add-on products, which must be additionally installed on the front-end server. For more information about Fiori apps, see à Application Help à Function-Oriented View à SAP Fiori Apps for SAP NetWeaver (direct link to version 7.51).


Optional: SAP Portal and SAP Fiori Front-end Server (on Premise)

SAP Fiori launchpad can be integrated into SAP Portal (see also Note “2031108 – SAP Fiori Integration with SAP Enterprise Portal – Central note”). ABAP FES is required. For more details please refer to note “2261419 – Maintenance Strategy for FLP on Portal“.

Optional: SAP Business Client 6.0 and SAP Fiori Front End Server (On-Premise)

With SAP Business Client 6.0 for the first time, you can launch SAP GUI for Windows transactions directly from the SAP Fiori Launchpad. SAP Business Client offers an integration of the SAP Fiori launchpad to allow a unified SAP Fiori user experience:

  • SAP Fiori launchpad as start page, connecting directly to the SAP ABAP Frontend Server
  • Launch SAP GUI transactions using embedded SAP GUI for Windows
  • Business role configuration purely SAP Fiori launchpad-based

For more information, see SAP Business Client for Desktop – SAP BC.


2.1  SAP Web Dispatcher

You may also consider installing SAP Web Dispatcher as a reverse proxy or load balancer in front of Fiori Front-end Server. For more information about SAP Web Dispatcher, see Installing SAP Web Dispatcher and SAP note 908097.


2.2 SAP Fiori Front-end Server 2.0

SAP Fiori front-end server 2.0 is available for three NetWeaver Application Server ABAP versions: AS ABAP 7.50 or AS ABAP 7.40 or AS ABAP 7.31. The instance for 7.31 is not recommended if higher versions of AS ABAP are feasible. FES 2.0 contains:

  • Software component version USER INTERFACE TECHNOLOGY 7.50 (or UI Add-on 2.0 for NW 7.31)
  • Software component version SAP NW GATEWAY FOUNDATION 7.40 or 7.50 (depending on AS ABAP) or Gateway 2.0, for instance, NW 7.31
  • SAP Fiori app implementation foundation (software component version SAPUIFT 100)
  • Software component version UI FOR BASIS APPLICATIONS 100 (only for AS ABAP 7.50)

For more information about SAP Fiori front-end server 2.0, see SAP Note 2219596.


2.3   SAP Fiori Front-end Server 3.0

SAP Fiori front-end server 3.0 is available for three different NetWeaver Application Server ABAP versions: AS ABAP 7.51 or AS ABAP 7.50 or AS ABAP 7.40. It contains:

  • Always software component version USER INTERFACE TECHNOLOGY 7.51
  • Software component version SAP NW GATEWAY FOUNDATION 7.40, 7.50 or 7.51 (depending on AS ABAP)
  • SAP Fiori app implementation foundation (software component version SAPUIFT 100)(deprecated)
  • Software component version UI FOR BASIS APPLICATIONS 200

For more information about SAP Fiori front-end server 3.0, see SAP Note 2355644

Remark: SAP Fiori front-end server 3.0 provides the technology for SAP Fiori 2.0. SAP Fiori 2.0 includes a new visual theme called SAP Belize.


2.4   SAP Fiori Front-end Server 4.0

SAP Fiori front-end server 4.0 is available for 4 different NetWeaver Application Server ABAP versions: AS ABAP 7.52, 7.51, 7.50 or 7.40. It contains:

  • Always software component version USER INTERFACE TECHNOLOGY 7.52
  • Software component version SAP NW GATEWAY FOUNDATION 7.40, 7.50, 7.51 (depending on the underlying AS ABAP). SAP_GWFND 7.52 for AS ABAP 7.52 is planned not be part of the add-on delivery. It is planned to be part of the AS ABAP stack definition.
  • SAP Fiori app implementation foundation (software component version SAPUIFT 100)(deprecated)
  • Software component version UI FOR BASIS APPLICATIONS 300

For more information about SAP Fiori front-end server 4.0, see SAP Note 2355644.

Remark: SAP Fiori front-end server 4.0 provides the technology for SAP Fiori 2.0.


2.5 Remarks: Older Front-end Server deployment options:

Newer SAP Fiori app front-end components always require an “SAP Fiori Front-End Server” based on NW AS ABAP. Older SAP Fiori apps allow the use of the SAP User Interface Add-On for SAP NetWeaver, based on NetWeaver AS ABAP 7.31. The SAP UI Add-on is available in version 1.0 and 2.0. A successor version of UI Add-on 2.0 is not planned.

SAP UI Add-on 1.0 can be upgraded to FES 2.0, UI Add-on 2.0 can be migrated to FES 2.0 or higher.

For more information, see documentation User Interface Add-On for SAP NetWeaver and Setup of SAP Fiori System Landscape for SAP Business Suite.

From NW AS ABAP 7.40 on, the components of SAP UI Add-on are included into AS ABAP. Some of the older Fiori Apps allow the usage of NW AS ABAP 7.40 without FES 2.0 as a prerequisite. NW AS ABAP can be migrated to FES 2.0 or upgraded to FES 3.0 or higher.



3  Planning an Installation or UPDATE with SAP Maintenance Planner

SAP Solution Manager’s cloud-based Maintenance Planner enables easy and efficient planning of all changes in your SAP system landscape. It is the successor of Maintenance Optimizer, Landscape Planner, and Landscape Management Database (LMDB) Product System Editor and combines their functionalities and is mandatory for planning SAP S/4HANA and SAP NetWeaver 7.5+ based systems. Maintenance Planner consolidates critical tasks such as a definition of product maintenance dependencies, generation of a stack configuration file, and selection of archives in a single tool.

For more information, see

With the maintenance planner, you can:

  • Get an overview of the system landscape, including system dependencies, before planning a change.
  • Determine the impact of a system change on your landscape, with features like product maintenance dependency.
  • Download the stack XML that contains all the planned changes, and put the required files in a download basket.
  • It offers integrated processes for installation of SAP Fiori Apps and conversion to SAP S/4HANA


Planning with the Maintenance Planner

The overall process of planning an installation or update is the following:

  1. In Maintenance Planner, select existing system (embedded deployment) or plan installation of a new system (hub deployment).
  2. Optional: Upload system data to the Customer Profile through SLD/LMDB to calculate further Add-on installations, Updates, upgrades, or conversion of existing systems.
  3. Choose target product version and Support package stack for all involved systems.
  4. Generate and download consolidated stack.xml and archives (download basket) for front-end server and optional together with “sl-toolset”. SL-toolset contains Software Provisioning Manager (SWPM) and Software Update Manager (SUM).
  5. Use stack.xml for installation with Software Provisioning Manager or for updates and add-on installation (such as FES on top of an existing AS ABAP) Software Update Manager.

Access Maintenance Planner directly.


Planning Installation of SAP Fiori Apps with Maintenance Planner

For more information about planning and installing Fiori Apps with Maintenance Planner, see blog Simplified Installation of SAP Fiori Apps with Maintenance Planner.



4  Install or Update SAP Fiori Front-end Server

For installing or updating SAP Fiori Front-end Server you need to download the Software Logistics Toolset (SL Toolset) first. Installation requires the Software Provisioning Manager of SL toolset

For more information about installation in general, see and the SAP NetWeaver Guide Finder. For more information about SAP NetWeaver AS ABAP, see


4.1  Software Logistics Toolset (SL Toolset)

The SL Toolset ( contains the Software Provisioning Manager (SWPM) for Installation of a new AS ABAP and Software Update Manager (SUM) for installing the SAP Fiori Front-end Server-Add-on or updating an existing FES-system.

We recommend that you always download the latest versions of the SL tools with the latest available SPS, as they contain the latest corrections and are updated regularly. Please note that you can only download the SL tools, but not the SL Toolset as such.


Installation with Software Provisioning Manager and Installation Guides

Software Provisioning Manager 1.0 is the successor of the product- and release-specific delivery of provisioning tools. It provides the latest SAPinst version with software provisioning services for several products and releases for all platforms.

Software provisioning manager covers the use cases system installation, system copy, migration and rename and is thus the tool for installing the require AS ABAP for SAP Fiori Front-end Server

The installation guides for the different AS ABAP database and operating system platforms can be found at à System Provisioning“ à „Installation Option“


Add-On Installation with Software Update Manager and Guides

The Software Update Manager is a multi-purpose tool that supports various processes, such as performing a release upgrade, installing enhancement packages, applying support package stacks, installing add-ons such as SAP Fiori Front-end Server, or updating single components.

Overview of SUM procedure

  1. Plan your maintenance activity (Maintenance Planner)
  2. Download the SUM and the documentation from
  3. Extract the archive to a folder on the primary application server (central instance) of your SAP system
  4. Update SAP Host Agent to latest patch level; configure SAP Host Agent (see guide);
  5. Connect from your local PC via browser
  6. Configure the SUM, especially point to the stack.xml as result of Maintenance Optimizer Transaction
  7. Execute the maintenance on your system (Note: Before the upgrade, installation of additional SAP Notes listed in the CHECKS.LOG file might be required)

Documentation about installing FES as an add-on to an existing AS ABAP or updating or upgrading Fiori Front-end Server is available in the Software Update Manager Guide: à „System Maintenance“ à „Software Update Manager (SUM) 1.0.


SAP Add-On Installation Tool (SAINT)

SAP Add-On Installation Tool (transaction SAINT) is the previous Add-on installation process for AS ABAP. It does not support stack.xml definition and dependencies. Technically it is possible to import Add-ons such as FES with SAP Add-On Installation Tool (transaction SAINT), but it is not recommended, or it is recommended to update with stack.xml definition and SUM during the next update. For more information see à SAP Add-On Installation Tool.


5  Post-Installation


Before installing individual apps in your SAP Fiori system landscape, SAP Fiori Front-end Server has to be configured. Which tasks are relevant depends on your system landscape and the types of app that you want to implement. For more information, see à Configuration.


Product Availability Matrix (PAM)

The Product Availability Matrix (PAM) is the single point of information for SAP Fiori Front-end Server and its contained components, such as end of maintenance dates, upgrade paths, landscapes, related product versions and technical release information (e.g. operating systems).


Maintenance Strategy

For information on the maintenance duration, refer to the maintenance strategy and SAP Note 2217489.


6  Information about Fiori Apps

For information on products, which run on SAP Fiori front-end server please, see and SAP Fiori apps reference library.



You must be Logged on to comment or reply to a post.
  • Hi Oliver,


    Very nice and detailed blog which gives lot of clarifications!!

    Thank you very much!


    I have one question on the dependency of Fiori 2.0 on SAP Portal and Fiori 2.0 on SAP Gateway system. (SAP front End Server)


    I have created one question as well which can be accessed at below link. Can you please look into?

    It would be very helpful if you provide your comments on it.





      Hi Bhavik, just one short remark, we should not use "SAP Gateway system" for "SAP Fiori Front-end Server". Technically is pretty similar, but FES comes with the required stack definition for Fiori Apps, esp. for the newer Fiori 2.0 apps. That should make things easier.

  • Thanks Oliver for the response.


    My actual question was dependency between Fiori 2.0 on SAP Portal and Fiori 2.0 on SAP FES.

    Can you comment if there are any dependencies based on the question I have posted?





      Hi, according to SAP Note 2031108 - SAP Fiori Integration with SAP Enterprise Portal - Central note, Portal 7.50 SP07 minimum is required for SAP_UI 7.51, which contains SAPUI5 1.40 (innovation)/1.44(maintenance) and which is necessary for FES 3.0 and Fiori 2.0.

  • Hi Oliver,

    thanks for this very helpful overview on SAP Fiori FES.

    Btw not only Portal benefits from the SAP Fiori launchpad integration. SAP Business Client integrates the FLP as well. With SAP Business Client 6.0 you can launch native SAP GUI for Windows transactions directly from the FLP (using the embedded SAP GUI for Windows)!

    FLP standalone starts transactions with SAP GUI for HTML.

    More information see SAP Business Client 6.0


  • this blog is a little help - but

    on every new issues - SAP everytime creates a big chaos in information about installation and possible architectures.


    we are with business-suite ECC-6.0 (EHP7) on NW-740-SPS13

    SAP_GWFND 740-SPS14 is installed as separate component

    SAP_UI 740-SPS15 is installed as separate compontent.


    PAM shows from NW740 two possible add-on installation (both for 740)

    • SAP FIORI FRONT-END Server 2.0
    • SAP FIORI FRONT-END Server 3.0


    but the MaintenancePlanner did not offer FIORI Front-End Server 3.0 for our ECC-System ???

    MP only offers FIORI Front-End Server 2.0  - but did not go on (the Confirm-Button is disabled) 

    ?? what to do ?


    is it possible to install FIORI Front-End Server 3.0 on SAP-ECC-6.0 NW-740 ?? 




    • Hello Christoph,

      this seems to be an issue in the Maintenance Planner. FES 3.0 is released for NW 7.40 and no restriction for ECC usage, due to my knowledge. I think MP offers the possibility to ignore this warning and to proceed(?).  In general I recommend to use hub deployment/setup for FES. In that case you are independent from the backend life cycle.

      Note: Please be aware with upgrade to SAP UI 7.51/ FES 3.0 you get a new theme for Fiori applications, called “Belize”. Also the Fiori apps need to have the appropriate version for FES 3.0.

      BR, Oliver


  • thanks, but sorry, next question:

    we are with business-suite ECC-6.0 (EHP7-SPS11) on NW-740-SPS13


    now we have a new Fiori Front-End Server (Hub) NW-7.50_SPS06

    with this components:

    SAP_BASIS 750 0006 SAPK-75006INSAPBASIS SAP Basiskomponente
    SAP_ABA   750 0006 SAPK-75006INSAPABA   Anwendungsübergreifende Komponente
    SAP_GWFND 750 0006 SAPK-75006INSAPGWFND SAP Gateway Foundation
    SAP_UI    751 0001 SAPK-75101INSAPUI    User Interface Technology
    ST-PI     740 0005 SAPK-74005INSTPI     SAP Solution Tools Plug-In
    SAP_BW    750 0006 SAPK-75006INSAPBW    SAP Business Warehouse
    UIBAS001  200 0001 SAPK-20001INUIBAS001 UI for Basis Applications 1.0
    IW_FNDGC  100 0005 SAPK-10005INIWFNDGC  SAP IW FNDGC 100
    WEBCUIF   748 0001 SAPK-74801INWEBCUIF  SAP Web UI Framework
    SAPUIFT   100 0001 SAPK-10001INSAPUIFT  SAP UI Frontend Implementation Technology
    UIRT401   100 0011 SAPK-10011INUIRT401  UI für Handelsfiliale


    developing team now is requesting for additional components:

    UI5_731   100 004 SAPK-10004INUI5731    SAP UI5 TEAM PROVIDER ON 731
    UISAPUI5  100 004 SAPK-10004INUISAPUI5  SAP UI5
    what to do ? 
    are this 3 requested components correct to add on to 
    a NW-7.50_SPS06 Fiori Front-End Server Hub ?? or is that a result of "old" documentation found on UI5 websites ? i found several new SPS to that 3 Components up to SPS
    UI5_731   100 017 SAPK-10017INUI5731    SAP UI5 TEAM PROVIDER ON 731
    UI5_731   200 007 SAPK-20007INUI5731    SAP UI5 TEAM PROVIDER ON 731
    UISAPUI5  100 017 SAPK-10017INUISAPUI5  SAP UI5
    what are corresponding and installable components and what SPS of that components 

    MaintenancePlanner (of course) did not offer and did not accept that components as Add-On installation on FES NW-750_SPS06
    is that another missing function in MaintenancePlanner ??
    • Dear Christoph,

      I'm pretty sure your development team does not need UI5_731. That was released in 2012 and does not match your NetWeaver 7.40 based ERP Backend and also not your 7.50 Frontend server. The SAPUI5 Components and the SAP Fiori Launchpad is part of:

      SAP_UI    751

      so perhaps ask your development team which SAP Fiori Apps they want to activate and look them up in the Fiori Apps Library. From the Implementation Information -> Installation you can start the Maintenance Planner which will provide you the correct information of what to install.

      Best regards

  • Hello Christoph,
    agreed with Gregor, Frontend Server 3.0 requires the Netweaver 7.51 Platform, thus it is compatible with S/4 1610 as embedded use case.

    Frontend Server 3.0 is not compatible with BW/4 as the Abap Layer differs (7.51 vs. 7.5A), but a BW on HANA System with 7.51 innovation stack would also work as embedded case.

    However to have all mentioned SAP Systems available through the Frontend Server 3.0/Fiori a dedicated Hub is necessary.

    Best Regards Roland

    • Roland,

      Is it possible to install the Fiori Front-End Server 3.0 as an add-on to a BW NetWeaver 7.40 SPS15 (on premise) system?

      Or is the hub deployment the only option to use Fiori applications against a BW system?


  • Hi all.

    We chose hub deployment for installation SAP Fiori Front-End Server.

    If we have  three back-end system(dev, test, productive ), do we need 3 FES servers((dev, test, productive ) ?

    • technically not, typically yes. this is the standard setup, not specific to Fiori.

      You could also run dev embedded, or even test. However you loose then the ability to test your settings before transporting them into prod. As the effort for setting up an extra AS ABAP system is reasonable, I do not recommend it.


      FES 3.0 has SAP UI 7.51 with SAPUI5 1.44 (maintenance) and FES 4.0 has SAP UI 7.52 with SAPUI5 1.48 and higher (innovation).

      FES 4.0 also offers now an AS ABAP 7.52 (with Gateway Foundation 7.52) as additional "instance" to run frontend server, which is recommended for SAP S/4HANA 1709.


  • Hello Oliver,

    not covered in this nice article was the usage of the frontend server in the cloud. An interesting topic in this context is the question, how do I deploy my set of Fiori apps to the cloud frontend server?

    I have checked our enterprise system and I cannot find one of the 53 apps listed for the business suite.

    Is there an add-on missing?


    Best regards, Stefan





      Hi Stefan,

      Cloud would be an extra blog.

      The "frontend server" in the cloud is called “SAP Fiori Cloud”. Looks pretty much the same for end users, as it uses the same UI5 shell, but is server side a different implementation.

      You can see an end user trial here:

      SAP Fiori Cloud for S4H documentation is here.

      Basically it is a SAP Cloud Platform Portal with at least one “Fiori Launchpad Site” in it defined. In this FLP site, you can reference Fiori apps from your account “catalog”, which can contain Fiori apps which are available from SAP, or custom apps deployed on SAP CP via SAP WEB IDE.

      Available Fiori Apps from SAP on SAP CP can be found here:

      In the SAP CP trial you cannot see any of the available SAP Fiori Apps by default.
      you need to sign up for SAP Fiori Cloud and your subscriptions has to be registered.


  • Hi Oliver,

    Currently we are an embedded frontend 4.0 with our S/4 HANA 1709 build but decided to go with a  hub model. Do we have a to uninstall the current embedded FES?. Our plan is to have full fronend/gateway  landscape.




  • Hi Oliver,

    Thanks for the blog, very good and informative indeed.

    I have a question though, would it be possible to install ABAP frontend with a S/4HANA On-Premise backend?

    Best regards


    • Hi Daniel,

      Do you mean to install an FES (based on ABAP) frontend with an S/4HANA on-prem backend? If so, yes, I should think so. I'm still new at the FES landscape options myself (we're deploying our own for the first time), but I believe what matters is that you have compatible versions of the Fiori apps installed on the FES for the version of backend you intend to connect to.