SM13 - Update was terminated - ISU_S_LOYALACC_CHANGE

Hi,
There is custom report for loyalty points calculations. it calculates and saves record in ELACCZ table. When we run report for large numbers of CA, it gives SAPoffice express info - Express document "Update was terminated received" from ..
This error can be seen in SM13 transaction, this tcode shows the data when update was executed and also brings us to the point where it failed in debug mode.
I analysed that error is generated in FM ISU_S_LOYALACC_CHANGE which internally calls ISU_LACC_WRITE_DOCUMENT.
From data its found that the exporting parameter X_OBJ-LACC-IELACCZ[] of ISU_S_LOYALACC_CHANGE contains duplicate record which fails the validation in ISU_LACC_WRITE_DOCUMENT. It should not contain the duplicate record.
It is sure that while the passing the X_OBJ, X_OBJ-LACC-IELACCZ is having unique entries only. but seems like ISU_S_LOYALACC_CHANGE adds one existing entry again in X_OBJ-LACC-IELACCZ[].
This is the issue happnes in 2-3 in range of thousands of CA. There is no particular SAP note for this.
Please suggest.
-Murtuza

Hello,
Just a suggestion...if I understand the issue correctly..
You should check the setting within the customizing table ELACCTAB....
If you have selected field Contract: seperation is choosen via contract, for each contract a new tab strip is displayed...
If you set this to division and only one tab strip should appear and ALL the contracts should be displayed....
I hope this is helpful for you.
Regards
Olivia

Similar Messages

'update was terminated' while creating billing document VF01

Hi all,
i need a solution urgently ..except for paticular document no all documents that i post using VF01 create successfully document no.
but for a paticular document no(may be it is of some type that i am unable to) while creaing billing document no it gives a message 'document created successfully' ,but when i try to click any button after that e.g BACK it shows a messge 'Update was terminated for author ....' in my inbox. and vf03 shows the documentdoesn't exist.
in st22 i checked one dump . when i gave a break point at that point the cursor never reached the code.
I also checked SM13 and it showed all fms as init. and one fm 'RV_MESSAGE_UPDATE ' as error . i aws unable find the fm in the main program .
one more thing when i create bill document for other document type it shows messge 'Document saved ....(no accounting document created)' but for this one i am getting messge 'document saved.......' .
I asked one collegue he told me might be some OSS notes required for it . i am working on a unicoded system ECC 6.0 version.but he is not sure .
Has any body faced the same problem..and what was the soln....if oss notes are required than how could i find it..and what was the no...........
THANKS IN ADVANCE ...................

THANKS for the reply.
i am new to sap .can u tell me in detail where actually i can check for number range of the document . one more when i checked the sm13 and started debugging it gave me for a certain character set (may be in chineses) present in the table ,the transfer command gives a dump. now the problem is it is too long 132 and don't no forwhich character it gives an dump.how can i check the characters maintained in the system. it gives a dump CX_SY_CONVERSION_CODEPAGE ,At the conversion of a text from codepage '4102' to codepage '4110':
i am not sure this causes the mesages 'Updation was terminated' . what u people think.
thanks ..

Exprees document update was terminated received from author "laxman"in miro

Hi MM experts
My user trying to create invoice wth reference po no in miro t.code during saving system showing error Exprees document update was terminated received from author "laxman"i have checked in transaction OMRJ t.code ,there is no overlap in number ranges.number ranges also available.in sm13 t.code i checked error shown below
function module: MRM_INVOICE_DOCUMENT_POST
status :Update was terminated
Report:LMRMEU01
Row:77
error details class M8,NUMBER 185
Invoice document 5105785402 2011 could not be created
IN MIR4 t.code I CHECK THIS NO 5105785402 THIS ALREADY EXISTING INVOICE NUMBER SHOWN.WHY SYSTEM TRIGGERING
THIS NUMBER IN SM13.PLZ SUGGEST
Regards
Mohan

This type of express document may cause due to over lap of number ranges and if the same transaction is run by diff users at same time...........................
In your case there is change in number range assignment in current number.....
Check the last consumed number in the system and assign the coming number range in current number...
Hope this may help you.
BR,
Patil

Express document "Update was terminated" received from author in J2IUN.

Hi,
Pl. help
At the time excise utlization this message is come
Express document "Update was terminated" received from author
Suresh Yadav

hi
"For your update terminate problem please proceed accordingly
goto SM13, there you can see the updates terminated & their logs.
Click on one of the Updates terminated with transaction.
Double click on the line , you will see alist of Function modules, click on the function module in red, here click on the log to see more details on the reason for update termination.
in the dump anlysis you can see the reason for dump.
Act as per the dump anlaysis. usuall reasons for the dump is any new changes to the program or number range error ."
Please take help of ABAPEr for Dump analysis , if it is sytem issue take hlep of BASIS
Thanks & Regards
Kishore

Express document "Update was terminated" received from author in MM01

Hi gurus,
When we are trying to create the MM by using the t-code MM01 we are getting the error message as Express document "Update was terminated" received from author "XXXX". Based on this error we have verified the t-code SM13 and received the below details and there is no dumb in ST22.
Update was terminated
Created       SOLIYAPPAN SADASIVAM on   23.11.2011 ; 05:07:18
Update was terminated
System ID....   MD1
Client.......   500
User.....   SSADASIVAM
Transaction..   MM01
Update key...   4ECC6061B2567110E10080000A795665
Generated....   23.11.2011, 05:07:18
Completed....   23.11.2011, 05:07:18
Error Info...   Error inserting in table MBEW
Please suggest me how to fix this issue.
Thanks
Sada

Hi Jürgen,
When we verified SM13 the error is occuring as below when we double click the SM13 error.
1    MATERIAL_UPDATE_DB        V1 (no retry)     Error
Please suggest me how to proceed further.
Thanks
Sada

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

Hi All,
We are getting the below error message at the time of goods receipt at receving plant for STO OBD delivery, when user trying to post the GR, then GR number created and when they try to open the number , then they get this error message.
Express Document "update was terminated" received from author
When we went in to SM13 and saw that everything is fine , there was no message in red.
Erro details showing the s032 update error with Internal session terminated with a runtime error DBIF_RSQL_SQL_ERROR.
Short text
SQL error "-413" when accessing table "S032".
What happened?
Error Text of the Database: "SQL0413N Overflow occurred during numeric data type conversion. SQLSTATE=22003 row=1"
Please help to solve this issue ASAP.
Thanks,
Muru

Hello
This is probably an overflow of a field on the infostructure S032.
Please check this table for this material and plant combination and observe if there is any field with a high value.
As a workaround, you may deactivate the updating of S032 via OMO9 to "no updating" to avoid the dump.
Best regards,
Caetano Almeida

MRKO Error : Express document "update was terminated" received from author

Hi Gurus,
When settling Consignment through MRKO we are getting error 'Express document "update was terminated" received from author xxxx' in ECD system.
At workplace inbox, the error shows "Error Info... XS 007: Address invalid".
Please note that I am not getting any short dump at ST22 for the same error.
My queries are:
1. How can I create a short dump for this error....this will help in analyzing the issue.
2. What are the probable reasons for this error can be.
Thanks in advance for helping.
Regards,
MC

Hi,
I have tried SM13 and getting ERROR XS007(Address Invalid).
Diagnosis says:
The address specified is invalid or initial (address value, address type INT).
Procedure:
Enter a correct address that is suitable for address type INT.
The formats are:
1. INT (Internet Mail Address): <name>@<domain> or comment<name>@<domain> or <name>@<domain>(comment)
2. FAX(fax addresses): <country><number>
ETC
Now as already told, I have properly maintained mail-id in "Email" field & "StandardComm.Mtd" field as E-Mail of the Vendor Master.
The mail ID is my official ID and working.
Please advice further.
Regards,
MC.

FMBBC Express document " Update was terminated error"

Hi ,
while saving data FMBBC i am getting saved message , after that if i come out of the Tcode i am getting message as
Express document " update was terminated".I was debugging the standard code found that the error comes from SXOP table entry, This table is get filled from FM SO_EXPRESS_FLAG_SET. But this FM is called from background I think. There is no job also created.After displaying the message automatically the SXOP table entry is get deleted. I want to debug this FM or wht is the reason for displaying message.
Regards,
siva kumar

Following steps may help you.
1. GO to SM13 transaction.
2. Check your update request.
3. You can see exact point in the standard program where you are getting this message

Express document 'Update was terminated' in vf02

Hi Gurus,
I am getting Express document 'Update was terminated' error while triggerring customized
output type in vf02.
i found dump in st22 and describes as below.
Error analysis :
This program is triggered in the update task. There, the
following ABAP/4 statements are not allowed:
- CALL SCREEN
- CALL DIALOG
- CALL TRANSACTION
- SUBMIT
Pls kindly suggest me what could be the reason

Hi Sheshikanth,
you have an exit in the update section of the transaction VF02 calling one of those statements (CALL...). This is prohibited.
Go to SM13 and follow the error. You will find the code that is causing your problem.
regards,
Edgar

In update task & Express document Update was terminated

Hi all
Need help!
Requirement: When i do confirmation through CO11N i have to do GI through a BADI.
Solution: I have written a wrapper Update module(internally has /AFS/BAPI_GOODSMVT_CREATE) with Start delayed and called that module(in update task) in the method MB_DOCUMENT_BEFORE_UPDATE of the definition MB_DOCUMENT_BADI.
It works fine when every thing is correct, but if GI fails its still confirms the confimation and "Express document Update was terminated" pops up when i push the back button. I have written a abort statement in the update module if goods movement fails. When i check SM13 it shows the reason for erroring out. But my requirement is to stop the complete transaction if GI fails and put the error message at the bottom of screen(CO11N)
How can i do this?
Appreciate any suggestions.

Hi,
I don't think that it is possible. It's too late to call rollback. The FM in update task is called after command COMMIT WORK. Here is a quote from ABAP documentation:
If during the update an error occurs, the update work process executes a database rollback, returns the log record with a note into table VBLOG and informs the user whose program has created the log record by SAPMail. After removing the error cause, the returned log records can be updated again.
So you should call that module only in case that you are 100% sure that it will be processed correctly.
Cheers

Error :Display document : Update was terminated.While displaying the PO

Hi All,
I am creating a PO with respect to contract in SAP 4.6C system using ME21.PO is getting created successfully.But when I want to display the same in ME23 it giving me a message 'Display document : Update was terminated'.( an express message is getting generated to view in SBWP transaction code ).
I went through some of SDN forums and checked the tcode SM13 to resolve the issue .I found that there is no ABAP dump got generated for the same .
Please help me to resolve the issue ..
Regards,
Praveen GB.

Hi Lakshman.
I did that, systesm is showing below error :
1 ME_CREATE_DOCUMENT V1 NORMAL Err
when click on that ,I got one more window with an option to check ABAP dump,But there is no ABAP dump exists for the same.
I cheked in ST22 also there is no DUMP available for the above issue.
Please let me know how to crack this issue.
Regards.,
Praveen GB

Error : "Express Document Update was terminated"

Hi All,
           When creating a PO & after saving, I get a message PO number successfully created. But when I press "Back" button I immediately get a SAP mail "Express Document Update was Terminated".
In SM13 - the following error is shown:-
FM:- RV_MESSAGE_UPDATE Error:- TD 427: Element PO_TERMS_AND_CONDITIONS.
I had read all the previous threads relating to this issue.
Based on the above threads I checked the number range & it seems to be correct. So, I'd like to know what causes this error and also how to solve it.
Any inputs related to this would be of great help.
Thanks
Ramky.G

Hi Deivakaniraja,
                     Thanks for the response.
Option 1 - the flag is already unchecked only.
Option 2 - What should be checked in Terms & Conditions?
Hi Volkan,
                  Thanks for the response.
Actually am an ABAPer and am posting this message on behalf of my Functional.
After double clicking the error line in SM13 only I'm getting this one below:-
FM:- RV_MESSAGE_UPDATE Error:- TD 427: Element PO_TERMS_AND_CONDITIONS.
Thanks & am currently debugging the error in program and also kindly let me know if there's any other solution that could be possible.
Regards
Ramky.G

Update was terminated during PO creation

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

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

Update was Terminated when creating a Sales Order

Hiii...
When the sales order was created for the first time in the QAS System, it thrown a update error saying "Update was terminated user XXXXX". I checked the error message in SM13 and found that the error was in
RV_MESSAGE_UPDATE.
When i check the dump of this, there was a dump saying
" The length of COMMON PART "VEDACOM" in program "RVADOR01" is incorrect."
"Error analysis"
The structure of the COMMON PART "VEDACOM" in program "RVADOR01" is
different from the corresponding area in the calling program
"/SMB40/RVADOR01".
Length of the COMMON PART in program RVADOR01: 6600 bytes.
Length of the COMMON PART in program /SMB40/RVADOR01: 2840 bytes.
There is probably an error in the program
"RSNAST00".
This is for V1 Document type for ZA01 Output type.
Error occured at
896 * restore original NAST record (in case TNAPR-RONAM changed something)
NAST = TEMP_NAST.
The same thing is working fine in DEV. But problem in QAS. This is the first document generated in QAS.
Kindly help.
Best Regards,
Srikanth.

SAP Note 1614849 addresses this.
Cause
There are two common reasons for the dump: a) Z-program or b) Incorrect
Program
Resolution
Replace the Z-programs with the standard output
Check the following customizing: SPRO > SD > Basic Functions >
Output Control > Output determination using the condition technique >
Maintain Output Determination for sales documents > Maintain output types.
Select Output type ‘BA00’, double click on “Processing Routines” and change for
medium 1 the program from ‘/SMB40/RVADOR01’ to for example‘RVADOR01’

Update was terminated '' received from author

Hi Experts
Any clue why this error comes while performing goods movement
update was terminated '' received from author
I've was told in the forum to check in SM13
Was able to see the following error message in SM13
00671: ABAP:/4 processor: SAPSQL_ARRAY_INSERT_DUPREC
Thanks

abhi,
as max and siva have told, check in ST22...
there, check the source code extract on which line it failed. you can also check what values were there at that particular time by checking the variable stored in that dump as well...
if you are still note sure, click on that source code(shown in that dump->source code extract) .. and keep a break point there and then see what really happened there by re-executing your transaction.

SM13 - Update was terminated - ISU_S_LOYALACC_CHANGE

Similar Messages

Maybe you are looking for