How To Fix /SMB/CENTRALDATA026 - Saving is currently not possible, try again later (locked by &1)

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/CENTRALDATA -

• Message number: 026

• Message text: Saving is currently not possible, try again later (locked by &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 /SMB/CENTRALDATA026 - Saving is currently not possible, try again later (locked by &1) ?

  The SAP error message /SMB/CENTRALDATA026 Saving is currently not possible, try again later (locked by &1) typically indicates that a certain data object or resource is currently locked by another user or process. This can happen in various scenarios, such as when multiple users are trying to access or modify the same data simultaneously.
  Cause:
  
  Data Locking: The most common cause is that the data you are trying to save is locked by another user or transaction. This can occur if another user is currently editing the same data or if a previous transaction did not release the lock properly.
  Long-running Transactions: If a transaction takes too long to complete, it may hold locks longer than expected, preventing others from accessing the data.
  System Issues: Occasionally, system issues or bugs can lead to locks not being released properly.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for a few moments and then try saving again. If the lock is temporary, it may be released shortly.
  Identify the Lock: Use transaction code SM12 to check for locks in the system. You can see which user or process is holding the lock. If you have the necessary permissions, you can also release the lock if it is safe to do so.
  Check for Long-running Transactions: Use transaction code SM66 to monitor active processes in the system. Look for any long-running transactions that might be holding locks.
  Contact the User: If you identify the user or process that is holding the lock, you may want to contact them to see if they can release the lock or if they are done with their transaction.
  System Administrator: If you are unable to resolve the issue, contact your SAP system administrator for assistance. They may have additional tools or permissions to investigate and resolve the locking issue.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  SM66: To monitor active processes.
  SM21: To check system logs for any related errors or warnings.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. Sometimes, specific versions of SAP may have bugs that are documented in SAP Notes.
  Documentation: Review SAP documentation for more information on data locking and transaction management.
  
  By following these steps, you should be able to identify the cause of the lock and take appropriate action to resolve the issue.