Skip to end of metadata
Go to start of metadata

SAP Screen Personas

Personas Authorization checks and transaction SU53

SAP SCREEN PERSONAS KNOWLEDGE BASE - by Tamas Hoznek , Dominik Ofenloch


In the past we received many questions like "Every time a user starts a transaction, a Personas authorization check fails. How can I get rid of this check?". This article describes how you can minimize the number of such authorization checks.


SAP Screen Personas 3.0 offers a very detailed authorization concept. For each user you can set up authorizations for a specific client technology/framework and for a specific transaction code. Furthermore, for each transaction/user combination you can set up different user authorization levels, for example "Display flavor only", "Set up default flavor" and "Share flavor with other users". Based on the standard delivered /PERSONAS/* user roles, you can build your own custom roles as necessary, granting access to only the features each user needs to complete their tasks.

To offer you this detailed authorization concept, SAP Screen Personas needs to execute authorization checks on each transaction startup. In case a user has insufficient authorizations, this will lead to failing authorization checks which may lead to confusion. So how can you avoid or minimize the number of authorization checks? The following sections will show you some strategies for this.

Update your SAP Screen Personas installation

First of all, update your SAP Screen Personas installation. This is important not just in this context, but as a general recommendation. You can verify whether your installation is up-to-date as described in this Knowledge Base Article.

Important: Even if your system is fully up-to-date, it is still possible to see some failing authorization checks, depending on what access is granted to users.

Disable SAP Screen Personas for a specific GUI technology

In many customer scenarios SAP Screen Personas gets enabled for one specific client technology only. If you want to use SAP Screen Personas only in SAP GUI for HTML (webgui), you can disable it for all users in all other clients (Windows GUI, Java GUI). In this case the authorization checks will no longer be executed.

You can find more information in our Knowledge Base Article Deactivating SAP Screen Personas.

Set a user parameter to disable Personas

To disable Personas completely for a specific user, you can also use the user parameter "/PERSONAS/RUN_MODE". For this you have to set this user parameter to value "O" (=off) or 0. You can maintain user parameters in transaction SU01. In the same transaction, you can also use the highlighted corresponding personalization objects for this purpose:

Windows GUI: Update your Windows GUI

When using Personas in Windows GUI, we strongly recommend to update your local Windows GUI to the latest SAP GUI release and patch level. This solves various issues including authorization problems, performance issues and other bugs.



Important News

This knowledge base is not solely SAP provided content - but community driven. Please also check on SMP and for SAP released information and notes on SAP Screen Personas.

Create New Article

Compare SAP Screen Personas versions

Search the KB

How to Open OSS Message

 What information is needed for creating OSS message?

  1. Make Sure you are on the latest patches and notes.
  2. Kernel Patch Level
  3. Two Types of connections to your environment: HTTP and R/3
  4. All the connections should be tested with proper credentials provided
  5. Steps to re-create the issue
  6. Attach related logs
  7. File tickets against BC_PER

Client settings can be viewed/edited using transaction sm30 and opening maintenance view for table /personas/sttngs.