cancel
Showing results for 
Search instead for 
Did you mean: 

SAPSQL_ARRAY_INSERT_DUPREC Dump in SAPLCLVF program for CA-CL-CL component

Former Member
0 Kudos

hello All,

have googled this st22 error but found no exact answer for the Dump happening while creating the Equipment using IE01

Dump data:

Dump data

Category               ABAP Programming Error

Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC

Except.                CX_SY_OPEN_SQL_DB

ABAP Program           SAPLCLVF

Application Component  CA-CL-CL

Date and Time          27.10.2015 11:35:53

Short text

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

What happened?

     Error in the ABAP Application Program

     The current ABAP program "SAPLCLVF" had to be terminated because i

     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.

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

Termination occurred in the ABAP program "SAPLCLVF" - in "PFLEGEN_ALL_TABS".

The main program was "RSM13000 ".

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

of the (Include) program "LCLVFF10".

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

The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

procedure "PFLEGEN_ALL_TABS" "(FORM)", but it was neither handled locally nor

  declared

in the RAISING clause of its signature.

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

6 of the (Include program "LCLVFF10 ".

can some one help me how to resolve this Dumps for IE01 tcode

we have observed that same object number is available in KSSK and even we are getting confirmation message like equipment is created but then its is ending up with Dump in the system.

Accepted Solutions (1)

Accepted Solutions (1)

MTerence
Active Contributor
0 Kudos

Hi Naseer,

Refer below note, note is old, but check whether the reports can be useful

60523 - Classification data is not archived/BS503


Regards

Terence

mathewzdavis
Active Participant
0 Kudos

Hi

I think you inserted a record with a key that already exists.

Regards

Former Member
0 Kudos

Thanks Maria,

if you have faced this before can you help us understand the actual reason on the failure.

just consider the below as inputs for my query:

this record has updated for the very first time in KSSK table we have checked at the Oracle database level also.

as and when the Business tried creating it using IE01 it went to Dump but strange thing is we are receiving the Equipment created successfully confirmation in the status Bar.

Your views on the reason behind this behavior will be very helpful as tech team after seeing the reason of Dump they just concluded that it went to Dump only because of Entry that is updated in KSSK table

MTerence
Active Contributor
0 Kudos

Hi Naseer,

Did you check whether there is any update failure occured in SM13

I didn't face this issue earlier, so i cannot confirm it from my part.

If you are able to replicate this issue, then raise this with SAP

Regards

Terence

Former Member
0 Kudos

Thanks Maria for the quick reply,

yes we have failures in SM13, st22 and sm58 too.

will raise this with SAP Thanks every one for the support

henning_abel
Participant
0 Kudos

Dear Naseer,

could you please let us know what was the reason and solution for this error?

We're facing the same problem here.

Thanks and BR,

Henning

Answers (0)