As you know, SAP Fiori is the latest user interface from SAP that satisfies all modern design principles. SAP systems, such as the SAP S/4HANA or SAP Business Suite are using Fiori UX to provide an personalized, adaptive and role-based user experience. All Fiori apps are HTML5 based and come with a rich user interfaces for modern web business applications and responsiveness across browsers and devices.
In the past the primary focus for the businesses has been to meet business requirements and not to deliver a great user experience. As a result many customers still rely on ABAP and Web Dynpro based classic transactions. The development and maintenance of these applications gets further complicated with each additional custom enhancement.
Since 2014 SAP Fiori is available at no separate charges, customer have a good opportunity to improve their user experience. Since Fiori UX got evolved more and more customers want to find out how to transform their existing applications and how to identify areas where UX improvements provide the most impact.
In this blog series we want to help you to identify the potential areas where SAP Fiori would benefit your business most.
As a starting point for our SAP Fiori journey blog series you should get a good overview which transactions are commonly used in your SAP system. The following steps explain how to use the SAP workload monitor transaction ST03 to identify the most commonly used applications in your SAP system. You further learn how to prioritize this list of applications to identify Fiori adoption and UX improvement possibilities .
Steps to follow
1. In production ECC execute transaction SM37, select job name ‘SAP_COLLECTOR_FOR_PERFMONITOR’ and make sure the job, which is needed to collect analytical data in your system, is scheduled
2. If the background job exists, continue with step 13, if not, schedule it as follow (steps 3 - 12):
3. Run transaction SM36
4. Enter the following name in the field ‘Job Name’: SAP_COLLECTOR_FOR_PERFMONITOR
5. Select the ‘Step’ button and enter the name ‘RSCOLL00’ for the ABAP program
6. Save the configuration
7. Go back to the previous screen by clicking the green ‘Back’ button
8. Save the configuration
9. Define the start condition by clicking the "Start Condition" button
10. Click "Immediate" and select the "Periodic job" checkbox
11. Click the "Period values" button and choose “Hourly”. Then click on the “Save” icon
12. Save the configuration
13. In production ECC go to T-Code ‘ST03’. If you encounter ‘No system load data available’, the background job SAP_COLLECTOR_FOR_PERFMONITOR is not correctly configured (if so repeat steps 3-12 and try it again)
14. Select ‘Workload’ -> ‘Total’ for the last month
15. Select ‘Transaction Profile - Standard’ and in the right panel under ‘Aggregation’ choose the option ‘Transaction’ (if this option is greyed out it is already selected)
16. Now you see a list of reports and transactions and the number of executed dialog steps. This list provides us with some indication how frequently the application is used, however you have to consider that the number of dialog steps are not always a correct indication as it is influenced by the user and the the type of application. We recommend to export the data to a spreadsheet and edit the list to your personal needs. To do so click on ‘Export’, select ‘Spreadsheet’ and save the list in XLSX format
17. In Excel you can now customize the spreadsheet by extending your list with additional attributes that help you to identify applications where UX improvements provide the most impact. You can e.g. add new criteria that support your rating of the most used transactions in your system. Such criteria could for example be your business rating, the user satisfaction associated with the application, its UI complexity and many more.
You can find some more information in the following videos from SAP:
We would like to hear your feedback. What is the outcome in your case? What transactions are worth implementing in Fiori and SAP UI5? Please add your comments below!