/O in the transaction

[Former Member]

Hi all,

We want to prevent the user of using /O when putting the transaction ( we want to prevent new SAP windows) : is there any solution with the authorizations to make the system refuse actions beginnig with /O ?

Thank you in advance !!

[Former Member]

You can try to hide the "command window" but I don't believe that it will really work. At least I have strong doubts.

You can try to restrict ALL authority for object S_TCODE and S_DEVELOP, which is a good place to start if that is what you are looking for.

Cheers,

Julius

[Former Member]

>

> Hi all,
> 
> We want to prevent the user of using /O when putting the transaction ( we want to prevent new SAP windows) : is there any solution with the authorizations to make the system refuse actions beginnig with /O ?
> Thank you in advance !!

You can't, nor should you control this through authorisations. If you have an issue with users doing this then this is usually down to training.

rdisp/max_alt_modes controls number of gui sessions they can spawn per login session, but if you set this = 1 (standard is 6) then you will stop everyone on that app server creating new sessions

[jurjen_heeck]

>

> rdisp/max_alt_modes controls number of gui sessions they can spawn per login session, but if you set this = 1 (standard is 6) then you will stop everyone on that app server creating new sessions

And you'll stop them printing locally as well...... The lpd process on the front ent requires its own session.

[Former Member]

>

> And you'll stop them printing locally as well...... The lpd process on the front ent requires its own session.

Good point, I didn't realise an extra session was needed, but it makes sense when you think about it.

[Former Member]

Quistion is: WHY do you not want users to run more sessions as it can be verry handy for users to do so!!