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

Similar Messages

  • 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

  • Crytal Reports 2008 SP3 - BAiO Reports - Dump 'DYNPRO_SEND_IN_BACKGROUND'

    Hello,
    we have following BAiO-Installation:
    SAP-Kernel Informationen
    SAP-Kernel :  701_REL
    Datenbank Client Library : SQLDBC 7.6.6.006 CL 216871
    hergestellt auf  :  NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00
    hergestellt am  :  Feb 24 2009 23:27:20
    Support-Level  :  0
    Kernel Patchnummer : 32
    Source-Id  :  0.032
    DBSL Patchnummer : 024
    ICU Version : 3.0 Unicode Version 4.0.1
    libsapu16 Version : 2.0025  Feb 24 2009 21:13:21
    Crystal Report 2008
    CR Developer
    Version: 12.3.0.601
    During the binding of some Crystal Reports there are Dumps in SAP-System 'DYNPRO_SEND_IN_BACKGROUND' -  Error message: "SNC disabled to start insecure programs, reject request
      to start olca9056.633415DC6762B03AFC0 from host=olca9056 TP=sapgw01"
    Know everyone this mistake?
    Thanks and  greeting Peggy Nosek
    Reports, which running:
    - Cost Analysis Planned vs. Actual Order Costs.rpt
    - Financial Statements.rpt
    - GL_Statement.rpt
    - Purchasing Group Analysis.rpt
    - Travel by Cost and Location.rpt
    Reports with dump:
    - AP Open Items.rpt
    - Controlling Dashboard.rpt
    - Cost Analysis - Planned vs. Actual Cost Variance for Cost Centers.rpt
    - Credit Memo Analysis.rpt
    - Customer Fact Sheet.rpt
    - Customer Standard Analysis.rpt
    - List of Personnel Travel Expense.rpt
    - List of Sales Orders.rpt
    - New Quotations and Orders Values and Numbers.rpt
    - Sales analysis by product material.rpt
    - Sales Dashboard.rpt
    - Sales Organization Analysis.rpt
    - Stock Overview.rpt
    - Vendor Analysis.rpt
    - Vendor Comparison.rpt
    - Vendor Fact Sheet.rpt

    Hello Ingo,
    the dumps will be created by connection of tables.
    For example the Report "Customer Standard Analysis.rpt":
    If I binding the report on my SAP-Sytem there are the dump:
    DYNPRO_SEND_IN_BACKGROUND
    "SNC disabled to start insecure programs, reject request  to start olca9056.1846712AC676934D59A0 from host=olca9056 TP=sapgw01"
    This report include following tables: kna1, makt, s001.
    If I build a new Report with table  there are the dump:
    - kna1
    DYNPRO_SEND_IN_BACKGROUND
    Aktuelles Dynpro: "SAPMSSY0 " 0120.
    "SNC disabled to start insecure programs, reject request to start olca9056.63348BC67693BAEAD0 from host=olca9056 TP=sapgw01"
    -makt
    DYNPRO_SEND_IN_BACKGROUND
    Aktuelles Dynpro: "SAPMSSY0 " 0120.
    "SNC disabled to start insecure programs, reject request  to start olca9056.18467106C6769401E660 from host=olca9056 TP=sapgw01"
    - s001
    DYNPRO_SEND_IN_BACKGROUND
    Aktuelles Dynpro: "SAPMSSY0 " 0120.
    "SNC disabled to start insecure programs, reject request  to start olca9056.184671640676946DBF20 from host=olca9056 TP=sapgw01"
    greets Peggy

  • 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.

  • Urgent!! Dumps!!! DYNPRO_SEND_IN_BACKGROUND

    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,
    Edited by: Afi C on Apr 17, 2008 12:31 PM
    Edited by: Afi C on Apr 17, 2008 12:32 PM

    Hi Afi,
    If the system raise a popup screen or need an user interaction during a background process, you can get "DYNPRO_SEND_IN_BACKGROUND" error. Possibly, you are connecting to a remote server at background process. At the middle of the process, the system is asking for an interaction from the user. In order to find out which dialog appears during the process, take a look into your short dump in detail. You can find some strings that belongs to the dialog box inside of short dump.
    Best regards,

  • DYNPRO_SEND_IN_BACKGROUND  Short dump

    In updated teask  there are some updated function modules are executed. These function modules are giving error in popup saying "Buffer Tables are not up to date". the message  long text it is "To analyze the error, you can set a breakpoint in the function module 'BBP_PD_ABORT' and look at the call-up hierarchy in debugging mode."
    So I kept some break point in that function module, now it is giving the following short dump "DYNPRO_SEND_IN_BACKGROUND ",
    please tell me what to do
    Thanks & Regards,
    Raghu,

    Right, it is trying to throw a debug screen when in background.  You must remove the breakpoint.
    Regards,
    Rich Heilman

  • 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 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?

  • 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

  • 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

  • RFC/BAPI Call (ABAP Web Dynpro)- DYNPRO_SEND_IN_BACKGROUND

    Hi all,
    I'm developing an ABAP Web Dynpro application which utilise a RFC enabled function module. When I tried to execute the function module through the browser it terminated with an abap dump. I checked ST22 and found the following dump: 'DYNPRO_SEND_IN_BACKGROUND'. However when I tried executing it using SE37, the function module works fine.
    Any ideas?
    Ricky

    Hello Ricky,
    to my guts feeling that should be fine, but I have never used call dialog in such a scenario. If I were in your shoes I would try to break down the problem:
    - Is it of general nature?
    - Is it specific to this dialog?
    To distinquish that I would write the most basic dialog and use it the same way as the target one. If this fails too, using FuBa´s with call dialog seems to be not possible => try to avoid that situation. If the test succeeds, well the hunt for the needle in the haystack is open.
    Good Luck
      Klaus

  • Calling another program in the print program through FORM ENTRY

    Hi All,
    Have a requirement that I need to submit the program with variant to a print program.
    But it is giving dump "Statement "SUBMIT" is not allowed in this form" while executing through VF04.
    I have tried by using CALL FUNCTION  "func" in update task .Inside the "func"  in I have coded the logic of
    submit program using selection-set VARIANT.
    Even then while executing through VF04 got the dump "DYNPRO_SEND_IN_BACKGROUND" and "POSTING_ILLEGAL_STATEMENT ".
    Kindly advise to resolve the issue.

    Hi,
    PLease make sure that u r using both smartforms and report..
    Once the function called the report program, whether control back to the print program..
    Using debugger please check..
    put a break-point in your program and find where that dump is arised..
    whether u want report only or smartform only...
    If the same problem arises again,
    Paste your report program code inside the print program instead of using SUBMIT..
    let me know what the issue u r facing
    regards
    vijay

  • Is it possible to launch internet services from a BSP?

    Hi. I've created a BSP in SRM and what we want to do is allow users to be able to choose from a few options, 1 of which needs to then open the SRM shopping transaction, which is an internet service.
    I have tried calling the transaction which points to the service, but get a dump "DYNPRO_SEND_IN_BACKGROUND". I think it might be trying to call it as a gui transaction.
    Does anyone know if it is possible to call it as a web service, and if so how?
    Any help would be very much appreciated.
    Regards,
    Dave.

    Hi. I am trying to open the SRM shopping cart transaction BBPSC02 from a BSP page.
    I only get the JS error when calling it from BSP, when I call it from SRM menu it is fine.
    The BSP is also called from within SRM, I put it in a role.
    What we want exactly is for a user to log into SRM then use the BSP. The BSP will have a few options, 1 of them is to create a shopping cart. If the user chooses that option then we need to call the shopping cart transaction BBPSC02 and it needs to work as normal.
    To be honest if we can get all functions working by being called from the BSP then we could bypass logging into SRM and just call the BSP, but we would need to be able to call all SRM transactions to do it this way.
    Thanks a lot for your help.
    Regards,
    Dave.

  • 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.

  • SDCCN - Dump with "DYNPRO_SEND_IN_BACKGROUND"

    Hello,
    I'm facing an error in SDCCN functionality. When checking Early Watch Alerts with transaction DSWP I get a red alert flag with a system. When trying to reach system with RFC connection, I get an error message "Dynpro without connection to user".
    In target system I get a dump with runtime error "DYNPRO_SEND_IN_BACKGROUND".
    I found a few notes but none of them in relationship with SDCCN (49730, 1551958, 1520800).
    Does anybody know this problem and can help me out?
    Thanks in advance,
    Julia

    Hi Julia,
    This error is usually raised when a non-dialog user is specified for dialog processing.
    On the red flag icon in DSWP, that would be the Trusted RFC you'd be using, so for that RFC, in SM59
    what kind of user is being specified. Have you tried checking the box use current user?
    In Solman in DSWP in the client tab you can also test the Trusted RFC and ensure the smread and smtrusted RFCs are speciofied for Data COllection and Read Analysis.
    Regards,
    Paul

Maybe you are looking for