INVALID_XML SAP ABAP Runtime Error invalid xml

INVALID_XML is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: S - ST Runtime Error

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.

INVALID_XML ABAP Runtime Error

Please see st error for more details about the possible cause of this runtime error and how it could be avoided.

Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.

The following operation

<runtime parameter>

creates a badly formed document. Error:

<runtime parameter> Invalid XML document for serialization. Please see st error for more details about the possible cause of this runtime error and how it could be avoided.

During serialization of ABAP data to XML with a simple transformation program, a badly formed XML document is created. The serialization process has to be terminated.

The reasons for this might be as follows:

1. Another simple transformation template or program is called in a simple transformation program. In the template or program that is called, statements are executed that result in a badly formed XML document. It might not be possible to recognize this situation until the calling simple transformation program is continued.

2. An ABAP method is called in a simple transformation program. In the called ABAP program, the underlying XML Writer is used, either by calling another transformation or calling ABAP methods..
When the calling transformation program is continued, the system finds that the XML document is not properly formed any more. <runtime parameter>APDOCU ABENABAP_ST Please see st error for more details about the possible cause of this runtime error and how it could be avoided.