How To Fix CM_SUB_MLI020 - Request cannot be approved; no authorization for &2

CM_SUB_MLI020 - Overview

• Message type: E = Error

• Message class: CM_SUB_MLI - Messages for Multilevel Inheritance

• Message number: 020

• Message text: Request cannot be approved; no authorization for &2

What causes this issue?

You cannot approve the inheritance relationship request created by the
specification &V1&. You do not have authorization for the specification
&V2&.

How to fix this error?

INCLUDE EHS_NA_IF_AUTH_IS_NEEDED OBJECT DOKU ID TX

Procedure for System Administrators

INCLUDE EHS_NA_CHECK_AUTH_OF_USER OBJECT DOKU ID TX
<ZH>Additional information</>
INCLUDE EHS_SAF_27A_INHERIT_GENERAL2 OBJECT DOKU ID TX
You require the following authorizations to be able to create
inheritance relationships:
INCLUDE EHS_SAF_27A_INHERIT_AUTH OBJECT DOKU ID TX

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

INCLUDE EHS_SAF_27A_INHERIT_AUTH2 OBJECT DOKU ID TX

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_SUB_MLI020 - Request cannot be approved; no authorization for &2 ?

  The SAP error message CM_SUB_MLI020 indicates that a user is attempting to approve a request but lacks the necessary authorization for a specific action or object. This error typically arises in the context of SAP's Change Management or Transport Management systems, where users need specific permissions to approve changes or requests.
  
  Cause:
  
  Lack of Authorization: The user does not have the required authorization object assigned to their user profile. This could be due to missing roles or authorizations in their user account.
  Role Configuration: The roles assigned to the user may not include the necessary permissions for the specific action they are trying to perform.
  Object-Specific Restrictions: The error message may refer to a specific object (indicated by &2 in the message) that the user does not have access to.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to analyze the authorization check. This will show which authorization object failed and why.
  Review