How To Fix CM_EHENV_SCEN014 - Cannot create new revision; an overlapping revision "&2" is locked in &1

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_EHENV_SCEN - Compliance Scenario Messages

• Message number: 014

• Message text: Cannot create new revision; an overlapping revision "&2" is locked in &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 CM_EHENV_SCEN014 - Cannot create new revision; an overlapping revision "&2" is locked in &1 ?

  The SAP error message CM_EHENV_SCEN014 indicates that there is an attempt to create a new revision of a scenario in the Environment Management (EHENV) component, but it cannot proceed because there is an overlapping revision that is currently locked. The message typically includes placeholders like "&1" for the environment and "&2" for the revision number that is locked.
  Cause:
  
  Locked Revision: The primary cause of this error is that there is an existing revision of the scenario that overlaps with the new revision you are trying to create, and this existing revision is locked. This could happen if:
  
  Another user is currently working on that revision.
  A process or transaction is holding a lock on the revision.
  The revision is in a state that does not allow further modifications.
  
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check for Locks:
  
  Use transaction codes like SM12 to check for locks in the system. Look for any entries related to the locked revision and see if you can identify the user or process that is holding the lock.
  
  
  
  Release the Lock:
  
  If you find that a user or process is holding the lock unnecessarily, you can ask them to release it. If they are not available, and if you have the necessary authorizations, you can manually delete the lock entry in SM12.
  
  
  
  Wait for the Lock to be Released:
  
  If the lock is due to a legitimate process (like a background job), you may need to wait until that process completes.
  
  
  
  Check Revision Overlap:
  
  Ensure that the new revision you are trying to create does not overlap with the existing locked revision. If it does, you may need to adjust your revisioning strategy.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation or consult with your SAP Basis or functional team for any specific configurations or settings that might be causing the locking behavior.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to view and manage locks), SE11 (to check table definitions), and SE80 (to explore objects).
  User Authorizations: Ensure that you have the necessary authorizations to manage locks and revisions in the system.
  SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address the issue.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.