Get Example source ABAP code based on a different SAP table
XML Interface 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
ABAP_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 allows parameters and variables from ST programs to be created 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.
ABAP_MODIFICATION_2 Mapping of XML schema data types
Previously, asXML allowed only mapping of the elementary predefined ABAP types to XML schema data types and vice versa. 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.
Latest notes:This change was introduced in Release 7.0, SP14. The domain XSDQNAME is available from Release 7.0, EhP1.
ABAP_MODIFICATION_3 Lengths specified in simple transformations
In the ST statements tt:value, tt:write and tt:read can be used to specify lengths in order to provide a minimum length for serialization of character strings and byte strings and a m aximum length for deserialization.
ABAP_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.
ABAP_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 statement CALL TRANSFORMATION.
ABAP_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 CALL TRANSFORMATION statement, to control the handling of stack references.
Latest notes:This change was transported back as far as Release 6.20 (in Release 7.0, from SP6).
ABAP_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 CALL TRANSFORMATION statement, to control the handling of boxed components. The new value is also the new default setting.
ABAP_MODIFICATION_8 New transformation option technical_types
error or ignore can be selected for the new transformation option technical_types of the CALL TRANSFORMATION statement, to control the handling of data reference variables with unknown dynamic types.
Latest notes:This change was transported back as far as Release 6.20 (in Release 7.0, from SP6).
ABAP_MODIFICATION_9 New transformation option clear
all, supplied, or none can be selected for the new transformation option clear of the CALL TRANSFORMATION statement, to control the initialization of the ABAP target fields during deserialization.
