Web Dynpro: Running Web Dynpro Applications over SAPGUI using the HTML Control

[Former Member]

In my Web Dynpro: Running Web Dynpro Applications over SAPGUI I showed how to access Web Dynpro Applications via SAPGUI using the function WDY_EXECUTE_IN_PLACE.

In this I will do the same application but using the the class CL_GUI_HTML_VIEWER.

Developing

Creating the program

Go to the Object Navigator (SE80) and create a new program.

Include programs

Now in the created program, add the following include programs:

INCLUDE mzwda_htmltop                           .  " global Data INCLUDE mzwda_htmlo01                           .  " PBO-Modules INCLUDE mzwda_htmli01                           .  " PAI-Modules INCLUDE mzwda_htmlf01                           .  " FORM-Routines

GUI status and title

Create a GUI status like follows:

And a GUI title:

Global declarations and variables

Add the following code to the MZWDA_HTMLTOP include:

TYPE-POOLS vrm. DATA: * Interface variables   ok_code        TYPE sy-ucomm, "User command   application    TYPE wdy_application_name, "Input listbox   gt_application TYPE vrm_values, "Listbox items   gr_container   TYPE REF TO cl_gui_custom_container, "Container   gr_html_viewer TYPE REF TO cl_gui_html_viewer. "HTML control

Creating the screen

Now create a screen:

Screen attributes

Screen layout

Screen elements attributes

• Text Field:

 

• Input Output Field:

• Button:

• Custom Control:

Screen element list

Screen flow logic

The screen flow logic is:

PROCESS BEFORE OUTPUT.   MODULE status_0100.   MODULE pbo_0100. PROCESS AFTER INPUT.   MODULE user_command_0100.

PBO modules logic

MODULE status_0100 OUTPUT.   SET PF-STATUS '100'.   SET TITLEBAR '100'. ENDMODULE. MODULE pbo_0100 OUTPUT.   PERFORM fill_listbox.   PERFORM create_objects. ENDMODULE.

PAI module logic

MODULE user_command_0100 INPUT.   CASE ok_code.     WHEN 'BACK' OR 'CANC' OR 'EXIT'.       gr_html_viewer->free( ).       gr_container->free( ).       LEAVE PROGRAM.     WHEN 'RUN'.       PERFORM show_wda.   ENDCASE. ENDMODULE.

Include MZWDA_HTMLF01 logic

FORM fill_listbox.   DATA ls_application LIKE LINE OF gt_application.    IF gt_application IS INITIAL.     ls_application-key  = 'WDT_FLIGHTLIST'.     ls_application-text = 'WDT_FLIGHTLIST'.     APPEND ls_application TO gt_application.     ls_application-key  = 'WDT_FLIGHTLIST_SIMPLE'.     ls_application-text = 'WDT_FLIGHTLIST_SIMPLE'.     APPEND ls_application TO gt_application.      CALL FUNCTION 'VRM_SET_VALUES'       EXPORTING         id              = 'APPLICATION'         values          = gt_application       EXCEPTIONS         id_illegal_name = 1         OTHERS          = 2.   ENDIF. ENDFORM. FORM create_objects.   IF gr_container IS NOT BOUND.     CREATE OBJECT gr_container       EXPORTING         container_name = 'CC_WDA'.     CREATE OBJECT gr_html_viewer       EXPORTING         parent             = gr_container       EXCEPTIONS         cntl_error         = 1         cntl_install_error = 2         dp_install_error   = 3         dp_error           = 4.     IF sy-subrc = 0.       cl_gui_cfw=>flush( ).     ENDIF.   ENDIF. ENDFORM. FORM show_wda.   DATA ls_url TYPE c LENGTH 255.    CASE application.     WHEN 'WDT_FLIGHTLIST'.       ls_url = 'HTTP://SAPSERVER:8000/SAP/BC/WEBDYNPRO/SAP/WDT_FLIGHTLIST'.     WHEN 'WDT_FLIGHTLIST_SIMPLE'.       ls_url = 'HTTP://SAPSERVER:8000/SAP/BC/WEBDYNPRO/SAP/WDT_FLIGHTLIST_SIMPLE'.   ENDCASE.    IF ls_url IS NOT INITIAL.     gr_html_viewer->show_url( url = ls_url ).   ENDIF. ENDFORM.

Finish

Now it's necessary to activate all objects and create a transaction like follows:

The result

 

This blog was based on the SAP program RSDEMO_HTML_VIEWER and I got some references in the blog from thomas.jung/blog - Updated!: Calling a BSP application from a SAPGui Transaction.

And you can get more information about the class CL_GUI_HTML_VIEWER in the SAP Help Documentation.