User admin and authorization

User admin and authorization

User admin and authorization used to be easy in the old days. We defined roles with authorization in R/3 DEV and C&T to R/3 PRO. When Workplace added to our system landscape, user admin and authorization became very difficult. Should we use CUA? Which should be the "central system" in CUA environment, R/3 DEV, R/3 PRO or Workplace? Where to add a user? Where to do the authorization?


    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.

A lot of this is personal preference, but in my experience... It is better to have one CUA setup for non-production clients and instances, and another for production. I would set up CUA to run out of WP controlling production (however in my experience it works best if CUA can have its own client for administration). For Non-Production: I would setup up a client "001" on your Dev box to control all of the other non-production clients. CUA is a great tool, I have implemented it twice, over multiple landscapes and versions. But, it does complicate things. Just wait till you have to do a client copy...


This was first published in January 2002