In VF01 error Update was terminated (Brazil Localization

Hi Gurus,
When I create inovice through VF01 based on delivery document number, at that time system is sending error message to my SAP inbox. The error message is as under. ( I am working with Brazil Sales scenario of Nota Fiscal.) In this Nota fiscal document will get created once invoice is saved.
Update was terminated
System ID....   T01
Client.......   301
User.....   LAVISDIN
Transaction..   VF01
Update key...   4AE5A1A787093256E1000000C0A80122
Generated....   26.10.2009, 23:09:04
Completed....   26.10.2009, 23:09:05
Error Info...   Processing log for program J_1BNFPR routine ENTRY
Awaiting for your reply.
Thanks & Regards,
Thiru

Hi,
I think OUTPUT was activated for you document
check the below settings
Cross-Application Components  General Application Functions  Nota Fiscal  Maintain Number Ranges
Cross-Application Components  General Application Functions  Nota Fiscal  Define Nota Fiscal Item Types
Cross-Application Components  General Application Functions  Nota Fiscal  Define Nota Fiscal Item Types
Cross-Application Components  General Application Functions  Nota Fiscal  OUTPUT TYPES.
the main issue will be you have not defined the FORM for the OUTPUT type.
Please cehck the settings and revert back if you need more details
thanks,
santosh

Similar Messages

In VF01 Error: Update Was Terminated

Dear Friends,
When we are trying to create Invoice for a delivery no. system has created the Invoice no.& then
disappear,
We also tried to display the invoice using VF03 t-code but in vain.
Error: Update was Terminated

Hi ,
Goto transaction SM13 and check the updates request and see what it says.
Generally these types of Error Updates in transactions will occur , if there was any changes/updates in the number ranges
since you are getting this error in Billing creation VF01, please check the nmber ranges in VN01
Hope this will solve your problem
regards,
santosh

Error Update was terminated at time of VFO1

Dear All,
I have created sales order with ref to contract no through standard BAPI ,now i am going to create bill with ref to sales order (which i have created through BAPI),while saving the bill it will give me error Update was terminated and in SBWP .i have received mail that contains:
Transaction..   VF01
Update key...   4A98C715DA854584E10000000A08351C
Generated....   29.08.2009, 16:34:28
Completed....   29.08.2009, 16:34:29
Error Info...   M2 815: Error while determ. loc. crcy: exchange rate type M
After that i have created as sales order without use of BAPI with same contract number ,and after that i have created bill with ref to sales order at that while saving it give me no error
so pls help me out on this,

Can you contact you functional team showing the below message
Error Info... M2 815: Error while determ. loc. crcy: exchange rate type M
Check ifthe below note give you some help.
Note 1362966 - BAPI: FAGL_PLANNING - incorrect exchange rate type is used
Thanks
Rishi Abrol

Error 'Update Was Terminated' - While clearing an open item

Hi,
We are facing a problem where we receive an error - "Update Was Terminated" when we try to clear some entries for 3-4 vendors (posted in period 12 of year 2006. it happens only for those 3-4 vendors). We have identified the problem as follows:
1) We ran program SAPF190 and found that there is a defference in the 'debit balance' and Total of line items' for these vendors. I ran program SAPF71 (in Quality server) which rectified some entries. However, some entries still remain incorrect and these entries that still remain incorrect are ones - "which have a posting date of 10 oct 2006, but the posting period picked up by the document header is period 12, instead of period 7". Now, some other documents posted for the same vendor on the same date have picked up the correct posting period i.e. 7. I am really baffled at how this actually happened and howcome the system allowed it??
2) After running program SAPF190, there were some entries that got corrected (these entries were just not captured by the system in the balance field, and did not have the same problem as the entries mentioned above where the wrong posting period was picked by the system). When i tried to clear the line items for the vendors whose entries had been rectified, it still gve the update error. When i checked the number range status, i noticed something very odd:
"The number range status shows a number much higher than what the system is automatically picking for the documents (e.g system picks 230 as the document number when posting, but the number range staus in FBN1 shows current number as 256). Also, once 256 is reached (i posted 26 documents for it) and we post the 257th document, the error remains and the status number now moves up 100 places to 356). At this time if i post another document it picks the number 258 instead of 356...and if i keep posting documents till 356 is reached, im sure when i post the 357th document, the status will jump to 456)
Can someone please help me here!! I dont understand how and why this is happening!!
Thanks!!
Regards,
Angad

>
Ravi Sankar Venna wrote:
> Hello,
>
> Please let me know the ERROR name you are getting and what is the transaction code you are using to clear. (F.13 or F-44)
>
> Try to analyze the dump in ST22.
>
> Regards,
>
> Ravi
Hi,
The error is "Update was terminated" . It sends this message to my inbox!! After searching a bit i found about the two reports - SAPF190 and SAPF071. After running them i found some balance mis-match. I ran the two programs and it rectified those mis-matched entries!! However, even after that, it is giving me the same "update was terminated" error. We are using F-44 for clearing.
This error is coming only for those entries which we had posted using a user-exit. Basiaclly these are entries for late payment which were programmed to be posted directly at the time of invoicing. I just checked the code of the exit, and these entries were (astonishingly) made directly into the BKPF and BSEG tables (infact the posting period was hard-coded to '12', which is why even when my posting date for these documents is 10.10.2006, it still enters posting period '12' in the header instead of '7'.). Therefore, there were balance mis-match when we saw the monthly balance in FK10N and compared it with the line items total for that month. However, on running report SAPF071, it corrected those entries, but the update error problem still persists!!
The exact error:
Update was terminated
System ID....   QAS
Client.......   100
User.....   MOHGYA323233
Transaction..   FB1K
Update key...   4A206A2D00E5001202000000C0A80A35
Generated....   04.06.2009, 11:24:59
Completed....   04.06.2009, 11:24:59
Error info...   F1 805: Clearing: Line item 001

How to rectify this error "Update was terminated" when i save the tcodeMe42

Hi,
I am working in Me42 transaction, after filling the messages when i give save its throwing an error message
"Update was terminated" received from author" Author name".
Why is error occuring what is the cause how to rectify

Hi anitha,
1. This error is occuring
   when the transaction data is being posted,
   in the background via update task.
(using update FM)
2. goto tcode SM13
   to analyse the error.
(u may take help of basis team)
regards,
amit m.

Error : Update was terminated

Hello Experts,
While creating orders in PP, PM, and PS module the system is throwing error as "Update was terminated". In ST22 it throws the dump as RUNTIME ERROR : sapsql_array_insert_duprec. The data is not stored in the table while the number range for perticular order is get consumed. we have checked the number ranges, there is no inconsistancies with the number ranges, no upgradation
have been done also we haven't transfered any kind of data from
external system.
Please reply as soon as possible.
Thanking you in advance.
Amit sirsath

Hi Amit,
Check the OSS note number 668466. You can aslo adjust the number range and check. Even i had similiar problem and thought there was no inconsistency in the number range, still i adjusted and that's how my problem was solved.
Regards,
Satyajit

Error"Update was terminated' while doing picking and data was not saved

hi experts,
I have created a sales order. for that i created a deliery.then i created shipment .and i have put pick qty and batch.
it gives a message Express document " Updated was terminated "received from author XXXX.
and picking is not saved and i'm not able to do PGI.
Please help me.....
Thanks in advance,
ria

Hai,
Analyse this error in ST22 - ABAP runtime error or in SM13 - update request.The system will show the error update records in red color. Click the error & see the problem in funciton module.THis may be because of no ranges problem or any changes in print out program. Also if u have any BADI activation for the sale order & any changes in this program also leads to this error.

Getting the Error Update was Terminated

Hi Friends,
when i am using MIGO tcode after entering the material no, quantity, plant and storage location, after saving it will shows the "Update was terminated".
Can any one pls help me how to rectify such type of errors.
Advance Thanks,
Sudhir K.

Hi Sudhir,
There are various notes related to this problem in service market place like 664829, 431282, 777409. Find out your SAP release and search for the right note.
This error usually occurs when duplicate entries are entered in the database.
Reward points if useful.
Regards,
Soumya.

In VL01 error "update was terminated" afee executing userexit

Fort the following scenario i have implimented the below mentioned userexit but i am getting error after completion of PGI "update terminated"
Customer creates Outbound delivery using T-code - VL01N and in the same screen there is PGI Tab (refer attachment). PGI is very important as it updates the stock in the system alongwith the accounting document.
User may skip doing PGI and save the an Outbound delivery. In order to make it full proof, it should be like unless and until the PGI is done the system should not allow the user to save the document.
Program SAPMV50A
include MV50AFZ1
FORM USEREXIT_SAVE_DOCUMENT
FORM USEREXIT_SAVE_DOCUMENT.
*{ INSERT &$&$&$&$ 1
IF sy-tcode = 'VL01N'.
if vbuk-wbstk <> 'C'.
Message ' You are not Completed PGI for Delivery' Type 'E'.
Else.
ENDIF.
endif.
*} INSERT
ENDFORM.

Hi,
If you use E meesage type, the update termination will occur, to avoid this change the code
Regards
Shiva

Error in creation of billing document: update was terminated

hi experts,
i am facing one problem while creating "Billing Document" in VF01 . After i save it says 'Document 941700032 has been saved' but later after i click on tht it shows d error "update was terminated' and billing document no i not getting created .
Thanks

After save, and during SAP's update processing, a fatal error occured, causing a rollback of the transaction. Since the user is no longer in that same transaction at this point, SAP issues the Express Document to attempt to inform that there was a failure. Check ST22 for abend...in the meantime, check for exit coding that may be causing an error...In my previous life, working with SD/LE at lot, I was able to get these regularly by fouling up my exit coding....lol.

Error 'Express document "update was terminated" from the author'.

Dear All,
I have created a delivery doc(PGI) with ref to sales doc, it gave the
del doc no. while creating billing do with ref to this del doc I am getting
an error " update was terminated". when I cheched Vlo2n it says that the doc does not exist.
Even I have done PGI the stock is not deducted( MMBE).
   Please help me to rectify this error.
   Thanx and Regards
    Narender.N

Check if number range is maintained for accounting document to be generated at PGI level. You will have to consult an FI consultant for the same.
Also check the document flow & there is high possibility that PGI is not saved, but number range utilized during the transaction.
Regards,
Rajesh Banka
Reward points if helpful

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

Hi,
In VA01 tcode, we created a sales order and it generated sales document number. When we go to VA02, it was throwing an error 'Express document "update was terminated" from the author'.
How can we rectify this error??
Ur help is highly appreciated.....
Thanks,
Ravindra.


> Hi,
>
> Thanks for all who gave suggestions.
>
> I studied dump, it was giving a runtime error
> "SAPSQL_ARRAY_INSERT_DUPREC". I thought some
> duplicate records are existing, but I found nothing.
>
> Actually for year 2006, new number ranges were
> generated, the range is 74101 to 74200. Its picking
> sequential sales document number and giving the
> message that document is saved in the status bar in
> VA01. 
Sales orders are not like material documents or accounting documents that they are dependent on the year. The numbers can repeat for material documents or accounting documents if they are in two different years. But that is not the case for sales orders. They are not dependent on the year they are created. The number simply cannot be a duplicate

>If I search for that generated doc number in
> the related table, I didnt find that.
Which table did you search?

> But when I see in VA02, it was throwing this error
> "update was terminated".
If it is not there in the table you searched, then how come you are able to go to VA02(change sales order) transaction for the same order that you said is not in the table?
> I think my problem is clear to U ALL.
Please clarify.
Srinivas

Update was terminated on WSM8 " POSTING_ILLEGAL_STATEMENT"

Hi all
our system is ecc6 with IS -retail activated. support Stack level is 12 and database is oracle , os is windows.
We are getting express document error " Update was terminated " when executing WSM8 . on ST22, we are getting following error
POSTING_ILLEGAL_STATEMENT . We applied note 1053491
which is similar to the issue but it does not solve.
Here are the st22 dump details
Runtime Errors POSTING_ILLEGAL_STATEMENT
Date and Time 24.04.2008 19:03:48
Short text
Statement "COMMIT" is not allowed in this form.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSYDB" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
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
There is probably an error in the program
"SAPLSYDB".
This program is triggered in the update task. There, the
following ABAP/4 statements are not allowed:
- CALL SCREEN
- CALL DIALOG
- CALL TRANSACTION
- SUBMIT
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"POSTING_ILLEGAL_STATEMENT" " "
"SAPLSYDB" or "LSYDBU27"
"DB_COMMIT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
this is sm21 error log
Time      Type      Nr      Clt      User      TCode      Grp      N      Text
18:09:55      UP1      006      600      SAUGATA             AB      0      Run-time error "POSTING_ILLEGAL_STATEMENT" occurred
Run-time error "POSTING_ILLEGAL_STATEMENT" occurred
Details
Recording at local and central time........................ 24.04.2008 18:09:55
Task......      Process      User......      Terminal      Session      TCode      Program      Cl      Problem cl      Package
05460      V1 Update Task No. 006      SAUGATA      LB-TULIP      1                    T      Transaction Problem      SABP
Further details for this message type
Module nam      Line      Error text
thxxvb      1346      ThVBCheckCommit
Documentation for system log message AB 0 :
The specified runtime error has occurred in the system.
Parameter
abcdefghijklmnopqrstuvwxyz .. POSTING_ILLEGAL_STATEMENT
Technical details
File      Offset      RecFm      System log type      Grp      N      variable message data
66      160740      l      Error (Module, Row)      AB      0      ThVBCheckCommit thxxvb 1346
Please check and let me know if you need more details.

Hi Jelena,
Here is the source code extract where error is .   Will this be a standard sap program or a program modified by abaper?.
Source Code Extract
Line SourceCde
1 FUNCTION DB_COMMIT.
2 *"----
    3 ""Lokale Schnittstelle:
    4 *"----
    5
6   EXEC SQL.
>>>>>     COMMIT WORK
8   ENDEXEC.
9
10 ENDFUNCTION.
Can you share some more tips on this.
Thank you once again for that help full answer.

Update was terminated SAPSQL_ARRAY_INSERT_DUPREC

Hi,
We are trying to make our custom calculations in VA01, VA02 and because of this we need to update VBUP table. We updated the fields of xvbup and yvbup, but we receive an error "Update was terminated SAPSQL_ARRAY_INSERT_DUPREC".How

Hi,
Check in SM13.
The update termination will be shown. Put a break point at that step and in update debugging check the entries which are being populated in your internal tables.
The issue might be that there is already and entry in the database table and someone is passign value in XVBUP with update indicator as 'I'
If XVBUP is correct then check if someone has wrongly modified YVBUP.
We had faced a similar problem and in that case the culprit was wrong entries in YVBAP internal table.
Regards,
Ankur Parab

In VF01 error Update was terminated (Brazil Localization

Similar Messages

Maybe you are looking for