GuiXT is shipped on the SAP product CD and is installed with the SAP GUI. To activate GuiXT, choose (as of SAP GUI Release 4.6B) the pushbutton Adjustment of the local layout in the standard toolbar of the SAP system, and then Activate GuiXT.
Profile parameters for GuiXT are saved in the Windows registry. Alternatively, you can use the file GUIXT.INI for profile parameters. This makes sense if you want to install GuiXT on other PCs by help of a predefined profile. You can use parameters contained in the file GUIXT.INI to determine which scripts can be used from where for certain transactions.
If you want to make GuiXT available for a larger number of users that should not change scripts, just install GuiXT on a network server. Be aware of the following:
· SAP GUI must be installed on the network server
· the GuiXT programs (GUIXT.EXE, GUIXT.DLL, GUIXT.INI and other programs) must be installed in the central SAP GUI directory
· the GuiXT window can be hidden for the end users via the profile parameter ‘StartMinimized Yes’ or ‘StartHidden Yes’
· the GuiXT scripts must be stored on the central server.
Note the hints for the installation in the documentation of Synactive Ltd (www.synactive.com) in the section Download and the explanations in SAPNet under the alias GuiXT.
The GuiXT Designer, the InputAssistant and the GuiXT Viewer are not included on the SAP product CD. You can receive these tools at Synactive Ltd.
Using the GuiXT Designer, you can process a screen in WYSIWYG mode. A corresponding script is recorded at the same time.
You can use the InputAssistant to record repeated user inputs. The InputAssistant is also required for the reduction of screens in a transaction
You can use the GuiXT Viewer to utilize all functions of HTML to concisely prepare display transactions of the SAP system.
The GuiXT scripts are stored as normal ASCII text files. You can determine the directory in which the scripts are located with the parameter:
This is how the entry might look:
Overall there are four profile parameter for the storage of GuiXT scripts at your disposal. These are the parameters Directory1,Directory2, Directory3 and Directory4. They are searched in reverse order for a fitting script (starting with Directory4). The first script that is found is executed.
If scripts are to be utilized company-wide, they could, for example, be stored in Directory1. The profile parameter would then refer to the according server directory. Directory2 could contain scripts for specific user groups and Directory4 individual GuiXT scripts.
By the usage of system variables in the names of the script directories, differing SAP systems and clients can be addressed for differing script directories:
&client is replaced by the current client
&database is replaced by the current database number (system Id)
Every GuiXT script refers to exactly one screen of a program. The screens are stored in the Repository under the ABAP program name and a 4-digit number, for example, screen 0100 of the program SAPMV45A . If you want to create a GuiXT script for a transaction, activate GuiXT in the standard toolbar, start the transaction and choose Edit ® Script in the GuiXT window . The editor opens with a corresponding script name.
GuiXT scripts are language-dependent. A language key must be specified accordingly in the name of the GuiXT script.
E - English
D - German
I - Italian
J - Japanese etc.
The name of a script file is made up as follows:
pppppppp : ABAP program name
L : Language key D, E, F, I, J , ... (1-digit language key from the SAP system)
nnnn : 4-digit screen number
GuiXT scripts are language-dependent. If transactions are used in several languages, you must recreate your GuiXT scripts for each language.
For further information, refer to Adjusting a Transaction with GuiXT