Runtime Error: sapsql_array_insert_duprec

Hi Everybody,
we are working on Trainingsystem for SAP FSCM.
We are using an IDES System with EhP4 for this purpose.
We are facing a Runtime Error when creating a new Collection Worklist. TC: UDM_GENWL
I have found the SAP note: 952367 which fits perectly to our issue.
But this note is valid only for FINBASIS 600.
We are working on FINBASIS 604.
Has anybody an Idea, what we con do here
Or has experience with this error?
Thanks a lot in advanced
Kind Regards
Oliver

I think you are trying to insert the record in the table for which there is already an entry exists in the table with the primary key specified.

Similar Messages

Runtime error SAPSQL_ARRAY_INSERT_DUPREC during migo

Hi Friends,
When I try doing MIGO with reference to a PO and save the document it gives me runtime error SAPSQL_ARRAY_INSERT_DUPREC.
I have check the buffer, and the no. range everything is perfect, but still i am getting this error.
Can anyone please give me the possible solution for this. Is there any SAP note that I need to apply.
Regards,
Wasim.

Hello Wasim,
The common cause of this termination is the material document
number range as per note 31793 - SAPSQL_ARRAY_INSERT_DUPREC.
So please check if the current numbers are synchronized with the
database tables:
OMBT trx x MKPF table
OMH6 trx x EKKO table
If it has the same number range the sort dump should not be raised
anymore.
The main root causes are:
-> when you are transporting number ranges from one client to another;
-> when you face a shut down in your system and you have defined a
buffer application server tolerance in transaction SNRO;
-> when you are doing the posting by using BAPI's and for some reason
the BAPI failed.
I hope it helps you.
Best Regards,
Fábio Almeida
MM Consultant

Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC in t-code KO02

Hi Guru,
I got runtime error in transaction KO02, below i given all the details.
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
    Use an ABAP/4 Open SQL array insert only if you are sure that none of
    the records passed already exists in the database.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
    "SAPLA02S" or "LA02SF00"
    "INSERT_ENTRIES"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
    In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"INSERT_ENTRIES" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
Information on where terminated
    Termination occurred in the ABAP program "SAPLA02S" - in "INSERT_ENTRIES".
    The main program was "RSM13000 ".
    In the source code you have the termination point in line 132
    of the (Include) program "LA02SF00".
    The program "SAPLA02S" was started in the update system.
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "INSERT_ENTRIES" "(FORM)", but it was neither handled locally nor
     declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLA02S "; its source code begins in line
    85 of the (Include program "LA02SF00 ".
Plz tell me if some one have idea to solve this problem,
Thanks,
Namdev

Hi,
check in the OSS and see if there is any note available:
e.g.
Note 78466 - RA_ASSET_MODIFIKATION - SAPSQL_ARRAY_INSERT_DUPREC
https://service.sap.com/sap/support/notes/78466
Best regards.

FP 05-Runtime Error-SAPSQL_ARRAY_INSERT_DUPREC

Hi experts
We are getting runtime error SAPSQLARRAY_INSERT_DUPREC_ while posting payments. We enter 500 items in the payment lot and when we select post payment lot 450 items were posted, 50 items not posted. None of the items (un posted 50 items) gone to clarification.
When we checked the ST22 and find the problem at below statement
INSERT DFKKOPK FROM TABLE DB_DFKKOPK.
Pl help me.
Regards
Srinivas

Hi Srinivas,
This short dump happens when the system tried to insert data into database table but the key is already exist or duplicate in the internal table.
The solution may be vary accoring to the root cause of the problem,
1) If it happen in QAS or DEV, it may be because some data has been copied from production and the key already exist in database table, you need to change the number range object for this.
2) Check the posting and user exits whether there is any duplicate in the posting or any logic to make it duplicates. Fix the posting or change the program logic for this problem.
3) Check OSS Note for this message. If you apply all the note and the problem still persists. Contact SAP Support to solve the problem.
Chaiphon

Getting runtime error SAPSQL_ARRAY_INSERT_DUPREC In production

Hi,
can somebody help me regarding below issue.i am abaper.
During SAP technical monitoring it has been noticed
that there are many System dumps SAPSQL_ARRAY_INSERT_DUPREC other terms in the dump file are SALLZED7, LZED7F01, and UPDATE_TORGUE_TABLE. The user is WF-BATCH and is in a dialogue session. Error Message : SAPSQL_ARRAY_INSERT_DUPREC
Report : SAPLZED7

Hello ,
Thanks for ur reply.
i am providing detailed dump information , please guide me if anything u get.
What happened?    The database system detected a deadlock and avoided it by rolling back
    your transaction.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
     in
    procedure "/TOPFLOW/BDE_ZPRM_VERBUCHER" "(FUNCTION)", nor was it propagated by
     a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    The database system recognized that your last operation on the database
    would have led to a deadlock.
    Therefore, your transaction was rolled back
    to avoid this.
    ORACLE always terminates any transaction that would result in deadlock.
    The other transactions involved in this potential deadlock
    are not affected by the termination.
How to correct the error
    Database error text........: "ORA-00060: deadlock detected while waiting for
     resource"
    Internal call code.........: "[RSQL/DELE//TOPFLOW/BTANM ]"
    Please check the entries in the system log (Transaction SM21).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "/TOPFLOW/SAPLBDE_ZPRM" or "/TOPFLOW/LBDE_ZPRMU25"
    "/TOPFLOW/BDE_ZPRM_VERBUCHER"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
Information on where terminated    Termination occurred in the ABAP program "/TOPFLOW/SAPLBDE_ZPRM" - in
     "/TOPFLOW/BDE_ZPRM_VERBUCHER".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 26
    of the (Include) program "/TOPFLOW/LBDE_ZPRMU25".
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "/TOPFLOW/BDE_ZPRM_VERBUCHER" "(FUNCTION)", but it was neither
     handled locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "/TOPFLOW/SAPLBDE_ZPRM "; its source code begins in
     line
    1 of the (Include program "/TOPFLOW/LBDE_ZPRMU25 ".

Runtime errors SAPSQL_ARRAY_INSERT_DUPREC

Hi Team,
We are facing daly batch jobs failure while planned to production order conversion (Programe-PPIO_Entry).I can found following analysis in ST22.Pleas help me to solve this problem.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
     in
    procedure "HEADER_POST" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.
Can anybody suggest what corrective action do i need to take.
Thanks in advance

Hi
The dump may happen due to incorrect current number in the number range interval.
e.g. the number range of produciton order, the highest number in the order table, e.g. AKFO, is 1000, but the current number assigned to the number range interval is 900, then the system will assign a new number 901 = 900 + 1 to the new order then the dump comes as the number 901 already exist in table AFKO. Please change the current number to the one higher than the highest number of table, e.g. 1001 then no dump will happen.
While creating the produciton order, several number range objects other than order number is called so you need check them as well. The SAP note 24097 includes a report which can get the hightest number of tabls for the objects can be checked.
Here is the detail of the note and the report for your reference.
Long text
Symptom
When you create a production order, the system generates error message:
"ERROR DURING STATUS_UPDATE" The update was canceled
ABAP processor: SAPSQL_ARRAY_INSERT_DUPREC;
The termination occurred in the ABAP/4 program "SAPLBSVU"
Additional key words
CO01, CO40, CO41, MD04, VA01, COR1, Create order
Cause and prerequisites
The copying of sales order data between clients means that objects were
transferred with numbers that are higher than the current status of the
respective number range objects in the target client. When a new order
is created, number assignment according to the status of the number
range objects results in double entries.
Solution
You must adapt the status of the number range objects according to the
copied data: In the configuration menu of Master Planning (Transaction
OLPF) under Master Data -> Order -> Number ranges (Transactions CO80,
CO81, CO82, CO83, CY89).
You can transport the statuses of the number range objects from the
source client of your copied sales order data into the target client.
However, you should always be careful when changing the number ranges
since multiple assignment of the same numbers can result in IRREPARABLE
inconsistencies in your system.
You should only ever INCREASE the current status of a number range
object !!!
You can determine the highest number status of the respective objects
with attached selection report. For the order numbers, you must note
that the highest current number status can only be determined correctly
if no external number assignment was used.
REPORT DETMAXNO.
This report determines the highest numbers of order dependent number *
ranges like order number, confirmation number, reservation number,   *
operation number, capacity requirement number.                       *
Attention: the maximum order number determined by this report is     *
           only valid if you only use internal numbers
TABLES: AUFK, AFKO, AFVC, RESB, KBED.
DATA: ORD_MAX   LIKE AUFK-AUFNR,
        CONF_MAX LIKE AFKO-RUECK,
        CONF_MAX1 LIKE AFKO-RUECK,
        RSNUM_MAX LIKE RESB-RSNUM,
        AUFPL_MAX LIKE AFVC-AUFPL,
        BEDID_MAX LIKE KBED-BEDID.
                                                                  Page 3
maximum order number
   SELECT MAX( AUFNR ) FROM AUFK INTO ORD_MAX.
   IF SY-SUBRC IS INITIAL.
     WRITE: / 'Max. of order numbers: ', ORD_MAX.
   ENDIF.
maximum confirmation number
   SELECT MAX( RUECK ) FROM AFVC INTO CONF_MAX.          "operation conf.
   SELECT MAX( RUECK ) FROM AFKO INTO CONF_MAX1.            "header conf.
   IF SY-SUBRC IS INITIAL.
     IF CONF_MAX1 > CONF_MAX.
       CONF_MAX = CONF_MAX1.
     ENDIF.
     WRITE: / 'Max. of confirmation numbers: ', CONF_MAX.
   ENDIF.
maximum reservation number
   SELECT MAX( RSNUM ) FROM RESB INTO RSNUM_MAX.
   IF SY-SUBRC IS INITIAL.
     WRITE: /'Max. of reservation number: ', RSNUM_MAX.
   ENDIF.
maximum operation number
   SELECT MAX( AUFPL ) FROM AFVC INTO AUFPL_MAX.
    IF SY-SUBRC IS INITIAL.
      WRITE: /'Max. operation number: ', AUFPL_MAX.
    ENDIF.
maximum capacity requirement number
    SELECT MAX( BEDID ) FROM KBED INTO BEDID_MAX.
    IF SY-SUBRC IS INITIAL.
      WRITE: /'Max. capacity requirement number: ', BEDID_MAX.
    ENDIF.

ABAP runtime errors    SAPSQL_ARRAY_INSERT_DUPREC

Hi,
Its a production dump.I know the functionality of this dump.
But my question is program [SAPLZED7] in the dump doesn't exist in the system.I am also forwarding details below replated to dump.Please give some hint how to solve it??
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
The current ABAP/4 program "SAPLZED7 " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"SAPSQL_ARRAY_INSERT_DUPREC"
"SAPLZED7 " or "LZED7F01 "
"UPDATE_TORQUE_TABLE"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.

Sometimes, the DUPREC is due to SNRO problem.
if you have several document type link to the same object number, the program could tries to insert a number already taked
(I don't look your program)
Regards

AFAB ABAP runtime error SAPSQL_ARRAY_INSERT_DUPREC

Hi,
Please, can somebody help me?
When running AFAB for period 08 2009, the job gets cancelled and the job log says: The ABAP/4 Open SQL array insert results in duplicate database records.
If you use an ABAP/4 Open SQL array insert to insert a record in the database and that record already exists with the same key, this results in a termination.
I already checked SAP notes and I cannot find a solution to run the depreciation for period 08 without getting the error.
Regards*

Hello,
Please check if the following notes are useful
Note 1093774 - Entries created incorrectly in table ANLBZA
Note 118731 - Transfer: Inconsistencies in Customizing
If still you cannot resolved this issue, then you can please raise a call with SAP (high priority)
Regards,
Ravi

SAPSQL_ARRAY_INSERT_DUPREC - ABAP runtime error

Dear Experts,
I am getting a abap dump.
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Exception CX_SY_OPEN_SQL_DB
Error analysis |
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", nor was it propagated
by a RAISING clause.
Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated. The reason for the exception is: If you use an ABAP/4 Open SQL array insert to insert a record in the database and that record already exists with the same key, this results in a termination.
Information on where terminated
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
Termination occurred in the ABAP program "SAPLSBAL_DB_INTERNAL" - in
"BAL_DB_INTERNAL_NO_UPDATE_TASK". The main program was "SWNCCOLL ".
In the source code you have the termination point in line 64
of the (Include) program "LSBAL_DB_INTERNALU02".
The program "SAPLSBAL_DB_INTERNAL" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "SAPADMIN"
Job Number..... 16160100
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", but it was neither
handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "SAPLSBAL_DB_INTERNAL "; its source code begins in
line
1 of the (Include program "LSBAL_DB_INTERNALU02 ".
Please give me your suggestions to sort out this problem
Thanks in advance
Venkat

Check note 196113 it contains the solution to your problem.
Most of the time this issue is due to a mismatch between the last assigned log number in table BALHDR and the one in the number range object.

SAPSQL_ARRAY_INSERT_DUPREC Runtime error

I am getting following error what could be the error please suggest me.
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
Date and Time          18.08.2010 20:39:30
Short text
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in the ABAP Application Program
The current ABAP program "/SAPAPO/SAPLDM_MATERIAL" had to be terminated because
it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "/SAPAPO/DM_PRODUCTS_POST" "(FUNCTION)", nor was it propagated by a
RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
"/SAPAPO/SAPLDM_MATERIAL" or "/SAPAPO/LDM_MATERIALU46"
"/SAPAPO/DM_PRODUCTS_POST"
|

Dear
this dump can have several reasons.
If you are on SCM7.0 and you have implemented the BADI solution of note 918542 , this can be the rootcause of the problem. The solution is covered in the standard on SCM7.0 and not neccessary anymore for this SCM release.
Due to the BADI, the system tries to create the products twice (in BADI and in standard) which leads to the SQL error. If this is you case could you please deimplement the BADI solution? You can process the queue afterwards which should go through without any error.
The problem can also happen due to a user exit e.g. EXIT_SAPLCMAT_001.
Regards,
Tibor

While trying to change a BOM with transaction CS02, a runtime error appears

While trying to change a BOM with transaction CS02, a runtime error appears.
In intial screen he entered material ,plant BOM usage and date valid from after executed then id displayed item list in that he wantu2019s delete one item, he has been deleted selected item after that when he was saving he is getting runtime error
Developer trace
ABAP Program SAPLKED1_WRITE_CE4_BPS1                 .
Source LKED1_WRITE_CE4_BPS1U01                  Line 30.
Error Code SAPSQL_ARRAY_INSERT_DUPREC.
Module $Id: //bas/640_REL/src/krn/runt/absapsql.c#17 $ SAP.
Function HandleRsqlErrors Line 775.
RABAX: level LEV_RX_STDERR completed.
RABAX: level LEV_RX_RFC_ERROR entered.
RABAX: level LEV_RX_RFC_ERROR completed.
RABAX: level LEV_RX_RFC_CLOSE entered.
RABAX: level LEV_RX_RFC_CLOSE completed.
RABAX: level LEV_RX_IMC_ERROR entered.
RABAX: level LEV_RX_IMC_ERROR completed.
RABAX: level LEV_RX_DATASET_CLOSE entered.
RABAX: level LEV_RX_DATASET_CLOSE completed.
RABAX: level LEV_RX_RESET_SHMLOCKS entered.
RABAX: level LEV_RX_RESET_SHMLOCKS completed.
RABAX: level LEV_RX_ERROR_SAVE entered.
RABAX: level LEV_RX_ERROR_SAVE completed.
RABAX: level LEV_RX_ERROR_TPDA entered.
RABAX: level LEV_RX_ERROR_TPDA completed.
RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
RABAX: level LEV_RX_END entered.
RABAX: level LEV_RX_END completed.
RABAX: end RX_RFC
In sm21
Perform rollback
Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
     Short dump "090618 110101 donalda 11557 " generated
Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
       Occurred on     18.06.2009 at   11:01:01
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLKED1_WRITE_CE4_BPS1" had to be terminated because
one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"RKE_WRITE_CE4__BPS1" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
The exception must either be prevented, caught within the procedure
"RKE_WRITE_CE4__BPS1"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
"SAPLKED1_WRITE_CE4_BPS1" or "LKED1_WRITE_CE4_BPS1U01"
"RKE_WRITE_CE4__BPS1"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.

Hi ,
you are getting beacuse u are trying to do mass update to database.
Please check that below note are applicable to your system.
Note 453313 - DBIF_RSQL_ERROR_INTERNAL for mass insert
Note 869534 - AFS MRP doesn't work properly with all BOM item categories
Thanks Rishi Abrol

FI-SL error SAPSQL_ARRAY_INSERT_DUPREC during direct posting to the SL.

I am working on FI- Special Ledger and currently encountering an error:
I am trying to post journals to the special purpose ledger using a local file where I am encountering the following error:
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "INS_XXXXXA" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
XXXXXA is the custom database table name.
The form mentioned is a item table for one the special ledger which has been custom defined.
I have debugged the code and found out the following:
1. There are two records which needs to be updated to the items table of the ledger.
2. When I checked the items table the key value (which needs to be updated) doesn't exist currently.
3. I saw some resolution on the number range definition which i tried to apply but not fruitful.
Although the new records which needs to be inserted to the database table is not there I am getting the error SAPSQL_ARRAY_INSERT_DUPREC.
Please let me know of any suggestion to resolve the issue.
I might have not correctly implemented the solution for the number range.
Your valuable suggestions will be awarded accordingly.
Also let me know if anymore clarity is required.
Kind Regards,
himansu roy

Hello everyone,
Got the issue and resolution.
The problem was in the custom code the ledger update was happening twice so the duplicate entries were giving dump during the COMMIT.
Regards,
Himansu Roy

Run-time error SAPSQL_ARRAY_INSERT_DUPREC occurred

When creating a new SyncBo (T51) instance after syncing eventually MI Clients shows the following message:
[20070315 01:28:14:343] E [MI/Sync ] Received exception info code 10 and detailed message "Exception while callSync: The ABAP/4 Open SQL arrayinsert results in duplicate database records. records in the data base."
In sm21 shows message:
AB0 Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
AB1 > Short dump "070316 205056 sapnw ELDA " generated
Looking for SAPSQL_ARRAY_INSERT_DUPREC error in SAP Note we found the note 817849 (Runtime error SAPSQL_ARRAY_INSERT_DUPREC occurs during sync).
We have downloaded and applied this note in Backend as note requires and ALL prerequisites of this note. Also we have upgraded to SP19 and Kernel to 155 (part 1 and 2). But problem continues and the client that happened this problem does not work any more, all new SyncBO instances created goes to MEREP_MON as Waiting status.
The dump on duplicate record is happening when the user is synchronizing and when a record is getting inserted to table merep_10100.
The solution /workaround could be to do a client reset for those devicesand test again and see if it is happening, but error returns happening after this.
When this happen SyncBo instance keeps on Waiting status (MEREP_MON). We couldn't understand why this happen suddenly and then no more new SyncBo could be created, all goes to Waiting status. Reprocess (ShiftF5) or start handler (Shift10) does not take any effect.
Best Regards,
Rogério

Hi Ajith
I am getting the same error and below is the error message from ST22. The only change is I am using for MTR application and the sync fails for the 2nd time when synched for patches for the MTR application. As it is generic sync, could you please advice to get rid of the problem.
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"LOG_INSERT_DB" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
Thanks, Raj

Transaction Code F.50 Runtime Error

Dear Friends,
While executing T.code F.50, I am getting the following Error
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Exceptn                CX_SY_OPEN_SQL_DB
Date and Time          25.06.2009 11:27:31
ShrtText
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLF049" had to be terminated because one of the
     statements could not be executed.
This is probably due to an error in the ABAP program.
Error analysis
An exception occurred. This exception is dealt with in more detail below
     . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
      neither
caught nor passed along using a RAISING clause, in the procedure
      "SICHERN_IN_DB" "(FORM)"
Since the caller of the procedure could not have expected this exception
      to occur, the running program was terminated.
     The reason for the exception is:
     If you use an ABAP/4 Open SQL array insert to insert a record in
     the database and that record already exists with the same key,
     this results in a termination.
      (With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
Program                                 SAPLF049
Include                                 LF049F00
Row                                     74
Module type                             (FORM)
Module Name                             SICHERN_IN_DB
gger Location of Exception
Program                                 SAPLF049
Include                                 LF049F00
Row                                     86
Module type                             (FORM)
Module Name                             SICHERN_IN_DB
rce Code Extract
e SourceCde
56 *      Insert von RF048 aus CRF048 (bei Commit Work)                   *
57 *----
58 FORM RELATION_SAVE.
59
60   CHECK NOT CRF048[] IS INITIAL.
61   INSERT RF048 FROM TABLE CRF048.
62   REFRESH CRF048.
63
64 ENDFORM.                    "RELATION_SAVE
65
66
67
68 *eject
69 *----
70 *      Form SICHERN_IN_DB                                             *
71 *----
72 *      Masseninsert/update aus Z-Tabellen                              *
73 *----
74 FORM SICHERN_IN_DB.
75
76 * Lokale Daten
77 DATA:
78       ld_xnetb   TYPE xnetb,
79       anz_belnr TYPE i.
80
81 *------ Aufteilungstabellen -
82
83 * Einfügen                                                             *
84
85 * BFIT_A0
>>>   INSERT BFIT_A0 FROM TABLE ZBFIT_A0.
87   IF SY-SUBRC <> 0.
88     MESSAGE A153.
89   ENDIF.
90
91 * BFIT_A
92   INSERT BFIT_A FROM TABLE ZBFIT_A.
93   IF SY-SUBRC <> 0.
94     MESSAGE A154.
95   ENDIF.
96
97 * BFOD_A
98   INSERT BFOD_A FROM TABLE ZBFOD_A.
99   IF SY-SUBRC <> 0.
100     MESSAGE A155.
101   ENDIF.
102
103 * BFOD_AB
104   INSERT BFOD_AB FROM TABLE ZBFOD_AB.
105   IF SY-SUBRC <> 0.
How to reslove the error? Please advise.
Thanks and Regards
Sridhar

Hi,
Well it looks quite difficult to understand.......The only thing it says clearly that this is happening because of duplicate Primary Key insertion.

Runtime Error while creating FINANCIAL STATEMENT VERSION

Hi Experts,
The major concern of the problem is related with the new creation of FINANCIAL STATEMENT VERSION.
(SPRO --> IMG --> Financial Accounting --> General Ledger Accounting --> Business Transactinons --> Closing > Document> Define Financial Statement Versions.)
My quries is that is it possiable to maintain more then one FSV for the same company code or for same chart of account.
If yes then we are trying to do it . But the problem reflect, be the indication that we can`t maintain more then one code.
Its giving an runtime error
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB
Date and Time          15.03.2008 18:36:04
Short text
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLFAGL_FSV" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
      in
procedure "FSV_TEXTS_CONVERT" "(FORM)", nor was it propagated by a RAISING
      clause.
Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     If you use an ABAP/4 Open SQL array insert to insert a record in
     the database and that record already exists with the same key,
     this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
     situation, processing does not terminate, but SY-SUBRC is set to 4.)
We are trying Its giving an abap dump
Rest the technicall aspect that is comming in ABAP Dump i am not
getting.....so pls inquire according to yourself.
Kind Regards,
Sudhanshu

Hello
Logically speaking, a company code can have more than one FSV as long as they share the same chart of accounts.
When COA is common, the FSV pattern can be designed seperatly to serve the purpose of varied reporting.
The dump you are getting is a temporary snag. Take a screen shot from SM54 after you execute the report and pass it to BASIS for analysis. They would fix that.
Reg
assign points if useful

Runtime Error: sapsql_array_insert_duprec

Similar Messages

Maybe you are looking for