Yes, GuiXT does have a naming convention.

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, and so on.

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, and so on. 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.

Example:

MENUS000.E0040.txt or '''MENUPR00.E0040.txt '''

• http://www.guixt.com
• http://www.guixt.com/index.php?mpane=documentation
• Subscribe to: guixt@yahoogroups.com

Here are the steps to run GuiXT and Designer: If you have installed a previous version of GuiXT Pro, please uninstall that first before installing this version.

• Execute GuiXT then execute the SAP Front end. After logging in.
• Choose the transaction screen that you want to be modified.
• Click Tools menu and select Designer option on GuiXT.
• GuiXT Designer will be launched and will display the same SAP screen for editing
• You may now change the layout of the SAP screen by editing the screen on the Designer
• When you're satisfied with the new layout, choose File/Save and do not change the default file name that is presented
• Save the script file. You may now traverse back and refresh the SAP screen to see the new layout.

The components and their functions are:

• GuiXT: Changes text and removes redundant data-entry fields in SAP ERP without changing core SAP ERP data. This engine is bundled with SAP GUI and shipped in the Presentation CD of SAP ERP.
• Designer: WYSIWYG editor to re-paint SAP ERP screens, automatically generates GuiXT scripts
• Input Assistant: Streamlines business processes, by combining stock SAP ERP screens and transactions into a customized, personalized error-free and user-friendly data entry screen. Input assistant can also provide local value help for GuiXT and SAP ERP fields
• Viewer: Component viewer integrates HTML with SAP GUI. Viewer can also integrate HTML based help with SAP GUI. Viewer can provide field based help and/or screen based help
• Deployer: Deployer automates and simplifies the deployment and installation of GuiXT in an enterprise
• GuiXT RF: Create new or customize/combine existing transactions for SAPConsole. Primarily for RF Mobile Data Entry, this tool eliminates the need of creating and customizing new transactions in ABAP

Yes. The SAP screens may change in a new correction level or new release, making changes in the scripts necessary. In practice, these problems, when they occur, are easy to solve. Our experience so far is that they normally do not occur in a correction level. On the other hand, you should include a certain amount of time for the adaptation of the GuiXT scripts when you plan a new SAP ERP release. Compared with the training of your end users to deal with the new screens, the adaptation of the scripts is not significant. Indeed, you should keep in mind the possibility that GuiXT will save much time and money otherwise needed for end user training. For example, if SAP adds a new entry field on a screen, you would normally have to teach your users what to do with this field. With GuiXT, you can simply delete the field, or you can display appropriate radio buttons for immediate input, or you can include a quick info or a comment for this field.

No. The SAP ERP application logic and the transaction flow remain untouched. There is no possibility of deactivating the SAP ERP consistency checks with GUI XT, or to modify the transaction logic in any way. GUI XT simply offers a new layout of the screens combined with enhanced input support.

This is not dangerous so far as data integrity is concerned. However, we believe it is preferable to retain a centralized responsibility for the application of GUI XT, either for the whole company or for specified groups.

Yes. In the GuiXT profile you can include a placeholder variable &client in each of the 4 directory names. At run time, &client is replaced by the current client number. With this technique, you can, for example, define 2 directories to be client independent, and a third to be client specific.

.sy1 type of files are used by Designer. GuiXT generates this file when Tools->Designer on GuiXT window or Refresh on Designer window is clicked. This file contains screen protocol information used by Designer to render the screen looking like SAP screen. .inp type of files are used by input assistant. These are text files (can be edited using notepad) that store the current history information. These files need not be deployed to the end users.

Deploy GuiXT scripts (*.txt), Input Scripts (*.txt) and image files (if any)

• Step 1: Deploy GuiXT Program files (GuiXT.dll and GuiXT.exe)
• Step 2: Configure GuiXT (Typically through GuiXT.ini and / or user catalogs)
• Step 3: Deploy GuiXT and / or Input Scripts (Local machine, Network file servers, web / ftp servers, SAP web repository)

You can deactivate GuiXT from SAP via this registry entry in

HKEY_CURRENT_USER/Software/SAP/SAPGUI Front/SAP Frontend Server/Administration.

Add a string variable with the name "DisappearItems" and the value "Activate GuiXT". If this variable already exists already you can add the new entry "Activate GuiXT" at the end separated by ';'

eg: "Generate graphic;Activate GuiXT"

The users will no longer be able to activate or deactivate GuiXT. If GuiXT should be always active you have to set the variable "GuiXT" in

HKEY_CURRENT_USER/SOFTWARE/SAP/SAPGUI Front/SAPGUI frontend server/Customize to '1'

Here you see the GuiXT Customizations. Please see the path from HKEY_CURRENT_USER to GUIXT settings in the screenshot below.

The WiKi link below describes each setting. The Wiki also discusses other details in setting up GuiXT.

http://www.guixt.com/documentation/?n=PmWiki.GuiXTConfiguration#name2