SU53 as first transaction code on login

[Former Member]

Hi All,

When i execute SU53 as the first transaction code on logging in, the following output is obtained

Object Class BC_A

Authorization Obj. S_CTS_SADM

CTS_ADMFCT TABL

DESTSYS <SID>

DOMAIN ' '

Why is this so?

Regards,

[Former Member]

Hi,

SU53 is used to check most recent authorization failure. Whenever a user executes a transaction to which that user is not authorized the same gets reflected in SU53 along with the user's buffer only if SU53 is executed immediately after the failed authorization.

Now BC_A is basis administration object class. I am not pretty sure about this error. But try executing this transaction after breaching some authorization. I think you wont get similar result then.

Good Luck,

Rasheed

[Former Member]

Take a look in the include SUSR0001. It would appear that someone activated the SAPGui logon exit to do something after the user has logged on.

My guess is that it is calling one of the thuser* functions to find the application server which the user is logged onto and then there is a check table behind it somewhere.

Possibly the problem is with the technical implementation, but in most cases you can simply ignore this S_CTS_ADMI TABL check.

Cheers,

Julius

[Bernhard_SAP]

Hello gentle*,

S_CTS_SADM is delivred for CTS+

The CTS+ object is checked after the normal CTS-object has been checke w/o success. In this case for 99,9% the object S_CTS_ADMI has been checked beforehand.

As SU53 shows only the last failed check, you won't see the s_cts_admi check in su53, but you would see it if you use ST01.

Why is s_cts_admi checked?

-->

It's a side effect of the more personalized application design. So some applications try to find out, which buttons should be shown - and which are useless because of missing authorizations. Most of this 'hidden or silent' authorization checks will be processed in generic tools like table maintenance or generic application menus. But also while starting the easy access menu!!! That is the case immediatley after log in......

Also if an application stops due too missing authorizations and returns to the easy access menu, the failed authorization check in the application is not latest, because returning to eht easy access the silent check is performed again, and if it fails again, it is displayed in SU53.....

b.rgds,

Bernhard

[Former Member]

Hi

Thanks for your answers ; They are really helpful;

Regards,

Edited by: gentlexyz gentlexyz on Dec 1, 2009 4:44 AM