GuiXT in Transaction Variants and Screen Variants

Use the GuiXT function to edit a GuiXT script from transaction variant maintenance. The script is then stored together with its corresponding screen variant in the database. The GuiXT process downloads the script to the frontend if no current version is already on the frontend. GuiXT scripts are transported along with their corresponding screen variants.


GuiXT requires user SAPCPIC with password ADMIN in client 000. In the GuiXT program, these defaults can be customized to meet the user's requirements by choosing Edit ® Profile.

When GuiXT scripts are used in screen variants, or the Business Document Service is used, the RFC user in client 000 should have the following authorizations:

Authorization object:

Field values:

S_RFC: Authorization check during RFC access


S_BDS_DS: Authorization for Business Document Service

ACTVT 03,30


In this example, you create a transaction or screen variant for the transaction described in the section Adjusting Transactions Using GuiXT. You assign a GuiXT script that exists for the second screen to the corresponding screen variant. The image contained in the GuiXT script is stored using the Business Document Service.

Proceed as follows:

  1. Create a transaction variant for the transaction. On the dialog box of the second screen, choose the GuiXT pushbutton.

  2. The editor appears. Choose the Load local file pushbutton and enter the name of the GuiXT script.
  3. Choose the Image files pushbutton to store the image shown in the transaction using the Business Document Service.

    On the dialog box that appears, choose Business Document Server.

    There are two other radio buttons available on this dialog box, Local file and Database. SAP recommends that you store images using the Business Document Service. The Business Document Service does not only provide general document management functions but also a link to the Transport Organizer. Only files with the extensions .BMP, .GIF, and .JPG are supported.

    To use an image for a GuiXT script, enter TA_VARIANTS_IMAGES in the field Class name.

    In the field Object Key, enter a name of your choice (for example, DEMO). In this case, the object key is a description of the directory in which you store your image files.

    If this directory contains image files already, choose Refresh display to update the data. The image files stored in the directory specified are then displayed in the lower part of the screen.

  4. Choose Import to load images from your PC for the Business Document Service. The system displays a dialog box. Choose the desired file.

    The name of the image and other attributes are displayed in the lower part of the screen.

    The Lifetime is specified in days.

    Your company has changed its logo as of a specific date and you want the new logo to be displayed on SAP screens instead of the old one. You have restricted the validity of the old logo image to a specific number of days. When the validity of the old logo runs out, the new logo will automatically be downloaded to all PCs affected, if required, provided that you give the new logo the same file name as the old logo image file.

  5. Double-click the desired file name. The system displays a dialog box with the description of the image file. In this case:


When you confirm the dialog box, the corresponding Image statement is placed at the beginning of the GuiXT script.


To transport an image file, choose Navigator. The system takes you to the Business Document Navigator. Choose the desired image, and then choose Transport documents. Further information can be found in Business Document Service.

You can also use transaction SHDI to store image files used in GuiXT scripts, in the SAP System.