SCUA

16
Generated by Jive on 2013-03-18+01:00 1 CUA Configuration steps Steps need to be performed to set up the CUA: Steps to Set Up the CUA 1. Create Administrator 2. Specify Logical systems 3. Assign logical systems to client 4. Create system users 5. Create RFC destinations 6. Create CUA 7. Set field distributor parameters 8. Synchronization of company addresses 9. Transfer Users Below are the systems considered as an example to set up CUA: System ABC with client 123 System PQR with client 456 System XYZ with client 789 Here, we will set system ABC (client 123) as a CUA central system(D16 is also refered as CUA system) and other systems(T16,PQR and XYZ) as child systems. As per this structure, we will proceed with above mentioned steps: 1. 1. Create Administrator User In a completely new system that is to be set up, an administration user needs to be created with which all further steps can be performed. To create such administrator user: Login to all systems with user SAP* and create the user in t-code SU01 Assign the relevant administrator role to user Apply the security measures to secure SAP* user against misuse

description

cua

Transcript of SCUA

Page 1: SCUA

Generated by Jive on 2013-03-18+01:001

CUA Configuration steps

Steps need to be performed to set up the CUA:

Steps to Set Up the CUA

1. Create Administrator2. Specify Logical systems3. Assign logical systems to client4. Create system users5. Create RFC destinations6. Create CUA7. Set field distributor parameters8. Synchronization of company addresses9. Transfer Users

Below are the systems considered as an example to set up CUA:

• System ABC with client 123• System PQR with client 456• System XYZ with client 789

Here, we will set system ABC (client 123) as a CUA central system(D16 is also refered asCUA system) and other systems(T16,PQR and XYZ) as child systems. As per this structure,we will proceed with above mentioned steps:

1. 1. Create Administrator User

In a completely new system that is to be set up, an administration user needs to be createdwith which all further steps can be performed. To create such administrator user:

• Login to all systems with user SAP* and create the user in t-code SU01• Assign the relevant administrator role to user• Apply the security measures to secure SAP* user against misuse

Page 2: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:002

2. Specify Logical systems

In CUA landscape, SAP systems are identified with Logical system names. Due to this,Logical systems need to be created for every system which is going to be included inCUA landscape. This is one time task to be performed before setting up CUA. The Logicalsystems can be defined be following below steps:

• Login to system ABC (client 123) with administrator user created in step 1• Go to t-code BD54 You can; alternatively maintain the table view V_TBDLS using transaction SM30.• Choose Edit ? New Entries

In the LogSystem column, create a new logical name in capital letters for every CUA system (that is,for the central and all child systems including those from other SAP Systems). Here, the standardnaming convention for logical system is <System ID>CLNT<Client>. In this way, the below logicalsystems will be created in CUA central system (ABC system):

• ABCCLNT123• PQRCLNT456

Page 3: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:003

• XYZCLNT789

In the same way, create the logical system name for the central system in all childsystems.

D16 is CUA and it has T16 logical system in BD54

T16 is child and it has CUA D16 logical system in BD54

Page 4: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:004

3. Assign logical systems to client

We need to perform this cross-client procedure only once for each SAP system as perbelow procedure:

• Login with administrator user and execute the t-code SCC4• Switch to change mode• Call the detail display of the client that you want to assign a logical system by double clicking on the line of

the client• In the Logical System field, specify the name of the logical system to which the selected client is to be

assigned

Page 5: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:005

  Ex: – If we execute the t-code SCC4 in system ABC then, open the client 123and maintain the logical system name as ABCCLNT123  

Assign logical system name in scc4

4.Create system users

System users are required for the internal communication of the systems in an ALE group.These system users, defined in the target systems, are entered in RFC destinations in thecalling systems.

Note: – No license fees apply to these system users.

Page 6: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:006

To simplify the maintenance of system users, use the following naming conventions:

• In the central system (system ABC), the naming convention will be CUA_<system Id>. This system user isused in the RFC destinations from child to central system. With this naming convention, we need to createthe system user in system ABC with name: CUA_ABC

• In the child systems, the naming convention CUA__<System Id>_<Client>. These system users are usedin the RFC destinations from central to child system. With this naming convention, we need to create thesystem users as below:

Table 1

Below are SAP delivered roles for system users which need to be copied to customernamespace before assigning them to system users.

Roles in Central system:

• SAP_BC_USR_CUA_SETUP_CENTRAL• SAP_BC_USR_CUA_CENTRAL• SAP_BC_USR_CUA_CENTRAL_BDIST

Roles in child system:

• SAP_BC_USR_CUA_SETUP_CLIENT• SAP_BC_USR_CUA_CLIENT

With these details, we need to create the respective users with their applicableauthorizations in t-code SU01 as below:

Table 2

Create users with above roles in child system to maintain in CUA system RFC’sfor connection between CUA and child systems.

D16

Page 7: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:007

T16

Page 8: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:008

5. Create RFC destinations

Till this step, we are ready with Logical systems and system users, Now, we need to createRFC connections between the systems as mentioned in below steps:

• Login to central system ABC, execute the t-code SM59 and Choose Create.

Table 3

Note: – You must create the name of the RFC destination in capitalletters.

Page 9: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:009

• Confirm your entries with ENTER• Choose the option Host Name for Save as and Confirm your entries with ENTER• Specify the name of the SAP system of the child system (such as PQR) in the target system ID field. To do

this, overwrite the automatic entry.• Specify the message server of the target system in the MessageServer field. To do this, overwrite the

automatic entry.• Save your entries.• To define the return connection, repeat the procedure in the child system for the central system• To determine whether the network connection between the two systems is functioning correctly, choose

Test Connection.

In this way, we have created the RFC connections (with names identical to Logicalsystem name of target system) in each SAP systems.

6. Create CUA

Till now, we have connected all the systems ABC, PQR and XYZ as in below figure:

Page 10: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:0010

figure – Create CUA – Central User Administration

Now, we will define the system ABC as CUA in this landscape as detailed in below steps:

• Login to system ABC and execute the t-code SCUA• Enter the name of your distribution model, such as CUA.• Choose Create.• Enter the name of the child systems viz. PQRCLNT456 and XYZCLNT789• Save your entries.

In this way, we have defined the system ABC as central system. After completion ofthis step, you can no longer create user master records in the child systems.

SCUA IN D16

Page 11: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:0011

Page 12: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:0012

7. Set field distributor parameters

In Central User Administration, we can use the distribution parameters in transaction SCUMto determine where individual parts of a user master record are maintained.

• In the central system• Locally in the child system• In the child system with automatic redistribution to the central system and the other CUA child system

Every input field of the user maintenance transaction SU01 has a field attribute that youset once in the central system with transaction SCUM during Customizing. To perform thiscustomizing, perform the below steps:

Page 13: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:0013

• Login to system ABC and execute the t-code SCUM

The system displays the User Distribution Field Selection screen, with tab pages of the fieldswhose distribution parameters you can set. You can select the following options on the tabpages:

SAP Set field distributor parameters

• To maintain the other parameters, too, switch to the other tab pages. The tab pages correspond to those ofuser maintenance.

• Save your entries. The distribution parameters are automatically transferred to the child systems.

SCUM IN D16

Page 14: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:0014

8. Synchronization of company addresses

The company addresses are maintained in individual systems PQR and XYZ. To enableCUA to communicate properly you must ensure that at least the central system containscomplete information about all valid company addresses. You then distribute this completecompany address set to all child systems, meaning that there is a consistent status ofcompany addresses in the entire CUA.

Steps:

• Login to central system ABC and execute the t-code SCUG• Select the first child system PQR and choose Synchronize Company Addresses in the Central System• Process all sub lists for the address categories in succession and repeat the above steps for system XYZ• Choose Back to start the address distribution from the central system.• Choose Distribute Synchronized Company Addresses to target Systems icon.

SCUG IN D16

Page 15: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:0015

1. 9. Transfer Users

As soon as we have configured the CUA, the users from child systems need to betransferred to Central system so that we can see their authorization details (such as rolesto be assigned to users for child system and the roles assigned to them). The procedure isgiven in below steps:

• Login to central system ABC and execute the t-code SCUG• Place the cursor on central system name appeared on the screen and click on the Transfer Users.• The system displays the following tab pages:

Page 16: SCUA

CUA Configuration steps

Generated by Jive on 2013-03-18+01:0016

SAP Transfer User

• Select all new and changed users and choose Transfer Users.• Perform the above 2 steps for child systems PQR and XYZ• After you have completed the user transfer, remove the roles Z_SAP_BC_CUA_SETUP_CENTRAL and

Z_SAP_BC_USR_CUA_SETUP_CLIENT from the system users.

At this stage, the CUA set up is completed.