From the technological perspective, SAPâ€™s Web Dynpro for ABAP and Java is really a revolutionary part of the introduction of web-based UI technology. It’s totally unlike any design paradigm ever utilized by SAP before and signifies a quantum leap in the introduction of web-based, ERP programs.
What’s the Design Philosophy Behind Web Dynpro?
Web Dynpro Primary Benefits
- Web Dynproâ€™s main goal is to enable application developers to create powerful Web applications with a minimum of effort using descriptive tools in a structured design process.
- One guiding principle in the Web Dynpro philosophy is: the fewer lines of hand-written code there are in the UI, the better. Web Dynpro pursues this goal in two ways.
- Web Dynpro uses a declarative, language-neutral metamodel for defining a user interface. From this abstract definition, The development environment generates the required Java/ABAP code.Â Hand-written code still has its place but is confined to that required to manipulate the business data, not the user interface.
- Web Dynpro provides technical features such as support for internationalization, flicker-free interaction and a clean separation of the business logic and the user interface. This separation is achieved through a modified implementation of the Model-View-Controller (MVC) design paradigm.Â MVC was invented by Trygve Reenskaug in the late seventies and first implemented in the Smalltalk-80 language.
- Since the repetitive tasks of UI coding have been all but eliminated, the developer can focus their attention on the flow of business data through the application.
- Web Dynpro applications can run on a range of devices and on various types of network â€“ an important feature for collaboration scenarios.
Metamodel Concept and Declarative Programming
- A Web Dynpro application is developed using a declarative programming approach. Within the ABAP Workbench, there are special tools that allow you to build and abstract representation of your application in the form of a Web Dynpro metamodel. The necessary source code is then generated automatically and conforms to a standard architecture known as the Web Dynpro Framework (WDF).
- The WDF allows each controller within a component to have a set of standard hook methods. It is within these hook methods that any required custom coding can be placed.
- In addition to the events provided by the WDF, you can also define your own events for a Web Dynpro application.
- All Web Dynpro applications are constructed from the same basic units. However, through the use of custom coding in the standard hook methods, the standard framework can be extended to supply any required business functionality.
Application Situations with Web Dynpro
- RFC Modules, for example, BAPIâ€™s within an SAP ABAP after sales system. This interface is supplied by the Adaptive RFC Layer (aRFC).
- Enterprise JavaBeans (EJBs) which encapsulate application logic.
- Web Services
- A node must exist in the context of the controller acting as the mapping origin. This node need not have any declared child nodes or attributes.
- The mapping origin controller must be a custom controller.
- The controller containing the mapped node must declare the use of the mapping origin controller as a required controller.
Data binding is the means by which data is automatically transported from a view controllerâ€™s context to a UI element in its layout.You may not bind UI elements to context nodes or attributes that occur in some other controller. UI elements are private to the view controller within which they are declared.
The data binding process decouples the UI element object from the application code within the view controller. Therefore, in order to manipulate UI element properties, the application code in the view controller needs only manipulate the values of context nodes and attributes to which the UI elements are bound. The Web Dynpro Framework then manages the following two tasks:
- The transport of data from the context to the UI element during the screen rendering process.
- Repopulating the context from the UI element after data is entered by the user.
Windows, View Sets and View Areas
- All the possible views that could exist in the componentâ€™s visual interface.
- The layout and position of those views within view sets and view areas
- The navigation links that exist between different views
You can embed either a single view or one or more view sets into a window. Each view set in turn is divided into view areas, each of which can have one or more views or view sets embedded within it.A view area can only display one view at a time. Navigation links must be defined between views in order for the contents of a view area to be replaced.
View areas can be blanked out by creating an empty view whose inbound plug responds to an appropriate navigation event.
Web Dynpro Architecture
- The horizontal dotted line separates the entities that are visible from outside the component, from those that are only visible from within the component.
- A view consists of a view layout and the corresponding view controller. A view can contain navigation plugs, methods, and a context.
- A window embeds one or more views and has a corresponding window controller. A window can contain navigation plugs, methods, and a context.
Web Dynpro Application
In the same way that the functionality in an ABAP module pool can be accessed by defining multiple transaction codes, so the functionality of a single Web Dynpro component can be accessed by defining multiple applications.
To be able to define an Web Dynpro application, you have to specify
- The component to be invoked. This component is then known as the â€œrootâ€ component,
- Which interface view of the root component will be used as the initial view assembly,
- Which inbound plug will act as the entry point for the nominated interface view (this inbound plug must have the Startup check box selected)
Watch out this space as we introduce some tutorials covering every aspects of web Dynpro ABAP.
Floorplan Manager for Webdynpro – Developers Handbook
FPM (Floorplan Manager) is an application provided by Web dynpro Application that provides a framework for developing webdynpro applications interfaces which are consistent with the SAP’s UI guidelines.
Download Developers Guide Floorplan Manager.
Wait… Where you looking for Webdynpro for Java
Good collection of tutorials on SAP Web Dynpro for Java tutorials covering the below topics. Get started here and then download the rest below.
- Introduction to Web Dynpro
- Working with UI Elements
- Working wtih UI Modeling
- Error Handling
- Generic UI Services
- Dynamic Programming
- EJB Model
- Web Services Model
- Adaptive RFC Model
- Working with Popups
- Business Graphics
- Structuring Web Dynpro Applications