SAP Fiori Infrastructure setup
I have recently gone through a lot of content for SAP Fiori on S/4 HANA. What I observed is that there is material and MA* guides available for a central hub deployment but it is much less when it comes to an embedded deployment. Though they can be leveraged for an embedded deployment, SAP Fiori implementation and apps activation is relatively easier in an embedded scenario and not all steps from the central hub scenario are applicable. In this blog post, I am making an effort to detail steps involved from Basis perspective for an embedded deployment on S/4 HANA.
SAP Fiori infrastructure can be setup by executing the tasklists available through STC01. Tasklists are client-specific though they can have cross-client tasks within them. They can be monitored from transaction STC02.
Tasklist 1: SAP_GW_FIORI_ERP_ONE_CLNT_SETUP –
- Activates Gateway
- Create SAP system alias LOCAL with RFC destination ‘NONE’ and is flagged at ‘Local GW’. It is captured in a customizing transport request
- Creation of RFC destination and alias mapping, HTTP service activation
- The following services are activated –
- /UI2/FIORI – node group
- If a transportable package is selected, Odata service activation is captured in a workbench transport request.
To run SAP Fiori Launchpad, following services are to be active –
For running SAP Fiori launchpad designer as an administrator, the following services are needed in addition:
- Following reports are scheduled to run periodically in background
Tasklist2: SAP_FIORI_FOUNDATION_S4 –
- Activates the following HTTP services for SAP Web GUI
- Activates the following HTTP services for SAP Fiori
- Creates aliases ‘FIORI_MENU’ and other source system aliases for SAP Fiori system and does target system alias mapping
- Activates following services
- Creates following Z roles
Tasklist 3: SAP_ESH_INITIAL_SETUP_WRK_CLIENT –
- Activates following services that are essential for running Enterprise Search
- Select Models to Create Connectors – choose SAPAPPLH
- Updates software components
- Creates search connectors for the selected models of software component and indexes them
Enterprise search related steps after client copy –
ESH_COCKPIT gives error saying ‘Current client is a copy of another client’ after a client copy.
Try to run the tasklist SAP_ESH_ADJUST_AFTER_CLIENT_COPY. If it fails, run the next task list SAP_ESH_RESET that resets the Enterprise Search to the initial state in your working client.
Run the initial setup task list SAP_ESH_INITIAL_SETUP_WRK_CLIENT now.
SAP Fiori apps activation
SAP Fiori apps configuration data can be retrieved from SAP Fiori apps library –
Apps can be searched with App ID or name of the app or the Odata service name. Select the app to view the details of that app.
‘Implementation Information’ tab gives information that is needed to activate the app. Firstly, check whether it is applicable for your version of S/4 HANA and select the version aptly.
- Installation dropdown shows the software component the app comes with.
- Configuration dropdown lists the services, aliases, target mappings, catalogs, roles and search connectors that correspond to an app.
Activation of Transactional Apps –
Transactional apps have one or more OData services and ICF nodes to be activated. Few number of apps can be activated manually.
To activate Odata service, go to transaction /n/iwfnd/maint_service. Choose Add Service and give the service name. For an embedded deployment, Co-deployed box needs to be checked and no system alias should be given. Choose all the selected Odata services and select Add service, mention the name of the package that should constitute the apps. It prompts for a Workbench request.
To activate ICF nodes, go to SICF and activated the required ICF nodes.
In case of number of apps to activate, tasklists can be utilized. Multiple tasklists have tasks to activate app related services. There are tasklists to activate Odata service and ICF nodes separately which can be utilized for simpler way of activation – SAP_GATEWAY_ACTIVATE_ODATA_SERV & SAP_BASIS_ACTIVATE_ICF_NODES.
Activation of Analytical Apps –
Similar to transactional apps that involve activation of Odata services and ICF nodes. BW client needs to be setup, as per note 2289865 – Configuration steps for SAP S/4HANA Analytics.
Activation of Factsheet type of Apps –
In addition to Odata service and ICF node activation, factsheet apps have a search connector that has to be configured. Name of the search connector(s) can be found under the Configuration drop down of the app in the apps library.
If ESH tasklist is executed with SAPAPPLH software component, search connectors for most apps are already setup. The same can be validated from the ESH_COCKPIT, look for the required search connector in Find. If it is not available, it can be created by choosing Create option. Select the required Software component from dropdown and all the search connectors pertaining to that component are listed. Select the required ones and choose Create Connector.
Activation of Design Studio type of Apps –
Design studio apps have a BEx query in addition to service activation. Some queries are already available in the system, the same can be checked by executing the query from RSRT. If it is not available, it needs to be activated from RSOR.
Activation of SAP GUI type of Apps –
SAP GUI type of apps usually have a system alias to be maintained by the basis team. The alias name can be known from apps library. It has to be maintained in /iwfnd/routing and is captured in a customizing transport request. In the case of a multi-client SAP system, the TR needs to be copied to other clients for the app to function as expected.
Activation of Webdynpro type of Apps –
Webdynpro type of apps have BEx queries to be activated, ensure that they exist and are active in the system. In addition, they can also have a System alias mentioned in the ‘Technical Configuration’ section. This system alias has to be maintained in /iwfnd/routing for the app to function as expected.
|Issue with My Inbox app||
Error ‘Tasks Façade note implemented for provider’ occurs while accessing My Inbox app.
My Inbox app should have a system alias assigned with Software component as /IWPGW/BWF. Go to SPRO – SAP Netweaver -> SAP Gateway -> OData Channel -> Configuration -> Connection settings -> SAP Gateway to SAP system -> Manage SAP system alias – create a system alias with software version as /IWPGW/BWF, assign it to the Odata service from /iwfnd/maint_service.
Reference – Snote # 2704570
|Error: found in negative cache||
Error in negative cache on selecting any line item for Material documents in app F1077. Same error can be seen in a few other apps as well.
Additional ICF services referenced in the browser console log need to be activated.
Reference – Snote # 2480245
|Error due to missing configurations||Some apps have configuration activities performed by the functional team in addition to service activation and target mappings. Some configuration steps are detailed on apps library or in SAP Notes. When the app does not function as expected, the same could be logged either in SLG1 logs or /iwfnd/error_log or /iwbep/error_log.|
|No System Alias found||If there are no system alias errors, check the logs to see which alias it is looking for. Ensure that Odata services are activated with Co-Deployed Processing mode unless for apps that have special requirement on alias like My Inbox. If it is an SAP GUI or Webdynpro type of app, check the apps library to see if it has a system alias to be maintained.|
|BEx query output does not give decimal values||Number of decimal places in the output can be maintained in the transaction CUNI.|
|Backend error occured||
Certain apps give error as ‘Received “[-1002] expected …. The complete batch was ‘.
This can be resolved with kernel upgrade.
In summary, these are the relevant Basis activities involved in setting up infrastructure for activation of SAP Fiori apps in an embedded deployment on S/4 HANA. I shall update the post based on my learnings.
Please leave your feedback in the comments section.