Runtime Error SAPSQL_ARRAY_INSERT_DUPREC for Insertio on table PBED

[Former Member]

Hi,

Is there any SAP Note to rectify the error or any solution?

It happened in standard program : SAPLM60U. Include name : LM60UF0P Form name : PBET_BEARBEITEN

ST22 information below:

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 "PBET_BEARBEITEN" "(FORM)", nor was it propagated by a RAISING

clause.

Information on where terminated
    Termination occurred in the ABAP program "SAPLM60U" - in "PBET_BEARBEITEN".
    The main program was "RSM13000 ".

    In the source code you have the termination point in line 272
    of the (Include) program "LM60UF0P".
    The program "SAPLM60U" was started in the update system.
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "PBET_BEARBEITEN" "(FORM)", but it was neither handled locally nor
    declared
    in the RAISING clause of its signature.

    The procedure is in program "SAPLM60U "; its source code begins in line
    203 of the (Include program "LM60UF0P ".

[Former Member]

Hi Paul,

some entries already exist in this table:

Try to reproduce this error and debug this line. So you can see, which entries should be inserted. (Itab: da_pbedi)

There are two Scenarios:

Same primary keys or same unique index.

If you enhanced this table with a unique Index, check if you need it as unique...

Otherwise you have some inconsistencies. You could check SM13 for Example if some Update-Processes are still to be executed.

regards

Jan Martin

[former_member219338]

Hi Paul,

do you has copied customizing from one system to another?

Because it seems that a number range has problems.

[Former Member]

Hi Paul,

It is a standard error but custom one...

What I mean is the table is already having the entry you are showing in the debug mode activate update debugger and put a breakpoint on this line.

Check the entries in this table and check if the entry with this key is already existing in the PBED table.

Also check if the number range [if any for this field] has been reset.

Regards