How To Fix 01672 - Child system &1 is part of another CUA, &2 (CUA &3 not activated)

SAP Error Message - Details

• Message type: E = Error

• Message class: 01 -

• Message number: 672

• Message text: Child system &1 is part of another CUA, &2 (CUA &3 not activated)

What causes this issue?

The child system &V1& is already part of the CUA &V2&, which is
administered from the central system &V4&.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

The CUA &V3& has not been activated in this child system (&V1&).

How to fix this error?

If you actually want to move the child system &V1& from the CUA &V2& to
the CUA &V3&, first remove it by calling the report RSDELCUA in the old
CUA central system (deletion option: Child Systems).
If this has been caused by an inconsistency, and the child system &V1&
is no longer registered with the old CUA (&V2&), delete the old CUA data
by calling the report RSDELCUA locally in the child system &V1&
(deletion option: Invalid Content in CUA Tables).

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 01672 - Child system &1 is part of another CUA, &2 (CUA &3 not activated) ?

  The SAP error message 01672 indicates that the child system you are trying to add to a Central User Administration (CUA) is already part of another CUA. This situation arises when you attempt to include a child system in a CUA configuration, but that child system is already associated with a different CUA.
  Cause:
  
  Existing CUA Association: The child system (&1) is already linked to another CUA (&2), which prevents it from being added to the new CUA (&3).
  CUA Not Activated: The CUA you are trying to add the child system to is not activated, which can also lead to this error.
  
  Solution:
  
  
  Check Current CUA Configuration:
  
  Use transaction code SU01 or SU10 to check the user assignments and see which CUA the child system is currently associated with.
  You can also check the CUA settings in transaction SCUA to see the current configuration.
  
  
  
  Remove from Existing CUA:
  
  If you want to move the child system to a new CUA, you will need to remove it from the existing CUA. This typically involves:
  
  Accessing the existing CUA configuration (using SCUA).
  Removing the child system from the CUA.
  
  
  
  
  
  Activate the New CUA:
  
  Ensure that the new CUA (&3) is properly activated. You can do this in transaction SCUA by checking the activation status and making sure all necessary configurations are in place.
  
  
  
  Re-add the Child System:
  
  After removing the child system from the old CUA and ensuring the new CUA is activated, you can attempt to add the child system to the new CUA again.
  
  
  
  Related Information:
  
  CUA Overview: Central User Administration (CUA) allows for centralized management of user accounts across multiple SAP systems.
  Transaction Codes:
  
  SCUA: Central User Administration configuration.
  SU01: User maintenance.
  SU10: Mass user maintenance.
  
  
  Documentation: Refer to SAP Help documentation for detailed steps on configuring CUA and managing user accounts.
  
  Important Considerations:
  
  Ensure that you have the necessary authorizations to make changes to CUA configurations.
  Always back up your configurations before making significant changes to avoid data loss or misconfigurations.
  Test the changes in a development or test environment before applying them to production systems.