Central User Administration1. Create Users for RFC connection in Both Central and child systems:EC2---> Central system--> EC2CLNT001EC3---> Child system--> EC3CLNT001C7D---> Child system--> C7DCLNT800In central system: Create service user (CUA_EC2) Using SU01:

Enter all details of user and clicks save:

In Child system:Create service user (CUA_EC3) using su01:

Enter all details all user and click save:

Create Logical systems in both central and child systems using BD54:In central system: Go to BD54 Click ok

Click new entries:

Enter logical system and name:

Click ok:

Click ok:

Create own request:

In child system:Create Logical system using BD54 click ok:

Enter Logical system and name and click save :

Click ok:

Create own request:

Click ok:

Assign logical system to client in both systems:In Central system (EC2)Go to SCC4 Click change and display:

Select Logical system and click save:

Clicks continue:

In Child system (EC3):Go to SCC4 Click continue:

Select logical system and click save:

Click ok:

Create RFC connection Using SM59:In Central system (EC2):Go to SM59 Create connection type 3:

Enter technical setting values:

Enter Logon and security details:

Click ok:

RFC Connection test:

In Child system (EC3)RFC creation using SM59:

Enter RFC details and technical setting details

Enter Logon and security details of EC2 And click save:

Click continue:

Connection test:

Create a model view in Central system using BD64 Click change and edit :

Click creates model view:

Enter Model view name and text details:

Model view created:

After creating Model view Click Add BAPI:

Enter sender and receiver Logical system, interface and method name:

Enter sender and receiver Logical system, interface and method name for maintaining company Address:

Clicks Save:

Generate partner profiles BD64 --> Environment --> generate Partner profiles:

Enter Model View and Partner systems execute:

Partner profile created:

Create Distribute model in BD64 -->edit -->model -->distribute model click:

Select Model View:

Click Continue:

Already Selected Logical systems shown below click continue:

Distributed Model is created:

Create CUA using SCUA:Select or Enter Model view And click create:

Enter child systems and save selected systems:

Clicks continue:

Finally click Complete Save:

Central User Administration (CUA) configured:

Adding one more child system using BD64:For Adding one more child we need create one service user (CUA_C7D) in Child system Using SU01 and also create a Logical Systems (C7DCLNT800 & EC2CLNT001) using BD54 and assign child client. After this create RFC connections For C7D Name as C7DCLNT800 Using SM59 in Central system and EC2CLNT001 In child systems.Add child system in Model view Using BD64Click change and edit click Add BAPI:

Enter sender and receiver Logical system, interface and method name:

Enter sender and receiver Logical system, interface and method name for company Address:

Clicks save:

Generate partner profiles BD64 --> Environment --> generate Partner profiles:

Enter Model view and child system details:

Profiles generated:

Create Distribute Model Using BD64 -->Edit-->Model view -->Distribute:

Select Model view and click continue:

Shown below selected child systems automatically clicks continue:

Distributed model is created:

Go to SCUA:Click change and select one more child system:

Clicks continue:

Click complete save:

One more child system is created:

CUA Logs checking using SCUL:

Select all distribution status check boxes:

Now we can see any error, succesful, unconfimed or Warning is there or not:

Removing child systems from central system using SA38:Run report RSDELCUA

From below screen you can select child system or total CUA or any invalid content in CUA tables:

Here shown table name all data about selected system, here selected the test indicator because it is for testing:

This is in test mode if we need to delete come back and deselect the test indicator and save.After this saves and delete the data about the central system and child system in Using WE20:This data was under partner profiles---> partner type LS Select the system and delete one by one:

After this you can log in into child system and delete data using WE20:

Transfer user from central to child systems using SALE or SCUG or In the Implementation Guide (IMG, transaction SALE), chooseModeling and Implementing Business ProcessesPredefined ALE Business ProcessesCentral User AdministrationTransfer Users from New Systems:

Place the cursor on the central system and chooseTransfer Users:

1) New users: These users are not yet contained in central user administration. By choosing Transfer users, you can transfer the selected users into the central system. This transfers all user parameters such as address and logon data, as well as profiles and roles. In the future, the user will be maintained centrally.

2) Identical users: These are users with identical user IDs (that is, their name and user name is the same). You can transfer these users into the central system. Local data is overwritten.

3) Different users: These users are already in central user administration but under different user IDs. Rename these users in the dependent system to the correct user name that is centrally maintained, or correct the name of the user in the user address, so the user can be transferred in the next step.

4) Already central users: These users are already in the central user administration under the same name. This user is already maintained centrally.

After this we can select any users and click transfer:

We need to transfer users from child to central you can Place the cursor on the central system:

Click transfer users:

Synchronize company addresses using SCUC:

Now see synchronization of the company addresses:

If we need to use a particular user in particular system we need assign a particular system in system tab using SU01:

Set field distributor parameters using SCUM:Select change and display:Now available to give parameters it is used to maintain parameter between central and child system:

1) Global: Data can only be maintained in the central system and is completely distributed.

2) Proposal: A default value is maintained in the central system. This value is distributed when a user is created and is then maintained locally.

3) Redistribution: Data is maintained both centrally and locally. Each time data is changed locally; this change is redistributed to the central system and from there distributed to the other dependent systems.

4) Local: Data can only be maintained in the dependent system. Data changes are not distributed to other systems.

5) Everywhere: Data is maintained both centrally and locally. However, data changes are not redistributed to other systems.