Hi Sisila,
In terms of design, ideally CUA should resides in a system that has minimum downtime. The reason is because if CUA is down for system maintenance, managing user master records in child systems might cause an issue. Hence, Solution Manager is a good choice and the rest of the SAP systems should be the child systems.
Other design settings that you might need to think about include if you are going to allow changing passwords in child systems, locking user-ids in child systems etc that you could control in txn SCUM. The benefits of allowing is, you could still manage these activities in case your CUA is not available.
Lastly, do a Pilot run first with a few non-Prod child systems and see how it goes. This allows you to foresee issues that you could potentially encounter in your SAP environment e.g. too many idocs generated and system parameters need to be adjusted to meet the needs etc.
CUA is a very mature technology so you can find many OSS notes and documentation to resolve what you might have encounter. I implemented it in 2010 and we never look back. By far, this is one of the most value-added function to implement if Identity Management implementation is yet to be possible in an organisation.
Cheers.
Annie
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.