How To Fix EIDESWD060 - Switch document &1 does not contain message data with number &2

SAP Error Message - Details

• Message type: E = Error

• Message class: EIDESWD - Message for Change of Supplier/Service

• Message number: 060

• Message text: Switch document &1 does not contain message data with number &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 EIDESWD060 - Switch document &1 does not contain message data with number &2 ?

  The SAP error message EIDESWD060 indicates that a switch document (identified by the number &1) does not contain the expected message data with the specified number &2. This error typically arises in the context of SAP's document management or workflow processes, particularly when dealing with switch documents that are used to manage and track changes in data.
  Cause:
  
  Missing Data: The switch document may not have been properly created or populated with the necessary message data.
  Incorrect Document Number: The document number provided may be incorrect or does not exist in the system.
  Data Deletion: The message data might have been deleted or not yet created due to a process error.
  Configuration Issues: There may be configuration issues in the system that prevent the proper linking of message data to the switch document.
  
  Solution:
  
  Verify Document Number: Check the document number &1 to ensure it is correct and exists in the system. You can do this by searching for the switch document in the relevant transaction (e.g., using transaction codes like SWI1 or SWI2).
  Check Message Data: Investigate whether the message data with number &2 exists. You may need to look into the relevant tables or use transaction codes to find the associated message data.
  Recreate Document: If the switch document is missing data, consider recreating it or reprocessing the relevant workflow to ensure that all necessary data is captured.
  Review Configuration: Check the configuration settings related to switch documents and message handling in your SAP system. Ensure that all necessary settings are correctly configured.
  Consult Logs: Look at system logs or application logs (using transaction SLG1) for any additional error messages or warnings that could provide more context about the issue.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that might address this specific error message or provide patches or updates.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to workflow and document management, such as SWI1 (Work Item Selection), SWI2 (Work Item Overview), and SWU3 (Automatic Workflow Customizing).
  SAP Documentation: Review SAP documentation related to switch documents and message handling for more detailed information on how these components interact.
  Support Community: Consider reaching out to the SAP Community or forums for additional insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis or technical support team for further investigation.