Error during Goods Issue "Update was terminated"

[Former Member]

Hi,

While doing Goods Issue (Mov Type 201), the system save the Document, but when we display the Document, the System gives the following message:

Update was terminated

System ID.... DEV

Client....... 400

User..... MMUSER1

Transaction.. MIGO

Update key... B4E937DFC88FF1F3998B00215E73E462

Generated.... 25.03.2010, 14:09:53

Completed.... 25.03.2010, 14:09:53

Error Info... F1 109: Line item 001

Please note that using MMPI, we have opened the back period. There is not problem in posting the Goods Receipt/ Goods Transfer/ Invoice Posting.

Please help.

Regards,

[JL23 · Accepted solution]

execute SM13 and list the posting failure, click the header icon to see the error message.

[Former Member · Accepted solution]

Hi,

Thanks for the reply.

Error details:

Class : F1

Number : 109

Error: F1 109: Line item 001

Report: LF005S01

Information: (50) = VB_WITH_ENQUEUE, VB_ENQUEUES_RELEASED,

Update key: F4F837DFD7A7F18F998B00215E73E462

Regards,

[JL23 · Accepted solution]

the message text for F1 109 is : Line item & already exists in document & & &

SAP does not allow to create duplicate records in its database.

try again, if you get the error again, then there must be something wrong with your number range.

[Former Member]

contact BASIS consultant. they will help in solving this type of errors.

This is not a problem with mm

[JL23]

I am pretty certain that this is an MM or FI issue, certainly not something for Basis admins.

They may have the best knowledge on transaction SM13 for analysis the root cause, but it is caused by wrong functional customizing.

[Former Member]

hii

This is also due to authorization problem with ur id .

SO once this erroe comes in screen, jus run transaction code SU53 , u'll come to know whta are the objects are missing in ur id.

So check with basis team and rectify the issue.

thanks

[Former Member]

Hi,

I have got SAP_ALL.

Regards,

[JL23]

an update termination happens only in an unexpected case, no authority is an expected case and SAP would issue a status message long before posting.

In your case SAP determined a document number (item number) that is already in the data base. hence it can technically not store the document.

such things happen if one transports a number range from a development system, but in dev systems the current number is much lower than in a production system, so the next number that is taken from the number range is already used and stored in a table.

or if one resets number ranges after an archiving run or for any other intention.

[Former Member]

Hi,

We are using Standard SAP Number Range.

I was able to do the Goods Issue till today morning.

The error came when I changed the Period using MMPI. I donu2019t know the exact reason, but we have not changed the Configuration.

Regards,

[JL23]

you may have number ranges per year, probably in finance.

So you could have determined a new number from current number range but you actually post into the previous year, and the document with this number is already in the database.

[JL23]

SAP describes this situation in OSS Note 31793 - SAPSQL_ARRAY_INSERT_DUPREC during goods movements