SAP INTERFACE TECH - Guide
Get Example source ABAP code based on a different SAP table
GUIDELINE 5.18
Selecting the User Interface Technology
ABAP_BACKGROUND
Various UI technologies can be used in the ABAP environment. We distinguish between classic technologies, which are based on the SAP GUI and are almost completely integrated into the ABAP language, and new Web-based technologies, which display the UI in a
The classic SAP GUI technologies are:
A classic dynpro is a component of an ABAP program. It is created using the Screen Painter in the ABAP Workbench and called using either a transaction code or the
A selection screen is a specific classic dynpro that is not created manually in the Screen Painter. Instead, you define it using the
Classic lists are used to output data in a structured and formatted display. The formatted data is stored in a list buffer using specific ABAP statements (such as
The new Web-based technologies are:
Web Dynpro ABAP is a technology for creating platform-independent, Web-based interfaces. The architecture of Web Dynpro is based on the Model View Controller approach (MVC) for
ABAP_RULE
Use Web Dynpro ABAP whenever possible to create the UIs of new application programs.
ABAP_DETAILS
Web Dynpro ABAP is SAP's standard
Compared to Web Dynpro, the
The classic SAP UI technology # classic dynpros based on the SAP GUI, including selection screens and lists # is no longer sufficient for modern and flexible business applications where the user interface must be accessible in a portal, for example. The MVC approach is not supported by frameworks or by any relevant tools.
Exception
The various UI technologies are not interoperable. In other words, it is usually not possible to switch parts of an application based on classical dynpros (including selection screens and classic lists) to Web Dynpro ABAP. In addition, the commonly implemented dynpro programming model was previously not very oriented toward SoC. This makes it difficult or even impossible to implement a changeover for the purpose of further development. Consequently, in exceptional cases, classic dynpros and/or selection screens might be required if a new development needs to be included in an existing framework. For these exceptional cases, the following rules have been devised to ensure that these obsolete UI technologies are handled using a more modern approach.
Note
In general, you can replace the UI technology of an application that is strictly modeled on the
Note
Web Dynpro ABAP itself is not part of the ABAP language. Specific guidelines regarding the use of Web Dynpro ABAP are not covered by these programming guidelines, which mainly focus on using the ABAP language to implement services.
Example
The transaction
Since the sample application strictly separates all concerns, you can use it with different UIs, without having to make adjustments to the application and persistency logic. The SoC is therefore a critical prerequisite for potential changeovers from classic dynpros to Web Dynpro ABAP.