Dump in DYNPRO_SEND_IN_BACKGROUND program in SAPMSYST

Hi ,
Runtime Errors         DYNPRO_SEND_IN_BACKGROUND
ABAP Program           SAPMSYST
how to solve this issues . what is the exact proposed solution
Category               ABAP Programming Error
Runtime Errors         DYNPRO_SEND_IN_BACKGROUND
Except.                CX_SY_SEND_DYNPRO_NO_RECEIVER
ABAP Program           SAPMSYST
Application Component BC-SEC
Short text
     Screen output without connection to user.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPMSYST" had to be terminated becau
     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: "SAPMSYST " 0040.
    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"
   "SAPMSYST" or " "
   "SYSTEM-EXIT"
   If you cannot solve the problem yourself and want to send an error
   notification to SAP, include the following information:
   1. The description of the current problem (short dump)
      To save the description, choose "System->List->Save->Local File
   (Unconverted)".
   2. Corresponding system log
      Display the system log by calling transaction SM21.
      Restrict the time interval to 10 minutes before and five minutes
   after the short dump. Then choose "System->List->Save->Local File
   (Unconverted)".
   3. If the problem occurs in a problem of your own or a modified SAP
   program: The source code of the program
      In the editor, choose "Utilities->More
   Utilities->Upload/Download->Download".
Information on where terminated
    Termination occurred in the ABAP program "SAPMSYST" - in "SYSTEM-EXIT".
    The main program was "SAPMSYST ".
    In the source code you have the termination point in line 0
    of the (Include) program " ".

Hi Sai,
Message clearly says that it is trying to call a screen in background when you execute your program.
Please check and debug where it is calling a screen and at what condition. Is it from standard code or from some enhancement.
Richa.

Similar Messages

Short dump in standard program

Hi Friends,
below description is short dump for standard program.
Please see the below and help me how to correct the program.
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Internal error: Program   , include   , form   .
Technical information about the message:
Diagnosis
     An unexpected error has occurred.
Procedure
     If you can reproduce the error, contact the SAP Hotline quoting the
     error number.
Message classe...... "GR"
Number.............. 214
How to correct the error
Probably the only way to eliminate the error is to correct the program.
                                                                                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:
"MESSAGE_TYPE_X" C
"SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"
"F80_FILL_COL_TAB"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
                                                                                2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
Thanks & Regards,
Sree
Edited by: adepus on Oct 7, 2009 12:39 PM
Edited by: adepus on Oct 7, 2009 12:39 PM

Hi Clemens,
I am getting a dump error as shown below. Could you please find some resolution for this issue. we just made some changes to the transaction GS02(Just added a GL account to one of the sets).
Runtime Error MESSAGE_TYPE_X
ShrtText
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
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
Short text of error message:
Internal error: Program , include , form .
Technical information about the message:
Diagnosis
An unexpected error has occurred.
Procedure
If you can reproduce the error, contact the SAP Hotline quoting the
error number.
Message classe...... "GR"
Number.............. 214
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"MESSAGE_TYPE_X" C
"SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"
"F80_FILL_COL_TAB"
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.
Source Code
79 MESSAGE x214.
80 ENDIF.
81 PERFORM e08_read_object_index(sapfgsb0)
82 USING fcolumns-dim_index.
83 IF c-subrc 0. MESSAGE x214. ENDIF.
84 c_dsentry = c-tval-from.
85 IF c_dsentry '='.
86 READ TABLE data_fields BINARY SEARCH
87 WITH KEY tab = rep_table
88 dsentry = c_dsentry.
>>>> IF sy-subrc 0. MESSAGE x214. ENDIF.
90 ENDIF.
91 WHEN OTHERS.
92 c_dsentry = '*'.
93 ENDCASE.
94 ENDIF.
Regards,
Pavan

What are the major situations to go to the short dump in abap programming?

What are the major situations to go to the short dump in abap programming?

Hi,
The major situations that an ABAP Program can result a dumb are as follows...
1) Poor coding i.e., if the data in the data base is less, then even a poor code can give you the result. But when you transport the program into Production, then there the same program will give you a dump, resulting 'TIMED OUT' error. So performance tunning is required for each and every program.
2) while calling a function module.
3) extracting of data into fields which are not type casted.
4) in case of x/y value, one should check the value of 'y' should not be zero, else a dump will result.
these are few which i can give for time being........

GETWA_NOT_ASSIGNED dump error in program SAPLSLVC

Hi,
    I am using REUSE_ALV_GRID_DISPLAY FM to print ALV report and getting GETWA_NOT_ASSIGNED dump error in program SAPLSLVC.
I check the SAP Note for this error.. no luck..
Any one face similar issue.
Cheers
Senthil

Hi,
    Here is my source code.
Layout
it_layout-no_input          = 'X'.
it_layout-colwidth_optimize = 'X'.
it_layout-zebra = 'X'.
it_layout-get_selinfos = 'X'.
it_layout-box_fieldname = 'SEL'.
it_layout-detail_initial_lines = 'X'.
it_layout-detail_titlebar = 'Details'.
ALV
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            i_callback_pf_status_set = y_pfstatus
            i_callback_program      = y_repid
           i_callback_user_command = 'USER_COMMAND'
            i_grid_title           = y_outtext
            is_layout               = it_layout
            it_fieldcat             = it_fieldcat[]
            i_save                  = 'X'
       TABLES
            t_outtab                = it_out
       EXCEPTIONS
            program_error           = 1
            OTHERS                  = 2.
I am still getting dump error.
Any parameter missing..!
Thanks
Senthil

ABAP Dump : TSV_TNEW_PAGE_ALLOC_FAILED in program SAPLCOM_PARTNER_OB

Hi All,
            I am getting the dump TSV_TNEW_PAGE_ALLOC_FAILED in program SAPLCOM_PARTNER_OB in LCOM_PARTNER_OB in line 165.
Short text
    No more storage space available for extending an internal table.
What happened
You attempted to extend an internal table, but the required space was not available.
The error is occuring in line
INSERT GS_CURRENT_PARTNERSET INTO TABLE GT_PARTNERSETS.
CT_PARTNER[] = GS_CURRENT_PARTNERSET-PARTNER[]. "#EC ENHOK
ENDIF.
   The amount of storage space (in bytes) filled at termination time was:
   Roll area...................... 6221152
   Extended memory (EM)........... 3909511400
   Assigned memory (HEAP)......... 2000692032
   Short area..................... " "
   Paging area.................... 417792
   Maximum address space.......... 18446697117078316543
The dump is occuring in the standard program. Is there any note for this.
Kindly help.
Thanks,

>             I am getting the dump TSV_TNEW_PAGE_ALLOC_FAILED in program SAPLCOM_PARTNER_OB in LCOM_PARTNER_OB in line 165.
>    Extended memory (EM)........... 3909511400
>    Assigned memory (HEAP)......... 2000692032
> The dump is occuring in the standard program. Is there any note for this.
Did you try a notes search?
This program is already using roughly 6 GB of RAM which seems quite a lot.
What transaction/process is triggering this error? It may be that a user just selects too much data.
Markus

Dump ITAB_ILLEGAL_SORT_ORDER_BLK in program RBDAPP01

Hi Colleagues,
I am facing ITAB_ILLEGAL_SORT_ORDER_BLK dump while executing program RBDAPP01.
Please help me on this.
Thanks & Regards
Amit Sharma

Hi Savitha,
I have searched in SAP service market place. I found a total of 63 notes for dump ITAB_ILLEGAL_SORT_ORDER_BLK. But none of them will help me. This job is working fine but only one Idoc is in status 64, which is leading the job to dump. I have seen all Idocs are getting successfully processed except that one.Only solution I believe I have is to create a Idoc with same data in development system and debug in inbound function module mode. But for that I have to manually copy the idoc from production to development via WE19 Tcode. Is there any easier way to create a replica of Idoc.
Thanks & Regards
Amit Sharma

Dump VT02n - DYNPRO_SEND_IN_BACKGROUND

Hi All,
I m getting a dump - the dump says the below error :
"DYNPRO_SEND_IN_BACKGROUND" " "
"SAPMV56A" or " "
"TRANSPORT_LESEN"
The current ABAP program "SAPMV56A" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Can any tell - what could be the reason of the dump ?
This happend only in Production, not on other systems - hence we dont even have rigths ro debug in PRD system...so if any one has come across this error, it will be easy for us to sugges to basis guys/FD folks.
Thank you !!
Senthil

Short text
Screen output without connection to user.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPMV56A" 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: "SAPMV56A " 1011.
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" " "
"SAPMV56A" or " "
"TRANSPORT_LESEN"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:

A short dump in the program with a certain error message...

Hi all,
I'd run a program to do an insertion into a customized table.
During the run, it popped up a short dump error messages below :
value larger than specified precision allows for this column#TC020 %M
I've search for that column #TCO20 .... and i couldn't find it in my custom table...
Why SAP gave such a hard description on the error found? I can't determine which field/column in my table that is causing the error dump during INSERT event in my program.
Is there any explanation on that message that could help me?
Thanks
William Wilstroth

Hi,
Better u seee again where u r getting error i the code . still if u r not getting see in dump analysys(ST22) and select
no:8 -- which is source code extract where u can get correct error inf.
Plz reply me.
Regards
Durgaprasad.

Short Dump-Syntax error program"CL_RSD_MULTIPROV==CP" after EHP1SP5 upgrade

Hi,
MultiProvider Activation/Display data is resulting into short dump with following text
Error in the ABAP Application Program
The current ABAP program "CL_RSD_MULTIPROV_CHECK========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_RSD_MULTIPROV==============CP " in include
"CL_RSD_MULTIPROV==============CM010 " in
line 1:
"Method "CHECK_LINITFL" is not declared or inherited in class "CL_RSD_M"
"ULTIPROV". -"
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "CL_RSD_MULTIPROV_CHECK========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
We have recently upgraded to EHP1SP5. We noticed this issue just after that.
Regards,
PD

Hi,
Please check the note 1461401.
1461401 - System error in the program CL_RSD_MULTIPROV_CHECK
This note should help you.
Regards,
Rafael

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.

Short dump error in program SAPMV50A after modification

Dear gurus
i have done some modification in vl02n through Badi and it is working fine in Development server.
when i transport it to quality server and test it
it giving a short dump in vl02n while vl01n is working perfectly fine and showing my modification too..
below is the error mentioned
Database error text........: "Unsupported database type in parameter/column
    (168)."
   Internal call code.........: "[RSQL/READ/LIKP ]"
   Please check the entries in the system log (Transaction SM21).
   If the error occures in a non-modified SAP program, you may be able t
   find an interim solution in an SAP Note.
   If you have access to SAP Notes, carry out a search with the followin
   keywords:
   "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
   "SAPMV50A" or "MV50AFDB"
   "LIKP_SELECT"
   If you cannot solve the problem yourself and want to send an error
   notification to SAP, include the following information:
Please help
Regards
Saad Nisar

i have created two append structure in standard tables of LIKP & LIPS which are activated and so as LIKP and LIPS
my Badi is also activated and my customized program is also activated.
While making outbound delivery in Quality server it works fine but when i want to make changes in that created delivery it throws dump error
short text
   SQL error in the database when accessing a table.
issing RAISING Clause in Interface
   Program                                 SAPMV50A
   Include                                 MV50AFDB
   Row                                     14
   Module type                             (FORM)
   Module Name                             LIKP_SELECT
rigger Location of Exception
   Program                                 SAPMV50A
   Include                                 MV50AFDB
   Row                                     20
   Module type                             (FORM)
   Module Name                             LIKP_SELECT

ABAP Dump GETWA_NOT_ASSIGNED_RANGE for program /SDF/CL_EM_DUMP_COLLECTOR=====CP

Hello,
I am getting ABAP runtime error GETWA_NOT_ASSIGNED_RANGE every 10 minutes in my ECC Production system. This dump is occurring for program /SDF/CL_EM_DUMP_COLLECTOR=====CP with short text as "Field symbol is not assigned".
Error Analysis:
"A field symbol that was not assigned was accessed
(data segment no. "-1").
The field symbol is no longer assigned because there was an attempt
makde previously in a Unicode program to set the field symbol using
ASSIGN with offset and/or length specification. Here, the memory
addressed by the offset/length specification was not within the
allowed area."
Information on where terminated:
"Termination occurred in the ABAP program "/SDF/CL_EM_DUMP_COLLECTOR=====CP" -
     in "GET_FIELDTABLE".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 51
    of the (Include) program "/SDF/CL_EM_DUMP_COLLECTOR=====CM005"."
Server-Side Connection Information:
"Information on caller of Remote Function Call (RFC):
    System.............. "Solution Manager"
    Installation Number. " "
    Database Release.... 702
    Kernel Release...... 720
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchronous and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. Prod Client
    User................ "SolMan user"
    Transaction......... " "
    Call Program........."SAPLE2EEM_DATA_COLLECTION"
    Function Module..... "/SDF/E2EEM_GET_DATA"
    Call Destination.... "SM_<ECC_PROD>_READ"
    Source Server....... "Solution Manager"
    Source IP Address... "Solution Manager"
    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0"
I searched for SAP notes and other SCN discussion but could not find relevant information. Can someone please assist me? Thanks.
Tanay

Hi Srivastava,
What process or transaction you are executing, when you got this dump, please share the detail.
In SAP there so many areas where we can have this ABAP dump, please also share the snap shot in ST22 " How to Correct" part of dump which carries the exact program name e.g. in below snapshot program name, short text, etc is given to search SAP note.
Please also refer to the following sap notes:
1840910 - Dump CHECK_SELOPT_ILLEGAL_SIGN
1729771 - Collective corrections as of ST-PI 2008_1 SP06
1011229 - ST-PI: Corrections for E2E Diagnostics
Regards
Javed

Core dump with deque program

Hey all, here is the small deque program...
When this program was run for upto 529 entires it works fine. When tried for 530 entries it dumps core.
By the way instead of push_front if we use push_back, it works fine. However, we are facing this problem with Sun ONE Studio 11 after our successful compiler upgrade.
If any one has any idea why the following program dumping core with 530 entires?
cut and paste and compile and run ./deque 530, you will receive a core dump in Solaris 10/Sun one Studio 11 (CC 5.8 compiler). Important: make sure you run Solaris 10/Sun One Studio 11 CC 5.8 compiler compiled code.
IT IS NOT DUMPING CORE IN OLDER VERSIONS....
==========deque.cc===================
#include <deque>
#include <iostream>
int main( int argc, char* argv[] )
std::deque< int > container;
std::cout << "maxSize:" << container.max_size() << "\n";
int last( 530 );
if ( argc > 1 )
last = atoi( argv[ argc - 1 ] );
std::cout << "Building to " << last << "\n";
for ( int i = 0; i < last; ++ i )
container.push_front( i );
int idx = 0;
for ( std::deque< int >::const_iterator
iter = container.begin();
iter != container.end();
++ iter, ++ idx )
std::cout << idx << ": " << (*iter) << "\n";
std::cout << "maxSize:" << container.max_size() << "\n";
return 0;
The pstack output from core file...
core 'core.deque' of 3869: ./deque 530
00011a40 main (2, ffbfd7ec, ffbfd758, ffbfd768, ffbfd768, ffbfd630) + 2b8
00011358 _start (0, 0, 0, 0, 0, 0) + 108

The patch that fixes CR 6363210 involves the header files for the deque implementation in Sun Studio 10 and 11. The runtime library /usr/lib/libCstd.so.1 also has that code in it. Whether you generate the affected functions inline in your code, or pick them up from the runtime library, depends on various compiler options.
If you have not installed the latest C++ runtime library patch and get these functions from the runtime library, you will not have the benefit of the bug fix.
You can get all current patches here:
http://developers.sun.com/sunstudio/downloads/patches/index.jsp
If after installing current patches you still have the problem, please post a stand-alone code example that shows the problem.

Regarding dump in print program for form 16 tranction code PC00_M40_F16

Hi gurus,
           While executing the tcode PC00_M40_F16 I am getting short dump. details are given
           below. here K1 is Payroll area. its data type is char2 and program is standard program
           so why its generating dump, please gide, thanks
Runtime Errors         CONVT_NO_NUMBER.
Unable to interpret "K1 " as a number.
22|*&      Form READ_INFOTYPES                                                                |
23
24
     Read the Employee Data from the Infotypes
25
26
FORM READ_INFOTYPES.
27
28
RP-PROVIDE-FROM-LAST P0001 SPACE PBEGDA PENDDA.
29
30
RP-PROVIDE-FROM-LAST P0002 SPACE PBEGDA PENDDA.
31
IF PNP-SW-FOUND EQ 0.
32
MESSAGE S089(HRPADIN01) WITH '0002' PERNR-PERNR PBEGDA PENDDA.
33
There is no infotype & for personnel no & from period & to &
34
PERFORM BUILD_ERROR TABLES HR_ERROR
35
USING SPACE SY-MSGID SY-MSGNO
36
SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
37
REJECT.
38
ENDIF.
39
40
RP-PROVIDE-FROM-LAST P0021 '11' PBEGDA PENDDA.
41
42
RP-PROVIDE-FROM-LAST P0185 '02' PBEGDA PENDDA.
43
44
SELECT SINGLE KWERT FROM T511K INTO KWERT
45
WHERE MOLGA = CALCMOLGA
46
AND KONST = 'ADDSS'
47
AND BEGDA <= PBEGDA
48
AND ENDDA >= PBEGDA.
49
>>>>>
RP-PROVIDE-FROM-LAST P0006 KWERT PBEGDA PENDDA.
51
52
'AND PNPESSCF = SPACE' has been added below for ESS changes
53
IF PNP-SW-FOUND EQ 0 AND PNPESSCF = SPACE.
54
MESSAGE S089(HRPADIN01) WITH '0185' PERNR-PERNR PBEGDA PENDDA.
55
There is no infotype & for personnel no & from period & to &
56
PERFORM BUILD_ERROR TABLES HR_ERROR
57
USING SPACE SY-MSGID SY-MSGNO
58
SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
59
ENDIF.
60
61
ENDFORM.                              " READ_INFOTYPES
62
63
64
*&      Form FILL_MAIN_TAB
65
66
FORM FILL_MAIN_TAB.
67
Loop at RT and fill MAIN_TAB with required wage types
68
CLEAR MAIN_TAB.
69
CLEAR EMPLOYER_TAX.

Hi Mani,
Check if u have implemented BAdI for the address 'HR_IN_ER_ADDRESS'.
if yes then check the SAP service market place, as SAP has released one new for the same. But its applicable only if BAdI is implemented.
Let me know if u r still any issue.
Regards,
Praveen

Short Dump in ABAP program "SAPLOLEA" - in "AC_SYSTEM_FLUSH

Hi Can You tell me the reason and solution for this dump,
Information on where terminated
    Termination occurred in the ABAP program "SAPLOLEA" - in "AC_SYSTEM_FLUSH".
    The main program was "ZXXX ".
    In the source code you have the termination point in line 29
    of the (Include) program "LOLEAU02".

The only input I got from production is
User and Transaction
    Client.............. 300
    User................ "xxxxx"
    Language key........ "E"
    Transaction......... "Zaaa"
    Program............. "SAPLOLEA"
    Screen.............. "SAPLSLVC_FULLSCREEN 0500"
    Screen line......... 0
   Information on where terminated
    Termination occurred in the ABAP program "SAPLOLEA" - in "AC_SYSTEM_FLUSH".
    The main program was "Zaaaa ".
    In the source code you have the termination point in line 29
    of the (Include) program "LOLEAU02".

Dump in DYNPRO_SEND_IN_BACKGROUND program in SAPMSYST

Similar Messages

Maybe you are looking for