ABAP_to_the_Future

12
Web Dynpro ABAP and Floorplan Manager
At this point, you can navigate to the Web Dynpro Application node, which is
somewhat like a transaction code, and click the Test icon (or press (F8)). Up pops
a browser in which you’ll see the screen flow shown at the start of this section
(Figure 12.27).
Figure 12.27 Testing the WDA Monster Monitor
Obviously, this application needs lots more bells and whistles. This example
deliberately omits things that did not add value to this discussion.
12.3 Using Floorplan Manager to Modify Existing WDA
Components
In the last section, you performed two common developer tasks: building an
overview screen with a list of objects and displaying a single business object
record (in this case, the business object was a monster). If, over the course of his
career, a programmer creates applications to display such data for 10 different custom
business objects, those objects will most likely come out looking 10 different
ways (if only subtly) and most probably will not look like standard SAP screens
that show such data.
Internally, SAP has historically been ev en more inconsiste nt; one of the most
common complaints about SAP is its UI, sp ecifically how the transactions in the
different modules have different looks an d feels. This criticism is not unwarranted:
posting a journal in SAP ERP Financials does not look much like creating
a sales order, and creating a sales orde r looks nothing like creating a purchase
order. One can only presume that the development teams in SAP ERP Financials,
546