Skip to Content

How to cleanup the CUA entries

Hi all,

I'm in the process of doing some client cleanup prior to an upgrade project. I am also just learning about the CUA system so have been reading through the docs.

Our landscape:

UTL - Solution Manager and CUA (7 ehp1)

DEV - Development (ecc5)

QAS - Quality (ecc5)

PRD - Production (ecc5)

This was set up about 5 years ago during intial implementation, and little has been done to manage the CUA child entries to match up with client useage changes over that time. At this point, security uses CUA for some clients and local user admin for others. When I use t-code SCUA I get the message the "CUA definition is inconsistant, for repair see long text." And I beileve the issue it is complaiing about is there are child systems still defined in CUA that don't exist, or no longer have a connection.

I'm wanting to remove these old child systems, and will delete the actual clients where then exist after removing them from CUA.

What I'm not to clear on yet is what happens after I go through the steps on the central system

a. T-CODE SCUA

b. T-CODE WE20

c. T-CODE BD64

Since I'll be deleting the associated clients on the respective system, do I need to do the steps for deleting a CUA child on the local system as well? Then delete the client?

At some point I'll be adding the new CUA child entries for the actual/used clients as well. But I thought I'd go through the delete process first.

Any corrections or clarifications as to what I'm attempting to do will be much appreciated!

Thanks 😉

Laurie McGinley

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Sep 30, 2010 at 05:34 PM

    If I understand you correctly, you are trying to remove some clients that are no longer used or connected. If you have a system connected to CUA and it needs to be disconnected, you should run transaction SA38 and execute for program RSDELCUA. Select the Child system that you want to disconnect and in Test mode, click Execute. If you get the log file with no errors, run this without the Test box checked. This will remove the client system from the CUA landscape.

    Reconnecting Client System back to CUA

    To reconnect a system that has previously been setup in CUA, but was disconnected or a system that was refreshed, you will need to run transaction SCUA and add the client system into the Maintain System Landscape screen. Once completed, you will need to run transaction SCUG to migrate the users back into CUA.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi,

      first perform the deletion (scua or rsdelcua). Afterwards clean up bd64 and we20. You need to clean up we20 and bd64 in the removed child systems as well. If the child has become disconnected already in the past, it will note get the deletion information form the central system (reachability by rfc etc.). Then simply remove the whole stuff in the child with rsdelcua.(and bd64/we20).

      RSDELCUA only removes the CUA relevant table entries, not the ALE stuff. Therefore we20/bd64 clean up is required to be performed seperately.

      b.rgds, Bernhard