<?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: Tree view calling multiple transaction in overview screen in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/tree-view-calling-multiple-transaction-in-overview-screen/m-p/744379#M35648</link>
    <description>&lt;P&gt;For a simple menu create a class that will display the menu with an OO class in a docking container attached to left of screen. But by default the left panel wont be displayed as the called transaction/class/FM/report must also handle the display of the panel. Call intially this class in a simple program that only display a white screen or a picture for example.&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Now, if you want something like SE80, every dynpro of the called transaction/class/program should also contain a call to this class to handle the left panel &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;For sample (SE80) perform a where-used search on interface IF_WB_MANAGER, or look for call of modules named wb_manager in logic of workbench tools such as abap program, class or FM editor.&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;</description>
    <pubDate>Fri, 13 Jul 2018 12:04:05 GMT</pubDate>
    <dc:creator>RaymondGiuseppi</dc:creator>
    <dc:date>2018-07-13T12:04:05Z</dc:date>
    <item>
      <title>Tree view calling multiple transaction in overview screen</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/tree-view-calling-multiple-transaction-in-overview-screen/m-p/744378#M35647</link>
      <description>&lt;P&gt;Hello Experts,&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;I want to create treeview / link / Button at the left side which will be veriaous Z TCODES and want to open the corresponding transaction in right side-overview screen.&lt;/P&gt;
  &lt;P&gt;Is it possible in some way?&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jul 2018 11:29:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/tree-view-calling-multiple-transaction-in-overview-screen/m-p/744378#M35647</guid>
      <dc:creator>former_member550878</dc:creator>
      <dc:date>2018-07-13T11:29:35Z</dc:date>
    </item>
    <item>
      <title>Re: Tree view calling multiple transaction in overview screen</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/tree-view-calling-multiple-transaction-in-overview-screen/m-p/744379#M35648</link>
      <description>&lt;P&gt;For a simple menu create a class that will display the menu with an OO class in a docking container attached to left of screen. But by default the left panel wont be displayed as the called transaction/class/FM/report must also handle the display of the panel. Call intially this class in a simple program that only display a white screen or a picture for example.&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Now, if you want something like SE80, every dynpro of the called transaction/class/program should also contain a call to this class to handle the left panel &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;For sample (SE80) perform a where-used search on interface IF_WB_MANAGER, or look for call of modules named wb_manager in logic of workbench tools such as abap program, class or FM editor.&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 13 Jul 2018 12:04:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/tree-view-calling-multiple-transaction-in-overview-screen/m-p/744379#M35648</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2018-07-13T12:04:05Z</dc:date>
    </item>
  </channel>
</rss>

