<?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: abap general in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-general/m-p/2537675#M576254</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;&amp;lt;b&amp;gt;1) Sum:&amp;lt;/b&amp;gt; You can only use this statement within a LOOP. If you use SUM in an AT - ENDAT block, the system calculates totals for the numeric fields of all lines in the current line group and writes them to the corresponding fields in the work area. If you use the SUM statement outside an AT - ENDAT block (single entry processing), the system calculates totals for the numeric fields of all lines of the internal table in each loop pass and writes them to the corresponding fields of the work area. It therefore only makes sense to use the SUM statement in AT...ENDAT blocks. If the table contains a nested table, you cannot use the SUM statement. Neither can you use it if you are using a field symbol instead of a work area in the LOOP statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Collect: If an entry with the same key already exists, the COLLECT statement does not append a new line, but adds the contents of the numeric fields in the work area to the contents of the numeric fields in the existing entry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;u can also go through this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;SUM:&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;When processing an internal table in a block starting with LOOP and concluded by ENDLOOP , SUM calculates the control totals of all fields of type I , F and P (see also ABAP/4 number types ) and places them in the LOOP output area (header line of the internal table or an explicitly specified work area). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you use SUM in a LOOP with an explicitly specified output area, this output area must be compatible with the line type of the internal table.When using LOOP to process a sorted extract (see SORT ), the control total &lt;/P&gt;&lt;P&gt;of f at the end of the group appears in the field SUM(f) - - if f is type I , F or P . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;COLLECT:&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;COLLECT is used to create unique or compressed datsets. The key fields are the default key fields of the internal table itab . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use only COLLECT to fill an internal table, COLLECT makes sure that the internal table does not contain two entries with the same default key fields. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If, besides its default key fields, the internal table contains number fields,the contents of these number fields are added together if the internal table already contains an entry with the same key fields. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the default key of an internal table processed with COLLECT is blank, all the values are added up in the first table line. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you specify wa INTO , the entry to be processed is taken from the explicitly specified work area wa . If not, it comes from the header line of the internal table itab . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After COLLECT , the system field SY-TABIX contains the index of the - existing or new - table entry with default key fields which match those of the entry to be processed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;COLLECT can create unique or compressed datasets and should be used precisely for this purpose. If uniqueness or compression are unimportant, or two values with identical default key field values could not possibly occur in your particular task, you should use APPEND instead. However, for a unique or compressed dataset which is also efficient, COLLECT is the statement to use.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you process a table with COLLECT , you should also use COLLECT to fill it. Only by doing this can you guarantee that the internal table will actually be unique or compressed, as described above and COLLECT will run very efficiently. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use COLLECT with an explicitly specified work area, it must be compatible with the line type of the internal table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;refer.&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="1972406"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;EDITOR CALL&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Syntax &lt;/P&gt;&lt;P&gt;EDITOR-CALL FOR REPORT prog [DISPLAY-MODE]. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This statement starts the ABAP editor for the source text of the program specified in prog. prog has to be a character-type data object, which contains the name of a program in capital letters that exists in the Repository. Otherwise you will get a corresponding status message. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After starting the ABAP editor, it provides the full functionality, as if called from the ABAP-Workbench. You can navigate forward to branch to other tools. After returning from the ABAP-editor, the current program continues after the statement EDITOR-CALL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This statement bypasses the authority checks that are performed when calling the ABAP editor via transaction code. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Addition &lt;/P&gt;&lt;P&gt;... DISPLAY-MODE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ABAP editor starts by default in change-mode. The addition DISPLAY-MODE causes the ABAP editor to start in display-mode. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this solved thread,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="51885"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;&lt;/P&gt;&lt;P&gt;3)&amp;lt;/b&amp;gt; yes u can have more thn one selection screen.. u can design various selection screen by having different screen number..&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;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ashu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Jul 2007 05:54:43 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-16T05:54:43Z</dc:date>
    <item>
      <title>abap general</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-general/m-p/2537673#M576252</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is the difference b/w the SUM, COLLECT, EDITOR CALL .&lt;/P&gt;&lt;P&gt;Can we have more than one  selection screens , if how .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 15 Jul 2007 13:18:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-general/m-p/2537673#M576252</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-15T13:18:18Z</dc:date>
    </item>
    <item>
      <title>Re: abap general</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-general/m-p/2537674#M576253</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;In selection screen you can have multiple blocks. I dont think is there any way to have more than 1. May be we can set it by positioning X and Y parameters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;SUM:&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;If you use the SUM statement outside an AT-ENDAT block (single entry processing), the system calculates totals for the numeric fields of all lines of the internal table in each loop pass and writes them to the corresponding fields of the work area. It therefore only makes sense to use the SUM statement in AT-ENDAT blocks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Collect:&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the line is inserted, the system checks whether there is already a table entry that matches the key. If there is no corresponding entry already in the table, the COLLECT statement has the same effect as inserting the new line. If an entry with the same key already exists, the COLLECT statement does not append a new line, but adds the contents of the numeric fields in the work area to the contents of the numeric fields in the existing entry.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should only use the COLLECT statement if you want to create summarized tables. If you use other statements to insert table entries, you may end up with duplicate entries. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Editor-Call&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Displays the internal table itab in an editor similiar to the ABAP Editor. You can then use normal editor functions to make changes. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Changes to the table contents are only adopted if you save before leaving the editor. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ex. &lt;/P&gt;&lt;P&gt;DATA: BEGIN OF T OCCURS 200, &lt;/P&gt;&lt;P&gt;TEXT1(60),TEXT2(12), &lt;/P&gt;&lt;P&gt;END OF T. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;T-TEXT1 = 'Text 1'. T-TEXT2 = 'A'. APPEND T. &lt;/P&gt;&lt;P&gt;T-TEXT1 = 'Text 2'. T-TEXT2 = 'B'. APPEND T. &lt;/P&gt;&lt;P&gt;T-TEXT1 = 'Text 3'. T-TEXT2 = 'C'. APPEND T. &lt;/P&gt;&lt;P&gt;T-TEXT1 = 'Text 4'. T-TEXT2 = 'D'. APPEND T. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EDITOR-CALL FOR T TITLE 'Editor for internal tables'. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT T. &lt;/P&gt;&lt;P&gt;WRITE: / T-TEXT1, T-TEXT2. &lt;/P&gt;&lt;P&gt;ENDLOOP. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. EDITOR-CALL FOR REPORT prog . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reads the program prog from the library and places it in the ABAP/4 Editor. &lt;/P&gt;&lt;P&gt;When you save (with F11), the program is written back to the library. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ex.&lt;/P&gt;&lt;P&gt;EDITOR-CALL FOR REPORT 'ZSAPTEST' DISPLAY-MODE.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2007 05:53:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-general/m-p/2537674#M576253</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-16T05:53:08Z</dc:date>
    </item>
    <item>
      <title>Re: abap general</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-general/m-p/2537675#M576254</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;&amp;lt;b&amp;gt;1) Sum:&amp;lt;/b&amp;gt; You can only use this statement within a LOOP. If you use SUM in an AT - ENDAT block, the system calculates totals for the numeric fields of all lines in the current line group and writes them to the corresponding fields in the work area. If you use the SUM statement outside an AT - ENDAT block (single entry processing), the system calculates totals for the numeric fields of all lines of the internal table in each loop pass and writes them to the corresponding fields of the work area. It therefore only makes sense to use the SUM statement in AT...ENDAT blocks. If the table contains a nested table, you cannot use the SUM statement. Neither can you use it if you are using a field symbol instead of a work area in the LOOP statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Collect: If an entry with the same key already exists, the COLLECT statement does not append a new line, but adds the contents of the numeric fields in the work area to the contents of the numeric fields in the existing entry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;u can also go through this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;SUM:&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;When processing an internal table in a block starting with LOOP and concluded by ENDLOOP , SUM calculates the control totals of all fields of type I , F and P (see also ABAP/4 number types ) and places them in the LOOP output area (header line of the internal table or an explicitly specified work area). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you use SUM in a LOOP with an explicitly specified output area, this output area must be compatible with the line type of the internal table.When using LOOP to process a sorted extract (see SORT ), the control total &lt;/P&gt;&lt;P&gt;of f at the end of the group appears in the field SUM(f) - - if f is type I , F or P . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;COLLECT:&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;COLLECT is used to create unique or compressed datsets. The key fields are the default key fields of the internal table itab . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use only COLLECT to fill an internal table, COLLECT makes sure that the internal table does not contain two entries with the same default key fields. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If, besides its default key fields, the internal table contains number fields,the contents of these number fields are added together if the internal table already contains an entry with the same key fields. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the default key of an internal table processed with COLLECT is blank, all the values are added up in the first table line. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you specify wa INTO , the entry to be processed is taken from the explicitly specified work area wa . If not, it comes from the header line of the internal table itab . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After COLLECT , the system field SY-TABIX contains the index of the - existing or new - table entry with default key fields which match those of the entry to be processed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;COLLECT can create unique or compressed datasets and should be used precisely for this purpose. If uniqueness or compression are unimportant, or two values with identical default key field values could not possibly occur in your particular task, you should use APPEND instead. However, for a unique or compressed dataset which is also efficient, COLLECT is the statement to use.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you process a table with COLLECT , you should also use COLLECT to fill it. Only by doing this can you guarantee that the internal table will actually be unique or compressed, as described above and COLLECT will run very efficiently. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use COLLECT with an explicitly specified work area, it must be compatible with the line type of the internal table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;refer.&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="1972406"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;EDITOR CALL&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Syntax &lt;/P&gt;&lt;P&gt;EDITOR-CALL FOR REPORT prog [DISPLAY-MODE]. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This statement starts the ABAP editor for the source text of the program specified in prog. prog has to be a character-type data object, which contains the name of a program in capital letters that exists in the Repository. Otherwise you will get a corresponding status message. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After starting the ABAP editor, it provides the full functionality, as if called from the ABAP-Workbench. You can navigate forward to branch to other tools. After returning from the ABAP-editor, the current program continues after the statement EDITOR-CALL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This statement bypasses the authority checks that are performed when calling the ABAP editor via transaction code. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Addition &lt;/P&gt;&lt;P&gt;... DISPLAY-MODE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ABAP editor starts by default in change-mode. The addition DISPLAY-MODE causes the ABAP editor to start in display-mode. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this solved thread,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="51885"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;&lt;/P&gt;&lt;P&gt;3)&amp;lt;/b&amp;gt; yes u can have more thn one selection screen.. u can design various selection screen by having different screen number..&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;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ashu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2007 05:54:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-general/m-p/2537675#M576254</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-16T05:54:43Z</dc:date>
    </item>
  </channel>
</rss>

