SAP Solution Manager Diagnostics

7.1 Managed System Configuration

for SAP Business Objects Financial
Consolidation

Applies to:
SAP Business Objects Financial Consolidation, version for 7.5 and 10.0. As Managing System an SAP
Solution Manager 7.1 SP03 or higher is required unless mentioned otherwise.

Summary
SAP Business Objects Financial 7.5 and 10.0 have been integrated into Solution Manager 7.1 to support
Root Cause Analysis application SAP Solution Manager Diagnostics (SMD). This document describes how
to setup and configure SMD of an SAP Solution Manager managing system with and for BOFC managed
system.

Authors: Rob Bulusu, Morgan Che

Company: SAP America Inc., SAP China
Created on: 25 October 2011

Author Bio

Ravikanth Bulusu (Rob) works for SAP US, Active Global Support. His area of specialization
includes development, implementation of SAP Business Process Operations - RUN SAP Like
a Factory, integration of E2E Root Cause Analysis, and Diagnostics support integration into
Solution Manager.

Morgan Che is working for SAP China, Active Global Support. His current focus area is the
support of SAP Business Objects Financial Consolidation solutions.
As product integrator, Morgan works on SAP Solution Manager Diagnostic content for SAP and
Business Objects products and applications.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 1
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

Table of Contents
How to use this document .................................................................................................................................. 3
Managed System Setup and Configuration in Solution Manager 7.1 (SP03 and higher) .................................. 3
Prerequisites ................................................................................................................................................... 3
Managed System Setup for SAP Business Objects Financial Consolidation 7.5/10.0 ................................... 4
Technical system setup for SAP BOFC Application Server ......................................................................................... 4
Technical system setup for SAP BOFC Web Server ................................................................................................. 10
Diagnostics Configuration for BOFC Server ................................................................................................. 13
Diagnostics Configuration for BOFC Application Server ............................................................................................ 13
Diagnostics Configuration for BOFC Web Server ...................................................................................................... 17
Related Content ................................................................................................................................................ 21
Copyright........................................................................................................................................................... 22

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 2
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

How to use this document

Diagnostics in SAP Solution Manager depends on the definition of technical system in SAP Solution
Manager. This document describes the steps needed to create and configure technical systems for SAP
Business Objects Financial Consolidation 7.5 and 10.0 in the system landscape of SAP Solution Manager
7.1. Here is brief preview:
 Chapter 2.1 lists the prerequisites we have to meet before launching Technical System setup and
Managed System configuration in Solution Manager 7.1.
 Chapter 2.2 describes how to create a technical system by using Technical System Editor, which will
be further configured by using transaction SOLMAN_SETUP.
 Chapter 2.3 focuses on Managed System configuration in Solution Manager.

Managed System Setup and Configuration in Solution Manager 7.1 (SP03 and higher)
SAP Solution Manager Diagnostics in SAP Solution Manager depends on the definition of technical systems
in SAP Solution Manager System Landscape Directory. In the following, we describe the steps required to
create or maintain the technical systems for SAP BOFC.

Prerequisites
Before starting configuring a technical system for diagnostics in SAP Solution Manager, we have to ensure
that the following prerequisites are all fulfilled:
1. Basic Configuration of SAP Solution Manager
Before starting the managed system setup and configuration of a technical system for SAP Solution
Manager Diagnostics in SAP Solution Manager, you have to ensure the prerequisites referred in the
below page are fulfilled:

SAP Solution Manager Setup & Configuration

http://wiki.sdn.sap.com/wiki/display/SMSETUP/Home
.
2. Diagnostics Agent is installed
For each system that we want to diagnose via Solution Manager, the diagnostics agent needs to be
installed.
For more Information, please refer to:
http://service.sap.com/diagnostics -> Installation & Configuration -> Diagnostics Agent Installation
Guide.
3. Permission that requires to connect agent to SLD server and Solution Manager
During SMD agent installation, we require to provide user accounts to connect agent to SLD server
and Solution Manager. Please make sure the user accounts we use have such permissions to do so.
4. Willy Introscope .Net Agent has been configured
Willy Introscope .Net agent is a bytecode agent monitoring the .Net based components. For BOFC, it
will monitor BOFC Web Server and report metrics to Enterprise Manager in the real time way.

To install and configure it, please see SAP Note 1126554 – Wily Introscope .Net Agent.
5. Managed System has been installed
Before setting up technical system in Solution Manager, please ensure BOFC 7.5 or 10.0 server has
been correctly installed on the host or virtual system.

For more information about BOFC system installation, please refer to the BOFC installation guide
published at the below link:
https://websmp210.sap-ag.de/instguide ->SAP BusinessObjects -> SAP BusinessObjects Enterprise
Performance Management (EPM) ->Financial Consolidation
6. Ncs.conf and SapAgentConfig,xml file should be customized accordingly

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 3
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

Ncs.conf is a configuration file on BOFC server side, which plays a switch role to enable NCS
(Native Component Supportability) based instrumentations for Enterprise Manager and is also
precondition for Working Loading Analysis of BOFC Application Server in Solution Manager.
Additionally, SapAgentConfig.xml should be uploaded to Solution Manager to ensure WMI and NCS
instrumentation function work.

To download Ncs.conf & SapAgentConfig.xml file and configure them, please refer to SAP Note
1365266- RCA:Managed System Setup for BOBJ Financial Cons. 10.5-7.5.
7. Managed System is connected to SLD infrastructure
In order to enable a central maintenance of systems in SAP Solution Manager, we need to setup a
SLD infrastructure to which each managed system is connected to. There are several possibilities
how this infrastructure can be designed.

For more Information, please visit at:

https://www.sdn.sap.com/irj/sdn/nw-sld-> Planning Guide -> System Landscape Directory
8. Bridge your central SLD to the SAP Solution Manager SLD
If your SAP Solution Manager system is not your central SLD system, we need to setup a bridge
forwarding from your central SLD to your SAP Solution Manager SLD.

For More information of this topic, please refer to SAP Note 1148028
9. Solution Manager Support Package version requirements
To check Solution Manager Support Package version requirements for BOFC diagnostic functions,
please refer to SAP Note 1010428 ->End-to-End Diagnostics.
10. Landscape Fetch Job in SAP Solution Manager is scheduled
System landscape maintenance in SAP Solution Manager retrieves the system landscape data
regularly from the configured SLD. This is done via the landscape fetch job which is normally
scheduled during configuration. We can reschedule this job via transaction SMSY_SETUP.

Managed System Setup for SAP Business Objects Financial Consolidation 7.5/10.0
For Solution Manager 7.1, SAP Business Objects Financial Consolidation Application Server and Web
Server use the different method for technical system setup. Here, we individually present the setup process
for both servers.
For more information about Solution Manager 7.1 SP01, you can refer to the following information:
SAP Note 1583348 – Documentation: SAP Solution Manager 7.1
SAP Note 1431633 – SAP Solution Manager 7.1 Installation

Technical system setup for SAP BOFC Application Server

For BOFC Application Server, we can either directly create technical system in Technical System Editor or
use Payload file to register technical system via Sldreg.exe to SLD. To use Payload file registration method,
we need to customize payload file based on the real situation, which differentiates from one system to the
other. Here, for convenience, we only take creation technical System in Technical System Editor for example
to demonstrate how to setup technical system in Solution Manager 7.1.Afterwards, we perform the managed
system configuration based on it by using the “Diagnostics setup wizard”.
1. To create Technical System directly via Technical System Editor, firstly open System Configuration
wizard via transaction: SOLMAN_SETUP. And then, select “Managed System Configuration” ->
“System Operations” ->”Create System” to lunch “Technical System Editor”. Alternatively, you can
use LMDB transaction to open “Technical System Editor” directly.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 4
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

2. In “Technical System Editor”, choose Unspecific Cluster System (UNSPEDIFIC) in dropdown list and
click “Next” to continue.

3. In “System Name”, input System Name that will display in Solution Manager later on.
In “Technology Type”, select SBOP Financial Consolidation (BOFC_Cluster) in dropdown list.
In “Central Host Name”, input the server name. In the end, click “Next”.

4. Click “Save” to finish Technical System creation. And then, the Technical System Editor dialogue will
pop up, which allows us to define more information about our technical system.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 5
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

5. There are 4 steps involving in “Technical System Editor”. Let’s start with “Define Header Data”.

In “Define Header Data”, view the information and ensure it is correct. Click “Next” to continue.

6. In “Assign Database”, click “Assign Database System” and choose” Create New Database System”.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 6
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

7. There are 3 steps for creating a Database system.

In “Choose System Type” step, ensure the type is Database System (DBSYSTEM).

In step 2 “Define the System”, fill out Database Name, Database Host and Database Type according
to the real situation.

In “Define Extended SID” step, input SID or simply accept the predefined one and click “Save” to
finish the Database system creation.

8. Go back to “Assign Database” dialogue, locate Database instance we created in the previous step
and click “OK” to confirm. Afterwards, click “Next” to continue.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 7
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

9. In “Define Technical Instance”, click “Add” and fill out Server Name, Technology Type with “BOFC
Application Server (BOFC_APPServer)” and Host. After completing, choose “Ok” and “Next”.

10. In “Maintain assigned Software” step, click “Add”. In pop-up windows, choose “Used by instance”
and input Fin* as search condition. And then, navigate BOBJ FINANCIALCONS 7.5 or SBOP
FINANCIAL CONS 10.0 depending on the BOFC version installed on the server and click “Add” to
complete software component assignment. Finally, click “Save” to finish Technical System creation.
To view the detailed definition, we can click “Display Navigation Tree”.

In “navigation tree view”, we can evaluate and adjust the definition. If everything is ok, click “Save” to
finish technical system setup.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 8
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 9
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

Technical system setup for SAP BOFC Web Server

For BOFC Web Server, it uses auto-discovery mechanism offered by SAPHostAgent to automatically
discover and create the Web Server technical instance in SLD once connecting SMD agent to Solution
Manager. That means we do not need to create Web Server instance from the scratch and most of
information will be filled up by auto-discovery. We can add the missing information manually in Technical
System Editor later on after technical instance has been generated in Solution Manager. Meanwhile, to
support auto-discovery, please note the SAPHostAgent version is at least: Kernel Version 720 with Patch
Number 54.
1. To view Web Server instance in SLD, open “Technical System Editor” by using LMDB transaction. In
system type drop down list, choose Microsoft Internet Information Services (MSIISINST). In
“Extended System ID”, locate Web Server instance generated for our system (host name information
can indicate which one we should select) and click “Ok” to confirm.

2. Click “Maintain” to view the detail information.

3. In Software category->Product Instances tab, choose “Add” to lunch Software Component selection
windows. Input SBOP Fin* as search condition and locate SBOP FINANCIAL CONS 10.0 Fin.Cons
WebServer for SBOP FINANCIAL CONS 10.0 version, and then click “Add”. For BOFC 7.5, we can
use BOBJ FIN* as search condition, navigate BOBJ FINANCIAL CONS 7.5 Web Server for selection.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 10
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

4. In Software category->Software Component Version tab, choose “Add”. Highlight “Used by Instance”
in “Select Technical Instances” where the Software Component should be added. Input SBOF Fin*
as search condition and locate SBOP FINANCIAL CONS WEB SITE 10.0 for SBOP FINANCIAL
CONS 10.0 version, and then click “Add”. For the prior versions, such as BOBJ FINANCIALCONS
7.5, we can use BOBJ FIN* as search condition.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 11
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

5. In Technical Instance tab, check if the websites and corresponding paths have been correctly
discovered.

6. In Host -> Host Details, check if the host relevant information has been correctly discovered. If they
are all discovered, the technical system setup of BOFC web is done. Otherwise, we should add it by
our own.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 12
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

Diagnostics Configuration for BOFC Server

After ensuring that all prerequisites are met and finishing Technical System creation, we can individually start
diagnostics configuration for both BOFC Application Server and Web Server.

Diagnostics Configuration for BOFC Application Server

1. Open the configuration wizard for SAP Solution Manager via transaction: SOLMAN_SETUP.
2. Select “Managed System Configuration.
3. Select system type of the system we want to configure. Typically, choose “Unspecific” type.
4. For Unspecific based systems, we need to select the Technical System for configuration..
5. Select “Configure System” to lunch configuration wizard.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 13
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

6. In Select Product, click “Edit” to enter edit mode and ensure statues indicator is green. Click “Next” to
finish.

7. The check prerequisites checks if all requirements for configuring diagnostics are fulfilled on the
managed system. Select “Execute” to automatically perform the check. If there are some errors and
warnings, such as Managed System does not meet the Diagnostics prerequisites etc, you can simply
ignore. The detailed results can be accessed through the “Show” link in the log table after selecting
the line item for the check. Click “Next” to jump in the next step.

8. In “Assign Diagnostics Agent” step, please choose the agent we setup on the managed system and
choose “Assign” to attach the agent to the current Solution Manager.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 14
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

 If there is no agent in “Agent Assignment”, which means the agent has not connected to the
Solution Manager. We should connect it to Solution Manager at first by choosing “Agent
Candidate Administration”.

 Input SLD server credentials to access the agent installed on Managed System.

 Select the agent that needs to be connected to Solution Manager. Fill out “SMD user” and
“ Password” with the user acount which is able to and click Apply to lunch agent attachment.

 When agent state says Associated, go back to Agent Assignment step to finish the agent
assignment.
9. In “Enter System Parameters”, choose Introscope EM in Enter System Parameters, which SMD
agent will collect data from.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 15
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

10. In “Enter landscape Parameter” step, click the last row of landscape options and define the actual
path where we install BOFC Applicaiton Server.
Example:
BOFC 7.5 - C:\Program Files\SAP BusinessObjects\
And then, choose “Save Landscape Parameter”. When finishing, choose “Next” to continue.

11. The last step is to configure system by selecting “Execute All”. Ensure all the Status indicators are
green. In case of red indication, please open “Show” link to see the detailed message.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 16
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

Diagnostics Configuration for BOFC Web Server

1. Open the configuration wizard for SAP Solution Manager via transaction: SOLMAN_SETUP.
2. Select “Managed System Configuration”.
3. Select system type of the system we want to configure. Typically, choose MSIISINST type.
4. In MSIISINST system list, select the technical system for configuration.
5. Select “Configure System” to lunch configuration wizard.

6. In “Select Product”, ensure to switch edit mode by clicking “Edit” and system information is correct.
Click “Next” to enter next step.

7. The check prerequisites checks if all requirements for configuring diagnostics are fulfilled on the
managed system. Select “Execute” to automatically perform the check. If there are some errors,
such as Managed System does not fulfil the Diagnostics prerequisites etc, please simply ignore. The
detailed results can be accessed through the “Show” link in the log table after selecting the line item
for the check.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 17
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

8. In “Assign Diagnostics Agent”, please choose the agent we setup on managed system and choose
“Assign” to attach the agent to the Solution Manager you are working on.

 If there is no agent in Agent Assignment, which means the agent has not connected to the
Solution Manager. We can connect it to Solution Manager at first by choosing “Agent
Candidate Administration” in “SLD Agent Candidates” tab.

 Input SLD server credentials to access the agent installed on Managed System.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 18
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

 Select the agent that needs to be connected to Solution Manager. Input SMD user name
and password and click “Apply” to lunch agent attachment process.

 When agent state indicates Associated, go back to “Agent Assignment” step to finish agent
assignment by click “Assign” button.
9. In “Enter System Parameters”, choose Introscope EM in Enter System Parameters, which SMD
agent will collect data from.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 19
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

10. In “Enter landscape Parameter” step, ensure the information displaying here is correct and click
“Next”.

11. The step 6 is to configure system by selecting “Execute All”. Ensure all the Statuses are green. If
there are warnings or errors, please click “Show” link in log table for see the detailed information.
Here, we finish Managed system setup for BOFC App server and Web server.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 20
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

Related Content
SAP Note 1265070 - Diagnostics - Setup of Managed Systems
SAP Note 1365266 - RCA: Managed System Setup for BOBJ Financial Cons. 10.5-7.5
SAP Note 1126554 - CA Wily Introscope .Net agent installation

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 21
 SAP Solution Manager Diagnostics 7.1 Managed System Configuration for SAP Business Objects Financial Consolidation

Copyright
© Copyright 2011 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 Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., 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.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 22