How To Fix MDG_SF105 - Missing authorization

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_SF - MDG: Sample Model SFlight

• Message number: 105

• Message text: 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 MDG_SF105 - Missing authorization ?

  The SAP error message MDG_SF105: Missing authorization typically occurs in the context of SAP Master Data Governance (MDG) when a user attempts to perform an action for which they do not have the necessary authorizations. This can happen in various scenarios, such as when trying to create, change, or display master data.
  Cause:
  The primary cause of this error is that the user lacks the required authorization objects or roles that are necessary to perform the specific action in the MDG application. This can be due to:
  
  Missing Roles: The user has not been assigned the appropriate roles that include the necessary authorizations.
  Authorization Objects: The specific authorization objects required for the action are not included in the user's roles.
  Profile Issues: The user profile may not be correctly configured to allow access to the MDG functionalities.
  Custom Authorizations: If the organization has customized the authorization checks, the user may not meet the custom criteria.
  
  Solution:
  To resolve the MDG_SF105 Missing authorization error, you can follow these steps:
  
  
  Check User Roles:
  
  Verify the roles assigned to the user in transaction SU01 (User Maintenance).
  Ensure that the user has the necessary roles that provide access to the MDG functionalities.
  
  
  
  Review Authorization Objects:
  
  Use transaction SU53 immediately after the error occurs to check which authorization objects are missing.
  This transaction will show the last authorization check and can help identify what is lacking.
  
  
  
  Adjust Authorizations:
  
  If you identify missing authorization objects, work with your SAP security team to adjust the roles or create new ones that include the necessary authorizations.
  Ensure that the roles are properly assigned to the user.
  
  
  
  Testing:
  
  After making changes to the roles or authorizations, have the user log out and log back in to ensure that the changes take effect.
  Test the action again to confirm that the error has been resolved.
  
  
  
  Documentation:
  
  Document any changes made to user roles and authorizations for future reference and compliance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU01: User Maintenance
  SU53: Display Authorization Check
  PFCG: Role Maintenance (to manage roles and authorizations)
  
  
  
  Authorization Concepts:
  
  Understand the basic concepts of SAP authorization, including roles, profiles, and authorization objects.
  Familiarize yourself with the specific authorization objects related to MDG, such as those starting with MDG_*.
  
  
  
  SAP Notes:
  
  Check for any relevant SAP Notes that may address specific issues related to authorization in MDG.
  
  
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or security team for further investigation.