Symptom
- A mapping runtime parser exception occurs for Process Integration (PI) messages received from Sender systems that use an SM59 TCP/IP (type 'T') connection to connect to PI Sender adapters, e.g., RFC and IDoc_AEE.
An error trace message exception would resembles the following :-
====================================================
Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1></SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException:</SAP:P2>
<SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.ParserE</SAP:P3>
<SAP:P4>xception: XMLParser : #0 not allowed in Character~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping
com.sap.aii.utilxi.misc.api.BaseRuntimeException:Fatal Error:
com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not
allowed in Character~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Read more...
Environment
- PI Release Independent
- SAP NetWeaver
- SAP Process Integration
Product
SAP NetWeaver Process Integration 7.1 ; SAP NetWeaver all versions ; SAP enhancement package 1 for SAP NetWeaver Process Integration 7.1
Keywords
Non-Unicode, Unicode , KBA , BC-XI-IBC-MAP , Mapping , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview