<?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 Bapi call failing in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-call-failing/m-p/4983802#M1161132</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 calling a bapi FM to update a field called timeslot in the notifications, that are being passed from an internal table to the called FM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  In the output i notice some discrepancies. Like if there are 5-6 notifications then the first notification time slot is not updated. I tried giving the commit work statement with a wait of 1 second , in that case some of the notification is not updated, mostly the second one. Interestingly each time only one of the notification fails to update from the whole list given.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone help??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Jan 2009 02:27:53 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-01-07T02:27:53Z</dc:date>
    <item>
      <title>Bapi call failing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-call-failing/m-p/4983802#M1161132</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 calling a bapi FM to update a field called timeslot in the notifications, that are being passed from an internal table to the called FM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  In the output i notice some discrepancies. Like if there are 5-6 notifications then the first notification time slot is not updated. I tried giving the commit work statement with a wait of 1 second , in that case some of the notification is not updated, mostly the second one. Interestingly each time only one of the notification fails to update from the whole list given.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone help??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jan 2009 02:27:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-call-failing/m-p/4983802#M1161132</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-07T02:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: Bapi call failing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-call-failing/m-p/4983803#M1161133</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jaydeep,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please check your BAPI's return code first. I guess in return structure you are getting message type 'E'. Probably this would be the reason else it should work fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Amit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 03:38:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-call-failing/m-p/4983803#M1161133</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-14T03:38:48Z</dc:date>
    </item>
    <item>
      <title>Re: Bapi call failing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-call-failing/m-p/4983804#M1161134</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try giving DESTINATION 'NONE' while calling the BAPI&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 08:22:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-call-failing/m-p/4983804#M1161134</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-14T08:22:58Z</dc:date>
    </item>
    <item>
      <title>Re: Bapi call failing</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-call-failing/m-p/4983805#M1161135</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt; it's not a commit problem.&lt;/P&gt;&lt;P&gt;You have to put a break point after the BAPI call and watch the internal table of the messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remeber: with the bapi you have to use the FM BAPI_TRANSACTION_COMMIT (if all goes right) and NOT the commit-work instruction (commit+wait doesen't works with BAPI's)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bye&lt;/P&gt;&lt;P&gt;Andrea&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jan 2009 09:26:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-call-failing/m-p/4983805#M1161135</guid>
      <dc:creator>andrea_galluccio2</dc:creator>
      <dc:date>2009-01-14T09:26:56Z</dc:date>
    </item>
  </channel>
</rss>

