Scribd
Upload
52 views

SAP ABAP Web Dynpro Interview Questions and Answers

MVC architecture concepts are used in ABAP Web Dynpro, with views holding UI elements, controllers managing flow logic, and models/assistance classes containing business logic. Some advantages of ABAP Web Dynpro include using the MVC paradigm, separating flow and business logic, fully integrating with the ABAP workbench, reusing existing back-end programs and Web Dynpro components, and not requiring a Java stack.

Uploaded by

Bharath Komarapalem
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
52 views

SAP ABAP Web Dynpro Interview Questions and Answers

MVC architecture concepts are used in ABAP Web Dynpro, with views holding UI elements, controllers managing flow logic, and models/assistance classes containing business logic. Some advantages of ABAP Web Dynpro include using the MVC paradigm, separating flow and business logic, fully integrating with the ABAP workbench, reusing existing back-end programs and Web Dynpro components, and not requiring a Java stack.

Uploaded by

Bharath Komarapalem
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

SAP ABAP Web Dynpro Interview Questions and Answers

1. MVC Architecture Concepts and usage of the same in ABAP Web Dynpro Ans: As per the MVC Architecture there is a clear separation between flow logic, view and the Business Logic. View holds all the UI elements that are visible in the UI, Controllers have the flow logic. Business logic is held in the Model which is in the form of Assistance class in Web Dynpro context. 2. What are the Advantages of ABAP Web Dynpro? Ans: 1. Web Dynpro programming model uses MVC (Model View controller) design paradigm. 2. Clear separation between the flow logic and the business logic. Here the flow logic is written in the views, windows, components and the business logic is mostly written in Assistance class. 3. Complete integration of web based framework into ABAP workbench. 4. Reuse of the existing back end programs (ex: function modules, classes). 5. Reuse of the WD components possible (Component Usage). 6. No Java stack required to run Web Dynpro applications.

You might also like