<?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 program flow. in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-program-flow/m-p/6055812#M1353178</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just to add to Kathick's explanation. ABAP is an &lt;U&gt;event-driven programming language&lt;/U&gt;. The general flow of an ABAP program is controlled by events.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is a good -practice to code event processing blocks in the order in which they will be triggered during execution.  However, they do not have to be coded in a sequential order.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the first thing i learnt in ABAP basics class &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Suhas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Sep 2009 11:27:45 GMT</pubDate>
    <dc:creator>SuhaSaha</dc:creator>
    <dc:date>2009-09-14T11:27:45Z</dc:date>
    <item>
      <title>ABAP program flow.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-program-flow/m-p/6055810#M1353176</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;whenever i write abap program, i usually maintain following program flow.  is it right from performance tuning point of view?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) include statements&lt;/P&gt;&lt;P&gt;2) DATABASE TABLES&lt;/P&gt;&lt;P&gt;3)  VARIABLE DECLARATIONS&lt;/P&gt;&lt;P&gt;4) SELECTION-SCREEN&lt;/P&gt;&lt;P&gt;5) FIELD SYMBOLS&lt;/P&gt;&lt;P&gt;6) INITIALIZATION&lt;/P&gt;&lt;P&gt;7) AT SELECTION SCREEN&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":smiling_face_with_sunglasses:"&gt;😎&lt;/span&gt; TOP OF PAGE&lt;/P&gt;&lt;P&gt;9) END OF PAGE&lt;/P&gt;&lt;P&gt;10) START OF SELECTION&lt;/P&gt;&lt;P&gt;11) END OF SELECTION&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please advise&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Santosh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Sep 2009 09:33:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-program-flow/m-p/6055810#M1353176</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-14T09:33:35Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP program flow.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-program-flow/m-p/6055811#M1353177</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;In my opinion, you don't have to consider performance in writing an reporting event. Its the same whether you write a event at the top or bottom or inside an include.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But its a good practice to use a ordered approach as mentioned by you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Karthik D&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Sep 2009 11:02:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-program-flow/m-p/6055811#M1353177</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-14T11:02:43Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP program flow.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-program-flow/m-p/6055812#M1353178</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just to add to Kathick's explanation. ABAP is an &lt;U&gt;event-driven programming language&lt;/U&gt;. The general flow of an ABAP program is controlled by events.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is a good -practice to code event processing blocks in the order in which they will be triggered during execution.  However, they do not have to be coded in a sequential order.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the first thing i learnt in ABAP basics class &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Suhas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Sep 2009 11:27:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-program-flow/m-p/6055812#M1353178</guid>
      <dc:creator>SuhaSaha</dc:creator>
      <dc:date>2009-09-14T11:27:45Z</dc:date>
    </item>
  </channel>
</rss>

