Question:
Users want to display program contents. Is there any equivalent transaction of SE38 but gives access to display only ? Thanks
Answer:
Best read the SAP documentation on auth object S_DEVELOP .
Answer:
number of ways round of doing this - Ket is absolutely right about activity 03 on S_DEVELOP -, make sure you have locked down S_PROGRAM too. You might also try looking for other transactions with more interrogation functions: I like SE80 - pretty handy because you can see the transactions that are linked to it in the list of folders beneath.
I am sure a sage once said "never give anyone SE38 in Production".....
_________________
???
Answer:
number of ways round of doing this - Ket is absolutely right about activity 03 on S_DEVELOP -, make sure you have locked down S_PROGRAM too. You might also try looking for other transactions with more interrogation functions: I like SE80 - pretty handy because you can see the transactions that are linked to it in the list of folders beneath.
I am sure a sage once said "never give anyone SE38 in Production".....
SE38 isn't the problem. It is granting access to S_DEVELOP activity 03 without locking down S_PROGRAM authority. That may be mitigated somewhat in te latest versions of SAP has it appears that the code editor accessed from the navigation tools has an authorization check for a transaction code built into it.
_________________
bwSecurity
Answer:
What type of users are asking for this access? I'd find it hard to believe that end users wanted to see ABAP code. If it is developers etc who want to check the code in Production then re-direct them to the QA system.
The main issue is with S_PROGRAM and giving the ability to run any program if this isn't locked down.