Express Document "Update was terminated" received from author " " in MIGO

[Former Member]

Hi Experts,

After posting a PO and exiting from the transaction i get an dialog box of Express Document "Update was terminated"  received from author.

and a dump of Call screen in Tcode MIGO.

Did also check in st22 for Active calls it gave a include program and the line numbers where it was affected.

How can it be solved

Thanks

[former_member212002]

What is the dump you get??

[Former Member]

Is it a duplicate key error?  If so on what table?

[Former Member]

Hi,

Normally this error comes when database encounters inconsistency.i.e Duplicate entries in database

Check all your number ranges of MIGO..may be duplicate number ranges are there.. for that object

Regards

Tejas

[former_member196490]

Please post the dump you are getting. Thsi message is displayed when some error is encountered while updating the Dbtables.

You can keep an external  breakpoint at the statement that is giving the dump. Then before executing MIGO,activate update debugging to check the issue.

[Former Member]

Hi Shamal,

Check the termination details in SM13 and share here.

BR.

[Former Member]

Hi All,

When i post the PO it should be printed but it does not print.After posting the PO it says that document has been created but does not show any history in Table ekbe.

The detail dump says

"Posting_ Illegal_Statements"

Statement " Call Screen" is not allowed in this form

Thanks

[Former Member]

Hi Shamal,

Seems you have a custom driver program whose logic is incorrect. Please refer http://scn.sap.com/thread/81254. It will give you clues.

BR.

[Wil_Wilstroth]

Hi Shamal,

Recently, I did get "Update Was Terminated" message pop up, my case was different than yours. Mine was due to a print program (driver) that's causing it.

However, in your case, you might want to :

1. Go to SM13, and check what is causing the "Update Was Terminated". SM13 holds these messages here.

2. Click on the line "Update Was Terminated" and see which program is causing it.

Your error, in your replied, is pretty vague... I guess guys up there who are helping you would love to have more information so they could help you further.

Regards,

William

[former_member195402]

Hi Shamal,

there have been several similar issues in SCN like

http://scn.sap.com/thread/876475

all dealing with program SAPLKKBL.

Please post your dump and show the called program list to us.

Maybe there is a customer exit or BADI or BTE which causes this issue.

Similar issues are described in SAP notes 1472777 and 1573274 (not matching MIGO).

Regards,

Klaus

[Former Member]

Hi All,

In SM13 i got this details.

1

DISPSATZ_BESTANDSFUEHRUNG

V1

Initial

2

ME_UPDATE_GOODS_RECEIPT

V1

Initial

3

ME_CONFIRMATION_EKET_UPD

V1

Initial

4

MCE_STATISTICS_UPD_V1

V1

Initial

5

MCE_STATISTICS_UPD_V2

V2

Initial

6

MB_UPDATE_TASKS

V1 (no retry)

Initial

7

MCB_STATISTICS_UPD_V1

V1

Initial

8

MCB_STATISTICS_UPD_V2

V2

Initial

9

CKML_F_POST_INDEX

V1 (no retry)

Initial

10

POST_DOCUMENT

V1

Initial

11

ISJP_INVSUMIT_SAVE

V1

Initial

12

ISJP_INVSUM_SAVE

V1

Initial

13

G_GLDB_POSTING_A

V1

Initial

14

AC_DOCUMENT_MM_UPDATE

V2

Initial

15

RV_MESSAGE_UPDATE

V1

Error

Pls Help.

Thanks

[Former Member]

Hi,

Please check number ranges are correct or not for migo accouting or Migo document

Please take help of Functional person once..

Regards

Tejas

[Sijin_Chandran]

Hello Shamal ,

It seems someone has played with the number range settings for MIGO documents .

Confirm the same from your functional consultant.

[former_member183378]

Hello Shamal,

Please check this  thread to fix your error.

http://scn.sap.com/thread/1490921

Thanks & Regards,

Lakshmi S