<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: logic for displaying nested nodes. in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-displaying-nested-nodes/m-p/8199779#M1626164</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Same remark as Florian &lt;SPAN __jive_emoticon_name="wink"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Moreover, could you tell us which technology (class, function module, other...) you used for your hierarchical report?&lt;/P&gt;&lt;P&gt;And if you can paste your code of the tree building (please we're not interested in the CHVW part, which is not the issue), that would be fine too!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sandra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 05 Sep 2011 14:11:56 GMT</pubDate>
    <dc:creator>Sandra_Rossi</dc:creator>
    <dc:date>2011-09-05T14:11:56Z</dc:date>
    <item>
      <title>logic for displaying nested nodes.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-displaying-nested-nodes/m-p/8199774#M1626159</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;helo all &lt;/P&gt;&lt;P&gt;i have to display a report in a heirarchical tree structure . I am able to display the report in heirarchical format . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following is my requirement . I'm able to do it for 2 nodes . but how to build the nodes for the below requirement .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Step 1 : Once User enters DB, Go to CHVW  with No Receipt Indicator as Space and CHARG as DB # Entered on screen(Parent Node)&lt;/P&gt;&lt;P&gt;Step2: Check the Movement indicator if it is u2018Bu2019 then itu2019s a Raw material No further Drill Down (Last Node), If It is u2018Fu2019 then Go to Step 3.&lt;/P&gt;&lt;P&gt;Step 3: Get all the Unique DB # and Corresponding Orders, Display only DB# on Output (Child Nodes)&lt;/P&gt;&lt;P&gt;OUTPUT - ALV TREE STRUCTURE&lt;/P&gt;&lt;P&gt;If User Clicks on any DB# (Child Node):&lt;/P&gt;&lt;P&gt;      Then DB# Selected Will Become a Parent Node, Repeat the Same Process from 1 to 3. &lt;/P&gt;&lt;P&gt;Table: CHVW                                                                                DB#  Order   DB#  Order&lt;/P&gt;&lt;P&gt;Tree   &lt;/P&gt;&lt;P&gt; DB1&lt;/P&gt;&lt;P&gt;-	 DB1.1&lt;/P&gt;&lt;P&gt;   -     DB1.1.1&lt;/P&gt;&lt;P&gt;   -     DB1.1.2&lt;/P&gt;&lt;P&gt;   -     DB1.1.3&lt;/P&gt;&lt;P&gt;            -   DB1.1.3.1                               -&lt;/P&gt;&lt;HR originaltext="----" /&gt;&lt;P&gt; DB # of Raw material No further drill Down&lt;/P&gt;&lt;P&gt;                  -  Material Document          -&lt;/P&gt;&lt;HR originaltext="----" /&gt;&lt;P&gt; Display Material Doc #&lt;/P&gt;&lt;P&gt;    -      DB1.2&lt;/P&gt;&lt;P&gt;                  -      DB1.3&lt;/P&gt;&lt;P&gt;                         -  DB1.3.1&lt;/P&gt;&lt;P&gt;                        -   DB1.3.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can anone give me some clue..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Sep 2011 12:45:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-displaying-nested-nodes/m-p/8199774#M1626159</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-09-05T12:45:53Z</dc:date>
    </item>
    <item>
      <title>Re: logic for displaying nested nodes.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-displaying-nested-nodes/m-p/8199775#M1626160</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;make sure your node keys are unique. that should be the most important Trick.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Sep 2011 13:23:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-displaying-nested-nodes/m-p/8199775#M1626160</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-09-05T13:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: logic for displaying nested nodes.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-displaying-nested-nodes/m-p/8199776#M1626161</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;instead of pasting your specification, could you ask your question clearly? You're able to "do it" for 2 nodes? Do you mean you have created one parent DB1 and its child node DB1.1? And now why can't you add a child DB1.1.1 to DB1.1, what happens exactly? (I ask because adding a node just requires to indicate its relationship to another node)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sandra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Sep 2011 13:24:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-displaying-nested-nodes/m-p/8199776#M1626161</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2011-09-05T13:24:14Z</dc:date>
    </item>
    <item>
      <title>Re: logic for displaying nested nodes.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-displaying-nested-nodes/m-p/8199777#M1626162</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yea Sandra , You are right .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; let me explain my requirement clearly . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;first of all i need to use only table CHVW for my requirement . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the user enters the batch number in the selection screen. For that batch number, i have fetch the production order number and batch number .this forms the first node . &lt;/P&gt;&lt;P&gt;For the second node , i have to again select from Chvw table using the production order numbers obtained from the first select statement . the batch numbers obtained from this select query will form the second nodes. IF the movement type indicator is B ,then these is the last node &lt;/P&gt;&lt;P&gt;otherwise we have to repeat above procedure untill we movement type indicator for a particular batch number is 'B'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i'e for each of the batch numbers in the second nodes, i have to again get the production orders and for that production orders i have to fetch the batch numbers again .these will form the 3rd node . &lt;/P&gt;&lt;P&gt;if at this step the movemtn type indicator is 'B' ths is the last node. other wise the same step should be repeated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;could u plz give me some clue ....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Sep 2011 13:36:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-displaying-nested-nodes/m-p/8199777#M1626162</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-09-05T13:36:00Z</dc:date>
    </item>
    <item>
      <title>Re: logic for displaying nested nodes.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-displaying-nested-nodes/m-p/8199778#M1626163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I did read your clarification, but still i dont really understand where parent and child relations come into play here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is it specifically where you struggle? And how do you struggle?&lt;/P&gt;&lt;P&gt;Do you get a dump or what?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you struggle adding a second node on first level?&lt;/P&gt;&lt;P&gt;Do you struggle adding a child node?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How far do you get until now?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Sep 2011 14:03:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-displaying-nested-nodes/m-p/8199778#M1626163</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-09-05T14:03:06Z</dc:date>
    </item>
    <item>
      <title>Re: logic for displaying nested nodes.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-displaying-nested-nodes/m-p/8199779#M1626164</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Same remark as Florian &lt;SPAN __jive_emoticon_name="wink"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Moreover, could you tell us which technology (class, function module, other...) you used for your hierarchical report?&lt;/P&gt;&lt;P&gt;And if you can paste your code of the tree building (please we're not interested in the CHVW part, which is not the issue), that would be fine too!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sandra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Sep 2011 14:11:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-displaying-nested-nodes/m-p/8199779#M1626164</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2011-09-05T14:11:56Z</dc:date>
    </item>
  </channel>
</rss>

