cancel
Showing results for 
Search instead for 
Did you mean: 

Transformation Error

Former Member
0 Kudos

Krishna and other thanks for your help. I checked my message mapping and I am getting the following error

Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) a0, 20, 3c(:main:, row:2, col:4) com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) a0, 20, 3c(:main:, row:2, col:4) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:130) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) a0, 20, 3c(:main:, row:2, col:4)(:main:, row=2, col=4) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) a0, 20, 3c(:main:, row:2, col:4) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2668) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) -


at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) a0, 20, 3c(:main:, row:2, col:4) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2668) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 3 more Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) a0, 20, 3c(:main:, row:2, col:4)

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Did anyone get the solution for this issue?

Thanks

former_member206604
Active Contributor
0 Kudos

Hi,

I think this is parser error due to some invalid characters in the data. Try using different encoding like ISO-8859-1

Thanks,

Prakash

Former Member
0 Kudos

Where exactly I have to used the differet encoding?

Thanks Praksh

former_member206604
Active Contributor
0 Kudos

Hi,

If you are using file adapter as a sender you can select the Encoding type there. You can also do it in your XSD.

Please tell us the whole scenario..

Thanks,

Prakash

bhavesh_kantilal
Active Contributor
0 Kudos

Mohini,

Can you give look into the incoming payload and use the same to test your message mapping. check if there is any invalid data in it.

If you are using the sender file adapter, then use then you can change the encoding in the file adapter itself.

REgards,

Bhavesh

Former Member
0 Kudos

Source Structure

-

-


-

Target Structure

-

-


Mapping

-

-


Request Mapped to constant [], 1..1

DataRequest Mapped to constant [], 1..1

InternalID to InternalID

domain to Domain (its an attribute)

Only in the above mapping Its causing issue. whats wrong with that.

bhavesh_kantilal
Active Contributor
0 Kudos

Mohini,

Try mapping EmpoyeeMessage ot source to REQUEST and DATAREQUEST of the target.

Regards,

Bhavesh

former_member206604
Active Contributor
0 Kudos

Hi Mohini,

Try what Bhavesh said if you still face the same problem

Copy the following XSLT into a File ChangeEncoding.xsl and then zip it. Import it under Imported Archive and add one more mapping program in the interface mapping and this shoule be before the Message Mapping.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="text/xml" version="1.0" encoding="ISO-8859-1" indent="yes"/>
<xsl:template match="/">
<xsl:copy-of select="child::node()"/>
</xsl:template>
</xsl:stylesheet>

If you face the same problem post the source XML exactly and the expected target XML.

Thanks,

Prakash