sm 7.1-howto - transfer content between sap solution manager systems
DESCRIPTION
SM 7.1 - Transfer Content Between SAP Solution Manager SystemsTRANSCRIPT
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP Solution Manager - Content TransferThis document provides information on architectural anddesign questions, such as which SAP Solution Managercontent is transferable and how.
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
SAP Solution Manager 7.0 & 7.0 EHP1 and aboveCONTENT TRANSFERVersion: 1.7Date:October 2012
2
TABLE OF CONTENTS
PREFACE .......................................................................................................................................................... 31. OPERATIONS AND SOLUTIONS ................................................................................................................ 42. PROJECT MANAGEMENT .......................................................................................................................... 62.1 Projects ........................................................................................................................................................ 62.1.1 Documents ................................................................................................................................................ 72.1.2 Templates ................................................................................................................................................. 72.2 Roadmap ..................................................................................................................................................... 82.3 Solution Documentation Assistant ............................................................................................................... 83. INCIDENT MANAGEMENT .......................................................................................................................... 84. CHANGE MANAGEMENT ............................................................................................................................ 85. TEST MANAGEMENT .................................................................................................................................. 86. ROOT CAUSE ANALYSIS ........................................................................................................................... 97. TECHNICAL DEPENDENCIES .................................................................................................................... 97.1 System Landscape Directory (SLD) ............................................................................................................ 97.2 RFCs, CCMS, and SCOT ............................................................................................................................ 97.3 SAP Business Intelligence and Wily Enterprise Manager Data .................................................................. 97.4 Maintenance Optimizer and License Keys .................................................................................................. 97.5 Central Performance History (CPH) .......................................................................................................... 108. HOW TO ...................................................................................................................................................... 118.1.1 Solution Transfer .................................................................................................................................... 118.1.2 Project Transfer ...................................................................................................................................... 138.1.3 Template Transfer .................................................................................................................................. 168.1.4 Roadmap Transfer .................................................................................................................................. 208.1.5 Solution Documentation Assistant .......................................................................................................... 208.1.6 Test plan Transfer................................................................................................................................... 22
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
3
PREFACE
This document provides information to drive decisions about changing an existing SAP Solution Managersystem, planning a new one, or upgrade an existing SAP Solution Manager 7.01 to a higher release. Itanswers architectural questions to enable decision-makers to design a best-run SAP Solution Managerconcept. Common decisions to be made are:
New SAP Solution Manager installation or upgrade.
Merge or split organizational units resulting, for example, from the sale of company branches.
Correct mistakes made during previous design phases or add missing knowledge about SAPSolution Manager architecture.
The recommendations refer only to content transfer from one productive SAP Solution Manager system toanother. There are no recommendations for managed systems.
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
4
1.OPERATIONS AND SOLUTIONS
Operations is one of the key functions in SAP Solution Manager. It handles your daily business (operations).The majority of Operations content is bundled in a virtual container known as a Solution. This is the locationfor system and process information, data, and documentation, including system administration data and corebusiness process knowledge.1
Not all Operations content is transferable.
SAP distinguishes between Solution content transfer, and the transfer of SAP Solution Manager systeminfrastructure, such as the CCMS or SAP Solution Manager Diagnostics.The matrix below provides an initial overview of transfer possibilities, followed by best practices forperforming the transfer in each area and function.
1http://service.sap.com/~sapidb/011000358700000558132009E
Scenario/Function Transferable? How Remarks
Central System
AdministrationNo
Early Watch AlertNo
Existing EWA reports can be archived in an opticalarchive (see SAP note 546685)
Service Level ReportNo
Existing SLR reports can be archived in an opticalarchive
Business Process andInterfaceMonitoring
YesInitial transfer by
transactionSolution_Transfer
Only the customizing (setup session) is transferred.After the migration, manual generation and activationare required in the new system. Alert history wil l belost.
System Monitoring Only the customizing (setup session) is transferred.After the migration, manual generation and activationare required in the new system. Alert history will belost.In an upgrade it has to be decided whether a transportis appropriate, or the new Monitoring and AlertingInfrastructure is to be used (seehttp://wiki.sdn.sap.com/wiki/display/TechOps/Home)
Collaboration Issues, Expertise-on-Demand requests, and tasks aretransferred. The service plan must be synchronizedwith SAP Backend
Solution definitions
Documentation
Service Plan
http://service.sap.com/~sapidb/011000358700000558132009Ehttp://service.sap.com/~sapidb/011000358700000558132009Ehttp://service.sap.com/~sapidb/011000358700000558132009Ehttp://wiki.sdn.sap.com/wiki/display/TechOps/Homehttp://wiki.sdn.sap.com/wiki/display/TechOps/Homehttp://wiki.sdn.sap.com/wiki/display/TechOps/Homehttp://service.sap.com/~sapidb/011000358700000558132009E -
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
5
Show how thisprocedureis executed in SAP Solution Manager.
Issue Management
Service Deskmessages No
Logical ComponentsNo
To be defined & maintained prior to Solution transfer.Logical components must be created and assigned tothe transferred solution again, in the new system.
Change historyNo
Change documents cannot be transferred from onesystem in another.
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
6
2. PROJECT MANAGEMENT
This chapter describes project-related aspects of transferring content into another SAP Solution Managersystem. It is limited to the most important aspects of making projects initially available in different SAPSolution Manager systems.
2.1 Proj ects2
All projects can be transported in a transport request, which is created using transactionSOLAR_PROJECT_ADMIN.This functionality ensures that all assignments made to the project are included in the transport. However,there are some limitations.
After a successful transport, administration data such as the project landscape, team members, and projectstandards need to be adapted to fit the new system.
The following elements are transported:
Project structure (e.g. scenarios, processes, process steps) with all assignments (transactions,configuration objects, development objects, test cases, ...)
All documents
Structure attributes
Assigned test cases (manual test cases and eCatts) which are stored centrally in the SolutionManager system
Assigned TBOMs (as of SAP Solution Manager 7.1)
Status values in roadmaps directly assigned to a project, and project-related documents assigned to
this roadmap.
The following elements cannot be transported:
Change history of changes on the tabs
Assigned service messages and issues
Assigned end users and end user roles
Assignments of administration (tab) data, such as team member assignments, keywords, status
Document settings in the Knowledge Warehouse (definitions of document attributes and statusschemes)
2Data migration of projects between systems is not supported as of SAP Solution Manager 7.0 (between SAP Solution Manager 2.1/2.2
and SAP Solution Manager 3.1/3.2 data migration was supported via transaction SOLAR_MIGRATION, see SAP Note 644123).
Scenario/FunctionTrans-ferable?
How Remarks
Projects
Yes
TransactionSOLAR_PROJECT_ADMIN
See details in chapter2.1 Projects
Templates See details in chapter2.1.2 Templates
Roadmaps Transaction RMDEF or reportRM_TRANSPORT_FUNCTION
See details in chapter2.2 Roadmap
SolutionDocumentation
Assistant
TransactionSOLMAN_WORKCENTER or
SM_ WORKCENTER
See details in chapter2.3 SolutionDocumentation Assistant
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
7
Show how thisprocedureis executed in SAP Solution Manager.
Logical Components (must be created and assigned again to the transferred project, in the newsystem)
Assigned TBOMs (valid up to SAP Solution Manager 7.01)
Issues and Service Desk messages are not collected while the project transport is created
2.1.1 Docum ents
Documents usually consist of the most recent version (the version displayed in a project) and changeversions, which are created automatically whenever a document is changed.The transport function in SOLAR_PROJECT_ADMIN transfers documents with all change versionsonly ifthe following prerequisites are fulfilled in the Solution Manager system:
1. For systems with support package ST 400 SP18SP26, and support package ST 710 SP1SP3,SAP Note 1624346 must be installed.
2. Table IWPROPVAL must not containthe following entry:
AREA: IWBSOLAR
CLASS: (= space) NAME: IWBSOLAR_TRANSPORT_STATUS VALUE: RELEASED
If table IWPROPVAL contains such an entry, remove it, if you want to transfer all changeversions of the assigned documents.
Please note that documents stored on a third -par ty supp l ier 's con tent server and n ot on an SAP
Content Server wil l not b e transp orted directly . Please pay attention to SAP Note 865561 describ ing a
workaround for th is s i tuat ion.
2.1.2 Temp lates
Templates are created and maintained in template projects, which can be transferred in the same way asother projects, e.g. implementation projects. To be able to transfer templates or complete template projects,both the templates and the template project must be assigned to a transportable package. The package isassigned when the template project and a template are created. A transportable package can be assignedlater, but it is very time-consuming (moving all relevant objects from a local package, e.g. $TMP to atransportable package).
As well as transporting the whole template project (including all templates), single templates, created withinthe template project, can be transported separately, using the template transport function inSOLAR_PROJECT_ADMIN. Once a template has been transported to the target system, it is visible there toall projects, in the Scope tab in transaction SOLAR_PROJECT_ADMIN.Note: the following restrictions apply to transporting a template, compared to transporting projects:
The template transport transfers only the most recent version of a document. Change versions ofdocuments cannot be transferred with this function.
Documentation on the Project Documentation tab is not included in the transport of a singletemplate.
Remark with respect to template project transport:
If the template project has to be transported finally into a target SAP Solution Manager system, the originalityof this project has to be switched into the target SAP Solution Manager system too. This requires additional
activities by using a relocation transport request. Afterwards the template project can be further processed inthe new target system.
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
8
Show how thisprocedureis executed in SAP Solution Manager.
Show how thisprocedureis executed in SAP Solution Manager.
Show how thisprocedureis executed in SAP Solution Manager.
SAP note 1304462describes in the chapter Solution how to proceed, in order to switch the originatingsystem from the old to the new originating system.
2.2 Roadmap
Roadmaps created by the customer can be transported in transaction RMDEFusing reportRM_TRANSPORT_FUNCTION. This report packs the roadmap structure with all the relevant languages,documents (phase and task descriptions), accelerators, entry screen, and roadmap attributes (Flavors,Roles, Subject Areas) into a transport request.Only the most recent version of assigned documents is transferred. Change versions of documents are nottransferred with the roadmap transport.
2.3 Solut ion Docum entat ion A ssistant
You can download or upload the check rules for your Analysis Project using the Solution DocumentationAssistant functionality. The Analysis Project contains the business process structure, including transactionassignments and assigned check rules. The data is exchanged between the two systems using XML filetransfer methodology.
3. INCIDENT MANAGEMENT
The transfer of support messages (incidents) from one SAP Solution Manager system to another is notsupported. For solution-specific service desk messages (and issues), see chapter0 1. Operations andSolutions,and for project-specific service desk messages (and issues), see chapter Error! Referencesource not found.Error! Reference source not found..
4. CHANGE MANAGEMENT
The transfer of change documents from one SAP Solution Manager system to another is not supported.
5. TEST MANAGEMENT
The Test Workbench includes functionality for transporting test plans and test packages.Test plans and test packages are always transported completely: you cannot transport only the changes thathave been made to them. Test plans and test packages with a transportable package assigned to them canonly be changed if you allow changes to repository objects.The transport connection in the Test Workbench does not include the assignment of test cases and TBOMsto projects. There is no functionality for transporting assignments made to a project. Use the transportfunction in transaction SOLAR_PROJECT_ADMIN to transport the corresponding project separately.The tester assignment, the test status and test-related messages of a test plan are not transported in thestandard, because these entities are specific to systems and clients.
Show how thisprocedureis executed in SAP Solution Manager.
https://service.sap.com/sap/support/notes/1304462https://service.sap.com/sap/support/notes/1304462https://service.sap.com/sap/support/notes/1304462 -
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
9
6. ROOT CAUSE ANALYSIS
There is no tool support for transferring data between SAP Solution Manager systems in the SAP SolutionManager Diagnostics environment. This applies both to configuration data and to the diagnostics datacollected by the agents configured on the managed systems.It is possible, however, to extract the diagnostics data out of the Business Intelligence system in SAPSolution Manager (or a connected one) using standard BI tools. This data can also be re-imported. SAPSolution Manager provides no tool support for this type of data transfer, or to enable the other SAP SolutionManager system to use the transferred data.
7. TECHNICAL DEPENDENCIES
This chapter provides an overview of the technical layer of SAP Solution Manager, and the related aspects oftransferring content.
7.1 System Land scape Directory (SLD)
The System Landscape Directory (SLD) is a technical CIM (common information model) database thatcontains all the informationsuch as server name, SID and product data like SP Stacks or patch levelforthe connected systems. The SLD is a central information provider that can gather this information, and act assingle point of access for the administrator, and tools/services that use this dataThe local SLD of a Solution Manager system is usually connected to one or more central SLDs, which deliverthis information via the SLD bridge to the local SLD of the Solution Manager system. Information exchangewith the central SLD is not possible. A regular job in the Solution Manager system synchronizes the databetween the central and the local SLD. Another job (LANDSCAPE FETCH) synchronizes the local SLD withthe SMSY.When merging systems, you can group SLDs and adapt the usage relationship when you import the contentof one or more SLDs to the new one. For a detailed description, see note 935474.
7.2 RFCs, CCMS, and SCOT
You cannot transport RFC connections, so you need to regenerate all the required RFC connectionssuchas READ, LOGIN or TRUSTED RFCin the new productive SAP Solution Manager system.
CCMS configurations can be transported using a monitoring properties variant.Detailed information can befound here3.
There is no tool for transporting customizing settings in transaction SCOT, and certain system/client-relatedsettings, such as the Default Domain, should not be transported, and must be reconfigured in the newsystem.
7.3 SAP Bus iness Intel l igenc e and Wil y Enterpris e Manager Data
All the data stored in the SAP Business Intelligence system in SAP Solution Manager, or connected to theSAP Solution Manager system as BI storage, can be extracted and imported to another SAP SolutionManager BI, with the SAP Business Intelligence tools (SAP Solution Manager provides no tool forcollecting/exporting data that is relevant to SAP Solution Manager from the SAP Solution Manager BIdirectly). If you have Wily Introscope, you can only merge the data from one or more Enterprise Managers,by full copy. You stop the Enterprise Managers, copy the data directories from the source EnterpriseManager to the target, and restart them. You cannot import additional data from a different IS EM.
7.4 Maintenance Optimizer and License Keys
3http://help.sap.com/saphelp_nw73/helpdata/en/21/5de988166811d294cc00a0c93033f7/frameset.htm
http://help.sap.com/saphelp_nw73/helpdata/en/21/5de988166811d294cc00a0c93033f7/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/21/5de988166811d294cc00a0c93033f7/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/21/5de988166811d294cc00a0c93033f7/frameset.htmhttp://help.sap.com/saphelp_nw73/helpdata/en/21/5de988166811d294cc00a0c93033f7/frameset.htm -
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
10
The transfer of maintenance procedures (Maintenance Optimizer transactions) from one SAP SolutionManager system to another is not supported.For high-security customers, a possible option is to download the license keys with one Solution Managersystem, and transfer them as xml files to a second Solution Manager system.
7.5 Central Performanc e History (CPH)
CPH configuration tables and the CPH transaction data table (cluster table) are also transportable.
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
11
8. HOW TO
8.1.1 Solut ion Transfer
What to do Screen Display
Select the solution totransport, in transactionSOLUTION_TRANSFERin SAP Solution Manager,and mark the items to betransported, in the Scopearea. Choose the transporttarget. Click Next, to startthe export.
Once the export is
completed, you will beprompted to store the filesolution.zip. Save it to thedesignated destination.The transport request IDwill be shown in the statusline.
Put the previously-createdtransport request in thetransport directory of yourSAP Solution Manager,and import it in transactionSTMS.
Execute transactionSOLUTION_TRANSFER.
A browser windows opens.Choose the location of thesolution.zip file, andupload it to the SAP
Solution Manager.
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
12
Returnto topic content
Once, the solution.zip isuploaded, choose theTarget Solution. This is apreviously-created newsolution, or an existingone. Choose the target
logical components, theimport option and thescope. Click Import.
If the transport request hasnot yet been imported, thesystem tells you whichtransport request now hasto be imported.
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
13
8.1.2 Pro ject Trans fer
What to do Screen Display
Select the project totransport, in transactionSOLAR_PROJECT_ADMINin SAP Solution Manager.
Mark the project
Select Transport from thetop menu or click on thetransport icon
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
14
If you choose AllLanguages please refer toSAP note 1742533
Enter a transport request(NOT a local request).
Download the data file ofthis transport request, andupload it into the transportfolders of the SAP SolutionManager. The transport isvisible in the import queue intransaction STMS.
Select transport request and
start the import.
https://service.sap.com/sap/support/notes/1742533https://service.sap.com/sap/support/notes/1742533https://service.sap.com/sap/support/notes/1742533 -
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
15
Returnto topic content
The import can beperformed immediately, orscheduled.
On the Option tab, markIgnore Invalid ComponentVersion (in an upgradefrom SAP SolutionManager 7.01 to 7.1).
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
16
8.1.3 Temp late Transf er
What to do Screen Display
Select the template projectin which you have stored thetemplate to transport, intransactionSOLAR_PROJECT_ADMINin SAP Solution Manager.
Open the template project
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
17
Choose the Template tab,and select the template fromthe list.
Click on Transport
Click on Continue
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
18
Select an option, and clickContinue.
Follow the instruction on thescreen, to select a role ofthe project systemlandscape, and clickContinue.
Choose a transport request/task, and the languages,and click Continue. If youmark the checkbox here,unreleased documents willalso be collected.
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
19
Returnto topic content
If there are local objects,reassign them to atransportable package.
Finished.
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
20
Returnto topic content
8.1.4 Roadm ap Transfer
8.1.5 Solut ion Docum entat ion Assistant
What to do Screen Display
Select the roadmap totransport, in transactionRMDEFin SAP SolutionManager. The context menucontains Transport
Select a transport requestand the content options.
What to do Screen Display
Execute transactionSOLMAN_WORKCENTERin SAP Solution Manager,and choose the work centerSolution Documentation
Assistant. Navigate to theContent Interface andchoose either DownloadCheck Rules or DownloadAnalysis Project, dependingwhat you are going to
export.
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
21
Returnto topic content
a.) Select Download CheckRules, click Search, selectthe Check Steps and clickDownload, to store the zipfile on your PC.
b.) Select DownloadAnalysis Project, select theAnalysis Project, and clickDownload, to store the zipfile on your PC.
To upload the previouslystored zip files (from SAPSolution Manager 7.01 or7.1) execute transactionSOLMAN_WORKCENTER,select the SolutionDocumentation Assistantwork center, navigate to theContent Interface, and clickUpload Content.
Select the previously storedzip files, and click Start, toimport the content.
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
SAP SOLUTION MANAGERCONTENT TRANSFER
22
Returnto topic content
8.1.6 Test plan Tran sfer
What to do Screen Display
Select the test plan totransport, in transactionSOLMAN_WORKCENTER,in SAP Solution Manager. Inthe menu Test Plan,choose Transport TestPlan.
Select the objects to betransported, and click on
Transport.Fill in a transport request (orcreate a new one).
-
5/21/2018 SM 7.1-HowTo - Transfer Content Between SAP Solution Manager Systems - slidep...
http:///reader/full/sm-71-howto-transfer-content-between-sap-solution-manag
2012 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAPBusinessObjects Explorer, StreamWork, SAP HANA, and other SAP
products and services mentioned herein as well as their respectivelogos are trademarks or registered trademarks of SAP AG in Germanyand other countries.
Business Objects and the Business Objects logo, BusinessObjects,
Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, andother Business Objects products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAPcompany.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL
Anywhere, and other Sybase products and services mentioned hereinas well as their respective logos are trademarks or registered
trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are
registered trademarks of Crossgate AG in Germany and other
countries. Crossgate 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 ofany 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.
www.sap.com