Skip to Content
0
Former Member
Dec 31, 2007 at 05:29 AM

short dump while running on produiction server

166 Views

problem: For particular input scenario it gives following short dump.

But for same scenario on production server it runs correctly.

Both the versions are same & active. code is also same.

ABAP runtime errors GETWA_NOT_ASSIGNED

Occurred on 28.12.2007 at 11:16:11

-


>> Short dump has not been completely stored. It is too big.

-


Field symbol has not yet been assigned.

-


What happened?

-


The current ABAP/4 program "SAPLCEI0 " 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

-


You attempted to access an unassigned field symbol

(data segment 2941).

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.

-


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:

-


"GETWA_NOT_ASSIGNED"

"SAPLCEI0 " or "LCEI0U29 "

"CEI0_DDB_HAS_VALUES_INTERNAL"

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.

-


System environment

-


SAP Release.............. "46C"

Application server....... "SAPCLUN"

Network address.......... "172.18.112.20"

Operating system......... "Windows NT"

Release.................. "5.2"

Hardware type............ "16x Intel 80158"

Database server.......... "DBCLUN"

Database type............ "MSSQL"

Database name............ "PRD"

Database owner........... "dbo"

Character set............ "English_United State"

SAP kernel............... "46D"

Created on............... "Apr 9 2006 21:37:58"

Created in............... "NT 4.0 1381 Service Pack 6 x86 MS VC++ 12.00"

Database version......... "SQL_Server_7.00 "

Patch level.............. "2225"

Patch text............... " "

Supported environment....

Database................. "MSSQL 6.5.213 or higher, MSSQL 7.0.1 or higher"

SAP database version..... "46D"

Operating system......... "Windows NT 4.0, Windows NT 5.0, Windows NT 5.1,

Windows NT 5.2, , System build information:,

-


, LCHN : "

-


User, transaction...

-


Client.............. 400

User................ "QPBASIC"

Language key........ "E"

Transaction......... "QA02 "

Program............. "SAPLCEI0 "

Screen.............. "SAPLQPL1 0200"

Screen line......... 34

-


Information on where termination occurred

-


The termination occurred in the ABAP/4 program "SAPLCEI0 " in

"CEI0_DDB_HAS_VALUES_INTERNAL".

The main program was "SAPLQPL1 ".

The termination occurred in line 49

of the source code of program "LCEI0U29 " (when calling the editor 490).

-


Source code extract

-


000190 *" EXCEPTIONS

000200 *" NOT_FOUND

000210 *"----


000220

000230 DATA:

000240 ls_charac TYPE api_char,

000250 lt_charac TYPE STANDARD TABLE OF api_char,

000260 ls_vali TYPE api_vali.

000270

000280 DATA: ls_mi TYPE ts_mi,

000290 ls_wi TYPE ts_wi,

000300 ls_icv TYPE ts_value,

000310 ls_defval TYPE ts_defval,

000320 ls_inco_val TYPE ts_inco_val,

000330 ls_char_list TYPE ts_char_list,

000340 lv_subrc TYPE sy-subrc,

000350 lv_kntype TYPE cukntype.

000360

000370 data: ls_vallist TYPE ddb_c04, "676840

000380 lt_vallist TYPE STANDARD TABLE OF ddb_c04, "676840

000390 ls_restrict type ddb_c03, "699141

000400 lt_restrict type STANDARD TABLE OF ddb_c03, "699141

000410 lv_rflag type c. "676840

000420

000430 *----


000440 REFRESH exp_values.

000450

000460 DESCRIBE TABLE imp_characteristics LINES sy-tfill.

000470 IF sy-tfill EQ 0.

000480 LOOP AT <gt_char_list>

-


> INTO ls_char_list.

000500 ls_charac-atinn = ls_char_list-atinn.

000510 APPEND ls_charac TO lt_charac.

000520 ENDLOOP.

000530 ELSE.

000540 lt_charac = imp_characteristics[].

000550 ENDIF.

000560

000570 LOOP AT lt_charac

000580 INTO ls_charac.

000590 IF ls_charac-atnam NE space.

000600 * input: name

000610 PERFORM read_mi_with_atnam

000620 USING

000630 ls_charac-atnam

000640 CHANGING

000650 lv_subrc

000660 ls_mi.

000670 ELSE.

000680 * input: atinn

-


Contents of system fields

-


SY field contents..................... SY field contents.....................

-


-


-


-


SY-SUBRC 0 SY-INDEX 0

SY-TABIX 0 SY-DBCNT 1

SY-FDPOS 1 SY-LSIND 0

SY-PAGNO 0 SY-LINNO 1

SY-COLNO 1