How To Fix FKK_MDG_CHECK020 - No authorization for creation of locks for process &1.

SAP Error Message - Details

• Message type: E = Error

• Message class: FKK_MDG_CHECK - Contract Account Check Messages

• Message number: 020

• Message text: No authorization for creation of locks for process &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 FKK_MDG_CHECK020 - No authorization for creation of locks for process &1. ?

  The SAP error message FKK_MDG_CHECK020 indicates that a user does not have the necessary authorization to create locks for a specific process in the SAP system. This error typically occurs in the context of the Contract Accounts Receivable and Payable (FI-CA) module, particularly when dealing with Master Data Governance (MDG) processes.
  Cause:
  The primary cause of this error is a lack of appropriate authorization in the user's role or profile. The system checks for specific authorizations related to locking mechanisms that are used to prevent concurrent processing of data in the system. If the user does not have the required authorization object, the system will throw this error.
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to see which authorization check failed. This will provide insight into what specific authorization is missing.
  
  
  
  Review Authorization Roles:
  
  Check the roles assigned to the user in transaction PFCG. Ensure that the roles include the necessary authorization objects related to the locking mechanism for the specific process indicated in the error message.
  
  
  
  Add Required Authorizations:
  
  If the required authorization is missing, you may need to add it to the user's role. The relevant authorization object for locking in FI-CA is typically F_SKA1_AEN or similar, depending on the specific process.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to modify roles or authorizations, contact your SAP security team or administrator. They can help you identify and assign the correct authorizations.
  
  
  
  Testing:
  
  After making changes to the user’s authorizations, have the user log out and log back in to ensure that the new authorizations take effect. Then, attempt to perform the action that previously resulted in the error.
  
  
  
  Related Information:
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects in SAP that pertain to the FI-CA module and locking mechanisms.
  SAP Notes: Check for any SAP Notes related to this error message or the specific process you are working with. SAP Notes can provide additional context or solutions for known issues.
  Documentation: Review SAP documentation for Master Data Governance and FI-CA to understand the processes involved and the necessary authorizations.
  
  By following these steps, you should be able to resolve the FKK_MDG_CHECK020 error and ensure that the user has the necessary permissions to create locks for the specified process.