Lock inheritance with "CALL FUNCTION func IN BACKGROUND TASK"

I see that the "SAP Lock concept" documentation states that for locks obtained with _scope = '3', all UPDATE tasks (spawned via "CALL FUNCTION func IN UPDATE TASK" inherit the lock (which is released only once all such update tasks and the calling process have requested a DEQUEUE).
What should happen when instead, I use "CALL FUNCTION func IN BACKGROUND TASK" (for doing the update in a queue)? Are the locks inherited here as well?
Cheers!

Hopefully not, as a background task may be executed late. While update tasks are to be executed quickly (if not, administrators should review the system configuration, like increasing the number of UPD workprocesses).
Solution: In the background task, redo the locks, as if it was a background job.

Similar Messages

CALL FUNCTION func STARTING NEW TASK task

hi,
i developed rfc to extract data and send to xi
as my interface is Async
as per soem documents it was mentioned the syntax
CALL FUNCTION func STARTING NEW TASK task
wat is the task ? in the syntax
and how do i use it
jeff

Hi suresh,
this is the code of RFC. if i execute without RFCDESTINATION it executes successfully. when i use RFC DESTINATION it shows error
call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException
i created RFC destination using TCP/IP and registered program. same parameters i am mentioning in XI.
FUNCTION z_bank_reconciliation.
""Local interface:
*" IMPORTING
*"     VALUE(COMP_CODE) TYPE BUKRS
*"     VALUE(HOUSE_BANK) TYPE HBKID
*"     VALUE(ACCOUNT_ID) TYPE HKTID
*" TABLES
*"      CHQDETAILS STRUCTURE ZPAYR
DATA: itab LIKE payr OCCURS 0 WITH HEADER LINE.
DATA: jtab LIKE payr OCCURS 0 WITH HEADER LINE.
DATA: it_bank LIKE zbankrecon OCCURS 0 WITH HEADER LINE.
DATA: it_bank1 LIKE zpayr OCCURS 0 WITH HEADER LINE.
TYPES : BEGIN OF ty_bseg ,
             bukrs LIKE bseg-bukrs,
             hbkid LIKE bseg-hbkid,
             belnr LIKE bseg-belnr,
             zlsch LIKE bseg-zlsch,
             kostl LIKE bseg-kostl,
             hkont LIKE bseg-hkont,
             bzdat LIKE bseg-bzdat,
         END OF ty_bseg.
TYPES : BEGIN OF ty_t012 ,
              bukrs LIKE t012-bukrs,
              bankl LIKE t012-bankl,
              bankn LIKE t012k-bankn,
         END OF ty_t012.
TABLES : payr, t012, t012k, bseg.
DATA : itpayr LIKE zpayr OCCURS 0 WITH HEADER LINE,
         itt012 TYPE STANDARD TABLE OF ty_t012,
         itbseg TYPE STANDARD TABLE OF ty_bseg,
         wa_itt012 TYPE ty_t012,
         wa_itbseg TYPE ty_bseg,
         total TYPE n.
SELECT * FROM zbankrecon INTO TABLE it_bank
                   FOR ALL ENTRIES IN itab
                   WHERE chequeno EQ itab-chect.
SELECT abukrs abankl b~bankn
              INTO CORRESPONDING FIELDS OF TABLE
              itt012 FROM t012 AS a
      INNER JOIN t012k AS b ON bbukrs = abukrs AND b~hbkid =
house_bank AND b~hktid = account_id
            WHERE abukrs = comp_code AND ahbkid = house_bank.
DELETE ADJACENT DUPLICATES FROM itt012.
SELECT zbukr hbkid hktid vblnr gjahr zaldt checf chect znme1 rwbtr
waers zaldt zbnkl FROM payr INTO CORRESPONDING FIELDS OF TABLE itpayr
    WHERE ( zbukr = comp_code AND hbkid = house_bank ) AND hktid =
    account_id.
SELECT bukrs hbkid belnr zlsch kostl hkont bzdat FROM bseg INTO TABLE
itbseg
WHERE bukrs = comp_code AND hbkid = house_bank.
SORT itt012 BY bankl.
SORT itbseg BY belnr.
READ TABLE itt012 INTO wa_itt012 INDEX 1.
LOOP AT itpayr.
    read table itbseg into wa_itbseg with key bukrs = itpayr-zbukr
hbkid = itpayr-hbkid.
    if sy-subrc = 0.
      itpayr-kostl = wa_itbseg-kostl.
      itpayr-hkont = wa_itbseg-hkont.
     itpayr-bldat = wa_itbseg-bzdat.
      itpayr-zlsch = wa_itbseg-zlsch.
    endif.
    itpayr-zbnkl = wa_itt012-bankl.
    itpayr-zbnkn = wa_itt012-bankn.
    MODIFY itpayr.
    APPEND itpayr TO chqdetails.
ENDLOOP.
LOOP AT chqdetails.
    READ TABLE it_bank WITH KEY chequeno = chqdetails-chect.
    IF sy-subrc NE 0.
      MOVE chqdetails TO it_bank1.
      APPEND it_bank1.
      CLEAR it_bank1.
    ENDIF.
ENDLOOP.
REFRESH chqdetails.
chqdetails[] = it_bank1[].
LOOP AT it_bank1.
    MOVE : it_bank1-chect TO zbankrecon-chequeno,
    sy-datum TO zbankrecon-check_date,
    sy-uzeit TO zbankrecon-check_time.
    INSERT zbankrecon.
    CLEAR zbankrecon.
ENDLOOP.
ENDFUNCTION.

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

Calling function module in background task

Hello,
There is one function module which is called in background task. Is there any chance that background task is not created and function module is not executed. That function module is supposed to send some outbound message. The FM is called in one user exit. I don't have any idea as why it is called as background task. The probem is that this message is not getting send sometimes.(sometimes it gets send ). Because of this I am not able to make any conclusion.
Please respond if anyone has come across such scenario before.
Thanks in advance,
Minal

Check the below link...it might be helpfull
It should be executed....check it with different data as to what might fail
http://help.sap.com/saphelp_nw04/helpdata/EN/8f/53b67ad30be445b0ccc968d69bc6ff/content.htm
http://help.sap.com/abapdocu/en/ABAPCALL_FUNCTION_BACKGROUND_TASK.htm

Calling function modules in background task

Hi All,
I am creating a notification in the background and linking it to an order. This I am doing inside a function module which is called in background task as a separate unit. I should change the user status of this newly created notification. This I am doing in another FM called as a separate unit. Now my requirement is that, I need to perform the status change only after the new notification is committed to the database. I would like to know if i can provide some time lag between the 2 FM execution. Can anyone tell me how much time will be consumed to commit the data to the database tables irrespective of the length of the data. Say for example, if i have hundreds of notifications within the object list tab of an order, I want to know what is the maximum time it will take to commit this to the database table so that I can put a wait conditionat the stat of the second FM call.
Thanks

Ok thanks. But let me tell you 1 thing, actually I am calling these 2 FMs within an enhancement section just before another FM CO_ZV_ORDER_POST which is actually doing a commit work. So is it OK if I call the 1st FM in background task and the second FM in update task in the same place as I am calling the FMs now(i.e., before CO_ZV_ORDER_POST)?

Function module in background task

Hi,
I have a user-exit, that must modify a value. But this value have a lock entry (it's my own transaction that set this lock-entry). So I would like to call a function in background task to modify the value when the lock entry disapear.
But ...
I don't see anything append in the SM50.
If I call the function not in background, I could debug the function.
When I set background debugging nothing append.
I have set the RFC option in the function module.
CALL FUNCTION 'ZCALL_MB26_CONFIRMATION_OT'
IN BACKGROUND TASK AS SEPARATE UNIT DESTINATION 'NONE'
Rgd
Frédéric

Hello Fred,
This is a sample code to wait for unlock (but if a user is in modification it can be endless).
data : w_garg like seqg3-garg.
data : t_enq like seqg3 occurs 0.
concatenate sy-mandt tplnr into w_garg.
do.
    refresh t_enq.
    call function 'ENQUEUE_READ'
     exporting
       gclient                     = sy-mandt
       gname                       = 'IFLOT'
       garg                        = w_garg
GUNAME                      = SY-UNAME
LOCAL                       = ' '
IMPORTING
NUMBER                      =
SUBRC                       =
      tables
        enq                         = t_enq
EXCEPTIONS
COMMUNICATION_FAILURE       = 1
SYSTEM_FAILURE              = 2
OTHERS                      = 3
    if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    endif.
    if t_enq[] is initial.
      exit.
    endif.
enddo.
David

Problem in Call function .. starting new task

Hi,
I want to execute a dialog program in background. I am trying to use call function starting new task.
I am facing some syntax issue. Can any one guide me how to use call function starting new task. The function module is RFC FM. Do we need to define task some where before use please guide.
Thanks in advance. A sample program will be gr8.

Hi,
Incase you want to call a RFC FM in background you can call ity like this.
     call function 'Y_L_TO_CREATE_HUPAST' in background task
             exporting
          venum   = y_v_venum
          backg   = 'X'
           buser   = y_lv_uname
          langu   = sy-langu
          objky   = y_lv_objky
          printer = y_lv_printer.
Here Y_L_TO_CREATE_HUPAST is a RFC FM.
Regards,
Ankur Parab

Error in debugging tRFC Function module (in background task) in SM58

Hi,
I am trying to debug this statement:
CALL FUNCTION 'CRM_UPLOAD_TRIGGER'
IN BACKGROUND TASK
DESTINATION gv_smof_erpsh-rfcdest AS SEPARATE UNIT
I have followed these steps:
When you debug a program that calls function modules using the IN BACKGROUND TASK addition, they are processed in a background work process (additional internal session). If you set the In background task: Do not process option, the system collects the function calls, but does not start the background work process. The Debugger assigns a transaction ID, which identifies the background work process uniquely. You can now start the Debugger for the background work process using transaction SM58. You can select the function module concerned here, and then execute it via the Edit menu.
but still i cant find any entry in SM58.
Can anybody help me out in this?
Thanks a lot.
Best Regards,
Shweta

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

Incorrect parameter with CALL FUNCTION - WE19

hi! All
while creating IDOC through WE19 - Start Inbound it creates IDOC with Status - 64."IDoc ready to be transferred to application" "No filters , No conversion , No version change ."
Incorrect parameter with CALL FUNCTION
This parameter was "MASSAVEINFOS".
but i have Included this parameter in my Function module.
INPUT_METHOD TYPE INPUTMETHD
MASS_PROCESSING TYPE MASS_PROC
NO_APPLICATION_LOG LIKE SY-DATAR
MASSAVEINFOS LIKE MASSSAVINF
whats the mistake i have done.
Regards
Kv

That will not be possible KV, as the call to the FM is not being made, as far as i see you have completed the needed settings.
As i do not have access to an SAP system, i suggest that you try below,
1) Go to WE19, enter the IDOC number and F8.
2) In this screen, click on Inbound function module.
3) In the field for inbound function module press F4, it should list your FM name here if all the necessary we42/82/57, BD51 and WE20 have been done correctly.
Another thing that you can try is, on WE19,
1) Idoc Number F8
2) /h - to start Debug
3) Now click on Standard inbound, in the debug mode press F5 once.
4) Now put a break point on all message statement
See where exactly the message of wrong FM is being thrown, it will most probably be after a select statement on one of the tables associated with WE42/82/57/BD51 etc. With this you will where you have missed out.
All the best !!!
Regards,
Chen
Edited by: Chen K V on Mar 18, 2010 8:55 AM

Call function module in backgrouns task and in update task

Hi Gurus,Pls crear me on the " <b>Call function module in backgrouns task and in update task</b>".
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

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.

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'BAPI_USER_CHANGE' starting new task 'TEST'

Hi All,
I have problem with starting new task statement, I am using one FM after that am using starting new task 'TEST'
statement but its not working in one system its working fine in other systems, Please help me who this works.
Thanks in Advance.
Eg: Call Function'BAPI_USER_CHANGE' starting new task 'TEST'
Regar

Thanks Lqueiroz ,
Now again i am getting a DUMP by saying ,
"An error occurred when executing a REMOTE FUNCTION CALL.
It was logged under the name "At least one entry could not be "
on the called page."
so what can be the reason for this
call function 'ZRFC_PER_DIEM' starting new task lc_taskid performing subr on end of task
        exporting
          h_guid      = it_header_guid_n
          request_obj = lt_requested_objects_n.
      wait up to '1' seconds.
      read table gt_scl into ls_scl index 1.
      p_transaction_per_diem = ls_scl-value.
      read table gt_scl into ls_scl index 2.
      transaction_currency_code = ls_scl-value.
form subr   using task_id type clike.
data: p_transaction_per_diem type char13,
        transaction_currency_code type char3.
receive results from function 'ZRFC_PER_DIEM'
                           tables
                            value = gt_scl.
So basically i am getting dumo when receive statenment is running , by giving above dump.
Regards
PG

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

Behaviour of CALL FUNCTION fname STARTING NEW TASK DESTINATION 'NONE'

As per ABAP help documentation, the statement CALL FUNCTION fname STARTING NEW TASK DESTINATION 'NONE' should create a new main session in same user session.The behaviour is wrong as per documentation.
But current behaviour:
The statement CALL FUNCTION fname STARTING NEW TASK DESTINATION 'NONE' is creating a new user session.
Any reason?

Hi Prakash,
I'd agree with Suhas, that you're reading the documentation wrong. Here's your quote:
As per ABAP help documentation, the statement CALL FUNCTION fname STARTING NEW TASK DESTINATION 'NONE' should create a new main session in current user session.
If you look at the help, you can see that it says:
When the destination NONE is used, a new main session is opened for the current user session.
Do you see the difference? Also, note that in this context main session basically means that we're talking about a new external session:
Each task ID defines a separate RFC connection with its own context, meaning that, in the case of repeated function module calls of the same task ID, the global data of the relevant function group can be accessed, if the connection still exists.
In dialog processing, note that the maximum number of six main sessions cannot be exceeded, else an error message is displayed.
If you're still in doubt, check out the online ABAP documentation for [CALL FUNCTION - STARTING NEW TASK|http://help.sap.com/abapdocu_70/en/ABAPCALL_FUNCTION_STARTING.htm]. So I'd say the documentation is in line with the actual behavior.
Cheers, harald

Lock inheritance with "CALL FUNCTION func IN BACKGROUND TASK"

Similar Messages

Maybe you are looking for