ABAP_to_the_Future

Building the WDA Application 12.2
6. Configure settings to let the user navigate from one window to another in order
to see a different view.
7. Create the WDA equivalent of a transact ion code, which is in fact a URL; this
allows users to call the application.
8. (Here’s the fun bit!) Do the necessary ABAP coding to bring the Monster Monitor
to life.
12.2.1 Creating a Web Dynpro Component
Your first step in building a WDA application is to create a component. To do this,
open Transaction SE80. In the dropdown box in the top left of SE80, choose Web
Dynpro Component/Interface. You’re going to call the WDA component (program)
WDC_MONSTER_MONITOR. When you click the Display button, naturally you
get this message: Web Dynpro Comp./Intf. Zwdc _monster_monitor does not
exist. Create Object? As it turns out, you do want to create the object, so say Yes.
In Figure 12.4, you can see the resultin g pop-up box, in which you have some
questions to answer. Apart from obvious things like the text description, the system
proposes names for the default window and a default view.
Figure 12.4 Creating a WDA Component
The proposed name of the default window is the same as th e component itself.
It’s a good practice to change the name, because having different constructs with
the exact same names referring to different things can make your head spin. The
proposed name for the default view is MAIN, which is fair enough, but a more
meaningful name would make it obvious that it’s a view and would be related to
what it’s going to be displaying.
517