<?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: view table vs standard table in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/view-table-vs-standard-table/m-p/1833163#M354893</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hii thr,&lt;/P&gt;&lt;P&gt;standard tables are always there but it depends upon your requirement what you want,you can always select data from tables but if the no of tables,fields and data is large it becomes a performance issue,veiws are very helpful in such cases there are 3 types of views have a look,please reward points if of any use to you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The followings are different types of views: &lt;/P&gt;&lt;P&gt;- Database View   (SE11) &lt;/P&gt;&lt;P&gt;Database views are implement an inner join, that is, only records of the primary table (selected via the join operation) for which the corresponding records of the secondary tables also exist are fetched. Inconsistencies between primary and secondary table could, therefore, lead to a reduced selection set.  &lt;/P&gt;&lt;P&gt;In database views, the join conditions can be formulated using equality relationships between any base fields. In the other types of view, they must be taken from existing foreign keys. That is, tables can only be collected in a maintenance or help view if they are linked to one another via foreign keys. &lt;/P&gt;&lt;P&gt;- Help View    ( SE54) &lt;/P&gt;&lt;P&gt;Help views are used to output additional information when the online help system is called.  &lt;/P&gt;&lt;P&gt;When the F4 button is pressed for a screen field, a check is first made on whether a matchcode is defined for this field. If this is not the case, the help view is displayed in which the check table of the field is the primary table. Thus, for each table no more than one help view can be created, that is, a table can only be primary table in at most one help view.  &lt;/P&gt;&lt;P&gt;- Projection View &lt;/P&gt;&lt;P&gt;Projection views are used to suppress or mask certain fields in a table (projection), thus minimizing the number of interfaces. This means that only the data that is actually required is exchanged when the database is accessed. &lt;/P&gt;&lt;P&gt;A projection view can draw upon only one table. Selection conditions cannot be specified for projection views. &lt;/P&gt;&lt;P&gt;- Maintenance View   ( SE54 ) &lt;/P&gt;&lt;P&gt;Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 10 Jan 2007 11:53:14 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-01-10T11:53:14Z</dc:date>
    <item>
      <title>view table vs standard table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/view-table-vs-standard-table/m-p/1833159#M354889</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;i am new to abap programming, i want to know which table are always to use in real environment? view or standard table? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Besides, any reference book has specify all sap table, view, function etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jan 2007 01:32:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/view-table-vs-standard-table/m-p/1833159#M354889</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-05T01:32:13Z</dc:date>
    </item>
    <item>
      <title>Re: view table vs standard table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/view-table-vs-standard-table/m-p/1833160#M354890</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Depends on your requirement. Sometimes if SAP views are available, it may make sense to use them to improve performance. Most of the time , we end up going against tables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please chekc this link for the list of standard tables.&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.erpgenie.com/abap/tables.htm" target="test_blank"&gt;http://www.erpgenie.com/abap/tables.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jan 2007 01:50:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/view-table-vs-standard-table/m-p/1833160#M354890</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-05T01:50:27Z</dc:date>
    </item>
    <item>
      <title>Re: view table vs standard table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/view-table-vs-standard-table/m-p/1833161#M354891</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Most of the time we come accross Transparent tables in our day to day scenario.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;views are logically a combination of one or more tables. the view is not physically stored ,it is being derived from one or more tables. view is basically a join of tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;- Gopi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jan 2007 02:27:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/view-table-vs-standard-table/m-p/1833161#M354891</guid>
      <dc:creator>gopi_narendra</dc:creator>
      <dc:date>2007-01-05T02:27:51Z</dc:date>
    </item>
    <item>
      <title>Re: view table vs standard table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/view-table-vs-standard-table/m-p/1833162#M354892</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you need info from one table....Use a Standard Table...If you need to read info for two or more tables, use a View.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Both Transparent Tables and Views can be viewed and created on TX. SE11.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Blag.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jan 2007 16:47:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/view-table-vs-standard-table/m-p/1833162#M354892</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-08T16:47:17Z</dc:date>
    </item>
    <item>
      <title>Re: view table vs standard table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/view-table-vs-standard-table/m-p/1833163#M354893</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hii thr,&lt;/P&gt;&lt;P&gt;standard tables are always there but it depends upon your requirement what you want,you can always select data from tables but if the no of tables,fields and data is large it becomes a performance issue,veiws are very helpful in such cases there are 3 types of views have a look,please reward points if of any use to you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The followings are different types of views: &lt;/P&gt;&lt;P&gt;- Database View   (SE11) &lt;/P&gt;&lt;P&gt;Database views are implement an inner join, that is, only records of the primary table (selected via the join operation) for which the corresponding records of the secondary tables also exist are fetched. Inconsistencies between primary and secondary table could, therefore, lead to a reduced selection set.  &lt;/P&gt;&lt;P&gt;In database views, the join conditions can be formulated using equality relationships between any base fields. In the other types of view, they must be taken from existing foreign keys. That is, tables can only be collected in a maintenance or help view if they are linked to one another via foreign keys. &lt;/P&gt;&lt;P&gt;- Help View    ( SE54) &lt;/P&gt;&lt;P&gt;Help views are used to output additional information when the online help system is called.  &lt;/P&gt;&lt;P&gt;When the F4 button is pressed for a screen field, a check is first made on whether a matchcode is defined for this field. If this is not the case, the help view is displayed in which the check table of the field is the primary table. Thus, for each table no more than one help view can be created, that is, a table can only be primary table in at most one help view.  &lt;/P&gt;&lt;P&gt;- Projection View &lt;/P&gt;&lt;P&gt;Projection views are used to suppress or mask certain fields in a table (projection), thus minimizing the number of interfaces. This means that only the data that is actually required is exchanged when the database is accessed. &lt;/P&gt;&lt;P&gt;A projection view can draw upon only one table. Selection conditions cannot be specified for projection views. &lt;/P&gt;&lt;P&gt;- Maintenance View   ( SE54 ) &lt;/P&gt;&lt;P&gt;Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jan 2007 11:53:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/view-table-vs-standard-table/m-p/1833163#M354893</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-10T11:53:14Z</dc:date>
    </item>
  </channel>
</rss>

