How To Fix MODEL072 - Class link area '&1' / Version &2 locked

SAP Error Message - Details

• Message type: E = Error

• Message class: MODEL - Modeling

• Message number: 072

• Message text: Class link area '&1' / Version &2 locked

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 MODEL072 - Class link area '&1' / Version &2 locked ?

  The SAP error message MODEL072 indicates that a class link area (specified by &1) and a version (specified by &2) are locked. This typically occurs in the context of SAP's Model Management, particularly when dealing with planning models or data models in SAP BW (Business Warehouse) or SAP Analytics Cloud.
  Cause:
  
  
  Locking Mechanism: The error is usually caused by a locking mechanism in SAP that prevents changes to a model or version while it is being used or modified by another user or process. This can happen if:
  
  Another user is currently editing the model or version.
  A background job is running that is using the model or version.
  The model or version was not properly released or unlocked after a previous operation.
  
  
  
  Version Management: If the version of the model is set to "locked" status, it cannot be modified until it is unlocked.
  
  
  Solution:
  
  
  Check Locks: 
  
  Use transaction code SM12 to check for any active locks on the model or version. You can filter by the user or object type to find relevant locks.
  If you find a lock that is no longer needed, you can delete it (if you have the necessary authorizations).
  
  
  
  Release the Lock: 
  
  If the model or version is locked due to a user session, you may need to communicate with the user to ensure they complete their work and release the lock.
  If it is a background job, you may need to wait for it to complete or check if it can be canceled.
  
  
  
  Unlock the Version: 
  
  If the version is locked due to its status, you may need to change the status of the version to "unlocked" using the appropriate transaction or function in the SAP system.
  
  
  
  Consult Documentation: 
  
  Review the SAP documentation or help resources related to model management and version control for specific instructions on how to manage locks and versions.
  
  
  
  Contact Support: 
  
  If the issue persists and you cannot identify the cause, consider reaching out to your SAP Basis or support team for assistance.
  
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SM12: To view and manage locks.
  SE11: To check data dictionary objects related to the model.
  RSRT: To run queries and check if the model is being used in any reports.
  
  
  
  User Authorizations: Ensure that you have the necessary authorizations to unlock models and versions, as some actions may be restricted based on user roles.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to the MODEL072 error, as SAP frequently updates its knowledge base with solutions to common problems.
  
  
  By following these steps, you should be able to resolve the MODEL072 error and continue working with your SAP models and versions.