Central User Administration- Guide to Setup & Administration of the CUA

7/31/2019 Central User Administration- Guide to Setup & Administration of the CUA

1/3

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

[email protected](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 theSAP system one at a time. Unfortunately SAP's traditional solution to that problem, known asCUA, has a reputation for causing even more headaches than it solves. But with newer releasesof SAP, CUA is able to automate those repetitive tasks into an effective tool for user mgmt on abroad level. Joey explains the process of setting up CUA step by step & closes with a section onuser mgmt. within CUA & a handy chart of common CUA setup errors with their resolutions.

Click here to read this Snippet
http://www.erptips.com/Snippets/jaqhcpergb.pdf#page=2http://www.erptips.com/Snippets/jaqhcpergb.pdf#page=2


2/3

SAPtips 2004 Klee Associates, Inc.

Page5

April/May2004VolumeIIIssue2

www.S

APt

ips.com

SAPtips

SAPtips

result in nothing - quite anticli-mactic. This actually indicates asuccessful logon. A logon screenwould indicate that the user id orpassword was incorrect.

Set Up CUANow that we've done these five

preliminary steps, we're ready tosetup CUA.

1. Logon to the parent, SX20and execute transaction coSCUA. Create the CUname, CUA_300, as shownFigure 10.

Next, enter the logical systename for both child system(SX3777 and SX4707). The lastep is to save. The successfresult is green traffic lights. Ared means an error. If any errooccur, investigate the causes anfix, or, if needed, create a neCUA. For common errors a

solutions, see Figure 12 in the setion titled Common Problems nethe end of this article.

That should have been painleenough. The actual setup shoube relatively trouble-free if preparatory tasks are performas designed and planned. Tnext steps involve configuratiand moving users into CUA.

2. Use transaction code SCU

to customize field distribtion in CUA control. Cutomize means: what data dwant to control, and wherSee Figure 11 for the SCUfield selection screen.

The following are definitions the selection options: GlobLocal, Proposal and RetVal.

Journal

Journal

Figure 9: Creating New RFC Destinations Using Transaction Code SM59

Create in RFC Destination Type Hostname System Number Username PasswordName

SX2 SX2010 3 Hostname of SX2 System Number of SX2 CUA_SX2 SOMEPASS

SX2 SX3777 3 Hostname of SX3 System Number of SX3 CUA_SX3_777 SOMEPASS

SX2 SX4707 3 Hostname of SX4 System Number of SX4 CUA_SX4_707 SOMEPASS



Figure 10: Creating CUA Name CUA_300

Figure 11: CUA Field Selection Screen


3/3

SAPtips 2004 Klee Associates, Inc.

Page6

April/May2004VolumeIIIssue2

www.S

APt

ips.com

SAPtips

SAPtipsJournal

Journal

Global:Data is only maintained in the

parent. Changed data is automat-

ically 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. Aftercreation and transmission, data isonly maintained in the childclient.

RetVal:Data is maintained in both par-

ent and child. Any change in thechild will be distributed back tothe parent. Changes are then dis-tributed to other child clients.

3. The next step is to maintainassignment of Companyaddress data with reportRSADRCK2 in the child.

4. Import Company addressdata using transaction codeSCUG. Import data by childname. Check for any dis-crepancies between the Com-pany address data in theparent and in its childrenwith transaction codeSUCOMP. After data is cor-rect in the parent, distributeto children. Perform this stepfor all children.

5. Ensure user groups that existin the children also exist inthe parent and vise versa.Use transaction code SUGRto display and maintain theuser groups. This must bedone manually in all childrenand parents.

6. Transfer users to parentusing transaction code SCUG

for each child. Import new,identical, and different usersunder CUA control. Newusers will be added to CUA asmetadata per the child. Iden-tical and different users willbe included in CUA withmetadata stored in CUAtransferring to the child.

7. Check for any errors and cor-rect via transaction codeSCUL.

8. Schedule a job that executesreport SUSR_ZBV_GET_RECEIVER_PROFILES in

the parent. This job synchro-nizes the movement of rolenames between child andparent. In short, it informsthe parent of any text changeswhich have occurred in thechild. This way, users can beassociated to the current rolesdefined in the child.

9. Check CUA setup by con-firming

the existence of all childrenin the distribution model(transaction code BD64)

and

the existence of all childrenin the CUA model (transac-tion code SCUA).

10. Remove roles SAP_BC_USR_CUA_SETUP_CEN-

TRAL and SAP_BC_USRCUA_SETUP_CLIENfrom the communicati

users after CUA setup complete.

Operations with CUANow that the setup is comple

let's go over some operationtasks like:

Creating users

Locking users

Changing password

Assigning roles to users

Resolving common CUproblems

Creating usersAll administrative tasks a

now performed from the pareusing the standard user maintnance transaction SU01. Tonly additional item is t

appearance of a Systems taHere we specify where the usexists. As an example, lets creauser TEST only in child clieSX4707.

1. Log on to the parent SX20with a user that has usmaintenance authorizatioIn addition to standaauthorizations, the user mualso have authorizatiS_USER_SYS.

2. Assign values in Address anLogon data.

3. Assign values in Systems tby selecting SX4707.

4. Assign values in the roles taNotice an additional columappears. This column spefies which role the user haswhich system.

Check for any errors

and correct via

transaction code

SCUL.

Central User Administration- Guide to Setup & Administration of the CUA

Documents

Transcript of Central User Administration- Guide to Setup & Administration of the CUA