SAP Screen Personas – When to use
There is no question of Fiori App Vs SAP Screen Personas. SAP envisioned them to be complimentary and their strengths and weaknesses can reinforce each other.
SAP Screen Personas are cheaper and faster way to “appify” an existing standard (or even) custom transactions. You can create a Persona on top of transaction and then expose it as a tile in Fiori launchpad and the user does not have to know that it is not Fiori. Let’s see some cases, where SAP Screen Personas can be used.
Personalize an existing transaction to convert it into a role-based transaction. Existing SAP transactions are used by users with different roles where they populate different sets of data. If you want to make an app for this transaction, you can use Screen Personas to personalize around user roles and remove the extra fields.
Simplify Interaction with standard transactions. SAP screens are daunting for new users. They may need to interface with few fields but the transactions have tons of fields. Just remove the extra fields by building personas.
Combine multiple transaction for a user role in a dashboard. It is no brainer that it can save a lot of user training effort if user are exposed to a dashboard transaction. It is like their home page when they login and they have everything there whatever they need (or mostly need). It is very useful for users who have limited authorizations and tasks in SAP.
What do you think about Screen Personas. Please feel free to share your inputs in the comment section. 🙂
