Web Dynpro for ABAP is the SAP standard user interface technology for developing Web applications in the ABAP environment. It consists of a runtime and graphical development environment with special Web Dynpro tools. Web Dynpro tools are integrated in the ABAP Workbench (SE80).
Web Dynpro uses ABAP as a programming language. It uses ABAP stack to execute the Web Dynpro ABAP objects. Web dynpro for ABAP supports ALV, select-options etc,. ABAP Web dynpro is not highly developed language.

• Reduces the implementation effort by using graphical tools.
• Reuse and better maintainability of components for development.
• Layout and navigation are easily changed using the Web Dynpro tools.
• User interface accessibility is supported.
• Full integration in the ABAP development environment.
• Structural changes are easy.
• Automatic data transportation using data binding.

Web Dynpro for ABAP is the SAP standard user interface technology for developing Web applications in the ABAP environment. It consists of a runtime and graphical development environment with special Web Dynpro tools. Web Dynpro tools are integrated in the ABAP Workbench (SE80).
Web Dynpro uses ABAP as a programming language. It uses ABAP stack to execute the Web Dynpro ABAP objects. Web dynpro for ABAP supports ALV, select-options etc,. ABAP Web dynpro is not highly developed language.
Web Dynpro benefits are specified below –

• Reduces the implementation effort by using graphical tools.
• Reuse and better maintainability of components for development.
• Layout and navigation are easily changed using the Web Dynpro tools.
• User interface accessibility is supported.
• Full integration in the ABAP development environment.
• Structural changes are easy.
• Automatic data transportation using data binding.

Use SE80 transaction to access Web Dynpro runtime environment and graphical tools in ABAP workbench.
Object list contains −

• Dynpro Component
• Controller
• Interface
• View
• Web Dynpro application

Web Dynpro applications are based on MVC model, whereas −
Model - This allows the access to back end data in a Web Dynpro application.
View - This is used to ensure the representation of data in a web browser.
Controller - This is used to control communication between Model and view where it takes input from users, processes data from model and displays the data in browser.

Each Web Dynpro application contains at least one view and it is used to define layout of a user interface. Each view consists of multiple user element and a controller and context.
The controller is used to process user request and data. Context contains data to that elements of view are bound.

The inbound and outbound plugs are part of view controller.
Inbound plug defines the starting point of view.
Outbound plug describes about the subsequent view to be called.

In Web Dynpro, window uses multiple views or view sets.
A view can only be displayed when it is embedding in a view.
A window always contains one or more views that are connected by navigation links.

In ABAP Workbench, we can create and show messages with information for end users of Dynpro application. These messages are displayed on the screen. These are user interactive messages that displays important information about Web Dynpro application.

• Interactive Scenario
• Print Scenario
• Offline Scenario
• Using digital signature

SAP List viewer used to add ALV component and provides a flexible environment to display lists and tabular structure. A standard output consists of header, tool bar and an output table.
User can make the settings to add column display, aggregations, sorting options using additional dialog boxes.

Events can be created to enable communication between controllers. We can allow one controller to trigger events in different controller. All events created in component controller; they are available in component.

In a Web Dynpro application, url automatically gets generated. We can find the generated URL of application in Properties tab.
URL structure can be of two types –
SAP namespace
<schema>://<host>.<domain>.<extension>:<port>/sap/abap/webdynpro/<namespace>/<application name>
Custom namespace
<schema>://<host>.<domain>.<extension>:<port>/sap/abap/xyz/<namespace>/webdynpro/<application name>

Version management used to manage older version of an object, compare versions or to reset them. In version management, we can store different versions of ABAP development objects.
In an ABAP workbench, we can compare different versions of −

• Views
• Windows
• Controllers