How To Fix MDG_GN035 - Blueprint &1 is already being executed by &4

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_GN - Messages from the Generator

• Message number: 035

• Message text: Blueprint &1 is already being executed by &4

What causes this issue?

Blueprint &V1& for configuration object &V2& with configuration key
&V3& is currently locked by user &V4&.

System Response

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

How to fix this error?

Contact user &V4& and repeat the transaction.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MDG_GN035 - Blueprint &1 is already being executed by &4 ?

  The SAP error message MDG_GN035 indicates that a blueprint (in this case, identified as &1) is already being executed by another user or process (identified as &4). This typically occurs in the context of SAP Master Data Governance (MDG) when multiple users attempt to execute the same blueprint simultaneously.
  Cause:
  
  Concurrent Execution: The most common cause of this error is that another user is currently executing the same blueprint, which prevents other users from starting the same process until the first one is completed.
  Session Lock: The system may have a session lock on the blueprint due to a previous execution that has not yet been completed or has encountered an issue.
  Long-Running Processes: If the blueprint execution takes a long time, it may lead to this error if another user tries to execute it before the first execution finishes.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user (or process) to complete the execution of the blueprint and then try again.
  Check Active Sessions: If you have access, check the active sessions in the system to see if the blueprint is indeed being executed by another user. You can use transaction codes like SM50 or SM66 to monitor active processes.
  Contact the User: If you identify the user who is executing the blueprint, you may want to contact them to understand their timeline for completion.
  Terminate the Process: If you have the necessary authorizations and it is appropriate to do so, you can terminate the process that is holding the lock. This should be done with caution, as it may lead to data inconsistencies.
  System Logs: Check system logs for any issues related to the blueprint execution that might provide more context on why it is still running or if it has encountered an error.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like MDGIMG (for configuration) and MDG_BS_MAT (for material governance) to navigate through the MDG functionalities.
  SAP Notes: Check for any relevant SAP Notes that might address known issues or provide patches related to this error.
  Documentation: Review the SAP MDG documentation for best practices on managing blueprints and understanding execution locks.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.