Srm 7.0master Guide

Master GuideSAP Supplier Relationship Management powered by SAPNetWeaver®Using SAP SRM Server 7.0®

Target Audience

n System administratorsn Technology consultants

PUBLICDocument version: 1.2 ‒ 03/12/2010Material number: 50098575

Document History

Caution

Before you start the implementation, make sure you have the latest version of this document. Youcan 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 tosection 2.2 Software Component Matrix

2/72 PUBLIC 03/12/2010

http://service.sap.com/instguides



Table of Contents

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . 71.1 About this Document . . . . . . . . . . . . . . . . . . . . . 81.2 Planning Information . . . . . . . . . . . . . . . . . . . . . 101.3 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2 SAP SRMOverview . . . . . . . . . . . . . . . . . . . . . 132.1 Software Units of SAP SRM . . . . . . . . . . . . . . . . . . . 132.1.1 Application Components: SAP SRM Software Units . . . . . . . . . . 132.1.2 Technology Components . . . . . . . . . . . . . . . . . . . 152.1.3 Non-SAP Components . . . . . . . . . . . . . . . . . . . . 162.2 Software Component Matrix . . . . . . . . . . . . . . . . . . 162.3 System Landscape . . . . . . . . . . . . . . . . . . . . . . 172.4 Overall Installation Sequence . . . . . . . . . . . . . . . . . . 182.5 Automated Post-Installation Configuration Tools . . . . . . . . . . 192.5.1 Automated Configuration of the Portal Systems . . . . . . . . . . . 192.5.2 Automated Configuration of SAP SRM and SAP ERP System Integration . . 192.5.3 Automated Configuration of SAP SRM and One Client System Integration . 192.5.4 Automated Configuration of SAP SRM and SAP NetWeaver BW System

Integration . . . . . . . . . . . . . . . . . . . . . . . . . 192.6 Service-Oriented Architecture (SOA) . . . . . . . . . . . . . . . 202.7 SAP SRM on One Client in SAP ERP . . . . . . . . . . . . . . . 202.8 Flexible Deployment Variants . . . . . . . . . . . . . . . . . . 212.8.1 Deployment Options . . . . . . . . . . . . . . . . . . . . . 212.8.2 Technical Scenarios . . . . . . . . . . . . . . . . . . . . . 212.8.3 Business Scenarios . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 3 Business Scenarios of SAP SRM . . . . . . . . . . . . . . . . 233.1 Self-Service Procurement . . . . . . . . . . . . . . . . . . . 233.1.1 Overview of Self-Service Procurement (Classic) . . . . . . . . . . . 233.1.2 Overview of Self-Service Procurement (Extended Classic) . . . . . . . . 243.1.3 Technical System Landscape . . . . . . . . . . . . . . . . . . 243.1.4 Implementation Sequence . . . . . . . . . . . . . . . . . . . 253.2 Plan-Driven Procurement . . . . . . . . . . . . . . . . . . . 283.2.1 Overview of Plan-Driven Procurement with Plant Maintenance . . . . . 283.2.2 Overview of Plan-Driven Procurement with Supplier Integration . . . . . 28

03/12/2010 PUBLIC 3/72

3.2.3 Technical System Landscape . . . . . . . . . . . . . . . . . . 293.2.4 Implementation Sequence . . . . . . . . . . . . . . . . . . . 303.3 Service Procurement . . . . . . . . . . . . . . . . . . . . . 323.3.1 Overview of Service Procurement (Classic) . . . . . . . . . . . . . 323.3.2 Overview of Service Procurement External Staffing . . . . . . . . . . 333.3.3 Technical System Landscape . . . . . . . . . . . . . . . . . . 343.3.4 Implementation Sequence . . . . . . . . . . . . . . . . . . . 343.4 Catalog Content Management . . . . . . . . . . . . . . . . . 373.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 373.4.2 Technical System Landscape . . . . . . . . . . . . . . . . . . 373.4.3 Implementation Sequence . . . . . . . . . . . . . . . . . . . 383.5 Analytics . . . . . . . . . . . . . . . . . . . . . . . . . 393.5.1 Overview of Spend Analysis . . . . . . . . . . . . . . . . . . 393.5.2 Overview of Supplier Evaluation . . . . . . . . . . . . . . . . . 403.5.3 Technical System Landscape . . . . . . . . . . . . . . . . . . 413.5.4 Implementation Sequence . . . . . . . . . . . . . . . . . . . 413.6 Operational Contract Management . . . . . . . . . . . . . . . . 433.6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 433.6.2 Technical System Landscape . . . . . . . . . . . . . . . . . . 443.6.3 Implementation Sequence . . . . . . . . . . . . . . . . . . . 453.7 Strategic Sourcing . . . . . . . . . . . . . . . . . . . . . . 473.7.1 Overview of Strategic Sourcing with RFx . . . . . . . . . . . . . . 483.7.2 Overview of Strategic Sourcing with Live Auction . . . . . . . . . . 483.7.3 Technical System Landscape . . . . . . . . . . . . . . . . . . 493.7.4 Implementation Sequence . . . . . . . . . . . . . . . . . . . 49

Chapter 4 Business Scenarios of SAP SRM-PPS . . . . . . . . . . . . . . 534.1 Technical System Landscape . . . . . . . . . . . . . . . . . . 544.2 Public Sourcing and Tendering . . . . . . . . . . . . . . . . . 554.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 554.3 Contract Management and Administration . . . . . . . . . . . . . 554.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 554.4 Operational Procurement . . . . . . . . . . . . . . . . . . . 564.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 564.5 Procurement Services . . . . . . . . . . . . . . . . . . . . . 574.5.1 Overview of Procurement Services (Automated Sourcing) . . . . . . . 574.5.2 Overview of Procurement Services (Manual Sourcing) . . . . . . . . . 57

Chapter 5 SAP Solution Manager . . . . . . . . . . . . . . . . . . . . 59

Chapter 6 References . . . . . . . . . . . . . . . . . . . . . . . . 61

4/72 PUBLIC 03/12/2010

Chapter 7 Media List . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter A Reference . . . . . . . . . . . . . . . . . . . . . . . . . 65A.1 The Main SAP Documentation Types . . . . . . . . . . . . . . . 65

03/12/2010 PUBLIC 5/72

6/72 PUBLIC 03/12/2010

1 Getting Started

1 Getting Started

The SAP Supplier Relationship Management® (SAP SRM) Master Guide provides a central startingpoint for the technical implementation of SAP SRM.To facilitate the implementation process, all information within this document is organized byscenario. You can choose from several generic business scenarios and find all the information relevantfor 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 aredescribed in detail.The complete SAP SRM solution consists of the following top-level scenarios and business scenarios:SRM Core

n Self-Service Procurementl Self-Service Procurement (Classic)l Self-Service Procurement (Extended Classic)

n Plan-Driven Procurementl Plan-Driven Procurement with Plant Maintenance

l Plan-Driven Procurement with Supplier Integration

n Service Procurementl Service Procurement Classic

l Service Procurement External Staffing

n Strategic Sourcingl Strategic Sourcing with RFxl Strategic Sourcing with Live Auction

n Operational Contract Managementn Catalog Content Managementn Analyticsl Spend Analysisl Supplier Evaluation

SRM Procurement for Public Sector

Note

The SRM Procurement for Public Sector business scenarios require a special license agreement.

03/12/2010 PUBLIC 7/72

1 Getting Started1.1 About this Document

Caution

You must install SAP SRM 7.0 SP01 before you activate the SRM PPS business functions. Activatingthe 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 Public Sourcing and Tenderingn Contract Management and Administrationn Operational Procurementn Procurement Servicesl Procurement Services with Automated Sourcingl Procurement Services with Manual Sourcing

Note

For information about upgrading the SAP SRM business scenarios, see the SAP SRM UpgradeMaster Guide. This guide provides information about the overall upgrade sequences, referencesto related documentation, SAP Notes, and additional upgrade information for each businessscenario of SAP SRM. The Upgrade Master Guide is available on SAP Service Marketplace athttp://service.sap.com/instguides SAP Business Suite Applications SAP SRM SAP SRM 7.0

1.1 About this Document

PurposeThis Master Guide is the central starting point for the technical implementation of SAP SRM. Youcan find cross-scenario implementation information as well as scenario-specific information inthis guide.

Note

You can use SAP SRM 7.0 with SAP NetWeaver 7.01. This implementation option is called ContinuousInnovation. As of May 6th 2009, you can also use SAP SRM 7.0 with SAP NetWeaver 7.0. Thisimplementation option is called Easy Adoption.This guide, including the graphics, describes the Continuous Innovation implementationoption of SAP SRM 7.0 only. For information on the software components required for EasyAdoption, see the Software Component Matrix for SAP SRM 7.0 on the SAP Service Marketplace athttp://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 MasterGuide, which you can find on SAP ServiceMarketplace at http://service.sap.com/instguides

SAP Business Suite Applications SAP SRM SAP SRM 7.0

8/72 PUBLIC 03/12/2010




http://service.sap.com/srm-inst




1 Getting Started1.1 About this Document

Use the Master Guide to get an overview of SAP SRM, its software units, and its scenarios froma technical perspective. The Master Guide is a planning tool that helps you to design your systemlandscape. It refers you to the required detailed documentation, mainly:

n Installation guides for single software unitsn SAP Notes

n Configuration documentationn 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 informationcrucial to the installation.

n SAP SRM Overview [page 13] contains:l A short introduction to the SAP Business Suite solution

l The software component matrixl The minimal system landscapel 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 areused, including technical system landscape examples

l Information about the overall installation sequence and subsequent stepsl References [page 61] to related installation guidesl Information about mutual dependencies that affect two or more components within the

business scenarion 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 implementationcontent 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 SAPSRM 7.0 and the latest installation and configuration guides on SAP Service Marketplace athttp://service.sap.com/instguides . We strongly recommend that you use the documents

available here. The guides are regularly updated.

Constraints

03/12/2010 PUBLIC 9/72




1 Getting Started1.2 Planning Information

n The business scenarios that are presented here serve as examples of how you can use SAP softwarein your company. The business scenarios are only intended as models and do not necessarily runthe way they are described here in your customer-specific system landscape. Ensure to check yourrequirements and systems to determine whether these scenarios can be used productively at yoursite. Furthermore, we recommend that you test these scenarios thoroughly in your test systems toensure they are complete and free of errors before going live.

n This Master Guide primarily discusses the overall technical implementation of SAP SRM, ratherthan its subordinate components. This means that additional software dependencies mightexist without being mentioned explicitly in this document. You can find more information oncomponent-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 contenton SAP Service Marketplace:

Content Location on SAP Service Marketplace

The latest version of the installation and upgradeguides for SAP SRM, links to related SAP Notes

http://service.sap.com/instguides Installationand Upgrade Guides SAP Business Suite Applications SAPSRM SAP SRM 7.0 Server

Released platforms http://service.sap.com/platforms ProductAvailability 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 furtherdocuments

http://service.sap.com/srm SRM 7.0

Information about SAP SRM Support Package stacksand download of Support Package stacks

http://service.sap.com/sp-stacks

Download of SAP software (SAP Software DistributionCenter)

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 03/12/2010



http://service.sap.com/platforms


http://service.sap.com/security

http://service.sap.com/security

http://service.sap.com/solutionmanager


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

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

http://service.sap.com/sizing


http://service.sap.com/srm

http://service.sap.com/srm





http://service.sap.com/notes




1 Getting Started1.3 Important SAP Notes

1.3 Important SAP Notes

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

SAP Note Title Description

1224284 Enterprise Services Bundles ‒Required Technical Usages andBusiness Functions

Lists business-related grouping ofEnterprise Services

1177779 SRM-MDMCatalog 3.0 Installation

1230438 Solution Manager Content for SAPSRM 7.0

1223493 SAP SRM 7.0: Release &Information Note

03/12/2010 PUBLIC 11/72




http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1224284&_NLANG=en&_NVERS=0




This page is left blank for documentsthat are printed on both sides.

2 SAP SRM Overview

2 SAP SRM Overview

This section gives you an overview of the application components of SAP Supplier RelationshipManagement (SAP SRM). It also provides system landscape and installation sequence information, aswell as a brief introduction to Service Oriented Architecture (SOA) and the One Client deploymentoption.

Note

You can use SAP SRM 7.0 with SAP NetWeaver 7.01. This implementation option is called ContinuousInnovation. As of May 6th 2009, you can also use SAP SRM 7.0 with SAP NetWeaver 7.0. Thisimplementation option is called Easy Adoption.This section, including the graphics, describes the Continuous Innovation implementationoption of SAP SRM 7.0 only. For information on the software components required for EasyAdoption, see the Software Component Matrix for SAP SRM 7.0 on the SAP Service Marketplace athttp://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 technologycomponents that comprise SAP SRM 7.0.

2.1.1 Application Components: SAP SRM Software Units

n SAP Supplier Relationship Management ServerThe SAP Supplier Relationship Management Server (SAP SRM Server) includes both SAP SRMand SAP Bidding Engine.SAP SRM is based on SAP NetWeaver Application Server® (AS) and is an application and databaseinstance installation released on several database and operating system platforms (for moreinformation, see SAP Service Marketplace at http://service.sap.com/platforms PlatformAvailability Matrix .

n SAP Bidding EnginePurchasers can use SAP Bidding Engine to create and process RFx, and bidders can use SAP BiddingEngine to submit bids in response to these RFx. Both purchasers and bidders can use reverse

03/12/2010 PUBLIC 13/72





2 SAP SRM Overview2.1 Software Units of SAP SRM

auction functions in a separate Live Auction application. Purchasers can define rules for biddingand bidders can submit bids in real time.

n Online Transaction Processing SystemAn online transaction processing system (OLTP), for example, SAP ERP system, is used in the SAPSRM 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 aswell as in other SAP software units.

n SAP NetWeaver Business IntelligenceBusiness Intelligence (BI) provides infrastructure for:l Data warehousingl A range of analytical technologies and functionsl Web-based reporting and analysisl 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 datal Open analysis interfaces that make available various interfaces for connecting front-end tools of

third-party providersl Web design API allowing for the implementation of highly individualized scenarios as well as

more demanding applications containing customer-defined interface elementsBI is the foundation for the SRM scenario Spend Analysis, and can be installed for the others. BIincludes 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 alsorequire BI-Java, AS-Java, and SAP Enterprise Portal. Other combinations can be used in onesystem as well.

n SAP NetWeaver Enterprise PortalSAP NetWeaver Portal serves as a single point of entry to the applications, services, and informationof the organization.Running an Enterprise Portal is an IT scenario providing role-based and secure access to all typesof applications, services, and information in an enterprise workset environment.Customers can benefit from the numerous predefined business packages available to them, orthey can create their own content.

n Live Auction Cockpit Web Presentation ServerLive Auction Cockpit Web Presentation Server is a J2EE-based software unit comprising a virtualauction floor for reverse auctions, real-time monitoring, real-time bidding, a tight integration toall procurement processes, and a state-of-the-art user interface.

n 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, automaticdocument classification, and search and aggregation over structured data in SAP applications.

14/72 PUBLIC 03/12/2010

2 SAP SRM Overview2.1 Software Units of SAP SRM

TREX can handle text from documents in numerous formats, including Microsoft Office andAdobe 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-basedclassification, offer users great power and flexibility.

Note

To use the SAP NetWeaver Enterprise Search application (Embedded Search), the installation ofSAP NetWeaver Search and Classification (TREX) 7.1 is required.

n SRM-MDM CatalogThe SRM-MDMCatalog is based on SAPNetWeaverMaster DataManagement (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 andsupporting 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 toconnect 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 alsocontains core components for Business Process Management for application-embedded andapplication-unbounded processes.

n SAP GUIThe latest release of the SAP GUI software (such as SAP GUI 6.20) can be used with all the previousSAP component releases. Consequently, older SAP systems can also benefit from the features thatare 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 systemsand other SAP components. The SAP R/3 Plug-In supplies the SAP components with transactiondata and master data in real time. With it SAP application components like SAP CRM can be

03/12/2010 PUBLIC 15/72

2 SAP SRM Overview2.2 Software Component Matrix

linked with certain industry-specific components. All SAP-industry-specific components basedon SAP R/3 4.7 and higher SAP R/3 releases require an SAP R/3 Plug-In. The SAP R/3 Plug-In isan 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. Youcan order the most recent SAP R/3 Plug-In releases free of charge or download them from theSAP 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 athttp://service.sap.com/r3-plug-in .

n SAP NetWeaver Application ServerApplication Server (AS) is the application platform of SAP NetWeaver and, consequently, of theSAP 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 environmentfor 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 SRMbusiness scenarios and their associated software units, in both ContinuousInnovation and Easy Adoption, see the Software Component Matrix for SAP SRM 7.0 on the SAPService 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 SAPNetWeaver 7.01. The Easy Adoption functions require SAP NetWeaver 7.0.

For the latest component version and patch level requirements, see SAP Service Marketplace athttp://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 03/12/2010

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







2 SAP SRM Overview2.3 System Landscape

Note

This Master Guide provides just one way to implement each business scenario. For other ways toimplement business scenarios, see the Scenario & Process Component list in SAP Service Marketplaceat http://service.sap.com/scl . The Scenario & Process Component list helps you to findimplementation alternatives for SAP solutions, business scenarios, and processes. It shows you whichapplication components are needed to implement a business scenario or process.

The exact locations of the required software components on the corresponding DVD(s) andCD(s) that are shipped with the SAP SRM 7.0 package can be found at SAP Service Marketplace athttp://service.sap.com/instguides SAP Business Suite Applications SAP SRM SAP SRM 7.0 .

Note

For each component listed in the Software Component Matrix, there are software requirements thatare not explicitly mentioned in this documentation. Component-specific software requirementsare documented for a component in its installation guide. All related implementation guides arelisted 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 suppliertexts, 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 systemlandscape as your production landscape.Enhanced requirements on performance, scalability, high availability, and security reasons cannot bemet 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 moreinformation about released platforms for SAP SRM. see SAP Service Marketplace athttp://service.sap.com/platforms Product Availability Matrix .

n Provide a sufficiently sized server. For information on sizing, see SAP Service Marketplace athttp://service.sap.com/sizing .

03/12/2010 PUBLIC 17/72

http://service.sap.com/scl












2 SAP SRM Overview2.4 Overall Installation Sequence

Caution

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

2.4 Overall Installation Sequence

PurposeThe following figure describes the installation sequence for SAP SRM comprising components of allSAP SRM business scenarios.

Figure 1:

Note

Some of these software components may be optional for some/all business scenarios. For moreinformation 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 softwarecomponents on the same level can be installed at the same time on the appropriate machine (forexample, different project groups could install SAP ERP and SAP PI simultaneously).

18/72 PUBLIC 03/12/2010

2 SAP SRM Overview2.5 Automated Post-Installation Configuration Tools

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 integrationof the SAP Supplier Relationship Management (SAP SRM) and SAP NetWeaver Portal systems.For more information about automating this integration, see SAP Service Marketplace athttp://service.sap.com/instguides 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 ERPSystem Integration

You can automate the mandatory configuration steps necessary to configure the integrationof the SAP Supplier Relationship Management (SAP SRM) and SAP ERP systems. Formore information about automating this integration, see SAP Service Marketplace athttp://service.sap.com/instguides SAP Business Suite Applications SAP SRM SAP SRM Server

7.0 Guide for Automated Configuration: Connecting SAP SRM to SAP ERP .

2.5.3 Automated Configuration of SAP SRM and One ClientSystem Integration

You can automate the mandatory configuration steps necessary to configure the integration ofthe SAP Supplier Relationship Management (SAP SRM) and SAP SRM on One Client in SAPERP. For more information about automating this integration, see SAP Service Marketplace athttp://service.sap.com/instguides SAP Business Suite Applications SAP SRM SAP SRM Server

7.0 Guide for Automated Configuration: Connecting SAP SRM to One Client .

2.5.4 Automated Configuration of SAP SRM and SAPNetWeaver BW System Integration

You can automate the mandatory configuration steps necessary to configure the integration of theSAP Supplier Relationship Management (SAP SRM) and SAP NetWeaver Business Warehouse (SAPNetWeaver BW) systems. For more information about automating this integration, see SAP ServiceMarketplace at http://service.sap.com/instguides SAP Business Suite Applications SAP SRMSAP SRM Server 7.0 Guide for Automated Configuration: Connecting SAP SRM to SAP BW .

03/12/2010 PUBLIC 19/72





2 SAP SRM Overview2.6 Service-Oriented Architecture (SOA)

2.6 Service-Oriented Architecture (SOA)

In general, service-oriented architecture (SOA) is an architectural pattern that requires all exposedfunctionality to be published as services in a platform-independent manner. These services can beconsumed by other applications. To successfully utilize SOA on an enterprise level, you need toconsider several additional aspects. All interfaces need to be clearly defined and stable and make useof global (at least landscape-wide) data types. Both points ensure loose coupling and reliability forservice consumers and avoid superfluous transformations caused by technically different, whilesemantically identical information. To establish additional reliability, all services must follow clearlydefined communication and behavioral patterns — Clients need to know whether services aresynchronous or asynchronous, whether they return an answer, how they handle exceptions andwhich security policy they use.Additionally, the underlying business model (interaction between business objects) needs to betransparent to establish common ground in terms of relationships between business objects that playa role when calling services.For more information about services, see ES Workplace at www.sdn.sap.com Enterprise SOAExplore Enterprise Services ES Workplace

Forward error handling (FEH) for asynchronous inbound interfaces

Forward error handling (FEH) is required only for asynchronous inbound interfaces. Asynchronousservices do not confirm the arrival of a document into the inbound interface, so that the status ofa transmitted document is unknown for the sender system (that is, the sender system does notknow whether the document was created correctly). FEH avoids such confusion, as any erroneousdocuments are collected in the Post-Processing Office (PPO) of the receiver system. FEH supportsthe correction and reprocessing of the documents from the PPO.For information about Enterprise Services Bundles, see SAP Note 1224284.

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 EnhancementPack 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 SolutionManager at SAP ERP Configuration Structures SAP enhancement package 4 for SAP ERP 6.0 Basicsettings for enhancement pack 4

20/72 PUBLIC 03/12/2010

http://www.sdn.sap.com



2 SAP SRM Overview2.8 Flexible Deployment Variants

2.8 Flexible Deployment Variants

The following two flexible deployment variants are available in SAP Supplier RelationshipManagement 7.0 (SAP SRM 7.0):

n Portal-independent navigation frameYou can use this function to work with SAP SRM if you are not using the SAP NetWeaver Portaland therefore cannot use its navigation frame. When using the portal-independent navigationframe, an inbox for processing work items, alerts, and notifications is also available.

n BW-independent analyticsYou 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 (SAPNetWeaver BW) system.

ConfigurationSee 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, theinbox, 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.

For more information about what scenarios and functions are supported for SAP SRM on One Clientin SAP ERP, see section SAP SRM on One Client in SAP ERP [page 20] 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 notsupported 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) arecompatible with the following technical scenarios:

03/12/2010 PUBLIC 21/72

2 SAP SRM Overview2.8 Flexible Deployment Variants

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 flexibledeployment 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 theportal-independent navigation frame.

BW-Independent Analytics

You can use BW-independent analytics with all of the business scenarios in SAP SRM except for theSpend Analysis and Supplier Evaluation business scenarios.

22/72 PUBLIC 03/12/2010

3 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 ) foralternatives. The Scenario & Process Component List helps you to find realization alternatives forSAP solutions, business scenarios, and processes. It shows you which application components areneeded 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 Overview Self-Service Procurement (Classic)n Overview Self-Service Procurement (Extended Classic)n Technical System Landscapen 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. Thisrelieves your purchasing department of a huge administrative burden while making the procurementprocess faster and more responsive. In this scenario, only the shopping cart is created in the SAPSupplier Relationship Management (SAP SRM) system. All other procurement documents, such aspurchase orders, goods receipts, and invoices, are located in the back-end system.The Self-Service Procurement (Classic) business scenario comprises these process steps:

1. Processing Shopping Carts2. Processing Purchase Requisitions in SAP ERP3. Processing Purchase Orders in SAP ERP4. Inbound Processing and Receipt Confirmation with Warehouse Management5. Verifying Logistics Invoices Online/In Background

03/12/2010 PUBLIC 23/72




3 Business Scenarios of SAP SRM3.1 Self-Service Procurement

6. Analyzing Self-Service Procurement

3.1.2 Overview of Self-Service Procurement (ExtendedClassic)

Your employees can use this business scenario to create and manage their own requisitions. Thisrelieves your purchasing department of a huge administrative burden, while making the procurementprocess faster and more responsive. In this scenario, shopping carts and purchase orders are createdin the SAP Supplier Relationship Management (SAP SRM) system, and are then replicated to theback-end system. The purchase order in SAP SRM is the leading purchase order; it cannot be changedin the back-end system. Goods receipts and invoices can be pre-entered in SAP SRM or entereddirectly 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. Processing Shopping Carts2. Searching for Sources of Supply Centrally3. Processing Purchase Orders in SAP SRM4. Inbound Processing and Receipt Confirmation without Warehouse Management5. Confirming Receipt of Inbound Goods in SAP SRM6. Processing Invoices in SAP SRM7. Verifying Logistics Invoices (Online/In Background)8. 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 scenarioto meet your needs, see:

n SAP Service Marketplace at http://service.sap.com/platforms Platform Availability Matrix

n SAP Service Marketplace at http://service.sap.com/slo

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

24/72 PUBLIC 03/12/2010




http://service.sap.com/slo




Figure 2:

For a more readable version of this graphic, go to the SAP Service Marketplace athttp://service.sap.com/instguides SAP Business Suite SAP SRM SAP SRM 7.0

n IPC 7.0 is part of the component AP 7.0n 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, applicationconfiguration) required to implement the business scenario. Rows containing optional componentsare shaded. The scenario can function without these optional components; but they do provideadditional functions.Installation

Note

n See the section Overall Installation Sequence [page 18], especially if you want to implement morethan one SAP SRM business scenario at a time.

n For documentation referenced in the following table, see the section References [page 61].

03/12/2010 PUBLIC 25/72





No. Action (Corresponding Documentation Remarks/Subsequent Steps

Install SAP Process Integration. [MasterGuide ‒ SAP NetWeaver 7.01]

The use of SAP Process Integration is optionalbut it is required for outbound XML-basedmessaging or for connecting non-SAPplanning or execution systems.

CautionSAP Process Integration requires a dedicatedSAP Web Application Server. This meansthat the running of applications in otherclients of the same SAP Web AS is notsupported.

If you installed SAP Process Integration,import the integration objects for SAP SRMinto the SAP Process Integration. Import thePI content for the following components:n

SAP SRM Server 7.0n

SAP SRM-MDM Catalog 3.0n

SAP BI Content 7.0.4

/

1

Download and install the latest SLDContent from SAP Service Marketplaceat http://service.sap.com/swdc

Download Support Packages and Patches Entryby Application Group Additional ComponentsSAP Master Data for SLD .

/

2 Install/Integrate SAP ERP (SAP R/3 4.7 orhigher recommended)

SAP ERP is not part of this installation andare not contained in the installation package.A separate SAP ERP installation package isrequired.

3 Install SAP R/3 Plug-In (2004.1 or higher ifone is available):n For the installation, see SAP Notes 704564

(R/3 plug-in: PI 2004.1 installation/deltaupgrade) and 708736 (Release restrictionsR/3 Plug-in 2004.1).

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

Not required for customers with an SAP R/3Enterprise 47x200 back-end system. FromSAP R/3 Enterprise 47x200 onwards, theformer plug-in functions are delivered withthe SAP_APPL component. Not required ifexclusively local PO handling is performed,or no SAP back-end system is used.

4 Install SAP SRM Server 7.0 comprising SAPBidding Engine[Installation Guide ‒ SAP SRM Server 7.0]

/

26/72 PUBLIC 03/12/2010



http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=704564 &_NLANG=en&_NVERS=0






5 Install SRM-MDM Catalog 3.0. For moreinformation, see SAP Note 1177779(regardingSRM-MDM Catalog) [SAP SRM-MDMCatalog 3.0 Installation Guide]

/

6 Install SAP NetWeaver 7.0® Search andClassification (TREX) [SAP NetWeaver 7.0Installation Guide: Search and Classification(TREX)]

n Perform the installation steps to set upan RFC connection

n Automatic language recognition is notrequired. You can adopt the defaultsettings for document languages duringthe installation of SAP NetWeaver 7.0®TREX

n No Python extensions are required

7 Install SAP SRM Server for SAP SUS.[Installation Guide ‒ SAP SRM Server on<Platform>:<Database>]

You can install a separate SAP SRM Server forSUS or use the SAP SRM Server you installedin step 4 for that purpose.

8 Install SAP BI 7.01 plus SAP BI Content 7.04:

1. Install SAP Web AS ABAP 7.01, whichincludes SAP BI 7.01 and PI_BASIS 7.01.

2. Configure the database of your SAP WebAS for SAP BI as described in SAP Note567745.

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

For a minimal system landscape, you caninstall SAP BI on your SAP SRM Server.Install the SAP BI Business Content Add-Onon the SAP SRM Server as described in SAPNote 1172899.For more information, see the Master Guide— SAP NetWeaver 7.0.

The use of SAP BI is optional. See thedescription of this component in the SoftwareComponent Matrix [page 16] to decide whether itis required for your business scenario. Afterthe BI ABAP upgrade, you should install theJava parts of BI (BI-Java) to take advantage ofall new functionality. For more information,see Installation Guide ‒ SAP NetWeaver 7.01.

9 Install SAP NetWeaver 7.01 ‒ EnterprisePortal. [Master Guide ‒ SAP NetWeaver 7.01]

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

10 Import the following Business Packages intothe Enterprise Portal:n Business Package for SAP SRM 7.0n Business Package for Supplier

Collaboration 4.0

Download the Business Packages from theSAP Developer Network www.sdn.sap.com

Portal Content Portfolio

ConfigurationSee SAP Solution Manager content for Self-Service Procurement.

03/12/2010 PUBLIC 27/72







3 Business Scenarios of SAP SRM3.2 Plan-Driven Procurement

3.2 Plan-Driven Procurement


n Overview of Plan-Driven Procurement with Plant Maintenance

n Overview of Plan-Driven Procurement with Supplier Integrationn Technical System Landscapen Implementation sequence

3.2.1 Overview of Plan-Driven Procurement with PlantMaintenance

You can use this business scenario to process requirements that have been generated in systems otherthan SAP SRM. In a highly integrated procurement process, demand for products can come fromseveral different planning systems that reside outside of SAP SRM, such as material requirementsplanning (MRP) systems for production planning, automated production systems (APS) foradvanced, constraint-based planning, project systems for project planning, or plant maintenancesystems for maintenance and repair planning. Plan-Driven procurement is especially important forthe procurement of direct materials. Demand from production is transferred to SAP SRM using anopen XML interface. Within SAP SRM, a contract can be automatically assigned to the demand anda purchase order sent out.The Plan-Driven Procurement with Plant Maintenance business scenario comprises these processsteps:

1. Processing Purchase Requisitions in SAP ERP2. Searching for Sources of Supply3. Processing Purchase Orders in SAP SRM4. Receipt Confirmation without Warehouse Management5. Receipt Confirmation with Warehouse Management6. Processing Leasing Invoices in SAP SRM7. Verifying Logistics Invoices in Background8. Verifying Logistics Invoices Online9. Processing Evaluated Receipt Settlements (ERS) in SAP ERP10. Analyzing Plan-Driven Procurement

3.2.2 Overview of Plan-Driven Procurement with SupplierIntegration

You can use this business scenario to procure direct materials with SAP Materials Management (SAPMM) and, at the same time, to integrate your suppliers into this process. If necessary, you can connect

28/72 PUBLIC 03/12/2010


multiple supplier systems to your procurement system. This allows you, as a buyer, to collaboratewith your suppliers, using the web-based tool SAP SRM Supplier Self-Service, starting with thepurchase order via shipping notification to the invoice.The Plan-Driven Procurement with Supplier Integration business scenario comprises these processsteps:

1. Processing Purchase Requisitions in SAP ERP2. Processing Purchase Orders in SAP ERP3. Processing Delivery Schedules4. Processing Sales Orders in SRM-SUS5. Processing Shipping Notifications6. Receipt Confirmation without Warehouse Management7. Receipt Confirmation with Warehouse Management8. Processing Invoices in SAP SRM9. Verifying Logistics Invoices in Background10. Verifying Logistics Invoices Online11. Processing Evaluated Receipt Settlements (ERS) in SAP ERP12. Analyzing Plan-Driven Procurement13. Performing Order Collaboration Using Supplier Network


Note




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

03/12/2010 PUBLIC 29/72








Figure 3:





Note



30/72 PUBLIC 03/12/2010






Install SAP Process Integration. [MasterGuide ‒ SAP NetWeaver 7.01] Caution

SAP Process Integration requires a dedicatedSAP Web Application Server. This meansthat the running of applications in otherclients of the same SAP Web AS is notsupported.


SAP SRM Server 7.0n

SAP BI Content 7.0.4 (optional)

/

1

Download and install the latest SLDContent from SAP Service Marketplace at

service.sap.com/swdc DownloadSupport Packages and Patches Entry by ApplicationGroup Additional Components SAP MasterData for SLD .

/





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

Not required for customers with an SAP R/3Enterprise 47x200 back-end system. FromSAP R/3 Enterprise 47x200 onwards, theformer plug-in functions are delivered withthe SAP_APPL component.

4 Install SAP SRM 7.0[Installation Guide ‒ SAP SRM 7.0]

/


/

6 Install SAP SRM Server for SUS.[Installation Guide ‒ SAP SRM Server on<Platform>:<Database>


03/12/2010 PUBLIC 31/72




3 Business Scenarios of SAP SRM3.3 Service Procurement






The use of SAP BI is optional. See thedescription of this component in the SoftwareComponent Matrix [page 16] to decide whether itis required for your business scenario. Afterthe BI ABAP upgrade, you should install theJava parts of BI (BI-Java) to take advantage ofall new functionality. For more information,see Installation Guide ‒ SAP NetWeaver 7.01.



9 Import the following Business Package intothe Enterprise Portal:n Business Package for SAP SRM 7.0



ConfigurationSee SAP Solution Manager content for Plan-Driven Procurement.

3.3 Service Procurement


n Overview of Service Procurement (Classic)n Overview of Service Procurement External Staffingn Technical System Landscapen Implementation sequence

3.3.1 Overview of Service Procurement (Classic)

You can use this business scenario to cover the entire service procurement process using structuredservice requirements for external procurement. A purchase requisition is created in SAP MaterialsManagement (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 03/12/2010







1. Purchase Requisition with Service Directories2. Searching for Sources of Supply Centrally3. Processing RFx Events4. Evaluating RFx Responses5. Processing Follow-On Documents6. Processing Purchase Orders in SAP ERP7. Processing Sales Orders in SUS8. Entering Services in SAP RM9. Entering Services in SAP ERP10. Processing Invoices11. Verifying Logistics Invoices in Background12. Verifying Logistics Invoices Online13. Processing Evaluated Receipt Settlements (ERS) in SAP ERP14. 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 ExternalStaffing. 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 yoursuppliers by connecting a supplier system like supplier self-services (SUS) to your procurementsystem. Your service providers can then enter services performed and create invoices for theseservices. 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. Requesting External Staff2. Processing Shopping Carts3. Processing Purchase Orders in SAP SRM4. Processing Sales Orders in SUS5. Entering Services in SAP SRM6. Processing Invoices in SAP SRM7. Processing Evaluated Receipt Settlements (ERS) in SAP SRM8. Carrying Out Third-Party Rebilling9. Analyzing Service Procurement

03/12/2010 PUBLIC 33/72



Note




The following figure shows the underlying architecture of Service Procurement.

Figure 4:




This section lists the sequence of steps (installation, technical configuration, applicationconfiguration) required to implement the business scenario. Rows containing optional componentsare shaded. The scenario can function without these optional components; but they do provideadditional functions.

34/72 PUBLIC 03/12/2010











Installation

Note







SAP SRM Server 7.0n



/

1

Download and install the latest SLDContent from SAP Service Marketplace at

service.sap.com/swdc DownloadSupport Packages and Patches Entry by ApplicationGroup Additional Components SAP MasterData for SLD .

/






Not required for customers with an SAP R/3Enterprise 47x200 back-end system. FromSAP R/3 Enterprise 47x200 onwards, theformer plug-in functions are delivered withthe SAP_APPL component. Not required ifexclusively local PO handling is performed,or no back-end system is used.

03/12/2010 PUBLIC 35/72





4 Install SAP SRM Server 7.0 comprisingSAP Bidding Engine and SAP SupplierSelf-Services[Installation Guide ‒ SAP SRM Server 7.0]

/

5 Install SAP SRM-MDMCatalog 3.0. Formoreinformation, see SAP Note 1057316 . [SAPSRM-MDMCatalog 3.0 Installation Guide]

/


n Perform the installation steps to set upan RFC connection

n Automatic language recognition is notrequired. You can adopt the defaultsettings for document languages duringthe installation of SAP® NetWeaver 7.0TREX









The use of SAP BI is optional. See thedescription of this component in the SoftwareComponent Matrix [page 16] to decide whether itis required for your business scenario.After the BI ABAP upgrade, you shouldinstall the Java parts of BI (BI-Java) to takeadvantage of all new functionality.For more information, see the SAPNetWeaver 7.01 Installation Guide.



10 Import the following Business Packages intothe Enterprise Portal:n Business Package for SAP SRM 7.0n Business Package for Supplier

Collaboration 4.0



ConfigurationSee SAP Solution Manager content for Service Procurement.

36/72 PUBLIC 03/12/2010







3 Business Scenarios of SAP SRM3.4 Catalog Content Management

3.4 Catalog Content Management


n Overview

n Technical System Landscapen Implementation sequence

3.4.1 Overview

DescriptionYou can use this business scenario to import andmanage product content, make this content availablein an MDM data repository, and access it via the Web browser in your SAP Supplier RelationshipManagement (SAP SRM) procurement processes.The business processes run as follows:

1. Managing Content in SRM-MDM Catalog2. Searching in Catalog Data


Note

For information about the technical system landscape and about how to plan the business scenarioto meet your needs, see: http://service.sap.com/platforms Platform Availability Matrix

The following figure shows the underlying architecture of the SRM-MDMCatalog including existingconnections.

03/12/2010 PUBLIC 37/72




3 Business Scenarios of SAP SRM3.4 Catalog Content Management

Figure 5:





Note

n For latest Support Package and patch level requirements, see the SAP SRM-MDM Catalog3.0 Installation Guide



38/72 PUBLIC 03/12/2010




3 Business Scenarios of SAP SRM3.5 Analytics




1

After you install SAP Process Integration,import the integration objects for SAP SRMinto the SAP Process Integration. Import thePI content for the following components:n

SAP SRM Server 7.0

/

2 Install SAP SRM Server 7.0 comprising SAPBidding Engine[Installation Guide ‒ SAP SRM Server 7.0]

/

3 Install SAP SRM-MDM Catalog 3.0. Formore information, see SAP Note 1177779.

/

4 Install SAP NetWeaver 7.01 ‒ EnterprisePortal. [Master Guide ‒ SAP NetWeaver 7.01,part of the installation package]

The use of SAP NetWeaver Enterprise Portalis optional. It is required for the integrationof SAP SRM into a workset.

ConfigurationSee SAP Solution Manager Content for Catalog Content Management.

3.5 Analytics


n Overview of Spend Analysisn Overview of Supplier Evaluationn Technical System Landscapen Implementation sequence

3.5.1 Overview of Spend Analysis

You can use this business scenario to analyze the expenditure of your company, using data from a widerange of heterogeneous systems as well as from all relevant business units and areas. SAP SupplierRelationship Management (SAP SRM) uses the business intelligence features of SAP NetWeaver toaccess connected systems, and extract the information needed to gain insight into spending practices

03/12/2010 PUBLIC 39/72



across the entire corporate group. The reports cover spending for direct and indirect material, as wellas 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 otherdetailed information about the procurement

2. Harmonization of master data for reporting purposes, allowing for identification of duplicatesuppliers and assignment of product to standard classification schemas such as the United NationsStandard Products and Services Code (UNSPSC) and eCl@ss. The harmonization can be doneeither by using SAP NetWeaver Business Intelligence (SAP NetWeaver BI) Local Master DataAlignment (for limited data volumes), or by integration of SAP NetWeaver BI with the SAP MasterData Management (SAP MDM) application.

With these features, SAP SRM provides you with a clear view of procurement costs and supply-basedata by highlighting consolidated spend volume, supplier redundancies, and demand aggregationopportunities.The Spend Analysis business scenario comprises these process steps:

1. Consolidating Master Data Using BI Master Data Alignment2. Consolidating Master Data Using SAP MDM3. 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. Tomeet your specific requirements, you can configure individual surveys and questionnaires, select thecriteria that you want to evaluate, and stipulate when the evaluation is to take place. After the datahas been transferred to SAP NetWeaver Business Intelligence (SAP NetWeaver BI), several reports areavailable 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 incomingresponses 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-dayactivities on the basis of operational documents. You can also use this scenario with the supplier list toimprove 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 03/12/2010



Note




The following figure shows the underlying architecture of Analytics.

Figure 6:




This section lists the sequence of steps (installation, technical configuration, applicationconfiguration) required to implement the business scenario. Rows containing optional componentsare shaded. The scenario can function without these optional components; but they do provideadditional functions.

03/12/2010 PUBLIC 41/72











Installation

Note

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



Install/Integrate SAP ERP (SAP R/3 4.7 orhigher recommended)


1

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

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

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

Not required for customers with an SAP R/3Enterprise 47x200 back-end system. FromSAP R/3 Enterprise 47x200 onwards, theformer plug-in functionalities are deliveredwith the SAP_APPL component. Otherwisethe installation of the SAP R/3 Plug-In isrequired if you installed an SAP back-endsystem in the previous step.

2 Install SAP SRM Server 7.0 comprising SAPBidding Engine and Supplier Self-Services[Installation Guide ‒ SAP SRM Server 7.0]

/






After the BI ABAP upgrade, you shouldinstall the Java parts of BI (BI-Java) to takeadvantage of all new functionality. For moreinformation, see Installation Guide ‒ SAPNetWeaver 7.01.

42/72 PUBLIC 03/12/2010







3 Business Scenarios of SAP SRM3.6 Operational Contract Management



5 Import the following Business Package intothe Enterprise Portal:Business Package for SAP SRM 7.0



ConfigurationSee SAP Solution Manager content for Analytics.

3.6 Operational Contract Management


n Overview

n Technical System Landscapen 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 groupinglogic, 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 SAPERP for a source of supply determination, and a specific type of contract or scheduling agreement canbe created there. While determining a source of supply, you can access central contracts directly. Theprice is determined in SAP SRM before the SAP ERP purchase order is sent to the supplier. You cancreate and change central contracts and renegotiate existing contracts directly with a supplier, orthrough the creation of an RFx. You can automatically assign a contract as a source of supply, or itcan be listed as one of numerous potential source of supply contracts. A strategic purchaser can createa contract whenever they anticipate a long-term relationship with a supplier. Contract managementenables purchasers from various parts of the company at different locations to take advantage of theterms of globally-negotiated contracts for specific product categories. You can provide users withspecific levels of authorization to contracts, and you can categorize documents as confidential.You can distribute central contracts to release-authorized purchasing organizations, and theseorganizations can then use them as source of supply in the appropriate SAP ERP system. Hierarchiescan be used to organize, structure, display, and search for contracts. If you use SAPNetWeaver BusinessIntelligence (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.

03/12/2010 PUBLIC 43/72




The Operational Contract Management business scenario comprises these process steps:

1. Define Usage of Central Contracts2. Developing Contracts3. Processing Contracts and Sourcing Rules in SAP ERP4. Negotiating Contracts5. Process Delivery Schedules6. Searching for Sources of Supply Centrally7. Monitoring Contracts


Note




The following figure shows the underlying architecture of Operational Contract Management.

Figure 7:


44/72 PUBLIC 03/12/2010











n IPC 7.0 is part of the SAP WebASn 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 Portall LAC WPS can be deployed on the Portal

n The Business Packages shown above are: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 installedon 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.



Note



03/12/2010 PUBLIC 45/72



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-basedmessaging or for connecting non-SAP planningor execution systems.

CautionSAP Process Integration requires a dedicated SAPWeb Application Server. This means that therunning of applications in other clients of thesame SAP Web AS is not supported.

If you installed SAP Process Integration, importthe integration objects for SAP SRM into the SAPProcess Integration. Import the PI content forthe following components:n

SAP SRM Server 7.0n



/

1

Download and install the latest SLDContent from SAP Service Marketplace atservice.sap.com/swdc Download Support

Packages and Patches Entry by Application GroupAdditional Components SAP Master Data for SLD .

/

2 Install/Integrate SAP ERP (SAP R/3 4.7 or higherrecommended)

SAP ERP is not part of this installation and arenot contained in the installation package. Aseparate SAP ERP installation package is required.

3 Install SAP R/3 Plug-In (2004.1 or higher if one isavailable):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-in2004.1).


Not required for customers with an SAP R/3Enterprise 47x200 back-end system. FromSAPR/3Enterprise 47x200 onwards, the former plug-infunctions are delivered with the SAP_APPLcomponent. Not required if exclusively local POhandling is performed or no back-end system isused.

4 Install SAP SRM Server 7.0[Installation Guide ‒ SAP SRM Server 7.0]

/

5 Install SRM-MDM Catalog 3.0. For moreinformation, see SAP Note 1177779. [SAPSRM-MDM Catalog 3.0 Installation Guide]

/

46/72 PUBLIC 03/12/2010




3 Business Scenarios of SAP SRM3.7 Strategic Sourcing


n Perform the installation steps to set up anRFC connection

n Automatic language recognition is notrequired. You can adopt the defaultsettings for document languages during theinstallation of SAP NetWeaver 7.0® TREX



You can install a separate SAP SRM Server forSUS or use the SAP SRM Server you installed instep 4 for that purpose.


1. Install SAP Web AS ABAP 7.01, which includesSAP BI 7.01 and PI_BASIS 7.01.

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


For a minimal system landscape, you can installSAP BI on your SAP SRM Server. Install the SAPBI Business Content Add-On on the SAP SRMServer 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 descriptionof this component in the Software Component Matrix[page 16] to decide whether it is required for yourbusiness scenario. After the BI ABAP upgrade,you should install the Java parts of BI (BI-Java)to take advantage of all new functionality. Formore information, see Installation Guide ‒ SAPNetWeaver 7.01.

9 Install SAP NetWeaver 7.01 ‒ Enterprise Portal.[Master Guide ‒ SAP NetWeaver 7.01]

The use of SAP NetWeaver Enterprise Portal ismandatory. It is required for the integration ofSAP SRM into a workset.

10 Import the following Business Package into theEnterprise Portal:n Business Package for SAP SRM 7.0

Download the Business Packages from the SAPDeveloper Network www.sdn.sap.com PortalContent Portfolio

ConfigurationSee SAP Solution Manager content for Operational Contract Management.

3.7 Strategic Sourcing


n Overview of Strategic Sourcing with RFxn Overview of Strategic Sourcing with Live Auctionn Technical System Landscapen Implementation sequence

03/12/2010 PUBLIC 47/72






3.7.1 Overview of Strategic Sourcing with RFx

You can use this business scenario to source goods using RFx (request for information, requestfor proposal, and/or request for quotation). You can use this business scenario with or withoutintegration 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 integratedocument storage functionality ‒ maintained in cFolders ‒ in the RFx. After you have received bidsfrom 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. Processing Shopping Carts2. Processing Purchase Requisitions in SAP ERP3. Searching for Sources of Supply Centrally4. Negotiating Contracts5. Processing Bidding Events6. Processing Collaborative Bidding Events Using cFolders7. Evaluating Bids8. Processing Follow-On Documents9. 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, forexample, define bidding rules. Bidders can submit bids in real time in a separate live auctionapplication. 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 todetermine the best source of supply. After you have received bids from suppliers, you can create apurchase order or contract (local or global outline agreement) directly from the sourcing cockpit orin SAP Bidding Engine as a result of the auction.The Strategic Sourcing with Live Auction business scenario comprises these process steps:

1. Processing Shopping Carts2. Processing Purchase Requisitions in SAP ERP3. Searching for Sources of Supply Centrally4. Conducting Live Auctions5. Evaluating Bids6. Processing Follow-On Documents7. Analyzing Sourcing with Live Auction

48/72 PUBLIC 03/12/2010



Note




The following figure shows the underlying architecture of Strategic Sourcing.

Figure 8:





03/12/2010 PUBLIC 49/72











Note




Install SAP Process Integration. [Master Guide‒ SAP NetWeaver 7.01] Caution

SAP Process Integration requires a dedicatedSAP Web Application Server. This means thatthe running of applications in other clients ofthe same SAP Web AS is not supported.

If you installed SAP Process Integration, importthe integration objects for SAP SRM into theSAP Process Integration. Import the PI contentfor the following components:n

SAP SRM Server 7.0n

SAP SRM-MDM Catalog 3.0

/

1

Download and install the latest SLDContent from SAP Service Marketplace atservice.sap.com/swdc Download Support

Packages and Patches Entry by Application GroupAdditional Components SAP Master Data for SLD .

/

2 Install/Integrate SAP ERP (SAP R/3 4.7 or higherrecommended)


3 Install SAP R/3 Plug-In (2004.1 or higher if one isavailable):n For the installation, see SAP Notes 704564



Not required for customers with an SAP R/3Enterprise 47x200 back-end system. FromSAP R/3 Enterprise 47x200 onwards, theformer plug-in functions are delivered withthe SAP_APPL component. Otherwise, theinstallation of the SAP R/3 Plug-In is requiredif you installed an SAP back-end system in theprevious step.

4 Install SAP SRM Server 7.0 comprising SAPBidding Engine and SAP Supplier Self-Services[Installation Guide ‒ SAP SRM Server 7.0]

/

5 Install SAP SRM-MDM Catalog 3.0. For moreinformation, see SAP Note 1057316 . [SAPSRM-MDM Catalog 3.0 Installation Guide]

/

50/72 PUBLIC 03/12/2010







n Perform the installation steps to set up anRFC connection

n Automatic language recognition is notrequired. You can adopt the defaultsettings for document languages during theinstallation of SAP NetWeaver 7.0® TREX


7 Install Live Auction Cockpit Web PresentationServer (LACWPS) 7.0. [ComponentInstallation Guide ‒ SAP SupplierRelationship Management 7.0 ABAP +Java on <Platform>:<Database>]

The use of Live Auction Web PresentationServer is optional.You can install LACWPS either on a standaloneJ2EE Engine or on a J2EE Engine installed as anAdd-In on the central instance.



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


For a minimal system landscape, you can installSAP BI on your SAP SRM Server. Install the SAPBI Business Content Add-On on the SAP SRMServer 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 descriptionof this component in the Software ComponentMatrix [page 16] to decide whether it is requiredfor your business scenario.After the BI ABAP upgrade, you should installthe Java parts of BI (BI-Java) to take advantageof all new functionality.For more information, see Installation Guide‒ SAP NetWeaver 7.01.

9 Install SAP NetWeaver 7.01 ‒ Enterprise Portal.[Master Guide ‒ SAP NetWeaver 7.01]

The use of SAP NetWeaver Enterprise Portal ismandatory. It is required for the integration ofSAP SRM into a workset.

10 Import the following Business Packages into theEnterprise Portal:n Business Package for SAP SRM 7.0n Business Package for Supplier Collaboration

2.0

Download the Business Packages from the SAPDeveloper Network www.sdn.sap.com


ConfigurationSee SAP Solution Manager content for Strategic Sourcing.

03/12/2010 PUBLIC 51/72





4 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). TheseSAP PPS scenarios require a special license agreement.

Caution

To use SAP Procurement for Public Sector, SAP SRM must be deployed as an extended classicscenario. 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 connectedto the SAP SRM system. Multi back-end deployment is not supported for SAP Procurement forPublic Sector.

Caution

You must install SAP SRM 7.0 SP01 before you activate the SAP PPS business functions. Activating thebusiness functions is irreversible; once they have been activated, you cannot deactivate them. Beaware 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 moreinformation, 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

03/12/2010 PUBLIC 53/72

4 Business Scenarios of SAP SRM-PPS4.1 Technical System Landscape

SRM 7.0 only.

4.1 Technical System Landscape

Figure 9:


Figure 10:

Description:

n IPC 7.0 is part of SAP WebASn 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 Portall 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)l SRMMDMCAT1000_0.ZIP (XI Content for SRM-MDM Catalog)

54/72 PUBLIC 03/12/2010




4 Business Scenarios of SAP SRM-PPS4.2 Public Sourcing and Tendering

l SRMMDMCAT1000_1.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 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. Youcan create legally-compliant documents within a secure infrastructure that integrates SAP RecordsManagement and procurement processes to fulfill audit requirements.The Public Sourcing and Tendering business scenario comprises the following business processes:

n Prequalification of RFx Respondentsn Public RFx Publishingn Tender Fee Processingn Earnest Money Deposit Handlingn Two-Envelope RFx Responsen Multi-Party Verification at RFx Response Openingn RFx Response Evaluationn Electronic Contract File Creation

n 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 orpurchase order with a supplier. This negotiation may be based on the outcome of the tenderingprocess as described in the Public Sourcing and Tendering business scenario. Once pricingarrangements, clauses, payment, terms, and delivery conditions have been agreed upon, the contractor purchase order enters an approval workflow. Upon approval, the contract or purchase order iscentrally created in SAP Supplier Relationship Management (SAP SRM). Operational purchasers cantake advantage of the conditions negotiated. When users seek a specific product or service from acontract or contract-type line item in a mixed-use purchase order, a purchase order is created, whichis then sent to the supplier. The supplier ships the required goods or provides the service to the

03/12/2010 PUBLIC 55/72

4 Business Scenarios of SAP SRM-PPS4.4 Operational Procurement

designated recipient. The user then completes a goods receipt or service entry on the basis of whichthe 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 allprocurement documents created. After award, any contract or purchase order modifications, as wellas their supporting documentation, are also automatically added to the electronic contract file. Thefile continues to capture contractual information through closeout.The Public Sourcing and Tendering business scenario comprises the following business processes:

n Complex Contract Creation (SAP Document Builder)n Guaranteed Minimum

n Closeout Execution

n Contract Tracking and Monitoringn Electronic Contract File Creation

n Post-Award Procedure

n Options Definitionn 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 forprocurement (for example, demands for spare parts coming from plant maintenance, demands forraw 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 arepresented to the purchaser in work lists that support him in converting the requisitions into contractsor purchase orders. The purchaser can check the source of supply and the price and conditions thathave 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 Complex Sourcingn Exercise Optionsn Electronic Contract File Creation

n Budget Integrationn Order Trackingn Acceptance at Origin for PPSn Acknowledgement and Delivery

56/72 PUBLIC 03/12/2010

4 Business Scenarios of SAP SRM-PPS4.5 Procurement Services

n Invoice Verification

n Selective Release

n Workload Prioritization

n 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 (AutomatedSourcing)

You can use this business scenario to satisfy requirements from external customers. In this scenariothe purchasing agency satisfies the requirements either by delivery from stock, by creation of a releaseorder against an existing contract, or by creation of a purchase order.The Procurement Services (Automated Sourcing) business scenario comprises the following businessprocesses:

n Processing of External Requirements (Automated Sourcing)n Third-Party Processingn 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 scenariothe purchasing agency satisfies the requirements either by delivery from stock, by creation of a releaseorder against an existing contract, or by creation of a purchase order.The Procurement Services (Manual Sourcing) business scenario comprises the following businessprocesses:

n Processing of External Requirements (Manual Sourcing)n Third Party Processingn Inventory Management and Delivery from Stock

03/12/2010 PUBLIC 57/72

5 SAP Solution Manager


SAP provides the SAP SolutionManager as the platform for efficiently supporting the implementationand operation of your SAP solution. SAP Solution Manager significantly accelerates theimplementation process, and helps you achieve your business goals. It contains predefinedimplementation content (Customizing activities and transactions, as well as documentation and SAPNotes) to help you configure your SAP SRM solution. In addition, SAP delivers support services basedon 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 Server7.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, seethe installation or upgrade guide for SAP SRM Server 7.0.

In SAP SRM 7.0, the SAP Solution Manager contains standard implementation content for thebusiness scenarios, covering all key capabilities of the SAP SRM Solution Map. This enables a fastimplementation 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 Documentation of core business processes that are changed or implemented during Ramp-Upn Plan your solution landscapen Connection of existing systems and activation of SAP EarlyWatchAlertn Setup Solution Manager Diagnostics for root cause analysis of Java componentsn Handover of processes and systems to support organization after Go Liven 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 SAPSolution Manager.

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

03/12/2010 PUBLIC 59/72



n System infrastructure, scenarios, installation and configuration of SAP SolutionManager: Master Guide- SAP Solution Manager available on SAP Service Marketplace athttp://service.sap.com/instguides SAP Components SAP Solution Manager .

n Benefits and usage scenarios: SAP Solution Manager — Learning Maps availableon SAP Service Marketplace at http://service.sap.com/rkt-solman orhttp://service.sap.com/solutionmanager .

n Additional information: SAP Service Marketplace athttp://service.sap.com/solutionmanager and in the Master

guide for SAP enhancement package 1 for SAP NetWeaver 7.0 available athttp://service.sap.com/instguides

The following information summarizes installation considerations:

n Each SAP SRM (or SAP NetWeaver) system landscape must be assigned to an installation of theSAP Solution Manager. In the event of a support-relevant incident within your SAP systemlandscape, SAP Support requires remote access to the SAP Solution Manager that hosts theaffected system landscape.

n If you already have an SAP Solution Manager deployment in place, you can also use it to managethe solution you build with SAP NetWeaver and SAP SRM as well. In this case, we recommendupdating 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, eachinstallation 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 SolutionManager, especially if you are using time-critical functions like Support Desk. If you also developyour own content, a three-system landscape with development, test, and production environmentis recommended.

60/72 PUBLIC 03/12/2010




http://service.sap.com/rkt-solman












6 References

6 References

Caution

Make sure you have the latest documentation version by checking SAP Service Marketplace athttp://service.sap.com/instguides 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<Platform>:<Database>

SAP Service Marketplace athttp://service.sap.com/instguides

SAP Business Suite SAP SRM SAP SRM 7.0

Master Guide— SAP NetWeaver 7.0 SAP Service Marketplace athttp://service.sap.com/instguides

SAP NetWeaver

Upgrade Master Guide— SAP SRM 7.0 SAP Service Marketplace athttp://service.sap.com/instguides


Installation Guide SAP NetWeaver 7.0 Search andClassification (TREX)

SAP Service Marketplace athttp://service.sap.com/instguides

SAP NetWeaver

<Business Scenario> See SAP Solution Manager for SAP SRM

Configuration documentation for SAP SRM 7.0 foreach business scenario

All configuration documentation for SAP SRM 7.0 isavailable in SAP Solution Manager.

SAP SRM-MDM Catalog 3.0 Installation Guide SAP Service Marketplace athttp://service.sap.com/instguides


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

03/12/2010 PUBLIC 61/72
















6 References

SAP Note Number Title

1177779 SRM-MDM Catalog 3.0 Installation

567745 Composite note BW 3.x performance: DB-specificsetting

62/72 PUBLIC 03/12/2010



7 Media List

7 Media List

For information on the SAP SRM 7.0 media list, go to http://service.sap.com/instguides

Installation and Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM Server 7.0

03/12/2010 PUBLIC 63/72




A Reference

A Reference

A.1 The Main SAP Documentation Types

The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software.

Figure 11: Documentation Types in the Software Life Cycle

Cross-Phase Documentation

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

n Target group:l Relevant for all target groups

n Current version:l On SAP Help Portal at http://help.sap.com Additional Information Glossary (direct

access) or Terminology (as terminology CD)l In the SAP system in transaction STERM

03/12/2010 PUBLIC 65/72

http://help.sap.com

A ReferenceA.1 The Main SAP Documentation Types

SAP Library is a collection of documentation for SAP software covering functions and processes.

n Target group:l Consultants

l System administratorsl 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 forraising security levels. A collective security guide is available for SAP NetWeaver. This documentcontains general guidelines and suggestions. SAP applications have a security guide of their own.

n Target group:l System administratorsl Technology consultantsl Solution consultants

n Current version:l On SAP Service Marketplace at http://service.sap.com/securityguide

Implementation

Themaster guide is the starting point for implementing an SAP solution. It lists the requiredinstallable units for each business or IT scenario. It provides scenario-specific descriptions ofpreparation, execution, and follow-up of an implementation. It also provides references to otherdocuments, such as installation guides, the technical infrastructure guide and SAP Notes.

n Target group:l Technology consultantsl 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, takinginto account the combinations of operating systems and databases. It does not describe anybusiness-related configuration.

n Target group:l Technology consultantsl Project teams for implementations


Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform. One of its main functions is the configuration of business and IT scenarios. It containsCustomizing activities, transactions, and so on, as well as documentation.

66/72 PUBLIC 03/12/2010

http://help.sap.com

http://service.sap.com/securityguide










n Target group:l Technology consultantsl Solution consultants

l Project teams for implementationsn Current version: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 SolutionManager, which refers to the relevant Customizing activities in the individual SAP systems, is used.)

n Target group:l Solution consultants

l Project teams for implementations or upgradesn 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 SAPNetWeaver, and precedes the solution operations guide. The manual refers users to the tools anddocumentation that are needed to carry out various tasks, such as monitoring, backup/restore,master data maintenance, transports, and tests.

n Target group:l System administrators


The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed. It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks.

n Target group:l System administratorsl Technology consultantsl Solution consultants


Upgrade

The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of anupgrade. It also refers to other documents, such as the upgrade guides and SAP Notes.

03/12/2010 PUBLIC 67/72








n Target group:l Technology consultantsl Project teams for upgrades


The upgrade guide describes the technical upgrade of an installable unit, taking into accountthe combinations of operating systems and databases. It does not describe any business-relatedconfiguration.

n Target group:l Technology consultantsl Project teams for upgrades


Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release. Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG).

n Target group:l Consultants

l Project teams for upgradesn Current version:l On SAP Service Marketplace at http://service.sap.com/releasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)

68/72 PUBLIC 03/12/2010







http://service.sap.com/releasenotes



Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

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 thedocumentation

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 tospecific 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, messagesn Source code or syntax quoted directly from a programn 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 languagewhen they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

03/12/2010 PUBLIC 69/72

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2010 SAP AG. All rights reserved.

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof 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 othersoftware 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 SystemsIncorporated 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 registeredtrademarks 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 implementedby Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves informational purposes only. Nationalproduct 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 notbe liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2from Michael Kay (http://saxon.sf.net/), XSLT version 1.

70/72 PUBLIC 03/12/2010

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable andsevere 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 SAP’s Support Services and may not be modified oraltered in any way.

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

03/12/2010 PUBLIC 71/72




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

© Copyright 2010 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 bechanged without prior notice.

Srm 7.0master Guide

Documents

Transcript of Srm 7.0master Guide