What settings other than authorization objects can restrict a user to execute a t-code?

[Former Member]

We received a issue in which a user is not able to execute a t-code. We compared his access with other user who has same access.

SU53 dumps are showing different result for both the users, however both users have same roles and authorizations. What settings other than authorization objects can restrict a user to execute a t-code?

[Former Member]

You can only use user roles/profiles. This is the standard way to achieve the requirement.

Else you try SM01 to lock/unlock transaction for ALL the users in the system (developer users too).

In your case i think the problem is related to User Profiles or Users Parameters.

Please note for example that sometimes roles are done checking a specific authority object but by default when you run a transaction the user load a forbidden value.

For example in BMBC...here you have to set the user parameter BICUG or the transaction will fail to run properly (if you set a specific authority check on BMBC layout type).

So...check SU3 for users parameters. Maybe you will find the solution there..else only the roles can be the problem.