Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC

Former Member
0 Likes
807

Hello Everyone,

i am getting short dumps in ecc system during data extraction to bi system. please provide me any related notes or suggestions to resolve the issue.

short dump details as follows:

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 "SAPLEDI1" 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 "F09_IDOC_INSERT_WITH_NUMBER" "(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.)

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"

"SAPLEDI1" or "LEDI1F09"

"F09_IDOC_INSERT_WITH_NUMBER"

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

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

"F09_IDOC_INSERT_WITH_NUMBER" "(FORM)", or its possible occurrence must be

declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

there is no note mentioned here.

Thanks and Regards,

Kasi

2 REPLIES 2
Read only

Former Member
0 Likes
574

Hi,

You are trying to add a duplicate record to some table.

I.e a record already exists in your databasde with same set of primary keys.

Check the dump log in ST22, it will give you the table name as well.

Hope it helps,

Raj

Read only

Former Member
0 Likes
574

hi kasi,

The origin of the problem can be the number of idocs in the system. I fixed this error in a customer installation using the we11 to remove old idocs (before 2011).

kind regards