This blog covers latest information and known issues for the SAP S/4HANA 2025 Fully-Activated Appliance, delivered via SAP Cloud Appliance Library (SAP CAL).
The overview blog for the appliance can be found here.
The known issues for older appliance releases are here: 2023 / 2022 /
If you would like to ask a support question, please do so in the SAP CAL Community.
Technical Topics
Initial system performance after instance creation or re-activate
When you create an instance or suspend / re-activate it, the system performance will be slower, especially within the Fiori Launchpad. Also, the first click on a Fiori tile will be significantly slower. This is due to initial caching in the system and will become faster if you continue working.
Other performance tuning tips are:
- Choose the cloud provider location nearest to you (for good network latency)
- The demo users contain a relatively large number of roles and Fiori tiles. You can copy these demo users in TCode SU01 and adapt accordingly e.g. remove roles, create your own roles / Fiori catalogs, or personalize the Fiori launchpad (see also the SAP Fiori Rapid Activation demo guide on the appliance demo page).
Note: SGEN has been performed to pre-compile ABAP coding.
Initial demo users (S4H_.... and others eg. BPINST) are locked
This works as intended and helps to increase the security of newly created appliances. Please log on with DDIC or SAP* and unlock the desired dialog users. They usually still have the password Welcome1, hence, it is recommended to assign a new (strong) password after unlocking them. Another alternative is copying the default users to your own user IDs.
Transport system (STMS) is not configured by default
Please check the SAP standard documentation how to configure the transport system in a new system.
Client 400: Fiori not fully configured
In client 400, only the generic Gateway service is activated, ie. you can log on to the Fiori launchpad but will encounter errors in Fiori or the App Finder.
To correct it, please follow the below steps in client 400 with a dialog user with SAP_ALL authorizations (unlock BPINST and assign SAP_ALL, or create your own suited dialog user):
1. tCode /nSTC01: Run task list SAP_FIORI_LAUNCHPAD_INIT_SETUP . If the task list execution halts with a warning about ambiguous RFC destination names, re-start the task list execution (F8 key).
2. tCode /nSTC01: Run task list SAP_FIORI_FOUNDATION_S4. If the task list execution halts with a warning about ambiguous RFC destination names, re-start the task list execution (F8 key).
3. tCode /n/IWFND/MAINT_SERVICE: Search for service ZPAGE_BUILDER_PERS and assign the system alias LOCAL to it in the right lower pane. This will fix the issue with loading catalogs in the Fiori App Finder.
4. Optional: Generate "Z-roles" out of the standard SAP_BR... roles using the task list SAP_FIORI_CONTENT_ACTIVATION in STC01 (please see the respective documentation for details)
Issues with specific business scenarios
Fiori Content Manager (transaction /UI2/FLPCM_CUST): ABAP dump when assigning a catalog to a role
Symptom:
In /UI2/FLPCM_CUST > Catalog tab > Search for a catalog > Click “Show usage in roles” (upper pane) > Click “Assign role” (lower pane) > Choose a role and click OK > Runtime error “OBJECTS_OBJREF_NOT_ASSIGNED_NO” occurs
Solution / Workaround:
Before starting the above sequence, switch once from the catalogs tab to the roles tab and then back to the catalogs tab; then the error does not occur.
Data Migration Cockpit
The demo scenarios for "direct transfer" are not available with the initial release of the SAP S/4HANA 2025 Fully-Activated Appliance.
Bluesky
