How To Fix /SMB/MD_AS_CUST035 - Error during ECATT processing: No specific error messages is returned

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/MD_AS_CUST -

• Message number: 035

• Message text: Error during ECATT processing: No specific error messages is returned

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/MD_AS_CUST035 - Error during ECATT processing: No specific error messages is returned ?

  The SAP error message /SMB/MD_AS_CUST035 indicates that there was an issue during the execution of an eCATT (extended Computer Aided Test Tool) script, but no specific error messages were returned to provide further details about the failure. This can make troubleshooting a bit challenging, but here are some common causes, potential solutions, and related information that may help you resolve the issue:
  Possible Causes:
  
  Script Errors: There may be logical errors or incorrect configurations in the eCATT script itself.
  Authorization Issues: The user executing the eCATT may not have the necessary authorizations to perform certain actions.
  Data Issues: The data being processed by the eCATT may be incorrect or incomplete, leading to failures.
  System Configuration: There may be issues with the system configuration or settings that affect the execution of the eCATT.
  Transaction Errors: The transactions being called within the eCATT may have their own issues, such as missing data or incorrect parameters.
  
  Solutions:
  
  Check the eCATT Script: Review the script for any logical errors, incorrect parameters, or missing data. Ensure that all required fields are populated correctly.
  Review Authorizations: Verify that the user executing the eCATT has the necessary authorizations for all actions being performed in the script.
  Debugging: Use the debugging features of eCATT to step through the script and identify where it fails. This can provide insights into what might be going wrong.
  Check Logs: Look at the eCATT logs and transaction logs for any additional information that might indicate what went wrong. You can access logs through transaction SLG1 or eCATT transaction codes.
  Test with Sample Data: If possible, run the eCATT with a smaller set of sample data to see if the issue persists. This can help isolate the problem.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide guidance on similar issues.
  
  Related Information:
  
  eCATT Documentation: Familiarize yourself with the eCATT documentation available in the SAP Help Portal, which provides detailed information on how to create and troubleshoot eCATT scripts.
  SAP Community: Engage with the SAP Community forums where other users may have encountered similar issues and can provide insights or solutions.
  SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.