How To Fix ECCEDI602 - Error determining supplier &1, subrc = &2

SAP Error Message - Details

• Message type: E = Error

• Message class: ECCEDI - IS-U Deregulation: IDoc Processing

• Message number: 602

• Message text: Error determining supplier &1, subrc = &2

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 ECCEDI602 - Error determining supplier &1, subrc = &2 ?

  The SAP error message ECCEDI602, which states "Error determining supplier &1, subrc = &2," typically occurs in the context of Electronic Data Interchange (EDI) processes, particularly when the system is unable to find or determine the supplier based on the provided information.
  Cause:
  
  Missing or Incorrect Supplier Data: The supplier information may not be correctly maintained in the system. This could include missing entries in the vendor master data or incorrect data formats.
  Configuration Issues: There may be issues with the configuration settings related to EDI or the specific message type being processed.
  Data Mapping Issues: If the data being sent does not match the expected format or structure, the system may fail to identify the supplier.
  Authorization Issues: The user or process attempting to access the supplier data may not have the necessary authorizations.
  Subrc Value: The subrc (sub-return code) value can provide additional context about the specific issue. Different values indicate different problems, such as no data found, authorization failure, etc.
  
  Solution:
  
  Check Vendor Master Data: Verify that the supplier/vendor master data is correctly maintained in the system. Ensure that the supplier number exists and is active.
  Review EDI Configuration: Check the EDI configuration settings to ensure that they are set up correctly for the specific message type and that the mapping is correct.
  Analyze the Subrc Value: Look up the specific subrc value in the SAP documentation or system to understand the exact nature of the error. This can provide insights into what went wrong.
  Check Authorizations: Ensure that the user or process has the necessary authorizations to access the supplier data.
  Debugging: If the issue persists, consider debugging the process to trace where the error occurs. This may involve looking at the function modules or programs involved in the EDI processing.
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide patches or updates that could resolve the issue.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like SE11 (Data Dictionary) to check the structure of the tables involved, or SE37 (Function Module) to analyze the function modules that are being called during the EDI process.
  SAP Community: Engaging with the SAP Community or forums can provide additional insights from other users who may have encountered similar issues.
  Documentation: Refer to SAP documentation for EDI processes and error handling to gain a deeper understanding of how to troubleshoot and resolve such errors.
  
  By following these steps, you should be able to identify and resolve the issue related to the ECCEDI602 error message.