<?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: Call Function in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-function/m-p/1312392#M162376</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CALL FUNCTION func IN UPDATE TASK. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Extras: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. ... EXPORTING  p1 = f1     ... pn = fn &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. ... TABLES     p1 = itab1  ... pn = itabn &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect &lt;/P&gt;&lt;P&gt;Flags the function module func for execution in the update task. It is not executed at once, but the data passed with EXPORTING or TABLES is placed in a database table and a subsequent COMMIT WORK then causes the function module to be executed by the update task. Update function modules must be flagged as such in the Function Builder &lt;/P&gt;&lt;P&gt;The return value is not set. &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 1 &lt;/P&gt;&lt;P&gt;... EXPORTING p1 = f1 ... pn = fn &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect &lt;/P&gt;&lt;P&gt;Values of fields and field strings specified under EXPORTING are passed from the calling program to the function module. In the function module, the formal parameters are defined as import parameters. In the interface definition, default values must be assigned to all import parameters of the update function module. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Addition 2 &lt;/P&gt;&lt;P&gt;... TABLES p1 = itab1 ... pn = itabn &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect &lt;/P&gt;&lt;P&gt;TABLES passes references to internal tables. All table parameters of the function module must have values. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;With update function modules, both import parameters and exceptions are ignored when the call is made. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During updating processes of function modules, you may not make any calls using the language statements SUBMIT, CALL DIALOG, CALL SCREEN, CALL TRANSACTION, COMMIT WORK or ROLLBACK WORK . All other language elements that trigger a database Commit (for example, a screen change using the MESSAGE statement) also lead to a runtime error during updating.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Jun 2006 14:39:07 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-06-08T14:39:07Z</dc:date>
    <item>
      <title>Call Function</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-function/m-p/1312390#M162374</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;  Can any one detail the exact difference between Call Function and Call Function in Update Task.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sreedhar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Jun 2006 14:29:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-function/m-p/1312390#M162374</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-06-08T14:29:58Z</dc:date>
    </item>
    <item>
      <title>Re: Call Function</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-function/m-p/1312391#M162375</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CALL FUNCTION will fire the function module in the same dialog process as your current session.  CALL FUNCTION in UPDATE TASK, will be fired in a totally separate process, specifically an UPDATE process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rich Heilman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Jun 2006 14:38:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-function/m-p/1312391#M162375</guid>
      <dc:creator>RichHeilman</dc:creator>
      <dc:date>2006-06-08T14:38:52Z</dc:date>
    </item>
    <item>
      <title>Re: Call Function</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-function/m-p/1312392#M162376</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CALL FUNCTION func IN UPDATE TASK. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Extras: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. ... EXPORTING  p1 = f1     ... pn = fn &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. ... TABLES     p1 = itab1  ... pn = itabn &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect &lt;/P&gt;&lt;P&gt;Flags the function module func for execution in the update task. It is not executed at once, but the data passed with EXPORTING or TABLES is placed in a database table and a subsequent COMMIT WORK then causes the function module to be executed by the update task. Update function modules must be flagged as such in the Function Builder &lt;/P&gt;&lt;P&gt;The return value is not set. &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 1 &lt;/P&gt;&lt;P&gt;... EXPORTING p1 = f1 ... pn = fn &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect &lt;/P&gt;&lt;P&gt;Values of fields and field strings specified under EXPORTING are passed from the calling program to the function module. In the function module, the formal parameters are defined as import parameters. In the interface definition, default values must be assigned to all import parameters of the update function module. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Addition 2 &lt;/P&gt;&lt;P&gt;... TABLES p1 = itab1 ... pn = itabn &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect &lt;/P&gt;&lt;P&gt;TABLES passes references to internal tables. All table parameters of the function module must have values. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;With update function modules, both import parameters and exceptions are ignored when the call is made. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During updating processes of function modules, you may not make any calls using the language statements SUBMIT, CALL DIALOG, CALL SCREEN, CALL TRANSACTION, COMMIT WORK or ROLLBACK WORK . All other language elements that trigger a database Commit (for example, a screen change using the MESSAGE statement) also lead to a runtime error during updating.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Jun 2006 14:39:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-function/m-p/1312392#M162376</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-06-08T14:39:07Z</dc:date>
    </item>
    <item>
      <title>Re: Call Function</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-function/m-p/1312393#M162377</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;  When u call a function it is called when the stetament is encountered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When u call function in update task :- that particular function is called only when data is committed .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;that is at the time of SAVE only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward Points if solved.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Jun 2006 14:39:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-function/m-p/1312393#M162377</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-06-08T14:39:35Z</dc:date>
    </item>
    <item>
      <title>Re: Call Function</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-function/m-p/1312394#M162378</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;call function normally will be in the same process,after call function finish then rest of the process continues...&lt;/P&gt;&lt;P&gt; but call function  update task will start different thread , with out disturbing the main process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;vijay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Jun 2006 14:42:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-function/m-p/1312394#M162378</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-06-08T14:42:38Z</dc:date>
    </item>
  </channel>
</rss>

