Describing SAP S/4HANA

The general system roles in the SAP Fiori system landscape do not change when moving to SAP S/4HANA. The SAP Fiori launchpad running in a client still connects to the FES via the SAP Web Dispatcher. What changes are the capabilities of the BES, which now has optimized code for SAP HANA as an SAP S/4HANA. General information about the FES can be found in the SAP Note 2590653 – SAP Fiori front-end server deployment for SAP S/4HANA.

All application types are available for SAP S/4HANA (S4H). The important difference to the SAP Business Suite is that there is only one architecture type for all application types. All applications act like transactional apps communicating via SAP Gateway over the FES with the BES now an S4H. Only the classic applications and in some scenarios the SAP Fiori search connect directly to the S4H.

The hub deployment option will be supported also for SAP S/4HANA 2025. Nevertheless, there might be restrictions regarding the availability of future new features. Some features might only be available in the embedded deployment due to technical reasons.

The recommended deployment option for SAP S/4HANA is the embedded deployment. The main reason is that with SAP S/4HANA all data and functions reside in one system. A hub system for routing requests to certain back-ends is no longer needed. In addition, many configuration steps for SAP Fiori get easier when having everything in one system.