<?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 update and background in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/update-and-background/m-p/1101679#M103637</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;what's the difference between calling a func mod in update task and in a background task.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 Nov 2005 16:41:58 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-11-04T16:41:58Z</dc:date>
    <item>
      <title>update and background</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/update-and-background/m-p/1101679#M103637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;what's the difference between calling a func mod in update task and in a background task.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Nov 2005 16:41:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/update-and-background/m-p/1101679#M103637</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-11-04T16:41:58Z</dc:date>
    </item>
    <item>
      <title>Re: update and background</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/update-and-background/m-p/1101680#M103638</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If calling in Update Task, then it runs in an UPdate Work process, if you call in background task, it is running in a background task.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The update task is a little special though.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REad on.....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;i&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Variant 3 &lt;/P&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;Additions: &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;&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;&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;&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;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;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Administration transaction &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Related &lt;/P&gt;&lt;P&gt;COMMIT WORK, SET UPDATE TASK LOCAL &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/i&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;Rich Heilman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Nov 2005 16:50:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/update-and-background/m-p/1101680#M103638</guid>
      <dc:creator>RichHeilman</dc:creator>
      <dc:date>2005-11-04T16:50:20Z</dc:date>
    </item>
    <item>
      <title>Re: update and background</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/update-and-background/m-p/1101681#M103639</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you say the background task, seperate work process is allocated .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Nov 2005 16:50:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/update-and-background/m-p/1101681#M103639</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-11-04T16:50:34Z</dc:date>
    </item>
    <item>
      <title>Re: update and background</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/update-and-background/m-p/1101682#M103640</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 background task the FM is executed in asyncronous: the FM is executed but the main program does not wait for the FM termination (it continues immediately after the call of FM)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  in update task (often used with update/insert/modify of DB tables) the FM is not executed immediately, but when a commit work is called (only then the update task is executed).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Manuel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Nov 2005 16:56:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/update-and-background/m-p/1101682#M103640</guid>
      <dc:creator>manuel_bassani</dc:creator>
      <dc:date>2005-11-04T16:56:30Z</dc:date>
    </item>
  </channel>
</rss>

