Use case: How to get an overview of how the User Acceptance Tests (UAT) for the SAP Fiori apps is going?

With the Most frequently used apps function of the Fiori Tracker, SAP S/4 HANA implementation, that project manager is getting, is a perfect overview of how the UAT is progressing.

Please, take a look at the screenshot of this function:

Note the columns with the application start count:

  • In total (“Total”)
  • For last calendar week (“Last calendar week”)
  • For the current day (“Today”)

With a large number of the applications to be tested, the information, on whether any user has run the app, gives a good indicator of how the testing is progressing.

The function has a filleting for:

  • Functional area
  • Application type

So, it is a valuable source of information for every manager to see, what is the activity for different functional areas. The statistic can be generated per business line and used for status meetings on test progress. It also gives a glance at how performing the tests team members are occupied at the time.

The records for each run are collected as long, as the plugin is enabled. Also, all other statistic analyses can be performed. The statistics can also take under the consideration the data from other aspects covered with the Fiori Tracker like:

  • sign-offs from “Sign off” functionality
  • assignments to roles or catalogs

Use case: Enforcing naming conventions for groups, catalogs, and roles

Each set of the implemented SAP Fiori apps will require grouping them into the Fiori launchpad catalogs and groups. In projects with functional streams, a number of functional leads (3-7) come up with their set of groups depending on their stream users needs.

The consistent naming convention, that is shared between the streams, will speed up the process of dealing with catalogs and groups later when other team members, like the SAP Fiori developers or Basis specialists, start handing them in the process of support and maintenance.

To address that need Fiori Tracker has a function of enforcing the naming conventions. By default, it enforces a fixed prefix:

ZC_* for catalogs and ZG_* for groups.

It can be also set to enforce the stream linkage in the following form:

ZC_P2P_*, ZC_O2C_*.

All this enables speedy navigation in other tools like SAP Fiori designer. Entering a fixed prefix allows listing all custom catalogs and business groups. Extending it with the stream name limits the list to a particular stream which later, when different team members manage the catalog, proves to be very handy.

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.

List of applications in the scope filtered by the application name

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.

General view of Fiori application details

2. “To be” documentation for Fiori launchpad groups

3. Information who is responsible for testing and whether the test was done

Use case: Finding out the test users for specific business roles

Each SAP S/4 HANA implementation project team member or support team member conducts the tests. On a daily basis, each specialist runs numerous test cases. Whenever it is testing during official test phases, or replicating the issue that the end user encountered, there is a need to access the system with the user, that has the respective business roles.

As Fiori Tracker holds the repository of all business roles it is also the best place to keep the link of the roles to the test users.

This simple view, that is available in 2 clicks, saves a lot of time as the SAP team members get the correct uses in seconds.