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

ALV problem

Former Member
0 Likes
983

Hi guys,

I have a problem with alv grid.

My program calls an alv grid with a custum button for elaboration, after the program calls another alv grid with results of elaboration.

Problem: When I push back or abbend button in the second alv, that one dumping!

any suggestion?

Bye

6 REPLIES 6
Read only

Sandeep_Panghal
Product and Topic Expert
Product and Topic Expert
0 Likes
794

Hi Andrea,

I think you are using the same OK_CODE for two functions , try clearing the function Code(ok_code) before going to second screen.

Rgds,

Sandeep

Read only

Former Member
0 Likes
794

it would be more helpful if u can write the dump message

santhosh

Read only

Former Member
0 Likes
794

I can clear ok code, but it isn't sufficente....

dump:

<a href="http://www.hostfiles.org/download.php?id=FF9FCC38">http://www.hostfiles.org/download.php?id=FF9FCC38</a>

<a href="http://www.hostfiles.org/download.php?id=4D471D9D">http://www.hostfiles.org/download.php?id=4D471D9D</a>

thanks

Read only

Former Member
0 Likes
794

ABAP runtime errors MOVE_TO_LIT_NOTALLOWED_NODATA

Occurred on 11.04.2007 at 12:56:27

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

Assignment error: Overwriting a protected field.

What happened?

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

The program tried to assign a new value to a field even though

it is protected against changes.

The following objects are protected:

- Character or numeric literals,

- Constants (CONSTANTS),

- Function module and method parameters with the type IMPORTING

REFERENCE,

- Untyped field symbols to which a field has not yet been assigned

using ASSIGN,

- TABLES parameters, if the corresponding actual parameter is protected

against changes,

- USING reference parameters and CHANGING parameters in FORMS, if the

actual parameter is protected against changes,

- Field symbols, if the field assigned using ASSIGN is protected against

changes,

- External write access to attributes with the READ-ONLY property.

How to correct the error

The field you want to overwrite is a parameter or a field symbol:

Declare the parameter as a VALUE parameter or pass an auxiliary field

to which you assigned the value from the constant before the call.

Alternatively, you can assign the auxiliary field to the field symbol

instead of the constant.

If the error occurred in one of your own programs or in an SAP program

that you modified, try to correct it yourself.

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:

"MOVE_TO_LIT_NOTALLOWED_NODATA"

"SAPLSLVC_FULLSCREEN " or "LSLVC_FULLSCREENF02 "

"MARKS_SAVE"

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.

Read only

Former Member
0 Likes
794

Solved!!!!

I let gs_layout-box_fieldname = 'X' in the second ALV.

Thanks

Read only

0 Likes
794

Thank you for sharing the solution Andrea, that was helpful.

Best regards,

Bruno