How To Fix MDG_FICA_CHECK035 - No authorization for deleting BP data in authorization group &1

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_FICA_CHECK - Contract Account Check Messages

• Message number: 035

• Message text: No authorization for deleting BP data in authorization group &1

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_FICA_CHECK035 - No authorization for deleting BP data in authorization group &1 ?

  The SAP error message MDG_FICA_CHECK035 indicates that a user does not have the necessary authorization to delete Business Partner (BP) data in a specific authorization group. This error typically arises in the context of SAP Master Data Governance (MDG) for Financial Accounting (FICA) when a user attempts to perform an action that requires higher privileges than they possess.
  Cause:
  The primary cause of this error is a lack of authorization for the user in the specified authorization group. Authorization groups are used in SAP to control access to certain data and functions based on user roles. If a user tries to delete BP data that is protected by an authorization group they are not authorized for, this error will be triggered.
  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 is missing.
  
  
  
  Review Authorization Roles:
  
  Review the roles assigned to the user in transaction PFCG. Ensure that the roles include the necessary authorizations for the relevant authorization group.
  
  
  
  Modify Authorization Roles:
  
  If the user does not have the required authorization, you may need to modify the existing roles or create a new role that includes the necessary authorizations for deleting BP data in the specified authorization group.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to change roles or authorizations, consult with your SAP security team or administrator. They can help you understand the authorization requirements and make the necessary adjustments.
  
  
  
  Testing:
  
  After making changes to the user’s authorizations, have the user attempt the action again to ensure that the issue is resolved.
  
  
  
  Related Information:
  
  Authorization Objects: The specific authorization objects related to Business Partner data management may include F_BKPF_BUP (for Business Partner) and others depending on the specific actions being performed.
  Documentation: Refer to SAP documentation for detailed information on authorization management and best practices for setting up roles and authorizations.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on authorization errors related to MDG and FICA.
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the MDG_FICA_CHECK035 error.