‎2007 Oct 04 7:59 AM
hi ,
can any one send me an example or any scenario where we use update task concept.
‎2007 Oct 04 8:05 AM
hi
good
go through this link
http://help.sap.com/saphelp_nw04/helpdata/en/23/edae617ba64e85bd4997f25c77eb1f/content.htm
thanks
mrutyun^
‎2007 Oct 04 8:00 AM
Hi,
Calling a FM in Update Task is one of the bundling techniques used in ABAP to avail functionality provided by SAP Update System. Here all database updates are processed at the end of the SAP LUW in contrast to normal FM call where the database updates are done and commited at the time of call (Database LUW). It is necessary to bundle all your database updates in an SAP LUW e.g. all database updates in a transaction (like VA01) should be bundled. Almost all standard SAP transactions use bundling techniques.
This technique separates the dialog process and update process. The dialog part of the transaction can span more than one screen(one dialog step) and can be processsed by more than one dialog work process. A work process is released when the dialog step changes (screen changes) and the work process sends a database commit (called Implicit Database LUW). So with each screen change there is a database commit and database remains in consistent state.
Now when using bundling technique, when a COMMIT WORK is encountered, system ends the dialog process with a dialog work porcess and starts the update process using an update work process.
The dialog step containing the COMMIT WORK is considerd as the last dialog step of the transaction and all the update function modules are processed now in the last dialog step by the update work process though they were called earlier during the earlier dialog steps.
It is necessary to create update FMs to take advantage of this technique. The update FM is created FM by setting the Update function radiobutton in the Attributes tab in SE37.
In a normal FM call, if there are database updates (UPDATE, INSERT, MODIFY, DELETE) than database is commited after the FM processing is over as the FM starts its own Database LUW and ends it too.
SET UPDATE TASK LOCAL is same as calling a transaction using CALL TRANSACTION in LOCAL mode. Here the database updates are handled by the same dialog work process that was handling the dialog process hence the name LOCAL. System doesn't try to find a separate work process. I have not used LOCAL mode so far and really don't have any idea about the usage requirements.
Thanks,
Reward If Helpful.
‎2007 Oct 04 8:05 AM
hi
good
go through this link
http://help.sap.com/saphelp_nw04/helpdata/en/23/edae617ba64e85bd4997f25c77eb1f/content.htm
thanks
mrutyun^