Run time error : sapsql_array_insert_duprec

Hello Experts,

While creating orders in PP, PM, and PS module the system is throwing error as "Update was terminated". In ST22 it throws the dump as RUNTIME ERROR : sapsql_array_insert_duprec.</b> The data is not stored in the table while the number range for perticular order is get consumed. we have checked the number ranges, there is no inconsistancies with the number ranges, no upgradation

have been done also we haven't transfered any kind of data from

external system.

Please reply as soon as possible.

Thanking you in advance.

Amit sirsath

SAP Managed Tags:
NW AS Java Administrator (NWA)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (3)

Hi Amit,

Update error is due to insertion of duplicate record which also resulted in ABAP Dumps.

Could you update us with error details from SM13 ?

Regards,
Sreeni

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Sreeni,

Thanks for your fast response.

The following are the Error details of SM13:

Module Name(Function): STATUS_UPDATE

Type: V1

Update Return Code: Error

Status of the Update Module -

Status: Update was terminated

Report: LBSVUU01

Row: 60

Error Details: Internal session terminated with a runtime error (see ST22)

Class: 00

Number: 671

Regards,

Ravi

Hi Ravi

The dump suggests that there is an attempt to enter duplicate entries.

Hence - need to check on these :

1. Is the dump coming for all the users / or only specific user .

2. If for specific user - then please check the transaction used and the data entered in the same.

Also please upload your ST22 dump for the update error you mentioned above. This would give information regarding the transaction etc.

Thanks

Rishi

Hi Rishi,

1. Is the dump coming for all the users / or only specific user .

This is hapenning for all the users

2. If for specific user - then please check the transaction used and the data entered in the same.

As mentioned, it is not for a specific user and as of now we noticed this problem for CJ20N, COR1...

The reason why i am not uploading the ST22 dump is, already the same dump is available in this blog which is posted by Mr. Amit Shirsath Feb 29, 2012 11:18 AM

Regards,

Ravi

Resolved...

Solution:

As instructed in SAP Note: 1652205 we have changed the current number with the existing latest numbers in the number ranges.

Thanks for coming up with some hints.

Regards,

Ravi

Hi Ravi,

we are also getting same issue. where we have to check the existing latest number range to change the current number.

kindly suggest.

Regards,

Siddu.

Siddu,

Run transaction SNUM.

Enter Object (eg. AUF_PLAN).

Click number ranges.

Select Interval or Status.

From top menu => Interval => Change current Number

Thanks,

Sreeni

Dear Amit,

Could you please provide the error log from SM13.

Thanks,

Veeresh K R

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Amit,

This is a typical case of data duplication.

Can you post the ST22 Dump here in the posts ? , I think there is a clear case of data duplication somewhere in the transaction you are using.

One of the item that you are entering may already exist.

Regards,

Siddhesh

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello siddesh,

Thank you for ur reply. here is the dump.

many thank.

ABAP runtime errors SAPSQL_ARRAY_INSERT_DUPREC

Occurred on 22.10.2007 at 13:13:56

The ABAP/4 Open SQL array insert results in duplicate database records.

What happened?

The current ABAP/4 program "SAPLBSVU " 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"

"SAPLBSVU " or "LBSVUU01 "

"STATUS_UPDATE"

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.

System environment

SAP Release.............. "46C"

Application server....... "devsap"

Network address.......... "172.16.10.10"

Operating system......... "OSF1"

Release.................. "V5.1"

Hardware type............ "alpha"

Database server.......... "devsap"

Database type............ "ORACLE"

Database name............ "DEV"

Database owner........... "SAPR3"

Character set............ "en_US.ISO8859-1"

SAP kernel............... "46D"

Created on............... "Aug 25 2005 20:41:23"

Created in............... "OSF1 V4.0 878 alpha"

Database version......... "OCI_805_64__OCI_7_API "

Patch level.............. "2113"

Patch text............... " "

Supported environment....

Database................. "ORACLE 8.0.5.., ORACLE 8.0.6.., ORACLE

8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.."

SAP database version..... "46D"

Operating system......... "OSF1 V3.2, OSF1 V4.0, OSF1 V5.0, OSF1 V5.1, , System

build information:, -

, LCHN : 775484"

User, transaction...

Client.............. 280

User................ "PPPCS"

Language key........ "E"

Transaction......... "CO01 "

Program............. "SAPLBSVU "

Screen.............. "RSM13000 3000"

Screen line......... 2

Information on where termination occurred

The termination occurred in the ABAP/4 program "SAPLBSVU " in

"STATUS_UPDATE".

The main program was "RSM13000 ".

The termination occurred in line 61

of the source code of program "LBSVUU01 " (when calling the editor 610).

The program "SAPLBSVU " was started in the update system.

Source code extract

000310 CHECK: jsto_upd-chgnr > '000',

000320 jsto_upd-stsma NE jsto_upd-stsma_old.

000330 CLEAR jcdo_tab.

000340 MOVE-CORRESPONDING jsto_upd TO jcdo_tab.

000350 MOVE-CORRESPONDING chdat TO jcdo_tab.

000360 jcdo_tab-stsma_new = jsto_upd-stsma.

000370 APPEND jcdo_tab.

000380 ENDLOOP.

000390 * Änderungen zu Einzelstatus (Insert)

000400 LOOP AT jest_ins WHERE chgkz = 'X'.

000410 CHECK jest_ins-chgnr > '000'.

000420 CLEAR jcds_tab.

000430 MOVE-CORRESPONDING jest_ins TO jcds_tab.

000440 MOVE-CORRESPONDING chdat TO jcds_tab.

000450 jcds_tab-chind = 'I'.

000460 APPEND jcds_tab.

000470 ENDLOOP.

000480 * Änderungen zu Einzelstatus (Update)

000490 LOOP AT jest_upd WHERE chgkz = 'X'.

000500 CHECK jest_upd-chgnr > '000'.

000510 CLEAR jcds_tab.

000520 MOVE-CORRESPONDING jest_upd TO jcds_tab.

000530 MOVE-CORRESPONDING chdat TO jcds_tab.

000540 jcds_tab-chind = 'U'.

000550 APPEND jcds_tab.

000560 ENDLOOP.

000570 * Verbuchung Statusobjekte

000580 DESCRIBE TABLE jsto_ins LINES sy-tabix.

000590 IF sy-tabix > 0.

000600 INSERT jsto CLIENT SPECIFIED

FROM TABLE jsto_ins.

000620 ENDIF.

000630 DESCRIBE TABLE jsto_upd LINES sy-tabix.

000640 IF sy-tabix > 0.

000650 field-symbols -OBJNR AND

000790 STAT LIKE 'E%'.

000800 ENDIF.

Contents of system fields

SY field contents..................... SY field contents.....................

SY-SUBRC 4 SY-INDEX 0

SY-TABIX 11 SY-DBCNT 0

SY-FDPOS 1 SY-LSIND 0

SY-PAGNO 0 SY-LINNO 1

SY-COLNO 1

Chosen variables

Name.......................... Contents.1........2........3....+....4

JCDS_TAB 280QL030000015600 I0207001PPPCS

3335433333333333322222222433333335554522

2801C03000001560000000000902070010003300

... + 40 20071022131354 CO01

2222233333333333333222244332222222222222

000002007102213135400003F010000000000000

... + 80 I

22224

00009

CHDAT PPPCS 20071022131354CO01

5554522222223333333333333344332222222222

000330000000200710221313543F010000000000

... + 40

222222

000000

ETAB[] Table[initial]

0000FFFD

0000FFFF

CHDAT+0(26) PPPCS 20071022131354

55545222222233333333333333

00033000000020071022131354

JCDS_TAB[] #########################(##P###########

0000000000000000000000000200500000002000

0000000000000000000000004800040000003000

... + 40 ####0###0#######ÿÿÿÿU########### #æA####

1000300030000000FFFF50000000000027E40000

0000020000000000FFFF5000200043000F611000

... + 80 #DæA####################################

04E4000000000000000000000000000000000000

8461100000000000000000000000000000000000

... + 120 ########################0#######

00000000

0000000

JSTO_INS[] #########################(##`###########

0000000000000000000000000200600000000000

000000000000000000000000480006000000B000

... + 40 ################ÿÿÿÿ(###########ðwæA####

0000100010000000FFFF200000000000F7E40000

A000E200E000A000FFFF80002000430007611000

... + 80 #yæA####################################

97E4000000000000000000000000000000000000

8961100000000000000000000000000000000000

... + 120 ########################,#######

00000000

0000000

%_PRINT 000

2222333222222222222222222222222222222222

0000000000000000000000000000000000000000

... + 40

2222222222222222222222222222222222222222

0000000000000000000000000000000000000000

... + 80 0 ########

2222222222320000000022222222222222222222

0000000000000000000000000000000000000000

... + 120

22222222

0000000

SY-XPROG

2222222222222222222222222222222222222222

0000000000000000000000000000000000000000

SY-TABIX 11

0000

B000

SY ########################################

0000000000000000000000000000000000000000

00000000B000B00000000000A000000000000000

... + 40 ####################################(###

0000000000000000000090000000000000002000

00001000100000001000A0000000000000008000

... + 80 ########################################

0000000000000000000000000000000000000000

0000000000004000000000000000000000000000

... + 120 ####################################¢###

00000000

0000000

ETAB

222222222222222222222222222222222222222

000000000000000000000000000000000000000

???

Active calls / events

No.... Type........ Name..........................

Programm

Include Line

1 FUNCTION STATUS_UPDATE

SAPLBSVU

LBSVUU01 61

2 FORM STATUS_UPDATE

SAPLBSVU

LBSVUV01 55

3 FORM VB_CALL_FUNC

RSM13000

RSM13000 5485

4 FORM VB_V1_EXEC

RSM13000

RSM13000 5236

5 FORM VB_V1_NORMAL

RSM13000

RSM13000 3963

6 MODULE (PBO) VBEXEC

RSM13000

RSM13000 3812

Internal notes

The termination occurred in the function "ExecuteCall" of the SAP

Basis System, specifically in line 5820 of the module

"//bas/46D/src/krn/runt/absapsql.c#21".

The internal operation just processed is "SQLS".

The internal session was started at 20071022131354.

Active calls in SAP kernel

0: 0x1205e9298

OSF_stacktrace

dptstack.c : 879

dw.sapDEV_DVEBMGS00 .text

1: 0x1205e91b4

CTrcStack2

dptstack.c : 265

dw.sapDEV_DVEBMGS00 .text

2: 0x1205e9114

CTrcStack

dptstack.c : 165

dw.sapDEV_DVEBMGS00 .text

3: 0x12095e590

rabax_CStackSave

abrabax.c : 5783

dw.sapDEV_DVEBMGS00 .text

4: 0x120955208

ab_rabax

abrabax.c : 852

dw.sapDEV_DVEBMGS00 .text

5: 0x1208acde0

ExecuteCall

absapsql.c : 5820

dw.sapDEV_DVEBMGS00 .text

6: 0x12089ed68

ab_jsqls

absapsql.c : 666

dw.sapDEV_DVEBMGS00 .text

7: 0x120793a58

ab_extri

abextri.c : 925

dw.sapDEV_DVEBMGS00 .text

8: 0x120864660

ab_xevent

abrunt1.c : 250

dw.sapDEV_DVEBMGS00 .text

9: 0x12096728c

ab_dstep

abdynpro.c : 431

dw.sapDEV_DVEBMGS00 .text

10: 0x120687b08

dynpmcal

dymainstp.c : 2188

dw.sapDEV_DVEBMGS00 .text

11: 0x1206838f8

dynppbo0

dymainstp.c : 464

dw.sapDEV_DVEBMGS00 .text

12: 0x12068307c

dynprctl

dymainstp.c : 301

dw.sapDEV_DVEBMGS00 .text

13: 0x12067fd1c

dynpen00

dymain.c : 1204

dw.sapDEV_DVEBMGS00 .text

14: 0x1204d522c

Thdynpen00

thxxhead.c : 3892

dw.sapDEV_DVEBMGS00 .text

15: 0x1204d470c

TskhLoop

thxxhead.c : 3715

dw.sapDEV_DVEBMGS00 .text

16: 0x1204cc0e0

tskhstart

thxxhead.c : 954

dw.sapDEV_DVEBMGS00 .text

17: 0x120461610

DpMain

dpxxdisp.c : 850

dw.sapDEV_DVEBMGS00 .text

18: 0x12045fe54

main

thxxanf.c : 50

dw.sapDEV_DVEBMGS00 .text

List of ABAP programs affected

Type

Program

Gen. date time

LoadSize

Prg	RSM13000	31.03.2006 12:33:31	234496
Prg	SAPMSSYD	11.08.2000 15:06:13	16384
Prg	SAPFSYSCALLS	21.12.1999 19:32:31	7168
Typ	VBHDR	02.11.1998 09:57:15	3072
Typ	VBMOD	08.08.1995 14:49:58	2048
Prg	SAPLQPBU	06.02.2006 12:00:38	47104
Typ	QALS	20.07.2002 11:37:53	27648
Prg	SAPLDISP	08.02.2007 13:28:40	371712
Typ	T000MD	01.04.1998 02:11:56	1024
Typ	T399D	14.05.1998 22:44:13	9216
Typ	T001W	18.11.1998 16:27:15	7168
Prg	SAPLSCAL	06.02.2006 10:38:33	26624
Typ	T440B	01.04.1998 01:53:56	2048
Prg	SAPLMATL	08.02.2007 13:28:40	493568
Typ	T001K	01.02.2000 14:56:09	3072
Prg	SAPLMG21	08.02.2007 13:29:04	162816
Typ	MARA	08.02.2007 13:28:36	15360
Prg	SAPLMG22	08.02.2007 13:28:40	117760
Typ	MARC	04.01.2000 18:04:45	23552
Typ	T438A	29.07.1998 19:29:57	3072
Typ	MDVM	15.04.1998 00:02:48	2048
Prg	CL_EXITHANDLER================	06.02.2006 10:33:18	13312
Prg	CL_ABAP_TYPEDESCR=============	04.01.2000 19:06:00	17408
Prg	CL_ABAP_ELEMDESCR=============	04.01.2000 19:06:00	13312
Prg	CL_ABAP_DATADESCR=============	04.01.2000 19:06:00	11264
Prg	CL_ABAP_REFDESCR==============	04.01.2000 19:06:00	14336
Prg	CL_ABAP_STRUCTDESCR===========	04.01.2000 19:06:00	16384
Prg	CL_ABAP_COMPLEXDESCR==========	04.01.2000 19:06:00	11264
Prg	CL_ABAP_TABLEDESCR============	04.01.2000 19:06:00	16384
Prg	CL_ABAP_CLASSDESCR============	04.01.2000 19:06:00	23552
Prg	CL_ABAP_OBJECTDESCR===========	04.01.2000 19:06:00	28672
Prg	CL_ABAP_INTFDESCR=============	04.01.2000 19:06:00	21504
Prg	IF_EX_INSPECTIONLOT_UPDATE====	01.12.1999 18:43:19	5120
Typ	SXS_INTER	30.11.1998 15:55:16	1024
Prg	SAPLSEXV	31.03.2006 12:32:34	155648
Prg	SAPLSXCH	06.02.2006 10:39:04	80896
Typ	V_EXT_ACT	14.10.1999 22:16:55	2048
Prg	CL_EX_INSPECTIONLOT_UPDATE====	01.12.1999 18:37:00	27648
Prg	CL_EXIT_MASTER================	01.02.2000 09:29:10	10240
Typ	V_EXT_IMP	14.10.1999 22:16:55	2048
Prg	SAPLBSVU	24.07.2002 15:35:15	36864
Typ	JEST_UPD	09.12.1999 18:54:13	2048
Typ	JSTO	27.08.1994 20:32:55	2048
Typ	JSTO_UPD	27.08.1994 21:32:34	2048
Typ	ONR00	14.12.1992 11:16:42	1024

List of internal tables

Header of PROG=SAPLBSVUDATA=JCDS_TAB[]

TABH+ 0(20) = 0000000000000000000000000000000000000000

TABH+ 20(20) = 0000000004280000500400000000000023000000

TABH+ 40(20) = 10000000300200003000000000000000FFFFFFFF

TABH+ 60(20) = 550000000200000004030000207FE64101000000

TABH+ 80(20) = 0844E64101000000000000000000000000000000

TABH+100(20) = 0000000000000000000000000000000000000000

TABH+120(20) = 0000000000000000000000000000000000000000

TABH+140(12) = 000000003000000000000000

id = 48 (0x30000000)

fill = 35 (0x23000000)

lineAdmin = 560 (0x30020000)

lineAlloc = 48 (0x30000000)

tabi = 0x207FE64101000000

pghook = 0x0844E64101000000

index = 0x0000000000000000

hshook = 0x0000000000000000

btree = 0x0000000000000000

reghook = 0x0000000000000000

lopc = 0 (0x00000000)

occu = 16 (0x10000000)

rank = 0 (0x00000000)

loop = -1 (0xFFFFFFFF)

leng = 85 (0x5500)

fcnt = 0 (0x0000)

lock = 0

shrd = 0

access = 1 (stdAccess)

idxKind = 0 (noIndex)

unique = 2 (nonUnique)

cmpMode = 2 (cmpSingleMcmp)

pb_func = 0x0000000000000000

pb_handle = 0x0000000000000000

Directory of application tables (contents)

Program

Name.......... Contents.1........2........3....+....

Directory of data areas (administration information)

Hi,

I have the same problem. Can you solve it? In this case, can you explian what it's happening.

Thanks!

Hi,

I am also facing the same dump problem in our client, in Release 701.

Please share the solution.

Thanks

Ravi

Hi Ravi,

Please check in t. code SM13.

Double click on failed update due to this dump you will find the error message.

Please send the same.

Regards

Ganesh Datt Tiwari

Hi Ganesh,

Thanks for your fast response.

The following are the Error details of SM13:

Module Name(Function): STATUS_UPDATE

Type: V1

Update Return Code: Error

Status of the Update Module -

Status: Update was terminated

Report: LBSVUU01

Row: 60

Error Details: Internal session terminated with a runtime error (see ST22)

Class: 00

Number: 671

Regards,

Ravi

Ask a Question

Top Q&A Solution Author

User

Count