BPC RCA & Monitoring

Best Practice for SAP BPC

Version Date: January 2010
Contents
1

Root Cause Analysis ..........................................................................................................................2

1.1

1.2

1.3

1.1.1

Change Reporting (Viewer and Compare) ......................................................................2

1.1.2

File System Browser ........................................................................................................5

1.1.3

OS Command Console ....................................................................................................7

BPC RCA ABAP Transactions or Programs.........................................................................10

1.2.1

BPC Performance Statistics ...........................................................................................10

1.2.2

Shared Query Engine Tester.......................................................................................... 11

1.2.3

Script Logic Tester .........................................................................................................12

1.2.4

DM Package Run Tester ................................................................................................13

BPC RCA with BPC Log Files ..............................................................................................14

1.3.1

BPC Log files on BPC Clients side / BPC for Office ......................................................14

1.3.2

BPC Log files on BPC .NET server ...............................................................................14

1.3.3

BPC Log files on BPC BW/ABAP Server.......................................................................15

Monitoring Tools ...............................................................................................................................16

2.1

BPC ABAP Server (BI with Solution Manager) ....................................................................16

2.2

CA Wily Introscope ...............................................................................................................16

2.3
3

Solution Manager with BPC NetWeaver Version (with Diagnostic Agent) .............................2

2.2.1

CA Wily Introscope.NET Agent ......................................................................................16

2.2.2

CA Wily Introscope Workstation.....................................................................................17

2.2.3

Wily Transaction Trace...................................................................................................25

CCMS Monitoring with SAPCCMSR Agent .........................................................................32

Further Information ...........................................................................................................................33

3.1

Memory Metrics Information Appendix..............................................................................33

Best Practice: BPC NW RCA & Monitoring

1 Root Cause Analysis

1.1 Solution Manager with BPC NetWeaver Version
(with Diagnostic Agent)

1.1.1 Change Reporting (Viewer and

Compare)
With Solution Managers Change Reporting, we can view the content of BPC_NW components
configuration file to check the current configuration values (Viewer) in order to identify wrong values.
We can also compare configuration values between 2 technical systems, or between 2 dates on one
technical system (Compare) to identify what had been changed or the difference.

To perform BPC_NW configuration changes monitoring, you can use the Change Reporting tool in
SAP Solution Manager Work Centers. Go to Root Cause Analysis System Analysis Select the
correct System ID Click the Change Reporting button.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

Inside Change Reporting there are 2 tabs, Viewer tab and Compare tab.

Change Reporting: Viewer

Under the Viewer tab, you can view the important configuration files of each BPC_NW components
(BPC .NET Server, Microsoft IIS and Microsoft .NET Framework) by expanding the selected node.
Select the date on the Timestamp and click Apply. On each selected configuration node, you will see
the detail or contents of the configuration on the right hand side. Select the configuration file in the
Store List will expands the content of the configuration file on Store Content.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

Change Reporting: Compare

With Compare, you can make a configuration file comparison between 2 different BPC Technical
Systems in the Solution Manager or you can do comparison of configuration file on a BPC Technical
System between 2 dates.
With this Compare function, you should be able to identify the difference between working and notworking environment cases or worked yesterday but not today cases.

The Compare screen contains 3 areas:

1. Reference System/date
2. Custom System/date
3. Result Summary

Select the base configuration of a Technical System and/or Date in the Reference area and the
counterpart for comparison in the Custom area then select the configuration node. Choose
comparison type, Fast or Deep, and click Compare.
The result of the comparison will be shown in the Result Summary area.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

1.1.2

File System Browser

With Solution Managers File System Browser, we can browse BPC_NW components files, put the
files into our basket for later analysis, and download the files into our local drive.
To use the File System Browser in Solution Managers Work Centers, go to Root Cause Analysis
Hot Analysis Select the application server host of interest File System Browser

Tips: You must have Internet Explorer as your default browser to open the File System Browser.
On the opened Internet Explorer, you will find 3 pre-defined folders:

BPC folder, pointed to %Drive%:\BPC folder in the application server.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

sap folder, pointed to %Drive%:\USR folder in the application server.

WINDOWS folder, pointed to %Drive%:\WINDOWS folder in the application server.

You can add file(s) into your basket by marking a checkbox on the file(s) and either clicking Add All to
Basket or Add Selection to Basket at the top of the page.

You can show the content of your Basket by clicking the Show Basket button at the top of the page.

To download the files, or open or show your Basket, select the file(s) and click the Get All/GetFile
button at the top of the page. Then, on the pop up window, choose Click Here To Save The File. You
can delete them from the Basket by clicking the Remove File or Remove All button.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

Tips: The content of the Basket will be removed automatically when your session ends if you do not
save the basket via Basket Manager.
You can use Basket Manager to organize your file(s) into more than one Basket and load them back
to workspace when you need them.
After you add a file(s) into a Basket, it will be saved in <current> basket which is temporary basket.
You can permanently save the Basket and give it a name in Basket Manager.
To save and name the Basket, go to Basket Manager select <current> Basket click Edit.
Edit the Name field (remove <current> text) and type in your Basket name and write some text in
Description field.

You can load back the Baskets content by clicking the Load button in Basket Manager and you will
see the loaded file(s) in the Basket in File System Browser.
Tips: When you save again after the loading, the file(s) will be stored in a new Basket.
To delete a saved Basket, click the Delete button in the Basket Manager.

1.1.3

OS Command Console

With Solution Managers OS Command Console, we can run the pre-defined Operating System
commands to help us to troubleshoot at OS level.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

To open the OS Command Console in Solution Managers Work Centers, go to Root Cause Analysis
Hot Analysis Select the application server host of interest Os Command Console.

Tips: You must have Internet Explorer as your default browser to open the OS Command Console.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

OS Command Console window contains 3 main panes:
1. Prompt pane
2. Result pane
3. History pane
In the Prompt pane, you select the monitored system, the hostname, Group of commands, and the
command that you want to run. Please note that you can only run the pre-defined commands in the
Prompt Pane. You can put parameter(s) for the command (optional) and you can specify whether to
run the command once (Option = Simple) or you want to run the command multiple time (Option =
Recurrent) by specifying the Interval for each run.
Here are some pre-defined OS Commands that would be helpful:

No.

Group

Command

Description

Network

Netstat

Shows active connections on the server

Network

IPConfig

Shows the IP configuration on the server

Network

Ping

Test connection from the server to the other computer

System

Tasklist

Shows the current running processes on the server (similar

to Task Manager)

System

CpuStat

Shows the CPU usage on the server

System

MemStat

Shows the current memory usage on the server

In Result pane, you will see the result of the command that you run.
In History pane, the command(s) that you run will be logged for your future reference. You can delete
the whole commands history by clicking the Clear History button or clicking the Delete Command
button for deleting single command history.

2010 SAP AG

10

Best Practice: BPC NW RCA & Monitoring

1.2 BPC RCA ABAP Transactions or Programs

1.2.1

BPC Performance Statistics

Transaction Code: UJSTAT

ABAP Report: UJ0_STATISTICS_RPT

SAP BPC Performance Statistics is a new functionality starting from BPC 7.0 NW and is based on the
concept of BI statistics. The Statistics Framework in SAP BPC is a central, generic framework
designed to help monitor performance for SAP BPC modules like Shared Query Engine (SQE), Write
Back, Script Logic run and so on.
With this framework, we can identify and analyze areas for improvement, both in terms of development,
and performance tuning in the customers system. Like BI Statistics, SAP BPC statistics works on the
concept of ACTIONS and EVENTS.

ACTIONS are the different types of requests that can be issued. Examples include Write Back
data; Read data through SQE; Run K2 Script Logic. They are stored in table UJ0_ACTION
(text table is UJ0_ACTIONT)

EVENTS are discrete functions inside an SAP BPC module. For example, Events inside WriteBack request could be Check Security, Check Work Status, and so on. They are stored in
table UJ0_EVENTS (table text is UJ0_EVENTST)

By default, the BPC Performance Statistics is disabled for all applications and we have to turn it on for
the application that we need to do troubleshooting on it. This is controlled by a new BPC Application
Web Admin Parameter called BPC_STATISTICS. It has two values ON and OFF (actually, any
value other then ON will result in the system treating Statistics as being off). When you toggle this
value, you will automatically turn on/off the SAP NetWeaver BI statistics for the Multiprovider assigned
to this application.

Application Parameter:

After you enable the statistics, run the business transaction that has performance issue and then
analyze the statistics data with UJSTAT transaction on the ABAP server.
UJSTAT transaction

Select by:
Statistics GUID value (optional)
BPC User
Start Date
Start Time

2010 SAP AG

Action being performed

Appset
Application

11

Best Practice: BPC NW RCA & Monitoring

:

SAP BPC Statistics example:

1.2.2

Shared Query Engine Tester

Transaction Code: ABAP Report: UJQ_SQE_TEST

You can use SQE Test application to do troubleshooting on the ABAP layer data retrieving process in
BPC_NW. With this tool we could localize the data retrieving problem whether it is happening in the
ABAP layer or on the .NET layer.
In terms of performance issues on the BPC_NW data retrieving (when a user reported slow response
time on opening reports or input schedules), we could find root cause with this tool and run ABAP
Trace (T-Code: ST12) to profile the retrieving process.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

1.2.3

12

Script Logic Tester

Transaction Code: UJKT

ABAP Report: UJK_SCRIPT_LOGIC_TESTER
Script logic is a user-owned logic calculation on BPC_NW data and it will be run on the ABAP layer.
Improper script logic writing would create performance issues, and Script Logic Tester is the tool to
help us to troubleshoot on the ABAP side.
In terms of performance issues on the BPC_NW script logic, we could find root cause with this tool and
run ABAP Trace (T-Code: ST12) to profile the script logic run process.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

1.2.4

13

DM Package Run Tester

Transaction Code: ABAP Report: UJD_TEST_PACKAGE

With this tool, we can run a Data Manager package directly in the ABAP layer and do troubleshooting
as needed to narrow down the problem on the ABAP layer.
In terms of performance issues on the BPC_NW DM package, we could find root cause with this tool
and run an ABAP Trace (T-Code: ST12) to profile the DM package run process.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

14

1.3 BPC RCA with BPC Log Files

There are 3 areas where BPC will generate log files to help problem troubleshooting activities.
1.

BPC Client side / BPC for Office

2.

BPC .NET Server

3.

BPC BW/ABAP Server

1.3.1 BPC Log files on BPC Clients side /

BPC for Office
There are 2 ways to enable logging into file for BPC Clients.
1.

BEFORE SP06
a)

Enable deep log with the following steps:

b)

Use the BPC administrator to set Appset parameter: LOGLEVEL in BPC webadmin
(LOGLEVEL = 4 for verbose logging).

c)

The end user to logon to the excel client and open up the template that requires long sending
time.

d)

Click refresh or Send data button, you will find newly created log files under
Drive:\My Documents\BPC\Logging\ . If support is required, you can should attach the
log file in the CSS message for SAP to further analyze the issue.

2.

AFTER SP06 (SAP Note: 1396222)

Logging: Before SP06, client side logging and server side logging are controlled by the same
AppSet parameter LOGLEVEL. After SP06, client side logging can be turned on or turned off
independently by setting AppSet Parameter ENABLE_CLIENT_LOGGING.

1.3.2

BPC Log files on BPC .NET server

The BPC .NET Middle Tier offers three primary logging mechanisms. Each of these logs gives
different information:

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

a)

SAP BPC .NET Server logs (C:\BPC\Logging)

b)

Microsoft IIS Server logs

c)

Microsoft Windows Event Viewer

15

Enable deep BPC .NET Server log with the following steps:

SAP BPC .NET Server logs: Located in "Drive:\BPC\Logging" and only errors are logged by
default LOGLEVEL. Logs are time-stamped by date and new file is created for each day (SAP
Note: 1286991).

Use the BPC administrator to set Appset parameter: LOGLEVEL to 4 in BPC webadmin for
verbose log.

1.3.3

BPC Log files on BPC BW/ABAP Server

You can analyze the BPC log within the ABAP Application Log transaction: SLG1. Filter the log to
display only BPC related log with UJ* keyword in the log object.

Please be noted, there are also other useful log files in ABAP server which could be used in the
troubleshooting, such as:
1) ABAP Dump Analysis (t-Code: ST22)
2) ABAP System Log (t-Code : SM21)

For more information on BPC_NW Logging, see SAP Note: 1286991.

2010 SAP AG

16

Best Practice: BPC NW RCA & Monitoring

2 Monitoring Tools
2.1 BPC ABAP Server (BI with Solution Manager)
Refer to the BI Administration Cockpit details on SAP Help Portal.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/48/bc406a800a4226951dcc57428e03f2/frameset.ht
m

2.2 CA Wily Introscope

2.2.1

CA Wily Introscope.NET Agent

CA Wily Introscope .NET Agent, we can monitor the BPC .NET Application Server. The
Introscope .NET Agent instruments the BPC .NET components by measuring the average response
time of the methods in .NET classes and stores it in the CA Wily Introscope Enterprise Manager.
BPC App

BPC App

Server

Server

Enterprice
Manager

.NET
Agent

.NET
Agent

BPC App
Server
.Net
Agent

Introscope
Workstation
/Webview

CA Wily Introscope instruments 2 areas in BPC_NW which are:

1. Send Data processes
2. Retrieve Data processes

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

2.2.2

17

CA Wily Introscope Workstation

With CA Wily Introscope WorkStation or Introscope Webview, we can monitor the average response
time of each BPC_NW .NET components that get involved during each process.
You can access the Introscope WorkStation or Introscope Webview from Solution Manager Work
Centers Host Analysis Select the BPC system Introscope WorkStation or Introscope Webview
(on left pane under Offline Analysis)

This document will use Introscope Workstation as a guideline, but you will find the similar functionality
and look & feel on Introscope Webview, which is a web based GUI.
On the pop up logon screen, type in the Wily Introscope username and password:

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

18

Inside the Introscope Workstation Console view, you will find BPC_NW and BPC_NW on the
navigation dashboard. Note: We will discuss BPC_NW later.

There are 2 links in BPC_NW navigation: Triage link to BPC_NW Triage dashboard and Overview link
to BPC_NW Overview dashboard.
Click the Overview link. You will be brought to BPC_NW Overview dashboard as shown below. The
Overview dashboard contains 2 quick links to:
1. BPC_NW Retrieve Data Triage dashboard
2. BPC_NW Send Data Triage dashboard

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

19

Click the Triage link; you will be brought to BPC_NW Triage dashboard as shown below. The Triage
dashboard contains the Average response time graph of Web Services of each BPC_NW processes
like Retrieve Data process and Send Data process. These graphs would give you a quick view of the
Web Services average response time of each process so you can find the higher response time
activities in your BPC_NW system quickly.
There are quick links to CPU and Memory usage for each OS processes where you can jump into the
CPU utilization dashboard and Memory utilization dashboard for further analysis.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

20

2.2.2.1 Using Introscope Workstation: How to Read

the Graph
On every graph, if you hover your mouse on a point in the graph, you will get value information of the
measure.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

2.2.2.2 Using Introscope Workstation: How to

Analyze Retrieve Data Process
You can start the Retrieve Data process analysis on the Introscope Workstation by go to BPC
Retrieve Data dashboard from BPC Overview dashboard click on BPC Retrieve Data link.

The Retrieve Data dashboard shows the metrics of each component which are involved in data
retrieving process. It measures the average response time start from when a retrieve request come
into the system from Microsoft IIS web services, BPC DLL library components, BPC Retrieve Proxy
and ABAP Proxy components. Therefore, this looks more like a request calls flow in BPC_NW
Retrieve Data process.

2010 SAP AG

21

22

Best Practice: BPC NW RCA & Monitoring

.net server

ABAP Server
BPC Proxy

TCP/IP

BPC WS
Components
DLL

ABAP Proxy

IIS

HTTP/s - SOAP

MS Excel BPC
Plug-In

Please note that this is a simplified diagram to get the picture of Retrieve Data process quickly.
When a request comes in, you will see a metric in the BPC WebService graph followed by a metric in
BPC DLL Library. The request will be forwarded to BPC proxy components which in turn make the
communication to ABAP Server via ABAP Proxy.
On any bottleneck in the retrieving process, you will see a high average response time on the specific
component. Remember that the average response time on the BPC WebService graph included the
average response time from BPC DLL Library and therefore the average response time of BPC Proxy
and so on to the back end.
Tips: To analyze a high response time in this .NET server s components, you have to first analyze
the ABAP server s average retrieving time to find out if it is caused by the bottleneck back end. Tools
such as UJSTAT could be helpful. UJSTAT shows metric both for query data engine (Shared Query
Engine) and send data engine (Write Engine) on the ABAP Server.

2.2.2.3 Using Introscope Workstation: How to

Analyze Send Data process
You can start the Send Data process analysis on Introscope Workstation by going to the BPC Send
Data dashboard from the BPC Overview dashboard click on BPC Send Data link.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

23

The Send Data dashboard shows the metrics of each component which is involved in data sending
process. It measures the average response time, starting from when a retrieve request comes into the
system from Microsoft IIS web services. These are BPC DLL library components which are divided
into the data sent from BPC for Office and BPC for Web. This request will go through the BPC Proxy
and ABAP Proxy components before it goes to the ABAP Server.
Tip: To analyze a high response time in this .NET server s components, you have to first analyze the
ABAP server s average retrieving time to find out if it is caused by the bottleneck back end. Tools
such as UJSTAT could be helpful. UJSTAT shows metric both for query data engine (Shared Query
Engine) and send data engine (Write Engine) on the ABAP Server.

2.2.2.4 Using Introscope Workstation: How to

Analyze CPU and Memory Usage
To extend your analysis of total CPU utilization of each OS process in BPC_NW, you can go to
BPC_NW Triage dashboard click BPC Application Server CPU Usage link on the right-hand side.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

You will find the OS processes of BPC_NW .NET server. The higher value on the CPU metrics is
100%
For memory analysis for OS processes of BPC_NW, you can go to BPC_NW Triage dashboard
click the BPC Application Server Memory Usage link on the right-hand side.

2010 SAP AG

24

Best Practice: BPC NW RCA & Monitoring

25

There are 5 memory metrics for each OS process which are; Private Bytes, Working Set, Working Set
Peak, Virtual Bytes, and Virtual Bytes Peak. See Memory Metrics Information Appendix for more
information.

2.2.3

Wily Transaction Trace

Wily Transaction Trace is part of the CA Wily Introscope that could provide a quick catch to the user
transaction like:
1.

By Transaction s Response time

2.

By Transaction s Error during the run

3.

By Transaction s HTTP properties (UserID, SessionID, URL, and so on)

4.

The transactions that you specified by .NET namespace/operationname and filter

You can find the Wily Transaction Trace in the Wily Introscope WorkStation by going to WorkStation
New Transaction Trace Session.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

To catch transactions by its response time, you can specify the minimum response time of a
transaction that you want to catch either in milliseconds or in seconds.

2010 SAP AG

26

Best Practice: BPC NW RCA & Monitoring

To catch transactions by HTTP properties, you can select the HTTP property in the drop down box
and set the value to be matched.

To catch transactions by error message, you can select the Error Matching and set the value to be
matched.

2010 SAP AG

27

Best Practice: BPC NW RCA & Monitoring

To catch transactions by its namespace/operationname, you can select the namespace or

operationname, and set the value to be matched

2010 SAP AG

28

Best Practice: BPC NW RCA & Monitoring

Set the trace session duration and select either all Agents from all recognized hosts or a specific
Agent (You can select more than one Agent with Ctrl or Shift button).

2010 SAP AG

29

Best Practice: BPC NW RCA & Monitoring

During the transaction capturing, you will see all the transactions which correspond to your filter
options. Click the transaction; you will see more detailed information of the transaction in the lower
section of the screen with a different point of view.
Summary View:

Trace View:

Tree View:

2010 SAP AG

30

Best Practice: BPC NW RCA & Monitoring

Plain Table Viewer:

2010 SAP AG

31

32

Best Practice: BPC NW RCA & Monitoring

2.3 CCMS Monitoring with SAPCCMSR Agent

SAP Solution Manager 7.0 EhP1 can be used as a central monitoring system for SAP Business
Objects Business Planning and Consolidation, both Microsoft and NetWeaver versions. It provides
Basic availability monitoring (GRMG scenario), error monitoring (log files and Windows Event log
monitoring), operating system monitoring (process monitoring) and alert monitoring.

See SAP Note: 1379214 - CCMS-based Monitoring for SAP BusinessObjects BPC NetWeaver for
further information about CCMS monitoring setup and configuration on BPC_NW. The SAP Note is
also workable for BPC_NW 7.0 NetWeaver. In this case, the ABAP managed system is older than
NetWeaver 7.02 so you have to follow the case 2 in that SAP: 1379214 to setup the basic System
Monitoring for BPC (see SAP Note 1368387, case 2)
- a managing system (CEN) older than NetWeaver 7.01,
- a managed system (Satellite) older than NetWeaver 7.02, which means an RFC-enabled satellite
system. In case of BPC, the satellite system in this case is technically represented by the SAPCCMSR
Agent as per SAP Note 209834.

Application
Server(s)

ABAP Server (BI

Ehp1)

IIS + BPC
components
SAPCCMSR

SAPCCMSR

SOLMAN
Central
Monitoring
System (CEN)

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

33

3 Further Information
3.1 Memory Metrics Information Appendix
1. Private Bytes: represents the amount of private virtual memory a process has allocated. This
memory cannot be shared with other processes. If the Private Bytes metric rises steadily, the
process is exhibiting a memory leak bug.
2. Working Set: represents the virtual address space of the process that is currently resident in
physical memory. When you see the Working Set metric goes down steadily, there are 2
possibilities: 1) The process released un-used memory pages from the physical memory or 2) the
system is run out of free physical memory.
3. Working Set Peak: represents the peak amount of Working Set that has been used by a process.
4. Virtual Bytes: the current size, in bytes, of the virtual address space for this process. The virtual
address space limit of a user mode process is 2 GB, unless 3 GB address space is enabled by
using the /3GB switch in boot.ini. Performance degrades as this limit is approached, and typically
results in a process or system crash.
5. Virtual Bytes Peak: represents the peak amount of Virtual Bytes that has been used by a process.

2010 SAP AG

Best Practice: BPC NW RCA & Monitoring

34

Copyright 2010 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 , NT , EXCEL , Word , PowerPoint and SQL Server are registered trademarks of
Microsoft Corporation.

IBM , DB2 , OS/2 , DB2/6000 , Parallel Sysplex , MVS/ESA , RS/6000 , AIX , S/390 , AS/400 , OS/390 , and

OS/400 are registered trademarks of IBM Corporation.

ORACLE is a registered trademark of ORACLE Corporation.

TM

INFORMIX -OnLine for SAP and Informix Dynamic Server are registered trademarks of Informix Software
Incorporated.

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

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

JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun
Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch,
BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned
are trademarks or registered trademarks of their respective companies.
Disclaimer: SAP AG assumes no responsibility for errors or omissions in these materials. These materials are
provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied
warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or
consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or
completeness of the information, text, graphics, links or other items contained within these materials. SAP has no
control over the information that you may access through the use of hot links contained in these materials and
does not endorse your use of third party Web pages nor provide any warranty whatsoever relating to third party
Web pages.

2010 SAP AG