<?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 Background job delay in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/background-job-delay/m-p/5506048#M1259344</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a problem. When saving production order, I need to schedule job, which runs 5 seconds after current time and changes some fields in production order.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Problem is, that this job is alwayse delayed. Sometimes it is only 10 seconds, sometimes one minute. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can I ensure to start job in planned time without delay?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&amp;amp;regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jirka&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 17 Apr 2009 12:13:27 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-04-17T12:13:27Z</dc:date>
    <item>
      <title>Background job delay</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/background-job-delay/m-p/5506048#M1259344</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a problem. When saving production order, I need to schedule job, which runs 5 seconds after current time and changes some fields in production order.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Problem is, that this job is alwayse delayed. Sometimes it is only 10 seconds, sometimes one minute. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can I ensure to start job in planned time without delay?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&amp;amp;regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jirka&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Apr 2009 12:13:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/background-job-delay/m-p/5506048#M1259344</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-04-17T12:13:27Z</dc:date>
    </item>
    <item>
      <title>Re: Background job delay</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/background-job-delay/m-p/5506049#M1259345</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jirka,&lt;/P&gt;&lt;P&gt;           While we configure the background job scheduling you must have given immediate start.Am I correct.When we specify it means that the action reaction is quick immediately.We know that the process execution within SAP is so vast that the process has to wait for a bit of time that is what the cause of the delay you can check while the process you trying to achieve in the mean time you can check SM51 or SM 50 both youo can see that the delay is just because of the work processor availabilty.To improve the performance of the process please do contact the basis team.&lt;/P&gt;&lt;P&gt;Hope your query resolves.&lt;/P&gt;&lt;P&gt;Have a best day ahead.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Apr 2009 12:20:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/background-job-delay/m-p/5506049#M1259345</guid>
      <dc:creator>gaursri</dc:creator>
      <dc:date>2009-04-17T12:20:48Z</dc:date>
    </item>
    <item>
      <title>Re: Background job delay</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/background-job-delay/m-p/5506050#M1259346</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jirka,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the job procesing, you always will have this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you need that another program runs after the creation of the production order, you can execute your second step in a function module in update task or in background task.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This ensure you that the process is executed just before the commit work (the FM must be marked as a RFC FM)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Pepe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Apr 2009 12:32:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/background-job-delay/m-p/5506050#M1259346</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-04-17T12:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: Background job delay</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/background-job-delay/m-p/5506051#M1259347</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks a lot, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IN BACKGROUND TASK statement solved my problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jirka&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Apr 2009 22:06:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/background-job-delay/m-p/5506051#M1259347</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-04-17T22:06:43Z</dc:date>
    </item>
  </channel>
</rss>

