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

manisha_naik9
Discoverer
0 Likes
5,339

img-0524.jpeg

Short Text

Screen output without connection to user.

What happened?

Error in the ABAP application program.

The current ABAP program "SAPMSSY0" had to be terminated because it found a

statement that could not be executed.

What can I do?

Note which actions and entries caused the error to occur.

Consult your SAP administrator.

Using transaction ST22 for ABAP dump analysis, you can view, manage,

and retain termination messages for longer periods.

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.

Error analysis

An exception has occurred which is explained in more detail below. The

exception, which is assigned to class 'CX_SY_SEND_DYNPRO_NO_RECEIVER' was not

caught and

therefore caused a runtime error. The reason for the exception is:

Attempt made to send an image to a user during background processing.

Current screen: "SAPMSSY0" 0120.

Additional information from system:

"Currently running as cpic server."

How to correct the error

If the error occurs in one of your own ABAP programs or an SAP program

that you have modified, try to remedy the error.

If the error occurs in a non-modfied SAP program, you might be able to

find a solution in the SAP Notes system. If you have access to the SAP

Notes system, check there first using the following keywords:

"DYNPRO_SEND_IN_BACKGROUND" CX_SY_SEND_DYNPRO_NO_RECEIVER

"SAPMSSY0" bzw.

"SYSTEM-EXIT"

If you cannot solve the problem yourself, please send the following

information to SAP:

1. This description of the problem (short dump)

To do this, choose System -> List -> Save -> Local File (unconverted)

on the screen you are in now.

2. A suitable system log

To do this, call the system log in transaction SM21. Restrict the time

interval to ten minutes before the short dump and five minutes after

it. In the display, choose System -> List -> Save -> Local File

(unconverted).

3. If these are programs of your own, or modified SAP programs: Source

code of these programs

To do this, choose More Utilities -> Upload/Download -> Download in

the Editor.

4. Details regarding the conditions under which the error occurred or

which actions and input caused the error.


I have attached the image as well. can some one please help me on this

4 REPLIES 4
Read only

Dominik_Tylczynski
SAP Champion
SAP Champion
0 Likes
5,176

It's all but impossible to tell the details from your screenshot. You'd need to provide the entire short dump. The problem is that a screen is send during background processing. Background processing can't display the screen as it doesn't have access to your local computer, hence the dump. That's all what can be said without more details on the dump.

Read only

manisha_naik9
Discoverer
0 Likes
5,176

Hi Dominik,

i have updated the question with complete dump.

Read only

RaymondGiuseppi
Active Contributor
0 Likes
5,176

Where did you paste the dump file?

(Especially the part starting with 'Active Calls/Events', look for some dynpro call, e.g. a popup FM)

Read only

0 Likes
3,096

Hi @manisha_naik9 ,

Do you have any update to solve this issue?

Currently i am facing the same problem. Really appreciate if you can show how to fix the issue. Thank you