Skip to Content

How to disable the default Flavor in Windows GUI when using Screen Personas 3

Apr 10, 2017 at 02:45 PM


avatar image

Hi Experts,

for some personas scenarios ist very important to forbid strictly that a user uses the default flavor.

At the moment we can set the default flavor in the role assignment and permit to use the flavor galery.

But if any user works with a non personas compatible SAP GUI for Windows (wrong patchlevel, wrong theme, set sap logon support bit) he gets nevertheless the default flavor and he can use it.

The goal would be disable a transaction (Flavor) for SAP GUI for Windows and to allow the same for the SICF Personas GUI


to disable the default Flavor even a user works with a non personas compatible SAP GUI for Windows.

Thx and best regards,


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Steve Rumsby
Apr 11, 2017 at 12:02 PM

If you use a GUI (native, or web) that does not support Personas, or which allows Personas to be disabled (via Windows registry settings, for example), then you will get the standard SAPgui transactions. There's no way to avoid that.

Why do you need to prevent users from using the standard transactions?


Show 4 Share
10 |10000 characters needed characters left characters exceeded

An example which occurs several times:

For a business case a transaction have to be used in a certain way.
The Users must know exactly how to use the transaction. If they do it wrong a power user have to fix it with elaborate work.

Now with Personas i can create flavors for this business case, so a user have no more chance to make something wrong. (really great… no more time-intensive trainings, less extra work for the power users)

The only Problem is that i want to force the users to use the personas flavor.
If a percentage of users are furthermore working with the standard transaction I have nothing achieved :-( and the acceptance of Personas is reduced :-(

With hundreds of users and many different customers the problem could not be brought under control.

Another Point:

If a customer wants so change the UI strategy to HTML/UI5 in the medium term he also need a possibility to disable the windows gui step by step.


I just had this crazy idea (or hack?) of having some sort of an ABAP enhancement to the transaction, which would check whether the user's session is a Personas one and if not, it'd display an appropriate message and exit. I've not attempted this yet but it should be doable, perhaps based on some code out of SM04 or something like that.

At the moment I don't have a better idea.


That sounds like something I'd suggest :-)

It would mean adding an enhancement to every transaction you need to work this way, so it wouldn't scale well. But for just a small number of transactions, assuming suitable enhancements are available, it might work.

How would you check that Personas is enabled in the current session?


Hi Steve,

I'm glad (actually honored) that our minds work a little alike in situations like this :)

Well, in SM04 we have the "Application Info" column, which makes a Personas session easily identifiable. So as long as we can establish a link between the current session and the corresponding row in the SM04 list, we should be golden. Trouble is, I didn't investigate yet what this takes. There may even be a better way to make this determination, I don't know... it would take some digging to figure out the easiest method.

As far as the enhancement goes, I'm not concerned because if all else fails, there is always some implicit enhancement point available at the beginning of a transaction - but of course such a solution would have to be tailored to each selected transaction. Unless we tie this into some code that runs when any transaction is started (if such a thing exists).

I may play around with this as time permits, because I believe the use case brought up by Thomas is a valid one. But if you have a better idea than this, I'm all ears :)