sap supplier relationship management powered by sap netweaver

Master Guide

SAP SupplierRelationshipManagementpowered by SAPNetWeaverUsing SAP® SRM Server 6.0Target Audience

System administrators

Technology consultants

Document Version 1.4 – April, 2008

Material Number 50081528

© Copyright 2007 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.

Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registeredtrademarks 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, Informix, i5/OS, POWER, POWER5, OpenPower andPowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are eithertrademarks or registered trademarks of Adobe Systems Incorporated inthe 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 theOpen Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., usedunder 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, andother SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AGin Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of theirrespective companies. Data contained in this document servesinformational purposes only. National product specifications mayvary.

These materials are subject to change without notice. These materialsare 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 omissionswith respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additionalwarranty.

DisclaimerSome components of this product are based on Java™. Any codechange in these components may cause unpredictable and severemalfunctions and is therefore expressively prohibited, as is anydecompilation of these components.

Any Java™ Source Code delivered with this product is only to be usedby SAP’s Support Services and may not be modified or altered in anyway.

Documentation in the SAP Service MarketplaceYou can find this documentation at the following Internet address:service.sap.com/instguides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

Typographic ConventionsType Style Represents

Example Text Words or characters thatappear on the screen. Theseinclude field names, screentitles, pushbuttons as well asmenu names, paths andoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrasesin body text, titles of graphicsand tables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, tablenames, and individual keywords of a programminglanguage, when surrounded bybody text, for example,SELECT and INCLUDE.

Example text Screen output. This includesfile and directory names andtheir paths, messages, namesof variables and parameters,source code as well as namesof installation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Exampletext>

Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, forexample, function keys (suchas F2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Master Guide SAP SRM

4 March 2007

History of ChangesThe Master Guide is regularly updated in SAP Service Marketplace atservice.sap.com/instguides.

Make sure you have the latest version of the Master Guide by checking SAPService Marketplace immediately before starting the installation.

The following table provides an overview of the most important changes that were made inthe latest versions.

Master Guide Version Important Changes

1.0 (December, 2006) New Category Management business scenario; scenariochanges

1.1 (March, 2007) Incorporated input from Solution Validation

Product Names: SAP has recently changed some of thenaming of SAP products. Note that the old names are still inuse and therefore the following product names aresynonymous:

Old Name: mySAP SRM 6.0 = SAP SRM 2007 (New Name)

Old Name: SAP NetWeaver 7.0 = SAP NetWeaver 2004s (NewName)

1.2 (October, 2007) The software component matrix entry for SAP MDM DataServer 5.5 has been changed because it is now an optionalcomponent that is only used in data harmonization andconsolidation scenarios.

References to CPRXRPM notes added.

1.3 (December, 2007) A new section Enterprise Service-Oriented Architecture hasbeen added to Section 2 SAP SRM Overview.

1.4 (February, 2008) Software component matrix revised and resulting revisionsmade to the rest of the guide.

1 Getting Started

March 2007 5

ContentsHistory of Changes ................................................................................4

1 Getting Started.................................................................................71.1 About this Document.......................................................................81.2 Related Information .........................................................................9

1.2.1 Planning Information .......................................................................... 91.2.2 Further Useful Links ......................................................................... 10

1.3 Important SAP Notes .....................................................................102 SAP SRM Overview .......................................................................12

2.1 Software Units of SAP SRM ..........................................................122.1.1 Application Components: SRM 2007 Software Units..................... 122.1.3 Technology Components ................................................................. 152.1.4 Non-SAP Components...................................................................... 18

2.2 Software Component Matrix .........................................................192.3 System Landscape.........................................................................21

2.3.1 Minimal System Landscape.............................................................. 212.4. Overall Installation Sequence ......................................................222.5 Enterprise Service-Oriented Architecture (SOA) ........................23

3 Business Scenarios of SAP SRM ................................................243.2 Contract Management ...................................................................24

3.2.1 Overview ............................................................................................ 243.2.2 Technical System Landscape .......................................................... 25

3.3 Service Procurement .....................................................................313.3.1 Overview ............................................................................................ 313.3.2 Technical System Landscape .......................................................... 313.3.3 Implementation Sequence................................................................ 33

3.4 Strategic Sourcing .........................................................................373.4.1 Overview ............................................................................................ 373.4.2 Technical System Landscape .......................................................... 383.4.3 Implementation Sequence................................................................ 41

3.5 Plan-Driven Procurement ..............................................................463.5.1 Overview ............................................................................................ 463.5.2 Technical System Landscape .......................................................... 473.5.3 Implementation Sequence................................................................ 49

3.6 Catalog Content Management ......................................................523.6.1 Overview ............................................................................................ 523.6.2 Technical System Landscape .......................................................... 523.6.3 Implementation Sequence................................................................ 54

1 Getting Started

6 March 2007

3.7 Self-Service Procurement .............................................................583.7.1 Overview ............................................................................................ 583.7.2 Technical System Landscape .......................................................... 593.7.3 Implementation Sequence................................................................ 62

3.8 Spend Analysis ..............................................................................653.8.1 Overview ............................................................................................ 653.8.2 Technical System Landscape .......................................................... 663.8.3 Implementation Sequence................................................................ 67

4 Solution-Wide Topics....................................................................704.1 Solution Manager ...........................................................................70

5 References .....................................................................................726 Additional Information ..................................................................74

6.1 Importing Integration Objects for SAP SRM on SAP ProcessIntegration.............................................................................................746.2 Patching Your SAP SRM Solution ................................................75

7 Media List .......................................................................................76Software Components and DVD / CD Structure ...................................... 76

8 The Main SAP Documentation Types .........................................78

1 Getting Started

March 2007 7

1 Getting StartedThe SAP Supplier Relationship Management (SAP SRM) Master Guide provides a centralstarting point for the technical implementation of SAP SRM.

To facilitate the implementation process, all information within this document is organized byscenario. You can choose from several generic business scenarios and find all theinformation relevant for the technical implementation of a specific business scenario in thatsection.

Each business scenario supports a number of variants. In this Master Guide only key variantsare described in detail.

For information about upgrading the SAP SRM business scenarios, see theUpgrade Master Guide –SAP SRM. This guide provides information about theoverall upgrade sequences, references to related documentation, SAP Notes, andadditional upgrade information for each business scenario of SAP SRM. TheUpgrade Master Guide is available on SAP Service Marketplace athttp://service.sap.com/instguides SAP Business Suite Applications

SAP SRM. The complete SAP SRM solution consists of the following top-level scenarios and

business scenarios:

Self-Service Procurement

Plan-Driven Procurement

Service Procurement

Catalog Content Management

Strategic Sourcing

Spend Analysis

Contract Management

http://service.sap.com/instguides

1 Getting Started

1.1 About this Document

8 March 2007

1.1 About this DocumentPurposeThis Master Guide is the central starting point for the technical implementation of SAP SRM.You can find cross-scenario implementation information as well as scenario-specificinformation in this guide.

The central starting point for the technical upgrade of your SAP solution isthe Upgrade Master Guide, which you can find on SAP ServiceMarketplace at service.sap.com/instguides SAP Business SuiteApplications SAP SRM.

Use the Master Guide to get an overview of SAP SRM, its software units, and its scenariosfrom a technical perspective. The Master Guide is a planning tool that helps you to designyour system landscape. It refers you to the required detailed documentation, mainly:

Installation guides for single software units

SAP Notes

Configuration documentation

SAP Library documentation

For a general overview of the available SAP documentation, see The Main SAPDocumentation Types.

The Master Guide consists of the following sections:

Getting Started contains information about using this document and related informationcrucial to the installation.

SAP SRM Overview contains:

o A short introduction to the SAP™ Business Suite solution

o The software component matrix

o Minimal system landscape

o Overall installation sequence

Business Scenarios of SAP SRM contains information for each business scenariocomprising:

o An overview of the business scenario

o Examples of how the different components interact, and what protocols andinterfaces are used, including technical system landscape examples

o Information about the overall installation sequence and subsequent steps

o References to related installation guides

o Information about mutual dependencies that affect two or more components withinthe business scenario

Software Component Matrix contains a short description of every software componentin this solution.

Depending on the specific business scenarios to be implemented, many differentinstallation guides and various configuration documentation may be required.The SRM 2007 implementation content is clearly organized according to installation orconfiguration activity.


1 Getting Started

1.2 Related Information

March 2007 9

Installation documentation is available in installation guides on SAP ServiceMarketplace.Configuration documentation is only available as SAP Solution Manager Content.References lists the documentation referenced in this Master Guide.

Additional Information contains information on how to:

Install/patch the SAP® NetWeaver Process Integration (PI) (formerly ExchangeInfrastructure (XI)) as part of SAP SRM.

Patch your SAP SRM solution (for example, if you want to patch your solution fromSupport Package 02 to Support Package 03).

You can find the most current information about the technical implementationof SAP SRM 2007 and the latest installation and configuration guides on SAPService Marketplace atservice.sap.com/instguides.We strongly recommend that you use the documents available here. Theguides are regularly updated.

Constraints The business scenarios that are presented here serve as examples of how you can use

SAP software in your company. The business scenarios are only intended as models anddo not necessarily run the way they are described here in your customer-specific systemlandscape. Ensure to check your requirements and systems to determine whether thesescenarios can be used productively at your site. Furthermore, we recommend that youtest these scenarios thoroughly in your test systems to ensure they are complete and freeof errors before going live.

This Master Guide primarily discusses the overall technical implementation of SAP SRM,rather than its subordinate components. This means that additional softwaredependencies might exist without being mentioned explicitly in this document. You canfind more information on component-specific software dependencies in the correspondinginstallation guides.

1.2 Related Information1.2.1 Planning InformationFor more information about planning topics not covered in this guide, see the followingcontent on SAP Service Marketplace:

Content Location in SAP Service Marketplace

The latest version of the installation andupgrade guides for SAP SRM and SAPSRM Server, links to related SAP Notes

service.sap.com/instguides SAPBusiness Suite Applications SAPSRM Using SAP SRM Server 6.0

SAP Enterprise Service-OrientedArchitecture Master Guide

service.sap.com/instguides SAPBusiness Suite Applications SAPERP SAP ERP 6.0 SAPenhancement packages for SAP ERP6.0 SAP enhancement package 3for SAP ERP 6.0

Released platforms service.sap.com/platforms ProductAvailability Matrix



http://service.sap.com/platforms

1 Getting Started

1.3 Important SAP Notes

10 March 2007

General security information for SAPsystems.

service.sap.com/security

SAP Solution Manager service.sap.com/solutionmanager

SAP R/3 plug-in releases and availability service.sap.com/R3-plug-in

Hardware sizing service.sap.com/sizing

Information about SRM components andfurther documents

service.sap.com/srm SAP SRM inDetail

Information about SAP SRM SupportPackage stacks and download ofSupport Package stacks

service.sap.com/sp-stacks

Download of SAP software(SAP Software Distribution Center)

service.sap.com/swdc

1.2.2 Further Useful LinksContent Location on SAP Service Marketplace

Information about creating error messages service.sap.com/messages

SAP Notes search service.sap.com/notes

SAP Software Distribution Center (softwaredownload and ordering of software)

service.sap.com/swdc

SAP Online Knowledge Products (OKPs) –role-specific Learning Maps

service.sap.com/rkt

1.3 Important SAP NotesYou must read the SAP Installation Notes before you start the installation. These SAP Notescontain the most recent information about the installation as well as corrections to theinstallation documentation.

Make sure that you have the up-to-date version of each SAP Note, which you can find in theSAP Service Marketplace at service.sap.com/notes.

SAP Note Title Description

1102079 SAP SRM 2007 SP03BI Content Changes

Summarizes obsolete BI objects

995220 SRM 6.0Support Package 00

Release Information Note







http://service.sap.com/solutionmanager

http://service.sap.com/solutionmanager

1 Getting Started

1.3 Important SAP Notes

March 2007 11

854170 Switching on componentVM Container

This note is required to enable the VirtualMachine Container (VMC), part of the SAPBasis 7.00. The VMC must be enabled for theIPC component, which is itself installedautomatically with the SAP_AP 7.0.

66971 Supported front-endplatforms

Supported Microsoft Windows releases for thestandard SAP GUI.

1057316 SRM-MDM Catalog 2.0Installation

Installation Note

967123 SAP SRM 6.0 Installationon Windows

Additional information for installation on aWindows operating system.

853694 Upgrading to SAP BasisRelease 700 withCPRXRPM 400

This note is important if you want to perform anadd-on upgrade to SAP Basis Release 700(SAP_BASIS 700) with CPRXRPM 400.

1080594 Installing CPRXRPM 400SR1 on Basis Release700

Installation of CPRXRPM 400 SR1 usingtransaction SAINT

2 SAP SRM Overview

2.1 Software Units of SAP SRM

12 March 2007

2 SAP SRM OverviewSAP Supplier Relationship Management maximizes the return on all supplier relationshipsacross all categories of spending at all times. It covers the entire supply cycle from strategicsourcing to operational procurement and supplier enablement to leveraging consolidatedcontent and master data.

With SAP SRM, you can collaborate with all suppliers for all purchased goods and services,enabling you to continually optimize supplier selection, shorten cycle times, and devisesourcing and procurement strategies.

2.1 Software Units of SAP SRMThis section provides additional information about the primary software components of thisSAP Business Suite solution.

Only a subset of these components is required for the installation of anysingle business scenario. For a scenario-specific overview of components,see the section Business Scenarios of SAP SRM.

SAP implements all capabilities and features of SAP Business Suite solutions using thefollowing SAP Business Suite components. SAP SRM uses

Application components

Technology components

You can install and upgrade the components separately. Each component has its ownrelease plan.

2.1.1 Application Components: SRM 2007Software UnitsThe following application components implement and support SAP Business Suite cross-industry solutions.

SAP Supplier Relationship Management ServerThe SAP Supplier Relationship Management Server (SAP SRM Server) includes both SAPEnterprise Buyer and SAP Bidding Engine.

SAP Enterprise Buyer is based on SAP NetWeaver Application Server (AS) and is anapplication and database instance installation released on several database and operatingsystem platforms (for more information, see SAP Service Marketplace atservice.sap.com/platforms Platform Availability Matrix). With it you can:

Create and process requirement requests, purchase orders, and reservations with orwithout electronic catalogs

Approve and reject purchases

Receive and enter service information at the desktop

Use status, invoicing, and reporting functions

Users can purchase goods and services straight from their workplace, leaving purchasingdepartments free to focus on strategic purchasing operations. This helps streamlinerequisition processes and, consequently, all indirect procurement processes. The overall cost


2 SAP SRM Overview


March 2007 13

of procurement is reduced and the purchasing department has visibility and control acrossthe entire procurement chain.

SAP Enterprise Buyer contains business scenarios for professional purchasers.

For example, with SAP Enterprise Buyer, you can publish RFx in Internet marketplaces foryour specific industry branch, extending your potential reach to the entire Internet community.By the same means, interested parties can access the RFx and submit their bids directly fromthe marketplace. SAP Enterprise Buyer also supports restricted RFx. RFx can also beconverted to reverse auctions.

Another business scenario contains the interface to the Business Intelligence (BI) system.Professional purchasers use the information from the BI system to, for example, rate aprovider’s services or analyze their employees’ purchases.

In addition to maintenance, repairs, and operation (MRO), BI supports the end-to-endprocurement of direct materials. Direct procurement scenarios involve the seamlessintegration of SAP Enterprise Buyer with SAP APO, BI, and SAP or non-SAP back-endsystems. SAP Enterprise Buyer also supports - on a project basis - a comprehensive range ofmobile applications.

UseSAP Enterprise Buyer is the central procurement and sourcing system for all SAP SRMscenarios. It empowers employees with self-service procurement, enables centralized directprocurement, and provides the professional purchaser with tools for making sourcingdecisions.

The SAP SRM solution requires the SAP Enterprise Buyer system for downloading materialsdata and (optionally) using the Business Intelligence capabilities offered by SAPNetWeaver.

SAP Bidding Engine

Purchasers can use SAP Bidding Engine to create and process RFx, and bidders can useSAP Bidding Engine to submit bids in response to these RFx. Both purchasers and bidderscan use reverse auction functions in a separate Live Auction application. Purchasers candefine rules for bidding and bidders can submit bids in real time.

Online Transaction Processing SystemAn Online transaction processing system (OLTP), for example, SAP ERP system, is used inthe SAP Enterprise Buyer environment as a back-end system for materials management andfinancials.

UseData is exchanged between the SAP Enterprise Buyer system and a connected OLTPsystem.

The SAP Enterprise Buyer system can be installed without an OLTP back end in astandalone configuration.

If a SAP ERP system is used as an OLTP system, the plug-in supports data exchange inSAP Enterprise Buyer as well as in other SAP software units such as BI or SAP APO.

2 SAP SRM Overview


14 March 2007

SAP NetWeaver Business IntelligenceBusiness Intelligence (BI) provides infrastructure for:

Data warehousing

A range of analytical technologies and functions

Web-based reporting and analysis

Information Broadcasting for distributing BI content by e-mail or by the workset, either asprecalculated documents with past data, or as links with live data

Open analysis interfaces that make available various interfaces for connecting front-endtools of third-party providers

Web design API allowing for the implementation of highly individualized scenarios as wellas more demanding applications containing customer-defined interface elements

BI Java Components (BI-Java) provide the Java runtime environment for IT scenarios suchas Enterprise Reporting, Query and Analysis, and Business Planning and Analytical Services.BI-Java enables variants such as information broadcasting and ad-hoc query & analysis aswell as enabling Web Dynpro-based BI applications and third-party data access via universaldata integration.

UseBI is the foundation for the SRM scenario Spend Analysis, and can be installed for the others.BI includes the complete ABAP stack of the SAP NetWeaver BI data warehouse and BIplatform units.

BI requires AS-ABAP as prerequisite in the same system. Usually, scenarios running on BIalso require BI-Java, AS-Java, and SAP Enterprise Portal. Other combinations can be usedin one system as well.

SAP NetWeaver Enterprise PortalSAP NetWeaver Portal serves as a single point of entry to the applications, services, andinformation of the organization.

Running an Enterprise Portal is an IT scenario providing role-based and secure access to alltypes of applications, services, and information in an enterprise workset environment.

Customers can benefit from the numerous predefined business packages available to them,or they can create their own content.

This scenario includes the following variants:

Providing Uniform Content AccessOrganizations can develop, configure, and operate a knowledge-based, Web-like userinterface to give users a consistent environment for accessing content. For example,organizations may integrate both SAP and non-SAP applications into the enterpriseworkset using a single, consistent front end.

Implementing a Global Portal (Federated Portal)Organizations can use the federated workset approach to share content between SAPNetWeaver portals and also third-party WSRP-compliant (Web Services for RemotePortlets) portals to create a single virtual-content pool.

Live Auction Cockpit Web Presentation Server

2 SAP SRM Overview


March 2007 15

Live Auction Cockpit Web Presentation Server is a J2EE-based software unit comprising:

Virtual auction floor for reverse auctions

Real-time monitoring

Real-time bidding

Instant messaging (chat)

Tight integration to all procurement processes

State-of-the-art user interface

SAP® NetWeaver 7.0 Search and Classification (TREX)SAP NetWeaver Search and Classification (TREX) offers an integrated set of services.

TREX services include search and retrieval in large document collections, text mining,automatic document classification, and search and aggregation over structured data in SAPapplications. TREX can handle text from documents in numerous formats, including MicrosoftOffice and Adobe formats (PDF), and more than 30 languages. TREX search options, suchas exact, Boolean, fuzzy, or linguistic search, and classification options such as query-basedor example-based classification, offer users great power and flexibility.

SRM-MDM CatalogThe SRM-MDM Catalog is based on SAP NetWeaver Master Data Management (MDM)technology. It combines SAP MDM Server 6.0 with a Java-based and SRM-specific searchenvironment.

The SRM-MDM Catalog provides the following functions:

Import product hierarchy

Upload product data from supplier

Map imported hierarchy and products to repository

Transfer info records and contracts from ERP

Transfer product data from SRM

Transfer contracts data from SRM

Enrich product data

Approve product data

Define masks

Define validations

Enable web content

Browse in catalog and search for catalog items

Transfer data to procurement system

2.1.3 Technology Components

2 SAP SRM Overview


16 March 2007

Technology components are software and middleware components for implementing andsupporting SAP Business Suite solutions.

SAP NetWeaver Process Integration (PI)

Separate licensing is required for SAP NetWeaver Process Integration, if SAPSRM is used to connect with non-SAP systems, or with external tradingpartners.

SAP NetWeaver Process Integration (PI) comprises core components for modeling,designing, automating, and integrating the processes of one or more application systems. Forthe integration of internal and cross-company processes, PI is used to incorporate all thefunctions of Exchange Infrastructure (XI). PI also contains core components for BusinessProcess Management for application-embedded and application-unbounded processes.

2 SAP SRM Overview


March 2007 17

SAP GUIThe latest release of the SAP GUI software (such as SAP GUI 6.20) can be used with allprevious SAP component releases. Consequently, older SAP systems can also benefit fromthe features that are only available in the newer SAP GUI releases, such as support forWindows XP.

Use the latest available front-end software.

SAP R/3 Plug-InThe SAP R/3 Plug-In is an interface for exchanging data between one or several SAP R/3systems and other SAP components. The SAP R/3 Plug-In supplies the SAP componentswith transaction data and master data in real time. With it SAP application components likeSAP APO or SAP CRM can be linked together with certain industry-specific components. AllSAP industry-specific components based on SAP R/3 4.6B or higher SAP R/3 releasesrequire an SAP R/3 Plug-In. The SAP R/3 Plug-In is an add-on to SAP R/3.

SAP R/3 Plug-Ins are shipped with SAP application components (SAP APO, SAP BI, SAPBBP, SAP EBP, SAP CRM, and SAP SEM) and with industry-specific SAP componentsbased on SAP R/3 4.6B or higher SAP R/3 releases. You can order the most recent SAP R/3Plug-In releases free of charge or download them from the SAP Service Marketplace.

Depending on the combination of the SAP R/3 Plug-In release and version and the SAP R/3release, certain SAP R/3 support package levels are required for installing the SAP R/3 Plug-In.

For more information and for download, see SAP Service Marketplace atservice.sap.com/r3-plug-in.

SAP NetWeaver Application ServerApplication Server (AS) is the application platform of SAP NetWeaver and, consequently, ofthe SAP Business Suite. It provides the technological foundation for all other SAP softwareunits.

Different basic system variants exist for AS. The variants and their differences are:

Variant Engines you may operate

ABAP+Java system ABAP Engine and J2EE Engine

Java system J2EE Engine only

ABAP system ABAP Engine only

SAP SRM Server 6.0 is based on SAP NetWeaver 2004(s).

UseSince AS comprises the ABAP Engine, Java Engine or both, it can provide a runtimeenvironment for both ABAP and Java applications.

AS includes a platform for quickly developing and deploying dynamic and collaborative Webapplications or other thin-client applications such as WAP or PDA and supports all provenSAP programming models and technologies. With AS, SAP supports open Internetstandards, including protocols such as HTTP, HTTPS, and SMTP, as well as Internetdocument standards such as HTML and XML.

Open integration capabilities provide access to existing SAP and non-SAP applications.

All integration facilities supported by SAP are available with AS. The Java Connector or the.NET Connector gives ABAP applications access to Java or .NET components and viceversa.

2 SAP SRM Overview

18 March 2007

In addition, the Internet Communication Framework (ICF) enables ABAP programs to directlyprocess and distribute HTTP requests. Consequently, AS can serve as both an HTTP serverand a client.

It serves as an HTTP server for:

Bringing applications to the user via a Web browser either directly or via a standardWeb server.

Accessing other Web applications for collecting information and data.

To complete Web connectivity, AS provides full support for sending and receiving e-mails viaSMTP.

Building BlocksUsage type AS comprises the following main building blocks:

Central instance

Central service instance

The central service instance forms the communication and synchronization basis for theJ2EE cluster.

Database instance

AS-Java has its own database schema. Consequently, a database instance is also amandatory installation component for an AS-Java system installation.

For installation of a system that supports both ABAP and Java, both the ABAP and theJava schema are installed in the same database.

Exception:If your SAP system runs on Informix, a separate MaxDB or IBM DB2 UDB forUNIX and Windows is required for the Java database schema.

Dialog instances, if required

Dialog instances are SAP instances comprising:

o Dispatcher, IGS, and CCMS agents

o For AS-ABAP and AS-Java in one system and AS-Java system:J2EE server processes

o For AS-ABAP and AS-Java in one system and AS-ABAP system:Gateway and certain ABAP work processes (dialog, batch, spool, or update)

Dialog instances are installed on application servers.

The dialog instances of AS-Java systems are called J2EE dialog instances.

SAP GUI

See separate component description above.

2.1.4 Non-SAP ComponentsNo non-SAP component is part of SAP SRM.

2 SAP SRM Overview

March 2007 19

2.2 Software Component MatrixThis section provides an overview of which business scenario of SRM uses which softwareunit.

For the latest component version and patch level requirements, see SAP ServiceMarketplace at service.sap.com/sp-stacks SAP SRM 6.0 and the Release andInformation Note which is available for each Support Package stack (SAP note number islisted on the page).

This Master Guide provides just one way to implement each businessscenario. For other ways to implement business scenarios, see the Scenario& Process Component List in SAP Service Marketplace atservice.sap.com/scl. The Scenario & Process Component List helpsyou to find realization alternatives for SAP solutions, business scenarios andprocesses. It shows you which application components are needed to realizea business scenario or process.

The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 6.0 package can be found at SAP ServiceMarketplace at service.sap.com/instguides SAP Business Suite ApplicationsSAP SRM.

Note that for each component listed below there are software requirementsthat are not explicitly mentioned in this documentation. Component-specificsoftware requirements are documented for a component in its installationguide. All related implementation guides are listed in References.

Software Components SRM Business Scenarios

SAP

Delivered

Content

Self

Serv

ice

Proc

urem

ent

Plan

Driv

en P

rocu

rem

ent

Serv

ice

Proc

urem

ent

Cat

alog

Con

tent

Man

agem

ent

Ana

lytic

s

Con

trac

t Man

agem

ent

Stra

tegi

c S

ourc

ing

SAP® Supplier Relationship

Management Server 6.0

(SAP SRM Server 6.0,

based on SAP® Web

Application Server

M M M M M M M


2 SAP SRM Overview

2.2 Software Component Matrix

20 March 2007

7.00, comprises SAP®

Enterprise Buyer, SAP®

Bidding Engine and Supplier

Self-Services)

Live Auction Cockpit web

presentation server

(LACWPS) 6.0

- - - - - - M (i)

SRM-MDM Catalog 2.0 O O O M - O O

SAP WebAS ABAP 7.00 M M M M M M M

SAP WebAS Java 7.00 M M M M M M M

SAP Netweaver® 7.0

Search and Classification

(TREX)

O M - - - O O

SAP Netweaver® BI 7.0 O O O - M O O

SAP

NetWeaver® BI_CONT

7.03

O O O - M O O

SAP Netweaver®

Enterprise Portal 7.0

M M M M M M M

Business

Package for

SRM Server

6.0

M M M M M M M

SAP Netweaver® Process

Integration 7.0

O M M O M

(ii)

O O

XI Content

for SAP SRM

Server 6.0

O M M O - O O

XI Content

for SAP

NetWeaver

BI Content

7.03

O O O O - - -

XI Content for

SRM-MDM

Catalog

O O O O - O O

SAP Netweaver® MDM 5.5 O O - - O O O

2 SAP SRM Overview

March 2007 21

(ii)

SAP Netweaver® Adobe

Document Server 7.0

O O M - - O O

cProject 4.0 - O - O - - O

SAP Document Builder - - - - - M -

SAP® R/3 OLTP as of 3.1i up

to SAP® R/3 Enterprise 4.70,

ERP 1.0, ERP 2.0

(SAP R/3 4.6C or higher

recommended)

M M O - O O O

SAP R/3 Plug-In 2004.1 or

higher if one is available

M M O - O O O

SAP GUI 7.0 or Higher M M M M M M M

0 = Optional business or technology enhancement for this scenarioLegend:M = Mandatory minimum requirement for the deployment variants of this scenario(i) With Live Auction(ii) For Master Data Harmonization / Consolidation

You require SAP® NetWeaver 7.0 TREX in the following cases:

o When you use the contract management application to search for information suchas vendor texts, internal notes, and attachments.

o When you want to use the metadata search functionality or use BI accelerator withinAnalytics.

2.3 System Landscape2.3.1 Minimal System Landscape

We strongly recommend that you use a minimal system landscape for testand demo purposes only. For performance, scalability, high availability, andsecurity reasons, do not use a minimal system landscape as your productionlandscape.

2 SAP SRM Overview

22 March 2007

Enhanced requirements on performance, scalability, high availability, andsecurity reasons cannot be met by a minimal system landscape. Forinformation on creating productive system landscapes, see SAP ServiceMarketplace at service.sap.com/ti.

The installation of this minimal system landscape is possible only if you:

o Choose an operating system and a database that supports all components.For more information about released platforms for SAP SRM, see SAP ServiceMarketplace at service.sap.com/platforms Product Availability Matrix.

o Provide a sufficiently sized server. For information on sizing, see SAP ServiceMarketplace at service.sap.com/sizing.

SAP Process Integration requires a dedicated SAP Web Application Server.This means that running applications in other clients of the same SAP WebAS is not supported.

2.4. Overall Installation SequencePurposeThe following figure describes the installation sequence for SAP SRM comprisingcomponents of all SAP SRM business scenarios.

SAPOLTP

SAPPI

SRMServer(EBP)

cProjects

SAPMDM

SRMMDM

Catalog

SAPTREX

Time

SRMServer(SUS)

SAPBI

SAPEP

Legend:based on AS-ABAPbased on AS-JAVAbased on AS-ABAP and AS-JAVAbased on C/C++ or similarPortal BP or XI ContentBI Content

ADSLACWPS

Contentfor SRM

BPSRM

BPCategory

Mgmt.

BIContent

Contentfor BI

Contentfor SRM

MDM Cat.

Duet

SAP SRM Server can be installed either as non-Unicode or Unicode SystemSAP ITS and SAP IPC do not require a separate installation, as they are partof the SAP SRM Server.


2 SAP SRM Overview

2.5 Enterprise Service-Oriented Architecture (SOA)

March 2007 23

Some of these software components may be optional for some/all businessscenarios.For more information about the installation sequence of each businessscenario, see <Business Scenario> Implementation Sequence.

If you want to implement more than one SAP SRM business scenario at a time note thatsoftware components on the same level can be installed at the same time on the appropriatemachine (for example, different project groups could install SAP R/3 and SAP PIsimultaneously).

2.5 Enterprise Service-OrientedArchitecture (SOA)Enterprise service-oriented architecture (enterprise SOA) is an IT architecture for developingservices-based, enterprise-scale business solutions. An enterprise service is a series of Webservices combined with business logic that can be accessed and used repeatedly to supporta particular business process.

SAP Supplier Relationship Management (SAP SRM) supports enterprise SOA for many of itsbusiness services. The technical implementation of SAP SRM services as web services isdescribed in the Master Guide for enterprise SOA, available from the SAP ServiceMarketplace at sevice.sap.com/instguides SAP Business Suite Applications SAPERP SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAPenhancement package 3 for SAP ERP 6.0

3 Business Scenarios of SAP SRM

24 March 2007


This Master Guide provides just one way of implementing each businessscenario. See the Scenario & Process Component List in SAP ServiceMarketplace (service.sap.com/scl) for alternatives. The Scenario &Process Component List helps you to find realization alternatives for SAPsolutions, business scenarios and processes. It shows you which applicationcomponents are needed to realize a business scenario or process.

3.2 Contract ManagementFor this business scenario, the following topics are covered:

Overview

Technical system landscape

Overview of the implementation sequence

3.2.1 OverviewThe Contract Management business scenario comprises four process steps:

Contract negotiation

Creation

Execution

Monitoring.

A strategic purchaser has to finalize the purchasing contract or global outline agreement(GOA) created out of the legal contract before the operational contract is available forexecution. With a GOA, the SRM distribution features provide a powerful mechanism forcreating local contracts in multiple SAP ERP back-end systems. Furthermore, the SRMdistribution feature can be used to maintain and lock the distributed contracts out of the GOA.

Contract management enables purchasers in various parts of the company at differentlocations to take advantage of the terms in globally-negotiated contracts for specific productcategories.

The SRM purchasing contract and GOAs can also be created directly in SRM without a legalcontract. Those operational contracts can be renegotiated via a RFQ or Reverse Auction inthe SAP SRM Bidding Engine. The winning bid can update an existing operational contract orcreate a new operational contract in the SAP SRM system.

You can also provide users with specific levels of authorization for operational contracts andGOAs, and categorize these contracts as confidential to further restrict access to sensitivecontracts.

You can use contract hierarchies to organize, structure, display, and search for youroperational contracts.


3.2 Contract Management

March 2007 25

If you use SAP Business Intelligence (SAP BI), you can view various consolidated reports ofcontract management. For example, you can view the aggregated value released against allthe contracts in a contract hierarchy.

The legal and operational contract repository also provides a powerful search functionalitywith free text search.

TasksSample tasks for the Contract Management business scenario include:

A legal template administrator creating and maintaining legal contract templates

A legal contract creator creating legal contracts

A legal contract creator amending legal contracts

A legal contract creator searching and monitoring legal contracts

A strategic purchaser negotiating a long-term contract with a vendor to deliver goods ofa specific commodity

A strategic purchaser maintaining a GOA database that includes target quantities

A strategic purchaser monitoring contract compliance

An operational purchaser searching for applicable contracts within a central contractdatabase and putting contracts into effect

An operational purchaser adding local contract information

An operational purchaser managing planning and production processes

An operational purchaser creating purchase orders against a contract

Deployment OptionsFor Contract Management, the following deployment options are available.

Classic scenario

Standalone scenario

3.2.2 Technical System Landscape

For information about the technical system landscape and about how to planthe business scenario to meet your needs, see: SAP Service Marketplace at

service.sap.com/platforms Platform Availability Matrix

SAP Service Marketplace at service.sap.com/slo





26 March 2007

The following figure shows the underlying architecture of Contract Management.

See the Component Software Matrix for the correct catalog version.

Description:

IPC 7.0 is part of SAP WebAS

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

o Knowlege Management (KM)

o Collaboration room

o Universal Worklist (UWL)

o ADS can be deployed on the Portal

o LAC WPS can be deployed on the Portal

The Business Packages shown above are:

o BPSRM00_0.sca (BP for mySAP SRM 2007)

The XI Content Packages shown above are:

o SRMSERV6000_0.ZIP (XI Content for SAP SRM 2007 Server)

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

o SRMMDMCAT1000_1.ZIP (XI Content for SRM-MDM Catalog)

TREX is a separately installed instance. For scalability, multiple TREX instances canbe installed on multiple servers.

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



March 2007 27

The connection between the SRM Server and the R/3 Backend System is RFC-based. IDocs are only using in specific cases, for example when Billing Documentsare exchanged.

3.2.3 Implementation SequenceThis section lists the sequence of steps (installation, technical configuration, applicationconfiguration) required to implement the business scenario. Rows containing optionalcomponents are shaded. The scenario can function without these optional components; butthey do provide additional functions.

3.2.3.1 Installation

For latest Support Package and patch level requirements, see SAP ServiceMarketplace at service.sap.com/sp-stacks SAP SRM 6.0 and theRelease and Information Note which is available for each Support Packagestack (SAP note number is listed on the page).

See the section Overall Installation Sequence, especially if you want toimplement more than one SRM business scenario at a time.

For documentation referenced in the following table, see section References.

No. Action

(Corresponding Documentation)

Remarks/Subsequent Steps

Install SAP Process Integration

[Master Guide – SAP NetWeaver 7.0]

The use of SAP ProcessIntegration is optional but isrequired for loading contractsinto the catalog, sending productcategory hierarchies to SRM in afile (via PI), or for connecting tonon-SAP planning or executionsystems.

SAP Process Integrationrequires a dedicated SAP WebApplication Server meaning thatthe running of applications inother clients of the same SAPWeb AS is not supported.

1

If you installed SAP Process Integration, import theintegration objects for SAP SRM into the SAP ProcessIntegration.

Import the PI content for the following components:

SAP SRM Server 6.0

SAP SRM-MDM Catalog

SAP BI Content 7.0.3

/



28 March 2007

No. Action



Download and install the latest SLD Content from SAPService Marketplace at service.sap.com/swdcDownload Support Packages and Patches Entryby Application Group Additional ComponentsSAP Master Data for SLD.

/

Install/Integrate SAP R/3 or SAP R/3 Enterprise (SAPR/3 4.6C or higher recommended).

[SAP R/3 Installation on <Platform>: <Database>, or

Installation Guide – SAP R/3 Enterprise on <Platform>:<Database>]

SAP R/3 Enterprise is not part ofthis installation and is notcontained in the installationpackage. A separate SAP R/3Enterprise installation package isrequired.

2

Install SAP R/3 Plug-In (2004.1 or higher if one isavailable):

For the installation, see SAP Notes 704564 (R/3plug-in: PI 2004.1 installation/delta upgrade) and708736 (Release restrictions R/3 Plug-in2004.1).

For more information about SAP R/3 Plug-Ins,see SAP Service Marketplace atservice.sap.com/r3-plug-in.

Not required for customers withan ERP 2.0 back-end system.From ERP 2.0 onwards, theformer plug-in functionalities aredelivered with the SAP_APPLcomponent.

Not required if exclusively localPO handling is performed or noSAP R/3 system is used as aback-end system.

3 Install SAP SRM Server 6.0

[Installation Guide – SAP SRM Server on <Platform>:<Database>]

/

4 Install SAP Internet Transaction Server (7.00)

[SAP@Web Installation Guide located on the SAPServer Components CD]

You have to use the internal SAPITS. This is integrated into theSAP SRM Server (SAP ITS 7.0).

5 Install SAP SRM-MDM Catalog 2.0 as per SAP Note

1057316 /

6 Install SAP® NetWeaver 7.0 Search andClassification (TREX)

[SAP NetWeaver 7.0 Installation Guide: Search andClassification (TREX)]

Perform the installationsteps to set up an RFCconnection

Automatic languagerecognition is not required.You can adopt the defaultsettings for documentlanguages during theinstallation of SAP®

NetWeaver 7.0 TREX.

No Python extensions arerequired

7 Install SAP SRM Server for SAP SUS.

[Installation Guide – SAP SRM Server on <Platform>:

You can install a separate SAPSRM Server for SUS or use theSAP SRM Server you installed in

http://service.sap.com/r3-plug-in




March 2007 29

No. Action



<Database>] step 3 for that purpose.

8 Install SAP BI:

1. Install SAP Web AS ABAP 7.00, whichincludes SAP BI 7.0 and PI_BASIS2005_1_700.

[Installation Guide – SAP Web Application ServerABAP on <Platform>: <Database>]

2. Configure the database of your SAP Web ASfor SAP BI as described in SAP Note 567745.

3. Install SAP BI Business Content Add-OnBI_CONT 7.0.3 on the SAP Web AS ABAPsystem as described in SAP Note 916834.

For a minimal system landscape, you can install SAPBI on your SAP SRM Server. Install the SAP BIBusiness Content Add-On on the SAP SRM Server asdescribed in SAP Note 916834.

For more information, see the Master Guide – SAPNetWeaver 7.0.

The use of SAP BI is optional.See the description of thiscomponent in Component MatrixOverview to decide if it isrequired for your businessscenario.

After the BI ABAP upgrade,install the Java parts of BI (BI-Java) to take advantage of allnew functionality.

For more information, seeInstallation Guide – SAPNetWeaver 7.0.

9 Install SAP NetWeaver 7.0 – Enterprise Portal.


The use of SAP NetWeaverEnterprise Portal is mandatory. Itis required for the integration ofSAP SRM into a workset.

10 Import the following Business Packages into theEnterprise Portal:

Business Package for SAP SRM 2007

The SCA file delivered with theBusiness Package for SAP SRM 2007isBPSRM00_0.sca

Download the BusinessPackages from the SAPDeveloper Networkwww.sdn.sap.com PortalContent Portfolio



30 March 2007

3.2.3.2 ConfigurationSee SAP Solution Manager content for Contract Management.

3.2.3.3 UpgradeSee the Upgrade Master Guide – SAP SRM.


March 2007 31

3.3 Service ProcurementFor this business scenario, the following topics are covered:

Overview

Technical System Landscape


3.3.1 OverviewYou can use this business scenario to cover the entire service procurement process. Beforeordering external staff or services, you can, for example, send a request to one or more suppliersfor detailed information on a specific service or the availability of individual service agents. Afterreceiving the suppliers’ responses and accepting one of these bids, the corresponding purchaseorder is automatically created. Time and expenses then have to be entered into the system and,finally, the invoice is created.

You can integrate your suppliers into the procurement process by connecting a supplier systemsuch as Supplier Self-Services to your procurement system. This allows service agents to enterservices performed and create invoices for these services. You have to approve all documentscreated by your suppliers and you always retain a complete overview of all business processes.


For information about the technical system landscape and about how to plan thebusiness scenario to meet your needs, see: SAP Service Marketplace at service.sap.com/platforms Platform

Availability Matrix


The following figure shows the underlying architecture of Service Procurement including existingconnections.





3.3 Service Procurement

32 March 2007


March 2007 33

Legend:

XML

IPC 7.0 is part of the component AP 7.0

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

3.3.3 Implementation SequenceThis section lists the sequence of steps (installation, technical configuration, applicationconfiguration) required to implement the business scenario. Rows containing optionalcomponents are shaded. The scenario can function without these optional components; but theydo provide additional functions.


For latest Support Package and patch level requirements, see SAP ServiceMarketplace at service.sap.com/sp-stacks SAP SRM 6.0 and the



34 March 2007

Release and Information Note which is available for each Support Package stack(SAP note number is listed on the page).

See Overall Installation Sequence, if you want to implement more than one SRMbusiness scenario at a time.

For documentation referenced in the following table, see References.

No. Action

(Corresponding Documentation)Remarks/SubsequentSteps

Install SAP Process Integration.

[Master Guide – SAP NetWeaver 7.0, part of the installationpackage]

SAP Process Integrationrequires a dedicated SAPWeb Application Server.This means that therunning of applications inother clients of the sameSAP Web AS is notsupported.



SAP SRM Server 6.0


SAP SRM-MDM Catalog 2.0

/

1

Download and install the latest SLD Content from SAPService Marketplace at service.sap.com/swdcDownload Support Packages and Patches Entry byApplication Group Additional Components SAP MasterData for SLD.

/

2 Install/Integrate SAP R/3 or SAP R/3 Enterprise (SAP R/34.6C or higher recommended)



SAP R/3 and SAP R/3Enterprise are not part ofthis installation and are notcontained in theinstallation package. Aseparate SAP R/3 or SAPR/3 Enterprise installationpackage is required.


March 2007 35

No. Action


Install SAP R/3 Plug-In (2004.1 or higher if one is available)

For the installation, see SAP Notes 704564 (R/3 plug-in: PI 2004.1 installation/delta upgrade) and 708736(Release restrictions R/3 Plug-in 2004.1).

For more information about SAP R/3 Plug-Ins, seeSAP Service Marketplace at:service.sap.com/r3-plug-in

Not required for customerswith an ERP 2.0 back-endsystem. From ERP 2.0onwards, the former plug-in functionalities aredelivered with theSAP_APPL component.Otherwise the installationof the SAP R/3 Plug-In isrequired if you installed anSAP R/3 system in theprevious step.

3 Install SAP SRM Server 6.0 comprising:

SAP Bidding Engine

Supplier Self-Service


/


[SAP@Web Installation Guide located on the ServerComponents CD]

You have to use theinternal SAP ITS. This isintegrated into the SAPSRM Server (SAP ITS7.0).

The external ITS is notsupported.

5 Install SAP SRM-MDM Catalog 2.0 as per SAP Note1057316

/

6 Install SAP® NetWeaver 7.0 Search and Classification(TREX)


Perform theinstallation steps toset up an RFCconnection.

Automatic languagerecognition is notrequired. You canadopt the defaultsettings fordocumentlanguages duringthe installation ofSAP® NetWeaver7.0 TREX.

No Pythonextensions arerequired.





36 March 2007

No. Action




You can install a separateSAP SRM Server for SUSor use the SAP SRMServer you installed instep 3 for that purpose.

8 Install SAP BI 7.0 plus SAP BI Content 7.0.3:

1. Install SAP Web AS ABAP 7.00. This includes SAPB/ 7.0 and PI_BASIS 2005_1_700.


2. Configure the database of your SAP Web AS forSAP BI as described in SAP Note 567745.

3. Install SAP BI Business Content Add-On BI_CONT7.0.3 on the SAP Web AS ABAP system asdescribed in SAP Note 916834.

For a minimal system landscape, you can install SAP BI onyour SAP SRM Server. Install the SAP BI Business ContentAdd-On on the SAP SRM Server as described in SAP Note916834.


The use of the SAP BI isoptional. See thedescription of thiscomponent in ComponentMatrix Overview to decideif it is required for yourbusiness scenario.

After the BI ABAPupgrade, install the Javaparts of BI (BI-Java) totake advantage of all newfunctionality.



[Master Guide – SAP NetWeaver 7.0 ]

The use of SAPNetWeaver EnterprisePortal is optional. It isrequired for the integrationof SAP SRM into aworkset.

10 Import the following Business Package into the EnterprisePortal:

Business Package for SRM 6.0

The SCA file delivered with the BusinessPackage for SAP SRM 2007isBPSRM00_0.sca

Download the BusinessPackages from the SAPDeveloper Networkwww.sdn.sap.comPortal Content Portfolio

3.3.3.2 ConfigurationSee SAP Solution Manager content for Service Procurement.



March 2007 37

3.4 Strategic SourcingFor this business scenario, the following topics are covered:

Overview of the top-level scenario Strategy Sourcing comprising the following businessscenarios:

Supply Strategy Development

Supplier Selection

Contract Negotiation and Management

Relationship Monitoring

Operational Sourcing

Live Auctioning



3.4.1 OverviewYou can use this business scenario to process all your requirements and optimize your source ofsupply for each individual item. You can identify cost-saving opportunities and evaluate suppliers’ability to provide materials and services at low cost, high quality, and on schedule. Once youhave determined the best source of supply for your requirements, you can collaborate in projectteams both internally and with your suppliers to establish ongoing relationships based oncontracts and global outline agreements.

TasksSample tasks for the Strategic Sourcing business scenario include:

An electronics manufacturer discovering that certain components have become a commodity –and formulating a strategy to source them locally

A company opening a new facility in East Asia and redefining the sourcing strategy for thatregion

Analysis of hidden procurement costs triggering a supplier de-proliferation initiative

CPG company certifying different raw material vendors

A company locating different suppliers for upcoming new product development

A financial institution maintaining lists of suppliers for different MRO materials

A consulting company reducing its supplier base by establishing a preferred airline policy andreducing the number of permissible airlines

A bank aggregating its paper demand to improve MRO pricing A company presenting a ‘supplier cockpit’ tool to their professional purchasers where sources

of supply can be found or created for requirements


3.4 Strategic Sourcing

38 March 2007

A professional purchaser negotiating a long-term contract with a supplier to deliver goods of aspecific commodity

A professional purchaser and the IT department jointly negotiating a contract for an IT serviceproject with the IT service provider

A manufacturer monitoring its suppliers to gain insight into the value contributed to thebusiness from individual suppliers

A professional purchaser creating a reverse auction to find a supplier for specific non standardengineering software not covered by the catalog

A professional purchaser manually assigning a contract to a demand for office furniture


For information about the technical system landscape and about how to plan thebusiness scenario to meet your needs, see: SAP Service Marketplace at service.sap.com/platforms Platform

Availability Matrix





March 2007 39

The following figure shows the underlying architecture of Strategic Sourcing.


Legend:



40 March 2007

XML




March 2007 41



For latest Support Package and patch level requirements, see SAP ServiceMarketplace at service.sap.com/sp-stacks SAP SRM 6.0 and theRelease and Information Note which is available for each Support Package stack(SAP note number is listed on the page).

See Overall Installation Sequence, if you want to implement more than one SRMbusiness scenario at a time.


No. Action



[Master Guide – SAP NetWeaver 7.0] SAP Process Integrationrequires a dedicated SAPWeb Application Server.This means that therunning of applications inother clients of the sameSAP Web AS is notsupported.

If you installed SAP Process Integration, import the integrationobjects for SAP SRM into the SAP Process Integration.


SAP SRM Server 6.0


/

1

Download and install the latest SLD Content from SAP ServiceMarketplace at service.sap.com/swdc DownloadSupport Packages and Patches Entry by Application Group

Additional Components SAP Master Data for SLD.

/



42 March 2007

No. Action


Install/Integrate SAP R/3 or SAP R/3 Enterprise (SAP R/34.6C or higher recommended).



SAP R/3 and SAP R/3Enterprise are not part ofthis installation and are notcontained in the installationpackage. A separate SAPR/3 or SAP R/3 Enterpriseinstallation package isrequired.

2

Install SAP R/3 Plug-In (2004.1 or higher if one is available):

For the installation, see SAP Notes 704564 (R/3 plug-in:PI 2004.1 installation/delta upgrade) and 708736(Release restrictions R/3 Plug-in 2004.1).

For more information about SAP R/3 Plug-Ins, see SAPService Marketplace at:service.sap.com/r3-plug-in

Not required for customerswith an ERP 2.0 back-endsystem. From ERP 2.0onwards, the former plug-infunctionalities are deliveredwith the SAP_APPLcomponent. Otherwise theinstallation of the SAP R/3Plug-In is required if youinstalled an SAP R/3system in the previousstep.


SAP Bidding Engine

Supplier Self-Service


/

4 Install SAP Internet Transaction Server. (7.00)

[SAP@Web Installation Guide located on the ServerComponents CD]

You have to use theinternal SAP ITS. This isintegrated into the SAPSRM Server (SAP ITS 7.0).Note that the external ITSis not supported.

5 Install SAP SRM-MDM Catalog 2.0 as per SAP Note 1057316 /




March 2007 43

No. Action




Perform theinstallation steps toset up an RFCconnection.

Automatic languagerecognition is notrequired. You canadopt the defaultsettings fordocument languagesduring theinstallation of SAP®

NetWeaver 7.0TREX.

No Pythonextensions arerequired.

7 Install Live Auction Cockpit Web Presentation Server(LACWPS) 5.0.

[Component Installation Guide – SAP Supplier RelationshipManagement 6.0 ABAP + Java on <Platform>: <Database]

The use of Live AuctionWeb Presentation Server isoptional.

You can install LACWPSeither on a standaloneJ2EE Engine or on a J2EEEngine installed as an Add-In on the central instance.

8 Install SAP BI:

1. Install SAP Web AS ABAP 7.00. This includes SAP Bi7.0 and PI_BASIS 2005_1_700.


2. Configure the database of your SAP Web AS for SAPBI as described in SAP Note 567745.

3. Install SAP BI Business Content Add-On BI_CONT7.0.3 on the SAP Web AS ABAP system as describedin SAP Note 916834.


For more information, see the documentation Master GuideSAP NetWeaver 7.0.

The use of the SAP BI isoptional. See thedescription of thiscomponent in SoftwareComponents Overview todecide if it is required foryour business scenario.

After the BI ABAP upgrade,you should install the Javaparts of BI (BI-Java) to takeadvantage of all newfunctionality.




44 March 2007

No. Action



[Master Guide SAP NetWeaver 7.0]




The SCA file delivered with the BusinessPackage for SAP SRM 2007 isBPSRM00_0.sca



March 2007 45

3.4.3.2 ConfigurationSee SAP Solution Manager content for Strategic Sourcing.

3.4.3.3 UpgradeSee the documentation Upgrade Master Guide – SAP SRM.


3.5 Plan-Driven Procurement

46 March 2007

3.5 Plan-Driven ProcurementFor this business scenario, the following topics are covered:

Overview



3.5.1 OverviewDescriptionPlan-Driven Procurement automates and streamlines ordering processes for regularly neededcore materials. You can use this business scenario to procure requirements for materials thathave been generated in external systems. By integrating the SRM System with planning, design,and maintenance systems, you can accelerate your procurement and integrate the operationalprocurement with your Supply Chain Management solution. The business scenario supports third-party order processing. In this scenario the product goes directly from the vendor to the customerof the purchasing company. The purchase order to the vendor contains the necessary informationfor this.

You can set up the business scenario in such a way as to link one or more MaterialsManagement systems (SAP-MM) with Materials Requirements Planning (SAP-PP-MRP) to one ormore vendor systems (SAP Supplier Self-Services).

You can continue to plan requirements in SAP Advanced Planner and Optimizer (SAP APO).

TasksSample tasks for Plan-Driven Procurement include:

• A manufacturing company with many disparate planning systems consolidating allprocurement (direct and indirect) in one e-procurement hub

• A company performing planned and unplanned maintenance centralizing procurementactivities in a single application.

Deployment OptionsThe Extended Scenario deployment option is available.

You implement the SAP Enterprise Buyer system and one or more ERP systems. The completeprocurement process runs in the SAP Enterprise Buyer system. The leading purchase order iscreated in the SAP Enterprise Buyer system and changes to it must be made there, with a copyof it replicated to the back-end system. Goods receipts (confirmations) and invoices can also beentered initially in the SAP Enterprise Buyer system. Purchase order data is updated in the back-end system from SAP Enterprise Buyer. Goods receipt and invoice data are updated from theback-end system.

Requirement OptionsFor Plan-Driven Procurement, materials requirements from a product master can be receivedfrom:

• An APS (Advanced Planning and Scheduling) system, for example SAP APO

• SAP R/3 MM



March 2007 47

• Other external systems via an open XML interface


For information about the technical system landscape and about how to plan thebusiness scenario to meet your needs, see the Minimal System Landscape atSAP Service Marketplace at service.sap.com/platforms Platform AvailabilityMatrix.

The following figure shows the underlying architecture of Plan-Driven Procurement.


Legend:



48 March 2007

XML

• IPC 7.0 is part of the component AP 7.0

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

March 2007 49


3.5.3.1 Installation For latest Support Package and patch level requirements, see SAP Service Marketplace at

service.sap.com/sp-stacks SAP SRM 6.0 and the Release and Information Notewhich is available for each Support Package stack (SAP note number is listed on the page).

See section Overall Installation Sequence, if you want to implement more than one SRMbusiness scenario at a time.

It is assumed that an MRP (Material Requirements Planning) system – for example, SAPAPO – is already installed.


No. Action





SAP Process Integration requires adedicated SAP Web ApplicationServer. This means that the running ofapplications in other clients of thesame SAP Web AS is not supported.

After you install SAP Process Integration,import the integration objects for SAP SRM intothe SAP Process Integration.

Import the PI content for the followingcomponents:

• SAP SRM Server 6.0

• SAP BI Content 7.0.3 (optional)

/

1

Download and install the latest SLD Contentfrom SAP Service Marketplace atservice.sap.com/swdc DownloadSupport Packages and Patches Entry byApplication Group Additional ComponentsSAP Master Data for SLD.

/


50 March 2007

Install/Integrate SAP R/3 or SAP R/3Enterprise (SAP R/3 4.6C or higherrecommended).

[SAP R/3 Installation on <Platform>:<Database>, or

Installation Guide – SAP R/3 Enterprise on<Platform>: <Database>]

SAP R/3 and SAP R/3 Enterprise are notpart of this installation and are thereforenot contained in the installation package.A separate SAP R/3 or SAP R/3Enterprise installation package isrequired.

2

Install SAP R/3 Plug-In (2004.1 or higher ifone is available)

• For the installation, see SAP Notes704564 (R/3 plug-in: PI 2004.1installation/delta upgrade) and 708736(Release restrictions R/3 Plug-in 2004.1).

• For more information about SAPR/3 Plug-Ins, see SAP Service Marketplaceat: service.sap.com/r3-plug-in

Not required for customers with an ERP2.0 back-end system. From ERP 2.0onwards, the former plug-in functionalitiesare delivered with the SAP_APPLcomponent.

3 Install SAP SRM 2007.

[Installation Guide –SAP SRM Server on<Platform>: <Database>]

/

4 Install SAP Internet Transaction Server(7.00)

[SAP@Web Installation Guide located on theServer Components CD]

You have to use the internal SAP ITS,integrated into the SAP SRM Server(SAP ITS 7.0). Note that the external ITSis not supported.

5 Install SAP®

NetWeaver 7.0 Search andClassification (TREX)

[SAP NetWeaver 7.0 Installation Guide:Search and Classification (TREX)]

/


[Installation Guide –SAP SRM Server on<Platform>: <Database>]

You can install a separate SAP SRMServer for SUS or use the SAP SRMServer you installed in step 3 for thispurpose.


March 2007 51

7 Install SAP BI:

1. Install SAP Web AS ABAP 7.00,which includes SAP BI 7.0,PI_BASIS 2005_1_700.

[Installation Guide – SAP Web ApplicationServer ABAP on <Platform>: <Database>]

2. Configure the database of your SAPWeb AS for SAP BI according toSAP Note 567745.

3. Install SAP BI Business ContentAdd-On BI_CONT 7.0.3 on the SAPWeb AS ABAP system according toSAP Note 916834.

For a minimal system landscape, you caninstall SAP BI on your SAP SRM Server.Install the SAP BI Business Content Add-Onon the SAP SRM Server as described in SAPNote 916834.

For more information, see the Master Guide– SAP NetWeaver 7.0, included in theinstallation package.

The use of SAP BI is optional. See thedescription of this component in sectionComponent Matrix Overview to decide if itis required for your business scenario.

After the BI ABAP upgrade, you shouldinstall the Java parts of BI (BI-Java) totake advantage of all new functionality.For more information, see InstallationGuide – SAP NetWeaver 7.0.

8 Install SAP NetWeaver Enterprise Portal7.0.

[Master Guide – SAP NetWeaver 7.0, part ofthe installation package]

The use of SAP NetWeaver EnterprisePortal is optional. It is required for theintegration of SAP SRM into a workset.

9 Import the following Business Package intothe Enterprise Portal:

Business Package for SAP SRM2007

The SCA file delivered withthe Business Package forSAP SRM 2007 isBPSRM00_0.sca

Download the Business Packages fromthe SAP Developer Networkwww.sdn.sap.com Portal ContentPortfolio

3.5.3.2 ConfigurationSee SAP Solution Manager content for Plan Driven Procurement.

3.5.3.3 UpgradeSee the documentation Upgrade Master Guide – SAP SRM.


52 March 2007

3.6 Catalog Content ManagementFor this business scenario, the following topics are covered:

Overview



3.6.1 OverviewDescriptionThe Catalog Content Management business scenario provides a solution for creating,maintaining, and managing catalog content within your e-procurement application.

TaskA Catalog Manager imports structures and adjusts catalog content in the SAP MDM DataManager and then makes content available to catalog users via Web browser.


For information about the technical system landscape and about how to planthe business scenario to meet your needs, see: SAP Service Marketplace at service.sap.com/platforms Platform

Availability Matrix



March 2007 53

The following figure shows the underlying architecture of the SRM-MDM Catalog includingexisting connections.



54 March 2007

Legend:

XML



3.6.3 Implementation Sequence


March 2007 55

This section lists the sequence of steps (installation, technical configuration, applicationconfiguration) required to implement the business scenario. Rows containing optionalcomponents are shaded. The scenario can function without these optional components; butthey do provide additional functions.



See the section Overall Installation Sequence, especially if you want toimplement more than one SRM business scenario at a time.


No. Action




SAP Process Integrationrequires a dedicated SAPWeb Application Server.This means that therunning of applications inother clients of the sameSAP Web AS is notsupported.

1

After you install SAP Process Integration, import the integrationobjects for SAP SRM into the SAP Process Integration.


SAP SRM Server 6.0

/


SAP Bidding Engine


/

3 Install SAP SRM-MDM Catalog 2.0.

For information, see SAP Note 1057316.

/


56 March 2007

No. Action






March 2007 57

3.6.3.2 ConfigurationSee SAP Solution Manager content for Catalog Content Management.


58 March 2007

3.7 Self-Service ProcurementFor this business scenario, the following topics are covered:

Overview



3.7.1 OverviewSelf-Service Procurement enables your employees to create and manage their ownrequirement requests. This relieves your purchasing department of a huge administrativeburden while making the procurement process both faster and more responsive.

TasksTypical tasks for the business scenario Self-Service Procurement tasks include:

Employees buying office materials or IT equipment from catalogs

Employees buying items that are not covered in catalogs from centrally agreedcontracts, for example procurement of services

Capturing requirement requests for materials not covered in catalogs or outlineagreements by employees to provide a single point of contact for purchase requisitions

Professional buyers purchasing standard, indirect material without auction


March 2007 59

Deployment OptionsThe following section describes the deployment options that are supported for Self-ServiceProcurement. However, the open and flexible design of SAP Enterprise Buyer also allowsyou to combine the described deployment options.

Classic deployment

You implement the SAP Enterprise Buyer system and one or more ERP systems. AllMaterials Management (MM) is mapped in the ERP system. Accounting (FI) andControlling (CO) are processed in the ERP system.

The extended classic deployment

You implement the SAP Enterprise Buyer system and one or more ERP systems. Thecomplete procurement process takes place in the SAP Enterprise Buyer system. Thepurchase order in the SAP Enterprise Buyer system is the leading purchase order.Goods receipts (confirmations) and invoices can be pre-entered in the SAP EnterpriseBuyer system. Purchase order data in the back-end system is updated from SAPEnterprise Buyer. Goods receipt and invoice data is updated from the back-endsystem.

The standalone deployment

In this deployment scenario, you have no Materials Management (MM) in your ERPsystem and are using the Materials Management functions in the SAP EnterpriseBuyer system for all non production procurement. If required, you can connectAccounting (FI) and Controlling (CO), however, this is optional.


For information about the technical system landscape and about how to planthe business scenario to meet your needs, see: the section Minimal System Landscape

SAP Service Marketplace at service.sap.com/platforms PlatformAvailability Matrix



60 March 2007

The following figure shows the underlying architecture of Self-Service Procurement.


Legend:


March 2007 61

XML




62 March 2007

3.7.3 Implementation SequenceThis section lists the sequence of steps (installation, technical configuration, applicationconfiguration) required to implement the business scenario. Rows containing optionalcomponents are shaded. The scenario can function without these optional components; butthey do provide additional functions.


See Overall Installation Sequence, if you want to implement more than oneSRM business scenario at a time.



No. Action

[Corresponding Documentation]




The use of SAP ProcessIntegration is optional but it isrequired for outbound XML-based messaging or forconnecting non-SAP planning orexecution systems.

SAP Process Integrationrequires a dedicated SAP WebApplication Server. This meansthat the running of applicationsin other clients of the same SAPWeb AS is not supported.

1



SAP SRM Server 6.0



/


March 2007 63

No. Action



Download and install the latest SLD Content from SAPService Marketplace at service.sap.com/swdcDownload Support Packages and Patches Entryby Application Group Additional ComponentsSAP Master Data for SLD.

/

Install/Integrate SAP R/3 or SAP R/3 Enterprise (SAPR/3 4.6C or higher recommended).



SAP R/3 and SAP R/3 Enterpriseare not part of this installationand are not contained in theinstallation package. A separateSAP R/3 or SAP R/3 Enterpriseinstallation package is required.

2

Install SAP R/3 Plug-In (2004.1 or higher if one isavailable):

For the installation, see SAP Notes 704564 (R/3plug-in: PI 2004.1 installation/delta upgrade) and708736 (Release restrictions R/3 Plug-in2004.1).

For more information about SAP R/3 Plug-Ins,see SAP Service Marketplace atservice.sap.com/r3-plug-in.

Not required for customers withan ERP 2.0 back-end system.From ERP 2.0 onwards, theformer plug-in functionalities aredelivered with the SAP_APPLcomponent.

Not required if exclusively localPO handling is performed or noSAP R/3 system is used asback-end system.

3 Install SAP SRM 2007


/


[SAP@Web Installation Guide located on the SAPServer Components CD]

You have to use the internal SAPITS, integrated into the SAPSRM Server (SAP ITS 7.0).

The external ITS is notsupported.

5 Install SAP Catalog Content Management 2.0 (CCM)or SRM-MDM Catalog 2.0

For information, see:

SAP Note 835170 (regarding SAP-CCM)

SAP Note 1057316 (regarding SRM-MDMCatalog)

/

6 Install SAP® NetWeaver 7.0 Search andClassification (TREX)


Perform the installationsteps to set up an RFCconnection

Automatic languagerecognition is not required.You can adopt the defaultsettings for documentlanguages during theinstallation of SAP®




64 March 2007

No. Action



NetWeaver 7.0 TREX.

No Python extensions arerequired



You can install a separate SAPSRM Server for SUS or use theSAP SRM Server you installed instep 3 for that purpose.

8 Install SAP BI:

1. Install SAP Web AS ABAP 7.00, which includesSAP BI 7.0 and PI_BASIS 2005_1_700.


2. Configure the database of your SAP Web AS forSAP BI as described in SAP Note 567745.

3. Install SAP BI Business Content Add-On BI_CONT7.0.2 on the SAP Web AS ABAP system asdescribed in SAP Note 916834.

For a minimal system landscape, you can install SAPBI on your SAP SRM Server. Install the SAP BIBusiness Content Add-On on the SAP SRM Server asdescribed in SAP Note 916834.


The use of SAP BI is optional.See the description of thiscomponent in ComponentSoftware Matrix Overview todecide if it is required for yourbusiness scenario.

After the BI ABAP upgrade, youshould install the Java parts of BI(BI-Java) to take advantage of allnew functionality. For moreinformation, see InstallationGuide – SAP NetWeaver 7.0.

9 Install SAP NetWeaver Enterprise Portal 7.0.


The use of SAP NetWeaverEnterprise Portal is optional. It isrequired for the integration ofSAP SRM into a workset.

10 Import the following Business Package into theEnterprise Portal:


The SCA file delivered with theBusiness Package for SAP SRM 2007is BPSRM00_0.sca

Business Package for Supplier Collaboration 2.0

Download the BusinessPackages from the SAPDeveloper Networkwww.sdn.sap.com PortalContent Portfolio


March 2007 65

3.7.3.2 ConfigurationSee SAP Solution Manager content for Self-Service Procurement.


3.8 Spend AnalysisFor this business scenario, the following topics are covered:

Overview



3.8.1 OverviewSpend Analysis is a decision-support application that enables you, as a purchaser, to analyzeyour total spending across system and organizational boundaries. The analyses can beperformed per supplier, per product, or per product category.

The system landscape comprises one or more SAP R/3 back-end and SAP Enterprise Buyersystems connected to a single SAP NetWeaver Business Information Warehouse (SAP BI).Analyses are based on documents from Financial Accounting, restructured according toprocurement needs. You can enrich document information with category and contractinformation from the procurement systems.

Master data has to be consolidated to identify identical suppliers and identical productsstemming from either the same or different systems. Two options are available for identifyingidentical suppliers and identical products:

Use the Advanced Master Data Maintenance included in SAP BI.Advanced Master Data Maintenance provides you with a mechanism to manuallymatch supplier records and product records. You can also assign standard categoryschemas from your local systems such as UNSPSC or ecl@ss to the purchasingcategories enabling you to report on consolidated product categories.

SAP MDM can be used for matching, grouping and classification of supplier andproducts. There is an integration between SAP BI and SAP MDM.


66 March 2007


For information about the technical system landscape and about how to planthe business scenario to meet your needs, see: SAP Service Marketplace at service.sap.com/platforms Platform

Availability Matrix

The following figure shows the underlying architecture of Spend Analysis including existingconnections.



March 2007 67

Legend:

XML



3.8.3 Implementation SequenceThis section lists the sequence of steps (installation, technical configuration, application andconfiguration) required to implement the business scenario. Rows containing optionalcomponents are shaded. The scenario can function without these optional components; butthey do provide additional functions.




68 March 2007

See Overall Installation Sequence, if you want to implement more than oneSRM business scenario at a time.


No. Action(Corresponding Documentation)

Remarks/SubsequentSteps

Install/Integrate SAP R/3 or SAP R/3 Enterprise (SAP R/34.6C or higher recommended)



SAP R/3 and SAP R/3Enterprise are not part ofthis installation and arenot contained in theinstallation package. Aseparate SAP R/3 or SAPR/3 Enterprise installationpackage is required.

1

Install SAP R/3 Plug-In (2004.1 or higher if one is available)

For the installation, see SAP Notes 704564 (R/3 plug-in:PI 2004.1 installation/delta upgrade) and 708736(Release restrictions R/3 Plug-in 2004.1).

For more information about SAP R/3 Plug-Ins, see SAPService Marketplace at:service.sap.com/r3-plug-in

Not required forcustomers with an ERP2.0 back-end system.From ERP 2.0 onwards,the former plug-infunctionalities aredelivered with theSAP_APPL component.Otherwise the installationof the SAP R/3 Plug-In isrequired if you installed anSAP R/3 system in theprevious step.


SAP Bidding Engine

Supplier Self-Services


/


[SAP@Web Installation Guide]

You have to use theinternal SAP ITS,integrated into the SAPSRM Server (SAP ITS7.0).



/

5 Install SAP BI

1. Install SAP Web AS ABAP 7.00, which includes SAPBI 7.0 and PI_BASIS 2005_1_700.


2. Configure the database of your SAP Web AS for SAP

After the BI ABAPupgrade, you shouldinstall the Java parts of BI(BI-Java) to takeadvantage of all newfunctionality. For moreinformation, seeInstallation Guide – SAP




March 2007 69

No. Action


BI as described in SAP Note 567745.

3. Install SAP BI Business Content Add-On BI_CONT7.0.2 on the SAP Web AS ABAP system as describedin SAP Note 916834.


For more information, see the Master Guide – SAP NetWeaver7.0.

NetWeaver 7.0.

6 Install SAP NetWeaver Enterprise Portal 7.0.


The use of SAPNetWeaver EnterprisePortal is mandatory. It isrequired for the integrationof SAP SRM into aworkset.




3.8.3.2 ConfigurationSee SAP Solution Manager content for Spend Analysis.


4 Solution-Wide Topics

70 March 2007

4 Solution-Wide Topics4.1 Solution ManagerSAP provides the SAP Solution Manager as the platform for efficiently supporting theimplementation and operation of your SAP SRM solution. SAP Solution Manager significantlyaccelerates the implementation process and helps you achieve your business goals. Itcontains predefined implementation content (IMG activities and transactions as well asdocumentation and SAP Notes) to help you configure your SRM Solution. In addition, SAPdelivers Support Services based on the business scenarios designed and documented inSAP Solution Manager.

The use of SAP Solution Manager is mandatory for SAP SRM 2007. When you install SAPSRM Server 6.0 or upgrade to this release, you are asked to enter a key generated by theSolution Manager. For more information, see the installation or upgrade guide for SAP SRMServer 6.0.

In SAP SRM 2007, the SAP Solution Manager contains standard implementation content fornine business scenarios, covering all key capabilities of the SAP SRM Solution Map. Thisenables a fast implementation of the entire solution in units of business processes.In your SAP SRM project, execute the following activities using SAP Solution Manager:

Documentation of core business processes that are changed or implemented duringRamp-Up

Plan your Solution Landscape

Connection of existing systems and activation of SAP EarlyWatch Alert

Setup Solution Manager Diagnostics for root cause analysis of Java components

Handover of processes and systems to support organization after Go Live

Configuration of your scenario according to the documentation contained in SAPSolution Manager

Document, configure, and test the previously defined business processes.Train users via SAP Solution Manager.

For more information, see the following information source for SAP Solution Manager:

System infrastructure, scenarios, installation and configuration of SAP SolutionManager: Master Guide – SAP Solution Manager available on SAP ServiceMarketplace at service.sap.com/instguides SAP Components SAPSolution Manager.

Benefits and usage scenarios: SAP Solution Manager – Learning Maps available onSAP Service Marketplace at service.sap.com/rkt-solman orservice.sap.com/solutionmanager.

Additional information: SAP Service Marketplace atservice.sap.com/solutionmanager and in the documentation Master GuideSAP NetWeaver 7.0 available at service.sap.com/instguides

The following information summarizes installation considerations:

Each SAP SRM (or SAP NetWeaver) system landscape must be assigned to aninstallation of the SAP Solution Manager. In the event of a support relevant incidentwithin your SAP system landscape, SAP Support requires remote access to the SAPSolution Manager that hosts the affected system landscape.

4 Solution-Wide Topics

March 2007 71

If you already have a SAP Solution Manager deployment in place, you can also use itto manage the solution you build with SAP NetWeaver and SAP SRM as well. In thiscase, we recommend updating SAP Solution Manager and Solution Manager contentto the latest version.

It is possible to install multiple instances of the SAP Solution Manager. In this case,each installation should host separate business solutions.

To reduce the risk of unavailability, do not install SAP Solution Manager as a centralcomponent. Instead, operate a two system landscape with test and productionenvironment of SAP Solution Manager, especially if you are using time criticalfunctions like Support Desk. If you also develop your own content, a three-systemlandscape with development, test and production environment is recommended.

5 References

72 March 2007

5 References

Make sure you have the latest documentation version by checking SAP ServiceMarketplace at service.sap.com/instguides SAP Business Suite Applications

SAP SRM Using SAP SRM Server 6.0 immediately before starting the installation.List of referenced documentation for this SAP Business Suite solution and its businessscenarios.

Title Where to find

Installation Guide – SAP SRM 6.0 on<Platform>: <Database>

SAP Service Marketplace at:service.sap.com/instguides SAPBusiness Suite Applications SAP SRM

Using SAP SRM Server 6.0

Master Guide – SAP NetWeaver 7.0 Part of the SAP NetWeaver delivery; SAPService Marketplace at:service.sap.com/instguides

Upgrade Master Guide –SAP SRM 2007

SAP Service Marketplace at:service.sap.com/instguides SAPBusiness Suite Applications SAP SRM

Using SAP SRM Server 6.0

Installation Guide SAP NetWeaver 7.0Search and Classification (TREX)

SAP Service Marketplace atservice.sap.com/instguides SAPNetWeaver SAP NetWeaver 7.0 (2004s)

Installation Installation StandaloneEngines SAP NetWeaver Search andClassification TREX

Language Transport (BC-CTS-LAN) 6.40 SAP Service Marketplace at:service.sap.com/instguides SAPNetweaver SAP NetWeaver 7.0 (2004s)

Operations Cross-NetWeaverLanguage Transport Documentation SAPNetWeaver 7.0

SAP Front End Installation Guide SAP NetWeaver 7.0 DVD

* Presentation* Server Components* Content Server

Installation Guide – SAP R/3 Enterprise on<Platform>: <Database>

Part of the SAP R/3 Enterprise delivery, SAPService Marketplace at: service.sap.com/instguides SAP Components SAPR/3 Enterprise <release>

SAP R/3 Installation on <Platform>:<Database>

Part of the SAP R/3 delivery, SAP ServiceMarketplace at: service.sap.com/instguides SAP Components SAPR/3 <release>

<Business Scenario> See SAP Solution Manger for SRM





5 References

March 2007 73

Configuration documentation for SAP SRM2007 for each business scenario

All configuration documentation for SAPSRM 2007 is available in SAP SolutionManager ST-ICO 160 for SRM 3.0.

Note: This information is available only in theSolution Manager. Additionally, an SRMimplementation roadmap and an SRMupgrade roadmap are available there.

List of SAP NotesThe following table lists all SAP Notes referred to in this document.

SAP Note Number Title

1102079 SRM 2007 SP03 BI Content Changes

995220 SRM 6.0 Support Package 00




854170 Switching on component VM Container

66971 Supported frontend platforms

967123 SAP SRM 6.0 Installation on Windows

972263 SAP SRM 6.0 Installation on UNIX

836200 Importing PI content

1057316 SRM-MDM Catalog 2.0 Installation

704564 R/3 Plug-In PI 2004 Installation/Delta Upgrade

1095730 SRM 6.0 Support Package 02 and higher

708736 Release Restrictions R/3 Plug-in

567745 Composite Note BW 3.X Performance: DB-Specific Setting

916834 BI_Cont. 7.03 Installation and Upgrade Information

835170 Installation or Delta Upgrade to CCM 2.0

1080594 Installing CPRXRPM 400 SR1 on Basis Release 700

6 Additional Information

74 March 2007

6 Additional Information6.1 Importing Integration Objects for SAPSRM on SAP Process IntegrationPerform the following procedure to:

Complete the SAP Process Integration installation for SAP SRM (for more information,see section <Your Business Scenario> Implementation Sequence above) or

Patch the already existing SAP Exchange Infrastructure as part of patching SAP SRM(for more information, see the corresponding SAP Note Support Package <Number> forSAP SRM 2007 and Patching your SAP SRM Solution.

For more information about importing Integration Objects, see SAP Note836200.

If PI content is imported, existing content in the namespaces used by SAP islost. Customer changes in those namespaces are treated as modificationsand are also lost. There is no modification adjustment available.

Procedure1. On the SAP Exchange Infrastructure host (Integration Builder), create the directory

<systemdir>/xi/repository_server/import, if it does not already exist.

<systemdir> is the system directory that you specified during theinstallation of the SAP Exchange Infrastructure server.

2. Copy all *.TPT files from <SRM-XI Content CD>/TPT to the directory<systemdir>/xi/repository_server/import.

If you want to patch the existing SAP Exchange Infrastructure as part ofpatching SAP SRM, perform the following steps instead:a. Download all *.TPZ files from the SAP Service Marketplace at the Internet

address: service.sap.com/swdc Download Support Packages andPatches Entry by Application Group SAP Application ComponentsSAP SRM (WITH EBP) SAP SRM 6.0 XI CONTENT

b. Copy these downloaded *.TPZ files to the directory<systemdir>/xi/repository_server/import.

3. Start the Repository (Design) tool of the Integration Builder.

For more information, see the SAP Process Integration online documentationat help.sap.com SAP NetWeaver Process Integration SAPExchange Infrastructure Design and Configuration Time IntegrationBuilder.

4. Choose Object Import XI 3.0 Development Object.

6 Additional Information

March 2007 75

5. Select all *.TPT files you have copied to the import directory.

Successfully imported files get automatically moved to the directory<systemdir>/xi/repository_server/importedFiles.

6.2 Patching Your SAP SRM SolutionTo patch your SAP SRM solution (for example, from SRM 4.0 SP02 to SRM 4.0 SP03),proceed as follows:

1. Check SAP Service Marketplace at service.sap.com/patches SAP SupportPackages in Detail Schedules for Support Packages SRM Support PackageSchedule EBP 6.0 Support Package Schedule for the number of the latest releasedSupport Package and the corresponding SAP Note Support Package <Number> for SAPSRM 2007

2. Patch your SAP components according to this SAP Note Support Package <Number> forSAP SRM 2007:

You can obtain required support packages / binary patches from SAP ServiceMarketplace at the Internet address: service.sap.com/patches Entry byApplication Group SAP Application Components SRM (WITH EBP) SRM6.0..

For general information about installing Java Support Packages with Java SupportPackage Manager (JSPM), see the SAP Help Portal at help.sap.comDocumentation SAP NetWeaver SAP NetWeaver 7.0 SAP NetWeaverLibrary SAP NetWeaver Key Capabilities of Solution Life Cycle ManagementSoftware Life-Cycle Management Software Maintenance Java SupportPackage Manager.

If required, patch the existing SAP Exchange Infrastructure according to section 6.1.

7 Media List

76 March 2007

7 Media ListSoftware Components and DVD / CD StructureThis section summarizes the exact location of the required software components on thecorresponding DVD(s) and CD(s) shipped with the SAP SRM 6.0 package. If appropriate,references to other sources are also included.

The material numbers of the corresponding DVDs and CDs may change as newupdates become necessary. Therefore, make certain that you always use the mostup-to-date version of the indicated data carrier(s).

The following table lists the software components that belong to SAP SRM 6.0. For moreinformation about the SAP NetWeaver media list, go to service.sap.com/installNW7.0 orservice.sap.com/upgradeNW7.0. For more information about the SAP Solution Managermedia list, go to service.sap.com/instguides SAP Components SAP SolutionManager Release 4.0 Media List SAP Solution Manager 4.0.

Before you attempt to install any of the following components, ensure that you are using thecurrent version of the installation documentation. For SAP NetWeaver ’04s, you can find therelevant guides at service.sap.com/instguidesNW7.0 Installation.

Additionally, visit the SAP Software Distribution Center in SAP Service Marketplace atservice.sap.com/swdc. Within the SAP Software Distribution Center, you can download anySAP software component(s) to which your enterprise is entitled. The correspondingauthorizations are automatically generated from the licenses. To obtain the software you require,you can either download the corresponding files directly (by simply clicking on the file name) oryou can use the SAP Download Manager.

http://service.sap.com/swdc

7 Media List

March 2007 77

SAP SRM 2007Components DVD / CD Label Description / Additional

InformationmySAP Business Suite 2005Installation Master forSAP NetWeaver 2004s SR2SAP SRM 6.0

SAP SRM 6.0 Installation Master<Operating System>

SAP SRM 6.0SAP Installation Export

SAP SRM 6.0 Installation Export

SAP SRM 6.0SAP Language DVDDE, EN, ES, FR, IT, NL, CA, CS,DA, EL, FI, HU, NO, PL, PT, RU,SK, TR, JA, KO, TH, ZF, ZHSAP SRM 6.0SRM ComponentscProjectsPortal ContentXI Content

SAP SRM 6.0 Components

SAP SRM 6.0SAP Upgrade Master

SAP SRM 6.0 Java Upgrade for all OSSAP SRM 6.0 Upgrade Master<Operating System>SAP SRM 6.0 UC-Upgrade Master<Operating System>

SAP SRM 6.0SAP Upgrade Export

SAP SRM 6.0 Upgrade Export

SRM-MDM CATALOG 2.0mySAP SRM Catalog

SRM-MDM CATALOG 2.0

Complete NetWeave2004 SR2,except for the Installer DVD DVD

SAP SRM 6.0 SAP SRM 2007SP03based on SAP NetWeaver® 7.0Support Package Stack 12HTML – Help for WindowsStandard HTML (Plain HTML)

CPRXRPM 400Project and Portfolio Management4.based on NetWeaver® 2004sSPS 07including BI Content Add-On 3HTML-Help for WindowsStandard HTML (Plain HTML)

DVD ODoc. Project/Portfolio Mngmnt.4.00

Online Doc SRM 6.0 No Online Doc for SRM 6.0 SP00

SAP SRM Server 6.0

SAP SRM 6.0Java Components

SAP SRM 6.0 Java Components

8 The Main SAP Documentation Types

78 March 2007

8 The Main SAP Documentation TypesThe following is an overview of the most important documentation types that you need inthe various phases in the life cycle of an SAP solution.

Documentation types in the software life cycle

ImplementationImplementation

Master Guide

ConfigurationDocumentation Release Notes

ComponentInstallation Guide

ComponentUpgrade Guide

Upgrade Master Guide

OperationOperation UpgradeUpgrade

Solution ManagementGuide

Implementation Guide (IMG) Delta and Upgrade IMG

Security Guide

SAP Library

SAPterm

Cross-Phase DocumentationSAPterm

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30languages, as well as many definitions and glossary entries in English and German.

Target group:

Relevant for all target groups

Current version:

Located in the SAP Help Portal at help.sap.com Additional Information Glossary(direct Access) or Terminology (available as terminology CD)

In the SAP-System in transaction STERM

SAP Library

The SAP Library is a collection of function- and process-oriented documentation for SAPcomponents. The SAP Library also contains the Business Scenario Descriptions.

Target group:

o Consultants

o System administrators


March 2007 79

o Project teams for implementations or upgrades

Current version:

o Located in the SAP Help Portal at help.sap.com

o Located in the SAP Service Marketplace at service.sap.com/ibc (only the BusinessScenario Descriptions)

Implementation Guide (IMG)

The Implementation Guide is a tool for configuring the SAP system to meet customerrequirements. Its structure and documentation are component-oriented.

Target group:

o Solution consultants

o Project teams for implementations or upgrades

Current version:

o In the SAP menu of the SAP system under Tools Customizing IMG

ImplementationMaster Guide

The Master Guide is the starting point for implementing an SAP solution. It lists the requiredSAP components and third party applications that are required for each Business Scenario. Itprovides scenario-specific descriptions of preparation, execution, and follow-up of animplementation. It also offers references to other documents, such as Component InstallationGuides and SAP Notes.

Target group:

o Technology consultants

o System administrators

o Project teams for implementations

Current version:

o Located in the SAP Service Marketplace at service.sap.com/instguides

Component Installation Guide

The Component Installation Guide describes the technical implementation of an SAPcomponent, taking into account the combinations of operating systems and databases. Itdoes not describe any business-related configuration.

Target group:



Current version:


Configuration Documentation in SAP Solution Manager

SAP Solution Manager is a tool with various functions, one of its main functions being theconfiguration of SAP solutions and Business Scenarios. It contains IMG activities,transactions, and so on, as well as documentation. Instead of the configurationdocumentation in SAP Solution Manager, there may be separate Business Scenario


80 March 2007

Configuration Guides in the SAP Service Marketplace for earlier shipments of the BusinessScenarios.

Target group:

o Solution consultants


Current version:

o In SAP Solution Manager

o Located in the SAP Service Marketplace at service.sap.com/ibc

UpgradeUpgrade Master Guide

The Upgrade Master Guide is the starting point for upgrading the Business Scenarios of anSAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an upgrade. It also refers to other documents, such as the Component Upgrade Guidesand SAP Notes. Instead of an Upgrade Master Guide, there may be several BusinessScenario Upgrade Guides or a Solution Upgrade Guide for earlier shipments of the BusinessScenarios of an SAP solution.

Target group:


o Project teams for upgrades

Current version:


Component Upgrade Guide

The Component Upgrade Guide describes the technical upgrade of an SAP component,taking into account the combinations of operating systems and databases. It does notdescribe any business-related configuration.

Target group:



Current version:


Release Notes

Release notes are documents that contain short descriptions of new features or changes inan SAP component since the previous release. Release notes about ABAP developmentsenable the SAP system to generate delta and upgrade IMGs.

Target group:

o Consultants


Current version:

o Located in the SAP Service Marketplace at service.sap.com/releasenotes


March 2007 81

o In the SAP menu of the SAP system under Help Release information