Dump DYNPRO_SEND_IN_BACKGROUND

[ashish_vikas]

Hello friends,

may i ask your help for below dump which is coming in our CRM system, i tried searching notes but didnt found a suitable one.

Runtime Errors DYNPRO_SEND_IN_BACKGROUND

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 has

come across a statement that unfortunately cannot be executed.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

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

During background processing, the system attempted to send a

screen to a user.

Current screen: "SAPMSSY0 " 0120.

How to correct the error

If the error occurred in your own ABAP program or in an SAP

program you modified, try to remove the error.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"DYNPRO_SEND_IN_BACKGROUND" " "

"SAPMSSY0" or " "

"SYSTEM-EXIT"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

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

actions and input led to the error.

User and Transaction

Client.............. xxx

User................ user

Language Key........ "E"

Transaction......... " "

Transactions ID..... "xyz"

Program............. "SAPMSSY0"

Screen.............. "SAPMSSY0 0120"

Screen Line......... 0

Information on caller of Remote Function Call (RFC):

System.............. "CRM"

Database Release.... 701

Kernel Release...... 701

Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)

Call Type........... "synchron and transactional (emode 0, imode 0)"

Inbound TID.........."0A64BCEB101D4EDEE5968272"

Inbound Queue Name..."R3AD_CUSTOMEVT0982"

Outbound TID........." "

Outbound Queue Name.." "

Client.............. 888

User................ "USER"

Transaction......... " "

Call Program........."SAPLIRFC"

Function Module..... "TRFC_QIN_DEST_SHIP"

Additional information on RFC logon:

Trusted Relationship " "

Logon Return Code... 0

Trusted Return Code. 0

Note: For releases < 4.0, information on the RFC caller are often

only partially available.

rmation on where terminated

Termination occurred in the ABAP program "SAPMSSY0" - in "SYSTEM-EXIT".

The main program was "SAPMSSY1 ".

In the source code you have the termination point in line 0

of the (Include) program " ".

thanks

ashish vikas

[Former Member]

Hi Vikas,

I'm not very experienced in CRM system, but can you describe your scenario in more details, so that others who solved the same issue can help.

I wonder if your case is the same like in [this thread|;, it has been answered by Maggie.

Otherwise, from the description in ST22, it said that there is a screen called or submitted when the program is running in background and this is of course not allowed.

I think there are 2 options that you can try:

- Try to apply a suitable note ( I know you did that, but may be there are some other notes that can be applied ? )

- Debug the program ( internal or external ) with command option. In debugging mode, press F9, enter some keywords in the tab Command like : "Call function", or "call screen", or "submit", or "call transaction" etc...It will jump to the point where the dump happens.

Thanks,

paul

[Former Member]

Hello,

Please inform the full dump description. The session "Active Calls/Events" will give more information.

This dump raise when you are running a background process and the program trigger a screen/popup.

You can find a SAP note for your case, If you cannot find any you can change the program by yourself. I think changing the user type to D (dialog) or S (service) could solve, but I am not sure.

I face this problem few weeks ago and solve with SAP Note 1853157, but you need to check if session Active Calls/Events have the FM FAGL_CHECK_GENERATION in the list.

Best regards,

César