Skip to Content
Technical Articles

SAP Fiori for SAP S/4HANA – SAP Fiori Rapid Activation: Transport from Development to Production systems

Relevant for S/4HANA 1909, 1809, 1709

With the release of SAP Fiori Rapid Activation back in 2018, SAP provided a procedure to mass activate SAP Fiori Apps. The focus of the early release of Rapid Activation was to be used mainly in Sandbox systems for the discovery and explore phases of a project based on the Activate methodology.

Based on the positive feedback from multiple customers SAP now provides transport options for the task lists in Rapid Activation meaning you can use this procedure in your Development system and transport content to your after-Development systems like QA, Pre-PRD and PRD. By doing this you will save time and effort when activating SAP Fiori in your landscape.

SAP has provided a central note with information on how OData services activated through task lists in Development system can be activated again in the Production System: SAP Note 2886433 – Fiori Setup: Activation of OData Services in Prod Systems with task lists. However, we are aware that you may need additional guidance depending on your project status, hence, the SAP S/4HANA Regional Implementation Group (RIG) has created a brief document explaining the procedure to move content from your Development system to after-Development systems based on the following procedure:

  • Run Rapid Activation in Your Development system with transport options active.
  • Move Transports to subsequent system
  • Run Rapid Activation with only a defined subset of tasks

By doing this, you will ensure your complete SAP Fiori landscape is active and configured with the same parametrization and the exact same content is available across your landscape.

You will find a detailed guide here: SAP S/4HANA Fiori Rapid Activation Transport Move To Production Strategy

Please note that for the described scenario we recommend defining a transportable development package and using this package while running Rapid Activation. Package reallocation is currently not covered by the task list but can be done manually through transaction SE03.

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.



You must be Logged on to comment or reply to a post.
  • Hi Jorge,

    Great reading. I found the document really clean and straightforward. I had this very question in my mind on what would be the best practices to avoid re-work or overwriting configs.

    I have to say, SAP is making the Fiori activation easy and fast which helps in the customer adoption.

    Thanks for sharing!

  • Thanks for this post, It’s a good path to follow for the implementation of the Fiori Rapid Activation in the whole landscape. Until recently I’ve had several doubts if I needed to implement these tasklist over and over again in every system, but with these approach it’s very clear and faster than ever to do the whole process.

  • Hi Jorge,
    your Blog & Document suggests Activation steps on After-Development systems.

    Does that mean cut out Activation steps have to be done on Production system – what if the Prod is not open?

    • Hi Deep,

      Yes, you need to run the steps in PRD. Overall this would be creating RFC’s and scheduling jobs, for this the system does not need to be open.

      When you run the task lists in PRD, if you select the tasks listed in the document, you do not need to have the system open as these tasks do not update/modify configuration in the system. All client dependent config is moved via transports.