Comparison - SAP Fiori UI5 and SAP Screen Personas : The Good, The Bad, and The Ugly

July 9, 2017

SAP provides two paths to a delightful user experience (UX)

SAP Fiori UI5 apps and SAP Screen Personas are two ways to achieve the SAP Fiori user experience.

  • The Fiori UI5 UX strategy aims to transform the transactional operational model to a role-oriented one
  • SAP Screen Personas simplifies scenarios not yet covered by Fiori applications or for your custom transactions

UI v/s UX

There is a distinction between User Interface (UI) and User experience (UX).

User interface deals with intuitive screen design, screen flow, buttons and colors.

User experience deals with how users feel when they interact with the technology. It includes integration between processes, people and technology

Example:  Uber

  • Intuitive screen design to call a ride from your mobile phone  > Great UI
  • You can walk out of your ride without using your mobile phone >  Great UX

Perspective

SAP provided technologies (Fiori UI5, Personas) can be used to improve UI for screens as part of organization’s UX improvement initiative. Here is a perspective of each technology.

1. Fiori UI5 apps:

The Good:

  • Role based development
  • Develop once, use on any device i.e. Mobile phone, tablet and desktop
  • Develop based on your need (independent of existing SAP transactions)
  • Leverage SAP Fiori Launchpad to personalize landing screen
  • Fiori design is the future UI for all SAP products
  • Dynamic search functionality
  • Smart tiles with analytical annotation

The Bad:

  • High cost of development
  • Different approach for development compare to traditional development (Design thinking)
  • Need to provide complete “end to end functionality” for designated roles otherwise users ends up in two different user interface (Fiori and SAP GUI)

The Ugly:

  • High cost of change (develop once and develop right)
  • Easy to deviate from SAP’s Fiori design guideline

Bottom line:

  • Great for complex business process. High development cost. High UX improvement. Long term approach.

2. SAP Screen Personas

The Good:

  • Modify existing transactions (standard and custom) > Keep existing business logic
  • Easy to simplify > remove fields
  • Relatively easy to beautify screens by applying themes
  • Great screen editing interface for screen editing and great libraries for JavaScript
  • Great for simplifying display transactions
  • Can be integrated with the Fiori Launchpad

The Bad:

  • Limited to SAP GUI transactions (Very difficult to combine different edit transactions on one screen > It gets ugly pretty fast)
  • JavaScript can be used only for front end development i.e. SAP GUI for HTML screen
  • Limited to fixed screen-size per theme (You need to create flavors for every screen size. Development time multiplies with every flavor)
  • Every transaction needs flavor (i.e. Three flavors for MM01, MM02 and MM03). Multiple flavors if you are creating different variants for different users groups

The Ugly:

  • For edit transactions it gets ugly to merge fields from multiple tabs esp. grids
  • It gets even uglier if you have mandatory fields on different tabs
  • Must have ABAP expert and JavaScript developer for any meaningful automation or screen development
  • Numbers of scripts and flavors can get out of hand very quickly
  • Screen can look like Fiori screen but will not provide intuitive UI functionality available for Fiori UI5

Bottom line:

Great for simple transactions and linear business process. Limited development efforts. Limited UX improvement gain.

3. Hybrid approach:

Improve UX by implementing Fiori UI5 and SAP Screen Personas

  • The man who chases two rabbits, catches neither. ~ Confucius
  • If you “the organization” wants to chase two rabbits, setup two different teams and send them to chase one rabbit each ~ Confucius 3.0
Also posted at : https://experience.sap.com/topic/perspective-two-paths-to-a-delightful-user-experience-ux/
 

Cycle counting

May 13, 2013
Cycle counting: Configuration, Process flow and Implementation

This is brief overview of cycle counting process in inventory management (IM). 

What is cycle counting?

Cycle counting is a method of physical inventory whereby inventory is counted at regular intervals within a fiscal year. Physical inventory may be required by financial accounting rules or tax regulations. Cycle counting process is less disruptive to operations. This process can be integrated in daily operations for example count 2...

Continue reading...
 

Steps for closing period in SAP

April 27, 2013
Steps for closing Period – MM FI CO

As many of us struggle with changing periods in our DEV and QA environments, here is quick reference for closing period. In doubt, please consult with your FI/CO expert.

There can be upto four transaction involved depending on your situation.

  • MMRV - Allow posting to previous period  
  • MMPV - Close Periods
  • OB52 - Change view "Posting Periods: Specify Time Intervals"
  • OKP1 - Maintain Period Lock

 
1. MMRV – View current period / Allow posting to previous period

This...

Continue reading...
 

Brief overview of Outline Agreements

October 3, 2012

What is Outline Agreements? Where it fits in purchasing process?

The outline purchase agreement is often referred to as a blanket or umbrella purchase order. It is basically a long-term agreement between the purchasing department and vendor for material or services for a defined period of time. The purchasing department negotiates with the vendor a set of terms and conditions that are fixed for the period of agreement.


Which business requirements lead to use of outline agreement?

  1. Wh...

Continue reading...
 

Procurement 101

June 4, 2012

 
Procurement process includes necessary activities for the external procurement of goods and services. Procurement ensures that all required goods and services are ordered from and delivered by the vendor in sufficient quantities and in satisfactory time.
 
Procurement types

 
In the SAP Material management’s procurement process, you procure either for stock, service, and direct consumption. You can determine the purpose for which ordered materials are being procured in the purchase order, for ...

Continue reading...
 

Gamification or Simplification: which path you will choose?

May 30, 2012
Why?
 
Why bother with either? Good question. Reason companies need to update user interface (UI) could be because internet/apps revolution in past years changed user expectation from ERP system. New users who are looking at SAP for first time are asking why is the user interface so difficult to navigate? SAP did a great job when they introduced ‘Enjoy’ transactions for MIGO, ME21N etc, but it’s been a while since anything changed for core SAP GUI functionality. 

Again same question: Why b...

Continue reading...
 

Championing SAP Plant maintenance at your organization

April 24, 2012

Do you feel that in your organization SAP Plant maintenance is not being used at its full potential? Do you think you can integrate maintenance activities with other departments? SAP plant maintenance module can’t work on it’s own. It needs to be integrated with other modules in order to get maximum benefits.

Here is two phase approach:

a) Optimizing use of SAP PM in department

b) Increase integration with other module



Optimize use of SAP PM in your business


1. Keep SAP plant maintenance data ...


Continue reading...
 

Make a free website with Yola