Get Example source ABAP code based on a different SAP table
VERSION 5 IN
ABAP and XML This section describes how XML data can be created and read in ABAP. The main topics are
processing and creating XML data using parsers and renderers that are created and used using the APIs of class libraries,
the direct transformation of ABAP data to XML format (serialization) and reads of data in XML format to ABAP data objects (deserialization) using transformations that exist as programs in the repository. ABAP provides the following technologies for handling XML:
Class libraries for XML
Transformations for XML Class libraries enable the parsing and rendering of general XML data, while transformations are used mostly to serialize ABAP data to XML and deserialize XML data to ABAP. The technologies are linked by the fact that objects of the class libraries can serve as the source and target of transformations.
Latest notes:
In this documentation, the term XML data generally indicates a character string or byte string whose value is in XML format and which can occur in various forms, such as strings or internal tables. The term XML document generally indicates the representation of XML data in DOM format.
When storing in formats other than UTF-8, it should be noted that the XML data must be prefixed with a byte order (BOM), in accordance with the XML standard. This applies specifically to storing character-like data in the character representation UCS-2 used by the ABAP programming language. This can mean that XML data that was written as character-like data in a Unicode system cannot be handled directly as such in a non-Unicode system. NON_V5_HINTS
When XML data is stored in strings or internal tables, it is best to use byte strings or byte-like line types and the UTF-8 code page for the representation. The sXML Library supports byte-like storage only. The iXML Library and the statement CALL TRANSFORMATION also support text strings and internal tables with character-like data types. ABAP_HINT_END
