Srm 600 Architecture

5/21/2018 Srm 600 Architecture

1/21

SAP AG 1

SAP AG2005

SRM 6.0 Architecture


2/21

SAP AG 2

SAP AG2006

Objectives

Contents

mySAP SRM Architecture

Objectives

At the end of this chapter, you will be able to:

Understand the SAP NetWeaver usage types and what is

relevant to SRM 6.0

Understand the different components available in SRM 6.0

List the necessary components per SRM Scenario

Describe which components are using the ABAP Stack, and

which the J2EE Stack

Explain the system landscapes per scenario


3/21

SAP AG 3

SAP AG2006

Systems with Usage Types Standalone Engines

Usage Type,

for Example AS-ABAP

Standalone Engine

for Example AS-JAVA

Standalone Engine

for Example TREX

Usage Type,

for example EP

Standalone Engine

for Example AS-ABAP

Usage Type,

for example SRM

Usage Type,

for example AS-JAVA

SAP NetWeaver 2004s Usage Types

Systems are the main building blocks of SAP NetWeaver

They are identified by unique system IDs (SAPSID) and configured for

a certain purpose, as indicated by Usage Types

When necessary, systems can be extended by further Usage Types

Usage Type,

for example ECC 6.0Usage Type E

for example AS-ABAP

*) For more information on Usage Types, see Learning Map Technical Concepts for mySAP ERP 2005, Unit Usage Types

depends on

Usage types:

Are a new structuring element for SAP software on a technical level

Determine the intended purpose of a system and the role it plays in a given (distributed) IT scenario

Describe how (an installation of) SAP NetWeaver is used and which capabilities are offered to the

overall IT landscape

Represent the installed (part of an) SAP NetWeaver system with basic configuration

Represent the capabilities offered by a collection of installed and configured (technical) software

components

Are built from technical software components

May require other usage types in the same system to operate

Can optionally be run in one system also with usage types that they do not require to operate


4/21

SAP AG 4

SAP AG2006

Mapping of Usage Types in SAP NetWeaver 2004s

AS-JAVAAS-JAVAApplication Server JavaWeb AS

AS-ABAPAS-ABAPApplication Server

ABAPWeb AS

AS-ABAP

AS-JAVAPIProcess IntegrationXI + Web AS

AS-JAVAEPEnterprise PortalEP

AS-ABAP

AS-JAVAMIMobile InfrastructureWeb AS

AS-JAVADIDevelopment

Infrastructure

Web AS + certain

Java comp.

AS-JAVABI-JavaBI Java ComponentsBW + Web AS

BW

Previous NW

components

providing certain

capabilities

Business Intelligence

Usage Type with

SAP NetWeaver

2004s

BI

Short name

AS-ABAP

Required

Usage Type

This graphics shows the dependencies between SAP NetWeaver 2004s usage types.

Example:

The usage Type Process Integration (PI), which requires the usage type AS-ABAP and AS-JAVA

In other words, an SAP XI system runs on an SAP WebAS where the ABAP and the Java Stack must be

installed


5/21

SAP AG 5

SAP AG 2006

Usage Types Relevant for SRM 6.0

AS-JAVALAC WPSSAP Live Auctioning Cockpit

AS-JAVAcProject SuiteSAP Cproject Suite

AS-ABAPAS-ABAPApplication Server ABAP

AS-ABAP, [AS-JAVA]Solution ManagerSAP Solution Manager

AS-ABAP, [AS-JAVA]BISAP NW Business Intelligence

None (C/C++ based)TREXSAP SRM (WITH SAP EBP) [TREX]

AS-JAVAEPSAP NW Enterprise Portal

AS-JAVAAS-JAVAApplication Server Java

AS-ABAP, AS-JAVAPISAP NW Process Integration

EPBP-SRMSAP NW Enterprise Portal Content

AS-ABAP3.1I, 4.6C recomm.SAP OLTP Backend System

AS-JAVAMDMSRM-MDM Catalog

AS-ABAPSRM ServerSAP SRM SUS & BIDDING ENGINE

SAP SRM (WITH SAP EBP)

Usage Type

SRM Server

Short name

AS-ABAP

Required Usage Type

SAP SRM

The SAP Supplier Relationship Management Server (SAP SRM Server) includes both SAP Enterprise

Buyer and SAP Bidding Engine.

OLTP System

Online transaction processing system (for example, SAP ERP system) that is used in the SAP Enterprise

Buyer environment as a backend system. It is used for materials management and financials. Data is

exchanged between the SAP Enterprise Buyer system and a connected OLTP system. It is possible to

install the SAP Enterprise Buyer system without an OLTP backend in a standalone configuration

SAP NW Business Intelligence BI provides the foundation for the SRM scenario Spend Analysis, and can optionally be installed for the

others. BI includes the complete ABAP stack of the SAP NetWeaver BI data warehouse and BI

platform units. BI requires AS-ABAP as prerequisite in the same system. Usually, scenarios running on

BI also require BI-Java, AS-Java and EP. Other combinations can be used in one system as well.

SAP NetWeaver Enterprise Portal

SAP NetWeaver Portal serves as a single point of entry to the applications, services, and information of

the organization. Running an Enterprise Portal is an IT scenario whose implementation provides role-

based and secure access to all types of applications, services, and information in an enterprise portal

environment.

Live Auction Cockpit Web Presentation Server

Live Auction Cockpit Web Presentation Server is a J2EE-based software unit, which provides functions

for virtual auctions, bidding, chatting and so on.


6/21

SAP AG 6

SAP NetWeaver Search and Classification (TREX)

TREX services include search and retrieval in large document collections, text mining, automatic

document classification, and search and aggregation over structured data in SAP applications.

SRM-MDM Catalog

The SRM-MDM Catalog is a software component based on SAP NetWeaver MDM technology. It

combines SAP MDM Server 6.0 with a Java-based and SRM-specific search environment. The CatalogManager imports, structures and adjusts the catalog content. He provides for usergroup-specific masks

and after the content has been confirmed by the Catalog Content Approver enables the content to be

accessible for the catalog users via Web browser.

SAP NetWeaver Process Integration (PI)

SAP NetWeaver Process Integration (PI) consists of core components to model, design, automate, and

integrate the processes of one or more application systems. For the integration of internal and cross-

company processes, PI is used to incorporate all the functions of what was formerly known as Exchange

Infrastructure (XI). In addition, PI contains core components for Business Process Management for

application-embedded and application-unbounded processes.

Please Note: Separate licensing is required for SAP NetWeaver Process Integration if mySAP SRM isused to connect with non-SAP systems or with external trading partners.


7/21

SAP AG 7

SAP AG 2006

Legend

LAC

WPS

SRM

Server

TCP / IP

XML

Transfer protocol type

ABAP based software component

JAVA based software component

Document format type

Application Platform

Technology Platform

TREX C/C++ based software component

EBP Subcomponent (no own installation procedure)

Optional software component


8/21

SAP AG 8

SAP AG 2006

SAP WebAS Java 7.0SAP WebAS ABAP 7.0 (incl. ITS 7.0)

SAP NetWeaver Portal 7.0

SAP NetWeaver AS Java 7.0

SAP NetWeaver Exchange Infrastructure 7.0 (SAP NetWeaver XI 7.0)

SAP WebAS ABAP 7.0 SAP WebAS JAVA 7.0

SAP SRM Server 6.0

EBP

Bidding Engine

SUS

LAC WPS

6.0

JCo

SAP

NetWeaver

BI 7.0 TREX 7.0

Application Platform (incl. SAP IPC 7.0)

cprojects

4.0

SRM MDM

Catalog 1.0

SRM MDM

Catalog UI

MDM 5.5

Duet

1.0

SAP SRM 6.0 Components Overview

Please Note: You cannot connect an XI 3.0 to SRM 6.0. This combination is not supported.

IPC 7.0 is part of the component AP 7.0

No R/3 Plug-ins are needed for ERP 2.0 and higher


9/21

SAP AG 9

SAP AG 2006

SAP SRM 6.0 Scenario Component Matrix

OOOMOSAP Netweaver TREX 7.0

O

O

O

O

O

M

O

O

M

M

M*)MDuet 1.0 and SAP Document Builder

MOMOOSAP NW Adobe Document Server 7.0

MOOcProjects 4.0

MOOOOOXI Content for SRM MDM Catalog 1.0

MOOOOXI Content for SAP NetWeaver BI

Content 7.0.3

MOOMMOXI Content for SAP SRM Server 6.0

MOMOOOOOBusiness Packages for Category Mgmt.

MMMMMMMMBusiness Package for SRM Server 6.0

MMOMMOOOSAP NetWeaver BI_CONT 7.0.3

MMOMOOMSRM-MDM Catalog 1.0

MLive Auction Cockpit (LACWPS) 6.0

MMMMMMMMMSAP SRM Server 6.0

NetWeaver componentsSRM standard scenarios

SelfSer

vice

Procure

ment

PlanDriven

Procure

ment

Service

Procurement

Catalog

ContentMgmt.

Analytic

s

Categor

yManagement

Contrac

tManagement

WebAS

ABAP7.0

SAPITS

7.0

WebAS

Java7.0

MDM5.5

BI7.0

EP7.0

PI7.0

Legend:

O = optional

M = mandatory

Legend:

O = optional

M = mandatory

StrategicSourcing

Please see the SRM Master Guide for more detailed and complete information.

O = optional, Business or technology enhancement for this scenario

M = mandatory, Minimum requirement for the deployment variants of this scenario

The following WebAS Java 7.0 based components can be deployed on the Enterprise Portal

LAC WPS 6.0

ADS 7.0

cProjects 4.0

Duet 1.0 and SAP Document Builder are only required for Contract Management, when Legal &Operational Contract Collaboration is implemented.

*) For Duet 1.0, Web AS 6.40 is required


10/21

SAP AG 10

SAP AG 2006

SAP NetWeaver: Process Integration 7.0

Self-Service Procurement

Firewall

http(s)

http(s)

http(s) / OCI

SRM-MDM Catalog 1.0

SAP NWMDM

console

SAP NWMDM data

manager

SAP NWMDM import

manager

SRM-MDM

Catalog:

search

(Web Dynpro)

SAP NW

MDM

server

SAP NWMDM

import server

SAP BW 7.0

BI_CONT 7.0.3

Basis plug-in

mySAP

SRM 6.0

server

WD

EBP

IPC 7.0

ADS

SAP R/3 back-endsystem

SAP R/3 plug-in

FI/CO

Portal layer

SAP NetWeaver

XI integration

engine

SAP NetWeaverXI integrationengine

Application gateway

MM

IDoc

SAP NetWeaverXIproxy

framework

SAP NetWeaverXI integration

engine

SAP NetWeaver XI contentfor SRM-MDM Catalog SAP NetWeaver XI content for mySAP SRM 6.0 server

TCP / FTP(s)

XML

XML

Business package

for mySAP SRM 6.0

RFC

http(s) / OCI

http(s)

RFC

Portal core

IPC 7.0 is part of SAP WebAS

On the Portal layer, is is sufficient to deploy the Portal Core components (no KM, collaboration room are

required)

ADS can be deployed on the Portal

The Business Packages shown on this slide are:

BPSRM00_0.sca (BP for mySAP SRM 6.0)

The XI Content Packages shown on this slide are:

SRMSERV6000_0.ZIP (XI Content for SRM 6.0 Server)

SRMMDMCAT1000_0.ZIP (XI Content for SRM-MDM Catalog)


No R/3 Plug-ins needed for mySAP ERP 2005 (ECC 6.0) and higher.


11/21

SAP AG 11

SAP AG 2006

SAP NetWeaver: process integration 7.0

Plan-Driven Procurement

SRM-MDM Catalog 1.0

SAP NWMDM

console

SAP NWMDM data

manager

SAP NWMDM import

manager

SRM-MDM

Catalog:

search

(Web Dynpro)

SAP NetWeaver

MDM

server

SAP NetWeaverMDM

import server

SAP BW 7.0

BI_CONT 7.0.3

Basis plug-in

mySAP

SRM 6.0

server

WD

EBP

IPC 7.0

ADS


SAP R/3 plug-in

FI/CO IPC 7.0

mySAP

SRM 6.0

server

BSP

SUS

SAP NetWeaver

XI proxyframework

SAP

NetWeaverXI integrationengine

Portal layer

RFC

RFC

SAP NetWeaver

XI integration

engine

SAP NetWeaver XI content for mySAP SRM 6.0 server

XMLIDoc adapter

ADS

MM

TREX 7.0

RFC

IDoc

Business package

for mySAP SRM 6.0

Firewall

RFC

http(s)

http(s)

Application gateway

http(s) / OCI

http(s) / OCI

Portal core



required)






TREX is a separately installed instance. For scalability, multiple TREX instances can be installed on

multiple servers.



12/21

SAP AG 12

SAP AG 2006

Service Procurement

SAP BW 7.0

BI_CONT 7.0.3

Basis plug-in

mySAP

SRM 6.0

server

WD

EBP

SAP NetWeaveer XI proxy

framework

SAP NetWeaver XI

integration engine

IPC 7.0

ADS

SAP R/3 backendSystem

SAP R/3 plugiIn

FI/CO IPC 7.0

mySAP

SRM 6.0

server

BSP

SUS

SAP NetWeaveer

XI proxyframework

SAPNEtWeaverXI

integrationengine

Portal layer

(IDoc)

RFC


SAP NetWeaver XI

integrationengine

XML

SAP NetWeaver XI content for SRM-MDM Catalog SAP NetWeaver XI content for mySAP SRM 6.0 server

XMLFile adapter

XML

TCP / FTP(s)

http(s)

ADS

Business package

for mySAP SRM 6.0

RFC

Firewall

RFC

http(s)

http(s)

http(s) / OCI

Application gateway

SRM-MDM Catalog 1.0

SAP NWMDM

console

SAP NWMDM data

manager

SAP NWMDM import

manager

SRM-MDM

Catalog:

search

(Web Dynpro)

SAP NW

MDM

server

SAP NWMDM

import server

Portal core



required)










13/21

SAP AG 13

SAP AG 2006

Analytics (with Master Data Consolidation)

SAP BW 7.0

BI_CONT 7.0.3

Basis plug-in

mySAP

SRM 6.0

server

WD

EBP


SAP R/3 plug-in

FI/CO

Portal layer

RFC

(IDoc)


SAP NetWeaver

XI integration

engine

SAP NetWeaver XI content for SAP NetWeaver Business

Intelligence content 7.1.3

SAP NetWeaver XI content for SAP

NetWeaver MDM server

File adapterTCP / FTP(s)

http(s)

Business package

for mySAP SRM 6.0

FTP(s)

RFC

SAP NetWeaver XI content for mySAP SRM 6.0 server

XML

XMLXML

Firewall

http(s)

http(s)

Application gateway

SRM-MDM Catalog 1.0

SAP NWMDM

console

SAP NWMDM data

manager

SAP NWMDM import

manager

SAP NetWeaver

MDM

server

SAP NetWeaverMDM

import server

Portal core


required)







XI Content for BI



14/21

SAP AG 14

SAP AG 2006

Sourcing

SAP BW 7.0

BI_CONT 7.0.3

Basis plug-in

mySAP

SRM 6.0server

WD

EBP

SAP NetWeaverXI proxy

framework

SAP NetWeaver XI

integration engine

IPC 7.0

ADS

SAP R/3back-endsystem

SAP R/3

plug-in

MMIPC 7.0

mySAP

SRM 6.0

server

BSP

SUS


framework

SAP NetWeaverXI integration

engine

Portal layer

(IDoc)

RFC

RFC


SAP NetWeaver

XI integration

engine

XML


XML

ADS

Business package

for mySAP SRM 6.0

Bidding

engine

TREX 7.0

LACWPS 6.0

TCP / FTP(s)

XML

http(s)

File/FTP adapter

Firewall

RFC

http(s)

http(s)

Application gateway

http(s) / OCI

http(s) / OCI

SRM-MDM Catalog 1.0

SAP NWMDM

console

SAP NWMDM data

manager

SAP NWMDM import

manager

SRM-MDM

Catalog:

search

(Web Dynpro)

SAP NetWeaver

MDM

server

SAP NetWeaverMDM

import server

Portal core



required)


LAC WPS can be deployed on the Portal



The XI Content Packages shown on this slide are: SRMSERV6000_0.ZIP (XI Content for SRM 6.0 Server)




multiple servers.



15/21

SAP AG 15

SAP AG 2006

Contract Management (with Legal Contract Authoring)

http(s)

SAP BW 7.0

BI_CONT 7.0.3

Basis plug-in

mySAP

SRM 6.0server

WD

EBP


framework

SAP NetWeaver XI

integration engine

IPC 7.0

ADS

SAP R/3 back-end system

SAP R/3 plug-

in

MM


framework

SAP NetWeaver XI

integrationengine

(IDoc)

RFC


SAP NetWeaver

XI integration

engine

XML


XML

Document

builder

TREX 7.0(contracts)

TCP / FTP(s) File/FTP adapter

FI/CO

SAP add-on

forDuet 1.0

Duet 1.0

server

http(s)

Please check the

minimum system

requirements for Duet

Firewall

Microsoft Office client and client

frameworkLAN

http(s)

http(s)

Portal layer Business package

for mySAP SRM 6.0

Duet meta data server

Knowledge management / collaboration room / UWL

Firewall

RFC

Application gateway

SRM-MDM Catalog 1.0

SAP NWMDM

console

SAP NWMDM data

manager

SAP NWMDM import

manager

SRM-MDM

Catalog:

search

(Web Dynpro)

SAP NetWeaver

MDM

server

SAP NetWeaverMDM

import server

Portal core


On the Portal Layer, you must deploy the Portal Core plus the following Portal Java Components:

Knowlege Management (KM)

collaboration room

Universal Worklist (UWL)


LAC WPS can be deployed on the Portal

DUET 1.0 requires WebAS 6.40 SP17, and must therefore be installed on a separate AS-JAVA (SAP

J2EE Engine). Duet 1.0 CANNOT be deployed on the Portal.

The following Duet Add-On Package must be installed:

- SRMOSPCONTRJAVA00_0.sca (The Duet Java Addon for Legal Contract authoring)

- and, optionally as of SP1 or SP2: SRMOSPSHOCAJAVA00_0.sca (The Duet Java Addon for

Shopping Cart approval)








multiple servers.



16/21

SAP AG 16

SAP AG 2006


Catalog and Content Management

mySAP

SRM 6.0

server

WD

EBP


framework

SAP NetWeaver XI

integration engine

Portal layer

SAP NetWeaver

XI integration

engine

SAP NetWeaver XI content for SRM-MDM Catalog SAP NetWeaver XI content for mySAP SRM 6.0 server

File/FTP adapter

XML catalog

upload

TCP / FTP(s)

XML

Master data

contract data

XML

Business package

for mySAP SRM 6.0

Firewall

http(s)

Application gateway

http(s)

http(s) / OCI

http(s) / OCI

SRM-MDM Catalog 1.0

SAP NWMDM

console

SAP NWMDM data

manager

SAP NWMDM import

manager

SRM-MDM

Catalog:

search

(Web Dynpro)

SAP NW

MDM

server

SAP NWMDM

import server

Portal core


required)








17/21

SAP AG 17

SAP AG2006

Category Management

mySAP SRM

6.0 server

CatMan

Bids,

contracts, and

master data

SAP BW 7.0

BI_CONT 7.0.3

Basis plug-in

Portal layer

Knowledge management/

collaboration room/ UWL

cProjects

4.0

cProjects

4.0

CatMan

Web Dynpro

Java application

RFC

RFC

Adaptive RFC

Business package

for mySAP SRM 6.0

Business package

for CatMan

Business package

for project portfoliomanagement

and design collaboration 4.0

Firewall

Application gateway

http(s)

http(s)

On the Portal Layer, you must deploy the Portal Core plus the following Portal Java Components:

Knowlege Management (KM)

collaboration room

Universal Worklist (UWL)

cProjects (Java part of cProjects) can be deployed on the Portal

Category Management (CatMan) can be deployed on the Portal



BPSRMCM00_0.sca (BP for CatMan)

BPSRMCMCONT00_0.sca (BP for CatMan)

BP for portfolio management and collaboration


18/21

SAP AG 18

SAP AG2006

Supplier Qualification

http(s) / OPI

http(s) / OPI

mySAP

SRM 6.0

server

WD

EBP

mySAP

SRM 6.0

server

BSP

RoS


SAP R/3 plug-in

MM

RFC

RFC

Portal layer

Business package

for mySAP SRM 6.0

Firewall

Application gateway

Portal core


required)





19/21

SAP AG 19

SAP AG2006

SRM_PLUS Package - Overview

The SRM_PLUS package was built to avoid naming conflicts with ABAP objects in

an ERP System

You have two installation options:

Install SRM Server 6.0 and ERP 2005 in the same client of one system.In this case, you must not install SRM_PLUS at all

Install SRM Server 6.0 and ERP 2005 on two different systems (SIDs).

In this case, you have to install SRM_PLUS on the SRM system.

Note: Only the following scenarios are supported in the one-client option:

Self-Service Procurement (classic deployment) since ERP 2004

Self-Service Procurement with supplier integration for MRO materials (since ERP 2004 Content Shipment)

Service Procurement (lean deployment)- since ERP 2005

Invoice Management System (part of Plan Driven Procurement) - since ERP 2005

Catalog and Content Management - since ERP 2004

SAP SRM Server 6.0

ERP 2005

(SAP ECC 6.0)

SAP SRM

Server 6.0

SRM_PLUS

Either

SAP ERP

or

NO SAP

ERP !

Option 1 restricted SRM functionality Option 2 full SRM functionality

NO SRM_PLUS

mySAP SRM2005 includes two different software components

SRM_SERVER

SRM_PLUS

SRM_SERVER Add-On on ERP only includes the software component

SRM_SERVER since SRM_PLUS contains objects with naming conflicts

to ERP objects or objects not needed for the add-on on ERP

Both software components do have there own transport layer

SRM_SERVER: /SEBP/

SRM_PLUS: /SRPL/

This add-on will not be deployed when SRM is deployed as an add-on over ECC (Core component of

ERP)

For the one-client scenario only the integration scenarios classic and extended classic restricted to the self

service and service procurement business scenario shall be supported; and one ECC shall be supported


20/21

SAP AG 20

SAP AG 2006

Summary

Contents

mySAP SRM Architecture

Now you are able to:

Understand the SAP NetWeaver usage types and what is

relevant to SRM 6.0

Understand the different components available in SRM 6.0

List the necessary components per SRM Scenario

Describe which components are using the ABAP Stack, andwhich the J2EE Stack

Explain the system landscapes per scenario


21/21

SAP AG 21

SAP AG2006

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 containedherein 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.

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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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. All other product and service names mentioned arethe trademarks of their respective companies. Data contained in this document serves informational 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 withoutthe express prior written permission 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 that this 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 the accuracy 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 or implied, including but not limited to theimplied 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 ofthese materials. This limitation shall 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 hotlinks 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.

Copyright 2006 SAP AG. All Rights Reserved

Documents

Srm 600 Architecture