<?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: INTERNAL TABLES in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/3015637#M712662</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A unique key would be helpful in determining a single record from the internal table while performing a search using that key.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whereas, a non-unique key would not be able to distinctly find out a specific single record for the search that is made using that key. In a table which uses a non-unique key Read statement would pick the first record which shall validate the search criteria.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The optional additions UNIQUE or NON-UNIQUE determine whether the key is to be unique or non-unique, that is, whether the table can accept duplicate entries. If you do not specify UNIQUE or NON-UNIQUE for the key, the table type is generic in this respect. As such, it can only be used for specifying types. When you specify the table type simultaneously, you must note the following restrictions: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You cannot use the UNIQUE addition for standard tables. The system always generates the NON-UNIQUE addition automatically. &lt;/P&gt;&lt;P&gt;You must always specify the UNIQUE option when you create a hashed table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 Nov 2007 08:22:42 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-11-02T08:22:42Z</dc:date>
    <item>
      <title>INTERNAL TABLES</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/3015636#M712661</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;WHAT IS THE DIFF. BETWEEN UNIQUE KEY AND NON-UNIQUE KEY IN INTERNAL TABLES?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Nov 2007 08:21:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/3015636#M712661</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-02T08:21:42Z</dc:date>
    </item>
    <item>
      <title>Re: INTERNAL TABLES</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/3015637#M712662</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A unique key would be helpful in determining a single record from the internal table while performing a search using that key.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whereas, a non-unique key would not be able to distinctly find out a specific single record for the search that is made using that key. In a table which uses a non-unique key Read statement would pick the first record which shall validate the search criteria.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The optional additions UNIQUE or NON-UNIQUE determine whether the key is to be unique or non-unique, that is, whether the table can accept duplicate entries. If you do not specify UNIQUE or NON-UNIQUE for the key, the table type is generic in this respect. As such, it can only be used for specifying types. When you specify the table type simultaneously, you must note the following restrictions: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You cannot use the UNIQUE addition for standard tables. The system always generates the NON-UNIQUE addition automatically. &lt;/P&gt;&lt;P&gt;You must always specify the UNIQUE option when you create a hashed table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Nov 2007 08:22:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/3015637#M712662</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-02T08:22:42Z</dc:date>
    </item>
    <item>
      <title>Re: INTERNAL TABLES</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/3015638#M712663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;unique key is a way of searching  records from the data base with specified key.&lt;/P&gt;&lt;P&gt;Non-unique is the way of searching without any specialisation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Nov 2007 16:52:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/3015638#M712663</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-08T16:52:48Z</dc:date>
    </item>
    <item>
      <title>Re: INTERNAL TABLES</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/3015639#M712664</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sudhakar,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Key&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The key identifies table rows. There are two kinds of key for internal tables - the standard key and a user-defined key. You can specify whether the key should be &amp;lt;b&amp;gt;UNIQUE&amp;lt;/b&amp;gt; or &amp;lt;b&amp;gt;NON-UNIQUE&amp;lt;/b&amp;gt;. Internal tables with a unique key cannot contain duplicate entries. The uniqueness depends on the table access method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At tables with structured row type, the standard key is formed from all character-type columns of the internal table. If a table has an elementary line type, the default key is the entire line. The default key of an internal table whose line type is an internal table, the default key is empty. At tables with non-structured row type, the standard key consists of the entire row. If the row type is also a table, an empty key is defined.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The user-defined key can contain any columns of the internal table that are no internal table themselves, and do not contain internal tables. References are allowed as table keys. Internal tables with a user-defined key are called key tables. When you define the key, the sequence of the key fields is significant. You should remember this, for example, if you intend to sort the table according to the key.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unique key: it means that field having only the unique value only. eg. if u have a name field with unique key than u cant insert two rows having same name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Non Unique Key: means you can insert a duplicate data in that field. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See below link as well..&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="3821722"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope ur problem is solved..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward points if useful..&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards.&lt;/P&gt;&lt;P&gt;ilesh 24x7&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 18 Nov 2007 08:00:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/3015639#M712664</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-18T08:00:49Z</dc:date>
    </item>
    <item>
      <title>Re: INTERNAL TABLES</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/3015640#M712665</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;a unique doesnt allow duplicates into table, whereas the other one does&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Jan 2008 22:12:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/3015640#M712665</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-20T22:12:16Z</dc:date>
    </item>
    <item>
      <title>Re: INTERNAL TABLES</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/3015641#M712666</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;a unique doesnt allow duplicates into table, whereas the other one does&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Jan 2008 22:12:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/3015641#M712666</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-20T22:12:36Z</dc:date>
    </item>
  </channel>
</rss>

