CUA - Adding Child systems after implementation

[Former Member]

Hello all, just have a quick question:

We have about 10 systems all with 8-10 clients in each of them and are in desperate need of the CUA. I wanted to just do a couple of systems at first so that everyone could get used to the CUA and then add the rest of the systems at a later time. Is there anything wrong with this? Or does the whole distribution model have to be setup BEFORE setting up the CUA?

Thanks

[Former Member]

Hi Jason,

I wanted to just do a couple of systems at first

It will be a good idea to add only few client (non-critical) to CUA initially. This will give better idea on configuration and issues that you may encounter. Later you can add other critical systems.

first so that everyone could get used to the CUA

Only Basis or Security will get used to CUA, for users it will be transparent.

-Pinkle

[Former Member]

Ok thank you and yes I am aware that only security/basis will be using it... that's who I was talking about

[Former Member]

you dont need to add all the clients into distribution model. you can do it whenever you want.

[Former Member]

Hi Jason,

workign on CUA is very easy. The idea of implementing CUA with a few clients is a good idea, but, including all clients does not result in any wrong usage, as, users are transparent with this setup, only security team works on CUA.

for any reference on configuration of CUA, below link is good:

http://sapbasisnotes.blogspot.com/search/label/CUA%20CONFIGURATION

[Former Member]

Thanks for all your help

[Former Member]

i know your question is answered but i wanted to add my comment anyway - i was not around the last few days ... so: endure it now !

there's no restriction as to when to add other clients/systems to your distribution model. you can go step by step here if you like.

i have an adivce anyway: normally i do it systemwise (not client-wise) because in that way i find it more transparent what ports (WE20/21) and rfc-destinations (SM59) i have created (because i maintain them with the same names/numbers in all the systems in one landscape - just in case there is a system-copy to a new sandbox or somesuch ... then my settings will already be there).

but that's just a personel preference.