Recently, I have attended several presentations in which the SAP speaker states that when it comes to SAP user experience, “everything is Fiori.” Many of my customers and colleagues have asked me what this means, especially in the context of SAP Screen Personas. In this blog, I will attempt to clarify this statement and show how SAP Screen Personas complements SAP Fiori UX.

The definition of Fiori has changed

When we originally launched SAP Fiori, it was a collection of apps to replace the most commonly used functions of SAP Business Suite.These apps had several very important characteristics.

/wp-content/uploads/2015/01/twitter_633525.png SAP Fiori means: simple, role-based, responsive, coherent, and delightful.

/wp-content/uploads/2015/01/paradigmshift_633526.png

 

The market embraced this approach to disaggregating SAP software, such as CRM, SRM, HCM, and SCM, into relevant tasks and activities for end user roles across the enterprise.

In response, we created more apps for more user roles to make more functions of SAP ERP accessible through a variety of devices. Based on continued positive feedback, we expanded the meaning of SAP Fiori to include not just the apps, but also represent the concept, design and technology. Now, SAP Fiori is the new user experience for SAP software, across solutions such as S4HANA, SAP Simple Finance and SAP Business Suite. This is what we mean by “everything is Fiori.”

A consistent user experience across SAP functionality

Frequently, I hear customers express their desire for a consistent user experience across SAP. For some organizations, this means a single entry point. For others, they want all SAP applications to have some family resemblance. For example, when you use Microsoft Office, Word, Excel, and PowerPoint all do different things, but they have a similar look and feel.

Several solutions have emerged over the years from SAP that provide elements of a unified user experience. NetWeaver Business Client (NWBC), the SAP Portal, and now Fiori Launchpad are all essentially shells to hold other content such as Dynpro-based transaction screens or Web Dynpro applications. Or even new Fiori applications.

The UX strategy covers new and existing applications

If you think about the SAP UX strategy, we offer a three-pronged approach: New, Renew, Enable. With the updated Fiori definition, we now deliver all new applications with the Fiori user experience. And many renewed parts of SAP ERP are available with the Fiori user experience (the aforementioned apps).

What about all the remaining functionality in the Business Suite? There are over 10,000 SAP-provided transaction codes in the SAP GUI, through which over 80% of users still access SAP. This is where SAP Screen Personas fits in. It enables you to modify any SAP GUI transaction so it has the Fiori characteristics.

/wp-content/uploads/2015/01/twitter_633525.png SAP Screen Personas lets you make SAP ERP transactions look like Fiori apps.

Making everything look like Fiori with SAP Screen Personas is often faster and easier than developing custom applications, if the underlying transactions do most of what you want.

While many customers are embracing the Fiori design, you can use whatever visual design you want to make the screens consistent with how you consume enterprise applications at your company. I have seen some customers integrate SAP transactions into their corporate portal using SAP Screen Personas. The resulting screens do not look anything like classic SAP. Some users do not even realize they are using SAP.

I have heard some people say that SAP Screen Personas and Fiori are ways to deliver cloud-like usability for on-premise systems. Certainly, they are a great way to prepare your company for the cloud and help you run simple.

/wp-content/uploads/2015/01/designprinciples_633542.png

Everything is Fiori means better usability for you

Who would not want their enterprise software to be intuitive, optimized for specific user roles, and run on a variety of devices? This is what the Fiori user experience is all about. SAP Screen Personas is a great way for you to deliver this capability to your users.

Here is a style guide that allows you to build Fiori designs using SAP Screen Personas 3.0.

For the SAP Screen Personas product team, Peter Spielvogel.

To report this post you need to login first.

24 Comments

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

  1. Daniel Ruiz

    hi Peter,

     

    in your last statement you mention we can produce Fiori-like Applications using Personas. which version actually can do such? – I understand by Fiori-like the ability to product applications using the design guidelines of Fiori.. please correct me if not accurate, I still did not find an easy way to do such.

     

    on the topic, Fiori seems to be only a good choice when dealing with mobile or smaller form factors than a desktop.. I hardly think applying the guidelines of Fiori into a desktop form factor is a good design decision – seems to be a lot of waste and unbalanced screen elements, even on the app-framework the master-detail and full screen modes are not as smart or provides far less usability than material design from Google.. check Google Inbox for instance, the way they handle lists and inner elements inside lists, or even material design forms seems to utilize screen real-state a lot better.

     

     

    on the other hand, some stuff I’ve seen from SAP uses the ux3 namespace components which IMO, provides a far better result for desktop form factor than m namespace, and ux3 namespace seems to be vastly used by SAP to deliver applications, but they are not mobile ready – wouldn’t make more sense Personas utilize more of ux3 and follow ux3 patterns other than Fiori patterns? – Personas have a extremely heavy load of resources comparing to any other small footprint framework (or application if you like) which already kinda restricts the use to desktop, why not focus on something else other than Fiori to produce better results?

     

     

    last, I’d be really keen to see SAP split the scripting engine from the flavor management in Personas – this would be awesome since a developer would be capable of easily ‘mapping’ whatever he developed into a SAP GUI screen, execute functions and read/parse back the result.. in fact, I believe this is the real power behind of Personas, as I find the elements to use to design screens extremely limited.

     

     

    Cheers,

    D.

    (0) 
    1. Peter Spielvogel Post author

      Hi Daniel,

      You raise many points here, so let me address them individually.

       

      It is possible to build screens that look like Fiori in both SAP Screen Personas 2.0 and 3.0. The style guide for 2.0 is available now. The Fiori style guide for SAP Screen Personas 3.0 is being developed and will come out as part of the planned RDS (rapid deployment solution).

       

      Fiori can be used across all form factors – phone, tablet, and desktop. The responsive design presents more content on the screen the larger the available real estate. If want to put more information on the desktop than the standard Fiori design, then you can modify the Fiori screens using Web IDE.

       

      In SAP Screen Personas 3.0, we have separated the design and scripting functionality. Each has its own menu optimized for the roles that will generally be using them. You can now build the screens using a more intuitive menu structure and theming engine. Scripts are built in a separate window, built in more of a development environment style. Once the scripts are written and tested, you then go back to the editing mode to attach scripts to the buttons.

       

      I will ask someone from the development organization to address your namespace question.

       

      Regards,
      Peter

      (0) 
      1. Daniel Ruiz

        hi Peter,

         

        “It is possible to build screens that look like Fiori in both SAP Screen Personas 2.0 and 3.0. The style guide for 2.0 is available now.” – would you mind hyperlink the documentation here? – I simply can’t find this information.. – would be pretty great to be honest, we’re in a process with two customers deciding to adopt Personas 2 and I still have time to do something about it.


        well, I understand Fiori can be used across all form factors, this is not what I questioned.. – all I said is that, no one in their sane mind would develop on sap.m / blue_crystal (which is what you folks in SAP named Fiori) when dealing with desktop.. don’t you find strange all the players who actually ‘lead’ UX doing something different than what SAP is doing at this moment? – the boat has sort of passed, the patterns applied in Fiori are old patterns, forcing a developer to end up with an old pattern for UX is not really nice..


        about Personas 3, I’m part of the ramp-up.. – I understand we have two windows, one with a extremely limited wysiwyg (which is what we use to edit the flavor) and another pull up panel with the ‘script editor’… however, my question was not this, it was something else.

         

         

        – why not release the js objects used in the personas composer application to be used outside of personas, as a standalone technology? – this way we could use the scripting engine outside personas.. of course personas could still use it internally, but this way SAP would extend its possible usage.



        Cheers,

        D.


        (0) 
        1. Tobias Queck

          Hi Daniel,

           

          Your point about the scripting engine is a very good point. As usual, what I am saying next is not a promise of a feature or a product.

           

          If you look at how scripting has changed from 2.0 to 3.0, you can see that it changed from being a feature in the editor, into a separate component that is part of Personas but separated from the editor. If you check the back-end tables, you can also see that the scripts have there own structure and are not part of the standard flavor changes anymore. However, at this point in time, they are still linked to a flavor. We are looking into the possibility of detaching them from a flavor and making them globally available (within Personas) to be called from other flavor specific event handlers.

           

          Why would you want to use the scripting engine outside of Personas? With Personas you can bind the scripts to control/screen events, without it you would have to write your own application that remote-controls the WebGUI. If you write your own application, wouldn’t it be better to build it using Gateway service to fetch/manipulate data?

           

          Since you are part of the ramp-up already, why not discussing this in the next ramp-up accelerator call?

           

          Cheers!

          Tobias Queck

          SAP Screen Personas

          Lead Architect

          (0) 
          1. Daniel Ruiz

            hi Tobias,

             

            yeah, I understand how the scripting engine works, the objects you guys created in the ui5 composer app for Personas.. there is some stuff I could actually play around and enhance to abstract it a little bit to be used ‘outside’ the personas shell.. – main reason why I believe something like this could be good is due the fact some ‘processes’ already coded in the dynpro’s – and by this, I mean update processes pretty much, fetching would usually become some ICF SREST node (I personally don’t like the GW oData since I find most of the stuff built in there slower than coding it myself) – but perhaps, for one or two ‘queries’ that there is a dynpro screen built already, it could even be a target for such too.

             

            – having such, someone could pretty much code using whatever toolset they want and finalize a dynpro transaction, and considering the dynpro screen does it’s job it may actually save some development time (of course, it’s a performance trade off)

             

             

            in regards your first question, I agree: writing a custom application from scratch will always provide better results, but there is no such thing as a ‘clear API’ in ABAP, this way we always end up having to code a lot of back-end logic, that somehow is already there in the dynpro screens, it’s just the ‘format’ of that code is not really re-usable – also, as Peter mentioned in his blog, “10,000 SAP-provided transaction codes” – means, we would have access to utilize some of these.. and don’t get me wrong here, in a developers view I understand all the benefits of coding the services and opening up an API that should already exist in SAP for the last 15 years, but there is some appealing to business being able to ‘face-lift’ a dynpro screen, reason why Personas exist.  =)

             

             

            Since you are part of the ramp-up already, why not discussing this in the next ramp-up accelerator call?”

             

            – I have no idea what’s this about, but I will check with the folks here how can we join in.. used Personas 2 and Personas 3 and I believe Personas 3 is far superior, more than happy to provide some feedback on the correct channel.

             

             

             

            Cheers,

            D.

            (0) 
            1. Tobias Queck

              Hi Daniel,

               

              You should have received an invitation for the next call by now. I am looking forward to continuing the discussion on the phone.

               

              Cheers!

              Tobias Queck

              SAP Screen Personas

              Lead Architect

              (0) 
              1. Daniel Ruiz

                hi Tobias,

                 

                yeah I did, thanks for that.. will try to join in, it’s pretty early for me in NZ but hopefully I will be able to attend.

                 

                 

                Cheers,

                D.

                (0) 
      2. Mike Andries

        The style guide for 2.0 is available now.” – would you mind hyperlink the documentation here? – I simply can’t find this information.

        Agree….where is this information??

        (0) 
      3. Rob Scofield

        Hi Peter,

        I am also interested in finding the “style guide for 2.0”.  I got a Fiori style guide for Personas many months ago but it was very much a draft – I think I got it from the link draft of a style guide document within SAP Screen Personas Practitioner Forum session 13 summary, but the link was only available until 8/8/2014.  The only thing I can find is the generic Fiori design guide at:

        https://experience.sap.com/fiori-guidelines/

         

        Rob

        (0) 
          1. Todd Barber

            Peter,

             

            Thanks for the information.  I just went through the style guide.  I do have two questions:

             

            1.  You reference numerous image files – like Fiori_LaunchPad_Hdr_1200x48.png.  Where can we find those files?

             

            2.  You reference the Fiori Icon Font.  Can the font be used in lieu of an image, or do you have to download the image as a file to use it?

             

            Thanks,

            Todd

            (0) 
            1. Saurabha Joglekar

              Hi Todd,

               

              I have the same question.

              Have you yet found the resources, where in we can find all those images mentioned in the Style Guide ?

               

              @Peter – Please shed some light as so where these resources are available. I have recently taken your OpenSAP course. And its really wonderful.

               

              Regards

              Saurabha J

              (0) 
                    1. Saurabha Joglekar

                      Hi Tamas,

                       

                      I have gone through that, hence I was able to point out that the resources mentioned in that post say for Launchpad-Background use Fiori_Gradient.png are not listed.

                       

                      The guide lists various resources like Fiori_BasicPage_Hdr_1200x48.png or Fiori_Gradient.png and many more. But there is no link to download these resources so that they can be used in Personas screens.

                       

                      Regards

                      Saurabha J

                      (0) 
    2. Guillaume GARCIA

      Hi,

       

      I can’t agree more on this, Daniel!

       

      Fiori on desktop

      On desktop (especially with the huge resolution people have nowadays), Fiori apps look rather “empty” so-to-say. It even may seem counter-productive since the process is split up into several screens where – on desktop – you could easily have reduced it to 1 single screen.

       

      Theming Screen Personas using Fiori Guidelines

      Besides, AFAIK, SAP Fiori can change the theme using the UI Theme Designer but Screen Personas follows a different concept* with its own internal theming (correct me if I’m wrong).

      Thus, each time you update the theme using UI Theme Designer, you will end up changing manually all of this in Screen Personas?

      Last point, I very much liked the approach by Tobias about “Screen Personas responsiveness”: Giving an SAP transaction a responsive design with SAP Screen Personas 3.0 but, to say the truth, isn’t it a clever trick compared to what Fiori offers “for free” (assuming you use the sap.m library)?

      Imagine you decline your Flavor for n population categories, you will end up having to maintain 3*n flavors in case you want to support 3 different resolutions?

       

      *just wanted to know if UI Theme Designer support for Screen Personas is planned/part of the roadmap?

       

      Best regards,

      Guillaume

      (0) 
      1. Peter Spielvogel Post author

        SAP Screen Personas does not work with Theme Designer. Since our themes must work across the different SAP GUIs, we had to create our own theme engine so the designs you create in Web GUI will also render properly in SAP GUI.

        (0) 
        1. Guillaume GARCIA

          Hi Peter,

           

           

           

          Thanks to your answer.

          There is some confusion (at least, on my side) because we can read on UX Explorer (https://uxexplorer.hana.ondemand.com/_item.html?id=135#!/facet/112) that UI Theme Designer is supported by SAP Gui for HTML and SAP Screen Personas is HTML-based.

           

           

           

          Is this possible to create a flavor based on a SAP Gui for HTML that would be theme using UI Theme Designer?

          If yes, the theme would then be “frozen” into this particular flavor, right?

           

           

           

          Thanks in advance for your insights.

           

           

          Best regards,

          Guillaume

          (0) 
          1. Peter Spielvogel Post author

            SAP Screen Personas cannot use Theme Designer because the themes we build must work across both SAP GUI for HTML (Web GUI) and SAP GUI for Windows (SAP GUI). SAP GUI for Windows cannot use CSS (cascading style sheets) as it is not browser-based.

             

            Regards,

            Peter

            (0) 
            1. Guillaume GARCIA

              Thank you, Peter!

               

              PS: I enrolled the SAP Screen Personas course on openSAP and I must say that – for a non-native English speaker like me – you’ref SO easy to understand (no offense to some of your German colleagues…)

              (0) 

Leave a Reply