SAP ABAP Webdynpro Tutorial

1/30/2014
SAP-ABAP-Webdynpro-Tutorial
HOME
Home
ABAP INTERVIEW QUESTIONS
About Us
Cross Applications
Contact US
RFC
BAPI
Privacy Policy
ALE IDOC
REPORTS
SAP
DIALOG PROGRAMMING
Downloads
Object Oriented ABAP
SCRIPTS
SMARTFORMS
BDC
ENHANCEMENTS
SAP Interview Questions with Answers Books

Web Dynpro
Work Flow
Downloads
Your contribution can keep this blog alive!!!
SAP ABAP Interview Questions

Like
1,336 people like SAP ABAP Interview Questions.
Facebook social plugin
Recommend this on Google
GOOGLE TRANSLATOR
Select Language
Pow ered by
Translate
FOLLOW BY EMAIL
Email address...
SAP Web dynpro, ABAP Webdynpro is the SAP standard UI(User Interface)
technology. ABAP Web dynpro used for developing web based business
applications without knowing HTML(Hyper Text Markup Language) or Javascript.
SAP Webdynpro is developed using ABAP and also Java, here in this post we are
going to know about detail over view on SAP Webdynpro ABAP introduction and
webdynpro tutorial. Click on read more to view this article.
Submit
Search
FOLLOW US ON TWITTER!
SAP ABAP Intervie

Follow
SAP Webdynpro ABAP Tutorial
+1
+ 96
SAP Webdynpro ABAP, Webdynpro is the SAP standard UI(User Interface) technology
used for developing web based business applications without knowing HTML(Hyper Text
Markup Language) or Javascript. SAP Webdynpro is developed using ABAP and also Java
here in this post we are going to know about detail over view on SAP Webdynpro ABAP.
POPULAR POSTS
50 SAP ABAP Interview Questions for Freshers &
Experienced
What is Web Dynpro:
ABAP Object Oriented Interview Questions Answers

ALE-IDOC-Interview-Questions
--> Webdynpro is the SAP standard UI technology used for developing web
business applications without knowing HTML or Javascript
--> Strict separation between the layout and business data
SAP Project Management Realtime Interview

Questions Answers
Object Oriented ABAP OOABAP Tutorials-5 Working
with Methods
SAP Web Dynpro ABAP Interview Questions
Answers
--> Reuse and better maintainability through reusability

SAP Script Interview Questions
--> Automatic input checks
SAP ALV Report Interview Questions

SAP BADI Interview Questions
--> Automatic data transport using data binding
--> WYSIWYG view editor
http://www.sapabapiq.com/2013/04/sap-abap-webdynpro-tutorial.html
Web Dynpro ABAP Interview Questions Answers
BLOG ARCHIVE
1/9
1/30/2014
2014 (14)
2013 (64)
Contents of Webdynpro:
December (4)
November (4)
Concept of View
October (1)
September (5)
Components of View Layout
August (8)
July (2)
Properties Tab
June (4)
May (5)
Context Tab
April (7)
abap-data-dictionary-interview-questions-2
Methods Tab
abap-data-dictionay-interview-questions-1
SAP-R3-System-Architecture-Interviewquestions
Attributes Tab
SAP-Tcodes-for-Client-User-Administration
Concept of Component Controller
Application
Displaying Messages
ABAP-Modularization-Techniques-Real-TimeInterview...
SAP-ABAP-Modularization-TechniquesInterview-Quest...
March (4)
February (18)
January (2)
Supply Function
2012 (74)
Cardinality Property
TOTAL PAGEVIEWS
Singleton
4 3 5 7 8 3
Lead Selection
Hook Methods
Types of Controllers
Hook Methods Chart
View and it's Concept :

We can add different UI elements that can be nested on in the other one to create
the screen.
Each view has a view controller that is automatically created for this view and each
view has several tabs (Properties, Layout, Outbound Plug, Inbound Plug,
2/9
1/30/2014
Attributes, Context, Actions and Methods).
Components of View Layout:
1) UI Element Library
2) View Designer
3) Context Menu
4) UI elements properties and
5) UI element Hierarchy
1) Properties Tab:
Here we can set the lifetime of the view
1) Framework controlled Controller by Framework
2) When Visible Lifetime limited to its visibility.
2) Context Tab:
The data are stored in the context and the UI elements are only objects the user
interacts with.
3) Methods Tab in webdynpro:
Event Handler Methods
3/9
1/30/2014
Hook Methods and (wddoinit, wddoexit etc)
User-defined instance methods
4) Attributes Tab in web dynpro:
i) wd_context:
It is a reference to the controller context. IF_WD_CONTEXT_NODE interface
provides several methods that enable us to obtain read and write access to a
context node.
ii) wd_this:
This is a self reference to local controller interface. We can use it to call user
defined methods.
iii) wd_comp_controller:
It is a reference variable of IG_COMPONENT CONTROLLER type that we can use to
access all the publically accessible methods of the component global generated
interface of the corresponding component controller.
Concept of Component Controller in webdynpro:
Data required across different views can be stored in this context
Application:
For the execution of the Web Dynpro Component.
Displaying Messages:
On the properties tab of an application we can specify how the messages are
handled.
1) Show Message component on demand
4/9
1/30/2014
2) Always display message component
Supply Function:
Each node may have a supply function defined for it and automatically called by
the Web Dynpro Framework.
The scope of using a supply function is to populate a context node. In certain
cases , we can use the Hook Method wddoinit instead of a supply function.
Cardinality Property:
It tells us how many elements a context node may have at runtime.
1 to 1 Exactly one context element is instantiated
0 to 1 Maximum one context element is instantiated
0 to n Zero or more context element is instantiated
1 to n One or more context element is instantiated
Singleton:
Unlike the Cardinality of a node which describes the number of possible elements
within the node the Singleton property determines whether or not these
elements are set for all the parent node (Non-Singleton) or for exactly one
element of the parent node (Singleton).
Lead Selection:
At runtime, every child set as a singleton contains elements for exactly one
element of the parent node. For this purpose, one element from the set of
possible elements of the parent node must be highlighted.
This is achieved by initializing lead selection. For each newly created context node,
5/9
1/30/2014
lead selection is initialized automatically.
Hook Methods:
These methods cannot be deleted and represent the interface between the
Framework and our application. The Hook Methods are called in a specific
sequence according to a Phase Model.
Types of Controllers:
1) Component Controller
2) View Controller
3) Window Controller
4) Custom Controller
Hook Methods Chart:
1)wddoinit():
This method can be considered the controller constructor. It is automatically
called when the controller is initialized for the first time.
2) wddoexit():
6/9
1/30/2014
This method can be considered as the controller destructor. It is automatically
called when exiting the controller, and can be used for executing closing
statements.
3) wddomodifyview():
This method is mostly used in the dynamic programming, it is a method used
for modifying the view before rendering.(Dynamically modifying the view)
4)wddobeforeaction():
We can use this method to perform our own validation before an action is
triggered.Check_mandatory_attr_on_view)
5) wddocontextmenu():
It is used to provide the hierarchical context menus in Web Dynpro views.
We can create a context menu at design time, by using the CONTEXT_MENUS
root, or dynamically, by coding the wddooncontext menu method.
6) wddoafteraction():
This method is called for all visible views at the time an action is executed.
Here functions can be placed that are carried out equally for all associated event
handlers.
This avoids any unnecessary multiple programming in the event handlers.
7) wddoonopen() & wddoonclose()
There are two methods are only processed when a window is opened or closed as
7/9
1/30/2014
a dialog box.
Since the opening of dialog box does not involve any navigation, no inbound plug
is called and therefore no event handler method is processed.
The wddoonopen method can therrefore be used to implement initializations.
8) wddodobeforenavigation():
It can be used to perform an additional validation of those controller contexts that
are required
in
the application
but
have not
been
validated
in
the
request/response cycle yet.
This is important for more complex Web Dynpro applications in particular. This
method is used for the component assigned to the phase model instance and
all embedded components.
9) wddopostprocessing():
This method is called in the process step before rendering. Therrefore it allows
you to add application specific clean-up processes.
10) Wddoapplicationstatechange():
This method replaces the WDDOEXIT method in the phase model.
"You found the information helpful and want to say thanks? Your donation is enough to
inspire us to do more. Thanks a bunch!"
Posted in: ABAP Interview Questions, SAP Webdynpro ABAP, Webdynpro
New er Post
Home
Older Post
8/9
1/30/2014
2 comments:
Black said...
Looking for Webdynpro abap questions?
27 May 2013 08:06
vijaykumar chowdary said...

very useful
10 July 2013 10:36
Post a Comment
Note: only a member of this blog may post a comment.
Enter your comment...
Comment as:
Publish
Google Account
Preview
Categories
ABAP Interview Questions (98) ABAP Open SQL Statements (1) ABAP Syntax Rules (5) ABAP WORKBENCH (2)
ALE IDOC (4) ALE IDOC Interview Questions (4) ALV Interview Questions (3) BADI (2) BAPI (1) BAPI Interview Questions (1) BDC (6)
BDC Interview Questions (6) Classical Reports Interview Question (2) Conditional Statements (1) Cross Applications (3) Data
Dictionary (22) Data Type Questins (1) Data types (1) Dialog programming (5) Dialog Programming Interview Questions (4) DOMAIN
Interview Questions (1) IDoc Tutorials (2) Interactive Report Interview Questions (3) Internal Tables (1) Lock Object Interview Questions (1)
Logical Database (1) Modularization Interview Questions (4) Module Pool Programming (5) Object Oriented ABAP (17) Object
Oriented ABAP Interview Questions (14) OOABAP (8) Reports (11) Reports Interview Questions (9) RFC (1) RFC Interview
Questions (1) SAP
ABAP Interview Questions (25) SAP ABAP Introduction (44)
SAP ABAP Message Types (2) SAP
SAP Basics (64)
BADI Interview Questions (2)

SAP Books (2) SAP Certification (1) SAP CONSULTANTS (5) SAP
ENHANCEMENTS (3) SAP EXITS (2) SAP EXITS ( SAP ENHANCEMENTS ) Interview Questions (1) SAP Free Books (1) SAP HR (2) SAP
Lock Object (1) SAP Open SQL Statements (1) SAP R/3 Architecture (4) SAP Search help (1) SAP Smartforms (1) SAP Smartforms
Interview Questions (2) SAP Tables (5) SAP Tcodes (9) SAP Views (1) SAP Webdynpro ABAP (12) SAP Work Processors (2) SAP
Workflow (3) Scripts (3) Scripts Interview Questions (2) Search Help Interview Questions (1) Smartforms (1) Table Maintenance
Generator (1) Tables in SAP (2) Tables Interview Questions (3) Type Group Interview Questions (1) Variable Declaration (1) Views
Interview Questions (1) Webdynpro (12)
Protected Blog
Copyright 2013 SAP ABAP Interview Questions | Powered by Blogger
This blog is not affiliated to SAP AG |SAP is trademark of SAP AG |The information collected from various sources use information w ith your ow n risk.
9/9

SAP ABAP Webdynpro Tutorial

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SAP ABAP Webdynpro Tutorial

Enviado por

Direitos autorais:

Formatos disponíveis

1/30/2014

ABAP INTERVIEW QUESTIONS

Object Oriented ABAP

SAP Interview Questions with Answers Books

Your contribution can keep this blog alive!!!

SAP ABAP Interview Questions

1,336 people like SAP ABAP Interview Questions.

Facebook social plugin

SAP ABAP Intervie

SAP Webdynpro ABAP Tutorial

What is Web Dynpro:

ABAP Object Oriented Interview Questions Answers

SAP Project Management Realtime Interview

--> Reuse and better maintainability through reusability

--> Automatic input checks

SAP ALV Report Interview Questions

--> Automatic data transport using data binding

--> WYSIWYG view editor

Web Dynpro ABAP Interview Questions Answers

Components of View Layout

Concept of Component Controller

Hook Methods Chart

View and it's Concept :

Components of View Layout:

4) UI elements properties and

Here we can set the lifetime of the view

1) Framework controlled Controller by Framework

2) When Visible Lifetime limited to its visibility.

3) Methods Tab in webdynpro:

Event Handler Methods

User-defined instance methods

4) Attributes Tab in web dynpro:

It is a reference to the controller context. IF_WD_CONTEXT_NODE interface

It is a reference variable of IG_COMPONENT CONTROLLER type that we can use to

interface of the corresponding component controller.

Concept of Component Controller in webdynpro:

Data required across different views can be stored in this context

For the execution of the Web Dynpro Component.

1) Show Message component on demand

the Web Dynpro Framework.

The scope of using a supply function is to populate a context node. In certain

It tells us how many elements a context node may have at runtime.

1 to 1 Exactly one context element is instantiated

0 to 1 Maximum one context element is instantiated

0 to n Zero or more context element is instantiated

1 to n One or more context element is instantiated

element of the parent node (Singleton).

possible elements of the parent node must be highlighted.

sequence according to a Phase Model.

Hook Methods Chart:

This method can be considered the controller constructor. It is automatically

called when the controller is initialized for the first time.

This method is mostly used in the dynamic programming, it is a method used

for modifying the view before rendering.(Dynamically modifying the view)

It is used to provide the hierarchical context menus in Web Dynpro views.

We can create a context menu at design time, by using the CONTEXT_MENUS

root, or dynamically, by coding the wddooncontext menu method.

This avoids any unnecessary multiple programming in the event handlers.

7) wddoonopen() & wddoonclose()

is called and therefore no event handler method is processed.

The wddoonopen method can therrefore be used to implement initializations.

It can be used to perform an additional validation of those controller contexts that

request/response cycle yet.

all embedded components.