Dump in LKKBLF99
Hi
I get this error :-
In statement
"STRLEN( obj )..."
the argument "obj" can only take a character-type data object.
The termination occurred in the ABAP/4 program "SAPLKKBL " in
"GEN_FIELD_OUT2".
The main program was "ZRTUS001_V1 ".
The termination occurred in line 3914
of the source code of program "LKKBLF99 " (when calling the editor 39140).
Please give some suggestions
I think UR using ALV to display output .. and while populating
fieldcatalog UR passing 'N'/other than type 'C' for DATATYPE ..
Can U paste the coding ... ?
Edited by: Srinivas Gurram Reddy on Apr 22, 2008 8:16 PM
Similar Messages
-
ABAP dump "GETWA_NOT_ASSIGNED" C
HI,
kindly suggest we are getting a abap dump while downloading a file and when i check the error in service market place its shows that we have to apply support packages.can i directly apply support packages by downloading the market or i have to raise a query fro exact support packages to market place.
my version-mssql2005-ecc5-640version.
kindly see the below abap dump.
Runtime Error GETWA_NOT_ASSIGNED
Date and Time 21.10.2008 11:25:01
ShrtText
Field symbol has not yet been assigned.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLKKBL" 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
You attempted to access an unassigned field symbol
(data segment 169).
This error may occur for any of the following reasons:
- You address a typed field symbol before it is set using ASSIGN
- You address a field symbol that points to a line in an internal table
that has been deleted
- You address a field symbol that had previously been reset using
UNASSIGN, or that pointed to a local field that no longer exists
- You address a global function interface parameter, even
though the relevant function module is not active,
that is it is not in the list of active calls. You can get the list
of active calls from the this short dump.
How to correct the error
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:
"GETWA_NOT_ASSIGNED" C
"SAPLKKBL" or "LKKBLF99"
"GEN_FIELD_OUT2"
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....... "TERHSAPTST01"
Network address.......... "10.129.48.15"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "TERHSAPTST01"
Database type............ "MSSQL"
Database name............ "INQ"
Database owner........... "inq"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Mar 21 2007 23:46:50"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "175"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory usage.............
Roll..................... 8176
EM....................... 12542784
Heap..................... 0
Page..................... 286720
MM Used.................. 8264648
MM Free.................. 95024
SAP Release.............. "640"
User and Transaction
Client.............. 100
User................ "CHINNIJ"
Language key........ "E"
Transaction......... "ZSDOST "
Program............. "SAPLKKBL"
Screen.............. "SAPLKKBL 0500"
Screen line......... 3
Information on where terminated
The termination occurred in the ABAP program "SAPLKKBL" in "GEN_FIELD_OUT2".
The main program was "ZSDSO_ORDER_STATUS ".
The termination occurred in line 3380 of the source code of the (Include)
program "LKKBLF99"
of the source code of program "LKKBLF99" (when calling the editor 33800).
Source Code Extract
Line SourceCde
3350 else.
3351 assign <fs74> to <field>.
3352 gs_fc = gs_sfc74.
3353 endif.
3354 when 075.
3355 if gs_out_flags-slave ne 'X'.
3356 assign <fm75> to <field>.
3357 gs_fc = gs_mfc75.
3358 else.
3359 assign <fs75> to <field>.
3360 gs_fc = gs_sfc75.
3361 endif.
3362 when 076.
3363 if gs_out_flags-slave ne 'X'.
3364 assign <fm76> to <field>.
3365 gs_fc = gs_mfc76.
3366 else.
3367 assign <fs76> to <field>.
3368 gs_fc = gs_sfc76.
3369 endif.
3370 when 077.
3371 if gs_out_flags-slave ne 'X'.
3372 assign <fm77> to <field>.
3373 gs_fc = gs_mfc77.
3374 else.
3375 assign <fs77> to <field>.
3376 gs_fc = gs_sfc77.
3377 endif.
3378 when 078.
3379 if gs_out_flags-slave ne 'X'.
>>>>> assign <fm78> to <field>.
3381 gs_fc = gs_mfc78.
3382 else.
3383 assign <fs78> to <field>.
3384 gs_fc = gs_sfc78.
3385 endif.
3386 when 079.
3387 if gs_out_flags-slave ne 'X'.
3388 assign <fm79> to <field>.
3389 gs_fc = gs_mfc79.
3390 else.
3391 assign <fs79> to <field>.
3392 gs_fc = gs_sfc79.
3393 endif.
3394 when 080.
3395 if gs_out_flags-slave ne 'X'.
3396 assign <fm80> to <field>.
3397 gs_fc = gs_mfc80.
3398 else.
3399 assign <fs80> to <field>.
Contents of system fields
Name Val.
SY-SUBRC 4
SY-INDEX 78
SY-TABIX 0
SY-DBCNT 0
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 1
SY-LINNO 7
SY-COLNO 1002
SY-PFKEY STANDARD
SY-UCOMM %PC
SY-TITLE Order Data ware house
SY-MSGTY
SY-MSGID
SY-MSGNO 000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No. Ty. Program Include Line
Name
16 FORM SAPLKKBL LKKBLF99 3380
GEN_FIELD_OUT2
15 FORM SAPLKKBL LKKBLF99 777
GEN_LINE_OUT
14 FORM SAPLKKBL LKKBLF98 1314
DATA_OUT_SIMPLE
13 FORM SAPLKKBL LKKBLF01 360
LIST_OUTPUT_NEW
12 FORM SAPLKKBL LKKBLF01 6109
FIRST_LIST_DISPLAY
11 MODULE (PBO) SAPLKKBL LKKBLO01 11
LIST_DISPLAY
10 FUNCTION SAPLKKBL LKKBLU01 419
K_KKB_LIST_DISPLAY
9 METHOD CL_GUI_ALV_GRID===============CP CL_GUI_ALV_GRID===============CM00R 455
CL_GUI_ALV_GRID=>PRINT_BACKEND
8 METHOD CL_GUI_ALV_GRID===============CP CL_GUI_ALV_GRID===============CM008 3
CL_GUI_ALV_GRID=>EXPORT_TO_LOCAL_FILE
7 METHOD CL_GUI_ALV_GRID===============CP CL_GUI_ALV_GRID===============CM007 481
CL_GUI_ALV_GRID=>EXECUTE_FCODE
6 METHOD CL_GUI_ALV_GRID===============CP CL_GUI_ALV_GRID===============CM01E 58
CL_GUI_ALV_GRID=>SET_FUNCTION_CODE
5 FORM SAPLSLVC_FULLSCREEN LSLVC_FULLSCREENF01 1167
PAI
4 MODULE (PAI) SAPLSLVC_FULLSCREEN LSLVC_FULLSCREENI01 4
PAI
3 FUNCTION SAPLSLVC_FULLSCREEN LSLVC_FULLSCREENU01 186
REUSE_ALV_GRID_DISPLAY
2 FORM ZSDSO_ORDER_STATUS ZSDSO_ORDER_STATUS 1305
DATA_DISPLAY
1 EVENT ZSDSO_ORDER_STATUS ZSDSO_ORDER_STATUS 632
START-OF-SELECTION
Chosen variables
Name
Val.
No. 16 Ty. FORM
Name GEN_FIELD_OUT2
<FS76>
<FIELD>
222
000
000
000
GS_FC
##M#MVGR5 I_OUT
0040454532222222222222222222222222454552222222222222222222222222222222222222222222222222222222
10D0D672500000000000000000000000009FF540000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GS_SFC76
0000222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GFLG_FIELD
2
0
0
0
GS_SFC24
0000222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GS_OUT-FIELD_COLCOUNT
78
4000
E000
GT_INFO_COUNTTAB_OUTTAB
Table[initial]
SY-REPID
SAPLKKBL
5454444422222222222222222222222222222222
310CBB2C00000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
GS_OUT_FLAGS-SLAVE
2
0
0
0
SPACE
2
0
0
0
<FM77>
222
000
000
000
GS_MFC77
##M#MVGR5 I_OUT
0040454532222222222222222222222222454552222222222222222222222222222222222222222222222222222222
10D0D672500000000000000000000000009FF540000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
<FS77>
GS_SFC77
0000222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
TC_FIELD_LIST-CX
<initial>
<initial>
<initial>
GT_INFO_FILTER_OUTTAB
Table[initial]
<FM78>
GS_MFC78
##N#ZRELEASE I_OUT
0040554444542222222222222222222222454552222222222222222222222222222222222222222222222222222222
10E0A25C513500000000000000000000009FF540000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
<FS78>
GS_SFC78
0000222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
HEAD
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
G_INFO_POPUP
2
0
0
0
No. 15 Ty. FORM
Name GEN_LINE_OUT
GT_STACK2-S_SUBTOT_OPTIONS-OFFSET
0
0000
0000
%_DUMMY$$
2222
0000
0000
0000
SYST-REPID
SAPLKKBL
5454444422222222222222222222222222222222
310CBB2C00000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
GS_ACT_GROUP-SUBTOT
2
0
0
0
GS_OUT_FLAGS-SUM
2
0
0
0
EUINFO
0000000000000000###
2222222222222222222222222222222222222222222222200022222222222222222222222223333333333333333000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_SPACE
2
0
0
0
GS_OUT_FLAGS-HOTLINE
2
0
0
0
GS_OUT-COL
2
0000
2000
GS_OUT-INT
0
0000
0000
GS_OUT-ROWS
1
0000Hi,
We got a lot of short dumps with the same error when we upgraded from 46C to ECC6.
They were all for reports that used ALV and in evry case, corrections were needed to the field catalog.
I suggest that you double and triple check the table and field names in your field catalog. ALV is a lot more sensitive in ECC6 (or performs less checks) and it is possible that you're experiencing the same problem in ECC5.
Hope that answers your question
Alex Dixon -
Runtime Error in source code - LKKBLF99 during MB51
Dear All,
I have config receipt indicator: X Stock Transport Order in MB51. It is Working Completely good in Development in Quality. But it is having dump during i run into production server.
Information on where terminated
Termination occurred in the ABAP program "SAPLKKBL" - in "GEN_FIELD_OUT2".
The main program was "RM07DOCS ".
In the source code you have the termination point in line 2839
of the (Include) program "LKKBLF99".
2825 ----
2826 * FORM GEN_FIELD_OUT2 *
2827 ----
2828 * ........ *
2829 ----
2830 form gen_field_out2.
2831 field-symbols <l_initial>.
2832
2833 case gs_out-field_colcount.
2834 when 001.
2835 if gs_out_flags-slave ne 'X'.
2836 assign <fm01> to <field>.
2837 gs_fc = gs_mfc01.
2838 else.
>>>>> assign <fs01> to <field>.
2840 gs_fc = gs_sfc01.
2841 endif.
Don't understand what happened. Let me have some solution AEAP.
Regards,
Swapnil VaidyaRuntime Errors GETWA_NOT_ASSIGNED
Termination occurred in the ABAP program "SAPLKKBL" - in "GEN_FIELD_OUT2".
The main program was "RM07DOCS ".
In the source code you have the termination point in line 2839
of the (Include) program "LKKBLF99".
Source Code Extract
Line SourceCde
2809 of structure t_outtab_slave to <fs96>.
2810 gs_sfc96 = gs_out_fieldcat.
2811 when 97.
2812 assign component gs_out_fieldcat-fieldname
2813 of structure t_outtab_slave to <fs97>.
2814 gs_sfc97 = gs_out_fieldcat.
2815 when 98.
2816 assign component gs_out_fieldcat-fieldname
2817 of structure t_outtab_slave to <fs98>.
2818 gs_sfc98 = gs_out_fieldcat.
2819 when 99.
2820 assign component gs_out_fieldcat-fieldname
2821 of structure t_outtab_slave to <fs99>.
2822 gs_sfc99 = gs_out_fieldcat.
2823 endcase.
2824 endform. "field_assign_hier_slave
2825 ----
2826 * FORM GEN_FIELD_OUT2 *
2827 ----
2828 * ........ *
2829 ----
2830 form gen_field_out2.
2831 field-symbols <l_initial>.
2832
2833 case gs_out-field_colcount.
2834 when 001.
2835 if gs_out_flags-slave ne 'X'.
2836 assign <fm01> to <field>.
2837 gs_fc = gs_mfc01.
2838 else.
>>>>> assign <fs01> to <field>.
2840 gs_fc = gs_sfc01.
2841 endif.
2842 when 002.
2843 if gs_out_flags-slave ne 'X'.
2844 assign <fm02> to <field>.
2845 gs_fc = gs_mfc02.
2846 else.
2847 assign <fs02> to <field>.
2848 gs_fc = gs_sfc02.
2849 endif.
2850 when 003.
2851 if gs_out_flags-slave ne 'X'.
2852 assign <fm03> to <field>.
2853 gs_fc = gs_mfc03.
2854 else.
2855 assign <fs03> to <field>.
2856 gs_fc = gs_sfc03.
2857 endif.
2858 when 004. -
Dump GETWA_NOT_ASSIGNED in ALV OO
Hi experts, i have a problem ... i created an ALV OO but when i wanna dowload the ALV's lines the program trigger a DUMP: GETWA_NOT_ASSIGNED in program SAPLKKBL ... i know that it's a clasic DUMP about ALV's ... please i need your help.
Thanks.
David CarballidoHi Uwe ... i created a structure and called to FM LVC_FIELDCATALOG_MERGE to create my fieldcat and the program trigger the same DUMP.
Errores tiempo ejecucióGETWA_NOT_ASSIGNED
ocurrido el 23.09.2008 a 17:10:54
>> Dump breve ABAP no almacenado completamente (muy grande)
Field symbol has not yet been assigned.
¿Qué ha sucedido?
The current ABAP/4 program "SAPLKKBL " 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.
¿Qué puede hacer?
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.
Análisis error
You attempted to access an unassigned field symbol
(data segment 1069).
This error occurs:
- if you address a typed field symbol before it has been set with
ASSIGN or
- if you address a field symbol that has been reset with UNASSIGN
or pointed to a local field that no longer exists, or
- if you address a field symbol that pointed to a line of an internal
table that has now been deleted, or
- if you address a global function interface partameter, even
though the relevant function module is not active,
i.e. it is not in the list of active calls. You can get the list
of active calls from the this short dump.
Notas para corregir errores
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:
"GETWA_NOT_ASSIGNED"
"SAPLKKBL " or "LKKBLF99 "
"GEN_FIELD_OUT2"
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.
Usuario, transacción....
Client.............. 200
User................ "BCDCARBALLID"
Language key........ "S"
Transaction......... "SEU_INT "
Program............. "SAPLKKBL "
Screen.............. "SAPLKKBL 0500"
Screen line......... 3
Info posición de cancelación
The termination occurred in the ABAP/4 program "SAPLKKBL " in
"GEN_FIELD_OUT2".
The main program was "ZFI_RPT_PDB_005 ".
The termination occurred in line 3824
of the source code of program "LKKBLF99 " (when calling the editor 38240).
Detalle código fuente
037940 * Color settings "K_COLCOLOR
037950 if gs_out_flags-sum is initial.
037960 if gs_fc-hotspot = 'X' and gs_out_flags-hotline is initial
037970 and gt_stack-is_layout-no_hotspot is initial.
037980 format hotspot on.
037990 elseif gs_fc-hotspot = 'V'
038000 and gs_out_flags-hotline is initial and not <field> is initial
038010 and gt_stack-is_layout-no_hotspot is initial.
038020 format hotspot on.
038030 endif.
038040 if gs_fc-input = 'X' and
038050 gt_stack-is_layout-no_input is initial and
038060 gs_fc-checkbox is initial.
038070 format input on.
038080 format intensified off.
038090 endif.
038100 if not gs_fc-emphasize is initial and gs_out-info is initial.
038110 perform field_color_normal using gs_fc
038120 * gt_stack-is_layout
038130 gs_out-info.
038140 endif.
038150
038160 * complex logic with internal table for color description
038170 if gs_out_flags-mcoltab = 'X' and gs_out_flags-slave ne 'X' and
038180 gs_out_flags-sum ne 'X'.
038190
038200 perform field_color_complex using <coltab>
038210 gs_fc
038220 gs_out_flags-inverse.
038230 elseif gs_out_flags-scoltab = 'X' and gs_out_flags-slave = 'X' and
-----> gs_out_flags-sum ne 'X'.
038250
038260 * perform field_color_complex using <coltab> " DEL FGS_COLOR
038270 perform field_color_complex using <coltab_slave> " INS FGS_COLOR
038280 gs_fc
038290 gs_out_flags-inverse.
038300 endif.
038310 endif.
038320
038330 *--- Prüfung Ausgabelänge
038340 clear gs_out-hlplen.
038350 * Edit-Mask
038360 if gs_fc-tech_form = 7.
038370 write <field> to gs_out-hlpchar
038380 using edit mask gs_fc-edit_mask.
038390 gs_out-hlplen = strlen( gs_out-hlpchar ).
038400 * Bei NUMC führende '0' und ' ' nicht berücksichtigen
038410 elseif gs_fc-tech_form = 6.
038420 write <field> to gs_out-hlpchar no-zero left-justified.
038430 if gs_fc-just = 'R'. -
Hi,
getting dump when using 'Print' command. the dump details are:
in debugging it is stopping a method for 'TOP OF PAGE'
I have used the FM for top page CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = vt_list_top_of_page.
The current statement only supports character-type data objects.
What happened?
The current ABAP/4 program "SAPLKKBL " 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
In statement
"STRLEN( obj )..."
the argument "obj" can only take a character-type data object.
In this case, the operand "obj" has the non-character type "P".
How to correct the error
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:
"OBJECTS_NOT_CHARLIKE"
"SAPLKKBL " or "LKKBLF99 "
"GEN_FIELD_OUT2"
f you cannot solve the problem yourself, please send the
ollowing documents to SAP:
. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
. 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.
. 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.
. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
please help meHi Sri!
The REUSE_ALV* function modules can not run in update task (there is a call screen included) - your printing seems to be in an update task (e.g. when you have a message output '4 - immediate').
Check, if it's possible to run this in background (in case of messages with 1 / 2: by job), otherwise you need to remove the FM module - no other help, sorry.
Regards,
Christian -
I am running a proram in background mode. I got a dump showing the error as
The termination occurred in the ABAP program "SAPLKKBL" in "GEN_FIELD_OUT2".
The main program was "ZALVSTAR".
The termination occurred in line 3897 of the source code of the (Include)
program "LKKBLF99"
of the source code of program "LKKBLF99" (when calling the editor 38970).
The program "SAPLKKBL" was started as a background job.
But when i ran the program in fore ground, it is displaying the output.
Please clarify this issue.Manjunath,
You might have written code there which will can not execute in background
Ex: Display POP_UP screen or messages.
Go and check the code at that particular code and paste here we can give solution.
system will show arrow mark where the program code giving dump. -
hi experts,
we are running the ZDMS it is open .we go to search it is going to dump...
Error analysis
You attempted to access an unassigned field symbol
(data segment 95).
This error may occur if
- You address a typed field symbol before it has been set wit
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.
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:
"GETWA_NOT_ASSIGNED" " "
"SAPLKKBL" or "LKKBLF99"
"GEN_FIELD_OUT2"
thanks
ajaiHi Brad,
thanks for reply below is the source code
Runtime Errors GETWA_NOT_ASSIGNED
Date and Time 04/17/2008 02:10:12
Short text
Field symbol has not yet been assigned.
What happened?
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.
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
You attempted to access an unassigned field symbol
(data segment 95).
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.
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:
"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.
System environment
SAP-Release 700
Application server... "devqas"
Network address...... "157.116.126.249"
Operating system..... "OS400"
Release.............. "5.4"
Hardware type........ "0010000F685B"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "devqas"
Database type..... "DB400"
Database name..... "DEV"
Database user ID.. "R3DEVDATA"
Char.set.... "en_US.ISO8859-1"
SAP kernel....... 700
created (date)... "Jul 1 2007 21:56:03"
create on........ "AIX 2 5 005DD9CD4C00 (iSeries)"
Database version. "DB4_53"
Patch level. 117
Patch text.. " "
Database............. "V5R3, V5R4"
SAP database version. 700
Operating system..... "OS400 3 5, OS400 4 5"
Memory consumption
Roll.... 16128
EM...... 16759680
Heap.... 0
Page.... 188416
MM Used. 5316496
MM Free. 3060616
User and Transaction
Client.............. 100
User................ "RAHALKAR"
Language key........ "E"
Transaction......... "ZDMS "
Transactions ID..... "480699B806F50C5AE10080039D747EF9"
Program............. "SAPLKKBL"
Screen.............. "SAPLKKBL 0500"
Screen line......... 3
Information on where terminated
Termination occurred in the ABAP program "SAPLKKBL" - in "GEN_FIELD_OUT2".
The main program was "ZDMS_REPORTING ".
In the source code you have the termination point in line 2820
of the (Include) program "LKKBLF99".
Source Code Extract
Line SourceCde
2790 form gen_field_out2.
2791 field-symbols METRIC_DEFAULT
0
0000
0000
CON_LISTTYPE-HIER_SEQU
H
4
8
No. 6 Ty. FORM
Name FIRST_LIST_DISPLAY
RSJOBINFO
00000000000000 ####
222222222222222222222222222222223333333333333322222222222222222222222222222222220000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LR_CONTENT
F0000000
F0000000
LR_ABAP
F0000000
F0000000
%_FMBX_WA
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T_OUTTAB[]
Table IT_41[742x2440]
T_OUTTAB
DCKER160-ALSKD-AKNY-03611 00000PERSAUD OPER160-NYCKD-NYAK-02588 DCKER160 ALS
4444533324454424445233333222333335455454222224545333245444245442333332224444533322222222244522
43B52160D1C3B4D1BE9D0361100000000052315400000F052160DE93B4DE91BD0258800043B521600000000001C300
GT_DUMMY[]
Table IT_183[0x1]
FUNCTION-POOL=KKBLDATA=GT_DUMMY[]
Table reference: 51
TABH+ 0(20) = 000000000000000007000000D8393D0000000000
TABH+ 20(20) = 00000033000000B70000000000000001FFFFFFFF
TABH+ 40(16) = 04000063000041500064248C01800000
store = 0x0000000000000000
ext1 = 0x07000000D8393D00
shmId = 0 (0x00000000)
id = 51 (0x00000033)
label = 183 (0x000000B7)
fill = 0 (0x00000000)
leng = 1 (0x00000001)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000288
occu = 100 (0x00000064)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 1 (cmpSingleByte)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
collHook = 0x0000000000000000
ext2 = 0x07000000D838C600
>>>>> 2nd level extension part <<<<<
tabhBack = 0x07000000D83A2440
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
GT_DUMMY
2
0
GS_SFC87
0000000022222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GS_SFC83
0000000022222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GT_STACK-IS_LAYOUT+1031(30)
222222222222222222222222222222
000000000000000000000000000000
GT_STACK-IS_LAYOUT+530(1)
2
0
CL_GUI_CONTROL=>LIFETIME_DEFAULT
0
0000
0000
No. 5 Ty. MODULE (PBO)
Name LIST_DISPLAY
GS_MFC32
0.0.0.0.0.0.1. LKV_NO DMS_TAB
0000000244554422222222222222222222222244555442222222222222222222222222222222222222222222222222
00010000CB6FEF0000000000000000000000004D3F4120000000000000000000000000000000000000000000000000
<%_TABLE_ASEXDOM>
No. 4 Ty. FUNCTION
Name K_KKB_LIST_DISPLAY
GS_SFC31
0000000022222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GS_MFC78
#######NSUBJECT3 DMS_TAB
0000000455444453222222222222222222222244555442222222222222222222222222222222222222222222222222
0001000E352A534300000000000000000000004D3F4120000000000000000000000000000000000000000000000000
GS_SFC34
0000000022222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_SCREEN_START_LINE
0
0000
0000
GT_STACK-IS_LAYOUT+2276(1)
2
0
GT_STACK-IS_LAYOUT+2272(1)
2
0
G_ULINE
TOP_OF_PAGE2
545544554443222222222222222222
4F0FF6F01752000000000000000000
SY-XFORM
NEW-LINE
445244442222222222222222222222
E57DC9E50000000000000000000000
GS_SFC35
0000000022222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_SCREEN_START_COLUMN
0
0000
0000
GS_SFC36
0000000022222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GS_SFC37
0000000022222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_SCREEN_END_COLUMN
0
0000
0000
GS_SFC38
0000000022222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_SCREEN_END_LINE
0
0000
0000
No. 3 Ty. FUNCTION
Name REUSE_ALV_LIST_DISPLAY
IR_SALV_LIST_ADAPTER
F0000000
F0000000
IS_LAYOUT
0.0.0.0.0.0.1. X
2000000022522222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000000
IS_PRINT
1. ##### # 000
2222222222222222222222222222222222222222222022200000222022223332222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IS_REPREP_ID
22222222222222222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000000000000000
IS_SEL_HIDE
###########ÿÿÿÿ
200000000000FFFF
000000000000FFFF
IS_VARIANT
ZDMS_REPORTING
5445554545544422222222222222222222222222222222222222222222222222222222222222222222222222222222
A4D3F250F249E700000000000000000000000000000000000000000000000000000000000000000000000000000000
IT_EVENTS
Table[initial]
IT_EVENT_EXIT
Table[initial]
IT_EXCEPT_QINFO
Table[initial]
IT_EXCLUDING
Table[initial]
IT_FIELDCAT
Table IT_44[82x732]
FUNCTION=REUSE_ALV_LIST_DISPLAYDATA=IT_FIELDCAT
Table reference: 30
TABH+ 0(20) = 07000000D8415A10000000000000000000000000
TABH+ 20(20) = 0000001E0000002C00000052000002DCFFFFFFFF
TABH+ 40(16) = 0400004600000B10000124C021800000
store = 0x07000000D8415A10
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 30 (0x0000001E)
label = 44 (0x0000002C)
fill = 82 (0x00000052)
leng = 732 (0x000002DC)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000040
occu = 1 (0x00000001)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data Stack Trace:
AixStack() at 0x10009c54c
CTrcStack2() at 0x10009c644
rabax_CStackSave__Fv() at 0x100087720
ab_rabax() at 0x10008458c
getwa_abswa__FUiN21() at 0x100481f24
ab_DataToAttaDseg__FPC7AB_DATAP8BaseAttaP10AB_DATASEGUi() at 0x100472b14
AssiField__Fv() at 0x100cb01a4
ab_jassi__Fv() at 0x100cafda4
ab_extri__Fv() at 0x10045db70
ab_xevent__FPCc() at 0x100bd70ac
ab_dstep() at 0x1006cf51c
dynpmcal() at 0x100f96218
dynppbo0() at 0x100f942ac
dynprctl() at 0x100f9cc18
dynpen00() at 0x100d45fe0
Thdynpen00() at 0x1000b5a18
TskhLoop() at 0x1000ba540
ThStart() at 0x1000d0a64
DpMain() at 0x100f4bda8
nlsui_main() at 0x10184fde8
Thu Apr 17 02:10:11 2008
Library (SRV)PGM Module Function/Statement No.
QSYS QP2USER2 QP2API __Qp2Fork 8
Thu Apr 17 02:10:12 2008
QSYS QP2USER2 QP2API runpase_main__FPi 6
QSYS QP2USER2 QP2API runpase_common__FiPvT2 2
SAP700NEW O4PRTLIB AS4STACK As4Stack_From_PASE 4
SAP700NEW O4PRTLIB AS4STACK As4StackOut 14
SAP700NEW O4PRTLIB AS4STACK MATINVS2_8O4_StackFv 12
List of ABAP programs affected
Index Typ Program Group Date Time Size Lang.
0 Prg ZDMS_REPORTING 0 01/03/2008 19:53:59 154624 E
1 Prg SAPMSSY0 1 04/09/2008 08:18:47 73728 E
2 Prg SAPMSSYD 1 08/16/2006 12:06:37 18432 E
3 Prg SAPFSYSCALLS 1 09/09/2004 14:18:32 6144 E
4 Prg RSDBRUNT 0 08/16/2006 12:06:27 226304 E
5 Typ RSSCR 0 03/30/2005 10:21:45 5120
6 Prg RSDBSPBL 0 03/30/2005 10:21:58 59392 E
7 Prg SAPDB__S 0 03/30/2005 10:22:01 16384 E
8 Typ VARID 0 05/12/1997 16:51:30 4096
9 Typ SSCRFIELDS 0 05/13/1997 12:54:26 4096
10 Prg %_CSYDB0 0 03/30/2005 10:21:45 28672 E
11 Prg RSDBSPVA 0 04/09/2008 07:54:55 114688 E
12 Prg SAPLSVAR 12 04/09/2008 07:48:02 695296 E
13 Typ VARIS 0 05/12/1997 15:27:21 2048
14 Typ RSVAMEMKEY 0 05/07/1997 13:07:49 2048
15 Prg RSDBSPMC 0 08/16/2006 11:55:58 67584 E
16 Typ DDSHDESCR 0 09/03/1997 03:05:16 3072
17 Typ SPPARAMS 0 05/07/1997 13:10:38 2048
18 Prg SAPLICON 18 08/16/2006 11:55:59 24576 E
19 Prg %_CICON 18 01/25/2006 11:06:59 76800 E
20 Typ ICONT 0 08/16/2006 11:55:57 2048
21 Prg SAPLSABE 21 09/09/2004 14:18:36 10240 E
22 Prg SAPLSECU 22 04/09/2008 07:39:40 74752 E
23 Typ RSSUBINFO 0 10/14/1999 22:01:03 3072
24 Typ RSPARAMS 0 04/04/1995 16:12:11 2048
25 Prg SAPLSLDB 25 01/25/2006 11:07:10 69632 E
26 Prg SAPLDSYA 26 04/05/2008 16:23:52 39936 E
27 Prg SAPFSDS1 26 03/30/2005 10:22:01 47104 E
28 Typ TDCLD 0 11/02/1998 09:51:35 5120
29 Prg SAPLSDOD 29 01/25/2006 10:59:45 39936 E
30 Typ DOKIL 0 05/12/1997 16:46:17 3072
31 Prg SAPCNVE 31 09/09/2004 14:36:10 6144 E
32 Prg SAPLLANG 32 04/05/2008 16:17:17 8192 E
33 Typ T002 0 04/05/2008 16:13:21 2048
34 Typ RSEXFCODE 0 08/13/1997 12:52:57 2048
35 Prg RSDYNSS0 0 04/08/2008 06:32:32 44032 E
36 Prg SAPFSPOR 0 09/09/2004 14:18:32 12288 E
37 Typ RSPARINT 0 04/10/1995 09:58:38 2048
38 Typ RSSELINT 0 04/04/1995 16:12:37 2048
39 Prg SAPLSCNT 39 02/18/2005 14:16:06 24576 E
40 Typ DYCBOX 0 08/20/1998 11:16:53 2048
41 Prg SAPLSVSM 41 01/05/2006 12:25:28 24576 E
42 Prg SAPLSGUI 42 04/09/2008 07:55:13 67584 E
43 Prg SAPLSTTM 43 07/05/2005 13:10:18 62464 E
44 Prg SAPLSBDC 44 02/21/2008 18:04:36 37888 E
45 Prg CL_DATAPROVIDER===============CP 45 02/28/2005 21:00:46 40960 E
46 Prg %_CCNTL 45 02/18/2005 14:15:08 12288 E
47 Typ OBJ_RECORD 0 02/14/1998 08:30:43 2048
48 Prg SAPLSTUP 48 01/05/2006 12:20:05 64512 E
49 Prg SAPLCNDP 49 04/09/2008 07:33:10 178176 E
50 Prg SAPSHDTV 39 01/05/2005 16:26:16 28672 E
51 Prg SAPFGUICNTL 1 02/18/2005 14:15:08 20480 E
52 Prg SAPLOLEA 52 04/05/2008 22:55:54 86016 E
53 Prg SAPLSFES 53 04/09/2008 07:55:13 230400 E
54 Prg SAPLSPLUGIN 54 09/09/2004 14:18:36 7168 E
55 Typ ARFCRDATA 0 02/13/2005 18:20:24 6144
56 Prg SAPLGRFC 56 02/13/2005 18:20:25 14336 E
57 Typ SWCBCONT 0 11/15/2000 17:55:11 3072
58 Typ OLE_VERBS 0 04/04/1995 16:02:20 2048
59 Typ OLE_PA 0 04/04/1995 16:02:19 2048
60 Typ SSCRTEXTS 0 09/03/1997 03:12:33 3072
61 Typ RSVUVINT 0 01/15/1996 16:09:23 2048
62 Typ ZDMS_NUMBER 0 02/21/2008 12:35:01 4096
63 Typ DRAW 0 02/21/2008 18:12:20 8192
64 Typ LVC_S_ROID 0 10/14/1999 21:58:04 2048
65 Typ AUSP 0 09/18/2001 10:02:23 5120
66 Typ ZV_M_MERKB 0 02/22/2008 11:38:13 3072
67 Typ ZSCA_DMS_DOCS 0 02/21/2008 12:35:20 17408
68 Prg %_CSLIS 0 01/25/2006 11:07:06 68608 E
69 Typ DTC_S_LAYO 0 12/04/2000 12:46:23 6144
70 Prg SAPLSALV 70 04/09/2008 07:25:41 216064 E
71 Prg %_CKKBLO 70 04/08/2008 07:18:11 107520 E
72 Typ ALV_S_PCTL 0 01/25/2006 10:54:38 7168
73 Typ PRI_PARAMS 0 11/02/1998 09:46:12 5120
74 Typ ARC_PARAMS 0 08/28/1997 08:36:28 4096
75 Typ DISVARIANT 0 07/29/1998 18:25:39 2048
76 Prg SAPLSKBB 76 04/08/2008 07:18:23 59392 E
77 Prg CL_ALV_VARIANT================CP 77 04/09/2008 07:19:53 118784 E
78 Typ LVC_S_LAYO 0 05/18/2004 14:08:00 13312
79 Typ LVC_S_DD01 0 05/18/2004 14:06:56 2048
80 Typ LVC_S_TOTO 0 12/04/2000 12:48:07 4096
81 Typ LVC_S_PRNT 0 01/25/2006 10:55:42 9216
82 Prg SAPLSKBH 82 04/09/2008 08:15:28 702464 E
83 Prg SAPLSSN1 83 04/05/2008 16:17:51 23552 E
84 Prg SAPLSDIFRUNTIME 84 07/05/2005 13:11:53 82944 E
85 Typ DDFIXVALUE 0 08/27/1999 18:04:56 2048
86 Typ X031L 0 07/05/2005 13:10:15 6144
87 Typ DFIES 0 12/28/2004 17:06:45 8192
88 Prg SAPLSDNT 88 04/09/2008 07:32:54 198656 E
89 Prg SAPLSUGS 89 03/31/2006 11:14:08 40960 E
90 Prg SAPLSKBS 90 04/08/2008 07:18:23 256000 E
91 Typ LTVARIANT 0 11/15/2000 17:38:31 4096
92 Typ LVC_S_RNGS 0 11/10/1999 17:41:05 2048
93 Typ V_LTDX 0 11/09/2000 14:27:10 4096
94 Typ LTDXT 0 11/15/2000 17:38:31 3072
95 Typ LTDXD 0 11/15/2000 17:38:30 3072
96 Typ LTDXS 0 11/15/2000 17:38:30 2048
97 Prg CL_SALV_VERI_RUN==============CP 97 04/09/2008 07:19:53 72704 E
98 Prg CL_SALV_VERI_MAINTAIN=========CP 98 04/09/2008 07:19:53 166912 E
99 Prg SAPLKKBL 99 04/09/2008 08:16:20 1086464 E
100 Prg CL_SALV_LIST_ADAPTER==========CP 100 04/08/2008 07:18:11 48128 E
101 Typ LVC_S_STBL 0 11/30/1998 15:53:11 2048
102 Prg CL_SALV_ADAPTER===============CP 102 04/08/2008 07:10:15 8192 E
103 Prg IF_SALV_ADAPTER===============IP 99 04/08/2008 07:10:15 6144 E
104 Prg SAPLSLVX 104 04/08/2008 07:18:23 28672 E
105 Prg CL_SALV_TOOLTIP===============CP 105 04/05/2008 23:18:59 10240 E
106 Prg CL_SALV_METADATA_BASE=========CP 106 04/05/2008 23:17:58 7168 E
107 Prg CL_SALV_METADATA==============CP 107 04/05/2008 23:18:59 7168 E
108 Typ LTDXKEY 0 07/29/1998 18:46:24 2048
109 Prg CL_ABAP_CHAR_UTILITIES========CP 109 07/05/2005 13:10:15 11264 E
110 Prg CL_SALV_BS_RUNTIME_INFO=======CP 110 04/08/2008 07:18:11 34816 E
111 Prg CX_SALV_BS_SC_RUNTIME_INFO====CP 111 04/05/2008 23:12:46 10240 E
112 Typ SCX_SRCPOS 0 05/18/2004 14:07:11 2048
113 Prg CX_SALV_BS_SC_MSG=============CP 113 04/05/2008 23:12:46 9216 E
114 Prg CX_SALV_BS_SC=================CP 114 04/05/2008 23:12:45 8192 E
115 Prg CX_STATIC_CHECK===============CP 115 07/05/2005 13:10:16 8192 E
116 Prg CX_ROOT=======================CP 116 04/08/2008 05:35:49 9216 E
117 Prg CX_NO_CHECK===================CP 117 07/05/2005 13:10:16 8192 E
118 Typ LVC_S_SGRP 0 11/15/2000 17:38:36 2048
119 Typ DTC_S_TS 0 08/27/1999 18:05:22 3072
120 Typ LVC_S_COL 0 12/21/1999 19:15:32 2048
121 Typ ALV_S_QINF 0 02/14/2002 14:03:24 2048
122 Prg SAPLKKBL_EXT 122 04/08/2008 07:18:22 15360 E
123 Typ ASEXDOM 0 11/09/2000 14:18:18 2048
124 Typ DD01L 0 12/28/2004 17:07:19 5120
125 Typ FLT_S_LAYO 0 12/04/2000 12:46:41 3072
126 Prg SAPLSLVC 126 04/09/2008 07:47:55 374784 E
127 Prg SAPLSLVC_DIALOG 127 04/09/2008 07:47:55 591872 E
128 Typ LVC_S_FILT 0 11/15/2000 17:38:34 6144
129 Typ RSDSSELOPT 0 04/04/1995 16:11:56 2048
130 Typ LVC_S_RPRP 0 12/04/2000 12:48:05 2048
131 Typ LVC_S_FCAT 0 05/18/2004 14:08:02 16384
132 Prg %_CRSDS 127 02/18/2005 14:15:39 8192 E
133 Prg %_CSSCR 127 03/30/2005 10:21:45 9216 E
134 Typ RSDSFIELDS 0 08/20/1998 10:57:22 2048
135 Typ FLDCONVERT 0 11/09/2000 14:07:44 4096
136 Typ RSDSTEXTS 0 08/20/1998 10:57:32 2048
137 Typ RSDSEVFLDS 0 08/20/1998 11:23:14 2048
138 Typ LVC_S_SELF 0 12/04/2000 12:48:07 3072
139 Prg SAPLSPRI 139 04/09/2008 07:47:57 302080 E
140 Prg CL_ABAP_TYPEDESCR=============CP 140 07/05/2005 13:10:15 25600 E
141 Prg CL_ABAP_ELEMDESCR=============CP 141 07/03/2006 10:26:16 31744 E
142 Prg CL_ABAP_DATADESCR=============CP 142 07/05/2005 13:10:15 16384 E
143 Prg CL_ABAP_REFDESCR==============CP 143 07/05/2005 13:10:15 20480 E
144 Prg CL_ABAP_STRUCTDESCR===========CP 144 04/09/2008 07:46:57 34816 E
145 Prg CL_ABAP_COMPLEXDESCR==========CP 145 07/05/2005 13:10:15 14336 E
146 Prg CL_ABAP_TABLEDESCR============CP 146 07/05/2005 13:10:15 21504 E
147 Prg CL_ABAP_CLASSDESCR============CP 147 07/05/2005 13:10:15 25600 E
148 Prg CL_ABAP_OBJECTDESCR===========CP 148 07/05/2005 13:10:15 29696 E
149 Prg CL_ABAP_INTFDESCR=============CP 149 07/05/2005 13:10:15 20480 E
150 Prg CL_ABAP_SOFT_REFERENCE========CP 150 07/05/2005 13:10:15 8192 E
151 Prg CL_ABAP_REFERENCE=============CP 151 09/09/2004 14:18:16 6144 E
152 Prg CL_ALV_XSLT_TRANSFORM=========CP 152 04/08/2008 05:52:50 15360 E
153 Prg CL_SALV_FORM_ABAP=============CP 153 04/08/2008 05:36:11 30720 E
154 Prg CL_SALV_FORM_ABSTRACT=========CP 154 01/05/2006 12:07:55 7168 E
155 Prg CL_SALV_FORM==================CP 155 04/08/2008 05:35:59 9216 E
156 Prg CL_SALV_FORM_CONTENT==========CP 156 07/05/2005 13:10:15 7168 E
157 Prg SAPLSYMB 157 08/16/2006 11:56:00 94208 E
158 Prg CL_ABAP_LIST_UTIL_INTERNAL====CP 158 07/05/2005 13:10:15 14336 E
159 Prg CL_SCP_LINEBREAK_UTIL=========CP 159 07/05/2005 13:10:15 12288 E
160 Prg CL_ABAP_LIST_UTILITIES========CP 160 07/05/2005 13:10:15 18432 E
161 Prg %_CSYDES 99 02/18/2005 14:16:04 7168 E
162 Prg CL_GUI_ALV_GRID===============CP 162 04/09/2008 08:15:28 620544 E
163 Typ LVC_S_RPID 0 11/10/1998 05:38:53 2048
164 Typ LVC_S_LAYL 0 11/09/2000 14:09:15 2048
165 Typ LVC_S_BDS 0 09/09/2004 14:16:48 16384
166 Prg CL_GUI_ALV_GRID_BASE==========CP 166 04/09/2008 07:25:08 201728 E
167 Prg CL_GUI_CONTROL================CP 167 02/28/2005 21:03:09 103424 E
168 Prg CL_GUI_OBJECT=================CP 168 04/09/2008 07:47:07 370688 E
169 Prg CL_GUI_CFW====================CP 169 02/28/2005 21:03:09 153600 E
170 Prg CL_GUI_PROPS_CONSUMER=========CP 170 02/18/2005 14:15:08 26624 E
171 Prg SAPLTHFB 171 04/09/2008 07:55:13 342016 E
172 Typ EUDB 0 11/06/2003 20:28:08 8192
173 Prg CL_DYNAMIC_GUI_EXTENSIONS=====CP 173 02/18/2005 14:15:28 33792 E
174 Typ TOLE 0 07/29/1998 19:56:01 3072
175 Prg %_COLE2 52 02/18/2005 14:15:28 8192 E
176 Prg SAPLSCP2 176 04/09/2008 07:29:18 112640 E
177 Typ SWCONT 0 04/04/1995 16:18:01 2048
178 Prg IF_SALV_C_CELL_TYPE===========IP 99 09/30/2004 13:31:06 4096 E
179 Typ EUINFO 0 07/16/1997 14:45:04 6144
180 Typ SYST 0 09/09/2004 14:18:12 27648
181 Prg IF_CACHED_PROP================IP 167 02/18/2005 14:12:55 4096 E
182 Typ RSJOBINFO 0 04/29/1992 14:52:25 3072
183 Prg %_CSYLDB 0 02/18/2005 14:15:48 6144 E
184 Typ RSVARKEY 0 05/07/1997 13:07:54 2048
185 Typ CAT_SVARS 0 05/18/2004 10:32:36 2048
186 Typ LVC_S_MSG 0 12/04/2000 12:48:05 5120
187 Typ DEVPAR 0 12/04/2000 12:46:11 3072
188 Typ PRIPAR_EXT 0 05/18/2004 14:07:03 3072
189 Typ PRIPAR_EX2 0 11/09/2000 14:10:39 2048
190 Typ PRIPAR_EX3 0 05/18/2004 14:07:03 3072
191 Typ PRI_LAYOUT 0 11/06/2003 20:30:04 3072
192 Typ RSTXP 0 11/06/2003 20:30:36 14336
193 Prg IF_SALV_BS_C_TT===============IP 70 04/05/2008 23:17:50 6144 E
194 Prg IF_SALV_C_TABLE_OBJECTS=======IP 70 09/30/2004 13:26:19 4096 E
195 Prg IF_SALV_C_BOOL_SAP============IP 70 07/05/2005 13:10:16 4096 E
196 Typ USR02 0 02/18/2005 13:54:26 7168
Directory of Application Tables
Name Date Time Lngth
Val.
Program ZDMS_REPORTING
SYST 09/09/2004 14:18:12 00002408
0000000x010000000x0100000000000
USR02 / / : : 00000244
000000000000000000000000
SSCRFIELDS 09/09/2004 14:18:02 00000854
SSCRTEXTS / / : : 00000371
Program RSDBRUNT
RSVUVINT / / : : 00000047
VARID / / : : 00000132
ZDMS_REPORTING
Program SAPLSVAR
VARIS / / : : 00000061
100ZDMS_REPORTING 1000T1
Program SAPLICON
ICONT / / : : 00000065
E@20@Select: Equal to
Program SAPFSDS1
TDCLD / / : : 00000050
RE DOKU 8R XX XXLIMUDOKUX x1E0XR3TRPROGX
Program SAPLSDOD
DOKIL / / : : 00000076
Program SAPLLANG
T002 / / : : 00000005
ES1EN
Program SAPLOLEA
TOLE / / : : 00000197
SAPGUI.APPLICATION {83658045-6571-3232-
Program SAPLSKBS
LTDXS / / : : 00000065
Program SAPLKKBL
RSJOBINFO / / : : 00000084
00000000000000
EUINFO / / : : 00003096
0000
Program CL_GUI_PROPS_CONSUMER=========CP
EUDB / / : : 00003940
%C000310004806980C06F50C5AE10080039D747EF9 0000
ABAP Control Blocks (CONT)
Index Name Fl PAR0 PAR1 PAR2 PAR3 PAR4 PAR5 PAR6 Source Code Line
46388 BRAF 05 0008 LKKBLF99 2811
46389 ASSI 80 0000 402E 401A 0000 0000 0000 0000 LKKBLF99 2812
46393 move FF 047C 0221 0054 LKKBLF99 2813
46395 BRAX 00 0007 LKKBLF99 2814
46396 ASSI 80 0000 4091 401A 0000 0000 0000 0000 LKKBLF99 2815
46400 move FF 047C 0221 00B7 LKKBLF99 2816
46402 BRAX 00 07E0 LKKBLF99 2818
46403 cmpr 00 00CA 05F1 0004 LKKBLF99 2818
46405 BRAN 02 0002 LKKBLF99 2818
46406 BRAX 00 0012 LKKBLF99 2818
46407 cmp1 00 0242 061D 0007 LKKBLF99 2819
46409 BRAF 05 0008 LKKBLF99 2819
>>>>> ASSI 80 0000 402F 401A 0000 0000 0000 0000 LKKBLF99 2820
46414 move FF 047C 0221 0055 LKKBLF99 2821
46416 BRAX 00 0007 LKKBLF99 2822
46417 ASSI 80 0000 4092 401A 0000 0000 0000 0000 LKKBLF99 2823
46421 move FF 047C 0221 00B8 LKKBLF99 2824
46423 BRAX 00 07CB LKKBLF99 2826
46424 cmpr 00 00CA 05F1 0005 LKKBLF99 2826
46426 BRAN 02 0002 LKKBLF99 2826
thanks
ajai -
Lock ups and dumping psyical memory!!!
Hi i have just installed a new pc most of the stuff im useing is from my old computer so i know they work fine im running a:
P4 3GHZ Prescot 800MHz, HT-Enabled
865PE Neo2-P
512 DDR-400 Twin moss
ATI Radeon 9000 pro
PSU-400
XP Pro
My computer locks up alot when running intense games (games have worked before no problem) i also get a error saying dumping pysical memory, i have looked about and tried to solve this myself, i found that someone was haveing the exact same problem as me and he fixed it by turning the FSB down as his memory wasnt compatable with his motherboard if doing that works how do i do it ?
Many thanks JonathanFlappa, Your memory " clock" is fine and there is no need to "underclock it" as long as you did not mess with the Bios.
I had the same problems. I could not even get thru a Clean install of windows as it would Blue Screen
1- are you running in " Dual Channel Mode"?
2- If so is your memory a " match Set"?
some times memory even thought it has the same markings is not matched . Dual channel sets are matched and made to run together in "Dual Channel Mode"{
( Even though I had the same manufacturer memory my set would not run in Dual Channel without " Blue Screening" I bought a Matched Set of Kingston Valueram and have not had a problem since
3- If it is not a matched set, pull one stick out and run it for a while , if it still bluescreens try the other stick
4- raise your memory voltage to 2.7 or 2.8 ( which ever is the lowest that it runs stable)
5- If all this does not work , run MEMTEST to see if there is a problem with both sticks
6- you are running a Bios Version that supports the " Prescott Microcode" right?
Let us know what your findings are
Good Luck
Dave -
Report J_1IEWT_CERT getting cancelled, generating ABAP dump!
A long running report J_1IEWT_CERT in background mode is getting cancelled after running for a while and generating the following dump :
Error analysis
When changing or deleting one or more lines of the internal table
"\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]" or when inserting in the table
"\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]", 0 was used as
the line index. An index less than or equal to zero is not
allowed.
The error can occur when using the following options:
1. "INDEX idx" for specifying the line number in the table
"\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]"
where you want to change, insert or delete.
2. "FROM idx" for specifying the start index when deleting a line
area from or inserting a line area into the table
"\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
3. "TO idx" for specifying the end index when deleting a line
area from or inserting a line area into the table
"\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
At the time of the termination, the table contained 17008 lines.
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:
"TABLE_INVALID_INDEX" " "
"J_1IEWT_CERT" or "J_1IEWT_CERT_F01"
"FILTER_DATA"
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".
Tried searching for some SAP Notes to fix the issue, no success as of now, Please help me out...Have you checked these notes ?
363107 Short dump occurs during TDS certificate printing.
803806 Error while genrating TDS certificate 03.01.2005
1066049 J1INCERT - Error while generating TDS certificate
Regards,
Subhash -
Short dump 'Table does not exist in database'
Hello All,
When a report is executing it is going to short dump by saying 'Table does not exist in database'. As per the short dump analysis this issue is happening because of the following Native SQL statement statement :
Program : %_T050N0 (This is a dynamic program generating by SAP )
Form Name : DYN_LIC_SEL_TOT
exec sql performing LOOP_MOVE_WRITE_ISAP.
select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty into :dcat-lplate, :dcat-matnr,
:dcat-werks, :dcat-charg, :dcat-holdflag,
:dcat-qty from ZLICENSE_R2 where itm_num = :p_matnr and
model_lot = :p_charg
endexec.
As per the customer this issue occurring since they migrated the SAP back-end data base from Oralce to DB6. Here I felt that ZLICENSE_R2 is not migrated from the Oracle to DB6. But as per the BASIS Team, even this table was not maintained in Oracle also. If the table was not maintained in the Oracle, this issue should have been there even before migration also.
Following is the short dump details:
Short text
Table does not exist in database.
What happened?
The table or view name used does not
exist in the database.
The error occurred in the current database connection "DEFAULT".
What can you do?
Check the spelling of the table names in your report.
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_NATIVE_SQL_ERROR', was not
caught in
procedure "DYN_LIC_SEL_TOT" "(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:
Triggering SQL statement: "select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty from ZLICENSE_R2 where itm_num = ? and model_lot = ? "
Database error code: "-204"
Could you please let me know what might be the reason for this issue.
Many Thanks in Advance.Transaction SE11, input ZLICENSE_R2 for table name, and display the table. Did the table display? If not, that is the main problem.
If the table displays, go to menu item Utilities -> Database Object -> Database Utility
In the resulting screen, under the "Status" fields, you should see text "Exists in the database." If you don't, then the table exists in the dictionary, but doesn't exist in the database system. Click the "Create database table" button and then you should be able to run the program.
You may need basis team's help to carryout some of these actions. -
Short Dump while scrolling in a maintenance view
A maintenance view has one field, defined as "Radiobutton".
1) Select the radiobutton for one entry.
2) Scroll down so that in the new page (i.e. the entries displayed in the new page) the entry selected in the first step is not visible.
3) Select any radiobutton again corresponding to any of the entries displayed in the new page.
4) On scrolling up again the short dump occurs.
The short dump text says "More than one radio button is active".
Any inputs in this regards are appreciated.
Thanks.
Gajendra.Hi,
that means you are trying to make two radio buttons active.
parameters: ra radiobutton group g1 default = 'X',
rb radiobutton group g1.
ra = 'X'.
and rb = 'X'.
in your case so obviously it will dump.
check your coding..
and show your code...
Regards
vijay -
Is it possible to create manually a dump?
Dear all,
I have a question about Dumps created in SAP while programs run with unpredicted errors.
I have a specific table defined in the dictionary which has two coloumns progId and path.
The first one is a unique identifier given to a program and the second column is an absolute path on the
unix server where SAP is installed.
For example
MyProg | /usr/tmpbatch/data/E200
Means that the ABAP program named 'MyProg' will run and its output file (the output of the program) and the
log file are created in /usr/tmpbatch/data/E200.
In each of my programs, first of all I check the content of this table in order to ensure that the path is defined for the
given program (and therefore I may be able to create avec success both output and log files). If there is no entry
in the table for the given program, I leave the program by calling the STOP instruction.
My programs run at night, so the next day the corresponding users read the content of the generated output/log files.
As a result, if the path is not defined properly for a given program in the table, the program is not run and therefore
there will be no output/logfile the next day.
My question is How can I inform the user who arrives the next day observing that one program has not been run? How
can I tell him by some kind of system message that the program exited because the path for the files had not been defined in
my table?
Each morning, we can analyse the dumps which were produced during the precedent day. So that we may know
(approximately) what went wrong. But as far as I know, dumps are generated automatically by the system. Is it possible
to generate a dump (by calling some fucntion) with an appropriate error message for my problem?
Thanks in advance,
DariyooshHello again,
First of all I would like to thank everybody for their attention to my problem and
for spending time for answering my question. Thank you all very much.
Currently, Thomas' solution about MESSAGE_TYPE_X seems to work pretty well
for my problem. As all of you mentioned that, there should be softer methods to inform
users. One main problem is that the program which lanuches my programs during night
is not a sap user, it is a Unix scheduler (please forgive me I don't know these administration
details and how they work) so according to what the administrator told me it is not possible
to send email. As a result, I think I may go with MESSAGE_TYPE_X until I found another proper way.
Once again, thank you all for your help.
Kind Regards,
Dariyoosh -
Error while importing a dump file in Oracle 10g R1
Hi all,
While trying to import a schema using Data Dump, I am facing the following issue -
UDI-00018 - Import utility version can not be more recent than the Data Dump server.
Following is the version information of the source and target DB and the utilities :
Source DB server : 10.1.0.2.0
Export utility : 10.1.0.2.0
Import utility : 10.1.0.2.0
Target DB server : 10.1.0.2.0
Export utility : 10.2.0.1.0
Import utility : 10.2.0.1.0
I can figure out the cause for the problem, but don't know how to resolve it.
Any help will be appreciated.
Thanks in advance.
Gitika KhuranaHow did you get thre DMP file created and how are you trying to import the dump file? Could you post the commands you're using, please?
-
Error_Exception dump while opening the report in RRMX
Hi All,
When User trying to open the report Error_Exception dump is coming for few Info Providers. Please find attached dump for your reference.Issue is res loved, We have analyze the short dump ,when loads were running and at that if time user executed the queries then that dump was occuring.
-
SHORT DUMP WHILE EXECUTING DTP.
Hi Gurus,
I have got a short dump while executing DTP the Error is as Follows.
Runtime Error: MESSAGE_TYPE_X.
Reasons for Error: 1.The installation of the SAP GUI on the present server is faulty or obselete
2.There is a error in the application program
And i have sent the sreen shot of the Short Dump to BASIS TEAM and they have replied me that they have to install some patches and it will take some time.
But i have no much time and i have to someway or the other execute the DTP and load the data.
Is there any shortcuts for this i mean to say without the involvement of Basis team that i can do in th BI System
Regards
Amar.Hi Amar,
If the problem is with with System itself, how can we all have a short cut in that case. You may give it another trial, but you have to wait for the patches to be applied. Ask your basis team to get it done ASAP.
Thanks..
Shambhu
Maybe you are looking for
-
Issue with font of correct answers
As you can see below, the correct answer provided during question review is too large to fit within the box that is provided for it. I have scoured the user manual and forums to figure out which object this is in order to change its font, but I have
-
If you are on the Monthly view and you create an event that spans multiple days but have specific start and end times (i.e. not "All Day Events"), for example, 9am Tuesday to 1pm Wednesday, then iCal fails to display the event spanning the days. It o
-
Suddenly cannot open mail app on my computer
cannot open mail app? Has always been fine, much of touched something I'm not familiar with??
-
My recently transferred songs are not playing in my Iphone.
My recently transferred songs are not playing in my Iphone. Even though the files appear to be there, I simply cannot access them. A small circle with a dot appear on the side of each file. What is happening?
-
Two tier battery percent level indication
My phone behaves as though there are two different battery levels, (about 30% different) and it switches between them. So that sometimes I perceive an apparently rapid drop, and sometimes I see an increase in level without any charging. It may stay i