<?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: Dirty update in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/dirty-update/m-p/5251915#M1213344</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What about function module with an update using attribute 'Coll. run' (collective run). then start via program RSM13005&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS  This option is used SAP internal only (special form of V2 update, asynchronously)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;May be this helpful to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; a®&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Feb 2009 15:08:42 GMT</pubDate>
    <dc:creator>former_member194669</dc:creator>
    <dc:date>2009-02-11T15:08:42Z</dc:date>
    <item>
      <title>Dirty update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dirty-update/m-p/5251914#M1213343</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 need to update a database table (Z) and i have to free the resource at once to not produce a deadlock situatiuon. On the other hand, i'm not allowed to do a normal commit, because this will commit all open resources without the application developper notice which may lead to unpredictable results.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas on how to archive that? First i thought shared memory might be solution but this is not really for built for many updates.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm open for every suggestion, sending a "message" to another report or starting threads or whatever.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Feb 2009 14:29:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dirty-update/m-p/5251914#M1213343</guid>
      <dc:creator>rainer_hbenthal</dc:creator>
      <dc:date>2009-02-11T14:29:36Z</dc:date>
    </item>
    <item>
      <title>Re: Dirty update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dirty-update/m-p/5251915#M1213344</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What about function module with an update using attribute 'Coll. run' (collective run). then start via program RSM13005&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS  This option is used SAP internal only (special form of V2 update, asynchronously)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;May be this helpful to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; a®&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Feb 2009 15:08:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dirty-update/m-p/5251915#M1213344</guid>
      <dc:creator>former_member194669</dc:creator>
      <dc:date>2009-02-11T15:08:42Z</dc:date>
    </item>
  </channel>
</rss>

