Category: for SAP Fiori developers

We have designed Fiori Tracker components to enable flexible installation options. Depending on your SAP landscape setup and your organization constraints, you can deploy Fiori Tracker in the way that suits your project the best. The recommended Fiori Tracker architecture is shown below:

Fiori Tracker architecture

The tool can also be set to work directly on the SAP Gateway without the SAP Solution Manager – find all deployment options in section “Deployment options” of the Fiori Tracker manual.

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.

That is how typical Excel sheet for grouping and catalog assignments for SAP Fiori Launchpad applications looks like

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 the time maintaining spreadsheets, or spend even more time discussing, with project team members, how to maintain them so they 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 very frustrating.

Fiori Tracker takes away this repetitive, administrative task by presenting how the existing apps are linked with the existing catalogs and what impact the changes will have to the catalogs. You get the view on the history of the changes that get logged with date and time stamp each time the change is made.

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