cancel
Showing results for 
Search instead for 
Did you mean: 

DYNPRO_SEND_IN_BACKGROUND dump when workflow executes a background task

Former Member
0 Kudos

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!

Accepted Solutions (1)

Accepted Solutions (1)

former_member554978
Active Contributor
0 Kudos

Probably this could be an authorization issue.

please check with authorization whether recently they have done any changes to users authorizations.

Former Member
0 Kudos

Hi Swaminathan,

My user ID has a developer role so I'm not sure this will work. Thanks anyway.

Answers (3)

Answers (3)

SagarSontakke
Active Participant
0 Kudos

Hello Dan,

Cant you create additional method to acoomplish your requirement instead of calling report RSWUWFML2.

You can create separate method to send email....

Regards,

Sagar

SagarSontakke
Active Participant
0 Kudos

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

Former Member
0 Kudos

Hi SVS,

I did run a simulation of the program and also the caller itself and no screen appeared (execution was successful). In addition to that I checked the flag "Errors only".

I know if something goes wrong It will send a screen back, it's just that I need to know why it hits that dump even for a successful run.

bpawanchand
Active Contributor
0 Kudos

You can create a variant of RSWUWFML2 by providing the mail body and the subject and you can schedule this particular variant , when ever a particular task's workitem id is created......

Former Member
0 Kudos

Hi Pavan,

The mail has to be sent right after a specific deadline of the workitem so I don't think this is a good idea. In addition to that, I'm trying as much as possible to incorporate the program into the workflow.