How To Fix ED586 - A new version for message &2 was created under the number &1

SAP Error Message - Details

• Message type: E = Error

• Message class: ED - ABAP/4 Editor messages

• Message number: 586

• Message text: A new version for message &2 was created under the number &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 ED586 - A new version for message &2 was created under the number &1 ?

  The SAP error message ED586 indicates that a new version of a message has been created, and it provides information about the message number and the version number. This typically occurs in the context of message management in SAP, particularly when dealing with message classes and message texts.
  Cause:
  The error message ED586 is triggered when:
  
  A new version of a message is created in the system, which may happen during the transport of message texts or when changes are made to existing messages.
  The system detects that there is a version conflict, meaning that the message you are trying to access or use has been updated or modified, and the system is informing you of the new version.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  Check Message Versions: Use transaction SE91 (Message Maintenance) to check the message class and the specific message number. Look for the new version of the message and review the changes made.
  Update References: If your application or program is referencing the old version of the message, update it to use the new version.
  Transport Requests: If this issue arose after a transport, ensure that all relevant transport requests have been properly imported into the target system.
  Consistency Check: Run a consistency check to ensure that all message texts are up to date and that there are no inconsistencies in the message classes.
  Documentation: Review any documentation or change logs related to the message class to understand what changes were made and why.
  
  Related Information:
  
  Message Classes: In SAP, messages are organized into message classes, which are collections of related messages. Each message has a unique number within its class.
  Message Texts: Messages can be translated into different languages, and each version may have different text based on the language settings.
  Transport Management: Changes to message texts are often transported between systems (e.g., from development to production), and versioning helps manage these changes.
  
  If the issue persists after following these steps, consider reaching out to your SAP Basis or development team for further assistance, as they may need to investigate the transport logs or system settings.