How To Fix EIDESWD085 - Cannot find temporary switch document and message data for &1

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 085

• Message text: Cannot find temporary switch document and message data for &1

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 EIDESWD085 - Cannot find temporary switch document and message data for &1 ?

  The SAP error message EIDESWD085, which states "Cannot find temporary switch document and message data for &1," typically occurs in the context of the SAP EDI (Electronic Data Interchange) or IDoc (Intermediate Document) processing. This error indicates that the system is unable to locate the temporary switch document or the associated message data for the specified identifier (&1).
  Causes:
  
  Missing Temporary Document: The temporary switch document that is supposed to be created during the processing of an IDoc or EDI message may not have been generated or may have been deleted.
  Database Issues: There could be issues with the database where the temporary documents are stored, such as corruption or connectivity problems.
  Configuration Issues: Incorrect configuration settings in the EDI/IDoc processing might lead to the inability to find the required documents.
  Timing Issues: If the processing of the IDoc is not synchronized properly, it may lead to situations where the temporary document is not available when needed.
  
  Solutions:
  
  Check IDoc Status: Use transaction WE02 or WE05 to check the status of the IDoc. Look for any errors or issues that might indicate why the temporary document is missing.
  Reprocess IDoc: If the IDoc is in an error state, you may need to reprocess it. This can be done using transaction BD87 or by using the appropriate function module.
  Review Configuration: Ensure that the EDI/IDoc configuration is set up correctly. Check the partner profiles and message types to ensure they are configured to create temporary documents as expected.
  Database Check: If you suspect database issues, work with your database administrator to check for any inconsistencies or problems that might be affecting the temporary document storage.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error. There may be patches or updates that resolve known issues.
  Debugging: If the issue persists, consider debugging the process to identify where the temporary document is expected to be created and why it is not being found.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as WE02 (Display IDoc), WE05 (IDoc List), and BD87 (Reprocess IDocs).
  SAP Documentation: Review SAP documentation related to EDI and IDoc processing for best practices and troubleshooting steps.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  If the problem continues after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.