SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 1

Frequently Asked Questions - SAP

NetWeaver Business Client

Applies to:

SAP NetWeaver Business Client (all versions).

Summary

Frequently Asked Questions

Author: Julie Plummer

Company: SAP AG

Created on: 17 October 2012

Author Bio

I am currently Product Manager for SAP NetWeaver Business Client.I have been involved in NW UI topics since 2005, having joined SAP in 1998.Previously, I provided Technical Support for Adobe for 4 years.I graduated in 1992 with a BA Hons in Languages for Interpreting and Translation; and gained a postgraduate Diploma in Business Administration in 1994.

Frequently Asked Questions - SAP NetWeaver Business Client

SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 2

Table of Contents

General ............................................................................................................................................................... 3

Authentication ................................................................................................................................................. 3

Compatibility .................................................................................................................................................... 3

Documentation ................................................................................................................................................ 3

Performance .................................................................................................................................................... 3

Personalization ................................................................................................................................................ 4

Positioning: NWBC vs SAP GUI vs Portal ...................................................................................................... 5

Positioning : Desktop vs HTML client ............................................................................................................. 5

Programming Aspects ..................................................................................................................................... 6

Roles (PFCG) .................................................................................................................................................. 6

System Connections ....................................................................................................................................... 6

Integration ........................................................................................................................................................... 8

Adobe Reader ................................................................................................................................................. 8

Business Server Pages (BSPs) ...................................................................................................................... 8

Business Suite: CRM ...................................................................................................................................... 8

Business Suite: ESS/MSS .............................................................................................................................. 9

Business Suite: Side Panel ............................................................................................................................. 9

Business Suite: SRM ...................................................................................................................................... 9

Business Suite: Web Dynpro ABAP-based Applications ................................................................................ 9

HTML5........................................................................................................................................................... 10

IBM WebSphere/ Microsoft Sharepoint ......................................................................................................... 10

Microsoft Silverlight ....................................................................................................................................... 10

SAP NetWeaver Portal .................................................................................................................................. 10

Third-Party Content ....................................................................................................................................... 11

Related Content ................................................................................................................................................ 11

Copyright ........................................................................................................................................................... 12

Frequently Asked Questions - SAP NetWeaver Business Client

SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 3

SAP NetWeaver Business Client : Frequently Asked Questions

General

Authentication

Q: How does the SAP GUI protocol recognize the NWBC web logon (in PFCG mode)?

A: NWBC uses HTTP to contact the ABAP system, which then sends back a MYSAPSS02 cookie. This is then used to talk to the ABAP system. This should be in the documentation – See SAP Lbrary : 7.1 NWBC and Authentication

Compatibility

Q: Are NWBC 3.5 and 4.0 downwards compatible?

A: Yes, NWBC 3.0, 3.5 and 4.0 can connect to all backends from NW 7.00 SP21, NW 7.01 SP06 onwards. This means that end users can connect to any system with this release or highrer. However, some features require a higher release- such as Side Panel, which requires ECC6.0, EHP6.

Documentation

NWBC 3.5 NWBC 4.0

Main SAP Notes for NWBC requirements are: 1029940 SAP NetWeaver Business Client Requirements and Restrictions 1620514 NWBC 3.5 for Desktop: Requirements and Restrictions 1620576 NWBC 3.5 for HTML: Requirements and Restrictions

Performance

Q: Can NWBC manage over 10,000 users?

A: Yes, see the section in the documentation on the performance profile for NWBC: SAP Library : 8

Performance Aspects

Q: What are the performance characteristics / bandwidth requirements for NWBC?

A: This is explained in detail in the documentation, in chapter 8 on Performance Aspects and in subchapters.

Q: Does NWBC support load balancing?

A: You could place a reverse proxy in front of your application servers to spread the load, and allow you to later dynamically consider additional servers. Or start NWBC for Desktop (!) via the message server to automatically lock onto the least busy application server. This is described in detail in the documentation. SAP Library : 3.6 Using NWBC with a Load Balancer

Q: What sort of overhead is there that might affect performance?

A: The performance and overhead footprint of all applications running within NWBC are still the same as if they would run standalone. The question is what additional overhead does NWBC add?

Frequently Asked Questions - SAP NetWeaver Business Client

SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 4

NWBC for Desktop: It accesses the server only once during startup to authenticate the user and then to verify that the navigation tree in its cache is still valid. In the usual case, two HTTP requests are all that are needed once a day for NWBC for Desktop (extra features, such as searching for transactions, does add additional requests to the server, but these should be the norm on a shop floor). NWBC for HTML: The server renders the shell. Each interaction with the shell, for example starting a new application, results in a small amount of network overhead to get a new shell rendered from the ABAP server, plus of course the ABAP session. ABAP runtime: The client fires a set of HTTP requests to the server. For the desktop client, it is the sequence of requests to validate its cache. For the HTML shell it is the series of requests to trigger the navigation. The ABAP runtime becomes stateful (keeps the ABAP session) for 15-30 seconds, before the session is cleared again. As such, the overhead is very little on ABAP. (Keep in mind that the desktop client only calls once on startup.) In addition, with the v3.5 ABAP runtime (NW7.03+), we have added in memory objects to cache complex role operations, which will dramatically speed up the HTML shell’s performance if this is preferred.

Q: What are the performance requirements for VPN-/MPLS connections using NWBC 3.0 or the portal.?

A: The NWBC client requirements are similar to normal applications. Initially, NWBC for desktop loads the navigation tree and caches it on the client. After caching the network traffic is the same as when an application is run in standalone mode.

By default, NWBC for desktop uses SAP GUI for Windows instead of SAP GUI for HTML.

Personalization

Q Can I change the work center/service map icons?

Yes.

In both 3.5 and 4.0, you can change the Work Center/ Service Map icons in Role Maintenance (PFCG): SAP Library: 5.5 Navigation Tree (scroll down to “Other Node Details).

In 3.5, you can also change Work Center icons by right-clicking the tab. See SAP Library : 2.3 Navigation

. (This is no longer relevant in 4.0).

Q: Can I add custom icons to the work center/service map?

A: No

Q: In NWBC 4.0, can I change the welcome message?

The message on the Index page can be replaced by a different text, even with parameters.

Use parameter WELCOME_MESSAGE in the backend configuration table NWBC_CFG. See also SAP Library: 4.6 Configuration in Table NWBC_CFG

Q: If an end user makes personalization changes in NWBC are they valid for his or her user ID or for his or her local installation?

A: All changes stored locally on a user’s PC (for example reordering of work centers / icons for work centers / hide some work centers / font changes/ etc) do not work on another PC.

All changes within canvas applications are stored on the server and would work on another computer.

Personalization: Options are stored locally and are Windows-user specific. The sequence of the work centers and the icons are even stored per connection and per user accessing the connection.

Frequently Asked Questions - SAP NetWeaver Business Client

SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 5

Positioning: NWBC vs SAP GUI vs Portal

Q: In what situations would you recommend NWBC over SAP GUI?

A: NWBC is of particular interest to customers familiar with SAP GUI who also want to work with the new Web Dynpro ABAP screens within one unified environment. NWBC supports role-based navigation so that the end user sees those applications that are relevant to his or her role.

Q: Does NWBC share technology with SAP GUI?

A: Yes, SAP GUI for Windows is also installed with NWBC since end users want to work with the traditional SAP GUI screens as well as with Web Dynpro applications.

Q: Will NWBC typically be co-deployed with SAP GUI, as a complementary technology?

A: Generally NWBC and SAP GUI will be installed together although they can be installed separately.

Q: Are there plans to align more closely in future, or merge roadmaps?

Yes. The next versions of NWBC and SAP GUI will be released jointly as one product.

Q: When is NWBC expected to become the ‘go to’ desktop client? Will we start to phase out SAP GUI? If so, when?

A: NWBC 3.0 is the “go-to” desktop client and is being rolled out externally. You can check the relevant EHPs in the Product Availability Matrix on the Service Marketplace. NWBC does not replace SAP GUI because it uses SAP GUI to display the traditional SAP GUI screens.

Q: In what situations would you recommend NWBC over the portal?

A: NWBC is most suited to the needs of the power user, that is, someone concentrating on transactions processing a large amount of data in an ABAP-centric system landscape. A typical example would be a payroll clerk. NWBC is of particular interest to customers familiar with SAP GUI who also want to work with the new Web Dynpro ABAP screens within one unified environment.

Q: In what situations would you recommend the portal over NWBC?

A: The portal is most suited to users working with a variety of systems (SAP and non-SAP) often in different locations; or for customers who want to integrate Mobile and Cloud solutions. A typical example would be a Product Manager. The other strengths of the portal include collaboration, document management and branding.

Q: I have Microsoft Sharepoint/ IBM WebSphere. Should I use SAP Enterprise Portal or SAP NetWeaver Business Client in conjunction with these?

A: Both SAP Enterprise Portal and SAP NetWeaver Business Client (HTML Client) work with Microsoft Sharepoint or IBM WebSphere. Which one you use depends on your other requirements – see above. To integrate NWBC with either Microsoft Sharepoint or IBM WebSphere, see the following documentation: 9.1 How To Integrate NWBC into a Microsoft SharePoint Portal 9.2 How to Integrate NWBC into an IBM WebSphere Portal

Positioning : Desktop vs HTML client

What are the benefits of NWBC (HTML)?

Access to ABAP systems Zero footprint Use case for NWBC (HTML):

Frequently Asked Questions - SAP NetWeaver Business Client

SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 6

Extranet: eg Volkswagen runs SAP. Its component suppliers do not, necessarily. They can use NWBC for HTML To access (parts of) VW's ABAP-based systems.

Q: What are the main differences between the HTML NWBC and the desktop NWBC?

Desktop NWBC performance is better, how much better depends on number of work centers, size of navigation tree, which browser is used, and the power of the PC

HTML NWBC uses SAP GUI for HTML; desktop NWBC uses SAP GUI for Windows

HTML NWBC has no overflow, no D+D of work centers, no search

All-in-One uses the desktop NWBC

HTML NWBC does NOT use the portal, only ABAP systems

HTML NWBC is aimed at the casual user

The HTML NWBC has an address field for a URL.

Programming Aspects

Q: In the installation under C:\Program Files\SAP\NWBC\ there are a number of executables, dlls and other files. What do they do?

A: NWBC.exe – That is what gets executed when you click on the icon on the desktop.

NWBCCore.exe – This is the main process to run NWBC.

NWBCSAPlets. Exe – This is an SAP widget engine for SAPLets (not productized)

NWBCURLHandler. Exe – This is a small launcher to react to a URL like: „sap-nwbc://“. It is used to start NWBC against a specific server. The customer can create “sap-nwbc://xxx” link Web page and by click user would start NWBC.

sapAcfDummy. Html - Acf specific (Active Component Framework). Used for JGannt/JNett, Microsoft Office integration

SAPAcfEolasPatch.js

Roles (PFCG)

Q: How much work is involved in maintaining roles in PFCG? Doesn’t that generate work and raise costs for migrating from SAP GUI to NWBC?

Before you maintain the roles you have to clearly define the business processes. You can then derive the business roles from these and then turn them fairly quickly into PFCG roles. Creating the menus should then be straightforward. In our experience most customers need to spend more time defining their business processes. This leads to concrete, time-consuming but crucial preliminary questions of the form: “Is Mr. X allowed to do Y or only Z?” and “To what extent to we want to restrict our employees’ working environment?”

Q: What happens if roles are duplicated?

A: NWBC uses a merging function, so there are no double entries.

Q: Can you import roles from one system to another?

A: Yes, using SM59 see SAP Library: 5.11 Remote Systems

System Connections

Q: Is there a maximum number of systems?

A: There is no technical limitation to the number of systems.

Frequently Asked Questions - SAP NetWeaver Business Client

SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 7

But: The more systems you have the more complex it is to maintain. PFCG was not built to maintain lots of systems. If you have lots of systems use the portal. It has better tools.

Q: Can NWBC manage over 10,000 users?

A: Yes, see the section in the documentation on the performance profile for NWBC: SAP Library : 8

Performance Aspects

Q: Is there an .ini file for NWBC?

A: Yes, there is an ini file to maintain technical information as with SAP GUI.

Q: Can you access more than one system?

A: Yes, you can access 2 or more systems by opening 2 instances of NWBC.

Q: While using NWBC, how can I ascertain which system I am logged into (DEV, QA, PRD)?

A: Here, we have to distinguish between NWBC for desktop and NWBC for HTML. Desktop client : you can find out about NWBC using the menu options Help -> About NetWeaver Business Client and then you can find out even more by clicking System Information. You can also click on the SAP icon right at the bottom of the NWBC to access system information. But that does not tell you whether you are in a QM system etc. In new versions if NWBC for Desktop such as 4.0 or in the HTML Add-On our developers are working on theming. For example, you could display the shell in a different colour depending on whether the system is a production system, a QM system or a development system. With the HTML version you can specify a Welcome message. This message appears at the top of NWBC. You could mention the system type (eg QM) in this Welcome message. HTML Client: Welcome Message (currently only in NW 7.31), see docu chapter 4.6 Here is the technical background: *** WELCOME_MESSAGE At runtime, the system selects the welcome message in the logon language. If no matching language entry is found, LANG=' ' or LANG='*' is used as a fallback. The welcome message is displayed in NWBC for HTML next to the Log Off pushbutton. The VALUE field contains the text. You can use the following placeholders: � &NAME&: first name � &SURNAME&: last name � &FULL_NAME&: full name � &USER&: user name � &CLIENT&: client � &SYSTEM&: system ID ***

Q: Does NWBC cause bandwidth problems?

A: Usage of the SAP GUI for Windows instead of SAP GUI for HTML results in a significant bandwidth reduction. The NWBC for Windows shell is rendered on the client side and the role XML is cached on the client side. Therefore shell rendering is generally a bandwidth reduction compared with the NetWeaver Portal shell. Web content (like BSP or Web Dynpro) running within NWBC is unchanged in its bandwidth requirements.

Frequently Asked Questions - SAP NetWeaver Business Client

SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 8

Q: Is there a maximum number of windows that can be open in NWBC?

A: So far there is no limitation from the NWBC side, except a memory limit. It is possible to open 100 windows, but be careful; some servers limit the number of open sessions. For example, by default, SAP J2EE limits the number of open Web Dynpro JAVA applications to 20. With SAP GUI you can have a maximum of 6 windows open in parallel.

Q: Do the connections have to be defined for SAP GUI and for NWBC, that is, twice?

A: Yes.

Q: Which client technology is recommended by SAP for customers running Linux if they use roles that mix Dynpro and Web Dynpro applications?

A: NWBC for desktop does not run on Linux. NWBC uses SAP GUI for Windows to display dynpros. It does not use the Java GUI. However, NWBC for HTML does run in Firefox, which will work on Linux.

Citrix: Q: Does NWBC support Citrix?

A: Yes, Testing@SAP” contains a NWBC installation.

NWBC for Desktop works on Windows platforms, also on Citrix. NWBC for HTML is browser-based (see SAP’s browser PAM); it also runs in Citrix environments.

Integration

Adobe Reader

Q: Does the documentation specify which version of Adobe Reader has to be installed? Or does NWBC itself incorporate a specific version of Adobe Reader?

A: There are no specific requirements regarding NWBC and Adobe Reader. When forms are displayed in NWBC then this involves forms integrated in Web Dynpro ABAP. For information about browser support for Adobe Forms please read the PAM (Product Availability Matrix), available on SAP Service Marketplace.

Business Server Pages (BSPs)

Q: Are there are any technical restrictions when linking Business Server Pages within the NetWeaver Business Client?

A: There is no limitation for BSP or Web Dynpro ABAP technology for NWBC.

Business Suite: CRM

Q: Can I integrate CRM Content in NWBC?

Yes:

First, you need to set up a connection and trusted relationship between the two systems:

Connecting Two Backend Systems - Part One (RFC Connections)

Connecting Two Backend Systems - Part Two (Trusted Relationships)

Connecting Two Backend Systems - Part Three (Single Sign-On)

Then, you need to follow the documentation:

9.3 How to Integrate CRM Content in NWBC

Frequently Asked Questions - SAP NetWeaver Business Client

SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 9

Business Suite: ESS/MSS

“As of EhP5 for ERP 6.0, We officially support NWBC scenario for ESS/MSS. For casual users like ESS we position NWBC HTML since it is zero footprint client (no installation). However even NWBC Desktop is supported. “You can find the deployment options described in help portals. http://help.sap.com/erp2005_ehp_05/helpdata/en/44/bfc5a026ea4689a964b14609bd4111/frameset.htm

http://help.sap.com/erp_mss_addon10/helpdata/en/2a/8dcc65a90444e2bf6ab0b39d05b455/frameset.htm

“We have also a consulting note 1450179 that describes all kinds of combinations possible. “For NWBC environment, we provide POWL for all kind of approval scenarios based on SAP workflow. For specific approvals like Leave and Time entry approvals there is better functionality offered compared to UWL (like multiple approvals in a single click). “There are no restrictions from ESS/MSS WD ABAP application consumption perspective to use NWBC. However customer must decide switching from portal based on overall requirements like how much they do specific branding, theming, custom development & help content.

Business Suite: Side Panel

Note: The aim of this section is to cover questions not in the documentation. Before posting an additional question, please read the documentation: SAP Library : 5.10 Side Panel

Q: Can customers display documentation in the side panel?

A: Yes. There is an appropriate chip: Title = SAP Help Portal Name = X-SAP-WDY-CHIP:WDR_CHIP_IFRAME Package = SWDP_CCP_WD_API This is generally available. (It defaults to Page Builder docu, but you can get to SAP Library from there). Alternatively, Side Panels can include a Web Chip, which expects a URL ; docu can be accessed by URL; therefore the customer could also make their own.

Q: Are there side panels with map data, for example where a simple address can be displayed?

A: Yes. For example, one could: 1. Create a Web CHIP. 2. Specify the URL for Google Maps. 3. Specify the appropriate URL parameter.

For more details, see SAP Library : 6.7 Side Panel Programming

Q: In which release are the Side Panel and the Page Builder available?

A: NWBC for Desktop 3.5 comes along with the Side Panel. You define the side panel in the back end in transaction PFCG from release NW7.03 onwards. The same is true of some Page Builder chip features. The side panel is part of NW7.03, shipping in Suite ECC6 EHP6. Page Builder is already available with 7.02, Business All-In-One is using this in their shipment

Business Suite: SRM

See also SAP Note 1378659

Business Suite: Web Dynpro ABAP-based Applications

If a screen has been converted to WDA can I still revert to SAP GUI if I prefer the old screen?

SAP does not convert each SAP GUI screen 1 to 1 to a new WDA screen. The new WDA screens are always part of new process and engineered for support the new process. The assumption is that the SAP GUI

Frequently Asked Questions - SAP NetWeaver Business Client

SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 10

screen is replaced by the new process. However, users are generally still able to access the old SAP GUI transactions. They are still available in the system. It may be the case that the old transactions are no longer part of the role.

Q: What percentage of screens have been converted to WDA? Is there a roadmap for this? Will all SAP GUI screens be converted eventually? With EhP6 we have more than 2000 WDA screens. The redesign depends always on the end-user needs and the corresponding use cases.

Q: How much work is involved for the customer in converting SAP GUI screens to WDA screens? It depends. As most WDA screens are related to new processes some minor end user training might be required. As the end user can also personalize the screens, these features need to be explained. It is possible to configure WDA screens via the Floor Plan Manage (FPM). The customer can also use the FPM to create his own screens. If the customers uses for example our Business Object Layer (BOL) he can create the UI via configuration of the FPM against the BOL framework.

Q: Are the new WDA screens automatically available when a new EHP is installed or does each screen have to be activated?

You need to activate the corresponding Business Functions. Only after a Business Function activation the new screens will be visible.

HTML5

Q: What does the roadmap look like for rendering HTML5 pages?

A: If a customer has IE 9+ (with an HTML 5 rendering engine) on his computer then NWBC will render HTML 5 based pages.

Keep in mind we always use Internet Explorer as the HTML rendering engine.

IBM WebSphere/ Microsoft Sharepoint

Q: I have Microsoft Sharepoint/ IBM WebSphere. Should I use SAP Enterprise Portal or SAP NetWeaver Business Client in conjunction with these?

A: Both SAP Enterprise Portal and SAP NetWeaver Business Client (HTML Client) work with Microsoft Sharepoint or IBM WebSphere. Which one you use depends on your other requirements – see above. To integrate NWBC with either Microsoft Sharepoint or IBM WebSphere, see the following documentation: 9.1 How To Integrate NWBC into a Microsoft SharePoint Portal 9.2 How to Integrate NWBC into an IBM WebSphere Portal

Microsoft Silverlight

Q: A customer has some Silverlight applications. I assume they are “integrated” in NWBC using a URL. Is this correct?

A: Yes, they can run Silverlight application as a normal URL-based application. Of course, the Silverlight plug-in must be installed on the user’s PC.

SAP NetWeaver Portal

Q: How should we deal with users who access SAP both via Portal (casual HCM) and directly (primary job function)?

A: One option is for them to use the portal most of the time and then to talk directly to the back end using NWBC for HTML. Another is to use just NWBC for desktop but using a portal connection rather than talking directly to the back end.

Frequently Asked Questions - SAP NetWeaver Business Client

SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 11

Third-Party Content

Q: What options are there for integrating 3rd

party applications in NWBC?.

A: In general, you can integrate any third-party content that can be accessed by URL.

In Web Dynpro, you can integrate 3rd party UI controls via FlashIsland/SilverlightIslands into Web Dynpro screens.

It’s possible to run/launch 3rd party application from NetWeaver Business Client by defining a new entry in PFCG with “Web address/file URL” type (like Web Dynpro/Transaction/other types).

Related Content

SCN Space : UI Technology

Web Dynpro ABAP

SAP NetWeaver Portal

Frequently Asked Questions - SAP NetWeaver Business Client

SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 12

Copyright

© Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Oracle Corporation.

JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.