You are on page 1of 5

WOOLWORTHS LIMITED

CUA Guide
Removing a Child System from Central User
Administration

Version: 1.1 Date: 30/05/2011

Copyright © 2011 by Woolworths IT. All rights reserved. No part of this document may be
presented, reproduced or copied in any form or by any means (graphical, electronic or
mechanical including photocopying, recording tape or by any information storage and retrieval
system) without the express written permission of Woolworths Ltd.
1 INTRODUCTION

1.1 Document Purpose


This document guides you through how to remove ‘Child’ systems from Central User
Administration System (CUA).
The procedure in this guide is an ‘emergency procedure’ to be followed in the event of CUA
being unavailable for whatever reason.
This guide also covers the procedure to reconnect the Child Systems back to CUA when it
becomes available.

2 THE PRODUCTION CUA LANDSCAPE

PSMCLNT100

CUA Future SAP Prod


PSMCLNT160 Systems

PRDCLNT300 BWPCLNT300 PPICLNT300

ALE Distribution Model : WW-PRD-CUA

Currently we have the following systems./ clients in the CUA ALE Model:
• PRDCLNT300 – ECC System
• BWPCLNT300 –BIW System
• PPICLNT300 - PI/XI System
• PSMCLNT100 - Solution Manager System
3 THE CUA ALE / RFC USERS

The User Ids to push iDocs from CUA to Child systems:


PSMCLNT160  PRDCLNT300 : CUA-PRD
PSMCLNT160  BWPCLNT300 : CUA-BWP
PSMCLNT160  PPICLNT300 : CUA-PPI
PSMCLNT160  PSMCLNT100 : CUA-PSM

The relevant ids are setup in SM59 in CUA and the Child system.

4 REMOVING CHILD SYSTEM FROM THE CUA

Procedure in the Central System


...

1. Log on to the child system.


2. Run report RSDELCUA (for example, using transaction SA38).
The system displays the screen Delete Central User Administration. The name of the
distribution model is displayed under Central User Administration.
3. In the Delete group box, choose the Child system option, and enter the child system to be
removed from the CUA (for example, using input help).
Note: Complete CUA option is greyed out. This only allows us to delete child systems.
4. Set the Test indicator, and choose Execute.
The system displays an overview of the data to be deleted.
5. If the test results are satisfactory, choose back and deselect the test indicator. Then
choose Execute.
The system displays an overview of the deleted data.
6. Repeat the above steps in all child systems to remove from the CUA.
Now you are ready to do user Admin in each child system

5 RE-ACTIVATING CENTERAL USER ADMIN – CUA

1. Log on to the Central System (PSMCLNT160).


2. Execute BD64 in Change mode
3. Highlight the ALE Model (i.e. WW-PRD-CUA)
4. Select from Menu : Edit > Model View > Distribute (Pic. ALE Model Distribution)
Pic. ALE Model Distribution

5. In Distribute Model View screen, all the Child systems are displayed. (see below)

Pic. Distribute Model View - Child Systems


6. Select the child systems you wish to distribute by highlighting them.
7. Press continue (Green tick)
8. Successful distribution will show the below message for the Child system being distributed
– Model view ‘Name of the View’ has been changed

Pic. Log of Model View Distribution.

9. If there is an error message in the Log the check the following:


• Transaction SCUA > see if the logical systems names of the child systems are
present. If not enter the names here and then save the systems.
• Check in transaction WE20 to see if the Logical system(LS) entries are present.
• Test the RFC connections in SM59. Test in CUA as well as child systems.
• Ensure that passwords are valid in RFC Ids in SM59.

10. After fixing any errors in 9 go back to step 4 to trigger the distribution of ALE Model.
11. Test to verify that CUA works properly by creating a test id in CUA that has access in
all child systems.
12. Check in Transaction SCUL to verify that iDocs have distributed for all child systems.