Tag: testing

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:

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

Imagine loving the ease of recording Jira tickets while testing… Report your issues with SAP Fiori apps directly from Fiori Launchpad or an application itself. SAP Fiori applications are identified fully – not only with URL, but with full friendly name and description. All relevant data like SAP system id, application name and application library id […]

Imagine loving the ease of recording Jira tickets while testing! Report your issues with SAP Fiori apps directly from Fiori Launchpad or an application itself. SAP Fiori applications are identified fully – not only with URL but with full friendly name and description.

All relevant data like SAP system id, application name and application library id get filled automatically. The screenshot gets saved and attached to the Jira issue by clicking the checkbox.