How To Fix CPCL_VERS079 - Version &1 is in process

SAP Error Message - Details

• Message type: E = Error

• Message class: CPCL_VERS - Task List Version

• Message number: 079

• Message text: Version &1 is in process

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 CPCL_VERS079 - Version &1 is in process ?

  The SAP error message CPCL_VERS079, which states "Version &1 is in process," typically occurs in the context of version management in SAP, particularly when dealing with configuration or planning versions in modules like SAP Controlling (CO) or SAP Project System (PS). This error indicates that the specified version is currently being processed or is locked by another user or process, preventing further actions on it.
  Cause:
  
  Version Locking: The version you are trying to access or modify is currently locked because another user is working on it or a background job is processing it.
  Incomplete Processes: There may be ongoing processes that have not yet completed, such as data uploads, calculations, or other transactions that involve the version.
  User Sessions: Sometimes, a user may have an open session that is holding a lock on the version.
  
  Solution:
  
  Check for Active Sessions: Verify if another user is currently working on the version. You can use transaction codes like SM12 (to check for locks) or SM66 (to view active processes) to identify if the version is locked by another user.
  Wait for Completion: If a background job is processing the version, you may need to wait until it completes. You can check the status of background jobs using transaction code SM37.
  Release Locks: If you find that a session is holding a lock unnecessarily, you may need to contact the user or administrator to release the lock. In some cases, you can manually delete the lock using transaction SM12, but this should be done with caution.
  Check Configuration: Ensure that the version is not set to a status that prevents changes (e.g., "locked" or "completed"). You may need to change the status if you have the necessary authorizations.
  Consult Documentation: Review SAP documentation or notes related to version management for any specific instructions or known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SM12: To view and manage locks.
  SM37: To monitor background jobs.
  SM66: To see all active processes in the system.
  
  
  SAP Notes: Check SAP Notes for any updates or patches related to version management issues.
  User Authorizations: Ensure that you have the necessary authorizations to access and modify the version in question.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.