10-25-2011 7:20 AM
Hi All,
After client refresh from Production to QA reports which are having mail options are dumping saying that Abap Dump
"SAPSQL_ARRAY_INSERT_DUPREC"
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.
Regards
sas.
Edited by: saslove sap on Oct 25, 2011 8:34 AM
10-25-2011 7:56 AM
Check the SAP notes relevant to "SAPSQL_ARRAY_INSERT_DUPREC"
I found some like 196113, 62985, 777712.
10-25-2011 8:56 AM
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:
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
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
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.
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 "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,
10-25-2011 1:22 PM
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.
10-25-2011 4:29 PM
So which number range need to be updated .. Kindly let me know
Regards
sas
10-25-2011 4:39 PM
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.
Rob
10-25-2011 4:44 PM
Hmm Yeah I work as Basis, functional and techincal. Hope you understand my issue and this issue
Regards
sas
10-25-2011 7:00 PM
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.
10-25-2011 9:51 PM
I hear ya..
Hmm Yeah I work as Basis, functional and techincal. Hope you understand my issue and this issue
Regards
sas
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
[581559|https://service.sap.com/sap/support/notes/581559]
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.
10-25-2011 7:17 PM
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.