Solution : https://service.sap.com/sap/support/notes/1657121 (SAP Service marketplace login required)
Summary :
The SAP Note addresses performance issues when using CALL TRANSFORMATION ID for deserializing XML documents to ABAP fields, noting excessive time consumption. The problem is traced to the XML runtime's handling of large payloads necessitating content conversion, especially with non-UTF-8 encoding. The recommended resolution includes updating to the latest kernel (disp+work) available on the SAP service marketplace and modifying approaches to XML serialization/deserialization. Specifically, adopting type X fields mitigates encoding conversion needs, as these fields inherently utilize UTF-8, streamlining processing and preventing similar issues.
Key words :
call transformation id takes, id transformation automatically, sap service marketplace, avoiding unexpected issues, exponetional runtime behavior, call transformation, xml runtime, xml document, abap fields, large payload
Related Notes :
1515148 | Problems with XML in fields of type C and type STRING |
1017101 | Encoding Problems with ABAP XML Processing |