Click on Edit->Profile in the GuiXT window in order to display and change the profile parameters.
All profile parameters are normally stored in the Windows registry. There is also the possibility of working with a guixt.ini file instead. This makes sense if you work with different profile variants, or if you want to install GuiXT with a predefined profile on other computers.
You put a file guixt.ini in the SAP GUI folder. The file should contain the statement
since otherwise values read in Windows registry could overwrite your guixt.ini settings.
Please refer to （location of GuiXT profile) for additional information.
The parameter names for guixt.ini can be found here location of GuiXT profile
Here you specify various directories. They can be on your personal PC or on the local network. You can either name the drive by the letter or use the UNC notation.
You can also use system variables to define SAP-System dependant (&database), client dependant (&client) or user dependant (&winuser) directories (i.e.: Directory1 \Server\GuiXT\scripts&database). Windows environment variables offer a further possibility. Please use the notation &%[ENVNAME], where ENVNAME is the name of the variable. Example: C:&%[GUIXTDIR]\Scripts.
Scripts1,… Scripts4 are the directories that are searched for GuiXT scripts. The search sequence is always Scripts4, then Scripts3, then Scripts2, then Scripts1. You could, for example, have company-wide scripts in Scripts1, and some scripts of your own in Scripts2. Especially if you develop new scripts it makes sense to use your own directory for a certain period of time. You can activate and deactivate the script directories as you go along.
GuiXT Scripts, Images (gif, jpg) and InputScripts can be stored in
- local files, e.g. in C:\GuiXT\Scripts
- central file servers, e.g. \p00145\GuiXT\Scripts
- http-servers, e.g. http://www.synactive.com/demo.d.45
- ftp-servers, e.g. ftp://synactive.com/demo.d.45
- SAP Web Repository (SAP database), e.g. sapwr:z.guixt.demo
For details please click on GuiXT scripts in SAP Web Repository
History is the directory used by the InputAssistant. Both the history of input fields and the definition of input sets are stored here.
Shared input sets is also read by the InputAssistant. In this directory you can define Input Sets that are shared by several users.
Domains contains the domain files used for local value help (InputAssistant).
Help views Directory with own help files. For each transaction you can create a separate html or pdf file, e.g. “e.transaction.VA01.html” for transaction VA01, language key E.
In addition, GuiXT expects an image file “help.gif” in this folder (format 18x18 pixel. e.g. ). This is the icon that GuiXT displays in the toolbar if a help file for the current transaction exists. You can use an image command with ViewHelp=… to override the help file.
In the SAP logon screen the help file e.transaction.logon.html is searched. Here the language key is set according to the language of the logon screen.
- Component “Controls” is required for this option
Local script buffer contains the scripts and images that are read from a central file server or from the SAP database (transaction variants in SAP). They are automatically synchronized with the server or the SAP database via a common time stamp. See also File cache parameter below.
User catalog. here you can specify in a text file, different user dependant script directories. Refer to description user catalog for additional information.
.NET class libraries contains the .NET class libraries for the “Controls” component. You may specify local directories, network folders, http or ftp folders, SAP Web Repository or SAP Mime Repository. See the CallVB documentation for details on how you can call up a .NET function from a GuiXT script.
Mark the components that you are using.
Please mark “GuiXT” and no other components if you want to use GuiXT without a license key.
You can specify the names of SAP systems for which the GuiXT configuration should be active. The names of the systems can be found in “System” “Status” “Database data” “Name”, e.g. D11. You can specify several systems.
When GuiXT is started, the GuiXT window can be visible, visible and minimized, or hidden. The “hidden” mode is especially useful for users that do not need to change GuiXT scripts or options.
Please note that the profile screen will no longer be available when you activate the “hidden” option. If you start GuiXT again with the parameter “visible”, the GuiXT window is shown and you can change the profile options:
In GuiXT scripts you can inquire about these user options with if Q[Option=xxxx]. For example, you can offer an option display_help. When the user activates this option in the profile, you can display a help text for certain transactions, either as image file using Image or as rtf or html file using View. Each user can then decide individually whether or not to use the help text.
Controls are automatically built up when processing an InputScript (without activating this option you have to use “Enable Controls” in InputScript). It is generally useful to enable this option.
If you mark this option GuiXT searches the scripts without a language key, e.g. instead of SAPMF05A.E0100.txt it reads the file SAPMF05A.0100.txt.
In addition, in the screen elements you will now find the technical field name in the first column.
JsLibrary or VbsLibrary
The following parameters are possible only in guixt.ini:
- IgnoreRegistry Yes
The GuiXT profile entries in the Windows registry are ignored if you specify IgnoreRegistry Yes. This makes sense if all parameters should be taken from guixt.ini. In this case, put the guixt.ini file into the SAP GUI directory.
- Optional No
If GuiXT is activated in the SAP GUI options, then it is no longer possible to deactivate it.
Please note that this command is not possible in Enjoy mode.
In this case you have to modify the registry entry
HKEY_CURRENT_USER/Software/SAP/SAPGUI Front/SAP Frontend Server/Administration
and add a string variable with the name “DisappearItems” and value “Activate GuiXT”. If this variable exists already with some other menu entries, you can add the new entry “Activate GuiXT” at the end separated by ‘;’, e.g. “Generate graphic;Activate GuiXT”.
If GuiXT should always be active, you have to set the variable “GuiXT” in
HKEY_CURRENT_USER/Software/SAP/SAPGUI Front/SAP Frontend Server/Customize
Maximum time, in seconds, allowed for file access to “http://…”, “ftp://…” or “\server…” files. Example:
- FileAccessTimeout 60
After 1 minute (60 seconds) GuiXT tries to get the file from its cache instead. A log entry is made in GuiXT protocol.
If you do not specify FileAccessTimeout explicitly, GuiXT takes a default value of 300 = 5 minutes.
Maximum time allowed for RFC call, in seconds. Example:
- RfcAccessTimeout 10
Each RFC call will be cancelled after 10 seconds.
Specifies a shared folder, open to all front end PCs, and for which GuiXT will enter the following information for each user: SAP System, user name, SAP GUI version, GuiXT version, active GuiXT components.
**Typical guixt.ini file:** IgnoreRegistry Yes StartHidden Yes // Components Component GuiXT Component InputAssistant Component Controls // License keys and license file Key mycompany.E72.glkmeehvrdnz Key mycompany.Q72.gtdnenhvrdnz Key mycompany.P72.htglomhvrdnz LicenseFile \\P00112\GuiXT\guixtlicense.txt // Scripts and Input Sets from Server Directory1 \\P00112\GuiXT\Scripts InputSets \\P00112\GuiXT\Inputsets // History HistoryUpdate Yes History C:\GuiXT\History // Local value help Domains \\P00112\GuiXT\Domains // Cache Replication Yes Directory0 C:\GuiXT\Temp