Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Indeed, even in its most early frame, this less known wizard of basic change, could be truly valuable for ABAP designers. I think, ABAP designers would love to have a graphical utility to create basic change/XSLT code. I was writing some glad-code to consume an external web service from ABAP. As the web service was returning the result data in the form of an XML string, I wound up composing a Simple Transformation to get the qualities in ABAP inner table.

Consuming webservice from ABAP is Xn SE80->Repository Browser->Enterprise Services->[ right click to bring the context menu ] -->Create Proxy [ use WSDL URL e.g. to generate proxy through wizard ]. Xn LPCONFIG to configure the logical port.

I detected this enchantment stick in Simple Transformation editorial manager [ Transaction XSLT_TOOL ] and attempted to make it work. Be that as it may, couldn't unravel and composed the ST physically. Strangely, I couldn't discover any data about this alleged "Alter Simple Transformation Graphically" include. With all due respect, I looked on SAP OSS, SAP Help and SDN. There you go ...Well hunt include on SAP Sites.. is awesome in any case ;)

After a year, I coincidentally was venerating ( designers do this regularly ) my old code and it helped me to remember this utility. I gave figuring a shot by and by and figured out how to find something worth sharing. Learn SAP ABAP here.

Service proxy call provides data in the form of XML result. Code for proxy call is as below:


Now the result variable lv_output will be having the data in the form of an XML string as below. 
Note: You can use a function module SCOL_TRACE_SHOW_XML to show the XML data on screen.


In order to transform the XML to ABAP internal table, I decided to use Simple Transformation. Now I will generate the simple transformation as below:

1. Create Table Type ZNEWDATASET in transaction SE11. The hierarchy structure should be compatible with the XML hierarchy.

2. Now create the ST program in transaction XSLT_TOOL. Spot the magic stick in the editor menu.

3. Click on 'Edit Simple Transformation Graphically' button (magic stick) and you will get the editor as below. Create a new root (right click - context menu ) in "Data Roots" section. I've named it NEWDATASET but the important thing is to enter the correct type, created earlier.

4. Now you can see the data root hierarchy as below. Drag and Drop the NEWDATASET root on right panel ( Simple Transfromation ). It automaically generates the ST nodes corresponding to the ABAP structure. However, you need to adjust the names as per the XML element names.

5. Now adjust the names in ST panel as per actual XML element names.

6. Save and Activate. The ST program (Z_TEST), generated by the utility, is as below: 

<?sap.transform simple?>
<tt:transform xmlns:tt="" xmlns:ddic=""
    <tt:root name="NEWDATASET" type="ddic:ZNEWDATASET"/>
                    <tt:loop ref=".NEWDATASET">
                                     <Town tt:value-ref="TOWN"/>
                                     <County tt:value-ref="COUNTY"/>
                                    <PostCode tt:value-ref="POST_CODE"/>

7. Now use the code below to get data into ABAP internal table. 


data : result type ZNEWDATASET, "itab of table type ZNEWDATASET wa_result like line of result. 
call transformation Z_TEST source xml lv_output-GET_UKLOCATION_BY_POST_CODE_R result newdataset = result[]. 
LOOP AT result into wa_result. WRITE :/ wa_result-TOWN, wa_result-COUNTY, wa_result-POST_CODE. ENDLOOP.

Source: SAPBlog

  • No labels