<?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: Database View Vs Maintanence View in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/database-view-vs-maintanence-view/m-p/842540#M44494</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sundara,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(I don't know if you mean differences between SE16 and SM30...)&lt;/P&gt;&lt;P&gt;Well, as far as I can see, I prefer SM30's in order to "give" this maintenance to users, as it would be too dangerous to let them enter tx SE16.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What we do is: we create a Z-transaction which calls SM30 with a couple of parameters, who determine what table we want to change.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps. BR,&lt;/P&gt;&lt;P&gt;Alvaro&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Feb 2005 15:41:39 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-02-14T15:41:39Z</dc:date>
    <item>
      <title>Database View Vs Maintanence View</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/database-view-vs-maintanence-view/m-p/842538#M44492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Friends&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why did SAP design two types of views as above ?(forget projection and help views for the moment).&lt;/P&gt;&lt;P&gt;Is it not possible to control the read only part from Maintanence views when multiple tables are involved as done by Database Views ?&lt;/P&gt;&lt;P&gt;What are the additional benefits by using Maintanence views ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would be glad if anyone can explain me the differnces b/w these two types of views.&lt;/P&gt;&lt;P&gt;Apart from the conventional differences, what I need mainly is, "Is it not possible to achieve the functionalities of a database view from a Maintanence view itself ?"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Prasad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Feb 2005 15:23:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/database-view-vs-maintanence-view/m-p/842538#M44492</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-02-14T15:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: Database View Vs Maintanence View</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/database-view-vs-maintanence-view/m-p/842539#M44493</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;Incase of Database View there is a chance u would not get the most updated information&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whereas in the case of Maintenance View u would get the most updated Information&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Feb 2005 15:27:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/database-view-vs-maintanence-view/m-p/842539#M44493</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-02-14T15:27:12Z</dc:date>
    </item>
    <item>
      <title>Re: Database View Vs Maintanence View</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/database-view-vs-maintanence-view/m-p/842540#M44494</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sundara,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(I don't know if you mean differences between SE16 and SM30...)&lt;/P&gt;&lt;P&gt;Well, as far as I can see, I prefer SM30's in order to "give" this maintenance to users, as it would be too dangerous to let them enter tx SE16.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What we do is: we create a Z-transaction which calls SM30 with a couple of parameters, who determine what table we want to change.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps. BR,&lt;/P&gt;&lt;P&gt;Alvaro&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Feb 2005 15:41:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/database-view-vs-maintanence-view/m-p/842540#M44494</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-02-14T15:41:39Z</dc:date>
    </item>
    <item>
      <title>Re: Database View Vs Maintanence View</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/database-view-vs-maintanence-view/m-p/842541#M44495</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sundara,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The set of data that can be selected with a view greatly depends on whether the view implements an&lt;/P&gt;&lt;P&gt;inner join or an outer join.&lt;/P&gt;&lt;P&gt;n With an inner join, you only get those records which have an entry in all the tables included in the&lt;/P&gt;&lt;P&gt;view. With an outer join, on the other hand, those records that do not have a corresponding entry in&lt;/P&gt;&lt;P&gt;some of the tables included in the view are also selected.&lt;/P&gt;&lt;P&gt;n The hit list found with an inner join can therefore be a subset of the hit list found with an outer join.&lt;/P&gt;&lt;P&gt;n Database views implement an inner join. You only get those records which have an entry in all the&lt;/P&gt;&lt;P&gt;tables included in the view.&lt;/P&gt;&lt;P&gt;n Maintenance views implement an outer join.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maintenance views may not be used as the selection method for search helps. Normally a database&lt;/P&gt;&lt;P&gt;view is used. However, you should note that database views (in the R/3 System) are always created&lt;/P&gt;&lt;P&gt;with an inner join. As a result, only those values having an entry in each of the tables involved are&lt;/P&gt;&lt;P&gt;offered in the input help. Sometimes the values should be determined with an outer join. In this case&lt;/P&gt;&lt;P&gt;you should choose a help view as the selection method&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Immanuel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Feb 2005 16:25:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/database-view-vs-maintanence-view/m-p/842541#M44495</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-02-14T16:25:19Z</dc:date>
    </item>
  </channel>
</rss>

