Skip to Content
SAP Visual Business

HowTo setup Visual Business Native Client


Native Client installation

The native ActiveX client for Visual Business is shipped as a standard SAPSetup Installer, which can be downloaded from the SAP Service Market Place. The setup program will install the 32bit and 64bit (VB 2.x only) version of the control in parallel. After installation you will find program sapvbgui.exe on the client machine. You can run it as a first check for an successful installation.

Usage scenarios

The native Visual Business control can be used in multiple ways. The possibilities may vary depending on the release and installed software components of the ABAP backend. Here are some options:

Visual Business VersionUI Technologymin. Backend requiredTest applicationWrapper
1.1WebDynpro / FPMSAP_BS_FND 7.02 SP06FPM application VBC_GEOMAP_GENACF
2.0WebDynpro / FPMSAP_BS_FND 7.31 SP04FPM application VBC_GEOMAP_GEN2ACF
2.0WebDynpro ChipSAP_BS_FND 7.31 SP08FPM application VBC_GEOMAP_CHIP_TESTACF
2.1SAPGUIUI Ext. AddOn 1.0 for NW 7.00 SP05ABAP report VBI_GUI_TEST-
2.1WebDynproUI Ext. AddOn 1.0 for NW 7.02 SP05WD application VBI_WD_TESTACF
2.1WebDynpro ChipUI Ext. AddOn 1.0 for NW 7.02 SP05



2.1FPMSAP_UI 7.40 SP04HTML Island

ACF related setup

The ACF wrapper control for ActiveX components in WebDynpro is automatically installed from the backend upon first use. For this installation on the client PC must be possible. Alternatively you can download the installer from the SAP Service Market Place and install it upfront.

Whitelist installation

Visual Business 1.1 is based on Microsoft .Net and requires no further setup for ACF.

Visual Business 2.x is a native ActiveX control and requires a suitable ACF whitelist to be installed on the client. An ACF whitelist is client dependent customizing in the ABAP backend. The delivery customizing for Visual Business includes a whitelist VB200 for VB 2.0 and VB210 for VB 2.1.

With transaction ACF_WHITELIST_SETUP you can select the suitable whitelist and download a related certificate to the client PC. This needs to be done for each system/client combination you want to use with Visual Business! The certificate name will be stored in the user directory under ./AppData/Roaming/SAP and follows the naming convention SAPFrontendService<SystemID>CLNT<Client><CertID>.cer.

If you do not find one of the whitelists mentioned above you need either to copy the delivery customizing from client 000 or you create a new whitelist with transaction WDR_ACF_WLIST. Just enter the suitable name (VB200 or VB210) and save the whitelist.

The whitelist certificate handling in general is described in all detail in note 1706291. This note mentions especially the required installation of SAPCryptolib in the system. If the certificate is not working this lib might be missing. Note 800240 explains how the availability of the lib can be checked.


If the ACF control does not find a valid whitelist certificate for the Visual Business control it usually shows a blue area with the text "SAPACF control". Further it opens a ACF Trace window with error messages. If the trace window does not open or shows too less information you can set the tracelevel in the backend by making an entry in either VBCD_ACF_TRACELV (VB 2.0) or VBID_ACF_TRACELV (VB 2.1) using transaction SE16.

The trace show error messages like:

  • Could not open file C:\Users\<user>\AppData\Roaming\SAP\SAPFrontendService<SystemID>CLNT<Client><CertID>.cer
  • put_innerClassId|ClassId {00100000-2011-0070-2000-FC7214A1CD7B} not an allowed InnerClass

  • ...

which gives more inside into the actual cause.

Client PC requirements

Based on the used technology the Visual Business Control is limited to the Microsoft Windows platform.

The Visual Business 1.1 version is based on .Net 3.51 and runs on Windows XP and later. It requires a DirectX 9 compatible graphics device.

Version 2.x of Visual Business requires a DirectX 10.1 compatible graphics device, which leads to Microsoft Vista as minimum OS requirement.

Troubleshoot display issues

If you experience issues with the rendering of the Visual Business control, such as black background, very raw edges, false colors, or even crashes, you should check if there is an update for the graphics device driver. Usually you should not rely on the Windows Update for this, but check directly on the vendor site of either the graphics device or the PC/laptop. If this does not solve the issue you may force Visual Business to drop hardware accelerated rendering and use software rendering for maximum compatibility. To do so add environment variable WDRENDERMODE with value WARP in the system administration.

Troubleshoot network issues

The Visual Business control retrieves the maps data directly from the internet based on the given map configuration from the backend. Thus if you see objects, but no map in the background, you have network issues. There are various possible reasons:

  • Wrong map provider URLs in the backend configuration
  • Missing/wrong proxy setting
  • Visual Business does not detect proxy settings

The most reliable way to troubleshoot network issues is to install Fiddler. This free tool will establish a local HTTP/HTTPS proxy on the client PC allowing to trace the complete network communication of the Visual Business control. In the Fiddler trace you see the URLs called and the related HTTP status. This gives you inside whether the URLs are wrong or a proxy is missing.

If it is not possible to install Fiddler on the client machine you can try the build in trace. In order to enable this feature you have first set a flag per user in the backend. Call transaction SE16 and load table VBID_CLNT_TRACE. Proceed with Execute(F8) on the selection screen to see all existing entries. If there is no entriy for your user on the relevant client than create a new one. Otherwise mark the existing entry and select change(F6). Set the field VBI_CLIENT_TRACE to true (X) and save your changes.

Now run the application. Hold down Ctrl+Alt key and right click the control. This should open the Visual Business Properties dialog window. Only if tracing is enable from the backend you can choose tab Trace. There you flag trace component Network and close the dialog with OK.

Move and zoom the map in order to trigger map update requests. Open the properties dialog again and choose View Trace on the Trace tab. Now you should see the requested URLs with a request ID and the request result for a certain ID in a later trace entry.

In order to see not just the URLs and the request result, but also the response data, you have to choose Trace Level HEX.

No comments