How To Fix /MOC/CONFIG112 - It is not allowed to use CR type of category &1 as subordinate CR types

/MOC/CONFIG112 - Overview

• Message type: E = Error

• Message class: /MOC/CONFIG -

• Message number: 112

• Message text: It is not allowed to use CR type of category &1 as subordinate CR types

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/CONFIG112 - It is not allowed to use CR type of category &1 as subordinate CR types ?

  The SAP error message /MOC/CONFIG112 indicates that there is a configuration issue related to Change Request (CR) types in the SAP system. Specifically, it states that a certain CR type (denoted by &1) is not allowed to be used as a subordinate CR type under another CR type. This typically occurs in the context of managing change requests in SAP Solution Manager or similar environments where change management is configured.
  
  Cause:
  
  Configuration Error: The CR type you are trying to use as a subordinate type is not configured to be used in that manner. This could be due to restrictions set in the system configuration.
  Hierarchy Restrictions: Certain CR types may have restrictions on their usage in a hierarchy, meaning they can only be used at a certain level and not as subordinates to other types.
  Incorrect Assignment: The CR type may have been incorrectly assigned in the configuration settings, leading to this error