Sie sind auf Seite 1von 82

Developing User Interfaces with Web

Dynpro for ABAP

Thomas Jung, SAP NetWeaver Solution Management


Disclaimer

This presentation outlines our general product direction and should not be relied on in
making a purchase decision. This presentation is not subject to your license
agreement or any other agreement with SAP. SAP has no obligation to pursue any
course of business outlined in this presentation or to develop or release any
functionality mentioned in this presentation. This presentation and SAP's strategy and
possible future developments are subject to change and may be changed by SAP at
any time for any reason without notice. This document is provided without a warranty
of any kind, either express or implied, including but not limited to, the implied
warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP assumes no responsibility for errors or omissions in this document, except if
such damages were caused by SAP intentionally or grossly negligent.

SAP AG 2009. All rights reserved. / Page 2


Agenda

1. Web Dynpro Motivation


2. Web Dynpro ABAP Programming Model
2.1. Views and UI Elements
2.2. Controllers and Context
2.3. Component Usage and Navigation
3. Web Dynpro Integration Capabilities
3.1. Integration into SAP NetWeaver Portal
3.2. Adobe Interactive Forms
3.3. Adobe Flash Islands
4. Summary

SAP AG 2009. All rights reserved. / Page 3


Objectives of Web Dynpro

Model-based UI development
Enforce clear separation between UI logic and business logic
Little coding, lots of design
Declarative UI development

Future Proof UI Declaration


Browser, Web Dynpro Client, Mobile Device,
Client technology independent UI definition

Central implementation of user interface standards


Accessibility support
Adobe Forms integration
Centrally provided UI elements
Internationalization support

Supports major platforms


Java (as of SAP NetWeaver '04), ABAP (as of SAP NetWeaver 7.0)

SAP AG 2009. All rights reserved. / Page 4


Motivation Web Dynpro

Web Dynpro
UI definition independent of
client technology
Web Smart other?
As much abstract declaration as possible Browser Client
Different rendering engines for different
(future) UI technologies without adapting
application coding
http://..... http://..... ???
HTML, JS XBCML, delta ???

Rendering Rendering Rendering


Engine Engine Engine

Meta Data
<xml>
<wd:xxx>
</xml>

Web Dynpro

SAP AG 2009. All rights reserved. / Page 5


Application Scenarios With Web Dynpro

SAP NetWeaver Portal


NetWeaver
Web Dynpro iView Web Dynpro iView
Business Client

Web Dynpro J2EE ABAP Web Dynpro


Web Dynpro
App Web Dynpro Web Dynpro Web Dynpro
App
App App
Runtime Runtime

ABAP
SAP
RFC, WS Workbench
NetWeaver
Developer
Studio
RMI

J2EE ABAP Business


Server EJB (e.a.) Server API (BAPI,
Backend
Business Business
Data Application
Web Services) Data

SAP AG 2009. All rights reserved. / Page 6


Web Dynpro Development in ABAP

Development completely
integrated into ABAP
Workbench
Graphical View Layout design
Declarative UI development
ABAP editor with forward
navigation
ABAP dictionary data types
directly available
Simple remote debugging
Functionality and services of
the ABAP environment directly
usable

ABAP lifecycle management


Transport
Translation
Enhancements

SAP AG 2009. All rights reserved. / Page 7


DEMO WB in Workbench
One SAP Product Family with Harmonized
User Experience Web Dynpro HTML

SAP AG 2009. All rights reserved. / Page 9


One SAP Product Family with Harmonized
User Experience Web Dynpro SmartClient

SAP AG 2009. All rights reserved. / Page 10


One SAP Product Family with Harmonized
User Experience Web Dynpro Flex

SAP AG 2009. All rights reserved. / Page 11


DEMO NWBC / Flex Client
Web Dynpro AJAX Client Succeeds HTML Client

Web Dynpro AJAX Client


Drag&Drop, Suggestion, Page Rearrangement
Use of XMLHTTPRequestObject
Validation of Simple Data Types
Extensive Keyboard Support
hot keys, access keys, function keys
In-place editing, fluid animations
Enhanced client/server communication
supporting on-demand JavaScript
New Web Dynpro UI theme SAP Tradeshow
Plus
New Lightspeed rendering engine with support
for inline CSS, JavaScript load on demand and
other performance enhancements

SAP AG 2009. All rights reserved. / Page 13


Lightspeed Rendering (7.01)

Performance improvements by new Lightspeed rendering


Only stylesheet data and client scripting is loaded that really is required for the
current screen
Reduction of client side rendering time leading to overall performance improvements
More stable rendering framework
Some changes in look and feel of existing applications (e.g. no paginator for tables
any longer)
Prerequisite for Signature design (WDTHEMEROOT=sap_tradeshow_plus)
New UI elements require Lightspeed
Switched on by default

SAP AG 2009. All rights reserved. / Page 14


DEMO Lightspeed
UI Design in Web Dynpro Advantages and
Limitations

Dozens of UI elements provided, like buttons, checkboxes,


trees, or roadmaps, with specific properties and events
- Adding custom properties/events to existing elements or
adding custom UI elements is not possible

Layout managers like Flow Layout or Matrix Layout for an easy


arrangement of UI elements
- No pixel perfect layout, no direct manipulation of
HTML/JavaScript

User interaction like F4 help or drag & drop


- Often roundtrips required, no RIA behavior

Perfect for most business requirements, but maybe not for all.

Islands as supplements for Web Dynpro


SAP AG 2009. All rights reserved. / Page 16
What Is an Island for Web Dynpro?

Regular programming model known for Web Dynpro


Web Dynpro

Data
interchange
possible

Island (displayed in plugin player)

SAP AG 2009. All rights reserved. / Page 17


Which Island Technologies Are Available?

Adobe Flash Islands


Based on Adobe Flex components
Available since NetWeaver 7.11 (ABAP and Java)
Available since NetWeaver 7.01 (ABAP only)
Controlled UI technology at SAP

Microsoft Silverlight Islands


Based on Microsoft .NET components
NetWeaver 7.02 / 7.2 (ABAP & Java)

Microsoft ActiveX Islands


SAP internal use only!
Available since NetWeaver 7.01 (ABAP only)

Web Widgets (HTML Islands)


Planned: NetWeaver 7.2 (Java only)

SAP AG 2009. All rights reserved. / Page 18


Examples- Cover Flow Product Selector

SAP AG 2009. All rights reserved. / Page 19


Examples- Google Maps

SAP AG 2009. All rights reserved. / Page 20


Examples- Interactive Organization Chart

SAP AG 2009. All rights reserved. / Page 21


New in NW 7.02/7.20
Microsoft Silverlight Islands

Works nearly identical to Adobe


Flash Islands except using the
Microsoft Silverlight Framework
SAP supplies a runtime library
(WDSilverlightIslandLibrary.dll)
in the
/SAP/PUBLIC/BC/UR/nw7/
SilverlightIslands/ MIME Folder

SAP AG 2009. All rights reserved. / Page 22


DEMO Islands
Floorplan Manager
Easy and highly productive configuration of applications

The Floorplan Manager is the preferred and mandatory tool for the creation
of new Web Dynpro ABAP applications in the SAP Business Suite

Consistency across Web Dynpro ABAP


applications

Easy configuration of predefined building


blocks

Compliance with
all SAP User Interface guidelines

APIs provided for standard functionality


like event handling and dynamic behavior

Modification free
customers adaptations of Web Dynpro
applications

Full integration in standard SAP Lifecycle


Management

Available for customers: NW 7.0 EHP 1

SAP AG 2009. All rights reserved. / Page 24


OIF (Object Instance Floorplan)

Identification
Region

Message Region
Contextual
Navigation Region
(Top)

View Container

Contextual
Navigation Region
(Bottom)

SAP AG 2009. All rights reserved. / Page 25


OIF (Object Instance Floorplan)

Floorplan
- provided by FPM
- only configuration
- dynamic behavior is possible
- no coding necessary

Content Area

Content View
- developed by application
- WD Abap coding

SAP AG 2009. All rights reserved. / Page 26


DEMO Floorplan Manager
Agenda

1. Web Dynpro Motivation


2. Web Dynpro ABAP Programming Model
2.1. Views and UI Elements
2.2. Controllers and Context
2.3. Component Usage and Navigation
3. Web Dynpro Integration Capabilities
3.1. Integration into SAP NetWeaver Portal
3.2. Adobe Interactive Forms
3.3. Adobe Flash Islands
4. Summary

SAP AG 2009. All rights reserved. / Page 28


Meta-Model Declarations and Custom Coding

Compiler

Run able App


Meta-data
Generated
Web Code
Dynpro Generator
Tools Custom
Code

Meta-model Declarations Custom Coding

Guarantees common app. design Guarantees universality

Good for graphical tool support Good for data-driven, dynamic apps
Implementation of business rules
Screen Layout and Nesting
Navigation and Error Handling Dynamic screen modifications

Data Flow Access to services (files etc.)

Componentization Portal eventing


...
...
SAP AG 2009. All rights reserved. / Page 29
Model View Controller (MVC)

Original MVC design for decoupling presentation and


application logic
Generates the application
data without caring how it
Model will be displayed.
Binds the user and business
interaction layers together. All
intermediate processing is
performed here.
Business Interaction Layer

Request User Interaction Layer


Controller
Response
Visualizes the application
data without caring how it
Binding Layer was generated.

View

SAP AG 2009. All rights reserved. / Page 30


Web Dynpro Component Architecture

SAP Web Dynpro uses principles of MVC paradigm

Controller handle the


Component Interface
user input and steer
Interface Interface
the application Interface viewview Controller
M

Views define the layout

Model hold and


Component
provide the business Controller
Window M
logic

Usage declarations
Window Controller
Components
M

Contains Usage
declarations Model 1

View M
View Custom
Controller
Layout Controller Model 2
M

Business Logic

W e b D y n p r o C o m p o n e n t (Models)

SAP AG 2009. All rights reserved. / Page 31


Web Dynpro Components

Web Dynpro Component contains


Windows
Views Component Component
UI elements Controller
Window
Layout View
View
Controllers Controller
Context Data
Eventing
Methods
Attributes
Component Interface View View
Interface Contr. Controller

Interface View

SAP AG 2009. All rights reserved. / Page 32


Agenda

1. Web Dynpro Motivation


2. Web Dynpro ABAP Programming Model
2.1. Views and UI Elements
2.2. Controllers and Context
2.3. Component Usage and Navigation
3. Web Dynpro Integration Capabilities
3.1. Integration into SAP NetWeaver Portal
3.2. Adobe Interactive Forms
3.3. Adobe Flash Islands
4. Summary

SAP AG 2009. All rights reserved. / Page 33


Views and UI Elements

Window
View
Is embedded into window
View
Defines the visible layout via predefined UI
elements
Does not contain any HTML or scripting

UI elements
Are the smallest UI building blocks (button, input
field,)
Available as provided UI element libraries
Have properties which steer their behavior
Can be nested with Container UI elements
Are positioned in hierarchical structure

SAP AG 2009. All rights reserved. / Page 34


Defining View Layout

UI
UI element element
libraries tree of
view

Properties of
selected UI
element

View
layout

SAP AG 2009. All rights reserved. / Page 35


UI Element Categories

Various categories of UI elements are supported

Each UI element object is represented as an abstract class that is independent


of any client presentation layer.
SAP AG 2009. All rights reserved. / Page 36
DEMO Hello World
Agenda

1. Web Dynpro Motivation


2. Web Dynpro ABAP Programming Model
2.1. Views and UI Elements
2.2. Controllers and Context
2.3. Component Usage and Navigation
3. Web Dynpro Integration Capabilities
3.1. Integration into SAP NetWeaver Portal
3.2. Adobe Interactive Forms
3.3. Adobe Flash Islands
4. Summary

SAP AG 2009. All rights reserved. / Page 38


Controller and Context

View Controller
Controller
Context
Contains the logic of the UI layer Root Node
Implements event handlers Node N1
Reads and writes context node content LH Attribute CARR

Each view has its own view controller Paris Attribute DEP_AIRP

Node N2
Context
Hierarchy of nodes and attributes
Contains the data of the UI method WD_DO_INIT
node = wd_context->get_child_node(N1).
Nodes and attributes can be bound to UI
node->set_attribute( name = DEP_AIRP
elements value = Paris).
Framework takes care of updating the
values Method onAction_GOTO_NEXT
node = wd_context->get_child_node(N1).
node->get_attribute( name = CARR
value = carrier ).

SAP AG 2009. All rights reserved. / Page 39


View Controller and View Context

Window

View View Controller

T* Context
Node BP

T* PART_NAME

PARTNER_ID

Node N2
Controller
contains methods
and events for
user interactions Method onAction_GOTO_NEXT
node = wd_context->get_child_node(BP).
node->get_attribute( name = PART_NAME
value = part_name ).

SAP AG 2009. All rights reserved. / Page 40


Context Node Elements

View View Controller

Context
Node BP Node 1 (Cardinality 0...n)

011 PARTNER_ID
012 013 PARTNER_ID
TECU.PARTNER_NAME
Asia Laur.. PARTNER_NAME

DE COUNTRY
JP FR COUNTRY

Node 2

Elements of a
context node

method WD_DO_INIT
* BusPartners: internal table
...
node->bind_elements( partners ).

SAP AG 2009. All rights reserved. / Page 41


DEMO Simple View & Table
Component Controller and Context Mapping

Component Controller Component Controller


Controller which is the backbone of the Component Controller
component Context
Has its own Context Root Node
Contains the logic for interaction with the Node 1
model (ABAP class, function modules, BAPIs,
Web Services)
Node 2 Model
Context Mapping
Class,
Nodes of Component Controller context can Node 3
be mapped to nodes of other contexts ABAP
Objects
Framework takes care of data transport
API,
(references)
Method show_flights
BAPIs,
flights = BO->get
node1 = wd_context->
Other WD
node1->bind_elements(
flights ). Compo-
nent,

SAP AG 2009. All rights reserved. / Page 43


Component Controller

Mapping of
Component context data Component Controller

Window Component Controller


Context
View View Controller
Context
Node 1
Context
Node 1

Node 2

Node 3

Model Class,
ABAP
Method show_bpartners
BPs = BO->get Objects API,
Component node1 = wd_context->
controller connects node1->bind_elements( BAPIs,
BPs ).
to business logic Other WD
and gets/sets data Component,

SAP AG 2009. All rights reserved. / Page 44
Exercise #1
How to Log on

Logon to Windows

User: student
pwd: teched09!

Logon to SAP workshop system


System: M23 client: 800
User: CD264A-## (## = group number)
pwd: teched09

SAP AG 2009. All rights reserved. / Page 46


Views in Views

ViewContainer UI element
Views can be structured with ViewContainer UI elements
How there are arranged within each other is declared in the window

Window MAIN_VIEW View Controller

MAIN_VIEW Context
Node 1
ViewCont.
SO_VIEW
ViewContainer

SORDER_VIEW View Controller

Label Context
Node 1

Node 2

SAP AG 2009. All rights reserved. / Page 47


Interaction Between Views and Controllers

Component Component Controller


Mapping of
context data
Window Component Controller
View View Controller Context
Context Context
Node BP Node BP
011 011
TEC TEC

OnLeadSelection Node SO
wd_comp_cont-> 5..3
View Controller
get_sorders() Node 3
View
View View Controller
Label
Context
Label Context Method get_sorders
Root Node SOs = BO->get
Node 1 Node SO node = wd_cont->
PressAttribut1
Attribut2 5..3 node->bind_table(
SOs ).
Node 2

SAP AG 2009. All rights reserved. / Page 48


Context Node at Design Time

Declaration of Context
Nodes
Create metadata which defines the
structure of the context Context
Two dimensional hierarchy like files
SALES_ORDERS (0...n)
and folders
503 SO_ID
But each node can be a collection
ITelo SELLER_COMP
Min and max number of elements in
a node is steered by Cardinality 052007 CREATE_DATE

(0..1) ITEMS (0n)

(1..1) ITEM_ID

(0..n) PRODUCT_NAME

(1..n)

SAP AG 2009. All rights reserved. / Page 49


Complex Data in Context Node

Context at runtime View Controller


Nodes with cardinality (0..n) can
contain several elements at runtime Context
SALES_ORDERS (0...n)
Each element can have its own set
of sub nodes at runtime which are 501 SR
502 503 S_ORDER_ID

again collections of elements 123.03 Swiss


403.0 99.99 AMOUNT

Example: Sales Orders with


051003 www
051223 052709 DATE

Items ITEMS

ITEM_ID
Items of selected sales order should
PRODUCT_NAME
be displayed in second table on
the same view
Each sales order has its own set of
items

SAP AG 2009. All rights reserved. / Page 50


Supply Function of Context Node

Supply Function
Is triggered if lead selection of
parent element changes
Is implemented as method of
controller
Has access to parent element
Singleton property of context
node steers if supply function is
called
Every time lead selection
changes
Only at first time for each
element

SAP AG 2009. All rights reserved. / Page 51


Exercise #2 & #3
Agenda

1. Web Dynpro Motivation


2. Web Dynpro ABAP Programming Model
2.1. Views and UI Elements
2.2. Controllers and Context
2.3. Component Usage and Navigation
3. Web Dynpro Integration Capabilities
3.1. Integration into SAP NetWeaver Portal
3.2. Adobe Interactive Forms
3.3. Adobe Flash Islands
4. Summary

SAP AG 2009. All rights reserved. / Page 53


Web Dynpro Component Usage

Reuse of Web Dynpro


Components
Real business applications usually
consist of several WD
components
Reusable components for
dedicated often used tasks in
different applications
Customer address display
Order details

Generic components as part of
the Web Dynpro environment Comp Inter Comp B
Comp A
ALV Contr. face
Select Options Context Context
Message Viewer

Method A Method B

Event E Event E

SAP AG 2009. All rights reserved. / Page 54


Web Dynpro Component Usage

Main Comp A Main Comp B Main Component

Sub Comp A Sub Comp B


Sub Component
Several main components need Main component needs different
the same functionality functionalities in a given view area
Functionality is developed once in View container provides place for
reusable component sub components
Main components declare Several Component Usages to
Component Usage of sub different sub components with the
component same Interface are defined
Sub component is instantiated in Which component is used is
each main component at runtime decided at runtime
SAP AG 2009. All rights reserved. / Page 55
Web Dynpro Component Reuse

Main Component A Comp


Controller Interface Sub Component B
Window Controller Window
View Context Context
Node Node
View View

Method A Method B

Event E Event E

Windows of a used component can


Interface Sub Component C
be embedded as Interface Views
Controller Window
into own windows or views
Context
Methods, events and context nodes Node

can be declared as part of the


View
Interface Method C

Access via Interface Controller with Event E

Context node mapping


Method call, Events raised
Embedding of Interface View
SAP AG 2009. All rights reserved. / Page 56
Concepts: Component Interface

Interface
Component Controller Component
Controller
Interface Contr. Window
Context
Component Contr.
View View Controller
Root Node
Context
Root Node
Node 1 Context
Node 1 Root Node
Node 1

Method SET_AIRP.
Node 2
View Controller
Node 3
View View Controller
View
Label
Context
Interface View
method SET_AIRP Label Contexth
Root Node Root Node
Label
Node 1 Node 1
PressAttribut1
Attribut2

Method
ViewSORT_FLIGHT
Controller Node 2
View
Label
Context
Press
Attribut1
Label
Root Node
Attribut2
Node 2
Label1
Node
Node 2

SAP AG 2009. All rights reserved. / Page 57


Navigation Between Views

Window

Customer Customer
Details Sales Orders
Out In

Inbound plug

Outbound plug

Navigation link

To define the navigation between two views, you need to create exit
and entry points for each view using outbound and inbound plugs.

Only then you can specify the navigation flow using navigation links

SAP AG 2009. All rights reserved. / Page 58


Plugs and Navigation

Create
Create Outbound Plug
Window Action

View View Controller


SHOW_SORDERS EXIT_VIEW

OnActionSHOW_SORDERS
OUT
wd_this->
fire_EXIT_VIEW_plg( ). Create
IN Navigatio
n Link

View View Controller


HandleSHOW_SO SHOW_SO

OUT Create
Inbound Plug
IN

SAP AG 2009. All rights reserved. / Page 59


Exercise #4
Agenda

1. Web Dynpro Motivation


2. Web Dynpro ABAP Programming Model
2.1. Views and UI Elements
2.2. Controllers and Context
2.3. Component Usage and Navigation
3. Web Dynpro Integration Capabilities
3.1. Integration into SAP NetWeaver Portal
3.2. Adobe Interactive Forms
3.3. Adobe Flash Islands
4. Summary

SAP AG 2009. All rights reserved. / Page 61


Agenda

1. Web Dynpro Motivation


2. Web Dynpro ABAP Programming Model
2.1. Views and UI Elements
2.2. Controllers and Context
2.3. Component Usage and Navigation
3. Web Dynpro Integration Capabilities
3.1. Integration into SAP NetWeaver Portal
3.2. Adobe Interactive Forms
3.3. Adobe Flash Islands
4. Summary

SAP AG 2009. All rights reserved. / Page 62


Web Dynpro and SAP NetWeaver Portal

Portal Integration
Generic iViews for displaying
Web Dynpro Applications
Easy integration via Web Dynpro
iView Wizard
Central User management
Portal eventing support
Object Based Navigation
Unified branding by portal
themes

SAP AG 2009. All rights reserved. / Page 63


Portal Integration

SAP Portal
Web AS ABAP application system is declared
in portal Portal iView

Server, port,
User mapping
Create iView for WD ABAP application
iView points to logical backend server, name
space and WD application Application Server Java
iView is assigned to portal role

WD Application

WD Component
Window
View

Application Server ABAP


SAP AG 2009. All rights reserved. / Page 64
DEMO Portal Integration
A Consistent and Flexible SAP NetWeaver UI

SAP NetWeaver Portal: SAP NetWeaver Business Client SAP NetWeaver Portal Client
(smart client on Microsoft Windows desktop) (zero footprint client with Web 2.0)
The yellow pages
of enterprise apps and
UI assets, with new
Web 2.0 services and
collaboration

Web Dynpro: The


heartbeat of the
runtime for enterprise
applications, providing
client abstraction
support

Provides the 1 SAP NetWeaver Portal Platform + UI Services


flexibility of model-
driven UI for both 2 Web Dynpro ABAP & Java Prog. Model + Runtime
declarative
programming and
3 Visual Composer Modeling + Eclipse
UI modeling of
Visual Composer

SAP AG 2009. All rights reserved. / Page 66


DEMO NWBC
Agenda

1. Web Dynpro Motivation


2. Web Dynpro ABAP Programming Model
2.1. Views and UI Elements
2.2. Controllers and Context
2.3. Component Usage and Navigation
3. Web Dynpro Integration Capabilities
3.1. Integration into SAP NetWeaver Portal
3.2. Adobe Interactive Forms
3.3. Adobe Flash Islands
4. Summary

SAP AG 2009. All rights reserved. / Page 68


What Does it Look Like ?

Paper-like
layout
Self-explanatory
Natural look and
feel

User Handling Background Services


Save locally Structured data in XML
Distribute via email / Portal Prefilled application values
Digital signature (future) Prefilled list boxes, help values,
Local printing Automatic data extraction
and integration in application

SAP AG 2009. All rights reserved. / Page 69


Adobe Interactive Forms in WD ABAP

Basic Forms Functionality


Define Form in system
Layout (Adobe Designer)
Data structure
Form is generated
Function for generating
PDF
API for setting/getting
data

Integration into Web Dynpro


Place Form in InteractiveForm
UI container element
Map context data to forms API
Form is displayed at runtime
Printing
Interactive Form

SAP AG 2009. All rights reserved. / Page 70


DEMO IFbA
Agenda

1. Web Dynpro Motivation


2. Web Dynpro ABAP Programming Model
2.1. Views and UI Elements
2.2. Controllers and Context
2.3. Component Usage and Navigation
3. Web Dynpro Integration Capabilities
3.1. Integration into SAP NetWeaver Portal
3.2. Adobe Interactive Forms
3.3. Adobe Flash Islands
4. Summary

SAP AG 2009. All rights reserved. / Page 72


Adobe Flash Islands in WD ABAP

Adobe Flash Applications


Rich Internet Applications for
complex visualization tasks
Developed in Adobe Flex Builder
Running in Adobe Flash Player
Used if Web Dynpro UI elements
are not sufficient for required
user experience

Integration into Web Dynpro


Running as WD Island
Contained in MIME repository
Communication to WD
component via
SAP Flash Library
Context Nodes
Events

SAP AG 2009. All rights reserved. / Page 73


DEMO Flash Islands
Agenda

1. Web Dynpro Motivation


2. Web Dynpro ABAP Programming Model
2.1. Views and UI Elements
2.2. Controllers and Context
2.3. Component Usage and Navigation
3. Web Dynpro Integration Capabilities
3.1. Integration into SAP NetWeaver Portal
3.2. Adobe Interactive Forms
3.3. Adobe Flash Islands
4. Summary

SAP AG 2009. All rights reserved. / Page 75


DEMO Final
Summary

Web Dynpro is SAPs UI strategy


Declarative, MVC based UI programming
model
UI definition independent of rendering
technology
Web Dynpro for ABAP available with SAP
NetWeaver 7.0
Programming model similar to Web Dynpro
for Java
Completely Integrated into the SAP
NetWeaver Application Server ABAP

SAP AG 2009. All rights reserved. / Page 77


Virtual SAP TechEd :
Extend your SAP TechEd Year Round

Best of SAP TechEd at Your fingertips


View sessions that you missed
Replay and review sessions that you
attended
Quality SAP TechEd Training
Best Practices
Product Roadmaps
Learn at your own pace
Gain Access to sessions recorded in
2006, 2007, 2008 and
2009* (*available December 2009)
24/7 Access online/offline
Flexible Course Syllabus
Volume Licensing
Special Pricing for multiple subscribers

http://www.sdn.sap.com/irj/scn/virtualteched-allsessions

SAP AG 2009. All rights reserved. / Page 78


Further Information

SAP Public Web:


SAP Developer Network (SDN): www.sdn.sap.com
Business Process Expert (BPX) Community: www.bpx.sap.com
SAP BusinessObjects Community (BOC): www.boc.sap.com
Web Dynpro ABAP: http://www.sdn.sap.com/irj/sdn/nw-wdabap
NWBC: http://www.sdn.sap.com/irj/sdn/nw-businessclient
Islands: http://www.sdn.sap.com/irj/sdn/adobe-flash-islands
FPM: http://www.sdn.sap.com/irj/sdn/nw-wdabap?rid=/webcontent/uuid/00b4312a-
ac72-2b10-e0ad-e0219cfeb78e
Related SAP Education and Certification Opportunities
http://www.sap.com/education/
NET310: 5-day introductory classroom training on Web Dynpro ABAP
NET311: 3-day classroom training on advanced Web Dynpro ABAP
NET312: 3-day classroom training on UI elements
NET313: new 2-day classroom training on Floorplan Manager

SAP AG 2009. All rights reserved. / Page 79


Further Information

Related Workshops/Lectures at SAP TechEd 2009


CD102, Web Dynpro ABAP Overview, Lecture (1 hour)
CD264, Developing User Interfaces with Web Dynpro ABAP, Hands-On
(4 hours)
CD260, ABAP Development: Update Your Skills to SAP NetWeaver 7,
Hands-on (4 hours)
UP162, Personalization, Configuration, and Customization of Web
Dynpro ABAP with Floorplan Manager, Hands-On (2 hours)
UP100, SAPs User Interaction Strategy: Introduction and Novelties in
SAP NetWeaver 7.2, Lecture (2 hours)
UP107, SAP NetWeaver Business Client, Lecture (1 hour)
UP264, Creating Online and Offline Form Processing Scenarios with
Adobe Forms and Web Dynpro for ABAP, Hands-On (2 hours)
UP250, ASUG Influence: SAP NetWeaver User Interaction Strategy
and User Interface Technology
SAP AG 2009. All rights reserved. / Page 80
Thank You!
Contact
Feedback
Please complete your session evaluation.

Be courteous deposit your trash,


and do not take the handouts for the following session.