Typically each S/4 HANA implementation has a number of huge Excel sheets containing application details and its assignments to catalogs, groups, and roles. Unfortunately, these sheets get often out of sync causing most of the parts not to be up-to-date. Once they are out of date handling any catalog or role hanges becomes a nightmare.
As SAP Fiori developer or SAP basis specialist who in most cases is in charge of provisioning Fiori launchpad changes, you are the one responsible for keeping apps in order. You have two choices: either spend time maintaining spreadsheets or spend even more time discussing with project team members how to maintain them so they themselves can come up with consistent requests for changes. Either way, you end up spending more time on not doing what you are specialized in which can be frustrating.
Fiori Tracker takse away this repetitive, administrative task by presenting how existing apps are linked with existing catalogs and what impact will have the cahnges to catalogs. You get the view on the history of chagnes that gets logged with date and time stamp each time the change is made.
To have the Groups ready in Fiori launchpad requires effort from sevral parties:
Functional specialist – for requiremnts
SAP Fiori for Fiori Launchpad – configuration
SAP Basis specialist- for authorization roles setup
again Functional – for unit testing
In result, the whole process takes a number of stages and time and might lead to a situation where some of the groups are not unit tested. It is very easy to end up with the case where the groups that were not earlier checked are reported as groups that have issues. For example:
certain apps are missing
apps are not starting properly
Title or descriptions are diffrent then expected
Fiori Tracker helps to avoid this situatons and have a goup setup ready in one shot and without surprises.
Here is how:
1. For each Fiori app in scope of the project there is an information record with general data
So for starters with Fiori Tracker you can see whether th app is already included in the scope of the project. If it has an entry in Fiori Tracker the app was earlier agreed to be included in the scope and configured.
If the missing app is not in scope it requires additional steps and will take more time to setup comparing to just enabling the app that is already in place. You can see when was it included in scope (give a chance to identifie latecommers and allows to controle scope creep), provisioned in each system and how it is configured.
2. “To be” documentation for Fiori launchpad groups
3. Information who is responsible for testing and whether the test was done