Unsported character error in message mapping

I use a sender mail adapter to read an xml and then map it to another message type. Most of the time, it's ok. But when there are some special German character such as ö ä ß, then I get the "unsuported character" error.
Anyone could help?
thanks!
com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 32(:main:, row:11, col:14) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205) at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143) at com.sap.engine.lib.xml.parser.XMLParser.scanCharData(XMLParser.java:2000) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2445) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) 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(SAXParser.java:345) 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:534) -
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:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 32(:main:, row:11, col:14) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205) at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143) at com.sap.engine.lib.xml.parser.XMLParser.scanCharData(XMLParser.java:2000) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2445) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) 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) ... 4 more com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 32(:main:, row:11, col:14) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205) at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143) at com.sap.engine.lib.xml.parser.XMLParser.scanCharData(XMLParser.java:2000) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2445) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) 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(SAXParser.java:345) 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:534) -
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:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 32(:main:, row:11, col:14) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205) at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143) at com.sap.engine.lib.xml.parser.XMLParser.scanCharData(XMLParser.java:2000) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2445) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) 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) ... 4 more

As the mail server provides the correct encoding, the MessageTransformBean does the conversion to UTF-8.
If the encoding was not set by the mail server, then the MessageTransformBean would only set the content type, but not do any conversion.
When you are not sure, if the content type is by the mail server, you can apply the MessageTransformBean twice: First with iso-8859-1, second with UTF-8
I am not sure, why the mapping tool cannot do the conversion, but I think this is because the content type is not application/xml. But this is only a guess.
What happens, when you only apply the MessageTransformBean, but do not change the XML encoding?

Similar Messages

Error: "Operation (Message) Mapping ... does not exist" during activation

Hello Colleagues,
I face following problem at our PI 7.1 System.
After import and activating Integration Builder (Directory) Objects I received the Error "Operation (Message) Mapping ... does not exist" but the object (s) exist at Enterprise Service Builder (Integration Repository) at respective Software Component Version.
The individual Product and respective Software Component Version was created at SLD and imported at Enterprise Service Builder (Integration Repository). Afterwards Namespaces with different objects was created incl. the missing Operation Mapping.
As Check:
When I try to import under menu Tools\Apply Model from ES Repository at Integration Builder (Integration Directory) i see onyl SAP (SAP BASIS 7.1) Software Components.
I am not able to find any object regarding the individual created Product\Software Component.
So, i asume objects from the Enterprise Service Builder (Integration Repository) aren't available at Integration Builder (Integration Directory).
SLD cache refresh and application restart already performed.
Any idea?
Many thanks in advance!
Regards,
Jochen

Hi Laxmi,
attached short steps that we performed.
In general in upfront:
This behavior happend after import objects from DEV to TEST for Enterprise Services Builder (IR) and Ingegration Builder (ID) in addition manual object creation at SLD for Technical Systems and Business Systems.
We don't have (currently) a central SLD for each environments DEV, TEST, PROD (not finished setup up to now). For each environments we have a local SLD at PI (XI).
Deployment steps:
- Product and respective Software Component Version created under Software Catalog
- objects creation at SLD for Technical Systems
- objects creation at SLD for Business Systems
- objects imported from DEV to TEST for Enterprise Services Builder (IR) incl. save and activation
- objects imported from DEV to TEST for Integration Builder (ID)
- manual configuration for communication channels performed
- after save and activation i received following error message: "Object Operation Mapping: ... does not exist.
Because of this error message I thing objects out of the Enterprise Services Builder (IR) aren't available at Integration Builder (ID) but i don't know the cause.
Could you help me to understand this behavior?
Many thanks in advance!
Regards,
Jochen

System Error During Message Mapping

I've set up a simple mapping scenario that sends a DEBMAS06 IDoc from our R/3 system to XI mapping to DEBMAS06 and writing out to a file. I am getting the following system error during message mapping:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1>Server repository could not create function template for 'SMPP_CALL_JAVA_RUNTIME</SAP:P1>
I have gone back to the Design Builder and tested out the message mapping and the interface mapping and both work successfully. I have also taken the payload of the message and submitted it via the RWB and it generates the same error as when sent from R/3. Any other places I can look?

Hi Mike,
You have got the connectivity issue problem between ABAP and J2EE stack. When do the test in the Message Mapping, thats the J2EE and it works. But during the runtime it has to go to the Integratin Server, which is the ABAP stack. Fix the connectivity issue, check the smicm,trace and debug log etc.
Hope this helps.
Cheers,
Ranjan

Error Activating Message Mapping

HI All,
I am getting the below error when i try to activate any message mapping in the IR. Any ideas?
" Starting compilation Source code has syntax error: java.lang.NoClassDefFoundError: com/sun/tools/javac/Main Exception in thread "main"
Thank you in Advance.
D

Hi,
Is there recently been an update like WAS ABAP and WAS JAVA to SPS13(nw2004s)?
Please check this thread there are some pointers in it:
Re: 500 internal server error
Best regards,
Guido

Error in message Mapping(file to file scenario)

Hi friends,
In file to file scenario i am getting error like this while activating standard change list in IR.
Activation of the change list canceled Check result for Message Mapping MM_file2filejuly27 | URN:file2fileJuly27.com:
Starting compilation
Compilation complete
Check result for Software Component Version praba.com | PRABA.COM | 2007 | 0:
The standard error type ExchangeLogData is not defined for the namespace URN:file2fileJuly27.com
Save the software component version definition again. The object is then saved automatically
could you help me out how to correct this error?

Prabha,
You should not delete any existing standard Data types provided by SAP. ExchangeLogData and ExchangeDaultData are standard data types get created when you create new namespace.
If you have already deleted then copy them from other Namespace to your namespace. Activate your default data type first and then your objects.
Hope this will solve your problem.
Nilesh

Activation error in message mapping

Hi,
while activating Message mapping i am getting the error like this.
how to get rid of this error?
error:
Activation of the change list canceled Check result for Message Mapping MM_XXXXXX | http://www.xyerxd.com/mm
Imported source message has invalid reference IDoc
DEBMAS.DEBMAS06 | urn:sap-com:document:sap:idoc:messages
Imported target message has invalid reference Message Type MT_Receiver | http://www.xyerxd.com/mm

hi
Hope you are using the inactive versions of message/Idoc types for mapping.
First activate the message/Idoc types used in the message mapping.
Then open the message mapping, from the menu choose refresh.
Complete the mapping and test.
Now do the activation.
rgds,
Arun

Error in message mapping

I used MT_PerformRate for both sender side and receiver side in message mapping
When I goto interface mapping and click on the mapping program it gives following error.
The source or target structure has been changed or could not be found in the Integration Repository. The mapping definition contains elements or attributes that do not exist in the changed structure. The relevant entries will be deleted
Target structure has no such path: /ns0:MT_PerformRate/@EmpName. Skipping mapping
Target structure has no such path: /ns0:MT_PerformRate/@EmpNo. Skipping mapping
Target structure has no such path: /ns0:MT_PerformRate/@PerformRating. Skipping mapping
Target structure has no such path: /ns0:MT_PerformRate/@RatingDesc. Skipping mapping
Target structure has no such path: /ns0:MT_PerformRate/@EffectiveDate. Skipping mapping
In mapping editor target fileds are shown in red.
I can see two message mappings in Change list one with target fileds in red and one with green.
I do not know what is happening
PLs suggest

Thanks Amith and Ameer for your answers.
The exact reason was because I did not used recordset in my datatype creation.
But I did not set ignoreRecordsetName to true
For who get similar problem please see below details and link
A <Recordset> element is inserted in the XML structure for each recordset structure. This level is not always required, particularly if the recordset only contains one structure definition.
If you set the parameter to true, the <Recordset> element is not inserted.
http://help.sap.com/saphelp_nw70/helpdata/EN/2c/181077dd7d6b4ea6a8029b20bf7e55/frameset.htm
Thanks,
Raj

Error in Message-Mapping transformation

I'm getting an error while processing the data from JDBC to SAP through IDOC's.
During the application mapping com/sap/xi/tf/_MM_HRMD_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~
while testing the mapping in IR (message mapping) it got succesfull.
while testing the mapping in ID (Test configaration) with inbound payload we are getting the below error.
interface Mapping
... (173 lines)
Please provide the solution for this...

Hello,
Check out the trace thorougly in MONI as at which node/field the error is occuring.
W.r.t ID testing,kindly check your interface determination(sender,receiver parameters and also the inbound interface etc)
Regards
Madhu

Error in message mapping of IDoC Invoic02

Hi,
i have imported the invoic02 idoc into PI system. i have mapped the required field os idoc with standard XSD which is imported through ED. I'm able to most of the fields with idoc and XSD. however, some of the node in xsd are repaeting.
so here the part of xsd with which i'm mapping.
(first_node)ListOfTaxSummary                      0..1
(second_parent_node)TaxSummary                   1..unboubed
(child_node) tax                                 1..1
(element)TaxAmount                                0..1
(element)TaxCategoryCoded                         0..1
here the i have mapped ListOfTaxSummary    with the idoc node E1EDS01
TaxSummary with E1EDS01
tax with E1EDS01.
i tried all possibilities with different mapping. but i'm able to get the tax node under taxsummary with the element. the problem its been repeated as E1EDS01 idoc repeats.
please help us in solving this problem.
Thanks
Kind regards,
Lalitkumar.

Could someone tell me is there any relation for the above error in XML messages and to the message mapping?
The error mentions that you have used an IDOC in your mapping program which is not found in the ESR....you need to check if the IDOC is present in the ESR and is present under the correct SWCV.
Once you have done the check do some dummy change to the mapping and activate it (if in DEV) and then check the CACHE.

Error in Message Mapping "Target message IDOC: ORDRSP.ORDERS02 does not exi

Hi,
I have joined newly to the team.
When I tried to open one message mapping it throwinf follwing error...
"Target message IDOC: ORDRSP.ORDERS02 does not exist in software component version ID: 44423362454456485465..
Check whether the software component version ID: 44423362454456485465 is in Enterprise Service Repository. Import this version if necessary"
Is there any impact because of which in the message flow?
In my case some of the messages are failing with mapping error "runtime exception occured during application mapping com/sap/xi/tf/_SUS2MMOrderResponse_; java.lang.NullPointerException: while trying to invoke the method java.util.Map.get(java.lang.Object) of an object loaded from field com.sap.aii.map`"
And some of the messages are processed sucessfully and they also using the same mapping program 'SUS2MMOrderResponse'.
Could someone tell me is there any relation for the above error in XML messages and to the message mapping?
Regards
Baskaran K

Could someone tell me is there any relation for the above error in XML messages and to the message mapping?
The error mentions that you have used an IDOC in your mapping program which is not found in the ESR....you need to check if the IDOC is present in the ESR and is present under the correct SWCV.
Once you have done the check do some dummy change to the mapping and activate it (if in DEV) and then check the CACHE.

Runtime error in message mapping.

Hi experts.
My scenario is File --> PI --> File.
During the message mapping there are a few RFC lockups.
I have configured an communication component for the RFC destination, and a Receiver communication channel to the RFC system.
When I am trying to check the message mapping and the operation mapping from the integration builder every thing works just fine.
In the interface determination i have configured the rfc parameter for the mapping.
When I am trying to run the hole process i receive an error saying:"Runtime exception from: java.lang.nullPointerException:
null at com.sap.guid.GUID.parsHEXguid(guid.java:1015)
reguars Max

Hi.
As i have already said when I am trying to test the same operation mapping directly in the integration builder with the same message, it passes the mapping without any exceptions.
I think the catch may be in the fact that there are a few rfc calls inside the graphical mapping.
Any suggestions?
Regards Max.

GUID FormatExceptionError in End to End Scenario at runtime, but no error in Message Mapping test

Hi Friends
My scenario is Idoc to RFC and , my mapping is working fine and executing successfully in the message map tab but , it is failing in the End to End case at runtime with GUIDFormatException error, can anyone please help on this , I have searched the forum and no proper or concrete answers are available , creating a separate or new channel is not an option.

Hi,
Check in which step you are receiving this error
1st check in SXMB_MONI/trace
2nd If the above is successful then check in rwb/comm channel monitoring/receiver rfc channel.
Regards
Venkat

Compiler Process error in Message Mapping

Hi all,
I have recently installed an XI system.
First time when i create simple message mapping, it was showing compilation process error.
Please tell me what needs to be done so that message mapping works well. It is really urgent.
Thank you all.
Regards,
Kavan Shah

hi
check the HDD space on your XI server machine
try checking the java path on your XI machine
if this will not work contact the SAP via an OSS note
As this is a new XI server it probably means it
was incorrectly installed
Note:please reward points if solution found helpfull
Regards
Chandrakanth.k

Query Error in Message Mapping

Hi everyone
I am working on a BPM, that BPM has a Message Mapping that makes a Query to a DB.
When I send a message with multiple details its working in the following way:
1.- If the first detail makes a query of a catalogue that exists on the DB, and the second detail makes a query to a cataloge that does not exists on the DB it finishes with error.
2.- If the first detail has the query of an unexisting catalogue on the DB, and the second detail has the query that exists on the DB it finishes correctly.
Can someone give me some light on whats happenning here?
Thanks in advanced

Ended message

Error in message mapping - Cannot produce target element

As one step in my integration process, I am builing a very simple file to BPM integration (inbound MI async, outbound MI abstract).
The source type and the target type are completely equal - I am only doing some modifications to some of the content.
The type for both messages - source & target message - is an imported external definition (DTD), and hence no DT or MT are created.
As a first step I am trying to fill the target message with the content from the source message (without any modifications to the content). However, when testing this in the message mapping area, I get an error message already when filling the first element, the 'root node'.
The error message is as follows:
Start of test
Compilation of <MM name> successful
Cannot produce target element <elementname>. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element <elementname>. . Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
End of test
Any suggestions?
Thanks,
C

Thanks,
when creating the source message manually in the MM it worked - so nothing wrong with the mapping.
I saved this file and compared with the "original file" - containing the content which I wanted to upload, and on which the xsd (external definition) was based - and there where some inconsistancies.
I changed some values in the source XML which made it work, also when uploading the file from a drive.
So, I will go back to the source system and try to get a better XML.
Thanks for now!

Unsported character error in message mapping

Similar Messages

Maybe you are looking for