Top 13 Sap Gui Interview Questions You Must Prepare 19.May.2024

For activating, a user goes to transaction SE41, it is important to first select the Function Code itself and uses F7 (Extras > Function Active <-> Inactive).
Post-activation and saving, the Function Code will work as desired and expected.

If the additional error text indicates, that the library is missing, the user should try to solve the problem by reinstalling SAP GUI for Java. In other cases, please check document 909250, mostly in cases, the required C++ runtime is not found.

Start SAP Logon Right-click the SAP Logon icon in the task bar and choose "ABOUT". Note the file version displayed – XXXX.Y.ZZZ.WWWW. The first four digits (XXXX) represent the SAP GUI version (6100 = 6.10, 4640 = 46D). The second section of digits (Y) represents the compilation number of the SAP GUI. The next three digits (ZZZ) are the patch level of the SAP GUI. The last digits (WWWW) contain the build number.

  • By enabling the option to display the keys in the SAP GUI affects any app launched from the Fiori Launchpad which calls a transaction against the WebGUI (SAP GUI for HTML).
  • There is no option to show keys by default, for Web Dynpro or native Fiori apps.
  • Developers of native apps can opt to select to provide customization for field labels on a per-app basis; however, there is no global option available for this.

The SAP frontend installation guide (mat nr. 51010215) has excellent information on how to install and patch the SAP GUI, see 361222 for additional information about this. Both of these contain information about deploying the patch using the SAP installation server.

Sometimes it may be wise to patch a single workstation first to see whether the patch actually solves the current issue. In the following we describe how to patch a single workstation, depending on the GUI version/release:

On 46D:

  1. From SAPSERV3 or SAPNET, download the frontend patch and the localpat_46d.exe file, please note that you need both files!
  2. On the workstation, run the localpat_46d.exe file, this will then extract to a NETINST directory.
  3. Start a DOS prompt (or command prompt)
  4. Change directory to the NETINST directory under SAPPC
  5. Execute SAPSETUP /PATCH
  6. In the SAPSETUP application, browse for the SAP GUI patch and choose install.

On 6.10:

  1. Download the latest frontend patch
  3. Browse to the downloaded EXE file containing the SAP GUI patch
  4. Click OK
  5. Wait while the patch extracts
  6. Click Install

As of 6.20:

  1. Download the latest frontend patch
  2. Choose Control Panel - Add/remove programs - Sap Frontend - Change - Apply a SAP Frontend Patch
  3. Browse to the downloaded EXE file containing the SAP GUI patch
  4. Click OK
  5. Wait while the patch extracts
  6. Click Install The SAP GUI (all releases) can only be patched, when the GUI, or components used by the GUI is not running, so please close all sessions, SAP Logon, Outlook, and so on (in general close all programs running) prior to installing the patch. For further information please review also the GUI specific help. Choose the three-colored GUI icon, and select then the 'SAP GUI Help' menu.

You might come across the problem that the patch tool cancels the application of the SAP GUI patch. The reason is that some files might be in use. Just restart the machine and start again. Make sure, that no SAP GUI is currently running during the patch procedure.

In order to SAPGUI transactions in full size following changes have to be made:

  • User Logins into CRM System.
  • Goes to Transaction SE3@
  • User selects the function module LTX_CREATE SAP GUI SHORTCUT.
  • Goes to the Import parameters tab.
  • Selects the field IS WINDOW SIZE.
  • Assigned default value= 'MAXIMIZED'.
  • User Clicks on Save.

SAP BI4.0 installation on UNIX/LINUX doesn’t need SAP GUI.

All components which are essential for the Connectivity to SAP Systems are provided as a part of the core Installation package for SAP BI4.0.

For legacy (CR 2011) CR designer, the SAP GUI (with specific options selected) is needed for using the SAP toolbar (meant for the purpose of saving reports to BW), however as CR 2011 Designer is a Windows-based product, this requirement is not applicable for installations on UNIX as well as Linux installations.

The official download site for patches for the SAP GUI for Windows and the SAP GUI for Windows installation is the "Software Center" on the "SAP Service Marketplace": (password is required). In the right-hand frame choose "SAP GUI for Windows" -> "SAP GUI for Windows " -> "Win32". You can either download a patch by clicking the link "GUI.EXE" (e.g. "GUI46D.EXE") or using the download manager. The patch level of this patch is displayed in the column "Patch Level". APO, BW, KW and SEM users also will find patches for the corresponding Frontend Add-ons of these components in this section.

The upgrade is scheduled for November 29 - December 9, 201@Dates for the roll-out will appear in Take5 and Newsline two weeks prior to the upgrade, and you will be contacted by your computer support representative. The night prior to your scheduled upgrade you will need to make sure to leave your PC on for the upgrade to take place.

In order to change default download directory from SAP GUI user need to change default path in the setting of below registry:

[HKEY_LOCAL_MACHINE Software SAPSAP Shared] on 32-bit operating systems

[HKEY_LOCAL_MACHINE Software Wow6432NodeSAPSAP Shared] on 64bit operating systems

Key: SapWorkDir

Type: Expandable String Value

Value: The path you want to change

Note: Using the Registry Editor incorrectly can lead to serious issues; therefore, use the Registry Editor at your own risk.

  1. Initially, the user closes all the SAPGUI sessions/screens
  2. Opens SAPGUI and runs the transaction for displaying application where he wants to verify if SAPHTML control is utilized or not.

Now user needs to navigate Customize Local Layout (ALT + F12) ---> about... ---> Loaded DLLs ----> Clicks on fist item and types SAPHTML.
If the user finds "SAPHTML.ocx" then SAPHTML control has been used.

The upgrade is taking place in order to increase security and to support the SAP upgrade to ECC 6.0.