Runtime Error on CJ20n -- SAPSQL_ARRAY_INSERT_DUPREC

Hi, would like to ask what is the nature and how to resolve this error we've encountered when we're adding a new wbs element.
"Runtime error u201CSAPSQL_ARRAY_INSERT_DUPRECu201D usually occurs in transaction CJ20N and as a result , the system creates a pending Update on the sap table. "

Please refer this Consulting note.
Note 780035 - CN22: Update Termination SAPSQL_ARRAY_INSERT_DUPREC
In recent time I faced similar problem. When you use any BADI or User exit for the project structure, at that time your custom code is Hindering SAP Code, due to it sometimes your PS object not able to get the system status or internal object no. At that time these type of error comes.
For your reference Please go though below thread.
No object Status is available
With Regards
Nitin P.

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

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

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.

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.

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

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

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

Dump error during CK24 - SAPSQL_ARRAY_INSERT_DUPREC

Hi SAP Gurus,
i am facing problem during the material updation (T.Code CK24). before that i have done the material cost estimation then try to update material master by using t.code CK24. the following dump error occurs:
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB
Date and Time          19.06.2008 11:05:00
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 "SAPLKAUP" 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 "INSERT_TABLES" "(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.)
Missing RAISING Clause in Interface
Program                                 SAPLKAUP
Include                                 LKAUPF01
Row                                     397
Module type                             (FORM)
Module Name                             INSERT_TABLES
Trigger Location of Exception
Program                                 SAPLKAUP
Include                                 LKAUPF01
Row                                     464
Module type                             (FORM)
Module Name                             INSERT_TABLES
Source Code Extract
Line
SourceCde
434
ENDIF.
435
    Do not write empty CO document headers for parked documents!!
436
    --> ugly coding but it looks like that "empty" headers are
437
        possible in some circumstances
438
IF GD_PARKED_DOCUMENT = 'X' AND
439
COBK_INS-SUMBZ = 0 AND
440
COBK_INS-ALEBZ = 0.
441
DELETE COBK_INS.
442
CONTINUE.
443
ENDIF.
444
    DELBZ setzen
445
COBK_INS-DELBZ = 0.
446
    CPUDT/CPUTM setzen
447
    IF COBK_INS-CPUDT IS INITIAL
448
    OR COBK_INS-CPUTM IS INITIAL.
449
COBK_INS-CPUDT = SY-DATUM.
450
COBK_INS-CPUTM = SY-UZEIT.
451
    ENDIF.
452
    TIMESTMP setzen
453
    IF COBK_INS-TIMESTMP IS INITIAL.
454
COBK_INS-TIMESTMP = GD_TIMESTMP.
455
    ENDIF.
456
    USNAM setzen
457
IF COBK_INS-USNAM IS INITIAL.
458
COBK_INS-USNAM = SY-UNAME.
459
ENDIF.
460
    Aenderungen merken
461
MODIFY COBK_INS.
462
ENDLOOP.
463
.....COBK verbuchen...................................................
|>>>>>|    INSERT COBK FROM TABLE COBK_INS.                                                       |
465
noch kein REFRESH fuer COBK_INS -> wird noch fuer ALE gebraucht
466
ENDIF.
467
468
.....ggf. Einzelposten versenden......................................
469
IF NOT ALE[] IS INITIAL.
470
LOOP AT ALE.
471
PERFORM SEND_DOCUMENT USING ALE-KOKRS ALE-BELNR ALE-LOGSYSO.
472
    --> COBK_INS, COEP_INS und COEPL_INS werden hier gebraucht!
473
ENDLOOP.
474
REFRESH ALE.
475
ENDIF.
476
477
.....COEP verbuchen...................................................
478
IF NOT COEP_INS[] IS INITIAL AND GB_LATE_COEP_INS <> ON.
479
INSERT COEP FROM TABLE COEP_INS.
480
REFRESH COEP_INS. "REFRESH wird in UPDATE_TABLES gemacht!
481
ENDIF.
482
483
.....COEPL verbuchen..................................................
please help me to overcome this problem.
point will be rewarded
Than'x
Dhananjay

Hi,
Please provide me the solution for the above issue , I am also facing the same, what excatly is the remedy for this.
regards
Ritesh

ABAP Runtime Error Intermediate Save

Hello ,
I have an issue regarding following message that i see in the ABAP Runtime Error
A RAISE statement in the program "SAPLCOVG" raised the exception
condition "NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.
The system is giving as solution :
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:
"RAISE_EXCEPTION" " "
"SAPLCOVG" or "LCOVGU39"
"CO_VG_NETWORK_INIT_EXTERN_CALL"
or
"SAPLCOVG" "NOT_FOUND"
or
"SAPLCNPB_M " "NOT_FOUND"
This problem is situated in the CJ20N Project Builder with doing the intermediate Save
I have downloaded some notes but no implementation done .
What is the solution ?
Thank you
Davy

Hi Davy,
Please check SAP note 1461867.
Regards
Shrikant

AFAB: Runtime Error after client copy.

Hi all,
I'm having a problem with the transaction code AFAB (post client copy). After client copy from PRD to DEV, I'm encountering this runtime error "SAPSQL_ARRAY_INSERT_DUPREC - The ABAP/4 Open SQL array insert results in duplicate database records." whenever I tried to perform AFAB. Test run was executed successfully but I cannot complete the actual background processing.
I have try with other asset (in the same client) and encounter the same problem. Likewise, I have successfully completed the depre. if I try the same and other asset (in a different client on the same server).
I've check the number range in FBN1 and have verified that the range is correct.
Any advice as to how I can solve this problem?
Thank you.
Regards.
p/s: if there is duplication, how do I find where the duplication is located and how do I remove this duplication?
p/s 2: the standard SQL that is having this problem is "INSERT COBK FROM TABLE COBK_INS."
Edited by: Sek Yao Ooi on Aug 5, 2010 5:21 AM

Solution obtain from snote-83731 ; thanks to SAP-Marketplace's support.
Issue solved.

Urgent : Runtime error

hi All Gurus,
i am getting Runetime error while going to convert planned order to process order by using T.Code: MD04.
Error :
"Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB"
"|ShrtText                                                                                |
|    The ABAP/4 Open SQL array insert results in duplicate database records.                      -
|What happened?
Error in ABAP application program.
The current ABAP program "SAPLM61U" had to be terminated because one of the
statements could not be executed.
|    This is probably due to an error in the ABAP program.    "
it comes while Saving the order. Sometimes it saves order and sometime it gives error.
Another problem is that sometimes it is picking wrong production version.
plz help ASAP.
thnaks

Hi
This is ABNAP issue.
you better coordinate with your technical team memebr who can analise & solve.
Regartds
YMREDDY

Dump error in mb1a(SAPSQL_ARRAY_INSERT_DUPREC)

Dear Friends,
                       We got a dump error(SAPSQL_ARRAY_INSERT_DUPREC)
                       when relesing particular material of the production order in mb1a. the detail error is as follows.
ABAP runtime errors    SAPSQL_ARRAY_INSERT_DUPREC
"SAPSQL_ARRAY_INSERT_DUPREC"
"SAPLIEP1 " or "LIEP1U04 "
"REMAINDER_OF_EQUI_POST"
SAP Release.............. "46C"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "8x Intel 80686"
Database type............ "ORACLE"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "46D"
Created on............... "Jul 10 2006 21:36:37"
Created in............... "NT 4.0 1381 Service Pack 6 x86 MS VC++ 12.00"
Database version......... "OCI_920_SHARE__OCI_7_API "
Patch level.............. "2257"
Patch text............... " "
Transaction......... "MB1A "
000010   FUNCTION REMAINDER_OF_EQUI_POST.
000020   *"
000030   ""Verbuchungsfunktionsbaustein:
000040   *"
000050   ""Lokale Schnittstelle:
000060   *"       TABLES
000070   *"              SEREQUZ STRUCTURE EQUZ
000080   *"              SERILOA STRUCTURE ILOA
000090   *"              SEREQKT STRUCTURE EQKT
000100   *"
000110   DATA: RECORDS_POST LIKE SY-DBCNT.
000120   * Anzahl der zu verbuchenden Sätze fest
000130     DESCRIBE TABLE SEREQUZ LINES RECORDS_
000140
000150   * Zeitsegmente hinzufügen
000160
     >     INSERT EQUZ FROM TABLE SEREQUZ.
please let me know if you know the solution.
Thanks and Regards,
Shans.

Go to transaction code OMBT, click view "Intervals" and make sure the number range for previous fiscal year and current fiscal year is not clashing.
for example:
Year        From Number   To Number      Current Number
2010     4900000000     4999999999     5000533839
2011      5000000000     5999999999     5000135509
In the above case it will give this dump SAPSQL_ARRAY_INSERT_DUPREC. There may be other reason also.
You can also follow this method
Go to T-code SE16N and input table name MKPF.
Step find: Find the highest material document number.
Go to T-code SNUM or SNRO.and Input object MATBELEG ( direct OMBT)
Click on 'Number ranges' button.
Click on 'Intervals' button.
Check 'Current number'
Now compare it with the highest material document number of STEP FIND.
Change 'Current number' to a higher number.
From my experience this normally happens when number ranged is transported from DEV to PRD accidentally during some IMG config.

Runtime Error on CJ20n -- SAPSQL_ARRAY_INSERT_DUPREC

Similar Messages

Maybe you are looking for