Master Guide SRM 7.0

Master Guide
SAP Supplier Relationship Management powered by SAP

NetWeaver
Using SAP SRM Server 7.0
Target Audience
n System administrators
n Technology consultants
PUBLIC
Document version: 1.3 07/11/2011
Material number: 50103026
Document History
Caution
Before you start the implementation, make sure you have the latest version of this document. You
can find the latest version at the following location: http://service.sap.com/instguides
Installation and Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM Server 7.0 .
The following table provides an overview of the most important document changes.
Version
Date
Description
1.2
3/12/2010
Information on the Catalog Content Management business scenario added to

section 2.2 Software Component Matrix
1.3
7/11/2011
Information added about installation options with SAP NetWeaver 7.3 (for Java
Hubs)
2/72
PUBLIC
07/11/2011
Table of Contents
Chapter 1
1.1
1.2
1.3
Getting Started . .
About this Document .
Planning Information .
Important SAP Notes .
.
.
.
.
.
.
.
.
7
8
10
11
Chapter 2
2.1
2.1.1
2.1.2
2.1.3
2.2
2.3
2.4
2.5
2.5.1
2.5.2
2.5.3
2.5.4
.
.
.
.
.
.
.
.
.
.
.
.
13
13
13
15
16
16
17
18
19
19
19
19
2.6
2.7
2.8
2.8.1
2.8.2
2.8.3
SAP SRM Overview . . . . . . . . . . . . . . . . . . . .

Software Units of SAP SRM . . . . . . . . . . . . . . . . . .
Application Components: SAP SRM Software Units . . . . . . . . .
Technology Components . . . . . . . . . . . . . . . . . .
Non-SAP Components . . . . . . . . . . . . . . . . . . .
Software Component Matrix . . . . . . . . . . . . . . . . .
System Landscape . . . . . . . . . . . . . . . . . . . . .
Overall Installation Sequence . . . . . . . . . . . . . . . . .
Automated Post-Installation Configuration Tools . . . . . . . . .
Automated Configuration of the Portal Systems . . . . . . . . . .
Automated Configuration of SAP SRM and SAP ERP System Integration .
Automated Configuration of SAP SRM and One Client System Integration
Automated Configuration of SAP SRM and SAP NetWeaver BW System
Integration . . . . . . . . . . . . . . . . . . . . . . . .
Service-Oriented Architecture (SOA) . . . . . . . . . . . . . .
SAP SRM on One Client in SAP ERP . . . . . . . . . . . . . .
Flexible Deployment Variants . . . . . . . . . . . . . . . . .
Deployment Options . . . . . . . . . . . . . . . . . . . .
Technical Scenarios . . . . . . . . . . . . . . . . . . . .
Business Scenarios . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
20
20
21
21
21
22
22
Chapter 3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.2
3.2.1
3.2.2
Business Scenarios of SAP SRM . . . . . . . . . . .

Self-Service Procurement . . . . . . . . . . . . . .
Overview of Self-Service Procurement (Classic) . . . . . .
Overview of Self-Service Procurement (Extended Classic) . . .
Technical System Landscape . . . . . . . . . . . . .
Implementation Sequence . . . . . . . . . . . . . .
Plan-Driven Procurement . . . . . . . . . . . . . .
Overview of Plan-Driven Procurement with Plant Maintenance
Overview of Plan-Driven Procurement with Supplier Integration
.
.
.
.
.
.
.
.
.
23
23
23
24
24
25
28
28
28
07/11/2011
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
PUBLIC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3/72
3.2.3
3.2.4
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.4
3.4.1
3.4.2
3.4.3
3.5
3.5.1
3.5.2
3.5.3
3.5.4
3.6
3.6.1
3.6.2
3.6.3
3.7
3.7.1
3.7.2
3.7.3
3.7.4
Technical System Landscape . . . . . . . .

Implementation Sequence . . . . . . . . .
Service Procurement . . . . . . . . . . .
Overview of Service Procurement (Classic) . . .
Overview of Service Procurement External Staffing
Catalog Content Management . . . . . . .
Overview . . . . . . . . . . . . . . .
Analytics . . . . . . . . . . . . . . .
Overview of Spend Analysis . . . . . . . .
Overview of Supplier Evaluation . . . . . . .
Operational Contract Management . . . . . .
Overview . . . . . . . . . . . . . . .
Strategic Sourcing . . . . . . . . . . . .
Overview of Strategic Sourcing with RFx . . . .
Overview of Strategic Sourcing with Live Auction
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
29
30
32
32
33
34
34
37
37
37
38
39
39
40
41
41
43
43
44
45
47
48
48
49
49
Chapter 4
4.1
4.2
4.2.1
4.3
4.3.1
4.4
4.4.1
4.5
4.5.1
4.5.2
Business Scenarios of SAP SRM-PPS . . . . . . .

Technical System Landscape . . . . . . . . . . .
Public Sourcing and Tendering . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . .
Contract Management and Administration . . . . . .
Overview . . . . . . . . . . . . . . . . . .
Operational Procurement . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . .
Procurement Services . . . . . . . . . . . . . .
Overview of Procurement Services (Automated Sourcing)
Overview of Procurement Services (Manual Sourcing) . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
53
54
55
55
55
55
56
56
57
57
57
Chapter 5
SAP Solution Manager . . . . . . . . . . . . . . . . . . . .
59
Chapter 6
References . . . . . . . . . . . . . . . . . . . . . . . .
61
4/72
PUBLIC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
07/11/2011
Chapter 7
Media List . . . . . . . . . . . . . . . . . . . . . . . . .
63
Chapter A
A.1
Reference . . . . . . . . . . . . . . . . . . . . . . . . .
The Main SAP Documentation Types . . . . . . . . . . . . . . .
65
65
07/11/2011
PUBLIC
5/72
6/72
PUBLIC
07/11/2011
Getting Started
1 Getting Started
The SAP Supplier Relationship Management (SAP SRM) Master Guide provides a central starting
point for the technical implementation of SAP SRM.
To facilitate the implementation process, all information within this document is organized by
scenario. You can choose from several generic business scenarios and find all the information relevant
for the technical implementation of a business scenario in that section.
Each business scenario supports a number of variants. In this Master Guide, only key variants are
described in detail.
The complete SAP SRM solution consists of the following top-level scenarios and business scenarios:
SRM Core
n Self-Service Procurement
l Self-Service Procurement (Classic)
l Self-Service Procurement (Extended Classic)
n Plan-Driven Procurement
l Plan-Driven Procurement with Plant Maintenance
l Plan-Driven Procurement with Supplier Integration
n Service Procurement
l Service Procurement Classic
l Service Procurement External Staffing
n Strategic Sourcing
l Strategic Sourcing with RFx
l Strategic Sourcing with Live Auction
n Operational Contract Management
n Catalog Content Management
n Analytics
l Spend Analysis
l Supplier Evaluation
SRM Procurement for Public Sector
Note
The SRM Procurement for Public Sector business scenarios require a special license agreement.
07/11/2011
PUBLIC
7/72
1
1.1
Getting Started
About this Document
Caution
You must install SAP SRM 7.0 SP01 before you activate the SRM PPS business functions. Activating
the business functions is irreversible; once they have been activated, you cannot deactivate them.
Be aware that accidental activation might disrupt the other business processes.
n
n
n
n
Public Sourcing and Tendering

Contract Management and Administration
Operational Procurement
Procurement Services
l Procurement Services with Automated Sourcing
l Procurement Services with Manual Sourcing
Note
For information about upgrading the SAP SRM business scenarios, see the SAP SRM Upgrade
Master Guide. This guide provides information about the overall upgrade sequences, references
to related documentation, SAP Notes, and additional upgrade information for each business
scenario of SAP SRM. The Upgrade Master Guide is available on SAP Service Marketplace at
http://service.sap.com/instguides
SAP Business Suite Applications SAP SRM SAP SRM 7.0
1.1 About this Document

Purpose
This 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-specific information in
this guide.
Note
You can use SAP SRM 7.0 with SAP NetWeaver 7.01. This implementation option is called Continuous
Innovation. As of May 6th 2009, you can also use SAP SRM 7.0 with SAP NetWeaver 7.0. This
implementation option is called Easy Adoption.
This guide, including the graphics, describes the Continuous Innovation implementation
option of SAP SRM 7.0 only. For information on the software components required for Easy
Adoption, see the Software Component Matrix for SAP SRM 7.0 on the SAP Service Marketplace at
http://service.sap.com/srm-inst
SAP SRM SAP SRM Server 7.0
Note
The central starting point for the technical upgrade of your SAP solution is the Upgrade Master
Guide, which you can find on SAP Service Marketplace at http://service.sap.com/instguides
SAP Business Suite Applications SAP SRM SAP SRM 7.0
8/72
PUBLIC
07/11/2011
1
1.1
Getting Started
About this Document
Use the Master Guide to get an overview of SAP SRM, its software units, and its scenarios from
a technical perspective. The Master Guide is a planning tool that helps you to design your system
landscape. It refers you to the required detailed documentation, mainly:
n
n
n
n
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 SAP Documentation Types.
The Master Guide consists of the following sections:
n Getting Started [page 7] contains information about using this document and related information
crucial to the installation.
n SAP SRM Overview [page 13] contains:
l A short introduction to the SAP Business Suite solution
l The software component matrix
l The minimal system landscape
l The overall installation sequence
n Business Scenarios of SAP SRM [page 23] contains information for each business scenario comprising:
l An overview of the business scenario
l Examples of how the different components interact, and what protocols and interfaces are
used, including technical system landscape examples
l Information about the overall installation sequence and subsequent steps
l References [page 61] to related installation guides
l Information about mutual dependencies that affect two or more components within the
business scenario
n Software Component Matrix [page 16] contains a short description of every software component in this
solution.
n Depending on the specific business scenario to be implemented, many different installation guides
and various configuration documentation may be required. The SAP SRM 7.0 implementation
content is clearly organized according to installation or configuration activity.
l Installation documentation is available in installation guides on SAP Service Marketplace.
l Configuration documentation is only available as SAP Solution Manager Content.
l References [page 61] lists the documentation referenced in this Master Guide.
Note
You can find the most current information about the technical implementation of SAP
SRM 7.0 and the latest installation and configuration guides on SAP Service Marketplace at
http://service.sap.com/instguides . We strongly recommend that you use the documents
available here. The guides are regularly updated.
Constraints
07/11/2011
PUBLIC
9/72
1
1.2
Getting Started
Planning Information
n 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 and do not necessarily run
the way they are described here in your customer-specific system landscape. Ensure to check your
requirements and systems to determine whether these scenarios can be used productively at your
site. Furthermore, we recommend that you test these scenarios thoroughly in your test systems to
ensure they are complete and free of errors before going live.
n This Master Guide primarily discusses the overall technical implementation of SAP SRM, rather
than its subordinate components. This means that additional software dependencies might
exist without being mentioned explicitly in this document. You can find more information on
component-specific software dependencies in the corresponding installation guides.
1.2 Planning Information

For more information about planning topics not covered in this guide, see the following content
on SAP Service Marketplace:
Content
Location on SAP Service Marketplace
The latest version of the installation and upgrade

guides for SAP SRM, links to related SAP Notes
Installation
and Upgrade Guides SAP Business Suite Applications SAP
SRM SAP SRM 7.0 Server
Released platforms
http://service.sap.com/platforms
Product
Availability Matrix
General security information for SAP systems
http://service.sap.com/security
SAP Solution Manager
http://service.sap.com/solutionmanager
SAP R/3 plug-in releases and availability
http://service.sap.com/R3-plug-in
Hardware sizing
http://service.sap.com/sizing
Information about SRM components and further

documents
http://service.sap.com/srm
Information about SAP SRM Support Package stacks

and download of Support Package stacks
http://service.sap.com/sp-stacks
Download of SAP software (SAP Software Distribution

Center)
http://service.sap.com/swdc
SAP Notes search
http://service.sap.com/notes
SAP Online Knowledge Products (OKPs)

role-specific Learning Maps
http://service.sap.com/rkt
10/72
PUBLIC
SRM 7.0
07/11/2011
1
1.3
Getting Started
Important SAP Notes
1.3 Important SAP Notes

You must read the SAP Installation Notes before you start the installation. These SAP Notes
contain the most recent information about the installation as well as corrections to the installation
documentation.
Make sure that you have the up-to-date version of each SAP Note, which you can find in the SAP
Service Marketplace at http://service.sap.com/notes .
SAP Note
Title
Description
1468349
Installation Options with SAP

NetWeaver 7.3 (for Java Hubs)
This note describes which

applications can run on a hub
system with SAP NetWeaver 7.3
and as of which start release or
SAP Enhancement Package this is
possible.
1224284
Enterprise Services Bundles

Required Technical Usages and
Business Functions
Lists business-related grouping of

Enterprise Services
1177779
SRM-MDM Catalog 3.0 Installation
1230438
Solution Manager Content for SAP

SRM 7.0
1223493
SAP SRM 7.0: Release &

Information Note
07/11/2011
PUBLIC
11/72
This page is left blank for documents

that are printed on both sides.
SAP SRM Overview
2 SAP SRM Overview
This section gives you an overview of the application components of SAP Supplier Relationship
Management (SAP SRM). It also provides system landscape and installation sequence information, as
well as a brief introduction to Service Oriented Architecture (SOA) and the One Client deployment
option.
Note
You can use SAP SRM 7.0 with SAP NetWeaver 7.01. This implementation option is called Continuous
Innovation. As of May 6th 2009, you can also use SAP SRM 7.0 with SAP NetWeaver 7.0. This
implementation option is called Easy Adoption.
This section, including the graphics, describes the Continuous Innovation implementation
option of SAP SRM 7.0 only. For information on the software components required for Easy
Adoption, see the Software Component Matrix for SAP SRM 7.0 on the SAP Service Marketplace at
http://service.sap.com/srm-inst
SAP SRM SAP SRM Server 7.0
2.1 Software Units of SAP SRM

This section provides additional information about the primary application and technology
components that comprise SAP SRM 7.0.
2.1.1 Application Components: SAP SRM Software Units

n SAP Supplier Relationship Management Server
The SAP Supplier Relationship Management Server (SAP SRM Server) includes both SAP SRM
and SAP Bidding Engine.
SAP SRM is based on SAP NetWeaver Application Server (AS) and is an application and database
instance installation released on several database and operating system platforms (for more
information, see SAP Service Marketplace at http://service.sap.com/platforms Platform
Availability Matrix .
n SAP Bidding Engine
Purchasers can use SAP Bidding Engine to create and process RFx, and bidders can use SAP Bidding
Engine to submit bids in response to these RFx. Both purchasers and bidders can use reverse
07/11/2011
PUBLIC
13/72
2
2.1
SAP SRM Overview

Software Units of SAP SRM
auction functions in a separate Live Auction application. Purchasers can define rules for bidding
and bidders can submit bids in real time.
Online Transaction Processing System
An online transaction processing system (OLTP), for example, SAP ERP system, is used in the SAP
SRM environment as a back-end system for materials management and financials.
Data is exchanged between the SAP SRM system and a connected OLTP system.
The SAP SRM system can be installed without an OLTP back-end in a standalone configuration.
If an SAP ERP system is used as an OLTP system, the plug-in supports data exchange in SAP SRM as
well as in other SAP software units.
SAP NetWeaver Business Intelligence
Business Intelligence (BI) provides infrastructure for:
l Data warehousing
l A range of analytical technologies and functions
l Web-based reporting and analysis
l Information Broadcasting for distributing BI content by e-mail or by the workset, either as
precalculated documents with stored data, or as links with live data
l Open analysis interfaces that make available various interfaces for connecting front-end tools of
third-party providers
l Web design API allowing for the implementation of highly individualized scenarios as well as
more demanding applications containing customer-defined interface elements
BI 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 BI platform units.
BI requires AS-ABAP as prerequisite in the same system. Usually, scenarios running on BI also
require BI-Java, AS-Java, and SAP Enterprise Portal. Other combinations can be used in one
system as well.
SAP NetWeaver Enterprise Portal
SAP NetWeaver Portal serves as a single point of entry to the applications, services, and information
of the organization.
Running an Enterprise Portal is an IT scenario providing role-based and secure access to all types
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.
Live Auction Cockpit Web Presentation Server
Live Auction Cockpit Web Presentation Server is a J2EE-based software unit comprising a virtual
auction floor for reverse auctions, real-time monitoring, real-time bidding, a tight integration to
all procurement processes, and a 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 SAP applications.
14/72
PUBLIC
07/11/2011
2
2.1
SAP SRM Overview

Software Units of SAP SRM
TREX can handle text from documents in numerous formats, including Microsoft Office and
Adobe formats (PDF), and more than 30 languages. TREX search options, such as exact, Boolean,
fuzzy, or linguistic search, and classification options such as query-based or example-based
classification, offer users great power and flexibility.
Note
To use the SAP NetWeaver Enterprise Search application (Embedded Search), the installation of
SAP NetWeaver Search and Classification (TREX) 7.1 is required.
n SRM-MDM Catalog
The SRM-MDM Catalog is based on SAP NetWeaver Master Data Management (MDM) technology.
It combines SAP MDM Server 7.1 with a Java-based and SRM-specific search environment.
2.1.2 Technology Components

Technology components are software and middleware components for implementing and
supporting SAP Business Suite solutions:
n SAP NetWeaver Process Integration (PI)
Caution
Separate licensing is required for SAP NetWeaver Process Integration if SAP SRM is used to
connect with non-SAP systems, or with external trading partners.
SAP NetWeaver Process Integration (PI) comprises core components for modeling, designing,
automating, and integrating the processes of one or more application systems. SAP PI also
contains core components for Business Process Management for application-embedded and
application-unbounded processes.
n SAP GUI
The latest release of the SAP GUI software (such as SAP GUI 6.20) can be used with all the previous
SAP component releases. Consequently, older SAP systems can also benefit from the features that
are only available in the newer SAP GUI releases, such as support for Windows XP.
Note
Use the latest available front-end software.

n SAP R/3 Plug-In
The SAP R/3 Plug-In is an interface for exchanging data between one or several SAP R/3 systems
and other SAP components. The SAP R/3 Plug-In supplies the SAP components with transaction
data and master data in real time. With it SAP application components like SAP CRM can be
07/11/2011
PUBLIC
15/72
2
2.2
SAP SRM Overview

Software Component Matrix
linked with certain industry-specific components. All SAP-industry-specific components based

on SAP R/3 4.7 and higher SAP R/3 releases require 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 (for example, SAP BI, SAP CRM)
and with industry-specific SAP components based on SAP R/3 4.7 or higher SAP R/3 releases. You
can order the most recent SAP R/3 Plug-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/3 release,
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 at
http://service.sap.com/r3-plug-in .
n SAP NetWeaver Application Server
Application Server (AS) is the application platform of SAP NetWeaver and, consequently, of the
SAP Business Suite. It provides the technological foundation for all other SAP software units.
Since AS comprises the ABAP Engine, Java Engine or both, it can provide a runtime environment
for both ABAP and Java applications.
2.1.3 Non-SAP Components

SAP SRM does not include any non-SAP components.
2.2 Software Component Matrix

For an overview of SAP SRM business scenarios and their associated software units, in both Continuous
Innovation and Easy Adoption, see the Software Component Matrix for SAP SRM 7.0 on the SAP
Service Marketplace at http://service.sap.com/srm-inst SAP SRM SAP SRM Server 7.0
Note
The Continuous Innovation functions for SAP SRM 7.0, with some exceptions, require the use of SAP
NetWeaver 7.01. The Easy Adoption functions require SAP NetWeaver 7.0.
For the latest component version and patch level requirements, see SAP Service Marketplace at
http://service.sap.com/sp-stacks
SAP SRM 7.0 and the Release Information Note, which is
available for each Support Package stack (SAP Note number is listed on the page).
16/72
PUBLIC
07/11/2011
2
2.3
SAP SRM Overview

System Landscape
Note
This Master Guide provides just one way to implement each business scenario. For other ways to
implement business scenarios, see the Scenario & Process Component list in SAP Service Marketplace
at http://service.sap.com/scl . The Scenario & Process Component list helps you to find
implementation alternatives for SAP solutions, business scenarios, and processes. It shows you which
application components are needed to implement a business scenario or process.
The exact locations of the required software components on the corresponding DVD(s) and
CD(s) that are shipped with the SAP SRM 7.0 package can be found at SAP Service Marketplace at
SAP Business Suite Applications SAP SRM SAP SRM 7.0 .
Note
For each component listed in the Software Component Matrix, there are software requirements that
are not explicitly mentioned in this documentation. Component-specific software requirements
are documented for a component in its installation guide. All related implementation guides are
listed in 6 References [page 61].
You require SAP NetWeaver 7.0 TREX in the following cases:
n When you use the contract management application to search for information such as supplier
texts, internal notes, and attachments.
n When you want to use the metadata search functionality or use BI accelerator within Analytics.
2.3 System Landscape

Minimal System Landscape
Caution
We strongly recommend that you use a minimal system landscape for test and demo purposes only.
For performance, scalability, high availability, and security reasons, do not use a minimal system
landscape as your production landscape.
Enhanced requirements on performance, scalability, high availability, and security reasons cannot be
met by a minimal landscape.
The installation of this minimal system landscape is possible only if you:
n Choose an operating system and a database that supports all components. For more
information about released platforms for SAP SRM. see SAP Service Marketplace at
Product Availability Matrix .
n Provide a sufficiently sized server. For information on sizing, see SAP Service Marketplace at
http://service.sap.com/sizing .
07/11/2011
PUBLIC
17/72
2
2.4
SAP SRM Overview

Overall Installation Sequence
Caution
SAP Process Integration requires a dedicated SAP Web Application Server. This means that running
applications in other clients of the same Web AS is not supported.
Installation Options with SAP NetWeaver 7.3 (for Java Hubs)
For SAP Business Suite applications as of SAP Business Suite 7 that are based on an Application Server
Java and on hub systems, you can install these applications on SAP NetWeaver 7.3. You can also
change from your current release to SAP NetWeaver 7.3. Changing means upgrading or updating.
The following approaches for system landscapes for SAP NetWeaver 7.3 are possible:
n Upgrading to SAP NetWeaver 7.3 works for hub systems.
n Embedded deployment continues to work only for SAP NetWeaver 7.0x releases and their
enhancement packages (this means, for example, for SAP NetWeaver 7.00, SAP NetWeaver 7.01,
and SAP NetWeaver 7.02).
For more information about the technical background, see SAP Note 1468349. There you can find a
list of all the Java hubs that you can install on SAP NetWeaver 7.3.
2.4 Overall Installation Sequence

Purpose
The following figure describes the installation sequence for SAP SRM comprising components of all
SAP SRM business scenarios.
Figure 1:
18/72
PUBLIC
07/11/2011
2
2.5
SAP SRM Overview

Automated Post-Installation Configuration Tools
Note
Some of these software components may be optional for some/all business scenarios. For more
information about the installation sequence of each business scenario, see <Business Scenario>
Implementation Sequence.
If you want to implement more than one SAP SRM business scenario at a time note that software
components on the same level can be installed at the same time on the appropriate machine (for
example, different project groups could install SAP ERP and SAP PI simultaneously).
2.5 Automated Post-Installation Configuration Tools
2.5.1 Automated Configuration of the Portal Systems

You can automate the mandatory configuration steps necessary to configure the integration
of the SAP Supplier Relationship Management (SAP SRM) and SAP NetWeaver Portal systems.
For more information about automating this integration, see SAP Service Marketplace at
SAP Business Suite Applications SAP SRM SAP SRM Server
7.0 Guide for Automated Configuration: SAP SRM Portal .
2.5.2 Automated Configuration of SAP SRM and SAP ERP

System Integration
You can automate the mandatory configuration steps necessary to configure the integration
of the SAP Supplier Relationship Management (SAP SRM) and SAP ERP systems. For
more information about automating this integration, see SAP Service Marketplace at
7.0 Guide for Automated Configuration: Connecting SAP SRM to SAP ERP .
2.5.3 Automated Configuration of SAP SRM and One Client

System Integration
You can automate the mandatory configuration steps necessary to configure the integration of
the SAP Supplier Relationship Management (SAP SRM) and SAP SRM on One Client in SAP
ERP. For more information about automating this integration, see SAP Service Marketplace at
7.0 Guide for Automated Configuration: Connecting SAP SRM to One Client .
07/11/2011
PUBLIC
19/72
2
2.6
SAP SRM Overview

Service-Oriented Architecture (SOA)
2.5.4 Automated Configuration of SAP SRM and SAP

NetWeaver BW System Integration
You can automate the mandatory configuration steps necessary to configure the integration of the
SAP Supplier Relationship Management (SAP SRM) and SAP NetWeaver Business Warehouse (SAP
NetWeaver BW) systems. For more information about automating this integration, see SAP Service
Marketplace at http://service.sap.com/instguides SAP Business Suite Applications SAP SRM
SAP SRM Server 7.0 Guide for Automated Configuration: Connecting SAP SRM to SAP BW .
2.6 Service-Oriented Architecture (SOA)

In general, service-oriented architecture (SOA) is an architectural pattern that requires all exposed
functionality to be published as services in a platform-independent manner. These services can be
consumed by other applications. To successfully utilize SOA on an enterprise level, you need to
consider several additional aspects. All interfaces need to be clearly defined and stable and make use
of global (at least landscape-wide) data types. Both points ensure loose coupling and reliability for
service consumers and avoid superfluous transformations caused by technically different, while
semantically identical information. To establish additional reliability, all services must follow clearly
defined communication and behavioral patterns Clients need to know whether services are
synchronous or asynchronous, whether they return an answer, how they handle exceptions and
which security policy they use.
Additionally, the underlying business model (interaction between business objects) needs to be
transparent to establish common ground in terms of relationships between business objects that play
a role when calling services.
For more information about services, see ES Workplace at www.sdn.sap.com Enterprise SOA
Explore Enterprise Services ES Workplace
Forward error handling (FEH) for asynchronous inbound interfaces
Forward error handling (FEH) is required only for asynchronous inbound interfaces. Asynchronous
services do not confirm the arrival of a document into the inbound interface, so that the status of
a transmitted document is unknown for the sender system (that is, the sender system does not
know whether the document was created correctly). FEH avoids such confusion, as any erroneous
documents are collected in the Post-Processing Office (PPO) of the receiver system. FEH supports
the correction and reprocessing of the documents from the PPO.
For information about Enterprise Services Bundles, see SAP Note 1224284.
20/72
PUBLIC
07/11/2011
2
2.7
SAP SRM Overview

SAP SRM on One Client in SAP ERP
2.7 SAP SRM on One Client in SAP ERP

More Information
Note
The SAP SRM 7.0 One Client deployment mode is only possible with SAP ERP 6.0 Enhancement
Pack 04.
For more information about the installation of SAP SRM, see SAP Note 1172901.
For more information on the basic settings for SAP SRM on One Client in SAP ERP, see SAP Solution
Manager at SAP ERP Configuration Structures SAP enhancement package 4 for SAP ERP 6.0 Basic
settings for enhancement pack 4
2.8 Flexible Deployment Variants

The following two flexible deployment variants are available in SAP Supplier Relationship
Management 7.0 (SAP SRM 7.0):
n Portal-independent navigation frame
You can use this function to work with SAP SRM if you are not using the SAP NetWeaver Portal
and therefore cannot use its navigation frame. When using the portal-independent navigation
frame, an inbox for processing work items, alerts, and notifications is also available.
n BW-independent analytics
You can use several reports that allow you to analyze data directly in your SAP SRM system.
To use these reports, you do not have to install an SAP NetWeaver Business Warehouse (SAP
NetWeaver BW) system.
Configuration
See SAP Solution Manager content for flexible deployment variants.
2.8.1 Deployment Options

You can use the following deployment options to run the Portal-independent navigation frame, the
inbox, and BW-independent analytics in SAP Supplier Relationship Management 7.0 (SAP SRM 7.0):
n SAP SRM
n SAP SRM on One Client in SAP ERP
Note
This deployment option is only possible with SAP enhancement package 4 for SAP ERP 6.0.
07/11/2011
PUBLIC
21/72
2
2.8
SAP SRM Overview

Flexible Deployment Variants
For more information about what scenarios and functions are supported for SAP SRM on One Client
in SAP ERP, see section SAP SRM on One Client in SAP ERP [page 21] in this document.
The following solutions are not supported in combination with flexible deployment variants:
n Procurement for Public Sector (PPS)
n Supplier self-services (SUS)
n Registration of suppliers (ROS)
Furthermore, harmonized roles across SAP ERP and SAP SRM purchasing capabilities are not
supported in conjunction with the flexible deployment variants.
2.8.2 Technical Scenarios

Flexible deployment variants in SAP Supplier Relationship Management 7.0 (SAP SRM 7.0) are
compatible with the following technical scenarios:
n Classic
n Extended Classic
n Standalone
If you use SAP SRM on One Client with SAP ERP, only the Classic scenario is supported.
2.8.3 Business Scenarios

In this section, you can find information about restrictions in the compatibility of the flexible
deployment variants with the SAP Supplier Relationship Management (SAP SRM) business scenarios.
Portal-Independent Navigation Frame
You can use the portal-independent navigation frame with all of the business scenarios in SAP SRM.
Harmonized procurement in SAP SRM and SAP ERP is not supported when using the
portal-independent navigation frame.
BW-Independent Analytics
You can use BW-independent analytics with all of the business scenarios in SAP SRM except for the
Spend Analysis and Supplier Evaluation business scenarios.
22/72
PUBLIC
07/11/2011
Business Scenarios of SAP SRM
3 Business Scenarios of SAP SRM
Caution
This Master Guide provides just one way of implementing each business scenario. See the Scenario
& Process Component List in SAP Service Marketplace ( http://service.sap.com/scl ) for
alternatives. The Scenario & Process Component List helps you to find realization alternatives for
SAP solutions, business scenarios, and processes. It shows you which application components are
needed to realize a business scenario or process.
Note
The graphics in this section refer to Continuous Innovation in SAP SRM 7.0 only.
3.1 Self-Service Procurement

For this business scenario, the following topics are covered:
n
n
n
n
Overview Self-Service Procurement (Classic)

Overview Self-Service Procurement (Extended Classic)
Technical System Landscape
Implementation sequence
3.1.1 Overview of Self-Service Procurement (Classic)

Your employees can use this business scenario to create and manage their own requisitions. This
relieves your purchasing department of a huge administrative burden while making the procurement
process faster and more responsive. In this scenario, only the shopping cart is created in the SAP
Supplier Relationship Management (SAP SRM) system. All other procurement documents, such as
purchase orders, goods receipts, and invoices, are located in the back-end system.
The Self-Service Procurement (Classic) business scenario comprises these process steps:
1.
2.
3.
4.
5.
Processing Shopping Carts

Processing Purchase Requisitions in SAP ERP
Processing Purchase Orders in SAP ERP
Inbound Processing and Receipt Confirmation with Warehouse Management
Verifying Logistics Invoices Online/In Background
07/11/2011
PUBLIC
23/72
3
3.1

Self-Service Procurement
6. Analyzing Self-Service Procurement
3.1.2 Overview of Self-Service Procurement (Extended

Classic)
Your employees can use this business scenario to create and manage their own requisitions. This
relieves your purchasing department of a huge administrative burden, while making the procurement
process faster and more responsive. In this scenario, shopping carts and purchase orders are created
in the SAP Supplier Relationship Management (SAP SRM) system, and are then replicated to the
back-end system. The purchase order in SAP SRM is the leading purchase order; it cannot be changed
in the back-end system. Goods receipts and invoices can be pre-entered in SAP SRM or entered
directly in the back-end system. Sourcing, pricing, and tax determination take place in SAP SRM.
The Self-Service Procurement (Extended Classic) business scenario comprises these process steps:
1.
2.
3.
4.
5.
6.
7.
8.

Searching for Sources of Supply Centrally
Processing Purchase Orders in SAP SRM
Inbound Processing and Receipt Confirmation without Warehouse Management
Confirming Receipt of Inbound Goods in SAP SRM
Processing Invoices in SAP SRM
Verifying Logistics Invoices (Online/In Background)
Analyzing Self-Service Procurement
3.1.3 Technical System Landscape

Note
For information about the technical system landscape and about how to plan the business scenario
to meet your needs, see:
n SAP Service Marketplace at
Platform Availability Matrix
http://service.sap.com/slo
The following figure shows the underlying architecture of Self-Service Procurement.
24/72
PUBLIC
07/11/2011
3
3.1

Figure 2:
For a more readable version of this graphic, go to the SAP Service Marketplace at
SAP Business Suite SAP SRM SAP SRM 7.0
n IPC 7.0 is part of the component AP 7.0
n No R/3 Plug-ins are needed for SAP R/3 Enterprise 47x200 and higher
3.1.4 Implementation Sequence

This section lists the sequence of steps (installation, technical configuration, application
configuration) required to implement the business scenario. Rows containing optional components
are shaded. The scenario can function without these optional components; but they do provide
additional functions.
Installation
Note
n See the section Overall Installation Sequence [page 18], especially if you want to implement more
than one SAP SRM business scenario at a time.
n For documentation referenced in the following table, see the section References [page 61].
07/11/2011
PUBLIC
25/72
3
3.1

No.
Action (Corresponding Documentation
Remarks/Subsequent Steps
Install SAP Process Integration. [Master

Guide SAP NetWeaver 7.01]
The use of SAP Process Integration is optional

but it is required for outbound XML-based
messaging or for connecting non-SAP
planning or execution systems.
Caution
SAP Process Integration requires a dedicated

SAP Web Application Server. This means
that the running of applications in other
clients of the same SAP Web AS is not
supported.
If you installed SAP Process Integration,
/
import the integration objects for SAP SRM
into the SAP Process Integration. Import the
PI content for the following components:
n
SAP SRM Server 7.0
n
SAP SRM-MDM Catalog 3.0
n
SAP BI Content 7.0.4
Download and install the latest SLD
Content from SAP Service Marketplace
at http://service.sap.com/swdc
Download Support Packages and Patches Entry
by Application Group Additional Components
SAP Master Data for SLD .
Install/Integrate SAP ERP (SAP R/3 4.7 or

higher recommended)
SAP ERP is not part of this installation and

are not contained in the installation package.
A separate SAP ERP installation package is
required.
Install SAP R/3 Plug-In (2004.1 or higher if

one is available):
n 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).
n For more information about SAP R/3
Plug-Ins, see SAP Service Marketplace at
Not required for customers with an SAP R/3

Enterprise 47x200 back-end system. From
SAP R/3 Enterprise 47x200 onwards, the
former plug-in functions are delivered with
the SAP_APPL component. Not required if
exclusively local PO handling is performed,
or no SAP back-end system is used.
http://service.sap.com/r3-plug-in
26/72
Install SAP SRM Server 7.0 comprising SAP

Bidding Engine
[Installation Guide SAP SRM Server 7.0]
PUBLIC
.
/
07/11/2011
3
3.1

Install SRM-MDM Catalog 3.0. For more

/
information, see SAP Note 1177779(regarding
SRM-MDM Catalog) [SAP SRM-MDM
Catalog 3.0 Installation Guide]
Install SAP NetWeaver 7.0 Search and

Classification (TREX) [SAP NetWeaver 7.0
Installation Guide: Search and Classification
(TREX)]
n Perform the installation steps to set up

an RFC connection
n Automatic language recognition is not
required. You can adopt the default
settings for document languages during
the installation of SAP NetWeaver 7.0
TREX
n No Python extensions are required
Install SAP SRM Server for SAP SUS.

[Installation Guide SAP SRM Server on
<Platform>:<Database>]
You can install a separate SAP SRM Server for

SUS or use the SAP SRM Server you installed
in step 4 for that purpose.
Install SAP BI 7.01 plus SAP BI Content 7.04:

1. Install SAP Web AS ABAP 7.01, which
includes SAP BI 7.01 and PI_BASIS 7.01.
2. Configure the database of your SAP Web
AS for SAP BI as described in SAP Note
567745.
3. Install SAP BI Business Content Add-On
BI_CONT 7.0.4 on the SAP Web AS ABAP
system as described in SAP Note 1172899.
For a minimal system landscape, you can
install SAP BI on your SAP SRM Server.
Install the SAP BI Business Content Add-On
on the SAP SRM Server as described in SAP
Note 1172899.
For more information, see the Master Guide
SAP NetWeaver 7.0.
The use of SAP BI is optional. See the

description of this component in the Software
Component Matrix [page 16] to decide whether it
is required for your business scenario. After
the BI ABAP upgrade, you should install the
Java parts of BI (BI-Java) to take advantage of
all new functionality. For more information,
see Installation Guide SAP NetWeaver 7.01.
Install SAP NetWeaver 7.01 Enterprise

Portal. [Master Guide SAP NetWeaver 7.01]
The use of SAP NetWeaver Enterprise

Portal is mandatory. It is required for the
integration of SAP SRM into a workset.
10
Import the following Business Packages into

the Enterprise Portal:
n Business Package for SAP SRM 7.0
n Business Package for Supplier
Collaboration 4.0
Download the Business Packages from the

SAP Developer Network www.sdn.sap.com
Portal Content Portfolio
Configuration
See SAP Solution Manager content for Self-Service Procurement.
07/11/2011
PUBLIC
27/72
3
3.2

Plan-Driven Procurement
3.2 Plan-Driven Procurement

n
n
n
n
Overview of Plan-Driven Procurement with Plant Maintenance

Overview of Plan-Driven Procurement with Supplier Integration
3.2.1 Overview of Plan-Driven Procurement with Plant

Maintenance
You can use this business scenario to process requirements that have been generated in systems other
than SAP SRM. In a highly integrated procurement process, demand for products can come from
several different planning systems that reside outside of SAP SRM, such as material requirements
planning (MRP) systems for production planning, automated production systems (APS) for
advanced, constraint-based planning, project systems for project planning, or plant maintenance
systems for maintenance and repair planning. Plan-Driven procurement is especially important for
the procurement of direct materials. Demand from production is transferred to SAP SRM using an
open XML interface. Within SAP SRM, a contract can be automatically assigned to the demand and
a purchase order sent out.
The Plan-Driven Procurement with Plant Maintenance business scenario comprises these process
steps:
1. Processing Purchase Requisitions in SAP ERP
2. Searching for Sources of Supply
3. Processing Purchase Orders in SAP SRM
4. Receipt Confirmation without Warehouse Management
5. Receipt Confirmation with Warehouse Management
6. Processing Leasing Invoices in SAP SRM
7. Verifying Logistics Invoices in Background
8. Verifying Logistics Invoices Online
9. Processing Evaluated Receipt Settlements (ERS) in SAP ERP
10. Analyzing Plan-Driven Procurement
3.2.2 Overview of Plan-Driven Procurement with Supplier

Integration
You can use this business scenario to procure direct materials with SAP Materials Management (SAP
MM) and, at the same time, to integrate your suppliers into this process. If necessary, you can connect
28/72
PUBLIC
07/11/2011
3
3.2

multiple supplier systems to your procurement system. This allows you, as a buyer, to collaborate
with your suppliers, using the web-based tool SAP SRM Supplier Self-Service, starting with the
purchase order via shipping notification to the invoice.
The Plan-Driven Procurement with Supplier Integration business scenario comprises these process
steps:
1. Processing Purchase Requisitions in SAP ERP
2. Processing Purchase Orders in SAP ERP
3. Processing Delivery Schedules
4. Processing Sales Orders in SRM-SUS
5. Processing Shipping Notifications
6. Receipt Confirmation without Warehouse Management
7. Receipt Confirmation with Warehouse Management
8. Processing Invoices in SAP SRM
12. Analyzing Plan-Driven Procurement
13. Performing Order Collaboration Using Supplier Network

Note
The following figure shows the underlying architecture of Plan-Driven Procurement.
07/11/2011
PUBLIC
29/72
3
3.2

Figure 3:

Installation
Note
30/72
PUBLIC
07/11/2011
3
3.2

No.

Caution

supported.

/
n
SAP SRM Server 7.0
n
SAP BI Content 7.0.4 (optional)
Content from SAP Service Marketplace at
service.sap.com/swdc
Download
Support Packages and Patches Entry by Application
Group Additional Components SAP Master
Data for SLD .

higher recommended)

required.

one is available):
R/3 Plug-in 2004.1).
service.sap.com/r3-plug-in .

the SAP_APPL component.
Install SAP SRM 7.0

[Installation Guide SAP SRM 7.0]
/
(TREX)]
Install SAP SRM Server for SUS.

<Platform>:<Database>
07/11/2011
PUBLIC

31/72
3
3.3

Service Procurement

567745.
Note 1172899.
SAP NetWeaver 7.0.

is required for your business scenario. After
the BI ABAP upgrade, you should install the
Java parts of BI (BI-Java) to take advantage of
all new functionality. For more information,
see Installation Guide SAP NetWeaver 7.01.


Import the following Business Package into


Configuration
See SAP Solution Manager content for Plan-Driven Procurement.
3.3 Service Procurement

n
n
n
n
Overview of Service Procurement (Classic)

Overview of Service Procurement External Staffing
3.3.1 Overview of Service Procurement (Classic)

You can use this business scenario to cover the entire service procurement process using structured
service requirements for external procurement. A purchase requisition is created in SAP Materials
Management (SAP MM) and sent to Sourcing in SAP Supplier Relationship Management (SAP SRM),
where it is converted to an RFx. Response modifications are allowed.
The Service Procurement (Classic) business scenario comprises these process steps:
32/72
PUBLIC
07/11/2011
3
3.3

Service Procurement
1. Purchase Requisition with Service Directories

2. Searching for Sources of Supply Centrally
3. Processing RFx Events
4. Evaluating RFx Responses
5. Processing Follow-On Documents
6. Processing Purchase Orders in SAP ERP
7. Processing Sales Orders in SUS
8. Entering Services in SAP RM
9. Entering Services in SAP ERP
10. Processing Invoices
14. Analyzing Service Procurement
3.3.2 Overview of Service Procurement External Staffing

You can use this business scenario to cover the entire service procurement process for External
Staffing. The process starts when you send your request to the supplier. A purchase order is created,
times and expenses are entered in the system, and an invoice is created. You can interact with your
suppliers by connecting a supplier system like supplier self-services (SUS) to your procurement
system. Your service providers can then enter services performed and create invoices for these
services. All documents created by your suppliers have to be approved by an internal employee.
The Service Procurement External Staffing business scenario comprises these process steps:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Requesting External Staff

Processing Purchase Orders in SAP SRM
Processing Sales Orders in SUS
Entering Services in SAP SRM
Processing Invoices in SAP SRM
Processing Evaluated Receipt Settlements (ERS) in SAP SRM
Carrying Out Third-Party Rebilling
Analyzing Service Procurement
07/11/2011
PUBLIC
33/72
3
3.3

Service Procurement

Note
The following figure shows the underlying architecture of Service Procurement.

Figure 4:

34/72
PUBLIC
07/11/2011
3
3.3

Service Procurement
Installation
Note
No.

Caution

supported.

/
n
SAP SRM Server 7.0
n
n
Download
Support Packages and Patches Entry by Application
Group Additional Components SAP Master
Data for SLD .

higher recommended)

required.

one is available):
R/3 Plug-in 2004.1).

the SAP_APPL component. Not required if
exclusively local PO handling is performed,
or no back-end system is used.
07/11/2011
PUBLIC
35/72
3
3.3

Service Procurement
Install SAP SRM Server 7.0 comprising

SAP Bidding Engine and SAP Supplier
Self-Services
Install SAP SRM-MDM Catalog 3.0. For more /

information, see SAP Note 1057316 . [SAP
SRM-MDM Catalog 3.0 Installation Guide]

(TREX)]
n Perform the installation steps to set up

an RFC connection
settings for document languages during
the installation of SAP NetWeaver 7.0
TREX



567745.
Note 1172899.
SAP NetWeaver 7.0.

is required for your business scenario.
After the BI ABAP upgrade, you should
install the Java parts of BI (BI-Java) to take
advantage of all new functionality.
For more information, see the SAP
NetWeaver 7.01 Installation Guide.


10
Import the following Business Packages into

n Business Package for Supplier
Collaboration 4.0

Configuration
See SAP Solution Manager content for Service Procurement.
36/72
PUBLIC
07/11/2011
3
3.4

Catalog Content Management
3.4 Catalog Content Management

n Overview
n Technical System Landscape
n Implementation sequence
3.4.1 Overview
Description
You can use this business scenario to import and manage product content, make this content available
in an MDM data repository, and access it via the Web browser in your SAP Supplier Relationship
Management (SAP SRM) procurement processes.
The business processes run as follows:
1. Managing Content in SRM-MDM Catalog
2. Searching in Catalog Data

Note
to meet your needs, see: http://service.sap.com/platforms Platform Availability Matrix
The following figure shows the underlying architecture of the SRM-MDM Catalog including existing
connections.
07/11/2011
PUBLIC
37/72
3
3.4

Catalog Content Management
Figure 5:

Installation
Note
n For latest Support Package and patch level requirements, see the SAP SRM-MDM Catalog
3.0 Installation Guide
38/72
PUBLIC
07/11/2011
3
3.5

Analytics
No.

Caution

supported.
After you install SAP Process Integration,

/
n
SAP SRM Server 7.0
2

Bidding Engine
Install SAP SRM-MDM Catalog 3.0. For

more information, see SAP Note 1177779.

Portal. [Master Guide SAP NetWeaver 7.01,
part of the installation package]
The use of SAP NetWeaver Enterprise Portal

is optional. It is required for the integration
of SAP SRM into a workset.
Configuration
See SAP Solution Manager Content for Catalog Content Management.
3.5 Analytics
n
n
n
n
Overview of Spend Analysis

Overview of Supplier Evaluation
3.5.1 Overview of Spend Analysis

You can use this business scenario to analyze the expenditure of your company, using data from a wide
range of heterogeneous systems as well as from all relevant business units and areas. SAP Supplier
Relationship Management (SAP SRM) uses the business intelligence features of SAP NetWeaver to
access connected systems, and extract the information needed to gain insight into spending practices
07/11/2011
PUBLIC
39/72
3
3.5

Analytics
across the entire corporate group. The reports cover spending for direct and indirect material, as well
as for services. You can also configure your system to provide the following:
1. Capture of spend for procurement documents without any purchase order (PO) reference or other
detailed information about the procurement
2. Harmonization of master data for reporting purposes, allowing for identification of duplicate
suppliers and assignment of product to standard classification schemas such as the United Nations
Standard Products and Services Code (UNSPSC) and eCl@ss. The harmonization can be done
either by using SAP NetWeaver Business Intelligence (SAP NetWeaver BI) Local Master Data
Alignment (for limited data volumes), or by integration of SAP NetWeaver BI with the SAP Master
Data Management (SAP MDM) application.
With these features, SAP SRM provides you with a clear view of procurement costs and supply-base
data by highlighting consolidated spend volume, supplier redundancies, and demand aggregation
opportunities.
The Spend Analysis business scenario comprises these process steps:
1. Consolidating Master Data Using BI Master Data Alignment
2. Consolidating Master Data Using SAP MDM
3. Analyzing Spend
3.5.2 Overview of Supplier Evaluation

You can use this business scenario to evaluate your suppliers on the basis of Web-based surveys. To
meet your specific requirements, you can configure individual surveys and questionnaires, select the
criteria that you want to evaluate, and stipulate when the evaluation is to take place. After the data
has been transferred to SAP NetWeaver Business Intelligence (SAP NetWeaver BI), several reports are
available to help you to analyze the results, select suitable suppliers and negotiate best conditions.
With the Supplier Survey Cockpit, you can create and distribute surveys. You can monitor incoming
responses and send reminders to those who did not reply.
SAP Supplier Evaluation is also integrated into the following SAP Supplier Relationship Management
(SAP SRM) applications:
n Confirmation
n Invoice
n Supplier list
SAP Supplier Evaluation is used with the confirmation and invoice applications to evaluate day-to-day
activities on the basis of operational documents. You can also use this scenario with the supplier list to
improve the strategic and long-term supplier relationships.
The following business process runs in SAP NetWeaver BI:
Evaluating and Monitoring of Supplier Performance
40/72
PUBLIC
07/11/2011
3
3.5

Analytics

Note
The following figure shows the underlying architecture of Analytics.

Figure 6:

07/11/2011
PUBLIC
41/72
3
3.5

Analytics
Installation
Note
n See the section Overall Installation Sequence [page 18], especially if you want to implement more than
one SRM business scenario at a time.
No.

higher recommended)

required.

one is available):
n
For the installation, see SAP Notes 704564
R/3 Plug-in 2004.1).
n
For more information about SAP R/3

former plug-in functionalities are delivered
with the SAP_APPL component. Otherwise
the installation of the SAP R/3 Plug-In is
required if you installed an SAP back-end
system in the previous step.

Bidding Engine and Supplier Self-Services

567745.
Note 1172899.
SAP NetWeaver 7.0.
After the BI ABAP upgrade, you should

install the Java parts of BI (BI-Java) to take
advantage of all new functionality. For more
information, see Installation Guide SAP
NetWeaver 7.01.
42/72
PUBLIC
07/11/2011
3
3.6

Operational Contract Management


Import the following Business Package into

Business Package for SAP SRM 7.0

Configuration
See SAP Solution Manager content for Analytics.
3.6 Operational Contract Management

n Overview
n Technical System Landscape
n Implementation sequence
3.6.1 Overview
You can use this business scenario to access SAP Supplier Relationship Management (SAP SRM)
contract features, such as contract hierarchies, discount across contract hierarchies, and grouping
logic, when determining source of supply in SAP ERP. You can create a central contract in SAP SRM,
and it can then be used as source of supply in both SAP SRM and SAP ERP. Relevant data is sent to SAP
ERP for a source of supply determination, and a specific type of contract or scheduling agreement can
be created there. While determining a source of supply, you can access central contracts directly. The
price is determined in SAP SRM before the SAP ERP purchase order is sent to the supplier. You can
create and change central contracts and renegotiate existing contracts directly with a supplier, or
through the creation of an RFx. You can automatically assign a contract as a source of supply, or it
can be listed as one of numerous potential source of supply contracts. A strategic purchaser can create
a contract whenever they anticipate a long-term relationship with a supplier. Contract management
enables purchasers from various parts of the company at different locations to take advantage of the
terms of globally-negotiated contracts for specific product categories. You can provide users with
specific levels of authorization to contracts, and you can categorize documents as confidential.
You can distribute central contracts to release-authorized purchasing organizations, and these
organizations can then use them as source of supply in the appropriate SAP ERP system. Hierarchies
can be used to organize, structure, display, and search for contracts. If you use SAP NetWeaver Business
Intelligence (SAP NetWeaver BI), you can view various consolidated reports of contract management.
For example, you can view aggregated value released against all contracts in a contract hierarchy.
07/11/2011
PUBLIC
43/72
3
3.6

The Operational Contract Management business scenario comprises these process steps:
1.
2.
3.
4.
5.
6.
7.
Define Usage of Central Contracts

Developing Contracts
Processing Contracts and Sourcing Rules in SAP ERP
Negotiating Contracts
Process Delivery Schedules
Monitoring Contracts

Note
The following figure shows the underlying architecture of Operational Contract Management.
Figure 7:
44/72
PUBLIC
07/11/2011
3
3.6

n IPC 7.0 is part of the SAP WebAS

n On the Portal Layer, you must deploy the Portal Core plus the following Portal Java Components:
l Knowledge Management (KM)
l Collaboration room
l Universal Worklist (UWL)
l ADS can be deployed on the Portal
l LAC WPS can be deployed on the Portal
The
Business Packages shown above are:
n
l BPSRM00_0.sca (BP for mSAP SRM 2007)
n The XI Content Packages shown above are:
l SRMSERV7001_0.ZIP (XI Content for SAP SRM Server 7.0)
l SRMSERVIC7001_1.ZIP (XI Content for SAP SRM Server 7.0, SP01 Patch 1)
l SRMMDMCAT3001_0.ZIP (XI Content for SRM-MDM Catalog)
n TREX is a separately installed instance. For scalability, multiple TREX instances can be installed
on multiple servers.
n No R/3 Plug-ins needed for SAP ERP 2005 (ECC 6.0) and higher.
n The connection between the SRM Server and the back-end system is RFC-based. IDocs are only
used in specific cases, for example when Billing Documents are exchanged.

Installation
Note
07/11/2011
PUBLIC
45/72
3
3.6

No.
Install SAP Process Integration. [Master Guide

SAP NetWeaver 7.01]
The use of SAP Process Integration is optional,

but it is required for outbound XML-based
messaging or for connecting non-SAP planning
or execution systems.
Caution
SAP Process Integration requires a dedicated SAP

Web Application Server. This means that the
running of applications in other clients of the
same SAP Web AS is not supported.
If you installed SAP Process Integration, import /
the integration objects for SAP SRM into the SAP
Process Integration. Import the PI content for
the following components:
n
SAP SRM Server 7.0
n
n
Download Support
Packages and Patches Entry by Application Group
Additional Components SAP Master Data for SLD .
Install/Integrate SAP ERP (SAP R/3 4.7 or higher

recommended)
SAP ERP is not part of this installation and are

not contained in the installation package. A
separate SAP ERP installation package is required.
Install SAP R/3 Plug-In (2004.1 or higher if one is

available):
n 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).

Enterprise 47x200 back-end system. From SAP R/3
Enterprise 47x200 onwards, the former plug-in
functions are delivered with the SAP_APPL
component. Not required if exclusively local PO
handling is performed or no back-end system is
used.
Install SAP SRM Server 7.0

Install SRM-MDM Catalog 3.0. For more

information, see SAP Note 1177779. [SAP
46/72
PUBLIC
07/11/2011
3
3.7

Strategic Sourcing

(TREX)]
n Perform the installation steps to set up an

RFC connection
settings for document languages during the
installation of SAP NetWeaver 7.0 TREX


SUS or use the SAP SRM Server you installed in
step 4 for that purpose.

1. Install SAP Web AS ABAP 7.01, which includes
SAP BI 7.01 and PI_BASIS 7.01.
2. Configure the database of your SAP Web AS
for SAP BI as described in SAP Note 567745.
For a minimal system landscape, you can install
SAP BI on your SAP SRM Server. Install the SAP
BI Business Content Add-On on the SAP SRM
Server as described in SAP Note 1172899.
SAP NetWeaver 7.0.
The use of SAP BI is optional. See the description

of this component in the Software Component Matrix
[page 16] to decide whether it is required for your
business scenario. After the BI ABAP upgrade,
you should install the Java parts of BI (BI-Java)
to take advantage of all new functionality. For
more information, see Installation Guide SAP
NetWeaver 7.01.
Install SAP NetWeaver 7.01 Enterprise Portal.

[Master Guide SAP NetWeaver 7.01]
The use of SAP NetWeaver Enterprise Portal is

mandatory. It is required for the integration of
SAP SRM into a workset.
10
Import the following Business Package into the

Enterprise Portal:
Download the Business Packages from the SAP

Developer Network www.sdn.sap.com
Portal
Content Portfolio
Configuration
See SAP Solution Manager content for Operational Contract Management.
3.7 Strategic Sourcing

n
n
n
n
Overview of Strategic Sourcing with RFx

Overview of Strategic Sourcing with Live Auction
07/11/2011
PUBLIC
47/72
3
3.7

Strategic Sourcing
3.7.1 Overview of Strategic Sourcing with RFx

You can use this business scenario to source goods using RFx (request for information, request
for proposal, and/or request for quotation). You can use this business scenario with or without
integration of the sourcing cockpit. The sourcing cockpit helps you, as a professional purchaser,
to process your requirements and to determine the best source of supply. You can also integrate
document storage functionality maintained in cFolders in the RFx. After you have received bids
from suppliers, you can create a purchase order or contract (local or global outline agreement)
directly from the sourcing cockpit or in SAP Bidding Engine as a result of the RFx.
The Strategic Sourcing with RFx business scenario comprises these process steps:
1.
2.
3.
4.
5.
6.
7.
8.
9.

Negotiating Contracts
Processing Bidding Events
Processing Collaborative Bidding Events Using cFolders
Evaluating Bids
Processing Follow-On Documents
Analyzing Sourcing with RFx
3.7.2 Overview of Strategic Sourcing with Live Auction

You can use this business scenario to source goods using auctions. With auctions, you can, for
example, define bidding rules. Bidders can submit bids in real time in a separate live auction
application. You can use this business scenario with or without integration of the sourcing cockpit.
The sourcing cockpit helps you, as a professional purchaser, to process your requirements and to
determine the best source of supply. After you have received bids from suppliers, you can create a
purchase order or contract (local or global outline agreement) directly from the sourcing cockpit or
in SAP Bidding Engine as a result of the auction.
The Strategic Sourcing with Live Auction business scenario comprises these process steps:
1.
2.
3.
4.
5.
6.
7.

Conducting Live Auctions
Evaluating Bids
Processing Follow-On Documents
Analyzing Sourcing with Live Auction
48/72
PUBLIC
07/11/2011
3
3.7

Strategic Sourcing

Note
The following figure shows the underlying architecture of Strategic Sourcing.

Figure 8:

Installation
07/11/2011
PUBLIC
49/72
3
3.7

Strategic Sourcing
Note
No.
Install SAP Process Integration. [Master Guide

SAP NetWeaver 7.01]
Caution

SAP Web Application Server. This means that
the running of applications in other clients of
the same SAP Web AS is not supported.
If you installed SAP Process Integration, import /

the integration objects for SAP SRM into the
SAP Process Integration. Import the PI content
for the following components:
n
SAP SRM Server 7.0
n
/
Download Support
Packages and Patches Entry by Application Group
Additional Components SAP Master Data for SLD .
2
Install/Integrate SAP ERP (SAP R/3 4.7 or higher SAP ERP is not part of this installation and
recommended)
required.
Install SAP R/3 Plug-In (2004.1 or higher if one is

available):
R/3 Plug-in 2004.1).

the SAP_APPL component. Otherwise, the
installation of the SAP R/3 Plug-In is required
if you installed an SAP back-end system in the
previous step.

Bidding Engine and SAP Supplier Self-Services
Install SAP SRM-MDM Catalog 3.0. For more

information, see SAP Note 1057316 . [SAP
50/72
PUBLIC
07/11/2011
3
3.7

Strategic Sourcing

(TREX)]
n Perform the installation steps to set up an

RFC connection
settings for document languages during the
installation of SAP NetWeaver 7.0 TREX
Install Live Auction Cockpit Web Presentation

Server (LACWPS) 7.0. [Component
Installation Guide SAP Supplier
Relationship Management 7.0 ABAP +
Java on <Platform>:<Database>]
The use of Live Auction Web Presentation

Server is optional.
You can install LACWPS either on a standalone
J2EE Engine or on a J2EE Engine installed as an
Add-In on the central instance.

2. Configure the database of your SAP Web AS
for SAP BI as described in SAP Note 567745.
For a minimal system landscape, you can install
SAP BI on your SAP SRM Server. Install the SAP
BI Business Content Add-On on the SAP SRM
Server as described in SAP Note 1172899.
SAP NetWeaver 7.0.
The use of SAP BI is optional. See the description

of this component in the Software Component
Matrix [page 16] to decide whether it is required
for your business scenario.
After the BI ABAP upgrade, you should install
the Java parts of BI (BI-Java) to take advantage
of all new functionality.
For more information, see Installation Guide
SAP NetWeaver 7.01.
Install SAP NetWeaver 7.01 Enterprise Portal.

[Master Guide SAP NetWeaver 7.01]
The use of SAP NetWeaver Enterprise Portal is

mandatory. It is required for the integration of
SAP SRM into a workset.
10
Import the following Business Packages into the Download the Business Packages from the SAP
Enterprise Portal:
Developer Network www.sdn.sap.com
n Business Package for Supplier Collaboration
2.0
Configuration
See SAP Solution Manager content for Strategic Sourcing.
07/11/2011
PUBLIC
51/72

Business Scenarios of SAP SRM-PPS
4 Business Scenarios of SAP SRM-PPS
The following scenarios are relevant if you use SAP Procurement for Public Sector (SAP PPS). These
SAP PPS scenarios require a special license agreement.
Caution
To use SAP Procurement for Public Sector, SAP SRM must be deployed as an extended classic
scenario. Other SAP SRM technical scenarios (classic, standalone, SAP SRM in one client in SAP ERP)
are not supported for SAP PPS. Furthermore, only one SAP ERP back-end system can be connected
to the SAP SRM system. Multi back-end deployment is not supported for SAP Procurement for
Public Sector.
Caution
You must install SAP SRM 7.0 SP01 before you activate the SAP PPS business functions. Activating the
business functions is irreversible; once they have been activated, you cannot deactivate them. Be
aware that accidental activation might disrupt the other business processes.
To be able to use SAP PPS, you need to activate business functions in SAP SRM and SAP ERP. For more
information, see the Customizing activity Switching Business Functions.
Note
You cannot use SAP PPS with the Service Procurement business scenario.
Note
The graphics in this section refer to the Continuous Innovation implementation option of SAP
07/11/2011
PUBLIC
53/72
4
4.1

SRM 7.0 only.
4.1 Technical System Landscape

Figure 9:
Figure 10:
Description:
n IPC 7.0 is part of SAP WebAS
n On the Portal layer, you must deploy the Portal Core components plus the following Portal Java
components:
l Knowledge Management (KM)
l Collaboration Room
l Universal Worklist (UWL)
l ADS can be deployed on the Portal
l LAC WPS can be deployed on the Portal
n The Business Packages shown above are:
BPSRM00_0.sca (BP for mySAP SRM 2007)
n The XI Content packages shown above are:
l SRMSERV6000_0.ZIP (XI Content for SAP SRM 2007 Server)
54/72
PUBLIC
07/11/2011
4
4.2

Public Sourcing and Tendering

n TREX is a separately installed instance. For scalability, multiple TREX instances can be installed
on multiple servers.
n No ERP Plug-Ins needed for SAP ERP 2005 (ECC 6.0) and higher.
4.2 Public Sourcing and Tendering
4.2.1 Overview
You use this business scenario to manage complex, highly-regulated, competitive RFx processes. You
can create legally-compliant documents within a secure infrastructure that integrates SAP Records
Management and procurement processes to fulfill audit requirements.
The Public Sourcing and Tendering business scenario comprises the following business processes:
n
n
n
n
n
n
n
n
n
Prequalification of RFx Respondents

Public RFx Publishing
Tender Fee Processing
Earnest Money Deposit Handling
Two-Envelope RFx Response
Multi-Party Verification at RFx Response Opening
RFx Response Evaluation
Electronic Contract File Creation
Analyzing Public Sourcing and Tendering
4.3 Contract Management and Administration
4.3.1 Overview
You can use this business scenario to allow a professional purchaser to negotiate a contract or
purchase order with a supplier. This negotiation may be based on the outcome of the tendering
process as described in the Public Sourcing and Tendering business scenario. Once pricing
arrangements, clauses, payment, terms, and delivery conditions have been agreed upon, the contract
or purchase order enters an approval workflow. Upon approval, the contract or purchase order is
centrally created in SAP Supplier Relationship Management (SAP SRM). Operational purchasers can
take advantage of the conditions negotiated. When users seek a specific product or service from a
contract or contract-type line item in a mixed-use purchase order, a purchase order is created, which
is then sent to the supplier. The supplier ships the required goods or provides the service to the
07/11/2011
PUBLIC
55/72
4
4.4

Operational Procurement
designated recipient. The user then completes a goods receipt or service entry on the basis of which
the supplier creates an invoice. The invoice is then paid by the organization in charge of payment.
Additionally, the system automatically creates an electronic contract file that contains all
procurement documents created. After award, any contract or purchase order modifications, as well
as their supporting documentation, are also automatically added to the electronic contract file. The
file continues to capture contractual information through closeout.
The Public Sourcing and Tendering business scenario comprises the following business processes:
n
n
n
n
n
n
n
n
Complex Contract Creation (SAP Document Builder)

Guaranteed Minimum
Closeout Execution
Contract Tracking and Monitoring
Post-Award Procedure
Options Definition
Incremental Funding
4.4 Operational Procurement
4.4.1 Overview
You can use this business scenario to process the requirements that have been created and released for
procurement (for example, demands for spare parts coming from plant maintenance, demands for
raw materials determined in a planning run, or requests for office supplies entered by an employee.)
Requirements are transferred to the purchasing department as purchase requisitions. They are
presented to the purchaser in work lists that support him in converting the requisitions into contracts
or purchase orders. The purchaser can check the source of supply and the price and conditions that
have been assigned to a requisition and start a request for quotation or bidding process if necessary.
Release procedures are available to control critical procurement processes.
The Operational Procurement business scenario comprises the following business processes:
n
n
n
n
n
n
n
Complex Sourcing
Exercise Options
Budget Integration
Order Tracking
Acceptance at Origin for PPS
Acknowledgement and Delivery
56/72
PUBLIC
07/11/2011
4
4.5
n
n
n
n

Procurement Services
Invoice Verification
Selective Release
Workload Prioritization
Workload Redistribution
4.5 Procurement Services

n Overview of Procurement Services (Automated Sourcing)
n Overview of Procurement Services (Manual Sourcing)
4.5.1 Overview of Procurement Services (Automated

Sourcing)
You can use this business scenario to satisfy requirements from external customers. In this scenario
the purchasing agency satisfies the requirements either by delivery from stock, by creation of a release
order against an existing contract, or by creation of a purchase order.
The Procurement Services (Automated Sourcing) business scenario comprises the following business
processes:
n Processing of External Requirements (Automated Sourcing)
n Third-Party Processing
n Inventory Management and Delivery from Stock
4.5.2 Overview of Procurement Services (Manual Sourcing)

You can use this business scenario to satisfy requirements from external customers. In this scenario
the purchasing agency satisfies the requirements either by delivery from stock, by creation of a release
order against an existing contract, or by creation of a purchase order.
The Procurement Services (Manual Sourcing) business scenario comprises the following business
processes:
n Processing of External Requirements (Manual Sourcing)
n Third Party Processing
n Inventory Management and Delivery from Stock
07/11/2011
PUBLIC
57/72

5 SAP Solution Manager
SAP provides the SAP Solution Manager as the platform for efficiently supporting the implementation
and operation of your SAP solution. SAP Solution Manager significantly accelerates the
implementation process, and helps you achieve your business goals. It contains predefined
implementation content (Customizing activities and transactions, as well as documentation and SAP
Notes) to help you configure your SAP SRM solution. In addition, SAP delivers support services based
on the business scenarios designed and documented in SAP Solution Manager.
Caution
The use of SAP Solution Manager is mandatory for SAP SRM When you install SAP SRM Server
7.0 or upgrade to this release, you are prompted to enter a key generated by the Solution Manager.
Without this key, the installation or upgrade process cannot continue. For more information, see
the installation or upgrade guide for SAP SRM Server 7.0.
In SAP SRM 7.0, the SAP Solution Manager contains standard implementation content for the
business scenarios, covering all key capabilities of the SAP SRM Solution Map. This enables a fast
implementation of the entire solution in units of business processes.
For the most up-to-date information about the Solution Manager Content Release for SAP SRM 7.0,
see SAP Note 1230438.
In your SAP SRM project, execute the following activities using SAP Solution Manager:
n
n
n
n
n
n
Documentation of core business processes that are changed or implemented during Ramp-Up
Plan your solution landscape
Connection of existing systems and activation of SAP EarlyWatchAlert
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 SAP Solution
Manager
Recommendation
Document, configure, and test the previously defined business processes. Train users with SAP
Solution Manager.
For more information, see the following information source for SAP Solution Manager:
07/11/2011
PUBLIC
59/72
n System infrastructure, scenarios, installation and configuration of SAP Solution

Manager: Master Guide- SAP Solution Manager available on SAP Service Marketplace at
SAP Components SAP Solution Manager .
n Benefits and usage scenarios: SAP Solution Manager Learning Maps available
on SAP Service Marketplace at http://service.sap.com/rkt-solman or
http://service.sap.com/solutionmanager .
n Additional information: SAP Service Marketplace at
http://service.sap.com/solutionmanager
and in the Master
guide for SAP enhancement package 1 for SAP NetWeaver 7.0 available at
The following information summarizes installation considerations:

n Each SAP SRM (or SAP NetWeaver) system landscape must be assigned to an installation of the
SAP Solution Manager. In the event of a support-relevant incident within your SAP system
landscape, SAP Support requires remote access to the SAP Solution Manager that hosts the
affected system landscape.
n If you already have an SAP Solution Manager deployment in place, you can also use it to manage
the solution you build with SAP NetWeaver and SAP SRM as well. In this case, we recommend
updating SAP Solution Manager and Solution Manager content to the latest version.
n It is possible to install multiple instances of the SAP Solution Manager. In this case, each
installation should host separate business solutions.
n To reduce the risk of unavailability, do not install SAP Solution Manager as a central component.
Instead, operate a two-system landscape with test and production environment of SAP Solution
Manager, especially if you are using time-critical functions like Support Desk. If you also develop
your own content, a three-system landscape with development, test, and production environment
is recommended.
60/72
PUBLIC
07/11/2011
References
6 References
Caution
Make sure you have the latest documentation version by checking SAP Service Marketplace at
SAP Business Suite Applications SAP SRM Using SAP
SRM Server 7.0 immediately before starting the installation.
List of documentation references for this SAP Business Suite solution and its business scenarios:
Title
Where to find
Installation Guide SAP SRM 7.0 on

SAP Service Marketplace at

SAP Business Suite

Master Guide SAP NetWeaver 7.0
SAP SRM
SAP SRM 7.0

SAP NetWeaver
Upgrade Master Guide SAP SRM 7.0

SAP Business Suite

Installation Guide SAP NetWeaver 7.0 Search and
Classification (TREX)
SAP SRM
SAP SRM 7.0

SAP NetWeaver
<Business Scenario>
See SAP Solution Manager for SAP SRM
Configuration documentation for SAP SRM 7.0 for

each business scenario
All configuration documentation for SAP SRM 7.0 is

available in SAP Solution Manager.
SAP SRM-MDM Catalog 3.0 Installation Guide

SAP Business Suite
SAP SRM
SAP SRM 7.0
The following table lists all SAP Notes referred to in this document.
List of SAP Notes
SAP Note Number
Title
704564
R/3 Plug-In: PI 2004.1 installation/delta upgrade
708736
Release limitations concerning R/3 Plug-In 2004.1
07/11/2011
PUBLIC
61/72
References
SAP Note Number
Title
1177779
SRM-MDM Catalog 3.0 Installation
567745
Composite note BW 3.x performance: DB-specific

setting
62/72
PUBLIC
07/11/2011
Media List
7 Media List
You can find the media list for SAP SRM 7.0 on the SAP Service Marketplace at
http://service.sap.com/srm-inst under SAP SRM Server 7.0
Media List - SAP SRM7.0
07/11/2011
PUBLIC
63/72

Reference
A Reference
A.1 The Main SAP Documentation Types

The following is an overview of the most important documentation types that you need in the
various phases in the life cycle of SAP software.
Cross-Phase Documentation
SAPterm is SAPs terminology database. It contains SAP-specific vocabulary in over 30 languages, as

well as many glossary entries in English and German.
n Target group:
l Relevant for all target groups
Current
version:
n
l On SAP Help Portal at http://help.sap.com
l In the SAP system in transaction STERM
Glossary
SAP Library is a collection of documentation for SAP software covering functions and processes.
n Target group:
l Consultants
l System administrators
l Project teams for implementations or upgrades
n Current version:
l On SAP Help Portal at http://help.sap.com (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for
raising security levels. A collective security guide is available for SAP NetWeaver. This document
contains general guidelines and suggestions. SAP applications have a security guide of their own.
n Target group:
l Technology consultants
l Solution consultants
n Current version:
l On SAP Service Marketplace at http://service.sap.com/securityguide
Implementation
The master guide is the starting point for implementing an SAP solution. It lists the required
installable units for each business or IT scenario. It provides scenario-specific descriptions of
07/11/2011
PUBLIC
65/72
Reference
A.1
The Main SAP Documentation Types
preparation, execution, and follow-up of an implementation. It also provides references to other

documents, such as installation guides, the technical infrastructure guide and SAP Notes.
n Target group:
l Project teams for implementations
n Current version:
l On SAP Service Marketplace at http://service.sap.com/instguides
The installation guide describes the technical implementation of an installable unit, taking
into account the combinations of operating systems and databases. It does not describe any
business-related configuration.
n Target group:
n Current version:
Configuration Documentation in SAP Solution Manager SAP Solution Manager is a life-cycle
platform. One of its main functions is the configuration of business scenarios, business processes,
and implementable steps. It contains Customizing activities, transactions, and so on, as well as
documentation.
n Target group:
Current
version:
n
l In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system.
The Customizing activities and their documentation are structured from a functional perspective.
(In order to configure a whole system landscape from a process-oriented perspective, SAP Solution
Manager, which refers to the relevant Customizing activities in the individual SAP systems, is used.)
n Target group:
l Project teams for implementations or upgrades
n Current version:
l In the SAP menu of the SAP system under Tools
Customizing
IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver, and precedes the application operations guides of SAP Business Suite. The manual refers
66/72
PUBLIC
07/11/2011
Reference
A.1
users to the tools and documentation that are needed to carry out various tasks, such as monitoring,
backup/restore, master data maintenance, transports, and tests.
n Target group:
n Current version:
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed. It refers users to the tools and documentation
that are needed to carry out the various operations-related tasks.
n Target group:
n Current version:
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of
an upgrade. It also refers to other documents, such as upgrade guides and SAP Notes.
n Target group:
l Project teams for upgrades
n Current version:
The upgrade guide describes the technical upgrade of an installable unit, taking into account
the combinations of operating systems and databases. It does not describe any business-related
configuration.
n Target group:
n Current version:
Release notes are documents that contain short descriptions of new features in a particular release
or changes to existing features since the previous release. Release notes about ABAP developments
are the technical prerequisite for generating delta and upgrade Customizing in the Implementation
Guide (IMG).
n Target group:
07/11/2011
PUBLIC
67/72
Reference
A.1
l Consultants
n Current version:
l On SAP Service Marketplace at http://service.sap.com/releasenotes
l In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
68/72
PUBLIC
07/11/2011
Typographic Conventions
Example
Description
<Example>
Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, Enter your <User Name>.
Example
Example
Arrows separating the parts of a navigation path, for example, menu options
Example
Emphasized words or expressions
Example
Words or characters that you enter in the system exactly as they appear in the
documentation
http://www.sap.com
Textual cross-references to an internet address
/example
Quicklinks added to the internet address of a homepage to enable quick access to

specific content on the Web
123456
Hyperlink to an SAP Note, for example, SAP Note 123456
Example
n Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
n Cross-references to other documentation or published works
Example
n Output on the screen following a user action, for example, messages

n Source code or syntax quoted directly from a program
n File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE
Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE
Keys on the keyboard
07/11/2011
PUBLIC
69/72
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,
z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented
by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, and other SAP products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany
and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence,
Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks
or registered trademarks of Business Objects Software Ltd. in the United States and in other countries.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies
(SAP Group) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not
be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are
those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
70/72
PUBLIC
07/11/2011
This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2
from Michael Kay (http://saxon.sf.net/), XSLT version 1.
Disclaimer
Some components of this product are based on Java. Any code change in these components may cause unpredictable and
severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.
Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or
altered in any way.
Documentation in the SAP Service Marketplace
You can find this document at the following address: http://service.sap.com/instguides
07/11/2011
PUBLIC
71/72
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
Copyright 2011 SAP AG. All rights reserved.

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung
durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden.

Master Guide SRM 7.0

Uploaded by

Copyright:

Available Formats

Master Guide SRM 7.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Master Guide SRM 7.0

Uploaded by

Copyright:

Available Formats

Master Guide

SAP Supplier Relationship Management powered by SAP

Information on the Catalog Content Management business scenario added to

SAP SRM Overview . . . . . . . . . . . . . . . . . . . .

Business Scenarios of SAP SRM . . . . . . . . . . .

Technical System Landscape . . . . . . . .

Business Scenarios of SAP SRM-PPS . . . . . . .

SAP Solution Manager . . . . . . . . . . . . . . . . . . . .

Public Sourcing and Tendering

1.1 About this Document

Installation guides for single software units

1.2 Planning Information

Location on SAP Service Marketplace

The latest version of the installation and upgrade

SAP Solution Manager

SAP R/3 plug-in releases and availability

Information about SRM components and further

Information about SAP SRM Support Package stacks

Download of SAP software (SAP Software Distribution

SAP Notes search

SAP Online Knowledge Products (OKPs)

1.3 Important SAP Notes

Installation Options with SAP

This note describes which

Enterprise Services Bundles

Lists business-related grouping of

SRM-MDM Catalog 3.0 Installation

Solution Manager Content for SAP

SAP SRM 7.0: Release &

This page is left blank for documents

SAP SRM Overview

2 SAP SRM Overview

2.1 Software Units of SAP SRM

2.1.1 Application Components: SAP SRM Software Units

SAP SRM Overview

SAP SRM Overview

2.1.2 Technology Components

Use the latest available front-end software.

SAP SRM Overview

linked with certain industry-specific components. All SAP-industry-specific components based

2.1.3 Non-SAP Components

2.2 Software Component Matrix

SAP SRM Overview

2.3 System Landscape

SAP SRM Overview

2.4 Overall Installation Sequence

SAP SRM Overview

2.5 Automated Post-Installation Configuration Tools

2.5.1 Automated Configuration of the Portal Systems

2.5.2 Automated Configuration of SAP SRM and SAP ERP

2.5.3 Automated Configuration of SAP SRM and One Client

SAP SRM Overview

2.5.4 Automated Configuration of SAP SRM and SAP

2.6 Service-Oriented Architecture (SOA)

SAP SRM Overview

2.7 SAP SRM on One Client in SAP ERP

2.8 Flexible Deployment Variants

2.8.1 Deployment Options

SAP SRM Overview

2.8.2 Technical Scenarios