<?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: purpose in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/purpose/m-p/3752056#M902659</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sandeep&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example the hierarchical relationships between OrgManagement objects (e.g. OrgUnit, Job / Position, User) are stored in table HRP1001.&lt;/P&gt;&lt;P&gt;If you understand the relationships you may &lt;STRONG&gt;imagine&lt;/STRONG&gt; the hierarchy but it is obviously more user-friendly to display them acutally as a hiearchical tree.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 May 2008 03:20:57 GMT</pubDate>
    <dc:creator>uwe_schieferstein</dc:creator>
    <dc:date>2008-05-06T03:20:57Z</dc:date>
    <item>
      <title>purpose</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/purpose/m-p/3752054#M902657</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is the exact purpose of displaying data in a hierarchial manner by using a tree.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 May 2008 07:54:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/purpose/m-p/3752054#M902657</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-05T07:54:43Z</dc:date>
    </item>
    <item>
      <title>Re: purpose</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/purpose/m-p/3752055#M902658</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well I can't think of a better way to visually represent hierachical data. Can you?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 May 2008 22:37:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/purpose/m-p/3752055#M902658</guid>
      <dc:creator>GrahamRobbo</dc:creator>
      <dc:date>2008-05-05T22:37:39Z</dc:date>
    </item>
    <item>
      <title>Re: purpose</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/purpose/m-p/3752056#M902659</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sandeep&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example the hierarchical relationships between OrgManagement objects (e.g. OrgUnit, Job / Position, User) are stored in table HRP1001.&lt;/P&gt;&lt;P&gt;If you understand the relationships you may &lt;STRONG&gt;imagine&lt;/STRONG&gt; the hierarchy but it is obviously more user-friendly to display them acutally as a hiearchical tree.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 May 2008 03:20:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/purpose/m-p/3752056#M902659</guid>
      <dc:creator>uwe_schieferstein</dc:creator>
      <dc:date>2008-05-06T03:20:57Z</dc:date>
    </item>
  </channel>
</rss>

