Overview
After small break I would like to present you some details on how to activate Fiori Fact Sheet apps in S/4HANA environment.
Firstly, I would like to refresh your memory with small summary of available Fiori app types:
Transactional apps does not require any additional technical preparation, so we can use them just after activating in our Gateway System. Fact sheet apps is a different story. You won’t see them as tiles in Fiori Launchpad and to make them working it is required to perform additional configuration.
If you want to read more about Fact Sheet apps, please have a look on following blogs:
Getting (SAP Fiori) Fact Sheets Right
SAP Fiori - App Types (Transactional, Fact Sheets, Analytical)
Fiori Factsheet Configuration on S/4 HANA 1511 FPS01
Part 2 of my blog dealt with NW Gateway activation and during execution of task list to enable Fiori application we encounter several issues. If you want to know how to solve them, today’s blog should make everything clear.
Fiori Search
As mentioned earlier Fact Sheet apps does not show any tile on Fiori Launchpad. They are usually launched when executing search, but you can also call them from other apps. In our current configuration the search engine is not working, so you won’t be able to find anything. But with a bit of time we can make our Launchpad work like a Google 🙂
We start with preparation of two roles, by coping them to customer namespace on S/4HANA system.
SAP_ESH_LOCAL_ADMIN – For administrators to configure embedded search
SAP_ESH_SEARCH – For end users to use embedded search functionality
Next in t-code SFW5 we need to check if following Business Functions are activated:
The whole configuration is simplified and we just need to execute two Task List. Log in to client 000 and execute the first one, which does the initial setup of Embedded Search and prepares data model.
Last step of this task list runs for long time and therefore it is scheduled as background job and we can check progress in SM37:
When the job is finished and task list run has green status, we can log in to our working client and execute next one - SAP_ESH_INITIAL_SETUP_WRK_CLIENT, which is responsible for creating search connectors and activating ICF services. But just before executing, we need to prepare additional connection to database in DBACOCKPIT, which we provide as a parameter.
Another required parameter is Software Component. For S/4HANA installation it is SAPAPPLH. Depending on Fiori apps we want to activate, we can decide either to create all search connectors or only pre-selected based on Fiori app requirements.
When job is finished we can go to transaction ESH_COCKPIT, where we can see the status of each connector.
As the whole configuration went fine and the status for each connector is set to Active, we can check our configuration by executing report ESH_TEST_SEARCH.
If the setup is OK, report will return the G/L Account details.
Now let’s log in to our front-end system and activate OData services for fact sheet app. For the purpose of our test I selected one app that shows G/L Account details.
In Part 2 the activation of this app failed, but this time there was no issues!
Does it mean our setup is complete? Unfortunately, not. When we log in to Fiori Launchpad, we can see it allows us only to search for an apps.
And when we type our G/L Account, that we successfully tested before, nothing is found.
Why? When executing search, Fiori Launchpad is sending request to front-end server. But our connectors are deployed on S/4HANA system and therefore no results can be returned. To enable search functionality, it is required to implement SAP Web Dispatcher, that will redirect request to appropriate system.
Web Dispatcher
Installation of Web Dispatcher is very simple and it's done by SWPM, therefore I will show you only the minimal required configuration, which boils down to proper definition of systems in Web Dispatcher profile.
After restart we can log in to Fiori Launchpad and we immediately notice a difference. Now we can search for many different objects – not only apps.
What happens if we type our G/L Account?
Our search is now working as expected!
This is the fourth part of my blog series about S/4HANA installation and maintenance. You can access previous parts by using following links: Part 1 – Maintenance Planner, System Installation and Update Part 2 – SAP NW Gateway and Fiori Launchpad Part 3 – Best Practices Content Activation Part 4 – Fact Sheet apps, Fiori Search and Web Dispatcher Part 5 – Upgrade to 1610 Part 6 – Fully Activated Appliance on Microsoft Azure Part 7 – Fiori Launchpad SAML Single Sign-On with Azure AD |
- SAP Managed Tags:
24 Comments
