cancel
Showing results for 
Search instead for 
Did you mean: 

SAPSQL_ARRAY_INSERT_DUPREC

Former Member
0 Kudos

Hi All,

When we try to create user in our Dev environment we are getting dump "SAPSQL_ARRAY_INSERT_DUPREC"

can you please suggest what could be the possible reason for the dump.

Thanks&Regards

Shams

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Are you doing just one user or mass update ?

Mark

Former Member
0 Kudos

Hi Mark,

Actually we are trying to create new user by copying the existing user .It is working fine now was it due to source ID.

Please let me know what was the issue.

Thanks&Regards

Shams

Former Member
0 Kudos

Hi,

Unfortunately without knowing what was going on in the system at the time I doubt I could answer your question.

I am assuming an abap dump was created for the duprec ? Could always paste it for some analysis..

Mark

Former Member
0 Kudos

Hi Mark ,

Here is the dump which i got:

ABAP runtime errors SAPSQL_ARRAY_INSERT_DUPREC

Occurred on 17.12.2009 at 08:24:35

>> Short dump has not been completely stored. It is too big.

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

What happened?

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

"SAPLEDI1 " or "LEDI1F09 "

"F09_IDOC_INSERT_WITH_NUMBER"

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....... "usahs143"

Network address.......... "130.175.219.198"

Operating system......... "HP-UX"

Release.................. "B.11.23"

Hardware type............ "ia64"

Database server.......... "usahs143"

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

Database name............ "DL3"

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

Character set............ "es_ES.iso88591"

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

Created on............... "Aug 10 2008 21:44:24"

Created in............... "HP-UX B.11.23 U ia64"

Database version......... "OCI_102__OCI_7_API "

Patch level.............. "2415"

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.., ORACLE 10.2.0.."

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

Operating system......... "HP-UX B.10, HP-UX B.11, , System build information:,

, LCHN : "

User, transaction...

Client.............. 100

User................ "FZMJWM"

Language key........ "S"

Transaction......... "SU01 "

Program............. "SAPLEDI1 "

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

Information on where termination occurred

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

"F09_IDOC_INSERT_WITH_NUMBER".

The main program was "SAPMSUU0 ".

The termination occurred in line 86

of the source code of program "LEDI1F09 " (when calling the editor 860).

Source code extract

000560 LOOP AT LIST_CONTAINER_CREATE WHERE MANDT EQ SY-MANDT

000570 AND DOCNUM EQ IDENT.

000580 MOVE LIST_CONTAINER_CREATE TO LIST_CONTAINER_INSERT.

000590 LIST_CONTAINER_INSERT-DOCNUM = DOCNUM.

000600 APPEND LIST_CONTAINER_INSERT.

000610 DELETE LIST_CONTAINER_CREATE.

000620 ADD 1 TO MAXSEGNUM.

000630 ENDLOOP.

000640 if control-mestyp eq c_mestyp.

000650 perform rsebasis_devtype(rsebschk) using flag.

000660 if flag ne 'X'. "Anwendungssystem

000670 perform call_transform tables list_container_insert using control.

000680 endif.

000690 endif.

000700 INSERT EDID4 FROM TABLE LIST_CONTAINER_INSERT.

000710 * free list_container_insert

000720 FREE_RETURN = 1.

000730 ELSE. " no other IDoc is open in create-mode

000740 LOOP AT LIST_CONTAINER_CREATE WHERE MANDT EQ SY-MANDT

000750 AND DOCNUM EQ IDENT.

000760 LIST_CONTAINER_CREATE-DOCNUM = DOCNUM.

000770 MODIFY LIST_CONTAINER_CREATE.

000780 ADD 1 TO MAXSEGNUM.

000790 ENDLOOP.

000800 if control-mestyp eq c_mestyp.

000810 perform rsebasis_devtype(rsebschk) using flag.

000820 if flag ne 'X'. "Anwendungssystem

000830 perform call_transform tables list_container_create using control.

000840 endif.

000850 endif.

> INSERT EDID4 FROM TABLE LIST_CONTAINER_CREATE.

000870 * free list_container_create

000880 FREE_RETURN = 0.

000890 ENDIF.

000900

000910 * insert status records

000920

000930 SYN_ERROR_IN = ' '.

000940 CNTR_STATUS = 0.

000950 REFRESH LIST_STATUS.

000960 CLEAR LIST_STATUS.

000970 GET TIME.

000980

000990 * sort the status records, so that ALE-status are on the end of the list

001000 LOOP AT LIST_STATUS_CREATE

001010 WHERE MANDT EQ SY-MANDT

001020 AND ( STATUS EQ EDI_IDOC_ADDED

001030 OR STATUS EQ EDI_IDOC_SYNTAX_ERROR_OUT

001040 OR STATUS EQ EDI_IDOC_TO_BE_PROCESSED

001050 OR STATUS EQ EDI_IDOC_SYNTAX_ERROR_IN )

Contents of system fields

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

-


-


-


SY-SUBRC 0 SY-INDEX 1

SY-TABIX 1 SY-DBCNT 1

SY-FDPOS 0 SY-LSIND 0

SY-PAGNO 0 SY-LINNO 1

SY-COLNO 1

Chosen variables

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

-


MAXSEGNUM 000016

333333

000016

LIST_STATUS_CREATE-MANDT 100

333

100

CONTROL-MESTYP USERCLONE

554544444222222222222222222222

53523CFE5000000000000000000000

C_MESTYP FIDCCH

444444222222222222222222222222

694338000000000000000000000000

SY-XFORM CONVERSION_EXIT

444545544454545222222222222222

3FE65239FEF5894000000000000000

%_?NOT_ASSIGNED?

2222

0000

FLAG

2

0

RSJOBINFO 00000000

2222222222222222222222222222222233333333

0000000000000000000000000000000000000000

... + 40 000000

3333332222222222222222222222222222222222

0000000000000000000000000000000000000000

... + 80 ####

0000

0000

EDI_IDOC_WAS_CHANGED_IN 69

33

69

SPACE

2

0

LIST_CONTAINER_CREATE[] ########################################

0000000000000000000000000007000000000001

000000000000000000000000401F009000000000

... + 40 #######X#########,####### ######m#

0000000500010000FFFF020000000200C00086A1

0008000800000000FFFF4C000007900000006D88

... + 80 ####j;################################

C000863E00000000000000000000000000000000

00006AB800000000000000000000000000000000

... + 120 ###########################1####

00000000

0000000

LIST_CONTAINER_CREATE 1000000000000159018000000016E1BPCOMREM

3333333333333333333333333333434544454422

100000000000015901800000001651203FD25D00

... + 40 00000002##TELSESRG

2222222222222222223333333300544545542222

000000000000000000000000020045C353270000

... + 80

2222222222222222222222222222222222222222

0000000000000000000000000000000000000000

... + 120 002

22223332

0000002

CONTROL 100000000000015901846C 30 1A00000

3333333333333333333334233222222223433333

1000000000000159018463030000000001100000

... + 40 0002LSDL3CLNT200

3333454434445333222222222222222222222222

0002C34C33CE4200000000000000000000000000

... + 80

2222222222222222222222222222222222222222

0000000000000000000000000000000000000000

... + 120

22222222

0000000

ACTUAL_VALUE 000000

333333

000000

<%_TABLE_EDID4> ???

???

???

SYST ########################################

0000000000000001000000000000000000000000

0001000000010000000000000000000000000000

... + 40 #######################################,

0000000000000000000000000000000000000002

000100000001000000010000000000000000004C

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

0000000000000000000500000000000000000000

0000000000000000000000000000000000000000

... + 120 #######################################}

00000000

0000000

FREE_RETURN 0

0000

0000

IDENT 0000000000000001

3333333333333333

0000000000000001

EDI_FILE_OK 03

33

03

LIST_CONTAINER_SAVE[] Table[initial]

0000DFFF

0000FFFF

CNTR_STATUS 0000000000000000

3333333333333333

0000000000000000

LIST_STATUS[] Table[initial]

0000DFFF

0000FFFF

LIST_STATUS 0000000000000000000000000000000000000

2223333333333333333333333333333333333333

0000000000000000000000000000000000000000

... + 40 00000000000000000000000

3333333333333333333333322222222222222222

0000000000000000000000000000000000000000

... + 80

2222222222222222222222222222222222222222

0000000000000000000000000000000000000000

... + 120

22222222

0000000

<%_L05E> ???

???

???

SY-MANDT 100

333

100

<%_L05F> ???

???

???

Active calls / events

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

Programm

Include Line

1 FORM F09_IDOC_INSERT_WITH_NUMBER

SAPLEDI1

LEDI1F09 86

2 FUNCTION EDI_DOCUMENT_CLOSE_CREATE_TAB

SAPLEDI1

LEDI1U19 40

3 FUNCTION IDOC_CREATE_ON_DATABASE

SAPLBD11

LBD11U10 145

4 FUNCTION ALE_IDOCS_CREATE

SAPLBD11

LBD11U08 126

5 FUNCTION ALE_USER_CLONE

SAPLSU_USER

LSU_USERU14 131

6 FUNCTION SUSR_ZBV_USER_SEND

SAPLSUU6

LSUU6U02 239

7 FUNCTION SUSR_USER_DISTRIBUTE

SAPLSUU1

LSUU1U21 249

8 FUNCTION SUSR_USER_BUFFERS_TO_DB

SAPLSUU1

LSUU1U09 344

9 FORM SAVE

SAPLSUU0

LSUU0U02 3024

10 FUNCTION SUSR_USER_MAINT_WITH_DIALOG

SAPLSUU0

LSUU0U02 2628

11 EVENT START-OF-SELECTION

SAPMSUU0

SAPMSUU0 29

Internal notes

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

Basis System, specifically in line 5821 of the module

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

The internal operation just processed is "SQLS".

The internal session was started at 20091217082121.

Former Member
0 Kudos

Hello Shams,

Please check if OSS note 444154 helps you.

Regards.

Ruchit.

Former Member
0 Kudos

Oops just re-read your message. The issue is solved already.

Regards.

Ruchit.