How To Fix /MOC/CONFIG195 - Child change request type &1 cannot be used because it is inactive

/MOC/CONFIG195 - Overview

• Message type: E = Error

• Message class: /MOC/CONFIG -

• Message number: 195

• Message text: Child change request type &1 cannot be used because it is inactive

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /MOC/CONFIG195 - Child change request type &1 cannot be used because it is inactive ?

  The SAP error message /MOC/CONFIG195 indicates that a child change request type is inactive, which means that the system cannot process it in its current state. This error typically arises in the context of SAP Change Request Management (ChaRM) or similar configuration management processes.
  
  Cause:
  
  Inactive Change Request Type: The specific change request type referenced by &1 is not active in the system. This could be due to configuration settings where the change request type has been deactivated or not properly set up.
  
  Configuration Issues: There may be issues in the configuration of the change management process, such as missing or incorrect settings in the customizing tables.
  Transport Layer Issues: If the change request type is part of a transport layer that is not active or has not been properly imported, it may lead to this error.
  
  
  Solution:
  
  
  Activate the Change Request Type:
  
  Go to the SAP Customizing Implementation Guide (IMG) and navigate to the relevant section