Billing - VF01 Update Terminated

Hi,
I try to issue billing through delivery using tcode VF01. However when I click save, i receive an update terminated email in my inbox. Can anyone advice what is going wrong?
Update was terminated
System ID....   P08
Client.....     010
User.....   SGSW0TLLA
Transaction..   VF01
Update key...   33CDDE59D08F440B8170E7B43A906203
Generated....   09.01.2007, 03:24:06
Completed....   09.01.2007, 03:24:15

Hi,
I had found out the error due to the Nota Fiscal number go out of range, the path is :
IMG-Cross-Application Components-General Application Functions-Nota Fiscal-Number Ranges.
There is a t-code J1B3N for displaying the nota fiscal document. This is a special billing needed by Brazil for legal requirement.
Thank everyone for all your help and hope everyone had learned something new =)

Similar Messages

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 terminated when doing VF01

hello, friends.
we have a situation where Billing type F2 settings were changed (using VOFA). specifically, in field "Assignment" i specified "E" (billing document). supposedly, the billing document number will be used as assignment allocation. there are already billing documents created.
when these settings were done, i started getting error message "express document update terminated". the system says error has something to do with ABAP/4 processor CONVT_NO_NUMBER.
when i execute ST22 or SM13 to look at the problem, it says the system cannot interpret "1111" which is why the update was terminated. here, "1111" is the material number.
i tried switching the settings of F2 back to standard but the errors continue.
why is the system getting the material number as number range?
your help will be greatly appreciated.
many thanks.
jty

hello, friend.
i checked the other threads with similar subject, and i agree it may have something to do with number range. but i checked the number range of the billing document and i'm not sure i have the exact issue.
i suspect that when i changed the "Assignment" settings in VOFA, the synchronization with the Accounting Document (Allocation) number might have been affected. when i repeatedly tried to create billing document with reference to the same delivery document, the system uses a new billing document number when saving, but then this is lost.
would you think this is the more likely cause?
thanks.
jty

Update termination dump while saving sales order after updating billing pla

Hi,
Our client is facing a strange issue. The client has a sales order already created and WBS element assigned to it automatically. The sales order has many items, which are billed periodically. Whenever the particular item has to be billed. user attaches milestone in the project which is updated in the billing plan of the sales order. Then user goes into change view of sales order, and sees if the billing plan is getting updated. After user sees that billing plan is updated, he tries to save the sales order and the update termination dump comes.
We have analyzed this issue to some extent. Since the product hierarchy have been changed, the system checks for the duplicate records and throws the dump.
We have advised the user to follow following steps also:
   1) Delete existing billing plan if any assigned to the order. You can delete the billing plan by going into CJ20N and deleting the existing milestones completely.
   2) Please ensure network in project is release and sales order does not have credit block.
   3) Change Product Hierarchy in sales order (Please do not copy and paste from Material master instead select the same through F4 for each level.
   4) Once again create the milestones as required in the Project.
   5) We need to remove block of billing plan from Project only instead of from Order.
   6) Check order in display mode and ensure billing plan has appeared.
   7) Now goto change mode of the order and carry billing.
Above solution has solved the issue but sometimes it takes times for the above solution to work.
The user has to repeatedly follow above steps to save the billing plan.
We need to have permanent solution for the same. I would appreciate if anybody can help resolve this issue.
Thanks

Thanks All for providing me possible solutions.
The issue is resolved by one more step into what i had suggested in my questions
At step 3, after changing the product hierarchy, I simply go to billing plan tab, thereby generating billing plan even before I add milestones in the project.
To my understanding, generating billing plan in the sales order must be conflicting with the milestone being added to the billing plan from the project, giving 2 billing plan numbers in the background and throwing update termination dump.
Cheers!!

Update termination while creating billing

Hi All,
I have created adobe form and attached to one output type and when i am trying to create invoice from sales order system is giving updat termination message.
Could you please anyone tell me where is the exact problem in adobe form or in driver program.(Adobe form has been devloped in Finnish language )
I checked SM13 and there i can see RV_MESSAGE_UPDATE function module with error description.From that I am not able to trace.
Regards,
Sachin

Hi,
Go to SM13 and check the exact code which caused the Update termination.
You can see the place where you got the update termination.
or
Analyse the runtime error in ST22
Thanks & regards.

Update termination error in IW32 because of requisition flag change

Has anyone worked on IW32 to change the requisition flag of a work order from never to immediate. I tried doing this using BAPI_ALM_ORDER_MAINTAIN. It works fine for work order having operation control key same for every operation. But if this control key changes for any operation, then the update termination error occurs and hence the requisition flag change does not happen.
Thanks in Advance

Excise invoice is generated in the back ground on creation of the Invoice
Have you tried by changing the configuration so as the sytem not to generate excise invoice automatically in the background? If so, were you able to save the billing document successfully?
G. Lakshmipathi

Update termination in VA01

Hi,
While I am creating a Sale order & when I save it. I am getting a message Sale Order xxxxx is saved.
But I could not fine the sale order. I have found that Update terminations are happening with
Function Module MCV_STATISTICS_UPD_V1_ORDER
Status Update was terminated
Report LMCS0U32
Row 17
Error details Class: 00 Number: 671
00 671: ABAP/4 processor: SYNTAX_ERROR
Please can anyone advise
Thanks
vinod

Hi Vinod,
Any way standard progam/function modules are causing the update termination. So even you find some issue, bt we can't solve that one, we have to implement oss notes ( If issue is not in the user exit ).
I can see some oss notes available referring this issue. you can check those. even you can see SM13 , where you can get even more details for update termination.
you cn check the below Oss Note: 16966
https://service.sap.com/sap/support/notes/16966
When you create or change a document (VA01, VA02, VL01, VL04, VL02, VF01, VF04, VF02 etc.) update terminations occur in the ABAP processor: DBIF_RSQL_SQL_ERROR <table> in function modules
MCV_STATISTICS_UPD_V1_ORDER or MCV_STATISATICS_UPD_V2_ORDER or
MCV_STATISTICS_UPD_V1_DELIVER or MCV_STATISATICS_UPD_V2_DELIVER or
MCV_STATISTICS_UPD_V1_INVOICE or MCV_STATISATICS_UPD_V2_INVOICE.
A table from one of the following information structures is involved: S001 through S006 or S500 through S999.
Additional key words
Cause and prerequisites
DB parameters NextExt and MaxExt of the table are not sufficient.
Solution
Change the DB parameters of the involved table:
Increase NextExt by a factor of 10 and increase MaxExt to < 500. For detailed information on the procedure, please refer to the "Data Dictionary manual".
Source code corrections
Regards,
Naveen Veshala

UPDATE TERMINATED

Namaste Guru,
While raising an invoice for an sales order after doing delivery. While entering the T code VF01 I am getting the error "UPDATE TERMINATED BY AUTHOR".
I used the T.code SM13 where there was an error and when I have clicked on the REPEATE UPDATE icon
got message records could not be updated and when clicked on it it shows an error in the module RV_DELIVERIES_SAVE Type V1 Status error after repeating the update also I am getting the same error.
Have used ST22 t code also
Please help me with this I have been trying all the ways to rectify the error.
Please help.
With regards,
madhav

Dear Allie Barboni ,
A friend of mine had the same error and tried t codes SM13 and ST22 by which his problem was solved but the error appeared again.
I have tried all the possible ways even used the help of an ABAPer but no solution had come so i had to reload SAP in my system.
Hope your error gets through.
With regards,
Madhav

Update Termination during Billling

Hi ,
We are facing one major issue at the time of billing, the scenario is,
Scenario :
we have maintained the TEXT ID for serial number in order item ,and we have made settings such that the value in Text id gets copied to the same id in Delivery document and Billing document for the corresponding line item. At the time of Invoice document creation, a smartforms is being generated which reads the contents of this text id using the FM READ_TEXT.
If the Text ID is blank , we get an updation termination express mail but on the other hand if there is some value populated in the Text id then the process works fine. Pls Help!!!!
Thanks ,
Ramesh K.P
Thanks,
Ramesh K.P

Hi
Go thru the following link:
http://www.sapfans.com/forums/viewtopic.php?p=822485&sid=253f8b02796c0b390a5180b3d1a86661
may be useful
Regards
Aravind

Update Termination Error SSFCOMPOSER 173

Hi All,
I am facing a strange error in the production system.This error is not shown in development or test system.
I have created a smartform which is called from a billing document.Whenever business assigns an output type to the billing document and saves it, it gets an "Update Termination Error".
After checking the SAP inbox in production system, we have been able to retrieve the following message.
Error info : SSFCOMPOSER 173: Table LEFT_DATA.
From this, I understand that the dimensions of the table LEFT_DATA are larger than the window.But when checked, the dimensions of the table are smaller than the window, which ideally should not create any issues.
This error is occuring only in Production system.So, its hard to analyse it.
Any form of help will be highly appreciated.
Regards.

Yes, you are right.. your table has a problem.. but, I guess.. it is not related to the dimension... it is related to the number of columns.. I guess, some conditions inside your smartform might be wrong... which might triggered in production data..
Example: You table has 3 columns and if your smartform is trying to print data in fourth column this error may occur.
If I am wrong with the above assumption, then check the dimension of the table in all PAGES... EX: FIRST PAGE, SECOND PAGE etc, which are defined in your smartform.
Regards,
saiRam

Error while doing the billing (VF01)

hello,
we have created Debit memo request "1234" (doc type : DR). when i am doing the billing(VF01) for the debit memo "1234" we are encountering the error as bellow.
bellow message is from the log:
"001234 000010 "Create billing document" not allowed (Sys. status Cost, object VB001234000010)
Long txt
    Detail
     Diagnosis
         The status check for the status object VB001234000010
         indicated that the procedure "Create billing document"
         cannot be performed because Sys. status Cost forbids it.
     System Response
         Procedure "Create billing document" is not performed.
     Procedure
         If procedure "Create billing document" is to be performed,
         the Sys. status Cost of object VB001234000010 must be
         reset.
         Other statuses than Sys. status Cost can also prevent the
         procedure. This message does not tell you all statuses
         which currently prevent procedure "Create billing
         document"".

Hello,
First you check the requirement type in the order VA03 --> Overview screen --> Procurement tab --> check the requirement class for the line item.
Check, IMG u2013 Controlling u2013 Product Cost Controlling u2013 Control of sales order related production / prod. Cost by sales order u2013 Check Requirement class.
Check the requirement class from here. Remove all data from the Costing and Account Assignement tabs and save. It will be useful if you take the screenshot of the earlier setting, it will be helpful for you to revert back the config whenever you want.
Try to generate the billing document and let us know whether it worked?
Prase

Update termination during Periodic Posting in RE-FX

Hi,
I am getting a update termination error -SAPSQL_ARRAY_INSERT_DUPREC during periodic posting for Lease Out Contract. Tcode - RERAPP
We use deferred tax. This functionality is used to transfer service tax
credit from interimn account to final account as applicable in India.
As suggested in the note 913805 by SAP we deleted the BTE's in application Key FI-TAX
Inspite of that we get the same update error.
Also we observed that after deleting the BTE's our service tax credit
functionality is also not working.
Further I have observed the following:
I am getting error only while posting contracts with service tax.
Tax Code L1 Account Key OS1 & OS2 & OS3
Please help me in finding a soultion to this.
Thanks & Regards
Sanjay

Hi,
The transfer step will transfer controlling assignments from the contract to the rental objects. This is useful if you want to run the controlling reports in order to see a P&L statement for a Building for example.
Regards,

Update termination error at the time of order creation and chamge?

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

Hi,
Goto ST22 T.Code and analyse the error.The error message why it is terminated will be displayed here.
Or go to SBWP T.Code in the user where you got this error and check the inbox.
It will display why the error is appearing.
Show the same to the ABAPer and ask them to work on it.
I think your server may be slow and it will take some time to update the order created by you.But I am not sure.Check the error message.
Regards,
Krishna.

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

Billing - VF01 Update Terminated

Similar Messages

Maybe you are looking for