Question Re: DYNPRO_SEND_IN_BACKGROUND in Technology Q&A

DYNPRO_SEND_IN_BACKGROUND

Former Member — Tue, 25 Mar 2008 02:23:26 GMT

Hello,

I sometimes get a shortdump in my workflow and the background process is not triggered then.

DYNPRO_SEND_IN_BACKGROUND

Can anybody tell me what kind of problem that could be? I am using batch input in this method - could this be the reason?

The problem is that it happens just in a few cases, most of the time it runs trough properly.

Thanks a lot for your help,

Christoph

Re: DYNPRO_SEND_IN_BACKGROUND

Former Member — Tue, 25 Mar 2008 03:59:21 GMT

Hi Christoph,

Check the error log in the transaction ST22.

Re: DYNPRO_SEND_IN_BACKGROUND

Former Member — Tue, 25 Mar 2008 05:38:31 GMT

Hi,

I had come across a similar error during one of the workflow developments.

I had used a write statement in one of the methods.

Check if you have used it in your method. Or any other statement which involves a screen.

Regards

Shraddha

Re: DYNPRO_SEND_IN_BACKGROUND

Former Member — Tue, 25 Mar 2008 07:00:16 GMT

Hi,

thanks for this help,

In one method I used a write statement (used it for testing issues) - so I deleted it, hopefully it is working now.

For the other method I changed the 'BDC mode' - will see if it is working better now.

Anyway, thanks for all your help,

Christoph

Re: DYNPRO_SEND_IN_BACKGROUND

Former Member — Tue, 25 Mar 2008 07:34:21 GMT

Hi Christoph,

Please dont forget to reward points.........

Re: DYNPRO_SEND_IN_BACKGROUND

Former Member — Wed, 26 Mar 2008 07:12:08 GMT

Hi,

If you want to execute the bdc then change its mode to 'N'.

Hope this will solve your problem

Regards

Shraddha

Re: DYNPRO_SEND_IN_BACKGROUND

Former Member — Wed, 26 Mar 2008 09:03:13 GMT

Hi Christoph,

the error DYNPRO_SEND_IN_BACKGROUND will occur when a background proces tries to show a screen for user input. This can be a popup for a confirmation or to make a decision or to do something when a BDC runs into an error. Your main workflow will have the message "Execution interrupted" after this occurs.

On a case by case basis you might be able to fix the situation that caused the dump, it might be a data problem, and then restart the workflow using FM SAP_WAPI_ADM_WORKFLOW_RESUME with the ID of the main workflow.

Setting your MODE option to 'N' in your CALL TRANSACTION should solve the problem.

Hope this helps,

Gert.