<?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 Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-sapsql-array-insert-duprec/m-p/6191468#M1374716</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i am getting short dumps in ecc system during data extraction to bi system. please provide me any related notes or suggestions to resolve the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;short dump details as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Short text&lt;/P&gt;&lt;P&gt;    The ABAP/4 Open SQL array insert results in duplicate database records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What happened?&lt;/P&gt;&lt;P&gt;    Error in the ABAP Application Program&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    The current ABAP program "SAPLEDI1" had to be terminated because it has&lt;/P&gt;&lt;P&gt;    come across a statement that unfortunately cannot be executed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What can you do?&lt;/P&gt;&lt;P&gt;    Note down which actions and inputs caused the error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    To process the problem further, contact you SAP system&lt;/P&gt;&lt;P&gt;    administrator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    Using Transaction ST22 for ABAP Dump Analysis, you can look&lt;/P&gt;&lt;P&gt;    at and manage termination messages, and you can also&lt;/P&gt;&lt;P&gt;    keep them for a long time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error analysis&lt;/P&gt;&lt;P&gt;    An exception occurred that is explained in detail below.&lt;/P&gt;&lt;P&gt;    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught&lt;/P&gt;&lt;P&gt;     in&lt;/P&gt;&lt;P&gt;    procedure "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)", nor was it propagated by a&lt;/P&gt;&lt;P&gt;     RAISING clause.&lt;/P&gt;&lt;P&gt;    Since the caller of the procedure could not have anticipated that the&lt;/P&gt;&lt;P&gt;    exception would occur, the current program is terminated.&lt;/P&gt;&lt;P&gt;    The reason for the exception is:&lt;/P&gt;&lt;P&gt;    If you use an ABAP/4 Open SQL array insert to insert a record in&lt;/P&gt;&lt;P&gt;    the database and that record already exists with the same key,&lt;/P&gt;&lt;P&gt;    this results in a termination.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    (With an ABAP/4 Open SQL single record insert in the same error&lt;/P&gt;&lt;P&gt;    situation, processing does not terminate, but SY-SUBRC is set to 4.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to correct the error&lt;/P&gt;&lt;P&gt;    Use an ABAP/4 Open SQL array insert only if you are sure that none of&lt;/P&gt;&lt;P&gt;    the records passed already exists in the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    If the error occures in a non-modified SAP program, you may be able to&lt;/P&gt;&lt;P&gt;    find an interim solution in an SAP Note.&lt;/P&gt;&lt;P&gt;    If you have access to SAP Notes, carry out a search with the following&lt;/P&gt;&lt;P&gt;    keywords:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"&lt;/P&gt;&lt;P&gt;    "SAPLEDI1" or "LEDI1F09"&lt;/P&gt;&lt;P&gt;    "F09_IDOC_INSERT_WITH_NUMBER"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    If you cannot solve the problem yourself and want to send an error&lt;/P&gt;&lt;P&gt;    notification to SAP, include the following information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    1. The description of the current problem (short dump)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       To save the description, choose "System-&amp;gt;List-&amp;gt;Save-&amp;gt;Local File&lt;/P&gt;&lt;P&gt;    (Unconverted)".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    2. Corresponding system log&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       Display the system log by calling transaction SM21.&lt;/P&gt;&lt;P&gt;       Restrict the time interval to 10 minutes before and five minutes&lt;/P&gt;&lt;P&gt;    after the short dump. Then choose "System-&amp;gt;List-&amp;gt;Save-&amp;gt;Local File&lt;/P&gt;&lt;P&gt;3. If the problem occurs in a problem of your own or a modified SAP&lt;/P&gt;&lt;P&gt;program: The source code of the program&lt;/P&gt;&lt;P&gt;   In the editor, choose "Utilities-&amp;gt;More&lt;/P&gt;&lt;P&gt;Utilities-&amp;gt;Upload/Download-&amp;gt;Download".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. Details about the conditions under which the error occurred or which&lt;/P&gt;&lt;P&gt;actions and input led to the error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The exception must either be prevented, caught within proedure&lt;/P&gt;&lt;P&gt;"F09_IDOC_INSERT_WITH_NUMBER" "(FORM)", or its possible occurrence must be&lt;/P&gt;&lt;P&gt; declared in the&lt;/P&gt;&lt;P&gt;RAISING clause of the procedure.&lt;/P&gt;&lt;P&gt;To prevent the exception, note the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;there  is no note mentioned here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Kasi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 29 Sep 2009 09:58:48 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-09-29T09:58:48Z</dc:date>
    <item>
      <title>Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-sapsql-array-insert-duprec/m-p/6191468#M1374716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i am getting short dumps in ecc system during data extraction to bi system. please provide me any related notes or suggestions to resolve the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;short dump details as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Short text&lt;/P&gt;&lt;P&gt;    The ABAP/4 Open SQL array insert results in duplicate database records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What happened?&lt;/P&gt;&lt;P&gt;    Error in the ABAP Application Program&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    The current ABAP program "SAPLEDI1" had to be terminated because it has&lt;/P&gt;&lt;P&gt;    come across a statement that unfortunately cannot be executed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What can you do?&lt;/P&gt;&lt;P&gt;    Note down which actions and inputs caused the error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    To process the problem further, contact you SAP system&lt;/P&gt;&lt;P&gt;    administrator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    Using Transaction ST22 for ABAP Dump Analysis, you can look&lt;/P&gt;&lt;P&gt;    at and manage termination messages, and you can also&lt;/P&gt;&lt;P&gt;    keep them for a long time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error analysis&lt;/P&gt;&lt;P&gt;    An exception occurred that is explained in detail below.&lt;/P&gt;&lt;P&gt;    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught&lt;/P&gt;&lt;P&gt;     in&lt;/P&gt;&lt;P&gt;    procedure "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)", nor was it propagated by a&lt;/P&gt;&lt;P&gt;     RAISING clause.&lt;/P&gt;&lt;P&gt;    Since the caller of the procedure could not have anticipated that the&lt;/P&gt;&lt;P&gt;    exception would occur, the current program is terminated.&lt;/P&gt;&lt;P&gt;    The reason for the exception is:&lt;/P&gt;&lt;P&gt;    If you use an ABAP/4 Open SQL array insert to insert a record in&lt;/P&gt;&lt;P&gt;    the database and that record already exists with the same key,&lt;/P&gt;&lt;P&gt;    this results in a termination.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    (With an ABAP/4 Open SQL single record insert in the same error&lt;/P&gt;&lt;P&gt;    situation, processing does not terminate, but SY-SUBRC is set to 4.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to correct the error&lt;/P&gt;&lt;P&gt;    Use an ABAP/4 Open SQL array insert only if you are sure that none of&lt;/P&gt;&lt;P&gt;    the records passed already exists in the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    If the error occures in a non-modified SAP program, you may be able to&lt;/P&gt;&lt;P&gt;    find an interim solution in an SAP Note.&lt;/P&gt;&lt;P&gt;    If you have access to SAP Notes, carry out a search with the following&lt;/P&gt;&lt;P&gt;    keywords:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"&lt;/P&gt;&lt;P&gt;    "SAPLEDI1" or "LEDI1F09"&lt;/P&gt;&lt;P&gt;    "F09_IDOC_INSERT_WITH_NUMBER"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    If you cannot solve the problem yourself and want to send an error&lt;/P&gt;&lt;P&gt;    notification to SAP, include the following information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    1. The description of the current problem (short dump)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       To save the description, choose "System-&amp;gt;List-&amp;gt;Save-&amp;gt;Local File&lt;/P&gt;&lt;P&gt;    (Unconverted)".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    2. Corresponding system log&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       Display the system log by calling transaction SM21.&lt;/P&gt;&lt;P&gt;       Restrict the time interval to 10 minutes before and five minutes&lt;/P&gt;&lt;P&gt;    after the short dump. Then choose "System-&amp;gt;List-&amp;gt;Save-&amp;gt;Local File&lt;/P&gt;&lt;P&gt;3. If the problem occurs in a problem of your own or a modified SAP&lt;/P&gt;&lt;P&gt;program: The source code of the program&lt;/P&gt;&lt;P&gt;   In the editor, choose "Utilities-&amp;gt;More&lt;/P&gt;&lt;P&gt;Utilities-&amp;gt;Upload/Download-&amp;gt;Download".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. Details about the conditions under which the error occurred or which&lt;/P&gt;&lt;P&gt;actions and input led to the error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The exception must either be prevented, caught within proedure&lt;/P&gt;&lt;P&gt;"F09_IDOC_INSERT_WITH_NUMBER" "(FORM)", or its possible occurrence must be&lt;/P&gt;&lt;P&gt; declared in the&lt;/P&gt;&lt;P&gt;RAISING clause of the procedure.&lt;/P&gt;&lt;P&gt;To prevent the exception, note the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;there  is no note mentioned here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Kasi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Sep 2009 09:58:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-sapsql-array-insert-duprec/m-p/6191468#M1374716</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-29T09:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-sapsql-array-insert-duprec/m-p/6191469#M1374717</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 are trying to add a duplicate record to some table.&lt;/P&gt;&lt;P&gt;I.e a record already exists in your databasde with same set of primary keys.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the dump log in ST22, it will give you the table name as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps,&lt;/P&gt;&lt;P&gt;Raj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Sep 2009 10:01:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-sapsql-array-insert-duprec/m-p/6191469#M1374717</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-29T10:01:16Z</dc:date>
    </item>
    <item>
      <title>Re: Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-sapsql-array-insert-duprec/m-p/6191470#M1374718</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi kasi, &lt;/P&gt;&lt;P&gt;The origin of the problem can be the number of idocs in the system. I fixed this error in a customer installation using the we11 to remove old idocs (before 2011).&lt;/P&gt;&lt;P&gt;kind regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Mar 2012 16:28:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-errors-sapsql-array-insert-duprec/m-p/6191470#M1374718</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-03-06T16:28:52Z</dc:date>
    </item>
  </channel>
</rss>

