SAP Web Dynpro Interview Questions

Are you planning to attend an interview for the SAP Web Dynpro Developer role but confused about how to crack that interview also what would be the most probable SAP Web Dynpro interview questions that the interviewer may ask? Well, you have reached the right place. Tekslate has collected the most frequently asked SAP Web Dynpro interview questions which are often asked in multiple interviews.

In this article, we will cover the following:

• Web Dynpro Interview Questions
• Web DynPro In SAP ABAP

Web Dynpro Interview Questions

Q1) What is MVC in WebDynpro ABAP?

Ans: Basically, WebDynpro follows MVC M-Model (Business logic) V-View(Screen) C-Controller (Controls screen and Model)

Q2) What is Component Controller?

Ans: The component Controller is the King of all Controllers. It is the backbone of your Web Dynpro Component. It is like a Global or Top Include for your program. It controls the entire activity of your Web Dynpro Component

Q3) What is an Interface Controller?

Ans: Whenever we want views, nodes, or methods of a particular web Dynpro component to be available to other the outside world (i.e. other Webdynpro components), we make use of the Interface controller. Interface Controller is created by default when a Webdynpro component is created.

Interface Controller would generally come into the picture when you are doing component usage of some sort in web Dynpro i.e. re-using views/methods/nodes of one WD component in another.

Q4) How many component controllers can a Web Dynpro Component have?

Ans: Component Controller is only one. You can create multiple controllers, but those are called Custom Controllers.

Q5) What is a Custom Controller?

Ans: 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. In such a scenario, you can create one or more custom controllers and modularize or segregate the logic into separate parts using Custom Controller.

Q6) What is selection cardinality in WebDynpro ABAP?

Ans: WebDynpro ABAP training Bangalore specifies how many records that can be selected from a node.

Q7) Would you prefer creating multiple Custom Controllers OR would you go for separate Web Dynpro components and then do Component usage?

Ans: 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.

Q8) How many component controllers can a Web Dynpro Component have?

Ans: Component Controller is only one. You can create multiple controllers, but those are called Custom Controllers.

Q9) When do, views become available in the interface Controller?

Ans: Whenever we embed any view in a window, now that view becomes automatically available to the Interface Controller and shows up as an interface view in the Interface Controller. You do not have to declare a view as an interface view as is the case with interface nodes.

Q10) Is it true that each controller has its own Context node?

Ans: Yes, each controller has its own context, methods, and Events.

Q11) At design time, how do you decide whether to declare a node in the Component Controller or in the View Controller?

Ans: 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. However, If the node is specific to only one view, it can be defined in the View Controller. As the size of Webdynpro development grows, it starts becoming complex and the need to define attributes, nodes, methods, etc. at the Component Controller increases.

Web DynPro In SAP ABAP

Q12) Can you use multiple layouts in one view?

Ans: Layouts can be assigned at the container level. For example, you define the layout for your view at the ROOTUIELEMENT container level.

So if at all you want to use multiple layouts in one view, you can create multiple transparent containers and assign different layouts to them.

Q13) How do you introduce a line break for a UI element in any layout?

Ans: Say if you are using matrix layout, you will say Matrix Head data for the UI element for which you need a line break.

Q14) Can you call/launch one web Dynpro application from another Webdynpro application?

Ans: Yes, you can launch one Webdynpro application from another Webdynpro application.

First, you should get the URL of the Web Dynpro component that you want to launch, and second, call that URL in an external window.

To get the URL of any web Dynpro component, you use the FM

• CALL METHOD cl_wd_utilities=>construct_wd_url
• EXPORTING application_name = ‘ZDEMO’
• IMPORTING out_absolute_url = str.

Once you get the URL in str, you can call this web Dynpro using ‘str’ and fm: create_external_window.

Q15) How do you create an ALV Report/Editable ALV in Webdynpro?

Ans:

• Add the Standard ALV component to the web Dynpro Component.
• Use Components tab: Ex: ALV_MATS  type SLV_WD_TABLE
• Create a context node with the table field information to be displayed
• Write the ALV Default Code for table display
• Set the read-only attribute to false to switch to editable mode using
• the method set_read_only of the interface
• IF_SALV_WD_TABLE_SETTINGS implementing class
• CL_SALV_WD_CONFIG_TABLE).

Q16) What is the Web Dynpro Phase model?

Ans: Whenever a roundtrip occurs from the client (browser) to the server, a sequence of processing steps is executed. This sequence of processing steps in web Dynpro is called the ‘Phase Model’.

Executing all the tasks in the phase model is the responsibility of the Web Dynpro framework.

Each step is executed only once and errors if any are captured. If you want to get into the details, have a look at the webinar from Chris Whealy:

Q17) How will you delete selected rows in a Table / ALV?

Ans: 

• Get the Table / ALV data in an internal table.
• Delete the row selected by the user from the internal table.
• Re-bind the internal table to the node bound to the Table/ALV.

Q18) Can you run a Webdynpro Application in the background?

Ans: This is a tricky question. It doesn’t make sense to run a Webdynpro application in the background because in that case, you are beating the purpose of the MVC controller architecture for Webdynpro. However, you can build logic to create background jobs from a Web Dynpro Application. 

So we have by now put a bunch of questions here. Let me know how do you find these questions.

We haven’t yet covered Web Dynpro component usage, ALV, Select Options, OVS, the coding part in Web Dynpro, Web Dynpro enhancements, etc.

Q19) How do you read parameters passed in the Web Dynpro URL?

Ans: First, let’s understand how a typical Webdynpro application looks like:

When you create a web Dynpro application, you can see the link URL generated by web Dynpro.

Q20) Can you pass parameters in a Webdynpro URL?

Ans: Yes, you can pass parameters in Webdynpro URL and read them too in your Web Dynpro component.

Example: http://domainname.com:8000/sap/bc/webdynpro/sap/zdemo_webdynpro?sap-language=EN&var1=4500000001&var2=00010

Q21) What is the use of the Web Dynpro window?

Ans: In Web Dynpro, the window is used to use multiple views or view sets. A view can only be displayed when it is embedded in a view and a window always contain one or more views that are connected by navigation links. Each window contains inbound and outbound plugs and they can be included in the navigation chain. Inbound plugs within a window lead from the outbound plug of a view to the embedding window. Just like all other inbound plugs, they represent an event and thus call the event handler assigned to them.

Q22) Can you create multiple applications using a component in Web Dynpro?

Ans: Yes for a component, you can create any number of applications.