Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAPSQL_ARRAY_INSERT_DUPREC in iw21

Former Member
0 Likes
536

Hi Experts,

we have upgraded EHP1 to EHP4 .After upgradation, if i am trying to create the notification in iw21 and assign an order to the notification and while saving it is getting saved. and issueing order no as 'X'(X belongs to different order type )..

And if i run Tcode iw22 ,if i check the order no (X) linked to the notification order no is not available.

If i see the st22 it is telling the error "SAPSQL_ARRAY_INSERT_DUPREC' and if i see the ABAP editor it is showing the error in

funtion module STATUS_UPDATE in include LBSVUU01 from the program SAPLCOZV

"

IF sy-tabix > 0.

INSERT jsto CLIENT SPECIFIED

FROM TABLE jsto_ins."

i have searched for the notes 970434, 82295.But i think that will not solve the issue. i dont know which note should be applied.

Could you please help me to solve the issue.

1 REPLY 1
Read only

Tamas_Hoznek
Product and Topic Expert
Product and Topic Expert
0 Likes
432

Such problems usually occur because of misaligned number ranges or incorrect custom code (enhancements, user exits and the like). It is difficult to give you the exact reason without analyzing the actual dump you are getting.

The program terminates because it tries to insert a new status entry for the notification in the status table (JSTO). Apparently an entry with the same key exists already in this table that belongs to an already existing notification. The key for JSTO is derived from the notification number, it starts with QM...

Check the dump to see what the notification number is (in internal table jsto_ins) and verify the number range statuses. Adjust the number range of the notification type if necessary so that it doesn't overlap with already existing notifications in the DB.

Also, if you do have custom code / enhancements that are executed, it's possible that there is an illegal COMMIT that causes standard tables to get updated too early. If the number ranges are OK, that's also a possible area to check.