How To Fix EDATEX458 - You have not specified a message ID for the confirmation message

EDATEX458 - Overview

• Message type: E = Error

• Message class: EDATEX - Messages for Data Exchange Processes

• Message number: 458

• Message text: You have not specified a message ID for the confirmation message

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 EDATEX458 - You have not specified a message ID for the confirmation message ?

  The SAP error message EDATEX458, which states "You have not specified a message ID for the confirmation message," typically occurs in the context of Electronic Data Interchange (EDI) or IDoc processing. This error indicates that the system expects a message ID to be specified for a confirmation message, but it has not been provided.
  
  Cause:
  
  Missing Configuration: The message ID for the confirmation message may not be configured in the relevant settings for the EDI or IDoc processing.
  Incorrect Mapping: There may be an issue with the mapping of the IDoc types or message types, leading to the absence of a required message ID.
  Incomplete Data: The data being processed may be incomplete or incorrectly formatted, leading to the system not being able to identify the necessary message ID.
  
  
  Solution:
  
  
  Check Configuration:
  
  Go to the transaction code WE20 (Partner Profiles) and ensure that the partner profile for the relevant partner is correctly configured.
  Verify that the message type