SAP Solution Manager
Template Description
SAP Best Practices for Supplier Relationship
Management_V2
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
SAP Solution Manager Template Description
Copyright
© 2014 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate
company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting
an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated
companies’ strategy and possible future developments, products, and/or platform directions and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any
time for any reason without notice. The information in this document is not a commitment, promise, or
legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject
to various risks and uncertainties that could cause actual results to differ materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making purchasing decisions.
© SAP SE
Public
Page 2 of 10
SAP Best Practices
SAP Solution Manager Template Description
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
External Process
Business Process Alternative/Decision Choice
Typographic Conventions
Type Style
Description
Example text
Words or characters that appear on the screen. These include
field names, screen titles, pushbuttons as well as menu names,
paths and options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and
tables.
EXAMPLE TEXT
Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual
key words of a programming language, when surrounded by body
text, for example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their
paths, messages, source code, names of variables and
parameters as well as names of installation, upgrade and
database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or
the ENTER key.
Example text
Exact user entry. These are words or characters that you enter in
the system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace
these words and characters with appropriate entries.
© SAP SE
Public
Page 3 of 10
SAP Best Practices
SAP Solution Manager Template Description
SAP Supplier Relationship Management RapidDeployment Solution_V2
Technical Data
Technical Name of
Template
RDS_SRM_SRM703V2
Available as of
SAP Solution Manager
Content Add-On Release
ST-RDS 100 (latest support package)
Industry
No restriction
Business Variant
No restriction
Line of Business
LOB Procurement
Country or Region
No restriction
Product Releases
SAP SRM 7.0 EhP3 SP0004
SAP ERP 6.0 EhP7 SP0005
Prerequisites
You have set up your system landscape according to the Quick Guide, which you can find
attached to the respective SAP Note.
Implementation option: Multiple Backend (see chapter Features below): SAP Note 2049047
http://service.sap.com/sap/support/notes/2049047
Implementation option: SRM@ERP (see chapter Features below): SAP Note 2049080
http://service.sap.com/sap/support/notes/2049080
Implementation option: SAP Best Practices for Supplier Relationship Management (see
chapter Features below): SAP Note 2049112
http://service.sap.com/sap/support/notes/2049112
Features
With this SAP Solution Manager template, you can perform the implementation of either SAP
Supplier Relationship Management rapid-deployment solution V2 or SAP Best Practices for
Supplier Relationship Management solution V2.
SRM Business Processes in this RDS
The essential business processes supported by this RDS are:

Self-service procurement

Operational sourcing
 Central contract management
For each of them several implementation and deployment options can be chosen.
Self-Service Procurement
Self-service procurement enables employees to order goods or services using a browserbased employee self-service. Employees can use an internal or external online catalog to
search for items and to create a shopping cart. Internal approval workflows will be delivered
and can be adjusted according to your internal requirements and organizational setup.
Approved purchase requests get posted automatically and purchase orders are submitted to
the supplier. The process also includes the confirmation of goods receipts and the creation of
invoices as a self-service for the employee. Self-service procurement is particularly useful for
© SAP SE
Public
Page 4 of 10
SAP Best Practices
SAP Solution Manager Template Description
employees who only occasionally work in the system in order to request internal goods and
services.
Operational Sourcing
One of the main tasks of a purchaser is to bundle unsourced items, from purchase requests
and trigger sourcing events like a Request for Quotation (RFQ). Operational sourcing enables
a purchaser to consolidate and submit unsourced items to single or multiple bidders. After
receiving bid responses and awarding a bidder, a purchase order will be created to finally
conclude the process. Operational sourcing is particularly useful for employees or managers
who work in the system on a regular basis in order to carry out bidding events and
negotiations with supplier or bidders.
Central Contract Management
Central contract management enables the integration of existing procurement processes with
central contract management capabilities, enhancing the procure-to-pay process by
operational contract creation functionalities as well as contract distribution, monitoring, and
consumption. This preconfigured process offers you full integration of contract management
from central contract creation in your SAP Supplier Relationship Management (SAP SRM)
installation to operational procurement in single or multiple SAP ERP systems.
Implementation Options - Overview
The business processes of this solution can be deployed choosing between several
implementation options:
 Multiple Backend with three further deployment options
SRM@ERP (SAP Best Practices for Supplier Relationship Management)
Multiple Backend:
Name of solution package to be selected:
SAP Supplier Relationship Management (Multiple Backend) rapid-deployment solution_V2
One separate SAP SRM system is connected to one or several SAP ERP systems. Typically
this is the option of choice for globally acting enterprises with multiple ERP back-ends using
several procurement (MM) installations and a central high-capacity SRM installation. This
deployment needs a separate SRM server installation which can be connected to all existing
ERP (MM) systems.
Within multiple backend, there are three more deployment options for tailoring deployment to
your individual needs, depending on the business processes you select:

Classic

Extended classic
 Decoupled bidding
See the Details chapter below for more details of these three options.
SRM@ERP / SAP Best Practices for SRM:
Name of solution package to be selected:
SAP Supplier Relationship Management (SRM@ERP) rapid-deployment solution_V2 or SAP
Best Practices for Supplier Relationship Management_V2
One SRM client is available with one SAP ERP system as carrier. The deployment targets
small or medium enterprises with only one ERP system. With this solution and this option the
SRM functionality can be used with lowest TCI and TCO (BI, PI and Portal are optional).
Implementation Options – Details for the SRM Business Processes
© SAP SE
Public
Page 5 of 10
SAP Best Practices
SAP Solution Manager Template Description
Self-Service Procurement
This process is available with these deployment options:
Self-Service Procurement (Classic) in Multiple Backend deployment
In the classic scenario there is a strong integration between SRM and ERP. The main
procurement process takes place in the back-end ERP system(s).
Self-Service Procurement (Extended Classic) in Multiple Backend deployment
In the extended classic scenario the leading documents are in the SRM systems and will be
replicated to the back-end system where they cannot be changed. Goods receipts and
invoices can be pre-entered in the SAP SRM system, or entered directly in the back-end
system.
Self-Service Procurement - SRM@ERP and SAP Best Practices for SRM
One SRM client is available with one SAP ERP system as carrier.
Self-Service Procurement UI5
The self-service procurement UI5 enables you to create shopping carts from catalogs in an
easy and intuitive way, with little or no training. The internet-like look-and-feel, and the
dynamic web page features, which you know from online shopping and internet search
experiences, have been incorporated into your corporate buying experience. You can search
across internal and external catalogs to quickly find the products and services you need to
order. UI5 shopping cart is particularly useful for employees who only occasionally work in the
system in order to request internal goods and services.
This process is available in the Multiple Backend implementation option.
Operational Sourcing
This process is available with these deployment options:
Operational Sourcing (Classic) in Multiple Backend deployment
In the classic scenario there is a strong integration between SRM and ERP. The main
procurement process takes place in the back-end ERP systems.
Operational Sourcing (Extended Classic) in Multiple Backend deployment
In the extended classic scenario the leading documents are in the SRM systems and will be
replicated to the back-end system where they cannot be changed. Goods receipts and
invoices can be pre-entered in the SAP SRM system, or entered directly in the back-end
system.
Operational Sourcing - Bid Decoupling in Multiple Backend deployment
Bid decoupling can be used for both classic and extended classic scenarios for multiple
backend deployment. Bid decoupling enhances the security of the system, as the bidders
provide responses outside of the firewall.
Operational Sourcing - SRM@ERP and SAP Best Practices for SRM
One SRM client is available one a SAP ERP system as carrier.
Central Contract Management
This process is available in the Multiple Backend implementation option.
Please study the table below for the dependencies between these options.
The matrix shows which business processes are integrated and can therefore be combined:
© SAP SE
Public
Page 6 of 10
SAP Best Practices
SAP Solution Manager Template Description
Business
Process
Business
Scenario
Implementation
Option
Predecessor
Solution Package
Name
Self Service
Procurement classic
Supplier
Relationship
Management
Multiple backend
deployment
None
SAP Supplier
Relationship
Management
(Multiple Backend)
rapid-deployment
solution_V2
Self Service
Procurement extended classic
Supplier
Relationship
Management
Multiple backend
deployment
None
SAP Supplier
Relationship
Management
(Multiple Backend)
rapid-deployment
solution_V2
Self Service
Procurement
UI5
Supplier
Relationship
Management
Multiple backend
deployment
Self Service
Procurement
– classic or
extended
classic
SAP Supplier
Relationship
Management
(Multiple Backend)
rapid-deployment
solution_V2
Operational
Sourcing classic
Supplier
Relationship
Management
Multiple backend
deployment
Self Service
Procurement
– classic (1)
SAP Supplier
Relationship
Management
(Multiple Backend)
rapid-deployment
solution_V2
Operational
Sourcing extended classic
Supplier
Relationship
Management
Multiple backend
deployment
Self Service
Procurement
- extended
classic (1)
SAP Supplier
Relationship
Management
(Multiple Backend)
rapid-deployment
solution_V2
Operational
Sourcing –
Decoupled
Bidding
Supplier
Relationship
Management
Multiple backend
deployment
Self Service
Procurement
– classic or
extended
classic (1)
SAP Supplier
Relationship
Management
(Multiple Backend)
rapid-deployment
solution_V2
Central Contract
Management
Supplier
Relationship
Management
Multiple backend
deployment
None
SAP Supplier
Relationship
Management
(Multiple Backend)
rapid-deployment
solution_V2
Self Service
Procurement SRM@ ERP
and SAP Best
Practices for
SRM (2)
Supplier
Relationship
Management
SRM@ERP and
SAP Best
Practices for SRM
None
SAP Supplier
Relationship
Management
(SRM@ERP) rapiddeployment
solution_V2 and
SAP Best Practices
for Supplier
© SAP SE
Public
Page 7 of 10
SAP Best Practices
SAP Solution Manager Template Description
Relationship
Management_V2
Operational
Sourcing SRM@ERP (2)
and SAP Best
Practices for
SRM
Supplier
Relationship
Management
SRM@ERP and
SAP Best
Practices for SRM
Self Service
Procurement
- SRM@ERP
(1)
SAP Supplier
Relationship
Management
(SRM@ERP) rapiddeployment
solution_V2 and
SAP Best Practices
for Supplier
Relationship
Management_V2
Notes
(1) ERP procurement processes such as “Procurement without QM” and others can
also be used as the starting point for Operational Sourcing.
(2) The processes based on the SRM@ERP deployment cannot by combined with
any process from the multiple backend deployment.
Creating the SAP Solution Manager Project and
Selecting the Template
You have to create an implementation project to organize your work in SAP Solution Manager
(SOLAR_PROJECT_ADMIN).
To select the rapid-deployment solution or best practices solution within the implementation
project, carry out the following steps in transaction SOLAR_PROJECT_ADMIN in the SAP
Solution Manager system.
1. Go to the Scope tab.
2. Select the rapid-deployment solution or best practices solution:

If the system uses SAP Solution Manager 7.0 (ST 400) or SAP Solution Manager 7.1
(ST 710) < SP05:
a. Select the Template Selection sub-tab by clicking the hyperlink for further
information.
a. Search for the template RDS_SRM_SRM_703V2 with template name= SAP
SRM rapid-deployment solution_V2 or BP_SRM_SRM703V2 with template
name = SAP Best Practices for Supplier Relationship Management.

If the system uses SAP Solution Manager 7.1 (ST 710) (at least SP05):
a. Select the Solution Package sub-tab by clicking the hyperlink for further
information.
b. Search for the appropriate solution package as named in the Features
chapter above.

Ensure that SAP Note 1687765 (Robomate) is implemented in SAP Solution
Manager to be able to see the Solution Package sub-tab. This is a mandatory
step to be carried out in the SAP Solution Manager 7.1 (ST 710) SP05 upgrade.
3. Save your project.
© SAP SE
Public
Page 8 of 10
SAP Best Practices
SAP Solution Manager Template Description
4. A dialog box for the mapping of the Logical Components is displayed. Adjust the chosen
logical component via F4 help if needed. For more information, see the Quick Guide
section Preparation of Logical Components Used in Solution Manager Implementation
Project.

The dialog box is only displayed if technical objects have been assigned to the
project, which are managed by logical ccomponents. If the project only has
documentation assignments, the dialog box is not displayed.
Blueprinting and Implementing the Business Content
In general, there are several deployment options depending on the solution package. If you
want to implement several solution packages at a time you may have a mixture of deployment
options:

SAP Solution Manager only:
Activation content for SAP Best Practices solution builder is not provided or using
SAP Best Practices solution builder in the development system is not possible.
SAP Solution Manager content is provided for each solution package.

Combined use of SAP Solution Manager and SAP Best Practices solution builder:
Use SAP Best Practices solution builder to accelerate the configuration during the
complete implementation which is controlled by SAP Solution Manager.

For more information, see the Quick Guide for the solution package attached to
SAP Notes:
For implementation option: Multiple Backend (see chapter Features below): SAP
Note 2049047
http://service.sap.com/sap/support/notes/2049047
For implementation option: SRM@ERP (see chapter Features below): SAP Note
2049080
http://service.sap.com/sap/support/notes/2049080
For implementation option: SAP Best Practices for Supplier Relationship
Management (see chapter Features below): SAP Note 2049112
http://service.sap.com/sap/support/notes/2049112
When you have completed the pre-requisites according to the Pre-Delivery Requirements and
Checklist document (available in the Step-by-Step Guide, Start  Prepare Project  PreDelivery Requirements and Checklist), the project team can start with the installation and
configuration activities of the solution package in SAP Solution Manager.
1. Conduct blueprinting (Transaction SOLAR01)

Scope the business processes of your solution package
 Activate business functions assigned to the solution package
2. Conduct implementation (Transaction SOLAR02)
Configure your solution package. To avoid redundant configuration see the Prerequisite
Matrix.
© SAP SE
Public
Page 9 of 10
SAP Best Practices
SAP Solution Manager Template Description
The Prerequisites Matrix indicates which configuration building blocks, and
hence related configuration guides, have to be followed in which sequence to
configure the respective business process and to avoid redundant work in
SAP Solution Manager.
The Prerequisites Matrix can be found in the Step-by-Step Guide, Deploy:
Activate Solution  Manual activation and configuration page  Content
Library  Prerequisites Matrix.
To prepare SAP Best Practices solution builder with solution file and installation data you
have several options:

Using the scoping information of SAP Solution Manager to prepare SAP Best
Practices solution builder
If the solution package only consists of one solution file, in SAP Solution Manager
(transaction SOLAR01 or SOLAR02), choose menu entry Utilities (M)  Pass
Data to Solution Builder.

For this option, you are required to configure Web Services in advance.

Using the preparation described in the appropriate sections of the Quick Guide.

Using the Download Solution & Data from Web button in SAP Best Practices
solution builder Solution Editor view
3. For life-cycle reasons, document all changes made to the delivered solution package
content in SAP Solution Manager.
4. Continue with test and training using SAP Solution Manager content and techniques.
5. Go live and transfer implementation results into the SAP Solution Manager solution
directory.

For more information about SAP Solution Manager (inclusive system
administration and implementation aspects described in chapters below), see the
SAP Library documentation for SAP Solution Manager at
http://service.sap.com/solutionmanager.
© SAP SE
Public
Page 10 of 10