How To Fix EDATEX070 - IDoc &1 from category &2 was processed correctly

SAP Error Message - Details

• Message type: E = Error

• Message class: EDATEX - Messages for Data Exchange Processes

• Message number: 070

• Message text: IDoc &1 from category &2 was processed correctly

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 EDATEX070 - IDoc &1 from category &2 was processed correctly ?

  The SAP error message EDATEX070 indicates that an IDoc (Intermediate Document) was processed correctly, but it is often accompanied by additional context that may clarify the situation. The message typically means that the IDoc was successfully processed by the system, but there may be other issues or warnings that need to be addressed.
  Cause:
  
  IDoc Processing Status: The message indicates that the IDoc has been processed without errors, but it may not have resulted in the expected outcome (e.g., data not updated in the target system).
  Warnings or Information: Sometimes, the message may be part of a series of messages where other warnings or informational messages are present that could indicate potential issues.
  Configuration Issues: There may be configuration settings in the IDoc processing that need to be reviewed, such as partner profiles or message types.
  
  Solution:
  
  Check IDoc Status: Use transaction code WE02 or WE05 to check the status of the IDoc. Look for any warnings or additional messages that may provide more context.
  Review Logs: Check the application logs (transaction SLG1) for any related messages that could indicate why the IDoc was processed but did not yield the expected results.
  Verify Configuration: Ensure that the partner profiles (transaction WE20) and message types (transaction WE81) are correctly configured for the IDoc processing.
  Test IDoc Processing: If possible, test the IDoc processing with a smaller dataset or in a development environment to see if the issue can be replicated and diagnosed.
  Consult Documentation: Review SAP documentation or notes related to the specific IDoc type and processing to identify any known issues or additional configuration steps.
  
  Related Information:
  
  IDoc Types: Familiarize yourself with the specific IDoc type being processed, as different types may have unique requirements or configurations.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address known issues with the specific IDoc type or processing.
  Community Forums: Engage with SAP community forums or user groups to see if others have encountered similar issues and what solutions they found effective.
  
  If the issue persists after following these steps, it may be beneficial to involve your SAP Basis or technical team for further investigation.