Message fails in MONI.

Question

Hi,
I m triggering the IDOC from R3 the message is reaching in MONI but it is failing in moni.
I can figure out its a data problem but I am not sure because of which data the problem has come.
here is my error message which is coming in moni.
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0x15(:main:, row:1, col:27675) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException
How to trace the same pls suggest any worka arround.
I have manually put the data in message mapping and tested it is working correctly.
chirag.

Answer 1

Hi all,
I have figure out the problem.
because of special characters the message fails in MONI."#" character is in fact a control character from the R/3 system, which is a "negative acknowledge" (#0x15) character. This character is not valid for XML and in XML this is converted to NAK in XML. and in MONI it is look like   sign.
have a look at the below link:
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9420 [original link is broken] [original link is broken] [original link is broken]
Also here are my findings.
XML 1.0 allows only a few control characters.
The following is valid XML 1.0 character Range:
[2]   Char   ::=   #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]/* any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. */
Read more about character range of XML 1.0 here: http://www.w3.org/TR/REC-xml/#charsets
Hence you cannot event escape the control character #x15 in XML 1.0!!
XML 1.1 allows the use of character references to the control characters #x1 through #x1F, most of which are forbidden in XML 1.0
[2]   Char   ::=   [#x1-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]
Read more about character range of XML 1.1 here: http://www.w3.org/TR/xml11/#charsets
This is not the end of the problem, XML 1.1 does not allow you to use raw control characters, you will have to escape it using character references
For reasons of robustness, however, these characters still cannot be used directly in documents. In order to improve the robustness of character encoding detection, the additional control characters #x7F through #x9F, which were freely allowed in XML 1.0 documents, now must also appear only as character references.
You will find the above text here: http://www.w3.org/TR/xml11/#sec-xml11
thnx for ur support.
chirag
Edited by: Chirag Gohil on Oct 11, 2008 2:36 PM