Issue on Commit work

Hi Friends ,
I am calling function module where I have created Background Job and Submitted it . In Submit call I am updating the database table . In a LOOP am updating service entry sheets of one Purchase order . (1 PO consists of More than 1 Service entry sheets)
Here I am able to update only First SES when it is processing the Second Service Entry sheet the PO get Locked.
I have used the COMMIT and WAIT command after the updating the Service entry sheet.
Here I am getting PO LOCK error by Same USER.
Can u suggest me in this Scenario.
Thanks in advance.
Jagadeshwar.G

Thanks for information .
Even i have coded as follows .
ITAB records as follows
S1 - Servcice Sheet
P1 PO
X - other flds
S1   P1 X   X X
S2   P1 X X   X
S3   p1 X X    X
Loop at ITAB to WA.
UPDATE <ZTABLE> with .......
commit work and wait.
ENDLOOP.
Error Message : PO is already in process by XXXX.
- This program runs in Background .My problem is I can't test this prg in dev .
Could you please explain the situation u faced so that i can validate it . Thx in advance.
Thx

Similar Messages

Issue with Commit Work and Wait.

Hi All,
None of the programs are working in my system which are calling BAPI BAPI_TRANSACTION_COMMIT.
On COMMIT WORK AND WAIT statement, the process is going into indefinite loop. Everything was fine till last Thursday and there are no updates or patch level change or notes applied in the system.
Please advice.

<div style="text-align:left">We tried everything but still the issue is there.</div>
Normally it's much easier to get help if you try to be as detailed as possible when explaining the problem and what exactly you have tried. No offense, but tried everything most likely translates into almost everything...
Some information/checks I'd be looking for:
<ul style="list-style:square!important">
<li>What functions are (or coding is) involved? Are they all standard or custom?</li>
<li>Have you tried update debugging and/or the usual traces (runtime analysis, SQL trace, etc.)?</li>
<li>What do you see in the process overview?</li>
<li>What about system log, developer trace, database logs/alerts, etc.?</li>
</ul>
Obviously my list is much too short and incomplete - yours must be longer. If you share your results (including your exchange with SAP) I suspect you have a better chance (though of course no guarantee) of somebody providing a valuable clue.
Not sure if it's just me, but the part that sounds so odd and suspicious is that you only mention commits via BAPI_TRANSACTION_COMMIT. As this is just a wrapper around a COMMIT WORK I'm tempted to think it's the functionality that's invoked before (i.e. linked to the registered update functions/modules). Without any additional knowledge though, my first shot was for general update problems (which you ruled out).

Do CIF BAdIs issue implicit COMMIT WORKS (for FM's called "in update task")

I am calling the CIF BAdI:
/SAPAPO/TR_TRANSFER.
In the PUSH_LANE_DATA method of this BAdI, I want to call a function module "in update task".
To trigger the actual execution of this function module, do I have to code an explicit COMMIT WORK in the BAdI or will SAP automatically generate a COMMIT WORK when the BAdI ends?

Hope you have called the FM correctly with the additional importing parameter , also check if your FM is RFC enabled then check the "pass by value" option.

Commit work in FQevents in FICA(PERFORM commitroutine ON COMMIT )

Hello Experts,
i am trying to create an event to trigger a workflow using function module swe_event_create.
i am doing this in an FICA event 5500 after triggering this workflow i need to stop the further processing so i am using Error message statement.
when i am calling swe_event_create without commit work the event is not getting triggered .
when i checked the documentation of this event it was written that
To ensure the consistency of the system, note that you must not use the following language elements in events:
COMMIT WORK
ROLLBACK WORK
CALL FUNCTION 'DEQUEUE ALL'
Deletion of locks that you have not set yourself.
If you update additional data in an event and use the construction PERFORM commitroutine ON COMMIT to do this, note that:
At the end of the commitroutine, all internal tables from which data was updated must be initialized again to prevent a duplicate update in the next call.
A PERFORM rollbacktroutine ON ROLLBACK must also be called. In the rollbackroutine initialize the same data that is initialized at the end of the commitroutine.
If you want to carry out checks in an event, when you issue messages, note that background processing of the process terminates with warning messages. You should therefore avoid issuing warning messages if possible. However, you should definitely issue warning messages if the value of SY-BATCH is initial.
how i can use PERFORM commitroutine ON COMMIT could you please paste the code for this
also plz tell me
why my event is not getting generated without commit work . do we have any better way to do it

Hi Anit,
The FM SWE_EVENT_CREATE does its job, only when 'COMMIT WORK' is executed, after it. Now, as per the general programming guidelines (quoted in your question), you can't write COMMIT WORK in your code. You shouldn't, because it would write half baked document into database. Something that's undesirable. The workaround prescribed in the event documentation (again, as quoted in your question) allows to achieve the goal in following manner-
1. Do all calculations in your event and put the final values - that are necessary for the workflow - in global variables. Refer to the ABAP documentation for PERFORM ... ON COMMIT for choosing global variables over parameter passing.
2. Once that's done, make the call to the FM, as given below-
PERFORM start_wf ON COMMIT.   "Within the FM implementing the event 5500.
*&      Form start_wf
*       The form routine to initiate the workflow
FORM start_wf.
CALL FUNCTION 'SWE_EVENT_CREATE'
    EXPORTING
      objtype           = objtype
      objkey            = objkey
      event             = event
    TABLES
      event_container   = event_container
    EXCEPTIONS
      objtype_not_found = 1
      OTHERS            = 2.
IF sy-subrc <> 0.
    RETURN.
ENDIF.
CLEAR: objtype.
CLEAR: objkey.
CLEAR: event.
CLEAR: event_container.
"And all other global variables that are used in your call for this FM
ENDFORM.                    "start_wf
3. Note that you need to clean up the global variable set up in step 1 (also mentioned in the event documentation) . It is to ensure that some other call to the same FM doesn't use those values.
You needn't issue a COMMIT WORK statement anywhere in your code written in event 5500 implementation. The standard FMs, that update the SAP tables with document information have COMMIT WORK in them. As you have registered the FM 'start_wf' by PERFORM ... ON COMMIT, it would be executed along with the database update triggered by standard FM.

Automatic commit work after class method?

Hi guys,
after calling a class method, is there an automatic commit work? Or do I have to insert a commit work into the class method?
At which points, a commit work is automatically called?
Regards,
Basti

Hi,
there is so much confusion about commit, commit work and rollback:
1. At the end of LUW and at every interruption (screen display including message issued, RFC calls,...) an implicit database commit occurs.
2. COMMIT WORK will trigger all update task processes that have been registered before (call function in update task, perform on commit). Most BAPI functions use perform on commit. An implicit database commit ist not a COMMIT WORK.
3. Rollback work will delete all pending update tasks inclusing all database updates not yet commited.
4. Only the 'Master'of any process should rule the COMMIT WORK because COMMIT WORK means that ALL pending update tasks are executed. So only the caller on top of the hierarchy should issue the COMMIT WORK because a later ROLLBACK is not possible - ROLLBACK only works if not y<et committed.
These rules work independent of programming feature used - nothing different in oo.
Regards
Clemens

BDC commit work issue.

Hi all,
Im facing a issue in BDC:
In a loop there is a select query called and if sy-subrc = 0 the call transaction using mode N is called in the next step.
first time if the sy-subrc is ne 0 then call transaction is done which updates( considered as new entry )
the table used in the select query.
when the loop executes the second time the sy-subrc is still 4 instead of 0( previous data is not updated in DB ).
So after all the execution only the last record exists in the transaction,
that is the table control index is always 1 due to the select query failure.
Here the problem is when using mode N, when mode A is used its working fine.
The data is not getting updated in db in first loop cycle, so the select query in second loop cycle fails.
The select query gets executed for the same material no's.
I have also tried with explicit commit and synchrounous update is used
Thanks,
Keshav

Hi Suhas,
This applies when we open a cursor for select, use fetch to get the data. Ater the fetch if we commit, then it closes all the open cursors. So next fetch on the previously opened cursor will lead to dump.
Perfect example could be.
SELECT......
Do processing.
COMMIT WORK.
ENDSELECT.
Keshav,
I beleive you are not using SELECT ENDSELECT in your case. If it is SELECT SIGLE/SELECT INTO TABLE, OPEN, FETCH and CLOSE CURSOR operations happens at the back end during the select query execution. ( We can see ST05 trace for this). So as per my understanding COMMIT after the CALL TRANSACTION shouldn't cause any problem.
Please correct if i am wrong any where.
Thanks,
Vinod.

BCS: Performance Issue - Most of the time is spent doing commit work.

Hello,
We are experiencing performance issues with our BI server. This performance issue can been seen during our BCS runs. Our DBA has indicated that he sees a very high percentage of time time is spent doing "commit work".
Curretly, we are running BI7 nw2004s, Basis 700, support pack 14.
Anyone else experience this? As the BCS run is mainly stanard SAP code, I was wondering if there may be some snotes that correct this?
Thank you for any help you could provide us.

If it is related to SEM-BCS and new EHP releases, then there are still big problems with the monitor and tasks status management (meaning problems with performance). Is it the case? If yes, then you'd better look for already released notes reg this and formulate your own OSSs if you don't find anything relevant.

Commit work issue inside userexit while triggering sender proxy

Dear All,
We have a situation where in, a sender proxy is triggered inside the Userexit of a transaction. When we try to execute the proxy in a test program, the XML message is not reaching XI unless a commit work statement is put immediately after Proxy call method. But this solution cannot be incorporated inside the Userexit as that will commit the whole transaction. Also there are number of other methods triggered inside the Userexit after the Proxy is triggered.
Kindly respond to the below queries:
1. Is there a Standard commit after a userexit is triggered? if yes, shall that solve the problem?
2. Is there any solution other than commit work statement?
Thanks in Advance,
Zafar Ali

Hi,
Any userexit is part of a standard SAP program, every Standard SAP program esp any transaction like VA01, MIRO, ME21n etc will certainly have a commit work at the end of the transaction. or there will be a implicit commit work after a dialog step.
So when that commit work is executed, the proxy call wil be sent for sure.
So it will work if you don't put commit work in the userexit immediately after the proxy call.
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.

Error message when issuing a COMMIT in a store procedure

Hello experts,
Please help.
I have a problem where i cannot specify a COMMIT in a store
procedure. I have the following error message:
=================================================================
00034, 00000, "cannot %s in current PL/SQL session"
// *Cause: An attempt was made to issue a commit or rollback
from a PL/SQL
// object (procedure, function, package) in a session
which has this
// disabled (by 'alter session disable commit in
procedure')
// *Action: enable commits from PL/SQL in this session, or don't
attempt
// to use commit or rollback in PL/SQL when they are
disabled
// in the current session.
=================================================================
Thanks very much for a reply
Kind regards
Yogeeraj

The solution is to issue the statement
alter session enable commit in procedure;
However, I'd think carefully about doing this. Procedures are
often called as part of a wider transaction. If the procedure
issues a commit ALL the preceding work is also commited. If
there is something subsequent in the transaction that fails and
issues a rollback, it will onlt rollback the work done after the
procedure. This may lead to your database being in an
inconsistent state.
rgds, APC

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

Lock and Commit work in INBOUND IDOC

Hi Experts,
Problem is about lock and commit work
i need to receive idoc for Good receipt for purchase order.
For one Purchase Order i can receive many good receipt Idoc at the same time and when first came in Lock the Purchase Order and further idoc came after give Errors becouse purchase Order is lock.
Problem is not the serialization (the sequence is correct), but is the lock.
Any idea on how to fix this issue? (maybe there is some std settings??)
Cheers
Boris

Hello Guys
the packetsize is already set to 1 but the problem still again..... and where i can find this setting   "in Customizing choose Engineering Change Management ® Define statuses for master record". ?
Any way i try in function module in inbound to check the lock object with this sample code:
      DO 30 TIMES.
        CALL FUNCTION 'ENQUEUE_EMEKKOS'
         EXPORTING
           mode_ekko            = 'S'
           mandt                = sy-mandt
           ebeln                = goodsmvt_item-po_number
           _scope               = '2'
         EXCEPTIONS
           foreign_lock         = 1
           system_failure       = 2
           OTHERS               = 3.
        IF sy-subrc <> 0.
          WAIT UP TO 1 SECONDS.
        ELSE.
          EXIT.
        ENDIF.
      ENDDO.
but also with this....problem syill again...
thanks
Boris

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

I need to have COMMit WORK with in a FM, which is calling in UPDATE task

Hello
I am sending out the custom IDOC from SAP to partner application by writing a custom my_OB_IDOC_FM, well.
With in this my_OB_IDOC_FM, for some functionality, i am using a standard SAP FM and I need to use a COMMIT WORK immediately after this standard SAP FM call.
But, all my IDOC is calling in update task, so once am triggering IDOC (inturn my_OB_IDOC_FM is calling in UPDATE task) am getting dump because of that inside used COMIT WORK statement!
So, pls. let me know how can replace this COMMIT WORK or hoe can i fix my issue? can i do like CALL FUNCTION standard_SAP_FM in background task/seperate task? so that i can use COMMIT WORK?
Thank you

I've dealt with something similar before.
You could make a new z-program and run in a background job... like this:
* create the job
CALL FUNCTION 'JOB_OPEN'
      EXPORTING
          JOBNAME          = mv_JOBNAME
      IMPORTING
          JOBCOUNT         = mv_JOBCOUNT
      EXCEPTIONS
          CANT_CREATE_JOB = 1
          INVALID_JOB_DATA = 2
          JOBNAME_MISSING = 3
          OTHERS           = 4.
* submit the program to the job
    SUBMIT ZPROGRAM
      WITH i_ebeln in mr_ebeln
      WITH updall = 'X'
      WITH wq_simul = ''
      TO SAP-SPOOL
        DESTINATION sv_output_device
        IMMEDIATELY ''
        KEEP IN SPOOL 'X'
        WITHOUT SPOOL DYNPRO
      USER sy-uname
      VIA JOB mv_jobname NUMBER mv_jobcount
      AND RETURN.
* submit the job
CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
        JOBCOUNT             = mv_JOBCOUNT
        JOBNAME              = mv_JOBNAME
        STRTIMMED            = 'X'
    EXCEPTIONS
        CANT_START_IMMEDIATE = 1
        INVALID_STARTDATE    = 2
        JOBNAME_MISSING      = 3
        JOB_CLOSE_FAILED     = 4
        JOB_NOSTEPS          = 5
        JOB_NOTEX            = 6
        LOCK_FAILED          = 7
        OTHERS               = 8.

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.
<u><b>For your kind reference please check the below link</b></u>
<b>http://help.sap.com/saphelp_erp2005vp/helpdata/en/fc/eb3b64358411d1829f0000e
829fbfe/content.htm</b>
<b>
Reward points for all useful answers....
Cheers !
Moqeeth.</b>

Issue on Commit work

Similar Messages

Maybe you are looking for