Simple Transformation XML to ABAP   - error CX_ST_MATCH_ELEMENT

Hi all,
I have a problem with a transformation from xml to abap. My XML file (taken from a pdf file) is
<?xml version="1.0" encoding="iso-8859-1" ?>
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
  <NETWORK>E60000000000</NETWORK>
  <OPERAZIONE>0010</OPERAZIONE>
- <TABELLA>
- <ROW xmlns:xfa="http://www.xfa.org/schema/xfa-data/1.0/" xfa:dataNode="dataGroup">
  <MANDT>300</MANDT>
  <NETWORK>E60000000000</NETWORK>
  <OPERAZIONE>0010</OPERAZIONE>
  <ID_ACT>1</ID_ACT>
  <DESC_ACT>ATTIVITÀ1</DESC_ACT>
  <LONG_TXT></LONG_TXT>
  <MAKE_BUY></MAKE_BUY>
  <WP></WP>
  <EVENTO_TECH></EVENTO_TECH>
  <TIPO_LEGAME></TIPO_LEGAME>
  <CONSEGNA></CONSEGNA>
  </ROW>
- <ROW xmlns:xfa="http://www.xfa.org/schema/xfa-data/1.0/" xfa:dataNode="dataGroup">
  <MANDT>300</MANDT>
  <NETWORK>E60000000000</NETWORK>
  <OPERAZIONE>0010</OPERAZIONE>
  <ID_ACT>2</ID_ACT>
  <DESC_ACT>ATTIVITÀ2</DESC_ACT>
  <LONG_TXT>ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2</LONG_TXT>
  <MAKE_BUY>M</MAKE_BUY>
  <WP></WP>
  <EVENTO_TECH></EVENTO_TECH>
  <TIPO_LEGAME></TIPO_LEGAME>
  <CONSEGNA></CONSEGNA>
  </ROW>
  </TABELLA>
  </asx:values>
  </asx:abap>
my transformation is
<?sap.transform simple?>
<tt:transform xmlns:tt="http://www.sap.com/transformation-templates">
  <tt:root name="ROOT"></tt:root>
  <tt:root name="NETWORK"></tt:root>
  <tt:root name="OPERAZIONE"></tt:root>
  <tt:template>
  <abap>
    <values>
       <network>
           <tt:value ref="NETWORK"></tt:value>
       </network>
       <operazione>
           <tt:value ref="OPERAZIONE"></tt:value>
       </operazione>
       <tabella>
          <tt:loop ref=".ROOT" name="line">
            <mandt>
              <tt:value ref="$line.mandt"></tt:value>
            </mandt>
            <network>
              <tt:value ref="$line.network"></tt:value>
            </network>
            <OPERAZIONE>
              <tt:value ref="$line.OPERAZIONE"></tt:value>
            </OPERAZIONE>
            <ID_ACT>
              <tt:value ref="$line.ID_ACT"></tt:value>
            </ID_ACT>
            <DESC_ACT>
              <tt:value ref="$line.DESC_ACT"></tt:value>
            </DESC_ACT>
            <LONG_TXT>
              <tt:value ref="$line.LONG_TXT"></tt:value>
            </LONG_TXT>
            <MAKE_BUY>
              <tt:value ref="$line.MAKE_BUY"></tt:value>
            </MAKE_BUY>
            <WP>
              <tt:value ref="$line.WP"></tt:value>
            </WP>
            <EVENTO_TECH>
              <tt:value ref="$line.EVENTO_TECH"></tt:value>
            </EVENTO_TECH>
            <TIPO_LEGAME>
              <tt:value ref="$line.TIPO_LEGAME"></tt:value>
            </TIPO_LEGAME>
            <CONSEGNA>
              <tt:value ref="$line.CONSEGNA"></tt:value>
            </CONSEGNA>
         </tt:loop>
        </tabella>
      </values>
    </abap>
  </tt:template>
</tt:transform>
when I execute my code
the system dump with this error
ST_MATCH_FAIL
excep.  CX_ST_MATCH_ELEMENT
  TRY.
            CALL TRANSFORMATION ('ZT_NETWORK')
            SOURCE XML lv_xml_data_string
            RESULT  network = l_network
                    operazione = l_operazione
                    root = it_data_tmp.
          CATCH cx_sy_conversion_data_loss .
          CATCH cx_xslt_exception INTO xslt_error.
            xslt_message = xslt_error->get_text( ).
            WRITE:/ xslt_message .
        ENDTRY.
Any help?
thanks
enzo

Enzo Porcasi wrote:
> I have a problem with a transformation from xml to abap. My XML file (taken from a pdf file) is
>
<?xml version="1.0" encoding="iso-8859-1" ?>
>  <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
>  <asx:values>
Your XML is strange, it looks like a mix of pdf form content (xfa) and identity transformation (asx).
Could you explain more ?
Anyway, I tried to find out the errors (not only cx_st_match_element, that was just a catch missing), it works with the following program. Here are the main issues I have found :
- always catch exception class cx_st_error when you use simple transformations (it contains cx_st_match_element and all other simple transformation exceptions)
- xml "asx:abap" and "asx:values" in your input XML are useless, they are only used by identity transformation ("ID"); you may keep them if you want, but I advise you to see why they are in the xml !
- Use same case in your tags (if xml contains  in the transformation so that it corresponds to the input XML
- I renamed all abap names with prefix ABAP_ so that to clearly differentiate xml tags and abap field names (so that it is more easy to understand, for every sdn reader; I hope it will help as I didn't find many threads in the forum).
Simple transformation :
<?sap.transform simple?>
<tt:transform xmlns:tt="http://www.sap.com/transformation-templates">
  <tt:root name="ABAP_NETWORK"></tt:root>
  <tt:root name="ABAP_OPERAZIONE"></tt:root>
  <tt:root name="ABAP_TABELLA"></tt:root>
  <tt:template>
    <ROOT>
      <NETWORK>
        <tt:value ref=".ABAP_NETWORK"></tt:value>
      </NETWORK>
      <OPERAZIONE>
        <tt:value ref=".ABAP_OPERAZIONE"></tt:value>
      </OPERAZIONE>
      <TABELLA>
        <tt:loop ref=".ABAP_TABELLA" name="line">
          <ROW>
            <MANDT>
              <tt:value ref="$line.ABAP_MANDT"></tt:value>
            </MANDT>
            <NETWORK>
              <tt:value ref="$line.ABAP_NETWORK"></tt:value>
            </NETWORK>
            <OPERAZIONE>
              <tt:value ref="$line.ABAP_OPERAZIONE"></tt:value>
            </OPERAZIONE>
            <ID_ACT>
              <tt:value ref="$line.ABAP_ID_ACT"></tt:value>
            </ID_ACT>
            <DESC_ACT>
              <tt:value ref="$line.ABAP_DESC_ACT"></tt:value>
            </DESC_ACT>
            <LONG_TXT>
              <tt:value ref="$line.ABAP_LONG_TXT"></tt:value>
            </LONG_TXT>
            <MAKE_BUY>
              <tt:value ref="$line.ABAP_MAKE_BUY"></tt:value>
            </MAKE_BUY>
            <WP>
              <tt:value ref="$line.ABAP_WP"></tt:value>
            </WP>
            <EVENTO_TECH>
              <tt:value ref="$line.ABAP_EVENTO_TECH"></tt:value>
            </EVENTO_TECH>
            <TIPO_LEGAME>
              <tt:value ref="$line.ABAP_TIPO_LEGAME"></tt:value>
            </TIPO_LEGAME>
            <CONSEGNA>
              <tt:value ref="$line.ABAP_CONSEGNA"></tt:value>
            </CONSEGNA>
          </ROW>
        </tt:loop>
      </TABELLA>
    </ROOT>
  </tt:template>
</tt:transform>
Program and XML included :
REPORT  zsro2.
DATA l_network TYPE string.
DATA l_operazione TYPE string.
DATA : BEGIN OF lt_data_tmp OCCURS 0,
         abap_mandt      TYPE string,
         abap_network    TYPE string,
         abap_operazione TYPE string,
         abap_id_act     TYPE string,
         abap_desc_act   TYPE string,
         abap_long_txt   TYPE string,
         abap_make_buy   TYPE string,
         abap_wp         TYPE string,
         abap_evento_tech TYPE string,
         abap_tipo_legame TYPE string,
         abap_consegna   TYPE string,
       END OF lt_data_tmp.
DATA xslt_error TYPE REF TO cx_xslt_exception.
DATA lo_st_error TYPE REF TO cx_st_error.
DATA lv_xml_data_string TYPE string.
DATA xslt_message TYPE string.
DEFINE conc.
  concatenate lv_xml_data_string &1 into lv_xml_data_string.
END-OF-DEFINITION.
*conc '<?xml version="1.0" encoding="iso-8859-1" ?>'.
*conc '<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">'.
*conc '  <asx:values>'.
conc ' <ROOT>'.
conc '    <NETWORK>E60000000000</NETWORK> '.
conc '    <OPERAZIONE>0010</OPERAZIONE> '.
conc '    <TABELLA>'.
conc '      <ROW xmlns:xfa="http://www.xfa.org/schema/xfa-data/1.0/" xfa:dataNode="dataGroup">'.
conc '        <MANDT>300</MANDT> '.
conc '        <NETWORK>E60000000000</NETWORK> '.
conc '        <OPERAZIONE>0010</OPERAZIONE> '.
conc '        <ID_ACT>1</ID_ACT> '.
conc '        <DESC_ACT>ATTIVITÀ1</DESC_ACT> '.
conc '        <LONG_TXT></LONG_TXT> '.
conc '        <MAKE_BUY></MAKE_BUY> '.
conc '        <WP></WP> '.
conc '        <EVENTO_TECH></EVENTO_TECH> '.
conc '        <TIPO_LEGAME></TIPO_LEGAME> '.
conc '        <CONSEGNA></CONSEGNA> '.
conc '      </ROW>'.
conc '      <ROW xmlns:xfa="http://www.xfa.org/schema/xfa-data/1.0/" xfa:dataNode="dataGroup">'.
conc '        <MANDT>300</MANDT> '.
conc '        <NETWORK>E60000000000</NETWORK> '.
conc '        <OPERAZIONE>0010</OPERAZIONE> '.
conc '        <ID_ACT>2</ID_ACT> '.
conc '        <DESC_ACT>ATTIVITÀ2</DESC_ACT> '.
conc '        <LONG_TXT>ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2 ATTIVITÀ2</LONG_TXT> '.
conc '        <MAKE_BUY>M</MAKE_BUY> '.
conc '        <WP></WP> '.
conc '        <EVENTO_TECH></EVENTO_TECH> '.
conc '        <TIPO_LEGAME></TIPO_LEGAME> '.
conc '        <CONSEGNA></CONSEGNA> '.
conc '      </ROW>'.
conc '    </TABELLA>'.
conc ' </ROOT>'.
*conc '  </asx:values>'.
*conc '</asx:abap>'.
DATA lv_xml_data_string_2 TYPE string.
TRY.
    CALL TRANSFORMATION zsro
          SOURCE
            XML lv_xml_data_string
          RESULT
            abap_network    = l_network
            abap_operazione = l_operazione
            abap_tabella    = lt_data_tmp[].
  CATCH cx_sy_conversion_data_loss .
  CATCH cx_st_error INTO lo_st_error.
    xslt_message = lo_st_error->get_text( ).
    WRITE:/ xslt_message .
  CATCH cx_xslt_exception INTO xslt_error.
    xslt_message = xslt_error->get_text( ).
    WRITE:/ xslt_message .
ENDTRY.
BREAK-POINT.

Similar Messages

  • Simple transformation XML to ABAP, runtime error: CX_ST_REF_ACCESS

    Hi, all experts,
    I got a runtime error CX_ST_REF_ACCESS, while I tried to use Simple Transformation to transfer XML-String to ABAP internal table.
    Can anybody help me to fix the problem? Thanks very much. It's urgent.
    The code of transformation like this:
    <tt:root name="DATA"/>
      <tt:template>
        <node>
          <tt:deserialize>
            <tt:loop ref=".DATA" name="mdr_data">
              <tt:attribute name="type">
                <tt:value ref="$mdr_data.lf_type"/>
              </tt:attribute>
              <tt:attribute name="objid">
                <tt:value ref="$mdr_data.lf_objid"/>
              </tt:attribute>
              <tt:attribute name="name" value-ref="$mdr_data.lf_name"/>
              <tt:attribute name="short" value-ref="$mdr_data.lf_short"/>
            </tt:loop>
          </tt:deserialize>
        </node>
      </tt:template>
    The Data-structure in my Report:
    DATA: BEGIN OF ls_mdr_data,
            lf_type TYPE /ehr/ct_dt_bo_type,
            lf_objid TYPE realo,
            lf_name TYPE stext,
            lf_short TYPE short_d,
          END OF ls_mdr_data,
         lt_result_data like TABLE OF ls_mdr_data.
    If I call the transformation use the XML-String like:
    <node type="MDRFOLDER" objid="50016122" name="MDR Root Folder" short="MDR Root"/>
    I got the  error  CX_ST_REF_ACCESS:
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_ST_REF_ACCESS', was not  caught and
        therefore caused a runtime error.
        The reason for the exception is:
        The goal was to access variable "LF_TYPE". However, this access was not
        possible.

    Hi, all experts,
    I got a runtime error CX_ST_REF_ACCESS, while I tried to use Simple Transformation to transfer XML-String to ABAP internal table.
    Can anybody help me to fix the problem? Thanks very much. It's urgent.
    The code of transformation like this:
    <tt:root name="DATA"/>
      <tt:template>
        <node>
          <tt:deserialize>
            <tt:loop ref=".DATA" name="mdr_data">
              <tt:attribute name="type">
                <tt:value ref="$mdr_data.lf_type"/>
              </tt:attribute>
              <tt:attribute name="objid">
                <tt:value ref="$mdr_data.lf_objid"/>
              </tt:attribute>
              <tt:attribute name="name" value-ref="$mdr_data.lf_name"/>
              <tt:attribute name="short" value-ref="$mdr_data.lf_short"/>
            </tt:loop>
          </tt:deserialize>
        </node>
      </tt:template>
    The Data-structure in my Report:
    DATA: BEGIN OF ls_mdr_data,
            lf_type TYPE /ehr/ct_dt_bo_type,
            lf_objid TYPE realo,
            lf_name TYPE stext,
            lf_short TYPE short_d,
          END OF ls_mdr_data,
         lt_result_data like TABLE OF ls_mdr_data.
    If I call the transformation use the XML-String like:
    <node type="MDRFOLDER" objid="50016122" name="MDR Root Folder" short="MDR Root"/>
    I got the  error  CX_ST_REF_ACCESS:
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_ST_REF_ACCESS', was not  caught and
        therefore caused a runtime error.
        The reason for the exception is:
        The goal was to access variable "LF_TYPE". However, this access was not
        possible.

  • Simple Transformation XML to ABAP Content of tag with subtrees to string field

    Hi,
    I have an  requirement in which I have to do a transformation from an XML file to an structure.
    I need get the value of a tag that have subtrees and move that to a field in my structure.
    Example:
    <TAG1>value1</TAG1>
    <TAG2>value2</TAG2>
    <TAG3>
         <TAG4>value4</TAG4>
         <TAG5>value5</TAG5>
    </TAG3>
    Result expected in ABAP Structure:
    field1 -> tag1
    field2 -> tag2
    field3 -> <TAG4>value4</TAG4><TAG5>value5</TAG5>
    The contents of the tag TAG3 is variable, so I want to store it as a string.
    Can I make this with Simple Transformation?
    In my tests I can move only the value of each child tag for the given field structure.
    This syntax dont work:
    <TAG3 tt:value-ref="STRUCTURE.FIELD3"/>
    Thanks and Regards,
    Miguel Motta

    Hi Miguel
    Have a look at below snippets. Here I have tried to escape the text inside TAG3 so that it gets treated as single node during transformation.
    ABAP code
    DATA: BEGIN OF result,
            col1 TYPE string,
            col2 TYPE string,
            col3 TYPE string,
          END OF result.
    DATA: xml_string TYPE string VALUE
    '<ROOT> <TAG1>value1</TAG1> <TAG2>value2</TAG2> <TAG3> <TAG4>value4</TAG4> <TAG5>value5</TAG5> </TAG3> </ROOT>',
          part1 TYPE string,
          part2 TYPE string,
          part3 TYPE string.
    *   Escape the text inside TAG3 tag
    FIND REGEX '(.*<TAG3>)(.*)(</TAG3>.*)' IN xml_string SUBMATCHES part1 part2 part3.
    IF sy-subrc EQ 0.
      part2 = escape( val = part2 format = cl_abap_format=>e_xml_text ).
    *      REPLACE ALL OCCURRENCES OF '<' IN part2 WITH '&lt;'.
    *      REPLACE ALL OCCURRENCES OF '>' IN part2 WITH '&gt;'.
      xml_string = part1 && part2 && part3.
    ENDIF.
    TRY.
    * Display xml
        cl_abap_browser=>show_xml( EXPORTING xml_string = xml_string ).
    * Deserialization
        CALL TRANSFORMATION zmtest
          SOURCE XML xml_string
          RESULT para = result.
    * Check result
        WRITE:/ 'COL1=', result-col1,
              / 'COL2=', result-col2,
              / 'COL3=', result-col3.
      CATCH cx_st_error.
    * Error handling
        MESSAGE 'Error in Simple Transformation'
                TYPE 'I' DISPLAY LIKE 'E'.
    ENDTRY.
    Transformation code
    <?sap.transform simple?>
    <tt:transform xmlns:tt="http://www.sap.com/transformation-templates" template="temp" version="0.1">
       <tt:root name="PARA"/>
       <tt:template name="temp">
         <ROOT>
           <TAG1>
             <tt:value ref="PARA.COL1"/>
           </TAG1>
           <TAG2>
             <tt:value ref="PARA.COL2"/>
           </TAG2>
           <TAG3>
             <tt:value ref="PARA.COL3"/>
           </TAG3>
         </ROOT>
       </tt:template>
    </tt:transform>

  • Simple Transformation - XML to Internal Table Error

    I have a webservice call that returns XML.  I need to transform a portion of the response to an internal table, but my simple transformation is not working with loop processing.  I have read through most posts regarding the topic but they're either too old or related to serialization.  There aren't any exceptions thrown, but I don't get any data in the internal table (PAPERWORK root).  Below are some code snippets.  Any ideas on the problem with the XSLT template?  Thanks.
    Sample XML:
    <?xml version="1.0" encoding="utf-8" ?>
    <PrintVersionDataSet>
    <Result>
    <ReturnCode>W</ReturnCode>
    <ReturnMessage>There are reports with later version(s)</ReturnMessage>
    </Result>
    <Paperwork>
    <ReportCode>CVR</ReportCode>
    <ReportName>Cover Sheet</ReportName>
    <Version>2</Version>
    <PrintedDateTime>2009-05-01T09:54:04.1-05:00</PrintedDateTime>
    </Paperwork>
    <Paperwork>
    <ReportCode>SPS</ReportCode>
    <ReportName>Sponsor Summary</ReportName>
    <Version>2</Version>
    <PrintedDateTime>2009-05-01T09:54:04.99-05:00</PrintedDateTime>
    </Paperwork>
    </PrintVersionDataSet>
    XSLT Code:
    <?sap.transform simple?>
    <tt:transform xmlns:tt="http://www.sap.com/transformation-templates">
      <tt:root name="RESULT"/>
      <tt:root name="PAPERWORK"/>
      <tt:template>
        <PrintVersionDataSet>
          <Result tt:ref="RESULT">
            <ReturnCode>
              <tt:value ref="RETURNCODE"/>
            </ReturnCode>
            <ReturnMessage>
              <tt:value ref="RETURNMESSAGE"/>
            </ReturnMessage>
          </Result>
          <tt:deserialize>
            <tt:loop ref=".PAPERWORK">
              <Paperwork>
                <ReportCode>
                  <tt:value ref="REPORTCODE"/>
                </ReportCode>
                <ReportName>
                  <tt:value ref="REPORTNAME"/>
                </ReportName>
                <Version>
                  <tt:value ref="VERSION"/>
                </Version>
                <PrintedDateTime>
                  <tt:value ref="PRINTEDDATETIME"/>
                </PrintedDateTime>
              </Paperwork>
            </tt:loop>
          </tt:deserialize>
        </PrintVersionDataSet>
      </tt:template>
    </tt:transform>
    ABAP Call to Transform Data:
    TRY.
    CALL TRANSFORMATION Z_GA_PAPERWORK_VERS_WEBSVC
          SOURCE XML LS_RESPONSE-VERIFY_PRINT_VERSION_RESULT
          RESULT RESULT     = LS_RESULT
                 PAPERWORK  = LT_PAPERWORK.
        CATCH CX_ROOT INTO ROOT_EXCEPTION.
          CALL METHOD ROOT_EXCEPTION->IF_MESSAGE~GET_TEXT
            RECEIVING
              RESULT = LV_MESSAGE.
      ENDTRY.

    Upon further inspection and testing with a simple file and program, I can see that the XML structure isn't quite correct for the loop process.  There needs to be a single <PAPERWORK> node, instead of one for each table line in the file.  This should allow the loop to execute properly after a slight adjustment to the XSLT template.

  • Standard Transformation XML to ABAP

    Is there a sense to read bigger xml with standard transformations into an internal table?
    Or is it at least to restrictive?
    I can't find a real good documentation of it. Also I can't find out which way is the best to get my xml into a table.
    Can somebody give me a hint?
    Edited by: Rob Burbank on Feb 2, 2010 3:04 PM

    Does somebody know:
    I have 3 Elements in my XML.
    In Standard Transformation I know only the first element.
    The problem is, that the standard transformation does not ignore the other 2.
    <X>
    </A>
    </B>
    </C>
    </X>
    I get an Exception that a closing Tag for X is expected after processing A.
    Is there a way to make the standard transformation less sensitive?

  • Error in Simple transformation

    Hi Guys,
    I am very new to Simple transformation,there is an error in my ST,but I have no idea how to fix it,Please take a look at my simple transformation file.Thanks.
    I want to deseralize the XML file to ABAp Structure
    my xml file is like:
    <Content>
        <BookEntity  name="A">
            <Id>01</id>
            <Title>My Book A</Title>
        </BookEntity>
        <BookEntity  name="B">
            <Id>02</id>
            <Title>My Book B</Title>
            <Author>Jamy</Author>
        </BookEntity>
        <BookEntity  name="C">
            <Id>03</id>
            <Author>L</Author>
            <Year>2007</Year>
            <Group>C</Group>
        </BookEntity>
    </Content>
    my structure likes:
    DATA: BEGIN OF content,
            BEGIN OF bookentity,
              name    TYPE string,
              id      TYPE string,
              title   TYPE string,
              author             TYPE string,
              year       TYPE string,
              group    TYPE string,
            END OF contextentity,
          END OF content.
    <?sap.transform simple?>
    <tt:transform xmlns:tt="http://www.sap.com/transformation-templates">
    <tt:root name="ROOT" />
    <tt:template>
      <Content>
          <tt:loop ref=".ROOT" name="content" >
            <BookEntity tt:ref="bookentity">
                <tt:attribute name="name" value-ref="name" />
                   <tt:apply name="SUB">
                  <b>   <tt:with-parameter name="NAME" ref="name"/></b>  <--Error here
                   </tt:apply>
            </ContextEntity>
          </tt:loop>
         </Content>
      </tt:template>
    <tt:template name="SUB">
           <tt:context>
                <tt:parameter name="NAME"/>
           </tt:context>
                <tt:switch-var>
                <tt:cond-var check="NAME='A'">
                    <Id>
                      <tt:value ref="id"/>
                    </Id>
                    <Title>
                      <tt:value ref="title"/>
                    </Title>
                </tt:cond-var>
                <tt:cond-var check="NAME='B'">             
                    <Id>
                      <tt:value ref="id"/>
                    </Id>
                    <Title>
                      <tt:value ref="title"/>
                    </Title>
                    <Author>
           <tt:value ref="author"/>
                     </Author>
                </tt:cond-var>
                <tt:cond-var check="NAME='C'">            
                    <Id>
                      <tt:value ref="id"/>
                    </Id>
                    <Author>
                      <tt:value ref="author"/>
                    </Author>
                    <Year>
                      <tt:value ref="year"/>
                    </Year>
                    <Group>
                      <tt:value ref="group"/>
                    </Group>
                </tt:cond-var>
                </tt:switch-var>
    </tt:template>
    </tt:transform>

    Check the flag "use SAP XML toolkit" for the operation mapping and try, if that works then.
    Check the flag for all XSLT and Java mappings which is migrated from PI 7.0

  • Optional attributes in XML to ABAP transformation

    Hi,
    I have to deserialize (transformation xml to abap) an xml input file.
    I want to use SAP ST (Simple Transformations).
    This xml format is using attributes
    Such attributes can be transformed in ST with
    <tt:attribute name="item_id" value-ref="MATNR"/>
    I realized 2 problems:
    1. If the xml file does not contain every attribute which is in the transformation.
    This can be solved by tt:cond
    Sample
              <tt:cond>
                <tt:attribute name="uom" value-ref="BASE_UOM"/>
              </tt:cond>
    Now attribute uom is optional. Without the tt:cond the ST prragrom would throw exception if it is not in the file.
    2. If the xml file contains an attribute which is not used in the transformation.
    I tried to use tt:skip but it is not working for "<tt:attribute name= ... value-ref=... name" but only for "<tt:value-ref=...".
    I only want to get the values I need out of the parameter list.
    How can I achieve this without defining a transformation for every parameter in the xml file?
    Thanks and regards
    Michael

    Hi,
    thanks for reply. It took me into the right direction. You have to distinguish between elements (ordered structured nodes) and attributes (unordered structured nodes). In my case they are using attributes for the values of a material master.
    Here is a snippet (sample of the XML):
    <?xml version="1.0" encoding="utf-8"?>
    <TcPLMXML>
      <TCifEngPart item_id="1-3000-3630-00"
                   seMaterialType="HALB"
                   uom="ST"
                   seWeight="2000.0" seWeightUnit="KG">
      </TCifEngPart>
      <TCifEngPart item_id="1-30000-41002-00"
                   seMaterialType="HALB"
                   uom="ST"
      </TCifEngPart>
    </TcPLMXML>
    and my transformation:
          <tt:loop ref="MATERIAL_LIST">
            <TCifEngPart>
              <tt:attribute name="item_id" value-ref="MATNR"/>
              <tt:attribute name="object_name" value-ref="MATL_DESC"/>
              <tt:attribute name="seMaterialType" value-ref="MATL_TYPE"/>
              <tt:attribute name="uom" value-ref="BASE_UOM"/>
              <tt:cond>
                 <tt:attribute name="seLength" value-ref="LENGTH"/>
                 <tt:attribute name="seWidth" value-ref="WIDTH"/>
                 <tt:attribute name="seHeight" value-ref="HEIGHT"/>
              </tt:cond>
              <tt:skip>
                 <tt:attribute name="seWeight" />
                 <tt:attribute name="seVolume" />
              </tt:skip>
            </TCifEngPart>
          </tt:loop>
    Length, width and hight are optional in the XML and will be transferred to the corresponding SAP fields if they are in the input file Weight and volume will be ignored.
    This means all attributes I don't need I have to put within the tt:skip.
    Without this skip the transformation throws an error.
    In consequence if the partner system add new attributes I have to enhance the transformation in SAP.
    Is there any other way?

  • Simple transformation formatting

    Dear Expert,
    I would like to know how can I format my transformation result using simple transformation. I have an attribute that is supposed to display a date in the format YYYYMMDD. However, the default format is YYYY-MM-DD. How can I change this behavior in simple transformation? Thanks!
    Regards,
    Alex

    Hey Alex,
    do you have a solution already? I have the same problem, the format of the date in the XML-File is "20140101" and I can´t transform it with Simple Transformation to the ABAP Type DATS which waits for "2014-01-01" or "2014.01.01".
    the Transformation looks like this in the moment:
    <DATE tt:value-ref="DATE"/>
    The ABAP type of the field DATE is DATS. And the XML looks at this part like this:
    <DATE>20131201</DATE>
    Regards,
    Christoph

  • PARSE_APPLICATION_DATA Error during XML = ABAP conversion: Response Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SAS0446CC11CC6EC1AD4789 Line 24 An error occurred when deserializing in the simple transformation program /1SAI/SAS0446CC11CC6EC1AD4789

    Hi Experts ,
    i have a scenario proxy to soap  where i am getting error while getting the response .
    we are sending the request successfully and getting response .some times we are getting in proxy level error below
    PARSE_APPLICATION_DATA Error during XML => ABAP conversion: Response Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SAS0446CC11CC6EC1AD4789 Line 24 An error occurred when deserializing in the simple transformation program /1SAI/SAS0446CC11CC6EC1AD4789 (Cha
    Please help us to fix this bug in proxy response.
    Regards
    Ravi

    Hello Ravinder,
    Can you please post the complete stack trace, it seems to be some fields are getting truncated i,e data sent from the program to the proxy object might be violating some length restrictions.
    Please check your message interface field lengths and what is being passed to the proxy.
    Regards,
    Ravi.

  • Simple Transformation to deserialize an XML file into ABAP data structures?

    I'm attempting to write my first simple transformation to deserialize
    an XML file into ABAP data structures and I have a few questions.
    My simple transformation contains code like the following
    <tt:transform xmlns:tt="http://www.sap.com/transformation-templates"
                  xmlns:pp="http://www.sap.com/abapxml/types/defined" >
    <tt:type name="REPORT" line-type="?">
      <tt:node name="COMPANY_ID" type="C" length="10" />
      <tt:node name="JOB_ID" type="C" length="20" />
      <tt:node name="TYPE_CSV" type="C" length="1" />
      <tt:node name="TYPE_XLS" type="C" length="1" />
      <tt:node name="TYPE_PDF" type="C" length="1" />
      <tt:node name="IS_NEW" type="C" length="1" />
    </tt:type>
    <tt:root name="ROOT2" type="pp:REPORT" />
        <QueryResponse>
        <tt:loop ref="ROOT2" name="line">
          <QueryResponseRow>
            <CompanyID>
              <tt:value ref="$line.COMPANY_ID" />
            </CompanyID>
            <JobID>
              <tt:value ref="$line.JOB_ID" />
            </JobID>
            <ExportTypes>
              <tt:loop>
                <ExportType>
                   I don't know what to do here (see item 3, below)
                </ExportType>
              </tt:loop>
            </ExportTypes>
            <IsNew>
              <tt:value ref="$line.IS_NEW"
              map="val(' ') = xml('false'), val('X') = xml('true')" />
            </IsNew>
          </QueryResponseRow>
          </tt:loop>
        </QueryResponse>
        </tt:loop>
    1. In a DTD, an element can be designated as occurring zero or one
    time, zero or more times, or one or more times. How do I write the
    simple transformation to accommodate these possibilities?
    2. In trying to accommodate the "zero or more times" case, I am trying
    to use the <tt:loop> instruction. It occurs several layers deep in the
    XML hierarchy, but at the top level of the ABAP table. The internal
    table has a structure defined in the ABAP program, not in the data
    dictionary. In the simple transformation, I used <tt:type> and
    <tt:node> to define the structure of the internal table and then
    tried to use <tt:loop ref="ROOT2" name="line"> around the subtree that
    can occur zero or more times. But every variation I try seems to get
    different errors. Can anyone supply a working example of this?
    3. Among the fields in the internal table, I've defined three
    one-character fields named TYPE_CSV, TYPE_XLS, and TYPE_PDF. In the
    XML file, I expect zero to three elements of the form
    <ExportType exporttype='csv' />
    <ExportType exporttype='xls' />
    <ExportType exporttype='pdf' />
    I want to set field TYPE_CSV = 'X' if I find an ExportType element
    with its exporttype attribute set to 'csv'. I want to set field
    TYPE_XLS = 'X' if I find an ExportType element with its exporttype
    attribute set to 'xls'. I want to set field TYPE_PDF = 'X' if I find
    an ExportType element with its exporttype attribute set to 'pdf'. How
    can I do that?
    4. For an element that has a value like
    <ErrorCode>123</ErrorCode>
    in the simple transformation, the sequence
    <ErrorCode>  <tt:value ref="ROOT1.CODE" />  </ErrorCode>
    seems to work just fine.
    I have other situations where the XML reads
    <IsNew value='true' />
    I wanted to write
    <IsNew>
            <tt:value ref="$line.IS_NEW"
            map="val(' ') = xml('false'), val('X') = xml('true')" />
           </IsNew>
    but I'm afraid that the <tt:value> fails to deal with the fact that in
    the XML file the value is being passed as the value of an attribute
    (named "value"), rather than the value of the element itself. How do
    you handle this?

    Try this code below:
    data  l_xml_table2  type table of xml_line with header line.
    W_filename - This is a Path.
      if w_filename(02) = '
        open dataset w_filename for output in binary mode.
        if sy-subrc = 0.
          l_xml_table2[] = l_xml_table[].
          loop at l_xml_table2.
            transfer l_xml_table2 to w_filename.
          endloop.
        endif.
        close dataset w_filename.
      else.
        call method cl_gui_frontend_services=>gui_download
          exporting
            bin_filesize = l_xml_size
            filename     = w_filename
            filetype     = 'BIN'
          changing
            data_tab     = l_xml_table
          exceptions
            others       = 24.
        if sy-subrc <> 0.
          message id sy-msgid type sy-msgty number sy-msgno
                     with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        endif.

  • Simple Transformation from ABAP to XML and back

    Hi experts,
    Can anyone provide me a simple example of a 'simple transformation' that will convert and internal table with more than one column into XML via a simple transformation.
    I've spend days now reading SAP help and e-learning examples, but this just won't work and I am getting short dumps saying 'The goal was to access variable "ROOT". However, this access was notv possible.'
    Here is my ABAP:
    data: begin of struc,
               counter type i,
               aname type string,
               aname2 type string,
          end of struc.
    data: cnt_c type c.
    data: itab like table of struc with HEADER LINE,
          xml_string type xstring.
    do 3 times.
         move sy-index to: itab-counter, cnt_c.
         concatenate 'nameA' cnt_c into itab-aname.
         concatenate 'nameB' cnt_c into itab-aname2.
         append itab.
    enddo.
    CALL TRANSFORMATION Z_ST_TEST5
           SOURCE  ROOT = itab
           RESULT XML xml_string.
    CALL FUNCTION 'DISPLAY_XML_STRING'
      EXPORTING
        XML_STRING            = xml_string.
    skip 1.
    and here is my ST:
    <?sap.transform simple?>
    <tt:transform xmlns:tt="http://www.sap.com/transformation-templates">
      <tt:root name="ROOT"/>
        <tt:template>
         <TABLE>
          <tt:loop ref=".ROOT" name="line">
            <ITEM>
              <counter>
                <tt:value ref="$line.aname" />
              </counter>
              <name>
                <tt:value ref="$line.aname" />
              </name>
              <name2>
                <tt:value ref="$line.aname2" />
              </name2>
            </ITEM>
          </tt:loop>
         </TABLE>
        </tt:template>
    </tt:transform>

    Figured it out. The interla tables used in teh call transformation statement can never have a header line.

  • ABAP Simple Transformation - How to save XML to file with CL_FX_WRITER?

    Hello!
    When calling a Simple Transformation program for transformation from ABAP to XML, it is possible to specify RESULT XML rxml as a class reference variable of type CL_FX_WRITER, which points to an XML writer.
    How to handle CL_FX_WRITER in order to save XML to a file?
    Thanks and regards,
    Andrey

    Hallo Rainer!
    Many thanks. I have checked the profile parameter ztta/max_memreq_MB and it is set to 2048 MB in the development system. I hope, that won't be less on the client's machine. The only thing I did not clearly explained, is that I need to write XML data to the server. I am so sorry. Downloading to the local PC is very helpful for me also, but only for the test purposes.
    Regards,
    Andrey

  • Help with ABAP Structure to XML - Simple Transformation

    Hi guys,
    I need help with a Simple Transformation. I am trying to convert a structure in ABAP to XML String but i ma getting short dumps...
    Can any of you help.
    Thanks in advance.
    *& Report  ZTESTXML
    REPORT  ZTESTXML.
    class demo DEFINITION.
       PUBLIC SECTION.
       CLASS-METHODS main.
       ENDCLASS.
       CLASS demo IMPLEMENTATION.
         method main.
           data : begin of account,
                    partner type bu_partner,
                    primary(1),
                    update(3),
                    email(50),
                    memberid(4),
                    telephone(12),
                    fax(10),
                    dept(20),
                    end of account.
            data : xmlstr type xstring.
                    account-partner = '12345'.
                    account-primary = 'N'.
                    account-update = 'Yes'.
                    account-email = 'zz at hotmail.com'.
                    account-memberid = '555'.
                    account-telephone = '123-448-6710'.
                    account-fax = '345-123-7899'.
                    account-dept = 'Info Systems'.
                    call TRANSFORMATION ztest_inttable
                                        SOURCE account = 'account'
                                        result XML xmlstr.
           call FUNCTION 'DISPLAY_XML_STRING'
               EXPORTING xml_string = xmlstr.
           ENDMETHOD.
           ENDCLASS.
           start-of-SELECTION.
             demo=>main( ).
    Transformation
    <?sap.transform simple?>
    <tt:transform xmlns:tt="http://www.sap.com/transformation-templates">
      <tt:root name="account"/>
      <tt:template>
        <IGT_CRM_AccountInfo>
          <Account>
            <tt:ref name=".account">
              <tt:attribute name="Id" value-ref="PARTNER"/>
              <tt:attribute name="Primary" value-ref="primary"/>
              <tt:attribute name="Update" value-ref="update"/>
              <Contact>
                <tt:attribute name="EMail" value-ref="email"/>
                <tt:attribute name="Member Id" value-ref="memberid"/>
              </Contact>
              <Communications>
                <tt:attribute name="Telephone" value-ref="telephone"/>
                <tt:attribute name="Fax" value-ref="fax"/>
              </Communications>
              <IGT>
                <tt:attribute name="Department" value-ref="dept"/>
              </IGT>
            </tt:ref>
          </Account>
        </IGT_CRM_AccountInfo>
      </tt:template>
    </tt:transform>
    Dump message
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_ST_REF_ACCESS', was not caught in
    procedure "MAIN" "(METHOD)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    The goal was to access variable "PARTNER". However, this access was not
    possible.

    to convert abap itab or variable into xml string use ABAP key word call transformation.
    call transformation (`ID`)
                source output = itab[]
                result xml xml_out.
    where itab is your internal table or any abap variable.
    xml_out is type string which will hold the resulting xml.
    ID is the transformation program. if you wanto use your own transformation, use your XSLT or ST program there.
    Raja

  • Simple transformation error in converting XML to internal table

    Hi Team,
    I have an issue, its working in Dev, QA, and Prod in PI 7.0, once we upgrade it to PI 7.1 I'm getting the  below mention error,   
    Unknown Simple transformation error in converting XML to internal table
    Application error in mapping program ZF_INT006_FILE_TO_SAP_FILE, error code: , error text: Unknown Simple transformation error in converting XML to internal table An exception has occurred.
    Can any one suggest related notes are suggestion.
    appericate in advance for the solutions which you all provide me
    Thank you
    Venkat Anil

    Check the flag "use SAP XML toolkit" for the operation mapping and try, if that works then.
    Check the flag for all XSLT and Java mappings which is migrated from PI 7.0

  • ABAP to XML File (Simple Transformation)

    Hi guys,
    this is my first question here and if I do something wrong please tell me about it.
    I created my own simple transformation which I use in my program:
    CALL TRANSFORMATION ZST_MAGAZYN_BB
         SOURCE lt_magazyn_rh = lt_magazyn_rh[]
                lt_mag_hdr = lt_mag_hdr[]
                lt_mag_hdr2 = lt_mag_hdr2[]
         RESULT XML xml_string.
    Then I tried to use GUI_DOWNLOAD on "xml_string" but there is no content in output xml file (but file's size is not 0kb):
    DATA:  xml_table TYPE STANDARD TABLE OF string.
    APPEND xml_string TO xml_table.
    CALL FUNCTION 'GUI_DOWNLOAD'
       EXPORTING
         filename = 'C:\rh.xml'
       TABLES
         data_tab = xml_table.
    I would really appreciate your help.

    Try to change the path where you're saving the file.
    I had the same problem once, it was authorization. I couldn't save in C:\ root.
    Change filename = 'C:\rh.xml'   to    filename = 'C:\TEMP\rh.xml'.
    Or try any other path, but C:\

Maybe you are looking for

  • Error 150.30 with Photoshop Elements

    My Windows 7 PC died, and I've transferred photographs to my old Dell XP machine.  When I execute Elements, I get the error 150.30 message asking me to restart the maching.  I did that, but still get the error when executing Adobe.

  • Would a Mac-ready GPU work in a PC?

    I've been doing a lot of reading on getting the right graphics card for my set up and I can't get a fix on this question: Could I use a Mac-ready GPU in a PC?  (And if so, are any mods necessary?) I have a Mid-2010 Mac Pro (8-core) that currently has

  • RS232 Input and Output in the same time

    Hello I have problem with rs232.  I read information from my power supply by RS232 Input:  Expected string: 1923456789<CR>OK<CR> Channel 0  Measurement data request: GETD00\r  Measurement data format: 4a Channel 1  Measurement data request: (empty)  

  • I don't want to use the beta

    Is there any way to use the stable version of pages on icloud.com? I can't share Documents with people who don't use the beta right? Regards David

  • IMessage says the volume is full

    Ihr Volume ist nahezu voll, wodurch eingehende Nachrichten u. U. verloren gehen. What does this new message mean, it pops up with every new iMessage I receive ...