<?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: Performance issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/4993008#M1162928</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Macros can only be used in the program the are defined in and only after the definition.&lt;/P&gt;&lt;P&gt;Macros can take max 9 parameters.&lt;/P&gt;&lt;P&gt;Macros are expanded at compilation / generation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Subroutines (FORM) can be called from both the program the are defined in and other programs ('perform &lt;/P&gt;&lt;P&gt;' of 'perform in program ').&lt;/P&gt;&lt;P&gt;Subroutines can take any amount of parameters.&lt;/P&gt;&lt;P&gt;Subroutines are 'expanded' at runtime.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In general:&lt;/P&gt;&lt;P&gt;A MACRO is more or less an abbreviation for some lines of code that are used more than once or twice.&lt;/P&gt;&lt;P&gt;A FORM is a local subroutine (which can be called external).&lt;/P&gt;&lt;P&gt;A FUNCTION is (more or less) a subroutine that is called external.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since debugging a MACRO is not really possible, prevent the use of them (I've never used them, but seen them in action). If the subroutine is used only local (called internal) use a FORM. If the subroutine is called external (used by more than one program) use a FUNCTION.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;there shud be no difference performance wise. use it the way prefred according to your req with the difference stated above&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;reg&lt;/P&gt;&lt;P&gt;Ramya&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Ramya S on Jan 2, 2009 7:29 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 Jan 2009 06:28:24 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-01-02T06:28:24Z</dc:date>
    <item>
      <title>Performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/4993006#M1162926</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;Which one give the better performance Macros or Subrountines.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Suresh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jan 2009 06:23:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/4993006#M1162926</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-02T06:23:48Z</dc:date>
    </item>
    <item>
      <title>Re: Performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/4993007#M1162927</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;Both are one and the Same. Only difference is You cannot debbug the Macro.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jan 2009 06:26:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/4993007#M1162927</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-02T06:26:04Z</dc:date>
    </item>
    <item>
      <title>Re: Performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/4993008#M1162928</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Macros can only be used in the program the are defined in and only after the definition.&lt;/P&gt;&lt;P&gt;Macros can take max 9 parameters.&lt;/P&gt;&lt;P&gt;Macros are expanded at compilation / generation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Subroutines (FORM) can be called from both the program the are defined in and other programs ('perform &lt;/P&gt;&lt;P&gt;' of 'perform in program ').&lt;/P&gt;&lt;P&gt;Subroutines can take any amount of parameters.&lt;/P&gt;&lt;P&gt;Subroutines are 'expanded' at runtime.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In general:&lt;/P&gt;&lt;P&gt;A MACRO is more or less an abbreviation for some lines of code that are used more than once or twice.&lt;/P&gt;&lt;P&gt;A FORM is a local subroutine (which can be called external).&lt;/P&gt;&lt;P&gt;A FUNCTION is (more or less) a subroutine that is called external.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since debugging a MACRO is not really possible, prevent the use of them (I've never used them, but seen them in action). If the subroutine is used only local (called internal) use a FORM. If the subroutine is called external (used by more than one program) use a FUNCTION.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;there shud be no difference performance wise. use it the way prefred according to your req with the difference stated above&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;reg&lt;/P&gt;&lt;P&gt;Ramya&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Ramya S on Jan 2, 2009 7:29 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jan 2009 06:28:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/4993008#M1162928</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-02T06:28:24Z</dc:date>
    </item>
  </channel>
</rss>

