How To Fix /SCWM/EXCEPTION070 - Unable to write history for executed exception

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/EXCEPTION -

• Message number: 070

• Message text: Unable to write history for executed exception

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/EXCEPTION070 - Unable to write history for executed exception ?

  The SAP error message /SCWM/EXCEPTION070 Unable to write history for executed exception typically occurs in the context of SAP Extended Warehouse Management (EWM). This error indicates that the system is unable to log or write the history of a specific exception that has been executed. Here are some potential causes, solutions, and related information for this error:
  Causes:
  
  Database Issues: There may be issues with the database connection or the database itself, preventing the system from writing to the history table.
  Authorization Problems: The user executing the transaction may not have the necessary authorizations to write to the history log.
  Configuration Errors: There may be configuration issues in the EWM system that prevent the logging of exceptions.
  System Performance: If the system is under heavy load, it may not be able to process the write operation in a timely manner.
  Custom Code: If there are custom enhancements or modifications in the EWM system, they may interfere with the standard exception handling process.
  
  Solutions:
  
  Check Database Connection: Ensure that the database is up and running and that there are no connectivity issues. You can check the database logs for any errors.
  Review Authorizations: Verify that the user has the necessary authorizations to write to the history log. You may need to consult with your security team to ensure proper roles are assigned.
  Check Configuration: Review the EWM configuration settings related to exception handling and logging. Ensure that all necessary settings are correctly configured.
  Monitor System Performance: Check the system performance metrics to see if there are any bottlenecks. If the system is under heavy load, consider optimizing performance or scheduling batch jobs during off-peak hours.
  Debug Custom Code: If there are custom enhancements, debug the code to identify any issues that may be causing the error. You may need to consult with the development team for assistance.
  Check Logs: Review the application logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  Related Information:
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. SAP Notes often contain fixes or workarounds for known issues.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SCWM/EXC for exception handling and /SCWM/LOG for logging purposes.
  Documentation: Review the official SAP documentation for EWM to understand the exception handling framework and logging mechanisms.
  
  If the issue persists after trying the above solutions, it may be necessary to contact SAP support for further assistance.