This section contains the release notes for the following SAP GUI for Java 7.30 releases:

• Release 7.30 rev 2 (May, 2013)
• Release 7.30 rev 1 (February, 2013)
• Release 7.30 (December 20, 2012)

Release 7.30 rev 2 (May 2013)

• Enhancements and New Features

• Bug Fixes

Release 7.30 rev 1 (February 2013)

• Enhancements and New Features

• Bug Fixes

Release 7.30 (December 2012)

• Enhancements and New Features

Installation Logfiles

Those files are created in the %PROGRAMFILES%\SAP\SapSetup\LOGs folder

• NwSapSetup.log: Is written whenever NwSapSetup.exe is started and contains the actions taken during installation of frontend components, uninstallation, update or while addingor removing single components or packages.
• NwSapSetupAdmin.log: Is written whenever NwSapSetupAdmin is started. This means it contains information about creating, modifying or deleting packages, configuring the Automatic Workstation Update Service, applying patches to the installation source and so on.
• NwSapSetupUserNotificationTool.log: Contains information about the tool that displays status messages of the Automatic Workstation Update Service.
• NwSapSetupUserNotificationTool.log: Contains information about the tool that displays status messages of the Automatic Workstation Update Service.
• NwUpdateInstServer.log: Is written whenever NwUpdateInstServer.exe is started which is the case when new products are added to an installation source, when a patch is applied or when an  installation source is created. In the latter case NwCreateInstServer.exe creates an empty installation source without any products and then NwUpdateInstServer.exe is called in order to import the initial set of products like SAP GUI 7.20, Business Explorer and the usual suspects.
• gui720_.log: Is written by the self-extractor used in patches and only contains information about the extraction of files from the patch and cleaning up the temporary installation source after applying the patch. Between the extraction and cleaning up either NwUpdateInstServer.exe is used to update an installation source with the content of the patch or NwSapSetup.exe is started for applying the content of the patch to an installation on a client machine (local patching). The information about applying the content of the patch can then be found either in a NwUpdateInstServer.log or NwSapSetup.log depending on whether an installation source has been patched or a client machine. This log e.g. contains error messages when there is not enough disk space for extracting a patch or when a patch has been broken during download from SAP Service Marketplace due to bad lines or so.
• regsvr.log*: Contains information about registering a certain control.

Rotating Logfiles

NwSapSetup and the services DS and IS all have their own logfiles. On a client there are 10 NwSapSetup logfiles at a maximum. The most recent one of them is always NwSapSetup.log. If NwSapSetup.log already exists when NwSapSetup is started it will be renamed to NwSapSetup1.log and a new NwSapSetup.log will be created. An already existing NwSapSetup1.log will be renamed to NwSapSetup2.log and so on. The oldest existing NwSapSetup logfile is always NwSapSetup9.log. The same applies to the log files written by e.g. the Distribution Service (DS) or NwCreateInstServer.exe and so on.

What are GUI Controls?

"GUI controls are independent software components that run on the presentation server and are not part of the ABAP runtime environment of the application server."

A more practical definition of a GUI control would be: A GUI control is visual an element on the GUI screen which allows the user to enter, change or delete data. In that regards,a typical example can be: calendar control, the ALV, the tree control or a HTML control. These controls allow users to enter, edit or delete data.

The functions contained within GUI controls, such as scrolling through the texts (html control) or lists (ALV Grid), is performed on the presentation server (client) and free the application server of that work. On the other hand, GUI controls often work with large amounts of data, which is why frequent data transfers between the ABAP program (application server) and the GUI control (presentation server) can increase the load on the network (performance issue). From the developers perspective this means that the logic of a ABAP program should ensure that most of the work can be performed on the client and that synchronization with the backend (application server) is limited to the minimum.

There much more other GUI controls which unfortunately do not meet our practical definition, but they are at least visual elements which can alter or control the visual appearance of the GUI screen: Custom Container, Docking Container, Splitter Container, or a Tab-Strip. The technology of independent software components is the same like in all other GUI Controls, but these controls are not intended to carry any data -- They are intended to display a picture (like the Picture Container) or to control the alignment of other controls (Splitter Container).

Digression: The Control Framework

The definition of a GUI control states that "GUI controls are independent software components" -- independent in what way? We have to understand that communication between the GUI control and the ABAP program: In classical screen processing (not using any GUI control) an ABAP program communicates with the SAP-specific screen elements on the layout of a screen. GUI controls, on the other hand, are software objects with independent interfaces that are not connected to the classical data flow between the application server and presentation server. Communication between the ABAP program and the control is provided instead by the Control Framework (CFW), which contains components in the runtime environment of the application server as well as in an Automation Controller on the presentation server. The main feature of the CFW is that there is a global class in the class library for each GUI control supplied. The CFW forwards its method calls to the actual GUI control objects and iforms the objects of the ABAP program by triggering events about the user actions on the GUI control.

The Control Demo Center:

To differentiate between controls in a SAP system, the following can be used:

• Enjoy Demo center: Transaction dwdm
• Style Guide: Transaction bibs

The Enjoy Demo Center provides numerous show case transactions and reports that have been created in ABAP using GUI Control techniques. Many user interfaces including the ABAP Workbench itself have been redesigned for the new EnjoySAP Release. These examples demonstrate how to divide up a screen into different areas using docking and splitter GUI controls, and how to use tree control to display hierarchies.

=

The following are the SAP GUI Related Notes (SMP Login required to access the note)

SAP GUI FAQs in General:

What do I do in case logon problems occur?

Always verify logon problems on a different machine as it sometimes might be a local problem with your workstation. Usually you will be able to see a pop up box if you are experiencing a networking error. In the case you get to the first screen, the logon screen, please check with a colleague to log on as this might be a permission problem related only to your user account.

A networking error often will give you an error message with the code '10054 - connection reset by peer'. This is usually due to a broken network connection. Please verify this on an additional workstation. If you refer to your network administrator you can run a first basic diagnosis with the SAP tool 'NIPING' according to note 500235.

What to do if SAP Logon refuses to start?

Please run the SAP Logon-Trace. This trace is only available since release 4.6B.

How to start the SAP Logon-Trace?

On DOS-prompt type: "start saplogon/trace=3". These files will be generated: dev_xxxx.log and dev_xxxx.lgd.

How to stop the trace? Close SAP Logon.

This trace is also very helpful if insert/delete/change of entries in the Logon is not working. Moreover, if we have to figure out, with which parameters the GUI was started, this trace will help.

What should I do if the SAP GUI cannot connect to the SAP system, the response times of the SAP GUI are very bad or the communication between SAP GUI and backend is interrupted?

Please run the SAP GUI-trace.

How to start the SAP GUI-trace?

In SAP Logon press: Alt+Space -> Options -> Activate SAP-GUI trace level 'Level2' OK

Which files will be generated?

<= SAPGui 4.6d all dev_*.* files from SAPWORKDIR

>= SAPGui 6.10 all sapgui*.* files from SAPWORKDIR

What is the difference between 'Classic Design' and the 'New visual Design'?

SAP GUI features two different modes, New Visual (or Enjoy) Design and Classic Design (the older types of SAP GUI before 4.6 could be defined as Classic Design). Both designs are 100% compatible with the functionality connecting to SAP systems.

Classic Design: Under the three colored circles in the menu bar (the SAP GUI-Icon) you will find the options to manipulate SAP GUI Colors, Fonts and further user options. These options are to be set up by every user to suit personal preferences. There is no mean to apply these particular changes to your whole environment of every PC in your company.

New Visual Design: In this skin the icon to get to the option looks like a PC monitor and is placed at the right hand side of the menu bar. As SAP defined a certain look and feel you can only make changes in fonts and size only to a certain extent.

What kind of adjusting of the local layout of the GUI can be made?

This FAQ is not the right place for explaining all options which can be changed by the user. So, please review the GUI specific help. Choose the three-colored GUI icon, and select then the 'SAP GUI Help' menu. Go then to 'Adjusting the local layout'. In this section all possible configurations of the local layout are explained.

What SAP GUI can be used to run on non-Windows operating systems?

SAP GUI for Java can be used on various platforms, please refer to note 146505 and the SAP GUI Family page at http://scn.sap.com/community/gui

Where can SAP GUI for Java be downloaded?

SAP GUI 7.30 for JAVA

SAP GUI 7.30 for JAVA Patches

Where can SAP GUI for Windows be downloaded?

SAP GUI 7.30 for Windows

SAP GUI 7.30 for Windows Patches

When is the next release of SAP GUI for Java to be expected?

Please refer to Note # 1229666

What are the supported SAP GUI Platforms?

Please refer to Note # 66971

What are the new features in SAP GUI for Windows 7.30?

Please refer to Note # 1670678

What are the required Java runtime versions and other prerequisites for running SAP GUI for Java 7.30?

Please refer to Note # 1758540

How to install SAP GUI on Windows Terminal Server (WTS)?

Please refer to Note # 138869

How to limit Number of SAP GUI for Windows Sessions in the Portal?

Please refer to Note # 975004

How to find out, if a new version has been released?

Please refer to note 1014347 how to get notified by email as soon as a new version has been released.

How to resolve an issue when installing SAP GUI for Java?

Please create a support message and add the guiinstall.log file as an attachment. The installer displays the path in a message dialog, where guiinstall.log can be found.

How to resolve an issue when SAP GUI for JAVA is running inside the portal?

Please create a support message and add the guiinstall.log file as an attachment. The installer displays the path in a message dialog, where guiinstall.log can be found.

How to configure SAP Logon in SAP GUI for Java?

Please refer to chapters 7 and 9 of the documentation that comes with the SAP GUI for Java installation and is also available online at http://scn.sap.com/docs/DOC-25456

How to use the SAP Logon configuration of SAP GUI for Windows with SAP GUI for Java?

There are conversion scripts including documentation available at http://scn.sap.com/docs/DOC-25456

How to fix the error message "Attempt to load shared library failed"?

In case the additional error text indicates, that the library is missing, please try to solve the problem by reinstalling SAP GUI for Java. In other cases, please refer to note 909250, in most cases, the required C++ runtime is not found.

How to troubleshoot a certain transaction results in an ABAP dump?

In case this happens right after login and before displaying the easy access menu, this might be caused by missing codepage files. Please refer to note 550564. In other cases, please submit a bug report according to note 326558.

How to enable tracing in SAP GUI for Java?

Please refer to Note # 683960

How to fix SAP GUI Crash problem?

Please submit a bug report and attach the crash log-file (Linux and Windows hs_err_pid*.log, Mac SAPGUI*.crash)

How to report bugs?

Depending on the issue, it might be helpful to read the documentation or consult the SAP GUI forum on SDN (searching in old threads or posting a new thread with your question). The SAP GUI forum on SCN is available at http://scn.sap.com/community/gui. In case this does not help to solve the problem, please refer to note 326558, what information should be included in the support message.

How do I install SAP GUI on multiple PCs?

SAP also delivers a full-featured distribution tool for maintenance of large numbers of PCs. There is no necessity to use third party tools. See the Frontend Installation Guide and OSS note 361222 for details.

How do I uninstall and delete all SAP GUI files?

To perform silent, unattended uninstallation, enter the following commands:

NWSAPSetup.exe /Product=”<product name>” /Silent /Uninstall for uninstalling a certain product, for example SAPGUI710.

NWSAPSetup.exe /all /Silent /Uninstall for uninstalling all SAP components installed by SAPSetup without having to call specific command-lines for specific products

Is there a SAP GUI for Java available for my operating system platform?

Versions for the following platforms are available:

Mac OS see SAPNote # 509733 for further details

OS/2 OS/2 Warp 3/4

Linux RedHat Linux 7.1 / SuSe Linux 7.2

Solaris Ultra Sparc; SunOS 5.6, 5.7 or 5.8

AIX AIX 4.3.2 or 4.3.3

Tru64(*) 4.0D or higher HP-UX HP 9000 / HP-UX 11.0, HP-UX 11i Windows Win 98, NT 4, Win 2000, Windows XP (*) A Tru64 version is available on request only (customer message on component BC-FES-JAV required). For further details consult the documentation that ships with the software or notes 146505 and 509733.

What can I do if Dr. Watson errors occur?

For every Dr.Watson errors please make sure you can reproduce the problem on another PC. SAP Support can only track down problems if you are able to recreate them. Errors usually follow certain patterns. Intermittent problems like a crash once a day might occur by random and if you can't find a pattern we won't either. Moreover, please review notes # 559285 and 520688 including the optimization paragraph. Afterwards please send the new FrontException.TRC to SAP.

How to create the right trace files in case of issues with SAP GUI?

1 - SAPSETUP.LOG (created during installation of the GUI)

2 - SAPCHECK.SCK (created using attached note 323413)

3 - Trace files, created using attached note 50226

a - activate the trace

b - recreate the error

c - stop the trace

Please ZIP the files together in one archive and upload them to SAPSERVxusing attached note 40024. Please note that the trace described in note 50226, will result in the following files:

<= SAPGui 4.6d all dev_*.* files

from SAPWORKDIR >= SAPGui 6.10 all sapgui*.* files from SAPWORKDIR Please make sure that you include all the trace files.

How to fix “Missing particular elements  in display”, “wrong scrollbar”, “no resize events”, “wrong length of a list”?

Please run the Frontend-trace (see note 305363). In SAP GUI press the three-colored icon -> options -> trace -> Mode: Monitor - Trace-File: ENABLE [X] The Front.trc file will be generated.

How to fix ABAP shortdumps with CNTL_ERRORS in R/3 system?

Perform a SAPCHECK (see note 323413) and make an Automation trace according to note 158985. Send both files to SAPSERVx (note 40024). For further information please review also the GUI specific help. Choosethe three-colored GUI icon, and select then the 'SAP GUI Help' menu.

Introduction

This document describes how to set up and maintain an SAP GUI Installation Server for the efficient distribution of SAP Front end Components across workstations in your organization.

Overview

SAP’s Front-End Software Deployment Tool – Netweaver SAPSetup not only allows direct installations from distribution media, but also an Installation Server based deployment mechanism that helps distribute SAP Front-End Software to workstations over a network and also using Microsoft SCCM  to deploy the large number of users.

General Features of SAP GUI Installation Server:

Fully-featured installation, uninstallation, update, repair, and patch functions for SAP front end components:

• Front end components are available from an installation server or a distribution medium such as a DVD.
• Install new SAP front end components, uninstall existing ones, and update the remaining components in one cycle.

Easier and more reliable handling of SAP front end components by using installation servers:

• Maintain nearly all Windows-based SAP front end components on a single installation server.
• Integrate additional SAP front end components into an existing installation server, such as Import Product.
• Deploy multiple SAP front end components on workstations using a single command.
• Easily manage the installation server with wizard-driven user interfaces.
• Local Security Handling (LSH), when configured, lets you deploy SAP front end components on workstations without requiring administrator privileges on all machines.
• Whenever installed SAP front end components or packages change on the installation server, the automatic workstation update service (AWUS) will, once configured, automatically update the workstations and reboot them if necessary.
• Easier handling of multiple SAP front end components by configuration of installation packages – by implementing script events, you can customize and extend the installation of such packages.
• Controlling workstations remotely helps you to remotely access and control workstations on which you have administrator privileges. You can collect remote log files, execute processes remotely, and list remote processes.
• The directory for the creation of the installation server is configured automatically. By default, it is made NULL-session accessible. It can be shared automatically on the network for everyone to read.
• If NwSapSetup.exe is started from a batch file, the return code can be caught by the environment variable %ErrorLevel%.

Important Notes for the SAP GUI

It is important that you read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information about the installation, as well as corrections to the installation documentation.

0000026417_SAP GUI Resources Hardware and software

0000038119_SAP Logon Administration of functions

0000066971_Supported SAP GUI platforms

0000147519_Maintenance strategy deadlines for SAP GUI

0000166130_SAP front end Delivery and compatibility

0000328723_GUI default settings during installation

0000508649_Diagnosis of frontend installation problems

0000535308_How to apply a SAP Front End patch

0001053737_Expected release dates for SAP GUI for Windows & ITS Patches

0001085218_NetWeaver 7.x BW Frontend Patch Delivery Schedule

0001144671_New SAP Installer for SAPGUI for Windows 7.10

0001169612_Cannot start NWSAPSetupAdmin over a network path

0001397000_SAP GUI for Windows Security Execution of SAP Shortcuts

0001414580_Jaws & SAP GUI configuration

0001426178_SAP Logon (Pad) create and distribute server configuration file

0001442028_SAP GUI for Windows No support for Office 2010 64bit

0001583967_Release Information Note for SAPSetup 9.0

0001587566_Installation problems with SAPSetup Version 9.0

0001588323_SAP GUI for HTML cannot be started (NW Basis 7.30)

0001652770_BI 7.x in 730 DVD1-BI client tools - contents & versions

0001669254_SAP GUI 7.30_Branding image in title bar

0001670678_730_New Features

0001685221_SAP Logon maintain system entry without sapmsg.ini and service file

0001702037_BW 7.x Frontend in GUI 730 - First Customer Shipment

0001710864_SAP Logon 7.30_possibility to disable views via registry

0001726742_SAPBWNews NW 7.x BW Add-On Frontend Patch 300 - GUI 7.30

0001796138_SAPBWNews NW 7.x BW Add-On Frontend Patch 201 - GUI 7.30

0001797599_RRMX for BEx Analyzer 3X is not supported with SAP GUI 730

SAP GUI Software Download

(Note: Service Marketplace Login required downloading the software)

SAP GUI 7.30 For Windows

SAP GUI 7.30 For JAVA

SAP GUI 7.30 for Windows Patches

SAP GUI 7.30 for JAVA Patches

BI 7.0 ADDON FOR SAP GUI 7.30

Patches for SAPSetup 9.0

Hardware and Software Requirements

Make sure in advance that your system meets the following requirements:

• The host for server-based installations must meet the following conditions:
  • Accessible to all users at all times, even after the installation is complete. This is required for maintenance purposes such as the distribution of patches.
  • Have broadband network connection for high throughput
  • Have sufficiently free disk space for all SAP front end components
  • Use a Windows server as operating system

Note:  Read SAP Note 26417 to check that all hardware and software requirements for the front-end workstations have been met.

How to Setup an Installation Server

The installation process from an installation server is flexible, easy, and customizable. It makes maintenance easier in any phase of the distribution process, for example, when applying patches.

When installing SAP front end components with server-based workstation installation, the following options are available:

• Without user interaction (unattended)
• With user interaction (attended), where the user has the following options:
  • Select from installation packages that the administrator has configured
  • Select from a complete list of SAP front end components available on the installation server

The following figure shows how the installation with an installation server works.

With an installation server, the administrator can group various SAP front end components together as installation packages relevant for certain employee roles. The administrator can also specify which package particular users should receive, or offer a variety of packages and allow the user to choose the most appropriate one.

To keep workstations up to date automatically, use the automatic workstation update service (AWUS). Whenever the installation server is patched, or packages are updated on the installation server, this service will update the workstation(s) and reboot them, if necessary. The AWUS works regardless of whether a user is logged on or not:

Creating an Installation Server

NWCreateInstServer is a wizard-driven tool that helps the administrator to create a new installation server. After the server is set up, NwUpdateInstServer imports SAP front end components from the source into the newly created installation server.

Start NwCreateInstServer.exe from the Setup directory.

Choose Next to continue.

NwCreateInstServer.exe prompts you to supply the path to the directory in which you want to create the installation server.

Choose Browse to navigate to the directory in which you want to create the installation server. Ensure that the directory is empty.

Choose Verify to ensure that the chosen directory meets the prerequisites:

Choose Share to maintain the file-sharing properties of the selected directory for distributing using logon scripts and automatic workstation update service

Choose Next to continue.

Processing is recorded in the file NwCreateInstServer.log located in the SAPSetup log file directory.

The wizard confirms the successful installation of the installation server.

You now have a valid but empty SAPSetup installation server.

If you want to set up an empty installation server, you can skip the update by calling NwCreateInstServer.exe with the parameter /NoServerUpdate on the command line. In this case, the procedure ends here.

To update the installation server, reboot the Installation Server and execute NwUpdateInstServer.exe to transfer SAP front end components to your installation server.

Navigate to the Installation Server folder and Click verify to start the Update

The wizard displays the progress of the installation server update.

NwUpdateInstServer.exe transfers all SAP front end components available in the downloaded objects to the installation server.

If you have .NET Framework version 4 installed, choosing Finish Automatically starts NwSapSetupAdmin.exe from the recently updated installation server.

Administering an Installation Server

After you have successfully set up the installation server, you can find admin tools in the SETUP directory of the installation server.

• NWCreateInstServer: Installation Server Creation Wizard Driven Tool that helps in creating a basic Installation Server and configures.NET Security to administer it over a network path.
• NWUpdateInstServer: Installation Server Update Wizard Driven Tool is used to update an Installation Server with SAP Front-End Components. This utility will also automatically update older versions existing on an Installation Server by newer ones.
• NWSAPSetupAdmin: Installation Server Administration Wizard Driven Tool that helps in maintaining and configuring an Installation Server, creating packages, importing products, apply patches etc.  Administrators can create a Package Definition File to deploy the package using like Microsoft SCCM.
• NWSAPSetup: Front-End Installation Tool is used to install SAP Front-End Components available on the Installation Server on a Workstation, to update an installation or to perform un-installations.  Administrator can install manually or using command lines to perform the installation silently and unattended deployments
• NWCheckWorkstation: This utility is used to diagnose the health of the Workstation containing installed SAP front-end components. It creates a CAB-file with the error information. If required, you supply the logs to the SAP Primary Support.
• NWSAPSetupDS: This tool allows you to configure (Local Security Handling) that helps administrators to allow domain users with non-administrative privileges to install software locally on their workstations.

Import Product: Use this feature to add new products (for example, SAP front-end components) to an existing installation server for distribution over the network.

Export Product: Use this feature to export front-end components available on one installation server to another.

Delete Product: Use this feature to delete a product from an installation server.

Create Package: Use this feature to create packages for deployment. Packages can contain many components and their installation parameters can also be customized.

Create Package Definition File (PDF): You can create a package definition file (PDF) for an installation server package. PDF is a package description format that simplifies the interoperability and information exchange between the SAP Installer and system management products like the System Management Server from Microsoft.

Configure Package: Use this feature to change the attributes or the content of your packages.

Patch: Use this feature to patch components that are available on the installation server.

Local Security Handling: This feature allows workstation users to install SAP components from the installation server without requiring administrative privileges.

Automatic Workstation Update: Whenever the installation server is patched, or the packages installed are updated, this service will update the workstation and reboot them if necessary.  The workstation updater works in two modes - one in the presence of a logged-on user and another in his or her absence:

When a user is logged on, the user is informed of update availability and the update happens on the user's assent. The user is also informed if a reboot is necessary and the reboot is also only executed on the user's assent.

If no user is logged on, the update is done automatically and the reboot (if necessary) is done automatically, too.

Control Remote Workstations: This functionality uses the Windows Management Instrumentation (WMI) to help you remotely access and control workstations on which you have administration privileges. You access this feature via the Remote menu, where you find the options to:

Collect remote log files

Execute processes remotely

Enumerate remote processes

You find detailed information in section Controlling Remote Workstations.

Adding New SAP Front End Components to an Existing Installation Server

Click on Import Products

Click Next and follow the wizard instructions

Navigate to the product download location and select the “Setup” Folder

Product import completed

Updating Products on the Installation Server with a Newer Version

Start “NwUpdateInstServer” from the setup directory and follow the wizard instructions

Navigate to the Installation Server folder you want to update and “Verify” the Installation

Click Next to continue the installation

Check the logs for information if the Installation Server update fails for any reason.

Installation Server has been updated successfully

Deleting Products from the Installation Server

Right click on the product and choose “Delete product….” to delete the product.

Click Next to continue product deletion

Choose Close to finish the product deletion.

Creating a New Installation Package

Navigate to the Packages tab and Click on “New Package” to create a new Package.

Configuring Packages and Event Scripts

Switch to the Packages tab page. In the left window pane, you can see a tree listing the existing packages.

The (X) cross indicator next to a package indicates that the package is incomplete. This typically occurs when a product that the package contains has been deleted from the installation server. You can either delete this package or re-import the missing product.

Select the package that you want to customize and navigate to “Package Configuration”

• Verify the Package Parameters (Variable Name, Package Value and Variable Description)

Add event-scripting to perform custom actions on the user’s workstation during the installation of the package (for example, copying additional files). You can insert scripting samples delivered by SAP via Insert Script and adapt them to your requirements. The scripts are executed at the following events:

• On Begin Install: executed before the installation of a selected package
• On End Install: executed after the completion of package installation
• On Begin Uninstall: executed before the uninstallation of a selected package
• On End Uninstall: executed after the completion of package uninstallation
• On Begin Update: Executed before the update of a selected Package.
• On End Update: Executed after the completion of the Package update.

Example:  If you want to check a file for existence on the workstation, navigate to “On Installation End” tab and insert a script sample and modify according to your requirements.

Changing the Package Content

• Switch to the Packagestab. In the left window pane, you can see a tree listing the existing packages.
• Select the package for which you want to update the content, and choose Change Package Content.

You can now select or deselect components. Components added will be newly installed on the workstations. Those removed will be uninstalled from the workstations, if they are not part of any other package marked for installation. When updating a package, the package installation parameters are also refreshed and include new variables or delete those that belong to components that are no longer part of this package.

Follow on screen instructions and Save the package when you are finished.

Deleting an Installation Package

• Navigate to Packagesview.
• Right-click the package you want to delete.
• From the context menu, choose Delete Package.
• The package is deleted. It is removed from the Packages view.

Creating and Deploying a Single-File Installer for Packages

You can create single-file self-installing .exe-packages via NWSAPSetupAdmin.exe.

Such a package contains only those files that belong to the components that are a part of the package. Thus, it reduces your network load in certain distribution scenarios where you previously had to make local copies of your installation source before installing.

This single-file self-installer can also install silently without user interaction.

Creating a Self-Installing Package

In the Packages tree, right-click the package you want to create a self-installing file from, and choose Compress To Single-File Installer

Following the wizard instructions, you will get a single exe-self-extractor at the end of the process.

Deploying a Self-Installing Package

• The self-installing file created above can be executed on any workstation to install your package.
• Follow the installation wizard.
• This self-installing package can be installed silently (i.e. without user-interaction) when invoked with the command-line parameter /silent.
• This self-installing package can be installed with no dialog (i.e. user can see the installation progress) when invoked with the command-line parameter /nodlg.

Creating a Package Definition File (PDF)

You can create a package definition file (PDF) for an installation server package. PDF is a package description format that simplifies the interoperability and information exchange between the SAP Installer and system management products like the System Management Server from Microsoft.

On the Packages tab, right-click the package for which you want to create a PDF file and choose Create Package Definition File.

Choose the directory where you want to save the file, enter a file name, and choose Save.

Patching the Installation Server

Patching products on the installation server keeps them up-to-date with the most recent correction and enhancements from SAP.

Choose Patch Server.

Choose Next to continue.

Browse to a valid SAP patch file and choose Next to continue.

NWSAPSetupAdmin.exe now validates the patch, which takes a few minutes.

If the patch is valid, you are prompted to proceed with it.

To ensure that the installation server is not in use, the patch now closes NWSAPSetupAdmin.exe before continuing. It restarts NWSAPSetupAdmin.exe after completing the patch.

Choose Next to continue.

NWUpdateInstServer.exe starts patching the installation server.

Follow the patch wizard, choosing Next as required.

At the end of the process, you see a message indicating that the patch was successful.

Choose Close.

NWSAPSetupAdmin.exe now restarts.

Check Update Log Files:

%ProgramFiles%\SAP\SapSetup\Logs\NWUpdateInstServer.log.

If there are errors, you see a link to an Error Report. Any errors are recorded in the following file, which you can view using your normal web browser:

%ProgramFiles%\SAP\SapSetup\Errors\ NWUpdateInstServerErrors_<CurrentDateTime>.xml.

If you have a problem, create a problem message on component BC-FES-INS and attach these files to the message.

Configuring the Local Security Handling (LSH)

Local security handling (LSH) lets users on the network deploy SAP front-end components on their front ends using NetWeaver SAPSetup without requiring administrative privileges on each workstation.

Choose Services and select Configure local security handling.

The LSH configuration wizard starts.

Choose Next.

The wizard prompts you for the credentials of an account that has administrative privileges for all front ends on the network.

Enter the account name with domain qualifiers.

Choose Verify and Next

The wizard will be prompted to enter details for the installation service (IS) account, Verify, and choose Next to complete the process.

The wizard displays the success state in starting the distribution service and the status bar at the bottom of NWSAPSetupAdmin.exe displays the service state as Active.

Test the functioning of the LSH feature by starting NWSAPSetup.exe from this installation server on a front end where the logged-on user has ordinary user privileges (that is, the user does not have administrative privileges).

If the front-end installer starts successfully and is able to install components available on the installation server, the configuration is successful. If not, you need to reconfigure LSH.

LSH Related Notes

Note 1288344 - NwSapSetupAdmin: Could not store IS user data

Note 593486 - Installing the DS installation service (analysis notes)

Local Security Handling broken on patch level 6

7.xx Installing the DS installation service (analysis notes)

Note 1587566 - Installation problems with SapSetup Version 9.0

Configuring the Automatic Workstation Update Service (AWUS)

The SAP Automatic Workstation Update works only when installed on the workstation. Whenever the installation server is patched, or the packages installed are updated, this service will update the workstation(s) and reboot them if necessary. The workstation updater works in two modes - one in the presence of a logged-on user and another in his or her absence:

• When a user is logged on, the user is informed of update availability and the update happens on the user's assent. The user is also informed if a reboot is necessary and the reboot is also only executed on the user's assent.
• If no user is logged on, the update is done automatically and the reboot (if necessary) is done automatically, too.

Note: This service updates itself, when a patch of automatic workstation update is available.

Choose Services -> Configure automatic update.

The screen Automatic Workstation Update Configurations appears as shown in the following picture:

You have now several options:

• Update check frequency
  • The workstations that will have this feature installed, will poll the installation server at this interval to check for update availability. The default is 24 hours and the Maximum can be 744 hours.
• Enforce reboot after every update
  • When this flag is not set, the user is asked to reboot only if it is required to complete the deployment process. When the flag is set, a reboot is enforced, which means that the user is always asked to reboot.
• Additional Update Sources (optional)
  • You can index additional servers. The update service will then look up the indexed servers per line in the given order for available updates.

Save your entries and close the program.

To make the automatic workstation update service available on workstations, you should create a package using NWSapSetupAdmin.exe on the installation server. This package should consist of SAP GUI for Windows and SAP Automatic Workstation Update. Once automatic workstation update is installed, then the following programs will run on the workstation in the background: NWSAPSetupUserNotificationTool.exe and NWSAPAutoWorkstationUpdateService.exe.

Note: The front-end side will query the last 10 installation sources that are network paths.

You have configured the SAP Automatic Workstation Update and made it available on the workstations.

To disable the service, activate the option ‘Disable Automatic Workstation Updates’ in the configuration tool on the installation server (see picture above). This configuration change is propagated as an update to the workstations at the time of the next update check.

Note: Once disabled, this action cannot be undone until the Automatic Workstation Update Service is reinstalled.

AWUS Notes

Note 1584270 - AWUS & SapSrvSetup.xml

Note 1624251 - Moving an Installation Server to a new machine

Controlling Remote Workstations

The remote workstation control functionality helps you to remotely access and control workstations on which you have administration privileges.

Choose Remote.

You have now several options:

Collect Log Files

With this option, you can collect log files from remote workstations. For this, you just have to enter the workstation name. In case you want to collect log files from several machines, you have to separate the different names by a comma.

Look at the remote workstation log files on your local pc after download.

Execute Process Remotely (WMI)

With this option, you execute processes on a remote workstation. You just have to enter the workstation name as well as the application name in the appropriate field. Also, you can supply the application with the appropriate command line parameter, for example: c:\program files\sap\sapsetup\setup\nwsapsetup.exe /uninstall /all /silent. Then choose Execute to run the process on the remote machine.

Remote Task Manager (WMI)

With this option, you get a list of processes running on a remote workstation. Just enter the workstation name and choose Display. If you want to terminate a process, select the process and choose Terminate.

Note: Be careful with the Terminate option, because the user may lose unsaved date.

Troubleshooting

If you encounter problems with the WMI feature, diagnose WMI connectivity to a remote workstation using the Microsoft tool wbemtest.exe. Note, that you have to supply the connection namespace as \\WorkstationName\root\cimv2.

Delegation

In order to start an installation on a remote workstation that is located on an installation server, delegation is required to be activated for the client machine(s) in question. Please, refer to the Microsoft TechNet article at http://technet.microsoft.com/en-us/library/ee692772.aspx, question 10 for further details.

Installation Process

Installing SAP Front End Components from an Installation Server

This procedure tells you how to install Front end Components from an installation server

Start NWSAPSetup.exe from the SETUP folder on the installation server.

The SAPSetup installation wizard appears.

Choose Next.

The product list is displayed. Products that have already been installed are pre-selected as shown in the following picture:

Select the products or SAP front-end components that you want to install or deselect the ones you want to remove.

Yellow dots indicate changes in the selection list. The Green plus next to a product name indicates that “This item will be installed” when the user installs the package on his or her workstation.

The checkbox with no additional symbols indicates that “This item is already installed” Uncheck the product if you don’t want to reinstall.

If you deselect a product in this list that has already been installed, a Red minus appears to indicate that “This item will be uninstalled”

Follow the wizard instructions to finish the GUI installation.

Installing Packages Configured by the Administrator

This procedure lets you install or remove packages on your front end that have been configured by the administrator on the installation server.

Note: Be careful when removing packages. Make sure you do not mistakenly remove shared components that are used by other packages you want to keep.

Start NWSAPSetup.exe /package from the SETUP folder of the installation server.

A list of the packages that the user is authorized to install or uninstall is displayed. Packages that have already been installed are pre-selected.

In this case, the BW Package has been selected for installation. The yellow dot indicates a change in the selection list. The green plus next to the product name indicates that this object will be installed when the user installs the package on his or her workstation. If you deselected a package, you would see a red minus next to the object selected for de-installation.

Select the components or packages that you want to install or deselect the ones you want to remove.

Note: If errors occur during the installation, SAPSetup displays a link to a document in which the errors have been logged. Contact the administrator of the installation server or the network and pass on the information given in this document.

Installing Packages Using the Logon Script

Since the front-end software is normally installed on a large number of computers, NWSAPSetup lets you automate this task.

By inserting a command line into the logon scripts of the computers on which the front-end software is to be installed, you can start a package installation each time the user logs on.

Enter the following command (both the path and either the package name or unique package identifier must be used):

\\<server>\<shared folder>\setup\NWSAPSetup.exe /package:“<package command-line name>“ /silent

You can also call NWSAPSetupAdmin.exe in the same way to perform this task.

When you start this command for the first time on a computer, NWSAPSetup installs the specified package.

Updating a Workstation from an Installation Server

You can update the front end from an installation server.

Updating the front end basically involves the same steps as an installation; see section Installation of the SAP Front End from an Installation Server

You have the possibility to have the update run unattendedly or automatically:

For unattended update, use the following command line: \\<server_path>\setup\NWSAPSETUP.exe /UPDATE /silent

To update a specific package or product, add:

/package="package command-line name"

Or

/product="product command-line name"

You will find the command-line name of the package or product in the administrative console NWSAPSetupAdmin.exe.

For automatic update, you can use the SAP Automatic Workstation Update. Whenever the installation server is patched, or the packages installed are updated, this service will update the workstation(s) and reboot them if necessary. The workstation updater works in two modes - one in the presence of a logged-on user and another in his or her absence

• When a user is logged on, the user is informed of update availability and the update happens on the user's assent. The user is also informed if a reboot is necessary and the reboot is also only executed on the user's assent.
• If no user is logged on, the update is done automatically and the reboot (if necessary) is done automatically, too.

The SAP Automatic Workstation Update is not SAP GUI-specific, it works with all components available on the installation server. For details, see section 3.9 Configuring SAP Automatic Workstation Update.

Log Files

All the installation tools described in this document maintain an activity record in log files that you can find here:

%ProgramFiles%\SAP\SAPSetup\Logs

Each tool stores the last ten log files.

Error Files

Errors are stored in an XML format in files that you can view in any browser and you can find in the following folder:

%ProgramFiles%\SAP\SAPSetup\Errors

If you have a problem, create a problem message in BC-FES-INS and attach the relevant log files to the message.

Return Codes

The following table describes the return codes for NwSapSetup.exe

Additional Information

Troubleshooting

Note 508649 - Diagnosis of frontend installation problems

References

http://scn.sap.com/docs/DOC-25456

http://scn.sap.com/community/gui/blog/2013/05/08/sap-gui-730-installation-errors

http://scn.sap.com/docs/DOC-42976

http://scn.sap.com/community/gui/blog/2013/05/02/sap-gui-730-patches-and-relevant-notes

http://scn.sap.com/community/gui/blog/2013/05/10/sap-gui-branding

***********

Over the last few weeks, we have posted a selection of How To guides showing how you can use SAP Screen Personas to solve typical productivity issues. Most of these How To guides target SAP Screen Personas users who already have some experience with the product. Starting out with these advanced scripting tutorials might be overwhelming for some new users.

So, if you are new to Personas, and you want to personalize and simply your own experience with the SAP GUI screen, and you do not know how to get started, this document might be exactly what you were looking for.

Our first recommendation is to start with the first screen that you see when accessing your SAP system - the SAP Easy Access menu. There are several ways to change the screens to meet your needs. When you modify this screen with Personas, we recommend that you list all the transactions that you need to do on the corresponding SAP system and make them easily accessible from the start screen.

For example:

I, as a user on our internal demo system, need a cockpit that helps me to provide support to end-users.

So, I need to support the following main scenarios.

• Somebody needs help with the NWBC integration, so we need to go into PFCG
• A new user is required in cloud demo landscape, so we need to open the Netweaver Cloud Admin UI
• Something is wrong with an existing user, so we go into SU01D and check the user
• We also watch the SAP GUI space on SCN to see if somebody needs help with Personas.
• Last but not least, somebody reaches out to us and ask for help with a flavor in transaction XYZ

The following video shows how to convert the SAP Easy Access Menu into the Personas Support Cockpit.

(Watch this video with voice-over by Ian at http://www.youtube.com/watch?v=cd8XAvou2aU)

Step-by-step:

1. create a copy of Basic View
2. Simplify and beautify the existing screen
   1. remove all elements of the screen that are not needed
   2. add a background image
   3. add an additional image as a header
   4. add a label to the execute button
   5. rearrange the transaction code field and images
3. Add additional buttons
   1. add a launch button to jump directly into PFCG (to maintain roles)
   2. add a launch button to open a web page (Admin UI for our demo environment)
   3. add a script button to do a user lookup (leave it empty for now)
4. save and exit
5. populate the script button
   1. switch to basic view to record a script
   2. start the script recorder
   3. execute the sequence of steps that you always execute
   4. stop the script recorder
   5. go back to the flavor and go back into edit-mode
   6. add a custom text field
   7. upload the script and make it dynamic using copy/paste actions
6. finalize the screen
   1. add another launch button to open a menu entry (to logout)
   2. change colors of all buttons
   3. add html viewer showing the latest discussions in SCN in the SAP GUI space
7. save and exit
8. go back into production mode
   1. show the html viewer content
   2. demonstrate the script button
9. switch to other flavors to show other examples

As usual, if you want to learn more or discuss anything related to how to make your SAP GUI screens more functional using SAP Screen Personas, please start a discussion in the SAP GUI space on SCN.

SAP recommends to use ITSmobile, a technology based on ITS for SAP systems as of Basis release 4.6c and higher instead of the Web-enabled SAPConsole. ITS is SAP’s standard technology to bring applications based on ABAP-Dynpros to the web. For systems based on SAP NetWeaver releases higher than 7.0, the Web-enabled SAPConsole (also known as WebSAPConsole) will no longer be supported.

The following table shows the comparison between ITSmobile and WebSAPConsole:

Further Information

For information on ITSmobile see Creating Mobile Applications with ITSmobile.

And for more information on the ITSmobile/WebSAPConsole-Comparison, see SAP Note 1070064.

Hi all,

SAP GUI for Java 7.30 rev 3 is now available on Service MarketPlace.

For the direct link and user requirements please refer to here.

Enhancements and New Features

• Compatibility with new Java versions:
  • A significant change deep inside of the JVM implementation of Java 7 Update 25 (JDK 7u25) and newer has caused problems loading classes resulting in the startup process to fail. The code has been adapted to this new situation to make it work again.
• Security:
  • A menu for choosing the trust level classification of the current connection has been added.
• Templates:
  • The set of configuration files, which can be distributed by the templates mechanism, has been extended. Please refer to Installing Custom Templates in chapter Configuration Files for details.

Bugfixes

• Application startup:
  • There has been a potential race condition reading the configuration files causing the startup process to fail.
• Grid Control:
  • Some background colors have been wrong when using the Enjoy theme.
• Calendar Control:
  • There have been situations when the focus did not move.
  • The layout of the date picker sometimes was wrong resulting in a horizontal scrollbar.
• TextEdit Control:
  • Importing a file erratically has caused to deactivate the limitation to enter only a certain number of characters.
• Themes:
  • An issue with windows using the Design Window Decoratation has been solved.
  • With Tradeshow, the triangle to toggle the display of the status area was missing.

End of Support

SAP GUI for Java 7.20 is no longer supported because Oracle Java SE 6 is no longer supported. Please upgrade to SAP GUI for Java 7.30.

Best regards

Rolf-Martin

Universal Clients for Accessing SAP Systems

SAP GUI is SAP's universal client for accessing SAP functionality in SAP applications such as - SAP ERP, SAP Business Suite (SAP CRM, SAP SCM and SAP PLM), SAP Business Intelligence and so on. SAP GUI functions like a browser. It gets information from the SAP server like what, where, when and how, to display contents in its window. All members of the SAP GUI family have unique attributes that make them especially suited for different user environments. SAP GUI comes in the following three different flavors:

SAP GUI for Windows
SAP GUI for Windows is an implementation especially designed for the Windows operating system, providing a Windows-like user experience and integration with other applications, based on OLE interfaces or ActiveX controls.

SAP GUI for the Java Environment
SAP GUI for the Java environment is a unified SAP frontend for multiple platforms. It is based on a platform-independent architecture and Java implementation. As a major benefit, it provides access to SAP applications that are based on Control-Enabling and therefore used to be reserved for Windows users in the past. Please, note that SAP GUI for Java is also available on Windows.

SAP GUI for HTML
SAP GUI for HTML automatically maps the screen elements in SAP transactions to HTML using HTML Business functions available within the SAP Internet Transaction Server. A web browser is sufficient to access almost all transactions. Please note: Since SAP GUI for HTML is an application running on the ITS, you find corresponding information on the ITS page.
You can find detailed information on the different SAP GUI types under the following links:

• News
• Installation
• Platform Support and Maintenance Strategy
• Literature
• Presentations
• Downloads
• Notification on SAP GUI News
• Related Topics
• Release Information
• SAP GUI Forum

News

Installation

SAP GUI for Windows

SAP GUI for Java

SAP GUI for Java 7. 30 Download and Installation Information
This archive contains among others the SAP GUI for Java installation information.

SAP GUI for HTML/ITS

Platform Support and Maintenance Strategy

Literature

General Information
Frontend Network Requirements (SMP Login required!)
Distributed landscapes today lead to the fact that an increasing number of users connect to a central system from dispersed sites with varying degrees of available bandwidth. As a consequence, user access is through local area network (LAN) and wide area network WAN (dial-up, frame relay, Internet, etc.). This paper contains a description of SAP's frontend characteristics from both a LAN and a WAN perspective.
Please note that this paper does not discuss server-to-server traffic or printing.
SAP GUI Technical Infrastructure
The purpose of this guide is to give you an understanding of the different SAP GUI types, their specific properties and how they communicate with the SAP system. Also, it explains the performance requirements of the infrastructure and describes trouble-shooting options.

SAP GUI for Windows

SAP GUI for Windows 7.30 Help Guide (English Version)

SAP GUI for Windows 7.30 Help Guide (German Version)

This documentation describes the SAP GUI functions.

SAP GUI for Java

Presentations

Downloads

Notification on SAP GUI news

• SAP GUI for Windows
• SAP GUI for Java

Related Topics

SAP JAWS Screen Reader Extension Installation and Configuration

SAP GUI 7.30 and JAWS 13

This document is intended to be used with the appropriate SAP Screen Reader Extension file:  xSRX_36-20002057

This document makes the assumption that Freedom Scientific JAWS screen reader software version 13, SAP GUI 7.30 and Adobe Reader version 9 or above is installed.

Follow the steps below

It is suggested that you give temporary local admin rights to the user prior to installation and then log on as the user to do the installation and configuration.  Local admin rights may be removed after the installation is complete.

1. If JAWS screen reader software is not installed, install per Freedom Scientific instructions.
2. If SAPGUI is not installed, install the latest SAPGUI version 730 and any patches. Both the executables and installation manual can be downloaded from the service market place.
3. Configure the SAP GUI for JAWS. There are “Accessibility User” options for the SAPGUI which must be set.

SAPGUI configuration

Go to Start > Programs > SAP Front End > SAP GUI configuration. 

Choose Classic Theme, under Accessibility and scripting choose Accessibility and check all three checkboxes.

Choose Scripting and check only the Enable scripting check box, the other two must be unchecked.

Choose OK to apply the settings.

4. After the SAPGUI is installed and configured install the screen reader extensions. 

SAP Screen Reader Installation

Verify no previous Screen Reader Extension installed on your PC.  If you see the previous version installed, then uninstall the old version and install the new version.

(Download the latest version software available from the Service Market Place)

http://scn.sap.com/community/gui/blog/2013/05/29/sap-gui-730-download

Start the installation of the SAP Screen Reader Extension by running the file xSRX_XX-20002057. (XX indicates the version number)

Note: If the “Your system does not fulfill the prerequisites” screen appears when installing you need to verify that you have correctly installed JAWS and the SAPGUI or that Screen Reader Extensions are not already loaded.

Choose Next to continue and follow on screen instructions

There are two sets of files which must be installed in directories specific to the operating system.  The installer generally identifies the correct directories; accept the defaults. Choose Next to continue and follow on screen instructions

You should receive the completed installation message – Choose Close to finish the installation

Verify Screen Reader Extension installed by using add/remove programs in the control panel.  There will be a separate line for “SAP Screen Reader Extension”

Reboot the PC.

Log on as the user (still with local admin rights), make sure JAWS is started.

Start SAP and press Alt+F12 or use the mouse to select Customize Local Layout.

Choose Options

Verify Classic Theme and three checkboxes checked for Accessibility options. 

Choose Scripting

Verify only Enable scripting checkbox is checked for Scripting options.

Close all SAP windows and Restart SAP. 

Note: Jaws should still be running.

On this screen press the following key combinations.  Insert + 6.  That is the Insert key and the numeral 6 key, the numeral 6 key must be the one on the main keyboard NOT the one on the number pad.  You should now have a Jaws Configuration Manager screen that looks like the below screen.  Take note the Application on this window should be sapfront.

Expand Speech Verbosity and Select Verbosity Level.

From the speech Verbosity menu select the Verbosity Level and set to Beginner, Highest.

Generally all other options are set at the default.  The end user may require specific settings.

Select OK to close the window.

Close all windows and reboot the computer.

Jaws should start with Windows and announce the Windows logon.  If this does not happen, then the Jaws option to start when Windows starts was not selected during setup and needs to be set via the Jaws Options > Basics menu.

5.   Verify Adobe setup for Pay Statement use with JAWS.  In order for a Pay Statement to display properly for a JAWS user the image has to appear in a new window. Start Adobe Reader, Go to the menu bar, File > Edit > Preferences > Internet > Uncheck  Display PDF in Browser.  OK>.

*****

It feels a little early to be talking about Personas idioms, but in my experimentation so far and in talks with users it seems there are some things we will end up doing a lot. I suspect others will find the same so it seemed worthwhile to create a document describing these things. I'm allowing anyone to edit this document soplease feel free to add any idioms you discover so that we can all learn from each other.

Home screen techniques

Rather than simplifying individual transactions, the Personas work I've seen so far, and certainly what I've been doing, starts one step back by modifying the initial SAP home screen. Typically you remove most of the standard SAP stuff and turn that screen into a "cockpit" giving easy access to useful transactions, information and other things, to save users having to remember transaction codes or menu paths. Listed here are some useful things that can be done directly from this home screen. Here's an example of our first (incomplete) prototype, mostly using the two techniques described below to give users quick access to the information they need.

Transaction-free lookup

I've come across a number of situations where a user has a transaction number (e.g. a PO number or service order number) or some master data (e.g. a cost centre or a userid) and they want to simply check that it is what they think it is. They want to lookup the description or the user's full name. You can obviously run the corresponding display transaction for that, but if all you want is to check one field there is an easier way. Put a text field on the logon screen, a corresponding "Lookup" button and second text field for the result. The lookup button has a script that runs the transaction, grabs the necessary data and displays it back on the logon screen. The "Purchase Order" section above works like this:

For some added finesse, you can link the input text field and the lookup button, so that typing in a username and pressing enter also pushed the button. Then the lookup button doesn't even need to be on the screen, so you can hide it as I have above.

Skipping selection screens

Following on from the above, if you need to display more information than you can reasonably pull back onto the logon screen then you are going to have to run the display transaction after all. But if the identifier (username, transaction number, etc.) for the object you are wanting to display is already in a text field on the screen you can grab it, skip the display transaction's usual selection screen, and go straight to displaying the relevant information.

If you do this, don't forget that the back button will now not go back to where you came from but back to the selection screen. You might want to replace it with a script button that goes back twice, so the user doesn't see the skipped selection screen.

Hello SAP Community!

I recently had a problem with an SAP GUI update that I received. 

Now that I have found the solution, I'd like to share it with everyone. 

My company upgraded my SAP from version 7.1 to version 7.3. 

After my upgrade, I received a request to load some Activity Types.  In my company we have a Script set up in ABAP that loads Activity Types via a custom transaction. 

I go into the custom transaction code, select a radio button, enter a file path, and select Execute.

But, my new GUI made a Security pop-up come up that asks if I'd like to allow SAP to access the filepath that I entered.

This pop-up caused the script in the background of the transaction to stop running.

I attempted to select the checkbox (Remember my Decision) and re-run the process, but it did not fix anything.

Then i went into my security options and set them to prevent the pop-up, re-ran the process, and it still didn't fix anything.

Then, i went into my GUI Options and changed my GUI Theme from the "System Dependant Theme" to the "Enjoy" theme.  I tried to re-run my process, and it worked! 

I no longer  have the security pop-ups and I am able to load activity types with no issue! 

Have a lovely day!

Chrissy

Hi all,

SAP GUI for Java 7.30 rev 4 is now available on Service MarketPlace.

For the direct link and user requirements please refer to here.

Enhancements and New Features

• Java runtime version check:
  • At startup time, it is verified whether the Java runtime meets the feature requirements of SAP GUI for Java. In case the Java runtime is not sufficiant, a warning message is displayed.
• Undo/Redo:
  • Undo/Redo in entryfields now is more consistant with the behavior of other editors.     

Bugfixes

• Html Control:
  • Buttons in html forms were broken with Java 7 Update 25 (JDK 7u25) and newer caused by incompatible changes in the Java runtime internals. A workaround has been implemented.
• Grid Control:
  • Various issues with clipboard handling in editable grid control have been fixed.
• TextEdit Control:
  • The handling of limiting the text length (MAX_NUMBER_CHARS parameter in the constructor) has been made consistant regarding various ways to insert text into the control.
• SAPInfo Control (ABAP class CL_GUI_FRONTEND_SERVICES): 
  • Method DIRECTORY_LIST_FILES did not work when passing in the root directory as input parameter for DIRECTORY.     

End of Support

SAP GUI for Java 7.20 is no longer supported because Oracle Java SE 6 is no longer supported. Please upgrade to SAP GUI for Java 7.30.

Best regards

Rolf-Martin

Steps:

Go to transaction SMW0

We have two options

·                    HTML template for WebRFC applications

·                    Binary Data for WebRFC applications

HTML template for WebRFC applications

With this all web based text or html templates we can maintain here inside package with object.

Binary Data for WebRFC applications

With this all web based image or text we can maintain here inside package with object.

As:

We can also create our own object as: click on create button shown above:

Provide object name:

             Click on import button and provide the file name from presentation server:

Once image name is provided and clicked on open then it asked for the package as:

Press enter and provide your package name

Once the object is created then we need to go to SM30 transaction for table maintenance for table ‘SSM_CUST’ 

This table is mainly used for administrative purpose and has the functionality as
Set Values for the Session Manager / Profile Generator

It allows global setting for all user

         Now In this table we need to maintain the object path we have created above against ID “START_IMAGE”

         and for full window size we can provide” yes” and “no” to the ID “Resize_image”.
        

          Some other id’s are also there, if "ALL_USER_MENUS_OFF" is set to "YES" in upper-case letters then
          it globally deactivate all user menus.
         

Once provide we can have the image at the initial screen of the SAP as:

         The following steps can also be found from initial screen as:

Without changing any configurations unfortunately my searchbar in SE80 is missing.

I guess it is a memory problem because I started a huge Query on a MultiCube.

Well the result is that my searchbar in the developer workbench is missing.

And not only that. Some debugger-messages are blank too. (look at screenshots)

Well after rebooting my computer everything works fine again.

Time ago, I decided to look for a way to add some life and additional functionalities to my personal boring menu screen... Wait!
This not another document on how change background colours or image on the right upper...

And after some work, I wanted to share with you the results and how-to.

Let’s have a look at the differences:

Block 1: added pushbuttons in toolbar to exit SAP and navigate to SPRO in a new session.

Block 2: added gifs in application bar with different functionalities: navigate to Accuweather and to Google Maps, execute:
MS Word, SAP general menu and SAP logistics menu, send an email by outlook and navigate to Google and to SCN.

Block 3: added gifs in menu area with different functionalities: navigate to gmail, to SAP business workplace, to SPRO,
to Google and to SAP help portal, execute: SAP logistics menu, SAP financial menu, SAP workbench menu, SAP systems menu and SAP general menu.

Block 4 and Block 5: added a specific icon by client and descriptive text displayed in title bar on status bar to distinguish visually the client and transaction we’re working with. This will help to avoid committing mistakes when working with different clients and sessions in a smart way. Icon is only displayed in status bar.

Of course you’ll be able to add/remove pushbuttons, gifs and icons and adjust functionalities as you like after reading this document.

Interested?

Great, that means you’ll keep reading this document...

Steps

1-Create the following directory: C:\guixt\scripts. This is where our scripts will be stored by default. A script is a file that contains sentences to execute things. We don’t need to have programming skills for this script.

2- Open notepad editor, copy & paste the script at the end of the document and save it as  saplsmtr_navigation.0100.txt in C:\guixt\scripts and close it.

3-Icon and gifs. Download from http://ge.tt/1ngALYy to C:\guixt\scripts (download available for next 30 days). Alternatively you can create/use your own (change name of them in script if needed).

4- Activate GuiXT in our laptop & desktop. By doing so, script will be executed when creating a new session or after new login. This script is run locally in our laptop/desktop.

5- Test & Enjoy

Activating/Deactivating GuiXT

We need to use GuiXT, software developed by Synactive and available for free, with limited functionality. To use it, we need to activate it locally in our desktop/laptop.

To activate/deactivate, just click on customize local layout icon and click on Activate:

Once activated, minimize Guixt screen and at the bottom of our screen, a GuiXT icon becomes available

Now we click on GuiXT icon and select Edit, Profile and tic on No language key in script name in further options block. In that way, the scripts we create are non language dependant. We click on Ok button and minimize GuiXT screen.

Log out from SAP. Next time you log in, you should notice changes in your screen...But before, let’s keep reading.

Understanding this script

You can comment any sentence by setting at the beginning of it these two symbols \\ and it won’t be executed.

The script is divided into blocks that correspond with the blocks shown in the screenshot at the beginning of the document for better understanding.

Block 1: sentences executed here are similar of those executed in command field.

Block 2: sentences with start means that when clicking on a image (gif) system will start execute something (navigation on internet, execution of an executable...) when sentence starts with Input, is similar to using command field but thru an image.

You need to adjust the sentence mailto and set proper TO email.

Block 3: same as Block 2. Sentence POS will shift SAP menu downwards 2 lines.

Block 4 & 5: according to client number, we use a specific icon and a text that contains two system variables (_client and _transaction).

You need to replace client number by yours.

It’s not the goal of this document explain in detail syntax of the sentences in the script. You can find in Internet GuiXT documentation on syntax and keywords for further details.

Logon and test it

Log on and your screen should have a new look. Try different functionalities. If you want to know which functionally has every image, just click on GuiXT button and read the script we’ve copied and once done, minimize GuiXT screen (if you close it by mistake, you’ll have to logout and login).

If no GuiXT is displayed, check directory and script names and if GuiXT is activated.

Errors

If GuiXT icon is red

it means that there is an error in our script. If this happens, we click on GuiXT icon and a GuiXT window will open, containing our script and showing the error. We click on Edit, Script and notepad opens the script for us to modify.

Once we correct the sentence, we can save (file, save) and exit editor (file, exit) and finally minimize GuiXT screen. We open a new session to check the results (GuiXT icon in this new session should not be red, otherwise there’s still an issue and we have to repeat the process of editing the script and looking for the issue). This process (clicking in the GuiXT icon and edit & save & exit notepad) can also be used to update the script on the fly and see the results immediately. Remember to close editor (not GuiXT! If you close it, you’ll need to logout and logon) if you’re modifying on the fly to avoid having several scripts opened simultaneously with the risk of overwriting the script depending on the order you’ll close them.

Graphics

In block 1, SAP icons can be found with tcode RSTXICON (select Icons as Abap list and use values in column code. In the script the value must be between @’s).

In block 2 and 3 we can use images with extension bmp, gif or jpg. Size of gifs used in block 2 must be 18x18, while for block 3, they can we bigger, I used 34x34.

In block 4 we must use images with extension ico. Size I used is 32x32.

Gifs and icons come from free to use websites or created by myself.

Finally

To avoid someone updating the script, once it works fine, we can hide GuiXT icon. To do it, we click on GuiXT icon and select Edit,
Profile:

And in start window, select Hidden instead of normal.

If you need GuiXT icon back, execute guixt.exe visible in C:\Program Files\SAP\FrontEnd\SAPgui. It will be visible till you log off. If you want it visible permanently, update the profile and in start window area set normal.

Stop using GuiXT

If you decide to stop using GuiXT, deactivate Sap GuiXT as we saw at the beginning of the document. If you don’t want to use a script, rename or delete it.

Script. Copy & paste below sentences and change client number and mailto email as explained in step 2

//

// Start script

//

// Block 1

pushbutton (toolbar) "@VB@bye bye" "/nend"

pushbutton (toolbar) "@OJ@SPRO" "/ospro"

// Block 2 in tool bar gif size 18x18

image (toolbar) "C:\GuiXT\Scripts\jscn_18x18_1.gif" Start="http://scn.sap.com/welcome\"

image (toolbar) "C:\GuiXT\Scripts\google18x18.gif"   Start="http:\\www.google.com\"

image (toolbar) "c:\guixt\scripts\mail_18x18_1.gif"     start="mailto:xx@xx.com?subject=Some issues in system &V[_client]&body=Hello, "

image (toolbar) "C:\GuiXT\Scripts\menu18x18_log.gif" "Input=OK:/ns000_lo"

image (toolbar) "C:\GuiXT\Scripts\menu18x18.gif"    "Input=OK:/ns000"

image (toolbar) "C:\GuiXT\Scripts\word18x18.gif"      Start="C:\Program Files\Microsoft Office\Office12\winword.exe"

image (toolbar) "C:\GuiXT\Scripts\maps18x18.gif"     Start="http:\\maps.google.com\"

image (toolbar) "C:\GuiXT\Scripts\weather18x18.gif" Start="http://www.accuweather.com/"

// Block 3 in Menu Area gif size 34x34 Images horizontal

pos X[image_container] X[image_container]+(2,0)

image (0.1,0.1) (1,3)  "C:\GuiXT\Scripts\gmail234x34.gif"       Start="http:\\www.gmail.com\"

image (0.1,5.1) (1,8)  "C:\GuiXT\Scripts\sms34x34.gif"           "Input=OK:sbwp"

image (0.1,10.1) (1,13) "C:\GuiXT\Scripts\custo34x34.gif"      "Input=OK:spro"

image (0.1,15.1) (1,18) "C:\GuiXT\Scripts\google34x34.gif"     Start="http:\\www.google.com\"

image (0.1,20.1) (1,23) "C:\GuiXT\Scripts\sap34x34.gif"          Start="http:\\help.sap.com\"

image (0.1,25.1) (1,28) "C:\GuiXT\Scripts\Logistics34x34.gif" "Input=OK:s000_lo"

image (0.1,30.1) (1,33) "C:\GuiXT\Scripts\Finance34x34.gif"   "Input=OK:s000_fi"

image (0.1,35.1) (1,38) "C:\GuiXT\Scripts\Workbench34X34.gif" "Input=OK:s001"

image (0.1,40.1) (1,43) "C:\GuiXT\Scripts\System34x34.gif"    "Input=OK:s002"

image (0.1,45.1) (1,48) "C:\GuiXT\Scripts\General34x34.gif"   "Input=OK:s000"

// Block 3.A in Menu Area gif size 18x18 Images vertical

//pos X[image_container] X[image_container]+(0,5)

//image (0,0) "C:\GuiXT\Scripts\gmail18x18Alt.gif"     Start="http:\\www.gmail.com\"

//image (1,0) "C:\GuiXT\Scripts\sms18x18Alt.gif"       "Input=OK:sbwp"

//image (2,0) "C:\GuiXT\Scripts\custo18x18Alt.gif"     "Input=OK:spro"

//image (3,0) "C:\GuiXT\Scripts\google18x18Alt.gif"    Start="http:\\www.google.com\"

//image (4,0) "C:\GuiXT\Scripts\sap18x18Alt.gif"         Start="http:\\help.sap.com\"

//image (5,0) "C:\GuiXT\Scripts\Logistics18x18Alt.gif" "Input=OK:s000_lo"

//image (6,0) "C:\GuiXT\Scripts\Finance18x18Alt.gif"   "Input=OK:s000_fi"

//image (7,0) "C:\GuiXT\Scripts\Workbench18X18Alt.gif" "Input=OK:s001"

//image (8,0) "C:\GuiXT\Scripts\System18x18Alt.gif"    "Input=OK:s002"

//image (9,0) "C:\GuiXT\Scripts\General18x18Alt.gif"   "Input=OK:s000"

// Block 4 & 5

SET V[var1] "&"

if Q[client=500]

Icon "C:\guixt\scripts\social_aim.ico"

TitlePrefix "Client IDES &[_client]:&V[var1]V[_transaction]"

endif

// Adjust yourself for rest of your clients by removing // and using client and proper icon name 

// if Q[client=xxx]

// Icon "C:\GuiXT\Scripts\social_evernote.ico"

// TitlePrefix "Client IDES &[_client]:&V[var1]V[_transaction]"

// endif

// if Q[client=xxx]

// Icon "C:\GuiXT\Scripts\social_twitter_bird.ico"

// TitlePrefix "Client IDES &[_client]:&V[var1]V[_transaction]"

// endif

// if Q[client=xxx]

// Icon "C:\GuiXT\Scripts\social_apple.ico"

// TitlePrefix "Client IDES &[_client]:&V[var1]V[_transaction]"

// endif

// End script

A variant

You might prefer not having menu shifted downwards. We can set icons vertically on left side and shift menu rightwards. In that case, I recommend reduce size from 34x34 to 18x18 or less.

The only thing that we have to do is modify our script, commenting (//) block 3 and un-commenting block 3.A.

Last comment

You’ll notice that when creating a new session, added gifs in application bar shift leftwards. Opening a menu or executing a tcode in command field will set them to their original place.

Enjoy!

Regards,

JM