TL;DR: There is now a new task list SAP_FIORI_FCM_CATALOG_ACTIVATION to activate apps by business catalog, the sub-level of a business role. While the task list is run manually in your Development environment, there’s an option to have follow-up automated activation of catalogs in the rest of your system landscape when the catalog is transported.
There is now a new task list SAP_FIORI_FCM_CATALOG_ACTIVATION to mass activate apps by Business Catalog.
Task list SAP_FIORI_FCM_CONTENT_ACTIVATION in transaction STC01
IMPORTANT: Content activation task lists are only relevant to SAP S/4HANA Cloud, private edition and SAP S/4HANA on-premise customers. Like most of our rapid activation tooling, they work best for customers using an embedded FES (Fiori Front-end Server) .SAP S/4HANA Cloud, public edition customers are not affected.
In this blog post you will learn:
Since SAP S/4HANA 1709, the best practice has been activating apps by business role using rapid activation task lists. Separate tasks lists were provided for activating:
Each business role consists of one or more business catalogs. Each business catalog contains one or more apps.
With now over 3K SAP Fiori apps, 10K classic UIs, and more than 600 Business Roles released for SAP S/4HANA, some SAP business roles are now quite large. For example, in SAP S/4HANA 2023 the General Ledger Accountant includes 94 SAP Fiori apps and 152 classic UIs, collected into 36 business catalogs.
Some customers have requested that app activation be permitted on the business catalog level, i.e. at a sub-section of a business role.
Why? There are many approaches to SAP Fiori implementation.
Some customers want to grant a whole business role, some want to start with a small business role and add functionality over time. Activating a catalog at a time lets you build your role over time so you can minimize the effort of removing not-yet-wanted catalogs and apps from the role.
Hint: It’s also very handy for the occasional business catalog that is not directly assigned to a SAP Business Role. For example, business catalog SAP_BASIS_BC_ESH Enterprise Search contains some optional tools for managing the search. You can use the task list to activate the catalog, and then assign it to a custom business role.
Some customers have central maintenance teams who can execute everything needed for creating business roles for SAP Fiori. While others split responsibilities into separate teams. Catalog content activation can help you if you want to maintain strict segregation of duties between your UX, Security, and Basis teams.
For example,
There are number of ways you can organize your role update process. This is one possible scenario:
Example high-level process for launchpad content maintenance in a segregated duties scenario
Worth knowing: Official documentation for the task list is planned to be released with SAP S/4HANA 2023 FPS01 in the SAP Help Portal – SAP Fiori Overview – Set up and Configure SAP Fiori – in section Rapid Activation of SAP Fiori.
Hint: All example screenshots in this blog post were taken in a SAP S/4HANA 2022 FPS02 Fully Activated trial from SAP Cloud Appliance Library at https://cal.sap.com
The use case example: You have one or more apps that are in the same catalog and you want to activate them. Currently when you attempt to launch the app you see an empty screen. You have determined this caused by a missing service activation. Refer to FAQ section below and question: What symptoms might a business user see that suggest a service is not activated?
Example of an app which is not working because the services have not been activated
You run the task list in transaction STC01.
Select the task and press the Generate Task List Run button.
Generating a task list run in transaction STC01
Select the catalog(s) you want to activate. You can type/paste in a list of catalogs or select them from the existing catalogs in the system.
Use the Fill Parameters button of the relevant task to choose your business catalogs
You can select SAP business catalogs or custom business catalogs.
Choosing business catalogs from the catalogs in your system
Just as you do with role activation, nominate a transport package.
Showing the task to set the transport options and the Fill Parameter button to nominate the package
Hint: Our suggestion from S/4HANA RIG is to consider using the same package for all catalig activations. It can makes life somewhat simpler if you need to split or recombine roles.
Start the task list – you can run it in dialog mode (if you only have a few catalogs) or in background mode (if you have a larger list)
Example of starting the task list with the Start/Resume task list button
IMPORTANT: Never activate all catalogs! Many catalogs are industry-specific or for processes you will never run at your site. Avoid creating unnecessary overhead.
Check your task list has completed successfully.
Example of checking the task list status and log
You can also do a final check in the Launchpad Content Manager (transaction /UI2/FLPCM_CUST) to confirm the catalog is active.
Example of checking the catalog service activation status in the Launchpad Content Manager
As a final check you should check the app from the SAP Fiori launchpad.
That is you:
Example of the app which is working now that the services have been activated
IMPORTANT: As usual the task list is run manually in your Development system. If you would like the catalog activated automatically when it is transported through your environment this is now possible. Refer to the attachments on SAP Note 3383609 – Fiori Setup: Automated activation of OData Services in Prod Systems with task list for the prerequisites and the process to be followed.
You must be on SAP S/4HANA release 1909 or higher.
From SAP S/4HANA 2023 FPS01 the task list will be provided as part of your solution.
In releases prior to SAP S/4HANA 2023 FPS01 you need to add the task list to your system – this is 3 step process.
Running program NOTE_3339909 in transaction SA38
Example of running program NOTE_3339909 as a test run
Example of test run simulation log of program NOTE_333909
Example of running program NOTE_3339909 in update mode
Example of success log of program NOTE_3339909
Example of transaction SNOTE showing both SAP Notes are completely implemented
Yes.
A user might see an error when they launch the app that mentions a service activation issue.
A user might see a blank page when they launch the app.
The app partially appears but some features are not working. When the user checks App Support there is mention of an app activation error.
You can use the Launchpad Content Manager – i.e. transaction /UI2/FLPCM_CUST. Navigate to the catalogs tab. Find your catalog and confirm the content in catalog. Use the Check Services feature to check the Service Activation Status. Service activation status can be:
Example of a checking a catalog in the Launchpad Content Manager showing the catalog has service activation errors
You can check the Content in Catalog pane to see which apps are affected.
Example showing checking which apps have service activation errors in the Content in Catalog pane of the Launchpad Content Manager
Activating a catalog automatically when it is transported through your environment is possible. You will need to implement BADI CTS_IMPORT_FEEDBACK and mark your catalogs for transport.
Refer to the attachments on SAP Note 3383609 – Fiori Setup: Automated activation of OData Services in Prod Systems with task list for the prerequisites and the process to be followed.
No change.
The remaining apps in the catalog are activated.
Not easily. Technically you can go to transactions /IWFND/MAINT_SERVICE and SICF and manually de-activate the nodes. This is possible, if time-consuming.
Existing users are not affected. You still need to include the catalog in their business role before they can launch the apps.
Technically yes … but in practice DO NOT DO THIS. Why? There is a very high risk of activating many more apps that you want, and as mentioned earlier, turning them off again is high effort.
You’ll find much more on the community topic page for SAP Fiori for SAP S/4HANA
Other helpful links in the SAP Community:
Brought to you by the SAP S/4HANA Customer Care and RIG.