SAP Basis Notes
Fiori & UI Technologies •
/n/IWFND/MAINT_SERVICE /n/IWFND/ERROR_LOG /n/IWBEP/ERROR_LOG /n/IWFND/ROUTING ESH_COCKPIT /n/UI2/FLP_CUS_CONF /n/UI2/FLPCM_CUST

Deploying Embedded Fiori on SAP S/4HANA: STC01 Rapid Activation & Multi-Client Task Distribution

A concise 5-step STC01 Rapid Activation guide for Embedded Fiori on S/4HANA: Cross-client vs client-specific execution scoping, essential check/monitor T-codes, common short dumps with workarounds, and cache invalidation runbook.

1. 5-Step Rapid Activation Sequence (STC01) & Client Execution Scope #

The standard Rapid Activation process for SAP Fiori on SAP S/4HANA is executed sequentially across 5 Task Lists within transaction STC01:

Step Task List (STC01) Purpose & Key Operations Execution Scope Technical Notes
1 SAP_GW_FIORI_ERP_ONE_CLNT_SETUP Foundational Gateway Setup & Automatic ICF Activation
• Activates the global SAP Gateway engine
• Automatically activates all required ICF services (/sap/bc/ui5_ui5, /sap/bc/bsp, WebGUI, UI2, etc.) and core OData services
• Configures System Alias & Local RFC pointing to the current client		 EACH CLIENT
(or Transport)		 Execute on each client requiring Fiori access (or run on one client and transport). This task activates all ICF nodes automatically; manual activation in SICF is not required.
2 SAP_BW_SETUP_INITIAL_S4HANA Initialize S/4HANA Embedded Analytics
• Configures and activates the Embedded BW Client
• Installs essential InfoObjects & Hierarchies (0YEA_QUA_MON_DAY, 0WEEK_DAY, etc.) required by Analytical Fiori Apps		 ONCE ONLY
(BW Client only)		 Each S/4HANA system has strictly ONE BW Client (check via transaction RSA1 or table RSADMINA-BWMANDT). Execute only on the designated BW Client (e.g., Client 100). You must check "Force Installation" during the "Install essential BW Content" subtask.
3 SAP_ESH_INITIAL_SETUP_WRK_CLIENT Configure Enterprise Search (ESH) on SAP HANA
• Creates ESH Connectors to the SAP HANA database
• Generates search models for CDS Views and Business Objects
• Enables real-time search indexing for the current client		 EACH CLIENT Must precede SAP_FIORI_FOUNDATION_S4 to enable FLP search integration. Run in background mode to prevent timeout dumps.
4 SAP_FIORI_FOUNDATION_S4 Initialize Fiori Launchpad (FLP) Foundation
• Creates Local RFC Destinations (NONE, trusted) & System Alias (LOCAL)
• Integrates Enterprise Search (Step 3) into FLP
• Configures Spaces & Pages (Transaction /n/UI2/FLP_CUS_CONF)
• Generates foundational user/admin roles (Z_FIORI_FOUNDATION_ADMIN, Z_FIORI_FOUNDATION_USER)		 EACH CLIENT Required per client to establish client-specific foundation roles, system aliases, and Spaces & Pages configuration.
5 SAP_FIORI_CONTENT_ACTIVATION Activate Applications by SAP Business Roles
• Batch-activates OData services and ICF nodes for standard SAP_BR_* roles
• Generates customer business roles (prefixed with Z_BR_*) with authorization profiles in PFCG
• Optionally generates test users		 EACH CLIENT Always run in background mode. Split large role sets into batches of 20–50 roles to prevent memory exhaustion. *(For custom roles, use SAP_FIORI_FCM_CONTENT_ACTIVATION or transaction /n/UI2/FLPCM_CUST)*.

2. Essential T-Codes for Verification & Monitoring #

Reference table of Fiori-specific Transaction Codes used during activation, verification, and monitoring:

T-Code (SAP GUI) Name / Component Operational Purpose
/n/IWFND/MAINT_SERVICE Activate & Maintain Services Validate OData service catalog status, assign system aliases, and test endpoints via Gateway Client.
/n/IWFND/ERROR_LOG Gateway Hub Error Log Inspect Gateway-level errors when the Launchpad or apps return HTTP 400, 403, or 500.
/n/IWBEP/ERROR_LOG Backend Error Log Inspect backend OData provider errors (ABAP exceptions, runtime DPC/MPC errors).
/n/IWFND/ROUTING Service to System Alias Routing Verify OData service routing table points to the expected RFC destination and client.
ESH_COCKPIT Enterprise Search Admin Administer search connectors, inspect indexing progress, and diagnose search issues.
/n/UI2/FLP_CUS_CONF FLP Customizing Manage Spaces & Pages (SPACES_CUSTOMIZATION) and App Finder launchpad settings.
/n/UI2/FLPCM_CUST FLP Content Manager Verify catalog, tile, and target mapping integrity for customer roles.

3. Step-by-Step Short Dump Troubleshooting & Workarounds # 

                           COMMON SHORT DUMPS IN STC01 ACTIVATION
┌────────────────────────────────────────────────────────────────────────────────────────┐
│  Step 2: SAP_BW_SETUP_INITIAL_S4HANA ──────> Wrong BW Client / Missing "Force Install" │
│  Step 3: SAP_ESH_INITIAL_SETUP_WRK_CLIENT ─> TIME_OUT (Foreground execution / Heavy)   │
│  Step 4: SAP_FIORI_FOUNDATION_S4 ──────────> PXA_NO_FREE_SPACE / CX_SY_PROGRAM_NOT_FOUND│
│  Step 5: SAP_FIORI_CONTENT_ACTIVATION ─────> TSV_TNEW_PAGE_ALLOC_FAILED & TIME_OUT     │
└────────────────────────────────────────────────────────────────────────────────────────┘

1. Dump TIME_OUT (CX_SY_TIMEOUT) #

  • Affects: Step 3 (SAP_ESH_INITIAL_SETUP_WRK_CLIENT connector creation/indexing) and Step 5 (SAP_FIORI_CONTENT_ACTIVATION bulk OData activation).
  • Root Cause: Foreground execution exceeding rdisp/max_wprun_time (default 600s–1200s).
  • Workaround & Resolution:
    1. In transaction STC01, always select Execute in Background for Step 3 and Step 5.
    2. If dialog execution is required, temporarily set rdisp/max_wprun_time = 0 (unlimited) or 3600 (1 hour) via transaction RZ11. This parameter is dynamic and takes effect immediately without a system restart. Revert to default after activation completes.

2. Dump PXA_NO_FREE_SPACE #

  • Affects: Step 4 (SAP_FIORI_FOUNDATION_S4) and Step 5 (SAP_FIORI_CONTENT_ACTIVATION).
  • Root Cause: High-volume automatic compilation and loading of ABAP programs, classes, and CDS runtimes depletes the program buffer (abap/buffersize).
  • Workaround & Resolution:
    1. Open transaction RZ10, set abap/buffersize = 2000000 (2 GB), and restart the SAP instance before running activation.
    2. Run transaction SGEN (Generate ABAP Loads) in advance for components SAP_BASIS, SAP_GWFND, SAP_UI, and S4CORE to eliminate on-the-fly compilation overhead.

3. Dump TSV_TNEW_PAGE_ALLOC_FAILED #

  • Affects: Step 5 (SAP_FIORI_CONTENT_ACTIVATION) when activating large numbers of roles simultaneously.
  • Root Cause: Roll Extension or Heap memory exhaustion in the executing work process.
  • Workaround & Resolution:
    1. Split activation runs into batches of 20 to 50 roles.
    2. Open transaction SE38, run report RSMEMORY to dynamically expand memory quotas for the current session:
      • Roll Extension (Dia): Increase to 4000000000 (4 GB) or 8000000000 (8 GB).
      • Heap (Dia): Increase to 4000000000 (4 GB).
      • Press F8 / Transfer to apply changes immediately (no restart needed).
    3. Return to transaction STC02, select the interrupted session, and click Resume/Execute. Already activated services remain intact.

4. Step 2 (SAP_BW_SETUP_INITIAL_S4HANA) Failures #

  • Affects: Step 2 (SAP_BW_SETUP_INITIAL_S4HANA).
  • Root Cause:
    • Running the task on a secondary client (S/4HANA supports strictly one BW Client per system).
    • Failing to check "Force Installation", causing collision with pre-existing InfoObjects.
  • Workaround & Resolution:
    1. Identify the system's single designated BW Client via transaction RSA1 or table RSADMINA-BWMANDT. Execute exclusively in that client (typically Client 100).
    2. Under the "Install essential BW Content" subtask, ensure the Force Installation checkbox is checked.

5. Dump CX_SY_PROGRAM_NOT_FOUND / Missing Notes #

  • Affects: Steps 4 and 5, or when launching tiles on FLP.
  • Root Cause: Essential Fiori framework correction notes missing from the system.
  • Workaround & Resolution: Apply all prerequisites from the Composite SAP Note corresponding to the target S/4HANA release (e.g., Note 3336782 for S/4HANA 2023) prior to executing STC01.

4. Comprehensive Cache Invalidation Runbook #

When users encounter infinite loading spinners, missing tiles, or HTTP 403 / 500 errors after role modifications or activation, execute these four transactions sequentially:

1. Transaction: /n/UI2/INVALIDATE_CLIENT_CACHES   --> Invalidate UI2 client-level browser caches
2. Transaction: /n/UI2/INVALIDATE_GLOBAL_CACHES   --> Invalidate UI2 server-side global cache
3. Transaction: /n/IWBEP/CACHE_CLEANUP           --> Clear Backend OData metadata cache
4. Transaction: /n/IWFND/CACHE_CLEANUP           --> Clear Gateway Server OData cache

[!TIP]
Rebuilding UI5 App Index: If Fiori applications fail to load JavaScript modules or Component-preload.js, open transaction SE38 and execute report /UI5/APP_INDEX_CALCULATE with the option "Calculate for all apps".

5. Key SAP Notes for Rapid Activation #

SAP Note Title Scope
3336782 Composite SAP Note: Rapid Activation for SAP Fiori in SAP S/4HANA 2023 Master note for S/4HANA 2023
3143687 Composite SAP Note: Rapid Activation for SAP Fiori in SAP S/4HANA 2022 Master note for S/4HANA 2022
3085127 Composite SAP Note: Rapid Activation for SAP Fiori in SAP S/4HANA 2021 Master note for S/4HANA 2021
2686456 Fiori Setup: Content Activation for Business Roles Detailed guide for SAP_FIORI_CONTENT_ACTIVATION
2303900 Latest Information about BW Setup in S/4HANA Systems Single BW client rule & SAP_BW_SETUP_INITIAL_S4HANA
2636754 Composite Note for SAP S/4HANA Embedded Analytics Embedded Analytics notes and fixes for S/4HANA
2453516 New Installation of SAP S/4HANA - Central Note for Fiori Setup Core architecture and embedded deployment guide
2866227 Troubleshooting for Fiori Rapid Content Activation Comprehensive error catalog and issue resolutions