How To Fix USMD1159 - Authorization is inconsistent

USMD1159 - Overview

• Message type: E = Error

• Message class: USMD1 - Datenmodel

• Message number: 159

• Message text: Authorization is inconsistent

What causes this issue?

Authorizations for the authorization object USMD_MDAT can only be
assigned as follows:
<ZH>Data model</>: You can specify * for all authorizations, or a single
value or interval. You can also determine the activity. You cannot
assign additional values for entities, attributes, or other field names.
<ZH>Entity</>: If the data model is restricted to a single value, you
can also define * for all authorizations, or a single value or interval.
If the entity is likewise restricted to a single value, you can define
additional restrictions for the attributes or other field names.

System Response

The authorizations cannot be saved.

How to fix this error?

Assign the authorizations based on the described rules.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message USMD1159 - Authorization is inconsistent ?

  The SAP error message USMD1159, which states "Authorization is inconsistent," typically occurs in the context of SAP Master Data Governance (MDG) when there are issues related to user authorizations. This error indicates that the user's authorization to perform a certain action is not consistent with the required authorizations for that action.
  
  Cause:
  
  Missing Authorizations: The user may not have the necessary authorizations assigned to perform the action they are trying to execute.
  Inconsistent Role Assignments: The roles assigned to the user may not be properly configured or may conflict with each other.
  Changes in Authorization Objects: If there have been recent changes to authorization objects or roles, it may lead to inconsistencies.
  Transport Issues: If roles or authorizations were transported from one system to another, they may not have been properly assigned or configured in the target system.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to analyze the authorization check. This will