1) What is View Controller and where it lies in the architecture.

A) View Controller:

Each view has exactly one View Controller, which processes the actions performed by the user in the view. A view also has exactly one view context, which contains the data required for the view. A view controller and the corresponding context exist at least as long as the view is visible in the browser. If the view is replaced by a successive view, the local data are also no longer available. However, the lifetime can also be connected to the lifetime of the surrounding component. 2) What is WebDynpro Component? A) A Web Dynpro component is a reusable entity. It summarizes all components that are required as part of this programming unit for an executable Web Dynpro application. The Web Dynpro component concept offers a number of advantages: Structuring of the programming Creation of easily manageable application blocks Reusability of whole components Decoupling of software projects in both time and space

The Web Dynpro component contains any number of windows and views and their corresponding controllers. Additional Web Dynpro components can also be referenced.

3) What is WebDynpro Application? A) A Web Dynpro Application is an entry point into a Web Dynpro Component and is the only Web Dynpro entity that can be addressed via a URL. There is often (but not always) a one to one relationship between an interface view

and an application. In the same way that the functionality in an ABAP module pool can be accessed by defining multiple transaction codes, so the functionality of a single Web Dynpro component can be accessed by defining multiple applications.

4) What is Interface view and interface Controller? A) Interface Controller: Each Web Dynpro component contains exactly one interface controller. This controller is a global controller . This is visible within and outside the component and is used to exchange business data. An embedding component can also call an embedded component using this controller. The interface controller, is not an independently implemented object Instead, the visibility of methods and events of the component controller can be extended beyond the limitations of the component

5) What is Window? A) Each Web Dynpro component contains at least one Web Dynpro window. All views that are to be displayed when using a Web application are embedded in this window. The window is processed in the Window Editors of the ABAP Workbench. The required navigation between the individual views can be set up in the window (see Navigation).
A window is used to combine several Views and View Sets (the concept of view sets is only offered in Web Dynpro Java). A view can only be displayed by the browser if it has been embedded in a window. A window always contains one or more views, which are connected by navigation links. One of these views, or a view set, is specified as the start view and is displayed the first time the window is called.

6) What could be the model? What objects can be model? A) A Model could be any data source. SAP Table, BAPI, RFC, Function Module, WebDynpro Component, etc. 7) What is BAPI and RFC?

A) Business Application Programming Interfaces (BAPIs) enable access to SAP functions across
formal, stable and dialog-free interfaces. These interfaces can be used by external applications developed by customers and complementary software partners as well as by other SAP applications.

Remote Function Call(RFC) is the Function Module that can be call inside you sap system from one clent to other. 8) What are the steps to map a BAPI with WebDynpro Component? A) Start the Web Dynpro Wizard through menu option create -> service call from context menu of the Web Dynpro component. In the Wizard: - Use existing component controller - Use Function module: BAPI_FLIGHT_GETLIST - Select all parameters, except EXTENSION_IN and EXTENSION_OUT - Specify method name: EXECUTE_BAPI_FLIGHT_GETLIST

9) What is Service Call? A) Service Call is a procedure to map BAPIs and RFCs into WebDynpro Components. 10) What are Custom Controler? A) Custom controllers These are the internal building blocks of a Web Dynpro component and have no user interface. They are only to be used when some unit of functionality is required by several other controllers. For instance, a custom controller could be used, when a BAPI is called, and the information returned requires some sort of intermediate processing before it can be displayed. This custom controller could then be declared for use by several different view controllers. Do not create a custom controller simply because you can! Only use one where its presence will simplify or optimize the components architecture.