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 ERROR

Former Member
0 Likes
910

Hi All,

I have a ALV report with a Button with a Function Code.

I select a record and click on the button to get another ALV report.

It goes fine till then , but when i want to come back using BACK code it dumps stating

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 subroutines, 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,

- Key components of lines of internal tables with the type HASHED or

SORTED TABLE.

Here is teh Dumb analysis, Do i need to clear something before calling another ALV list fron One list ?

What happened?

Error in ABAP application program.

The current ABAP program "SAPLSLVC_FULLSCREEN " had to be terminated beca

one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

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.

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:

"MOVE_TO_LIT_NOTALLOWED_NODATA" C

"SAPLSLVC_FULLSCREEN " or "LSLVC_FULLSCREENF02 "

"MARKS_SAVE"

Information on where termination occurred

The termination occurred in the ABAP program "SAPLSLVC_FULLSCREEN " in

"MARKS_SAVE".

The main program was "ZBOM_DIST ".

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

program "LSLVC_FULLSCREENF02 "

of the source code of program "LSLVC_FULLSCREENF02 " (when calling the editor

6060).

7 REPLIES 7
Read only

former_member186741
Active Contributor
0 Likes
838

have you set these parameters properly:

i_callback_program = ???

i_callback_pf_status_set = '???'

Read only

0 Likes
838

Yes,

The i_callback_program = program name

& i_callback_pf_status_set = pf_status_set of the 1st alv

i_callback_program = sy-repid

i_callback_pf_status_set = 'STANDARD'

Read only

0 Likes
838

show us the usercommand exit form of the second program

Read only

Former Member
0 Likes
838

Hello Marc,

Iam also getting the same error at the same line and same program when i does the same thing as stated by the person posted this query...

Did zou find anz solution?? Can you please help me out if you found any solution for this.

Thanks in advance for the help!!!!

Read only

Former Member
0 Likes
838

This kind of dump usually occurs, if you try to change an import variable in your method. It has nothing to do with 'protected attributes' of a class. Sometimes it also occurs, when you try to change a variable via a field symbol, when the variable is already assigned to another field symbol.

Best regards,

Thomas

Read only

0 Likes
838

Hello,

This works fine in 4.6C version but in 4.7 it dumps because in 4.7 the control goes to the following line(<l_box> = ' '.) but in 4.6C the control dosent go to that line

a small piece of the code where its dumping:

if l_ucomm eq '&SAL' or l_ucomm eq '&ALL'.

if l_ucomm eq '&SAL'.

loop at t_outtab.

l_tabix = l_tabix + 1.

<l_box> = ' '.

modify t_outtab index l_tabix.

endloop.

Thanks in advance...

Regards,

Santhosh

Read only

0 Likes
838

Thanks everybody for spending time on this.

The problem is solved...