Community
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Strans XSLT-Programm Conversion error

Go to solution
mt13065
Explorer

on ‎2019 Mar 11 6:22 AM

0 Likes
1,879

I often use strans for XML->ABAP TABLE conversion, but I have encountered the following problem. The correct result should be that there is only one row of data in the ''GT_ORDER-PART'' of each row, but now he has two rows, he has read all the The data in "part", how can I make him correspond to ORDER?

Know the answer?

Help others by sharing your knowledge.

Answer

Need more details?

Request clarification before answering.

Show replies
Show replies
Sandra_Rossi
Active Contributor
‎2019 Mar 11 6:47 AM
0 Likes

Please post the code as text instead of image, so that we can easily answer by modifying portions of your code.

mt13065
Explorer
‎2019 Mar 11 7:19 AM
0 Likes

it's my strans code, I think it should be something wrong,hope someone can help me, best regards, T^T

Sandra_Rossi
Active Contributor
‎2019 Mar 11 7:27 AM
0 Likes

Thank you.

Note: you'd better correcting your original question rather than adding text.

If you want to reply to someone to add complements, please use the COMMENT button. ANSWER is only to propose a solution. If it's too late, you still have an option to convert your answer into a comment.

mt13065
Explorer
‎2019 Mar 11 7:33 AM 
<xsl:transform version="1.0"
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  xmlns:sap="http://www.sap.com/sapxsl"
>


<xsl:strip-space elements="*"/>


<xsl:template match="/">
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
    <asx:values>
        <ORDERS>
            <xsl:for-each select="/Orders/Order">
            <xsl:variable name="var1" select="/Orders/Order"/>
            <HEAD>
                <NAME>
                    <xsl:value-of select="Name"/>
                </NAME>
                <STRATEGY>
                    <xsl:value-of select="Strategy"/>
                </STRATEGY>
                <STARTDATE>
                    <xsl:value-of select="StartDate"/>
                </STARTDATE>
                <PART>
                    <xsl:for-each select="$var1/Parts/Part">
                       <ITEM>
                            <NAME>
                                <xsl:value-of select="Name"/>
                            </NAME>
                            <MEASURE>
                                <xsl:value-of select="Measure"/>
                            </MEASURE>
                        </ITEM>
                    </xsl:for-each>
                </PART>
            </HEAD>
            </xsl:for-each>
        </ORDERS>
    </asx:values>
</asx:abap>
</xsl:template>


</xsl:transform>

-------------------------------------my strans code↑

<Orders>
        <Order>
          <Name>Bend_001_10</Name>
          <Strategy>MaterialAdministrationOrder</Strategy>
          <StartDate>2018-07-13T08:00:00</StartDate>
          <TargetDate>2018-08-02T16:00:00</TargetDate>
          <Parts>
            <Part>
              <Name>B010_110_011V3</Name>
              <Measure>Metric</Measure>
            </Part>
          </Parts>
        </Order>
        <Order>
          <Age>2</Age>
          <Name>Zusammenbau Teil</Name>
          <Strategy>MaterialAdministrationOrder</Strategy>
          <StartDate>2018-07-13T08:00:00</StartDate>
          <Parts>
            <Part>
              <Name>Imported1</Name>
              <Measure>Metric</Measure>
            </Part>
          </Parts>
        </Order>
      </Orders>
-----------------------------------------my xml code↑
best regards.
View Entire Topic
Sandra_Rossi
Active Contributor
‎2019 Mar 11 7:47 AM
0 Likes

XSLT refers to nodes by using the XPATH language, which use absolute (start with / like in your example /OrdersOrder) or paths relative to the "context node" (not starting with /, like Parts/Part as I show below). The context node is changed by XSLT at runtime, for example for-each sets the context node to the currently-iterated node.

I think that should work:

            <xsl:for-each select="/Orders/Order">
                ...
                    <xsl:for-each select="Parts/Part">

Note: $var1/Parts/Part is equivalent to /Orders/Order/Parts/Part which starts from the root and parses all nodes matching that path.

Show replies
Show replies
mt13065
Explorer
‎2019 Mar 11 7:53 AM

oh my god,i'm so stupid,I tried /Parts/Part, but I didn't try what you said,thank you so much.

Sandra_Rossi
Active Contributor
‎2019 Mar 11 8:08 AM

By the way, you should better switch to the Simple Transformation language (provided that the transformations remain simple), because it's something like 10 times faster.

mt13065
Explorer
‎2019 Mar 11 8:33 AM
0 Likes

i will, but simple need create all fields in se11 ,If I am not mistaken.
but I am worried that the customer will add the fields that need to be read later. I am preparing to create a simple strans,thank you again.^_^

Sandra_Rossi
Active Contributor
‎2019 Mar 11 9:58 AM
0 Likes

A Simple Transformation may work without any reference to the DDIC i.e. the type of the data root is optional, in that case it's considered of type "any" and it will check the ABAP names when the transformation runs.

Ask a Question