SAP Fiori for SAP S/4HANA - Rapid Activation Transport Move to Production Strategy
PUBLIC
SAP Fiori for SAP S/4HANA Rapid Activation
Transport Move to Production Strategy
How-To-Guide
Version: September 2025
SAP Fiori for SAP S/4HANA Rapid Activation
Transport Move to Production Strategy
How-To-Guide
Version: September 2025
© 2024 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 2 / 30
Document History
The following table provides an overview of the most important document changes.
Table 1
Version Date Description
1.0 April 22, 2020 Initial Version
1.1 May 19, 2020 Style corrections
1.2 December 22, 2020 General update
1.3 September 27, 2021 General update
1.4 March 31, 2022 General update
1.5 November 22, 2024 General update for SAP S/4HANA release 2023
1.6 December, 2024 Corrections and clarifications
1.7 September 9, 2025 Further corrections and clarifications
Document History
The following table provides an overview of the most important document changes.
Table 1
Version Date Description
1.0 April 22, 2020 Initial Version
1.1 May 19, 2020 Style corrections
1.2 December 22, 2020 General update
1.3 September 27, 2021 General update
1.4 March 31, 2022 General update
1.5 November 22, 2024 General update for SAP S/4HANA release 2023
1.6 December, 2024 Corrections and clarifications
1.7 September 9, 2025 Further corrections and clarifications
© 2024 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 3 / 30
Table of contents
1 Introduction ........................................................................................................................................................... 4
1.1 How the transport of Rapid Activation works ..........................................................................................................................5
2 References ............................................................................................................................................................. 7
3 Prerequisites ......................................................................................................................................................... 9
4 Run SAP S/4HANA Fiori Rapid Activation in Development System ..........................................12
4.1 Task List: SAP_GW_FIORI_ERP_ONE_CLNT_SETUP .................................................................................................... 13
4.2 Task List: SAP_FIORI_FOUNDATION_S4 ................................................................................................................................ 15
4.3 Task List: SAP_FIORI_CONTENT_ACTIVATION.................................................................................................................. 17
4.4 Task List: SAP_FIORI_FCM_CONTENT_ACTIVATION ................................................................................................... 18
4.5 Task List: SAP_FIORI_FCM_CATALOG_ACTIVATION ................................................................................................... 19
4.6 Additional Information: Other Rapid Activation tools ................................................................................................... 20
5 Run SAP S/4HANA Fiori Rapid Activation in subsequent systems ............................................23
5.1 Task List: SAP_GW_FIORI_ERP_ONE_CLNT_SETUP................................................................................................ 24
5.1 Task List: SAP_FIORI_FOUNDATION_S4 ............................................................................................................................ 26
5.2 Task List: SAP_FIORI_CONTENT_ACTIVATION ............................................................................................................. 28
5.3 Task List: SAP_FIORI_FCM_CONTENT_ACTIVATION ............................................................................................... 29
5.4 Task List: SAP_FIORI_FCM_CATALOG_ACTIVATION ............................................................................................... 29
Table of contents
1 Introduction ........................................................................................................................................................... 4
1.1 How the transport of Rapid Activation works ..........................................................................................................................5
2 References ............................................................................................................................................................. 7
3 Prerequisites ......................................................................................................................................................... 9
4 Run SAP S/4HANA Fiori Rapid Activation in Development System ..........................................12
4.1 Task List: SAP_GW_FIORI_ERP_ONE_CLNT_SETUP .................................................................................................... 13
4.2 Task List: SAP_FIORI_FOUNDATION_S4 ................................................................................................................................ 15
4.3 Task List: SAP_FIORI_CONTENT_ACTIVATION.................................................................................................................. 17
4.4 Task List: SAP_FIORI_FCM_CONTENT_ACTIVATION ................................................................................................... 18
4.5 Task List: SAP_FIORI_FCM_CATALOG_ACTIVATION ................................................................................................... 19
4.6 Additional Information: Other Rapid Activation tools ................................................................................................... 20
5 Run SAP S/4HANA Fiori Rapid Activation in subsequent systems ............................................23
5.1 Task List: SAP_GW_FIORI_ERP_ONE_CLNT_SETUP................................................................................................ 24
5.1 Task List: SAP_FIORI_FOUNDATION_S4 ............................................................................................................................ 26
5.2 Task List: SAP_FIORI_CONTENT_ACTIVATION ............................................................................................................. 28
5.3 Task List: SAP_FIORI_FCM_CONTENT_ACTIVATION ............................................................................................... 29
5.4 Task List: SAP_FIORI_FCM_CATALOG_ACTIVATION ............................................................................................... 29
© 2024 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 4 / 30
This document explains how to manage transport of SAP Fiori activations for SAP S/4HANA
Cloud Private Edition and SAP S/4HANA on-premise.
All screenshots in this document have been taken using SAP GUI for HTML. However, you can optionally run
the steps using SAP GUI for Windows or SAP GUI for Java.
VERY IMPORTANT: The task lists and tasks listed in this document are based on SAP S/4HANA 2023 FPS01
and FPS02. For official advice and further guidance for your SAP S/4HANA release and FPS, refer to the SAP
Note "Composite SAP note: Rapid Activation for SAP Fiori in SAP S/4HANA <release> <FPSxx>" for your SAP
S/4HANA release and FPS.
1 Introduction
This document provides the steps required to run SAP Fiori rapid activation in the Development system,
capture changes to transport requests, and, after transport, apply the captured changes to subsequent
systems in your solution landscape. Additional manual tasks that must be applied directly in subsequent
systems are clarified.
IMPORTANT: SAP Fiori Rapid Activation is relevant to SAP S/4HANA systems deployed with an
embedded Fiori Front-end Server (FES). Embedded Fiori Front-end Server deployment mode has been the
recommended deployment for SAP S/4HANA since 2017. Refer to SAP Whitepaper SAP Fiori Deployment
Options and System Landscape Recommendations and SAP Note 2217489 - Maintenance and Update
Strategy for SAP Fiori Front-End Server
This document explains how to manage transport of SAP Fiori activations for SAP S/4HANA
Cloud Private Edition and SAP S/4HANA on-premise.
All screenshots in this document have been taken using SAP GUI for HTML. However, you can optionally run
the steps using SAP GUI for Windows or SAP GUI for Java.
VERY IMPORTANT: The task lists and tasks listed in this document are based on SAP S/4HANA 2023 FPS01
and FPS02. For official advice and further guidance for your SAP S/4HANA release and FPS, refer to the SAP
Note "Composite SAP note: Rapid Activation for SAP Fiori in SAP S/4HANA <release> <FPSxx>" for your SAP
S/4HANA release and FPS.
1 Introduction
This document provides the steps required to run SAP Fiori rapid activation in the Development system,
capture changes to transport requests, and, after transport, apply the captured changes to subsequent
systems in your solution landscape. Additional manual tasks that must be applied directly in subsequent
systems are clarified.
IMPORTANT: SAP Fiori Rapid Activation is relevant to SAP S/4HANA systems deployed with an
embedded Fiori Front-end Server (FES). Embedded Fiori Front-end Server deployment mode has been the
recommended deployment for SAP S/4HANA since 2017. Refer to SAP Whitepaper SAP Fiori Deployment
Options and System Landscape Recommendations and SAP Note 2217489 - Maintenance and Update
Strategy for SAP Fiori Front-End Server
© 2024 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 5 / 30
1.1 How the transport of Rapid Activation works
SAP Fiori rapid activation enables you, as a system administrator, to quickly activate SAP Fiori apps in your
system by running a series of task lists to perform the main activities. These task lists apply the current best
practice recommendations for establishing your SAP Fiori launchpad, launchpad features, launchpad content
(apps, transactions, and other classic UIs), and layouts. These tasks lists include:
1. SAP_GW_FIORI_ERP_ONE_CLNT_SETUP – To run the basic activation of SAP Gateway and SAP Fiori
Launchpad
2. SAP_FIORI_FOUNDATION_S4 – To setup the basic configurations of SAP Fiori in SAP S/4HANA
3. SAP_FIORI_CONTENT_ACTIVATION – To mass activate SAP Fiori apps in your SAP S/4HANA system by
delivered SAP Business Role
4. SAP_FIORI_FCM_CONTENT_ACTIVATION - To mass activate SAP Fiori apps in your SAP S/4HANA
system by custom business role
5. SAP_FIORI_FCM_CATALOG_ACTIVATION – To mass activate SAP Fiori apps by business catalog
All task lists contain client-specific (also known as “client dependent”) and cross-client (also known as
“client-independent” or system-wide) configuration tasks.
a) Examples of cross-client tasks are: HTTP service activation, OData service creation/activation.
b) Examples of client-specific tasks are: business role generation, test user creation.
Task lists can be re-executed whenever needed without side effects as, by default, the existing configuration
is not overwritten.
IMPORTANT: After running the task lists, you can make further adjustments to your SAP Fiori launchpad
using the recommended rapid activation tools. Refer to the section 4.6 Additional Information: Other
Rapid Activation tools. You typically make these changes in your Development system and capture any
additional changes to transport requests.
Transport options are included in all task lists to capture transportable configurations to transport requests.
Using transport requests to move transportable configurations from system to system:
• Ensures consistency across your landscape
• Minimizes configuration effort in subsequent systems
VERY IMPORTANT: Regardless of what is captured in transport requests, system-specific execution of task
lists is always required to apply system-specific changes. For example, to activate system-specific ICF nodes
for OData services. That is:
1. You run the task lists in your Development system.
2. Changes are captured by the task lists to transport requests ready for release.
3. You release and transport the transport requests to subsequent systems in your solution landscape.
4. You run the task lists again in the subsequent system to apply the transported changes and related
system-specific activities.
1.1 How the transport of Rapid Activation works
SAP Fiori rapid activation enables you, as a system administrator, to quickly activate SAP Fiori apps in your
system by running a series of task lists to perform the main activities. These task lists apply the current best
practice recommendations for establishing your SAP Fiori launchpad, launchpad features, launchpad content
(apps, transactions, and other classic UIs), and layouts. These tasks lists include:
1. SAP_GW_FIORI_ERP_ONE_CLNT_SETUP – To run the basic activation of SAP Gateway and SAP Fiori
Launchpad
2. SAP_FIORI_FOUNDATION_S4 – To setup the basic configurations of SAP Fiori in SAP S/4HANA
3. SAP_FIORI_CONTENT_ACTIVATION – To mass activate SAP Fiori apps in your SAP S/4HANA system by
delivered SAP Business Role
4. SAP_FIORI_FCM_CONTENT_ACTIVATION - To mass activate SAP Fiori apps in your SAP S/4HANA
system by custom business role
5. SAP_FIORI_FCM_CATALOG_ACTIVATION – To mass activate SAP Fiori apps by business catalog
All task lists contain client-specific (also known as “client dependent”) and cross-client (also known as
“client-independent” or system-wide) configuration tasks.
a) Examples of cross-client tasks are: HTTP service activation, OData service creation/activation.
b) Examples of client-specific tasks are: business role generation, test user creation.
Task lists can be re-executed whenever needed without side effects as, by default, the existing configuration
is not overwritten.
IMPORTANT: After running the task lists, you can make further adjustments to your SAP Fiori launchpad
using the recommended rapid activation tools. Refer to the section 4.6 Additional Information: Other
Rapid Activation tools. You typically make these changes in your Development system and capture any
additional changes to transport requests.
Transport options are included in all task lists to capture transportable configurations to transport requests.
Using transport requests to move transportable configurations from system to system:
• Ensures consistency across your landscape
• Minimizes configuration effort in subsequent systems
VERY IMPORTANT: Regardless of what is captured in transport requests, system-specific execution of task
lists is always required to apply system-specific changes. For example, to activate system-specific ICF nodes
for OData services. That is:
1. You run the task lists in your Development system.
2. Changes are captured by the task lists to transport requests ready for release.
3. You release and transport the transport requests to subsequent systems in your solution landscape.
4. You run the task lists again in the subsequent system to apply the transported changes and related
system-specific activities.