How To Fix /SCWM/CORE035 - Update of tables failed

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/CORE -

• Message number: 035

• Message text: Update of tables failed

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 /SCWM/CORE035 - Update of tables failed ?

  The SAP error message /SCWM/CORE035 Update of tables failed typically occurs in the context of the SAP Extended Warehouse Management (EWM) module. This error indicates that there was a failure in updating certain database tables during a transaction or process. Here are some common causes, potential solutions, and related information for this error:
  Causes:
  
  Database Locking Issues: The error may occur if there are locks on the database tables that prevent updates from being made.
  Data Consistency Issues: If there are inconsistencies in the data being processed, it may lead to a failure in updating the tables.
  Authorization Issues: The user executing the transaction may not have the necessary authorizations to update the tables.
  System Performance Issues: High load on the database or system can lead to timeouts or failures in processing updates.
  Custom Code or Enhancements: If there are custom developments or enhancements in the EWM system, they may interfere with standard processes and cause errors.
  
  Solutions:
  
  Check Database Locks: Use transaction codes like SM12 to check for any locks on the relevant tables. If locks are found, they may need to be released.
  Review Application Logs: Use transaction SLG1 to check application logs for more detailed error messages that can provide insights into the root cause.
  Data Consistency Check: Run consistency checks on the relevant data to ensure that there are no inconsistencies that could be causing the update to fail.
  User Authorizations: Verify that the user has the necessary authorizations to perform the action that is causing the error.
  Performance Monitoring: Monitor system performance and database performance to identify any bottlenecks that may be causing the issue.
  Debugging: If the error is related to custom code, debugging the relevant code may help identify the issue.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide patches.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM21 (System Log), ST22 (Dump Analysis), and SLG1 (Application Log) for troubleshooting.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  SAP Support: If the issue persists and cannot be resolved internally, consider reaching out to SAP Support for assistance.
  
  Conclusion:
  The /SCWM/CORE035 Update of tables failed error can stem from various issues, including database locks, data inconsistencies, and authorization problems. By systematically checking these areas and utilizing SAP tools for monitoring and debugging, you can often identify and resolve the underlying cause of the error.