Dump : DYNPRO_SEND_IN_BACKGROUND

[Former Member]

Hello All,

In one of the batch processing jobs we are receiving this error with the program dump : DYNPRO_SEND_IN_BACKGROUND

would be glad to know under what conditions this error occurs.

Thank you,

- Sravan

[Former Member]

This happens if a functiuon module is called that whant's to send some "SAPGUI material" back to the caller (e.g. a Dynpro or a message popup).

The Batchjob runs in a background process (obviously under control of a background user?) thus having no chance to process such an answer.

Try to catch this exception in the calling program and/or try to find out, where the function module does such ugly things and modify this part of the module.

Is the program running in batch mode your own application? And what about the called function module?

[Former Member]

Additional info:

This also happens in other kinds of work processes, if the calling user is not a user of type "Dialog". E.g. the calling user might be a communication or background user.

[Former Member]

Hello Volker,

Thanks for the posting.

Would like to clarify on the key term that u have used "calling user", does it refer to the authorization of the production personnel who have set up this Job or ......

Thank you,

- Sravan

[Former Member]

The calling user is the user under whose control the batch job runs. this might be the user ho has planned and released the batch job in transaction sm37 or it might be an explicitely defined background user for this job when defining and scheduling the batch job.

If you are not sure: It is the user you see in transactiuon SM37 in the job overview.

Regards,

Volker

[Former Member]

Thanks Volker,

As said i am looking into the User profile of the job scheduler. If post a message based on the out come of my findings.

Thankyou,

- Sravan

[Former Member]

Hi Sravan,

Good that this thread has been answered, however it would be appreciated if you could share your solution and the steps you did to fix this issue.

Regards,

Sanjiv

[Former Member]

This dump will occur if a CALL SCREEN (or similar) statement is part of the execution logic while the program is executing in background.

In background, program is trying to SEND the screen output where as it is not possible and hence the dump. You need to see the code where it is happening from there you can go.

Thanks

Anjaiah