Webdynpro ABAP is a standard UI technology for developing web applications in the ABAP environment. It uses an MVC architecture with models to fetch data, views to display the UI, and controllers to connect models and views. The main differences between ABAP Webdynpro and Java Webdynpro are that ABAP Webdynpro uses ABAP coding to access data directly while Java Webdynpro uses RFCs or web services, and the ABAP code is stored centrally on the server. Webdynpro applications are composed of components, views, and contexts to transport data. Navigation between views is established through links and plugs.

1. Webdynpro ABAP

2. Contents
 Introduction of WebDynpro
 MVC Architecture
 Difference between JAVA and ABAP Webdynpro
 WDA Components and layout
 Sample WD Application
2

3. INTRODUCTION
 Web Dynpro for ABAP(WD4A, WDA) is the SAP standard UI technology for developing Web
applications in the ABAP environment.
 Consists of a graphical development environment with special Web Dynpro tools that are
integrated in the ABAP Workbench (SE80).
 Webdynpro applications are built based on MVC architecture.
3

4. MVC Architecture
4
MVC Or "Model View Controller"
 Model enables the WD App to fetch data from
database or post data into database.
 View contains User Interface which helps to
display or accept data.
 Controller is a medium to connect model and
view.

5. Difference between JAVA and ABAP Webdynpro
 In WDA we use ABAP coding to get data but in Webdynpro JAVA we need RFC's or
Webservices to get the data.
 In WDA the code is stored centrally in the ABAP server, so it relieves the load from developer’s
machine where the code is stored in the case of Webdynpro JAVA.
 Webdynpro JAVA runs on J2EE engine which can support more number of web users at a
time.
5

6. WDA Explorer
SE 80
6

7. Webdynpro View Editor
7
Layout Tab Toolbar to “drag and drop”
UI element selection
Menu by selecting“Insert
Element”
Properties of the UI
element
View of context menu
from Change
selection

8. WebDynpro
Components
 Windows
 Views
 Layout
 Context
 Methods
 Component Controllers
 Context
 Events
Window
View
Controller
View
Component
Controller
View
Controller
View
Context Context
Context
WebDynpro Components

9. Context and Data Transport
 Context
 Like a data
container.
 Data Transport
between
controllers can
be established
with mapping
defintion.
Window
View ControllerView
Component
Controller
View ControllerView
Context
Node 1
Root Node
Context
Root Node
Node 1
Node 3
Node 2Context
Node 3
Root Node

10. Data Binding Process
Data Binding
View
Component controller
context
Component text
View controller
context
View layout
Root Node
FLIGHTS
BOOKINGS
BOOKID
CUSTID
CLASS
PASSN
PRICE
CARRID
CONNID
FLDATE
Root Node
FLIGHTS
BOOKINGS
BOOKID
CUSTID
CLASS
PASSN
PRICE
CARRID
CONNID
FLDATE

11. Navigation between Views
11
Window
Outbound plug
Navigation link
Inbound plug
Customer
List
Customer
Search
Out In

12. Questions ?
12
Email Us @ support@architectsap.com

13. Worldwide Offices:
USA (Dallas)
India (Pune)
Partner Offices:
Monterrey (Mexico)
Frankfurt (Germany)
Stockholm (Sweden)
Email:
support@architectsap.com
Corporate URL:
www.architectsap.com