XML Schema Import Into an Abap System

Kirill Smirnov's Blog: XML Schema Import Into an ABAP system Posted by Kirill Smirnov  Feb  Feb 2, 2015 

It sometimes happens... You do not have an SAP PI instance (or something similar), however you need to download (or upload) an XML file, and it is very hard to control the file structure. All you have is an XML schema provided by an external system, and there is a challenge - to re-create in SAP something similar to the file format described in the XSD. And remember - no SAP PI or other Integration Bus capable of doing the import on your behalf! This tiny utility uses standard SAP ABAP Proxy mechanism to import the data definition and create respective DDIC objects. The process flow is very similar to Service Consumer creation in SPROXY transaction, however with this utility you can use directly use an XSD file (dummy WSDL is created automatically). The utility was also inspired by this blog - http://sapblog.rmtiwari.com http://sapblog.rmtiwari.com.. Please note that in order to make this post easier to read, I've omitted some basic routines (e.g. for file selection dialogue, message output etc.). Global data and selection-screen: *&-----------------------*&---------------------------------------------------------------------------------------------------------* ------* *& Report Z_IMPORT_XML_SCHEMA *& *&------------------------*&-------------------------------I have used the following sequence: 1. File File upl uploa oad; d; 2. Conversion Conversion to WSDL - format format which is "native" for an ABAP/4 ABAP/4 proxy generato generator; r; 3. Instantiation Instantiation of the proxy proxy object object - using a generate generated d WSDL; 4. DDIC update update (and activation activation if desired); desired);

Step 1 - File upload: FORM upload_file USING iv_filename TYPE anyuri CHANGING cv_xcontent TYPE xstring. DATA: lo_slib_ret Step 2 - WSDL conversion: FORM xsd2wsdl USING iv_xcontent TYPE xstring CHANGING cv_wsdl TYPE xstring. DATA: lv_mes Step 3 - Instantiation of a proxy object: object : FORM init_proxy USING iv_wsdl TYPE xstring iv_pckg iv_praefix CHANGING Step 4 - DDIC update.... FORM save_proxy USING io_proxy TYPE REF TO cl_proxy. DATA: lx_error TYPE REF TO cx_proxy_gen_error, ....and activation: FORM activate_proxy USING io_proxy TYPE REF TO cl_proxy iv_trreq TYPE trkorr . DATA: If you prefer not to keep "redundant" development objects, feel free to delete the proxy itself (without deletion

of the subsequent objects

). However, it should affect nothing if the proxy definition is transported to the

production environment.

Generated by Jive on 2015-02-02+01:00 1

lt_objec

Kirill Smirnov's Blog: XML Schema Import Into an ABAP system

At the end of the day, you will get the DDIC structures which correspond to the ones described in an XML schema. Now using those structures your potential XML Simple Transformations will be really  simple. 36 Views Tags: abap, xml, import, sap_netweaver, xsd, xml_to_abap, proxies, external_definition, xml_schema, schema; There are no comments on this post

Generated by Jive on 2015-02-02+01:00 2