Skip to Content

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

1511

1610

1709

SAP Netweaver (Recommended)

7.50

7.51

7.52

SAP Fiori

1.0

2.0

2.0

SAP Fiori Front-End Server

2.0

3.0

4.0

 

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.

Thanks,

SAP S/4HANA RIG

To report this post you need to login first.

2 Comments

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

  1. Sandip Agarwalla

    Hello Benjamin

    Thanks for this info. I have few questions

    1) Where do I find relevant info for v1610 ?

    2) Why is the FES has a separate naming conventions like 3.0/4.0? After all its a Gateway server with all the UI components? Or is it different than a regular Gateway with UI-Add ons?

    Best Regards

    Sandip

    (0) 

Leave a Reply