Potential problem with RSUSR002 reports

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?

    Requires Free Membership to View

    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

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

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.

This was first published in June 2003