Update termination in Transaction ME9F

Hello MM Guru’s,
I would like to inform you that we are observing update termination in transaction ME9F for a particular user repeatedly in production environment.
Error in Functional Module: RV_MESSAGE_UPDATE
Error Message: WHT type Z4 missing in vendor master XXXXXXXX
When I check in vendor master data Indicator for withholding tax type Z4 already maintained.
It was strange why when users execute transaction ME9F the above updates terminate happens in the system.
I got a similar issue earlier where at that time Indicator for withholding tax type not maintained in vendor master data and I have informed business to maintain and re execute the transaction ME9F.
Request you to help me on this issue as I said this is a repeated one which is occurring for a particular user and I need to fix it by taking your valuable input.
Revert back in case you need any information required from my end.
Cheers,
Kumar S

Hello Bijay
I was asking you about my analysis (2 different users access ME9F for the same PO) done along with ABAPer whether its correct or not.
In your earlier response you have not responded to my analysis instead you are replying me that experts cant access my system.
I very well understand that our Experts cant access my system but they are always helping me for my all issues with their valuable input.
We just wanted to know whether we are deviating from the issue in this case.
I have also checked what other experts like Jurgen/AKPT & Mallinath suggested me and the analysis given below,
To inform experts that we never use custom print program and we are using standard SAPFM06P print program.But the layout is custom according to our business requirement.
Let me know still you need any clarification from my end.
Regards,
Kumar.S

Similar Messages

Update Terminated on transaction VL01N - VERKBELEG_WRITE_DOCUMENT

Hello gurus,
I'm trying to create a delivery based on a sales order.
When I save the document system says that outbound delivery was created, however after that a pop-up appears saying "Update Terminated" with error info "Error Info... DUPREC:POS&VERKBELEG&0000126659"
If I go to SM13 to check the log system display error on function module VERKBELEG_WRITE_DOCUMENT.
And no delivery document is created.
Do you have an ideia how to solve this?
Thanks and Regards,

Hi,
Refer to note:
[Note 208010 - Update termination in VERKBELEG_WRITE_DOCUMENT|https://service.sap.com/sap/support/notes/208010]
Also check your delivery document number range.
Cheers

Update Terminated" on FB01

Hi there,
Can someone please help,
I get the error "Update Terminated" on transaction FB01.
The error only comes up if one the customer's cards (in FD02->Payment Transaction->Payment Cards) is marked as a default card then otherwise the transaction goes through.
On ST22 and the error message is as follows
Nested call of Perform On Commit:
Caller SAPLT X_HANDLER
Program SAPLT X_HANDLER
Form SAVE_REG
Form %_ORDER_FORM_LEVEL is also mentioned somewhere in the error message.
One more strange thing about this is that the error only comes up in our QA system. The development
system is ok.
Is there anyone who has come accorss this or have an idea of what need to be fixed?

Two possibilities that I can think of:
A) Missing config in QA.
2) Missing transport.
Rob

Update termination error SAPSQL_ARRAY_INSERT_DUPREC with transaction f110

Hi ,
When we executed the transaction F110 for payment runs it gave an update termination error "Express document 'update was terminated' ".
Update was terminated
Error Info 00671: ABAP/4 Processor : SAPSQL_ARRAY_INSERT_DUPREC
Could you please anyone suggest me how to overcome this express document error.
Thanks,
Saran

Hi,
I think u r getting this exception as ur trying to INSERt a record which ia already existing, so try to change the data and Run the tcode.
Revert back if any issues,
Reward with points if helpful ,
Regards,
Naveen

Update Terminated Express document error triggered in VA01 Transaction

Hi to All,
I am facing problem when Sales Order is creating in VA01 Trasaction when document get created but after going to Va02 it is throwing error 'Update Terminated' I studied the Dump analysis and Update Analysis in ST22 and SM13 it is due to GETWA_NOT_ADSSIGNED. I cant understand what may be the problem. Can any one help me, Its urgent
Please help

> > check short dump in ST22 it will show more info on
> > which variable/table is causing this error.
> > one of the posisble reasons - WRONG vlaue in UPDKZ
> > field.
> > to check - set breakpoint to
> > USEREXIT_SAVE_DOCUMENT_PREPARE and at the end of
> this
> > userexit check the value of UPDKZ field in XVBAP,
> > XVBEP,... tables.
> > It should NOT have 'U' in VA01
>
> Thanks,
> Yes what u told is correct, after the
> userexit_save_document_prepare the updkz is becoming
> 'U' n how can we overcome this, i have to harcoded
> with 'I' when that is 'U'.
When i change XVBAP-updkz with 'I' then its not getting error but another error is coming of update termination. Error is 'sapsql_insert_duprec' but i check there are not Duplicate sales order and i also check the number intervals they are fine. Whay may the problem????
Can any one help. plzzzzzzzz.

Update termination error at the time of order creation

Dear gurus,
Facing an error at the time of creation of order.
system is giving update termination error & when we are going in change mode of that order system is giving an error message " SD document XXXX is not in the database or has been achieved"
please treat on priority
regards,
krai

Hello ,
"Update terminated " error has two reasongs.
First is system update was not active and hence terminated
For this to check Goto the transaction code SM13 and check whether the SYSTEM UPDATE is active or not.
If it is active ,
Then click on the Option TOBE updated in the status and execute, then in the next screen you can find some list of documents that are not updated and causing error .
Click on MODULES in the screen and find the erro which causing this error.
Most this kind of error will happen if something in the Funcion Module or USER EXIT is missing.
Please check and revert back if you need further details
Also check the link
http://help.sap.com/saphelp_nw04/helpdata/en/e5/de870535cd11d3acb00000e83539c3/frameset.htm
regards,
santosh

While saving service work order Update termination

Hi Friends,
We have a service order integration with Notifications. First we create a Notification and in turn create as service order.
When the order is saved it goes for a update termination and the error message is " 00 671: ABAP/4 processor: DBIF_RSQL_INVALID_RSQL " for IW52 transaction. Actually when we save it provides the order number but never gets updated in the data base.
Again when we create the order from Notification for the second time, order gets created by skipping a number. For example when we save the order if the ordewr number is 902345 where it is not created , then when we create again the order number is 902346.
Have any one come across such terminations in IW52 for IW32?
Regards,
Selva

Friends,
At last my problem was resolved as it was escalated to SAP and SAP analysed as below,
This problem is caused becuase of the error in database interface. As the database server and the application server is a mix of platforms with different internal character data representations, this error occurs,
The work around solution as narrated below,
" For this we need to set the following parameters on the Default and Instance Profiles:
Profile Name                            Parameter name         Current Value     Recomm by SAP
DEFAULT.PFL                           rdisp/vbname              not set           rdisp/vbname=$(rdisp/myname)
CRH DVEBMGS00 cr1apod        rdisp/wp no vb               2                  Greater than 0
CRH DVEBMGS00 cr1apod        rdisp/vb dispatching        1                  Set to 0
crap0 CRH 20                            rdisp/wp no vb                4                  Greater than 0
crap0 CRH 20                            rdisp/vb dispatching        1                  Set to 0
Inorder to reflect all the changes, System CRH-202 needs to be restarted. Basis have done the above changes through T.Code: RZ11 and CRH indicates the Quality client.
So the profile paprameters will be different in each of SAP systems.
Hope this will be very useful for future reference to all of us.
Regards,
selva

FSCM via WS-RM (without PI ) - Update termination issue

Hello experts .
We are trying to integrate SD with FSCM ( credit management) using WS-RM (without PI).
Details of the issue and steps followed so far.
Ideal Scenario :
Once we create / change a sales order ( in SD ) , the interface Creditworthinessquery_out (WS Consumer ) gets triggered (in SD) and the subsequent response CREDITWORTHINESSQUERY_IN(Provider) is triggered from FSCM (with the details of creditworthiness).Once the query response in received an notification is triggered from SD to FSCM (asynchronous service).
After receiving the query response the functionality of credit check happens while creating / changing the sales order .
Configuration steps followed in SOAMANAGER
We have created end points for all the relevant service interfaces (Providers) , and also created logical ports for the respective consumers.
During the creation of logical ports - for the consumers we used the WSDL (of the providers) as the inbound message action.
(This has been done to all the services query , notification that are relevant in our integration).
Current behavior / issue .
While creating sales order the sales order is not getting saved (getting updated in the database).System allows us to complete the sales order creation process and also we get a message as sales order saved successfully. But then there is a update terminated express document that pops up. Sales order is not getting updated in the database.
When I see the logs/traces in SOAMANAGER I see that the query out is successful , query in has the right response (in warning state though) . But no notification is being triggered ?? 
How to overcome this update termination issue ?
When we see the SM13 log , it points to SLD issue (LCR 010: Internal error in SLD API). why do we need a SLD without PI

Hi ,
Finally we are able to solve the update termination issue . But again we are using a work around .
Situation :
Once we executed the VA01 transaction we were getting update termination issue . After lots of debuggung we found that system was trying to get the Business system details ( Own business system data ) . The table lcrt_clntcache had no values.
Solution
We inserted appropriate values in the Table LCRT_CLNTCACH (business system data ) and now it works .This is a work around we got as of now.Credit checks are happening successfully and also integration is good .
(typically if we define business system in SLD (PI) , and run SLD_CHECK , this table gets populated , but in our case we are not using PI instead we are using WS-RM)
But now few questions arise .
a) Why do we need a business system in case we are not using PI ( typically we define business system and technical system in PI ) and instead using WS-RM ?
b) Is it a good practice to update the table ( as did in workaround above )?
c) Is this any bug and needs to be consulted with SAP ?
Please let me know your views .
Edited by: Vedula Adeep on Jan 16, 2012 8:42 AM

PO update terminated with error - migo

Experts,
Entering a goods receipt in R/3 for an SRM replicated P.O. (using trx.
MIGO). Upon backing out of the transaction, an "update terminated"
message is received with a short dump in the system log.
The Material doc. is posted correctly and all accounting documents are
posted correctly.
We looked at SAP note 131178 but this does not seem to be exactly what
we need.
This error does not happen every time. Sometimes the PO can be posted
without any short dump.
We are on using ECC 6.0 that is connected to SRM 5.5
Any help would be greatly appreciated.
Below is the output of the shortdump in ST22:
Runtime Errors         PERFORM_NOT_FOUND
Exception              CX_SY_DYN_CALL_ILLEGAL_FORM
Date and Time          10/10/2007 13:24:45
Short text
Call (PERFORM) to a non-existent routine.
What happened?
There exist various options:
Error in the ABAP Application Program
The current ABAP program "RMCSS012" 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 "RMCSS012" 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_DYN_CALL_ILLEGAL_FORM', was
not caught in
procedure "F0020_UPDATE" "(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:
The program "RMCSS012" is meant to execute an external PERFORM,
namely the routine "MCE1_100" of the program "SAPFMCEF", but
this routine does not exist.
This may be due to any of the following reasons:
1. One of the programs "RMCSS012" or "SAPFMCEF" is currently being developed.
The name "MCE1_100" of the called routine may be incorrect, or
the routine "MCE1_100" is not yet implemented in the program "SAPFMCEF".
2. If the program SAPMSSY1 is involved in the runtime error, one of
the function modules called via RFC is not flagged as remote-capable.
(see Transaction SE37 Goto -> Administration -> RFC flag)
3. There is an inconsistency in the system. The versions of the
|    programs "RMCSS012" and "SAPFMCEF" do not match.

Hi Pooja,
Check SAP Note 1015948 - AFS:Update terminated after PO Change ME22N. and SAP 485651
Thanks
Sunny

In SM13 updates terminates for transaction MIR7 only

Greetings,
Updates for transaction MIR7 are terminating. The tablespace is not full and other updates are successful.
I just want to explore the number range issue. I want to understand which number range might be used-up (i.e. update [OMRJ] or the invoive specific [SM56]). Please provide detailed informations in your response.
All fails at step/module:
"5     MRM_INVOICE_DOCUMENT_POST     V1     Error"
Error: M8 185: Invoice document 5105640270
Also advise who is repsonsible extending which number ranges (functional or basis)
Thanks

The problem is that the functional team says they have extended the number ranges, but the updates are still terminating. We even reset the No Range buffer in SM56 for all the application servers to no avail. There are no dumps in ST22. SM21 Log listed below:
                                                                                Time     Type Nr Clt User     TCode Priority Grp N Text
13:01:02 UP1 036 400 2488394                 D0 1 Transaction Canceled M8 185 ( 5105640496 2010 )
13:01:03 UP1 036 400 2488394                 R6 5 Update terminated
13:01:03 UP1 036 400 2488394                 R6 6 > Update key: 4B42ED19C648010DE10080000A031C2B
13:01:03 UP1 036 400 2488394                 R6 7 > Update module: MRM_INVOICE_DOCUMENT_POST
13:05:21 UP1 035 400 90015390                D0 1 Transaction Canceled M8 185 ( 5105640499 2010 )
13:05:21 UP1 035 400 90015390                R6 5 Update terminated
13:05:21 UP1 035 400 90015390                R6 6 > Update key: 4B445D6E931800AAE10080000A031C2B
13:05:21 UP1 035 400 90015390                R6 7 > Update module: MRM_INVOICE_DOCUMENT_POST
13:36:30 UP1 035 400 40002061                D0 1 Transaction Canceled M8 185 ( 5105640608 2010 )
13:36:30 UP1 035 400 40002061                R6 5 Update terminated
13:36:30 UP1 035 400 40002061                R6 6 > Update key: 4B45D676A7CB0093E10080000A031C29
13:36:30 UP1 035 400 40002061                R6 7 > Update module: MRM_INVOICE_DOCUMENT_POST
13:57:24 UP1 036 400 40002061                D0 1 Transaction Canceled M8 185 ( 5105640671 2010 )
13:57:24 UP1 036 400 40002061                R6 5 Update terminated
13:57:24 UP1 036 400 40002061                R6 6 > Update key: 4B44C5D7957E00A5E10080000A031C29
13:57:24 UP1 036 400 40002061                R6 7 > Update module: MRM_INVOICE_DOCUMENT_POST
14:04:08 UP1 035 400 90004221                D0 1 Transaction Canceled M8 185 ( 5105640675 2010 )
14:04:08 UP1 035 400 90004221                R6 5 Update terminated
14:04:08 UP1 035 400 90004221                R6 6 > Update key: 4B425375581E0096E10080000A031C29
14:04:08 UP1 035 400 90004221                R6 7 > Update module: MRM_INVOICE_DOCUMENT_POST
I just want to identify the root cause of this problem. If it is number ranges, table buffering or what else? If there is no proof, it always becomes a basis problem.

FBRA Update terminated

Hi guys,
We trying to reset clearing Doc using FBRA.
Message triggers via Express dcoument "Update Terminated".
I have checked the logs and in SM13 - indicates Update Terminated in Reverse_clearing.
I have executed FBRA couple of times but no use.
Finally it has reset the clering document but it does not display GL line items/ open items related to above document.
please help!!!!!!!

Hello
For multiple documents that require resetting and reversing (say after a
terminated payment run) I have been using batch uploads.
Unfortunately when you record (trx SHDB) the reset cleared items
transaction (trx FBRA) at the point of saving you do not get the option to
reverse the document aswell, the recording just saves without the 'popup'
giving you the option of just resetting or resetting and reversing or
cancelling. I have therefore been using a separate recording of
transaction FB08 (reverse FI document) to reverse the documents.
Rgds
suresh

Update termination in ME29N (Release PO)

Hi All,
I am getting an update termination mail to my sap mail box when I am trying to release one purchase order. " Error info... SO 451: Address <&> does not exist " (from mail) What might be the reasons?
Thanks in advance
jaison.

Hi Martin,
I checked in SM13. Error occured in function module RV_MESSAGE_UPDATE. Executed the transaction ME29N after putting break point in the function module. Flow control is not coming into RV_MESSAGE_UPDATE.
Regards
Jaison.

Update termination in FB1S

Hi Experts,
In our SAP (EEC5.0) system, we are getting an update termination.
Details:
Transaction:FB1S
Report:   SAPMF05A
Function Module        POST_DOCUMENT
Status                 Update was terminated
Report                 LF005F01
Error details   Class:     F1         Number:    801
F1 801: Clearing: Line item 002
There are plenty of termination happening everyday.
Can anyone advice me about the root cause of the issue? How to take care of this?
Thanks in advance.
Mark

Mark,
Yes, sorry about that... accidentally hit Enter. I was going to suggest taking a look at [Note 1004363|https://service.sap.com/sap/support/notes/1004363]. The error message you mentioned (F1 801) is called from function module POST_DOCUMENT -> form beleg_schreiben -> form bsed_insert, when the INSERT BSED statement fails. That's what led me to Note 1004363. Maybe you could debug to find out what BSED values you are trying to insert when the dump occurs. That might give you an idea of why the insert is failing.
Regards,
Jamie

Update Terminated for VF01

Dear Friends
When I am trying to create an invoice from vf01, during the time of saving the document, a message is coming as follows and billing document is not getting saved . No excise invoice is getting generated
Update was terminated
Transaction.. VF01
Update key... 529CE7DD8D64F109B1C2001A646A1292
Error Info... 8I 336: Error in allocating Excise invoice
In SM13, I found the following error. : J_1I4A_CREATE_SD_INV_UPDATE V1
Chandra

Dear Chandra,
Contact your BASIS-Administrator.
Meanwhile, Check with Your NUMBER RANGE MAINTENANCE in Transaction: SNUM, for Object: J_1IINTNUM
Best Regards,
Amit
Note: For more, refer my post:
[Update terminated|Re: ABAP run time error]

Update termination.

Iam getting an error while posting GR.the screen shows the document# but after coming out of the screen it shows
Update was terminated
" Express document "Update was terminated" received from author "Kiran Reddy" "
System ID....   RP1
Client.......   500
User.....   CCCKRE
Transaction..   MIGO
Update key...   4D864FC32FFF6107E10000000A080994
Generated....   21.03.2011, 01:06:21
Completed....   21.03.2011, 01:06:22
Error info...   00 671: ABAP/4 processor: DBIF_RSQL_SQL_ERROR
                                                                                Can any one explain about this.

When you get an update terminated.
1. Check with other user to ensure that there is no widespread system problem causing update problems.
2. If you have recently changed any code in a related user exit, this may be the cause
The ABAP dump (ST22) will show the details. Unless you know how to read the dumps, get some help from your ABAP consultant.

Update termination in Transaction ME9F

Similar Messages

Maybe you are looking for