DYNPRO_SEND_IN_BACKGROUND dump workflow

Hello,
I have made a upgrade to ECC6 and when i try to run workflow and it stay stuck on a task and gives the follow dump:
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.
Error analysis
    During background processing, the system attempted to send a
    screen to a user.
    Current screen: "SAPMSSY0 " 0120.
I already check the logical connections in SM59 and i have rfc destination WORKFLOW_LOCAL_010 with user logon WF-BATCH, i run also SWU3 transaction to configure workflow.
Anyone could help me.
Best Regards,
Eduardo Paiva

Hi,
In SWEL find out for which step this Error is being raised. Most probably this step or activity is set as a background process, so get into the task and uncheck the 'Background processing' under section Execution.
Regards
Anik
Edited by: ANIK SIRCAR on Sep 21, 2011 1:09 PM

Similar Messages

DYNPRO_SEND_IN_BACKGROUND dumps in Update debugging

Hi Experts,
I am getting DYNPRO_SEND_IN_BACKGROUND dumps when I apply update debugging for SAPMV45A (VA01). It should open another session in debug mode, instead it is getting a dumps. I got lot of notes on the dumps, but nothing is useful.
A little Info:
Information on where terminated
The termination occurred in the ABAP program "SAPLV45U" in
"RV_SALES_DOCUMENT_ADD".
The main program was "RSM13000 ".
The termination occurred in line 5 of the source code of the (Include)
program "LV45UV02"
of the source code of program "LV45UV02" (when calling the editor 50).
The program "SAPLV45U" was started in the update system.
Program "RSM13000" is used for opening session in Update debugging and for handline the task.
In this case commit work is not happening and update records are locked.
Thanks in advance.
--Sri.

hi
good
go through this bolg, i hope this ll help you to splve your problem.
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/weblogs/topic/24%3fx-o%3d100
thanks
mrutyun^

DYNPRO_SEND_IN_BACKGROUND dump when workflow executes a background task

Hi,
My project is currently in version 4.6. I have a custom version of the PO release workflow and in here I created an activity calling a Custom Task, which then calls a Custom Business Object Method and then calls a program (using Submit RSWUWFML2). Unfortunately everytime the workflow goes to the said activity it hits a dump -- DYNPRO_SEND_IN_BACKGROUND.
I've tried unchecking the flag "Advance with Dialog" inside the task but it didn't work. I know RSWUWFML2 most of the time should be scheduled in background but it just so happens that we have a certain scenario in which it should have a different body and subject. This is the reason why I opted to call it inside the workflow.
Do you have any idea what caused this? Thanks!

Hello Dan,
DYNPRO_SEND_IN_BACKGROUND is an exception which occurs when system tries to call screen in background. Calling screen in background is not possible.
Report RSWUWFML2 creates LIST at the end of this report which is nothing but a special type of screen. If you run this report as background task, definitely above exception will occur.
Schedule this report as job instead of using it in task.
Regards,
Sagar

DYNPRO_SEND_IN_BACKGROUND dump while processing delivery

Hello,
We have placed a BDC logic to create Invoice in MV50AFZ1 user exit of delivery. BDC session method is being used to create session for Invoice creation using transaction VF01. This isession is later executed in background job using program RSBDCSUB.
Although delivery gets processed successfully and Invoice also gets created, but we are getting a dump in ST22 with and error DYNPRO_SEND_IN_BACKGROUND. We are also getting an error in SM58 "Screen output without connection to User".
Can somene please help how this error can be removed.
Thanks & Regards,
Rohit

Hi,
This BDC logic has been placed in the Fuction Module. This Function Module is called as saperate unit in background task through MV50AFZ1. In this Function Module, VF01 batch session is created.
These batch sessions are later executed by a background job program RSBDCSUB. This batch job runs every 5 minutes.
Kind Regards,

DYNPRO_SEND_IN_BACKGROUND Dump due to Update Control Screen

Hi All,
I have a smartform which is being attached to a SO while creating from Idoc. Due to this smartform processing in update task, it is giving a update control screen and it is giving dump DYNPRO_SEND_IN_BACKGROUND.
My question: how to suppress this "Update Control" screen ? is there anything can be controlled from user status profile ?
Thanks,

What is the type of user?
Can you try with Dialog user or System user?

Dump workflow

Hello,
I have a workflow in status processing(for 2hours), but the workitem gives dump, is any way to change the status and proceed with workflow.
Best Regards,
Eduardo Paiva

Hello,
I think that already solved the problem; with user WF-BATCH, the workitem calls a screen:
Screen output without connection to user.
CX_SY_SEND_DYNPRO_NO_RECEIVER'
But now i have to continue with workflow.
Best Regards,
Eduardo Paiva

Difference between service and communication user

Hi,
We ran into a big problem in our CRM system getting millions of Dynpro_Send_in_background dumps while processing inbound queues R3AD* from R/3 system to CRM. Lots of Updates getting failed with CRM_SCHEDLIN_UPDATE_DU function module while executing report LCRM_SCHEDLIN_DUU01.
Error Details - CRM_ORDER_MISC 002: Error in updating object SCHEDLIN
We posted to SAP as well but did not find root cause. SAP saying we need to change RFC user "S_ECC_PR0400" from Service user to Communication user, that would stop the dump problem.
I want to know what is the unique difference between these users(Service & Comm) which will resolve the dump problem though I know the common difference between these users.
Thanks
Anju

Hi Anju ,
Communication 'C' User :
Use the user type Communikation for dialog-free communication between systems (for RFC or CPIC service users of different applications, for example, ALE, Workflow, TMS ZBV).
Dialog logon is not possible.
Service 'S' User :
A user of type Service is a dialog user available to a large anonymous set of users. It usually has closely-restricted authorizations.
Service users are e.g. used for anonymous system access via an ITS service. You can change a session which began as an anonymous session with a service user into a personal session under a dialog user with an individual authentification.
There is no check for obsolete/initial passwords at logon. Only the user administrator can change the password.
Multiple logon is allowed.
Hope this may help you.
Thanks
Gyan

DYNPRO_SEND_IN_BACKGROUND error in workflow

Hello All,
Iam getting the dump with error as 'DYNPRO_SEND_IN_BACKGROUND' in Production but not in Quality system ,while iam sending mail in workflow using FM SO_NEW_DOCUMENT_SEND_API1.
Could you please suggest what could be the error.
Thanks & Regards,
Nishanth Kumar

Hi,
If you run the calling program in background process and server program tries to output screen, the communication is always broken, regardless of user type. Make sure that RFC server program runs on a dialog work process. If you want to run that program in background job, you must modify the function module called so that it does not display any screens or list. Function module used here is 'ARFC_DEST_SHIP' with destination 'WORKFLOW_LOCAL_160'.
Regards,
Santhosh.

Dump error while Testing the Workflow

Hi Friends,
I have developed workflow for Approve and Reject Scenerio. But when i press Approve, the user should get the mail, same for Rejected also. When Test the Workflow, I am getting the Dump Error as
*Dump Error*********
Unable to read RFC destination WORKFLOW_LOCAL_320
Long text of error message:
Technical information about the message:
Message class....... "SWF_RUN"
Number.............. 617
Variable 1.......... "WORKFLOW_LOCAL_320"
Variable 2.......... "RFC_READ_DESTINATION_TYPE"
Variable 3.......... "DESTINATION_NOT_EXIST"
Variable 4.......... " "
Thanks in Advance. Rewarded if useful.
Naveen

Naveen,
It seems someone might have deleted the corresponding RFC destination (which is created automatically). Check in SM59.
ss

Process-controlled workflow hang due to dump

Hi all,
due to a temporary dump in an SRM 7 system, some document-related workflows are stucked... in other terms, these workflow processes have been started, the the dump occoured and by now, they seems to be stucked in "in process" state.
Tecnically, these are not workflow in error, so SWI2_DIAG is not helpful.
We'd like to unlock this situation and -eventually- restart the workflow process. How can we do it?
Thanks in advance for your help and support.
edit: system dump is now solved, which means, triggering the same workflow process will result in a success.
Edited by: Matteo Montalto on Jun 30, 2011 4:34 PM

Ok. There used to be OSS Note 1458380 - Process Controlled Workflow Restart Program, if the document is in "Awaiting Approval" Status.
Or do the manual restart by using tcode SWUE (Event trigger)
Object Category - ABAP Class
Object Type - /SAPSRM/CL_WF_PDO_SC
Event - READY_FOR_WORKFLOW
Object Key - <DOCUMENT_GUID>
Event Parameter - <SC Creator User ID>
and Click "Create Event" button
Use SWI1 to check whether the event is created and see whether the document is submitted for workflow triggering or use SWI6 to check for that SC document

Dump on screen when configuring Process controlled workflow

Hi Experts,
I am facing 1 problem in SAP SRM 7 ehp1. I am configuring Process controlled workflow. Previous workflow settings was Application controlled workflow as its been upgraded from SRM 5. If i run a RFX (BUS2200) cycle in application controlled workflow environment, it works flawlessly.
But when i change my workflow framework to process controlled workflow for all Business Objects. I face a dump when I am creating an RFX. The dump on the portal is:
http://dl3803.ltisap.com:8040/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif
DATREF_NOT_ASSIGNED
No access possible via the 'NULL' data reference
Method: PARTICIPATING_IN_ACTIVE_WF of program /SAPSRM/CL_PDO_DYN_MDA_WF_ADJ=CP
Method: EDIT_DURING_WORKFLOW of program /SAPSRM/CL_PDO_DYN_MDA_WF_ADJ=CP
Method: /SAPSRM/IF_PDO_META_CONF_BO~GET_BO_HDR_ACTION_METADATA of program /SAPSRM/CL_PDO_META_CONF_PROV=CP
Method: /SAPSRM/IF_PDO_META_CONSUMER~GET_ACTION_METADATA of program /SAPSRM/CL_PDO_META_BO_RFQ====CP
Method: /SAPSRM/IF_PDO_META_CONSUMER~GET_ACTION_METADATA of program /SAPSRM/CL_PDO_META_BO_RFQ_ADVCP
Method: /SAPSRM/IF_PDO_META_CONSUMER~GET_ACTION_METADATA of program /SAPSRM/CL_PDO_META_HANDLER===CP
Method: UPDATE_ACTIONS of program /SAPSRM/CL_CH_WD_MAP_IDENT====CP
Method: /SAPSRM/IF_CLL_MAPPER~REFRESH of program /SAPSRM/CL_CH_WD_MAP_IDENT====CP
Method: /SAPSRM/IF_CLL_MAPPER~REFRESH of program /SAPSRM/CL_CH_WD_IDEN_MAP_RFQ=CP
Method: OVERRIDE_LEAVE_INIT_SCREEN of program /SAPSRM/CL_FPM_OVRIDE_OIF=====CP
& when i check in st22. I get the dump as:
Category               ABAP Programming Error
Runtime Errors         DATREF_NOT_ASSIGNED
ABAP Program           /SAPSRM/CL_PDO_DYN_MDA_WF_ADJ=CP
Application Component SRM-EBP-PD
Date and Time          17.12.2011 15:46:56
and get dump at:
1 method PARTICIPATING_IN_ACTIVE_WF.
2   " this method returns ABAP_TRUE if the logon user has an active work item,
3   " i.e. he participates in an active approval workflow process.
4
5   DATA lv_curr_workitem_id    TYPE /sapsrm/wf_workitem_id.
6   DATA lr_process_info        TYPE ref to /SAPSRM/S_PDO_WF_PROCESS_INFO.
7
8   " the default:
9   rv_participates_in_active_wf = abap_false.
10
11   " The scenario is not valid for application-controlled workflow:
12   " Any agents who may edit the document (approver and requester)
13   " enter "Edit" mode right-away. No special handling possible.
14   lr_process_info = io_apf_md_context->get_process_info_ref( ).
>>>   IF lr_process_info->wf_version NE /sapsrm/if_wf_process_c=>GC_APF_VERSION_0200.
16     return.
17   endif.
18
19   " check if a valid workitem exists
20   lv_curr_workitem_id = io_apf_md_context->get_workitem_id( ).
21   IF lv_curr_workitem_id IS INITIAL.
22     RETURN.
23   ENDIF.
the only configuration I change in the system is I changed the workflow framework to process controlled workflow.
Kindly help.
Thanks
Anand

Hello Anand,
As per standard SAP recommendations the application-controlled workflow framework is only intended to be used if you are upgrading from SAP SRM 5.0 or earlier and you need to continue using your existing work-flows.
The default workflow framework setting is the process-controlled workflow from SRM 6.0 on-wards and the user will be provided a option to switch to the application-controlled workflow framework. The option to switch to process-controlled workflows is available only after you have once switched to application-controlled work flows but there will be a big caution that " If you switch from the application-controlled workflow framework to the process-controlled workflow framework; once a process-controlled workflow has been run, it is not supported that you switch back to application-controlled work-flows".
As per the details given i got a feel that we have tried executing the scenario by switching between application and process controlled workflow and hence the system have become inconsistent and its dumping.
I suggest you to raise a OSS ticket to SAP to resolve the issue.
Best Regards,
Rahul

Short Dump Error DYNPRO_SEND_IN_BACKGROUND

hello Experts
I am facing one problem while query execution as a short dump is coming with run time error DYNPRO_SEND_IN_BACKGROUND.
On the same time, the other query based on same Info provider is running perfectly without giving any error.
Plz help on this , I checked the forums but does not get any output.
Thanks in advance
Neha

Hi Neha,
Check the below SAP Note.
Note 1010525 - ABAP dump in precalculation server with system messages
Veerendra.

ABAP DUMP DYNPRO_SEND_IN_BACKGROUND

Hi Guys,
I am gettign this dump because of one BATCH user in the system. Can anybody please see into it and respond me back. I am attaching the exact error in this message,
Thanks
Irshad Mohammed
ABAP runtime errors    DYNPRO_SEND_IN_BACKGROUND
       Occurred on     09/27/2007 at 14:16:29
>> Short dump has not been completely stored. It is too big.
Screen output without connection to user.
What happened?
The current ABAP/4 program "SAPMSDYP " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
During background processing, the system attempted to send a
screen to a user.
Current screen: "SAPMSDYP " 0010.
How to correct the error
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"DYNPRO_SEND_IN_BACKGROUND"
"SAPMSDYP " or "<SYSINI> "
"%_CTL_OUTPUT"

Hi Irshad,
What report/transaction are you using in background ?
Regards.
Ruchit.

ABAP DUMP Dynpro_send_in_background occurs in ECC5.0

Hi experts,
We have one ECC5.0 environment which runs on AIX5.3 , and since yesterday, we have lots of ABAP dump Dynpro_send_in_background in st22, could anyone help me? I have searched from OSS and SDN, but seems no suitable case I can reference for our system. Please give me some hint,thank you.
System information
Version ：ECC5.0
patch level ：version 6.40 level 125
Database version ：Oracle 9.2.0.7
Long text in ST22
Runtime Error          DYNPRO_SEND_IN_BACKGROUND
Date and Time          01.07.2008 17:05:09
ShrtText
    Screen output without connection to user.
What happened?
    Error in ABAP application program.
    The current ABAP program "SAPMSSY0" 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: "SAPMSSY0 " 0120.
How to correct the error
    If the error occurred in one of your own programs or in an SAP program
    that you modified, try to correct it yourself.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "DYNPRO_SEND_IN_BACKGROUND" C
    "SAPMSSY0" or " "
    "SYSTEM-EXIT"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
       To obtain this, select in the current display "System->List->
       Save->Local File (unconverted)".
    2. A suitable printout of the system log
       To obtain this, call the system log through transaction SM21.
       Limit the time interval to 10 minutes before and 5 minutes
       after the short dump. In the display, then select the function
       "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, select the Editor function "Further Utilities->
       Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
System environment
    SAP Release.............. "640"
    Application server....... "yatptcp"
    Network address.......... "10.1.250.65"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00001E22D700"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 4
    Short dump setting....... "full"
    Database server.......... "yatptcp"
    Database type............ "ORACLE"
    Database name............ "TCP"
    Database owner........... "SAPTCP"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "May 1 2006 20:49:14"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "125"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
     10.2.0.."
    SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    Memory usage.............
    Roll..................... 16192
    EM....................... 25139136
    Heap..................... 0
    Page..................... 835584
    MM Used.................. 8185592
    MM Free.................. 191328
    SAP Release.............. "640"
User and Transaction
    Mandant............. 400
    Benutzer............ "KOERFCUSER"
    Sprachenschlüssel... "E"
    Transaktion......... " "
    Programm............ "SAPMSSY0"
    Dynpro.............. "SAPMSSY0 0120"
    Dynprozeile......... 0
    Informationen zum Aufrufer des Remote Function Calls (RFC):
    System.............. "TCP"
    Datenbank-Release... 640
    Kernel-Release...... 640
    Verbindungstyp...... 3 (2 = R/2, 3 = R/3, E = Extern, R = Reg. Extern)
    Aufrufsart.......... "synchron (imode 1)" (S = Synchron, a/A = Asynchron, T =
     Transakt. )
    Mandant............. 400
    Benutzer............ "KOERFCUSER"
    Transaktion......... " (Program: SAPLEDIN)"
    Funktionsbaustein... "IDOC_START_INBOUND"
    Aufruf-Destination.. "NONE"
    Quell-Server........ "yatptcp_TCP_01"
    Quell-IP-Adresse.... "10.1.250.65"
    Zusatzinformation zum RFC-Logon:
    Trusted Beziehung... " "
    Logon-Returncode.... 0
    Trusted-Returncode.. 0
    Bemerkung: Bei Releases < 4.0 sind die Informationen zum RFC-Aufrufer teilweise nicht vorhanden.
Information on where terminated
    The termination occurred in the ABAP program "SAPMSSY0" in "SYSTEM-EXIT".
    The main program was "SAPMSSY4 ".
    The termination occurred in line 0 of the source code of the (Include)
     program " "
    of the source code of program " " (when calling the editor 00).
Active Calls/Events
No.   Ty.          Program                             Include
      Name
    1 EVENT        SAPMSSY0                            ???
      SYSTEM-EXIT
Chosen variables
Name
    Val.
No.       1 Ty.          EVENT
Name SYSTEM-EXIT
SY-XPROG
    SAPMSSY0
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454555322222222222222222222222222222222
    310D339000000000000000000000000000000000
SY-XFORM
    NEW-LINE
    000000000000000000000000000000
    000000000000000000000000000000
    445244442222222222222222222222
    E57DC9E50000000000000000000000
Internal notes
    The termination occurred in the function "dynpex00" of the SAP
    Basis System, specifically in line 1513 of the module
     "//bas/640_REL/src/krn/dynp/dymain.c#9".
    The internal operation just processed is "----".
    The internal session was started at 20080701170507.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit      = unlimited
=> Stack limit     = 4294967296
=> Core limit      = 1073741312
=> File size limit = unlimited
=> Heap address = 0x0x118a5cf20
=> Stack address = 0xfffffffffff9f50
=> Stack low     = 0xfffffffffff9f50
=> Stack high    = 0xffffffffffff890
=> Stack Trace:
#AixStack() at 0x10004ae04
#CTrcStack2() at 0x10004aefc
#rabax_CStackSave__Fv() at 0x10007bb2c
#ab_rabax() at 0x100078bd8
#dypex00() at 0x10020a204
#dynpoutf() at 0x1011990c0
#dynprctl() at 0x10119fcf8
#dynpen00() at 0x10020de20
#Thdynpen00() at 0x1000a51f8
#TskhLoop() at 0x1000a884c
#tskhstart() at 0x1000becdc
#DpMain() at 0x101742da4
#nlsui_main() at 0x101716148
#main() at 0x101716104

Dear All,
Any Solution for this similar problem - In Web Dynpro Application when we call the following application the DYNPRO_SEND_IN_BACKGROUND runtime error happens.
Note
     The following error text was processed in the system XXX : Screen output without connection to user.
     The error occurred on the application server xxxxxxxx_XXX_00 and in the work process 0 .
     The termination type was: RABAX_STATE
     The ABAP call stack was:
SYSTEM-EXIT of program SAPLSTRD
Function: TRINT_POPUP_EDIT_CANCEL_SHOW of program SAPLSTRD
Form: RAISE_ERROR of program SAPLSTRD
Function: TRINT_OBJECTS_CHECK_AND_INSERT of program SAPLSTRD
Function: TR_OBJECTS_CHECK of program SAPLSTRD
Function: RH_HRPOBJECT_CORR_AT_SAVE of program SAPLRHWM
Form: UPDATE of program SAPUP50R
Form: PUT_INFOTYP_BUFFER of program SAPFP50P
Form: %_PROCESS_P_O_C of program SAPMSSY0
Form: %_COMMIT of program SAPMSSY0
What can I do?
     If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system E6Q in transaction ST22.
     If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server xxxxxxx_XXX_00 in transaction SM21.
     If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server qltr01d3801_E6Q_00 . In some situations, you may also need to analyze the trace files of other work processes.
     If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 300 -u: X.XXXX -l: E -s: E6Q -i: xxxxxx_XXX_00 -w: 0 -d: 20080709 -t: 155438 -v: RABAX_STATE -e: DYNPRO_SEND_IN_BACKGROUND
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team

Dump 'DYNPRO_SEND_IN_BACKGROUND'

Hi Guys,
I am getting this dump everyday in my system. Please help me.
Dump details:
Screen output without connection to user.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLSLST " 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.
Error analysis
During background processing, the system attempted to send a
screen to a user.
Current screen: "SAPLSLST " 0101.

I am providing the system log of dump, it may help to analyse.
07:04:27 DIA 0 510 NETCONNECTOR ME21 R68 Perform rollback
07:04:33 DIA 0 510 NETCONNECTOR ME21 AB0 Run-time error "DYNPRO_SEND_IN_BACKGROUND" occurred
07:04:34 DIA 0 510 NETCONNECTOR ME21 AB1 > Short dump "101220 070433 FRPIVSRV NETCONNECTOR" generated
07:04:45 DIA 1 510 NETCONNECTOR ME22 R68 Perform rollback
07:04:45 DIA 1 510 NETCONNECTOR ME22 AB0 Run-time error "DYNPRO_SEND_IN_BACKGROUND" occurred
07:04:45 DIA 1 510 NETCONNECTOR ME22 AB1 > Short dump "101220 070445 FRPIVSRV NETCONNECTOR" generated
07:05:23 DIA 0 510 NETCONNECTOR ME22 R68 Perform rollback
07:05:23 DIA 0 510 NETCONNECTOR ME22 AB0 Run-time error "DYNPRO_SEND_IN_BACKGROUND" occurred
07:05:23 DIA 0 510 NETCONNECTOR ME22 AB1 > Short dump "101220 070523 FRPIVSRV NETCONNECTOR" generated
07:05:23 DIA 0 510 NETCONNECTOR ME22 D01 Transaction Canceled SY 002 ( Screen output without connection to user. )
07:05:23 DIA 0 510 NETCONNECTOR ME22 R68 Perform rollback
07:05:30 DIA 0 510 NETCONNECTOR ME22 R68 Perform rollback
07:05:30 DIA 0 510 NETCONNECTOR ME22 AB0 Run-time error "DYNPRO_SEND_IN_BACKGROUND" occurred
07:05:30 DIA 0 510 NETCONNECTOR ME22 AB1 > Short dump "101220 070530 FRPIVSRV NETCONNECTOR" generated
07:05:31 DIA 0 510 NETCONNECTOR ME22 R68 Perform rollback

DYNPRO_SEND_IN_BACKGROUND dump workflow

Similar Messages

Maybe you are looking for