Skip to Content
Technical Articles
Author's profile photo Jorge Baltazar

SAP Fiori for SAP S/4HANA – SAP S/4HANA Embedded Fiori Configuration for Multiple Client Systems

As embedded Fiori configuration is recommended in an SAP S/4HANA implementation, we have created a new document to assist the Fiori setup in a single system with the requirement of multiple clients.

In this document we attempt to solve the following questions:

  • What are the prerequisites for running Rapid Activation?
  • How to configure an initial client with Fiori Rapid Activation?
  • How to configure additional clients where the new client is copied from 000 without initial Fiori configuration?
  • How to configure additional clients where the new client is copied from an existing client with Fiori configuration?

You will find the answers to these questions in this document: SAP S/4HANA Embedded Fiori Configuration for Multiple Client Systems

Once all settings are done, you can use the generated transports from the initial client to move content to your upcoming systems. You’ll find the details of this procedure in this blog: SAP Fiori for SAP S/4HANA – SAP Fiori Rapid Activation: Transport from Development to Production systems

To find out more about the recommended deployment options in SAP Fiori you can take a look at the SAP Fiori Deployment Options and System Landscape Recommendations.

If you are interested in learning more about the SAP Fiori Rapid Activation procedure you can find more details here SAP Fiori for S/4HANA – Rapid Activation Task List Updates and Quick Guide

I’d like to thank my friend and colleague Van Vi  for his dedication to create this document.

Becoming an SAP Fiori for SAP S/4HANA guru

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

Let us know your questions in the comments section.

Thanks,

SAP S/4HANA RIG

Assigned Tags

      6 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Carlos Tolosa
      Carlos Tolosa

      Hi Jorge!

      Congratulations for such a good and useful article.

      However, this got me wondering about the S/4HANA Embedded Fiori deployment versus the Hub Deployment option that is still over the table.

      I find myself that the embedded deployment is so much easier and faster to handle from the Fiori perspective. My personal opinion from my own experience is that the the Hub deployment (one separated server instance for the Backend and another one for the Fiori Frontend) is an overcomplication and lots of extra steps and troubleshooting for the Fiori config and lots more of that for multiple client deployments.

      But I've seen quite a few organizations that are being offered with the Hub deployment by default, even today, regardless of their size, use cases or available infrastructure. I've even seen that offered by SAP itself with the SAP HANA Enterprise Cloud (HEC) services which still offer the Hub Fiori deployment by default even for small organizations that don't necessary require that.

      So, my actual question given this article is:

      Do we still need the SAP S/4HANA Hub Fiori Deployment in any case in 2021 whatsoever?. And finally, if this is not required then: Is there and process for successfully transitioning from the Hub to Embedded deployment?. Lots of savings can happen here.

      Regards,

      Carlos.

      Author's profile photo Jorge Baltazar
      Jorge Baltazar
      Blog Post Author

      Hi Carlos,

      Embedded deployments in SAP S/4HANA are the recommended deployment option since 2017, this is a topic known across all teams in SAP and has even become the standard in SAP S/4HANA Private Edition (and in the base contract for this deployment).

      If your HEC provider positions a Hub deployment I'd strongly recommend you question this proposal. However, there could be some exceptions (especially in HEC) where customers could still use Hub deployments depending on their contract specifications so double checking your contract is also recommended.

      On the migration from Hub to Embedded we do have documentation available and a step-by-step guide. You can find them here:

      Migrate SAP Fiori

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

      Hope this helps!
      JB
      Author's profile photo Jorge Baltazar
      Jorge Baltazar
      Blog Post Author

      Hi Carlos,

      I've discussed this internally and we would like to understand your experiences and current situation regarding the following statement:

      But I've seen quite a few organizations that are being offered with the Hub deployment by default, even today, regardless of their size, use cases or available infrastructure. I've even seen that offered by SAP itself with the SAP HANA Enterprise Cloud (HEC) services which still offer the Hub Fiori deployment by default even for small organizations that don't necessary require that.

      Can you please contact me via Linkedin or a DM in this platform so we can arrange a meeting with you?

      Author's profile photo Timothy Muchena
      Timothy Muchena

      Hi Jorge

       

      Thanks for the informative document.

      Regarding embedded deployment, how do you handle apps like My Inbox where you have workflows coming from 2 different S/4Hana systems?

       

      Kind regards

      Author's profile photo Pradeep Rawat
      Pradeep Rawat

      Hello Jorge,

      How can we achieve MyInbox app integrated to multiple System( S/4 HANA , HANA MDG, ECC ) in Embedded deployment for On-Premise deployment.

      Author's profile photo Pradeep Belagihally
      Pradeep Belagihally

      Hi Jorge,

      Does the hub deployment provide better user experience if the users are in multiple geographical regions. Is there an option to have multiple fiori front end servers (in multiple regions) connected to one central S/4 HANA instance.

      Thanks,

      Pradeep