Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from henrikmadsen2 on Feb 11 at 7:31 AM the removal of SE16 should not stop other transactions from working. What
you may find is that you also removed S_TABU_DIS/ S_TABU_NAM when you
removed SE16 - and that is the problem.
But that is down to a less-than-ideal role design, more often than not. The
table related auth objects should be available with the transactions that
require them, such as OB52 and many others. If not, you will run into
trouble when stripping out SE16 access...
Hope that helps
/henrik
| | | ---------------Original Message---------------
From: Tushar
Sent: Thursday, February 11, 2016 12:03 AM
Subject: When Tcode SE16 Removed then Others Tcodes Or Reports Not Working?
I want to remove Tcode SE16 from pfcg from many roles, but when it is done, then many reports or tcodes not working properly, getting error, and I also do not want to give SE16 tcode. Though they have only display rights, because of security issues. So is there any way to do it. So that SE16 can be removed and all reports and tcodes also working fine?
Thanks |
| Reply to this email to post your response. __.____._ |    _.____.__ |
