Skip to content

ABAP Keyword Documentation →  ABAP - Release-Specific Changes →  Changes in Release 7.0 and its EhPs →  Changes in Release 7.0, EhP2 

XML Binding in Release 7.0, EhP2

In Release 7.0, EhP2 the interface between ABAP and XML has been enhanced as follows:


1. Access to ABAP Objects from simple transformations


2. Mapping of XML schema data types


3. Lengths specified in simple transformations


4. Validation of values in simple transformations


5. New values for transformation option value_handling


6. New values for transformation option data_refs


7. New value for transformation option initial_components


8. New transformation option technical_types


9. New transformation option clear

Other versions: 7.31 | 7.40 | 7.54

Modification 1

Access to ABAP Objects from Simple Transformations

The following new ST statements can be used to call methods of global classes and create objects of these classes in ST programs:

  • tt:call-method calls static methods or instance methods.
  • tt:create-object creates an instance of a global class.

For addressing objects, a new addition tt:ref-type of the statements tt:parameter and tt:variable has been introduced that makes it possible to create parameters and variables from ST programs explicitly as reference variables. Another new command tt:cast also enables a Down Cast of reference variables in ST programs.

See the ST Command Overview.

Modification 2

Mapping of XML Schema Data Types

Previously, asXML allowed only mappings of the elementary built-in ABAP types to XML schema data types and back. But this did not cover all XML schema data types. Special domains named XSD... have been introduced that allow mapping of further XML schema data types.


Notes

  • This change was introduced in Release 7.0, SP14.
  • The domain XSDQNAME is available from Release 7.0, EhP1.

Modification 3

Lengths Specified in Simple Transformations

In the ST statements tt:value, tt:write and tt:read can be used to make length specifications in order to provide a minimum length for serialization of character and type strings and a maximum length for deserialization.

Modification 4

Validation of Values in Simple Transformations

An XML schema type and further restrictions can now be specified in the ST statements tt:value, tt:write, and tt:read, to validate a value with respect to a value range.

Modification 5

New Values for Transformation Option value_handling

The new values "accept_decimal_loss" and "reject_illegal_characters" can be selected for the transformation option value_handling of the statement CALL TRANSFORMATION.

Modification 6

New Values for Transformation Option data_refs

The new values heap-or-error and heap-or-create can be selected for the transformation option data_refs of the statement CALL TRANSFORMATION, to control the handling of stack references.


Note

This change was transported back as far as Release 6.20 (in Release 7.0, from SP6).

Modification 7

New Value for Transformation Option initial_components

The new value suppress_boxed can be selected for the transformation option initial_components of the statement CALL TRANSFORMATION, to control the handling of boxed components. The new value is also the new default setting.

Modification 8

New Transformation Option technical_types

error or ignore can be selected for the new transformation option technical_types of the statement CALL TRANSFORMATION, to control the handling of data reference variables with unknown dynamic types.


Note

This change was transported back as far as Release 6.20 (in Release 7.0, from SP6).

Modification 9

New Transformation Option clear

all, supplied, or none can be selected for the new transformation option clear of the statement CALL TRANSFORMATION, to control the initialization of the ABAP target fields in deserializations.