How To Fix WGDS_CONFIRMATION085 - Message with id &1 and version &2 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: WGDS_CONFIRMATION - Confirmation messages

• Message number: 085

• Message text: Message with id &1 and version &2 does not exist

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 WGDS_CONFIRMATION085 - Message with id &1 and version &2 does not exist ?

  The SAP error message:
  WGDS_CONFIRMATION085: Message with id &1 and version &2 does not exist
  
  Cause:
  This error occurs when the system tries to find a specific message (usually a delivery or confirmation message) identified by a message ID and version, but it cannot find it in the system. This typically happens in the context of Warehouse Management (WM) or Extended Warehouse Management (EWM) when processing delivery confirmations or warehouse task confirmations.
  Common reasons include:
  
  The message type or version specified in the configuration does not exist or is not maintained.
  The message type/version is incorrectly configured in the system.
  The relevant message type/version has been deleted or not transported to the current system.
  Custom developments or enhancements are referring to a non-existent message ID/version.
  
  
  Solution:
  
  
  Check Message Type and Version Configuration:
  
  Go to transaction WE81 (Message Types) or WE82 (Message Type Versions) to verify if the message ID and version exist.
  If missing, create or maintain the required message type and version.
  
  
  
  Verify Warehouse Process Type or Confirmation Profile:
  
  In WM/EWM, check the configuration for the confirmation profile or warehouse process type that triggers the message.
  Ensure that the message ID and version assigned there are valid and exist in the system.
  
  
  
  Check ALE/IDoc Configuration:
  
  If the message relates to IDocs, verify the message type and version in the IDoc type configuration (transaction WE30, WE60).
  Make sure the message type/version is consistent with the IDoc processing.
  
  
  
  Transport and System Consistency:
  
  If the message type/version was recently created or changed, ensure that the transport was imported correctly into the system where the error occurs.
  
  
  
  Debugging:
  
  If the error persists, debug the program or function module that triggers the message to identify where the message ID and version are fetched and why they are missing.
  
  
  
  
  Related Information:
  
  
  Transactions:
  
  WE81 - Maintain Message Types
  WE82 - Maintain Message Type Versions
  WE30 - IDoc Type Development
  WE60 - IDoc Documentation
  SPRO - For configuration of warehouse confirmation profiles and process types
  
  
  
  Notes and Documentation:
  
  Check SAP Notes related to WM/EWM message handling.
  Review SAP Help Portal documentation on warehouse confirmation and message types.
  
  
  
  Common Context:
  
  This error is common during outbound delivery confirmation, inbound delivery confirmation, or warehouse task confirmation processes.
  It may also appear during EDI or ALE processing if the message type/version is not properly maintained.
  
  
  
  
  If you provide the exact message ID and version values (&1 and &2), I can help you check their standard existence or guide you on how to create them.