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.
SAP S/4HANA RIG