Dump from rfc user

[Former Member]

Hi All ,

I am getting this dump DYNPRO_SEND_IN_BACKGROUND

fro user RFC_USER .

I think it could be because of this function module .

CAmLL FUNCTION 'Z_BAPI_NOTIF_STAT_CHANGE'

STARTING NEW TASK 'SSND'

EXPORTING

notif_no = is_new_viqmel-qmnum

status_no = 'E0069'.

here is some info from the dump

Error analysis

During background processing, the system attempted to send a

screen to a user.

Current screen: "SAPLSMPO " 0100.

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" " "

"SAPLSMPO" 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".

16 EVENT SAPLSMPO ??? 0

SYSTEM-EXIT

15 FUNCTION SAPLSMPO LSMPOU01 60

SMPO_DISPLAY_MESSAGES

14 METHOD /MRSS/CL_RAC_INTEGRATION_SRV==CP /MRSS/CL_RAC_INTEGRATION_SRV==CM00F 15

/MRSS/CL_RAC_INTEGRATION_SRV=>CANCEL_SAVE

13 FUNCTION SAPLZMRS_RSN_NOTIFICATION LZMRS_RSN_NOTIFICATIONU03 1003

ZMRS_SERV_NOTIF_PUSH_TO_MRS

12 FUNCTION SAPLZMRS_RSN_NOTIFICATION LZMRS_RSN_NOTIFICATIONU01 153

ZMRSS_RSN_PUSH_FROM_PM000010

11 FUNCTION SAPLIBE1 LIBE1U07 63

OPEN_FI_PERFORM_PM000010_E

10 FORM SAPLIQS1 LIQS1F16 1001

GENERATE_NOTIFICATION_F16

9 FORM SAPLIQS1 LIQS1F16 153

POST_NOTIFICATION_F16

8 FUNCTION SAPLIQS1 LIQS1U05 60

IQS1_POST_NOTIFICATION

7 FORM SAPLIQS4 LIQS4F20 30

POST_NOTIFICATION_F20

6 FUNCTION SAPLIQS4 LIQS4U12 19

IQS4_SAVE_NOTIFICATION

5 FUNCTION SAPLIQS6 LIQS6U32 16

BAPI_SERVNOT_SAVE

4 FUNCTION SAPLZPM_NOTIF_STATCHG LZPM_NOTIF_STATCHGU01 207

Z_BAPI_NOTIF_STAT_CHANGE

3 FORM SAPLZPM_NOTIF_STATCHG LZPM_NOTIF_STATCHGU01 1

Z_BAPI_NOTIF_STAT_CHANGE

2 FORM SAPMSSY1 SAPMSSY1 85

REMOTE_FUNCTION_CALL

1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30

%_RFC_START

Kindly guide me in this regard .

[Sm1tje]

This is usually caused by statements like CALL SCREEN or something like it. Since this is an rfc user, screen processing is not possible. But that's exactly what is happening here. Try to find if there is a user exit, BAdI or whatever in which a screen is processed.

[Former Member]

thnx for ur rply

i ill try to find out

[Clemenss]

Hi Anit,

if you want to preserve the formatting, mark the formatted dump text with above <_> button as code, this helps. Check with PREVIEW.

The RFC user is not necessarily the problem. We have a working solution calling a FUNCTION .. DESTINATION 'NONE'. This starts a new session also as 'RFC' and allows all screen processing.

CALL FUNCTION 'Z_BAPI_NOTIF_STAT_CHANGE' STARTING NEW TASK

I don't know (I also don't think so) that STARTING NEW TASK is handled as background task. First try the DESTINATION 'NONE' solution. If it still dumps, you shouls analyse where the dump really comes from. Function group SMPO is used for message display. Please check the 'Active Calls/Events' section of the dump, this will help to find the reason.

Kind regards,

Clemens