Source of template: www.infograpia.com
When it comes to S/4HANA reporting, it is often understatement that introducing a new reporting strategy with new tools like SAP Fiori or SAP UI5 apps often means a significant change in the way users are accessing and using SAP.
Therefore, change management can play an important role to drive user acceptance when implementing a new reporting strategy. The following key areas might help you to define the appropriate mix of measures in this context:
- Overall SAP User Interface (UI)/User Experience (UX) strategy: ideally, your S/4 reporting strategy is embedded in your overall SAP UX/UI strategy to ensure that users have a coherent and homogeneous user experience across all access points and devices. Examples in this context: use of Fiori Launchpad as single point of access (not just SAP applications but also other related third-party applications to support your business or IT processes), use of Fiori apps vs. SAP GUI/Business Client or supported devices for UI/UX.
- Openness and willingness to change: user acceptance always plays a key role when introducing a new UI/UX and reporting tools. Therefore, you should ask yourself before rolling-out your new UI/UX (e.g. Fiori-based) “how open are our users for a new front-end/user interface?” or “how willing are users to learn and adopt a new front-end?” All benefits and advantages of a new Fiori-based UI using Fiori Launchpad and Fiori apps on different devices such as PC, tablets and smartphones can easily be lost when users are not ready for it. It often needs a strong commitment top down for senior management to the different teams to overcome resistance and enable the transition from the “old” to the “new” world. Thus, appropriate measures like information sessions, user trainings, etc. should be part of every S/4HANA project plan.
- Implementation budget: the budget is a critical factor in every project. Since the new SAP UI/UX and reporting capabilities can offer significant benefits for business processes, enough budget should be allocated. However, all reporting requirements should be part of a thorough cost-benefit analysis before being implemented. Examples in this context: use of S/4 Embedded Analytics or additional SAP BI tools like Analytics Cloud or BO
- SAP GUI “legacy”: An often underestimated factor relates to the simple question how long an organisation is already using the “traditional” SAP GUI. In other words, the ability to change is often substantially influenced by user habits and the previous “transactional” way of using the SAP GUI whereas the new role-based way of using a Fiori-based UI often means a significant mind shift.
In many cases S/4HANA reporting is strongly linked to the new area of SAP UI/UX using SAP Fiori and SAP UI5. In contrast, the legacy of the classic SAP GUI is still ubiquitous and often impacts the way of accessing SAP, especially when SAP GUI has already been used for many years. Therefore, I would definitely recommend to pay close attention to change management and define appropriate measures in this context.
*Please note that this blog post was already shared on LinkedIn