Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

DYNPRO_SEND_IN_BACKGROUND IN RBDAPP01

Former Member
0 Likes
835

Hi All,

I am using report RBDAPP01 with a list of Idoc numbers.

I have a z report which calculates the Idoc numbers and calls a function module in a seperate task ("starting new task" key word) .This function module calls the report RBDAPP01 .I have a background job around my z report. The problems is I get a short dump with the mesage DYNPRO_SEND_IN_BACKGROUND.

When I call the job directly with RBDAPP01,everthing is all right but as soon as I start a seperate task,the context is lost and RBDAPP01 losts.

I want to start 3 different threads ,each with different set of Idocs to be processed parallel .For this reason I am calling FM in seperate task.

Any Ideas?

Thanks and regards,

Bikram

Hi All,

I am using report RBDAPP01 with a list of Idoc numbers.

I have a z report which calculates the Idoc numbers and calls a function module in a seperate task ("starting new task" key word) .This function module calls the report RBDAPP01 .I have a background job around my z report. The problems is I get a short dump with the mesage DYNPRO_SEND_IN_BACKGROUND.

When I call the job directly with RBDAPP01,everthing is all right but as soon as I start a seperate task,the context is lost and RBDAPP01 losts.

I want to start 3 different threads ,each with different set of Idocs to be processed parallel .For this reason I am calling FM in seperate task.

Any Ideas?

Thanks and regards,

Bikram

4 REPLIES 4
Read only

Former Member
0 Likes
713

Just a guess, as the function module starts a new task and the selection screen is encountered, the error might be coming.

As a work around, you can try creating a background job with different selection parameters.

Function JOB_OPEN.

SUBMIT RBDAPP01 WITH PARAMETER VALUES VIA JOB NUMBER

Function JOB_CLOSE.

This way you will have 3 background jobs and you can also monitor them via SM37.

Regards,

Ravi

Read only

Former Member
0 Likes
713

Bikram,

Can you try by setting

sy-BATCH = 'X'

in your z report before the submit statement?

Let me know if its not working..

Cheers,

Thomas.

Read only

0 Likes
713

Hi Thomas,

sy-BATCH = 'X' does not seem to work.

Hi Ravi,

Could you kindly explain what you mean excetly.

I have to create the threads (three threads for three different catagories of data) and also ensure that there is only one thread of a perticuler catagory running at any given pont in time.I am doing this by locking the task type (the one that I am using in "starting new task TASKTYPE").

zreport->FM in new TaskType1,2,3 (check if this task if it is already running)->Submit report RBDAPP01 and return.

Regards,

Bikram

Read only

0 Likes
713

Hi,

My idea was not throught a function, but through multiple background jobs.

Instead of callin the function multiple times, create so manu jobs dynamically each time passing a different set of parameters. You wouldn't need a function module at all.

Regards,

Ravi