<?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: Effects:Using FM in a new Task in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/effects-using-fm-in-a-new-task/m-p/3814599#M917519</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;You better execute the 4 FM in a single task&lt;/P&gt;&lt;P&gt;Function modules that you call using CALL FUNCTION ... IN BACKGROUND TASK DESTINATION are registered for background execution in another SAP System when the program reaches the next COMMIT WORK statement (using Remote Function Call). After the COMMIT WORK, the dialog process does not wait for these function modules to be executed (asynchronous update). All of the function modules that you register in this way are executed together in a single database LUW&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you want to run in normal background i mean the same system, then there is no need to write any thing, you can use call FUNCTION MODULE statment. but make sure that GUI_* and WS_* function modules do not work in background&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: BVS on May 22, 2008 12:44 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 May 2008 10:43:29 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-05-22T10:43:29Z</dc:date>
    <item>
      <title>Effects:Using FM in a new Task</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/effects-using-fm-in-a-new-task/m-p/3814598#M917518</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;Can anyone tell me what could be effects of calling FM in a new task.&lt;/P&gt;&lt;P&gt;I am trying to use 4 FM in a new task in a single program  with different task names.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My program is run in background and will there be any effects(performance wise), and if so how can I avoid them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Sunil kumar P&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 May 2008 10:29:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/effects-using-fm-in-a-new-task/m-p/3814598#M917518</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-22T10:29:28Z</dc:date>
    </item>
    <item>
      <title>Re: Effects:Using FM in a new Task</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/effects-using-fm-in-a-new-task/m-p/3814599#M917519</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;You better execute the 4 FM in a single task&lt;/P&gt;&lt;P&gt;Function modules that you call using CALL FUNCTION ... IN BACKGROUND TASK DESTINATION are registered for background execution in another SAP System when the program reaches the next COMMIT WORK statement (using Remote Function Call). After the COMMIT WORK, the dialog process does not wait for these function modules to be executed (asynchronous update). All of the function modules that you register in this way are executed together in a single database LUW&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you want to run in normal background i mean the same system, then there is no need to write any thing, you can use call FUNCTION MODULE statment. but make sure that GUI_* and WS_* function modules do not work in background&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: BVS on May 22, 2008 12:44 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 May 2008 10:43:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/effects-using-fm-in-a-new-task/m-p/3814599#M917519</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-22T10:43:29Z</dc:date>
    </item>
    <item>
      <title>Re: Effects:Using FM in a new Task</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/effects-using-fm-in-a-new-task/m-p/3814600#M917520</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;BVS,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for you reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Presently I have ascenario where inside a loop i need to call all the 4 FM's based on different conditions. As they are taking much time to execute a single record, I have planed to use them in a new task where I can go for other record and call the FM again before even completing the process of the first one.&lt;/P&gt;&lt;P&gt;I do not have any commit works. For this program I want to schedule in the background job.&lt;/P&gt;&lt;P&gt;For this instance will ther be any effects of performance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have presently using the FM alternatively in new task as if I had used for every record it is giving me error for opening maximum number of sessions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sunil Kumar P&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 May 2008 10:58:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/effects-using-fm-in-a-new-task/m-p/3814600#M917520</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-22T10:58:25Z</dc:date>
    </item>
  </channel>
</rss>

