Within SAP NetWeaver 2004s BI, we can still use the traditional BW 3.x Frontend tools. In addition, we have new frontend tools available within the 2004s version. As there are multiple tools, we need to be cognizant of the supported versions of the client side software. Below, you will see links that show the supported internet browsers, operating systems, and Microsoft Office versions that the SAP BEx tools support.
This BLOG will discuss how to configure your browser parameters as well as discuss how to install the latest SAP NetWeaver 2004s BI Frontend Components. Keep in mind that it is always best to keep your frontend patches up to do date.
This is for SAP NetWeaver 2004s SPS8 or greater.
Setting up Internet Explorer 6.0
One of the first things to do if you have a browser issue is to clear all temporary files, cookies, and offline content from your browser cache.
If youre using Microsoft Internet Explorer, there are number of issues you may run into with the portal and frontend if you dont have your browser settings configured appropriately. To use the Web Analyzer or any functionality involving the SAP NetWeaver Portal, make sure you have your browser setup correctly.
I highly recommend updating to the latest support package of Internet Explorer (as of this article being written, that would be SP2). For sake of simplicity, Im going to focus on Internet Explorer 6.0 SP2 or greater. Previous releases have numerous issues and there are numerous hotfixes that apply. If youre using previous versions, see Microsofts knowledge base article at: http://support.microsoft.com/kb/827667/.
One of the common things that I would also suggest checking is that your proxy information is setup correctly within your Internet Explorer connection settings. I know this is low hanging fruit, but it is very important.
Within Internet Explorer, you should make sure that you add your SAP NetWeaver Portal and BI systems to the list of trusted sites within Internet Explorer. This is available through the Tools -> Internet Options -> Security -> Trusted Sites -> Sites area.
Within Internet Explorer, you should make sure that you add your SAP NetWeaver Portal and BI systems to the list of sites that are NOT blocked by the popup blocker. This is available through the Tools -> Internet Options -> Privacy -> Popup Blocker Settings
Within Internet Explorer, you should check your advanced tab settings.
If youre having issues with IE such that it wont decompress HTTP Content on IE 6 SP2. Ensure that your wininet.dll file is at the following version for IE 6 SP2.
10-Jun-2005 01:38 6.0.2900.2695 658,944 Wininet.dll
If it is not, see this Microsoft hotfix page
for a resolution to this issue.
One other thing to ensure that if you have any 3rd party popup blockers within Internet Explorer, such as Google Toolbar, Yahoo Toolbar, etc , make sure you disable the popup blocking or allow popups from the SAP systems domain.
Next, add your local domain to your trusted sites in Internet Explorer. If you cant add the entire domain, add the ABAP and JAVA systems manually.
In addition, you need the latest version of the mshtml.dll version for Windows XP SP2. This is mentioned and available in this microsoft hotfix: http://support.microsoft.com/kb/917425.
Setting up Internet Explorer 7.0
Internet Explorer 7.0 is supported for NetWeaver as of SPS10.
Setting up Mozilla Firefox
I typically recommend keeping your Mozilla Firefox browser up to date. Currently, Mozilla Firefox 22.214.171.124 has no known issues where hotfixes need to be applied.
Clear Cache if youre having issues.
Make sure that your proxy is defined for Mozilla Firefox.
Make sure you setup your BI and Portal system as Allowed to create cookies.
Make sure you setup your BI and Portal system as not blocked by the popup blocker.
To date, I have not had any client issues with Mozilla Firefox 126.96.36.199, although the Visual Composer Design Time only works with Internet Explorer.
Installing Latest Version of .NET 1.1 framework
Download and install the latest version of Microsoft .NET Framework 1.1. Currently, there is a version 2.0 available, but 1.1 is required. See OSS note 877774 for details.
Keep in mind this must be installed BEFORE SAPGUI or the BI Addon is installed.
Install Microsoft Visual J# .NET
This is a new Prerequisite (Note 964495): You need have installed “Microsoft Visual J# .NET Version 1.1 Redistributable Package”
Installing SAPGUI Client
To use the BEx Toolset, you will need to install the SAPGUI Client software. In general, you will need to download the following files. Keep in mind that as newer versions of the SAPGUI files become available, it is recommended to keep these up to date.
The first step is to download files. For sake of simplicity, Im going to talk about a completely new install. I do recommend that to ensure you have a clean install and all your SAPGUI files up to date, a clean install is the best option.
1. Go to Control Panel and remove SAPGUI. Uninstall all your SAP Frontend Components (Control Panel -> Add or Remove Programs -> SAP Front End)
2. The first step is to download the SAP Frontend Installer. Available at:
-> Installations and Upgrades
-> Entry by Application Group
-> SAP Frontend Components
-> SAP GUI FOR WINDOWS
-> SAP GUI FOR WINDOWS 6.40
-> NW 2004s SR1 Presentation – 6.40 Compilation 5 Present. 1/3
You only need this one file for SAPGUI BI components As of today (6/26/06), this is the latest file:
3. Extract the downloaded file to C:\SAPGUI_INSTALL\
4. Run Sapsweep to delete any frontend dlls or other components that are on this frontend machine.
5. Launch Microsoft Excel and run Help -> Detect and Repair to remove any references to SAP Addins.
6. Run Setup from C:\SAPGUI_INSTALL\DVD_NW_2004s_SR1_Presentation\PRES1\GUI\WINDOWS\WIN32\setup.exe Make sure you choose ALL components to install (including all addons). If you dont want to install all components, make sure you choose BI Addon, BW Addon, and SAPGUI as a minimum.
Update SAPGUI Client to latest patches
1. Download these files: Make sure you save the patch files as .exe files.
-> Support Packages and Patches
-> Entry by Application Group
-> SAP Frontend Components
-> SAP GUI for Windows 6.40
-> SAP GUI for Windows 6.40
Latest Patches for:
SAPsetup for SAP GUI 6.40
Currently, this is setup23 located at:
SAP GUI for Windows 6.40 Patch
Currently, this is patch21 located at:
SAP BW 3.5 AddOn Patch
Currently, this is BW 3.5 Patch 11 located at:
SAP Netweaver 2004s BI AddOn Patch
Currently this is SAP NetWeaver 2004s BI FEP 904 located at:
5. Run SAPsetup for SAP GUI 6.40
6. Run SAP GUI for Windows 6.40 Patch
7. Run SAP BW 3.5 AddOn Patch
8. Run SAP Netweaver 2004s BI AddOn Patch
Installing MSXML Parser
The latest version of Microsoft XML Parser should be installed. MSXML parser comes installed on Windows XP machines, but if youre using a prior operating system, you may need to install it. Also, you should make sure the version you are using is up to date. MSXML Parser is required for Visual Composer designtime.
Currently, the latest version is MSXML Parser 6.0 which is located at:
Installing Adobe SVG Viewer
Download and run Adobe SVG Viewer 3.0 http://www.adobe.com/support/downloads/product.jsp?product=46&platform=Windows Adobe SVG Viewer is required for all users that will use the Visual Composer Designtime. It is not required for any runtime users or for any other BEx tools (at least it isnt required yet )
Installing Adobe Flash Player
Download and Install Adobe Flash Player (v7.0+) – plug in for Internet Explorer 6.0 Adobe Flash Player is required for Visual Composer (both designtime and runtime). This is located at:
Ensure that the BExAnalyzer Application has authority to create dll’s in the user’s temp folder
If you have a viruscanner or DLL Creation blocking, make sure you allow the BExAnalyzer the authorization to create temporary DLLs as this occurs when the BEx Analyzer is launched. The dlls are generated from the .NET xml serialization framework and are only persistent while the application is running. These are deleted when the application is closed.
Verify SAPGUI Settings for BI
In excel, go to Tools -> Macro -> Security -> Trusted Publishers Verify the SAP AG certificate and make sure Trust Access to Visual Basic Project and Trust all installed addins and templates are checked.
Run C:\Program Files\SAP\FrontEnd\Bw\sapbexc350.xla and ensure there are no red files
Run C:\Program Files\SAP\FrontEnd\Bw\sapbexc700.xla and ensure there are no red files
Server Side Settings
Step 1 Ensure that your ABAP and JAVA systems are on the same fully qualified domain name. There are numerous cross-domain issues that could occur. Also, ensure that all communication server side is using the fully qualified domain name.
Step 2 You may be missing style elements which could cause incorrect rendering. If you are still having issues, try switching to an SAP Delivered Theme instead of Custom Theme on the Portal.
Keep in mind that this blog and the components are as of 7/26/06