<?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/2221140#M476951</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;- 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;reward points&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, 26 Apr 2007 06:22:50 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-04-26T06:22:50Z</dc:date>
    <item>
      <title>views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2221139#M476950</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;can u pls tell me how to create all views .pls tell step by step .how to give join conditions . give one examle program also.(database view &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;,maintainance view, help view , projection view)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.what is the purpose of help  view . pls tell how to create it step by step .what is the difference between all the view s.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2007 06:20:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2221139#M476950</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-26T06:20:48Z</dc:date>
    </item>
    <item>
      <title>Re: views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2221140#M476951</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;- 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;reward points&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, 26 Apr 2007 06:22:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2221140#M476951</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-26T06:22:50Z</dc:date>
    </item>
    <item>
      <title>Re: views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2221141#M476952</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&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;you will find the database view in such way.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2007 06:29:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2221141#M476952</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-26T06:29:09Z</dc:date>
    </item>
    <item>
      <title>Re: views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2221142#M476953</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ok. before save and activate. You have to select the columns you want to display in the "view fields" tab.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2007 06:31:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2221142#M476953</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-26T06:31:48Z</dc:date>
    </item>
    <item>
      <title>Re: views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2221143#M476954</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hai,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the procedure to create Data base Views:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Procedure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Enter an explanatory short text in the field Short text. &lt;/P&gt;&lt;P&gt;You can for example find the view at a later time using this short text.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Define the tables to be included in the view in the Tables field of the Tables/Join conditions tab page. &lt;/P&gt;&lt;P&gt;Keep in mind that you can only include transparent tables in a database view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Link the tables with join conditions. &lt;/P&gt;&lt;P&gt;If there are suitable foreign keys between the tables, you should copy the join conditions from these foreign keys (see Foreign Key Relationships and Join Conditions).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Place the cursor on a table name and choose Relationships. All foreign keys to other tables defined for this table are displayed. Select the foreign keys and choose Copy. The join condition is now derived from the definitions in the foreign key.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you only want to see the foreign key relationship existing between two tables, you must first select these two tables (click on the first column of the input area Tables) and then choose Relationships.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the View fields tab page, select the fields that you want to copy to the view. &lt;/P&gt;&lt;P&gt;Choose Table fields. All the tables contained in the view are displayed in a dialog box. Select a table. All the fields contained in this table are displayed. You can copy fields by selecting them in the first column and choosing Copy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also include an entire table in the view (see Includes in Database Views).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the Selection conditions tab page, you can (optionally) formulate restrictions for the data records to be displayed with the view (see Maintaining Selection Conditions for Views). &lt;/P&gt;&lt;P&gt;The selection conditions define the data records that can be selected with the view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With Goto ® Technical settings, you can (optionally) maintain the technical settings of the database view. &lt;/P&gt;&lt;P&gt;You can define whether and how the database view should be buffered here. Proceed as for the technical settings of a table (see Maintaining Technical Settings). Note that only the settings for buffering can be maintained for database views.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the Maintenance status tab page, select the maintenance status of the database view. &lt;/P&gt;&lt;P&gt;If the view contains more than one table, the maintenance status read only cannot be altered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Save your entries. You are asked to assign the view a development class. &lt;/P&gt;&lt;P&gt;You can change this development class later with Goto ® Object directory entry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Choose Activate Button.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope you got it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if it helps you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regds,&lt;/P&gt;&lt;P&gt;Rama chary.Pammi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2007 06:37:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/views/m-p/2221143#M476954</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-26T06:37:33Z</dc:date>
    </item>
  </channel>
</rss>

