ABAP Proxy – XML to ABAP Transformation

ABAP Proxy – XML to ABAP Transformation: When using the ABAP Proxy, Data is transformed from the XML Data Type to the corresponding ABAP Data Type or vice versa, based on the transformation generated by SAP. There will be instances when this transformation ends up in exceptions, leading to errors in the XML processing. I would like to show a way of finding out and modifying the default transformation generated in SAP for the ABAP Proxy.

Custom Transformation may be needed in occasions such as:

– Parsing and Transformation specific to the target system, such as Date, Time, Time Zone, and Number formats, and handling the XSD Attributes

– Restrictions on regeneration of the Proxy structure to suit different sender interfaces

This could throw exceptions such as:

– CX_ST_DESERIALIZATION_ERROR

– CX_ST_GROUP_MISSING_CASE

– CX_XSLT_RUNTIME_ERROR

– CX_ST_MATCH_ATTRIBUTE

The XML handling will then report errors such as:

– PARSE_APPLICATION_DATA

– CONVT_DATA_LOSS

These errors are usually associated with inbound proxies, and occur before the ABAP Proxy is executed. This leaves no room for error handling in the ABAP Proxy. Then the only place for such error handling is the XML Transformation. This option can also be used for XSL transformation in outbound proxies. In any case, the benefit is in maintaining a single Transformation program. It can be useful for any special XSL validations.

 

 

Finding the Transformation Program name associated with an
ABAP Proxy

 

 

 

 

 

 

Summary

 

 

Given the default setting of Standard and Simple, the transformation program names start with ‘/1SAI/TXS’ followed by the corresponding SPROXXSL table entry. This program can be used for testing and debugging, and can be edited as required. It is not yet clear as to if and how the customers can use the Extended and non-Simple XSL Transformation programs in the ABAP stack.