This month's article will be a study in the use of little-known tool available in the ABAP Debugger, the Web Dynpro Tool. The author is a co-worker and a friend.
ABAP Web Dynpro
Many people think of MVC design pattern as a means for separating data presentation from data processing, and this is certainly true. However, the separation of data presentation from data processing is only one use case of a much more fundamental concept — namely, the separation of those parts of the program that generate data from those parts that consume data — and it is this fundamental principle that you see time and again within the Web Dynpro architecture.
One of the best things about building Web Dynpro applications is that their architecture is defined declaratively, rather than programmatically. This means that you use graphical tools to build units of the application — for example, screen layout, the navigation paths from one screen to another, and the data structures used to hold the business data — and then the Web Dynpro development environment ties them together to create the final application.
What is web Dynpro? It’s SAP’s newest user interface (UI) development option for the SAP NetWeaver platform — has been designed to become the de facto option of choice for SAP development. Web Dynpro was created because, like every other software vendor in the Web space, SAP needed a longterm, strategic solution for the many problems faced by Web developers during the implementation of browser-based business applications.