A classic Dynpro is a component of an ABAP program that is created using the Screen Painter of the ABAPWorkbench. It is called either via a transaction code (dialog transaction) or CALL SCREEN. Calling a Dynpro always starts a Dynpro sequence.
Selection screens are special forms of Dynpro generated from a set of respective ABAP statements. They either are called automatically when executing executable programs, or can be specifically invoked via CALL SELECTIONSCREEN.
Classic lists provide the means for structured and formatted output of data. The formatted data is stored via special ABAP statements (e.g., WRITE and FORMAT) in a list buffer and is displayed in a dedicated Dynpro screen when it is called. A list is called either automatically when executing an executable program or via LEAVE TO LIST-PROCESSING.
In addition to these classic GUI techniques, there are newer techniques now available to the ABAP developer — these are handled via object-oriented interfaces:
GUI controls are components of the presentation server that are addressed from ABAP via ABAP Objects proxy classes of the Control Framework (CFW). GUI controls are still bound to classic Dynpros.
Business Server Pages (BSPs):
BSPs are the ABAP counterpart of Java Server Pages (JSPs).A BSP page is an HTML page with partly dynamic content. The dynamic content is provided by embedding server-side scripting written in ABAP. On the application server, a script appears as a generated ABAP Objects class.
Web Dynpro ABAP:
Web Dynpro is a technology used to create platform- and languageindependent Web-based interfaces. The architecture of Web Dynpros is based on the Model-View-Controller (MVC) approach. The Web Dynpro technology is available in SAP NWAS Java as well as in SAP NWAS ABAP (as of SAP NetWeaver 2004s). ABAPWeb Dynpros are created with the Web Dynpro Explorer of the ABAPWorkbench. Compared to classic Dynpros, an ABAPWeb Dynpro is not a component of an ABAP program but is used via class-based proxy objects.