Function called IN BACKGROUND TASK goes to work process DIA, not BGD

I'm calling a function IN BACKGROUND TASK
In SM50, I see it running in a DIA work process.
I want it to run in a BGD work process.
Can this be done?  If so, how?  If not, why not?

Hi...
It looks like, it will always run in DIA process and not Background process...I am not sure that we can change the work process
Check the below link..
http://help.sap.com/saphelp_40b/helpdata/pt/69/c24f864ba111d189750000e8322d00/content.htm
What is written in the link is...
"Background updates (CALL FUNCTION IN BACKGROUND TASK) represent a variant of remote function call that is synchronous with the end of a transaction (COMMIT WORK). In background updating, an update is run in another dialog work process that may be in the same or in another application server and R/3 System. Because such updates run in their own LUWs, they may start only after all critical updates have been completed. Otherwise, it would not be possible to roll back background changes in the event of an error in another update component. "
IF you get the answer of whether we can change the work process then please let us know...

Similar Messages

  • Use of function called "in background task"

    Hi folks!
    In my company there are rumors that a function called "in background task" can be used to make sure that all database changes of previous statements are already persisted. This would mean that a function called "in background task" can be used to read data from database that has been written by the same report - in any case (update dispatching over several instances,...). Usually this won't be a good idea (we know well about SAPs update concepts and read everything about it on help.sap.com). Has anybody some experiences about this or is there even a guru, able to explain why it will always work (or not)? We don't have evidence that the database has finished writing for sure when the function starts - that's why I'm worried.
    Example:
    REPORT test.
    INSERT something to database.
    CALL FUNCTION function in background task.
    End of the report
    Will it always work (when testing, it does)?
    Any help will be appreciated!
    Greetings

    Hi,
    Logically it is correct. BACKGROUND TASK Triggers an asynchronous process. This FM is executed in multiple steps.
    In first step system save the data passed to FM interface to buffer. When ever program encounters Explicit/implicit commit, the source code of the FM is processed.
    Note: You can't get back the data from this FM call.
    Check the F1 help on call function statement. You will get much more details.
    Thanks,
    Vinod.

  • 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

  • How to capture errors when a Function module is called as BACKGROUND TASK

    How to capture errors when a Function module is called as BACKGROUND TASK?.Please advise.
    FUNCTION ZRPM_DELETE_PROJECT_DATA_API.
    ""Local interface:
    *"  IMPORTING
    *"     VALUE(IV_EXTERNAL_ID) TYPE  RPM_TV_EXTID OPTIONAL
    *"     VALUE(IV_PROJECT_GUID) TYPE  RPM_TV_GUID OPTIONAL
    *"     VALUE(FLAG) TYPE  BOOLEAN OPTIONAL
    *"  EXPORTING
    *"     VALUE(EV_RC) TYPE  I
    *"     VALUE(EV_MSG) TYPE  STRING
    *"     VALUE(ET_MSG) TYPE  RPM_TT_MESSAGES
      IF flag = cl_rpm_co=>sc_true.
        Call function 'RPM_DELETE_PROJECT_DATA' IN BACKGROUND TASK
          EXPORTING
            IV_EXTERNAL_ID  = IV_EXTERNAL_ID
            IV_PROJECT_GUID = IV_PROJECT_GUID
          IMPORTING
            EV_RC           = EV_RC
            EV_MSG          = EV_RC
            ET_MSG          = ET_MSG.
        COMMIT WORK.
      ELSE.
        CALL FUNCTION 'RPM_DELETE_PROJECT_DATA'
          EXPORTING
            IV_EXTERNAL_ID  = IV_EXTERNAL_ID
            IV_PROJECT_GUID = IV_PROJECT_GUID
          IMPORTING
            EV_RC           = EV_RC
            EV_MSG          = EV_MSG
            ET_MSG          = ET_MSG.
      ENDIF.
    ENDFUNCTION.
    In above code how to capture 'EV_RC' when FM is called as background task.

    Prakash,
    CALL FUNCTION IN BACKGROUND TASK allows no IMPORTING parameters, so that your code will produce a syntax error.
    The calling program can only handle errors of remote function calls (RFC) if these are either
    - synchronous RFC  (that is CALL FUNCTION ... DESTINATION ...) or
    - asynchronous RFC (that is CALL FUNCTION STARTING NEW TASK ... DESTINATION ...).
    Both synchronous and asynchronous RFC allow the capturing of errors by means of exceptions. But that is a different topic.

  • Difference between calling a function module in background task and update

    Hi experts,
    Can someone explain me the basic difference between calling a FM in  background and update tasks?
    Also what is the advantage of using backgroud RFCs over the above 2.
    Thanks in advance,
    reddy

    This is essentially a difference of synchronization with the main program calling this FM.
    For Update task, we specify explicitely that we want to update some rows in a database table. But Update task is essentially for waiting that all tasks to do before are done and updating database at the end. The main point is that MF called in Update task wait for a COMMIT WORK to be executed.
    On the other hand FM in background task are executed immediatly and are not specific to updating database table : it can be a function that would return some values or something else like that.
    If you want to see more about difference between background jobs / update jobs, you can also have a look at transaction SM51. Here you will see all the servers composing your SAP instance and what kind of task they can execute :
    - background jobs corresponds to BATCH
    - update tasks corresponds to UPDATE
    Those 2 kinds of tasks stands not necessarily on the same server...
    Best regards,
    Samuel

  • 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)?

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

  • 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

  • Function Module MASTER_IDOC_DISTRIBUTE to be called in background task?

    Hi,
    We are generating outbound Idocs in a report. In this report we are using Function Module Master_Idoc_Distribute. Now we have faced some performance issues and the basis consultant is asking us to:
    Call the function module using CALL FUNCTION Master_Idoc_Distribute IN BACKGROUND TASK.
    1) How will calling the FM Master_IDOC_Distribute in background task help improve the performance?
    2) By calling the function module in background task, will it have any impact on the sequencing of the idocs? If yes what is the way out, as the idoc sequence is very important.
    Thanks in advance,
    Mick

    1) How will calling the FM Master_IDOC_Distribute in background task help improve the performance?
    ->Calling the FM in background task will help in performance as it will be called in the background process mode like a tRFC.So it will not occupy any dialog process which are limited.
    2) By calling the function module in background task, will it have any impact on the sequencing of the idocs? If yes what is the way out, as the idoc sequence is very important.
    ->It will not have any impact on IDoc sequence.

  • FM call in background task

    Hi,
    I have called a function module in background task. Inside this FM I create application log and put in all the messages in the log which can be viewed using the transaction SLG1. But if the creation of the log fails I want to display the info to the user and exit the FM. I cannot display the info using the Message statement here. I tried to raise an exception, etc. from this FM so that I can process the exception in the calling FM and display a message. But this does not work as the execution of the calling FM and called FM in rfc proceeds simultaneosly. I know I can see the error using transaction sm58 but I am looking for an option wherein I can directly inform the user. Does someone have a suggestion how can proceed with this?
    Thanks.
    Best Regards,
    Pooja

    Hi
    There are two ways for you to handle,
    one manually setting up the job through SM36 which is better and convinient,
    secondly through program using FM's JOB_OPEN, SUBMIT, JOB_CLOSE.
    Find below steps in doing both:
    Procedure 1:
    1. Goto Trans -> SM36
    2. Define a job with the program and variant if any
    3. Click on start condition in application tool bar
    4. In the pop-up window, click on Date/Time
    5. Below you can see a check box "Periodic Job"
    6. Next click on Period Values
    7. Select "Other Period"
    8. Now give '15' for Minutes
    9. Save the job
    In SM37 u can check the status of the jobs that u have assigned to background...
    Here u mention the job name or the report name to check the status of the job...
    After mentioning the job name or program name u just execute it.. ( without any name also u can execute then it gives u all the jobs set by your user name..
    the status colud be released,active,finished etc..
    Procedure 2 via Program:
    Below is a sample code for the same. Note the ZTEMP2 is the program i am scheduling with 15mins frequency.
    DATA: P_JOBCNT LIKE TBTCJOB-JOBCOUNT,
          L_RELEASE(1) TYPE c.
       CALL FUNCTION 'JOB_OPEN'
         EXPORTING
           JOBNAME                = 'ZTEMP2'
        IMPORTING
          JOBCOUNT               = P_JOBCNT
        EXCEPTIONS
          CANT_CREATE_JOB        = 1
          INVALID_JOB_DATA       = 2
          JOBNAME_MISSING        = 3
          OTHERS                 = 4.
       IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
       ENDIF.
       SUBMIT ZTEMP2 VIA JOB 'ZTEMP2' NUMBER P_JOBCNT
              TO SAP-SPOOL WITHOUT SPOOL DYNPRO
              WITH DESTINATION = 'HPMISPRT'
              WITH IMMEDIATELY = SPACE
              WITH KEEP_IN_SPOOL = 'X' AND RETURN.
       CALL FUNCTION 'JOB_CLOSE'
         EXPORTING
           JOBCOUNT                          = P_JOBCNT
           JOBNAME                           = 'ZTEMP2'
           STRTIMMED                         = 'X'
           PRDMINS                          = 15
        IMPORTING
          JOB_WAS_RELEASED                  = L_RELEASE
        EXCEPTIONS
          CANT_START_IMMEDIATE              = 1
          INVALID_STARTDATE                 = 2
          JOBNAME_MISSING                   = 3
          JOB_CLOSE_FAILED                  = 4
          JOB_NOSTEPS                       = 5
          JOB_NOTEX                         = 6
          LOCK_FAILED                       = 7
          INVALID_TARGET                    = 8
          OTHERS                            = 9.
       IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
       ENDIF.
    Hope the above helps you.
    Alternately use CALL FUNCTION func IN BACKGROUND TASK
    Regards,
    Sree

  • 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

  • How to get transaction id of a function called in background

    Hi all,
    does someone know how to retrieve t-id of a function called in background (tRFC) client side? I found
    'ARFC_GET_RECEIVER_TID'
    'ARFC_GET_TID'
    but these works server side (function called knows its t-id .. caller no). Is there some similiar client side so that after calling function I can retrieve its transaction id ? I know it's not the same context, for explaining better, what I need it's something like fork() in C, where process father (the one that forks) receive as return value process id of process forked.
    SEARCHING ON FORUM I see that many people answered on question about transaction id with sy-tcode misunderstanding the question. This transaction id it's not the tcode. This is the char 32 unique transaction code
    thank you
    regards
    Gabriele

    You can have a look at function TRFC_RECEIVER_INFO
    [qRFC API for the Inbound Queue|http://help.sap.com/saphelp_nw04/helpdata/en/21/5c5f3ca0dd9770e10000000a114084/content.htm]

  • 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

  • "disp+work" process in not getting started after kernel upgradation

    Hello Experts,
    Good day…..,
    I am new to SAP. I installed SAP ECC6 EHP4 with default kernel version 701 and it was working fine.
    I have upgraded kernel version from 701 to 741, but the “disp+work” process is not getting started after kernel upgrade.
    I have posted “dev_W0” log &
    “disp+work” command result obtained in CMD prompt of respective server.
    Please help me out in this. Thanks all in advance.
    “dev_w0” Log”
    trc file: "dev_w0", trc level: 1, release: "741"
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      all, MJ
    M sysno      55
    M sid        TNG
    M systemid   562 (PC with Windows NT)
    M relno      7410
    M patchlevel 0
    M patchno    42
    M intno      20020600
    M make multithreaded, Unicode, 64 bit, optimized
    M profile D:\usr\sap\TNG\SYS\profile\TNG_DVEBMGS55_ABTHMSSB01
    M pid        2392
    M
    M 
    M Wed Jul 23 02:04:35 2014
    M  kernel runs with dp version 208000(ext=117000) (@(#) DPLIB-INT-VERSION-208000-UC)
    M  length of sys_adm_ext is 500 bytes
    M  ***LOG Q0Q=> tskh_init, WPStart (Workp. 0 2392) [dpInit.c 731]
    M  DpCommonParamInit: rdisp/core_file_size = default --> no change
    I  MtxInit: 30000 0 0
    M 
    M Wed Jul 23 02:04:36 2014
    M  DpIPCInit2: read dp-profile-values from sys_adm_ext
    M  DpShMCreate: alloate/attach shared memory (mode=ATTACH)
    M  DpShMCreate: sizeof(wp_adm)                         24288    (1104)
    M  DpShMCreate: sizeof(tm_adm)                          51472080             (256080)
    M  DpShMCreate: sizeof(ca_adm)                           432000  (72)
    M  DpCommTableSize: max/headSize/ftSize/tableSize=500/16/7464064/7583152
    M  DpShMCreate: sizeof(comm_adm)                   7583152                (14904)
    M  DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    M  DpShMCreate: sizeof(slock_adm)                      0              (296)
    M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    M  DpShMCreate: sizeof(file_adm)                         0              (80)
    M  DpSockTableSize: max/headSize/ftSize/tableSize=500/16/520064/520080
    M  DpShMCreate: sizeof(sock_adm)                       520080  (1016)
    M  DpShMCreate: sizeof(vmc_adm)                       0              (3208)
    M  DpShMCreate: sizeof(wall_adm)                        (ft=41664/fi=67472/hd=64/rec=192)
    M  DpShMCreate: sizeof(amc_rec_adm)                              (ft=86464/fi=67472/hd=64/rec=416)
    M  DpShMCreate: sizeof(websocket_adm)                         (ft=28864/hd=64/rec=272)
    M  DpShMCreate: sizeof(gw_adm)          64
    M  DpShMCreate: sizeof(j2ee_adm)       3936
    M  DpShMCreate: SHM_DP_ADM_KEY                  (addr: 00000000103D0050, size: 60433936
    M  DpShMCreate: allocated sys_adm at 00000000103D0250
    M  DpShMCreate: allocated wp_adm_list at 00000000103E20F0
    M  DpShMCreate: allocated wp_adm at 00000000103E2410
    M  DpShMCreate: allocated tm_adm_list at 00000000103E84F0
    M  DpShMCreate: allocated tm_adm at 00000000103E8730
    M  DpShMCreate: allocated ca_adm at 00000000134FF000
    M  DpShMCreate: allocated comm_adm at 0000000013568980
    M  DpShMCreate: system runs without slock table
    M  DpShMCreate: allocated sock_adm at  0000000013CA4130
    M  DpShMCreate: allocated vmc_adm_list at 0000000013D232C0
    M  DpShMCreate: system runs without VMC
    M  DpShMCreate: allocated gw_adm at 0000000013D23560
    M  DpShMCreate: allocated j2ee_adm at 0000000013D237A0
    M  DpShMCreate: allocated ca_info at 0000000013D24900
    M  DpShMCreate: allocated wall_adm (ft) at 0000000013D24B40
    M  DpShMCreate: allocated wall_adm (fi) at 0000000013D2F000
    M  DpShMCreate: allocated wall_adm (head) at 0000000013D3F990
    M  DpShMCreate: allocated amc_rec_adm (ft) at 0000000013D3FBD0
    M  DpShMCreate: allocated amc_rec_adm (fi) at 0000000013D54F90
    M  DpShMCreate: allocated amc_rec_adm (head) at 0000000013D65920
    M  DpShMCreate: allocated websocket_adm (ft) at 0000000013D65B60
    M  DpShMCreate: allocated websocket_adm (head) at 0000000013D6CE20
    M  DpShMCreate: initialized 21 eyes
    M  DpCommAttachTable: attached comm table (header=0000000013568980/ft=0000000013568990/fi=0000000013C86E10)
    M  DpSockAttachTable: attached sock table (header=0000000013CA4130/ft=0000000013CA4140)
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  <ES> EsILock: use Semphore 33 for locking
    X  Using implementation view
    X  <EsNT> Using memory model view.
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.
    X 
    X Wed Jul 23 02:04:37 2014
    X  mm.dump: set maximum dump mem to 96 MB
    M  ThStart: taskhandler started
    M  ThInit: initializing DIA work process W0
    M 
    M Wed Jul 23 02:04:44 2014
    M  ThInit: running on host ABTHMSSB01
    I  MtxInit: 0 0 0
    M 
    M Wed Jul 23 02:04:45 2014
    M  calling db_connect ...
    B  Loading DB library 'D:\usr\sap\TNG\DVEBMGS55\exe\dboraslib.dll' ...
    B  Library 'D:\usr\sap\TNG\DVEBMGS55\exe\dboraslib.dll' loaded
    B  Version of 'D:\usr\sap\TNG\DVEBMGS55\exe\dboraslib.dll' is "741.10", patchlevel (0.42)
    C  Prepending D:\usr\sap\TNG\DVEBMGS55\exe to Path.
    C  Register application info.
    C 
    C Wed Jul 23 02:04:47 2014
    C  Oracle client version: 10.2.0.4.0, (dbsl 741 040714, UNICODE[2])
    C  Detailed Oracle client (patch) info not available.
    C  *** ERROR => Connect via SAPUSER not supported for kernel >= 740.
    [dbsloci.c    2406]
    C     Only Secure Connect method possible.
    M  ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 76]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c   2281]
    M Wed Jul 23 02:04:48 2014
    M 
    M  Info for wp 0
    M 
    M    pid = 2392
    M    severity = 0
    M    status = 0
    M    stat = WP_NEW
    M    waiting_for = NO_WAITING
    M    workerType = DP_WORKER_DIAWP
    M    act_cs_count = 0
    M    csTrack = 0
    M    csTrackRwExcl = 0
    M    csTrackRwShrd = 0
    M mode_cleaned_counter = 0
    M    control_flag = 0
    M    report = > <
    M    action = 0
    M    tab_name = >                              <
    M 
    M  ThIErrHandle: no current incoming request
    M 
    M 
    M *****************************************************************************
    M  *
    M  *  LOCATION SAP-Server ABTHMSSB01_TNG_55 on host ABTHMSSB01 (wp 0)
    M  *  ERROR ThInit: db_connect
    M  *
    M  *  TIME Wed Jul 23 02:04:48 2014
    M  *  RELEASE 741
    M  *  COMPONENT Taskhandler
    M  *  VERSION 1
    M  *  RC 16797709
    M  *  MODULE D:/depot/bas/741_REL/src/krn/si/th/thxxhead.c
    M  *  LINE 2470
    M  *  COUNTER 1
    M  *
    M  *****************************************************************************
    M 
    M  PfRejectStatistic: clear statistic record
    M  PfClearAllRec: clear statistic area
    M  PfClearAllRec: statRecordAction = STAT_RECORD_ACTION_REJECT
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hooks for event BEFORE_DUMP
    M  ThIErrHandle: entering ThSetStatError
    M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
    M  call ThrShutDown (1)...
    M  ***LOG Q02=> wp_halt, WPStop (Workp. 0 2392) [dpnttool.c 335]
    “Desp+Work” Command result:
    C:\Users\tngadm>disp+work
    disp+work information
    kernel release 741
    kernel make variant 741_REL
    compiled on NT 6.0 6002 x86 MS VC++ 16.00 for NTAMD64
    compiled for                  64 BIT
    compilation mode UNICODE
    compile time Jul  9 2014 16:39:46
    update level 0
    patch number 42
    source id 0.042
    RKS compatibility level 0
    supported environment
    database (SAP, table SVERS) 700
    710
    701
    702
    703
                                  711
    720
    730
    731
    732
    738
    740
    operating system
    Windows NT 5.1
    Windows NT 5.2
    Windows NT 6.0
    Windows NT 6.1
    Windows NT 6.2
    Windows NT 6.3
    C:\Users\tng

    C  *** ERROR => Connect via SAPUSER not supported for kernel >= 740.
    [dbsloci.c    2406]
    C     Only Secure Connect method possible.
    For this issue you need to set up SSFS.
    1639578 - SSFS as password storage for primary database connect
    I am new to SAP. I installed SAP ECC6 EHP4 with default kernel version 701 and it was working fine.
    I have upgraded kernel version from 701 to 741
    Are you sure kernel 741 is compatible with an EHP 4 system ?
    Read this SAP note
    1969546 - Release Roadmap Kernel 740
    Regards
    RB

  • Call function IN BACKGROUND TASK don't work

    Hello,
    I've a interface RFC to JDBC asyncronous.
    When i call function in R3 (IN BACKGROUND TASK), sy-subrc = 0, however i don't see any message in SXMB_MONI and runtime workbench.
    The CC sender (for RFC) is OK,
    what happen?
    thanks very much

    Have this code after your call function:
    CALL FUNCTION 'START_OF_BACKGROUNDTASK'
         EXPORTING
              STARTDATE = SY-DATUM
              STARTTIME = TIME
         EXCEPTIONS
              OTHERS    = 1.
    IF SY-SUBRC = 1.
      EXIT.
    ENDIF.
    COMMIT WORK.
    Also, if you want to call your RFC function module in async mode, you can try
    Call function '<fm name>' in update task....
    Regards,
    Ravi Kanth Talagana

Maybe you are looking for