176207705-sap-srm

8/10/2019 176207705-SAP-SRM

http://slidepdf.com/reader/full/176207705-sap-srm 1/94

Master Guide

mySAP™ Supplier

Relationship

Management

powered by SAP

NetWeaver™

Using SAP

®

SRM Server 5 5

Document Version 1.6 – November 9, 2006

Material Number 50075260

8/10/2019 176207705-SAP-SRM


SAP AG

Dietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www sap com

© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,

MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,

xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity,

Tivoli, and Informix are trademarks or registered trademarks of IBM

Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the

Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered trademarks of

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and

other SAP products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of SAP AG

in Germany and in several other countries all over the world. All other

product and service names mentioned are the trademarks of their

respective companies. Data contained in this document serves

informational purposes only. National product specifications may

vary.

These materials are subject to change without notice. These materials

are provided by SAP AG and its affiliated companies ("SAP Group")

for informational purposes only, without representation or warranty of

any kind, and SAP Group shall not be liable for errors or

omissions with respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in the express

warranty statements accompanying such products and services, if any.

Nothing herein should be construed as constituting an additional

warranty.

SAP Library document classification: PUBLIC

Disclaimer

Some components of this product are based on Java™. Any code

change in these components may cause unpredictable and severe

malfunctions and is therefore expressively prohibited, as is any

8/10/2019 176207705-SAP-SRM


Typographic Conventions Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Type Style Descripti onExample Text Words or characters quoted

from the screen. These includefield names, screen titles,pushbuttons labels, menunames, menu paths, and menuoptions.

Cross-references to other

documentationExample text Emphasized words or phrases

in body text, graphic titles, andtable titles

EXAMPLE TEXT Technical names of systemobjects. These include reportnames, program names,transaction codes, table

names, and key concepts of aprogramming language whenthey are surrounded by bodytext, for example, SELECT andINCLUDE.

Exampl e t ext Output on the screen. Thisincludes file and directorynames and their paths,messages, names of variables

and parameters, source text,and names of installation,upgrade and database tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asth i th

Additional icons are used in SAPLibrary documentation to help youidentify different types of information ata glance. For more information, see

Help on Help → General InformationClasses and Information Classes forBusiness Information Warehouse onthe first page of any version of SAPLibrary.

8/10/2019 176207705-SAP-SRM


Master Guide – mySAP SRM

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

Documentation types in the sof tware life cycle

ImplementationImplementation

Master Guide

Configuration

DocumentationRelease Notes

ComponentInstallation Guide

ComponentUpgrade Guide

Upgrade Master Guide

OperationOperation UpgradeUpgrade

Solution Management

Guide

Implementation Guide (IMG) Delta and Upgrade IMG

Security Guide

SAP Library

SAPterm

Cross-phase DocumentationSAPterm

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

• Target group:

Relevant for all target groups

• Current version:

Located in the SAP Help Portal at help.sap.com → Additional Information →

8/10/2019 176207705-SAP-SRM



•

Current version:Located in the SAP Help Portal at help.sap.com

Also located in the SAP Service Marketplace at service.sap.com/ibc (only the

descriptions of the business scenarios)

Implementation Guide (IMG)

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

• Target group:

Solution consultants

Project teams for implementations or upgrades


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

Security Guide

The Security Guide describes the settings for a medium security level and offers suggestionsfor raising security levels. A collective security guide is available for the SAP NetWeavertechnologies like SAP Web Application Server (SAP Web AS). This document containsgeneral guidelines and suggestions about system security. mySAP SRM has a SecurityGuide of its own.

• Target group:

Technology consultants


Project teams for implementations or upgrades


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

Implementation

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

8/10/2019 176207705-SAP-SRM



Component Installation Guide

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

• Target group:


Project teams for implementations


Located in the SAP Service Marketplace at ser vi ce. sap. com/ i nst gui des ->

mySAP Business Suite Solutions -> mySAP SRM

Configuration Documentation in SAP Solution Manager

SAP Solution Manager is a tool with various functions, one of its main functions being theconfiguration of SAP solutions and business scenarios. It contains IMG activities andtransactions as well as documentation and references to the relevant SAP Notes. The SRM5.0 configuration documentation is delivered with the ST-ICO 150 content shipment forSolution Manager.

The Solution Manager content replaces the Business Scenario Configuration Guides, whichwere delivered with earlier SRM shipments.

• Target group:


Project teams for implementation

• Current version:In SAP Solution Manager ST-ICO 150 content shipment

Production operationSolution Operation Guide

The Solution Operation Guide is the starting point for operating an SAP solution. The guiderefers users to the tools and documentation that are needed to carry out various tasks, such

as monitoring, backup/restore, master data maintenance, transports, and tests. It also refersusers to other documents, for example, the SAP Library, the Master Guide, and theComponent Management Guides.

• Target group:

System administrators

T h l lt t

8/10/2019 176207705-SAP-SRM



UpgradeUpgrade Master Guide

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

• Target group:


Project teams for upgrades


Located in the SAP Service Marketplace at ser vi ce. sap. com/ i nst gui des ->

mySAP Business Suite Solutions -> mySAP SRM

Component Upgrade Guide

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

• Target group:


Project teams for upgrades• Current version:

Located in the SAP Service Marketplace at ser vi ce. sap. com/ i nst gui des →

mySAP Business Suite Solutions → mySAP SRM

Release Notes

Release notes are documents that contain short descriptions of new features or changes inan SAP component since the previous release. Release notes about ABAP developments

enable the SAP system to generate delta and upgrade IMGs.

• Target group:

Consultants

Project teams for upgrades


8/10/2019 176207705-SAP-SRM



Contents 1 Gett ing Started .............................................................................11

1.1 Related Information .......................................................................14

1.2 SAP Solution Manager...................................................................15

1.3 Important SAP Notes .....................................................................16

1.4 History of Changes ........................................................................18

2 mySAP SRM Overview.................................................................19

2.1 Software Component Matrix .........................................................19

2.2 Solut ion-Wide Topics ....................................................................22

2.2.1 Minimal System Landscape ............................................................. 22

2.2.2 Overall Installation Sequence .......................................................... 24

2.3 Enterprise SOA Enablement of mySAP Supplier RelationshipManagement .........................................................................................25

3 Business Scenarios of mySAP SRM ..........................................26

3.1 Self-Service Procurement .............................................................26

3.1.1 Overview ............................................................................................26

3.1.2 Technical System Landscape .......................................................... 27

3.1.3 Implementation Sequence ................................................................ 29

3.1.3.1 Installation................................................................................................................29 3.1.3.2 Configuration............................................................................................................32 3.1.3.3 Solution Management..............................................................................................32 3.1.3.4 Upgrade ...................................................................................................................32

3.2 Plan-Driven Procurement ..............................................................33

3.2.1 Overview ............................................................................................33


3.2.3 Implementation Sequence ................................................................ 36 3.2.3.1 Installation................................................................................................................36 3.2.3.2 Configuration............................................................................................................39 3.2.3.3 Solution Management..............................................................................................39 3.2.3.4 Upgrade ...................................................................................................................39

3.3 Strategic Sourcing .........................................................................40

3 3 1 Overview 40

8/10/2019 176207705-SAP-SRM



3.4.3.1 Installation................................................................................................................50

3.4.3.2 Configuration............................................................................................................52 3.4.3.3 Solution Management..............................................................................................52 3.4.3.4 Upgrade ...................................................................................................................52

3.5 SRM-MDM Catalog .........................................................................53

3.5.1 Overview ............................................................................................53



3.5.3.1 Installation................................................................................................................55 3.5.3.2 Configuration............................................................................................................57 3.5.3.3 Solution Management..............................................................................................57

3.6 Service Procurement .....................................................................58

3.6.1 Overview ............................................................................................58


3.6.3 Implementation Sequence ................................................................ 61 3.5.3.1 Installation................................................................................................................61

3.5.3.2 Configuration............................................................................................................64 3.5.3.3 Solution Management..............................................................................................64 3.5.3.4 Upgrade ...................................................................................................................64

3.7 Spend Analysis ..............................................................................65

3.7.1 Overview ............................................................................................65




3.8 Contract Management ...................................................................70

3.8.1 Overview ............................................................................................70




3.9 SAP ERP 2005 – SAP SRM............................................................77

4 Software Components Overview 78

8/10/2019 176207705-SAP-SRM



6 Additional Information .................................................................90

6.1 Importing Integration Objects for mySAP SRM on SAPProcess Integration..............................................................................90

6.2 Patching your mySAP SRM Solution ...........................................91

7 Media Informat ion ........................................................................92

8/10/2019 176207705-SAP-SRM


1 Getting Started

1 Getting StartedThis Master Guide for mySAP™ Supplier Relationship Management (mySAP SRM) providesa central starting point for the technical implementation of mySAP SRM.

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

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

For information about upgrading the mySAP SRM business scenarios, see theUpgrade Master Guide – mySAP SRM. This guide provides information aboutthe overall upgrade sequences, references to related documentation, SAPNotes, and additional upgrade information for each business scenario of mySAP

SRM. The Upgrade Master Guide is available on SAP Service Marketplace atservice.sap.com/srm-inst.

The complete mySAP SRM solution consists of the following top-level scenarios andbusiness scenarios:

Self-Service Procurement

Self-Service Procurement enables your employees to create and manage their ownrequirement requests. This relieves your purchasing department of a huge

administrative burden while making the procurement process both faster and moreresponsive.

Plan-Driven Procurement

Plan-Driven Procurement automates and streamlines ordering processes for regularlyneeded core materials. Since mySAP SRM is integrated with planning, design, andorder-processing systems, you can link your procurement processes to a plan-drivenstrategy that gets you the materials you need for core business processes — exactlywhen you need them. Plan-Driven Procurement integrates seamlessly with backendsystems such as enterprise planning and production systems. The scenario allows youto integrate operational procurement with your existing supply chain managementsolution.

Service Procurement

E-procurement has produced great opportunities for saving costs in the purchasingprocess. However, companies generally fail to extend cost saving measures to

8/10/2019 176207705-SAP-SRM


1 Getting Started

Strategic Sourcing

The sourcing application in SAP Enterprise Buyer provides professional purchaserswith a wide range of actions and information to help them source their requirements. As a purchaser, you can use the interface to process the requirements and determinethe best source of supply. Once you have done this, you can create a purchase orderor contract directly from the sourcing application or SAP Bidding Engine. You can thensave it either locally or in the backend system, depending on the technical scenario youare using (classic, extended classic, or standalone).

Spend Analysis

Spend Analysis is a decision-support application that enables you as a purchaser toanalyze your total spending across system and organizational boundaries. You canperform the analysis per supplier, per product, or per product category.

Contract Management

Contract Management provides a solution for creating purchasing contracts and globaloutline agreements (GOA) and for changing them. It also provides a means torenegotiate existing contracts directly with the vendor or by creating a bid invitation. A

contract can be automatically assigned as a source of supply or displayed as apossible selection.

Structure of the Master Guide

This Master Guide consists of the following sections:

• Getting Started [page 11] contains valuable information about using this document andrelated information (documentation and SAP Notes) crucial to the installation.

• mySAP SRM Overview [page 19] contains the following information:

A short introduction to the mySAP™ Business Suite solution described in detail in therest of the document

The software component matrix that provides an overview of which business scenariosuse which components and if the corresponding component is mandatory oroptional

Minimal system landscape

Overall installation sequence

• Business Scenarios of mySAP SRM [page 26] contains the following information foreach business scenario of this solution:

An overview of the business scenario

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

8/10/2019 176207705-SAP-SRM


1 Getting Started

documentation is covered in installation guides available at the SAP Service

Marketplace. The configuration documentation is only available within SAP SolutionManager Content ST-ICO 150. In References [page 85] you can find an overview of alldocumentation referenced in this Master Guide.

You can find the most current information about the technical implementation ofthis mySAP Business Suite solution and the latest installation guides in SAPService Marketplace at:

service.sap.com/srm-inst.

We strongly recommend that you use the documents available there. Theguides are regularly updated.

• Additional Information [page 90] contains:

Additional information if you are installing/patching the SAP® NetWeaver Process

Integration (PI) (formerly Exchange Infrastructure (XI)) as part of mySAP SRM.

Information about how to patch your mySAP SRM solution (for example, if you want topatch your solution from Support Package 02 to Support Package 03).

8/10/2019 176207705-SAP-SRM


1 Getting Started

1.1 Related Information

1.1 Related InformationThe following list contains links to important information for implementing this mySAPBusiness Suite solution.

List of Links to Information in the SAP Service Marketplace

Content Location in SAP Service Marketplace

The latest version of the installation and

upgrade guides for mySAP SRM andSAP SRM Server, links to related SAPNotes

ser vi ce. sap. com/ sr m- i nst → mySAP

SRM → Using SAP SRM Server 5.5

Released platforms ser vi ce. sap. com/ pl at f orms → Product

Availability Matrix

Security Guide – mySAP SRM 5.0.Provides cross-component securityinformation for mySAP SRM; explains

security aspects relevant for systemlandscape design, network andcommunication security, and useradministration and authentication.

(This document will be available at theend of 2005.)

ser vi ce. sap. com/ sr m- i nst → mySAP →

SRM Using SAP SRM Server 5.5

General information about security forSAP systems.

ser vi ce. sap. com/ secur i t y

SAP Solution Manager ser vi ce. sap. com/ sol ut i onmanager

SAP R/3 plug-in releases and availability ser vi ce. sap. com/ R3- pl ug- i n

Hardware sizing ser vi ce. sap. com/ si z i ng

Information about SRM components andfurther documents

ser vi ce. sap. com/ sr m→ mySAP SRM in

Detail

Information about SAP SRM Support

Package stacks and download ofSupport Package stacks

ser vi ce. sap. com/ sp- st acks

Download of SAP software(SAP Software Distribution Center)

ser vi ce. sap. com/ swdc

http://service.sap.com/instguides

http://service.sap.com/platforms

http://service.sap.com/solutionmanager






8/10/2019 176207705-SAP-SRM


1 Getting Started

1.2 SAP Solut ion Manager

1.2 SAP Solution ManagerSAP provides the SAP Solution Manager as the platform to efficiently support theimplementation and operation of your mySAP SRM solution. Using SAP Solution Managersignificantly accelerates the implementation process and helps you to achieve your businessgoals. SAP Solution Manager contains predefined implementation content (IMG activities andtransactions as well as documentation and SAP Notes) that help you to configure your SRMSolution. In addition, SAP delivers Support Services based on the business scenariosdesigned and documented in SAP Solution Manager.

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

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

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

• Plan your Solution Landscape

• Connection of existing systems and activation of SAP EarlyWatch Alert

• Setup Solution Manager Diagnostics for root cause analysis of Java components

• Handover of processes and systems to support organization after Go Live

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

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

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

•

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

Solution Manager Guides

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

8/10/2019 176207705-SAP-SRM


1 Getting Started

1.3 Impor tant SAP Notes

Support requires remote access to the SAP Solution Manager that hosts the affected

system landscape.

• If you already have an SAP Solution Manager deployment in place, you can use it tomanage the solution you build up with SAP NetWeaver and mySAP SRM as well. Inthis case, it is highly recommended that you update SAP Solution Manager andSolution Manager content to the latest version.

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

•

If you want to reduce the risk of unavailability, do not install SAP Solution Manageras a central component. Instead, operate a two system landscape with test andproduction environment of SAP Solution Manager, especially if you are using timecritical functions like Support Desk. If you also develop your own content, a three-system landscape with development, test and production environment isrecommended.

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 theinstallation documentation.

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

List of Important SAP Notes

SAP Note Title Descript ion

856911 Composite note whichcollects together all notesrelating to the installation ofSAP SRM 5.0

This composite SAP Note is crucial for theSAP SRM 5.0 installation. It is a collection ofall SAP Notes relating to its installation.

It also contains all information relating to theSAP SRM installation that was not availablewhen the installation guide was published.

852894 SRM 5.0Support Package 01

Release and Information Note

708736 Release restrictions R/3Plug-in 2004.1

This SAP Note contains information aboutrestrictions to the productive use that isimportant for the installation of the SAP R/3Plug-In.

704564 R/3 plug-in: PI 2004.1 This SAP Note is required to install the SAP

8/10/2019 176207705-SAP-SRM


1 Getting Started

1.3 Important SAP Notes

855827 SAP SRM 5.0

Installation on Windows

Additional information for installation on a

Windows operating system.

855299 SAP SRM 5.0Installation on UNIX

Additional information for installation on aUNIX operating system.

855897 INST: mySAP ERP 05 ABAP on iSeries

Additional information for installation oniSeries.

835170 Installation of/Delta

Upgrade to CCM 200

This SAP Note contains information about

carrying out an Add-On installation/deltaupgrade with transaction SAINT.

9670088 SRM-MDM Catalog 1.0Installation &Configuration

This SAP Note contains information aboutcarrying out an installation and configurationof SRM-MDM Catalog 1.0.

8/10/2019 176207705-SAP-SRM


1 Getting Started

1.4 History of Changes

1.4 History of ChangesThe regularly updated Master Guide is available in the SAP Service Marketplace atservice.sap.com/srm-inst.

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

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

Master Guide Version Important Changes

1.0 (October 10, 2005) First version

1.1 (November 9, 2005) Architecture graphics replaced

1.2 (January 5, 2006) Minor changes

1.3 (March 28, 2006) Minor changes

1.4 (May 24, 2006) Minor changes for Support Release 1

1.5 (July 25, 2006) New SRM-MDM Catalog business scenarioincorporated; information on Enterprise SOA added

1.6 (November 9, 2006) Minor changes for Support Release 2

8/10/2019 176207705-SAP-SRM


2 mySAP SRM Overview

2.1 Software Component Matrix

2 mySAP SRM OverviewmySAP Supplier Relationship Management maximizes the return on all supplier relationshipsacross all categories of spending at all times. It covers the entire supply cycle from strategicsourcing to operational procurement and supplier enablement to leveraging consolidatedcontent and master data. With mySAP SRM, you can collaborate with all suppliers for allpurchased goods and services, enabling you to continually optimize supplier selection,shorten cycle times, and devise sourcing and procurement strategies.

Overview of Components

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

SAP NetWeaver Portal 7.0

SAP NetWeaver AS Java 7.0

SAP NetWeaver usage type Process Integration (PI)

SAP WebAS ABAP 7.0 SAP WebAS JAVA 7.0

SRM-MDM *Catalog 1.0

JVM

SAP SRM Server 5.5

EBP

Bidding Engine

SUS

LAC WPS

5.0

JCo

SAP

NetWeaver

BI 7.0 TREX 7.0for

SAP NetWeaver

App li cat ion Pl atform (Including SAP IPC 7.0)

SAP Catalog *Content Mgmt 2.0

(*alternative components )

2.1 Software Component MatrixThis section provides an overview of which business scenarios use which components in this

8/10/2019 176207705-SAP-SRM




Release and Information Note which is available for each Support Package

stack (SAP note number is listed on the page). For mySAP SRM 5.0 SupportRelease 01, see SAP Note 852894.

The exact locations of the required software components on the corresponding DVD(s) andCD(s) which are shipped with the SAP SRM 5.0 package can be found underhttp://service.sap.com/instguides mySAP Business Suite Solutions mySAP

SRM.

Business Scenario / Software Component Matrix (M = mandatory / O = optional)

Software Component Business Scenario

S e l f - S e r v i c e

P r o

c u r e m e n t

P l a

n - D r i v e n

P r o

c u r e m e n t

S t r a t e g i c

S o u r c i n g

C a t a l o g C o n t e n t

M a n a g e m e n t

S e r v i c e

P r o

c u r e m e n t

S p e n d A n a l y s i s

C o n t r a c t

M a n a g e m e n t

S R M - M D M C

a t a l o g

SAP® Supplier Relationship Management

Server 5.5 (SAP SRM Server 5.5)

(based on SAP® Web Application Server 7.00,

comprises SAP® Enterprise Buyer, SAP

®

Bidding Engine and Supplier Self-Services)

M M M M M M M M

SAP® Internet Transaction Server

(SAP ITS) 7.00

Note: Only the internal ITS is supported.

M M M M M M M M

SAP® NetWeaver Business Information

Warehouse(SAP BI) 7.0 plus SAP BI Content 7.0.2

O O O -- O M O --

SAP® Catalog Content Management 2.0 M -- O M O -- O --

SAP® SRM-MDM Catalog 1.0 M -- O -- O -- O M

SAP® NetWeaver 2004s Search and

Classification (TREX)M

(1)O O M O -- O --

SAP® Enterprise Portal 7.0 (Portal Server) O O O O O O O O

Business Packages for SAP NetWeaverEnterprise Portal 7 0:




8/10/2019 176207705-SAP-SRM




Software Component Business Scenario


P r o c u r e m e n t

P l a n - D r i v e n


S t r a t e g i c

S o u r c i n g


M a n a g e m e n t

S e r v i c e



C o n t r a c t

M a n a g e m e n t

S R M - M D M C

a t a l o g

-- M O -- O -- O --• SAP SRM Server 5.5

• SAP Catalog Content Management 2.0 -- -- -- O -- -- -- --

SAP GUI for Windows 6.40 M M M M M M M M

SAP® R/3 OLTP as of 3.1i up to SAP

® R/3

Enterprise 4.70, ERP 1.0, ERP 2.0

(SAP R/3 4.6C or higher recommended)

O O O -- O O O --

SAP R/3 Plug-In 2004.1 or higher if one isavailable

O O O -- O O O --

(1)You require SAP

® NetWeaver 2004s TREX in the following cases:

• When you use SAP Catalog Content Management 2.0

• When you use the contract management application to search for information such asvendor texts, internal notes, and attachments.

8/10/2019 176207705-SAP-SRM



2.2 Solution-Wide Topics

2.2 Solution-Wide Topics2.2.1 Minimal System LandscapeIn the mySAP SRM solution, you can install all software components (ABAP and non-ABAPcomponents) as shown in the figure below.

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

The installation of this minimal system landscape is possible only if you choose an operatingsystem and a database that supports all components.

For more information about released platforms for mySAP SRM, see SAP Service

Marketplace at ser vi ce. sap. com/ pl at f orms → Product Availability Matrix.

Furthermore, you must provide a sufficiently sized server. For information on sizing, see SAP

Service Marketplace at ser vi ce. sap. com/ si z i ng.

The figure only shows those SRM components behind the firewall.

SAP Process Integration requires a dedicated SAP Web Application Server.

This means that running applications in other clients of the same SAP Web ASis not supported.



8/10/2019 176207705-SAP-SRM




Single Host Installation of mySAP SRM

Database

# 100 EBP

PI_BASIS

Search

andClassifi-

cation

Process

Integration

(PI)

AS-ABAP 7.0

AS-ABAP 7.0

# 200 SUS

AS-Java 7.0

# 300 BW

LAC WPS

5.0

IPC 7.0

EP 7.0# 500 Catalog

Search

# 500 Catalog

Aut h.

SRM-Server 5.5

Catalog 2.0

(Add-on)

EBP and SUS can also run in one client. For more information, see the SAPImplementation Guide (SAP IMG), activity Determine Back-End System.

With regard to catalog management, this figure shows only an exampleinstallation. You can use SRM-MDM Catalog as an SAP NetWeaver-basedalternative to SAP CCM.

8/10/2019 176207705-SAP-SRM




2.2.2 Overall Installation SequenceThe following figure contains the installation sequence of mySAP SRM containing thecomponents of all business scenarios of mySAP SRM.

Depending on the business scenarios of mySAP SRM that you want toimplement, your installation sequence may only contain a subset of thesesoftware components.

For more information concerning the installation sequence of each business

scenario, see section <Business Scenario> → Implementation Sequence.

Software components on the same level can be installed at the same time on the appropriatemachine (for example, different project groups could install SAP R/3 and SAP PIsimultaneously). This is important to know if you want to implement more than one mySAPSRM business scenario at a time.

Installation Sequence of mySAP SRM

T i m e

SAP

IPC*

SRM

Server (SUS)

SAP

R/3

SRM

Server (EBP)

SAP

IPC*

SAP

PI

SAP

ITS

Remark:

Some of these software components may

be optional for some/all business scenarios

or not part of some business scenarios at

all. See the Software Component Matrix for

more information.

LAC

WPS

SAP

CCM

SAP

BI

SAP

EP

TREX

8/10/2019 176207705-SAP-SRM



2.3 Enterprise SOA Enablement of mySAP Supplier Relationship Management

2.3 Enterprise SOA Enablement of mySAPSupplier Relationship ManagementThe initial enterprise service-oriented architecture (enterprise SOA) enablement of mySAPSupplier Relationship Management is part of the SAP-wide activities to standardize theinterfaces of mySAP Business Suite applications.

For more information about the specific services delivered with the SRM Service

Enablement 5.5 add-on, see sdn.sap.com → Enterprise SOA → ES Workplace →

Browse Service Definitions → mySAP Supplier Relationship Management.

8/10/2019 176207705-SAP-SRM


3 Business Scenarios of mySAP SRM

3.1 Self-Service Procurement


This Master Guide provides just one way to implement each business scenario.For other ways to implement business scenarios, see the Scenario & ProcessComponent List in SAP Service Marketplace (service.sap.com/scl ). The

Scenario & Process Component List helps you to find realization alternatives forSAP solutions, business scenarios and processes. It shows you which

application components are needed to realize a business scenario or process.

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

Overview

Technical system landscape

Overview of the implementation sequence

3.1.1 Overview

Description

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

For more information on Self-Service Procurement, see the Business Scenario Descriptionsfor mySAP SRM.

Tasks

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

• Employees buying office materials or IT equipment from catalogs

• Employees buying items that are not covered in catalogs from centrally agreed

contracts, for example procurement of services• Capturing requirement requests for materials not covered in catalogs or outline

agreements by employees to provide a single point of contact for purchase requisitions

• Professional buyers purchasing standard, indirect material without auction

Process Chain

8/10/2019 176207705-SAP-SRM




Deployment Options

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

• Classic deployment

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

• The extended classic deployment

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

•

The standalone deploymentIn this deployment scenario, you have no Materials Management (MM) in your ERPsystem and are using the Materials Management functions in the SAP EnterpriseBuyer system for all non-production procurement. If required, you can connect Accounting (FI) and Controlling (CO). However, this is optional.

3.1.2 Technical System Landscape

For information about the technical system landscape and about how to plan thebusiness scenario to meet your needs, see:

• the section Minimal System Landscape [page 22]

• SAP Service Marketplace atser vi ce. sap. com/ pl at f orms Platform Availability Matrix



8/10/2019 176207705-SAP-SRM




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

Firewall

SAP NetWeaver

BI 7.0 IPC

7.0

RFC

BI CONT 7.0.2

R/3 Plug_In

R/3 3.1i –

SAP ECC 6.0

R/3 Plug_In

FI / COMM

(IDOC)

Appli cat ion Gateway

HTTP(S)HTTPS / OCI

SAP SRM

Server 5.5

EBP

ITS

PI

XI Content: SAP SRM Server 5.5 XI Content: SAP Catalog Content Management 2.0

XML XML

HTTP(S)

XI Integration

Engine

TREX 7.0

XI Proxy

Framework

XI Int.

Engine

XI Int.

Engine

RFC RFCXI ProxyFrame-

work

#

SRM-

MDM

Catalog

1.0

SAP

CatalogContent

Mgmt.

2.0

BSP

## alternative

components

Legend:

8/10/2019 176207705-SAP-SRM




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

• For latest Support Package and patch level requirements, see SAP Service

Marketplace at service.sap.com/sp-stacks → SAP SRM 5.0 and theRelease and Information Note which is available for each Support Packagestack (SAP note number is listed on the page).

• Also see section Overall Installation Sequence [page 24], especially if youwant to implement more than one SRM business scenario at a time.

• For documentation referenced in the following table, see section References[page 85].

3.1.3.1 Installation

No. Action

[Corresponding Documentation]

Remarks/Subsequent Steps

Install SAP Process Integration.

[Master Guide – SAP NetWeaver 2004s]

The use of SAP Process

Integration is optional. It isrequired for outbound XML-based messaging or forconnecting non-SAP planning orexecution systems.

SAP Process Integration

requires a dedicated SAP Web Application Server. This meansthat running applications in otherclients of the same SAP Web ASis not supported.

1

If you installed SAP Process Integration, import the

8/10/2019 176207705-SAP-SRM




No. Action



Download and install the latest SLD Content from SAPService Marketplace at service.sap.com/swdc →

Download → Support Packages and Patches → Entryby Application Group → Additional Components → SAP Master Data for SLD.

/

Install/Integrate SAP R/3 or SAP R/3 Enterprise (SAP

R/3 4.6C or higher recommended).[SAP R/3 Installation on <Platform>: <Database>, or

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

SAP R/3 and SAP R/3 Enterprise

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

2

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

• For the installation, see SAP Notes 704564 (R/3

plug-in: PI 2004.1 installation/delta upgrade) and708736 (Release restrictions R/3 Plug-in2004.1).

• For more information concerning SAP R/3 Plug-Ins, see SAP Service Marketplace atser vi ce. sap. com/ r3- pl ug- i n.

Not required for customers withan ERP 2.0 backend system.From ERP 2.0 onwards, theformer plug-in functionalities are

delivered with the SAP_APPLcomponent.

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

3 Install SAP SRM Server 5.5

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

/

4 Install SAP Internet Transaction Server (7.00)

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

You have to use the internal SAPITS, which is integrated into theSRM Server (SAP ITS 7.0). Notethat the external ITS is notsupported.

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

For information, see:

• SAP Note 835170 (regarding SAP-CCM)

• SAP Note 967088 (regarding SRM MDM

/

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



8/10/2019 176207705-SAP-SRM




No. Action



languages during the installation of SAP®

NetWeaver 2004s TREX.

• No Python extensions are required

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

7 Install SRM Server for SAP SUS.

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

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

8 Install SAP BI:

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

[Installation Guide – SAP Web Application Server

ABAP on <Platform>: <Database>]

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

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

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

For more information, see the Master Guide – SAPNetWeaver 2004s.

The use of SAP BI is optional.See the description of thiscomponent in SoftwareComponents Overview [page 70] to decide if it is required for your

business scenario. After the BI ABAP upgrade, youshould install the Java parts of BI(BI-Java) to take advantage of allnew functionality. For details,see Installation Guide – SAPNetWeaver 2004s.

9 Install SAP NetWeaver Enterprise Portal 7.0.


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

10 Import the following Business Packages into theEnterprise Portal:

• Business Package for SRM 5.0

• Business Package for Supplier Collaboration 2.0

Download the BusinessPackages from the SAPDeveloper Network

www.sdn.sap.com→ PortalContent Portfolio

3 B i S i f SAP SRM

8/10/2019 176207705-SAP-SRM




3.1.3.2 ConfigurationFor information about the configuration of this business scenario, see the configurationdocumentation for mySAP SRM in SAP Solution Manager.

3.1.3.3 Solution Management As central starting point for information about designing, implementing, and keeping yourenterprise’s information technology solution up and running, see the Solution OperationGuide – mySAP SRM, which will be available with Support Package 2.

3.1.3.4 UpgradeSee the Upgrade Master Guide – mySAP SRM.


8/10/2019 176207705-SAP-SRM



3.2 Plan-Driven Procurement

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

Overview



3.2.1 Overview

Description

Plan-Driven Procurement automates and streamlines ordering processes for regularlyneeded core materials. You can use this business scenario to procure requirements formaterials that have been generated in systems other than SAP Supplier RelationshipManagement (external systems). By integrating the SRM System with planning, design, andmaintenance systems, you can accelerate your procurement and integrate the operationalprocurement with your Supply Chain Management solution. The business scenario supports

third-party order processing, a special kind of procurement. Here the product goes directlyfrom the vendor to the customer of the purchasing company. The purchase order to thevendor contains the necessary information for this.

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

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

For more information on Plan-Driven Procurement, see the documentation BusinessScenario Descriptions for mySAP SRM.

Tasks

Examples of tasks for Plan-Driven Procurement include:

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

• A company performing planned and unplanned maintenance centralizes procurement

activities in a single application.

Process Chain

The following figure shows an example of a typical Plan-Driven Procurement process chain:

PLAN-DRIVEN PROCUREMENT


8/10/2019 176207705-SAP-SRM




purchase order is created there and changes to it must be made there, with a copy of it

replicated to the backend system. Goods receipts (confirmations) and invoices can also beentered initially in the SAP Enterprise Buyer system. Purchase order data is updated in thebackend system from SAP Enterprise Buyer. Goods receipt and invoice data are updatedfrom the backend system.

Requirement Options

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

•

An APS (Advanced Planning and Scheduling) system, for example SAP APO.• SAP R/3 MM.

• Other external systems via an open XML interface.



• the section Minimal System Landscape [page 22]

• SAP Service Marketplace at the Internet address:

ser vi ce. sap. com/ pl at f orms Platform Availability Matrix




8/10/2019 176207705-SAP-SRM




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

Legend:


8/10/2019 176207705-SAP-SRM


3 us ess Sce a os o yS S





Marketplace at service.sap.com/sp-stacks → SAP SRM 5.0 and the

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


• It is assumed that an MRP (Material Requirements Planning) system – forexample, SAP APO – is already installed.


No. Action




[Master Guide – SAP NetWeaver 2004s]SAP Process Integrationrequires a dedicated SAP Web Application Server. This meansthat running applications inother clients of the same SAP

Web AS is not supported. After you install SAP Process Integration, import theintegration objects for mySAP SRM into the SAPProcess Integration [page 90].

Import the PI content for the following components:

/

1


8/10/2019 176207705-SAP-SRM


y


No. Action



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

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


SAP R/3 and SAP R/3Enterprise are not part of thisinstallation and are thereforenot contained in the installationpackage. A separate SAP R/3or SAP R/3 Enterpriseinstallation package is required.

2

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

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

• For more information concerning SAP R/3 Plug-Ins, see SAP Service Marketplace at:ser vi ce. sap. com/ r3- pl ug- i n

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

3 Install SAP SRM Server 5.5.

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

/


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

You have to use the internalSAP ITS, which is integratedinto the SRM Server (SAP ITS

7.0). Note that the external ITSis not supported.

5 Install SAP®

NetWeaver 2004s Search andClassif ication (TREX)

[SAP NetWeaver 2004s Installation Guide: Search and

Classification (TREX)]

/


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

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





8/10/2019 176207705-SAP-SRM



No. Action



7 Install SAP BI:

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

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

2. Configure the database of your SAP Web ASfor SAP BI according to SAP Note 567745.

3. Install SAP BI Business Content Add-OnBI_CONT 7.0.2 on the SAP Web AS ABAPsystem according to SAP Note 847019.


For more information, see the Master Guide – SAPNetWeaver 2004s, included in the installation package.

The use of SAP BI is optional.See the description of thiscomponent in section SoftwareComponents Overview [page70] to decide if it is required foryour business scenario.

After the BI ABAP upgrade, you

should install the Java parts ofBI (BI-Java) to take advantageof all new functionality. Fordetails, see Installation Guide –SAP NetWeaver 2004s.


[Master Guide – SAP NetWeaver 2004s, part of theinstallation package]

The use of SAP NetWeaverEnterprise Portal is optional. Itis required for the integration ofmySAP SRM into a portal.

9 Import the following Business Packages into the

Enterprise Portal:



Download the Business

Packages from the SAPDeveloper Network

www. sdn. sap. com→ Portal

Content Portfolio


8/10/2019 176207705-SAP-SRM




3.2.3.3 Solution Management As central starting point for information about designing, implementing, and keeping yourenterprise’s information technology solution up and running, see the documentation SolutionOperation Guide – mySAP SRM.

3.2.3.4 UpgradeSee the documentation Upgrade Master Guide – mySAP SRM.


8/10/2019 176207705-SAP-SRM


3.3 Strategic Sourcing

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

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

• Supply Strategy Development

• Supplier Qualification

• Supplier Selection

• Contract Negotiation and Management

• Relationship Monitoring

• Operational Sourcing

• Live Auctioning



3.3.1 Overview

Description

You can use this business scenario to process all your requirements and optimize yoursource of supply for each individual item. You can identify cost-saving opportunities andevaluate suppliers’ ability to provide materials and services at low cost, high quality, and on

schedule. Once you have determined the best source of supply for your requirements, youcan collaborate in project teams both internally and with your suppliers to establish on-goingrelationships based on contracts and global outline agreements.

For more information on Strategic Sourcing, see the documentation Business ScenarioDescriptions for mySAP SRM.

Tasks

Sample tasks for the Strategic Sourcing business scenario include:

• An electronics manufacturer finds that certain components have become commodity –and formulates a strategy to source them locally.

• A company opens a new facility in East Asia and redefines the sourcing strategy forthat region.


8/10/2019 176207705-SAP-SRM



• A professional purchaser and the IT department jointly negotiate a contract for an ITservice project with the IT service provider.

• A company presents a “supplier cockpit” tool to their professional purchasers where allsupplier information is maintained.

• A manufacturer monitors its suppliers to gain insight into the value contributed to thebusiness from individual suppliers.

• A professional purchaser creates a reverse auction to find a supplier for specific non-standard engineering software not covered by the catalog.

• A professional purchaser manually assigns a contract to a demand for office furniture.

Process Chain

The following figure shows an example of a Strategic Sourcing process chain:

STRATEGIC SOURCING

Create andsubmit bid

InitiateRFQ/Auction

Bid analysisand evaluation

Determine

Winner Publish

RFQ/Auction


For information about the technical system landscape and about how to plan the

business scenario to meet your needs, see:

• Minimal System Landscape [page 22]

• SAP Service Marketplace at ser vi ce. sap. com/ pl at f orms Platform

Availability Matrix




8/10/2019 176207705-SAP-SRM



The following figure shows the underlying architecture of Strategic Sourcing.

HTTPS

Firewall

RFC

RFC

IPC

7.0

XML

PI

HTTPS / OCI

HTTP(S)

App licati on Gateway

SAP NetWeaver

BI 7.0

SAP NetWeaver BICONT 7.0.2

RFCXI ProxyFramework

XI Int.Engine

IPC

7.0


XI Int.Engine

R/3 3.1i –SAP ECC 6.0

MM

XI Content: SAP SRM Server 5.5

R/3 Plug_In

SAP SRM

Server 5.5

EBP

ITS

R/3 Plug_In

RFC

(IDOC)

XMLXI Integration

Engine

TREX 7.0for

SAP NetWeaver

SUS

SAP SRM Server 5.5

LAC WPS 5.0

BSP

XI Int.

Engine

XI ProxyFrame-

work

#

SRM-MDM

Catalog

1.0

SAP

Catalog

Content

Mgmt.2.0

#

(# alternative

components)

BSP

XI Content: SRM-MDM Catalog 1.0

or: SAP Catalog Content Management 2.0

TREX 7.0for

SAP NetWeaver

Legend:


8/10/2019 176207705-SAP-SRM










No. Action


Remarks/SubsequentSteps



SAP Process Integrationrequires a dedicated SAPWeb Application Server.This means that runningapplications in other clientsof the same SAP Web ASis not supported.

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

[page 90].


• SAP SRM Server 5.5

• SAP Catalog Content Management 2.0

/

1


3 3 St t i S i

8/10/2019 176207705-SAP-SRM



No. Action


Remarks/Subsequent

Steps

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



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

required.

2

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

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

• For more information concerning SAP R/3 Plug-Ins, seeSAP Service Marketplace at:ser vi ce. sap. com/ r3- pl ug- i n

Not required for customerswith an ERP 2.0 backendsystem. From ERP 2.0onwards, the former plug-infunctionalities are deliveredwith the SAP_APPLcomponent. Otherwise theinstallation of the SAP R/3

Plug-In is required if youinstalled an SAP R/3system in the previousstep.

3 Install SAP SRM Server 5.5 comprising:

• SAP Bidding Engine

• Supplier Self-Service


/

4 Install SAP Internet Transaction Server . (7.00)


You have to use theinternal SAP ITS, which isintegrated into the SRMServer (SAP ITS 7.0). Notethat the external ITS is notsupported.

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


/


3 3 Strategic Sourcing





8/10/2019 176207705-SAP-SRM



No. Action


Remarks/Subsequent

Steps

6 Install SAP®

NetWeaver 2004s Search and Class ification(TREX)

Use the following parameters during the installation (for moreinformation, see the documentation listed below):

• Perform the installation steps to set up an RFCconnection.

• Automatic language recognition is not required. You canadopt the default settings for document languagesduring the installation of SAP

®NetWeaver 2004s TREX.

• No Python extensions are required.


/

7 Install Live Auction Cockpit Web Presentation Server

(LACWPS) 5.0.

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

The use of Live Auction

Web Presentation Server isoptional.

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

8 Install SAP BI:

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

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

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

3. Install SAP BI Business Content Add-On BI_CONT

7.0.2 on the SAP Web AS ABAP system as describedin SAP Note 847019.

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

The use of the SAP BI is

optional. See thedescription of thiscomponent in SoftwareComponents Overview[page 70] to decide if it isrequired for your businessscenario.

After the BI ABAP upgrade,you should install the Javaparts of BI (BI-Java) to takeadvantage of all newfunctionality. For details,see Installation Guide –SAP NetWeaver 2004s.



8/10/2019 176207705-SAP-SRM



No. Action


Remarks/Subsequent

Steps

10 Import the following Business Packages into the EnterprisePortal:




www. sdn. sap. com→

Portal Content Portfolio



8/10/2019 176207705-SAP-SRM




3.3.3.3 Solution Management As central starting point for information about designing, implementing, and keeping yourenterprise’s information technology solution up and running, see the documentation SolutionOperation Guide – mySAP SRM.

3.3.3.4 UpgradeSee the documentation Upgrade Master Guide – mySAP SRM.


3.4 Catalog Content Management (CCM)

8/10/2019 176207705-SAP-SRM


g g ( )

3.4 Catalog Content Management (CCM)For this business scenario, the following topics are covered:

Overview



3.4.1 Overview

Description

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

For more information, see Business Scenario Descriptions for mySAP SRM.

Task

A Content Manager for example, creates and maintains a catalog with MRO material fromdifferent suppliers.

Process Chain

The following figure shows an example of a Catalog Content Management process chain:

CATALOG CONTENT MANAGEMENT

Import Catalog Manage CatalogDistribution of

Catalog

Provide Catalogdata for employee

usage




• SAP Service Marketplace at the Internet address:

ser vi ce sap com/ pl at f orms Platform Availability Matrix





8/10/2019 176207705-SAP-SRM


g g ( )

The following figure shows the underlying architecture of Catalog Content Managementincluding existing connections.

Legend:



8/10/2019 176207705-SAP-SRM








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

[page 85].

No. Action




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


requires a dedicated SAPWeb Application Server.This means that runningapplications in otherclients of the same SAPWeb AS is not supported.

After you install SAP Process Integration, import the integrationobjects for mySAP SRM into the SAP Process Integration[page 90].



• SAP Catalog Content Management 2.0

/

1



8/10/2019 176207705-SAP-SRM


No. Action





You have to use theinternal SAP ITS, which isintegrated into the SRMServer (SAP ITS 7.0).Note that the external ITSis not supported.

4 Install SAP Catalog Content Management 2.0.

For information, see SAP Note 835170.

/

5 Install SAP®



• Perform the installation steps to set up an RFC

connection.• Automatic language recognition is not required. You can

adopt the default settings for document languagesduring the installation of SAP

®NetWeaver 2004s TREX.



/

6 Install SAP NetWeaver Enterprise Portal 7.0.[Master Guide – SAP NetWeaver 2004s, part of the installationpackage]

The use of SAPNetWeaver EnterprisePortal is optional. It isrequired for the integrationof mySAP SRM into aportal.





www. sdn. sap. com→ Portal Content Portfolio



8/10/2019 176207705-SAP-SRM



3.4.3.3 Solution Management As central starting point for information about designing, implementing, and keeping yourenterprise’s information technology solution up and running, see the Solution OperationGuide – mySAP SRM.



3.5 SRM-MDM Catalog

8/10/2019 176207705-SAP-SRM


3.5 SRM-MDM CatalogFor this business scenario, the following topics are covered:

Overview



3.5.1 Overview

Description

The SRM-MDM Catalog business scenario provides a solution for creating, maintaining, andmanaging catalog content within your e-procurement application.

For more information, see Business Scenario Description in the SAP Service Marketplaceunder quick link i bc- sr m.

Task

A Catalog Manager imports, structures, and adjusts catalog content in the SAP MDM DataManager. Afterwards, he enables the content to be accessible for catalog users via a Webbrowser.

Process Chain

The following figure shows an example of an SRM-MDM Catalog process chain:

CONTENT MANAGEMENT with SRM-MDM Catalog

Import ProductInformation

Map and EnrichCatalog Data

Approve CatalogContent

Provide Web

Content for Catalog Users





3.5 SRM-MDM Catalog

8/10/2019 176207705-SAP-SRM


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

Firewall

App licat ion Gateway

HTTP(S)

SAP SRM

Server 5.5

EBP

ITS

PI

XI Content: SAP SRM Server 5.5, SAP SRM-MDM Catalog 1.0

XML XML

HTTP(S)

XI IntegrationEngine

XI ProxyFramework

XI Int.

Engine

RFC

TREX 7.0(Contracts)

Master Data;Contract Data

XML Catalog

Upload

SAP MDM

Server

SAP MDM

Import Server

SRM-MDM

CatalogSearch

(Web

Dynpro)

SAP SRM-MDM Catalog 1.0

SAP MDM

Console

SAP MDM

Import

Manager

SAP MDM

Data

Manager

FTP(S)

*

HTTP(S) / OCI

Legend:

SRM

Server

TCP / IP

XML

Transfer protocol type

ABAP-based sof tware component

Document format type

TREX C/C++ based software component


3.5 SRM-MDM Catalog

8/10/2019 176207705-SAP-SRM


• IPC 7.0 is part of the component AP 7.0

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

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







No. Action


Remarks/Subsequent

Steps



SAP Process Integrationrequires a dedicated SAPWeb Application Server.This means that runningapplications in other

clients of the same SAPWeb AS is not supported.

1

After you install SAP Process Integration, import the integrationobjects for mySAP SRM into the SAP Process Integration[page 90].

/


3.5 SRM-MDM Catalog

8/10/2019 176207705-SAP-SRM


No. Action





The use of SAPNetWeaver EnterprisePortal is optional. It isrequired for the integrationof mySAP SRM into aportal.


3.5 SRM-MDM Catalog

8/10/2019 176207705-SAP-SRM


3.5.3.2 ConfigurationFor information about the configuration of this business scenario, refer to the Integrated

Business Content for mySAP SRM in the SAP Service Marketplace under quick link i bc-sr m.

3.5.3.3 Solution Management As central starting point for information about designing, implementing, and keeping yourenterprise’s information technology solution up and running, see the Solution Operation

Guide – mySAP SRM.


3.6 Service Procurement

8/10/2019 176207705-SAP-SRM


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

Overview

Technical System Landscape


3.6.1 Overview

Description

You can use this business scenario to cover the entire service procurement process. Beforeordering external staff or services, you can send a request to one or more suppliers fordetailed information on a specific service or the availability of individual service agents, forexample. After receiving the suppliers’ responses and accepting one of these bids, thecorresponding purchase order is automatically created. Next, time and expenses have to beentered into the system and, finally, the invoice is created.

You can integrate your suppliers into the procurement process by connecting a suppliersystem like Supplier Self-Services to your procurement system. In this way, the serviceagents can enter services performed and create invoices for these services. You have toapprove all documents created by your suppliers and you always retain a complete overviewof all business processes.

For more information, see Business Scenario Descriptions for mySAP SRM.

Process Chain

The following figure shows an example of a Service Procurement process chain:

SERVICE PROCUREMENTRequesting

external staff Processing purchase

orders in SRM

Entering

services

Processinginvoices



8/10/2019 176207705-SAP-SRM






Availability Matrix

The following figure shows the underlying architecture of Service Procurement includingexisting connections.

Firewall

RFC

RFC

RFCIPC

7.0

XML XMLXI Integration

Engine

PI

HTTPSHTTPS / OCI

HTTP(S)

XI Integration

Engine

App li cati on Gateway

SAP NetWeaver

BI 7.0

SAP NetWeaverBI CONT 7.0.2


XI Int.

Engine

IPC

7.0


XI Int.

Engine

SAP SRMServer 5.5

SUS

BSPR/3 3.1i –

SAP ECC 6.0

FI / CO


R/3 Plug_In

SAP SRMServer 5.5

EBP

ITS

R/3 Plug_In

XML

Separate IPC for SUSnot n eeded if SUS

and EBP are

implemented i n thesame SAP system

RFCXI Int.

Engine

XI Proxy

Frame-work

#SRM-

MDMCatalog

1.0

SAPCatalogContent

Mgmt.2.0

#

(# alternative

components)

BSP

TREX 7.0







8/10/2019 176207705-SAP-SRM


Legend:

•

IPC 7.0 is part of the component AP 7.0• No R/3 Plug-ins are needed for ERP 2.0 and higher



8/10/2019 176207705-SAP-SRM









[page 85].

No. Action




[Master Guide – SAP NetWeaver 2004s, part of the

installation package]


requires a dedicated SAPWeb Application Server.This means that runningapplications in otherclients of the same SAPWeb AS is not supported.

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

Integration [page 90].Import the PI content for the following components:


• SAP BI Content 7.0.2

/

1



8/10/2019 176207705-SAP-SRM


No. Action



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



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

2

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

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

• For more information concerning SAP R/3 Plug-Ins,see SAP Service Marketplace at:ser vi ce. sap. com/ r3- pl ug- i n

Not required for customerswith an ERP 2.0 backendsystem. From ERP 2.0onwards, the former plug-in functionalities aredelivered with theSAP_APPL component.Otherwise the installation

of the SAP R/3 Plug-In isrequired if you installed anSAP R/3 system in theprevious step.



• Supplier Self-Service


/



You have to use theinternal SAP ITS, which isintegrated into the SRMServer (SAP ITS 7.0).Note that the external ITSis not supported.

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



/







8/10/2019 176207705-SAP-SRM


No. Action



6 Install SAP®



• Perform the installation steps to set up an RFCconnection.

• Automatic language recognition is not required. Youcan adopt the default settings for document languagesduring the installation of SAP

®NetWeaver 2004s

TREX.



/



You can install a separateSRM Server for SUS oruse the SRM Server youinstalled in step 3 for thatpurpose.

8 Install SAP BI 7.0 plus SAP BI Content 7.0.2:

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


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

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

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

For more information, see the Master Guide – SAPNetWeaver 2004s

The use of the SAP BI isoptional. See thedescription of thiscomponent in Software

Components Overview[page 70] to decide if it isrequired for your businessscenario.

After the BI ABAPupgrade, you should installthe Java parts of BI (BI-Java) to take advantage ofall new functionality. Fordetails, see InstallationGuide – SAP NetWeaver2004s.



8/10/2019 176207705-SAP-SRM



3.6.3.3 Solution Management As central starting point for information about designing, implementing, and keeping yourenterprise’s information technology solution up and running, see the Solution Operation

Guide – mySAP SRM.



3.7 Spend Analysis

8/10/2019 176207705-SAP-SRM


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

Overview



3.7.1 Overview

Description

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

The system landscape can consist of one or more SAP R/3 backend and SAP EnterpriseBuyer systems connected to a single SAP NetWeaver Business Information Warehouse (SAP BI). Analyses are based on documents from Financial Accounting restructured

according to procurement needs. You can enrich document information with category andcontract information from the procurement systems.

Master data has to be consolidated to identify identical suppliers and identical productsstemming from either the same or different systems. For this purpose, you can use AdvancedMaster Data Maintenance included in SAP BI. Advanced Master Data Maintenance providesyou with a mechanism to manually match supplier records and product records.

In addition to that, you can assign standard category schemas from your local systems suchas UNSPSC or ecl@ss to the purchasing categories enabling you to report on consolidated

product categories.For more information on Spend Analysis, see Business Scenario Descriptions for mySAPSRM.

Process Chain

The following figure shows an example of a Spend Analysis process chain:

SPEND ANALYSISCreating key mappings

for suppl iers andproducts

Transferring datafrom operational

systems into SAP BW

Ass ignin g standardcategories to

purchasing categories

Reporting in

SAP BW


3.7 Spend Analysis

8/10/2019 176207705-SAP-SRM






Availability Matrix

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


3.7 Spend Analysis

Legend:



8/10/2019 176207705-SAP-SRM


Legend:

• IPC 7.0 is part of the component AP 7.0

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

3.7.3 Implementation SequenceThis section lists the sequence of steps (installation, technical configuration, applicationconfiguration) required to implement the business scenario.







No Action Remarks/Subsequent


3.7 Spend Analysis


8/10/2019 176207705-SAP-SRM


No. Action



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

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

• For more information concerning SAP R/3 Plug-Ins, seeSAP Service Marketplace at:ser vi ce. sap. com/ r3- pl ug- i n

Not required forcustomers with an ERP2.0 backend system.From ERP 2.0 onwards,the former plug-infunctionalities aredelivered with theSAP_APPL component.

Otherwise the installationof the SAP R/3 Plug-In isrequired if you installed anSAP R/3 system in theprevious step.



• Supplier Self-Services[Installation Guide – SAP SRM Server on <Platform>:<Database>]

/


[SAP@Web Installation Guide]

You have to use theinternal SAP ITS, which isintegrated into the SRMServer (SAP ITS 7.0).Note that the external ITS

is not supported.

4 Install SAP®



/

5 Install SAP BI

1. Install SAP Web AS ABAP 7.00, which includes SAP

BI 7.0 and PI_BASIS 2005_1_700.


2. Configure the database of your SAP Web AS for SAPBI d ib d i SAP N t 567745

After the BI ABAPupgrade, you shouldinstall the Java parts of BI(BI-Java) to takeadvantage of all newfunctionality. For details,see Installation Guide –SAP NetWeaver 2004s.


3.7 Spend Analysis





8/10/2019 176207705-SAP-SRM


No. Action



[Master Guide – SAP NetWeaver 2004s] Portal is optional. It isrequired for the integrationof mySAP SRM into aportal.





www. sdn. sap. com→

Portal Content Portfolio





3.8 Contract Management

3 8 Contract Management

8/10/2019 176207705-SAP-SRM


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

Overview



3.8.1 Overview

Description

The Contract Management business scenario allows you to create, process, and monitorpurchasing contracts and global outline agreements (GOA). It also provides a means torenegotiate existing contracts directly with the vendor or by creating a bid invitation. Acontract can be automatically assigned as a source of supply or displayed as a possibleselection.

A strategic purchaser creates a contract or a GOA whenever a long-term relationship is

anticipated and the vendor can be considered as a source of supply. Contract managementenables purchasers from various parts of the company at different locations to takeadvantage of the terms of globally-negotiated contracts for specific product categories.

You can provide users with specific levels of authorization to contracts and GOAs, and alsocategorize these documents as confidential. You can distribute a GOA to the release-authorized purchasing organizations and these organizations can use the contracts andscheduling agreements created from the distributed GOA. You can use hierarchies toorganize, structure, display, and search for your contracts.

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

For more information on Contract Management, see the Business Scenario Descriptions formySAP SRM.

Tasks

Typical tasks for the Contract Management business scenario include:

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

• A strategic purchaser maintains a global outline agreement database that includest t titi



Process Chain

8/10/2019 176207705-SAP-SRM


Process Chain

The following figure shows an example of a Contract Management process chain.

CONTRACT MANAGEMENTPreparingContracts

NegotiatingContracts

ProcessingGlobal Outline Agreements

MonitoringContracts

ExecutingContracts

AnalyzingProcurement

Data

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

• Classic scenario

• Standalone scenario




• SAP Service Marketplace at

ser vi ce. sap. com/ pl at f orms

Platform Availability Matrix



The following figure shows the underlying architecture of Contract Management.



8/10/2019 176207705-SAP-SRM


(# alternative

components)

Firewall

SAP NetWeaver

BI 7.0IPC

7.0

RFC

SAP NetWeaver BI

CONT 7.0.2

R/3 Plug_In

R/3 3.1i –SAP ECC 6.0

R/3 Plug_In

FI / COMM

(IDOC)

App lic ation Gat eway

HTTP(S)HTTPS / OCI

PI


XML XML

HTTP(S)

XI Integration

Engine

TREX 7.0

XI ProxyFramework

XI Int.

EngineRFC RFC

TREX 7.0(Contracts )

SAP SRM Server

5.5

EBP

ITS

BiddingEngine

XI Int.

Engine

#

SRM-

MDM

Catalog

1.0

SAPCatalog

Content

Mgmt.2.0

BSP

#

XI Proxy

Frame-work



(# alternative

components)

Legend:



3 8 3 Implementation Sequence

8/10/2019 176207705-SAP-SRM


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







[page 85].

No. Action





The use of SAP ProcessIntegration is optional. It isrequired to load contracts into

the catalog, to send productcategory hierarchies to SRM in afile (via PI), or to connect to non-SAP planning or executionsystems.

SAP Process Integrationrequires a dedicated SAP Web

Application Server. This meansthat running applications in otherclients of the same SAP Web ASis not supported.

1

If i t ll d SAP P I t ti i t th



No. Action Remarks/Subsequent Steps

8/10/2019 176207705-SAP-SRM



Download and install the latest SLD Content from SAPService Marketplace at service.sap.com/swdc →

Download → Support Packages and Patches → Entryby Application Group → Additional Components → SAP Master Data for SLD.

/

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



SAP R/3 Enterprise is not part ofthis installation and is not

contained in the installationpackage. A separate SAP R/3Enterprise installation package isrequired.

2

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

• For the installation, see SAP Notes 704564 (R/3plug-in: PI 2004.1 installation/delta upgrade) and

708736 (Release restrictions R/3 Plug-in2004.1).

• For more information concerning SAP R/3 Plug-Ins, see SAP Service Marketplace atser vi ce. sap. com/ r3- pl ug- i n.

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

component.

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

3 Install SAP SRM Server 5.5

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

<Database>]

/


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

You have to use the internal SAPITS, which is integrated into theSRM Server (SAP ITS 7.0). Notethat the external ITS is notsupported.

5 Install SAP Catalog Content Management 2.0 (CCM)

or SRM-MDM Catalog 1.0.



• SAP Note 967088 (regarding SRM MDM

/



No. Action Remarks/Subsequent Steps




8/10/2019 176207705-SAP-SRM



languages during the installation of SAP®

NetWeaver 2004s TREX.

• No Python extensions are required



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

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

8 Install SAP BI:

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

[Installation Guide – SAP Web Application Server

ABAP on <Platform>: <Database>]

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

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


For more information, see the Master Guide – SAPNetWeaver 2004s.

The use of SAP BI is optional.See the description of thiscomponent in SoftwareComponents Overview [page 70] to decide if it is required for yourbusiness scenario.

After the BI ABAP upgrade, youshould install the Java parts of BI(BI-Java) to take advantage of allnew functionality. For details,see Installation Guide – SAPNetWeaver 2004s.



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

10 Import the following Business Packages into theEnterprise Portal:



www.sdn.sap.com→ PortalC f



3.8.3.2 Configuration

8/10/2019 176207705-SAP-SRM


3.8.3.2 Configuration

For information about the configuration of this business scenario, see the configurationdocumentation for mySAP SRM in SAP Solution Manager.




3.9 SAP ERP 2005 – SAP SRM

3.9 SAP ERP 2005 – SAP SRM

8/10/2019 176207705-SAP-SRM


Within SAP ERP 2005, SAP SRM can be deployed in the following ways:

• SAP SRM Server as an add-on to SAP ECC Server (product instance SAP ERP 2005 – SAP ECC) to run SRM in one client of the ERP system. This deployment option isnew in SAP ERP 2005.

• Installation of SAP SRM Server as a separate component to SAP ECC Server.

The following deployment and migration constraints apply:

• SRM as an add-on to mySAP ERP 2005 does not support hubdeployment.

• SAP ERP 2005 with SRM as an add-on does not support any multiplebackend functions for procurement.

• It is not possible to upgrade or migrate from a separately-installed SRMsystem to SAP ERP 2005 with SRM as an add-on.

The following Business Scenarios are available for SAP ERP 2005 – SAP SRM• Self-Service Procurement (classic deployment)

• Self-Service Procurement with Supplier Collaboration for MRO Procurement

• Service Procurement (lean deployment)

• Invoice Management System

• SRM-MDM Catalog or, alternatively, Catalog and Content Management

See the mySAP ERP 2005 Master Guide on the SAP Service Marketplace at

ser vi ce. sap. com/ i nst gui des mySAP Business Suite Solutions mySAP ERP

mySAP ERP 2005

Planning.

4 Software Components Overview

4.1 Softw are Units


8/10/2019 176207705-SAP-SRM


So a e Co po e s O e eThis section provides additional information about the primary software components of thismySAP Business Suite solution.

Only a subset of these components is required for the installation of any singlebusiness scenario. For a scenario-specific overview of components, see thesection Business Scenario Overview.

4.1 Software UnitsTechnically, SAP implements all capabilities and features of mySAP Business Suite solutionsusing a number of mySAP Business Suite components. There are three types of component:

• Application components

• Industry-specific components

• Technology components

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

4.1.1 SRM 2005 Software UnitsThe following application components implement and support mySAP Business Suite cross-industry solutions.

SAP Supplier Relationship Management ServerDefinition

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

SAP Enterprise Buyer is based on SAP NetWeaver Application Server (AS). It is anapplication and database instance installation released on several database and operating

system platforms (see SAP Service Marketplace at ser vi ce. sap. com/ pl at f orms

Platform Availability Matrix). It enables easy, full-cycle, inter-enterprise procurement. With ityou can:

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

A d j t h


4.1 Software Units

By the same means, interested parties can access the bid invitation and submit their bidsdirectly from the marketplace. SAP Enterprise Buyer also supports restricted bid invitations.



8/10/2019 176207705-SAP-SRM


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

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

Use

SAP Enterprise Buyer is the procurement and sourcing system that is the central part of anymySAP SRM scenario. It empowers employees with self-service procurement, enablescentralized direct procurement and provides the professional purchaser with tools to makethe right sourcing decisions.

The mySAP SRM solution requires the SAP Enterprise Buyer system for downloadingmaterials data and (optionally) using the Business Intelligence capabilities offered bySAPNetWeaver.

SAP Bidding Engine

Purchasers can use SAP Bidding Engine to create and process bid invitations, and bidderscan use SAP Bidding Engine to submit bids in response to these bid invitations. Bothpurchasers and bidders can use reverse auction functions in a separate Live Auctionapplication. Purchasers can define rules pertaining to bidding and bidders can submit bids inreal time.

OLTP System

Definition

Online transaction processing system (for example, SAP ERP system) that is used in theSAP Enterprise Buyer environment as a backend system. It is used for materialsmanagement and financials.

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

It is possible to install the SAP Enterprise Buyer system without an OLTP backend in at d l fi ti


4.1 Softw are Units

SAP NetWeaver Business Intelligence

8/10/2019 176207705-SAP-SRM


Definition

Business Intelligence (BI) provides the infrastructure for:

• Data warehousing

• A range of analytical technologies and functions

• Web-based reporting and analysis

• Information Broadcasting to distribute BI content by e-mail or by using the portal eitheras precalculated documents with past data, or as links with live data

• Open analysis interfaces that make available various interfaces for connecting front-end tools of third-party providers

• Web design API, which allows you to implement highly individual scenarios as well asmore demanding applications containing customer-defined interface elements

Business Intelligence Java Components (BI-Java) are used to provide the Java runtimeenvironment for IT scenarios such as Enterprise Reporting, Query and Analysis, and

Business Planning and Analytical Services. BI-Java enables variants such as informationbroadcasting and ad-hoc query & analysis. It also enables Web Dynpro-based BI applicationsand third-party data access via universal data integration.

Use

BI provides the foundation for the SRM scenario Spend Analysis, and can optionally beinstalled for the others. BI includes the complete ABAP stack of the SAP NetWeaver BI datawarehouse and BI platform units.

BI requires AS-ABAP as prerequisite in the same system. Usually, scenarios running on BIalso require BI-Java, AS-Java and EP. Other combinations can be used in one system aswell.

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

Running an Enterprise Portal is an IT scenario whose implementation provides role-based

and secure access to all types of applications, services, and information in an enterpriseportal environment.

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


4.1 Software Units

Implementing a Multitenant Portal Organizations that provide business process outsourcing (BPO) services can develop,configure and operate an enterprise portal that serves as the main management layer of

8/10/2019 176207705-SAP-SRM


configure, and operate an enterprise portal that serves as the main management layer ofthose services.

SAP Catalog Content ManagementSAP Catalog Content Management (SAP CCM) is an ABAP add-on. It consists of anauthoring tool and a search engine.

SAP Catalog Authoring Tool enables the Catalog Manager to use external supplier data tobuild up a unique master catalog. This unique master catalog can be used as a source for

creating procurement catalogs, which are then distributed to SAP Catalog Search Engine foremployee use.

SAP CCM provides the following functions:

SAP Catalog Authoring Tool

1. Upload schema

2. Upload complex service catalogs

This process step is available with SAP Catalog Content Management 2.0 on Basis700 only.

3. Upload supplier product data

If your suppliers use theBusiness Package for Supplier Collaboration, you can enablethem to upload their catalog data themselves. SAP Catalog Content Managementprovides an approval process to support this function.

4. Transfer product data from SRM

5. Transfer contract data from SRM

6. Filter and map products to catalog

7. Enrich product data

8. Check item history

9. Approve product data

10. Define views

11. Publish catalog

SAP Catalog Search Engine


4.1 Softw are Units

Live Auction Cockpit Web Presentation Server

8/10/2019 176207705-SAP-SRM


Live Auction Cockpit Web Presentation Server is a J2EE-based software unit, whichcomprises the following functions:

• Virtual auction floor for reverse auctions

• Real-time monitoring

• Real-time bidding

• Instant messaging (chat)

• Tight integration to all procurement processes

• State-of-the-art user interface

SAP® NetWeaver 2004s Search and Classification(TREX)SAP NetWeaver Search and Classification (TREX) offers an integrated set of services. TREXservices include search and retrieval in large document collections, text mining, automatic

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

SRM-MDM Catalog

The SRM-MDM Catalog is a software component based on SAP NetWeaver MDMtechnology. It combines SAP MDM Server 5.5 with a Java-based and SRM-specific searchenvironment. The Catalog Manager imports, structures and adjusts the catalog content. Heprovides for usergroup-specific masks and – after the content has been confirmed by theCatalog Content Approver – enables the content to be accessible for the catalog users viaWeb browser.

The SRM-MDM Catalog provides the following functions:

1. Import product hierarchy

2. Upload product data from supplier.

3. Map imported hierarchy and products to repository.


4.1 Software Units

11. Enable web content.

12. Browse in catalog and search for catalog items.

8/10/2019 176207705-SAP-SRM


g g

13. Transfer data to procurement system.

4.1.2 Industry-Specific ComponentsIndustry-specific components are used to implement and support industry solutions.Examples of mySAP Business Suite industry-specific components include SAP Automotive,

SAP Media, and SAP Oil &Gas.

mySAP SRM does not contain any industry-specific components.

4.1.3 Technology ComponentsTechnology components are software and middleware components used to implement andsupport solutions of mySAP Business Suite.

SAP NetWeaver Process Integration (PI)

Separate licensing is required for SAP NetWeaver Process Integration if mySAPSRM is used to connect with non-SAP systems or with external trading partners.

SAP NetWeaver Process Integration (PI) consists of core components to model, design,automate, and integrate the processes of one or more application systems. For theintegration of internal and cross-company processes, PI is used to incorporate all the

functions of what was formerly known as Exchange Infrastructure (XI). In addition, PIcontains core components for Business Process Management for application-embedded andapplication-unbounded processes.


4.1 Softw are Units

SAP GUI

8/10/2019 176207705-SAP-SRM


Generally, the latest release of the SAP GUI software (such as SAP GUI 6.20) can be usedwith all previous SAP component releases. As a result, older SAP systems can also benefitfrom the features that are only available in the newer SAP GUI releases, for example supportfor Windows XP.

Use the latest available front-end software.

SAP R/3 Plug-InThe SAP R/3 Plug-In is an interface, which enables the exchange of data between one orseveral SAP R/3 systems and other SAP components. The SAP R/3 Plug-In supplies theSAP components with transaction data and master data in real time. It also makes it possibleto use SAP application components like SAP APO or SAP CRM together with certainindustry-specific components. All SAP industry-specific components based on SAP R/3 4.6Bor higher SAP R/3 releases require an SAP R/3 Plug-In. The SAP R/3 Plug-In is an add-on toSAP R/3.

SAP R/3 Plug-Ins are shipped with SAP application components (SAP APO, SAP BI, SAPBBP, SAP EBP, SAP CRM, and SAP SEM) and with industry-specific SAP components

based on SAP R/3 4.6B or higher SAP R/3 releases. You can order the most recent SAP R/3Plug-In releases free of charge or download them from the SAP Service Marketplace.

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

For more information and for download, see SAP Service Marketplace atser vi ce. sap. com/ r3- pl ug- i n.

SAP NetWeaver Application Server

Definition

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

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

Variant Engines you may operate

ABAP+Java system ABAP Engine and J2EE Engine

Java system J2EE Engine only

ABAP system ABAP Engine only


4.2 Non-SAP Components

Open integration capabilities provide access to existing SAP and non-SAP applications. Allintegration facilities supported by SAP are available with AS. The Java Connector or the.NET Connector give ABAP applications access to Java or .NET components and vice versa.

8/10/2019 176207705-SAP-SRM


gIn addition, the Internet Communication Framework (ICF) enables ABAP programs toprocess and distribute HTTP requests directly. As a consequence, AS can serve as both anHTTP server and a client. It serves as an HTTP server for bringing applications to the uservia a Web browser either directly or via a standard Web server. It serves as an HTTP client toaccess other Web applications for collecting information and data. To complete Webconnectivity, AS provides full support for sending and receiving e-mails via SMTP.

Building Blocks

Usage type AS consists of the following main building blocks: Central instance

Central service instance

The central services instance forms the basis of communication and synchronizationfor the J2EE cluster.

Database instance

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

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

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

Dialog instances, if required

Dialog instances are SAP instances that include only:

Dispatcher, IGS, and CCMS agents

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

For AS-ABAP and AS-Java in one system and AS-ABAP system:

gateway and certain ABAP work processes (dialog, batch, spool, or update)

Dialog instances are installed on application servers.

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

SAP GUI

5 References

5.1 SAP Notes

5 References

8/10/2019 176207705-SAP-SRM


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

SAP Note Number Title

856911 Composite note which collects together all notes relating to theinstallation of SAP SRM 5.0

852894 SRM 5.0 Support Package 01708736 Release restrictions R/3 Plug-in 2004.1

704564 R/3 plug-in: PI 2004.1 installation/delta upgrade

854170 Switching on component "VM Container"

66971 Supported frontend platforms

855827 SAP SRM 5.0 Installation on Windows

855299 SAP SRM 5.0 Installation on UNIX

855897 INST: mySAP ERP 05 ABAP on iSeries

835170 Installation of/Delta Upgrade to CCM 200

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

847019 BI_CONT 7.02: Installation and Upgrade Information

772189 SUS-MM SP02: Important PI Configuration Information

836200 Importing PI content.

877235 Solution Manager Content for SRM 5.0

967088 SRM-MDM Catalog 1.0 Installation

5 References

5.2 Documentation

5.2 Documentation

8/10/2019 176207705-SAP-SRM


Make sure you have the latest documentation version by checking SAP Service Marketplace

at ser vi ce. sap. com/ sr m- i nst → mySAP SRM Using SAP SRM Server 5.5

immediately before starting the installation.

List of referenced documentation for this mySAP Business Suite solution and its businessscenarios.

Relevant for which Bus iness Scenario

M = mandatory / O = opti onal

Title Where to find


P r o

c u r e m e n t

P l a

n - D r i v e n

P r o

c u r e m e n t

S t r

a t e g i c

S o

u r c i n

C a

t a l o g C o n t e n t

M a

n a

e m e n t

S e r v i c e

P r o

c u r e m e n t

S p

e n d A n a l y s i s

C o

n t r a c t

M a

n a g e m e n t

S R

M - M D M C

a t a l o g

InstallationGuide – SAPSRM 5.0 on<Platform>:<Database>

SAP Service Marketplace

at: ser vi ce. sap. com/sr m- i nst

M M M M M M M M

Master Guide

– SAPNetWeaver2004s

Part of the SAP

NetWeaver delivery; SAPService Marketplace at:ser vi ce. sap. com/i nst al l NW2004s

Installation

O M O M O M O M

UpgradeMaster Guide –mySAP SRM

5.0


at: ser vi ce. sap. com/sr m- i nst mySAP

SRM Using SAP SRM

Server 5.5

O O O O O O -- O

InstallationGuide SAPNetWeaver

SAP Service Marketplaceat ser vi ce. sap. com/i nst al l NW2004s

M O M M O O M --

5 References

5.2 Documentation



Title Where to find

8/10/2019 176207705-SAP-SRM






S t r a t e g i c

S o u r c i n


M a n a

e m e n t

S e r v i c e



C o n t r a c t

M a n a g e m e n t

S R M - M D M C

a t a l o g

SAP FrontEndInstallationGuide

SAP NetWeaver 2004sDVD

* Presentation * Server Components * Content Server

M M M M M M M M

InstallationGuide – SAPR/3 Enterpriseon <Platform>:<Database>

Part of the SAP R/3Enterprise delivery, SAPService Marketplace at:

ser vi ce. sap. com/ i nst gui des SAP

Components SAP R/3Enterprise <release>

O O O -- O M O --

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

Part of the SAP R/3delivery, SAP ServiceMarketplace at:ser vi ce. sap. com/

i nst gui des SAPComponents SAP R/3 <release>

O O O -- O M O --

<BusinessScenario>

SAP Service Marketplaceat:ser vi ce. sap. com/ i bc-sr m for mySAP SRM

M M M M M M M M

Solution

OperationGuide –mySAP SRM


at:ser vi ce. sap. com/ sr m-i nst mySAP SRM

Using SAP SRM Server5 5

M M M M M M M M

5 References

5.2 Documentation



Title Where to find

8/10/2019 176207705-SAP-SRM






S t r a t e g i c

S o u r c i n


M a n a

e m e n t

S e r v i c e



C o n t r a c t

M a n a g e m e n t

S R M - M D M C

a t a l o g

Configurationdocumentationfor mySAPSRM 5.0 foreach businessscenario

All configurationdocumentation for mySAPSRM 5.0 is available inSAP Solution ManagerST-ICO 150 contentshipment. Please note:This information isavailable only in theSolution Manager.

Additionally, an SRMimplementation roadmapand an SRM upgraderoadmap are availablethere.

M M M M M M M M

6 Additional Information

6.1 Importing Integration Objects for mySAP SRM on SAP Process Integration


6 1 I ti I t ti Obj t f

8/10/2019 176207705-SAP-SRM


6.1 Importing Integration Objects formySAP SRM on SAP Process Integration

Use

Perform the following procedure to:

• Complete the SAP Process Integration installation for mySAP SRM (for more information,

see section <Your Business Scenario> Implementation Sequence above) or

• Patch the already existing SAP Exchange Infrastructure as part of patching mySAP SRM(for more information, see the corresponding SAP Note Support Package <Number> forSRM 5.0 and section Patching your mySAP SRM Solution [page 91]).

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

If PI content is imported, existing content in the namespaces used by SAP willbe lost. Customer changes in those namespaces will be treated asmodifications and will also be lost. There is no modification adjustmentavailable.

Procedure

1. On the SAP Exchange Infrastructure host (Integration Builder), create the directory<syst emdi r>/ xi / r eposi t ory_ser ver / i mpor t if it does not already exist.

<syst emdi r > is the system directory that you specified during the installation

of the SAP Exchange Infrastructure server.

2. Copy all *. TPT files from <SRM- XI Cont ent CD>/ TPT to the directory<syst emdi r>/ xi / r eposi t ory_ser ver / i mpor t .

If you want to patch the existing SAP Exchange Infrastructure as part of


6.2 Patching your mySAP SRM Solution

For more information, see the SAP Process Integration online documentation athel p sap com SAP NetWeaver Process Integration SAP Exchange

8/10/2019 176207705-SAP-SRM


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

Successfully imported files get automatically moved to the directory<syst emdi r>/ xi / r eposi t ory_ser ver / i mpor t edFi l es.

2. Patch your SAP components according to this SAP Note Support Package <Number> forSRM 5.0:

4. Choose Object Import XI 3.0 Development Object.

hel p. sap. com SAP NetWeaver Process Integration SAP Exchange

Infrastructure Design and Configuration Time Integration Builder.

1. Check SAP Service Marketplace at the Internet address: service.sap.com/patches

SAP Support Packages in Detail Schedules for Support Packages SRM SupportPackage Schedule EBP 5.0 (SRM 4.0) Support Package Schedule for the number ofthe latest released Support Package and the corresponding SAP Note Support Package<Number> for SRM 5.0.

To patch your mySAP SRM solution (for example, from SRM 4.0 SP02 to SRM 4.0 SP03),proceed as follows:

6.2 Patching your mySAP SRM Solution

• You can obtain required support packages / binary patches from SAP ServiceMarketplace at the Internet address: service.sap.com/patches Entry by

Application Group SAP Application Components SRM (WITH EBP) SRM5.0.

• For general information about installing Java Support Packages with Java SupportPackage Manager (JSPM), see the SAP Help Portal at help.sap.com ->Documentation -> SAP NetWeaver -> SAP NetWeaver 2004s -> SAP NetWeaverLibrary -> SAP NetWeaver -> Key Capabilities of Solution Life Cycle Management ->Software Life-Cycle Management -> Software Maintenance -> Java Support PackageManager .

• If required, patch the existing SAP Exchange Infrastructure according to sectionImporting Integration Objects for mySAP SRM on the S AP Process Integration [page 90].

7 Media Information

7 Media Information

Software Components and DVD / CD Structure

8/10/2019 176207705-SAP-SRM


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

The material numbers of the corresponding DVDs and CDs may change as new updates become necessary. Therefore, make certain that you

always use the most up-to-date version of the indicated data carrier(s).

The following table lists the software components that belong to SAP SRM 5.0. For more information about the SAP NetWeaver media list, go toser vi ce. sap. com/ i nst al l NW2004s or ser vi ce. sap. com/ upgr adeNW2004s. For more information about the SAP Solution Manager media list, go to

ser vi ce. sap. com/ i nst gui des SAP Components SAP Solution Manager Release 4.0 Media List SAP Solution Manager 4.0.

Before you attempt to install any of the following components, ensure that you are using the current version of the installation documentation. For SAP NetWeaver

’04s, you can find the relevant guides at ser vi ce. sap. com/ i nst gui desNW2004s Installation; the SRM installation guides are located at

ser vi ce. sap. com/ sr m- i nst

Using SAP SRM Server 5.5.

Furthermore, we recommend that you visit the SAP Software Distribution Center in SAP Service Marketplace at ser vi ce. sap. com/ swdc. Within the SAP

Software Distribution Center, you can download any SAP software component(s) to which your enterprise is entitled. The corresponding authorizations areautomatically generated from the licenses. To obtain the software you require, you can either download the corresponding files directly (by simply clicking on thefile name) or you can use the SAP Download Manager.

SAP SRM Support Package (SP4) is based on Support Package Stack 07 of NetWeaver 2004s. For more information on Support Package stacks,

consult SAP Service Marketplace at ser vi ce. sap. com/ sp- st acks . Also review the corresponding Release and Information Notes (RIN). For

your convenience, SAP Note 852894 lists all components that are relevant for SRM 5.0.

92 November 2006

7 Media Information

mySAP SRM 5.0 SR2 Components DVD / CD Label Descript ion / Addi tional Information

mySAP Business Suite 2005SAP Installation Master for:

SAP ERP 2005 SR2, SAP NETWEAVER 2004S SR2,SAP SRM 5 0 SR2 SAP SCM 5 0 SR2

The Installation Master is the starting point for installing SAP SRM 5.0. It is

also used to install new Dialog instances and IGS instances

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

http://service.sap.com/swdc

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

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

http://service.sap.com/swdc

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

8/10/2019 176207705-SAP-SRM


93 November 2006

SAP SRM 5.0 SR2, SAP SCM 5.0 SR2,SAP CRM 5.0 SR2

SAP SRM 5.0 SR2SAP SRM Server 5.5SAP Installation Export

Contains required installation files for SAP SRM 5.0 (in folders EXP1-EXP3)

SAP SRM 5.0 SR2SAP SRM Server 5.5SAP Upgrade Master DVD.

The Upgrade Master is the starting point for upgrading to SAP SRM 5.0

SAP SRM 5.0 SR2SAP SRM Server 5.5SAP Upgrade Export DVD

Contains required upgrade files for SAP SRM 5.0 in folders UPG1-UPG4

SAP SRM 5.0 SR2SAP Language DVDLanguages DE, EN, ES, FR, IT, NL, CA, CSDA, EL, FI, HU, NO, PL, PT, RU, SK, SVTR, JA, KO, TH, ZF, ZH

Contains language files for installation and upgrade of SAP SRM 5.0 infolders LANG1-LANG3

SAP NetWeaver 2004S SR2SAP Kernel 7.00

<Operating System><Database>

Contains SAP Kernel files for NetWeaver 2004s AS ABAP, ECC 6.0 ABAP

System and SRM 5.0 ABAP System (for installation and upgrade)

<Database Version>, RDBMS, <Operating System> Media for database software

SAP SRM Server 5.5 (leading component of SAP SRM 5.0)

<Database>, <Database Documentation> Database documentation (available for Oracle only)

SAP Catalog Content Management (SAP CCM) 2.0SAP CATALOG CONT.MGMT. 2.0_640SAP CATALOG CONT.MGMT. 2.0_700

Add-On Installation/Upgrade <Operating System>

Contains SRM Add-On Installation of SAP Catalog Content Management 2.0and XI Content for SAP CCM

SAP XI Content for CCM 2.0, 700 SAP Catalog Content Management 2.0

SAP XI Content for SRM Server 5.5SAP SRM 5.0 SR2SRM ComponentscProjects, Portal Content, XI Content

Contains XI Content for SAP APPL 46C, 46B, 470, 500, 600 and XI Contentfor SRM Server 5.5

8/10/2019 176207705-SAP-SRM


http://help.sap.com/

176207705-sap-srm

Documents