topic Re: VA41 - Update termination error - SAPSQL_ARRAY_INSERT_DUPREC in Application Development and Automation Discussions

VA41 - Update termination error - SAPSQL_ARRAY_INSERT_DUPREC

Former Member — Thu, 15 Sep 2011 09:16:52 GMT

Hi Experts,

While saving a contract through transaction VA41 i am facing the update termination error.

Dump Analysis :

Short text

The ABAP/4 Open SQL array insert results in duplicate database records.

Dump provide the following key words to search SAP note's

"SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"

"SAPLV45U" or "LV45UF0V"

"VBKD_BEARBEITEN"

But unfortunately i am not able to find relevant note for this issue.

Saw entries which got populated in DA_XVBKDI, found duplicate entries.

Note : Its is while creation of contract not at change of contract.

Any inputs will be appreciable.

Thanks all in advance.

Regards

Adnan.

Re: VA41 - Update termination error - SAPSQL_ARRAY_INSERT_DUPREC

Former Member — Thu, 15 Sep 2011 12:43:31 GMT

Check for any user exit, enhancement implementation. Please debug the code when the ITAB values are getting duplicate.

Shiva

Re: VA41 - Update termination error - SAPSQL_ARRAY_INSERT_DUPREC

Former Member — Thu, 15 Sep 2011 12:48:10 GMT

I don't think you will find any note for this..

As you may have messed up some codes in any enhancements/ exits.

You have set the UPDKZ variable to I instead of U. This is the reason of getting the error.

Debug the application and check if DA_XVBKDI has duplicate entries. Deleting the duplicate record will solve the issue

Cheers

Mishra!

Re: VA41 - Update termination error - SAPSQL_ARRAY_INSERT_DUPREC

Former Member — Thu, 15 Sep 2011 15:30:07 GMT

Hi,

May be one of the below reasons.

1) Data issue: You are using wrong data to create document

2) Bug in user exit or badi.

Thanks & Regards,

Reventh

Re: VA41 - Update termination error - SAPSQL_ARRAY_INSERT_DUPREC

former_member206439 — Thu, 15 Sep 2011 15:55:13 GMT

Hi A,

This error means that a transaction / program was attempting to commit

information to the database that would result in a duplicate entry in a

table with primary key. Depending on when and where you are getting it it

can be caused by some SAP bugs in Phsyical Inventory Document Clearing,

numbver ranges being out of synchronization after a client copy etc.

If this is your Production system search on OSS for a solution, if this is a

QA or DEV box - check number range object settings etc. to see if you have

become out of line since the last client copy went into them.

If you are using the SAP version below 4.7 then below SAP note may helpful for you.

Note 406861 - Update termination when saving sales order or contract

Thanks

Naresh

Edited by: Naresh Nelapatla on Sep 15, 2011 6:01 PM

Re: VA41 - Update termination error - SAPSQL_ARRAY_INSERT_DUPREC

sjeevan — Thu, 15 Sep 2011 16:50:36 GMT

I think it is number range problem for contract documents, I would suggest you to go to VOV8 and double click on the "Sales Document Type" which is giving you this error (for example VBOS). Now look at the field "No. range int. assig." It will have some number assigned to it (example 09). Note down that number and go to transaction VN01, click on overview and look for the number you noted down in the column NR status note down the number it is the number SAP is trying to assign when a contract is created but that number might already exists in VBAK table.

Solution: So go to VBAK table for document category G and look for the highest number assigned now go to VN01 in change mode and change "NR status" number one or two higher than the highest in VBAK. (for example if the highest number in VBAK of document category G "contracts" is 40073493 change current number in VN01 to 60073494)

Re: VA41 - Update termination error - SAPSQL_ARRAY_INSERT_DUPREC

Former Member — Thu, 22 Sep 2011 14:57:50 GMT

Thanks all for providing inputs.

@Shiva H - No relevant changes are found in enhancement.

@Abhinab - custom code is not setting the UPDKZ as 'I' it is standard.

@Reventh - No relevant changes are found in enhancement.

Faulty data possible... but same data is not reproducing the issue.

@Naresh & Jevan - number range is OK and it is 6.0.

Won't be able to debug as environment is prod. I saw table entries through transaction SM13.

Looking for more information.

Regards