How To Fix CRM_ICM_CMG072 - Case &1 cannot be added as a subcase due to missing authorization

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_ICM_CMG - Messages for ICM Cases & Leads

• Message number: 072

• Message text: Case &1 cannot be added as a subcase due to missing authorization

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 CRM_ICM_CMG072 - Case &1 cannot be added as a subcase due to missing authorization ?

  The SAP error message CRM_ICM_CMG072 indicates that a user is attempting to add a case as a subcase to another case, but they lack the necessary authorization to perform this action. This is a common issue in SAP Customer Relationship Management (CRM) systems, particularly when dealing with case management.
  
  Cause:
  The error is typically caused by one or more of the following reasons:
  
  Missing Authorizations: The user does not have the required authorization objects assigned to their user profile to add subcases.
  Role Configuration: The roles assigned to the user may not include the necessary permissions for case management activities.
  Organizational Restrictions: There may be organizational-level restrictions that prevent certain users from performing specific actions on cases.
  
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to check the authorization check that failed. This will provide insight into which specific authorization object is missing.
  Review the