As the size of Webdynpro development grows, it starts becoming complex and the need to define attributes,nodes,methods etc. However, If the node i s absolutely specific to only one view, it can be defined in the View Controller. Question 10: At design time how do you decide whether to declare a node in the Component Controller or in the View Controller? This again depends on the requirement: If the node is going to be accessed in multiple views, it should be declared at the Component Controller level. Question 9: Is it true that each controller has its own Context node ? Yes, Each controller has it‘s own context, methods, and Events. You do not have to declare a view as an interface view as is the case with interface nodes. Interface Node in Webdynpro ABAP Question 8: When do views become available in the interface Controller ? Whenever we embed any view in a window, at the moment that view becomes automatically available to the Interface Controller and shows up as an interface view in the Interface Controller. Interface Node in Webdynpro ABAP To create an interface node, set the interface property to yes as shown in the screenshot to the right : Once created, the interface node is indicated by a special symbol as shown in the figure below and the property Interface Node is set to yes: Will all 10 the nodes be available in the Interface controller? Nodes from the Component context are available to the interface controller only when the nodes are declared as interface nodes.To create an interface node, set the interface property to yes as shown in the screenshot below: Question 7: Suppose your Web Dynpro has 10 nodes in the Component Context. Note: If you are asked about the Web Dynpro architecture, you should talk about both Note: If the MVC framework and the controllers. You can create multiple controllers, but those are called Custom Controllers. Question 6: How many component controllers can a Web Dynpro Component have ? Component Controller is only one. This would actually depend on the requirement, but ideally separate Web dynpro components should be created and reused.One can also use the assistance class for segregating business logic. Question 5: Would you prefer creating multiple Custom Controllers OR would you go for separate Web Dynpro components and then do Component usage. In such a scenario, you can create one or more custom controllers and modularize or segregate the logic into separate parts using Custom Controller. Question 4: What is a Custom Controller? When your Component Controller grows big in size ( say more than 10-15 views and corresponding context nodes, methods, events, event handlers etc), it might become tough to handle everything in the Component Controller. re-using views/methods/nodes of one WD component in another. Interface Controller is created by default when a webdynpro component is created.Interface Controller would generally come into picture when you are doing component usage of some sort in web dynpro i.e. other webdynpro components), we make use of Interface controller. Question 3: What is an Interface Controller? Whenever we want views, nodes or methods of a particular web dynpro component to be available to other the outside world ( i.e. It controls the entire activity of your Web Dynpro Component. It is like a Global or Top Include for you program.

It is the backbone of your Web Dypro Component. Types of Controllers in webdynpro ABAP Question 2: What is Component Controller? Component Controller is the King of all Controllers.

SAP Web Dynpro ABAP Interview Questions with Answers Controllers in Web Dynpro: Question 1: What are the types of Controllers The types of controllers are listed in the screenshot below:

Download web dynpro abap application