SAP Fiori for SAP S/4HANA – Basic Configuration with help of Task Lists
UPDATE – Relevant for S/4HANA 1809, 1709, 1610, 1511
NOTE – You may still use these task lists for basic configurations in 1809 or lower, however, rapid activation method is preferred as described in note 2704570, following the architecture best practice for embedded S/4HANA deployments
If you have been working with Fiori technology for some time you will notice that currently it is easier to configure it than in earlier releases.
This is due to the implementation of configuration task lists in transaction STC01 which help perform all necessary configurations in an easy and simple manner and avoid as many errors as possible.
This blog will explain details around the usage of those task lists and on which server they should be executed.
When attempting to configure Fiori you first need to realize that there are different technologies involved, including:
- SAP Netweaver Gateway (which enables Odata protocol communication called up from the Fiori UI to access the back-end logic)
- SAPUI5 (HTML5 with SAP extensions, used in the Fiori Launchpad and Fiori apps) and
- Enterprise Search (for enabling search capabilities).
Fortunately, you can easily perform all the required configurations using task lists.
Configuration of the SAP Fiori Infrastructure
Following is a table including the necessary task lists and where to execute them in order to perform the basic configurations to get the Fiori infrastructure up and running:
|Task||Task List in STC01||Execute On||Description|
|SAP Gateway – Basic Configuration||SAP_GATEWAY_BASIC_CONFIG||Front-end Server||Performs basic configuration steps for SAP Gateway|
|SAP Fiori Launchpad Initial Setup||SAP_FIORI_LAUNCHPAD_INIT_SETUP||Front-end Server||Activate Launchpad OData and HTTP services on an SAP Gateway system|
|Create Trusted Connection from SAP System to SAP Gateway||SAP_SAP2GATEWAY_TRUSTED_CONFIG||Back-end Server||Creates a trusted connection from an SAP back-end system to the SAP Front-end Server (based on NW Gateway)|
|Enable Embedded Search||SAP_ESH_INITIAL_SETUP_000_CLIENT||Back-end Server||You use this task list for the automatic initial setup of Embedded Search in client 000|
|SAP Gateway – Add Backend System||SAP_GATEWAY_ADD_SYSTEM||Front-end Server||The task list creates or uses an existing trusted remote function call (RFC) destination, checks the single sign-on (SSO) profile parameters, configures the SSO ticket and creates a system alias.|
|SAP Gateway – Maintain System Alias||SAP_GATEWAY_ADD_SYSTEM_ALIAS||Front-end Server||Creates a system alias for an existing remote function call destination. Configure the remote function call destination as trusted.|
|Enable Embedded Search on working clients||SAP_ESH_INITIAL_SETUP_WRK_CLIENT||Back-endServer||Automatic initial setup of Embedded Search in working clients. This can take a long time, so start the task list in the background|
For detailed information on how to run these task lists refer to the Best Practices Guide MAA or the UI Technology Guides:
|UITECH OP1709UI Technology Guide for SAP S/4HANA, on-premise edition 1709||UITECH OP1709|
|UITECH OP1610UI Technology Guide for SAP S/4HANA, on-premise edition 1610||UITECH OP1610|
|UITECH OP1511 FPS02UI Technology Guide for SAP S/4HANA, on-premise edition 1511||UITECH OP1511 FPS02|
UPDATE – Running task list “SAP_ESH_INITIAL_SETUP_000_CLIENT” in S4HANA 1610 and 1709 is no longer required, you only need to run “SAP_ESH_INITIAL_SETUP_WRK_CLIENT”
Following is a table including the necessary task lists and where to execute them in order to perform the app implementation. Notice that each application will also require specific functional configuration steps which should also be reviewed.
|Task||Task List in STC01||Execute On||Description|
|SAP Basis – Activate HTTP Services (SICF)||SAP_BASIS_ACTIVATE_ICF_NODES||Front-end Server||Activate HTTP services (SICF) according to transaction SICF|
|SAP Gateway – Activate OData Services||SAP_GATEWAY_ACTIVATE_ODATA_SERV||Front-endServer||Activates OData Services|
For detailed information on how to run these task lists refer to the Best Practices Guide MAD or the UI Technology Guides.You can find additional information about the functional configurations required per app in the Fiori Apps Reference Library, however the high-level steps to configure the app are shown in the following table which you can also find in the Best Practices Guide MAD:
We also recommend reviewing the SAP Fiori for S/4HANA-10 Lessons Learned in S/4HANA 1511 projects blog.
Don’t know where to start? Try Getting Started with Documentation
Becoming a SAP Fiori for SAP S/4HANA guru
You’ll find much more on our SAP Fiori for SAP S/4HANA wiki
Do you have any questions? Let us know in the comments section.
SAP S/4HANA RIG
Interesting blog. Lots of valuable information. I like the last table consolidating the different aspects of automated procedures versus manual tasks.
Pleas keep up the good work! Really appreciate reading about it.
Maybe you can explore the following task in more detail "SAP_ESH_INITIAL_SETUP_WRK_CLIENT". I believe this is a crucial task that a lot of customers/partners have difficulties on accomplishing.
We are aware that some customers have had issues performing ESH activation. Fortunately, the required configuration steps are now clearly described in Best Practice Guide MAA. Overall, two task lists are needed for configuration:
While running this task list the most common issues are the ones we mention in the lessons learned post: SAP Fiori for S/4HANA – 10 Lessons Learned in S/4HANA 1511 projects 🙂
Hope this helps!
Great article, Jorge! You made my life a lot easier. 🙂
But is this task list also relevant for S/4 1709 ?
Thanks for this excellent blog!
I have the following question with regard to using the automated task lists. Suppose we use the automated task SAP_GATEWAY_ACTIVATE_ODATA_SERV to activate the required OData services in the development environment, is there any way we can add this to a transport request to move to the test environment? Or is it required to run the SAP_GATEWAY_ACTIVATE_ODATA_SERV task in the test and eventually in the production environment?
Our general recommendation is to run the task list per environment (DEV, QAS, PRD).
I understand sometimes following this recommendation is not always possible due to customer landscape requirements, but it is feasible to transport the Odata services activated by the task list.
These objects are generated as local objects for the user that ran the task list.
You can search these objects using transaction SE03 --> Change Object Directory Entries. Each of the activated services has 3 objects:
Make sure you add these objects to the TR so you won't have issues and note that the system alias assignment is not transported, hence you will need to run the task list to assign the system alias to the Odata service, so it may be easier to run the task list again as you already have the name of the active Odata services. If you don't have a list of active services you can use the abap program in this blog: https://blogs.sap.com/2017/11/30/fiori-for-s4hana-mass-odata-unassign/
Thanks a lot for your inputs Jorge! I will have the task list run in the individual environments (QAS and PRD) as per the recommendation.
I am quite confused - still. Maybe you can help me out. I was reading through different guides and also through this blog, but there are still some questions to be answered.
Currently I installed a Frontend Server 4.0 into a 1610 SPS04 system, so it is an embedded FES.
Now I am getting ready to configure the FES via task lists as stated above in this article. Questions here:
- How do I know precisely in which client the task list has to be executed? Yes, sometimes it is obviously (SAP_ESH_INITIAL_SETUP_000_CLIENT), but mostly to me it is not.
-- How do I know which task lists are mandatory in a hub-deployment and which task lists are mandatory in a embedded setup?
I appreciate your help and clarification 🙂
thank you for the information!
Do you know what can be done if one task list fails and running it again creates inconsistancys?
We exectued "SAP_FIORI_LAUNCHPAD_INIT_SETUP" and the second GATEWAY Phase (the one that activates the OData-Services) failed in the middle of the work. It assinged Local to INTEROP, the three page_builder services and transport then failed with the page_repository_cust_srv.
We ran it again and now in the SICF we only have the three repository services and interop, but the page services and Transport are missing but are in /IWFND/MAINT_SERVICE (with a grey traffic light for the IFC-node)
Is there any way to fix this without deleting the page services and adding them manually? (since we would have to open the producion system in order to do that... Something we really do not want to do - everything had worked fine in the test and quality system before...)
We recommend moving transports between systems so when you run the task lists in PRD with a subset of tasks they just "turn-on some switches", the recommended process is described here: https://blogs.sap.com/2020/05/20/sap-fiori-for-sap-s-4hana-sap-fiori-rapid-activation-transport-from-development-to-production-systems/
Looks to me that you are only having a problem with ICF node activation. So, assuming that you'll activate the same content as in QA and that OData system alias are already in place (co-deployed or routing based depending on your deployment), you could use report:
Process would be the following:
This report is a mass activation program for ICF nodes.
Thank you very much!
This does help us a lot, thank you!