Skip to Content

This is the second blog in a series that will look at the following five perspectives that are changing in the SAP world:

Two years ago, I wrote this blog series during SAP TechEd 2012 that explored which options SAP customers had when looking to improve the user experience of their SAP users.

The good news is that the options have not really changed, but the great news is that SAP has taken what were “technical frameworks” at that point  and incorporated them into products. Specifically, Fiori has gained momentum and, in line with Sam Yen’s UI strategy, it is now being used for all new applications (that I know of) and is being used to renew many more. Beyond this, SAP has continued to invest in SAP Screen Personas, which can be used to simplify or tweak SAPGUI and has removed the dependence on SilverLight – so it’s much easier to deploy.

I have even heard people whispering that this dynamic duo (Fiori/Personas) might become the primary way SAP Users interact with SAP – providing an additional option to classic SAP GUI.


Fiori – LaunchPad Personas – Select Functional Location
04_smart_Business.png Personas_1_After.png

Having said that, SAP GUI 7.40 just shipped, including the “Fiori Style” Blue Crystal Theme, and more interestingly, the 7.40 release that comes bundled with SAP NetWeaver Business Client (NWBC). This blog by my fellow SAP Mentor John Moy highlights the value SAP NetWeaver Business Client can add to classic SAP users. It is also worth remembering that many classic SAP GUI screens have been improved with Web Dynpro ABAP via Enhancement Packages (see this example for Plant Maintenance in EhP 6). Finally, look at Personal Object Worklists (POWL), which can help an SAP user understand which objects in the system need their attention (e.g “Purchase Orders past Goods Receipt Date for My Vendors”).

So we start to see a future where power users might use NWBC (hosting a variety of UI technologies) and casual users access content via Fiori LaunchPad/Fiori and Personas. The icing on the cake is the SAP Web IDE (this was formerly called “SAP River – Rapid Development Environment”) to extend existing applications and develop new ones.

River-RDE_Preview.png

So there are plenty of options – you can browser them all at the SAP UX Explorer.

So where do you start?

First Step:  Understand Your Problems

Plenty of people complain about “using SAP,” but not so many have really done any analysis on where the specific problems exist. So a logical first step is to perform an analysis of what is driving the problems.

I would suggest you start by creating a matrix that maps your user community and rates the level of problems users have. For the top three areas, you can start to assess what could be done to help and start to build the business case for a new user interface (I discussed a framework for doing this in the 2012 blog series).

Second Step:  Understand the Options

The second step, which can run in parallel with the first one, is to understand what the option are. OpenSAP can help here with courses on SAP UX strategy and SAP Fiori. You can also read the SAP UX Strategy and use SCN daily to engage with others who have already started their journey.

Third Step:  Hardware and Software

Depending on what you decide, some options will already be available in your landscape (quick wins), while others will require you to adjust your SAP landscape roadmap.

For proof of concepts, you might look at the Cloud Appliance Library or invest in your own innovation system. HANA Enterprise Cloud and HANA Cloud Platform also offer options for fast and lower-cost deployment options. Find more details in my next Cloud blog later this year.

Fourth Step: Create an Implementation Programme

Finally the rubber needs to hit the road. You need to create an implementation plan!

One good thing about most of the UX solutions is they can be run in parallel (not recommended for long term TCO, though). So you can select the best business case for UX renovation and work from there.

Conclusion

If you go through the above process, I predict two things:

  1. You’ll find a user interface solution you already have, or which could be adopted quickly.
  2. The user experience that most of your users get today will be radically transformed – and at the end of your three-to-five year roadmap, most users will never have heard of SAP GUI (even though some will still use it via NWBC or Personas).
To report this post you need to login first.

7 Comments

You must be Logged on to comment or reply to a post.

  1. Simon Kemp

    Hi Owen,

    Good blog, thanks for sharing.

    You say:

    So we start to see a future where power users might use NWBC (hosting a variety of UI technologies) and casual users access content via Fiori LaunchPad/Fiori and Personas.

    This is exactly the approach we are taking currently so it’s nice to see it being highlighted here.

    I think your first step above “Understand your problems” is critical – you need to be able to measure your success and you can’t do that without understanding where you’re starting from. At existing customers this is possible, on greenfield implementations it is somewhat harder and you need to rely more on the experience of your partner helping you to implement.

    Cheers,

    Simon

    (0) 
  2. Markus Theilen

    Hi Owen,

    great blog! It really comes to the right time for me and my company as we are thinking about the UI way of the future and are starting the journey into Fioriland.

    Thanks, Markus

    (0) 
    1. Owen Pettiford Post author

      Andy,

      You are right I should have mentioned the Enterprise Portal which is an option esp if an organisation has already invested in this platform as the Fiori LaunchPad running on EP provides the possibility to bring older content and Fiori content together.

      If it is a greenfield site, I think I would be looking at using the Gateway (ABAP) Fiori LaunchPad to do this, and moving forward I would look at the Fiori as a Service offering and the HANA Cloud Portal….more in my Cloud blog later this year 🙂

      Owen

      (0) 
      1. Andy Silvey

        Hi Owen,

        you’re right and this leads to the next logical step as Aviad recently described integrating Fiori and HCP   and HCP being the entry point to the SAP landscape.

        and that

        HCP is a very nice stepping stone into the Cloud.

        As a Portal practitioner, I am acutely aware of the need for good planning regarding web/mobile entry to SAP and especially from the perspective of one single point of entry, one url. To offer an opinion, I think there is nothing more untidy in any SAP Customer than when there are multiple entry point urls, one for ESS/MSS, one for SRM, one for BPM, one for Fiori, one for etc etc. Hence the Portal’s role in any landscape as the single point of entry along with of course the GateWay and Fiori as Aviad Rivlin so succinctly  described in the document, SAP Enterprise Portal and SAP Fiori – Common Architecture Recommendations

        Best regards,

        Andy.

        (0) 
  3. Denny Schreber

    Hi Owen,

    Thanks for this blog (series).

    Liked that whispering part 😀

    Interesting question is indeed how the Portal fits into that concept (having the LaunchPad available)?

    Cheers,

    Denny

    (0) 

Leave a Reply