|
Helpviews are essentially webviews that are displayed inside the SAP GUI window. They load an ordinary HTML file and allow you to provide additional information, instructions or helper functions to users, right next to the SAP screen. Helpviews are mainly used to show how to perform a specific SAP transaction, or to offer supporting functions such as search bars, quick navigation or sample data for beginners. They are therefore particularly well suited for training and for users who do not work with a transaction on a daily basis. Configuring the Helpview directory In the GuiXT Profile you specify the directory in which GuiXT looks for the Helpview files. As soon as a matching file exists for the current transaction, GuiXT automatically displays a help icon in the toolbar.
File naming and language detection Which HTML file is loaded depends on the SAP system logon language. The prefix of the file name controls the language:
When the user logs on in a particular language, GuiXT automatically picks the matching file. This means you can maintain a separate Helpview per transaction and language without ever having to change the GuiXT script itself. Supported file formats for help files GuiXT supports both HTML and PDF as formats for help files. GuiXT first searches for an HTML help file for the current transaction. If none exists, a PDF file with the same naming convention is searched for and displayed instead. Note: Interactive features are only available in HTML format. PDF files allow the display of static content only. Configuring the HelpView icon To display a help icon in the toolbar, you need to provide an icon file in the HelpView directory:
The icon is only displayed if a matching help file exists for the current
transaction. You can override the default icon file for individual
transactions using the
Image command with the
Logon screen help For the SAP logon screen, GuiXT searches for a help file matching the following naming pattern:
The placeholder Calling GuiXT functions from a Helpview Because a Helpview is a fully featured HTML page, it can contain JavaScript routines that in turn call GuiXT functions. This allows buttons, input fields or search results inside the Helpview to be connected directly to the SAP GUI window — for example to navigate to another screen, place the cursor on a specific field or transfer values into SAP fields. The JavaScript code itself is not explained in detail in this documentation. The complete sample project files are however available for download: » helpviews_sample_project.zip VA01 example: explaining error messages and offering actions In the following example for transaction VA01, the Helpview reads the current SAP error message and shows a more detailed explanation right next to it on how to fix it. In addition, two action buttons (BV and TA) are provided. Clicking BV automatically writes the value "BV" into the corresponding SAP field, so the user neither has to know the value nor type it in manually.
VA02 example: sortable table of recent orders In the Helpview for transaction VA02, five buttons each represent a time range (for example the last 7, 14 or 31 days). Clicking one of them loads a sortable table with the matching orders. Clicking an order number transfers it directly into the order field of the SAP screen.
The order list is read via
dbselect directly from the tables VBAK and KNA1. The
parameter
VA02 example: search bar with navigation The second VA02 Helpview contains a search bar with suggestions. Selecting a suggestion makes the SAP GUI window switch to the corresponding screen. If the suggestion points to a specific field, that field is additionally highlighted once focus returns to the SAP window. Even an untrained user can therefore quickly find their way around complex screens.
The actual navigation is handled by a GuiXT InputScript. It takes the
MM03 example: search bar for material views The same principle can be applied to almost any transaction. For the material display MM03, the Helpview offers a search bar for the individual material views (e.g. Basic Data 1, MRP 1). Selecting an entry runs through the view selection dialog and, if a specific field is given as the target, the cursor is then placed precisely on that field.
The corresponding InputScript shows how the view selection dialog
(
|