<?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: Calling 2 dependent BAPI in exit in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/calling-2-dependent-bapi-in-exit/m-p/12140144#M1975921</link>
    <description>&lt;P&gt;Why did you wrote "if I use IN UPDATE TASK I also cannot call COMMIT"    you don't need it in UPDATE TASK&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jan 2020 13:39:39 GMT</pubDate>
    <dc:creator>FredericGirod</dc:creator>
    <dc:date>2020-01-30T13:39:39Z</dc:date>
    <item>
      <title>Calling 2 dependent BAPI in exit</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/calling-2-dependent-bapi-in-exit/m-p/12140143#M1975920</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
  &lt;P&gt;I have a scenario where I have to call 2 BAPIs in an enhancement. These 2 BAPIs are dependent, first BAPI need to be committed first before the second can be called. &lt;/P&gt;
  &lt;P&gt;Now, in enhancements we cannot call COMMIT, if I use IN UPDATE TASK I also cannot call COMMIT. In this situation, how could I achieve it?&lt;/P&gt;
  &lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2020 13:30:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/calling-2-dependent-bapi-in-exit/m-p/12140143#M1975920</guid>
      <dc:creator>suwandi_cahyadi</dc:creator>
      <dc:date>2020-01-30T13:30:19Z</dc:date>
    </item>
    <item>
      <title>Re: Calling 2 dependent BAPI in exit</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/calling-2-dependent-bapi-in-exit/m-p/12140144#M1975921</link>
      <description>&lt;P&gt;Why did you wrote "if I use IN UPDATE TASK I also cannot call COMMIT"    you don't need it in UPDATE TASK&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2020 13:39:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/calling-2-dependent-bapi-in-exit/m-p/12140144#M1975921</guid>
      <dc:creator>FredericGirod</dc:creator>
      <dc:date>2020-01-30T13:39:39Z</dc:date>
    </item>
    <item>
      <title>Re: Calling 2 dependent BAPI in exit</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/calling-2-dependent-bapi-in-exit/m-p/12140145#M1975922</link>
      <description>&lt;P&gt;Calling BAPIs while another object is being saved to database is not a good idea. What if there are errors?&lt;/P&gt;&lt;P&gt;It should be developed more like a workflow: Enter object 1 to be created -&amp;gt; User saves -&amp;gt; BAdI to start workflow event in update task -&amp;gt; Commit work -&amp;gt; update task runs, database updates for object 1 -&amp;gt; event is started asynchronously -&amp;gt; actual database commit -&amp;gt; workflow starts -&amp;gt; BAPI 1 is called -&amp;gt; BAPI 2 is called. You can monitor workflow.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2020 14:01:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/calling-2-dependent-bapi-in-exit/m-p/12140145#M1975922</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2020-01-30T14:01:31Z</dc:date>
    </item>
  </channel>
</rss>

