The title is enlivened from the book “Let us C”. An extremely famous book on “C” at our region of the planet. Web Dynpro: It is neither a device with just intuitive (the people who have really not worked would agree that this) nor is it something just for the Nerds (some who have worked could parade). In this way, neither under gauge it nor be terrified of it. It resembles some other area of SAP ABAP, which assists the engineer with accomplishing the necessity and convey a few cool applications.
Here and the series to follow, we are intending to give the ideas to figure out the nuts and bolts of ABAP Web Dynpro. This series would go about as a take off platform for our perusers to foster their underlying Web Dynpro applications. We would hand hold you and give you some genuine task prerequisites and how to accomplish them.
This series wouldn’t give you definite speculations. There are lots of materials currently accessible for hypotheses and practice.
This would be not quite the same as others and would simply focus on the fundamentals; and a few pragmatic changes and deceives.
We should begin..
We can make obscure similarity between Web Dynpro terms and traditional ABAP expressions for effortlessness. Some of them are:
Context <=> Variable
Context node <=> Internal Table/Structures/Work Areas
Context attribute <=> Fields of variables ( single field or fields of structure / internal table )
Component Controller <=> TOP include program ( declare global variables )
Custom/View Controller <=> Sub routine ( declare local variables )
Windows <=> Windows ( container )
Views <=> Views ( content )
WD Applications <=> Transaction codes
There are various UI components in WD ABAP. Yet, the most generally utilized ones are:
1. Tray
2. Group
3. Transparent Container
4. Label
5. Text Edit/View
6. Input Field
7. View Container
8. Button
9. Message Area
10. Checkbox
11. Radio Button
12. Drop down by Index
13. Drop down by Key
14. Link to Action
15. Tab Strip
16. Toggle Button
Help Class.. What precisely is it?
Help Class is the “M” of the well known “MVC”, Model View Regulator. All the extraction, kneading and demonstrating ought to be finished in the help class.
What are the moves toward start an Internet Dynpro task?
Like any typical program, you ought to initially characterize the Sorts and Information (factors, interior tables, workspaces), i.e.in WD, you ought to announce the specific situations.
Generally, typical program has determination screen boundaries and select choices. By and large, the choice screen information are worldwide. Likewise in WD, the settings for the underlying view(s) are typically characterized at the Part Regulator Level (as they are worldwide).
In ordinary projects, the worldwide factors are consequently accessible in all subroutines. In WD, the setting of the worldwide part regulator are not naturally accessible to different regulators. We really want to plan the setting of part regulator to the individual custom/view regulators. By planning, it implies, setting with a similar name is made in the custom/view regulators (and they are connected). It resembles passing boundaries to the sub schedules in ordinary ABAP. Assuming the boundaries are changed in the sub daily practice, the equivalent is reflected in the calling program. Also assuming the setting of the part regulator is changed in the custom/view regulator, it is reflected universally.
This post is only a secret for the impending series. In the following post, we would show you in basic advances, how to make a web dypro application. Furthermore, we are certain, you wont fail to remember the means after you make one.
Thank you kindly for your time!!
YOU MAY LIKE THIS
Introduction to SAP ABAP for HANA
WhatsApp us