Commit work while debugging

Hi,
In the old debugger, there was only one session and commit work used to take place after every step of execution. In the new debugger, debugging takes place in two sessions. Will the commit work take place here too after every step of execution ?
Best Regards,
Raghu

Hi,
Just to clear some things. For debuger to make it possible to hold its state, there has to be reserved work proces for this need (normally when gui is launched wp is lost - there is no need to occupay it since application server has no job to do - it's waiting for user input). That's why there is a specific amount (can be changed) of wp defined for this purpose. So yes it is possible that you'll get commit after every step under debugger when this pool of free debuger wp is empty (many people are debugging in the same time). Explanation for this "commit every step" is that without dedicated wp that would be waiting for you, everytime you get back to your debugger, dynpro is being shown to you and as a result you lose wp, LUV is ended and so is your connenction between aplication server wp and DB wp. System has to do something with your changes - rollback or commit. SAP decided that it will be commit. I hope this is of any help
Best regards
Marcin Cholewczuk

Similar Messages

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.

ERROR while debugging a SELECT..ENDSELECT

Hello All,
We get an error while we go into the select..endselect loop during debugging. Because of this if we try to do some research on existing program with Select-endselect..it fails in the second pass of this loop.
This problem was not there earlier, but after we upgraded from 4.6 to 4.7 this problem is bugging us..every day. Does any one have a clue why ?
Thanks!!
Regards,
Vishal

Hi,
debugging a SELECT...ENDSELECT statements brings to a LUW commit work if no other work processes are available for debug.
See OSS notes 675, 2104.
From OSS note 675 **********************************
Cause and prerequisites
Chain of causes:
      1. There is a statement in one of the Select loops, that leads to a database Commit (or Rollback).
      2. A database Commit causes the database to lose the cursor.
      3. The system cannot automatically continue within Select loop after loss of cursor.
Following statements lead to a database Commit:
    * All statements that cause a change of screen (CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT, I/W-Message)
    * BREAK-POINT/ Debugging
      . if no debug process free
      . always after regeneration (in order to release generation lock).
    * WAIT Here a work process is released and a Commit is executed.
    * COMMIT WORK/ROLLBACK WORK
From OSS note 2104 **********************************
Solution
The "COMMITWORK" message appears in the ABAP debugger when programs
orscreensrequireregeneration,or when not enough free capacity
is available inthesystem (or else the debugger blocks a system
process).
Normallyonly one work process is released for debugging. This
isgenerally insufficient ina developmentsystem, as processes
can be blocked for other reasonstoo(background processing,
CPI-C connections,andso on).
The number of work processes made available for debugging can
be configured using the profileparameter
                  rdisp/wpdbug_max_no
Forexample:
                rdisp/wpdbug_max_no = 10
setsthe maximum number of work processes made available for
debuggingto 10. It may be necessary to generally increase the
numberofwork processesatthis time (parameter rdisp/wp_no_dia).
In all other known cases, an error in the application program is
involved.
Regards, Manuel

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 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.

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 while debugging in NWDS

Hi,
I am getting a "source not found" error while debugging in NWDS.
I put a break point in a particular class, but it never gets hit, instead I get an error saying "source is not found".
I have tried rebuilding, deploying and even starting the IDE but nothing works.
Can anybody help me here.
Regards
Arvind

Hi Arvind,
1) Have you set debug on in the server?
If not you need to on debug on SAP-J2EE engine(For web applications).
2) If that is a pure java class then it will work.
Regards,
Devender V

How to find list of internal tables while debugging

Hi Experts,
I am debugging a block of an ABAP program( User Exit ). Is there any facility to see what are the internal tables, work areas are available for that particular block? Can I see it new debugger? Because I don't know from which internal table I can take a particular value, which I need to populate in an user exit.
Thanks and regards,
Venkat.

hi,
you can find the exact answer here :
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/840ad679-0601-0010-cd8e-9989fd650822#q-6
under heading List of internal tables while debugging
regards
rahul

COMMIT WORK AND WAIT does not work

Hello,
I know this question has been asked many times in various forums. But the fact remains that there is no definitive solution found for this problem which does not involve WAIT UP TO n SECONDS or SELECT until the DB commit has been completed.
We have an IDoc based inbound interface for creating Project Defintion and WBS Elements. Here is how the code looks like in the processing function module:
* Create Project Defintion
CALL FUNCTION 'BAPI_PROJECTDEF_CREATE'
EXPORTING
    project_definition_stru = lwa_proj_bapi
TABLES
    e_message_table         = lt_messages.
* If no errors
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
    wait = 'X'.
* Other code
* Create WBS Element (BAPI could not be used because not all fields are allowed to be updated)
CALL TRANSACTION 'CJ11'
Now while creating the WBS Element, transaction CJ11 returns an error that 'Project does not exist'. This is not correct because the same Project was successfully created in the previous step.
It is clear that the problem is because of the delay in database commits.
This happens only with few IDoc's and not all of them. And of course, the problem does not occur if I induce WAIT UP TO n SECONDS after BAPI_TRANSACTION_COMMIT. But this is not the best practice.
The question is why BAPI_TRANSACTION_COMMIT does not wait even though we are forcing it to?
Thanks in advance
Sagar Acharya

Suhas wrote:
But i am baffled that although the COMMIT has happened earlier why is the data not updated in the DB ?
Well, it's just a [COMMIT WORK|http://help.sap.com/abapdocu_70/en/ABAPCOMMIT.htm] and not a [COMMIT WORK AND WAIT|http://help.sap.com/abapdocu_70/en/ABAPCOMMIT.htm#@@AND%20WAIT@@COMMIT%20WORK@@]. Let me quote the ABAP help:
If you do not specify the addition AND WAIT, the program does not wait until the update work process has executed it (asynchronous updating), but instead is resumed immediately after COMMIT WORK. However, if the addition AND WAIT is specified, program processing after COMMIT WORK will not continue until the update work process has executed the high-priority update function modules (synchronous updating).
@Sagar Acharya: Well, I thought you were looking for an explanation why sometimes the project isn't created (and you only had posted coding that showed details for step 1) - I'm trying hard, but my mind reading skills are rather limited yet...
So let's think about step 2 and 3: I assume that you made sure that your coding always references the correct WBS element. Again the commit (without wait) is done already via CJ11 (e.g. check form BUCHEN in SAPLCJWB). I'd expect though that the synchronous update mode should make this work. Since it doesn't, I'd try local update mode, which is what I'd choose in your case anyhow.
Apart from that my mind is pretty blank, except for the usual silly things to check. E.g. are you sure you're coding is correct, you are handling all return messages and log them for inspection later (e.g. application log), you are certain that the WBS was actually created by the same IDoc that throws the fit (and IDoc was not reprocessed), etc.
So maybe somebody else has better ideas...

COMMIT WORK: Timing of DB commit and update modules

Hi all,
Does anyone know categorically the order of starting the asynchronous update modules (CALL FUNCTION ... IN UPDATE TASK) and the database commit, when a COMMIT WORK is done?
Does COMMIT WORK:
- Do PERFORM ... ON COMMIT
- Start asynchronous update processing
- Do database commit
Or does it:
- Do PERFORM ... ON COMMIT
- Do database commit
- Start asynchronous update processing
My reason for asking is some code (not written by me!) that essentially raises CREATED workflow events in the update task, but performs the corresponding database inserts in the current work process.
It looks like we are getting the situation that sometimes the table entries do not exist when the update modules exist, which in turn suggests to me that perhaps the asynchronous update modules are started just before the database commit that is done when a COMMIT WORK statement is executed.
Cheers,
Scott

Christian,
Before the update module execution. Here's some code to highlight and let's assume it runs in a dialog process. And to everyone else, yes, I know this is a poor way to implement updates!
INSERT INTO zmyobject VALUES lv_myobject.
CALL FUNCTION 'SWE_EVENT_CREATE_IN_UPD_TASK'
IN UPDATE TASK
EXPORTING
    objtype = 'ZMYOBJECT'
    objkey = lv_myobject-key
    event   = 'CREATED'.
COMMIT WORK.
So I meant to ask the question of whether we could guarantee that the new record in table ZMYOBJECT would be committed to the database <i>before</i> the update module was executed. It really is a theoretical question though it did not begin as one.
I do not believe the answer to this problem can be determined by debugging, because given that these two steps occur so close in time to one another, by the time the update module appeared in the debugger, it would be unrealistic to expect that the DB insert performed in the dialog process had not been committed yet.
I might be wrong, but I really don't think you're going to find ABAP logic embedded in SAPMSSY0 or elsewhere that invokes the update modules or performs a DB commit. Rather, it is my suspicion that the COMMIT WORK statement works like this:
- Drop into the kernel
- Does a callback to SAPMSSY0 to execute form %_BEFORE_COMMIT to raise a static OO event
- Does a callback to SAPMSSY0 to execute form %_COMMIT and thereby process any PERFORM ... ON COMMIT
- Does a database commit
- Does a callback to SAPMSSY0 to execute form %_AFTER_COMMIT to raise another static OO event
Further, I believe that it is the database commit that now makes the queued CALL FUNCTION ... IN UPDATE TASK now visible in VBLOG to other processes.
Lastly, and this is of course wild speculation, I suspect that it is an update process running somewhere else that detects the new entries in VBLOG and grabs them for processing.
So, I'm kind of changing my position from earlier to state that I believe the COMMIT WORK statement does not directly trigger the update modules at all, rather it just does the database commit and this makes visible the pending update modules to the dispatcher / update work processes which probably grab the update LUW's on a first come first served basis.
At least, that is how I would design it :-).
Cheers,
Scott

How to use commit work in class cl_bls

Hi,
When i have used commit work after email sent,
it goes into dump.
Here is the code segment:
try.
    -------- create persistent send request ------------------------
      send_request = cl_bcs=>create_persistent( ).
    -------- create and set document -------------------------------
      pdf_content = cl_document_bcs=>xstring_to_solix( pdf_tab ).
      document = cl_document_bcs=>create_document(
            i_type    = 'PDF'
            i_hex     = pdf_content
            i_length = bytecount
            i_subject = sub ). "#EC NOTEXT
    add document object to send request
      send_request->set_document( document ).
    --------- add recipient (e-mail address) -----------------------
    create recipient object
      recipient = cl_cam_address_bcs=>create_internet_address( recip-recip ).
    add recipient object to send request
      send_request->add_recipient( recipient ).
    ---------- send document ---------------------------------------
      sent_to_all = send_request->send( i_with_error_screen = 'X' ).
     commit work.
      if sent_to_all is initial.
        message i500(sbcoms) with recip.
      else.
        message s022(so).
      endif.
------------ exception handling ----------------------------------
replace this rudimentary exception handling with your own one !!!
    catch cx_bcs into bcs_exception.
      message i865(so) with bcs_exception->error_type.
endtry.
What could be the reason?
Is there any way to use commit work in class while sending email as in SO_NEW_DOCUMENT_ATT_SEND_API1 fm?
Thanks.

Hi,
I have used
submit program.....
but in update task i have used it.
"Z_SD_ORDER_UPDATE".    program is a print driver program.
However error says:
There is probably an error in the program
"Z_SD_ORDER_UPDATE".
This program is triggered in the update task. There, the
following ABAP/4 statements are not allowed:
- CALL SCREEN
- CALL DIALOG
- CALL TRANSACTION
- SUBMIT
I used submit as:
WAIT UP TO 2 SECONDS.
SUBMIT rsconn01 WITH mode = 'INT'
                  WITH output = ' '
                AND RETURN.
Instead of submit i want to use commit work but i also get a dump after commit work too.
How can i use commit work in above code?
Thanks.

Source Not Found Error while Debugging

Hello,
I get annoying Errors while debugging a midlet. I reinstalled all programms an created a new midlet suite + midlet but the error is still there and the Midlet doesnt start.
i got Eclipse Version: 3.2.2, Eclipse ME 1.6.6, the newest WTK 2.5 and java.vm.version=1.6.0-b105.
I configured everything like www.eclipseme.org says it would be correct.
Running a Midlet works fine.
The bug opens an Helper.class file which says:
Class File Editor: Source not found: "The Jar of this classfile belongs to the container J2ME library [ Sun Java (TM) Wireless Toolkit 2.5 for CLDC/MediaControl]. To configure the source attachment, go directly to the corresponding configuration page (For example for JRE go to 'Installed JRE#s page in references).
Any clou how to fix this?? I need to debug my midlet :-/
THANKS!
Byby
pako

Hi,
I just had the same problem and navigated to this page here in hope for a solution...
However I've solved the problem now. On Eclipse, do the following.
1) Right-click on the added Jar-file (which is producing the problem)
2) On the popup-menu choose "Build Path" and "Configure Build Path..."
3) On the opening preference window, click the checkbox of the Jar
This is probably necessary because the jar has to be exported such that the simulator is able to execute it.
Greets,
Juri
http://juri-strumpflohner.blogspot.com

Since release 5.0 : commit work in ZXPADU02 is not working !

Hello everybody,
I try to send documents in FM ZXPADU02 following bcs_example, but the commit work has no effect. I set it like this
CALL METHOD send_request->send(
              EXPORTING
                i_with_error_screen = 'X'
              RECEIVING
                result              = sent_to_all ).
            commit work.
This sentence was working till 4.6c, but since we migrate to 5.0, the commit work is no more working. Sending documents via smartforms (in the same user exit) works because instead of using commit work, we set bcs_commit = 'X' in output-options.
We have no problem with commit work in normal reports, but I think that used in a user exit, the behavior has been changed since we are on ERP2004.
Any idea ?
Jean-Paul

Hello,
Of course, the code is activ, the sendmail is a very small part of it. I try to put many things with commit work (also commit work and wait). I set it almost ... everywhere include in the standard program SAPFP50M just after the CALL CUSTOMER-FUNCTION '002', no result. Nothing is done and when debugging sy-subrc is always at 0 after the commit.
Regards.
jp

JDeveloper 11.1.1.1.0 hangs while debugging a simple application

Hello all... I use Jdeveloper 11g in my Fedora linux ( version 9 ) machine. Jdev works fine normally, but when I try to debug a sample application it simply hangs and does not allow me to do anything besides going to console mode and killing off all the processes associated with Jdev in the following manner..
[sugantha@localhost ~]$ ps aux | grep jdev
and then kill -9 <PIDs>
The code where it hangs exactly is this...
*public void actionPerformed(ActionEvent e) {*
String cmd = e.getActionCommand();
*if (ON_TOP_COMMAND.equals(cmd)) {*
if (onTop.isSelected())
layeredPane.moveToFront(dukeLabel);
else
layeredPane.moveToBack(dukeLabel);
*} else if (LAYER_COMMAND.equals(cmd)) {*
int position = onTop.isSelected() ? 0 : 1;
layeredPane.setLayer(dukeLabel,
layerList.getSelectedIndex(),
position);
with the breakpoint placed in line 2 of the code shown.Pressing F7, F8 or F9 has no effect. Has anyone ever encountered this issue or is there a workaround to avoid this kind of behaviour while debugging in JDeveloper. Thanks in advance.

"Installing the ADF runtime is not required if you are using JDeveloper to run applications in Integrated WebLogic Server."
http://docs.oracle.com/cd/E24382_01/admin.1112/e16179/deploy.htm#BGBECCBE
When I explicitely add the groovy-lang-1.6.3.jar in "Project properties" --> "Libraries and Classpath" then it works!
The groovy-lang-1.6.3.jar gets deployed with the application.
But still, why isn't it sufficient to have "ADF Model Runtime" (containing groovy-lang-1.6.3.jar) added ??
Is the ADF Model Runtime library deployed with the application? Select Manage Libraries. Is the ADF Model Runtime library selected as Deployed By Default?
If a new library is created, is the library a Deploy by Default?
If a library is added to a Model or ViewController project and used in the other project is a dependency defined between projects?
On JDeveloper 11.1.1.4.0 the same application works when debugging it.
Does anybody know how to fix it. Is there a missing library which was automatically added in the old JDeveloper but is not any more in the new one?
JDeveloper 11.1.1.4.0 JDeveloper runtime libraries that are deployed into Oracle WebLogic Server to support ADF applications includes groovy-all-1.6.3.jar in the adf.oracle.domain.ear Library and System Classpath.
http://docs.oracle.com/cd/E23549_01/web.1111/e15470/ap_jdevlibs.htm#BCFCIGBJ
In JDeveloper 11.1.2.2.0 groovy-all-1.6.3.jar is included only in the adf.oracle.domain.ear Library, not the system classpath.
http://docs.oracle.com/cd/E26098_01/admin.1112/e16179/ap_jdevlibs.htm
And is 1.6.3 the right version for ADF 11.1.2.2.0 Applications or should I add a newer groovy version?
The groovy version is the same groovy-all-1.6.3.jar.
Edited by: dvohra16 on Sep 11, 2012 9:18 AM

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).

Commit work while debugging

Similar Messages

Maybe you are looking for