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.
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 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 Note 2739383 – Improvements for Workbench/Customizing Requests used in task lists|
Additionally, you can now find the SAP Fiori Rapid Activation – Quick guide to activate SAP Fiori which you can download and keep handy while you run the Rapid Activation procedure in your projects. This quick guide aims 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.
SAP S/4HANA RIG