Express document "Update was terminated"

[Former Member]

Hii all,

when i do PO with check mark of INFO UPDATE or, if i do Info record, after saving the document when i switch to back or another t-code, i get a error Express document "Update was terminated___"_ . plz give ur valuable ideas.

[former_member193326 · Accepted solution]

Hi,

Please go to transaction SM13 and select "interrupted updates flag".

Click ENTER and you will find the erroneous module. Double click this

module and you'll obtain a "pop-up" window in which technical data

of the error is shown.

Please send us all this information. Also click the button which says

"ABAP4 dump". If you obtain any dump please send the most important

search terms from the dump.

Best Regards,

Arminda Jack

[Former Member · Accepted solution]

thanks to all, i checked all number ranges, its correct. i am not able to find out that where is the lack.

yes, some module name is coming in picture. but its different with ME21 & ME11.

for ME21,

Report name is: LMEIUU12, ROW :31, Class : ME, Number :807. System error: error during insert in table EINA. few of them are ME_CREATE_DOCUMENT, EINKBELEG_WRITE_DOCUMENT, MCE_STATISTICS_UPD_V1,

and for ME11,

report is :LMEIUF01, class:06 and number 821.

[former_member187989 · Accepted solution]

Pl check info record 'Current number' in number range using OMEO,system might be using already existing number range,

which may cause this error.My guess is this problem may occur after transport request where number range in test

environment is also getting transported.

[Former Member · Accepted solution]

i checked very carefully the number ranges, current number is zero in OMEO. tell smth else. If i remove info record link from all, then this issue is not coming. what can be the missing point?

one thing more, this error is coming for my all company code on this client.

Edited by: Ms. nisha on Mar 2, 2011 6:25 AM

[former_member193326 · Accepted solution]

Hi,

You said that you have carefully looked at number ranges, did you also checked Object EINKBELEG Number Ranges for Purchasing Documents?

Can you please check the following:

Use transaction SE17 or 16 to find out the highest number that

is saved on the database. Then use transaction SNRO for the

number range object concerned and verify what is the current number

range counter. If this number is smaller than the one found with

transaction SE17, then this has caused the problem. In this case

please change the current number range counter to a value higher that

the one found in SE17. There are problably two number range values

for purchase orders and info records. Please check both ranges.

Best Regards,

Arminda Jack

[JL23 · Accepted solution]

What error message do you see in SM13 ?

That the express document you received is caused by number ranges is just an assumption of, but the only place you will know the real root cause is by clicking the header icon in SM13 for the failed posting.

[Former Member · Accepted solution]

yes, correct. this issuei coming due to number ranges issues only.

in system, INFO RECORD number was not getting updated automatically. so, there is need to change manually Current status., why it was happening, that cant say.

Issue has solved.

Thanks to all.

[Former Member]

closed.

thanks to all.

[former_member533946]

Hi dear,

Take halp of your BASIS guy.You can see the details of the message in the inbox of SAP business work place.

You can also get the details in SM13 and ST22.

[Former Member]

Hi!

It's hard to analyse your problems are there are lots of details missing...

Here some ideas.

please check in SPRO the screen layout of the purchase inforecord - are there for example some fields marked as obligatory?

Are the number ranges maintained, and are there a few numbers left?

have fun

flo

[Former Member]

please check the no range for Inforecord.

if the generated no range is not after the current range, u will get the error.

[JL23]

as always with update termination you have to execute SM13 to list your terminations.

then select one and click the header icon.

It will tell you why the update failed.