How To Fix EDATEX857 - Basic process &1 does not support aggregated IDocs

SAP Error Message - Details

• Message type: E = Error

• Message class: EDATEX - Messages for Data Exchange Processes

• Message number: 857

• Message text: Basic process &1 does not support aggregated IDocs

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 EDATEX857 - Basic process &1 does not support aggregated IDocs ?

  The SAP error message EDATEX857 indicates that the basic process you are trying to use does not support aggregated IDocs. This typically occurs when you are attempting to send or process IDocs that are aggregated (i.e., multiple IDocs combined into one) in a context where the system does not support this functionality.
  Cause:
  
  Unsupported Basic Process: The basic process you are using is not designed to handle aggregated IDocs. This can happen if the configuration or the IDoc type you are using does not support aggregation.
  Incorrect Configuration: The configuration settings for the IDoc processing may not be set up to handle aggregated IDocs.
  IDoc Type Limitations: Certain IDoc types or message types may not support aggregation due to their inherent design.
  
  Solution:
  
  Check Basic Process: Verify the basic process you are using and ensure that it is capable of handling aggregated IDocs. You may need to switch to a different process that supports aggregation.
  Review IDoc Configuration: Check the configuration settings in transaction WE20 (Partner Profiles) and WE21 (Port Definition) to ensure that they are set up correctly for the IDoc type you are using.
  Use Non-Aggregated IDocs: If aggregation is not necessary, consider sending non-aggregated IDocs instead. This may involve adjusting the way data is collected and sent to the SAP system.
  Consult Documentation: Review the SAP documentation for the specific IDoc type and basic process you are using to understand their capabilities and limitations regarding aggregation.
  Contact SAP Support: If you are unable to resolve the issue, consider reaching out to SAP support for assistance, especially if this is a critical business process.
  
  Related Information:
  
  IDoc Types: Familiarize yourself with the IDoc types and their capabilities. Some IDoc types are specifically designed for certain processes and may not support aggregation.
  SAP Notes: Check for any relevant SAP Notes that may address this issue or provide additional guidance on handling aggregated IDocs.
  Transaction Codes: Use transaction codes like WE02 (Display IDoc) and WE19 (Test IDoc) to analyze the IDocs being processed and troubleshoot any issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.