This blog will explain how you can execute a rapid activation of a set of FIORI lighthouse apps.
Questions that will be answered are:
- Which apps can be used for rapid setup?
- How to execute the rapid activation of FIORI lighthouse apps?
This blog assumes you have finished the basic activation of embedded FIORI on S4HANA, which is explained in this blog.
FIORI lighthouse apps
FIORI lighthouse apps are enabled for rapid activation. On the FIORI reference library site click on the Lighthouse scenario link to get a PDF full of all possible apps you can activate:
In the app finder you can also search for specific lighthouse apps:
Rapid activation of FIORI lighthouse app
We will take the following app as example to execute the rapid activation: app ID F1600A: Manage Purchase Contracts (Version 2):
In the implementation information scroll down to the authorization information section:
For now you can ignore the catalog and business group. Important here is the business role: SAP_BR_PURCHASER.
Goto transaction STC01 and select task list SAP_FIORI_CONTENT_ACTIVATION:
In the scope definition select the needed role SAP_BR_PURCHASER:
In the task list set the mandatory parameters process mode to co-deployment and Prefix to Z. Now start the task list execution and be patient. This might run up to 10 minutes.
This task list will now activate all ODATA services for the app group (not only for this single app, but the complete group!). It will activate all SICF nodes for the app group (yes, again the whole group). And it will generate the PFCG authorization role SAP_BR_PURCHASER.
If the task list is finished, assign the role SAP_BR_PURCHASER to your user ID.
Start the FIORI launchpad (transaction code /UI2/FLP):
You see that the tile Manage Purchase Contracts is visible. Since we activated a complete group, also the other tiles are immediately visible.
Clicking on the Manage Purchase Contracts tile gives immediate result:
This shows we can activate complete group of apps that immediately work, with minimal effort.
Bug fix OSS notes
Bug fix notes to apply: