Sales order not saved and number consumed

[former_member1195642]

Hi

While creating sales order with billing plan, sales order no. is populated in popup screen but while saving it is not saved and number is consumed. The number is not there in VBAK table.

I get the following run time error in st22.

SAPSQL_ARRAY_INSERT_DUPREC

"SAPSQL_ARRAY_INSERT_DUPREC"

"SAPLV60F " or "LV60FU05 "

"BILLING_SCHEDULE_SAVE"

I think it is a problem with billing plan number range but cannot simulate and how do I fix the root cause. Please need the experts' opinion.

Regards,

Neeraj Srivastava

[sarthak_mohantysd · Accepted solution]

Hello neeraj,

While creating sales order with billing plan, sales 
order no. is populated in popup screen but while 
saving it is not saved and number is consumed. 
The number is not there in VBAK table.
I get the following run time error in st22.

SAPSQL_ARRAY_INSERT_DUPREC
"SAPSQL_ARRAY_INSERT_DUPREC"
"SAPLV60F " or "LV60FU05 "
"BILLING_SCHEDULE_SAVE"

I think it is a problem with billing plan number range 
but cannot simulate and how do I fix the root cause. 
Please need the experts' opinion.

Could you please update the message number and message details which you are getting at

Sales Order processing event ? Also check whether the Billing plan number range is set in the T-code "SNRO".

Regards,

Sarthak

[former_member1195642 · Accepted solution]

Hi Sarthak

I do not get any message while processing sales order. It saves the sales order also but I cannot display it and number is consumed. Billing plan number is ok as next attempt goes successfull and order is created .

Regards,

Neeraj Srivastava

[former_member1195642]

Problem still unresolved

[former_member187989]

On new transport request to production client,

Sales document number range might be overwritten & also check current number

in SNRO for object "RV_BELEG".

Edited by: Jeyakanthan A on Mar 11, 2011 3:02 PM

[Former Member]

Hi,

Answer is in your error massage. SAPSQL_ARRAY_INSERT_DUPREC - duplicate records

This error is occurs most of time when there is number range conflict.

Example - You already created some document say SALES document in system 1 to 100 now next number is 101

But Now you reset this number range and try to create SALES order and save then system will give this error.

because number 1 is already in database.

So check all number ranges, and also take help of ABAPer and Basis to veryfiy from there side.

kapil

[Lakshmipathi]

Have a look at the following notes

1) Note 406861 - Update termination when saving sales order or contract

2) Note 497073 - Program termination when saving an order (DUPLICATE RECORD)

3) Note 835546 - CJ20N: termination with exception SAPSQL_ARRAY_INSERT_DUPREC

thanks

G. Lakshmipathi

[former_member1195642]

Hi Laksmi

Thank you very much for your reply.

Regards,

Neeraj Srivastava