General Click on Edit->Profile in the GuiXT window in order to display and change the profile parameters.

Technical information:
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 

IgnoreRegistry   Yes

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

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.
  • ftp-servers, e.g.
  • 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.



  Installed components

Mark the components that you are using.

Please mark "GuiXT" and no other components if you want to use GuiXT without a license key.

Component GuiXT
Component InputAssistant
Component Viewer
Component Designer

Component Controls

              License keys

You need a license key if you want to use the Synactive components. Only GuiXT itself, without any other component, requires no license key.

Please observe that the license key is specific for your choice of GuiXT components and for your SAP installation number and the names of your systems.

              License file

The components InputAssistant, GuiXT Controls and Viewer require a "GuiXT license file". The license file contains, among other things, the customer number, the licensed components and the number of users. When you buy a license Synactive automatically sends you the license file.


Enabled Systems

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. 

EnableSystem XXX
EnableSystem YYY
Start window

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:

guixt.exe visible

StartMinimized Yes/No
StartHidden Yes/No
File cache
If you activate the File cache option, then all files read from a central network server are replicated locally in order to minimize the network load (scripts, images, value sets...).
  • All files from a directory with UNC notation ( e.g. \\p00145\GuiXT\Scripts) are replicated locally
  • If you use a drive letter instead, e.g. S:, then no replication takes place, even if the drive letter is assigned to an external directory.
  • Before a replicated file is read from the local cache the first time during an SAP session, the update time on the server is checked. The file is loaded again from the server if necessary.
  • All subsequent times the file is read from the cache instead of the server during the same SAP session.

If you use GuiXT directories on web server (starting with http:// or ftp://) combine with GuiXT file cache for optimal performance

Replication Yes/No


All script files and the user catalog are kept in the cache in encrypted format. Images are not encrypted. 

CacheEncryption Yes/No
Icon Id

Refers to the Tip command in GuiXT scripts. You can specify any SAP standard icon id. It is used in order to indicate that a tip (quickinfo) is available.

System Trace

This option is only used for debugging purposes. When activated, the system displays a trace in a separate window. The trace can be saved to a file and sent to Synactive for further analysis.

When the Trace option is activated (see above), the system saves the trace to the file which is indicated here, incl. path

Trace Yes/No

Refers to the InputAssistant. If the Update active option is on, the InputAssistant updates the history files for each entry field.

With Show ... you can define which mouse buttons are used to show the input history. The application button on the keyboard can always be used.

The option Display history icon shows the HistoryIcon on the screen where history data have been stored. By pressing the icon the fields on the screen will be filled in with the latest values entered. The default value is "No".

HistoryUpdate Yes/No
HistoryOnRightButton Yes/No
HistoryOnMiddleButton Yes/No
HistoryShowIcon Yes/No
Further Options

No language key in script file name

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.

NoLanguageKey Yes/No
SAP-URL in html

If you mark this option you can work with SAP URL in any html display in Internet Explorer.

LinkSapUrl Yes/No
Enable Controls

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.

EnableControls Yes/No
Check all directories

GuiXT will search all specified directories for each script.

CheckAllDirectories Yes/No
profile16.png (1089 bytes) Text editor

GuiXT uses notepad as standard script editor. Instead of Notepad, you can work with a text editor of your choice e.g. the GuiXT Script Editor Pro developed by Synactive specifically for GuiXT scripts.

profile19.png (1089 bytes) JavaScript / VBScript files

GuiXT Controls: In this field you can specify the JavaScript / .vbs files that contain the JavScript / VBScript functions. You can indicate severals separated by "," (comma).

JsLibrary or VbsLibrary
User 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. 


profile15.png (1089 bytes)

RFC user

User name and password for remote function calls. The password is stored in encrypted format. Please see RFC (Remote Function Call) in GuiXT. You can also perform the RFC in the current client by selecting the option "Script download via current client".


RfcPasswordEnc (password encrypted)

Use the function

Tools->Encrpyt Password

in GuiXT window to generate the encrypted RFC password.

If you prefer to work with an RFC password without encryption and the password contains lower case characters, you must enclose it in inverted commas when you enter it in GuiXT profile or in guixt.ini. Otherwise the password is translated to uppercase and the RFC login does not work.

RfcConnect    Explicit connection parameters used in all RFC calls.  

It is possible to specify ASHOST= and SYSNR= directly, or to work with load balancing (MSHOST=... R3NAME=... GROUP...)
RfcConnect   ASHOST=tst0120.internal SYSNR=00

It is also possible to distinguish different systems:

RfcConnect  ifDatabase=C11  ASHOST=c11main.internal SYSNR=00
RfcConnect  ifDatabase=PR1  R3NAME=PR1 GROUP=PUBLIC

RfcCurrentClient Yes    Script download via current client

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

Further parameters in guixt.ini

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
to 1.


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.