DYNPRO_SEND_IN_BACKGROUND dump when workflow executes a background task

Hi,
My project is currently in version 4.6. I have a custom version of the PO release workflow and in here I created an activity calling a Custom Task, which then calls a Custom Business Object Method and then calls a program (using Submit RSWUWFML2). Unfortunately everytime the workflow goes to the said activity it hits a dump -- DYNPRO_SEND_IN_BACKGROUND.
I've tried unchecking the flag "Advance with Dialog" inside the task but it didn't work. I know RSWUWFML2 most of the time should be scheduled in background but it just so happens that we have a certain scenario in which it should have a different body and subject. This is the reason why I opted to call it inside the workflow.
Do you have any idea what caused this? Thanks!

Hello Dan,
DYNPRO_SEND_IN_BACKGROUND is an exception which occurs when system tries to call screen in background. Calling screen in background is not possible.
Report RSWUWFML2 creates LIST at the end of this report which is nothing but a special type of screen. If you run this report as background task, definitely above exception will occur.
Schedule this report as job instead of using it in task.
Regards,
Sagar

Similar Messages

User WF_BATCH dumps with TIME_OUT for a background task

Hello,
Situation :
While executing a workflow with a task defined as background task, the workflow creates a dump in ST22 after around 40 minutes. dump is because of TIME_OUT exception. And the workflow stays in status InProcess forever.
Question:
In my opinion background tasks do not have a time limit because they are executed as backgound batch jobs with batch user WF_BATCH. Then why do I get a TIME_OUT error ?
Is my assumption that workflow background task are just handled like other background jobs (sm36) is wrong ?
More Details :
I have a workflow with a task defined as background task (Task -> Basic Data -> Execution -> Check box 'Background processing' selected).
This task calls a method defined as 'Synchronous' method.
This method calls a ABAP FM having a select statement which selects large volume of Data.
If I execute this FM in Dialog mode definately I get a TIME_OUT. I understand this.
But what I do not understand is , while executing in background I do not expect TIME_OUT error since background jobs do not have a time limit. They can even run for several days.
Please let me know in what cases does a background job throws a time_out exception.esp wrt workflow.
Thanks in Advance
Shivanand

Check this link.
http://mailman.mit.edu/pipermail/sap-wug/2003-April/008883.html
Thanks
Arghadip

Function module not working when used with 'In Background Task'

hi,
this is my code
call function 'Z_IBD_FILL_ZINETACT'
              in background task
              destination 'SAPD220125'
              tables
                  it_net1 = it_net1
                  it_net2 = it_net2
                  it_net3 = it_net3 .
when this code is executed i am not getting any data in my internal tables i.e it_net1, it_net2, and it_net3
but i changed this code see the below code
      call function 'Z_IBD_FILL_ZINETACT'
             in background task (THIS IS COMMENTED)
              destination 'SAPD220125'
              tables
                  it_net1 = it_net1
                  it_net2 = it_net2
                  it_net3 = it_net3 .
now i am getting data into my internal tables
can any one tell me what can be the problem and how to solve it in my case
its very urgent

Hi,
Pls. go through the docu..
CALL FUNCTION
Variant 5
CALL FUNCTION func IN BACKGROUND TASK.
Additions:
1. ... AS SEPARATE UNIT
2. ... DESTINATION dest
3. ... EXPORTING p1 = f1    ... pn = fn
4. ... TABLES     p1 = itab1 ... pn = itabn
Effect
Flags the function module func to be run asynchronously. It is not executed at once, but the data passed with EXPORTING or TABLES is placed in a database table and the next COMMIT WORK executes it in another work process.
Note
This variant applies only as of Release 3.0, so both the client system and the server system must be Release 3.0 or higher.
Note
qRFC with Outbound Queue
This is an extension of tRFC. The tRFC is serialized using queues, ensuring that the sequence of LUWs required by the application is observed when the calls are sent.
For further information about qRFC, refer to the Serialized RFC: qRFC With Outbound Queue section of the SAP Library.
Addition 1
... AS SEPARATE UNIT
Effect
Executes the function module in a separate LUW under a new transaction ID.
Addition 2
... DESTINATION dest
Effect
Executes the function module externally as a Remote Function Call (RFC); dest can be a literal or a variable.
Depending on the specified destination, the function module is executed either in another R/3 System or as a C-implemented function module. Externally callable function modules must be flagged as such in the Function Builder (of the target system).
Since each destination defines its own program context, further calls to the same or different function modules with the same destination can access the local memory (global data) of these function modules.
Note
Note that a database commit occurs at each Remote Function Call (RFC). Consequently, you may not use Remote Function Calls between pairs of statements that open and close a database cursor (such as SELECT ... ENDSELECT).
Addition 3
... EXPORTING p1 = f1 ... pn = fn
Effect
EXPORTING passes values of fields and field strings from the calling program to the function module. In the function module, formal parameters are defined as import parameters. Default values must be assigned to all import parameters of the function module in the interface definition.
Addition 4
... TABLES p1 = itab1 ... pn = itabn
Effect
TABLES passes references to internal tables. All table parameters of the function module must contain values.
Notes
If several function module calls with the same destination are specified before COMMIT WORK, these normally form an LUW in the target system. Calls with the addition 1 are an exception to this rule - they each have their own LUW.
You cannot specify type 2 destinations (R/3 - R/2 connections).
(See Technical details and Administration transaction.)
Example
REPORT RS41503F.
/* This program performs a transactional RFC.
TABLES: SCUSTOM.
SELECT-OPTIONS: CUSTID FOR SCUSTOM-ID DEFAULT 1 TO 2.
PARAMETERS: DEST LIKE RFCDES-RFCDEST DEFAULT 'NONE',
            MODE DEFAULT 'N',
            TIME LIKE SY-UZEIT DEFAULT SY-UZEIT.
DATA: CUSTITAB TYPE TABLE OF CUST415,
      TAMESS   TYPE TABLE OF T100,
      WA_CUSTITAB TYPE CUST415.
SELECT ID NAME TELEPHONE INTO CORRESPONDING FIELDS OF TABLE CUSTITAB
               FROM SCUSTOM WHERE ID IN CUSTID ORDER BY ID.
PERFORM READ_CUSTITAB.
EDITOR-CALL FOR CUSTITAB TITLE 'Editor for table CUSTITAB'.
PERFORM READ_CUSTITAB.
CALL FUNCTION 'TRAIN415_RFC_CALLTRANSACTION'
     IN BACKGROUND TASK
     DESTINATION DEST
     EXPORTING
          TAMODE    = MODE
     TABLES
          CUSTTAB   = CUSTITAB.
CALL FUNCTION 'START_OF_BACKGROUNDTASK'
     EXPORTING
          STARTDATE = SY-DATUM
          STARTTIME = TIME
     EXCEPTIONS
          OTHERS    = 1.
IF SY-SUBRC = 1.
EXIT.
ENDIF.
COMMIT WORK.
CALL TRANSACTION 'SM58'.
      FORM READ_CUSTITAB                                   *
FORM READ_CUSTITAB.
WRITE: / 'System ID:', SY-SYSID.
SKIP.
LOOP AT CUSTITAB into WA_CUSTITAB
    WRITE: / WA_CUSTITAB-ID, WA_CUSTITAB-NAME,
             WA_CUSTITAB-TELEPHONE.
ENDLOOP.
ULINE.
ENDFORM.
Pls. reward if useful....

Dump when i executed bex query

i execute bex with my user ( i am sap_all), i haven't problem.
when i executed this same report ( with variable autorisation), i have this dump:
the dump:
Erreur d'exécution     GETWA_NOT_ASSIGNED
Date et heure          11.12.2009 17:26:11
Désignation
Field symbol has not yet been assigned.
Causes
Error in the ABAP Application Program
The current ABAP program "SAPLRSEC_CHECKS" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Solutions
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
    administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Analyse des erreurs
You attempted to access an unassigned field symbol
    (data segment 32774).
This error may occur if
    - You address a typed field symbol before it has been set with
      ASSIGN
- You address a field symbol that pointed to the line of an
      internal table that was deleted
    - You address a field symbol that was previously reset using
      UNASSIGN or that pointed to a local field that no
      longer exists
- You address a global function interface, although the
      respective function module is not active - that is, is
      not in the list of active calls. The list of active calls
      can be taken from this short dump.
Comment corriger l'erreur
If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
"GETWA_NOT_ASSIGNED" " "
    "SAPLRSEC_CHECKS" or "LRSEC_CHECKSF06"
    "LOOK_UP_STAR_VARIABLES"
If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
    (Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
end ******************
best regard
francoise

Try applying the following OSS Notes into your BW system. These should resolve the issue.
[OSS Note 1244842 - Termination LOOK_UP_STAR_VARIABLES-01-|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1244842] (relevant for BW 7.00 SP20, BW 7.01 SP3, BW 7.10 SP7 or BW 7.11 SP1)
[OSS Note 1290949 - Dump GETWA_NOT_ASSIGNED for Query on InfoSet|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1290949] (relevant for BW 7.00 SP21, BW 7.01 SP4, BW 7.10 SP8 or BW 7.11 SP2)

Hierarchy Activation dumps when itu0092s executed from Process Chain. u0096 BI 7.0

Issue:
CostElement Hierarchy sign reversal is updated manually using ABAP Program to update sign reversal, which updates H and J tables and activates the Hierarchy using func module RSHIER_HIER_CHECK_AND_ACTIVATE. It works fine when ABAP is executed manually as well as when Process Chain is executed in BW 3.5.
However, the same Process Chain in BI 7.0 it abends during Hierarchy Activation.
From the Dump, find below call sequence of programs for more details:
No.   Ty.          Program                             Include                             Line
      Name
6) METHOD       CL_RSSH_SHOW_LOG==============CP    CL_RSSH_SHOW_LOG==============CM008    53
CL_RSSH_SHOW_LOG=>CREATE_CONTAINER
5) METHOD       CL_RSSH_SHOW_LOG==============CP
CL_RSSH_SHOW_LOG==============CM007    52
CL_RSSH_SHOW_LOG=>SHOW_MESSAGES_WRITE_LOG
4) FUNCTION     SAPLRSHIER                          LRSHIERU03                            121
      RSHIER_HIER_CHECK_AND_ACTIVATE
3) FORM         ZBWUXXX1                            ZBXXXXX1                              382
005-ACTIVATE-HIER                                                     2) FORM         ZBWUXXX1                            ZBWUXXX1                              278
It abends during Container creation to send out a message.
Any help to resolve this issue would be highly appreciated.
Thanks, Vijay

Vijay,
Due to the age of this post I am assuming did you find a fix to the problem?
I actually would like more information about your abap program as we are trying to create a similar program.

Need error message in foregorund,when its executed in background

Hi
I have a program which runs in background every hour, so when the background job is active and if the same program is executed in foreground, i should throw an error in the selection screen.
Is there any table which has this information, one more thing, the status of the job should be active and not released that I should throw an error.
Pls respond.
Thanks

You have to use ENQUE and DEQUEUE function modules.
In INITIALIZATION event, add the following code:
CALL FUNCTION 'ENQUEUE_ESVARIANT'
       EXPORTING
            mandt          = sy-mandt
            report         = g_repid         "copy of SY-REPID
       EXCEPTIONS
            foreign_lock   = 1
            system_failure = 2
            OTHERS         = 3.
IF sy-subrc <> 0.
* Somehow display your error message here.
ENDIF.
In END-OF-SELECTION event, dequeue using the following code:
CALL FUNCTION 'DEQUEUE_ESVARIANT'
       EXPORTING
            mandt = sy-mandt
            report = g_repid.

Business Rules - how to stop when being executed in background?

Hello,
I have a very simple BR that is supposed to copy data from one version to another, however the BR timeouted and now is being executed in the background.
The thing is that it is being executed for two hours now. I can see the BR in the Job window with 'Processing' status.
I've set two system options HBR_MAX_WAIT_FOR_RULE and HBR_MONITOR_DELAY to 600000, and restarted the application and essbase, however the BR's status in Job window is still 'processing'.
Is there any way to:
1. Stop the execution of the business rule?
2. Verify what causes the BR to run for so long?
3. Does dense/sparse settings have the impact on BRs' execution time?
Kind regards
Marcin Stawny

Hi,
I take it we are talking classic planning.
You can terminate rules from within EAS, if you right click the analytic server and select edit sessions, you should see the rule running.
I am not sure why it says it still running maybe it has cached that it is running and still believes it is, have you restarted EAS?
Lots of different elements can be makinh a business rule run for a long time, the code/cube might need optimizing, it might be trying to copy a lot of data.....
Maybe worth posting more details on your database, number/name of dimensions, number of members, dense/sparse
Also the business rule code.
Cheers
John
http://john-goodwin.blogspot.com/

How to debug a background task that takes a lot of time to execute

My workflow consists of a background task which takes a significant amount of time to execute completely. I have executed the BO method from SWO1 and it works fine.. takes just few secs to execute.
But when this method is executed through workflow as a background task, it takes more than 20 mins to execute.
What can be the possible causes and how do I debug this.

Dear Tiyasha,
You can debug your task even if it is a back ground task.
The process is as follows :
The place where want to place your break point put an infinite while loop just before your actual code.Now execute your workflow , now go to sm54 there u will find your entry and from here you can go to the debugger .In the debugger make the value of the while loop to be true so that u can proceed.
Here u will able to debug it properly.
Regards,
Geet

Program giving dump when run in background

Hi All,
I have an ALV report in which I am using REUSE_ALV_GRID_DISPLAY.
The report works perfectly in foreground. But when I execute in background I am getting dump.
Dump details are given below.
ShrtText
    Unable to fulfil request for 134217728 bytes of memory space.
What happened?
    Each transaction requires some main memory space to process
    application data. If the operating system cannot provide any more
    space, the transaction is terminated.
What can you do?
    Try to find out (e.g. by targetted data selection) whether the
    transaction will run with less main memory.
    If there is a temporary bottleneck, execute the transaction again
    If the error persists, ask your system administrator to check the
    following profile parameters:
    o ztta/roll_area            (1.000.000 - 15.000.000)
           Classic roll area per user and internal mode
           usual amount of roll area per user and internal mode
    o ztta/roll_extension       (10.000.000 - 500.000.000)
           Amount of memory per user in extended memory (EM)
    o abap/heap_area_total      (100.000.000 - 1.500.000.000)
           Amount of memory (malloc) for all users of an application
           server. If several background processes are running on
           one server, temporary bottlenecks may occur.
           Of course, the amount of memory (in bytes) must also be
           available on the machine (main memory or file system swap).
           Caution:
           The operating system must be set up so that there is also
           enough memory for each process. Usually, the maximum address
           space is too small.
           Ask your hardware manufacturer or your competence center
           about this.
           In this case, consult your hardware vendor
    abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each dialog process.
    Parameters for background processes:
    abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each background process.
    Other memory-relevant parameters are:
    em/initial_size_MB:         (35-1200)
           Extended memory area from which all users of an
           application server can satisfy their memory requirement.
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
Error analysis
    More main memory area was requested.
    However, all the available space has been used up.
    Possible reasons:
    - Many (large) internal tables.
    - Many (large) programs active.
    - Deep nesting of subroutines with a lot of local data.
Can you please help on this ?

Hi,
Check you code properly.
The dump is because of an infinite loop which is running when you run the program in background and it is keeping appending or inserting the same table.
Check teh same.
regards,
Ankur Parab

Workflow hanged- Background Task in Process.

Hi All,
Workflow hanged at background task with status in Process due to a dump…we change the logic now.
How I can restart this task again?
I checked in SWPC its empty.
Thanks,
KP

Yes, SWI2_DIAG has a Restart Workflow' button.
Did you try it already?
Despite what the button name suggests, it 'resumes' the workflow from the current step
(it doesn't 'restart' from scratch).
cheers
Paul

PDF document first page is blank when executing in background

Hi,
I am creating spool before displyaing report output by using GET_PRINT_PARAMETERS and NEW PAGE PRINT ON option and displaying report header and report final internal table. calling NEW PAGE PRINT OFF
finally i am sending mail, by using SO_NEW_DOCUMENT_SEND_API1 function module in foreground executing and background execution.
When we execute in foreground i am recieveing mail and pdf is perfect.
when we execute in background i am recieveing mail. But when i opend the pdf document in mail, PDF doucment first page is balnk and second page onwards i am able to see the report output
why the PDF first page is blank when i execute the same report with same variant in back ground.
Please help me in this issue.
Thanks in advance
Raju

Hi Raju,
<li> Call ABAP4_COMMIT_WORK function module after NEW-PAGE PRINT OFF command.
NEW-PAGE PRINT OFF.
CALL FUNCTION 'ABAP4_COMMIT_WORK'.
Thanks
Venkat.O

Pop up Box while workflow executes an activity step

Hi Folks!
I dont know whether this is feasible or not, but please shoot your suggestions.
I want to display a pop up box in SAP GUI when a workflow executes a particular step. Basically, once my workflow starts, I have included a condition step (it checks the document type). So if the document type is 'X', then the workflow should proceed as usual. However, when the document type 's 'Y', the workflow should throw a pop up message over the screen and the workflow should terminate.
Now the reason why we want the pop up screen rather than an email/workitem is because we have two workflows that utilize the same business object (FIPP). There was a situation where an end user manually started *(thru 'services for object'-> start workflow) the wrong workflow for a document, due to which the document got posted without getting any approvals.
So what we would like to achieve is when the user manually starts the wrong workflow, the workflow should proceed and then when the check condition fails the user should get a pop up box immediately in SAP itself saying that the wrong workflow was started.
Your inputs/comments are most welcome.
Regards,
Anwar.

I am sorry but it is not possible to throw pop up every time, actually workflow consists of background task which got executed without user intervention and in those cases no pop up will come up.
You can get pop up box for dialog task (such as user decision etc)you have to write down business object method code for that.
there are many ways you can handle your situation:
1. Write down the Check FM for FIPP-Posted Event where you can check it whether it is approved or not, If not then do not complete the workflow and start some dialog WI and send across to approvers
(It is just outline, you have to formulate the solution around this outline).
2. Also you can check for BAdi or user Exit and directly can write down message for that, It seems more easy.
Cheers
Jai

Background Task status is halted in 'In Process'

Hello,
The background task in a workflow template is halted in the 'In Process' state and the workflow is not completed. When I tried to execute the method from SWO1 separately, it is working fine.
Please do let me know if I am missing out something.
Regards,
Samson

Hi Samson,
You can also check in tx SWU2 if there aren't any local rfc's stuck in there.
To investigate the problem tx SWPC might help (it is precisely designed to restart workflows with a background task stuck into "in progress" status).
You can also have a look at [this thread|Workflow hanging - ST22 and SWU2 empty; for more suggestions.
Cheers,
Patrick

DYNPRO_SEND_IN_BACKGROUND dumps in Update debugging

Hi Experts,
I am getting DYNPRO_SEND_IN_BACKGROUND dumps when I apply update debugging for SAPMV45A (VA01). It should open another session in debug mode, instead it is getting a dumps. I got lot of notes on the dumps, but nothing is useful.
A little Info:
Information on where terminated
The termination occurred in the ABAP program "SAPLV45U" in
"RV_SALES_DOCUMENT_ADD".
The main program was "RSM13000 ".
The termination occurred in line 5 of the source code of the (Include)
program "LV45UV02"
of the source code of program "LV45UV02" (when calling the editor 50).
The program "SAPLV45U" was started in the update system.
Program "RSM13000" is used for opening session in Update debugging and for handline the task.
In this case commit work is not happening and update records are locked.
Thanks in advance.
--Sri.

hi
good
go through this bolg, i hope this ll help you to splve your problem.
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/weblogs/topic/24%3fx-o%3d100
thanks
mrutyun^

Jquery in background task JavaScript runtime error: 'window' is undefined

How do we access the window variable in backgroundtasks ?
i need to use jquery and i get JavaScript runtime error: 'window' is undefined

It looks like jQuery is not written to be used from a web worker--or else you need a variant that is. This is because the global context in a background task written in JavaScript is
WorkerGlobalScope (see
http://www.w3.org/TR/workers/#workerglobalscope) not window, so window
isn't defined.
You might be able to work around a situation like this, depending on what is needed from
window. (I'm assuming jQuery is trying to initialize its UI libraries, in which case you probably won't be able to do that from a worker/background task. They can't do UI directly.)
If you need something from window, specifically, your running app, when it registers the background task, could also write the necessary values into the
Windows.Storage.ApplicationData.localSettings container as background tasks can access that at any time.
It could be possible, then, to write the necessary values from window
into local settings, then create a window object and populate it with those values before loading jQuery. It'd be a hack, but might get you where you need to be.
That said, because there are limitations on what you can do from a background task, and how long you can run, you might ask whether jQuery is really buying you anything in that context. I can't say, of course, but it's a reasonable question to ask before
trying this kind of workaround.
Kraig
Author,
Programming Windows 8 Apps with HTML, CSS, and JavaScript,
a free ebook from Microsoft Press

DYNPRO_SEND_IN_BACKGROUND dump when workflow executes a background task

Similar Messages

Maybe you are looking for