Technical Articles
SAP Fiori for S/4HANA – Rapid Activation Task List Updates and Quick Guide
Updated blog – Individual quick guides for SAP S/4HANA 2020 and SAP S/4HANA 1909 are now available!
SAP Fiori Rapid Activation has been in place for 3 years now and within those three years we have been delivering multiple corrections or modifications to the process and task lists that help making your life easier when you are running the activation process of SAP Fiori apps.
One of the most recent changes is the automatic deployment of OData services in Co-Deployed mode that comes by implementing the latest version of note 2686456 – Fiori Setup: Content Activation for SAP Business Roles.
With the newly delivered innovations, when you navigate to the configuration options in step Activate OData Services in task list SAP_FIORI_CONTENT_ACTIVATION you will now notice that the text for this configuration step is now only referring to OData service TASKPROCESSING (for My Inbox app). This could cause some confusion as there are no options to select the processing mode for the rest of the OData Services, but this is part of the automation that has been delivered via the updates.
You no longer need to define Co-Deployed routing mode for OData services. Except for TASKPROCESSING service, the task list will automatically configure all OData services with Co-Deployed routing mode.
If you do not find the same texts as in the image, this means that the note has not been correctly implemented. To solve this problem you only need to run report NOTE_2686456_POST which will not only help update the texts in the configuration step but also update the documentation in task list SAP_FIORI_CONTENT_ACTIVATION.
Another common question while running Rapid Activation with the latest updates is: Where does system alias LOCAL_TGW for TASKPROCESSING service come from?
The answer is quite simple, as part of the updates delivered via notes, we have included an additional step in task list SAP_FIORI_FOUNDATION_S4 to create a specific system alias for TASKPROCESSING service.
The name of this alias has changed from <SID><CLNT>_PGW to LOCAL_TGW so you can quickly differentiate between an SAP Fiori implementation in SAP Business Suite and an SAP Fiori Implementation in SAP S/4HANA.
Updates (2021/04/06):
Rapid Activation task lists SAP_FIORI_FOUNDATION_S4 also offers options to:
- Configure FLP for SAP Easy Access Menu
- Configure FLP for Notifications
- Set Fiori 3 as default theme
- Activate and Configure FLP for Spaces and Pages
These tasks are delivered by implementing the latest version of the task list via notes.
If you wish to use the latest versions of the SAP Fiori Rapid Activation Task Lists, make sure you always apply the latest versions of the following notes:
| Task List | SAP Note |
| SAP Gateway – Activate OData Services (SAP_GATEWAY_ACTIVATE_ODATA_SERV) | SAP Note 2630153 – Fiori Setup: Improvements OData service activation task list |
| SAP Fiori – Initial Setup for Fiori Applications S/4 (SAP_FIORI_FOUNDATION_S4) | SAP Note 2712785 – Fiori Setup: Initial Setup for Fiori Applications S/4 |
| SAP Fiori – Content activation for SAP Business Roles (SAP_FIORI_CONTENT_ACTIVATION) | SAP Note 2686456 – Fiori Setup: Content Activation for SAP Business Roles |
| SAP Fiori – Content activation for Business Roles (SAP_FIORI_FCM_CONTENT_ACTIVATION) | SAP Note 2813396 – Fiori Setup: Content Activation for Business Roles |
| SAP_SAP2GATEWAY_TRUSTED_CONFIG SAP_GATEWAY_ADD_SYSTEM SAP_GATEWAY_ACTIVATE_ODATA_SERV SAP_GATEWAY_ADD_SYSTEM_ALIAS SAP_FIORI_LAUNCHPAD_INIT_SETUP SAP_GW_FIORI_ERP_ONE_CLNT_SETUP |
SAP Note 2510134 – Fiori Setup: Updates for task lists for Gateway/Fiori configuration |
| SAP_BASIS_SETUP_INITIAL_CONFIG (>= 7.52) SAP_SAP2GATEWAY_TRUSTED_CONFIG (>= 7.50) SAP_GATEWAY_ADD_SYSTEM (>= 7.50) SAP_GATEWAY_ADD_SYSTEM_ALIAS (>= 7.50) SAP_FIORI_LAUNCHPAD_INIT_SETUP (>= 7.50) SAP_GATEWAY_ACTIVATE_ODATA_SERV (>= 7.50) SAP_FIORI_FOUNDATION_S4 (>=752) |
SAP Note 2739383 – Improvements for Workbench/Customizing Requests used in task lists |
Additionally, you can now find the quick guides:
SAP Fiori Rapid Activation – Quick Guide to activate SAP Fiori in SAP S/4HANA 2020
SAP Fiori Rapid Activation – Quick guide to activate SAP Fiori in SAP S/4HANA 1909
Which you can download and keep handy while you run the Rapid Activation procedure in your projects. These quick guides aim to be used as a guiding document for your implementation projects.
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 comments.
Thanks,
SAP S/4HANA RIG
Great information and the SAP Fiori Rapid Activation – Quick guide to activate SAP Fiori is an excellent resource too!
Hi jorge
First of all thanks for this article. It is usefull
Do we have this rapid activation facility for 1709 initial shipment pack?
And is there any best practice composite notes to be installed for 1709.
Regards,
Bhasker Reddy
Hi Bhasker,
Rapid Activation is available on S/4HANA 1709 FPS01 or higher. You can find the central notes here:
1709: https://launchpad.support.sap.com/#/notes/2695653
1809: https://launchpad.support.sap.com/#/notes/2704570
1909: https://launchpad.support.sap.com/#/notes/2834415
Hi Jorge
Very nice blog. I would like to know how we will take the activation or ODATA service and the roles crated from Development system to the quality and to production. Do we need to run these task list in each of the system independently.
Br
Divya
Hi Divya,
You will find the steps required to move from DEV to PRD in this blog:
SAP Fiori for SAP S/4HANA – SAP Fiori Rapid Activation: Transport from Development to Production systems
Thank you Jorge Baltazar for the great document and guide.
I have been looking at performing the rapid activation process in a development system to begin checking the overall functionality of Fiori in S/4HANA 2020.
We currently are already using Fiori, but in a very limited capacity - currently only use Fiori for purchase order approval and that is the only app that has been activated.
That being said, there is already some system configuration/settings that were previously completed to support that purchase order approval app.
Is there any risk that some existing configuration/connection settings would be overwritten if we deployed Fiori with the rapid activation process? Are there any additional considerations that need to be taken into account if a business is already using Fiori in a limited capacity but is looking to implement Fiori end-to-end?
Appreciate your help.