Regarding COMMIT WORK

Hi,
I am using two BAPIs 'BAPI_ACC_ACTIVITY_ALLOC_POST' and 'BAPI_NETWORK_CONF_ADD' in my custom function module. These two BAPIs are used as explained below:
1) Fisrt the BAPI 'BAPI_ACC_ACTIVITY_ALLOC_POST' is called. If sy-subrc NE '0', the error messages are read.
2) Then the BAPI 'BAPI_NETWORK_CONF_ADD' is called. If sy-subrc NE '0', its error messages are read.
3) If there is no error for the two BAPIs called above, then the actual posting is done by calling the BAPI
'BAPI_ACC_ACTIVITY_ALLOC_POST'. If sy-subrc EQ 0, Commit work.
I would like to know if the Commit work in third step will commit the changes of the steps 1 and 2 as the the statement COMMIT WORK completes the current SAP LUW.
Or will it commit the step 3 only.
Thanks & Regards,
Soumya.

Hi soumya,
you can rollback for the step 1& 2 if sy-subrc ne 0.
and then use the comit work if sy-subrc eq 0 for step 3.
Hope this will help you.
regards,
Phani.

Similar Messages

* Commit work on table using UPDATE statement.*

HI,
 This is Anil . I have problem regarding Commit work and Wait up to 2 seconds.
I am using Commit work on one Update table statement but it is not working . While doing debugging it is working
(means it is updating Table.) but while running the transaction directly it is not updating the table.
Check the statements :
Commit work.
Some Select stmt on <table>.
IF <condition.>
Update <table > statement.
if sy-subrc EQ 0.
 Commit work . ( This is not working while running transaction mean it is not updating table. While debuggint it it updating table.)
 wait up to 2 seconds.
endif.
endif.
Will that above Commit work causing any problem or what is the reason it is not updating table.
Please give some suggestion in this case.
Regards,
Anilreddy.

Hi
the below code with commit work is working finr for me.
only thing i suggest is to check sy-subrc value.
commit work.
update spfli set test = '1234' where carrid = 'AA'.
if sy-subrc eq 0.
commit work.
wait up to 2 seconds.
endif.
write: / sy-subrc.

COMMIT WORK AND WAIT

Message opened on behalf of colleague:
I just have a quick inquiry regarding COMMIT WORK AND WAIT, I
understand that this method performs the following:
"This form specifies synchronous processing. The COMMIT statement waits
for the end of processing. Control returns to your program after all
high priority (V1) function modules have run successfully."
"The AND WAIT form is convenient for switching old programs to
synchronous processing without having to re-write the code.
Functionally, using AND WAIT for update-task updates is just the same
as dialog-task updates with PERFORM ON COMMIT."
It says that before doing the actual commit it will wait for the end of
processing for all related updates against the transaction. However
does it also wait for any "user exits" to finish or does it go ahead
and performs the commit and updates then the user exit happens?
Thanks.

Hi User exit is part of the transaction where you call a subroutine, or another function module or BADI method. So in my opinion it will wait. Unless there is a explicit commit work coded inside the user exit.
regards,
Advait

CO54: Message is not sent to any destination: Commit Work is getting failed

Hello,
While processing the Messages from XFP to SAP Update is getting terminated due to the use of Commit Work. SAP Note 147467 - Update termination when sending process messages has been referred which is for 4.6C, but we are in ECC6.0.
While processing the message in second iteration Commit Work triggres and Update happens in the data base.
Following Issue is only concerned with Nested HUs
T-Code used CO54
Following are the analysis:
it looks like u201CCreate and Post a Physical Inventory Docu201D is failing in the initial processing because the inventory doc is created when the Transfer Order to the PSA (or the TO from the PSA) is not yet completed (quant is still locked somehow).
CO54, process message category=ZHU_CONS: HU to be consumed is a nested pallet (unpacking/ repacking and TOs to/from) and qty to consume is greater that HU qty in SAP (creation of a physical inventory doc is required).
1. The error occurs while clearing the inventory posting for the physical inventory document.
2. The surprising factor is the u201CProcess Messageu201D is not processed correctly for the first time.
3. Indeed it is successfully processed without any error if you do process it second time.
Error Log from C054 T-Code.
02.08.2010                                         Dynamic List Display                                                1
Type
Message text
LTxt
Message category: ZHU_CONS ---    Process message: 100000000000000621   "Send to All Destinations" Is Active
Message to be sent to destination:
ZHGI ZPP_0285_XFP_GOODSISSUE Individual Processing Is Active
=> Message will be sent to destination (check log for destination)
Message category: ZHU_CONS ---    Process message: 100000000000000621   "Send to All Destinations" Is Active
Message destination ZPP_0285_XFP_GOODSISSUE triggered COMMIT WORK
Input parameters OK, passed to source field structure
Step 0: Now checking if scenario with HU
Step 2: Scenario with HU, Now checking if HU nested
Step 3: HU nested, checking if HU in repack area
Step 4: HU not in repack area, moving it to repack area
HU moved to repack area, TO number 0000000873
Step 5: Depacking nested HU...
Nested HU depacked, HU pallet n°: 00176127111000461994
Steps 6-7: Moving back HUs to supply storage type / bin...
HU 00376127111000462001 moved back to original area with TO number 0000000875
Steps 6-7: Moving back HUs to supply storage type / bin...
No need to move back HU 00176127111000461994 (not in table LEIN)
Step 8: Checking if HU fully used and quantity matches HU system quantity
HU not fully used but picked quantity > HU quantity: inventory necessary
Step 9: Inventory needed, creating physical inventory document...
Physical inventory document 0000000126 created
Step 10: Adding weighted quantity on inventory document...
Weighted quantity entered in document 0000000126
Step 11: Posting rectification in inventory document 0000000126...
Physical inventory document 0000000126 rectified
Error: rectification for doc 0000000126 not updated in DB!
=> Destination ZHGI ZPP_0285_XFP_GOODSISSUE can currently not process the message
=> Message is not sent to any destination
The errors in SM13 for this contain the program SAPLZPP_0285_HUINV_ENH (creating/changing the HUM physical inventory doc). WM Function module L_LK01_VERARBEITEN is also involved.
From SM13, it displays the following piece of code in include LL03TF2M (read the LEIN table=Storage Units table):
WHEN CON_LK01_NACH.
       IF (LEIN-LGTYP = LK01-NLTYP AND
             LEIN-LGPLA = LK01-NLPLA) OR
              NOT P_LEDUM IS INITIAL.
       ELSE.
Das ist der Fall einer TA-Quittierung wo Von-Hu = Nach-HU ist und sofort die WA-Buchung erfolgt. Dann steht die HU noch auf dem Von-Platz, daher darf hier kein Fehler kommen, sondern es wird ein. Flag gesetzt, daß verhindert daß die LE fortgeschrieben wird.
         FLG_NO_LE_UPDATE = CON_X.
        MESSAGE A558 WITH P_LENUM.
       ENDIF.
Translation in English of the German text via Google:
"This is the case where confirmation of a TO source-HU = destination-HU, and now the WA (Good Issue?)- made book. Then, the HU is still on the From-space may therefore come here not a mistake, but it sets a flag that prevents that the LE is updated."
Thanks and Regards,
Prabhjot Singh
Edited by: Prabhjot Singh on Aug 2, 2010 4:39 PM

Hope you have carried out following things in Production ( Please refer to SAP help before actually doing it in production).
1. Transport the predefined characteristics from the SAP reference client (000) to your logon client.
2. Adopt Predefined Message Categories - In this step, you copy the process message categories supplied by SAP from internal tables as Customizing settings in your plants.

Reg. commit work in a follow-up action

friends
i am using the following approach to solve a requirement which is posted in this thread..How to send a mail after a usage decision is made in QA11?
got a nice reply too
i have defined a follow-up action and assigned a customized mail-sending fm to it..my doubts are, i am on 4.7..am able to send the mail to an internal id, but the problem is without using commit work and submit rsconn01 commands, am failing in doing the same...i have read in a thread that commit work or submit (if the called program uses commit work) will cause data inconsistencies and will trigger locks if it's used in any user-exit or badi...but in my case, when will a follow-up action actually take place? will it happen after all the database commits? if so, then i believe that even i use commit work and submit commands in my z mail sending fm, it wouldn't cause any problems...am just sort of afraid whether this approach is the correct one? or triggering the mail code from the last user exit or badi itself will solve the purpose? i believe not..please guide me on this friends...helpful replies will be appreciated and awarded..thanks in advance
Regards,
Sathish. R

less views and no answers:-(

How to execute Update Module FM after final commit work for a T-code.

Hello Folks,
I have a bit complex issue with my current object.
We have modified MM41/MM42 transactions and added a subscreen to fulfill the requirement.
We have designed the subscreen and embedded the same to MM41/MM42 through SPRO configuration.
Now for update business logic,i am trying to execute one Function module(Update Module) in update Task...so that it will be executed once after the final commit work will be done for MM41/MM42.
But its not executing.
To fulfill my requirement i need to execute the FM only after Final Commit work for MM41/MM42.
Please suggest in this regard.
Even i can see few BADI's which are triggering through MM01/MM02 but not through MM41/MM42.
BADI_ARTICLE_REF_RT
BADI_MATERIAL_CHECK
BADI_MAT_F_SPEC_SEL
Code with which i am trying is given below.
After PAI event of the subscreen---
1:        MODULE USER_COMMAND_9001.
2:       MODULE user_command_9001 INPUT.
                    PERFORM sub_save_mara ON COMMIT.
          ENDMODULE.
3:       FORM sub_save_mara.
                     CALL FUNCTION 'ZMMUPDATE_MARA_APPEND_STRUCT' "IN UPDATE TASK
                                    EXPORTING
                                             materialno = gv_matnr
                                             appendmara = ty_zzmara.
         ENDFORM.                    "sub_save_mara
4:                FUNCTION zmmupdate_mara_append_struct.
                  ""Update Function Module:
                   ""Local Interface:
                  *" IMPORTING
               *"     VALUE(MATERIALNO) TYPE MATNR
               *"     VALUE(APPENDMARA) TYPE ZZMARA
Data Declaration for Local use
DATA : w_mara TYPE mara.
Selecting the latest values for the material.
SELECT SINGLE * FROM mara INTO w_mara WHERE matnr = materialno.
IF sy-subrc = 0.
Move the ZZMARA values to structure MARA
    MOVE-CORRESPONDING appendmara TO w_mara.
Update the values in table MARA.
    MODIFY mara FROM w_mara.
ENDIF.
ENDFUNCTION.
Kindly suggest.Thanks in advance.
Regards
Ansumesh

Hi..
The code given by me will work fine provided the Final commit should happen.
Because to execute FM with update task,final commit work should happen which is mandatory and after that it will call the update task.
In my case final commit work was not happeneing because..SAP standard program was not able to detect wether there is any change in my sub-screen or not as the standard program & my custom program,subscreens are different.
As it was not able to detect the change,so final commit was not happening and hence update task also.
To provide the reference of change in my subscreen to standard program ,i set a flag as per the change in the subscreen
And exported the same to memory.
Then Implemented one enhacement spot in MATERIAL_CHANGE_CHECK_RETAIL Fm where i have Imported the flag value.
Based on my custom flag value,i have set one standard flag FLG_AENDERUNG_GES which tells SAP standard program for MM42 wether any change has happened or not.
The above solved my purpose.
Regards
Ansumesh

Commit work statement creating problem in CALL TRANSACTION

Hi Friends,
we are facing a problem where we need to call a standard program from a Zprogram.
we have tried the following ways.
1. Using SUBMIT statement , we are sending the parameters to the standard program, but when the standard program gives a
    dump our program cannot process further records. we are calling the submit statment in a loop. As because the standard
    program is giving dump our program is not able to process the next record in the loop and this should not be the case.
    To avoid this we have used the second method.
2. we used a CALL transaction, we have created a Tcode for the standard program and called this transaction in the calling
    program. We are passing the parameters for the standard program via BDC table. this works fine even when the standard
    program gives a dump but when ever the control   comes across a Commit work statement the the control comes back to our
   calling program with out executing the rest of the   statments after the commit.
now our concern is even though there is an commit work statement , statements after the commit work should also get executed in call transaction. Is thee any way?
Regards,
Sravan

Hi All,
I got the solution
DATA: ctu_parameters TYPE ctu_params.
ctu_parameters-dismode = 'E'.
ctu_parameters-updmode = 'A'.
ctu_parameters-racommit = 'X'. "No abortion by COMMIT WORK
CALL TRANSACTION USING itab_bdcdata OPTIONS FROM ctu_parameters.
the above code will work even if there is an commit work . This might help some others.

ABAP Dump on "COMMIT WORK"

The abap dump is occured in function module when the COMMIT WORK statement is executed.
This function module updates a custom table.
When creating a invoice through VF01 transaction this abap dump is occured.
But for the next time the invoice is created successfully.
What is the reason behind this.

Hi,
Refer
https://forums.sdn.sap.com/click.jspa?searchID=11053241&messageID=5085300
Regards
Kiran Sure

COMMIT WORK - performance problem

Dear Fellow SDNers,
I seek your help on the following problem:
Scenario : Inbound idoc which updates an Outbound delivery with Picked quantity, posts the goods issue and then creates billing document
Approach : I am using the function module SD_DELIVERY_UPDATE_PICKING to update the delivery from the idoc data and to post goods issue. Thereafter, i use BAPI_BILLINGDOC_CREATEMULTIPLE to create the billing document. Before calling this BAPI, I use a COMMIT WORK statement to update the relevant tables so as to enable invoice creation properly.
Problem: The COMMIT WORK statement takes a lot of time to execute (I have no update tasks that could lead to this), so much that the idoc (probably) has a timeout and ends up in status 64. As a result, the succeeding part of the code (after COMMIT WORK) is not executed and the billing document is not created.
When I debug this, the COMMIT WORK statement leads to a strange screen (which looks like a blank report output screen, with its title as "UPDATE CONTROL". However (of course), there is no timeout while debugging and the billing document is successfully created.
Could anyone provide some pointers to solve this problem?
regards,
Priyank

i have a custom function module Y_IDOC_INPUT_WMSPICK001 which is responsible for idoc inbound processing. SAP PI sends the inbound data to ECC and once this is done, this function module is executed.
This FM has the following code sequence inside it...
1) Call the FM SD_DELIVERY_UPDATE_PICKING
2) COMMIT WORK AND WAIT.
3) Call the BAPI_BILLINGDOC_CREATEMULTIPLE
Step1 is successfully executed, the step 2 takes a long time, and after that, the step 3 is not executed at all and the idoc ends up with a yellow light (status 64).
hope it clarifies what I am doing
regards,
Priyank

Commit Work in MIGO BADI

Hi,
Can we use COMMIT WORK statement in BADI? Hope its not advisable to use it.
I am using MB_MIGO_BADI~POST_DOCUMENT to update the GR Number in a custom table.
Sometimes the GR number is not getting updated in the custom table.
The modify statement given below does not updates the table sometime.
IF WA_ZMM_GATE_ENTRY-GR_NUMBER IS INITIAL.
      WA_ZMM_GATE_ENTRY-REFERENCE = GS_EXDATA_HEADER-REFERENCE.
      WA_ZMM_GATE_ENTRY-REFWERKS = GS_EXDATA_HEADER-WERKS.
      WA_ZMM_GATE_ENTRY-GR_NUMBER = IS_MKPF-MBLNR.
     WA_ZMM_GATE_ENTRY-GR_YEAR   = IS_MKPF-MJAHR.
     MODIFY ZMM_GATE_ENTRY FROM WA_ZMM_GATE_ENTRY .u201Dupdating the Z-table
ELSE.
      MESSAGE E901(ZMM) WITH GS_EXDATA_HEADER-GATEENTRYNO WA_ZMM_GATE_ENTRY-GR_NUMBER.
    ENDIF.
Is there any other option to replace the commit work in BADI?
Plz suggest...
Regards,
P.S.Chitra
Edited by: Chitra Karthik on Aug 10, 2010 11:19 AM

Hi,
I don't think even you do commit work it makes much difference and also Commit work also we can eliminate in the code.one more option is selecting the data from table to check whether it is updated or not.
IF WA_ZMM_GATE_ENTRY-GR_NUMBER IS INITIAL.
      WA_ZMM_GATE_ENTRY-REFERENCE = GS_EXDATA_HEADER-REFERENCE.
      WA_ZMM_GATE_ENTRY-REFWERKS = GS_EXDATA_HEADER-WERKS.
      WA_ZMM_GATE_ENTRY-GR_NUMBER = IS_MKPF-MBLNR.
     WA_ZMM_GATE_ENTRY-GR_YEAR   = IS_MKPF-MJAHR.
     MODIFY ZMM_GATE_ENTRY FROM WA_ZMM_GATE_ENTRY .u201Dupdating the Z-table
IF sy-subrc eq 0.
do.
select gr_number from ZMM_GATE_ENTRY where reference = GS_EXDATA_HEADER-REFERENCE.
if sy-subrc eq 0 and if gr_number is not initial. (record Found)-> means updated.
exit.
else.
MODIFY ZMM_GATE_ENTRY FROM WA_ZMM_GATE_ENTRY.
endif.
enddo.
endif.
ELSE.
      MESSAGE E901(ZMM) WITH GS_EXDATA_HEADER-GATEENTRYNO WA_ZMM_GATE_ENTRY-GR_NUMBER.
    ENDIF.
Regards,
Nagaraj

Commit work in BAPI

Hi Experts,
Why should not use COMMIT WORK in BAPI ? If I give COMMIT WORK in BAPI what is will happen?

Hi,
1. Why should not use COMMIT WORK in BAPI
I suppose you are asking this in context of Z BAPI and not standard BAPI.
The reason why we should not use is bcos SAP has recommended the design for BAPI in that manner.
2. If I give COMMIT WORK in BAPI what is will happen?
Well, as such there is nothing wrong going to happen. (Unless there is some dependent update in database)
To give you an example.
Suppose we have to update ZTABLE1 and ZTABLE2- the code for which is in TWO SEPARATE BAPIs.
Also it is requierd that if one fails, then other should not get updated. Either All or Either None case.
ZBAPI1 - TABLE1
ZBAPI2 - TABLE2
If ZBAPI1 is called and we have written commit work inside that, TABLE1 will get updated.
Then if there is any error in ZBAPI2, then TABLE2 will not get updated in hence the information will be INCONSISTENT.
3. Hence, the flow should be like this; (No commit work inside the bapi)
Main Program.
Call ZBAPI1.
Call ZBAPI2.
COMMIT WORK.
This will ensure that ALL or NONE happens.
regards,
amit m.

How Commit works?

Hello all,
A question:
We are having some problem running a JOB. The job is taking too much time to finish. However at end the Commit occurs.
Let´s suppose:
We are running a Program (in BACKEND) that updates a table
The Backend process has not finished (meaning: commit does not happen yet).
At same time, in a FRONTEND (portal), user is doing changes that affect the same program above.
The question is:
At the moment user makes the change(s), can this change occurs in the Backend process which is running?
Perhaps the question should be:
The entry(ies) in the Backend Process is LOCK when program is running? Then in this case if user makes a change in Frontend the change is not gonna happen in the Backend process?
Can someone help me out to understand this process.
Thanks in advance!
Regards,
Barbara

Hello Naimesh
Many thanks for your replay!!!! I am new in this subject and I have some little questions to be totally clear.
Following what you said in your last statement:
when you JOB is modifying some data and the commit work doesn't happen yet and somebody changes those data and save...then the data which was entered by user will be overwritten by the job's COMMIT WORK.
Questions:
1) In this case this will happen if the program is running without LOCK object, isnt it?
In our situation here: The JOB is take too much time to run
2) Is that possible that this occurs because the program is running without LOCK object?
3) Is there anyway to check if the program did run with or without LOCK object?
Many Thanks,
Barbara

Commit work

Hi all,
Please help me in this issue,
When we using Update ABAP statement what is the need of using again a commit statement if we dont use commit statement.
Thanks & Regards
Reddy

Hello Reddy,
COMMIT is used when you code directly in ABAP and make changes in the database and want to reflect in the database immediately.
When you perform COMMIT , all the LUW s work will be reflected to the database,
COMMIT WORK is the key word to make the database change. And whereas ROLLBACK is the opposite to commit work,
This statement will apply any outstanding database updates and wait until they have actually been put on the database before proceeding to the next statement.
An ordinary commit work will initiate the process to update the databases in a separate task and will press on in your abap.
COMMIT WORK: ( Asynchronous)
Your program does not wait for any acknowledgement. it just start executing the next statment after COMMIT WORK.
For your kind reference please check the below link
http://help.sap.com/saphelp_erp2005vp/helpdata/en/fc/eb3b64358411d1829f0000e
829fbfe/content.htm

Reward points for all useful answers....
Cheers !
Moqeeth.

How to use commit work as per the requirement?

Hi all,
Here i have a requirement about database table updation. I have to update a database table, at the time of doing commit work it has to check the following condition .
The data should be split up in different groups or records of no more than 2000 after which a commit to the database is executed.
So can anybody help me in this regard with a piece of code? and i want to know during updation how to lock the data base table and how to unlock? Is there any standard function modules to call regarding this locking and unlocking?
Thanks & Regards
Naidu

which table is that? and do you have any code so far?
Logically you need to loop thru your records, lock the table for that record, update the table , unlock the tabel record, count the entires so far, andi f it is 2000 issue commit work.

Invalid COMMIT WORK in an update function module. in VKM1 Tcode

Hi All,
I am getting the short dump with message "Invalid COMMIT WORK in an update function module. "
Calling a COMMIT WORK in an update process is not allowed
because the function modules triggered in a Logical Unit
of Work cannot then be processed correctly.
in FM : SO_DOCUMENT_SEND_API1
Prev. it was giving error in one of my driver program where I had written the commi Work after calling FM for sending fax :
"CONVERT_OTF_AND_FAX" .
call function 'CONVERT_OTF_AND_FAX'
    exporting
      FAXOPTIONS = W_ITCPP
      USER       = NAST-USNAM
    importing
      MSGID      = W_MSGID
      MSGNO      = W_MSGNO
      MSGV1      = W_MSGV1
      MSGV2      = W_MSGV2
      MSGV3      = W_MSGV3
      MSGV4      = W_MSGV4
    tables
      OTF        = IT_OTF.
if sy-subrc eq 0.
commit work.
submit RSCONN01 with MODE = 'FAX' and return.
endif.
Please explain me where and how I can change my code so that this error should not come?
Rgds.
MAdhuri

Hello, Suhas!
I am getting the short dump with message "Invalid COMMIT WORK in a COMMIT WORK or ROLLBACK WORK."
Short text
    Invalid COMMIT WORK in a COMMIT WORK or ROLLBACK WORK.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_FDT_CC_SERVICES============CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    The call of a COMMIT WORK in a FORM, that will not be executed until
    the commit or rollback point of the caller using the variant
    PERFORM ... ON COMMIT or PERFORM ... ON ROLLBACK is not permitted.
etc.
Could you help me to solve the issue?
Regards,
Kseniya Tsyganchuk

Regarding COMMIT WORK

Similar Messages

Maybe you are looking for