topic Re: Abap to XML multi-level structure in Application Development and Automation Discussions

Abap to XML multi-level structure

former_member605430 — Tue, 04 Aug 2009 12:55:25 GMT

Hi,

I need to extract invoice with header and item (more than 1) into XML file.

So, I found [this document|http://www.heidoc.net/joomla/development-mainmenu-31/22-sap~~xslt/15-sapxslt] that explain how to extract from [Abap to Xml |http://www.heidoc.net/joomla/development-mainmenu-31/22-sap~~xslt/15-sapxslt] a simple flat with one level structure.

I'm novice with XSLT transformation language.

I'm not able to generate a loop that create for each header a list of item data.

Please, there's anyone can help me with this problem?

Any Example code?

Re: Abap to XML multi-level structure

rainer_hbenthal — Tue, 04 Aug 2009 13:05:05 GMT

did you try call transformation?

Re: Abap to XML multi-level structure

former_member605430 — Tue, 04 Aug 2009 13:18:20 GMT

Yes, i do a call transformation but the result is like this:

- HEADER1

- ITEM1

-HEADER1

- ITEM2

This is not correct because header is the same.

the correct result that i need is:

- HEADER1

- ITEM1

- ITEM2.

I'm on a 4.7 release.

Re: Abap to XML multi-level structure

rainer_hbenthal — Tue, 04 Aug 2009 13:21:55 GMT

How does the type definition of the variable looks like you are transforming?

Re: Abap to XML multi-level structure

former_member605430 — Tue, 04 Aug 2009 13:41:26 GMT

This is the Program.

TYPE-POOLS: abap.

CONSTANTS gs_file TYPE string VALUE 'C:\tempo\customer.xml'.

TYPES: BEGIN OF ts_person,

cust_id(4) TYPE n,

firstname(20) TYPE c,

lastname(20) TYPE c,

codfisc(16),

campo1(16),

END OF ts_person.

Table for the XML content

DATA: gt_itab TYPE STANDARD TABLE OF char2048.

Table and work area for the data to fill the XML file with

DATA: gt_person TYPE STANDARD TABLE OF ts_person,

gs_person TYPE ts_person.

Source table that contains references
of the internal tables that go into the XML file

DATA: gt_source_itab TYPE abap_trans_srcbind_tab,

gs_source_wa TYPE abap_trans_resbind.

For error handling

DATA: gs_rif_ex TYPE REF TO cx_root,

gs_var_text TYPE string.

Fill the internal table

gs_person-cust_id = '3'.

gs_person-firstname = 'Bill'.

gs_person-lastname = 'Gates'.

gs_person-codfisc = 'ELFO1234'.

gs_person-campo1 = 'TEST'. "ITEM

APPEND gs_person TO gt_person.

gs_person-cust_id = '3'.

gs_person-firstname = 'Bill'.

gs_person-lastname = 'Gates'.

gs_person-codfisc = 'ELFO1234'.

gs_person-campo1 = 'TEST2'. "ITEM

APPEND gs_person TO gt_person.

GET REFERENCE OF gt_person INTO gs_source_wa-value.

gs_source_wa-name = 'IPERSON'.

APPEND gs_source_wa TO gt_source_itab.

GET REFERENCE OF gt_person INTO gs_source_wa-value.

gs_source_wa-name = 'IRIGA'.

APPEND gs_source_wa TO gt_source_itab.

Perform the XSLT stylesheet

TRY.

CALL TRANSFORMATION z_prova

SOURCE (gt_source_itab)

RESULT XML gt_itab.

CATCH cx_root INTO gs_rif_ex.

gs_var_text = gs_rif_ex->get_text( ).

MESSAGE gs_var_text TYPE 'E'.

ENDTRY.

The XML is not displayed.

Could you help me, please?

Edited by: Stefano Pastorelli on Aug 4, 2009 3:42 PM

Edited by: Stefano Pastorelli on Aug 4, 2009 3:43 PM

Edited by: Stefano Pastorelli on Aug 4, 2009 3:45 PM

Edited by: Stefano Pastorelli on Aug 4, 2009 3:47 PM

Edited by: Stefano Pastorelli on Aug 4, 2009 3:48 PM

Re: Abap to XML multi-level structure

rainer_hbenthal — Tue, 04 Aug 2009 14:21:49 GMT

next time please enclose the code in appropriate tags, you can find them on the right side whly creating a post.

second you should use xstring for the result xml in the transformation result.

third i can not understand the gt_source_itab, why dont you use the binding like

iperson = abapvar1 iriga = abapvar2

To avoid errors with your transforamtion z_prova first try to use transformation ID. If the xml is correct the change the xslt again to transform the xlm to your needs.


CALL TRANSFORMATION ID
SOURCE iperson = gt_person uriga = gt_person
RESULT XML xxml.

xxml should be declared like


DATA:
  xxml type xstring.

As you are on 4.7 you will have problems tith xstring, the debugger cant show it in readable format. So ypou have to use string at first changing to xstring if everything is ok. Another way of cheking the xml is the function


   call function 'DISPLAY_XML_STRING'
      exporting
        xml_string            = xxml
*         TITLE                 =
*         STARTING_X            = 5
*         STARTING_Y            = 5
      exceptions
        no_xml_document       = 1
        others                = 2.

    if sy-subrc > 0.
      message 'Cant display XML' type 'A'.
    endif.

but i dont know if this FM is available on 4.7