topic modulepool-screen in Application Development and Automation Discussions

modulepool-screen

Former Member — Fri, 22 Jun 2007 09:56:17 GMT

hi,

why do we use the

Loop at screen.

if screen-group = grp.

Screen-invisible = 0 / 1.

endif.

endloop.

Re: modulepool-screen

seshatalpasai_madala — Fri, 22 Jun 2007 10:14:17 GMT

Hi,

This is to hide the SCREEN fields that are grouped under the group name 'grp'.

So if you want hide some fields on some condition then generally you group then into one screen group (SCREEN-GROUP1 or SCREEN-GROUP2 or etc etc)

and then when you say

SCREEN-ACTIVE = 0 or SCREEN-INVISIBL = 0 that entriee group becomes invisible.

but you code is missing MODIFY SCREEN between LOOP AT SCREEN and ENDLOOP.

'0' is for making it invisible and '1' to make it visible.

Regards,

Sesh

Message was edited by:

Seshatalpasai Madala

Re: modulepool-screen

former_member196299 — Fri, 22 Jun 2007 10:19:40 GMT

hi ,

Loop at screen.

if screen-group = grp.

Screen-invisible = 0 / 1.

<b>modify screen .</b>

endif.

endloop.

Screen-group provides the information about the functionality group to whcih ur screen fields are assigned to .

By using screen-invisible , you can make the screen element invisible .

You use LOOP AT SCREEN ........ ENDLOOP to do runtime modifications to the screen elements .

the statement provided is used to make the screen fields invisible , which are assigned under a screen group .

Reward if helpful !

Regards,

Ranjita

Re: modulepool-screen

Former Member — Sat, 23 Jun 2007 19:06:14 GMT

This is done to modify the screen depending on the values entered.

For example, if user clicks any checkbox, then you can hide some other selections or add other variables on the screen.

For modulepool screens, for any variable created on the screen, the attributes contains group1, group2, group3 and group4. So, using this you can modify a set of variables together by grouping.

Remember that the screen modifications should be done only in PBO.

Regards

Navneet