<?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: views in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/1779577#M336052</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Views are the join of some tables. Definitely it is better than for all entries&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 30 Nov 2006 07:00:59 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-11-30T07:00:59Z</dc:date>
    <item>
      <title>views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/1779576#M336051</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi friends ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; i want to know the details about views . It will increase the performance ? . Is it better than for all entries ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanx ,&lt;/P&gt;&lt;P&gt;Senthil .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Nov 2006 06:57:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/1779576#M336051</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-30T06:57:58Z</dc:date>
    </item>
    <item>
      <title>Re: views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/1779577#M336052</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Views are the join of some tables. Definitely it is better than for all entries&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Nov 2006 07:00:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/1779577#M336052</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-30T07:00:59Z</dc:date>
    </item>
    <item>
      <title>Re: views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/1779578#M336053</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;There are 4 types views are avilable in SAP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Database View     -   To club more than one table&lt;/P&gt;&lt;P&gt;Projection View     -  To hide fields in one table&lt;/P&gt;&lt;P&gt;Maintanance View -  To maintain database records in table&lt;/P&gt;&lt;P&gt;Help View             - To provide help for a fields (Same functionality as Search help. This is outdated)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;View are improves perfromance in the following aspects&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. If you want to use more than two table in 'JOIN' condition better to use Views . It will improves performance of  a program&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. If you want to use mutiple FOR ALL ENTRIES clause, better to club all SELECT statement  in a view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Bhupal Reddy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Nov 2006 07:03:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/1779578#M336053</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-30T07:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/1779579#M336054</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;If you are using database view for 2 tables(only transparent table is allowed),then it will react as inner join.It will fetch the data faster.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Nov 2006 07:04:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/1779579#M336054</guid>
      <dc:creator>jayanthi_jayaraman</dc:creator>
      <dc:date>2006-11-30T07:04:28Z</dc:date>
    </item>
    <item>
      <title>Re: views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/1779580#M336055</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;senthil&lt;/P&gt;&lt;P&gt;1.Views does not contain data in it. It fetches data from the database only depending on the condition ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.Views are part of data dictionary. They are a window to view the data in database&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3.views can be used to give security to data. users can be allowed to view only basic data only&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;check this&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="2711791"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="2540621"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://forums.sdn.sap.com/click.jspa?searchID=234671&amp;amp;messageID=2590691" target="test_blank"&gt;https://forums.sdn.sap.com/click.jspa?searchID=234671&amp;amp;messageID=2590691&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-charitha.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Nov 2006 07:09:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/1779580#M336055</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-30T07:09:25Z</dc:date>
    </item>
    <item>
      <title>Re: views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/1779581#M336056</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;Based on the requirement you need to decide wether to create a VIEW or program FOR ALL ENTRIES. You can create a view for two database tables but you can use for all enteris in a SELECT query with an internal table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Click the following link:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ea0b446011d189700000e8322d00/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ea0b446011d189700000e8322d00/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Surya.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Nov 2006 07:29:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/1779581#M336056</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-30T07:29:46Z</dc:date>
    </item>
  </channel>
</rss>

