Solution Documentation with the Fiori Tracker tool – all in one

SAP Solution Manager provides various tools and methods for implementing and maintaining both SAP and customer solutions. The Solution Documentation model is based on a hierarchical structure, which uses a solution as the single, central point of access for all Solution Documentation content.

help.sap.com

The process of documenting applications (and/or business processes) is a very important issue for organizations that use IT solutions for providing their business core services. It is also necessary during the Fiori apps implementation. SolDoc could be a good tool to store final documentation as a result of the work of several functional consultants.

https://www.contiba.com/app/uploads/2018/01/2018-01-16_11h00_25.png
That’s how typical documentation tree of Fiori implementation looks like (it’s pre-beginning). Neverending story…

With Fiori Tracker the only thing you have to do is to put a link to the tab you are interested in (f. e. applications, roles, business catalogs).

Sounds like a fairy tale?

It does, but the funny fact is that it’s at your fingertips!

Complete documentation of Fiori Applications stored in SolDoc using Fiori Tracker URL.

By clicking this stored link you can proceed to the right documentation.

There is the same solution for business catalogs and roles.

Hope you fell in love with our solution for storing documentation in the SolDoc! If you want to implement it in your company – just let us know!

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

Fiori Tracker architecture

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.

Clarity on responsibility for SAP Fiori applications

One of the major goals of project management is the clarity on responsibility.

Fiori Tracker makes it crystal clear who is responsible for each SAP Fiori application available through SAP Fiori Launchpad. The information is available in seconds directly from the application itself (with Fiori Launchpad plugin), or through the application card view.

All applications in scope can be found with a Google-like search function. The responsibility is determined based on the application stream assignment: Each application is assigned to the stream, each stream has named functional consultant assigned. Applications that belong to P2P stream have P2P functional consultant set as responsible and so on, depending on how you decide to set up your streams. This way in case of changes, in a functional consultant position, the assignment is passed through the stream assignment, and there is no need to update attributes of the application itself.
Same assignment rule is applied for Fiori Launchpad business catalogs, groups, and roles.

During the implementation phase, you will find this function useful whenever you will need to:

  • Set the scope for implementation, testing or for go-live readiness for each stream
  • Assign resolving issues resulting from testing the application
  • Make decisions on assignment to roles, Fiori launchpad business catalogs or groups

During support when:

  • Set the assignee for issues reported by end users

Report on SAP Fiori application usage – apps popularity

There is currently no way in SAP standard to report usage of SAP Fiori applications (see SAP notes below) meaning, users can’t run the report and have the list of most popular SAP Fiori applications.

This is something many people have been looking for since the beginning of the SAP Fiori offering. So we (at Nype) have prepared the solution, which is based on the SAP Fiori launchpad plugin and the catalog of all the apps in the scope – you have a clear view on all started application details and their link to SAP Fiori library id. The report runs in the central system (you can choose SAP Solution Manager for that) that collects data separately for each of your systems in your system landscape.

Application usage report – Architecture

Here is how the report looks:

You can install the “Apps usage report for SAP Fiori launchpad” by downloading the transport from GitHub:

https://github.com/fioritracker/installation

And following those two install guides:

https://help.fioritracker.org/1909SPS06/#/installation-guide/basis-steps

https://help.fioritracker.org/1909SPS06/#/installation-guide/plugin

The report was priceless during the implementation when testing. It was also a huge help when deciding on the priority of adjusting the apps after the upgrade. As well as deciding on the business impact when users reported issues with specific apps. We also used it to detect scope creep – this is especially important when the number of custom and extended apps grows, and the project is not tracking who is responsible for maintaining new apps.

SAP notes on usage reports in SAP standard:

  • 2586237 – Metrics about SAP Fiori Launchpad
  • 2444406 – Google Analytics Integration with SAP Fiori
  • 2506498 – Monitoring SAP Fiori Application Usage
  • 2469965 – Tracking usage of mobile applications with SAP Fior