<?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: regarding call back  in perform statement in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-in-perform-statement/m-p/1663282#M293832</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;YOu can use the follwoing functionmodules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI_TRANSACTION_COMMIT&lt;/P&gt;&lt;P&gt;BAPI_TRANSACTION_ROLLBACK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since both are RFC-enabled, you can use for both purposes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Ramakrishna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 04 Nov 2006 16:31:22 GMT</pubDate>
    <dc:creator>venkata_ramisetti</dc:creator>
    <dc:date>2006-11-04T16:31:22Z</dc:date>
    <item>
      <title>regarding call back  in perform statement</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-in-perform-statement/m-p/1663281#M293831</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi all&lt;/P&gt;&lt;P&gt;i am using some custom remote function modules which they have used call transaction in it &lt;/P&gt;&lt;P&gt;now i am using some standard bapis and some custome rfc's &lt;/P&gt;&lt;P&gt; i have to update database when all functions are sucess or else i have to roll back all the updates &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;how to roll back this custom rfc's updates.&lt;/P&gt;&lt;P&gt;thanks &amp;amp; regards&lt;/P&gt;&lt;P&gt;kiran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 04 Nov 2006 16:25:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-in-perform-statement/m-p/1663281#M293831</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-04T16:25:31Z</dc:date>
    </item>
    <item>
      <title>Re: regarding call back  in perform statement</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-in-perform-statement/m-p/1663282#M293832</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;YOu can use the follwoing functionmodules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI_TRANSACTION_COMMIT&lt;/P&gt;&lt;P&gt;BAPI_TRANSACTION_ROLLBACK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since both are RFC-enabled, you can use for both purposes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Ramakrishna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 04 Nov 2006 16:31:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-in-perform-statement/m-p/1663282#M293832</guid>
      <dc:creator>venkata_ramisetti</dc:creator>
      <dc:date>2006-11-04T16:31:22Z</dc:date>
    </item>
    <item>
      <title>Re: regarding call back  in perform statement</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-in-perform-statement/m-p/1663283#M293833</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Kiran,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can code something like this after calling custom remote function module.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;...

IF SY-SUBRC = 0.
  COMMIT WORK.
ELSE.
  ROLLBACK WORK.
ENDIF.

...&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ferry Lianto&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please reward points if helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 04 Nov 2006 16:33:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-in-perform-statement/m-p/1663283#M293833</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-11-04T16:33:02Z</dc:date>
    </item>
    <item>
      <title>Re: regarding call back  in perform statement</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-in-perform-statement/m-p/1663284#M293834</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Kiran,&lt;/P&gt;&lt;P&gt;the invocation of a remote enabled fuba via RFC triggers an implicit commit work. So if the requirement is to update the local db only in case of successful remote computing any change to the db has to occur only after the FuBa returns.&lt;/P&gt;&lt;P&gt;If the requirement is that way that remote and local side should have a transactional behavior (common commit) you face the so called "2 phase commit" problem. To my knowledge there is no perfect solution available for this scenario.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Klaus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Nov 2006 22:45:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-in-perform-statement/m-p/1663284#M293834</guid>
      <dc:creator>former_member183804</dc:creator>
      <dc:date>2006-11-05T22:45:44Z</dc:date>
    </item>
  </channel>
</rss>

