Solution : https://service.sap.com/sap/support/notes/1017101 (SAP Service marketplace login required)
Summary :
SAP Note describes XML parsing issues in ABAP across various functions – iXML library, XSLT transformations, and simple transformations. Major symptoms involve errors during XML parsing, typically through IF_IXML_PARSER=>PARSE() method in iXML or exceptions like CX_XSLT_RUNTIME_ERROR and CX_ST_ERROR subclasses during transformations. Root causes are linked to malformed XML or encoding mismatches in XML documents handled in ABAP, particularly around encoding declarations and actual encoding. Solutions suggest debugging techniques using the ABAP debugger, emphasizing the importance of correct encoding practices and the use of binary-type variables for XML data to avoid encoding conflicts, especially during system Unicode migrations or RFC communications. Further, adjustments include suppressing or modifying incorrect encoding declarations via CALL TRANSFORMATION or direct string manipulation.
Key words :
customer component bc-aba-xml abap xml processing priority recommendations / additional info category, type string 1657121 call transformation id performance issue 1298098 chart engine - hiding key figures, type string 1319517 unicode collection note 1298098 chart engine - hiding key figures, sap notes 1657121 call transformation id performance issue 1515148 problems, replace section offset i2 length i1, abap xml processing tools insert, abap debugger offers comfortable means, 1319517 unicode collection note 1515148 problems, utf-16 character immediately terminates parsing, xml encoding conflicts easily arise
Related Notes :
| 1657121 | CALL TRANSFORMATION ID performance issue |
| 1515148 | Problems with XML in fields of type C and type STRING |
| 1319517 | Unicode Collection Note |
| 1298098 | Chart Engine - Hiding Key Figures |