Urgent!! Dumps!!! DYNPRO_SEND_IN_BACKGROUND

[Former Member]

Hi Experts,

We are in the process of upgrading our SRM 3.0 system to SRM 5.0 system.We use classic scenario and ECC 5.0 as the backend system.

We notice that every time SRM 5.0 system makes an RFC call to the

backend system, there is a short dump "DYNPRO_SEND_IN_BACKGROUND " with

text "Screen output without connection to user" occuring the the ECC

system. It happens only when a user login first time and create shopping cart, but if a user does not logout and create shopping cart, this dump does occur.

However this does not happen when the RFC call is made from SRM 3.0 system.

Dump:

ShrtText

Screen output without connection to user.

What happened?

Error in ABAP application program.

The current ABAP program "SAPLSPO4" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

What can you do?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

is especially useful if you want to keep a particular message.

Error analysis

During background processing, the system attempted to send a

screen to a user.

Current screen: "SAPLSPO4 " 0300.

Please Help.

Thanks,

[Former Member · Accepted solution]

Hi,refer to this link

https://www.sdn.sap.com/irj/sdn/webdynpro?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#15

[Sm1tje]

It's obvious, according to the DUMP message, that a dialog screen is called. This will give a short dump since you are operating in background.

Seems to me that there is a problem with the RFC user or the RFC destination. I imagine that when calling the RFC in the backend system, the usual SAP login screen is called in which username and password should be entered. This screen in background will result in short dump.

Try to recreate (change does not always work, for whatever reason that is) the RFC connection. If this doesn't work, try to recreate the RFC user (or copy to new RFC user). Also check the type of the RFC user...should not be DIALOG user of course.