Skip to Content
Author's profile photo Benjamin Hindelang

SAP Fiori for SAP S/4HANA 1709 – Architecture

Welcome back to the SAP Fiori in S/4HANA blog series brought to you by the S/4HANA Regional Implementation Group (RIG).

This blog provides a first overview on architecture and directs you to the basic sources of information. It is also part of a blog series about SAP Fiori for SAP S/4HANA 1709.

This blog refers to the following releases:

  • SAP S/4HANA 1709
  • SAP Fiori 2.0
  • SAPUI5 1.48
  • SAP NetWeaver 7.52

Preparation: Basic Sources of Information

You can familiarize yourself with the basic architecture concepts in SAP S/4HANA we recommend to work through the following sources of information:

Overview: Architecture Components

To familiarize yourself with the basic building blocks/components you need for using SAP Fiori for SAP S/4HANA 1709, please refer to:

SAP Fiori in SAP S/4HANA 1709 Overview

Note: Don’t be confused by the URL even though it contains SAP S/4HANA release 1511 in its name, all information is updated to release 1709

This overview diagram describes the basic setup for an SAP Fiori for SAP S/4HANA 1709 on premise installation:

Please make sure you also read through the following SAP note:

Landscape Deployment: SAP Fiori front-end server

SAP Fiori front-end server 4.0 is an add-on product version for SAP NetWeaver AS ABAP and delivers the front-end software components required to run Fiori 2.0 applications for S/4HANA 1709.

S/4 HANA Release




SAP Netweaver (Recommended)




SAP Fiori




SAP Fiori Front-End Server





Please refer to the following notes for more information on requirements:

Here you will find additional information concerning the landscape scenarios

Additional: Things to Check

You’ll find much more on our SAP Fiori for SAP S/4HANA wiki

Do you have any questions? Let us know in the comments section.



Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Bartosz Jarkowski
      Bartosz Jarkowski

      Great summary, thanks!



      Author's profile photo Chandrakanth Angannagari
      Chandrakanth Angannagari

      Hi, is it possible to


      1. start with Fiori as a embedded setup with S/4 and later move to a Hub model? What are the technical steps to do so
      2. start with Fiori on premise (hub or embedded) with S/4 and later move to Fiori on the cloud? What are the technical steps to do so
      Author's profile photo Chandrakanth Angannagari
      Chandrakanth Angannagari

      Also, with S/4 there is a strong dependency with Fiori (and the underlying netweaver) with the backend core. Thereby making the hub model not very flexible as the same system might not be compatible with other fiori apps of SAP Business Suite etc. Considering this there is traction towards moving to a embedded model. Can you please comment on this and also the performance aspects of such a setup?

      Author's profile photo Sundeep Sethi
      Sundeep Sethi

      Please check SAP Note

      2590653 - SAP Fiori front-end server deployment for SAP S/4HANA

      SAP recommends for landscapes with multiple SAP S/4HANA systems an embedded deployment of the SAP Fiori front-end server instead of a hub deployment, i.e. install the product version SAP Fiori for SAP S/4HANA together with the corresponding back-end product version SAP S/4HANA on the same system