By specifying the script directories in the GuiXT profile, it is possible to activate different GuiXT scripts on different PCs. This procedure is sometimes not sufficient:
If the user has to work on different PCs the configuration of the GuiXT scripts should not depend on the PC but on the SAP-user name
Instead of having an individual configuration on each PC a central standard configuration is preferred
Both objectives can be reached by specifying a user catalog (command “UserCatalog” in guixt.ini). Please follow the steps below:
1 Divide the users of your SAP system into groups associated with different scripts. To do so, simply create a text file (name could be for example usercatalog.txt), in which the groups and the specific script directories are specified.
// User groups:
// make correspondence to 1-4 script directories
M1 \P5008\GuiXT\General \P5008\GuiXT\M1
M2 \P5008\GuiXT\General \P5008\GuiXT\M2
// make correspondence to one user group
000/* MX // other users in client 000
* XX / / other users, all clients
// role or profile specific settings with
// Role=… or Profile=…
// (valid for all clients)
// You can query the value of a user parameter, e.g. parameter ZZGXT = “SALES”, using
// the notation Parameter.PID=value
By using // you can add comments in your script; spaces are ignored.
In the first part of the user catalog, 5 user groups are named: M1, M2, MX, TEST, XX. You can associate up to 4 directories for each group. If the names of the directories contain spaces please put them between " …".
In addition to the script directories you may specify the parameters VBDirectory=, JSLibrary= and VBSLibrary= . They have the same meaning as in guixt.ini. Example:
M1 \P5008\GuiXT\General \P5008\GuiXT\M1 VBDirectory="\P5008\GuiXT\M1\VB files"
In the second part of the user catalog you can specify exactly one group for each client/user. At the end of each client you can specify the correspondence for all remaining users by using client/*. You can also specify a client independent association by specifying * at the end of the catalog.
Sorting the users by alphabetical order is not necessary but it probably gives a better overview.
The specification none means that no directory is active. In this case, even directories specified directly will not be active.
For a centralized administration we recommend the use of a central .ini file, i.e.
On each individual PC you have the same standard guixt.ini file in the SAP GUI directory, in which you put the entry:
where P5003 is the central file server.
The file \P5003\guixt\guixt.ini contains the GuiXT options and the specification of a central user catalog.
Questions & answers about the user catalog:
Q: We are working with two productive systems C60 and HR2. Is it possible to specify a different user catalog for each system?
A: Yes, it is possible by using variable &database in the specification of UserCatalog, example:
In C60 the user catalog \P5003\GuiXT\C60\usercatalog.txt will be used, in HR2 the user catalog \P5003\GuiXT\HR2\usercatalog.txt.
Q: Which script directory will be used for the logon screen?
A: The user catalog will be read after the logon screen. For the logon screen itself, the given directories apply.
Q: What happens when the user cannot be found in the user catalog?
A: If an *-indication exists the corresponding user group will be associated. Otherwise the given directories will be used.
Q: When do modifications in the user catalog become active?
A: Modifications are not immediately active, but only at the next logon to SAP.
Q: Is it possible to put the user catalog on a webserver?
A: Yes, in this case just indicate the URL of the file, example: