<?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: Implicit database commit in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/implicit-database-commit/m-p/1575602#M259873</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi umesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. each of above 3 FM(s) process with COMMIT WORK,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't commit work&lt;/P&gt;&lt;P&gt;is required for any of the above&lt;/P&gt;&lt;P&gt;FMs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. We simply have to use these 3 FMs,&lt;/P&gt;&lt;P&gt;   and the job will get scheduled for background.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;amit m.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 26 Sep 2006 06:07:28 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-09-26T06:07:28Z</dc:date>
    <item>
      <title>Implicit database commit</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implicit-database-commit/m-p/1575601#M259872</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;I am using JOB_OPEN, JOB_SUBMIT, JOB_CLOSE FM(s) to schedule a background job. Requirement is to rollback the work (updates on database done before job submission) based on status of background job(rollback when job cancelled). But each of above 3 FM(s) process with COMMIT WORK, hence rolling back won't do good after job submission. Statment SUBMIT ~ AND RETURN can not be used as job logs are required for reference.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any way to achieve the requirement or defer a implicit database commit ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: Umesh Kushwah&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Sep 2006 06:05:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implicit-database-commit/m-p/1575601#M259872</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-26T06:05:09Z</dc:date>
    </item>
    <item>
      <title>Re: Implicit database commit</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implicit-database-commit/m-p/1575602#M259873</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi umesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. each of above 3 FM(s) process with COMMIT WORK,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't commit work&lt;/P&gt;&lt;P&gt;is required for any of the above&lt;/P&gt;&lt;P&gt;FMs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. We simply have to use these 3 FMs,&lt;/P&gt;&lt;P&gt;   and the job will get scheduled for background.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;amit m.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Sep 2006 06:07:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implicit-database-commit/m-p/1575602#M259873</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-26T06:07:28Z</dc:date>
    </item>
  </channel>
</rss>

