Basics of ABAP Webdynpro: Getting familiar with Webdynpro jargons

This is the first post of a series on ABAP Webdynpro basics. Prior to actually starting the WD part, this post is about the terms we commonly use while working in WD. Going through this post will make you comfortable reading the further post on this series. So here, let’s start..

Webdynpro Component: The object which we create using SE80 is WD component. While creating WD component, we have to give one view and one window’s name of this component. A WD component can host any number of views and windows.

Webdynpro application: When we are done with the creation of WD component, at last we have to create the WD application. While creating application, we have to give which window out of many existing; we want to be displayed while opening the application. This WD application will have a URL in it, which we will give to our customer for using the WD application.

View: WD component can have any number of views. View means the screen or pages which we want to see in WD application. All the UI designing part we do here in view.

Window: Again a WD component can have any number of windows. Windows basically contain the views. Each and every view has to be attached to some window in order to get displayed in the WD application. A window can have multiple views. So we have to make a view as default view of the window. So in case this window is going to be the WD application’s opening window, you can guess which view, out of many views which window holds, will going to be opening view.

Inbound/Outbound Plug: Now we have a window and this window has multiple views. We want to navigate from view1 to view2. Here plugs will come into picture. View1 will have the outbound plug and view 1 will have the inbound plug. And in window we will attach the outbound plug with the inbound one. Whenever we want the navigation, we will simply fire the outbound plug.

Context node: Context nodes are the entities which will actually be attached with the UI elements in order to be displayed. Of course we will make the local variable also, but ultimately we have to bind those variables to context node and context node will in turn be bind to UI elements.

To be continued…

Basics of ABAP Webdynpro: Getting familiar with Webdynpro jargons part 2

Happy Learning :)