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

screen-group1

jaheer_hussain
Active Contributor
0 Likes
2,346

Hello ,

In the below codes.

loop at screen.

    if screen-group eq 'A1'

screen-input = 0.

modify screen

endif.

endloop.

Here what  is  screen-group  eq  'A1'?   The above code is not  working.

Can some throw light on this issue,please?

With Regards,

Jaheer...

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,814

Hi Jaheer,

Screen groups are field attributes. You can find them in the screen painter.

The error in your code is that there is no group attribute, but group1,group2,group3 and group4.

Be aware that your code must be placed in the PBO of the screen you want to change.

Hope it helps.

Regards,

Christian

7 REPLIES 7
Read only

Former Member
0 Likes
1,815

Hi Jaheer,

Screen groups are field attributes. You can find them in the screen painter.

The error in your code is that there is no group attribute, but group1,group2,group3 and group4.

Be aware that your code must be placed in the PBO of the screen you want to change.

Hope it helps.

Regards,

Christian

Read only

0 Likes
1,814

Hi Christian,

Below is the my code.

MODULE STATUS_0111 OUTPUT.

   

IF ( SY-TCODE EQ 'ME23' OR

    SY-TCODE EQ 'ME23N' ) .

LOOP AT SCREEN.

 

  IF  SCREEN-GROUP1 EQ 'A1'.

     SCREEN-INPUT = 0.

   MODIFY SCREEN.

 

  ENDIF.

 

  ENDLOOP.

ENDIF.

In the screen attributes I set group1 as 'A'.

But still it is not working. Can you tell please what is the wrong here?

With Regards,

Jaheer

Read only

0 Likes
1,814

You have to set group1 as 'A1' not 'A'.

Read only

0 Likes
1,814

Sorry  I set A1.

With Regards,

Jaheer....

Read only

0 Likes
1,814

still doesn't work?

Read only

0 Likes
1,814

Yes.Still does  not work!!!!!

Read only

0 Likes
1,814

I've tested your code here and it works. I suggest you to move your code to a form routine, set a break point and then see what is happening in the debugger. Perhaps there is a later point that is enabling the field for input again.