cancel
Showing results for 
Search instead for 
Did you mean: 

SAPSQL_ARRAY_INSERT_DUPREC exception CX_SY_OPEN_SQL_DB

0 Kudos

Dear all

When i am posting purchase requisition with execution service for services in easy cost planning , the system showing the following error.

Update was terminated

Client.............. 120

User................ "TFERREIRA"

Language key........ "P"

Transaction......... "CJ9ECP "

Transactions ID..... "4C8964DF2C984A57E10000000A00003D"

Program............. "SAPLMLVK"

Screen.............. "RSM13000 3000"

Screen line......... 2

Error Info... ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC

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 "MS_UPDATE_ACCOUNT_SERVICE" "(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.

Regards,

Tiago Ferreira

Edited by: Virendra Pal on Sep 10, 2010 8:25 PM

please first search OSS and talk to your basis guys before posting

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member201206
Active Contributor
0 Kudos

Hi Tiago,

Do you have any customer codes in this area?

If not, please check the note 1329089 is valid for your system.

If the problem persists, you can raise a customer message to let SAP to have a look.

Kind regards,

Zhenbo

Former Member
0 Kudos

Hi,

Rightly suggested by Gokul, error is due to inserting duplicate records.

This may happen due to number ranges gone to their max value, system goes back to the first entry in number range.

Kindly check number ranges.

Regards,

Harsh.

Former Member
0 Kudos

Hi,

I think you are getting this error because of a duplicate entry in a table that is concerned with the transaction you are executing. I would suggest you to take the help of your ABAPer to resolve this.

Regards,

Gokul