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

SAP Error Message - Details

• 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 for Change Request Management.
  Check the status of the change request type in question and activate it if it is inactive.
  Path: SAP Solution Manager > Change Request Management > Change Request Types > Define Change Request Types.
  
  
  
  Check Configuration:
  
  Ensure that all necessary configurations for the change request type are correctly set up.
  Verify that the change request type is assigned to the correct project and that all dependencies are met.
  
  
  
  Review Transport Layer:
  
  If the change request type is part of a transport layer, ensure that the transport layer is active and that all necessary transports have been imported into the system.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to Change Request Management for any specific instructions or known issues regarding the change request type.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide additional insights or patches if this is a known issue.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like SPRO for configuration, SE09 or SE10 for transport management, and SOLMAN_WORKCENTER for accessing the Solution Manager work center.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Change Request Management Documentation: Familiarize yourself with the Change Request Management process in SAP Solution Manager, as it provides context for how change request types are utilized.
  
  By following these steps, you should be able to resolve the error and ensure that the child change request type can be used as intended.