I did not always think this way, and certainly there are exceptions to "lock things" at times, but I do agree with Mohammed... locking transactions is should not be used to protect functionality. You should use authorizations to use the functionality... to protect it or grant access to it.
Its the best procedure to asign/revoke the access of the specific T-Codes for a particular user. Locking the tcodes in SM01 lock it for entire client, and affect all the users.
You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
Add a comment