How To Fix ED035 - Source and destination message class

SAP Error Message - Details

• Message type: E = Error

• Message class: ED - ABAP/4 Editor messages

• Message number: 035

• Message text: Source and destination message class

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 ED035 - Source and destination message class ?

  The SAP error message ED035 typically relates to issues with the source and destination message classes in the context of Electronic Data Interchange (EDI) or IDoc processing. This error can occur when there is a mismatch or misconfiguration in the message types or when the system is unable to find the appropriate mapping for the source and destination message classes.
  Cause:
  
  Mismatch in Message Classes: The source and destination message classes may not match or may not be properly defined in the system.
  Configuration Issues: There may be issues in the configuration of the EDI/IDoc settings, such as incorrect partner profiles or message type definitions.
  Missing Mapping: The system may not have the necessary mapping defined for the source and destination message types.
  Transport Issues: If the message is being sent between different systems, there may be transport issues or configuration problems in the receiving system.
  
  Solution:
  
  
  Check Message Class Configuration:
  
  Verify that the source and destination message classes are correctly defined in the system.
  Ensure that the message types are correctly mapped in the partner profiles.
  
  
  
  Review Partner Profiles:
  
  Go to transaction code WE20 and check the partner profiles for the relevant partner. Ensure that the message types and processing codes are correctly set up.
  
  
  
  Check IDoc Types:
  
  Use transaction WE30 to check the IDoc types and ensure that they are correctly defined and activated.
  
  
  
  Mapping Configuration:
  
  If you are using a mapping tool (like SAP PI/PO), ensure that the mapping for the source and destination message types is correctly configured.
  
  
  
  Error Logs:
  
  Check the error logs using transaction WE02 or WE05 to get more details about the error and identify the specific message types involved.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test to ensure that the issue is resolved.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  WE20: Partner Profiles
  WE30: IDoc Types
  WE02/WE05: IDoc Monitoring
  
  
  Documentation: Refer to SAP Help documentation for EDI/IDoc processing for detailed configuration steps and best practices.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to error ED035.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis or EDI team for further investigation.