Skip to Content
Technical Articles

SAP Fiori for SAP S/4HANA – Transition from Standalone to Embedded Deployment in SAP S/4HANA

Relevant for S/4HANA 1909, 1809, 1709

As you may already be aware, the recommendation for SAP S/4HANA Fiori Architecture is to deploy in Embedded mode as described in the SAP Fiori Deployment Options and System Landscape Recommendations

We are aware that you may have started your SAP S/4HANA journey with a Standalone Deployment of Fiori for S/4HANA and a common question we receive for this scenario is how to move from a Standalone to an Embedded deployment of Fiori in S/4HANA now that deployment recommendations have been updated.

The Regional Implementation Group for SAP S/4HANA has had interesting experiences helping customers in their move from Standalone to Embedded Fiori deployments and as a result of these experiences we have released a step-by-step document containing the important details on how to run this content migration.

Overall, the main steps are:

  • Identify active content in Frontend Fiori system
  • Identify custom content in Frontend Fiori system
  • Install SAP Fiori Frontend components in Backend S/4HANA system
  • Transport custom content into Embedded Fiori system
  • Activate Fiori content in Embedded Fiori system
  • Update SAP Web Dispatcher configuration
  • Perform UAT

One important aspect of the proposed approach is that at a given moment you will have both the Standalone and Embedded Fiori deployments coexist, which will help you minimize the impact to your daily operations if you are have a large Fiori footprint.

All of this and more you will find in the step-by-step guide Moving from Standalone to Embedded Deployment in Fiori for SAP S/4HANA

Becoming a SAP Fiori for SAP S/4HANA guru

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.



You must be Logged on to comment or reply to a post.
  • Thanks, Jorge. Nice Blog!

    What are key pointers and deciding factors to make Fiori go from Standalone to Embedded, like pros/cons etc.? Any reference or blog on this topic available?

  • Hi Jorge,

    I have a hub deployment with two backend systems (S4 and CAR) and i'm planning going to an embedded deployment (s4 and fiori integration) with another separate backend system (CAR).

    Did you recommend this? Do you think there's may be any issues with this deployment?


    Thanks, regards!

    • Hello Jorge and Jorge 🙂


      I have the same question, can we implement S/4 hana as front end server for back end system CAR( Customer Active Repository for retail) ? As to do so we need to install the UI addon for CAR in S/4 system.


      Many thanks if any one of you can answer!

  • Hello Jorge,

    We are on standalone Fiori for S/4HANA 1610, Can you please suggest what is the procedure and steps required for converting Standalone  Fiori to Embedded Fiori for HANA1610  FPS2?

    We don't want to upgrade right now, I have already installed the required UI add-ons on my backed system, which has similar version as standalone Fiori.




  • Hi Jorge

    We are planning to migrate from Hub to embedded and plan to run both deployments concurrently until we are sure that the hub is working fine.

    We, however, have one S/4HANA backend system which will be the embedded system. Is it possible to have this system act as the Frontend server (Embedded) and at the same time be the backend system for the existing Hub FES? What are the risks involved if there are any?



    • Hi Timothy,

      This is possible and it is described in the document, you can continue to use the Hub system until you decide to completely switch to Embedded and best approach is to leverage Web Dispatcher to run a seamless transition.

      If you maintain full control of the access URL's to Hub/Embedded systems there should be no risks, however, if you release both accesses to end-users at the same time you may experiment higher loads in the system depending on the usage of both Fiori launchpads.