<?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: Doubts in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubts/m-p/3546615#M853246</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;1. &lt;STRONG&gt;Select Single&lt;/STRONG&gt; is used to read single entry from the Database.&lt;/P&gt;&lt;P&gt;1.1 &lt;STRONG&gt;UPTO ONE ROW&lt;/STRONG&gt; - To restrict the first line included in the selection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. &lt;STRONG&gt;Refresh&lt;/STRONG&gt; -  This always applies to the body of the table. As with the CLEAR statement, the memory used by the table before you initialized it remains allocated. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;CLEAR&lt;/STRONG&gt;  CLEAR &amp;lt;itab&amp;gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; This statement restores an internal table to the state it was in immediately after you declared it. This means that the table contains no lines. However, the memory already occupied by the memory up until you cleared it remains allocated to the table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are using internal tables with header lines, remember that the header line and the body of the table have the same name. If you want to address the body of the table in a comparison, you must place two brackets ([ ]) after the table name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CLEAR &amp;lt;itab&amp;gt;[].&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To ensure that the table itself has been initialized&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. Delete itab deletes contents of Internal Table&lt;/P&gt;&lt;P&gt;4. No events are present in Internal Table but you have events in Reports.&lt;/P&gt;&lt;P&gt;5.Events in Reports:&lt;/P&gt;&lt;P&gt; - Initialization&lt;/P&gt;&lt;P&gt; - At selection-screen output&lt;/P&gt;&lt;P&gt; - At Selection-screen on block&lt;/P&gt;&lt;P&gt; - At Selection-screen on field&lt;/P&gt;&lt;P&gt; - At Selection-screen &lt;/P&gt;&lt;P&gt; - Start-of-selection&lt;/P&gt;&lt;P&gt; - End-of-selcetion&lt;/P&gt;&lt;P&gt; - Top-of-page&lt;/P&gt;&lt;P&gt; - End-of-page&lt;/P&gt;&lt;P&gt; - At line-selection&lt;/P&gt;&lt;P&gt; - At pf&amp;lt;nn&amp;gt;&lt;/P&gt;&lt;P&gt; - At USer-Command&lt;/P&gt;&lt;P&gt;- Top-of-page during line-selection&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6. We've 3 Types of Internal Tables:&lt;/P&gt;&lt;P&gt;    Standard Internal Table,&lt;/P&gt;&lt;P&gt;    Sorted Internal Table &amp;amp;&lt;/P&gt;&lt;P&gt;    Hashed Internal Table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standard tables&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the most appropriate type if you are going to address the individual table entries using the index. Index access is the quickest possible access. You should fill a standard table by appending lines (ABAP APPEND statement), and read, modify and delete entries by specifying the index (INDEX option with the relevant ABAP command). The access time for a standard table increases in a linear relationship with the number of table entries. If you need key access, standard tables are particularly useful if you can fill and process the table in separate steps. For example, you could fill the table by appending entries, and then sort it. If you use the binary search option with key access, the response time is logarithmically proportional to the number of table entries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorted tables&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the most appropriate type if you need a table which is sorted as you fill it. You fill sorted tables using the INSERT statement. Entries are inserted according to the sort sequence defined through the table key. Any illegal entries are recognized as soon as you try to add them to the table. The response time for key access is logarithmically proportional to the number of table entries, since the system always uses a binary search. Sorted tables are particularly useful for partially sequential processing in a LOOP if you specify the beginning of the table key in the WHERE condition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hashed tables&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index. The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for processing large amounts of data. &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;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Iyswarya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Mar 2008 04:50:43 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-03-27T04:50:43Z</dc:date>
    <item>
      <title>Doubts</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubts/m-p/3546611#M853242</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;      I want to know about &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Select single&lt;/P&gt;&lt;P&gt;        and&lt;/P&gt;&lt;P&gt;    upto one row&lt;/P&gt;&lt;P&gt;2)refresh&lt;/P&gt;&lt;P&gt;       and &lt;/P&gt;&lt;P&gt;   clear&lt;/P&gt;&lt;P&gt;3) i want to delete the entire data in a table, write the statement for it&lt;/P&gt;&lt;P&gt;4)events in internal tables&lt;/P&gt;&lt;P&gt;5) events in sap&lt;/P&gt;&lt;P&gt;6)types of internal tables and difference between them&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;points will be awarded&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;nagaraju tankala&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Mar 2008 01:32:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/doubts/m-p/3546611#M853242</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-27T01:32:39Z</dc:date>
    </item>
    <item>
      <title>Re: Doubts</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubts/m-p/3546612#M853243</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nagaraju, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For all of u r qns u can answers in the forum. Plz search the forum. you will get quick and good answers from deferent peoples. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;Naresh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Mar 2008 01:41:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/doubts/m-p/3546612#M853243</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-27T01:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: Doubts</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubts/m-p/3546613#M853244</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;select single is used to fetch only one record which is required&lt;/P&gt;&lt;P&gt;here if u mention where condition then u get the required record&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where as in select upto one row&lt;/P&gt;&lt;P&gt;u get only single record that too only first record of the table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;refresh is used used too clear the contents of the table&lt;/P&gt;&lt;P&gt;where a s clear is used to refresh the contents of the work area&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if the table is with header line then to clear the body contents we use &lt;STRONG&gt;clear itab[]&lt;/STRONG&gt;  this is similar to refresh.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if the table is with out header line then we use &lt;STRONG&gt;refresh itab&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;to clear the body contents.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if u want to delete the table contents the use keyword &lt;STRONG&gt;DELETE&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Deleting from a Database Table &lt;/P&gt;&lt;P&gt;- DELETE FROM  dbtab. or &lt;/P&gt;&lt;P&gt;DELETE FROM (dbtabname). &lt;/P&gt;&lt;P&gt;- DELETE  dbtab      FROM wa. or &lt;/P&gt;&lt;P&gt;DELETE (dbtabname) FROM wa. &lt;/P&gt;&lt;P&gt;- DELETE  dbtab      FROM TABLE itab. or &lt;/P&gt;&lt;P&gt;DELETE (dbtabname) FROM TABLE itab. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Delete from an internal table &lt;/P&gt;&lt;P&gt;- DELETE itab. &lt;/P&gt;&lt;P&gt;- DELETE TABLE itab WITH TABLE KEY k1 = v1 ... kn = vn. &lt;/P&gt;&lt;P&gt;- DELETE TABLE itab [FROM wa]. &lt;/P&gt;&lt;P&gt;- DELETE itab INDEX idx. &lt;/P&gt;&lt;P&gt;- DELETE itab FROM idx1 TO idx2. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;events in report&lt;/U&gt;&lt;/P&gt;&lt;P&gt;INITIALZATION.&lt;/P&gt;&lt;P&gt;AT SELECTION-SCREEN OUTPUT.&lt;/P&gt;&lt;P&gt;AT SELECTION-SCREEN ON FIELD.&lt;/P&gt;&lt;P&gt;AT SELECTION-SCREEN ON BLOCK.&lt;/P&gt;&lt;P&gt;AT SELECTION-SCREEN.&lt;/P&gt;&lt;P&gt;START-OF-SELECTION.&lt;/P&gt;&lt;P&gt;END-OF-SELECTION.&lt;/P&gt;&lt;P&gt;TOP-OF-PAGE&lt;/P&gt;&lt;P&gt;END-OF-PAGE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standard tables. In a standard table, you can access data &lt;/P&gt;&lt;P&gt;using either the table index or the key. Since the key of a &lt;/P&gt;&lt;P&gt;standard table always has to be non-unique for &lt;/P&gt;&lt;P&gt;compatibility reasons, the system searches the whole table &lt;/P&gt;&lt;P&gt;each time you access it using the key. Consequently, you &lt;/P&gt;&lt;P&gt;should always use the index to access a standard table &lt;/P&gt;&lt;P&gt;whenever possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorted tables. In a sorted table, the system &lt;/P&gt;&lt;P&gt;automatically stores the entries and inserts new entries &lt;/P&gt;&lt;P&gt;sorted by the table key. The system uses a binary search on &lt;/P&gt;&lt;P&gt;the table when you access it using the key. You can specify &lt;/P&gt;&lt;P&gt;the key of a sorted table as unique. You will often use the &lt;/P&gt;&lt;P&gt;key to access a sorted table, but it is also possible to &lt;/P&gt;&lt;P&gt;use the index. Standard tables and sorted tables are &lt;/P&gt;&lt;P&gt;generically known as index tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hashed tables. You can only access a hashed table using &lt;/P&gt;&lt;P&gt;the key. There are certain conditions under which you can &lt;/P&gt;&lt;P&gt;considerably reduce the access times to large tables by &lt;/P&gt;&lt;P&gt;using a hashed table. The key of a hashed table must always &lt;/P&gt;&lt;P&gt;be unique.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Kodandarami Reddy.S on Mar 27, 2008 2:55 AM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Kodandarami Reddy.S on Mar 27, 2008 3:01 AM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Kodandarami Reddy.S on Mar 27, 2008 3:06 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Mar 2008 01:54:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/doubts/m-p/3546613#M853244</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-27T01:54:42Z</dc:date>
    </item>
    <item>
      <title>Re: Doubts</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubts/m-p/3546614#M853245</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;1.SELECT SINGLE -&amp;gt;SELECTS ONLY ONE ROW FROM DATABASE TABLE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.REFRESH DELETES WHOLE DATA IN INTERNAL TABLE &lt;/P&gt;&lt;P&gt;  CLEAR CLEARS THE HEADER OF THE INTERNAL TABLE&lt;/P&gt;&lt;P&gt;3.DELETE FROM &amp;lt;TABLE NAME&amp;gt; WHERE &amp;lt;CONDITION&amp;gt;&lt;/P&gt;&lt;P&gt;4.AT NEW...ENDAT,AT FIRST...ENDAT,AT LAST....ENDAT.&lt;/P&gt;&lt;P&gt;5.INITIALZATION.&lt;/P&gt;&lt;P&gt;AT SELECTION-SCREEN OUTPUT.&lt;/P&gt;&lt;P&gt;AT SELECTION-SCREEN ON FIELD.&lt;/P&gt;&lt;P&gt;AT SELECTION-SCREEN ON BLOCK.&lt;/P&gt;&lt;P&gt;AT SELECTION-SCREEN.&lt;/P&gt;&lt;P&gt;START-OF-SELECTION.&lt;/P&gt;&lt;P&gt;END-OF-SELECTION.&lt;/P&gt;&lt;P&gt;TOP-OF-PAGE&lt;/P&gt;&lt;P&gt;END-OF-PAGE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6.STANDARD(NORMAL),SORTED(SORTED BY KEY) AND HASHED(UNIQUE KEY)&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;&lt;/P&gt;&lt;P&gt;V.Balaji&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if Usefull...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Mar 2008 02:05:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/doubts/m-p/3546614#M853245</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-27T02:05:16Z</dc:date>
    </item>
    <item>
      <title>Re: Doubts</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubts/m-p/3546615#M853246</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;1. &lt;STRONG&gt;Select Single&lt;/STRONG&gt; is used to read single entry from the Database.&lt;/P&gt;&lt;P&gt;1.1 &lt;STRONG&gt;UPTO ONE ROW&lt;/STRONG&gt; - To restrict the first line included in the selection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. &lt;STRONG&gt;Refresh&lt;/STRONG&gt; -  This always applies to the body of the table. As with the CLEAR statement, the memory used by the table before you initialized it remains allocated. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;CLEAR&lt;/STRONG&gt;  CLEAR &amp;lt;itab&amp;gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; This statement restores an internal table to the state it was in immediately after you declared it. This means that the table contains no lines. However, the memory already occupied by the memory up until you cleared it remains allocated to the table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are using internal tables with header lines, remember that the header line and the body of the table have the same name. If you want to address the body of the table in a comparison, you must place two brackets ([ ]) after the table name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CLEAR &amp;lt;itab&amp;gt;[].&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To ensure that the table itself has been initialized&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. Delete itab deletes contents of Internal Table&lt;/P&gt;&lt;P&gt;4. No events are present in Internal Table but you have events in Reports.&lt;/P&gt;&lt;P&gt;5.Events in Reports:&lt;/P&gt;&lt;P&gt; - Initialization&lt;/P&gt;&lt;P&gt; - At selection-screen output&lt;/P&gt;&lt;P&gt; - At Selection-screen on block&lt;/P&gt;&lt;P&gt; - At Selection-screen on field&lt;/P&gt;&lt;P&gt; - At Selection-screen &lt;/P&gt;&lt;P&gt; - Start-of-selection&lt;/P&gt;&lt;P&gt; - End-of-selcetion&lt;/P&gt;&lt;P&gt; - Top-of-page&lt;/P&gt;&lt;P&gt; - End-of-page&lt;/P&gt;&lt;P&gt; - At line-selection&lt;/P&gt;&lt;P&gt; - At pf&amp;lt;nn&amp;gt;&lt;/P&gt;&lt;P&gt; - At USer-Command&lt;/P&gt;&lt;P&gt;- Top-of-page during line-selection&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6. We've 3 Types of Internal Tables:&lt;/P&gt;&lt;P&gt;    Standard Internal Table,&lt;/P&gt;&lt;P&gt;    Sorted Internal Table &amp;amp;&lt;/P&gt;&lt;P&gt;    Hashed Internal Table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standard tables&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the most appropriate type if you are going to address the individual table entries using the index. Index access is the quickest possible access. You should fill a standard table by appending lines (ABAP APPEND statement), and read, modify and delete entries by specifying the index (INDEX option with the relevant ABAP command). The access time for a standard table increases in a linear relationship with the number of table entries. If you need key access, standard tables are particularly useful if you can fill and process the table in separate steps. For example, you could fill the table by appending entries, and then sort it. If you use the binary search option with key access, the response time is logarithmically proportional to the number of table entries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorted tables&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the most appropriate type if you need a table which is sorted as you fill it. You fill sorted tables using the INSERT statement. Entries are inserted according to the sort sequence defined through the table key. Any illegal entries are recognized as soon as you try to add them to the table. The response time for key access is logarithmically proportional to the number of table entries, since the system always uses a binary search. Sorted tables are particularly useful for partially sequential processing in a LOOP if you specify the beginning of the table key in the WHERE condition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hashed tables&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index. The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for processing large amounts of data. &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;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Iyswarya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Mar 2008 04:50:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/doubts/m-p/3546615#M853246</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-27T04:50:43Z</dc:date>
    </item>
  </channel>
</rss>

