<?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 data dictionary in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616034#M275907</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi experts,&lt;/P&gt;&lt;P&gt;  why we need the projection view?if we have the &lt;/P&gt;&lt;P&gt;database view in data dictionary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     regards,&lt;/P&gt;&lt;P&gt;      prerna.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Sep 2006 11:46:00 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-09-27T11:46:00Z</dc:date>
    <item>
      <title>data dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616034#M275907</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi experts,&lt;/P&gt;&lt;P&gt;  why we need the projection view?if we have the &lt;/P&gt;&lt;P&gt;database view in data dictionary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     regards,&lt;/P&gt;&lt;P&gt;      prerna.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Sep 2006 11:46:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616034#M275907</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-27T11:46:00Z</dc:date>
    </item>
    <item>
      <title>Re: data dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616035#M275908</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;as i know the database view can have more than one table and wr as projection view can hae only one table and which ever fields u donot need we can suppress them&lt;/P&gt;&lt;P&gt;mahesh.g&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Sep 2006 11:47:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616035#M275908</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-27T11:47:44Z</dc:date>
    </item>
    <item>
      <title>Re: data dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616036#M275909</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;b&amp;gt;View type&lt;/P&gt;&lt;P&gt;Definition&lt;/P&gt;&lt;P&gt;The view type defines how a view is implemented and how one can access the view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Six different view types are supported at the moment:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Database view (type D): implemented with an equivalent view on the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Projection view (type P): used to mask out fields from a table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Help views (type H): used in the online help system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Structure view (type S): used to generate a structure from the view fields. The creation of structure views is no longer supported as of Release 3.0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maintenance view (type C): permits a business view on data and enables maintenance of this data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Entity view (type E): used to map entity types of the EDM to tables of the ABAP Dictionary. This view type is no longer supported as of Release 3.0.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Prabhu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Sep 2006 11:48:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616036#M275909</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-27T11:48:27Z</dc:date>
    </item>
    <item>
      <title>Re: data dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616037#M275910</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To restrict the fields and data you want to show of a table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't really use since I do this directly in the program code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Aubin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Sep 2006 11:48:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616037#M275910</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-27T11:48:37Z</dc:date>
    </item>
    <item>
      <title>Re: data dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616038#M275911</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;b&amp;gt;Database View   (SE11)&amp;lt;/b&amp;gt; &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;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &amp;lt;b&amp;gt;Projection View&amp;lt;/b&amp;gt; &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;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Bhanu.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        Bhanu Priya Mylavarapu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Nov 2006 06:42:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616038#M275911</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-27T06:42:31Z</dc:date>
    </item>
    <item>
      <title>Re: data dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616039#M275912</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;   Projection view ensure the suppression of fields during selection.Suppose we have 10 fields in a database table1 and 5 in databse table 2, but we want to select only 4 fields from table 1 and 2 fields from table 2.So we can have a projection view combining the fields to be selected from table1 and table2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rajesh Sahal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Nov 2006 14:07:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616039#M275912</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-27T14:07:07Z</dc:date>
    </item>
    <item>
      <title>Re: data dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616040#M275913</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;  Projection view contains fields from a single table. You can write the values to them through P.View.(Option write must be ticked). Imagine you have a big table and you don't want enter data in all of the fields while creating a record. Then you can choose the set fields along with primary, you want to enter and thus easily you can maintain data entry. Also this helps in viewing the data with limited desired fields for view. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward, if useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kiran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Nov 2006 04:46:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/1616040#M275913</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-28T04:46:05Z</dc:date>
    </item>
  </channel>
</rss>

