The static analysis: This helps understanding the code and data structure just by reading it.Step 3 - Understand how the Web Dynpro screen is populated. Everything including labels are hard coded. Please note that for the moment the screen will have no data to be displayed and will have no field control (all fields editable and visible). SAP UI5 library provides all the UI elements necessary to recreate such screen including search help fields. Step 2 - Build an identical screen with SAP UI5 This window that pops up now gives us all the necessary information to find the code in the SAP backend using SE80. We start by running the standard SAP application and do a right click on a UI field to bring up the Web Dynpro contextual menu: The following will show step by step how we work. This process is known as reverse engineering and is quite time consuming when the involved technologies/frameworks are not understood properly. The main idea of our approach is to understand how the Web Dynpro application was built and then start deconstructing it piece by piece. In this example, we will focus on the SAP on premise Travel and Expense solution and more specifically on the general data screen.
![what is web dynpro what is web dynpro](https://image.slidesharecdn.com/abap-webdynpro-130110140112-phpapp01/95/abap-web-dynpro-7-638.jpg)
What is web dynpro full#
![what is web dynpro what is web dynpro](https://media.springernature.com/lw785/springer-static/image/chp%3A10.1007%2F978-3-642-38247-5_16/MediaObjects/194310_2_En_16_Fig12_HTML.gif)
SAP modules still satisfy today’s business needs from a backend perspective but some of their user interfaces are no longer aligned with today’s modern user experience standards. This blog explains in 5 steps the technical approach we follow when transforming an ABAP based Web Dynpro solution into a Fiori like application built with SAP UI5.