Scripts

Where are the GuiXT Scripts stored? GuiXT Scripts are stored as normal ASCII files on your PC or on a file server in a LAN. You define the directory for the GuiXT scripts with a profile parameter in guixt.ini: 

Directory1 directoryname 

For example, 
Directory1 “C:\GuiXT\Script1″ 

Up to 4 directories can be specified: Directory1,…,Directory4. They are searched for a suitable script in reverse order Directory4,…,Directory1. For example Directory1 could contain company specific scripts and Directory2 could contain specific scripts for a certain user group. 

With GuiXT profile parameters you can assign different scripts for different user groups. If you are working in more than one R/3 system or in several client systems, you can use the following system variables in the directory names: 

&client is replaced by actual R/3 client 
&database is replaced by actual database (System Id) 

Example:

Directory1 “\\Server\GuiXT\scripts” 
Directory2 “F:\GuiXT\scripts\&database” 
Directory3 “C:\GuiXT\myscripts\&database”

Say we are working in R/3 system TST. GuiXT will first look for corresponding script indicated as Directory3 C:\GuiXT\myscripts\TST. If the script cannot be found there, GuiXT will then look for it in directory F:\GuiXT\scripts\TST and finally in directory \\Server\GuiXT\scripts.

On the R/3 Logon screen the variable &client will be replaced by the value 000 as client is not known at this stage.

Naming conventions for GuiXT Scripts Each GuiXT Script refers to exactly one R/3 screen (R/3 dynpro). In the R/3 repository the screens are identified using the ABAP program name and a 4-digit screen number, e.g. Screen 0100 for program SAPMF05A. Since GuiXT scripts are language specific (they contain field names, texts and images), their key also contains a language key, e.g. E for English, F for French, I for Italian, J for Japanese,… 

The name of a script file is constructed as follows: 

pppppppp.Lnnnn.txt 

pppppppp: ABAP program name 
 L: Language key E, F, I, J, … (1-character language key from the R/3 system) 
 nnnn: 4-digit screen number 

Example:  

SAPMF05A.E0100.txt 

This holds with the following two exceptions: 

  • The logon screen script is stored under Elogon.txt, Flogon.txt,.. Here the language key is the language in which the logon screen is displayed, since it is not yet known which language the user will choose.
  • The application menu scripts are stored using the names of the corresponding GUI programs MENUxxxx instead of SAPMSYST. This allows you to define a different screen layout for each of the application menu screens – screens that look relatively empty in the R/3 standard.. Examples are MENUS000.E0040.txt or MENUPR00.E0040.txt

You could use Image, View, Pushbutton in
order to design your own graphical application menus.

Scripts, naming conventions and directories