Use case: Identifying Fiori launchpad groups that were not tested

To have the Groups ready Fiori Launchpad requires effort from several parties:

• Functional specialist – for requirements
• SAP Fiori for Fiori Launchpad – configuration
• SAP Basis specialist- for authorization roles setup
• again, Functional – for unit testing

As a result, the whole process takes a number of stages, a lot of 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 different than expected

Fiori Tracker helps to avoid these situations and have a group set up ready in one shot, without any surprises.

Here is how:

1. For each Fiori app in the scope of the project, there is an information record with general data

So, for starters – you can see whether the app is already included in the scope of the project. If it has an entry in the Fiori Tracker, the app was earlier agreed to be included in the scope and configured.

If the missing app is not in the scope it requires additional steps and will take more time to set up, comparing to just enabling the app that is already in place.

You can see when was it included in the scope (give a chance to identify latecomers and allows to control 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