38
Page 1 Portal © SAP 2008 / LES Portal Advanced Page 2 Introduction Migration Strategy SRM Business Packages Portal Connections User Authentication & SSO Configuration Portal Roles & Users UWL Configuration Netweaver Business Client Appendix – Multiple SRM Integration Agenda sample for a picture in the divider slide

Portal

Embed Size (px)

Citation preview

Page 1: Portal

Page 1

Portal

© SAP 2008 / LES Portal Advanced Page 2

IntroductionMigration StrategySRM Business PackagesPortal ConnectionsUser Authentication & SSO ConfigurationPortal Roles & UsersUWL ConfigurationNetweaver Business ClientAppendix – Multiple SRM Integration

Agenda

sample for a picture

in the divider slide

Page 2: Portal

Page 2

© SAP 2008 / LES Portal Advanced Page 3

IntroductionMigration StrategySRM Business PackagesPortal ConnectionsUser Authentication & SSO ConfigurationPortal Roles & UsersUWL ConfigurationNetweaver Business ClientAppendix – Multiple SRM Integration

Agenda

sample for a picture

in the divider slide

© SAP 2008 / LES Portal Advanced Page 4

SAP Netweaver Portal - Introduction

The SAP NetWeaver Portal 7.0 (2004s) SP17Portal Version 7.0Netweaver 2004sSupport Package 17EHP1 Enhancement Package 1

Page 3: Portal

Page 3

© SAP 2008 / LES Portal Advanced Page 5

SAP Netweaver Portal - Introduction

© SAP 2008 / LES Portal Advanced Page 6

IntroductionMigration StrategySRM Business PackagesPortal ConnectionsUser Authentication & SSO ConfigurationPortal Roles & UsersUWL ConfigurationNetweaver Business ClientAppendix – Multiple SRM Integration

Agenda

sample for a picture

in the divider slide

Page 4: Portal

Page 4

© SAP 2008 / LES Portal Advanced Page 7

Portal 7.0 – Migration Strategy

Portal layerBusiness package

for mySAP SRM 7.0Portal core

Portal 6.0 on Web AS 6.40Business package

for mySAP SRM 5.0Portal core Portal core

Portal layerBusiness packagefor mySAPSRM 7.0Portal core

Portal 7.0 on SAP NW 7.0*2 - New Business packages

for SAP SRM 7.01 - New Portal Core Portal core5 - Customized Content

PersonalizationNews & Articles

Collaboration

Document

Page Building Cust. iViews

*Portal 7.0 on SAP NW has specific requirements for sizing, performance, scalability across multiple servers and load-balancing

Customized Content

3 - Export the customized content

4 - Import the customized content

SAP BW 7.0

BI_CONT 7.0.3

Basis plug-in

mySAP SRM7.0 server

WD SAP R/3 back-endsystem

SAP R/3 plug-in

FI/CO

http(s)

SAP BW

BI_CONT

Basis plug-in

mySAP SRM 5.0

WD SAP R/3 back-endsystem

SAP R/3 plug-in

FI/CO

http(s)

SAP BW 7.0

BI_CONT 7.0.3

Basis plug-in

mySAP SRM7.0 server

WD SAP R/3 back-endsystem

SAP R/3 plug-in

FI/CO

http(s)

SAP BI

BI_CONT

Basis plug-in

SAP SRM 70

WD ECC back -endsystem

SAP ECC plug-in

FI/CO

http(s)

© SAP 2008 / LES Portal Advanced Page 8

IntroductionMigration StrategySRM Business PackagesPortal ConnectionsUser Authentication & SSO ConfigurationPortal Roles & UsersUWL ConfigurationNetweaver Business ClientAppendix – Multiple SRM Integration

Agenda

sample for a picture

in the divider slide

Page 5: Portal

Page 5

© SAP 2008 / LES Portal Advanced Page 9

Business Package for SAP SRM 7.0 - Offerings

The business package for SAP SRM 7.0offers

Predefined portal content and roles for SRM-relatedbusiness processes

Predefined integration with SAP applications and singlesign-on to these applications.

A solution for portal user administration when variousbackend systems are deployed

Ongoing development of additional features with apredefined, reliable release schedule

A fully tested business packageSAP Consulting and customer support

Comprehensive SAP documentation within SAP SolutionManager

© SAP 2008 / LES Portal Advanced Page 10

Business Package for SAP SRM 7.0 - Offerings

The business package includes different roles for specialists in theprocurement process like

Strategic purchaser

Operational Purchaser

Purchasing assistant

Purchasing Manager etc.

Page 6: Portal

Page 6

© SAP 2008 / LES Portal Advanced Page 11

Business Package – Configuration Process

* Will be demonstrated in the Portal Advance Workshop

DownloadBusiness Package

FollowImportant

Instructionsfrom

SAP Notes

DeployBusinessPackage

Into Portal*

Checkthe

Deployment

Customizethe std.Roles and

BusinessObjects

© SAP 2008 / LES Portal Advanced Page 12

Business Package for SAP SRM 7.0 - Where tofind?

Use SAP Solution Manager for downloading the EP BusinessPackages. See the path described below:

Page 7: Portal

Page 7

© SAP 2008 / LES Portal Advanced Page 13

JSPM - Java Support Package ManagerIntroduction

New NetWeaver 2004s Tool: Java Support Package Manager (JSPM)JSPM is automatically deployed as part of every AS-JAVA usage type(as of NetWeaver 2004s)JSPM uses the former SAP deployment tool SDM (Software Delivery Manager) as underlying layer

Most important JSPM features:Displays support package level informationChecks dependencies between versions of software components

Checks whether a new software component version may correctly upgrade an existing software componentversion

Checks deployment dependencies between development components

Allows you to update kernel binaries and the SDM itself

Allows you to apply - a support package stack, single support packages, new software components that arenot part of an SAP usage type

Informs you if restarting of the J2EE Engine is necessary during the deployment process

Allows you to restart the deployment of support packages

© SAP 2008 / LES Portal Advanced Page 14

JSPM – Startup and Logon

Execute „go.bat“ in the <instance>\j2ee\JSPM directory to launch JSPM

Enter SDM Administrator password, so that JSPM can connect to SDM

Page 8: Portal

Page 8

© SAP 2008 / LES Portal Advanced Page 15

JSPM – Deployment Options

Choose „Deployment“, and then „New Software Components“ to apply newJava components to an existing system

© SAP 2008 / LES Portal Advanced Page 16

SDM – Deploy Business Package SRM 7.0

Page 9: Portal

Page 9

© SAP 2008 / LES Portal Advanced Page 17

SDM – Deploy Business Package SRM 7.0

© SAP 2008 / LES Portal Advanced Page 18

SDM – Deploy Business Package SRM 7.0

Page 10: Portal

Page 10

© SAP 2008 / LES Portal Advanced Page 19

Checking the Deployment

Logon to your portal with an administrator user, go to Content Administration -> PortalContent.The following objects should be added to your portal content:

Logon to your portal with an administrator user, go to Content Administration -> PortalContent.The following objects should be added to your portal content:

© SAP 2008 / LES Portal Advanced Page 20

Demo - Creating a new portal iView

Select iViewtemplate

Create portaliView

Edit the portaliView for definingparameters etc

Pick up theiView andadd to

navigation

Page 11: Portal

Page 11

© SAP 2008 / LES Portal Advanced Page 21

Creating a new portal iView

© SAP 2008 / LES Portal Advanced Page 22

Creating a new portal iView

Page 12: Portal

Page 12

© SAP 2008 / LES Portal Advanced Page 23

Creating a new portal iView

© SAP 2008 / LES Portal Advanced Page 24

Creating a new portal iView

Page 13: Portal

Page 13

© SAP 2008 / LES Portal Advanced Page 25

Creating a new portal iView

© SAP 2008 / LES Portal Advanced Page 26

Creating a new portal iView

Page 14: Portal

Page 14

© SAP 2008 / LES Portal Advanced Page 27

Creating a new portal iView

© SAP 2008 / LES Portal Advanced Page 28

Creating a new portal iView

Page 15: Portal

Page 15

© SAP 2008 / LES Portal Advanced Page 29

Creating a new portal iView

© SAP 2008 / LES Portal Advanced Page 30

Creating a new portal iView

Page 16: Portal

Page 16

© SAP 2008 / LES Portal Advanced Page 31

Creating a new portal iView

© SAP 2008 / LES Portal Advanced Page 32

IntroductionMigration StrategySRM Business PackagesPortal ConnectionsUser Authentication & SSO ConfigurationPortal Roles & UsersUWL ConfigurationNetweaver Business ClientAppendix – Multiple SRM Integration

Agenda

sample for a picture

in the divider slide

Page 17: Portal

Page 17

© SAP 2008 / LES Portal Advanced Page 33

Systems and System Aliases

To use the Business Package for SAP SRM 7.0, you must create a system object in the Portal toestablish a connection to the SAP SRM 7.0 server. You must assign the alias SAP_SRM to thissystem object.

For the Business Intelligence (BI) Reports to be displayed, you must create an additional systemobject which points to a SAP BI system. You must assign the alias SAP_BW to this systemobject.

This following slides outline how to configure the following:Creating System ObjectsConfiguring System Objects for Backend SystemsCreating and Adding a Backend System Alias

SAP BW 7.0

BI_CONT 7.0.3

Basis plug-in

SAP SRM2007 server

WD

EBP

SAP R/3 back-endsystem

SAP R/3 plug-in

FI/CO

Portal layerBusiness packagefor SAP SRM 7.0

http(s)

Portal core

© SAP 2008 / LES Portal Advanced Page 34

Connection to AS-ABAP (in SRM System)

Page 18: Portal

Page 18

© SAP 2008 / LES Portal Advanced Page 35

Connection to AS-ABAP (in SRM System)

Press next and open the newsystem for editing

© SAP 2008 / LES Portal Advanced Page 36

Connection to AS-ABAP (in SRM System)

1

2

3

Page 19: Portal

Page 19

© SAP 2008 / LES Portal Advanced Page 37

Connection Alias to SRM System

The portal alias is an unique alias namerepresenting a system connected to the

portal.

© SAP 2008 / LES Portal Advanced Page 38

Performing a Connection Test

Page 20: Portal

Page 20

© SAP 2008 / LES Portal Advanced Page 39

IntroductionMigration StrategySRM Business PackagesPortal ConnectionsUser Authentication & SSO ConfigurationPortal Roles & UsersUWL ConfigurationNetweaver Business ClientAppendix – Multiple SRM Integration

Agenda

sample for a picture

in the divider slide

© SAP 2008 / LES Portal Advanced Page 40

Portal WebDynpro User Authentication

SAP SRM Server (AS-ABAP)

Certificate

User: ABC

BP-SRM

AS-JAVA

Enterprise Portal

WebDynpro Application

User: ABC

Important facts:Identical user name in all systemsLocal assignment to roles/authentications

Page 21: Portal

Page 21

© SAP 2008 / LES Portal Advanced Page 41

Certificate Configuration

ABAPJ2EE

Enterprise Portal+ Web Dynpro Java

System

SRMSystem

1. Create Portal Certificate2. Export Portal Certificate1. Create Portal Certificate2. Export Portal Certificate

3. Import Portal Certificate4. Distribute Portal Certificate3. Import Portal Certificate4. Distribute Portal Certificate

For a detailed description, see SAP Note 711768For a detailed description, see SAP Note 711768

To implement Single Sign-On(SSO),Certificates must be createdand distributed

To implement Single Sign-On(SSO),Certificates must be createdand distributed

© SAP 2008 / LES Portal Advanced Page 42

Enterprise Portal - Create Portal Certificate

Create a new Portalcertificate, by using the“Keystore Administration”utility in the Enterprise Portal

Create a new Portalcertificate, by using the“Keystore Administration”utility in the Enterprise Portal

2

1

Page 22: Portal

Page 22

© SAP 2008 / LES Portal Advanced Page 43

SRM System - Import Portal Certificate

Import the Portal Certifcate (Example: KTP.cert) into the backendsystem (/nSTRUSTSSO2)

Choose type “Base64” and “Add to certificate List”

Now, the new System (here:KTP) appears in the SSO List

Import the Portal Certifcate (Example: KTP.cert) into the backendsystem (/nSTRUSTSSO2)

Choose type “Base64” and “Add to certificate List”

Now, the new System (here:KTP) appears in the SSO List

3

2

1

4

© SAP 2008 / LES Portal Advanced Page 44

SAP SRM System – Distribute Certificate

Do not forget to distribute the CertificatesDo not forget to distribute the Certificates

1

Page 23: Portal

Page 23

© SAP 2008 / LES Portal Advanced Page 45

SAP SRM System – Check SSO ProfileParameters

Parameter : login/accept_sso2_ticket = 1Parameter : login/create_sso2_ticket = 2

Example: login/accept_sso2_ticket:

Description:You can use SSO tickets to allow Single Sign-On (SSO) between SAP systems, and even beyond to non-SAP systems.

An SSO ticket can be a logon ticket or an assertion ticket. The logon ticket is transferred as a cookie with thename MYSAPSSO2.The assertion ticket is transferred as an HTTP header variable with the nameMYSAPSSO2.

SSO component systems should permit logon by SSO ticket (login/accept_sso2_ticket = 1).

Procedure (for all involved SAP systems):

1. Logon to the SRM system via SAPGui

2. Open transaction /nrz10 (Edit profiles)

3. Display your R3 instance profile (extenden maintenance option)

4. Check both parameters and create them if not available

© SAP 2008 / LES Portal Advanced Page 46

SAP SRM System – Check SSO ProfileParameters

1

2

3

4

Page 24: Portal

Page 24

© SAP 2008 / LES Portal Advanced Page 47

IntroductionMigration StrategySRM Business PackagesPortal ConnectionsUser Authentication & SSO ConfigurationPortal Roles & UsersUWL ConfigurationNetweaver Business ClientAppendix – Multiple SRM Systems

Agenda

sample for a picture

in the divider slide

© SAP 2008 / LES Portal Advanced Page 48

User Management Scenarios

There are a number of potential scenarios for User Management:Use Application Server ABAP as Data SourceUse Database as Data SourceUse LDAP Directory as Data Source

Enterprise Portal

UME

ABAP DataSource

LDAP DataSource

Local DB

Page 25: Portal

Page 25

© SAP 2008 / LES Portal Advanced Page 49

User Management Scenario – ABAP datasource

Users accessed from the ABAP data sourceAdd the ECC roles and SRM roles for a User and assign portal roles in the Enterprise Portal

Logon to ECC systemAdd the roles for this user in the ECC systemLogon to the SRM systemAdd the roles for this user in the SRM SystemLogon to the Enterprise Portal and access the user through the User Administration tab (as a PortalAdministrator)ECC roles and the SRM roles appear as Assigned groups for the user in the Enterprise PortalAssign the appropriate portal roles for this user to access the content of the Business Package forSRM7.0

Enterprise Portal(Assign Portal roles)ECC roles as *Groups*SRM roles as *Groups*

SRM system(Assign roles)(PPOMA_BBP user attributes)

ECC System(Assign roles)

User ABC

User ABC User ABC

© SAP 2008 / LES Portal Advanced Page 50

IntroductionMigration StrategySRM Business PackagesPortal ConnectionsUser Authentication & SSO ConfigurationPortal Roles & UsersUWL ConfigurationNetweaver Business ClientAppendix – Multiple SRM Systems

Agenda

sample for a picture

in the divider slide

Page 26: Portal

Page 26

© SAP 2008 / LES Portal Advanced Page 51

Universal Worklist - Feature Overview

The Universal Worklist enables SAP portal users to manage their workby bringing together assignments from different workflow systems.Features of the UWL are:

Gives you a unified and centralized way to access your work and the relevantinformation

Aggregates workflow task items from multiple and different systems in oneuniversal list (example: SRM, ESS, etc..)

Displays additional information as required from document and objectrepositories, including attachments and other details

Enables you to make direct decisions and actions

Helps you to personalize how work items are presented

Enables you to assign another user to your work items as a substitute in caseof planned or unplanned absence

© SAP 2008 / LES Portal Advanced Page 52

Configure the Universal Worklist (UWL)

Configure the Universal Worklist for the Business Package for mySAP SRM 7.0A system connection for the SRM backend must already existCreate the UWL system: System Administration System Configuration Universal Worklist &Workflow Universal Worklist Administration NewRegister the UWL system under: System Administration System Configuration UniversalWorklist & Workflow Universal Worklist Administration

Page 27: Portal

Page 27

© SAP 2008 / LES Portal Advanced Page 53

Change UWL configuration

With SRM 7.0 an own UWL Configuration file is delivered for displaying alerts and tasks within the UWLiView.

The UWL Configuration File is delivered as part of the SRM 7.0 Business Package(Configuration Name: com.sap.pct.srm.core).

Download the configuration file (in zip-format) to your local machine. Goto SystemAdministration System Configuration Universal Worklist & Workflow UniversalWorklist Administration Click to Administrate Item Types and View definitions

© SAP 2008 / LES Portal Advanced Page 54

Change UWL configuration – rename tab entrypoints

As an example let’s change the name of the tab names. “My Alerts” should be displaydinstead of “Alerts”. The names of tabs are specified in the corresponding language fileswithin the UWL configuration zip-file. For example, pick up the english language filecom.sap.pct.srm.core_en.properties to do this.

Page 28: Portal

Page 28

© SAP 2008 / LES Portal Advanced Page 55

Change UWL configuration – tab entries

Change the name to „myAlerts“, save it and put it

back to the UWLconfiguration file.

© SAP 2008 / LES Portal Advanced Page 56

Upload new UWL configuration

After changing the XML file, put the XML configuration file into the zip-archive andupload the modified version into the Portal.

Goto “Upload New Configuration”, specify the configuration name, pick up the zip-fileand upload it to the portal, press “yes, if you are asked to overwrite the currentconfiguration.

Page 29: Portal

Page 29

© SAP 2008 / LES Portal Advanced Page 57

Change UWL configuration – rename tab entrypoints

Result: name of the tab changed to My Alerts

Recommendation: to makes sure that your configuration won’t be overwritten after a Business Packageupdate, simply change the configuration name and the configuration zip file. Upload the newconfiguration to your portal.Example: com.sap.pct.srm.core.customer and com.sap.pct.srm.core.customer.zip

© SAP 2008 / LES Portal Advanced Page 58

Change UWL configuration – disable tab entrypoints

Example: disable notification tab

Solution:1. open the com.sap.pct.srm.core.xml file and goto entry Tab: Notification2. delete the entries for notifications and save your file3. put the com.sap.pct.srm.core.xml file back to your zip archive and upload the configuration

Page 30: Portal

Page 30

© SAP 2008 / LES Portal Advanced Page 59

IntroductionMigration StrategySRM Business PackagesPortal ConnectionsUser Authentication & SSO ConfigurationPortal Roles & UsersUWL ConfigurationNetweaver Business ClientAppendix – Multiple SRM Systems

Agenda

sample for a picture

in the divider slide

© SAP 2008 / LES Portal Advanced Page 60

Using SAP Netweaver Business Client in SRM7.0About SAP Netweaver Business Client:

The SAP NetWeaver Business Client (NWBC) is a new, desktop-based SAPintegration platform that provides end users with a seamless integration of portal-based transactions, classic SAP GUI-based transactions, and new applicationsdeveloped in Web Dynpro (ABAP and Java).

Existing browser-based SAP applications can also be integrated.

With the new UI front end of the Business Client existing UI portal services such asroles and navigation can be reused.

The NetWeaver Business Client is user interface (UI) software running on the desktopthat communicates via HTTP(s) to a server in order to display application interfaces.The interfaces make it easy for the user to start the required application.

Fully supported by Business Suite applications.

Page 31: Portal

Page 31

© SAP 2008 / LES Portal Advanced Page 61

Using SAP Netweaver Business Client in SRM7.0Main Components of Business Client UI:

The frame contains standard menu entries in the upper area, and miniature images ofopen sessions and transactions that enable simple navigation between screens(session tab area). The left part of the screen contains the role-based functions for theuser (home area).

The actual transaction the user is working in is displayed on the canvas or applicationcontent area. The canvas represents the native technology in which the sourceapplication created its screens.

Practically all standard UI technologies can be presented on a canvas:

Portal applications

Web Dynpro ABAP/Java applications

BSP Applications

HTML pages, Interactive forms and print forms (pdf)

Dynpro screens based on the classic dynpro programming model of SAP

© SAP 2008 / LES Portal Advanced Page 62

Using SAP Netweaver Business Client in SRM7.0

Page 32: Portal

Page 32

© SAP 2008 / LES Portal Advanced Page 63

Working with the SAP Netweaver BusinessClientBefore you start:

Install the SAP Netweaver Business Client Software on your local machine. Pleasefollow the documentation on SAP Service Marketplace.

Or, logon to the SAP Citrix Client. You will find a SAP Netweaver Business ClientInstallation on your desktop.

Double klick on theSAP Netweaver

Business Client Iconon your desktop

© SAP 2008 / LES Portal Advanced Page 64

Working with the SAP Netweaver BusinessClient

In the first step you have toconnect the Business Client

to your SRM 7.0 system.

Page 33: Portal

Page 33

© SAP 2008 / LES Portal Advanced Page 65

Working with the SAP Netweaver BusinessClient

© SAP 2008 / LES Portal Advanced Page 66

Working with the SAP Netweaver BusinessClient

Select your SRM system andpress „Switch To“.

Now, you will be asked foruser/password.

Page 34: Portal

Page 34

© SAP 2008 / LES Portal Advanced Page 67

Working with the SAP Netweaver BusinessClient

© SAP 2008 / LES Portal Advanced Page 68

Working with the SAP Netweaver Business Client

Page 35: Portal

Page 35

© SAP 2008 / LES Portal Advanced Page 69

Additional Informations

SAP Netweaver Business Client help pages

NWBC Wiki pages:http://nwbc.wdf.sap.corp:1080/

SAP Help:http://help.sap.com/saphelp_nw70/helpdata/EN/46/961aa951b3581ce10000000a1553f7/frameset.htm

© SAP 2008 / LES Portal Advanced Page 70

IntroductionMigration StrategySRM Business PackagesPortal ConnectionsUser Authentication & SSO ConfigurationPortal Roles & UsersUWL ConfigurationNetweaver Business ClientAppendix – Multiple SRM Systems

Agenda

sample for a picture

in the divider slide

Page 36: Portal

Page 36

© SAP 2008 / LES Portal Advanced Page 71

Example: Integration of two SRM 7.0 systemsinto a single portal instance

PortalInstance

SRM 7.0 System 1(Development)

SRM 7.0 System 2(Q-System)

User 1

User 2

Logon to portal

Logon to portal

Redirect toSRM System1

Redirect toSRM System2

Alias 1

Alias 2

© SAP 2008 / LES Portal Advanced Page 72

Example: one portal and two SRM 7.0 systems

Prerequisites:SRM 7.0 SP01/SP02

SRM users are unique, means you don’t have the same user ID in different SRMsystems.

SRM 7.0 Business Package SP01/SP02 deployed

Single-Sign-On is configured as described in Solution Manager

Steps in detail:1. Create two SRM 7.0 systems with two alias names. An alias is an unique

identifier for every system connected to the portal.

2. Create two UWL system connections based on the alias names used in step 1.

3. Create a new portal folder for new content

Page 37: Portal

Page 37

© SAP 2008 / LES Portal Advanced Page 73

Example: one portal and two SRM 7.0 systems

Steps in detail:

4. Copy all SRM 7.0 roles to the new portal folder (Delta Copy).

5. Change ID and names of the copied roles.

6. Change the default alias SAP_SRM for all iViews which are linked tothe copied roles.

7. Assign new roles to portal users

8. Test connections

Demo-Portal:http://p190963.wdf.sap.corp:50000/irj/portal

Demo-User: de_manager/training and maneu/training

* Check the Appendix - 1 for a detailed step-by-step instructions

© SAP 2008 / LES Portal Advanced Page 74

Further Information

Related SAP Education and Certification Opportunitieshttp://www.sap.com/education/

SAP Public Web:SAP Developer Network (SDN): http://www.sdn.sap.com/General Portal Information: https://www.sdn.sap.com/irj/sdn/netweaverPortal on SDN: http://www.sdn.sap.com/irj/sdn/nw-portalandcollaborationSAP Help Portal: http://help.sap.com/Search for SAP Notes: http://service.sap.com/notesProduct Availability Matrix http://service.sap.com/pamSP Stack Schedule http://service.sap.com/sp-stackshttp://www.sap.com/platform/netweaver/itpractices/userproductivity.epx

Page 38: Portal

Page 38

© SAP 2008 / LES Portal Advanced Page 75

Copyright 2008 SAP AGAll Rights ReservedNo 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 changedwithout prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius and other Business Objects products and services mentionedherein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in several other countries. Business Objects is an SAPCompany. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior writtenpermission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies,developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note thatthis document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant theaccuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express orimplied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitationshall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie diedazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Business Objects und das Business-Objects-Logo,BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius und andere im Text erwähnte Business-Objects-Produkte und -Dienstleistungen sowie die entsprechendenLogos sind Marken oder eingetragene Marken der Business Objects S. A. in den USA und anderen Ländern weltweit. Business Objects ist ein Unternehmen der SAP. Alle anderen in diesemDokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich unddienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Formauch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet. Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertragoder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts. SAP entsteht aus dieserPublikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherigeAnkündigung geändert werden.SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte,Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a.,aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialienentstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen,unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über InternetseitenDritter ab.Alle Rechte vorbehalten.