Document Update error

[former_member221515]

I am on SAP ECC 6.0 and i am using new GL concept with two ledgers (leading and non leading ledger).

When i post a document, it gets posted and a new document number is generated. Also the document number status is updated in TCode FBN1. As soon as i go to display document, it gives following error:

Express document "Update was terminated" received from author

Let me know what is the error?

Is there any document type and document number error.

[Former Member · Accepted solution]

Execute program RFVBER00 using SA38 (or SE38). Enter company code, from date and to date of terminations, user in the selection screen. Also select the 'Detail log' checkbox and run the program. The report should tell you what caused the update termination. Looks like a number range issue. I remember getting this error when the current number in number range is different from the most recent document in table BKPF (and/or FAGLFLEXA).

[former_member221515 · Accepted solution]

This message was moderated.

[former_member221515 · Accepted solution]

This message was moderated.

[Former Member · Accepted solution]

Hi,

we have laso faced same problem because some doc was in buffer. contact your basis team.

Regards

[former_member221515 · Accepted solution]

This message was moderated.

[Former Member · Accepted solution]

Since it is a test client, if deletion of all transaction data is not a concern, execute T Code OBR1 and reset all transaction data. This initializes number ranges as well.

[Former Member]

Is this happening in your live Production client or a sandbox client?

[former_member221515]

It is hapenning in test client. Sanbox was running fine.

[Former Member]

This happes to us all the time after a client copy to QAS or DEV is done while someone is in our Production client creating documents.

We have a special ledger (SPL). When someone creates an FI document a SPL document is also created. So each FI document has its own SPL document number

FI = 100000502 and SPL = 1000007217

Here is what we discovered. During our client copy the FI documents numbers get copied first (via some table). Later on the SPL documents get copied. But if someone in in PRD still creating documents there will be additional SPL documents copied that aren't linked to an FI document.

So after the client copy the target client will be as follows..

FI = 100000502 andSPL = 1000007217

[Former Member]

I didnt finish my last post...

FI = 100000502 and SPL = 1000007217

SPL = 1000007218

SPL = 1000007219

So when you create the next document and the system attempts to create the SPL document 1000007218 it already exists and then we get the "express update termination" error.

In the example above after the 2nd attempt (because thats how many documents are out of sync) the third attempt will be successful. Since this occurs in our test client we can easily replicate the attempts to get things bank in sync.

In other words, by the time we attempt FI # 100000505 the system can succesfully create the special ledger document number. I know there is probably an easier way (perhaps by deleting the additional SPL documents that don't have an FI document to correspond to).

[former_member221515]

I am not using special purpose ledger. I am using new GL concept

[Former Member]

Hi

Please check with your basis team

Thanks & Regards

Phaneendra