How To Fix /SAPCND/DD_CUSTOMIZE010 - Customizing for data determination blocked by other users

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/DD_CUSTOMIZE -

• Message number: 010

• Message text: Customizing for data determination blocked by other users

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 /SAPCND/DD_CUSTOMIZE010 - Customizing for data determination blocked by other users ?

  The SAP error message /SAPCND/DD_CUSTOMIZE010 indicates that the customizing for data determination is blocked by other users. This typically occurs when multiple users are trying to access or modify the same customizing settings simultaneously, leading to a lock situation.
  Cause:
  
  Concurrent Access: Another user is currently editing the same customizing settings, which causes a lock on the data.
  Long-running Transactions: A user may have started a transaction that is taking a long time to complete, thus holding the lock for an extended period.
  System Issues: Sometimes, system issues or bugs can lead to locks not being released properly.
  
  Solution:
  
  Wait and Retry: If the lock is due to another user, the simplest solution is to wait for that user to finish their work and then try again.
  Check Lock Entries: You can check the lock entries using transaction code SM12. This will show you which users are currently holding locks on the customizing tables.
  
  If you have the necessary authorizations, you can delete the lock entries, but this should be done with caution as it may disrupt the other user's work.
  
  
  Communicate with Users: If you identify the user holding the lock, you can communicate with them to understand their needs and coordinate the changes.
  Review System Performance: If locks are a frequent issue, it may be worth reviewing system performance and user activity to identify any patterns or long-running transactions that could be optimized.
  Check for Background Jobs: Sometimes, background jobs may hold locks. You can check for any running jobs using transaction SM37.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage lock entries.
  SM37: To check background jobs.
  SE11: To view table definitions and understand the structure of the customizing tables involved.
  
  
  User Roles and Authorizations: Ensure that users have the appropriate roles and authorizations to access and modify the customizing settings.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance related to this error message.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or consult SAP support for further assistance.