Calling Function Module in Update Task

Hello Experts,
Can anyone let me know about
Calling Function Module in Update Task.
Why do we use this " In Update Task " ??
How do we Use ??
What is the Use... ??
Kindly let me know....
Thanks and Regards
Pramod

hi,
Why do we use this " In Update Task " ??
The main update technique for bundling database changes in a single database LUW is to use CALL FUNCTION... IN UPDATE TASK.
How do we Use ??
A typical R/3 installation contains dialog work processes and at least one update work process. The update work processes are responsible for updating the database. When an ABAP program reaches a COMMIT WORK statement, any function modules from CALL FUNCTION... IN UPDATE TASK statements are released for processing in an update work process. The dialog process does not wait for the update to finish. This kind of update is called asynchronous update.
What is the Use... ??
Asynchronous update is useful when response time from the transaction is critical, and the database updates themselves are so complex that they justify the extra system load
Real time scenario.
Suppose a user wants to change an entry in a database table, or add a new one. He or she enters the necessary data, and then starts the update process by choosing Save. This starts the following procedure in the ABAP program:
Firstly, the program locks the database entry against other users, using the enqueue work process (or the message server in the case of a distributed system). This generates an entry in the lock table. The user is informed whether the update was successful, or whether the lock could not be set because of other users.
If the lock is set, the program reads the entry that is to be changed and modifies it. If the user has created a new entry, the program checks whether a record with the same key values already exists.
In the current dialog work process, the program calls a function module using CALL FUNCTION... IN UPDATE TASK, and this writes the change details as an entry in table VBLOG.
When the program is finished (maybe after further dialog steps), a COMMIT WORK statement starts the final part of the SAP LUW. The work process that is processing the current dialog step starts an update work process.
Based on the information passed to it from the dialog work process, the update work process reads the log entries belonging to the SAP LUW from table VBLOG.
The update work process passes this data to the database for updating, and analyzes the return message from the database. If the update was successful, the update work process triggers a database commit after the last database change and deletes the log entries from table VBLOG.
If an error occurred, the update work process triggers a database rollback, leaves the log entries in table VBLOG, flags them as containing errors, and sends a SAPoffice message to the user, who should then inform the system administrator.
The corresponding entries in the lock table are reset by the update work process.
Hope this is helpful, Do reward.

Similar Messages

Call function module in update task

Hi
I am using the follwoing logic in my prog
CALL FUNCTION 'Z_Update _Task'    In update task
EXPORTING
    t_vbak        = t_vbak.
But the program goes to dump at call function
Please let me know if the syntax i am using is correct.
Edited by: kittu reddy on Feb 28, 2008 5:29 AM

It might be the type conflict . Please check once .
Here am giving some information abt UPDATE TASK.
Why do we use this " In Update Task " ??
The main update technique for bundling database changes in a single
database LUW is to use CALL FUNCTION... IN UPDATE TASK.
How do we Use ??
A typical R/3 installation contains dialog work processes and at least one update work process. The update work processes are responsible for updating the database. When an ABAP program reaches a COMMIT WORK statement, any function modules from CALL FUNCTION... IN UPDATE TASK statements are released for processing in an update work process. The dialog process does not wait for the update to finish. This kind of update is called asynchronous update.
What is the Use... ??
Asynchronous update is useful when response time from the transaction is critical, and the database updates themselves are so complex that they justify the extra system load
Thanks
Jagadeesh

Call function module in backgrouns task and in update task

Hi Gurus,Pls crear me on the " Call function module in backgrouns task and in update task".
how it works and waht is the link with LUW releated to these .
also heard that commit work statement aslo linked with this.
Pls clarfiy me with expalnation of code.

Hi sridhar,
the explanation already given is correct and good. Small add-on:
All functions called during one LUW with addition IN UPDATE TASK are stored together with their actual parameters in a temporary memory area. The moment a COMMIT WORK is issued, the functions are released to be executed by a so-called update task which is running in the background. This explains why functions called in update task never return anything, no SY-SUBRC and no export or table parameters If a function called in update task raises an exception or runs into an error the calling user will get an express message informing about this. Also, all database updates done by this update process are rolled back to keep consistency.
This proceeding helps to keep database tables consistent and allows the user to keep on doing his work before all database updates are complete. You may have seen messages like "material will be changed" after saving. If you open the same material immediately, you'll get a message "object locked by...<yourself>". This means the update task is still running.
Regards,
Clemens

Function module with UPDATE TASK

All,
Have a look at the below code. While debugging the control is not going inside the function module called using call function ...... in update task statement.
I believe the function module is not executed immediately, but is scheduled for execution in a special work process (update work process). For this purpose, the name of the function module including the passed actual parameters is stored as a log record in the database table VBLOG. If the statement is executed during the update task, the addition IN UPDATE TASK is ignored.
The actual execution is triggered by the statement COMMIT WORK which is not happening in this case. The formal parameters of the function module receive the values of the actual parameters from table VBLOG. How can I read the entries in VBLOG? Why the function module is not executed? Please suggest.
PERFORM bte_publish ON COMMIT LEVEL 9.
* syncron update
 COMMIT WORK AND WAIT.
* Publish business transaction events. The function module have
* to call as last update module!
FORM bte_publish.
IF NOT gvt_nodes IS INITIAL.
 CALL FUNCTION 'CUSTOMER_HIERARCHY_THROW_BTE' IN UPDATE TASK
 EXPORTING
 ffi_valid_on = knvh-datab
 fti_event_list = gvt_nodes
 fti_event_listx = gvt_nodesx.
ENDIF.
ENDFORM. " BTE_PUBLISH
Thanks,

Right Naren. But I need to check inside the update function module, whether it is calling the BTE function module I had configured and the code which I had put in it. Any ideas?
The COMMIT WORK is returning 4 and hence I believe it is not popping up another debuggin session in which the update FM runs.
Thanks,
Message was edited by: Somen

How to debug function module in update task ?

Hi ,
          i have following code :
CALL FUNCTION 'ZSD_t_UPDATE' IN UPDATE TASK
             TABLES
                              it_xvbkd = xvbkd.
Inside this function module i have some code to debug . How can i debug it ?
I put the breakpoint in it but its not working .
It is triggered on save of a tcode .
Thanks and Regards .

My home-grown method:
Set your breakpoint in the FM.
In your transaction, just before you press save, enter hobble mode in your command box with '/h'.
press save.
In your first debug screen, toggle settings>system debugging ON (NetWeaver Drop-down menu) or see previous notes for earlier WebAS versions.
Select continue (F8).
The program should then stop at your break-point in the FM.

Function modules in Update task

Hi Folks,
What is the difference between
1.If a function module contains in attributes 'Update mode ' and run( without 'update task - keyword).
2.call function ' fun2' in update task.
In this case, do we need to set the attributes must be 'Update task'?
Please help me.
Thanks in advance
Bhavani

From F1 Help...

This statement registers the update function module specified in update_function. update_function must be a character-type field, which during execution of the statement contains the name of an update function module in uppercase letters.
An update function module is a function module, for which in the Function Builder the property update module is marked. The registration of an update function module is an essential part of the update task.
The function module is not executed immediately, but is scheduled for execution in a special work process (update work process). For this purpose, the name of the function module including the passed actual parameters is stored as a log record in the database table VBLOG. If the statement is executed during the update task, the addition IN UPDATE TASK is ignored.

Regards,
Rich Heilman

Regarding function module in update task

Hi,
I have a function module(Zxxx) which is update type. i have called the fun.module in my program (Zyyy) using the syntax CALL FUNCTION ZXXX IN UPDATE TASK. As I suppose to debug the function module, I activated the update debugging in the debugging screen. But the controll still not goen into the function module. Please let me know solution.
Thanks & regards,
Suresh

>
sureshkumar vaniyasekar wrote:
> I activated the update debugging in the debugging screen. But the controll still not goen into the function module.
Hello Suresh,
What do you mean by not going?
If you are trying to do an F5 at the function call, the debugger is not "enter" into the FM. This is because at this point the function call is registered but the FM is not executed.
Update FM calls registered in a particular LUW are executed(in a special "UPD" workprocess) when there is a COMMIT encountered(may be explicit or implicit).
Did you read the online help on [Update Debugging|http://help.sap.com/saphelp_NW70EHP1core/helpdata/en/c6/617d0ce68c11d2b2ab080009b43351/content.htm] & [Breakpoint behaviour during Update Debugging|http://help.sap.com/saphelp_NW70EHP1core/helpdata/en/c6/617cbee68c11d2b2ab080009b43351/content.htm]?
BR,
Suhas

RE:CALL FUNCTION update_function IN UPDATE TASK

Hi,
Can anyone give a sample code or a simple scenario for CALL FUNCTION update_function IN UPDATE TASK .
Thanks in advance,
Alex.

Hello George
In a project dealing with material master data I had the problem that I needed to update standard as well as customer tables at the same time when the user pushed the SAVE button.
For the standard tables I used BAPI_MATERIAL_MAINTAINDATA_RT (retail material) and for the customer tables I created my own SAVE function modules.
How to ensure that either both (standard and custom) tables are updated or not simultaneously?
I created a special SAVE function module which called both the standard BAPI and my custom SAVE function modules.
This "wrapper" SAVE function module was then called IN UPDATE TASK.
This way I created a LUW (logic unit of work) which comprised both standard and custom tables. If everything was ok both types of tables were updated, otherwise the entire transaction was rolled back.
Further reading: [Special LUW Considerations|http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbae3435c111d1829f0000e829fbfe/content.htm]
Regards
Uwe

CALL FUNCTION update_function IN UPDATE TASK

hi
please give me an example for implementation of CALL FUNCTION update_function IN UPDATE TASK
plz help.. its urgent
useful solutions will be rewarded
note: dont give me link. i need simple straight forward example
thanks
ravish

Hi,
 When u want to call function which has to be executed in the Update work process.
1. You have to set the "Processing Type" to "Update Module" and select "Immediate Start" which makes the function to be processed using V1 update process(for critical updates)
function module parameters must be passed by using Pass by Value only.
Export parameters are not supported.
In the source code of the function
to perform a ROLLBACK in case of any error
Generate a message using type A(Abend)
2. Call the function from the program using
 CALL FUNCTION 'Z_FM' in update task
 EXPORTING
TABLES
COMMIT WORK .
hope this will help.
Reward if so.
Regards,
Varma

What is the use of CALL FUNCTION MODULE - AT BACKGROUND TASK?

Hi experts,
I found Call functional module in background task will make the FM run at the next commit work as some people said. So I have some questions:
1 if we use COMMIT WORK commend, the pending FM will be called? If there are several FMs called at background task, what is the sequence of them? How many conditions will trigger the running of these FMs?
2 Where can I find the log of this pending FMs? In SAP library, it says there are 2 tables. But I checked these tables and can only find the FM name and user of it. And I can not understand content of these tables. It seems one is for the main information of FM, and the other is for the data of the FM, maybe the parameters.
3 If I call a FM in this way, Can I canncel it before the next commit work in some way?
Finally, thanks for reading and help.

HI,
When the COMMIT WORK statement is executed, the function modules registered for the current SAP-LUW are started in the order in which they were registered. ROLLBACK WORK deletes all previous registrations for the current SAP-LUW.
If the specified destination is not available when COMMIT WORK is executed, an executable program called RSARFCSE is started in background processing. By default, this tries to start the function modules registered for a SAP-LUW in their destination every 15 minutes and up to 30 times. These parameters can be changed in the transaction SM59. If the destination does not become available within the defined time, it is recorded in the database table ARFCSDATA as the entry "CPICERR". The entry in the database table ARFCSSTATE is deleted after a standard period of eight days

Difference between Function module in Update task

Hi folks,
What is the difference between
1. A function module calling in 'update task'( if attributes not set for update mode).
2.A function module's attributes set to update mode, but while calling not specified 'Update task'.
Please clarify this doubt.
Thanks in advance.
Bhavani

CALL FUNCTION func IN UPDATE TASK.
Additions:
1. ... EXPORTING p1 = f1 ... pn = fn
2. ... TABLES p1 = itab1 ... pn = itabn
Effect
Flags the function module func for execution in the update task. It is not executed at once, but the data passed with EXPORTING or TABLES is placed in a database table and a subsequent COMMIT WORK then causes the function module to be executed by the update task. Update function modules must be flagged as such in the Function Builder
The return value is not set.
Addition 1
... EXPORTING p1 = f1 ... pn = fn
Effect
Values of fields and field strings specified under EXPORTING are passed from the calling program to the function module. In the function module, the formal parameters are defined as import parameters. In the interface definition, default values must be assigned to all import parameters of the update function module.
Addition 2
... TABLES p1 = itab1 ... pn = itabn
Effect
TABLES passes references to internal tables. All table parameters of the function module must have values.
Note
With update function modules, both import parameters and exceptions are ignored when the call is made.
Administration transaction
Related
COMMIT WORK, SET UPDATE TASK LOCAL
regards,
kartikey.

ABAP Dump when calling Function Module Starting New Task

Hi all. I have a tricky situation now, I am doing a POC on parallel processing.
I am getting an ABAP dump on the following Call Function line which is in class lcl_steer_114numc (See below for full program):
METHOD start.
 CALL FUNCTION 'Z_ZZCLS_STEER_114NUMC'
 STARTING NEW TASK me->id
 CALLING me->finish ON END OF TASK.
ENDMETHOD. "start
However I get the following ABAP dump:
Short text
 Statement "CALL FUNCTION .. DESTINATION/STARTING NEW TASK/IN BACKGROUND TASK"
The function module only contains a wait statement to simulate parallel processing. It is strange that it dumps here, because when I change the FM call to another call that has been triggered successfully from other classes, it still produces the same ABAP dump.
The background of the Proof Of Concept is to see if I can get an event to trigger the next process that depends on the outcome of the previous process. Parallel processes are run in the start methods by calling RFC.
<Garbled code removed>
Moderator Message: Please post relevant portions of the code only.
Edited by: Suhas Saha on Jul 17, 2011 1:17 PM

Well, the thing is I did manage to run 3 other Function Modules asynchronously succeesfully prior to that function call, with the same exact function call syntax. Further more, I have tried editing it with your suggestion but I get the exact same dump.
The complete function group can be downloaded here (slinkee file):
https://docs.google.com/leaf?id=0B3sua1Bw4XK4ZmFhNzcwMTgtYzQ0Mi00NzQ4LTg5YTMtNDNlNWUxYTM2NTg3&hl=en_US
The complete program can be downloaded here (slinkee file):
https://docs.google.com/leaf?id=0B3sua1Bw4XK4YWJmNjU3ODYtODRmMy00Nzg2LThkNTUtZjNkNDRhZGQ3MTUw&hl=en_US
The complete ST22 dump can be found here:
https://docs.google.com/leaf?id=0B3sua1Bw4XK4ZDU1YmFkZDAtOTU5MS00ZTgwLWFlZTktNWZhMDUxMzJlZWNl&hl=en_US
Basically I ST22 gives me the following:
Runtime Errors RPERF_ILLEGAL_STATEMENT
Date and Time 17.07.2011 05:29:54
|Short text |
| Statement "CALL FUNCTION .. DESTINATION/STARTING NEW TASK/IN BACKGROUND TASK" |
|What happened? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "Z_ZZB1_CLOSE_PERIOD_TEST2" had to be terminated |
| because it has |
| come across a statement that unfortunately cannot be executed. |
And it explains it here (but is not helpful / relevant at all) as I ran the program from SE38.
|Error analysis |
| There is probably an error in the program |
| "Z_ZZB1_CLOSE_PERIOD_TEST2". |
| The program was probably called in a conversion exit |
| or in a field exit. These are implemented by |
| function modules called CONVERSION_EXIT_xxxxx_INPUT/OUTPUT or |
| USER_EXIT_xxxxx_INPUT. |
| Conversion exits are triggered during screen field transports or |
| WRITE statements, field exits during field transports from the |
| screen to the ABAP/4 program. |
| In this connection, the following ABAP/4 statements are not allowed: |
| |
I hope you try to download the slinkee files and you will notice the call function I performed was no different than the other call function RFC calls that really are working.

Call function module in new task

I need to call a function module starting new task but the problem is that it has inporting parameters also. Please help me in doing this. Points will be rewarded.

Look at the ABAP keywords RECEIVE RESULTS FROM FUNCTION. This is where you can get the results from the CALL FUNCTION MODULE... NEW TASK...
It's all in the ABAP help for CALL FUNCTION MODULE.
matt

Function module In Update Task is called more than once

Hi experts!!
I had a requirement to Create a Customer ( i will call it B) when another Customer (A) is created (ON SAVE).
I used a Badi to implement the requirement, and inside my Badi i have 2 Function Calls in Update Task.
The first one to create Customer B and the second one to send Customer's B data to another System.
Even though the second function call is inside an IF-ENDIF condition ( so that only Customer's B data are sent) the function is called twice sending the same data. My guess is that since the First Function saves the Customer to the database, that is the reason why the second Function is called twice.
Is there any way i can control how many times a Function In Update Task is called????
Please help!!
Thank you in advance!!

Hi BreakPoint & thank you for your reply!!
I tried your suggestion but even if i fill the flag during the first call the function is called twice. Looks like during the second database commit the function is called with the correct conditions met but twice.
Also while debugging it looks like it is only called once. It s very strange!
Any other ideas???

Regarding Error in Function Module in Update Task

Hi All,
If a function module is called in Update Task and there is some error generated from it, it comes as an exit message unlike in a normal function module.
Is there any possible way to avoid such an exit message?
Thanks in advance.
Regards,
Garima

Hi,
The problem is I am updating Z tables in a function and also calling a function in Update task to update a different set of tables.
Now, if for some reason there is an error in Update Function module, then my requirement is that rather than throwing an Exit message (which it is presently doing) the errors coming from the function should be captured so that the user knows what was wrong with the data he entered.
Is there any work around to the above requirement? Either all the tables should be updated or none of them should be updated.
Regards,
Garima Thapar.

Calling Function Module in Update Task

Similar Messages

Maybe you are looking for