0% found this document useful (0 votes)
67 views6 pages

Context Mapping

This document contains information about Vatsala Kishore's Web Dynpro project. It includes an introduction to Web Dynpro, its benefits, components and architecture. Specifically, it discusses context mapping and data binding, which allows sharing of data between controllers in Web Dynpro applications. Context mapping requires a root node in the controller for mapping and the used controller to declare the root node. In summary, context mapping provides easy data transport between controllers in Web Dynpro.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
67 views6 pages

Context Mapping

This document contains information about Vatsala Kishore's Web Dynpro project. It includes an introduction to Web Dynpro, its benefits, components and architecture. Specifically, it discusses context mapping and data binding, which allows sharing of data between controllers in Web Dynpro applications. Context mapping requires a root node in the controller for mapping and the used controller to declare the root node. In summary, context mapping provides easy data transport between controllers in Web Dynpro.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

NAME - VATSALA KISHORE

REGISTRATION NO.- 11704815

SECTION - KM040

ROLL NO.- 04
INTRODUCTION

1.1 WHAT IS WEB DYNPRO?

1. It stand for dynamic programming used to create web


applications in SAP.
2. They follow MVC paradigm that stands for Model View
Controller which uses get and set parameters.
3. We can enhance the entities of Web Dynpro applications
using Object Navigator(transaction code SE38).

1.2 BENEFITS OF WEB DYNPRO

Today’s world is completely shifting to internet and web


applications and so is SAP .To provide the users with heck loads
of opportunities in field of Web Dynpro concept is been
introduced in SAP and with that comes many benefits along
with it that can be listed as :
1. Some optimized codes
2. Re-useability
3. Equal access to every user.
WEB DYNPRO COMPONENTS
(ARCHITECTURE)

1. Web Dynpro component acts as a container for all the user


interface elements as well as those that are hidden like the
backhand codes.
2. The User Interface elements that are contained inside the Web
Dynpro component can be classified as :

 WINDOWS
1. It consists of multiple combinations of views and the flow between
them.
2. It also contains the navigation path.
3. It can have any number of views.

 VIEWS
1. It is a rectangular box shape potrayed to the user.
2. This rectangular space consists of various User Interface elementslike
the radio buttons,check boxes or the submit button.
3. It also contains the proper layout of the elements.

 CONTROLLERS
1. The main source code of the Web Dynpro is situated inside the
controller.
2. All the global variables of the controllers are termed as controller
attributes.
3. There is a context inside the controller were in all the data displayed
by the UI elements or their properties is stored in it in a heirarchical form.
2.1 CONTEXT MAPPING AND DATA
BINDING
(ANALYSIS)

 DATA BINDING

1. It is the connection between the UI elements on the screen


and the context attributes in the corresponding controller at the
backhand which in course helps us in data transport
automatically and easily.

 CONTEXT MAPPING

1. We have a proper controller for each view in order to have


data binding.
2. For every window consists of multiple views and each view
has its own view controller.
3. When data binding is done then referencing the variable in
one controller to another controller is what is called context
mapping.
4. The ease that context mapping provides in sharing of data
between the controllers.
5. Basically whenever a root node in one controller is accessed it
is automatically supplied with data from corresponding root
node of corresponding controller.
2.2PREREQUIREMENTS FOR CONTEXT

MAPPING

1. There should be a root node present in the controller for the


mapping and must also posses further child attributes.
2. The controller that has the mapped nodes must declare the
root node as a used controller.

CONCLUSION
In general if we talk of Context Mapping it is the mapping of
one context to another where we get an implied knowledge
regarding some product without stating it prior. Here in SAP
context mapping helps us to a great extent in terms of data
transport. With great ease access of data transport at the
backhand the outcome is reflected in a smooth on the fronthand.

REFERNCES
1. WIKI HOW
2. GOOGLE
3. SAP TECHNICAL.COM

You might also like