Potential problem with RSUSR002 reports
I have found a potential problem when using RSUSR002 report on users
able to use specific transactions. I have modified a role not disallow access to SE38. When the user attempts to access it, a message
stating that the user is not authorized displays across the bottom of the
gui screen as expected. However, when RSUSR002 is executed and SE38 is
entered to check authorized users the unauthorized user id is displayed.
Do you have any idea how that could happen?
When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.
Hannah Smalltree, Editorial Director
I have seen this. The report reads from some several UST* tables and
probably is picking up some bad data somewhere (the include: US002TOP
contains all the data declarations and could have a bug.) I think there is
an OSS note on this already.
Dig Deeper
-
People who read this also read...
This was first published in June 2003