03-06-2008 8:37 PM
03-06-2008 8:47 PM
get your developers to code in appropriate AUTHORITY-CHECK statements and logic into their custom programs linked to the Z tcodes
03-06-2008 9:01 PM
In addition to Alex's advise, please also consider calling function module AUTHORITY_CHECK_TCODE if it is a report transaction. There are also export parameters via which you can check whether the transaction can be called or not, and by which tcode. You can maintain these transaction pairs in SE97.
For some other transaction types (see FB01, or SE16 for example), there is a possibility to add an additional authorization object to be checked with values (optional) at the transaction start in transaction SE93. There are some old transactions which still check S_TCODE in there, but they usually check some sort of mutually inclusive authorization required to use the transaction.
Cheers,
Julius
03-07-2008 12:43 PM
Hi,
I strongly suggest to add the ztransactions and objects with transaction SU24 to the table usobt_c, so they will be available when using transaction PFCG when creating/maintaining roles.
Have fun
Bye
Jan van Roest
03-07-2008 2:08 PM
Hi Jan,
Yes, that is a very good point.
Also for customizing transactions...
Cheers,
Julius