WebDynpro- Web Dyanamic Program in ABAP

WebDynpro is a great modeling environment which stores the user-interface details in the form of metadata. We can write less code and fix bugs in a shorter time with lesser effort. It increases a programmer’s productivity by manifolds.

Webdynpro is nothing but one framework for development of user interface for use with SAP NetWeaver. It support programming for different platform such as JAVA, ABAP,.NET .

In case of JAVA webdynpro comes with extensive design tool. These tools are based upon Eclipse framework ans SAP’s NWDS

Technical Definition : WebDynpro is a client-independent programming model used for developing sophisticated user interfaces for web based business applications.

History: The name WebDynpro , Dynpro means Dynamic Program it is SAP’s Legacy technology for interactive UI’s.It is to Combine High Interactivity (dynamic GUI) and Zero Installation.

Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).

The Web Dynpro programmning model is based on the Model View Controller paradigm, and has the following features that build on the classic dynpro model:

* Clear separation of business logic and display logic
* Uniform metamodel for all types of user interfaces
* Execution on a number of client platforms
* Extensive platform independence of interfaces

What are the naming conventions to be followed while developing Web Dynpro applications?

Web Dynpro context names should use only the characters A..Z, a..z, 0..9, _ . Digits can be used only from 2nd position. The JAVA naming conventions can be followed but avoid using unicode characters to keep the names simple. However one should avoid using the prefixes wd, WD or IWD since these are the prefixes used during generation of internal coding entities.

Web Dynpro for ABAP or Web Dynpro for ABAP is the SAP standard UI technology for developing Web applications in the ABAP environment. It consists of a runtime environment and a graphical development environment with special Web Dynpro tools that are integrated in the ABAP Workbench (SE80)

Web Dynpro provides support for developing Web representation of a business application. You use specific tools to describe the properties of a Web Dynpro application in the form of Web Dynpro metadata. The necessary source code is then generated automatically and executed at runtime. In addition to the events offered by the framework, you can also define your own events for a Web Dynpro application. However, the event handling must always be programmed in separate source code areas which are executed automatically when the event is triggered at runtime.

In Web Dynpro, each user interface is always made up of the same basic elements. These elements of the metamodel can be statically declared using Web Dynpro tools.

It is also possible to implement elements of the metamodel at runtime and to change them or reintegrate them at runtime. Using these implementations, you can make changes or enhancements to a user interface that has been created by declarative methods by generating new interface structures at runtime.

This means that you can combine declarative processes and the implementation of source code.

Basic Concepts

1. View – is the central logical layout element in the Web Dynpro application.It is responsible for the presentation logic and for the browser layout.

Description of a visible screen area

Contains and lays out controls (aka widgets)
Defines actions (i.e. relevant input on controls by the user), which trigger event handling

2. Controller – active part of web dynpro application,handles the data flow between the model and the view in both directions

Performs event handling

Each component has a component controller
Each view has a view controller
Custom controllers may be added for further structuring

3. Model – is the interface to the back end systm and is responsible for providing data to the entire application.

Represents the data in the back end

4. Component

Reusable UI program package

Mostly contains views, often uses models
Communicates with other components via component interfaces

5. Application

Something runnable (from client application, i.e. web browser)

Identified by URL
Running an application means starting a component, navigating” to an initial view in an initial window.

6. Windows

Single UI unit representing a component’s user Interface/View Composition needed for embedding purposes.

7. Context

A controller contains a context which holds the data. The data flow between the contexts is referred to as context mapping.

Advantages for application developers:

● The use of declarative and graphical tools significantly reduces the implementation effort

● Web Dynpro supports a structured design process
● Strict separation between layout and business data
● Reuse and better maintainability by using components
● The layout and navigation is easily changed using the Web Dynpro tools
● Stateful applications are supported – that is, if the page is changed and the required data remains intact so that you can access it at any time throughout the entire application context.

Note that stateless applications are not possible.

● Automatic data transport using data binding
● Automatic input check
● User interface accessibility is supported
● Full integration in the reliable ABAP development environment

You can see more information about WebDynpro from : and



All about contents or data or information taken from or other sap related web sites which are available on the Internet for this BLOG.
If you find any doubts or mistakes please refer the other SAP/ABAP related sites .