L_to_create_int causes update termination

Hello,
I programmed a TO creation for a list of transfer requirements with the 3 function modules
l_to_prepare_item_int
l_to_add_item_int and finally
l_to_create_int.
Now, when I process several TRs for one batch material I have the following problem:
Either I call l_to_create_int only once after I have processed all TRs. In that case only one TO is created and one TR gets the total of all TR quantities whereas the other TRs remain open.(The TR number is on header level of the TO).
Or I call l_to_create_int each time the TR number changes, but then I get an update termination.
Has anybody an idea, what I am doing wrong here?
Thanks in advance for your help!
Frank

OK,
I found it on my own now. In the above described case it is necessary to delete the global variables of function group L03A before calling l_to_create_int. It looks like this:
CALL FUNCTION 'L_SAPLL03A_INIT_INT'.
No parameters required.
To whom it may concern.

Similar Messages

RMMR1MRS-When run in background cause update failure errors looking

hi,
RMMR1MRS report when run in background cause update failure errors .
There are few below reason for the error log.
1. for the PO invoice already generated - (its right if already invoice generated. should not happen again)
2. In MIGO, entire quantity has been reversed and also invoice generated with zero value - ( its right , should not happen invoice again )
3. Particular PO line item deleted - (its right if the PO line item deleted. ERS settlement not require)
For the all above reason, the update error occurs. But the mean time the program "RMMR1MRS" should not through the update error log.
Note: The job was not terminated due to this update error and also no harm because of the error log
can you please help on this update failure why it occurs.

Have you found a solution already? If so, please, share it with the community and close this thread.

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

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

"Update Termination" error when TECO is been done to Workorders in IW32

Hi Everyone,
I am facing some problem with IW32, what has happened is when I create a notifiaction and simulatenously do a TECO(technically completed) to a workoder in IW32, i get a error Update terminated.
I problem is it is not cretaing th notification too, after when i create a notification and click on TECO icon, it leave the IW32 screen and says Order#XXXX and Notification %000000000001 saved.
Note that recently the support pack has been applied to the system(ECC 6.0)
so when i freshly create a WO# and create a notification and do teco immediately i do not have any problem and notification too gets created.
I have problem only those WO# s which was created before support pack and notification and teco done now(i.e. after supprot pack is applied) .
Please help me on this, every day this seems to be a problem i get a couple tickets on this and unable to rectify this error
Regards,
Raj

Hi Everyone,
I forgot to add the error that causes Upadte terminte,
when i looked in SM13, it says Notification Missing, Since notification and teco happening simulataneously this is happening, but why is that when notification created and done Teco before and after Support pack works..
where as the WO# create before and notification and teco done later has problem..
is it some cofig problem..

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 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 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 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 when create customers

When I create and save a customer, the system issues an express
document afterwards telling that the 'Update was terminated'.
This happens only when I wanted create same customer # to new company code, which already exists in different compnay code through XD01.
The following update termination occurs:
F2 802: System error in table &, account & when inserting.
I found a note 916688 but it is belong to patch level 4 of ecc6.0, we are on level 7. Do you have any idea what is causing this or any other note that you can suggest. Advance thanks.

Hi,
Check the number range for this account group.
Are you using the same account group as the other one or some thing else.If you are using the another one then check the number range.
And also show this error to your ABAPer and ask him to debug the code.
Check in SM13 T.code to find the error where and why it is appearing?
Regards,
Krishna.

Update termination when I create customers

When I create and save a customer, the system issues an express
document afterwards telling that the 'Update was terminated'.
This happens only when I wanted create same customer # to new company code, which already exists in different compnay code through XD01.
The following update termination occurs:
F2 802: System error in table &, account & when inserting.
I found a note 916688 but it is belong to patch level 4 of ecc6.0, we are on level 7. Do you have any idea what is causing this or any other note that you can suggest. Advance thanks.

Hello
Try transaction FD01 because with XD01 system also attempts to create general data....
Ask an ABAP consultant to check the correction instructions in this note 916688 and compare in your system if the changes as per note are reflecting there.If not implement the note.Usually when ABAP consultant applies note using SNOTE he should get a message if not is applicable in your system or not.
Thanks
Vikas

Express Document: Update Terminated in VL02n -CONNE_IMPORT_WRONG_COMP_TYPE

Hello friends,
Am an abaper (fresher).
Actually i wanted spool to be generated when my delivery document is saved in transaction VL02n.
But when i save it and come out , am getting an error telling "Express document: Update terminated."
When i issue output to the delivery type am getting no response. But the status of the output type inside the document is processed (Green)
I have pasted below the SM13 error log.
Module Name Type Update Return Code
1 RV_DELIVERIES_SAVE V1 (no retry) Error
When i further look into it i get this error looking in ST22 it shows as mentioned below
00 671: ABAP/4 processor: CONNE_IMPORT_WRONG_COMP_TYPE
( My print program has no syntax errors. I have passed the control parameters for preparing my smartform for spool to be generated when i save the delivery document. )
Could you please help me in solving this issue ?
Thanks and Regards
Kausthub

Hi Kausthub,
although the print programs has no errors, it is possible that the output itself causes an update error. I remember when I created a sapscript form I forgot to define firstpage as follow-up-page of firstpage. Whenever more than one page was created, I got a dump in update processing - like you got it now.
On the other hand, CONNE_IMPORT_WRONG_COMP_TYPE should not be related to this - there are some SAP notes applicable.
Regards,
Clemens

Update Terminated Error in Va01-Help Appreciated

Hi ,
    When I create Sales Order in Va01 for order type ZCS,ZCD, and when i try to view that in Va02- It gives "UPDATE Terminated " from author .
I have already posted this in sdn before and i got the solution to check in ST22.
I have found the FM that caused the error.This parameter ord_pre_imp was empty as there were no order number.
CALL FUNCTION 'CO_BH_ORD_HEADER_PRE_READ'
       EXPORTING
            client              = client
            number_of_tasks     = number_of_tasks
            flg_ordnet_exploded = explode_ord_net
            flg_enq_set         = flg_set_enq
            import_message_id   = import_message_id
            caufv_single_imp    = caufv_single_imp
            trtyp_net           = trtyp_imp
            flg_no_gos          = flg_no_gos
            flg_called_to_copy = flg_called_to_copy
       IMPORTING
            flg_ordnet_read     = flg_ordnet_read
       TABLES
            aufpl_tab           = aufpl_tab
            ord_pre_tab         = ord_pre_imp
            bedid_tab           = bedid_tab
            rsnum_tab           = rsnum_tab
            number_tab          = number_tab
            autab_tab           = autab
       EXCEPTIONS
            not_found           = 01.
IF NOT sy-subrc IS INITIAL.
    RAISE not_found.
ELSE.
Need to know whether error due to configuration or technical. what i should do in this case.
U'r Help will be appreciated. Thanks in advance

Hi,
Check the error analysis in the ST22. Here you get the complete error analysis.
Furthermore if you want to check the updation error, then go to SM13 and see the update error analysis.
Hope this information helps you.
Regards.
Deepak SHarma.

Update Terminated with me22n

Hello,
Updates are terminating while updating PO in ME22n.
Function Module        ME_UPDATE_DOCUMENT
Status                 Update was terminated
Report                 LEINUU05
Row                    401
Error details   Class:     ME         Number:    808
ME 808: System error: error during update Table EKET
Please help to find out what can be the cause of this.

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

L_to_create_int causes update termination

Similar Messages

Maybe you are looking for