ABAP_to_the_Future

12
Web Dynpro ABAP and Floorplan Manager
Then, simply repeat this procedure three times, adding the MONSTER_HEADER view
to its related container and the table entries (e.g., the row that reads MONSTER_
HEADER_ALV / SALV_WD_TABLE / TABLE ) from the (F4) list of the two ALV grids
into their respective containers. You’ll end up with the screen shown in Figure
12.19.
Figure 12.19 Completed Window Definition
12.2.6 Navigating between Views Inside the Window
What you want in life is that, when the user chooses a line on the monster header
ALV grid and presses the Show Selected Monster button, he is taken to a new
screen that shows the selected monster header record and an ALV grid of monster
items. The view definition is all sewn up , which just leaves defining the navigation
from one view to another.
Only one view can be shown at any give n time inside a window, which is why
you embedded some smaller views to leave just two possible views: V_HEADER_
GRID (for the overview ) and V_DISPLAY_MONSTER (for single record display ). To
navigate between these views, use an outbound plug to leave one view, and a corresponding
inbound plug to go into the desired view (rather than using CALL
SCREEN XXX as you would in a classic DYNPRO).
Go the view you want the user to be able to navigate away from (V_HEADER_GRID),
and then move to the Outbound Plug tab (Figure 12.20). Add an entry called OP_
TO_DIS_MONSTER; OP stands for “outbound plug,” and the rest of the name reflects
the fact that when the navigation is invoked it will take the user to the DISPLAY_
MONSTER view.
532