SAP Screen Personas – Sample Case
SAP Screen Personas is controversial in a way that many customers do not find much benefit and in some cases, even experience performance issues after implementing Screen Personas (SP).
SP sits at the top of GUI transactions and it will take more time to load (even though in most cases it is negligible) the screen with SP. So where is the benefit.
Transaction IW21 may involve a sequence of steps to create a notification. But not all the fields are used by the person reporting the notification. In a typical case, the number of clicks can be reduced by 50% at least. Personas can be used to create a Fiori-like look and feel and the tile can be added to the launchpad. SP can also use native tools of a device like camera for taking pictures and scanning barcodes.
Benefits of using SP in this case:
- Get rid of the extra fields and screen.
- Default values can be added.
- Appified much faster than Fiori.
- Description texts can be added for the user, reducing the training cost.
- Barcode scanning and adding pictures made easy.
Remember, SAP has around 300,000 screens. Use the power of SP to create a role based (even an app) transaction and increase your productivity.
