DYNPRO_NOT_FOUND in abap program dumps in st22

Hi All,
We are facing an issue in Abap dumps
Run Time error DYNPRO_NOT_FOUND
Termination occurred in the ABAP program "MP058400" - in "SET_INIT_TAB".
The main program was "MP058400 ".
In the source code you have the termination point in line 49
of the (Include) program "MP058420".
I have an idea that it is releated to Screens but its a standard Tcode PA40 and info type 584.
Please suggest the how can i solve the dump.
Regards
Harsha Teja

Hi Deepak,
We had installed ECC 6.0 Ehp5 recently and released to HCM consultant they are testing PA30 infotype 584.
Regrads
Harsha Teja

Similar Messages

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

CONVT_NO_NUMBER Dump error in Process Chain Abap Program

Hi Experts,
The daily running process chain is failed at ABAP program with the error CONVT_NO_NUMBER.
The reason for the exception is:
The program attempted to interpret the value "40-799" as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
I am not familiar with ABAP.
Please suggest me how to proceed..
Thanks
<BMP>

Hi,
In ST22
Short text
    Unable to interpret "40-799" as a number.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', was not
     caught in
    procedure "FM_DIR_LIST" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    The program attempted to interpret the value "40-799" as a number, but
    since the value contravenes the rules for correct number formats,
    this was not possible.
I am trying post the code but SDN is not accepting more than 15000Char's
So can i get ur (mail) details
So that i can send u the exact code...
Thanks,
BMP

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

DYNPRO_NOT_FOUND : ABAP program "MP058400"

Dear Sir
Category ABAP Programming Error
Runtime Errors DYNPRO_NOT_FOUND
ABAP Program MP058400
Application Component PA-PA-IN
Dynpro does not exist.
The system attempted to use dynpro 0000 in program "MP058400".
This dynpro does not exist.
Kindly help for this
Regards
HARISH.B

Whether you have enhanced the code, any new customization lately?

ABAP program showing dump in Portal

Hi,
When we are trying to run an ABAP program in Portal its generating a dumb and a part of the message is
"The termination was triggered in function "getwa_abswa" of the SAP kernel, in line 1044 of the module "//bas/700_REL/src/krn/runt/abgetwa.c#4".
The internal operation just processed is "PAR2".
Internal mode was started at 20080115115135."
Error in the ABAP Application Program
The current ABAP program "SAPLSLVC" had to be terminated because it has come across a statement that unfortunately cannot be executed.
When the selection criteria is reduced the report is running. Can anyone suggest to how to overcome this problem.
Thanks n Regards,
Sasha.

Hi,
The dynamic table that is generated is not converting the exact output length in case of packed numbers.
Foe eg : If there is an packed field of length 7 , the dynamic table is converting it to Char 7 , but the actual output length of Pack 7 is 15.Hence it is giving short dump saying that Internal Table length is not sufficient.
Probably it might have worked for smaller tables for you because you might not have used Packed field in there.
Regards,
Vijay.

Can't open layout getting Dump in ST22

Hi All,
I am getting an layout no display and dump ST22 with the following details for few users, It seems the data set they try to open via the layout is locked but ususally when the layout is open and they select that version then they get a message ' this is locked or somthing', but I have never seen they can't even open the layout. Specially, with only one layout. Is there a table or somthing I can release that locked for this user? OR how can I resolve this issue!!! I am in SEM 4.0 Add-on into BW3.0B
The termination occurred in the ABAP program "SAPLUPC_DATASLICE" in
"UPC_DATASLICE_CHASEL_CHECK".
The main program was "SAPMHTTP ".
The termination occurred in line 162 of the source code of the (Include)
program "LUPC_DATASLICEU10"
of the source code of program "LUPC_DATASLICEU10" (when calling the editor
1620).

Hi,
I think the problem is related to Active/Deactive Dataslices.
In your case Dataslices is ACTIVE ??
Please put a break point in FM UPC_DATASLICE_CHASEL_CHECK and check exactly where are you getting the dump.
Just to analyse the problem , deactivate it and check whether you are getting the dump or not ?
Thanks
pratyush

ABAP program "SAPLCNTL" in "CHECK_OO": MESSAGE_TYPE_X

Hi,
I have a problem with a program with ALV-list. Sometimes it terminates with a dump. I can not reproduce the dumps and I can not find the reason for it. I do not know, if it only terminates on some clients.
In the program the alv table is refreshed with CL_GUI_ALV_GRID=>REFRESH_TABLE_DISPLAY. After this there is also a statement CALL METHOD cl_gui_cfw=>flush.
Can anyone help?
Kindly regards
Frank
Runtime Error          MESSAGE_TYPE_X
Date and Time          11.11.2008 11:24:28
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:
    Control Framework: Invalid Processing of ABAP Object Control
Technical information about the message:
     Diagnosis
You want to edit a control created with ABAP objects techniques
         (class-based Control Framework) using a function module (function
         module-based Control Framework). The system does not support this.
         The Class ID of the control is SAP.DataProvider.1.
     System response
The transaction is terminated.
     Procedure
Contact the person responsible for the SAP System.
    Message classe...... "DC"
    Number.............. 007
    Variable 1.......... "SAP.DataProvider.1"
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
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
"SAPLCNTL" or "LCNTLF01"
    "CHECK_OO"
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....... "gl3ap4"
    Network address.......... "194.69.46.206"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C2809E4C00"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 8
    Short dump setting....... "full"
Database server.......... "glince215"
    Database type............ "ORACLE"
    Database name............ "GL3"
    Database owner........... "SAPSR3"
Character set............ "C"
SAP kernel............... "640"
    Created on............... "Feb 18 2008 23:36:16"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
Patch level.............. "221"
    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, AIX 1 6"
Memory usage.............
    Roll..................... 16192
    EM....................... 16759424
    Heap..................... 0
    Page..................... 139264
    MM Used.................. 4672968
    MM Free.................. 3703952
    SAP Release.............. "640"
User and Transaction
Client.............. 001
    User................ "PB754"
    Language key........ "D"
    Transaction......... "ZVLA "
    Program............. "SAPLCNTL"
    Screen.............. "ZTCOCKPT 2000"
    Screen line......... 4
Information on where terminated
    The termination occurred in the ABAP program "SAPLCNTL" in "CHECK_OO".
    The main program was "ZTCOCKPT ".
The termination occurred in line 178 of the source code of the (Include)
     program "LCNTLF01"
of the source code of program "LCNTLF01" (when calling the editor 1780).
Source Code Extract
Line SourceCde
148 *---------------------------------------------------------------------*
149 *       FORM %_CONTROL_DISPATCH                                       *
150 *---------------------------------------------------------------------*
151 *
152 *---------------------------------------------------------------------*
153 * --> OKCODE                                                        *
154 *---------------------------------------------------------------------*
155 FORM %_CONTROL_DISPATCH.
156 * CALL FUNCTION 'CONTROL_DISPATCH'
157 *      EXPORTING
158 *           FCODE        = SY-UCOMM
159 *      EXCEPTIONS
160 *           CB_NOT_FOUND = 1
161 *           OTHERS       = 2.
162 ENDFORM.
163
164 FORM REGISTERGLOBALOCXEVENT
165 USING SHELLID TYPE I EVENT TYPE I.
166     CALL METHOD OF CL_GUI_OBJECT=>H_GUI 'RegisterGlobalOCXevent'
167       NO FLUSH
168       EXPORTING #1 = SHELLID
169                 #2 = EVENT.
170 ENDFORM.
171
172 form check_OO using p_handle type cntl_handle.
173 * check sy-uname = 'KSCHMIDT'.
174   call method cl_gui_cfw=>get_subscriber_by_id
175        exporting shellid = p_handle-shellid
176        exceptions others = 1.
177   if sy-subrc = 0.
>>>>>     message X007 with p_handle-clsid.
179   endif.
180
181 endform.
182
183 form check_oo_2 using p_shellid type i.
184   data l_handle type cntl_handle.
185 * check sy-uname = 'KSCHMIDT'.
186   call method cl_gui_cfw=>get_subscriber_by_id
187        exporting shellid = p_shellid
188        exceptions others = 1.
189   if sy-subrc = 0.
190     call function 'CNTH_HANDLE_BY_SHELLID'
191          exporting shellid = p_shellid
192          importing h_control = l_handle
193          exceptions others = 1.
194     message X007 with l_handle-clsid.
195   endif.
196 endform.
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 12
SY-DBCNT 1
SY-FDPOS 1
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY STAT2000
SY-UCOMM NSEL
SY-TITLE ZTCOCKPT Cockpit: Transporte Aufträge Lieferungen
SY-MSGTY X
SY-MSGID DC
SY-MSGNO 007
SY-MSGV1 SAP.DataProvider.1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No.   Ty.          Program                             Include                             Line
      Name
11 FORM         SAPLCNTL                            LCNTLF01                              178
      CHECK_OO
10 FUNCTION     SAPLCNTL                            LCNTLU13                               16
      CONTROL_DESTROY
9 FUNCTION     SAPLCNDP                            LCNDPU07                               22
      DP_DESTROY
8 FUNCTION     SAPLCNDP                            LCNDPU10                              103
      DP_CONTROL_ASSIGN_TABLE
    7 METHOD       CL_GUI_ALV_GRID_BASE==========CP    CL_GUI_ALV_GRID_BASE==========CM01U    37
      CL_GUI_ALV_GRID_BASE=>SET_TOOLBAR_BUTTONS
    6 METHOD       CL_GUI_ALV_GRID===============CP    CL_GUI_ALV_GRID===============CM01M    52
      CL_GUI_ALV_GRID=>SET_TOOLBAR
    5 METHOD       CL_GUI_ALV_GRID===============CP    CL_GUI_ALV_GRID===============CM01P   432
      CL_GUI_ALV_GRID=>SOFT_REFRESH_TABLE_DISPLAY
    4 METHOD       CL_GUI_ALV_GRID===============CP    CL_GUI_ALV_GRID===============CM00T   116
      CL_GUI_ALV_GRID=>REFRESH_TABLE_DISPLAY
    3 MODULE (PBO) ZTCOCKPT                            ZTCOCKPT                              652
      PBO_ALV_2000
2 FORM         ZTCOCKPT                            ZTCOCKPT                              167
      ALVAUSGABE
1 EVENT        ZTCOCKPT                            ZTCOCKPT_INC                          213
      START-OF-SELECTION
Chosen variables
Name
Val.
No.      11 Ty.          FORM
Name CHECK_OO
SY-REPID
SAPLCNTL
0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454445422222222222222222222222222222222
    310C3E4C00000000000000000000000000000000
%_VIASELSCR
0
4
P_HANDLE-SHELLID
128
0008
0000
BS_CENTER
768
0000
0030
%_DUMMY$$
0000
0000
2222
0000
FONT_ITALIC
1
0000
0001
SY-SUBRC
0
0000
0000
SY-XFORM
XAB_READ
000000000000000000000000000000
    000000000000000000000000000000
    544554442222222222222222222222
    812F25140000000000000000000000
SY-MSGID
DC
00000000000000000000
00000000000000000000
44222222222222222222
43000000000000000000
SS_SIMPLE
11
0000
000B
SS_BLACKRECT
4
0000
0004
SPACE
0
0
2
0
SY-MSGNO
007
000
000
333
007
SY-MSGV1
SAP.DataProvider.1
00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    54524676576766672322222222222222222222222222222222
    310E414102F69452E100000000000000000000000000000000
P_HANDLE-CLSID
SAP.DataProvider.1
0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    5452467657676667232222222222222222222222222222222222222222222222222222
    310E414102F69452E10000000000000000000000000000000000000000000000000000
SY-MSGV2
00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
SY-MSGV3
00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
SY-MSGV4
00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
No.      10 Ty.          FUNCTION
Name CONTROL_DESTROY
NO_FLUSH
X
0
0
5
8
H_CONTROL
OBJHOLE2##                                   7263                                       ####
    00000000FF000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    00000000FF000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    44444443FF222222222222222222222222222222222223333222222222222222222222222222222222222222080022
    F2A8FC52FF000000000000000000000000000000000007263000000000000000000000000000000000000000000A00
BS_DEFPUSHBUTTON
1
0000
0001
BS_LEFT
256
0000
0010
THIS_DUMMY_VALUE
0
0000
0000
BS_PUSHBUTTON
0
0000
0000
H_CONTROL-OBJ+16(4)
-1
FFFF
FFFF
SYST-REPID
SAPLCNTL
0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454445422222222222222222222222222222222
    310C3E4C00000000000000000000000000000000
H_CONTROL-HANDLE_TYPE
NO_OC
0000000000
0000000000
4454422222
EFFF300000
CNTL_TYPE_OCX
OCX
0000000000
0000000000
4452222222
F380000000
CNTL_TRUE
1
0000
0001
IS_ITSAC_767A497173BF11D28BB
0
0
2
0
AC_EXPORTS_4E238C5273BF11D28BB
    Table[initial]
AC_EXPO_WA_4E238C5273BF11D28BB
000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222233333333322222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No.       9 Ty.          FUNCTION
Name DP_DESTROY
H_DP
OBJHOLE2##                                   7263                                       ####
    00000000FF000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    00000000FF000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    44444443FF222222222222222222222222222222222223333222222222222222222222222222222222222222080022
    F2A8FC52FF000000000000000000000000000000000007263000000000000000000000000000000000000000000A00
G_STRETCH_UNICODE_COLS_VALID
    X
0
0
5
8
%_DUMMY$$
0000
0000
2222
0000
SY-SUBRC
0
0000
0000
SYST-REPID
SAPLCNDP
0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454444522222222222222222222222222222222
    310C3E4000000000000000000000000000000000

Hi Frank,
I doubt it is related to function 'LVC_FIELDCATALOG_MERGE' since the current SAP help documentation talks about using this function for the purpose that I'm sure you are using it. The short dump states that the problem is caused by the use of an "old" function-module-based control framework function combined with the class-based OO CFW.
     Diagnosis
You want to edit a control created with ABAP objects techniques
         (class-based Control Framework) using a function module (function
         module-based Control Framework). The system does not support this.
If you look at the call sequence in the short dump, function module 'CONTROL_DESTROY' is being called (which then calls function 'CHECK_OO' from which the error is sent). Function module 'CONTROL_DESTROY' is in function group CNTL which is part of the "old" function-module-based CFW.
Since the 'CONTROL_DESTROY' function is ultimately called as a result of your Z-program legitimately calling the standard SAP method CL_GUI_ALV_GRID=>REFRESH_TABLE_DISPLAY, I'd say you might want to consider opening a customer message with SAP providing as much detail and background as possible. But before you bother to do that (or while you are waiting to hear back from SAP) you may want to double-check your Z-program to make sure you aren't calling some other function modules from function groups CNTL or CNT0 (the "old" CFW function modules).
I've included just the call sequence from your short dump here for easier reference. Notice the order of the calls from 1 to 11, ending with functions 'CONTROL_DESTROY' and 'CHECK_OO'. I think 'CONTROL_DESTROY' may be causing the problem (??):
Active Calls/Events
No.   Ty.          Program                             Include                             Line
      Name
11 FORM         SAPLCNTL                            LCNTLF01                              178
      CHECK_OO
10 FUNCTION     SAPLCNTL                            LCNTLU13                               16
      CONTROL_DESTROY
9 FUNCTION     SAPLCNDP                            LCNDPU07                               22
      DP_DESTROY
8 FUNCTION     SAPLCNDP                            LCNDPU10                              103
      DP_CONTROL_ASSIGN_TABLE
    7 METHOD       CL_GUI_ALV_GRID_BASE==========CP    CL_GUI_ALV_GRID_BASE==========CM01U    37
      CL_GUI_ALV_GRID_BASE=>SET_TOOLBAR_BUTTONS
    6 METHOD       CL_GUI_ALV_GRID===============CP    CL_GUI_ALV_GRID===============CM01M    52
      CL_GUI_ALV_GRID=>SET_TOOLBAR
    5 METHOD       CL_GUI_ALV_GRID===============CP    CL_GUI_ALV_GRID===============CM01P   432
      CL_GUI_ALV_GRID=>SOFT_REFRESH_TABLE_DISPLAY
    4 METHOD       CL_GUI_ALV_GRID===============CP    CL_GUI_ALV_GRID===============CM00T   116
      CL_GUI_ALV_GRID=>REFRESH_TABLE_DISPLAY
    3 MODULE (PBO) ZTCOCKPT                            ZTCOCKPT                              652
      PBO_ALV_2000
2 FORM         ZTCOCKPT                            ZTCOCKPT                              167
      ALVAUSGABE
1 EVENT        ZTCOCKPT                            ZTCOCKPT_INC                          213
      START-OF-SELECTION
Regards,
Jamie
P.S. Please report back here if you find a solution (or if SAP finds one as a result of your customer message).

ABAP Program Termination in Process Chain

Hello
in my process chains i have one abap program and it is getting dump while loading.
where can i check whether this program got terminated in this particular chain.
as i have many chains i am not able to check in each and every chain.
kindly let me know where to check the program termination in process chains.
do i have any chance to set an automatic process for checking the termination of the program.
regards,
Ala.

Hi Ala,
If u know the process chain name, u can directly see log view of that process chain and right click on that failed ABAP program click "display mesaged". Now note down the error message and see that in st22.
If u dont know the process chain name..
In SM37 go to the job log for that pirticular job which is failed, it gives u tha program name and varient name.
now goto SE38 and give that program name and variant then click on display.It gives u process chain name.
Hope it helps.

Short dump in ST22

My application is running correctly and we never getting any dump in browser but in ST22 there are thousands of dumps recorded for application.
The details are as below. My all services are activated. Kindly suggest what could be the cause
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_WD_GENERAL
Date and Time          07/07/2011 10:39:42
Short text
     An exception occurred that was not caught.
What happened?
     The exception 'CX_WD_GENERAL' was raised, but it was not caught anywhere along
     the call hierarchy.
     Since exceptions represent error situations and this error was not
     adequately responded to, the running ABAP program
      'CX_WD_GENERAL=================CP' has to be
     terminated.
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 which is explained in detail below.
    The exception, which is assigned to class 'CX_WD_GENERAL', was not caught and
    therefore caused a runtime error.
    The reason for the exception is:
    WebDynpro Exception: ICF service node
    "/sap/bc/webdynpro/sap/App/undefined" does not exist (see SAP Note
    1109215).
How to correct 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:
    "UNCAUGHT_EXCEPTION" "CX_WD_GENERAL"
    "CX_WD_GENERAL=================CP" or "CX_WD_GENERAL=================CM003"
    "RAISE"

Hi Shefali,
In ST22 what does in show in the "Source Code Extract" session. Usually it points to code which raosed the exception.
You can try putting a breakpoint there and see what happens at runtime.
Please revert back in case of doubts.
Regards,
Sumit

ABAP program is terminated with error Function ROLLBACK on connection R/3

Hi,
We are reading a DB table A and matching with table B and placing into a internal table and further looping at the internal table.
Table A has 3- 5 million records
Table B has 2-4 million records
When the program run in batch or dialog process, it stops without apparently reason, it don not trace any log in ST22 transaction. When we trace it in SM21 trace the following log:
22:18:33 BTC 014 100                BZ Y Unexpected return value 1 when calling up DbSlR
22:18:33 BTC 014 100                BY J Function ROLLBACK on connection R/3 failed
22:18:33 BTC 014 100                R3 9 Error in DB rollback/SyFlush, return code 016384
22:18:33 BTC 014 100                Q0 2 Stop Workproc14, PID 729286
22:18:33 BTC 014 100                F3 T Invalid object name for TemSe object: " "
22:18:33 BTC 014 100                EC F Failed to create log for job BIDTPR_291659_1 22085900%_IMMEDIATE %NEWSTEP/
22:18:33 BTC 014 100                F2 0 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr'
22:18:33 BTC 014 100                R4 7 Delete session 001 after error 023
The tables and ABAP program are in a BW system.
Any idea what would be the cause. I found a similar problem in the forum but no solution provided there..
Regards
Rob

Hi Rob,
Please check the entries in the work process trace file from this time (dev_wp14 from the work directory)
Error in DB rollback/SyFlush, return code 016384
usually has a preceding entry in the wp log of
SHO: Could not allocate SHO segment of ..... bytes (rc=1)
Usually this is a result of a SELECT statement that returns a very large result set is executed.
While the result set is fetched the ABAP heap is exhausted. Since no
more memory is available the ABAP engine abruptly cancels the execution
and begins error handling. The database interface rejects to execute a
ROLLBACK statement while the SELECT statement is still active. As the
rollback fails the task handler restarts the SAP work process and no
ABAP short dump or job log entries can be written.
The rejected ROLLBACK is a direct result of the lack of ABAP heap memory
and does not represent an error in itself.
The solution here is to increase the memory areas "extended memory" and
/ or "heap". Please check/adjust your SAP memory settings!
As mentioned, Similar issues have been resolved with the note #741864.
The key is that the abap/shared_object_size_MB is too small for the
system and the operation performed, please increase this to 100MB to
start from the default of 20MB and then increase further if the dump
persists as more maybe needed of course. There is no problem increasing
this parameter since you have a 64bit system and SAP kernel.
Similar issues have been resolved with the note #741864 and note #986790
along with the increase in abap/shared_object_size_MB. These notes may
not be necessary just the increase but this issue frequently occurs in
these areas so perhaps they can help.
Hope this helps,
Paul

Error ABAP program "SAPLKKBL"

Hello,
I have a report that gives me the following DUMP when I run it through a JOB, I want an expert to help me see why the error:
                                                                                ¿Qué ha sucedido?
    Error in the ABAP Application Program
The current ABAP program "SAPLKKBL" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
¿Qué puede hacer?
    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.
Anál.errores
    You attempted to access an unassigned field symbol
    (data segment 121).
This error may occur if
    - You address a typed field symbol before it has been set with
      ASSIGN
    - You address a field symbol that pointed to the line of an
      internal table that was deleted
    - You address a field symbol that was previously reset using
      UNASSIGN or that pointed to a local field that no
      longer exists
    - You address a global function interface, although the
      respective function module is not active - that is, is
      not in the list of active calls. The list of active calls
      can be taken from this short dump.
Notas para corregir errores
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:
"GETWA_NOT_ASSIGNED" " "
    "SAPLKKBL" or "LKKBLF99"
    "GEN_FIELD_OUT2"
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.
The line gives me the error is:
   when 030.
      if gs_out_flags-slave ne 'X'.
        assign .
        gs_fc = gs_mfc30.
      else.
Thank you...

Hello,
The program when run on line no problem, runs fine, the problem is when running in the background ...
And if Z is a program...
Thank

ABAP program issue

Dear All,
I have written an ABAP program by which it writes few things on application server (overwrite mode).
I have included this program in the Process Chain but it is giving dump first time when it is running "DATASET_NOT_OPEN" whereas the path and all directories are created on application server.
When i try to repeat the process chain it is running successfully.
Please help on the same.
Regards,
SS

Check these links.
Re: SHORT DUMP! Exception: CX_SY_FILE_OPEN_MODE
CX_SY_FILE_OPEN_MODE - short dump on production but not in Dev and Test
Re: catching an exception 'CX_SY_FILE_OPEN_MODE'
Re: Issue in Uploading file to application server
Thanks.

BEx Login error - Termination occurred in the ABAP program "CL_GUI_FRONTEND

Dear All,
I am having error when i am trying to login in BEx Analyser / Quary Designer 7.0
i am using the same user ID password as when i used to login to SAP BW through Logon pad.
but still i am having the error "Name or Password is incorrect. (repeat logon)"
I did try RRMX in BW, i got
Runtime Errors         RAISE_EXCEPTION
Information on where terminated
    Termination occurred in the ABAP program "CL_GUI_FRONTEND_SERVICES======CP" -
     in "GUI_DOWNLOAD".
    The main program was "RRMX_START_EXCEL ".
    In the source code you have the termination point in line 89
    of the (Include) program "CL_GUI_FRONTEND_SERVICES======CM012".
the program in the error dump as
CALL FUNCTION 'GUI_DOWNLOAD'
       EXPORTING
            BIN_FILESIZE              = BIN_FILESIZE
            FILENAME                  = FILENAME
            FILETYPE                  = FILETYPE
            APPEND                    = APPEND
            WRITE_FIELD_SEPARATOR     = WRITE_FIELD_SEPARATOR
            HEADER                    = HEADER
            TRUNC_TRAILING_BLANKS     = TRUNC_TRAILING_BLANKS
            WRITE_LF                  = WRITE_LF
            COL_SELECT                = COL_SELECT
            COL_SELECT_MASK           = COL_SELECT_MASK
            DAT_MODE                  = DAT_MODE
            CONFIRM_OVERWRITE         = CONFIRM_OVERWRITE
            NO_AUTH_CHECK             = NO_AUTH_CHECK
            CODEPAGE                  = CODEPAGE
            IGNORE_CERR               = IGNORE_CERR
            REPLACEMENT               = REPLACEMENT
            WRITE_BOM                 = WRITE_BOM
            TRUNC_TRAILING_BLANKS_EOL = TRUNC_TRAILING_BLANKS_EOL
            WK1_N_FORMAT              = WK1_N_FORMAT
            WK1_N_SIZE                = WK1_N_SIZE
            WK1_T_FORMAT              = WK1_T_FORMAT
            WK1_T_SIZE                = WK1_T_SIZE
            SHOW_TRANSFER_STATUS      = SHOW_TRANSFER_STATUS
       IMPORTING
            FILELENGTH              = FILELENGTH
       TABLES
            DATA_TAB                = DATA_TAB
            FIELDNAMES              = FIELDNAMES
       EXCEPTIONS
            FILE_WRITE_ERROR        = 1
            NO_BATCH                = 2
            GUI_REFUSE_FILETRANSFER = 3
            INVALID_TYPE            = 4
            NO_AUTHORITY            = 5
            UNKNOWN_ERROR           = 6
            HEADER_NOT_ALLOWED      = 7
            SEPARATOR_NOT_ALLOWED   = 8
            FILESIZE_NOT_ALLOWED    = 9
            HEADER_TOO_LONG         = 10
            DP_ERROR_CREATE         = 11
            DP_ERROR_SEND           = 12
            DP_ERROR_WRITE          = 13
            UNKNOWN_DP_ERROR        = 14
            ACCESS_DENIED           = 15
            DP_OUT_OF_MEMORY        = 16
            DISK_FULL               = 17
            DP_TIMEOUT              = 18
            FILE_NOT_FOUND          = 19
            DATAPROVIDER_EXCEPTION = 20
            CONTROL_FLUSH_ERROR     = 21
            OTHERS                  = 22.
IF SY-SUBRC <> 0.
    case sy-subrc.
      when 1.
        RAISE FILE_WRITE_ERROR.
      when 2.
        RAISE NO_BATCH.
      when 3.
        RAISE GUI_REFUSE_FILETRANSFER.
      when 4.
        RAISE INVALID_TYPE .
      when 5.
        RAISE NO_AUTHORITY.
      when 6.
        RAISE UNKNOWN_ERROR.
      when 7.
        RAISE HEADER_NOT_ALLOWED.
      when 8.
        RAISE SEPARATOR_NOT_ALLOWED.
      when 9.
        RAISE FILESIZE_NOT_ALLOWED.
      when 10.
        RAISE HEADER_TOO_LONG.
      when 11.
        RAISE DP_ERROR_CREATE.
      when 12.
        RAISE DP_ERROR_SEND.
      when 13.
        RAISE DP_ERROR_WRITE.
      when 14.
        RAISE UNKNOWN_DP_ERROR.
>>>>when 15.
        RAISE ACCESS_DENIED.
krish

Hello,
the same type of problem was solved today this way (it´s due to a local client problem):
Start users local SAP GUI
In the left upper corner of SAP GUI select the menue and -> options.
Delete all cache files of SAP GUI and browse the local SAP GUI download folder of the users workstation. Rename the files in the download/workdir folder for example to *_old.
Logon to SAP system again, run RRMX again -> confirm download of bex config file -> Excel sheet should open now.
Important: also the end user has to configure some excel addin options (bex) otherwise the excel sheet will be blank / empty.
BR,
Alessandro

Termination occurred in the ABAP program "RK2APA00_POST" - in

Hi everybody...I have a cancelled job when run only in applications servers , I see a dump "message typeX" , but when job run in Central Instance not cancelled and finish ok.
The name Job is Zcupon and attach to continue dump info , sorry for extended but I want send all information possible.
know if you can add a file with the abstract and not have to paste the text of the dump, thanks for the help they can deliver.
Regards....Freddy Solar....
Errores tiempo ejec.   MESSAGE_TYPE_X
Fecha y hora           18.11.2008 06:35:30
Texto breve
The current application triggered a termination with a short dump.
¿Qué ha sucedido?
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).
Anál.errores
Short text of error message:
RFC_ERROR 4 Conversation 93690218 not found / CPIC-CALL: 'ThSA
Technical information about the message:
Message classe...... "KE"
Number.............. 628
Variable 1.......... "RFC_ERROR"
Variable 2.......... 4
Variable 3.......... "Conversation 93690218 not found / CPIC-CALL: 'ThSA"
Variable 4.......... " "
Last error logged in SAP kernel
Component............ "SAP-Gateway"
Place................ "SAP-Gateway on host SCPAPP1 / sapgw03"
Version.............. 2
Error code........... 728
Error text........... "Conversation 93690218 not found"
Description.......... " "
System call.......... " "
Module............... "gwxxrd.c"
Line................. 6156
The error reported by the operating system is:
Error number..... " "
Error text....... " "
Notas para corregir errores
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,
please use the following search criteria:
"RK2APA00_POST" "MESSAGE_TYPE_X"
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.
Entorno sistema
SAP-Release 700
Application server... "SCPAPP1"
Network address...... "10.1.40.130"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 3
Shortdump setting.... "full"
Database server... "BALTICO"
Database type..... "DB400"
Database name..... "SCP"
Database user ID.. "R3SCPDATA"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jun 30 2008 00:10:07"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "DB4_53"
Patch level. 167
Patch text.. " "
Database............. "V5R3, V5R4, V6R1"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 159213920
Heap.... 0
Page.... 5660672
MM Used. 145143664
MM Free. 5680112
Usuario y transacción
Client.............. 400
User................ "ZUSRTARJETAS"
Language key........ "S"
Transaction......... " "
Program............. "RK2APA00_POST"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Info posición de cancelación
Termination occurred in the ABAP program "RK2APA00_POST" - in
"INSERT_CE4_FLUSH_BUFFERS".
The main program was "ZVI_CUPON ".
In the source code you have the termination point in line 100
of the (Include) program "RKEVRK2A_POST_COMMIT__FIX".
The program "RK2APA00_POST" was started as a background job.
Job Name....... "ZCUPON"
Job Initiator.. "ZUSRTARJETAS"
Job Number..... 02044200
Detalle código fuente
Lín.
Txt.fte.
70
subrc = sy-subrc.
71
CLEAR: g_t_ce4a_dbbuf[], g_t_ce4_dbbuf[].
72
73
case subrc.
74
when 1.
75
    Records were to be inserted into the acct.ref. table CE4xxxx_ACCT
76
    but the acct. reference numbers were already occupied. Most likely
77
    This problem is due to a explicit or implicit change to the
78
    number range COPA_OBJ (subobject is the operating concern)
79
    e.g. caused by illegally transporting the contents of CO-PA
80
    transaction data table contents (CE4xxxx / CE4xxxx_ACCT).
81
    Please check OSS for notes with keywords RKEVRK2A_POST, KF216
82
    and CE4XXXX_ACCT. If you do not find any applicable notes please
83
    log an OSS message.
84
MESSAGE x216(kf) WITH gc_ce4acct_name.
85
86
when 2.
87
    Records were to be inserted into the segment table CE4xxxx
88
    but the segment numbers were already occupied. Most likely
89
    This problem is due to a explicit or implicit change to the
90
    number range COPA_OBJ (subobject is the operating concern)
91
    e.g. caused by illegally transporting the contents of CO-PA
92
    transaction data table contents (CE4xxxx).
93
    Please check OSS for notes with keywords RKEVRK2A_POST, KF203
94
    and CE4XXXX. If you do not find any applicable notes please
95
    log an OSS message.
96
MESSAGE x203(kf).
97
98
when 3 or 4.
99
    Communication error in RFC-Call
>>>>>
message x628(ke) with 'RFC_ERROR' subrc msg_text.
101
102
endcase.
103
104
ENDFORM.
105
Edited by: freddy solar on Jan 2, 2009 8:39 PM

Hi,
it looks like you have some problem with RFC. It stopped on the following line:
* Communication error in RFC-Call
message x628(ke) with 'RFC_ERROR' subrc msg_text.
Ask your basis guy to check it. The job on application server tried to connect to the central instance and it failed. The job run on central instance does not need to make any RFC call. Hence there is no problem in this case.
Regards

DYNPRO_NOT_FOUND in abap program dumps in st22

Similar Messages

Maybe you are looking for