How To Fix TB836 - Comparison run &1 is currently being edited by &2 (only display posisble)

SAP Error Message - Details

• Message type: E = Error

• Message class: TB - SM31 table maintenance messages

• Message number: 836

• Message text: Comparison run &1 is currently being edited by &2 (only display posisble)

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 TB836 - Comparison run &1 is currently being edited by &2 (only display posisble) ?

  The SAP error message TB836 indicates that a comparison run (typically related to the SAP Controlling module) is currently being edited by another user. This means that the system has locked the comparison run for editing, and you can only view it but not make any changes.
  Cause:
  
  Concurrent Access: Another user is currently editing the comparison run, which prevents you from making changes.
  Session Lock: The system has a session lock in place for the comparison run to ensure data integrity and prevent conflicts during editing.
  
  Solution:
  
  Wait for Release: The simplest solution is to wait until the other user has finished editing the comparison run. You can check with your colleagues to see if they are working on it.
  Check User Lock: If you have access, you can check the user sessions in transaction code SM04 or AL08 to see who is currently editing the comparison run.
  Contact the User: If you know who is editing the run, you can reach out to them to see if they can finish their work or if they can release the lock.
  Use a Different Comparison Run: If possible, you can work on a different comparison run that is not currently being edited.
  System Administrator: If the lock persists for an extended period and you cannot reach the user, you may need to contact your SAP system administrator to investigate further. They can release the lock if necessary.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM04 (User Overview) and AL08 (Global User Overview) to monitor user sessions.
  Documentation: Refer to SAP documentation or help files related to the specific module you are working with for more context on comparison runs and their management.
  User Roles: Ensure that you have the appropriate permissions to access and edit comparison runs in SAP.
  
  By following these steps, you should be able to resolve the issue or find a workaround until the comparison run is available for editing.