Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC

[Former Member]

Hi All,

We are repatedly getting this while creating DBM order using tx /dbm/order01. it is happening after doing the client copy. the issue seemed to be with BSIS table and probably the document # range is not correctly set due to the client copy.

Please find the details of the Dump.

Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC

Exception CX_SY_OPEN_SQL_DB

Date and Time 03/24/2011 12:36:31

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

come across a statement that unfortunately cannot be executed.

Could any 1 help.

[Former Member]

I think this is a number range issue. I've seen this in the past where during the client copy, your current number range is 1000 but transaction data is still coming in. That being said when you're complete with the client copy the number range and transaction data is out of sync. What you need to do is locate the number range and set the current number to match the transaction number.

Hope this helps.

[Former Member]

Could you please help us with the tx to find the number range and how to do the changes.

[Former Member]

This is pretty basic stuff. Your financial analyst should be able to do this.

Rob

[Former Member]

I am a Basis guy. so i do not have much information about this.

it would be great if you could help..

[Former Member]

Is any 1 able to help.

[Former Member]

Your FI functional analyst should be able to determine the number range. If not, you need to post more details about the transaction you're trying to post.

[Former Member]

What is tx? Transaction code? The tcode for number ranges is SNRO but you need to know which number range to change. This is where the FI functional analyst comes into play.