Update terminated- MCV_STATISTICS_UPD_V2_ORDER.

[Former Member]

After saving the sales order, I am getting the error -

"Express Document - Update Document Terminated".

SM13 shows the message error

MCV_STATISTICS_UPD_V2_ORDER. Can you give me some idea how to fix this ?

[Former Member]

Hi,

Have you activated LIS( logistic information systems). if yes, go to those settings and make it properly.

If you don't need LIS, deactivate it in sales order, item category, customer master and material master.

Regards

Sukumar

[former_member217000]

Hi Sunil,

How did you solve this problem? I am also facing the same.

Please reply.

Sameer

[jiteshmehta]

Dear Sunil

if you have not archived the sales document the cause is a problem by posting the sales document.

With the transaction SM13 vou could find all aborted postings. then in the most of the cases you will find an error message and the program where the problem occurred:

1 RV_SALES_DOCUMENT_UPDATE V1 NICHT NACHVB. err <<<<

2 SWE_EVENT_CREATE_IN_UPD_TASK V1 NORMAL init

3 CASH_FORECAST_SD_ORDER_UPD_3 V1 NORMAL init

4 MCV_STATISTICS_UPD_V1_ORDER V1 NORMAL init

5 MCV_STATISTICS_UPD_V2_ORDER V2 NORMAL init

6 MCV_UPDATE_CM_ORDER V1 NORMAL init

7 VERKBELEG_WRITE_DOCUMENT V1 NORMAL init

8 RV_MESSAGE_UPDATE V1 NORMAL init

Now please doubleclick on your entry:

00 671: ABAP-Prozessor: SAPSQL_ARRAY_INSERT_DUPREC

After that you could press the button 'Editor' and the you will find the program where the program stopped. Now it is important why this program stopped there. You have to analize the according data.

The cause of the most dumps is to find in the dialog session not in the posting session.

You could only find the problem if you are familiar with ABAP coding and debugging otherwise you have to ask a collegue which have experience with this analizing (maybe a consultant). Furtehermore it is important that you could reproduce the problem otherwise it is very hard to find the problem.

I hope this information help a little.

Best regards,

Jitesh