Commit work and wait in release 700 and 701

Hi guys,
it seems that commit work and wait does not behave same in release 700 and 701.
In 701, when using call transaction, upon execution of commit work and wait, it does not anymore proceed to the next lines of codes instead, it exits from the transaction. Hence, other updates are not being executed.
While in 700, it behaves properly.
Please advice.
Thanks!
Moderator message - (Almost) duplicate thread locked
Edited by: Rob Burbank on Jan 25, 2010 10:33 AM

You can use:
CALL TRANSACTION 'ZZZZ' OPTIONS FROM ITAB.
From F1 on CALL TRANSACTION:
... OPTIONS FROM opt
Effect
Allows you to control processing using the values of the componetns of the structure opt, which must have the ABAP Dictionary type CTU_PARAMS. The components have the following meanings:
RACOMMIT
Do not end transaction at COMMIT WORK
Rob

Similar Messages

My phone keeps on turning itself on therefore interrupts the ongoing "iPhone Recovery Mode" in iTunes. This then makes me go back to square one: restore and wait 4 hours over and over again. What do I do to make it not get up again?

My phone keeps on turning itself on, therefore interrupts the ongoing "iPhone Recovery Mode" in iTunes. This then makes me go back to square one: restore and wait 4 hours over and over again. What do I do to make it not get up again?

There's a whole lot to read in your post, and frankly I have not read it all.
Having said that, this troubleshooting guide should help:
http://support.apple.com/kb/TS1538
In particular, pay attention to the mobile device support sections near the bottom, assuming you have already done the items above it.

Fce 4 and the JVC's 700 and 100(pal)

Purchased two JVCs the 700 and the 100... will these work with FCE4
john

It's hard to tell you whether they are compatible until we actually see the specs for the cameras. Perhaps you could point us to the specs pages or give the full name of the model of the cameras?
Please help us to help you.

Hyperion and Siebel CRM release notes and Supported Operating System.

Hi DBA's
Kindly provide me the links for Release notes and What are the Operating system support for Hyperion and Siebel CRM?
Thanks in Advance.
Best Regards,
SG

Hi;
Thanks allot, the documents helped me and one last question regarding above versions of Hyperion and Siebel,
1) can i go with Windows 2008 Enterprise Edition 32bit Hyperion and Siebel?
2) is there any possibility that i want to keep database for both Hyperion and Siebel in Linux 4.0 ES 32bit and Application of Hyperion and Siebel in Windows 2008 EE 32bit?AFAIK Hyperion and Siebel new version is certified wiht Win2008 but i heard some of component not support on linux. Please check below
http://www.oracle.com/technetwork/middleware/bi-foundation/hyperion-supported-platforms-085957.html
http://download.oracle.com/docs/cd/E11886_01/V8/CORE/core_8_1.html
I suggest log a Sr and confirm it with oracle support if you have any doubt.
For your both question please move your post to related place which you could get more quick response, please visit :
Forum Home » Siebel
Forum Home » Business Intelligence Challenge to Go » Hyperion EPM
Regard
Helios

IPhone 6 Plus - what a terrible experience - Preordering and waiting on release day.

Long story, here goes.
Attempted to order the phone right after 3am EST - logged in at 2:55 EST - phones already available to order, so that was early. Was able to snag a iPhone 6 Plus 64gb in Grey. Date says 9/19 deliver by. Get my confirmation email 3 hours later - has a date of 10/14. Canceled my preorder same day as I was shown 2 different dates. So I decide to get one on launch day (9/19).
Wait in line at the West Chester OH (Tylersville Rd.) Verizon store. Was #31 in line, wait 2.5 hours just to get in the store, then have to wait for another hour before I can go up to the front to actually pick out a phone to order. Again, 6 Plus 64gb in Grey. SOLD OUT. No communication whatsoever from the staff to people in line or waiting that they were out of stock. I ask about 16gb and 128gb. None in Grey at all. Was told differently by a manager that there was additional stock for the 16gb and 128gb when I had just been told that no Grey models were in stock at all for the 6 Plus. One person did happen to nicely check other stores, but all locations were sold out of that model. Wasted 3 hours of my day when I could have been told 2 hours prior whether enough stock would be available. I seemed to be the only person not to get a phone up until that point, and I was only the 31st person in line. A little communication would have went a long way on both the preorder and the actual launch day process. So now I can't even order one and have it arrive by October, which is a joke in my opinion. I guess I should have kept my preorder active, but what to do when you are quoted two different dates? Verizon has really dropped the ball here and I will be looking into other competitors in the meantime.

Hi zharvey85,
I truly apologize for your experience at the store. However, we provided the pre order as a way to avoid needing to go to store as inventory availability are subject to change without notice. The pre order secures the device and the other email was for the shipping information. Perhaps you can re order the device online to get the ball rolling for you to get your iPhone 6 plus as desired as opposed to going to the store of which inventory can change depending on the availability.
Thank you!
EdW_VZW Follow us on twitter @VZWSupport

My ipad was having problems opening viewers, but I learned to power it off and wait about a minute and turn it back on and it rests the issue, do you have any other ways or ifs this the best it worked pretty good this time, but if it happens again

My Ipad has trouble opening setting tab and safari, it opens abd before you can enter anything the iPad shuts it down to the home screen, I mainly use my ipad for the internet or emails, I know the internet works because I still receive emails on it. Please help me out here.

Try clearing Safari, close all apps and reset the iPad.
Go to Settings>Safari>Clear Cookies and Data.
Tap the home button once. Then tap the home button twice and the recents tray will appear at the bottom of the screen. Tap and hold down on any app icon until it begins to wiggle. Tap the minus sign in the upper left corner of the app that you want to close. Tap the home button twice.
Reset the iPad by holding down on the sleep and home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider if it appears on the screen - let go of the buttons. Let the iPad start up.

Write to digital line and wait 20 mico sec and aquisition

i have DIO-32HS and PCI-6036E. i want to select a port by writing to digital port or line and then wait for 20 micro sec after thar i have to aquire data from AI.my problem is waiting 20 microseconds how i can achieve this?E-mail id:[email protected]

Here is what I suggest. I'm assuming you will use the DIO-32HS for writing to the digital line. You could use that digital line as a trigger for a counter on the PCI-6036E. When the counter is triggered, it could generate a single pulse with a delay of 20 microseconds and that pulse could be used as a trigger for analog input on the PCI-6036E.
There are LabVIEW shipping examples that will illustrate how to setup triggered counter and analog input applications. I hope this helps.
Regards,
Todd D.
Applications Engineer
National Instruments

COMMIT WORK AND WAIT USE

Hi Friends,
what is mean by COMMIT WORK AND WAIT.
when we use ths syntax...??
situation pls.
regards,
venu.

Hi,
To apply the changes made to the runtime objects of persistent classes to the actual persistent objects in the database, execute the COMMIT WORK statement. (Alternatively, use COMMIT WORK AND WAIT or SET UPDATE TASK LOCAL). Unless you are executing an object-oriented transaction from within the Transaction Service, you must include the COMMIT WORK statement explicitly in the program. Otherwise, it is encapsulated in the Transaction Service. (If you explicitly include the COMMIT WORK statement as described here, the t op-level transaction runs in compatibility mode).
The function of the COMMIT WORK statement is extended when you use it in conjunction with Object Services. Before COMMIT WORK closes the SAP LUW and triggers an update, it calls internal methods of the Persistence Service. These methods bundle the changes made to managed objects of the Persistence Service and pass them to a special update function module using CALL FUNCTION ... IN UPDATE TASK. Thus the Persistence Service works with traditional update methods. The update module is usually registered after any update modules that have already been registered. The update is then triggered and the update task executes the update module in the order in which they were registered.
After the system executes the COMMIT WORK statement, it sets the attributes of each persistent object in the ABAP program to initial. (That is, it calls the IF_OS_STATE~INVALIDATE method).
Local Update
If you want to change managed objects directly, rather than using the update module, you must change the update mode of the implicitly used Transaction Service. That is, the following statements must be executed before the COMMIT WORK statement:
DATA TM type ref to IF_OS_TRANSACTION_MANAGER.
DATA T type ref to IF_OS_TRANSACTION.
TM = CL_OS_SYSTEM=>GET_TRANSACTION_MANAGER( ).
T = TM->GET_CURRENT_TRANSACTION( ).
T->SET_MODE_UPDATE( OSCON_DMODE_DIRECT ).
COMMIT WORK.
To ensure database consistency, the local update is activated internally using SET UPDATE TASK LOCAL. In such cases, the system raises an exception if there are already update modules registered in the update task. You can only register additional classical update modules after setting the mode. They will then also be updated locally.
COMMIT
Basic form
COMMIT WORK.
Addition
... AND WAIT
Effect
Executes a database commit and thus closes a logical processing unit or Logical Unit of Work ( LUW ) (see also Transaction processing ). This means that
all database changes are made irrevocable and cannot be reversed with ROLLBACK WORK and
all database locks are released.
COMMIT WORK also
calls the subroutines specified by PERFORM ... ON COMMIT ,
executes asynchronously any update requests (see CALL FUNCTION ... IN UPDATE TASK ) specified in these subroutines or started just before,
processes the function modules specified in CALL FUNCTION ... IN BACKGROUND TASK ,
cancels all existing locks (see SAP locking concept ) if no update requests exist,
closes all open database cursors (see OPEN CURSOR ) and
resets the time slice counter to 0.
COMMIT WORK belongs to the Open SQL command set.
Return code value
The SY-SUBRC is set to 0.
Notes
All subroutines called with PERFORM ... ON COMMIT are processed in the LUW concluded by the COMMIT WORK command. All V1 update requests specified in CALL FUNCTION ... IN UPDATE TASK are also executed in one LUW . When all V1 update requests have been successfully concluded, the V2 update requests ("update with start delayed") are processed, each in one LUW . Parallel to this, the function modules specified in CALL FUNCTION ... IN BACKGROUND TASK are each executed in one LUW per destination.
COMMIT WORK commands processed within CALL DIALOG processing
- execute a database commit (see above),
- close all open database cursors,
- reset the time slice counter and
- call the function modules specified by CALL FUNCTION IN
BACKGROUND TASK in the CALL DIALOG processing.
However, subroutines and function modules called with PERFORM ... ON COMMIT or CALL FUNCTION ... IN UPDATE TASK in the CALL DIALOG processing are not executed in the calling transaction until a COMMIT WORK occurs.
Since COMMIT WORK closes all open database cursors, any attempt to continue a SELECT loop after a COMMIT WORK results in a runtime error. For the same reason, a FETCH after a COMMIT WORK on the now closed cursors also produces a runtime error. You must therefore ensure that any open cursors are no longer used after the COMMIT WORK .
With batch input and CALL TRANSACTION ... USING , COMMIT WORK successfully concludes the processing.
Addition
... AND WAIT
Effect
The addition ... AND WAIT makes the program wait until the type V1 updates have been completed.
The return code value is set as follows:
SY-SUBRC = 0 The update was successfully performed.
SY-SUBRC <> 0 The update could not be successfully performed.
Note
Runtime errors
COMMIT_IN_PERFORM_ON_COMMIT : COMMIT WORK is not allowed in a FORM callled with PERFORM ... ON COMMIT .
COMMIT_IN_POSTING : COMMIT WORK is not allowed in the update task.
if its useful reward points

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

BAPI_REQUISITION_CREATE Problem with COMMIT WORK AND WAIT

I ran into an issue and wanted to get your opinions about what might be happening.
This is my original code that did not work correctly using COMMIT WORK AND WAIT. After the select statement, lv_count was zero even though there were PR items that had been created. I'm thinking that the database update was not complete, but why would that be?
    CALL FUNCTION 'BAPI_REQUISITION_CREATE'
      IMPORTING
        number            = lv_number
      TABLES
        requisition_items = gt_reqitem
        return            = gt_return.
*   Purchase requisition has been created
    IF lv_number IS NOT INITIAL.
      COMMIT WORK AND WAIT.
*     Get number of items in PR
      SELECT COUNT( DISTINCT bnfpo ) INTO lv_count
        FROM eban
        WHERE banfn = lv_number.
This is my corrected code that works. I removed the AND WAIT from the commit statement and added a separate wait statement. I now get the correct number of PR items that were created.
    CALL FUNCTION 'BAPI_REQUISITION_CREATE'
      IMPORTING
        number            = lv_number
      TABLES
        requisition_items = gt_reqitem
        return            = gt_return.
*   Purchase requisition has been created
    IF lv_number IS NOT INITIAL.
      COMMIT WORK.
      WAIT UP TO 1 SECONDS.
*     Get number of items in PR
      SELECT COUNT( DISTINCT bnfpo ) INTO lv_count
        FROM eban
        WHERE banfn = lv_number.
Any ideas?
Brenda

Brenda Bankert wrote:
Yes, I was able to see the message in RETURN and no, I am not calling the FM in a loop. My program calls it one time.
> Brenda
If you were able to see the message 'Purchase requisition number & created' it means that the macro macro_end is getting executed within which the COMMIT WORK statement is encapsulated.
I have quickly developed a dirty program to test the behaviour of 'SET UPDATE TASK LOCAL' and it seems to work as expected.
Everytime I executed the below program with 'SET UPDATE TASK LOCAL', I see the value of lv_count as 1000, however if I execute the below program with out the statement 'SET UPDATE TASK LOCAL' the value of count varies everytime, typically around 10 - 15, however the database is successfully updated with all the 1000 entries, this makes me believe that the 'SET UPDATE TASK LOCAL' statement will infact make the subsequent COMMIT synchronous.
REPORT zytest.
DATA:
ls_zytest    TYPE zytest,
ls_db_zytest TYPE zytest,
lv_numc04    TYPE numc4 VALUE 1001,
lv_count     TYPE i,
lv_index     TYPE i.
DO 1000 TIMES.
lv_index = sy-index.
CLEAR ls_zytest.
lv_numc04 = lv_numc04 + 1.
CONCATENATE 'KF00' lv_numc04 INTO ls_zytest-keyfield1.
CONCATENATE 'KF00' lv_numc04 INTO ls_zytest-keyfield2.
SET UPDATE TASK LOCAL.
CALL FUNCTION 'ZYTEST_BAPI'
    EXPORTING
      is_zytest = ls_zytest.
SELECT SINGLE * FROM zytest INTO ls_db_zytest WHERE keyfield1 = ls_zytest-keyfield1
                                                  AND keyfield2 = ls_zytest-keyfield2.
IF sy-subrc IS INITIAL.
    WRITE:/ lv_index, ls_db_zytest-keyfield1,ls_db_zytest-keyfield2.
    lv_count = lv_count + 1.
ENDIF.
ENDDO.
WRITE:/ lv_count.
FUNCTION zytest_bapi .
*"*"Local Interface:
*" IMPORTING
*"     REFERENCE(IS_ZYTEST) TYPE ZYTEST
DATA: transaction_id LIKE arfctid.
clear transaction_id.
macro_start.
CALL FUNCTION 'ZYTEST_UPDATE' IN UPDATE TASK
    EXPORTING
      is_zytest = is_zytest.
macro_end.
ENDFUNCTION.
FUNCTION ZYTEST_UPDATE.
*"*"Update Function Module:
*"*"Local Interface:
*" IMPORTING
*"     VALUE(IS_ZYTEST) TYPE ZYTEST
INSERT zytest from is_zytest.
ENDFUNCTION.
definition of the database table 'ZYTEST'
MANDT     MANDT
KEYFIELD1     CHAR20
KEYFIELD2     CHAR20
NONKEYFIELD     CHAR50
-Rajesh

Stateless Release mode and the Commit issue

What are the implications of setting all the application modules to Stateless Release mode rather than Stateful?
I’ve read the documentation about this, but I need hands on expert’s opinions
Specially for a Web Application that a lot of public users will use?
We have an issue of the way commit work, if we edit a page and then navigate without saving to another page and then save at this second page, the commit will save all changes that have been done in both pages, even of the two pages are bound to two different VOs and two different Application modules, it is really strange, it seems that I need to know that the user is leaving the page so I can rollback, I do not understand this default behavior of ADF/BC ..
Any work around? Any opinions?

Hi,
the behavior is correct as it commits all pending changes. The release mode tells ADF BC how the application module is released to the pool if no longer needed by the user session. If release mode is stateful then the state of the current AM is passivated so it can be recovered. This has nothing to do with the page to page navigation.
If you want to undo changes performed on a page when navigation off the page, you call refresh(Row.DB_ROW...) on the current row
Frank

I have an I phone 4s, have had it little over a month and the charger is no longer working. Now I have to return it at my inconvenience and wait for a replacement. I am very disappointed considering it is Apple. Has anybody else had this problem?

I have an i phone 4s, I have had it just over a month. The charger is not working and it has to be returned. Very disappointed considering it is Apple I expected better and have never had this problem with any other phone. Now I have the inconvenience of having to return it and waiting for a replacement and in the meantime I'm without a phone. Has this happened to anyone else?

Wow, life is certainly tough for you.
S***t happens. That's why there's a warranty.

Commit work and roll back with simple language and simple example

hi guru
commit work and roll back with simple language and simple example

Hi,
The statement COMMIT WORK completes the current SAP LUW and opens a new one, storing all change requests for the current SAP LUW in the process. In this case, COMMIT WORK performs the following actions:
It executes all subroutines registered using PERFORM ON COMMIT.
The sequence is based on the order of registration or according to the priority specified using the LEVEL addition. Execution of the following statements is not permitted in a subroutine of this type:
PERFORM ... ON COMMIT|ROLLBACK
COMMIT WORK
ROLLBACK WORK
The statement CALL FUNCTION ... IN UPDATE TASK can be executed.
ROLL BACK:
The statement ROLLBACK WORK closes the current SAP-LUW and opens a new one. In doing so, all change requests of the current SAP-LUW are canceled. To do this, ROLLBACK WORK carries out the following actions:
1) Executes all subprograms registered with PERFORM ON ROLLBACK.
2) Deletes all subprograms registered with PERFORM ON COMMIT.
3) Raises an internal exception in the Object Services that makes sure that the attributes of persistent objects are initialised.
4) Deletes all update function modules registered with CALL FUNCTION ...IN UPDATE TASK from the VBLOG database table and deletes all transactional remote Function Calls registered with CALL FUNCTION ... IN BACKGROUND TASK from database tables ARFCSSTATE and ARFCSDATA.
5) Removal of all SAP locks set in the current program in which the formal parameter _SCOPE of the lock function module was set to the value 2.
6) Triggers a database rollback, which also ends the current database-LUW.

Applescript to launch an application and wait till it exits

I have written the applescript to launch an application and wait till it exits and but it is not working. Here is the code for that
tell application "/Applications/Pages.app" to activate
tell application "/Applications/Pages.app"
repeat until it is not running
end repeat
end tell
But when I tried to close the app, the script is still running. I think the reason is , even though I closed the window, that process is still running. Can you please help me to solve this problem?

Trying to make this kind of thing work from the script editor is going to give you headaches. A better approach is to create a script application. Copy the following code into the Script Editor, and then save it as an application with the "Stay open after run handler" checkbox checked. Then run the resulting script application directly.
on run
tell application "Pages" to activate
-- add a longish delay to allow the application to start
delay 5
end run
on idle
if application "Pages" is not running then
-- the application has quit, so go to the 'on quit' handler
quit
end if
end idle
on quit
-- do whatever you want to do after the application has quit
-- allow the app to quit itself
continue quit
end quit

I made an in app purchase, it said purchase successful but it never showed up. I was charged for it too and so far I've reported a problem about 3 times and I waited a full day and still no response.Happened before but i got an email that time.HELP

Made an in app purchase and it never showed up. Reported it and waited a full day and no response. What do i do from here?

How long ago did you last contact Support, and how ? If it's been longer than 48 hours, and only tried one method of contact, then you could try the other :
- the 'report a problem' page : http://reportaproblem.apple.com
- contacting iTunes Support via this page : http://www.apple.com/support/itunes/contact/ - click on Contact iTunes Store Support on the right-hand side of the page, then Purchases, Billing & Redemption

Commit work and wait in release 700 and 701

Similar Messages

Maybe you are looking for