GuiXT in “SAP GUI for HTML”

Its (Internet Transaction Server) and SAP GUI for HTML enable any PC with a  Web Browser and Internet to access an SAP System. 

As of  ITS 6.10 Patch 14 and GuiXT 2002 Q2 9, GuiXT can also be used with in SAP GUI for HTML on ITS servers (Windows only), to simplify SAP screens. This is particularly useful for two reasons

  • Users expect simple, easy to use screens, especially in Internet 

  • Performance in generating and networking is better with simple ‘no fat’ masks 

Here, GuiXT functions centrally in the  “agate” process of the ITS server. It is not necessary to install GuiXT for each and every user; the Web Browser is sufficient, with GuiXT, to enable the SAP system to function. GuiXT offers the user another view of the SAP system, but is otherwise fully transparent. 

Functional capacity  

Virtually the full gamut of  GuiXT functions are available, with the identical script language. Also role based layouts are possible, differentiated for various user groups. Just as in the Sapgui for Windows environment, no modification of the SAP system (Dynpros or programs) is necessary.

At present the following commands are not supported: 

  • “Image”   .gif or .jpg-images cannot be incorporated with GuiXT 

  • “ButtonSize”  The size of the pushbuttons cannot be altered

As regards Synactive add on components:

  • Designer: As before, it requires a SAP GUI for Windows environment; however the scripts you create can now be made available, as they are, in the ITS 

  • Viewer: Currently not supported

  • InputAssistant: Your own input fields, input scripts and single screen transactions, but no local value help 

An example

Sap Guixt its03 GuiXT in
Transaction MB1A, standard, in SAP GUI for HTML


Sap Guixt its04 GuiXT in  

Simplified with GuiXT


Corresponding GuiXT script.  The same script (in the same folder if desired) can be used simultaneously for SAP GUI for Windows and for SAP GUI for HTML:

Title “Goods Issue Nappa Ltd. “

// Delete “WM param.” button in toolbar
del P[WM parameters...]

// Replace input field “Reason for movement” by radio buttons
offset (4,0)
box (0,0) (5,43) “Reason for movement”
radiobutton (1,5) “Poor quality ” [Reason for movement] “0001″
radiobutton (2,5) “Incomplete “   [Reason for movement] “0002″
radiobutton (3,5) “Damaged “      [Reason for movement] “0003″
radiobutton (4,5) “Damage in transport” [Reason for movement] “0543″
del F[Reason for movement]

// Print options 
offset (10,0)
box (0,0) (4,43) “How it should be printed”
pos R[Indiv.slip w.inspect.text] (1,5)
pos R[Individual slip] (2,5)
pos R[Collective slip] (3,5)
Text R[Indiv.slip w.inspect.text] “Each item, including inspection text”
Text R[Individual slip] “Each item, no inspection text”
Text R[Collective slip] “All items in one document”

InstallationProceed as follows:

  1. Install ITS 6.10 Patch 14 or higher. The Setup is to be found at SAP Service Marketplace.

  2. Install GuiXT 2002 Q2 9 or higher. You find the Setup at Synactive Download-page. 

  3. Copy the files guixt.exe and guixt.dll from the GuiXT directory into the ITS Program directory. 
    Usually this is  C:\Program files\Sap\Its\2.0\programs

  4. Activate GuiXT for ITS in the Windows Registry (ITS 6.10) or in the configuration file ITSDefault.xml in the ITS “config” subfolder:

    ITS 6.10:


    ITS 6.20:
    <value name=”GuiXtEnabled type=”number“>1</value>

    Now GuiXT can also be activated and de-activated via the ITS administration.

  5. For testing we recommend you allow the ITS Service “ITS Manager” to interact with the desktop, since the GuiXT window will not be visible otherwise. In order to do this, activate the  Win2000 or NT Services manager, search for “ITS Manager”  and click on “Startup”. Then mark the checkbox “Allow Service to Interact with Desktop”.

  6. After restarting ITS Manager Service (press  Stop and Start in Service Manager), this option is active.  When you log on to SAP the next time. the GuiXT window will come up automatically. Now you can maintain GuiXT profile exactly as for SAP GUI for Windows. 

Please note: GuiXT cannot be used simultaneously on the ITS Server in ITS and in a local, active SAP GUI. If you wish to test the GuiXT settings on the ITS server in SAP GUI, you have to de-activate the ITS-Service.

Alternatively, you can use a guixt.ini file in the ITS program folder, that refers to a central guixt.ini file. This central guixt.ini file can then be refered to from a SAP GUI PC as well, facilitating your tests.

Example: Let us assume that your ITS Server is “itsmain01″. All GuiXT scripts and the file guixt.ini should be located in a folder “centralguixt” on the server  “p00012″. You work on a PC “pcm12″ with SAP GUI, where you can also logon to ITS using a browser.

  • On the ITS Server “itsmain01″ create a file  guixt.ini in the ITS program folder  C:\Program files\Sap\Its\2.0\programs. This file contains only one entry:
    SwitchTo  \\p00012\centralguixt\guixt.ini

  • On your PC “pcm12″  create a file  guixt.ini in the sapgui program folder  C:\Program files\Sappc\sapgui. It contains only the entry:
     SwitchTo  \\p00012\centralguixt\guixt.ini

  • On the server “p00012″ create a file guixt.ini where you specify the GuiXT profile parameters.

For productive use please start GuiXT with the  “StartHidden   Yes” option, since otherwise the GuiXT script window has to be constantly updated. All other entries are as described for SAP GUI environment.

InputScripts The processing of the InputScripts (component InputAssistant) takes place on the ITS server, not on the browser PC. When you process screens automatically in your InputScript, no html generation is needed and no transfer to the browser either. Instead your input (“Set” commands in InputScript) is directly fed back to the SAP system. Therefore the automated processing (e.g. single screen transaction) is considerably faster than a user could achieve manually, and uses less resources on the ITS server.


Sap Guixt its01 GuiXT in
Simplified example: MM01 (Create material) as single screen transaction


Sap Guixt its02 GuiXT in
All intermediate screens were processed automatically on the ITS Server


GuiXT in