on 02-03-2011 10:04 AM
Hi friends,
Please help me to resolve the following error:
when I am executing the scenario,I am getting the following error in sxmb_moni:
Runtime exception in message mapping transformation
Also observed the following error message when testing in message mapping:
Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:3, col:3) com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:3, col:3) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:832) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:3, col:3)(:main:, row=3, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:3, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(Unknown Source) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:832) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(Unknown Source) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:832) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:3, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(Unknown Source) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:832) Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:3, col:3)
11:58:05 End of test
No data allowed here: (hex) 2d, 20, 3c(:main:, row:3, col:3) - i think ur problem is more related to data which is coming from file.
R u using all string data type in ur data type definition of source structure? is there any hex value coming in the file
R u using simple graphical mapping?
chirag
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chirag,
When I tested with payload from sxmb_moni,I got the following error message in MM.
RuntimeException in Message-Mapping transformation: Runtime exception during processing target field mapping /WPUFIB01/IDOC/E1WPF01/E1WPF02/KNTOBJECT. The message is: Exception:[java.lang.NumberFormatException: For input string: "CBD163"] in class com.sap.aii.mappingtool.flib3.Arithm method formatNumber[CBD163, com.sap.aii.mappingtool.tf3.rt.Context@571d571d]
Thanks,
Srinivas.
There is some value in sender file, which is not acceptable into the target structure.
The error is coming in MM only & you need to check error detail in Test Message Mapping option.
As it is a data parse problem, the details will be avilable in Test Message Mapping only.
Also check your sender side File, has some special character ?
R u using format number function for this field mapping- /WPUFIB01/IDOC/E1WPF01/E1WPF02/KNTOBJECT
is this the value u have passed in input payload - "CBD163"
try to give numerical value as a input for testing n check whether it is giving the same error. with alpha numeric value format number will give an error.
chirag
Hi Chirag,
In MM, I observed for the field mapping in customer->FormatNumber( predefined function )->KNTOBJECT where FormatNumber is taking 10 digits but I am observing when the customer number is given as 800324 is showing as success but when customer number is given as,CBD200 is throwing exception.
Thanks,
Srinivas.
Hello friends,
Thank you so much for responding to my question.
Regards,
Srinivas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Srinivas,
-->The problem is in your mapping it self.the data which is in your file or payload is unable to parse that is the reason you are getting this error.
-->In the payload you might be getting special characters i guess.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
assumedly a not wellformed message. Open the message view, copy the source (context inside the container: "view source") and save it local as *.xml. Then open the file with XML Spy, the cursor will jump to the place the parser is complaining about.
Regards,
Udo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.