CUA for ECC6

Checklist before CUA

SM59 – Connectors (Setup by Basis)

Make sure the connectors are created.

Check they are pointing to the correct system. If not, inform Basis
Check which User is used for connection. Make sure the PW status is entered else it will prompt a logon
pad. Check also the ALEREMOTE user id has SAP_ALL in the other destinations.

T-code: WE21 – Check that the ports are created. if the pointers are available, check that they are
configured to the correct system. Click on them to check.
t-code WE20 – Check that there are 3 basic outbound parameters.

CCLONE, SYNCH and USERCLONE

Only the ‘Outbound Options’ is essential. All other tabs are not. Make sure the ‘Receiver port’ is selected
correctly  related to t-code WE21.
t-code: SALE (define logical systems)

check that all the logical systems are set up

Check that the RFC settings are correct for the Target System in the role

t-code: SM30  SSM_RFC

Check that the Variables are pointing to the RFC Destination.

t-code: SCUA.

*First is to CUA ECC only. This step is important cos for some reason, if we do not CUA ECC only, the ECC
in the ‘System’ tab will disappear.
t-code: SU10 – Assign the ECC in the system tabs for all the users. using the transfer users for ECC will
take too long and will typically time out.

Do it in groups like A* or B* and etc. Select unlock users only.

Select ALL and ‘Transfer’
Enter the system and then the ‘Save’ button. Acknowldge the next pop up box.
In the SCUA, enter the system for CUA. Click ‘Save Selected System’.

It should have an end result as below. If not, check the message and all the settings as above.
Go through each tab and click ‘Transfer users’. all the users should be in ‘Already Central user;’.

Sometimes there are some users which cannot be transferred cos they do not have last name. ignore
them.
To break complete CUA.

Select any systems or complete CUA

Execute in Background is faster.

BD64