Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

error in ALV

Former Member
0 Likes
1,806

Hi all, pls help me its urgent,

i'm displaying one internal table in alv gri .

i used 'REUSE_ALV_GRID_DISPALY' .

it gives me alv output . but when i'm clicking on 'LOCAL_FILE' button on application tool bar then it gives dump error .

the dump error is as follows ,

' Field symbol has not yet been assigned'.

ASSIGNED

Date and Time 21.05.2008 15:26:41

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

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

Network address.......... "192.168.0.27"

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

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

Hardware type............ "2x Intel 80686"

Character length......... 16 Bits

Pointer length........... 32 Bits

Work process number...... 1

Short dump setting....... "full"

Database server.......... "PRODUCTION"

Database type............ "ORACLE"

Database name............ "P50"

Database owner........... "SAPP50"

Character set............ "C"

SAP kernel............... "640"

Created on............... "Nov 26 2007 00:46:41"

Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version......... "OCI_920_SHARE "

Patch level.............. "210"

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

Supported environment....

Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE

10.2.0.."

SAP database version..... "640"

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

Windows NT 6.0"

Memory usage.............

Roll..................... 8176

EM....................... 27176032

Heap..................... 0

Page..................... 163840

MM Used.................. 15995976

MM Free.................. 724656

SAP Release.............. "640"

User and Transaction

Client.............. 610

User................ "DEVUSER"

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

Transaction......... "ZSB "

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

The termination occurred in line 2916 of the source code of the (Include)

program "LKKBLF99"

of the source code of program "LKKBLF99" (when calling the editor 29160).

Source Code Extract

Line SourceCde

2886 else.

2887 assign <fs12> to <field>.

2888 gs_fc = gs_sfc12.

2889 endif.

2890 when 013.

2891 if gs_out_flags-slave ne 'X'.

2892 assign <fm13> to <field>.

2893 gs_fc = gs_mfc13.

2894 else.

2895 assign <fs13> to <field>.

2896 gs_fc = gs_sfc13.

2897 endif.

2898 when 014.

2899 if gs_out_flags-slave ne 'X'.

2900 assign <fm14> to <field>.

2901 gs_fc = gs_mfc14.

2902 else.

2903 assign <fs14> to <field>.

2904 gs_fc = gs_sfc14.

2905 endif.

2906 when 015.

2907 if gs_out_flags-slave ne 'X'.

2908 assign <fm15> to <field>.

2909 gs_fc = gs_mfc15.

2910 else.

2911 assign <fs15> to <field>.

2912 gs_fc = gs_sfc15.

2913 endif.

2914 when 016.

2915 if gs_out_flags-slave ne 'X'.

>>>>> assign <fm16> to <field>.

2917 gs_fc = gs_mfc16.

2918 else.

2919 assign <fs16> to <field>.

2920 gs_fc = gs_sfc16.

2921 endif.

2922 when 017.

2923 if gs_out_flags-slave ne 'X'.

2924 assign <fm17> to <field>.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,306

Hi,

Please check whether you have given field name in upper case while filling the field catalog.Also check whether you have written the proper subroutine for the functioning of that code.Also,check whether you have provided proper function code for that button.

Hi all, pls help me its urgent,

i'm displaying one internal table in alv gri .

i used 'REUSE_ALV_GRID_DISPALY' .

it gives me alv output . but when i'm clicking on 'LOCAL_FILE' button on application tool bar then it gives dump error .

the dump error is as follows ,

' Field symbol has not yet been assigned'.

ASSIGNED

Date and Time 21.05.2008 15:26:41

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

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

Network address.......... "192.168.0.27"

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

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

Hardware type............ "2x Intel 80686"

Character length......... 16 Bits

Pointer length........... 32 Bits

Work process number...... 1

Short dump setting....... "full"

Database server.......... "PRODUCTION"

Database type............ "ORACLE"

Database name............ "P50"

Database owner........... "SAPP50"

Character set............ "C"

SAP kernel............... "640"

Created on............... "Nov 26 2007 00:46:41"

Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version......... "OCI_920_SHARE "

Patch level.............. "210"

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

Supported environment....

Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE

10.2.0.."

SAP database version..... "640"

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

Windows NT 6.0"

Memory usage.............

Roll..................... 8176

EM....................... 27176032

Heap..................... 0

Page..................... 163840

MM Used.................. 15995976

MM Free.................. 724656

SAP Release.............. "640"

User and Transaction

Client.............. 610

User................ "DEVUSER"

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

Transaction......... "ZSB "

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

The termination occurred in line 2916 of the source code of the (Include)

program "LKKBLF99"

of the source code of program "LKKBLF99" (when calling the editor 29160).

Source Code Extract

Line SourceCde

2886 else.

2887 assign <fs12> to <field>.

2888 gs_fc = gs_sfc12.

2889 endif.

2890 when 013.

2891 if gs_out_flags-slave ne 'X'.

2892 assign <fm13> to <field>.

2893 gs_fc = gs_mfc13.

2894 else.

2895 assign <fs13> to <field>.

2896 gs_fc = gs_sfc13.

2897 endif.

2898 when 014.

2899 if gs_out_flags-slave ne 'X'.

2900 assign <fm14> to <field>.

2901 gs_fc = gs_mfc14.

2902 else.

2903 assign <fs14> to <field>.

2904 gs_fc = gs_sfc14.

2905 endif.

2906 when 015.

2907 if gs_out_flags-slave ne 'X'.

2908 assign <fm15> to <field>.

2909 gs_fc = gs_mfc15.

2910 else.

2911 assign <fs15> to <field>.

2912 gs_fc = gs_sfc15.

2913 endif.

2914 when 016.

2915 if gs_out_flags-slave ne 'X'.

>>>>> assign <fm16> to <field>.

2917 gs_fc = gs_mfc16.

2918 else.

2919 assign <fs16> to <field>.

2920 gs_fc = gs_sfc16.

2921 endif.

2922 when 017.

2923 if gs_out_flags-slave ne 'X'.

2924 assign <fm17> to <field>.

6 REPLIES 6
Read only

Former Member
0 Likes
1,307

Hi,

Please check whether you have given field name in upper case while filling the field catalog.Also check whether you have written the proper subroutine for the functioning of that code.Also,check whether you have provided proper function code for that button.

Read only

0 Likes
1,306

THANKS VISHAL , MY PROBLEM HAS SOLVED ......

THANKS TI ALLL FOR REPLY

Read only

0 Likes
1,306

Why dont you guys post the solution for reference once the issue is fixed.

Read only

Former Member
0 Likes
1,306

hi

once try like this

just comment the g_table in the field cat

and try

Read only

Former Member
0 Likes
1,306

Hi,

check this program as reference..

*********************************************************************

TABLES: ekko.

type-pools slis.

data my type SLIS_T_FIELDCAT_ALV with header line.

selection-screen begin of block b1 with frame title text-001.

select-options: pur for ekko-ekorg obligatory,

ord1 for ekko-ebeln,

date1 for ekko-aedat obligatory.

selection-screen end of block b1.

DATA: begin of details occurs 10,

ord like EKKO-EBELN,

org like EKKO-EKORG,

date like EKKO-AEDAT,

ven like EKKO-LLIEF,

nam like LFA1-NAME1,

item like EKPO-EBELP,

mat like EKPO-MATNR,

plant like EKPO-WERKS,

text like EKPO-TXZ01,

qty like EKPO-MENGE,

end of details.

SELECT EKKOEBELN EKKOEKORG EKKOAEDAT EKKOLLIEF LFA1NAME1 EKPOEBELP

EKPOMATNR EKPOWERKS EKPOTXZ01 EKPOMENGE into table details FROM

EKKO INNER JOIN EKPO ON EKPOebeln = EKKOEBELN INNER JOIN LFA1 ON

EKKOLIFRE = LFA1NAME1.

CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'

EXPORTING

I_PROGRAM_NAME = sy-repid

I_INTERNAL_TABNAME = 'DETAILS'

  • I_STRUCTURE_NAME =

  • I_CLIENT_NEVER_DISPLAY = 'X'

I_INCLNAME = sy-repid

  • I_BYPASSING_BUFFER =

  • I_BUFFER_ACTIVE =

CHANGING

ct_fieldcat = my[].

  • EXCEPTIONS

  • INCONSISTENT_INTERFACE = 1

  • PROGRAM_ERROR = 2

  • OTHERS = 3

.

IF sy-subrc <> 0.

  • MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

  • WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

  • I_INTERFACE_CHECK = ' '

  • I_BYPASSING_BUFFER = ' '

  • I_BUFFER_ACTIVE = ' '

I_CALLBACK_PROGRAM = sy-repid

  • I_CALLBACK_PF_STATUS_SET = ' '

  • I_CALLBACK_USER_COMMAND = ' '

  • I_CALLBACK_TOP_OF_PAGE = ' '

  • I_CALLBACK_HTML_TOP_OF_PAGE = ' '

  • I_CALLBACK_HTML_END_OF_LIST = ' '

  • I_STRUCTURE_NAME =

  • I_BACKGROUND_ID = ' '

  • I_GRID_TITLE =

  • I_GRID_SETTINGS =

  • IS_LAYOUT =

IT_FIELDCAT = my[]

  • IT_EXCLUDING =

  • IT_SPECIAL_GROUPS =

  • IT_SORT =

  • IT_FILTER =

  • IS_SEL_HIDE =

  • I_DEFAULT = 'X'

  • I_SAVE = ' '

  • IS_VARIANT =

  • IT_EVENTS =

  • IT_EVENT_EXIT =

  • IS_PRINT =

  • IS_REPREP_ID =

  • I_SCREEN_START_COLUMN = 0

  • I_SCREEN_START_LINE = 0

  • I_SCREEN_END_COLUMN = 0

  • I_SCREEN_END_LINE = 0

  • IT_ALV_GRAPHICS =

  • IT_HYPERLINK =

  • IT_ADD_FIELDCAT =

  • IT_EXCEPT_QINFO =

  • I_HTML_HEIGHT_TOP =

  • I_HTML_HEIGHT_END =

  • IMPORTING

  • E_EXIT_CAUSED_BY_CALLER =

  • ES_EXIT_CAUSED_BY_USER =

TABLES

t_outtab = details[]

  • EXCEPTIONS

  • PROGRAM_ERROR = 1

  • OTHERS = 2

.

IF sy-subrc <> 0.

  • MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

  • WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

***********************************

hope this will help..

reward if useful.

with regards,

Syed

Read only

Former Member
0 Likes
1,306

unreadable