Central User Administration: Guide to Setup & Administration of the CUA Below is a snippet from one of hundreds of articles

available to ERPtips subscribers. If you would like a complimentary copy of the full article, please email Mark.Downs@ERPtips.com (include the title of the article in your email) To subscribe to ERPtips, go to www.ERPtips.com/Subscribe.asp. ERPtips Journal is published by Klee Associates, Inc. ERPtips University provides both public and onsite training for SAP clients. For more about ERPtips University, including the current schedule, click here: www.ERPtips.com/WorkshopSchedule.asp

Central User Administration: Guide to Setup & Administration of the CUA SAP users dread a repetitive task. Few tasks are more repetitive than adding new users to the SAP system one at a time. Unfortunately SAP's traditional solution to that problem, known as CUA, has a reputation for causing even more headaches than it solves. But with newer releases of SAP, CUA is able to automate those repetitive tasks into an effective tool for user mgmt on a broad level. Joey explains the process of setting up CUA step by step & closes with a section on user mgmt. within CUA & a handy chart of common CUA setup errors with their resolutions.

Click here to read this Snippet

SAPtipsJournal
www.SAPtips.com
Page 5

Create in
SX2 SX2 SX2 SX3 SX4

RFC Destination Name

SX2010 SX3777 SX4707 SX2010 SX2010

Type
3 3 3 3 3

Hostname
Hostname of SX2 Hostname of SX3 Hostname of SX4 Hostname of SX2 Hostname of SX2

System Number
System Number of SX2 System Number of SX3 System Number of SX4 System Number of SX2 System Number of SX2

Username
CUA_SX2 CUA_SX3_777 CUA_SX4_707 CUA_SX2 CUA_SX2

Password
SOMEPASS SOMEPASS SOMEPASS SOMEPASS SOMEPASS

Figure 9: Creating New RFC Destinations Using Transaction Code SM59

result in nothing - quite anticlimactic. This actually indicates a successful logon. A logon screen would indicate that the user id or password was incorrect.

Set Up CUA Now that we've done these five preliminary steps, we're ready to setup CUA.

1. Logon to the parent, SX2010 and execute transaction code SCUA. Create the CUA name, CUA_300, as shown in Figure 10. Next, enter the logical system name for both child systems (SX3777 and SX4707). The last step is to save. The successful result is green traffic lights. Any red means an error. If any errors occur, investigate the causes and fix, or, if needed, create a new CUA. For common errors and solutions, see Figure 12 in the section titled Common Problems near the end of this article. That should have been painless enough. The actual setup should be relatively trouble-free if all preparatory tasks are performed as designed and planned. The next steps involve configuration and moving users into CUA. 2. Use transaction code SCUM to customize field distribution in CUA control. Customize means: what data do I want to control, and where. See Figure 11 for the SCUM field selection screen. The following are definitions of the selection options: Global, Local, Proposal and RetVal.

April/May 2004 Volume II Issue 2

Figure 10: Creating CUA Name CUA_300

SAPtipsJournal

Figure 11: CUA Field Selection Screen

SAPtips 2004 Klee Associates, Inc.

SAPtipsJournal
www.SAPtips.com
Page 6

Global: Data is only maintained in the parent. Changed data is automatically sent to the child client. Local: Data is only maintained at the child and not redistributed. Proposal: A default value is created in the parent and sent to the child. After creation and transmission, data is only maintained in the child client. RetVal: Data is maintained in both parent and child. Any change in the child will be distributed back to the parent. Changes are then distributed to other child clients. 3. The next step is to maintain assignment of Company address data with report RSADRCK2 in the child. 4. Import Company address data using transaction code SCUG. Import data by child name. Check for any discrepancies between the Company address data in the parent and in its children with transaction code SUCOMP. After data is correct in the parent, distribute to children. Perform this step for all children. 5. Ensure user groups that exist in the children also exist in the parent and vise versa. Use transaction code SUGR to display and maintain the user groups. This must be done manually in all children and parents. 6. Transfer users to parent using transaction code SCUG

Check for any errors and correct via transaction code SCUL.
for each child. Import new, identical, and different users under CUA control. New users will be added to CUA as metadata per the child. Identical and different users will be included in CUA with metadata stored in CUA transferring to the child. 7. Check for any errors and correct via transaction code SCUL. 8. Schedule a job that executes report SUSR_ZBV_GET_ RECEIVER_PROFILES in the parent. This job synchronizes the movement of role names between child and parent. In short, it informs the parent of any text changes which have occurred in the child. This way, users can be associated to the current roles defined in the child. 9. Check CUA setup by confirming the existence of all children in the distribution model (transaction code BD64) and the existence of all children in the CUA model (transaction code SCUA). 10. Remove roles SAP_BC_ USR_CUA_SETUP_CENSAPtips 2004 Klee Associates, Inc.

TRAL and SAP_BC_USR_ CUA_SETUP_CLIENT from the communication users after CUA setup is complete.

Operations with CUA Now that the setup is complete, let's go over some operational tasks like:
Creating users Locking users Changing password Assigning roles to users Resolving problems common CUA

April/May 2004 Volume II Issue 2

Creating users All administrative tasks are now performed from the parent using the standard user maintenance transaction SU01. The only additional item is the appearance of a Systems tab. Here we specify where the user exists. As an example, lets create user TEST only in child client SX4707.
1. Log on to the parent SX2010 with a user that has user maintenance authorization. In addition to standard authorizations, the user must also have authorization S_USER_SYS. 2. Assign values in Address and Logon data. 3. Assign values in Systems tab by selecting SX4707. 4. Assign values in the roles tab. Notice an additional column appears. This column specifies which role the user has in which system.

SAPtipsJournal