How To Fix EA094 - IDoc cannot be sent in XML format

SAP Error Message - Details

• Message type: E = Error

• Message class: EA - IDoc Basis Messages

• Message number: 094

• Message text: IDoc cannot be sent in XML format

What causes this issue?

Possible causes of error:
<ZH>XML_NAMES_ERROR</> Error when creating document name.
<ZH>SOAP_MSGID_CREATE_FAILED</> System error when creating UUID.
<ZH>SOAP_MSGID_PREFIX_INVALID</> The IDoc is to be sent using SOAP and
the namespace <ZH> 'urn:sap-com:document:sap:idoc:soap:messages' </>. In
this case, the field <LS>ARCKEY</> is given a unique message ID that
contains the prefix <ZH>'urn:sap.com:msgid=' </>. The IDoc in question
already has an ID in this field of the control record, and this ID does
not contain the required prefix.
<ZH>SOAP_MSGID_INITIAL</> The field <LS>ARCKEY</> of the control record
has the value 'urn:sap.com:msgid='. In this case, the required prefix is
there, but the actual message ID is missing.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

The IDoc is saved with an error status.

How to fix this error?

Inform your system administrator.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EA094 - IDoc cannot be sent in XML format ?

  The SAP error message EA094 indicates that an IDoc (Intermediate Document) cannot be sent in XML format. This error typically arises when there is a configuration issue or a missing component in the system that prevents the IDoc from being processed correctly in XML format.
  Causes:
  
  
  Missing XML Configuration: The system may not be configured to handle XML format for IDocs. This could be due to missing settings in the IDoc configuration or the communication method.
  
  
  Incorrect IDoc Type: The IDoc type being used may not support XML format. Some IDoc types are designed to be sent in specific formats, and if the type does not support XML, this error will occur.
  
  
  Communication Channel Issues: If you are using a middleware (like SAP PI/PO or other integration tools), there may be issues with the communication channel that prevent the IDoc from being sent in XML format.
  
  
  Version Compatibility: There may be compatibility issues between the SAP version and the XML format being used.
  
  
  Missing or Incorrect Mapping: If there is a mapping issue in the middleware or in the IDoc processing logic, it may lead to this error.
  
  
  Solutions:
  
  
  Check IDoc Configuration: Ensure that the IDoc is configured correctly to be sent in XML format. This includes checking the settings in transaction WE20 (Partner Profiles) and WE21 (Port Definition).
  
  
  Verify IDoc Type: Confirm that the IDoc type you are using supports XML format. You can check this in transaction WE30 (IDoc Type Development).
  
  
  Review Communication Channels: If using middleware, check the configuration of the communication channels to ensure they are set up to handle XML format. This may involve checking the adapter settings in SAP PI/PO.
  
  
  Update SAP Notes: Check for any relevant SAP Notes that may address this issue. Sometimes, applying a specific note can resolve configuration or compatibility issues.
  
  
  Test with Different Formats: If possible, try sending the IDoc in a different format (like EDIFACT or plain text) to see if the issue is specific to XML.
  
  
  Consult Documentation: Review the SAP documentation for IDocs and XML processing to ensure that all necessary steps have been followed.
  
  
  Check for Errors in Middleware: If using middleware, check the logs for any errors that may provide more context on why the IDoc cannot be sent in XML format.
  
  
  Related Information:
  
  IDoc Basics: IDocs are used for data interchange between SAP systems and external systems. They can be sent in various formats, including XML, EDIFACT, and others.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as WE02 (Display IDoc), WE19 (Test IDoc), and WE20/WE21 for configuration.
  SAP Community: Engage with the SAP Community or forums for additional insights and solutions from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to involve your SAP Basis or technical team for further investigation.