Update was terminated during PO creation

Question

Dear All,
we recently copied the client in to a newserver, now we are doing testing
while creating PO i am getting error Update was terminated by the user xxxx, i checked sm13 (updated requets)
i found error status as Error in V2 Part
1     ME_CREATE_DOCUMENT             V1                                 Processed
2     EINKBELEG_WRITE_DOCUMENT     V1                                 Processed
3     MCE_STATISTICS_UPD_V1             V1                                 Processed
4     MCE_STATISTICS_UPD_V2              V2                                   Error
5     ME_CREATE_MRPRECORD_PO     V1                                 Processed
6     HANDLE_TEXT_ARRAY_AFTER_COMMIT          V1                 Processed
7     ME_UPDATE_QUOTA_DIALOG                           V1               Processed
8     OS_UPDATE_CLASS                                           V1          Processed
9     RV_MESSAGE_UPDATE                                           V1         Processed
here row now 4 showing error if i double clicked on it 
system showing
Status of update module alert box has come
function module  - MCE_STATISTICS_UPD_V2
status                  -MCE_STATISTICS_UPD_V2
Report                  -LMCS4F10
Row                     -1,262
Error details           class-00       number-671
00 671: ABAP/4 processor: LOAD_PROGRAM_NOT_FOUND
i found buttons 1)ABAP Editor (F5) 2)ABAP short dump (F6)
if clicked on abap short dump
Short text
    Program "RMCX0006 " not found.
What happened?
    There are several possibilities:
   Error in the ABAP Application Program
    The current ABAP program "SAPLMCS4" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    or
    Error in the SAP kernel.
    The current ABAP "SAPLMCS4" program had to be terminated because the
    ABAP processor detected an internal system error.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
keep them for a long time.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_PROGRAM_NOT_FOUND', was not
     caught in
    procedure "TMC2F_FROUT_CALL" "(FORM)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    On account of a branch in the program
    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
    or a transaction call, another ABAP/4 program
    is to be loaded, namely "RMCX0006 ".
    However, program "RMCX0006 " does not exist in the library.
    Possible reasons:
    a) Wrong program name specified in an external PERFORM or
       SUBMIT or, when defining a new transaction, a new
       dialog module or a new function module.
    b) Transport error
Regards
Gopala.S

Answer 1

Usually this error I anticipated were either related to printer message not configured properly, or accounting document not updating correctly. Check either or and see where the problem is.
Check this blog I wrote on this error:
I came across one problem at one of my projects which I would like to share for everyone's experience.
The problem was when client was doing MIGO and when he was saving the document, it was making the MM document, but when you hit back button or go for display it
came up with this error 'UPDATE WAS TERMINATED'. This problem came up in both MIGO and SD billing document posting.
Now I had to jott down what the problem really was, so I started closing up on problem, by creating many PO's and doing MIGO'S against them with different document types, all went great and those documents got posted, but when I used the same GL'S as client was using as he was charging it to cost center and the GL'S used there were consumption GL'S,those GL'S were causing the problem. How I found out that GL was causing problem, as I used another GL which was not for consumption and the document got posted.
Now as the problem got cornered, now we had to figure out how to solve it. Here at client we have two plants, one for Pakistan and one for Philippines, so I checked the same scenario on Pakistan and the document got posted with consumption GL as well. So now its more clear that problem is with client Philippines posting.
So I sat down with (ABAP) consultant to check out the problem. He went through his checking and pointed out that one document No.  40000400 was not getting updated. Now the question came what document this number is assigned to. Suddenly it clicked my mind to check the client Pk document which was posted with same Gl, so when we displayed that document we came to
know that this number range was getting assigned to CONTROLLING DOCUMENT.
So we went back in customizing, and found out that CONTROLLING DOCUMENT current number was stuck on 40000100, whereas the last number recorded in table was 40000400, so we updated the current number there and thats the end PROBLEM SOLVED. This controlling document Number was causing this problem on both MIGO and SD billing document.
Another solution which came to our mind was to clear the Buffer, so that the number ranges of the clients gets updated and we notified our basis person as well but in mean time we solved the issue.
Edited by: Afshad Irani on Aug 5, 2010 2:51 PM