The following table summarizes graphical elements available in the SAP GUI and indicates how to use them in HTML templates:
SAP System Source |
ABAP Element |
HTML Template |
Remarks |
---|---|---|---|
GUI status |
Function keys |
Can be used, but not supported. |
You can use F21, F23 for scrolling. Otherwise, define as function as pushbuttons. |
Menus |
Can be used, but not supported. |
Web browsers contain only browser-specific functions. You cannot merge menu options from SAP transactions. Use pushbuttons instead. |
|
SAP system screen |
I/O fields |
OK. |
Converted, no problem |
Text fields |
OK. |
Converted, no problem |
|
Text areas |
Can be used. |
Require manual changes to HTML template. |
|
Checkboxes |
Can be used. |
Require manual changes to HTML template. |
|
Radio buttons |
Can be used. |
Require manual changes to HTML template. |
|
Pushbuttons |
OK. |
Converted. |
|
Step loops |
OK. |
Some problems exist. |
|
Table controls |
Can be used. |
Require manual changes to HTML template. |
|
Tabstrip controls |
Do not use. |
||
Dropdown boxes |
Do not use. |
||
Icons |
Do not use. |
Instead, use the HTMLBusiness function mimeURL to embed icons in HTML template manually. |
|
Subscreens |
Can be used. |
Require manual changes to HTML template. Subscreens in SAP system correspond to HTML frames. A screen that contains subscreens corresponds to an HTML frameset. |
|
Group boxes |
Can be used, but not displayed in HTML. |
||
ABAP module |
Dialog boxes |
Can be used, but not supported in HTML. |
Requires setting of service file parameter ~popups. |
Field help (F1) |
Do not use. |
||
Input help (F4) |
Can be used, but not supported by HTML. |
Requires manual changes to HTML template. |