<?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/2524833#M571812</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;The followings are different types of views: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Database View (SE11) &lt;/P&gt;&lt;P&gt;&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;&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;&lt;/P&gt;&lt;P&gt;- Help View ( SE54) &lt;/P&gt;&lt;P&gt;&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;&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;&lt;/P&gt;&lt;P&gt;Go thru this link plzz&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm&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="449235"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;- Projection View &lt;/P&gt;&lt;P&gt;&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;&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;&lt;/P&gt;&lt;P&gt;- Maintenance View ( SE54 ) &lt;/P&gt;&lt;P&gt;&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;P&gt;&lt;/P&gt;&lt;P&gt;Please have a look at below link. It will help you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;for more detailed info look on:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm" target="test_blank"&gt;http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&amp;amp;" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&amp;amp;&lt;/A&gt;;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.Go to se11&lt;/P&gt;&lt;P&gt;2. select view radiobutton and give a name &lt;/P&gt;&lt;P&gt;3. Create&lt;/P&gt;&lt;P&gt;4. select type of view you want to create. Such as database view.&lt;/P&gt;&lt;P&gt;5. give short description&lt;/P&gt;&lt;P&gt;6. give a table name such as mara&lt;/P&gt;&lt;P&gt;7. press the pushbutton relationship. here you will find all the tables which are allowed to create view with mara.&lt;/P&gt;&lt;P&gt;8. select one or mane tables.&lt;/P&gt;&lt;P&gt;8 copy&lt;/P&gt;&lt;P&gt;9.save , check and activate. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward points for useful Answers&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anji&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 12 Jul 2007 09:15:21 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-12T09:15:21Z</dc:date>
    <item>
      <title>views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2524832#M571811</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is the purpose of various views?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Jul 2007 09:12:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2524832#M571811</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-12T09:12:56Z</dc:date>
    </item>
    <item>
      <title>Re: views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2524833#M571812</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;The followings are different types of views: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Database View (SE11) &lt;/P&gt;&lt;P&gt;&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;&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;&lt;/P&gt;&lt;P&gt;- Help View ( SE54) &lt;/P&gt;&lt;P&gt;&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;&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;&lt;/P&gt;&lt;P&gt;Go thru this link plzz&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm&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="449235"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;- Projection View &lt;/P&gt;&lt;P&gt;&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;&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;&lt;/P&gt;&lt;P&gt;- Maintenance View ( SE54 ) &lt;/P&gt;&lt;P&gt;&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;P&gt;&lt;/P&gt;&lt;P&gt;Please have a look at below link. It will help you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;for more detailed info look on:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm" target="test_blank"&gt;http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&amp;amp;" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&amp;amp;&lt;/A&gt;;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.Go to se11&lt;/P&gt;&lt;P&gt;2. select view radiobutton and give a name &lt;/P&gt;&lt;P&gt;3. Create&lt;/P&gt;&lt;P&gt;4. select type of view you want to create. Such as database view.&lt;/P&gt;&lt;P&gt;5. give short description&lt;/P&gt;&lt;P&gt;6. give a table name such as mara&lt;/P&gt;&lt;P&gt;7. press the pushbutton relationship. here you will find all the tables which are allowed to create view with mara.&lt;/P&gt;&lt;P&gt;8. select one or mane tables.&lt;/P&gt;&lt;P&gt;8 copy&lt;/P&gt;&lt;P&gt;9.save , check and activate. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward points for useful Answers&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anji&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Jul 2007 09:15:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2524833#M571812</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-12T09:15:21Z</dc:date>
    </item>
    <item>
      <title>Re: views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2524834#M571813</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Views:&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Data about an application object is often distributed on several tables. By defining a view, you can define an application-dependent view that combines this data. The structure of such a view is defined by specifying the tables and fields used in the view. Fields that are not required can be hidden, thereby minimizing interfaces. A view can be used in ABAP programs for data selection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Types:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Database Views&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data about an application object is often distributed on several database tables. A database view provides an application-specific view on such distributed data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Projection Views&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Projection views are used to hide fields of a table. This can minimize interfaces; for example when you access the database, you only read and write the field contents actually needed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Help Views&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You have to create a help view if a view with outer join is needed as selection method of a  search help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The selection method of a search help is either a table or a view. If you have to select data from several tables for the search help, you should generally use a database view as selection method. However, a database view always implements an inner join. If you need a view with outer join for the data selection, you have to use a help view as selection method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Maintenance Views&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A maintenance view permits you to maintain the data of an application object together. The data is automatically distributed in the underlying database tables. The maintenance status determines which accesses to the data of the underlying tables are possible with the maintenance view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if useful!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Jul 2007 09:17:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2524834#M571813</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-12T09:17:25Z</dc:date>
    </item>
  </channel>
</rss>

