Skip to content

ABAP Keyword Documentation →  ABAP − Reference →  Data Interfaces and Communication Interfaces →  ABAP and JSON →  Transformations for JSON 

Identity Transformation for JSON

The predefined identity transformation ID is executed internally so that all requirements for JSON transformations are met. The following combinations are possible:

  • ABAP data objects as source

    The ABAP data is serialized directly to its canonical JSON format asJSON. In this concept, the ABAP data is serialized first to its XML format asXML. This is then transformed to an asJSON-XML representation and passed to the writer.
  • XML data as XML source

    The XML source must be in JSON-XML format and is passed to the writer directly.
  • JSON data or JSON reader as XML source

    The JSON-XML data is passed to the writer directly.
  • ABAP data objects as target

    The JSON data must be in an asJSON format that matches the ABAP data objects. The JSON data is deserialized directly to the ABAP data objects. In this concept, an asJSON-XML representation of the asJSON data is edited that is first transformed to asXML and then deserialized to the ABAP data objects.
  • XML data as XML target

    The JSON-XML data is passed to the XML target directly.
  • JSON writer as XML target

    The JSON-XML data is passed to the writer directly.

When XML data is specified as an XML source or XML target, this covers all data that can be specified behind XML in CALL TRANSFORMATION, except for JSON data and JSON readers and writers.

Other versions: 7.31 | 7.40 | 7.54


  • Copies of the XSL transformation ID made from the repository to other XSLT programs are not handled like ID internally and cannot be used like ID for JSON data.

Executable Examples