CUA - Central User Admin - Issues and Learning

Question: Hi all

Anyone would like to share any major issues or learning or even any undocumented features for implementing CUA. One of our client is likely to be taking a decision for implementing CUA involving about 20+ systems.

Any inputs be much appreciated.

Thanks
_________________
SAPFAN

Answer:
If you start by reading the OSS notes at service.sap.com related to CUA you will be busy for a while and maybe reconsider.

Answer:
While some use CUA to contorl EVERYTHING and beleive all is fine, CUA was NOT built to do what you want. Its design was to manage WORKPLACE and ONE production client. CUA was to be configured on the Workplace system and control it and the production client. The product is NOT robust enough to meet stringent qualtity contorls nor has enough reconcilliation report to assist in its problems.

Answer:
I am not a big fan of CUA, but I strongly disagree with what John Jarboe has said in the previous post. I believe that it can be used to manage multiple production systems. In fact using it from Solution Manager across R/3, CRM, BW EBP can be ok. I wouldn't use it to manage test and development systems. It is too much trouble.

The problem with the CUA concept is that SAP has been branching out. EBP and CRM security have some novelties that are not well handled by CUA. BW also has some issues that CUA does not deal with well. And then what about personaliztion etc.? or HR integration?

Unfortunately user administration is a bit of a hodge-podge. Perhaps someday SAP will address the little mess they have created.

Answer:
I did not indicate it coulld NOT be used for multiple production system/client, just that it is not robust enough to do so, as your post indicates