How To Fix 01792 - The status of child system &1 has been changed

SAP Error Message - Details

• Message type: E = Error

• Message class: 01 -

• Message number: 792

• Message text: The status of child system &1 has been changed

What causes this issue?

CASE &V2&.
WHEN 'X'.
All users of child system &V1& have already been transferred to Central
User Administration (CUA).
The identifier of the child system with status #New# was removed.

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

WHEN 'Z'.
The client was included in Central User Administration. The child system
&V1& gets the status #New#.
WHEN OTHERS.
In child system &V1&, there are users who have not been transferred to
Central User Administration (CUA) yet.
ENDCASE.

How to fix this error?

Transfer these by using transaction SCUG.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 01792 - The status of child system &1 has been changed ?

  The SAP error message "01792 The status of child system &1 has been changed" typically occurs in the context of system landscape management, particularly when dealing with system monitoring or when managing child systems in a landscape (like in a Central Instance or when using Solution Manager).
  Cause:
  This error message indicates that the status of a child system (denoted by &1) has changed. This could happen due to various reasons, such as:
  
  The child system has been restarted or shut down.
  There are changes in the configuration of the child system.
  The child system is undergoing maintenance or updates.
  Network issues affecting the communication between the central system and the child system.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check the Status of the Child System:
  
  Log into the child system and verify its current status. Ensure that it is up and running without any issues.
  
  
  
  Review System Logs:
  
  Check the system logs (transaction SM21) for any errors or warnings that might indicate why the status changed.
  
  
  
  Network Connectivity:
  
  Ensure that there are no network issues preventing communication between the central system and the child system.
  
  
  
  System Configuration:
  
  Verify that the configuration settings for the child system in the central system are correct. This includes checking RFC connections and any relevant settings in transaction SM59.
  
  
  
  Monitoring Tools:
  
  If you are using SAP Solution Manager or any other monitoring tools, check their configuration and ensure they are correctly set up to monitor the child system.
  
  
  
  Restart Services:
  
  If the child system is down, restart the necessary services or the entire system if required.
  
  
  
  Consult Documentation:
  
  Refer to SAP Notes or documentation related to system landscape management for any specific guidance related to your version of SAP.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM59 (RFC Destinations), SM21 (System Log), and SMLG (Logon Groups) for monitoring and managing system statuses.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, consider reaching out to SAP support for further assistance.