SAPSQL_ARRAY_INSERT_DUPREC OBJECT_NUMBER_INSERT_VB

[Former Member]

HI,

I am getting a short dump in ST22. The error is attached herewith:

Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC

Exception CX_SY_OPEN_SQL_DB

Date and Time 15.10.2009 14:47:15

-

---

-

---

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 "SAPLBOVB" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

-

---

-

---

Information on where terminated

Termination occurred in the ABAP program "SAPLBOVB" - in

"OBJECT_NUMBER_INSERT_VB".

The main program was "RSM13000 ".

In the source code you have the termination point in line 17

of the (Include) program "LBOVBU02".

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

The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

procedure "OBJECT_NUMBER_INSERT_VB" "(FUNCTION)", but it was neither handled

locally nor declared

in the RAISING clause of its signature.

The procedure is in program "SAPLBOVB "; its source code begins in line

1 of the (Include program "LBOVBU02 ".

-

---

-

---

Source Code Extract

-

---

Line

SourceCde

-

---

1	FUNCTION OBJECT_NUMBER_INSERT_VB.
2	*"----
3	*"Verbuchungsfunktionsbaustein:
4	*"
5	*"Lokale Schnittstelle:
6	*" TABLES
7	*" ONR_INS STRUCTURE ONRVB
8	*"----
9
10	allgemeiner Index
11	REFRESH ONR00_TAB.
12	CLEAR ONR00_TAB.
13	LOOP AT ONR_INS.
14	MOVE-CORRESPONDING ONR_INS TO ONR00_TAB.
15	APPEND ONR00_TAB.
16	ENDLOOP.
>>>>>	INSERT ONR00 FROM TABLE ONR00_TAB.
18	Objektindex
19	INSERT ONRVB FROM TABLE ONR_INS.
20
21	ENDFUNCTION.

-

---

-

---

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 "OBJECT_NUMBER_INSERT_VB" "(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"

"SAPLBOVB" or "LBOVBU02"

"OBJECT_NUMBER_INSERT_VB"

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

"OBJECT_NUMBER_INSERT_VB" "(FUNCTION)", or its possible occurrence must be

declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

-

---

I can not find any relavant notes regarding this error. I have understood that is is getting short dump while updating a table. But not found a suitable solution to this problem

Please help me by suggesting a solution to this problem.

Thanks & Regards,

Sandy

[AnupKumar]

did you got any resolution for this issue.  I am facing issue in one of the system but exactly same scenario is working fine in another system.

Please let me know.

[Former Member]

This is a standard duplicate key entry error. The unit of work being executed (identified by the primary key) has already been stored in the database. What transaction and process were being executed when it happened?