Component documentation Screen Design Time Conversion 

Use

When you want to create Web Dynpro user interfaces that correspond to classical screens of ABAP programs, you can use the functions of the Screen Design Time Conversion. Based on the source code of the ABAP screen, the Screen Design Time Conversion creates Web Dynpro UI elements together with their corresponding context metadata and includes them in an existing Web Dynpro view. This view, filled with the generated UI elements, provides a first approximation of the underlying screen.

Caution The layout of the generated Web Dynpro UI elements will only be an approximation of the underlying screens. Manual rework will be necessary to

·  correct the layout,

·  extract the UI logic from the ABAP code, and

·  call business logic from Web Dynpro.

 

Screen Design Time Conversion is a pure design time tool and does not provide any runtime support for the generated Web Dynpro for ABAP objects, in particular, converting flow logic of the screen program and calling ABAP modules is out of scope.

The tool is implemented as a wizard within the Web Dynpro View Editor which provides a means to take a ABAP screen as a template for the layout of a part of a Web Dynpro view. The wizard will not change the ABAP code that was called by the screen program. As a result, all UI objects contained in the ABAP code, like GUI controls or ABAP lists, are not included in the conversion. These objects have to be rewritten using Web Dynpro for ABAP. For more information see Restrictions.

The used screens and ABAP program sources remain unchanged after the execution of the wizard.

 

 

Process Flow

To execute the conversion, proceed as follows:

...

  1.  Open the View Editor of the Web Dynpro Exlorer, switch to tab Layout and select This graphic is explained in the accompanying text.

  2.  In dialog window Template Gallery select Standard  → Screen.

  3.  In the next dialog box insert the name of the program, to which the screen belongs to, and the screen number that should be converted.

  4.  Choose Execute to start the conversion.

 

Result

For each screen element, a corresponding Web Dynpro UI element is created. All UI elements are inserted into a transparent container element, which is added at the end of the currently selected container in the Web Dynpro view layout.

Additionally, a context node containing all bindable attributes – that is, properties that are relevant to runtime modifications - is generated for each Web Dynpro UI element, with the exception of TabStrip. For more information see Dynpro Controls.

The ID of the element and its context node is usually identical to the name of the corresponding screen element. However, because the naming convention for Web Dynpro elements is more restrictive, the screen element names will be changed in some cases.

 

 

Was this page helpful to you?