topic he ABAP/4 Open SQL array insert results in duplicate database records in Application Development and Automation Discussions

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

Former Member — Sat, 23 Jan 2010 05:47:44 GMT

Dear Gurus,

II am getting a dump when I run MD02/ MD03. (t- code to run MRP)

Below is the message system is showing:

Please help

Thanks in Advance

Best Regards

Adhish

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 "SAPLM61U" 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

procedure "INSERT_MDSBI_IN_MDSB" "(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.)

1 *----

2 * ARRAY-INSERT auf MDSB

3 *----

4 FORM INSERT_MDSBI_IN_MDSB.

INSERT MDSB6 FROM TABLE MDSBI.

7 ADD SY-DBCNT TO STATS-RESBI. "statistics

8 ENDFORM.

Re: he ABAP/4 Open SQL array insert results in duplicate database records

Former Member — Sat, 23 Jan 2010 07:00:30 GMT

Hello

1. Check existing interval number in SNRO.

2. Search for SAP Notes for this.

Re: he ABAP/4 Open SQL array insert results in duplicate database records

Former Member — Tue, 06 Apr 2010 14:47:10 GMT

Hi,

There must be inconsistency in the number range. This happens when the current number in the number range for dependent requirements is lower than the highest number in the database table of the dependent requirements RESB.

Please check the current number in transaction OMI2. Here in the interval you can see the current number. Then please check the highest number in table RESB. If the current number in OMI2 is lower than the highest number in table RESB then this should be the reason for the dump.

Check and revert. If that's not the case we'll look into other possibilities.

In mean time check for SAP Note 138108.