Administration & Troubleshooting

Rapid Content Activation (STC01 Task Lists)

Rapid content activation is the set of SAP S/4HANA task lists, run in transaction STC01, that activate SAP Fiori launchpad content in bulk: OData services, ICF nodes, business roles and optionally test users. Rapid content activation works per business role or per catalog and replaces hundreds of manual activation steps, but it does not design roles.

Quick facts

Type
Automated configuration task lists (ABAP task manager)
Layer
Content, navigation & access
Run in
STC01 (task manager); runs monitored in STC02
Main task lists
SAP_FIORI_FOUNDATION_S4, SAP_FIORI_CONTENT_ACTIVATION, SAP_FIORI_FCM_CONTENT_ACTIVATION, SAP_FIORI_FCM_CATALOG_ACTIVATION
Prerequisite
Embedded SAP Fiori front-end server; hub deployment not supported
Who works with it
Basis administrators, SAP Fiori and security teams
Applies to
SAP S/4HANA on-premise and Private Edition
Layer: Content, navigation & accessWhere it sits ▾
Where it sits: L2 · Content, navigation & accessLayer: Content, navigation & access.L1L2L3L4L5L6BTP

Layer: Content, navigation & access

Open the architecture map →

Which rapid activation task lists exist, and in which order?

OrderTask listPurpose
0SAP_GW_FIORI_ERP_ONE_CLNT_SETUPGateway and SAP Fiori basic setup in one client
1SAP_FIORI_FOUNDATION_S4Launchpad setup: HTTP services, launchpad OData services, system aliases, caches, admin and user roles; run once in every system and client
2aSAP_FIORI_CONTENT_ACTIVATIONSAP business role templates: generates roles and optional test users, activates their services; meant for sandboxes
2bSAP_FIORI_FCM_CONTENT_ACTIVATIONCustomer business roles: activates services, updates role menus, can record OData services on workbench requests
2cSAP_FIORI_FCM_CATALOG_ACTIVATIONSame, per business catalog, for teams that separate UX, security and basis work

SAP supports these task lists from SAP Fiori front-end server 6.0 and SAP Fiori for SAP S/4HANA 1909 upward. Running them out of order is the most common cause of failed rapid content activation runs.

How do you run SAP_FIORI_CONTENT_ACTIVATION step by step?

  1. Implement the current task list notes (SAP documents SAP Note 2902673 as the overview).
  2. In STC01, enter SAP_FIORI_CONTENT_ACTIVATION and generate a task list run (F8).
  3. Select the SAP business roles, for example the purchaser template for a test of Alder Manufacturing's procurement scope. SAP advises background mode for many roles and no more than 100 roles per run.
  4. Keep the deployment mode at embedded (co-deployed) and enter a role prefix such as Z_.
  5. Optionally generate test users, one per role.
  6. Follow the run in STC02 and check the log for roles that failed.

The generated roles open the launchpad with the content listed for each role in the SAP Fiori apps reference library. Rapid content activation thus turns scoping in a sandbox into a hands-on review rather than a slide exercise.

What do rapid activation task lists transport, and what not?

  • Transported: activated OData services, if the task "Set transport options" runs in the development system; repository objects and cross-client settings.
  • Not transported: ICF node activation, RFC destinations, system aliases, users and role assignments. Repeat these in each system, for example by rerunning the task list.
  • Outside task lists: custom business catalogs, roles, spaces and pages follow their own transport tools.

Import requests in sequence from development to quality to production. Rapid content activation moves service activation through the landscape, but every system still needs its local technical setup.

What are common mistakes with rapid content activation?

  1. Activating every role. SAP explicitly advises against it; each role opens OData and ICF services that widen the attack surface. Pick roles from the reference library.
  2. Ignoring role prerequisites. Some roles need business functions switched on first and can cause the task list to dump.
  3. Using a hub front-end server. The task lists support only embedded deployment.
  4. Promoting generated template roles to production. They are for testing; production roles come from customer copies with reviewed authorizations in PFCG.
  5. Expecting a clean undo. Deactivating ICF services later needs separate reports for group processing of ICF services, described in SAP Note 1498575.

Most rapid content activation problems are scoping decisions made too broadly.

Rapid content activation vs. /IWFND/MAINT_SERVICE: what is the difference?

Rapid content activation (STC01)/IWFND/MAINT_SERVICE
Unit of workBusiness roles or catalogsOne OData V2 service
Also handlesICF nodes, roles, test users, role menusSystem aliases and ICF node of that service
Best forInitial setup and new scopeTargeted fixes and custom services
DeploymentEmbedded onlyEmbedded and hub

Rapid content activation is for activating scope in bulk; /IWFND/MAINT_SERVICE is for repairing or adding single services.

FAQ

Is rapid content activation available in SAP S/4HANA Cloud Public Edition?

No. In Public Edition, SAP operates the system and delivers activated content; customers assign business role templates in Maintain Business Roles. Rapid content activation applies to on-premise and Private Edition systems with an embedded SAP Fiori front-end server.

Should SAP_FIORI_CONTENT_ACTIVATION run in production?

No. It generates roles and test users from SAP templates, which suits sandbox scoping. For the development-to-production path, SAP provides SAP_FIORI_FCM_CONTENT_ACTIVATION, which works with customer roles and can record activated OData services on workbench requests.

Where do I see whether a task list run succeeded?

In STC02, the task list run monitor. It lists each run with the status of its tasks and their logs, so failed roles or services can be identified before the run is repeated.

Can I start rapid activation from the launchpad content manager?

Yes, as of SAP S/4HANA 2023 FPS01. The launchpad content manager can launch the rapid activation task list with selected catalogs or roles as criteria, which activates the services of all apps in that selection.

Sources

Applies to
SAP S/4HANA on-premise · SAP S/4HANA Cloud Private Edition
Last reviewed

SAP, SAP Fiori, SAPUI5, SAP S/4HANA, SAP BTP and other SAP products and services mentioned are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. This guide is independent and is not affiliated with, sponsored or endorsed by SAP SE.