Skip to Content

In customer meetings, at SAP and ASUG events, and through our inboxes, we continue to receive many questions about how SAP Screen Personas and SAP Fiori fit together. This blog is the latest discussion about their tight and complementary fit, especially in the context of Fiori 2.0 and SAP S/4HANA.

 

SAP Fiori is the user experience for SAP.

The term “Fiori” has held several meanings since we introduced it in 2013. First there were the Fiori apps, then the Fiori design principles, then the Fiori user experience. Extending the UX definition, Fiori 2.0 is the new face of SAP S/4HANA.

Fiori 2.0 introduces compelling new graphics, an extended desktop with access to more information, and the new visual theme, Belize. In addition, the Fiori user experience is expanding across SAP’s portfolio; SuccessFactors now has a Fiori appearance to access its functionality. Now when I hear people say “Fiori” in 2017, they generally mean the UX overall, rather than just the apps in the reference library. This is good news, as there are several ways to obtain the Fiori user experience.

 

Several ways exist to obtain the Fiori UX

For ECC customers (lower left corner of the chart), SAP Screen Personas is the fastest and easiest way to achieve the Fiori user experience. SAP’s Chief Design Officer, Sam Yen, said this at TechEd 2016 and it remains true now.

http://events.sap.com/teched/en/session/28909 (SAP Screen Personas discussion runs 40:00 – 44:30)

For custom transactions in SAP S/4HANA (primarily lower right corner), SAP Screen Personas is probably the best way to achieve the Fiori experience. It allows you to

  • Preserve your investments in business logic
  • Give your custom transactions the Fiori 2.0 look and feel without any back-end coding
  • Ensure a coherent UX across your SAP landscape for all users

For areas without Fiori coverage today in SAP S/4HANA, SAP Screen Personas is an excellent way to simplify the screens, especially if the business logic already exists in the underlying Dynpro transaction(s) or Web Dynpro applications.

 

SAP Screen Personas continue to evolve to align with developments in Fiori UX

With the latest version of SAP Screen Personas, we have made it even easier to create Fiori-inspired flavors. These flavors can include adaptive elements and be easily embedded into the Fiori Launchpad to create a seamless user experience.

We continue to maintain compatibility with SAP S/4HANA innovations such as the Belize theme, which provides the Fiori look for classic transactions.

The current SAP Screen Personas allows you to build flavors faster, with more consistent designs, using significantly less effort than with previous versions. (If you are on an older version, we encourage you to migrate.) In the past year, we have introduced:

  • Templates to build consistent designs across multiple transaction screens
  • Script libraries so you can reuse scripts across different transactions
  • More theming options to simplify creating Fiori-inspired designs

How can you obtain the Fiori user experience today?

  1. Select an app from the Fiori app reference library and deploy
  2. Use SAP Screen Personas and our Fiori design guidelines
  3. Develop your own Fiori app using BUILD, WebIDE, and Fiori elements
  4. Purchase SAP S/4HANA

If you are interested in using SAP Screen Personas to improve your SAP user experience, please let us know how we can help.

For the SAP Screen Personas product team, Peter Spielvogel.

 

To report this post you need to login first.

1 Comment

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

  1. Giangabriele Casci

    Hello Peter, thanks for your clear Tabular Synopsis — so Personas is meant for personalizing custom transactions: does it imply that bespoke T-codes cannot be “ported” into Fiori Apps and the bespoke logic needs to be rebuilt from scratch via UI5 / WebIDE?

     

    (0) 

Leave a Reply