Technical Articles
SAP Fiori for SAP S/4HANA – Transition from Standalone to Embedded Deployment in SAP S/4HANA
Relevant for S/4HANA 2022, 2021, 2020, 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.
Thanks,
SAP S/4HANA RIG
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 Amit,
You can find this information in the SAP Fiori Deployment Options and System Landscape Recommendations document. Please note that this document was recently updated and a summary of the updates is available in the following blog: SAP Fiori Deployment Options – Updates with SAP FES 6.0
Thanks Jorge! I appreciate your inputs.
Hi Jorge,
We are in process of upgrading the Fiori system [Standalone (1610) to Embedded Fiori to (1909)]
Need answers for below things and any help will be appreciated
Thanks and Regards
Swamy
Hi Jorge
i have a separate Fiori hub deployment. i want to convert ERP to S/4 HANA with embedded Fiori.
any procedure to convert (before/during/after SUM phase) Fiori frontend HUB to embedded?
Fiori is one horrible UI.... It hinders productivity and most of my clients straight away hate it. Period
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.
Thanks,
Sid
Hi Sid,
You can follow the steps outlined in the document, the only difference is the task lists you will use in your 1610 system as Rapid Activation is not available for this version.
You'll find those task lists here: https://blogs.sap.com/2016/10/12/fiori-s4hana-basic-configuration-help-task-lists/
Moving content and transports, identifying active content, and configuring Web Dispatcher is exactly the same.
Regards,
JB
Thanks Jorge, I'll give it a try.
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?
Thanks
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.
Thanks Jorge.
Much appreciated!
Kind regards
Hello Jorge, hello people.
Is there any official document or help that explains the reverse process?, Scenario: migration from Fiori Embedded deployment to Fiori Standalone.
Thanks in advance.
Hi Edwar,
Unfortunately, there is no such document and I don't think there will be as the overall strategy is to move Fiori to Embedded deployments.
What you could do is activate Launchpad from scratch in your new Standalone system (FLP + OData services + System Alias + system trust need to be activated/configured from scratch in your standalone system), once done you can move required transports (with UI personalizations, extensions, custom catalogs and groups) and you'll be ready.
Ok, Thank you Jorge.
Hello Jorge,
is there a newer version of the step-by-step guide Moving from Standalone to Embedded Deployment in Fiori for SAP S/4HANA or is the linked version from November 2019 the current one ?
Thanks in advance!
Ralph
Hi Ralph,
Steps are the same for newer version as well. I think the document in this blog covers all aspect for systems 1709 or newer.
Hope that helps.
Thanks,
Sid
Hi Jorge,
We are planning to upgrade 1709 to 2020 and also move from Standalone to Embedded deployment. Please suggest if we upgrade first and later move to Embedded model or migrate to Embedded and upgrade.
Thanks,
HK
Hi Hari,
I would say in your case it is better to do embedded migration first and then do the upgrade.
It does have some advantage like you don't need to setup dual n+1 landscape for both back-end and front-end (standalone). Also per SAP the embedded foot print is pretty small. Also 1709 is mature enough to do embedded migration (fewer issues than 1610 or lower version)
Hope that helps.
Thanks,
Sid
Thanks Sid for the response, I agree updating one environment would be easier compared to two.
Hi Jorge,
We're currently moving a Fiori Hub to Embedded following the guide http://bit.ly/2Jjsq5y
On page 54, it says to identify custom packages and developments to generate a transport request. It occurs that this is a quite old Fiori installation with a massive amount of catalogs, groups, etc. How can we create a massive transport including all the customer objects created so far?
It has been recently upgraded to 2021 but its installation dates 2013.
Thank you,
Andre