SAP SRM

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

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

© Copyright 2004 SAP AG. All rights reserved. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and No part of this publication may be reproduced or transmitted in any

other SAP products and services mentioned herein as well as their

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

respective logos are trademarks or registered trademarks of SAP AG

The information contained herein may be changed without prior

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

notice.

product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves

Some software products marketed by SAP AG and its distributors

informational purposes only. National product specifications may

contain proprietary software components of other software vendors.

vary.

Microsoft, Windows, Outlook, and PowerPoint are registered

These materials are subject to change without notice. These materials

trademarks of Microsoft Corporation.

are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of

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

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

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

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

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

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

Tivoli, and Informix are trademarks or registered trademarks of IBM

warranty statements accompanying such products and services, if any.

Corporation in the United States and/or other countries.

Nothing herein should be construed as constituting an additional warranty.

Oracle is a registered trademark of Oracle Corporation. SAP Library document classification: PUBLIC UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

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

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

change in these components may cause unpredictable and severe

VideoFrame, and MultiWin are trademarks or registered trademarks of

malfunctions and is therefore expressively prohibited, as is any

Citrix Systems, Inc.

decompilation of these components.

HTML, XML, XHTML and W3C are trademarks or registered

Any Java™ Source Code delivered with this product is only to be used

trademarks of W3C®, World Wide Web Consortium, Massachusetts

by SAP’s Support Services and may not be modified or altered in any

Institute of Technology.

way.

Java is a registered trademark of Sun Microsystems, Inc. Documentation in the SAP Service Marketplace JavaScript is a registered trademark of Sun Microsystems, Inc., used

You can find this documentation at the following address:

under license for technology invented and implemented by Netscape.

http://service.sap.com/xxxxxxxx

MaxDB is a trademark of MySQL AB, Sweden.

Typographic Conventions

Icons Icon

Meaning

Type Style

Description

Example Text

Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Caution

Cross-references to other documentation

Recommendation

Example text

Emphasized words or phrases in body text, graphic titles, and table titles

EXAMPLE TEXT

Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text

Output on the screen. This includes file and directory names 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 are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT

Keys on the keyboard, for example, F2 or ENTER.

Example Note

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help → General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Master Guide – mySAP SRM

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

Implementation

Operation

Upgrade

SAPterm

SAP Library

Upgrade Master Guide

Master Guide

Component Upgrade Guide

Component Installation Guide Security Guide Configuration Documentation

Release Notes

Implementation Guide (IMG)

Delta and Upgrade IMG

Solution Management Guide

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

Target group: Relevant for all target groups

•

Current version: Located in the SAP Help Portal at help.sap.com → Additional Information → Glossary (direct access) or Terminology (as terminology CD) In the SAP-System in transaction STERM

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

Target group: Consultants System administrators Project teams for implementations or upgrades

4

November 2006


•

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 customer requirements. Its structure and documentation are component-oriented. •

Target group: Solution consultants Project teams for implementations or upgrades

•

Current version: 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 suggestions for raising security levels. A collective security guide is available for the SAP NetWeaver technologies like SAP Web Application Server (SAP Web AS). This document contains general guidelines and suggestions about system security. mySAP SRM has a Security Guide of its own. •

Target group: Technology consultants Solution consultants Project teams for implementations or upgrades

•

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

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

Target group: Technology consultants System administrators Project teams for implementations

•

Current version: Located in the SAP Service Marketplace at service.sap.com/instguides-> mySAP Business Suite Solutions -> mySAP SRM

November 2006

5


Component Installation Guide The Component Installation Guide describes the technical implementation of an SAP component, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. •

Target group: Technology consultants Project teams for implementations

•

Current version: Located in the SAP Service Marketplace at service.sap.com/instguides -> 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 the configuration of SAP solutions and business scenarios. It contains IMG activities and transactions as well as documentation and references to the relevant SAP Notes. The SRM 5.0 configuration documentation is delivered with the ST-ICO 150 content shipment for Solution Manager. The Solution Manager content replaces the Business Scenario Configuration Guides, which were delivered with earlier SRM shipments. •

Target group: Solution consultants Project teams for implementation

•

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

Production operation Solution Operation Guide The Solution Operation Guide is the starting point for operating an SAP solution. The guide refers 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 refers users to other documents, for example, the SAP Library, the Master Guide, and the Component Management Guides. •

Target group: System administrators Technology consultants Solution consultants Project teams for implementations or upgrades

•

Current version: Located in the SAP Service Marketplace at service.sap.com/instguides-> mySAP Business Suite Solutions -> mySAP SRM

6

November 2006


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

Target group: Technology consultants Project teams for upgrades

•

Current version: Located in the SAP Service Marketplace at service.sap.com/instguides -> 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 not describe any business-related configuration. •

Target group: Technology consultants Project teams for upgrades

•

Current version: Located in the SAP Service Marketplace at service.sap.com/instguides → mySAP Business Suite Solutions → mySAP SRM

Release Notes Release notes are documents that contain short descriptions of new features or changes in an 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

•

Current version: Located in the SAP Service Marketplace at service.sap.com/releasenotes In the SAP menu of the SAP system under Help → Release information

November 2006

7


Contents 1 Getting 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 Solution-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 Relationship Management .........................................................................................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.2 Technical System Landscape .......................................................... 34 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 3.3.2 Technical System Landscape .......................................................... 41 3.3.3 Implementation Sequence ................................................................ 43 3.3.3.1 Installation................................................................................................................43 3.3.3.2 Configuration............................................................................................................47 3.3.3.3 Solution Management..............................................................................................47 3.3.3.4 Upgrade ...................................................................................................................47

3.4 Catalog Content Management ......................................................48 3.4.1 Overview ............................................................................................ 48 3.4.2 Technical System Landscape .......................................................... 48 3.4.3 Implementation Sequence ................................................................ 50

8

November 2006


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.2 Technical System Landscape .......................................................... 53 3.5.3 Implementation Sequence ................................................................ 55 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.2 Technical System Landscape .......................................................... 59 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.7.2 Technical System Landscape .......................................................... 66 3.7.3 Implementation Sequence ................................................................ 67 3.7.3.1 Installation................................................................................................................67 3.7.3.2 Configuration............................................................................................................69 3.7.3.3 Solution Management..............................................................................................69 3.6.3.4 Upgrade ...................................................................................................................69

3.8 Contract Management ...................................................................70 3.8.1 Overview ............................................................................................ 70 3.8.2 Technical System Landscape .......................................................... 71 3.8.3 Implementation Sequence ................................................................ 73 3.8.3.1 Installation................................................................................................................73 3.8.3.2 Configuration............................................................................................................76 3.8.3.3 Solution Management..............................................................................................76 3.8.3.4 Upgrade ...................................................................................................................76

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

4 Software Components Overview ................................................78 4.1 Software Units ................................................................................78 4.1.1 SRM 2005 Software Units ................................................................. 78 4.1.2 Industry-Specific Components ........................................................ 83 4.1.3 Technology Components ................................................................. 83

4.2 Non-SAP Components...................................................................85

5 References ....................................................................................86 5.1 SAP Notes.......................................................................................86 5.2 Documentation ...............................................................................87

November 2006

9


6 Additional Information .................................................................90 6.1 Importing Integration Objects for mySAP SRM on SAP Process Integration..............................................................................90 6.2 Patching your mySAP SRM Solution ...........................................91

7 Media Information ........................................................................92

10

November 2006

1 Getting Started

1 Getting Started This Master Guide for mySAP™ Supplier Relationship Management (mySAP SRM) provides a central starting point for the technical implementation of mySAP SRM. To facilitate the implementation process, all information within this document is organized by scenario. You can choose from several generic business scenarios and find all the information relevant for the technical implementation of a specific business scenario in that section. Each business scenario supports a number of variants. In this Master Guide only key variants are described in detail.

For information about upgrading the mySAP SRM business scenarios, see the Upgrade Master Guide – mySAP SRM. This guide provides information about the overall upgrade sequences, references to related documentation, SAP Notes, and additional upgrade information for each business scenario of mySAP SRM. The Upgrade Master Guide is available on SAP Service Marketplace at service.sap.com/srm-inst. The complete mySAP SRM solution consists of the following top-level scenarios and business scenarios:

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

Plan-Driven Procurement Plan-Driven Procurement automates and streamlines ordering processes for regularly needed core materials. Since mySAP SRM is integrated with planning, design, and order-processing systems, you can link your procurement processes to a plan-driven strategy that gets you the materials you need for core business processes — exactly when you need them. Plan-Driven Procurement integrates seamlessly with backend systems such as enterprise planning and production systems. The scenario allows you to integrate operational procurement with your existing supply chain management solution.

Service Procurement E-procurement has produced great opportunities for saving costs in the purchasing process. However, companies generally fail to extend cost saving measures to services, even though services amount to more than 50% of annual purchasing volumes. The Service Procurement business scenario within mySAP SRM covers a wide range of services such as temporary labor, consulting, maintenance, and facility management.

Catalog Management There are two business scenarios at your disposal that allow for creating, maintaining, and managing catalog content within your e-procurement application: • Catalog Content Management (CCM) • SRM-MDM Catalog

November 2006

11

1 Getting Started

Strategic Sourcing

The sourcing application in SAP Enterprise Buyer provides professional purchasers with 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 determine the best source of supply. Once you have done this, you can create a purchase order or contract directly from the sourcing application or SAP Bidding Engine. You can then save it either locally or in the backend system, depending on the technical scenario you are using (classic, extended classic, or standalone). Spend Analysis

Spend Analysis is a decision-support application that enables you as a purchaser to analyze your total spending across system and organizational boundaries. You can perform the analysis per supplier, per product, or per product category. Contract Management

Contract Management provides a solution for creating purchasing contracts and global outline agreements (GOA) and for changing them. It also provides a means to renegotiate 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 a possible 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 and related 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 the rest of the document The software component matrix that provides an overview of which business scenarios use which components and if the corresponding component is mandatory or optional Minimal system landscape Overall installation sequence

•

Business Scenarios of mySAP SRM [page 26] contains the following information for each business scenario of this solution: An overview of the business scenario Examples of how the different components interact, and what protocols and interfaces are used, including technical system landscape examples Information about the overall installation sequence and subsequent steps References to related installation guides Information about mutual dependencies that affect two or more components within the business scenario

12

•

Software Components Overview [page 70] contains a short description of every software component that is part of this solution.

•

Depending on the specific business scenarios to be implemented, many different installation guides and the configuration documentation may be required during the business scenario implementation process. The SRM 5.0 implementation content is clearly organized according to activity: installation or configuration. The installation

November 2006

1 Getting Started

documentation is covered in installation guides available at the SAP Service Marketplace. The configuration documentation is only available within SAP Solution Manager Content ST-ICO 150. In References [page 85] you can find an overview of all documentation referenced in this Master Guide.

You can find the most current information about the technical implementation of this mySAP Business Suite solution and the latest installation guides in SAP Service Marketplace at: service.sap.com/srm-inst. We strongly recommend that you use the documents available there. The guides 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 to patch your solution from Support Package 02 to Support Package 03).

November 2006

13

1 Getting Started 1.1 Related Information

1.1 Related Information The following list contains links to important information for implementing this mySAP Business 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 and SAP SRM Server, links to related SAP Notes

service.sap.com/srm-inst → mySAP SRM → Using SAP SRM Server 5.5

Released platforms

service.sap.com/platforms → Product Availability Matrix

Security Guide – mySAP SRM 5.0. Provides cross-component security information for mySAP SRM; explains security aspects relevant for system landscape design, network and communication security, and user administration and authentication.

service.sap.com/srm-inst → mySAP → SRM Using SAP SRM Server 5.5

(This document will be available at the end of 2005.) General information about security for SAP systems.

service.sap.com/security

SAP Solution Manager

service.sap.com/solutionmanager

SAP R/3 plug-in releases and availability

service.sap.com/R3-plug-in

Hardware sizing

service.sap.com/sizing

Information about SRM components and further documents

service.sap.com/srm → mySAP SRM in Detail

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

service.sap.com/sp-stacks

Download of SAP software (SAP Software Distribution Center)

service.sap.com/swdc

14

November 2006

1 Getting Started 1.2 SAP Solution Manager

1.2 SAP Solution Manager SAP provides the SAP Solution Manager as the platform to efficiently support the implementation and operation of your mySAP SRM solution. Using SAP Solution Manager significantly accelerates the implementation process and helps you to achieve your business goals. SAP Solution Manager contains predefined implementation content (IMG activities and transactions as well as documentation and SAP Notes) that help you to configure your SRM Solution. In addition, SAP delivers Support Services based on the business scenarios designed and documented in SAP Solution Manager. The use of SAP Solution Manager is mandatory for mySAP SRM 5.0. When you install SAP SRM Server 5.5 or upgrade to this release, you are asked to enter a key generated by the Solution Manager. For more information, see the installation or upgrade guide for SAP SRM Server 5.5. In mySAP SRM 5.0, the SAP Solution Manager contains standard implementation content for 7 business scenarios, covering all key capabilities of the mySAP SRM Solution Map. This enables 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 during Ramp-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 SAP Solution Manager

Document, configure and test the previously defined business processes. Train end 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 Solution Manager: Master Guide – SAP Solution Manager available on SAP Service Marketplace at service.sap.com/instguides Æ SAP Components Æ SAP Solution Manager Guides

•

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

•

For additional information about using the SAP Solution Manager content for SRM 5.0, see SAP Note 877235.

•

Additional information: SAP Service Marketplace at service.sap.com/solutionmanager and in the documentation Master Guide SAP NetWeaver 2004s available at service.sap.com/instguidesNW2004s

The following information summarizes installation considerations: •

Each mySAP SRM (or SAP NetWeaver) system landscape must be assigned to an installation of the SAP Solution Manager. SAP Solution Manager is the required platform to efficiently support the implementation and operation of your SAP solution. In the event of a support relevant incident within your SAP system landscape, SAP

November 2006

15

1 Getting Started 1.3 Important 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 to manage the solution you build up with SAP NetWeaver and mySAP SRM as well. In this case, it is highly recommended that you update SAP Solution Manager and Solution 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 Manager as a central component. Instead, operate a two system landscape with test and production environment of SAP Solution Manager, especially if you are using time critical functions like Support Desk. If you also develop your own content, a threesystem landscape with development, test and production environment is recommended.

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

Title

Description

Composite note which collects together all notes relating to the installation of SAP SRM 5.0

This composite SAP Note is crucial for the SAP SRM 5.0 installation. It is a collection of all SAP Notes relating to its installation.

852894

SRM 5.0 Support Package 01

Release and Information Note

708736

Release restrictions R/3 Plug-in 2004.1

This SAP Note contains information about restrictions to the productive use that is important for the installation of the SAP R/3 Plug-In.

704564

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

This SAP Note is required to install the SAP R/3 Plug-In. For more information, see SAP Service Marketplace at: service.sap.com/r3-plug-in

856911

854170

66971

16

Switching on component "VM Container"

Supported frontend platforms

It also contains all information relating to the SAP SRM installation that was not available when the installation guide was published.

This note is required to enable the Virtual Machine Container (VMC), which is part of the SAP Basis 7.00. The VMC must be enabled for the IPC component, which is itself installed automatically with the SAP_AP 7.0. Supported Microsoft Windows releases for the standard SAP GUI.

November 2006

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.0 Installation on UNIX

Additional information for installation on a UNIX operating system.

855897

INST: mySAP ERP 05 ABAP on iSeries

Additional information for installation on iSeries.

835170

Installation of/Delta Upgrade to CCM 200

This SAP Note contains information about carrying out an Add-On installation/delta upgrade with transaction SAINT.

SRM-MDM Catalog 1.0 Installation & Configuration

This SAP Note contains information about carrying out an installation and configuration of SRM-MDM Catalog 1.0.

9670088

November 2006

17

1 Getting Started 1.4 History of Changes

1.4 History of Changes The regularly updated Master Guide is available in the SAP Service Marketplace at service.sap.com/srm-inst.

Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace immediately before starting the installation. The following table provides an overview of the most important changes that were made in the 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 scenario incorporated; information on Enterprise SOA added

1.6 (November 9, 2006)

Minor changes for Support Release 2

18

November 2006

2 mySAP SRM Overview 2.1 Software Component Matrix

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

Overview of Components SAP NetWeaver Portal 7.0 SAP NetWeaver AS Java 7.0 SAP SRM Server 5.5 EBP (*alternative components )

Bidding Engine

SRM-MDM Catalog 1.0

*

SAP Catalog * Content Mgmt 2.0

SUS

SAP NetWeaver BI 7.0

LAC WPS 5.0 TREX 7.0 JCo

Application Platform (Including SAP IPC 7.0) SAP WebAS ABAP 7.0 (Incl. ITS 7.0)

for SAP NetWeaver

JVM

SAP WebAS Java 7.0

SAP NetWeaver usage type Process Integration (PI) SAP WebAS ABAP 7.0

SAP WebAS JAVA 7.0

2.1 Software Component Matrix This section provides an overview of which business scenarios use which components in this mySAP Business Suite solution.

Note that for each component listed below there are software requirements which are not explicitly mentioned in this documentation. Component-specific software requirements are documented for a component in its installation guide. All related implementation guides are listed in References [page 85].

For latest Support Package and patch level requirements, see SAP Service Marketplace at service.sap.com/sp-stacks → SAP SRM 5.0 and the

November 2006

19

2 mySAP SRM Overview 2.1 Software Component Matrix 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 Support Release 01, see SAP Note 852894. The exact locations of the required software components on the corresponding DVD(s) and CD(s) which are shipped with the SAP SRM 5.0 package can be found under http://service.sap.com/instguides Æ mySAP Business Suite Solutions Æ mySAP SRM. Business Scenario / Software Component Matrix (M = mandatory / O = optional)

Plan-Driven Procurement

Strategic Sourcing

Catalog Content Management

Service Procurement

Spend Analysis

Contract Management

SRM-MDM Catalog

Business Scenario

Self-Service Procurement

Software Component

M

M

M

M

M

M

M

M

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

--

M

--

O

--

O

--

O

M

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) SAP® Internet Transaction Server (SAP ITS) 7.00 Note: Only the internal ITS is supported.

®

SAP SRM-MDM Catalog 1.0 ®

(1)

SAP NetWeaver 2004s Search and Classification (TREX)

M

O

O

M

O

--

O

--

SAP® Enterprise Portal 7.0 (Portal Server)

O

O

O

O

O

O

O

O

Business Packages for SAP NetWeaver Enterprise Portal 7.0: •

Business Package for SRM (5.0)

O

O

O

O

O

O

O

O

•

Business Package for Supplier Collaboration (2.0)

O

O

O

O

O

--

--

--

Live Auction Cockpit Web Presentation Server (LACWPS) 5.0

--

--

O

--

--

--

--

--

SAP® NetWeaver Usage Type Process Integration (PI)

O

M

O

O

O

O

O

O

Process integration content (PI content) for

20

November 2006

2 mySAP SRM Overview 2.1 Software Component Matrix


Strategic Sourcing

Catalog Content Management

Service Procurement

Spend Analysis

Contract Management

SRM-MDM Catalog

Business Scenario


Software Component

•

SAP SRM Server 5.5

--

M

O

--

O

--

O

--

•

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

O

O

O

--

O

O

O

--

(SAP R/3 4.6C or higher recommended) SAP R/3 Plug-In 2004.1 or higher if one is available (1)

O

O

O

--

O

O

O

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 as vendor texts, internal notes, and attachments.

November 2006

21

--

2 mySAP SRM Overview 2.2 Solution-Wide Topics

2.2 Solution-Wide Topics 2.2.1 Minimal System Landscape In the mySAP SRM solution, you can install all software components (ABAP and non-ABAP components) as shown in the figure below.

Enhanced requirements on performance, scalability, high availability, and security reasons cannot be met by such a minimal system landscape. For information on creating productive system landscapes, see SAP Service Marketplace at service.sap.com/ti. The installation of this minimal system landscape is possible only if you choose an operating system and a database that supports all components. For more information about released platforms for mySAP SRM, see SAP Service Marketplace at service.sap.com/platforms → Product Availability Matrix. Furthermore, you must provide a sufficiently sized server. For information on sizing, see SAP Service Marketplace at service.sap.com/sizing. 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 AS is not supported.

22

November 2006


Single Host Installation of mySAP SRM

# 100 EBP # 200 SUS # 300 BW # 500 Catalog Search # 500 Catalog Auth. SRM-Server 5.5 Catalog 2.0 (Add-on) PI_BASIS

AS-ABAP 7.0

EP 7.0

IPC 7.0

Search and Classification

LAC WPS 5.0 AS-Java 7.0

Database

Process Integration (PI) AS-ABAP 7.0

EBP and SUS can also run in one client. For more information, see the SAP Implementation Guide (SAP IMG), activity Determine Back-End System. With regard to catalog management, this figure shows only an example installation. You can use SRM-MDM Catalog as an SAP NetWeaver-based alternative to SAP CCM.

November 2006

23


2.2.2 Overall Installation Sequence The following figure contains the installation sequence of mySAP SRM containing the components of all business scenarios of mySAP SRM.

Depending on the business scenarios of mySAP SRM that you want to implement, your installation sequence may only contain a subset of these software components. For more information concerning the installation sequence of each business scenario, see section → Implementation Sequence. Software components on the same level can be installed at the same time on the appropriate machine (for example, different project groups could install SAP R/3 and SAP PI simultaneously). This is important to know if you want to implement more than one mySAP SRM business scenario at a time.

Installation Sequence of mySAP SRM SAP PI

SRM Server

SRM Server

SAP R/3

SAP EP

(SUS)

(EBP)

Time

SAP ITS

SAP BI

SAP IPC*

SAP CCM

LAC WPS

TREX

SAP IPC*

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.

* IPC. See SAP Note 854170. This note is required to enable the Virtual Machine Container (VMC), which is part of the SAP Basis 7.00. The VMC must be enabled for the IPC component, which is itself installed automatically with the SAP_AP 7.0. With regard to catalog management, the above figure shows only an example installation. You can use SRM-MDM Catalog as a SAP NetWeaver-based alternative to SAP CCM.

24

November 2006

2 mySAP SRM Overview 2.3 Enterprise SOA Enablement of mySAP Supplier Relationship Management

2.3 Enterprise SOA Enablement of mySAP Supplier Relationship Management The initial enterprise service-oriented architecture (enterprise SOA) enablement of mySAP Supplier Relationship Management is part of the SAP-wide activities to standardize the interfaces 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.

November 2006

25

3 Business Scenarios of mySAP SRM 3.1 Self-Service Procurement

3 Business Scenarios of mySAP SRM This Master Guide provides just one way to implement each business scenario. For other ways to implement business scenarios, see the Scenario & Process Component List in SAP Service Marketplace (service.sap.com/scl). The Scenario & Process Component List helps you to find realization alternatives for SAP solutions, business scenarios and processes. It shows you which application components are needed to realize a business scenario or process.

3.1 Self-Service Procurement For 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 own requirement requests. This relieves your purchasing department of a huge administrative burden while making the procurement process both faster and more responsive. For more information on Self-Service Procurement, see the Business Scenario Descriptions for 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 The following figure shows an example of a Self-Service Procurement process chain:

SELF-SERVICE PROCUREMENT Requisition

26

Approval

Ordering

Goods Received

Invoice Handling

Payment

Accounting

November 2006


Deployment Options The following section describes the deployment options that are supported for Self-Service Procurement. However, the open and flexible design of SAP Enterprise Buyer also allows you to combine the described deployment options. •

Classic deployment You implement the SAP Enterprise Buyer system and one or more ERP systems. All Materials Management (MM) is mapped in the ERP system. Accounting (FI) and Controlling (CO) are processed in the ERP system.

•

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

•

The standalone deployment In this deployment scenario, you have no Materials Management (MM) in your ERP system and are using the Materials Management functions in the SAP Enterprise Buyer 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 the business scenario to meet your needs, see: •

the section Minimal System Landscape [page 22]

•

SAP Service Marketplace at service.sap.com/platforms Æ Platform Availability Matrix

November 2006

27

3 Business Scenarios of mySAP SRM 3.1 Self-Service Procurement The following figure shows the underlying architecture of Self-Service Procurement.

Application Gateway

HTTPS / OCI

HTTP(S)

Firewall BSP # alternative components

# SRMMDM Catalog 1.0

ITS SAP NetWeaver BI 7.0

# SAP Catalog Content Mgmt. 2.0

BI CONT 7.0.2

SAP SRM Server 5.5

R/3 Plug_In

EBP

IPC 7.0

R/3 3.1i – SAP ECC 6.0 MM

FI / CO

R/3 Plug_In (IDOC)

XI Int. Engine

XI Proxy Framework

XI Proxy

RFC

Framework

XI Int. Engine

RFC

TREX 7.0 RFC

HTTP(S)

XML

XI Content: SAP SRM Server 5.5

XI Integration Engine

XML

PI

XI Content: SAP Catalog Content Management 2.0

Legend:

28

•

IPC 7.0 is part of the component AP 7.0

•

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

November 2006


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

•

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

•

Also see section Overall Installation Sequence [page 24], especially if you want 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

Remarks/Subsequent Steps

[Corresponding Documentation] 1

Install SAP Process Integration. [Master Guide – SAP NetWeaver 2004s]

The use of SAP Process Integration is optional. It is required for outbound XMLbased messaging or for connecting non-SAP planning or execution systems.

SAP Process Integration requires a dedicated SAP Web Application Server. This means that running applications in other clients of the same SAP Web AS is not supported. If you installed SAP Process Integration, import the integration objects for mySAP SRM into the SAP Process Integration [page 90]. Import the PI content for the following components: •

SRM Server 5.5

•

SAP Catalog Content Management 2.0 (not necessary if you run SRM-MDM Catalog instead)

•

SAP BI Content 7.0.2

November 2006

/

29


No.

Action


[Corresponding Documentation] Download and install the latest SLD Content from SAP Service Marketplace at service.sap.com/swdc → Download → Support Packages and Patches → Entry by Application Group → Additional Components → SAP Master Data for SLD. 2

Install/Integrate SAP R/3 or SAP R/3 Enterprise (SAP R/3 4.6C or higher recommended). [SAP R/3 Installation on : , or Installation Guide – SAP R/3 Enterprise on : ] Install SAP R/3 Plug-In (2004.1 or higher if one is available):

3

•

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 PlugIns, see SAP Service Marketplace at service.sap.com/r3-plug-in.

Install SAP SRM Server 5.5

/

SAP R/3 and SAP R/3 Enterprise are not part of this installation and are not contained in the installation package. A separate SAP R/3 or SAP R/3 Enterprise installation package is required. Not required for customers with an ERP 2.0 backend system. From ERP 2.0 onwards, the former plug-in functionalities are delivered with the SAP_APPL component. Not required if exclusively local PO handling is performed or no SAP R/3 system is used as backend system. /

[Installation Guide – SAP SRM Server on : ] 4

Install SAP Internet Transaction Server (7.00) [SAP@Web Installation Guide located on the SAP Server Components CD]

5

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

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

/

For information, see: •

SAP Note 835170 (regarding SAP-CCM)

•

SAP Note 967088 (regarding SRM-MDM Catalog)

Install SAP® NetWeaver 2004s Search and Classification (TREX)

6

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

30

•

Perform the installation steps to set up an RFC connection

•

Automatic language recognition is not required. You can adopt the default settings for document

/

November 2006


No.

Action


[Corresponding Documentation] languages during the installation of SAP® NetWeaver 2004s TREX. •

No Python extensions are required

[SAP NetWeaver 2004s Installation Guide: Search and Classification (TREX)] 7

Install SRM Server for SAP SUS. [Installation Guide – SRM Server on : ]

8

Install SAP BI: 1. Install SAP Web AS ABAP 7.00, which includes SAP BI 7.0 and PI_BASIS 2005_1_700. [Installation Guide – SAP Web Application Server ABAP on : ] 2. Configure the database of your SAP Web AS for SAP BI as described in SAP Note 567745. 3. Install SAP BI Business Content Add-On BI_CONT 7.0.2 on the SAP Web AS ABAP system as described in SAP Note 847019.

You can install a separate SRM Server for SUS or use the SRM Server you installed in step 3 for that purpose. The use of SAP BI is optional. See the description of this component in Software Components Overview [page 70] to decide if it is required for your business scenario. After the BI ABAP upgrade, you should install the Java parts of BI (BI-Java) to take advantage of all new functionality. For details, see Installation Guide – SAP NetWeaver 2004s.

For a minimal system landscape, you can install SAP BI on your SAP SRM Server. Install the SAP BI Business Content Add-On on the SRM Server as described in SAP Note 847019. For more information, see the Master Guide – SAP NetWeaver 2004s. 9

Install SAP NetWeaver Enterprise Portal 7.0. [Master Guide – SAP NetWeaver 2004s]

10

Import the following Business Packages into the Enterprise Portal: •

Business Package for SRM 5.0

•

Business Package for Supplier Collaboration 2.0

November 2006

The use of SAP NetWeaver Enterprise Portal is optional. It is required for the integration of mySAP SRM into a portal. Download the Business Packages from the SAP Developer Network www.sdn.sap.com → Portal Content Portfolio

31


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

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

3.1.3.4 Upgrade See the Upgrade Master Guide – mySAP SRM.

32

November 2006

3 Business Scenarios of mySAP SRM 3.2 Plan-Driven Procurement

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

Overview



3.2.1 Overview Description Plan-Driven Procurement automates and streamlines ordering processes for regularly needed core materials. You can use this business scenario to procure requirements for materials that have been generated in systems other than SAP Supplier Relationship Management (external systems). By integrating the SRM System with planning, design, and maintenance systems, you can accelerate your procurement and integrate the operational procurement with your Supply Chain Management solution. The business scenario supports third-party order processing, a special kind of procurement. Here the product goes directly from the vendor to the customer of the purchasing company. The purchase order to the vendor contains the necessary information for this. You can set up the business scenario in such a way as to link one or more Materials Management systems (SAP-MM) with Materials Requirements Planning (SAP-PP-MRP) to one 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 Business Scenario Descriptions for mySAP SRM.

Tasks Examples of tasks for Plan-Driven Procurement include: •

A manufacturing company with many disparate planning systems consolidates all procurement (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 Planning Requisition Source of supply determination

Ordering

Goods Received

Invoice Handling

Payment Accounting

Deployment Options For Plan-Driven Procurement, the Extended Scenario deployment option is available. You implement the SAP Enterprise Buyer system and one or more ERP systems. The complete procurement process takes place in the SAP Enterprise Buyer system. The leading

November 2006

33

3 Business Scenarios of mySAP SRM 3.2 Plan-Driven Procurement 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 be entered initially in the SAP Enterprise Buyer system. Purchase order data is updated in the backend system from SAP Enterprise Buyer. Goods receipt and invoice data are updated from the backend system.

Requirement Options For Plan-Driven Procurement, materials requirements from a product master can be received from: •

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

•

SAP R/3 MM.

•

Other external systems via an open XML interface.

3.2.2 Technical System Landscape For information about the technical system landscape and about how to plan the business scenario to meet your needs, see:

34

•

the section Minimal System Landscape [page 22]

•

SAP Service Marketplace at the Internet address: service.sap.com/platforms Æ Platform Availability Matrix

November 2006

3 Business Scenarios of mySAP SRM 3.2 Plan-Driven Procurement The following figure shows the underlying architecture of Plan-Driven Procurement.

Legend:

•


•


November 2006

35



3.2.3.1 Installation

No.

•


•


•

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

•


Action




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

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

Import the PI content for the following components: •

SAP SRM Server 5.5

•

SAP BI Content 7.0.2 (optional)

•

SAP_APPL 4.6C, SAP_APPL 4.70, SAP_APPL 5.00 depending on the SAP R/3 or SAP ECC release you are using (optional). For more information, see SAP Note 772189.

Download and install the latest SLD Content from SAP Service Marketplace at service.sap.com/swdc → Download → Support Packages and Patches → Entry by Application Group → Additional Components → SAP Master Data for SLD.

36

/

November 2006


No.

Action



Install/Integrate SAP R/3 or SAP R/3 Enterprise (SAP R/3 4.6C or higher recommended). [SAP R/3 Installation on : , or Installation Guide – SAP R/3 Enterprise on : ] Install SAP R/3 Plug-In (2004.1 or higher if one is available)

3

•


•

For more information concerning SAP R/3 PlugIns, see SAP Service Marketplace at: service.sap.com/r3-plug-in

Install SAP SRM Server 5.5.

SAP R/3 and SAP R/3 Enterprise are not part of this installation and are therefore not contained in the installation package. A separate SAP R/3 or SAP R/3 Enterprise installation package is required. Not required for customers with an ERP 2.0 backend system. From ERP 2.0 onwards, the former plug-in functionalities are delivered with the SAP_APPL component.

/

[Installation Guide –SRM Server on : ] 4

Install SAP Internet Transaction Server (7.00) [SAP@Web Installation Guide located on the Server Components CD]

5



/


Install SRM Server for SAP SUS. [Installation Guide –SRM Server on : ]

November 2006

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

37


No.

Action



Install SAP BI: 1. Install SAP Web AS ABAP 7.00, which includes SAP BI 7.0, PI_BASIS 2005_1_700. [Installation Guide – SAP Web Application Server ABAP on : ] 2. Configure the database of your SAP Web AS for SAP BI according to SAP Note 567745. 3. Install SAP BI Business Content Add-On BI_CONT 7.0.2 on the SAP Web AS ABAP system according to SAP Note 847019.

The use of SAP BI is optional. See the description of this component in section Software Components Overview [page 70] to decide if it is required for your business scenario. After the BI ABAP upgrade, you should install the Java parts of BI (BI-Java) to take advantage of all new functionality. For details, see Installation Guide – SAP NetWeaver 2004s.

For a minimal system landscape, you can install SAP BI on your SAP SRM Server. Install the SAP BI Business Content Add-On on the SRM Server as described in SAP Note 847019. For more information, see the Master Guide – SAP NetWeaver 2004s, included in the installation package. 8

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

9

38



•



November 2006



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

3.2.3.4 Upgrade See the documentation Upgrade Master Guide – mySAP SRM.

November 2006

39

3 Business Scenarios of mySAP SRM 3.3 Strategic Sourcing

3.3 Strategic Sourcing For this business scenario, the following topics are covered: Overview of the top-level scenario Strategy Sourcing consisting of the following business scenarios:

•

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 your source of supply for each individual item. You can identify cost-saving opportunities and evaluate suppliers’ ability to provide materials and services at low cost, high quality, and on schedule. Once you have determined the best source of supply for your requirements, you can collaborate in project teams both internally and with your suppliers to establish on-going relationships based on contracts and global outline agreements. For more information on Strategic Sourcing, see the documentation Business Scenario Descriptions for mySAP SRM.

Tasks Sample tasks for the Strategic Sourcing business scenario include:

40

•

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 for that region.

•

Analysis of hidden procurement costs kicks off a “supplier de-proliferation” initiative.

•

CPG company certifies different raw material vendors.

•

A company locates different suppliers for upcoming new product development.

•

A financial institution maintains lists of suppliers for different MRO materials.

•

A consulting company reduces its supplier base by aggregating airline tickets to one airline.

•

A bank aggregates its paper demand to improve MRO pricing.

•

A professional purchaser negotiates a long-term contract with a supplier to deliver goods of a specific commodity.

November 2006

3 Business Scenarios of mySAP SRM 3.3 Strategic Sourcing •

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

•

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

•

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

•

A professional purchaser creates a reverse auction to find a supplier for specific nonstandard 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 Initiate RFQ/Auction

Publish RFQ/Auction

Create and submit bid

Bid analysis and evaluation

Determine Winner


Minimal System Landscape [page 22]

•


November 2006

41

3 Business Scenarios of mySAP SRM 3.3 Strategic Sourcing The following figure shows the underlying architecture of Strategic Sourcing.

Application Gateway

HTTPS

HTTPS / OCI

Firewall BSP # SRMMDM Catalog 1.0


XI Int. Engine

XI Proxy Framework

LAC WPS 5.0


ITS

SAP NetWeaver BI CONT 7.0.2

SAP SRM Server 5.5

R/3 Plug_In

EBP

BSP

MM SAP SRM Server 5.5

RFC RFC

RFC XI Proxy Framework

XI Int. Engine

TREX 7.0

(IDOC)

R/3 Plug_In

RFC

TREX 7.0 for SAP NetWeaver

for SAP NetWeaver

(# alternative components)

IPC 7.0

R/3 3.1i – SAP ECC 6.0

IPC 7.0

SUS RFC XI Proxy Framework

XI Int. Engine

HTTP(S)

XML

PI XI Integration Engine


XML

XI Content: SRM-MDM Catalog 1.0 or: SAP Catalog Content Management 2.0

Legend:

42

•


•


November 2006




No.

•


•


•


Action [Corresponding Documentation]

1



If you installed SAP Process Integration, import the integration objects for mySAP SRM into the SAP Process Integration [page 90].



SAP SRM Server 5.5

•



November 2006

/

43


No.


2

Install/Integrate SAP R/3 or SAP R/3 Enterprise (SAP R/3 4.6C or higher recommended). [SAP R/3 Installation on : , or Installation Guide – SAP R/3 Enterprise on : ]

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

3

•


•

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

Install SAP SRM Server 5.5 comprising: •

SAP Bidding Engine

•

Supplier Self-Service

Remarks/Subsequent Steps SAP R/3 and SAP R/3 Enterprise are not part of this installation and are not contained in the installation package. A separate SAP R/3 or SAP R/3 Enterprise installation package is required. Not required for customers with an ERP 2.0 backend system. From ERP 2.0 onwards, the former plug-in functionalities are delivered with the SAP_APPL component. Otherwise the installation of the SAP R/3 Plug-In is required if you installed an SAP R/3 system in the previous step. /


Install SAP Internet Transaction Server. (7.00) [SAP@Web Installation Guide located on the Server Components CD]

5

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


/

For information, see:

44

•


•

SAP Note 967088 (regarding SRM-MDM Catalog)

November 2006


No.


6


Install SAP® NetWeaver 2004s Search and Classification (TREX) Use the following parameters during the installation (for more information, see the documentation listed below): •

Perform the installation steps to set up an RFC connection.

•

Automatic language recognition is not required. You can adopt the default settings for document languages during the installation of SAP® NetWeaver 2004s TREX.

•

No Python extensions are required.

/


Install Live Auction Cockpit Web Presentation Server (LACWPS) 5.0. [Component Installation Guide – SAP Supplier Relationship Management 5.0 ABAP + Java on :
8

Install SAP BI: 1. Install SAP Web AS ABAP 7.00, which includes SAP Bi 7.0 and PI_BASIS 2005_1_700. [Installation Guide – SAP Web Application Server ABAP on : ] 2. Configure the database of your SAP Web AS for SAP BI as described in SAP Note 567745. 3. Install SAP BI Business Content Add-On BI_CONT 7.0.2 on the SAP Web AS ABAP system as described in SAP Note 847019. For a minimal system landscape, you can install SAP BI on your SAP SRM Server. Install the SAP BI Business Content Add-On on the SRM Server as described in SAP Note 847019.

The use of Live Auction Web Presentation Server is optional. You can install LACWPS either on a standalone J2EE Engine or on a J2EE Engine installed as an AddIn on the central instance. The use of the SAP BI is optional. See the description of this component in Software Components Overview [page 70] to decide if it is required for your business scenario. After the BI ABAP upgrade, you should install the Java parts of BI (BI-Java) to take advantage of all new functionality. For details, see Installation Guide – SAP NetWeaver 2004s.

For more information, see the documentation Master Guide SAP NetWeaver 2004s. 9

Install SAP NetWeaver Enterprise Portal 7.0. [Master Guide SAP NetWeaver 2004s]

November 2006

The use of SAP NetWeaver Enterprise Portal is optional. It is required for the integration of mySAP SRM into a portal.

45


No.


10

46



•


Remarks/Subsequent Steps Download the Business Packages from the SAP Developer Network www.sdn.sap.com → Portal Content Portfolio

November 2006



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

3.3.3.4 Upgrade See the documentation Upgrade Master Guide – mySAP SRM.

November 2006

47

3 Business Scenarios of mySAP SRM 3.4 Catalog Content Management (CCM)

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 from different suppliers.

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

CATALOG CONTENT MANAGEMENT Import Catalog

Manage Catalog

Distribution of Catalog

Provide Catalog data for employee usage

3.4.2 Technical System Landscape For information about the technical system landscape and about how to plan the business scenario to meet your needs, see:

48

•


•


November 2006

3 Business Scenarios of mySAP SRM 3.4 Catalog Content Management (CCM) The following figure shows the underlying architecture of Catalog Content Management including existing connections.

Legend:

•


•


November 2006

49




No.

•


•


•



1


Install SAP Process Integration. [Master Guide – SAP NetWeaver 2004s, part of the installation package]



Import the PI content for the following components:

2

•

SAP SRM Server 5.5

•



/

Install SAP SRM Server 5.5 comprising:

/

•

SAP Bidding Engine

•


[Installation Guide – SAP SRM Server on : ]

50

November 2006


No.


3


4

Install SAP Catalog Content Management 2.0.

Remarks/Subsequent Steps You have to use the internal SAP ITS, which is integrated into the SRM Server (SAP ITS 7.0). Note that the external ITS is not supported. /

For information, see SAP Note 835170. 5


/

Use the following parameters during the installation (for more information, see the documentation listed below): •


•


•




7



•


November 2006


51



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


52

November 2006

3 Business Scenarios of mySAP SRM 3.5 SRM-MDM Catalog

3.5 SRM-MDM Catalog For 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, and managing catalog content within your e-procurement application. For more information, see Business Scenario Description in the SAP Service Marketplace under quick link ibc-srm.

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

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

CONTENT MANAGEMENT with SRM-MDM Catalog Import Product Information

Map and Enrich Catalog Data

Approve Catalog Content

Provide Web Content for Catalog Users



•


November 2006

53

3 Business Scenarios of mySAP SRM 3.5 SRM-MDM Catalog The following figure shows the underlying architecture of the SRM-MDM Catalog including existing connections.

Application Gateway

HTTP(S)

Firewall

SAP SRM-MDM Catalog 1.0 SAP MDM Console

SAP MDM Data Manager

SAP MDM Import Manager

ITS

* SAP MDM Server

SRM-MDM Catalog Search (Web Dynpro)

SAP MDM Import Server

SAP SRM Server 5.5 EBP HTTP(S) / OCI

XI Proxy Framework

XI Int. Engine

RFC

TREX 7.0 (Contracts) HTTP(S)

FTP(S)

XML Catalog Upload


XML

XML

Master Data; Contract Data

PI

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

Legend:

TCP / IP

Transfer protocol type Document format type

XML SRM Server

ABAP-based software component

TREX

C/C++ based software component Optional software component

EBP

Subcomponent (no own installation procedure) Java layer Application Platform

*

Client components Technology Platform

54

November 2006

3 Business Scenarios of mySAP SRM 3.5 SRM-MDM Catalog •


•


3.5.3 Implementation Sequence This section lists the sequence of steps (installation, technical configuration, application configuration) required to implement the business scenario. Rows containing optional components are shaded. The scenario can function without these optional components, but they do provide additional functions.


No.

•


•


•



1






2

SAP SRM Server 5.5


/

SAP Bidding Engine


Install SAP SRM-MDM Catalog 1.0.

/

For information, see SAP Note 967088.

November 2006

55


No.


4


56

Remarks/Subsequent Steps The use of SAP NetWeaver Enterprise Portal is optional. It is required for the integration of mySAP SRM into a portal.

November 2006


3.5.3.2 Configuration For 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 ibcsrm.


November 2006

57

3 Business Scenarios of mySAP SRM 3.6 Service Procurement

3.6 Service Procurement For 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. Before ordering external staff or services, you can send a request to one or more suppliers for detailed information on a specific service or the availability of individual service agents, for example. After receiving the suppliers’ responses and accepting one of these bids, the corresponding purchase order is automatically created. Next, time and expenses have to be entered into the system and, finally, the invoice is created. You can integrate your suppliers into the procurement process by connecting a supplier system like Supplier Self-Services to your procurement system. In this way, the service agents can enter services performed and create invoices for these services. You have to approve all documents created by your suppliers and you always retain a complete overview of 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 PROCUREMENT Requesting external staff

58

Processing purchase orders in SRM

Entering services

Processing invoices

November 2006




•


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

Application Gateway

HTTPS / OCI

HTTPS

Firewall ITS

BSP # SRMMDM Catalog 1.0



XI Int. Engine

XI Proxy Framework


SAP SRM Server 5.5

R/3 Plug_In

EBP

RFC

RFC

TREX 7.0

XI Proxy RFC Framework

IPC 7.0

XI Int. Engine RFC

(# alternative components)

BSP

R/3 3.1i – SAP ECC 6.0 FI / CO

SAP SRM Server 5.5

R/3 Plug_In

SUS

Separate IPC for SUS not needed if SUS and EBP are implemented in the same SAP system

IPC 7.0

XI Proxy RFC Framework

XI Int. Engine

RFC

HTTP(S)

XML


November 2006

XML

Integration XIXIIntegration Engine Engine

XML

PI


59


Legend:

60

•


•


November 2006




No.

•


•


•



1



If you installed SAP Process Integration, import the integration objects for mySAP SRM into the SAP Process Integration [page 90].



SAP SRM Server 5.5

•


•



November 2006

/

61


No.


2

Install/Integrate SAP R/3 or SAP R/3 Enterprise (SAP R/3 4.6C or higher recommended) [SAP R/3 Installation on : , or Installation Guide – SAP R/3 Enterprise on : ]

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

3

•

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

•


Remarks/Subsequent Steps SAP R/3 and SAP R/3 Enterprise are not part of this installation and are not contained in the installation package. A separate SAP R/3 or SAP R/3 Enterprise installation package is required. Not required for customers with an ERP 2.0 backend system. From ERP 2.0 onwards, the former plugin functionalities are delivered with the SAP_APPL component. Otherwise the installation of the SAP R/3 Plug-In is required if you installed an SAP R/3 system in the previous step.


SAP Bidding Engine

•


/



5

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

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

For information, see:

62

•


•

.SAP Note 967088 (regarding SRM-MDM Catalog)

November 2006


No.


6


Install SAP® NetWeaver 2004s Search and Classification (TREX) Use the following parameters during the installation (for more information, see the documentation listed below): •


•


•


/


Install SRM Server for SAP SUS. [Installation Guide – SAP SRM Server on : ]

8

Install SAP BI 7.0 plus SAP BI Content 7.0.2: 1. Install SAP Web AS ABAP 7.00, which includes SAP B/ 7.0 and PI_BASIS 2005_1_700. [Installation Guide – SAP Web Application Server ABAP on : ] 2. Configure the database of your SAP Web AS for SAP BI as described in SAP Note 567745. 3. Install SAP BI Business Content Add-On BI_CONT 7.0.2 on the SAP Web AS ABAP system as described in SAP Note 847019. For a minimal system landscape, you can install SAP BI on your SAP SRM Server. Install the SAP BI Business Content Add-On on the SRM Server as described in SAP Note 847019.

You can install a separate SRM Server for SUS or use the SRM Server you installed in step 3 for that purpose. The use of the SAP BI is optional. See the description of this component in Software Components Overview [page 70] to decide if it is required for your business scenario. After the BI ABAP upgrade, you should install the Java parts of BI (BIJava) to take advantage of all new functionality. For details, see Installation Guide – SAP NetWeaver 2004s.

For more information, see the Master Guide – SAP NetWeaver 2004s. 9

Install SAP NetWeaver Enterprise Portal 7.0. [Master Guide – SAP NetWeaver 2004s ]

10



•


November 2006


63





64

November 2006

3 Business Scenarios of mySAP SRM 3.7 Spend Analysis

3.7 Spend Analysis For 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 analyze your total spending across system and organizational boundaries. The analyses can be performed per supplier, per product, or per product category. The system landscape can consist of one or more SAP R/3 backend and SAP Enterprise Buyer 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 and contract information from the procurement systems. Master data has to be consolidated to identify identical suppliers and identical products stemming from either the same or different systems. For this purpose, you can use Advanced Master Data Maintenance included in SAP BI. Advanced Master Data Maintenance provides you 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 such as 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 mySAP SRM.

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

SPEND ANALYSIS Transferring data from operational systems into SAP BW

November 2006

Creating key mappings for suppliers and products

Assigning standard categories to purchasing categories

Reporting in SAP BW

65




•


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

66

November 2006

3 Business Scenarios of mySAP SRM 3.7 Spend Analysis Legend:

•


•


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


No.

•


•


•



1

Install/Integrate SAP R/3 or SAP R/3 Enterprise (SAP R/3 4.6C or higher recommended) [SAP R/3 Installation on : , or Installation Guide – SAP R/3 Enterprise on : ]

November 2006

Remarks/Subsequent Steps SAP R/3 and SAP R/3 Enterprise are not part of this installation and are not contained in the installation package. A separate SAP R/3 or SAP R/3 Enterprise installation package is required.

67


No.

Action [Corresponding Documentation] Install SAP R/3 Plug-In (2004.1 or higher if one is available)

2

•


•



SAP Bidding Engine

•

Supplier Self-Services

Remarks/Subsequent Steps Not required for customers with an ERP 2.0 backend system. From ERP 2.0 onwards, the former plug-in functionalities are delivered with the SAP_APPL component. Otherwise the installation of the SAP R/3 Plug-In is required if you installed an SAP R/3 system in the previous step. /


Install SAP Internet Transaction Server (7.00) [SAP@Web Installation Guide]

4


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


Install SAP BI 1. Install SAP Web AS ABAP 7.00, which includes SAP BI 7.0 and PI_BASIS 2005_1_700. [Installation Guide – SAP Web Application Server ABAP on : ] 2. Configure the database of your SAP Web AS for SAP BI as described in SAP Note 567745.

After the BI ABAP upgrade, you should install the Java parts of BI (BI-Java) to take advantage of all new functionality. For details, see Installation Guide – SAP NetWeaver 2004s.

3. Install SAP BI Business Content Add-On BI_CONT 7.0.2 on the SAP Web AS ABAP system as described in SAP Note 847019. For a minimal system landscape, you can install SAP BI on your SAP SRM Server. Install the SAP BI Business Content Add-On on the SRM Server as described in SAP Note 847019. For more information, see the Master Guide – SAP NetWeaver 2004s. 6

68

Install SAP NetWeaver Enterprise Portal 7.0.

The use of SAP NetWeaver Enterprise

November 2006


No.


7


[Master Guide – SAP NetWeaver 2004s]

Portal is optional. It is required for the integration of mySAP SRM into a portal.

Import the following Business Packages into the Enterprise Portal:

Download the Business Packages from the SAP Developer Network www.sdn.sap.com → Portal Content Portfolio

•


•





November 2006

69

3 Business Scenarios of mySAP SRM 3.8 Contract Management

3.8 Contract Management For 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 monitor purchasing contracts and global outline agreements (GOA). It also provides a means to renegotiate 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 a possible selection. 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 management enables purchasers from various parts of the company at different locations to take advantage of the terms of globally-negotiated contracts for specific product categories. You can provide users with specific levels of authorization to contracts and GOAs, and also categorize these documents as confidential. You can distribute a GOA to the releaseauthorized purchasing organizations and these organizations can use the contracts and scheduling agreements created from the distributed GOA. You can use hierarchies to organize, structure, display, and search for your contracts. If you use SAP Business Intelligence (SAP BI), you can view various consolidated reports of contract management. For example, you can view the aggregated value released against all the contracts in a contract hierarchy. For more information on Contract Management, see the Business Scenario Descriptions for mySAP SRM.

Tasks Typical tasks for the Contract Management business scenario include:

70

•

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

•

A strategic purchaser maintains a global outline agreement database that includes target quantities.

•

A strategic purchaser monitors contract compliance.

•

An operational purchaser searches for applicable contracts within a central contract database and puts contracts into effect.

•

An operational purchaser adds local contract information.

•

An operational purchaser manages planning and production processes.

•

An operational purchaser creates purchase orders against a contract.

November 2006


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

CONTRACT MANAGEMENT Preparing Contracts

Negotiating Contracts

Executing Contracts

Processing Global Outline Agreements

Monitoring Contracts

Analyzing Procurement Data

Deployment Options For Contract Management, the following deployment options are available. •

Classic scenario

•

Standalone scenario



•


November 2006

71

3 Business Scenarios of mySAP SRM 3.8 Contract Management The following figure shows the underlying architecture of Contract Management. Application Gateway

HTTPS / OCI

HTTP(S)

Firewall SAP NetWeaver BI 7.0

BSP # SRMMDM Catalog 1.0

XI Int. Engine


ITS SAP SRM Server 5.5

IPC 7.0


R/3 3.1i – SAP ECC 6.0 MM

FI / CO

EBP Bidding Engine

R/3 Plug_In

XI Proxy Framework

XI Proxy

RFC

Framework

XI Int. Engine

R/3 Plug_In (IDOC) RFC

TREX 7.0

TREX 7.0 (# alternative components) (# alternative components)

(Contracts) RFC

HTTP(S)

PI XML



XML


Legend:

72

•


•

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

November 2006


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


No.

•


•


•


Action




The use of SAP Process Integration is optional. It is required to load contracts into the catalog, to send product category hierarchies to SRM in a file (via PI), or to connect to nonSAP planning or execution systems.

SAP Process Integration requires a dedicated SAP Web Application Server. This means that running applications in other clients of the same SAP Web AS is not supported. If you installed SAP Process Integration, import the integration objects for mySAP SRM into the SAP Process Integration [page 90]. Import the PI content for the following components: •

SRM Server 5.5

•


•


November 2006

/

73


No.

Action


[Corresponding Documentation] Download and install the latest SLD Content from SAP Service Marketplace at service.sap.com/swdc → Download → Support Packages and Patches → Entry by Application Group → Additional Components → SAP Master Data for SLD. 2

Install/Integrate SAP R/3 or SAP R/3 Enterprise (SAP R/3 4.6C or higher recommended). [SAP R/3 Installation on : , or Installation Guide – SAP R/3 Enterprise on : ] Install SAP R/3 Plug-In (2004.1 or higher if one is available):

3

•


•

For more information concerning SAP R/3 PlugIns, see SAP Service Marketplace at service.sap.com/r3-plug-in.

Install SAP SRM Server 5.5

/

SAP R/3 Enterprise is not part of this installation and is not contained in the installation package. A separate SAP R/3 Enterprise installation package is required. Not required for customers with an ERP 2.0 backend system. From ERP 2.0 onwards, the former plug-in functionalities are delivered with the SAP_APPL component. Not required if exclusively local PO handling is performed or no SAP R/3 system is used as backend system. /


Install SAP Internet Transaction Server (7.00) [SAP@Web Installation Guide located on the SAP Server Components CD]

5

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


/

For information, see: •


•

.SAP Note 967088 (regarding SRM-MDM Catalog)


6

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

74

•

Perform the installation steps to set up an RFC connection

•

Automatic language recognition is not required. You can adopt the default settings for document

/

November 2006


No.

Action


[Corresponding Documentation] languages during the installation of SAP® NetWeaver 2004s TREX. •

No Python extensions are required


Install SRM Server for SAP SUS. [Installation Guide – SRM Server on : ]

8

Install SAP BI: 1. Install SAP Web AS ABAP 7.00, which includes SAP BI 7.0 and PI_BASIS 2005_1_700. [Installation Guide – SAP Web Application Server ABAP on : ] 2. Configure the database of your SAP Web AS for SAP BI as described in SAP Note 567745. 3. Install SAP BI Business Content Add-On BI_CONT 7.0.2 on the SAP Web AS ABAP system as described in SAP Note 847019.

You can install a separate SRM Server for SUS or use the SRM Server you installed in step 3 for that purpose. The use of SAP BI is optional. See the description of this component in Software Components Overview [page 70] to decide if it is required for your business scenario. After the BI ABAP upgrade, you should install the Java parts of BI (BI-Java) to take advantage of all new functionality. For details, see Installation Guide – SAP NetWeaver 2004s.

For a minimal system landscape, you can install SAP BI on your SAP SRM Server. Install the SAP BI Business Content Add-On on the SRM Server as described in SAP Note 847019. For more information, see the Master Guide – SAP NetWeaver 2004s. 9

Install SAP NetWeaver Enterprise Portal 7.0. [Master Guide – SAP NetWeaver 2004s]

10



•


November 2006


75





76

November 2006

3 Business Scenarios of mySAP SRM 3.9 SAP ERP 2005 – SAP SRM

3.9 SAP ERP 2005 – 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 is new 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 hub deployment.

•

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

•

It is not possible to upgrade or migrate from a separately-installed SRM system 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 service.sap.com/instguides Æ mySAP Business Suite Solutions Æ mySAP ERP Æ mySAP ERP 2005 Æ Planning.

November 2006

77

4 Software Components Overview 4.1 Software Units

4 Software Components Overview This section provides additional information about the primary software components of this mySAP Business Suite solution.

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

4.1 Software Units Technically, SAP implements all capabilities and features of mySAP Business Suite solutions using 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 own release plan.

4.1.1 SRM 2005 Software Units The following application components implement and support mySAP Business Suite crossindustry solutions.

SAP Supplier Relationship Management Server Definition The SAP Supplier Relationship Management Server (SAP SRM Server) includes both SAP Enterprise Buyer and SAP Bidding Engine. SAP Enterprise Buyer is based on SAP NetWeaver Application Server (AS). It is an application and database instance installation released on several database and operating system platforms (see SAP Service Marketplace at service.sap.com/platforms Æ Platform Availability Matrix). It enables easy, full-cycle, inter-enterprise procurement. With it you can: •

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

•

Approve and reject purchases

•

Receive and enter service information at the desktop

•

Use status, invoicing, and reporting functions

End users can purchase goods and services straight from their workplace, leaving purchasing departments free to focus on strategic purchasing operations. This helps streamline requisition processes and, consequently, all indirect procurement processes, cutting the overall cost of procurement while providing the purchasing department with visibility and control across the entire procurement chain. SAP Enterprise Buyer contains business scenarios for professional purchasers. For example, with SAP Enterprise Buyer, you can publish bid invitations in Internet marketplaces for your specific branch of industry, extending your potential reach to the entire Internet community.

78

November 2006

4 Software Components Overview 4.1 Software Units By the same means, interested parties can access the bid invitation and submit their bids directly from the marketplace. SAP Enterprise Buyer also supports restricted bid invitations. 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 a provider’s services or analyze their employees’ purchases. In addition to maintenance, repairs, and operation (MRO), BI supports the end-to-end procurement of direct materials. Direct procurement scenarios involve the seamless integration of SAP Enterprise Buyer with SAP APO, BI, and SAP or non-SAP backend systems. 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 any mySAP SRM scenario. It empowers employees with self-service procurement, enables centralized direct procurement and provides the professional purchaser with tools to make the right sourcing decisions. The mySAP SRM solution requires the SAP Enterprise Buyer system for downloading materials data and (optionally) using the Business Intelligence capabilities offered by SAPNetWeaver. SAP Bidding Engine Purchasers can use SAP Bidding Engine to create and process bid invitations, and bidders can use SAP Bidding Engine to submit bids in response to these bid invitations. Both purchasers and bidders can use reverse auction functions in a separate Live Auction application. Purchasers can define rules pertaining to bidding and bidders can submit bids in real time.

OLTP System Definition Online transaction processing system (for example, SAP ERP system) that is used in the SAP Enterprise Buyer environment as a backend system. It is used for materials management and financials.

Use Data is exchanged between the SAP Enterprise Buyer system and a connected OLTP system. It is possible to install the SAP Enterprise Buyer system without an OLTP backend in a standalone configuration. If an SAP ERP system is used as an OLTP system, the plug-in supports data exchange not only within SAP Enterprise Buyer, but also with other SAP software units such as BI or SAP APO.

November 2006

79


SAP NetWeaver Business Intelligence 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 either as precalculated documents with past data, or as links with live data

•

Open analysis interfaces that make available various interfaces for connecting frontend tools of third-party providers

•

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

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

Use BI provides the foundation for the SRM scenario Spend Analysis, and can optionally be installed for the others. BI includes the complete ABAP stack of the SAP NetWeaver BI data warehouse and BI platform units. BI requires AS-ABAP as prerequisite in the same system. Usually, scenarios running on BI also require BI-Java, AS-Java and EP. Other combinations can be used in one system as well.

SAP NetWeaver Enterprise Portal SAP NetWeaver Portal serves as a single point of entry to the applications, services, and information of the organization. Running an Enterprise Portal is an IT scenario whose implementation provides role-based and secure access to all types of applications, services, and information in an enterprise portal environment. Customers can benefit from the numerous predefined business packages available to them, or they can create their own content. This scenario includes the following variants:

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

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

80

November 2006


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 those services.

SAP Catalog Content Management SAP Catalog Content Management (SAP CCM) is an ABAP add-on. It consists of an authoring tool and a search engine. SAP Catalog Authoring Tool enables the Catalog Manager to use external supplier data to build 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 for employee 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 Basis 700 only. 3. Upload supplier product data If your suppliers use theBusiness Package for Supplier Collaboration, you can enable them to upload their catalog data themselves. SAP Catalog Content Management provides 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 1. Browse in catalog 2. Search for items 3. Transfer data to procurement system

November 2006

81


Live Auction Cockpit Web Presentation Server Live Auction Cockpit Web Presentation Server is a J2EE-based software unit, which comprises 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. TREX services include search and retrieval in large document collections, text mining, automatic document classification, and search and aggregation over structured data in SAP applications. TREX can handle text from documents in numerous formats, including Microsoft Office and Adobe formats (PDF), and more than 30 languages. TREX search options, such as exact, boolean, fuzzy, or linguistic search, and classification options such as query-based or example-based classification, offer great power and flexibility to end users.

SRM-MDM Catalog The SRM-MDM Catalog is a software component based on SAP NetWeaver MDM technology. It combines SAP MDM Server 5.5 with a Java-based and SRM-specific search environment. The Catalog Manager imports, structures and adjusts the catalog content. He provides for usergroup-specific masks and – after the content has been confirmed by the Catalog Content Approver – enables the content to be accessible for the catalog users via Web 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. Transfer info records and contracts from ERP. 5. Transfer product data from SRM. 6. Transfer contracts data from SRM. 7. Enrich product data. 8. Approve product data. 9. Define masks. 10. Define validations.

82

November 2006

4 Software Components Overview 4.1 Software Units 11. Enable web content. 12. Browse in catalog and search for catalog items. 13. Transfer data to procurement system.

4.1.2 Industry-Specific Components Industry-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 Components Technology components are software and middleware components used to implement and support solutions of mySAP Business Suite.

SAP NetWeaver Process Integration (PI) Separate licensing is required for SAP NetWeaver Process Integration if mySAP SRM 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 the integration 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, PI contains core components for Business Process Management for application-embedded and application-unbounded processes.

November 2006

83


SAP GUI Generally, the latest release of the SAP GUI software (such as SAP GUI 6.20) can be used with all previous SAP component releases. As a result, older SAP systems can also benefit from the features that are only available in the newer SAP GUI releases, for example support for Windows XP. Use the latest available front-end software.

SAP R/3 Plug-In The SAP R/3 Plug-In is an interface, which enables the exchange of data between one or several SAP R/3 systems and other SAP components. The SAP R/3 Plug-In supplies the SAP components with transaction data and master data in real time. It also makes it possible to use SAP application components like SAP APO or SAP CRM together with certain industry-specific components. All SAP industry-specific components based on SAP R/3 4.6B or higher SAP R/3 releases require an SAP R/3 Plug-In. The SAP R/3 Plug-In is an add-on to SAP R/3. SAP R/3 Plug-Ins are shipped with SAP application components (SAP APO, SAP BI, SAP BBP, 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/3 Plug-In releases free of charge or download them from the SAP Service Marketplace. Depending on the combination of the SAP R/3 Plug-In release and version and the SAP R/3 release, certain SAP R/3 support package levels are required to install the SAP R/3 Plug-In. For more information and for download, see SAP Service Marketplace at service.sap.com/r3-plug-in.

SAP NetWeaver Application Server Definition Application Server (AS) is the application platform of SAP NetWeaver and, consequently, of the mySAP Business Suite. It provides the technological foundation for all other SAP software 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

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

Use As AS contains the ABAP Engine, the Java Engine, or both, it can provide a runtime environment for both ABAP and Java applications. AS includes a platform for quickly developing and deploying dynamic and collaborative Web applications or other thin-client applications (WAP, PDA, for example) and supports all proven SAP programming models and technologies. With AS, SAP natively supports open Internet standards including protocols such as HTTP, HTTPS, and SMTP, as well as Internet document standards like HTML and XML.

84

November 2006

4 Software Components Overview 4.2 Non-SAP Components Open integration capabilities provide access to existing SAP and non-SAP applications. All integration facilities supported by SAP are available with AS. The Java Connector or the .NET Connector give ABAP applications access to Java or .NET components and vice versa. In addition, the Internet Communication Framework (ICF) enables ABAP programs to process and distribute HTTP requests directly. As a consequence, AS can serve as both an HTTP server and a client. It serves as an HTTP server for bringing applications to the user via a Web browser either directly or via a standard Web server. It serves as an HTTP client to access other Web applications for collecting information and data. To complete Web connectivity, 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 synchronization for the J2EE cluster.

Database instance AS-Java has its own database schema. As a result, a database instance is also a mandatory 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 and the Java schema are installed in the same database.

Exception: If your SAP system is running on Informix, a separate MaxDB or IBM DB2 UDB for 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 See separate component description above.

4.2 Non-SAP Components No non-SAP component is part of mySAP SRM.

November 2006

85

5 References 5.1 SAP Notes

5 References 5.1 SAP Notes The 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 the installation of SAP SRM 5.0

852894

SRM 5.0 Support Package 01

708736

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

86

November 2006

5 References 5.2 Documentation

5.2 Documentation Make sure you have the latest documentation version by checking SAP Service Marketplace at service.sap.com/srm-inst → 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 business scenarios. Title

Where to find

Relevant for which Business Scenario

Catalog Content Management Service Procurement

M

M

M

M

M

Master Guide – SAP NetWeaver 2004s

Part of the SAP NetWeaver delivery; SAP Service Marketplace at: service.sap.com/ installNW2004s Æ Installation

O

M

O

M

O

Upgrade Master Guide – mySAP SRM 5.0

SAP Service Marketplace at: service.sap.com/ srm-inst Æ mySAP SRM Using SAP SRM Server 5.5

O

O

O

O

Installation Guide SAP NetWeaver 2004s Search and Classification (TREX)

SAP Service Marketplace at service.sap.com/ installNW2004s

M

O

M

Language Transport (BC-CTSLAN) 6.40

SAP Service Marketplace at: service.sap.com/ installNW2004s

O

O

O

November 2006

M

SRM-MDM Catalog

Strategic Sourcing

SAP Service Marketplace at: service.sap.com/ srm-inst

Contract Management


Installation Guide – SAP SRM 5.0 on :

Spend Analysis


M = mandatory / O = optional

M

M

M

O

M

O

O

--

O

M

O

O

M

--

O

O

O

O

O

87

5 References 5.2 Documentation Title

Where to find


Strategic Sourcing


Spend Analysis

M

M

M

M

M

Part of the SAP R/3 Enterprise delivery, SAP Service Marketplace at: service.sap.com/ instguides Æ SAP Components Æ SAP R/3 Enterprise Æ

O

O

O

--

O

SAP R/3 Installation on :

Part of the SAP R/3 delivery, SAP Service Marketplace at: service.sap.com/ instguides Æ SAP Components Æ SAP R/3 Æ

O

O

O

--

O

SAP Service Marketplace at: service.sap.com/ibcsrm Æ for mySAP SRM

M

M

M

M

Solution Operation Guide – mySAP SRM

SAP Service Marketplace at: service.sap.com/srminst Æ mySAP SRM Æ Using SAP SRM Server 5.5

M

M

M

Security Guide – my SAP SRM 5.0

SAP Service Marketplace at:

M

M

M

SAP NetWeaver 2004s DVD

Installation Guide – SAP R/3 Enterprise on :

88

SRM-MDM Catalog


M

SAP Front End Installation Guide

Contract Management



M

M

O

--

M

O

--

M

M

M

M

M

M

M

M

M

M

M

M

M

M

* Presentation * Server Components * Content Server M

service.sap.com/srminst Æ mySAP SRM Using SAP SRM Server 5.5

November 2006

5 References 5.2 Documentation Title

Where to find


November 2006

Spend Analysis

M

M

M

M

M

M

89

SRM-MDM Catalog


M

Contract Management

Strategic Sourcing

All configuration documentation for mySAP SRM 5.0 is available in SAP Solution Manager ST-ICO 150 content shipment. Please note: This information is available only in the Solution Manager. Additionally, an SRM implementation roadmap and an SRM upgrade roadmap are available there.


Configuration documentation for mySAP SRM 5.0 for each business scenario



M

6 Additional Information 6.1 Importing Integration Objects for mySAP SRM on SAP Process Integration

6 Additional Information 6.1 Importing Integration Objects for mySAP 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 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 for SRM 5.0 and section Patching your mySAP SRM Solution [page 91]).

For more information about importing Integration Objects, see SAP Note 836200.

If PI content is imported, existing content in the namespaces used by SAP will be lost. Customer changes in those namespaces will be treated as modifications and will also be lost. There is no modification adjustment available.

Procedure 1. On the SAP Exchange Infrastructure host (Integration Builder), create the directory /xi/repository_server/import if it does not already exist.

is the system directory that you specified during the installation of the SAP Exchange Infrastructure server. 2. Copy all *.TPT files from /TPT to the directory /xi/repository_server/import.

If you want to patch the existing SAP Exchange Infrastructure as part of patching mySAP SRM, perform the following steps instead: a. Download all *.TPZ files from the SAP Service Marketplace at the Internet address: service.sap.com/swdc Æ Download Æ Support Packages and Patches Æ Entry by Application Group Æ SAP Application Components Æ SAP SRM (WITH EBP) Æ SAP SRM 5.0 Æ XI CONTENT b. Copy these downloaded *.TPZ files to the directory /xi/repository_server/import. 3. Start the Repository (Design) tool of the Integration Builder.

90

November 2006

6 Additional Information 6.2 Patching your mySAP SRM Solution

For more information, see the SAP Process Integration online documentation at help.sap.com Æ SAP NetWeaver Æ Process Integration Æ SAP Exchange Infrastructure Æ Design and Configuration Time Æ Integration Builder. 4. Choose Object Æ Import XI 3.0 Development Object. 5. Select all *.TPT files you have copied to the import directory.

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

6.2 Patching your mySAP SRM Solution To patch your mySAP SRM solution (for example, from SRM 4.0 SP02 to SRM 4.0 SP03), proceed as follows: 1. Check SAP Service Marketplace at the Internet address: service.sap.com/patches Æ SAP Support Packages in Detail Æ Schedules for Support Packages Æ SRM Support Package Schedule Æ EBP 5.0 (SRM 4.0) Support Package Schedule for the number of the latest released Support Package and the corresponding SAP Note Support Package for SRM 5.0. 2. Patch your SAP components according to this SAP Note Support Package for SRM 5.0: •

You can obtain required support packages / binary patches from SAP Service Marketplace at the Internet address: service.sap.com/patches Æ Entry by Application Group Æ SAP Application Components Æ SRM (WITH EBP) Æ SRM 5.0.

•

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

•

If required, patch the existing SAP Exchange Infrastructure according to section Importing Integration Objects for mySAP SRM on the SAP Process Integration [page 90].

November 2006

91

7 Media Information

7 Media Information Software Components and DVD / CD Structure This section summarizes the exact location of the required software components on the corresponding DVD(s) and CD(s) shipped with the SAP SRM 5.0 package. 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 to service.sap.com/installNW2004s or service.sap.com/upgradeNW2004s. For more information about the SAP Solution Manager media list, go to service.sap.com/instguides Æ 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 service.sap.com/instguidesNW2004s Æ Installation; the SRM installation guides are located at service.sap.com/srm-inst Æ Using SAP SRM Server 5.5. Furthermore, we recommend that you visit the SAP Software Distribution Center in SAP Service Marketplace at service.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 are automatically generated from the licenses. To obtain the software you require, you can either download the corresponding files directly (by simply clicking on the file name) 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 service.sap.com/sp-stacks . 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

Description / Additional Information

mySAP Business Suite 2005 SAP Installation Master for: SAP ERP 2005 SR2, SAP NETWEAVER 2004S SR2, SAP SRM 5.0 SR2, SAP SCM 5.0 SR2, SAP CRM 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

SAP SRM 5.0 SR2 SAP SRM Server 5.5 SAP Installation Export

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

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

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

SAP SRM 5.0 SR2 SAP SRM Server 5.5 SAP Upgrade Export DVD

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

SAP SRM 5.0 SR2 SAP Language DVD Languages DE, EN, ES, FR, IT, NL, CA, CS DA, EL, FI, HU, NO, PL, PT, RU, SK, SV TR, JA, KO, TH, ZF, ZH

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

SAP NetWeaver 2004S SR2 SAP Kernel 7.00

Contains SAP Kernel files for NetWeaver 2004s AS ABAP, ECC 6.0 ABAP System and SRM 5.0 ABAP System (for installation and upgrade)

, RDBMS,

Media for database software

,

Database documentation (available for Oracle only)

SAP Catalog Content Management (SAP CCM) 2.0

SAP CATALOG CONT.MGMT. 2.0_640 SAP CATALOG CONT.MGMT. 2.0_700 Add-On Installation/Upgrade

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

SAP XI Content for CCM 2.0, 700


SAP XI Content for SRM Server 5.5

SAP SRM 5.0 SR2 SRM Components cProjects, Portal Content, XI Content

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

93

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

November 2006

7 Media Information mySAP Business Suite 2005 SAP Installation Master for: SAP ERP 2005 SR2, SAP NETWEAVER 2004S SR2 SAP SRM 5.0 SR2, SAP SCM 5.0 SR2 SAP CRM 5.0 SR2 SAP NETWEAVER 2004S SR2 Java based Software Components

SAP Live Auction Cockpit

mySAP Business Suite 2005 Java Components for: SAP ERP 2005 SR2 SAP CRM 5.0 SR2 SAP SCM 5.0 SR2 SAP SRM 5.0 SR2 SAP SRM 5.0 SR2 SAP SRM Server 5.5 SAP Upgrade Master DVD.

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. Contains Java software for SAP NetWeaver 2004s usages

Contains Java software for SAP SRM 5.0

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

, RDBMS,

Media for database software

,

Database documentation (available for Oracle only)

SAP NetWeaver 2004S SR2 SAP Kernel 7.00

Contains SAP Kernel files for NetWeaver 2004s usages and SAP Live Auction Cockpit

SAP GUI for Windows 6.40 SAP GUI for Java 6.40 SAP Server Components including SAP Internet Transaction Server 6.20 SAP Content Server 6.30 Adobe LiveCycle Designer 7.0

SAP NETWEAVER 2004S SR1 Presentation (SAP GUI for Windows 6.40 Comp. 5, SAP GUI for Java 6.40), Server Components, Content Server, Adobe LifeCycle Designer

Contains installation of SAP GUI for Windows release 6.40 (folder PRES1) and SAP GUI for Java (PRES2) as well as SAP Gateway and SDKs (folder PRES3), SAP Server Components including ITS 6.20 (folder SERV1), SAP Content Server 6.30 (folder CS), SAPDB for Content Server on UNIX (folder CS_SAPDB) and Adobe LiveCycle Designer 7.0 (folder ADOBE_LC_DES)

Portal Content cProject

SAP SRM 5.0 SR2 SRM Components CD cProjects Portal Content XI Content

Contains the Business Package BP SRM 5.0 and BP SUPPLIER COLLABORATION 2.0 and the ADD-ON Software SAP cProjects 400 Installation and Upgrade

Documentation SAP SRM 5.0 , HTML-Help for Windows, Standard HTML (Plain HTML)

Documentation for SAP SRM 5.0 in HTML Help for Windows and Standard HTML (Plain HTML)

Documentation for SAP SRM 5.0 Documentation for SAP CCM 2.0 3

SAP License Keys & License Audit

94

Documentation for SAP Catalog Content Management can be downloaded from the SAP Help Portal (help.sap.com Æ Documentation Æ mySAP Business Suite Æ mySAP Supplier Relationship Mgmt Æ SAP Catalog Content Management) License Keys for SAP Systems System Measurement Guide License Administration Workbench

SAP License Keys & License Audit contains the complete documentation as well as important information about the license auditing tools and the preparations you need to make for license auditing.

November 2006

SAP SRM

Recommend Documents