DYNPRO_SEND_IN_BACKGROUND IN RBDAPP01

Hi All,
I am using report RBDAPP01 with a list of Idoc numbers.
I have a z report which calculates the Idoc numbers and calls a function module in a seperate task ("starting new task" key word) .This function module calls the report RBDAPP01 .I have a background job around my z report. The problems is I get a short dump with the mesage DYNPRO_SEND_IN_BACKGROUND.
When I call the job directly with RBDAPP01,everthing is all right but as soon as I start a seperate task,the context is lost and RBDAPP01 losts.
I want to start 3 different threads ,each with different set of Idocs to be processed parallel .For this reason I am calling FM in seperate task.
Any Ideas?
Thanks and regards,
Bikram

Hi Thomas,
sy-BATCH = 'X' does not seem to work.
Hi Ravi,
Could you kindly explain what you mean excetly.
I have to create the threads (three threads for three different catagories of data) and also ensure that there is only one thread of a perticuler catagory running at any given pont in time.I am doing this by locking the task type (the one that I am using in "starting new task TASKTYPE").
zreport->FM in new TaskType1,2,3 (check if this task if it is already running)->Submit report RBDAPP01 and return.
Regards,
Bikram

Similar Messages

Program rbdapp01 when called from a program is not working

Hi Guys,
I am calling the program rbdapp01 from a custom program to reprocess an inbound ASN with IDOC status of 64. The code is listed as below in the custom program.
SUBMIT rbdapp01
WITH docnum = i_report_tab-docnum
WITH p_output = C_FALSE
AND RETURN.
After the execution of the custom program, the IIDOC is not processed and it remains in the status 64 with a message "Re processing deleted , inbound delivery IDOC , ,". When I run the program in debug mode, I can see that the control is going into the rbdapp01 program. But some where along the line, it is failing for what ever may be the reason and it does not process the IDCO, but it only populates the message.
But when I execute the same program rbdapp01 for the same IDOC from SE38, the IDOC is processed fine.
Looks like, I am missing something when I am calling this program rbdapp01 in another custom program. Any advice is really appreciated.
Regards
Rupesh.

Hi,
Please make use of this method of submit
DATA : rspar_tab TYPE TABLE OF rsparams,
        rspar_line LIKE LINE OF rspar_tab.
rspar_line-selname = 'DOCNUM'.
    rspar_line-sign    = 'I'.
    rspar_line-option = EQ'.
    rspar_line-low     = .
    rspar_line-high     = .
    APPEND rspar_line TO rspar_tab.
SUBMIT RBDAPP01 WITH SELECTION-TABLE rspar_tab.
Try to implement this code, hope this help outs
Thanks & Regards
Suresh

DYNPRO_SEND_IN_BACKGROUND when submitting a background job, when creating a

Hi.
We create sales orders via EDI. When certain sales orders are created, we execute user exists on the Sales Order save. During the User Exit, we submit/create (job_open_adk function, the submit command, and the job_close_adk function) a background job.
The background, is created and executed successfully, but we get 2
short dumps everytime.
The short dump is:
DYNPRO_SEND_IN_BACKGROUND
The description is:
Screen output without connection to user.
The short dump is for the user WF-BATCH.
I've used DEBUG and the shortdump occurs on the submit command.
submit zsd
to sap-spool
destination 'null'
immediately ''
keep in spool 'X'
without spool dynpro
and return
user l_user via job tbtcjob-jobname
number tbtcjob-jobcount
with p_vbeln = l_order
with p_ebeln = l_po
with p_uname = l_user.
Nothing should be displayed on the screen.
I used 'without spool dynpro' to prevent the 'Print Screen List' window
from appearing.
I've put this code into a TEST program. I ran the test program
myself. (under my ID) The program run perfectly. No
shortdump.
Similar code is used in other programs and it works perfectly - no shortdumps.
The short dump occurs when we use ALE/EDI to create a sales order.
The short dump has the ID WF-BATCH on it.
I'm guessing the problem is with the WF-BATCH ID. Are printer setting
missing on a Work Flow ID?
Any ideas why the 'without spool dynpro' parameter doesn't work for the
WF-BATCH ID?
I've tried searching OSS and I looked at the on-line help/documentation
on Submit. I saw a recommentation to use the
fuction 'GET_PRINT_PARAMETERS' to set all of the print parameters. I
tried this, but still got the short dumps.
Any suggestion on how I can run the Submit command and not get a short dump?
thanks,
Michelle

Hi,
Try this notes:
0100915 RSBDCREO: System hangs or parameters not effective
0377038 HR-CA-ALE: DYNPRO_SEND_IN_BACKGROUND for HR doc. d
0105165 Dump "DYNPRO_SEND_IN_BACKGROUND" in prog.SAPMSSY0
0169303 Warning messages displayed for settlement mass pro
0428489 VL10: Dump 'DYNPRO_SEND_IN_BACKGROUND' with backgr
[[http://forums.sdn.sap.com/thread.jspa?threadID=14875|http://forums.sdn.sap.com/thread.jspa?threadID=14875]]
Regards
HM

Error Screen output without connection to user DYNPRO_SEND_IN_BACKGROUND

Hi Experts
I am trying to debbug a BADI (for shc) in SRM 7.0 with external debugger.
I placed a breakpoint in the BADI, and logged into the portal screen,it is independent portal.
when i start to create the shc i get the error:     Screen output without connection to user
if i delete the breakpoint it work well.
the user i work with, has a developer key and SAP_ALL.
Runtime Errors      DYNPRO_SEND_IN_BACKGROUND
Exception              CX_SY_SEND_DYNPRO_NO_RECEIVER
Thanks
Almog
Edited by: almog126 on Jul 14, 2010 3:00 PM
Edited by: almog126 on Jul 14, 2010 3:00 PM

did you solve this?
We have now the same problem with any external debugging (WebServices/WebDynpro).

DYNPRO_SEND_IN_BACKGROUND SAPLSPO1 or LSPO1U06   POPUP_TO_CONFIRM

Hi
Request you all to go through the dump,
|What happened?
|
|
Error in the ABAP Application Program
|
|
|
|
The current ABAP program "SAPLSPO1" 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: "SAPLSPO1 " 0500.
|
|
|
|
Additional system information:
|
|
"currently running as cpic server"
|
|
|
|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" " "
|
|
"SAPLSPO1" or "LSPO1U06"
|
|
"POPUP_TO_CONFIRM"
|
|
|
|
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.
|
|
|
|System environment
|
|
SAP Release..... 731
|
|
SAP Basis Level. 0005
|
|
|
|
Application server... "lecc-prd-10"
|
|
Network address...... "172.18.218.141"
|
|
Operating system..... "Linux"
|
|
Release.............. "2.6.32-220.2.1.el6.x"
|
|
Hardware type........ "x86_64"
|
|
Character length.... 16 Bits
|
|
Pointer length....... 64 Bits
|
|
Work process number.. 8
|
|
Shortdump setting.... "full"
|
|
|
|
Database server... "lsdb-prd-2"
|
|
Database type..... "ORACLE"
|
|
Database name..... "EP1"
|
|
Database user ID.. "SAPSR3"
|
|
|
|
Terminal.......... " "
|
|
|
|
Char.set.... "C"
|
|
|
|
SAP kernel....... 720
|
|
created (date)... "Jan 15 2013 18:18:58"
|
|
create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr121116"
|
|
Database version. "OCI_112, 11.2.0.3.0, V1, default"
|
|
|
|
Patch level. 401
|
|
Patch text.. " "
|
|
|
|
Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
|
|
SAP database version. 720
|
|
Operating system..... "Linux 2.6, Linux 3"
|
|
|
|
Memory consumption
|
|
Roll.... 0
|
|
EM...... 12569424
|
|
Heap.... 0
|
|
Page.... 16384
|
|
MM Used. 10030984
|
|
MM Free. 2535400
|
|User and Transaction
|
|
Client.............. 100
|
|
User................ "EWMONECC"
|
|
Language key........ "E"
|
|
Transaction......... " "
|
|
Transaction ID...... "530F7949A5601689E1000000AC12DA41"
|
|
|
|
EPP Whole Context ID.... "005056B976AF1ED3A8902D8CE1BD4303"
|
|
EPP Connection ID....... "53109D4E863D7FBCE1000000AC12DA42"
|
|
EPP Caller Counter...... 1
|
|
|
|
Program............. "SAPLSPO1"
|
|
Screen.............. "SAPMSSY1 3004"
|
|
Screen Line......... 2
|
|
Debugger Active..... "none"
|
|Server-Side Connection Information
|
|
Information on caller of Remote Function Call (RFC):
|
|
System.............. "EP1"
|
|
Installation Number. 0020694200
|
|
Database Release.... 731
|
|
Kernel Release...... 720
|
|
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
|
|
Call Type........... "synchronous and transactional type Q (emode 0, imode 0)"
|
|
Inbound TID.........."AC12DA8A728B531098C05738"
|
|
Inbound Queue Name..."DLWSWP1CLNT1008000001383"
|
|
Outbound TID........." "
|
|
Outbound Queue Name.." "
|
|
|
|
Client.............. 100
|
|
User................ "EWMONECC"
|
|
Transaction......... " "
|
|
Call Program........."SAPLIRFC"
|
|
Function Module..... "TRFC_QIN_DEST_SHIP"
|
|
Call Destination.... "lecc-prd-10_EP1_00"
|
|
Source Server....... "lecc-prd-10_EP1_00"
|
|
Source IP Address... "172.18.218.141"
|
|
|
|
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 not available.
|
|
- The installation number is available from caller Release > 700
|
|
|
|
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.
|
|Information on where terminated
|
|
Termination occurred in the ABAP program "SAPLSPO1" - in "POPUP_TO_CONFIRM".
|
|
The main program was "SAPMSSY1 ".
|
|
|
|
In the source code you have the termination point in line 248
|
|
of the (Include) program "LSPO1U06".
|
|Source Code Extract
|
|Line |SourceCde
|
| 218|
PERFORM append_icon_to_button
|
| 219|
USING
icon_button_4
|
| 220|
l_quickinfo_button_4
"*048i
|
| 221|
CHANGING button_4.
|
| 222| ENDIF.
"974439 <<
|
| 223|
|
| 224|
|
| 225|* Aufbereitung des Fragetextes und Berechnung der Dynprogröße
|
| 226| PERFORM format_text TABLES text_tab1
|
| 227|
USING fragetext.
|
| 228|
|
| 229| PERFORM calculate_screen_size
|
| 230|
USING
|
| 231|
textlength
|
| 232|
start_spalte
|
| 233|
start_zeile
|
| 234|
CHANGING
|
| 235|
tab_len1
|
| 236|
tab_len2
|
| 237|
end_spalte
|
| 238|
end_zeile
|
| 239|
dynpro_nummer.
|
| 240|
|
| 241|
|
| 242|* Aufruf der Dialog-Dynpros
|
| 243|
|
| 244| CALL SCREEN dynpro_nummer STARTING AT start_spalte start_zeile
|
| 245|
ENDING   AT end_spalte   end_zeile.
|
| 246|
|
| 247|
|
|>>>>>| answer = antwort.
|
| 249|ENDFUNCTION.
|

Hi Madan,
I'm suggesting you for SAP Note 1265724 - BAPI technically close PO: Dump DYNPRO_SEND_IN_BACKGROUND
1739959 - DYNPRO_SEND_IN_BACKGROUND
Try to update kernel patch with the latest one available.
Need more info regarding which program or report you are executing .
Thanks,
Gaurav

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

Runtime Errors: DYNPRO_SEND_IN_BACKGROUND

Hi,
There are lots of dump called DYNPRO_SEND_IN_BACKGROUND in my prd system. The short text of the dump is Screen output without connection to user.
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.
Thanks,
Bismita

HI,
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.
"DYNPRO_SEND_IN_BACKGROUND" " "
"SAPMSSY0" or " "
"SYSTEM-EXIT"
Dump message: "DYNPRO_SEND_IN_BACKGROUND" " "
Program Name and Screen no: Current screen: "SAPMSSY0 " 0120.
As per our analysis using where user list this program hits 1.ECATT(Script), 2. Internet service.
We have deactivated the ECATT in production even though getting the same dump.
I don’t have any knowledge about internet service, so kindly suggest to me.
Regards,
Bismita

DYNPRO_SEND_IN_BACKGROUND errors in source system

Hi All,
Yesterday night we kicked DELTA Process Chain.
The PC failed While loading the 0GL_ACCOUNT Attributes, and showing the message Errors in Source System.
and also Failed at Cost Element Attributes but both the error messages are same.
Checked the source system connections and repeated the process, but it was failed again. and tried to load manually and again failed.
When we check the DUMP in Source system (ECC) in ST22 showing the message as below:
"DYNPRO_SEND_IN_BACKGROUND" Current screen: "SAPLSTRD " 0351
Note: We ran FULL load day before yesterday and Ran INITIAL yesterday, We are running DELTA TODAY.
one thing is we just deleted the GL attirbutes Requests manually and loaded INIT , we are able to do INIT load perfectly. but while trying DELTA only this problem is causing.
Thanks in Advance,
Teena

Hello ,
Sometimes the problem happens because the background users do not have the correct authorization. Please check the information in the SAP note 150315.
Kind Regards,
Des

DYNPRO_SEND_IN_BACKGROUND

Hi All,
I am getting the ABAP dumps in the Production DYNPRO_SEND_IN_BACKGROUND but i dont have any cancelled Background jobs.
I am posting my dump here, Please suggest me the solution for this
Category              ABAP Programming Error
Runtime Errors        DYNPRO_SEND_IN_BACKGROUND
Except.                CX_SY_SEND_DYNPRO_NO_RECEIVER
ABAP Program          SAPLSRABAX_EXC
Application Component BC-ABA-LA
Date and Time          10.03.2014 16:52:18
Short text
    Screen output without connection to user.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSRABAX_EXC" 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
    An exception occurred that is explained in 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:
    During background processing, the system attempted to send a screen to
    a user.
    Current screen: "SAPMSSY0 " 0120.
    Additional system information: "no window system type given"
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" "CX_SY_SEND_DYNPRO_NO_RECEIVER"
    "SAPLSRABAX_EXC" or "LSRABAX_EXCU01"
    "DISPLAY_EXC_SCREEN"
    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.
System environment
    SAP Release..... 702
    SAP Basis Level. 0006
    Application server... ""
    Network address...... ""
    Operating system..... "Windows NT"
    Release.............. "6.1"
    Hardware type........ "48x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... ""
    Database type..... "MSSQL"
    Database name..... "AZP"
    Database user ID.. "azp"
    Terminal.......... "215_PRT"
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "Sep 19 2011 23:29:58"
    create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"
    Database version. "SQL_Server_9.00 "
    Patch level. 105
    Patch text.. " "
    Database............. "MSSQL 9.00.2047 or higher"
    SAP database version. 720
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
    NT 6.0, Windows NT 6.1"
    Memory consumption
    Roll.... 0
    EM...... 8379584
    Heap.... 0
    Page.... 319488
    MM Used. 2337072
    MM Free. 1850048
User and Transaction
    Client.............. 000
    User................ " "
    Language key........ "F"
    Transaction......... "LAST_SHORTDUMP "
    Transaction ID...... "0966A8E3E0B7F1AD9306782BCB449F94"
    EPP Whole Context ID.... " "
    EPP Connection ID....... " "
    EPP Caller Counter...... 0
    Program............. "SAPLSRABAX_EXC"
    Screen.............. "SAPMS380 0100"
    Screen Line......... 6
    Debugger Active..... "none"
Information on where terminated
    Termination occurred in the ABAP program "SAPLSRABAX_EXC" - in
    "DISPLAY_EXC_SCREEN".
    The main program was "SAPMS380 ".
    In the source code you have the termination point in line 31
    of the (Include) program "LSRABAX_EXCU01".
Source Code Extract
Line
SourceCde
    1
FUNCTION DISPLAY_EXC_SCREEN.
    2
    3
*"*"Lokale Schnittstelle:
    4
*" IMPORTING
    5
*"    REFERENCE(P_LIVE_DUMP) TYPE FLAG DEFAULT SPACE
    6
*"    REFERENCE(P_SNAP) TYPE SNAP OPTIONAL
    7
*" EXPORTING
    8
*"    REFERENCE(P_PROCEED) TYPE FLAG
    9
*" CHANGING
10
*"    REFERENCE(P_FT) TYPE RSDUMP_FT_IT
11

Hi Praveen,
This Oss Note : 49730 may help you to understand the scenario

RBDAPP01 fails when packetsize is changed from 1 to 35

Hi,
For posting J3amat Idocs parallely, RBDAPP01 is executed in background with packet size 35. It failes with an exception PARM_NOT_VALID while reading the function J_3A1_LESEN_MARC_SINGLE which is called by the program RBDAPP01. When changed back to single processing it ran sucessfully ofcourse with more exectuion time. Why it fails in parallel processing and how to run it parallely?
Help on this highly appreciated.
Thanks.
Thripura.

Changing the recovery model has no impact on replication.
Please see:
http://technet.microsoft.com/en-us/library/ms151740.aspx
What recovery model is required on a replicated database?
Replication functions properly using any of the recovery models: simple, bulk-logged, or full. Merge replication tracks change by storing information in metadata tables. Transactional replication tracks changes by marking the transaction log, but this marking
process is not affected by the recovery model.

Get Idoc Types Processed by Jobs Running Programs RBDAPP01 or RBDMANI2

Hi Everyone! I would just like to ask if there is a way I can identify all background jobs which are processing a specific idoc type in SAP?
For example, I want to get the Jobs that are processing inbound idoc type WMMBXY using program RBDAPP01 or RBDMANI2.
Is there a way to extract this information?
Thanks in advance!

Vincent, we have a conservative approach RE those programs that re-process IDOCs in pending or error status : we do not define those jobs with open selections, instead we are specific in terms of message type and partner where applicable. We also set a limit in the number or attempts on a failed IDOC by setting a 'rolling start date' (like current date - 7). Besides audit considerations about lingering processes, you also need to take into account the impact of this process on the tale size. Each time the job runs and the IDOC fails, a status record will be added to the EDIDS table for each of those IDOC. If you do not pay attention, you may end up with large amounts of data. This is not only going to unplease your BASIS and DB administrator but eventually put in jeopardy your archiving process (wchich could lead to a system crash !!).
We usually aslo complement those jobs with a status change step (moving from error to no further processing) ; the date parameter can be set to something like anythiing with a creation date > current date + 3 months
To come back to your question : SM37 using the program name as parameter will help you find the associated jobs, but you might need to look into the step(s) and associated variant to get the messages those jobs / steps are processing

Re: ABAP runtime errors DYNPRO_SEND_IN_BACKGROUND

Hi Experts,
I'm getting so many dumps related to DYNPRO_SEND_IN_BACKGROUND. I am copying the Error analysis that is showing in the dump analysis.
Error analysis
During background processing, the system attempted to send a
screen to a user.
Current screen: "SAPMZACTIV " 2000.
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPMZACTIV " in
"%_CTL_OUTPUT".
The main program was "SAPMZACTIV ".
The termination occurred in line 37
of the source code of program "<SYSINI> " (when calling the editor 370).
Could you please help me on this and let me know if you need any further details.
Thanks & Regards,
Ravi.

Hello Ravi,
You say you are getting this error during "Error Analysis"?
Please review SAP Note 1011229 - ST-PI: Corrections for E2E Diagnostics
DYNPRO_SEND_IN_BACKGROUND is raised.
However, Miguel is correct that DYNPRO_SEND_IN_BACKGROUND errors are also addressed by ensuring you
have applied the basic functions Note for your SP Level
Please ensure the following Note that applies to your SP level has been applied to your system:
1334252     SAP Solution Manager: Basic functions: SP20 and SP21
1468591     SAP Solution Manager: Basic functions: SP25 and higher
1172948     SAP Solution Manager: Basic functions
1405878     SAP Solution Manager: Basic functions: SP22 to SP26
1373101     SAP Solution Manager 7.1: Basic functions
1552585     SAP Solution Manager: Basic functions 7.1 SP1
So check the Basic Functions Note is applied. If it is not, apply it, as it corrects many potential issues.
If it is on the system, or does not resolve, then apply SAP Note 1011229 - ST-PI: Corrections for E2E Diagnostics
Regards,
Paul

DYNPRO_SEND_IN_BACKGROUND IN RBDAPP01

Similar Messages

Maybe you are looking for