<?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: Help - Short Dump When Calling Standard SAP BAPI in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096196#M102203</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sam,&lt;/P&gt;&lt;P&gt;iv_x_save = ' ' tells the fcn module not to actually make the change.&lt;/P&gt;&lt;P&gt;This is empty when IV_TESTRUN = 'X' and vice versa.&lt;/P&gt;&lt;P&gt;Rgds&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 Dec 2005 09:32:34 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-12-13T09:32:34Z</dc:date>
    <item>
      <title>Help - Short Dump When Calling Standard SAP BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096191#M102198</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a program that creates a short dump in the background when I call a function module more than once in the same program.&lt;/P&gt;&lt;P&gt;Basically what I do is call BUPR_RELATIONSHIP_CREATE&lt;/P&gt;&lt;P&gt;for each relationship I need to create in our CRM system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I even do a COMMIT WORK AND WAIT after each call, however I get a short dump of DUPLICATE key insert (SAPSQL_ARRAY_INSERT_DUPREC)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking at SAP's own code where the dump occurs, SAP have commented out the line:&lt;/P&gt;&lt;P&gt;INSERT BUT051 FROM TABLE LT_BUT051 ACCEPTING DUPLICATE KEYS.   &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is an excerpt of the code from my program:&lt;/P&gt;&lt;P&gt;CALL FUNCTION 'BUPR_RELATIONSHIP_CREATE'&lt;/P&gt;&lt;P&gt;  EXPORTING&lt;/P&gt;&lt;P&gt;    iv_partner_1    = '0010003939'&lt;/P&gt;&lt;P&gt;    iv_partner_2    = '0010008090'&lt;/P&gt;&lt;P&gt;    iv_relationship = 'ZUR010'&lt;/P&gt;&lt;P&gt;    iv_date_from    = '00010101'&lt;/P&gt;&lt;P&gt;    iv_date_to      = '99991231'&lt;/P&gt;&lt;P&gt;    iv_testrun      = ' '&lt;/P&gt;&lt;P&gt;    iv_x_save       = 'X'&lt;/P&gt;&lt;P&gt;  TABLES&lt;/P&gt;&lt;P&gt;    et_return       = gt_return.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERFORM disp_error USING gs_warning.&lt;/P&gt;&lt;P&gt;COMMIT WORK AND WAIT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION 'BUPR_RELATIONSHIP_CREATE'&lt;/P&gt;&lt;P&gt;  EXPORTING&lt;/P&gt;&lt;P&gt;    iv_partner_1    = '0010003939'&lt;/P&gt;&lt;P&gt;    iv_partner_2    = '0010004555'&lt;/P&gt;&lt;P&gt;    iv_relationship = 'ZUR010'&lt;/P&gt;&lt;P&gt;    iv_date_from    = '00010101'&lt;/P&gt;&lt;P&gt;    iv_date_to      = '99991231'&lt;/P&gt;&lt;P&gt;    iv_testrun      = ' '&lt;/P&gt;&lt;P&gt;    iv_x_save       = 'X'&lt;/P&gt;&lt;P&gt;  TABLES&lt;/P&gt;&lt;P&gt;    et_return       = gt_return.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERFORM disp_error USING gs_warning.&lt;/P&gt;&lt;P&gt;COMMIT WORK AND WAIT.&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone offer any advice?&lt;/P&gt;&lt;P&gt;Many Thanks&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Dec 2005 15:17:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096191#M102198</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-12T15:17:29Z</dc:date>
    </item>
    <item>
      <title>Re: Help - Short Dump When Calling Standard SAP BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096192#M102199</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SAP hasn't released this BAPI (at least not in our &amp;lt;b&amp;gt;SRM&amp;lt;/b&amp;gt; system). But it's used in method if_crm_bsp_model_access_il~modify. So you might look there to see how it is used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Dec 2005 15:39:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096192#M102199</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-12T15:39:22Z</dc:date>
    </item>
    <item>
      <title>Re: Help - Short Dump When Calling Standard SAP BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096193#M102200</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you get this error the very first time you ran your program? Check in the table &amp;lt;b&amp;gt;BUT051&amp;lt;/b&amp;gt; whether an entry already exists for the combination you are trying to create!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Execute function module &amp;lt;b&amp;gt;BUPR_RELATIONSHIP_CHECK_EXIST&amp;lt;/b&amp;gt; for the same set of keys and see what message you get in the bapi return parameter.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Dec 2005 17:06:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096193#M102200</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-12T17:06:31Z</dc:date>
    </item>
    <item>
      <title>Re: Help - Short Dump When Calling Standard SAP BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096194#M102201</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I checked, the entry did not exist.&lt;/P&gt;&lt;P&gt;From further debugging this, it appears that if you call this function module multiple times with a COMMIt at the end each time, the memory does not get cleared.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example BUPR_RELATIONSHIP_CREATE calls BUS_BAPI_SAVE which takes no parameters.&lt;/P&gt;&lt;P&gt;This calls BUR_BUPR_UPDATE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The first time BUPR_RELATIONSHIP_CREATE is called, in BUR_BUPR_UPDATE internal table lt_but051 contains one entry, the first one. This relationship is then created and a COMMIT takes place.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The program then calls BUPR_RELATIONSHIP_CREATE to create the second relationship. When BUR_BUPR_UPDATE is called again, there are 2 entries in internal table lt_but051.&lt;/P&gt;&lt;P&gt;It then tries to create the relationships based on what is in this internal table.&lt;/P&gt;&lt;P&gt;Because the first entry has already been created, the short dump occurs and the second entry therefore does not get created.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP have commented out a piece of code previously and replaced it with new code, I guess this was to fix a bug. However I get a short dump.&lt;/P&gt;&lt;P&gt;See below from BUR_BUPR_UPDATE :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;   INSERT BUT051 FROM TABLE LT_BUT051 ACCEPTING DUPLICATE KEYS.&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;   IF SY-SUBRC &amp;lt;&amp;gt; 0.&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;     UPDATE BUT051 FROM TABLE LT_BUT051.&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;   ENDIF.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    INSERT but051 FROM TABLE lt_but051.&lt;/P&gt;&lt;P&gt;    IF sy-subrc &amp;lt;&amp;gt; 0.&lt;/P&gt;&lt;P&gt;      MESSAGE a855 WITH gc_tname_but051 ' ' ' ' ' '.&lt;/P&gt;&lt;P&gt;    ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Dec 2005 17:42:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096194#M102201</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-12T17:42:51Z</dc:date>
    </item>
    <item>
      <title>Re: Help - Short Dump When Calling Standard SAP BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096195#M102202</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok..I understand...so the itab in BUR_BUPR_UPDATE has to be cleared everytime we call this FM!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you know what is the use of export parameter &amp;lt;b&amp;gt;iv_x_save&amp;lt;/b&amp;gt;? May be try setting it to blank: &amp;lt;b&amp;gt;iv_x_save = ''&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Dec 2005 18:10:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096195#M102202</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-12T18:10:49Z</dc:date>
    </item>
    <item>
      <title>Re: Help - Short Dump When Calling Standard SAP BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096196#M102203</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sam,&lt;/P&gt;&lt;P&gt;iv_x_save = ' ' tells the fcn module not to actually make the change.&lt;/P&gt;&lt;P&gt;This is empty when IV_TESTRUN = 'X' and vice versa.&lt;/P&gt;&lt;P&gt;Rgds&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Dec 2005 09:32:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096196#M102203</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-13T09:32:34Z</dc:date>
    </item>
    <item>
      <title>Re: Help - Short Dump When Calling Standard SAP BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096197#M102204</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;has anybody got any clue how to proceed further&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Mar 2007 05:12:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096197#M102204</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-07T05:12:05Z</dc:date>
    </item>
    <item>
      <title>Re: Help - Short Dump When Calling Standard SAP BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096198#M102205</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;This is a SAP Bug probably. Use function module BAPI_TRANSACTION_COMMIT instead of commit work statement or CALL FUNCTION 'BUFFER_REFRESH_ALL' after commit work. This solves the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2008 15:43:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096198#M102205</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-19T15:43:37Z</dc:date>
    </item>
    <item>
      <title>Re: Help - Short Dump When Calling Standard SAP BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096199#M102206</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It may help to call the FM 'BUR_BUPR_EVENT_DLVE2' after completing all updates by FMs from function group BUD3 including those by BUR_BUPR_UPDATE. But be aware of locks' releases within FM '..._DLVE2'!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Feb 2011 13:49:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096199#M102206</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-24T13:49:32Z</dc:date>
    </item>
    <item>
      <title>Re: Help - Short Dump When Calling Standard SAP BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096200#M102207</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi David,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for BAPI, you should use funtion BAPI_TRANSACTION_COMMIT with parameter work = 'X' only. ASlso check the existence of the relationship before trying to create.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Feb 2011 14:30:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/help-short-dump-when-calling-standard-sap-bapi/m-p/1096200#M102207</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2011-02-24T14:30:42Z</dc:date>
    </item>
  </channel>
</rss>

