topic Re: Dump at VA01 - command Insert VBKD from table DA_XVBKDI in Application Development and Automation Discussions

Dump at VA01 - command Insert VBKD from table DA_XVBKDI

joo_gaia — Tue, 21 Dec 2010 11:30:46 GMT

The key user is facing an issue for a specific sales order. VA01 is dumping at the include LV45UF0V, form VBKD_BEARBEITEN,

instruction INSERT VBKD FROM TABLE DA_XVBKDI.

The reason of the dump is a duplicate key (run time error: SAPSQL_ARRAY_INSERT_DUPREC exception CX_SY_OPEN_SQL_DB).

I put a break point at this program but it is not stopping. Could you please advise about how can I get the data at DA_XVBKDI or do you have any clue about this error?

observation: we are running version 4.7

Thanks in advance.

João Gaia

Re: Dump at VA01 - command Insert VBKD from table DA_XVBKDI

Former Member — Tue, 21 Dec 2010 11:48:48 GMT

Hi,

Refer oss note 985130 and related notes .

[Refer this link for better help|;

I hope this information helps you.

Manjunath M

Edited by: manjunath4sap on Dec 21, 2010 12:50 PM

Re: Dump at VA01 - command Insert VBKD from table DA_XVBKDI

Former Member — Tue, 21 Dec 2010 11:51:54 GMT

Hi,

If you want to get the data in DA_XVBKDI , Press on Debugger (F7) when the dump occurs , you'll be in debugging mode ,

and you can get the entries in DA_XVBKDI.

Regards,

Srini.

Re: Dump at VA01 - command Insert VBKD from table DA_XVBKDI

Former Member — Tue, 21 Dec 2010 11:52:13 GMT

Hi,

You can check if the Number range object has been altered by some one.

Regards,

Rupesh R Nair.

Re: Dump at VA01 - command Insert VBKD from table DA_XVBKDI

brad_bohn — Tue, 21 Dec 2010 15:20:19 GMT


I put a break point at this program but it is not stopping

You need to turn on the update debugger to hit it, but you can check the contents of the VBKD table prior to be handed off multiple functions in the update task just by stopping at the save user exit or anywhere in the save code. I've seen that error before but it wasn't related to number ranges; I believe it was bad user exit coding that caused it.

You should also have an update terminate record in SM13 - you can go there to view the internal table contents as well.