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

Reports are dumping after client copy

Active Contributor
0 Kudos

Hi All,

After client refresh from Production to QA reports which are having mail options are dumping saying that Abap Dump


Error due to duplicate record entries, Dump analysis is saying. Could any one revert me back what should be done to this issue.

When I am searching I figured it out to be Make SNRO number range settings should be done, I have no idea about SNRO number rangings, So which piece (Object) of SNRO should be modified to set this same. ?.

awaiting for you reply.



Edited by: saslove sap on Oct 25, 2011 8:34 AM


Active Contributor
0 Kudos

Check the SAP notes relevant to "SAPSQL_ARRAY_INSERT_DUPREC"

I found some like 196113, 62985, 777712.

0 Kudos

Oops Sorry Gautham ,

None of them is solving my Huge bug.

below is details of the bug, if you can do any help that wwould be great, Mean while I am searching for options:

Exception              CX_SY_OPEN_SQL_DB
Date and Time          10/09/2011 11:18:01

 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 "SAPFSSO1" had to be terminated because it has
     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

     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.

 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 "SOES_INSARR" "(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,

0 Kudos

Please check the number range for that object.

System may be trying to create one number where that number is already copied in the system from production.

In that case you have to change the lnumber range data.

0 Kudos

So which number range need to be updated .. Kindly let me know



Former Member
0 Kudos

This is not an ABAP issue. Client copies are basis and number ranges are functional (the area depends on the particular number range). So get your functional analysts to talk to your basis analysts.


0 Kudos

Hmm Yeah I work as Basis, functional and techincal. Hope you understand my issue and this issue



0 Kudos

Hmm Yeah I work as Basis, functional and techincal. Hope you understand my issue and this issue

Quite honestly, I never understood why companies would invest in SAP software but wouldn't invest in the team supporting it. But I do understand that it's not your problem right now and we have a very small team (more than 1 person though) as well.

You've mentioned that short dump occurs when using mail. There is an SDN post that might be related:

Also there is much more information in the short dump than posted above. Use your analytical skills; if you're doing so much, you are supposed to be very smart.

0 Kudos

I hear ya..

Hmm Yeah I work as Basis, functional and techincal. Hope you understand my issue and this issue



Anyway I looked up the attributes of the program SAPFSSO1and it's title is

SAPoffice: External performs for DB manipulation

and found an SAP note regarding your issue


excerpt from note

The number range object SO_OBJ_ADR does not exist. When you send to a 
new address (fax or Internet), no number can be taken from the number range, 
and the above error message appears. The missing number range object can be 
caused by an incomplete client copy or a restarted system.

Related notes 140965, 766112.

Former Member
0 Kudos

Client copy would need to also copy all number ranges, to avoid just the kind of scenario described. You could compare all number ranges from the two systems, and modify the target system to have a higher current number.