Many times when we design a screen, we end up putting a lot of things on just that one screen. Collapsible sub-screens are great in that they prevent clutter while not missing out on displaying important data.
For example, consider wanting to display the following:
+ ABC
XYZ
Here ABC is some contents with a button to collapse and expand. Below it is some other contents XYZ.
Logic:
We call a Screen 0100.
Screen 100 has two Sub screen areas sub1 and sub2.
Sub1 has ABC and sub2 has XYZ.
PBO makes call to both the subscreens. The trick is that the Screen No Sub1 calls is dynamic. It either calls 101 or 201, based on if the subscreen 1 is expanded or collapsed.
-->Screen 101 has a button with icon collapse. Its functional code is "EXPCO'. Next to it, it has the contents ABC. (This represents the expanded mode).
-->Screen 201 has a button with icon EXPAND. Its functional code is also "EXPCO'. As it is in the collapsed mode, the contents ABC is not displayed.
On the functional code of 100 for the button EXPCO, we toggle the subscreen number to be called.
Code
REPORT Z_PP_EXPANDER.
data:
gv_screen type sy-DYNNR value '0101',
ok_code type sy-ucomm.
call screen 0100.
* SCreen 0100
PROCESS BEFORE OUTPUT.
* MODULE STATUS_0100.
CALL SUBSCREEN sub1 INCLUDING sy-repid gv_screen.
CALL SUBSCREEN sub2 INCLUDING sy-repid '0300'.
*
PROCESS AFTER INPUT.
MODULE USER_COMMAND_0100.
module USER_COMMAND_0100 input.
data:
lv_okcode type sy-ucomm.
lv_okcode = ok_code.
clear ok_code.
if lv_okcode = 'EXPCO'.
if gv_screen = '0101'.
gv_screen = '0201'.
else.
gv_screen = '0101'.
endif.
endif.
endmodule. " USER_COMMAND_0100 INPUT
Now define the other subscreens 101, 201 and 300.
