Show TOC Start of Content Area

Background documentation Concepts  Locate the document in its SAP Library structure

Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs). It provides a programming framework within which you can achieve a:

      Clear separation of business logic and display logic

      An application specification that is both client neutral and backend neutral

This document will lay out the structural concepts of a Web Dynpro application. You find information concerning following items:

      Underlying principles of separating presentation logic from business logic

Understand SAP’s implementation of the Model View Controller (MVC) design and find further basic concept consideration.

 More information: Web Dynpro and the Model View Controller Design

      Developing stateless applications

In addition to stateful Web Dynpro applications, also the stateless flavour is supported.

More information: Stateless Web Dynpro applications

      The client’s entry point into the functionality

The application in Web Dynpro terms is the URL that points to the visual interface of a certain Web Dynpro programming unit.

More information: Applications

      Reusable programming units   

The Web Dynpro component is the key element of a Web Dynpro application. It provides a reusable unit of code that corresponds to an atomic step within a business process.

More information: Components

      Access to business data and functionality

Model objects hide the technical communication layer needed to access data from a remote system.

More information: Models

      Active parts of a Web Dynpro component   

A Web Dynpro component contains various types of controllers, each of which play their well‑defined role within their component. Some of the controller types are responsible for the generation of information some for consuming those data by finally displaying the information on the screen.

More information: Controllers

      Data storage areas  

Every controller contains its specific data storage area referred to as the controller context.

More information: Contexts

      User interface (UI) layout

You position UI elements on a visible area referred to as view. You can combine various views on the screen. And you define the order in which views subsequently appear on the screen.

More information: Windows and Views

      User interaction handling

Client side events fired by a user’s interaction on a UI element may trigger some implemented action event handler method.

More information: Events and Actions

End of Content Area