Application Operations Guide Sap Supplier Relationship Management Powered by Sap Netweaver®

Application Operations Guide
SAP Supplier Relationship Management powered by SAP

NetWeaver®
Target Audience
n System Administrators
n Technology Consultants
PUBLIC
Document version: 1.0 ‒ 11/21/2008
Document History
Caution
Before you start the implementation, make sure you have the latest version of this document. You
can find the latest version at the following location: http://service.sap.com/instguides
Installation and Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM Server 7.0 .
The following table provides an overview of the most important document changes.
Version Date Description
1.0 11/21/2008 Final Version

[Description]
2/66 PUBLIC 11/21/2008

Table of Contents
Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . 7

1.1 About this Guide . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . 8
Chapter 2 Overview of SAP Supplier Relationship Management 7.0 . . . . . . 9

2.1 Technical System Landscape . . . . . . . . . . . . . . . . . . 9
2.1.1 ABAP Components . . . . . . . . . . . . . . . . . . . . . 9
2.1.2 Java Components . . . . . . . . . . . . . . . . . . . . . . 10
2.1.3 Additional Components . . . . . . . . . . . . . . . . . . . . 11
2.2 Software Component Matrix . . . . . . . . . . . . . . . . . . 12
2.3 Related Documentation . . . . . . . . . . . . . . . . . . . . 12
Chapter 3 Monitoring of SAP SRM . . . . . . . . . . . . . . . . . . . 15

3.1 Alert Monitoring with CCMS . . . . . . . . . . . . . . . . . . 15
3.1.1 CCMS Monitoring Installation and Setup . . . . . . . . . . . . . 16
3.1.2 Alert Monitoring of Components . . . . . . . . . . . . . . . . 16
3.1.2.1 SAP NetWeaver 7.01 Monitoring . . . . . . . . . . . . . . . . . 16
3.1.2.2 Monitoring SAP SRM Server 7.0 . . . . . . . . . . . . . . . . . 17
3.1.2.3 Monitoring of SAP LACWPS 7.0 . . . . . . . . . . . . . . . . . 18
3.1.2.3.1 GRMG Availability Monitoring for SAP LACWPS 7.0 . . . . . . . . . . 18
3.1.2.3.2 Activating GRMG Monitoring . . . . . . . . . . . . . . . . . 19
3.1.2.3.3 Verifying the GRMG Availability Monitoring . . . . . . . . . . . . 21
3.1.2.3.4 Troubleshooting GRMG Availability Monitoring . . . . . . . . . . . 22
3.1.2.4 SAP SRM Monitor . . . . . . . . . . . . . . . . . . . . . . 25
3.1.2.5 Monitoring SAP SRM-MDM Catalog 3.0 . . . . . . . . . . . . . . 28
3.1.2.5.1 SAP SRM-MDM Catalog 3.0 . . . . . . . . . . . . . . . . . . 28
3.1.2.5.2 GRMG Availability Monitoring for SAP SRM-MDM Catalog 3.0 . . . . . 29
3.2 Detailed Monitoring and Tools for Problem and Performance Analysis . . . 30
3.2.1 Component-Specific Analysis Tools . . . . . . . . . . . . . . . . 30
3.2.1.1 SAP Supplier Relationship Management (SAP SRM) 7.0 . . . . . . . . 30
3.2.1.2 SAP Live Auction Cockpit Web Presentation Server (LACWPS) 7.0 . . . . . 39
3.2.1.3 SAP SRM-MDM Catalog 3.0 . . . . . . . . . . . . . . . . . . 30
3.2.2 Scenario Problem Analysis Tools . . . . . . . . . . . . . . . . . 31
3.2.2.1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2.2.2 Data Archiving Monitors . . . . . . . . . . . . . . . . . . . 31
11/21/2008 PUBLIC 3/66

3.2.2.3 Distributed Statistical Records . . . . . . . . . . . . . . . . . . 31
3.2.2.4 Business Packages . . . . . . . . . . . . . . . . . . . . . . 32
3.2.3 Logs and Trace (Component or Scenario-Specific) . . . . . . . . . . 32
Chapter 4 Management of SAP SRM . . . . . . . . . . . . . . . . . . 33

4.1 Administration Tools of Software Components . . . . . . . . . . . 33
4.2 Software Configuration . . . . . . . . . . . . . . . . . . . . 33
4.3 Starting and Stopping . . . . . . . . . . . . . . . . . . . . . 34
4.4 Backup and Restore . . . . . . . . . . . . . . . . . . . . . 35
4.4.1 General Remarks . . . . . . . . . . . . . . . . . . . . . . 36
4.4.2 Backup of Individual Components in an SAP SRM Landscape . . . . . . 37
4.4.2.1 B&R for Operating System, Software, and Configuration Data . . . . . . 37
4.4.2.2 Database B&R . . . . . . . . . . . . . . . . . . . . . . . 38
4.4.2.3 B & R for SAP Web Application Server (WebAS) 7.01 . . . . . . . . . . 39
4.4.3 B&R for Individual System Components . . . . . . . . . . . . . . 39
4.4.3.1 SAP Live Auction Cockpit Web Presentation Server (LACWPS) 7.0 . . . . . 39
4.4.3.2 SAP SRM-MDM Catalog 3.0 . . . . . . . . . . . . . . . . . . 39
4.4.4 B&R for a Complete SAP SRM Landscape . . . . . . . . . . . . . 40
4.4.4.1 Landscape Shutdown . . . . . . . . . . . . . . . . . . . . . 40
4.4.4.2 Offline Backup of the SAP SRM Landscape . . . . . . . . . . . . . 40
4.4.4.3 Landscape Startup . . . . . . . . . . . . . . . . . . . . . . 41
4.4.5 B&R for an SAP SRM Business Scenario . . . . . . . . . . . . . . 41
4.5 System Copy . . . . . . . . . . . . . . . . . . . . . . . . 41
4.6 Scheduled and Manual Periodical Tasks . . . . . . . . . . . . . . 41
4.6.1 Periodical Tasks for SAP NetWeaver 7.01 . . . . . . . . . . . . . . 41
4.6.2 Periodical Tasks for SAP SRM 7.0 . . . . . . . . . . . . . . . . . 42
4.6.3 Periodical Tasks for SAP SRM-MDM Catalog 3.0 . . . . . . . . . . . 42
4.6.4 Manual Periodical Tasks for SAP SRM 7.0 . . . . . . . . . . . . . . 43
4.7 Log on and Load Balancing . . . . . . . . . . . . . . . . . . . 43
4.8 User Management . . . . . . . . . . . . . . . . . . . . . . 43
4.8.1 Portal User Management . . . . . . . . . . . . . . . . . . . 44
4.8.1.1 Activating the TPD for User Integration Between SAP SRM Server (SUS) and
SAP Enterprise Portal . . . . . . . . . . . . . . . . . . . . . 44
4.8.1.2 SRM Server (SUS) and Portal User Integration . . . . . . . . . . . . 45
Chapter 5 High Availability . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 6 Software Change Management . . . . . . . . . . . . . . . . 49

6.1 Transport and Change Management . . . . . . . . . . . . . . . 49
6.2 Development Requests and Development Release Management . . . . . 50
6.3 Support Packages and SAP Notes Implementation . . . . . . . . . . 50
6.4 Release and Upgrade Management . . . . . . . . . . . . . . . . 51
4/66 PUBLIC 11/21/2008

6.5 Template Management . . . . . . . . . . . . . . . . . . . . 51
6.6 Quality Management and Test Management . . . . . . . . . . . . 51
Chapter 7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . 53
Chapter 8 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.1 Categories of System Components for Backup and Restore . . . . . . . 55
8.2 Related Information . . . . . . . . . . . . . . . . . . . . . 57
Chapter A Reference . . . . . . . . . . . . . . . . . . . . . . . . . 59
A.1 The Main SAP Documentation Types . . . . . . . . . . . . . . . 59
11/21/2008 PUBLIC 5/66

6/66 PUBLIC 11/21/2008
1 Getting Started
1 Getting Started
Caution
This guide does not replace the daily operations section that we recommend customers create for
their specific production operations.
1.1 About this Guide
Designing, implementing, and running your SAP solution at peak performance 24 hours a day has
never been more vital for your business success than now.
This guide provides a starting point for managing your SAP solutions and maintaining and running
them optimally. It contains specific information for various tasks and lists the tools that you can use
to implement them. This guide also provides references to the documentation required for these
tasks, so you may need to consult other Guides such as the Master Guide and SAP Library.
The following NetWeaver documentation is especially important and must be used in conjunction
with this SRM Application Operations Guide as the SRM guide covers only SRM-specific topics, not
general NetWeaver topics:
Document Found At:
Technical Operations Manual for SAP NetWeaver http://help.sap.com SAP NetWeaver SAP
NetWeaver 7.0 Including Enhancement Package 1 System
Administration Technical Operations Manual
Operations Guide for SAP NetWeaver http://help.sap.com SAP NetWeaver SAP
Administration Operations
SAP NetWeaver Security Guide http://help.sap.com SAP NetWeaver SAP
Administration Security Guide
Solution Life Cycle Management by Key Capability http://help.sap.com SAP NetWeaver SAP
NetWeaver 7.0 Including Enhancement Package 1 Functional
View SAP NetWeaver by Key Capability
11/21/2008 PUBLIC 7/66

1 Getting Started
1.2 Important SAP Notes
1.2 Important SAP Notes
Caution
Check regularly to see which SAP Notes are available for the Application Operations Guide.
SAP Note Number Title

19227 Get the latest saposcol
209834 CCMS agent technology
797147 Wily Introscope Installation for SAP Customers
1126859 End-to-End Diagnostics SP15
8/66 PUBLIC 11/21/2008

2 Overview of SAP Supplier Relationship Management 7.0
2 Overview of SAP Supplier Relationship

Management 7.0
SAP Supplier Relationship Management 7.0 (SAP SRM 7.0) is delivered to customers as a Business
Suite Application for procurement and sourcing requirements.
2.1 Technical System Landscape

SAP Supplier Relationship Management 7.0 (SAP SRM 7.0) is based on SAP NetWeaver 7.01 Technology
and consists of various components, each of which serve a specific function (as is described in the
Master Guide).
For more information on the components and business scenarios, please see the Master Guide
at http://service.sap.com/instguides Installation and Upgrade Guides SAP Business Suite
Applications SAP SRM SAP SRM Server 7.0 .
The following diagrams summarize the technical components included in SAP SRM.
2.1.1 ABAP Components
The ABAP Components of SAP Supplier Relationship Management 7.0 (SAP SRM) include:
n SRM Server
l SRM Server 7.0
l SRM Plus 7.0
l SRM Extended Functionality 7.0
11/21/2008 PUBLIC 9/66

l SRM Extension Plus 7.0
Figure 1:
2.1.2 Java Components
The JAVA Components of SAP Supplier Relationship Management 7.0 (SAP SRM) include:
n Live Auction Cockpit
n CCM with SRM MDM Catalog
n TREX
n XI Content
n BI Content
n Portal Content
n Portal Content Supplier
n SRM Java
10/66 PUBLIC 11/21/2008

Figure 2:
2.1.3 Additional Components
The Additional Components of SAP Supplier Relationship Management 7.0 (SAP SRM 7.0) include:
n SAP Frontend Business Client
l NetWeaver Business Client 7.10
l SAP GUI for Windows 7.10 CORE
Figure 3:
11/21/2008 PUBLIC 11/66

2.2 Software Component Matrix
2.2 Software Component Matrix

For an overview of SAP SRM business scenarios and their associated software units, in both Continuous
Innovation and Easy Adoption, see the Software Component Matrix for SAP SRM 7.0 on the SAP
Service Marketplace at http://service.sap.com/srm-inst SAP SRM SAP SRM Server 7.0
Note
The Continuous Innovation functions for SAP SRM 7.0, with some exceptions, require the use of SAP
NetWeaver 7.01. The Easy Adoption functions require SAP NetWeaver 7.0.
For the latest component version and patch level requirements, see SAP Service Marketplace at
http://service.sap.com/sp-stacks SAP SRM 7.0 and the Release Information Note, which is
available for each Support Package stack (SAP Note number is listed on the page).
Note
This Master Guide provides just one way to implement each business scenario. For other ways to
implement business scenarios, see the Scenario & Process Component list in SAP Service Marketplace
at http://service.sap.com/scl . The Scenario & Process Component list helps you to find
implementation alternatives for SAP solutions, business scenarios, and processes. It shows you which
application components are needed to implement a business scenario or process.
The exact locations of the required software components on the corresponding DVD(s) and
CD(s) that are shipped with the SAP SRM 7.0 package can be found at SAP Service Marketplace at
http://service.sap.com/instguides SAP Business Suite Applications SAP SRM SAP SRM 7.0 .
Note
For each component listed in the Software Component Matrix, there are software requirements that
are not explicitly mentioned in this documentation. Component-specific software requirements are
documented for a component in its installation guide. All related implementation guides are listed
in 6 References [external document].
You require SAP NetWeaver 7.0® TREX in the following cases:

n When you use the contract management application to search for information such as supplier
texts, internal notes, and attachments.
n When you want to use the metadata search functionality or use BI accelerator within Analytics.
2.3 Related Documentation
The following table lists where you can find more information about the technical system landscape.
12/66 PUBLIC 11/21/2008

2.3 Related Documentation
Topic Guide/Tool Location on SAP Service Marketplace/SAP Help Portal

SAP SRM 7.0 Master Guide http://service.sap.com/instguides Installation
and Upgrade Guides SAP Business Suite Applications
SAP SRM SAP SRM Server 7.0
Sizing Quick Sizer Tool http://service.sap.com/sizing SAP
NetWeaver SAP NetWeaver in Detail Solution
Life-Cycle Management Hardware Sizing Quick Sizer
Tool
Technical Configuration Technical http://help.sap.com SAP NetWeaver
Infrastructure SAP NetWeaver 7.0 Including Enhancement Package 1
Guide Installation, Configuration, Upgrade Installation &
Implementation Documentation Center Installation
Technical Infrastructure Guide
Scalability Technical http://help.sap.com SAP NetWeaver
High Availability Technical http://help.sap.com SAP NetWeaver
Security Technical http://help.sap.com SAP NetWeaver
11/21/2008 PUBLIC 13/66

This page is left blank for documents
that are printed on both sides.
3 Monitoring of SAP SRM
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions. The aim
of this section is to provide information and documentation required to configure the Computing
Center Management System (CCMS) and create a user-defined SAP SRM monitor set reflecting a
customer-specific SAP SRM system landscape.
For more information on the underlying technology, see the SAP NetWeaver Technical Operations Manual at
http://help.sap.com/nw70 SAP NetWeaver 7.0 Including Enhancement Package 1 System Administration
Technical Operations Manual
As SAP SRM 7.0 is powered by SAP NetWeaver 7.01 Including Enhancement Package 1, we recommend
that you set up the Monitoring Infrastructure as described in the Monitoring Setup Guide for SAP NetWeaver
(MSG) at http://help.sap.com/nw70 SAP NetWeaver 7.0 Including Enhancement Package 1 System
Administration Operations Monitoring .
The Monitoring Setup Guide (MSG) is the foundation for the following sections and contains all the
information relevant to monitoring the SAP NetWeaver components used in SAP SRM 7.0. Proficient
knowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up and
manage the user-defined SRM monitors recommended within this guide.
3.1 Alert Monitoring with CCMS

Proactive, automatic monitoring is the basis for ensuring reliable operations for your SAP system
environment. SAP SRM provides you with the infrastructure and recommendations on how to set up
your alert monitoring in CCMS to recognize critical situations for SAP SRM as quickly as possible.
For more information, see the Monitoring Setup Guide for SAP NetWeaver (MSG) at
http://help.sap.com/nw70 SAP NetWeaver 7.0 Including Enhancement Package 1 System Administration
Operations Monitoring .
To configure alert monitoring with CCMS for SAP SRM 7.0, you must set up a Central Monitoring
System (CEN) and connect all SAP SRM 7.0 components to this CEN system. For a list of these
components and the business scenarios for which they are relevant, see section 2.2Scenario/Component
Matrix [external document].
You can access the SRM Server Monitoring templates, called SAP (CEN) EnterpriseBuyer Monitors,
using transaction RZ20 (see section 3.1.2.4 SAP SRM Monitor [page 25] for full details).
For more information, see the SRM Master Guide on the SAP Service Marketplace at
http://service.sap.com/instguides Installation and Upgrade Guides SAP Business Suite
11/21/2008 PUBLIC 15/66

Since SAP SRM 7.0 utilizes the complete SAP NetWeaver 7.0 Including Enhancement Package 1 stack,
you have to apply the SAP NetWeaver Monitoring Setup Guide (MSG) to the SAP SRM components
first. In addition to this, you can define special SAP SRM monitors in the CEN system’s CCMS.
3.1.1 CCMS Monitoring Installation and Setup

To enable the auto-alert mechanism of CCMS, see SAP Note 617547.
Recommendation
SAP recommends the usage of SAP NetWeaver 7.0 including enhancement package 1 for Central Monitoring.
3.1.2 Alert Monitoring of Components

One approach for monitoring an SAP SRM landscape is to monitor each component separately in the
CEN system. The other approach is to monitor across components based on a business scenario.
This section gives you an overview of how each SAP SRM component could be monitored using
CCMS. Which components need to be monitored depends on the SAP SRM scenario(s) implemented.
For more information, see section 2.2 Scenario/Component Matrix [external document].
Note
This monitoring set for SAP SRM 7.0 includes component-related monitors such as for SAP SRM 7.0
and Live Auction Cockpit 7.0 (LACWPS 7.0). These monitors are not delivered by SAP but can be
created in the CEN system. All Monitoring Tree Elements (MTE) used for these monitors are based
on the default monitoring templates delivered by SAP.
For information on editing or creating monitors and monitor sets, see the SAP NetWeaver
Monitoring Setup Guide (MSG) at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0
Including Enhancement Package 1 System Administration Operations Monitoring .
3.1.2.1 SAP NetWeaver 7.01 Monitoring
SAP NetWeaver 7.01 is the integration and application platform for SAP SRM 7.0, therefore the
following SAP NetWeaver components must be integrated into the monitoring infrastructure:
n SAP Web Application Server (ABAP) 7.01 [for SAP SRM 7.0]
n SAP Web Application Server (Java) 7.01 [for SAP LACWPS 7.0]
n SAP NetWeaver Usage Type Process Integration (PI)
n SAP NetWeaver Enterprise Portal 7.01
n SAP NetWeaver Business Intelligence 7.01 (SAP NetWeaver BI)
16/66 PUBLIC 11/21/2008

n For more information and detailed procedures, please see the SAP NetWeaver Monitoring Setup
Guide (MSG) at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 Including Enhancement
Package 1 System Administration Operations Monitoring and SAP NetWeaver 7.01 Technical
Operations Manual at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 Including
Enhancement Package 1 System Administration Technical Operations Manual .
3.1.2.2 Monitoring SAP SRM Server 7.0
The main component in your SAP SRM Solution is the SAP SRM 7.0. It is based on SAP Web
Application Server (ABAP) 7.01. For more information, please see the SAP NetWeaver Monitoring
Setup Guide (MSG) at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 Including
Enhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 7.01
Technical Operations Manual at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0
Including Enhancement Package 1 System Administration Technical Operations Manual .
Prerequisites
n Your SAP SRM Server 7.0 is connected to the CEN and registered as a remote system.
n The SAPCCM4X agent is registered and running for each SAP SRM Server 7.0 instance.
What to Monitor
Your SAP SRM Server 7.0 is running on SAP Web Application Server (ABAP) 7.01 ‒ which means the
primary points of failure are within the technical infrastructure.
Procedure
1. Go to transaction RZ20 and create a new monitor: SAP SRM Server 7.0 monitor.
2. On the top level, create a virtual node for each of the following areas:
n Back-end Monitoring
n Database
n Operating System
n System Configuration
n Log File Monitoring
3. On the second level, create rule-based monitors for each area as described in the following table:
Node Type Parameter Value
R/3 Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System <SRMServer_Systems>
Dialogue Response Time Virtual
Rule R3System <SRMServer_Systems>
MTEClass R3DialogResponseTime
11/21/2008 PUBLIC 17/66


Network Time Virtual
CCMS_GET_MTE_BY_CLASS Rule R3System <SRMServer_Systems>
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
MTEClass R3UsersLoggedIn
Database Virtual
MTEClass OperatingSystem
Operating System Virtual
MTEClass OperatingSystem
System Configuration Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System <SRMSERVER_SYSTEMS>
Dialog Response Time Virtual
CCMS_GET_MONITORING_CON- Rule R3System <SRMSERVER_SYSTEMS>
TEXT_NAMES
MoniSegment <ANY>
MoniContext System Configuration
Log File Monitoring Virtual
CCMS_GET_MTE_BY_CLASS Rule R3System <SRMSERVER_SYSTEMS>
MTEClass CcmsFileMonitoring no such MTE
class exists, needs to be changed to
filesystemMO
3.1.2.3 Monitoring of SAP LACWPS 7.0
3.1.2.3.1 GRMG Availability Monitoring for SAP LACWPS 7.0
Note
LACWPS 7.0 is Java applet front end for users with application, business and database management in
SAP SRM Server.
18/66 PUBLIC 11/21/2008

LACWPS 7.0 uses SAP SRM Server for data persistence and business logic, the MTE Auction (see section
3.1.2.4 SAP SRM Monitor [page 25]) takes care of the monitoring of LACWPS 7.0 application-specific
monitoring.
The following information is for setting GRMG heartbeat monitoring.
The Live Auction Cockpit runs on SAP Web Application Server (Java) 7.01 so the main focus of
monitoring this component is the monitoring of the SAP J2EE Engine.
For more information, see the SAP NetWeaver Monitoring Setup Guide (MSG) at
http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 Including Enhancement Package 1
System Administration Operations Monitoring and the SAP NetWeaver 7.01 Technical Operations
Manual at http://help.sap.com/nw70 SAP NetWeaver 7.0 Including Enhancement Package 1 System
Administration Technical Operations Manual .
3.1.2.3.2 Activating GRMG Monitoring
1. Obtain the XML format customizing files for the GRMG monitoring scenarios of Live Auction
Cockpit.
A GRMG customizing file tells the central monitoring system to run a particular GRMG
availability monitoring scenario ‒ that is, to monitor the availability and condition of a particular
component.
The GRMG customizing file is named la_grmg.xml for Live Auction Cockpit and it can be found
in <INSTDIR>:\usr\sap\<system name>\SYS\global\srmla\monitoring.
2. To adjust the customizing files, you need to edit the la_grmg.xml file using an XML editor or any
plain text editor. Change the URL specified in the <scenstarturl> element of the customizing file
to the correct hostname and port of your installation.
Example
If your installation uses hostname yourhostname on port 8080 then the value in between the
<scenstarturl> and </scenstarturl> tags should be:
<scenstarturl>http://yourhostname:8080/srm/heatBeat</scenstarturl>
Note
Each instance of Live Auction Cockpit that is to be monitored, is considered a scenario and needs
to be executed by the GRMG framework.
To monitor more than one instance of Live Auction Cockpit, you need to specify each of the
scenarios in the XML customizing file. For more information, see section Adding Scenarios to
the XML Customizing File (below).
3. Upload the customizing file into the central monitoring system.
11/21/2008 PUBLIC 19/66

a) Log on to the monitoring system as a user with administrator rights.

Make sure that you log on to the central application server. This is the server which offers the
enqueue service. You can determine which server is your central server with transaction SM51
or with transaction RZ03.
b) Start transaction GRMG by entering grmg in the OK field in the SAPGUI toolbar.
c) Click Upload a GRMG Scenario.
A file-selection dialog box is displayed.
d) Navigate to the directory in which the customizing file is located and select the file.
e) Click Open to upload the file.
In the first production release of this transaction, no confirmation message is presented. For
more information on verifying GRMG settings, see Verifying the GRMG Availability Monitoring
(below).
4. After you have uploaded all of the customizing files, start the availability monitoring.
Caution
Be sure that you are logged on to the central application server of the monitoring system before
carrying out this step. The central server is the one that offers the enqueue service. You can
determine which server this is in transaction SM51 or transaction RZ03.
To start the GRMG availability monitoring, click Start all scenarios in transaction GRMG.
Result
The function displays no confirmation message that the availability monitoring has started. For
more information on verifying GRMG settings, see section 3.1.2.3.3 Verifying the GRMG Availability
Monitoring [page 21].
Once you start GRMG monitoring, the monitoring scenarios which you installed run automatically.
The CCMS monitoring architecture repeats each GRMG availability monitoring scenario
automatically every ten minutes by default.
Adding Scenarios to the XML Customizing File

1. Copy everything in between the tags (including the tags themselves): <scenario> and
</scenario>.
2. Paste them below the last <scenario> tag.
3. Repeat this step for each additional instance you wish to monitor.
4. Modify the values in between <scenversion> and </scenversion>, and <sceninst> and
</sceninst>, so that they are unique for each instance.
Recommendation
We recommend that you use a value of 001 for the first instance and then increment the value by
one for each additional instance (002, 003, and so forth).
20/66 PUBLIC 11/21/2008

5. Change the URL specified between the <scenstarturl> and </scenstarturl> tags to the correct
and fully qualified hostname and port for this particular scenario.
3.1.2.3.3 Verifying the GRMG Availability Monitoring
Displaying Scenario Execution Status

This section describes how to verify that GRMG availability monitoring is running correctly and also
describes procedures for analyzing problems.
GRMG uses a hierarchical monitoring tree to report whether or not it was able to run an availability
monitoring scenario successfully.
1. Log on to the monitoring system as a user with administrator rights.
2. Start transaction RZ20.
The transaction presents the list of standard monitor collections in your system.
3. Expand the monitor collection named SAP CCMS Technical Expert Monitors.
The list of monitors in this collection is displayed.
4. Double-click on the monitor named All Monitoring Contexts.
The monitoring tree that reports the status of the monitoring architecture is displayed.
5. Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the
value specified for the element <scendesc> in the XML customizing file.)
You should now see a further subtree with the name Web Server of SRM Live Auction Scenario.
6. Expand the Web Server of SRM Live Auction Scenario node to open the subtree.
The following screen shot depicts an example of what you can expect to see:
Figure 4:
11/21/2008 PUBLIC 21/66

Result
If the Web Server of SRM Live Auction Scenario subtree is present and is green, then all GRMG monitoring
scenarios are running correctly; the GRMG application was contacted and returned a valid answer.
As the Heartbeat message indicates, you can view the availability data in the normal scenario subtree,
under the full name of the scenario.
If the Web Server of SRM Live Auction Scenario subtree is missing or the subtree or any of its branches are
red (red alert) or white (monitoring inactive), then an error occurred. For more information, see
section 3.1.2.3.4 Troubleshooting GRMG Availability Monitoring [page 22].
3.1.2.3.4 Troubleshooting GRMG Availability Monitoring
No GRMG_SelfMonitoring Subtree Found

If you were unable to verify the GRMG availability monitoring as described in secion 3.1.2.3.3 Verifying
the GRMG Availability Monitoring [page 21], then one of the following is most likely the cause:
n The GRMG availability monitoring was not started on the central application server of your
SAP system.
1. Check for other MoniInfra_<server name> subtrees in the CCMS Selfmonitoring monitor.
2. Delete any such trees.
3. Start GRMG monitoring on the central application server.
n None of the GRMG customizing files that you uploaded could be correctly processed.
1. Check the customizing by using transaction SE16 to display the entries in the following GRMG
customizing tables:
Customizing Table Required Contents
GRMG_SCENARIOS l The technical name [SCEN_NAME] of each
monitoring scenario that you uploaded
l The URL used by the scenario to test availability
GRMG_SCENARIO_T A descriptive name for each technical name
[SCEN_NAME] in GRMG_SCENARIOS
GRMG_PROPERTIES At least one entry for each technical name
[SCEN_NAME] in GRMG_SCENARIOS
GRMG_COMPONENTS An entry for each component name
[COMP_NAME] in GRMG_PROPERTIES
GRMG_COMPONENT_T A descriptive name for each component name
[COMP_NAME] in GRMG_COMPONENTS
If any of the required table content is missing, then the customizing file did not contain
complete or valid XML customizing data for GRMG.
22/66 PUBLIC 11/21/2008

2. Download the newest customizing files from the SAP Service Marketplace at the Internet
address service.sap.com/monitoring .
Caution
Do not attempt to correct customizing directly in the customizing tables. Instead, correct the
problems by editing the customizing XML file and uploading the file again.
GRMG_SelfMonitoring Subtree Found with Errors

If you were able to find the GRMG_SelfMonitoring subtree, click on the subtrees to open them and
display the execution status of each scenario.
A scenario error means that the monitoring architecture was unable to run the scenario. Possible
reasons include:
n The host specified in the scenario URL may have been unreachable.
n No answer was received.
n An invalid answer was received.
If a scenario error has occurred, then the scenario error tree looks similar to the following:
Figure 5:
In this example, an HTTP communication failure occurred. This means that the HTTP POST during
the GRMG monitoring request could not be completed successfully. The most likely cause is that
the HTTP server does not exist or was not running. The Heartbeat node includes the error messages
returned by the monitoring architecture as it tried to run the scenario.
Whenever a scenario error occurs, only the scenario error subtree is created or updated — not the
normal monitoring subtree — to allow the monitor to distinguish between failure to execute a
scenario, which may have many causes, and the non-availability of the monitored components. A
scenario failure does not necessarily mean that the monitored components are unavailable.
11/21/2008 PUBLIC 23/66

GRMG continues attempting to run each scenario every ten minutes (or whatever interval you have
defined), even if the scenario execution ends in a scenario error.
Possible scenario error messages and the most likely causes:
GRMG Scenario Error Message Cause

Reason for HTTP POST failure: 1. The URL specified in the scenario customizing
n HTTP communication failure points to a non-existent host or port.
n Connect failed Check that the URL is valid.
n Time-out occurred
2. The HTTP server specified in the URL is not
running.
Start the HTTP server if it is not running. If the
GRMG application runs on the same server as the
monitored components, then this error message
also means that the tested components are not
available.
Reason for HTTP POST failure: Your installation is having problems with the network
n TCP/IP error occurred configuration or with network operation.
n Data error occurred
Reason for HTTP POST failure: There is a problem with the HTTP service in the SAP
n Internal error occurred system you are using for monitoring. Check on the
status of this service with transaction SMICM.
Reason for HTTP POST failure: There is a problem with the HTTP server specified in
n System failure occurred the scenario URL.
Reason for HTTP POST failure: There is a problem with the HTTP client function
n Argument not found in the SAP system you are using for monitoring.
n Plug-in not active Check on the status of your HTTP operations with
l Internal error transaction SMICM.
l HTTP invalid state
Reason for HTTP POST failure: You are using an RFC destination of type HTTP
n Destination not found instead of specifying a URL directly in scenario
n Not authorized to use HTTP destination customizing.
The destination has either not been defined, or there
is a destination use authorization problem.
Reason for scenario failure: This scenario error often occurs when an HTML
n <no error message> response rather than an XML response has been
returned from the server specified in the scenario
URL. In this case, the XML parse engine may not
return specific errors that can be output in the
scenario error message.
Typically, such a scenario error means that the
GRMG application targeted in the scenario URL is
not installed at the target host.
The web server may return an HTML page with a
code 404 (page not found) message, or may return
some other non-XML response which confuses the
XML parser.
24/66 PUBLIC 11/21/2008

GRMG Scenario Error Message Cause

You should check that the GRMG application is
installed and runs correctly at the target host.
Reason for scenario failure: This error message may occur if a GRMG application
n No response for any component in request responds without reporting the status of any of the
n <no error message> components specified in the GRMG monitoring
request.
Check that the components specified in the GRMG
customizing file match those checked by the GRMG
application.
You can also compare the GRMG request and
response directly by switching on HTTP tracing briefly
(level 3) in transaction SMICM on the central server
of your monitoring system.
Reason for scenario failure: A formal DTD error, such as unbalanced tags,
n <Any message relating to invalid XML format> occurred in the response.
n <no error message> You can view the response directly by switching on
HTTP tracing briefly (level 3) in transaction SMICM
on the central server of your monitoring system.
Reason for scenario failure: There is a problem in the CCMS monitoring
n Any message having to do with the CCMS architecture.
monitoring architecture, such as Check the alerts elsewhere in the CCMS
- Invalid TID Selfmonitoring monitor for possible causes. Be sure,
- Wrong segment as well, that you have started GRMG monitoring only
on the central server of the SAP system that you are
using for monitoring.
3.1.2.4 SAP SRM Monitor
Note
In earlier releases, SAP SRM used to be known as SAP Enterprise Buyer. This is still reflected in the
name of the monitor tool, which is called SAP EnterpriseBuyer Monitors.
To reduce administrative tasks for system administration and monitoring, we recommend that
you create a separate monitor set with the SRM monitoring area, SAP (CEN) EnterpriseBuyer
Monitors, which includes multiple isolated monitors summarized into one single monitor. This
provides you with a simple separation between the middleware and SAP SRM Server.
Procedure
1. Go to transaction RZ20 and create a new monitor under the SRM monitor set created earlier: SAP
(CEN ) EnterpriseBuyer Monitors.
n Approval
11/21/2008 PUBLIC 25/66

n Auction
n Bid Invitation
n Component Planning
n Confirmation
n Contract Management
n Invoice
n Others
n Procurement Card
n Purchase Order
n Shopping Cart
n User Administration
3. On the second level, enter all MTE classes as rule-based monitors for each area as described in
the table below:
Approval Virtual
CCMS_DE- Rule R3System <SRMSERVER_SYSTEMS>
FINE_R3_SYSTEMS
CCMS_GET_MTE_BY_ Rule R3System <SRMSERVER_SYSTEMS>
CLASS_AND_CLIENT
R3Client <EBP Client>
MTEClass BBP_Approval
Auction Virtual
FINE_R3_SYSTEMS
CLASS_AND_CLIENT
MTEClass BBP_AUC
Bid Invitation Virtual
FINE_R3_SYSTEMS
CLASS_AND_CLIENT
MTEClass BBP_BID
Component Planning Virtual
FINE_R3_SYSTEMS
26/66 PUBLIC 11/21/2008


CLASS_AND_CLIENT
MTEClass BBP_PM
Confirmation Virtual
FINE_R3_SYSTEMS
CLASS_AND_CLIENT
MTEClass BBP_Confirmation
Contract Management Virtual
FINE_R3_SYSTEMS
CLASS_AND_CLIENT
MTEClass BBP_Contract
Invoice Virtual
FINE_R3_SYSTEMS
CLASS_AND_CLIENT
MTEClass BBP_INV
Others Virtual
FINE_R3_SYSTEMS
CLASS_AND_CLIENT
MTEClass BBP_OT
Procurement Card Virtual
FINE_R3_SYSTEMS
CLASS_AND_CLIENT
MTEClass BBP_PC
Purchase Orders Virtual
11/21/2008 PUBLIC 27/66


FINE_R3_SYSTEMS
CLASS_AND_CLIENT
MTEClass BBP_PO
Shopping Cart Virtual
FINE_R3_SYSTEMS
CLASS_AND_CLIENT
MTEClass BBP_ShoppingBasket
User Administration Virtual
FINE_R3_SYSTEMS
CLASS_AND_CLIENT
MTEClass BBP_US
3.1.2.5 Monitoring SAP SRM-MDM Catalog 3.0
3.1.2.5.1 SAP SRM-MDM Catalog 3.0
Note
SAP SRM-MDM Catalog is a Java WD Component for users with Database Repository in MDM
Server. SRM Server Transactions are connected to Catalog using Open Catalog Interface.
Note
For Details of MDM Core CCMS Monitoring Functionality refer to SAP Note 1008290.
SAP SRM-MDM Catalog 3.0 uses Data Repository of MDM Core (MDS and MDIS) for processing,
combined monitoring of MDM Core and SRM Server MTE Shopping Cart (see section 3.1.2.4), for post
process monitoring takes care of monitoring for SRM MDM Catalog.
The following information is for setting GRMG heartbeat monitoring for SRM-MDM Catalog.
28/66 PUBLIC 11/21/2008

3.1.2.5.2 GRMG Availability Monitoring for SAP SRM-MDM

Catalog 3.0
The SAP SRM-MDM Catalog runs on the SAP Web Application Server (Java) 7.01, so the main focus of
monitoring this component is the monitoring of the SAP J2EE Engine.
You can find information about monitoring the Web AS (Java) in the SAP NetWeaver Monitoring
Setup Guide (MSG) at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 Including
Enhancement Package 1 System Administration Operations Monitoring and the SAP NetWeaver 7.01
Technical Operations Manual at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0
Including Enhancement Package 1 System Administration Technical Operations Manual .
Prerequisites
n Your SRM MDM Catalog is connected to the CENtral monitoring System (CEN) and registered
as a remote system.
n The SAPCCMSR agent is registered and running for each SRM MDM Catalog instance.
Apart from the SAP J2EE Engine, the availability of the SRM MDM Catalog component can be
monitored using the GRMG technology of the CCMS.
Procedure
1. Go to transaction RZ20 and create a new monitor: SAP SRM-MDM Catalog UI
n J2EE Engine 7.01 on <Hostname>
n GRMG Availability Monitor
3. On the second level, create rule-based monitors for each area as described in the following table:
J2EE Engine 7.00 on <Hostname> Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
CCMS_GET_MTE_BY_CLASS Rule R3System J2EE_Systems
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System <CURRENT>
CCMS_GET_MTE_BY_CLASS Rule R3System <CURRENT>
MTEClass GRMG_<ScenName>
11/21/2008 PUBLIC 29/66

3.2 Detailed Monitoring and Tools for Problem and Performance Analysis
3.2 Detailed Monitoring and Tools for Problem and

Performance Analysis
3.2.1 Component-Specific Analysis Tools
3.2.1.1 SAP Supplier Relationship Management (SAP SRM) 7.0
SAP SRM 7.0 is technically based on SAP NetWeaver 7.01.

For information about technical problem analysis (for example, for database, operating system,
workload analysis, and so forth), see the SAP NetWeaver 7.01 Technical Operations Manual at
http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 Including Enhancement Package 1 System
The SAP SRM Application Operations Guide covers only differences and additional information
specific to the SAP SRM solution.
SAP SRM 7.0 application-specific logging information is written into the application log.
3.2.1.2 SAP Live Auction Cockpit Web Presentation Server

(LACWPS) 7.0
SAP LACWPS 7.0 is technically based on SAP NetWeaver 7.01

Note
LACWPS uses the SRM Server as its persistence layer, therefore detailed problem and performance
analysis must be done in both the LACWPS and in the SRM Server.
3.2.1.3 SAP SRM-MDM Catalog 3.0
SAP SRM-MDM Catalog 3.0 is technically based on SAP NetWeaver 7.01.

workload analysis, and so forth), see the SAP NetWeaver 7.01 Technical Operations Manual
30/66 PUBLIC 11/21/2008

http://sap.help.com/nw70 SAP NetWeaver Including Enhancement Package 1 System Administration

Technical Operations Manual .
The SAP SRM Applications Operations Guide covers only differences and additional information
3.2.2 Scenario Problem Analysis Tools

The following information applies to all SAP SRM 7.0 business scenarios.
3.2.2.1 Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and HTTP.
Administration Operations Monitoring and the SAP NetWeaver 7.01 Technical Operations Manual
at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 Including Enhancement Package 1
System Administration Technical Operations Manual .
3.2.2.2 Data Archiving Monitors
Administration Operations Monitoring and the SAP NetWeaver 7.01 Technical Operations Manual
System Administration Technical Operations Manual .
3.2.2.3 Distributed Statistical Records
For more information on the motivation behind distributed statistical records and how to define and
use them, see the SAP NetWeaver Monitoring Setup Guide (MSG) at http://help.sap.com
SAP NetWeaver SAP NetWeaver 7.0 Including Enhancement Package 1 System Administration Operations
Monitoring .
11/21/2008 PUBLIC 31/66

3.2.2.4 Business Packages
For more information regarding the analysis and monitoring of Business Packages and SAP Enterprise
Portal, see the SAP NetWeaver 7.01 Technical Operations Manual at http://help.sap.com SAP
NetWeaver SAP NetWeaver 7.0 Including Enhancement Package 1 System Administration Technical Operations
Manual .
For information about how to monitor the cache upload of the Business Package for Supplier
Collaboration, see SAP Note 749231.
3.2.3 Logs and Trace (Component or Scenario-Specific)
For LACWPS 7.0: Component specific monitoring

Logging Categories /Applications/SRMLA
Tracing Locations com.sap.srm.la
For SRM‒MDM 3.0: Component specific monitoring

Logging Categories /Apllications/MDM*
Tracing Locations com.sap.mdm.srmcat
Logging and tracing for ABAP components is done using transaction SLG1. Each log in the database
also has the attributes Object and Sub-object. These attributes describe the application which wrote the
log, and classify this application. You can find the object and sub-objects of SAP SRM applications
in the following list:
Software Component Object Sub-object Object text
SAP SRM SERVER /SAPSRM/* All Sub-objects
/SAPPSSRM/* All Sub-objects

BBP* Sll Sub-objects
32/66 PUBLIC 11/21/2008

4 Management of SAP SRM
SAP provides you with an infrastructure to help your technical support consultants and system
administrators effectively manage all SAP components and complete all tasks related to middleware
technology.
You can find more information about the underlying technology in the Technical Operations Manual at
http://help.sap.com/nw70 SAP NetWeaver 7.0 including enhancement package 1 System Administration
Technical Operations Manual .
4.1 Administration Tools of Software Components

All SAP SRM 7.0 components are technically based on SAP NetWeaver. 7.01. For information on
the relevant administration tools, see the SAP NetWeaver 7.01 Technical Operations Manual at
4.2 Software Configuration
All SAP SRM 7.0 components are technically based on SAP NetWeaver. 7.01. For information on
the relevant configuration tools, see the SAP NetWeaver 7.01 Technical Operations Manual at
http://help.sap.com SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 System
J2EE based components store their technical configuration parameters in the Configuration Manager
(CM) repository. For more information, see the SAP NetWeaver 7.01 Technical Operations Manual at
at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 Including Enhancement Package 1 System
Administration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (Application
Server for Java) Management Tools Config Tool .
11/21/2008 PUBLIC 33/66

4.3 Starting and Stopping
SAP SRM SERVER Configuration Tool(s) Detailed Description

SAP SRM SERVER Implementation Guide (IMG) The IMG is the standard SAP tool
for ABAP-based system used for
Component Customizing.
Use transaction SPRO to access the
IMG
SAP SRM SERVER SAP Solution Manager SAP Solution Manager is the
standard SAP tool for process- and
scenario-based configuration.
See SAP Note 1230438.
4.3 Starting and Stopping

The following information is scenario-independent.
Start and Stop Sequence and Tools
Software Component Start and Stop Sequence and Tools
Sequence Tool Documentation:
SAP Process Integration 1 n STARTSAP (UNIX) SAP NetWeaver 7.01 Technical
Server, PI (also known n SAP Management Operations Manual at
as SAP Exchange Console (Windows) http://help.sap.com
Infrastructure, XI) SAP NetWeaver SAP NetWeaver
7.0 Including Enhancement Package 1
Enterprise Buyer 2 n STARTSAP (UNIX) System Administration Technical
back-end (OLTP) n SAP Management Operations Manual .
Console (Windows)
SRM Server 3 n STARTSAP (UNIX)
n SAP Management
Console (Windows)
TRex 5 n Start Services
(Windows)
n Start Daemons (UNIX)
SAP LACWPS 7.0 6
Only if SAP Web
Application Server
7.01 (Java) is installed
standalone ‒ in case of
Add-In installation it is
started together with the
SRM Server
34/66 PUBLIC 11/21/2008

4.4 Backup and Restore

To ensure that you can restore and recover your system in case of failure, you should back up your
system landscape regularly.
The backup and restore procedure for SAP SRM consists of two parts:
n Backup and restore for each component
n Cross-system data dependencies and handling
The backup and restore process for your system landscape should not only consider SAP systems.
It should be embedded in your overall business requirements and take into account the overall
process flow of your company.
In addition, the backup concept must cover disaster recovery processes, for example loss of your
data center due to fire. Most important in this context is to ensure that backup devices are not lost
along with normal data storage. For more information, see section 8.1 Categories of System Components for
Backup and Restore [page 55]).
Based on the type of application data a component holds, we have used a categorization scheme that
can be used to analyze the backup requirements of any system component and to easily determine an
appropriate backup method for this component. The following table contains the component list
of the solution and the appropriate categories:
Component Category Application Data Type Backup Method for
Application Data
SAP SRM Server XI Original and Replicated n Database and log
backup
n File system backup
(full and/or
incremental)
SAP LACWPS (Add-In XI Original and Replicated n Included in SRM
Installation SRM Server) Server
SAP LACWPS (using VIII Original n Data is stored on SRM
standalone SAP WAS Java) Server
n Database and log
backup
(full and/or
incremental)
n New installation
SAP NetWeaver PI XI Original and Replicated n Database and log
backup
(full and/or
incremental)
SAP NetWeaver TREX III / IV n File system backup
11/21/2008 PUBLIC 35/66

4.4.1 General Remarks
Caution
This information assumes that readers are familiar with database and server administration and
therefore does not explain how to back up a relational database management system (RDBMS) or a
file system. If you have questions, contact your IT staff, and refer to the operations manuals provided
by your database and operating system suppliers.
SAP solutions use several SAP component systems to implement cross-system processes. Data is no
longer held centrally in a single system; instead it is distributed between several SAP components.
Due to the non-transactional character of the document workflow between the different landscape
components involved within one SAP SRM business scenario, it is impossible to find a common point
of consistency across the whole SAP SRM landscape.
The only backup type that can guarantee full physical and logical consistency (these terms are
explained below) of an SAP SRM landscape is an offline backup of the whole landscape conducted
after all business users have logged off and the complete business workflow has ended. Tools offering
manageability and monitoring of these tasks do not yet exist.
n Logical Consistency
Restores the SAPSRM system landscape (cross-system data consistency) to a consistent state. The
restoration applies at document level at the time of the backup. This includes the successful
roll-back of all open business transactions with respect to the exchange of documents (if a purchase
order is sent but a purchase order response has not yet been received, for example).
n Physical Consistency
Restores individual SAP SRM components to a consistent state, followed by a successful startup
of the restored components, and a successful reconnection to other components. Physical
consistency provides a working SAP SRM runtime in which newly created business documents can
be exchanged. It is required to develop a transactional conduct on user level to react to broken
workflows and outdated documents appearing after the restoration.
A distributed, business system landscape requires a detailed B & R concept. This concept must
account for both the business data (which is contained in databases) and the runtime infrastructure.
Regular backups keep the downtime of the system landscape to a minimum during restoration of
the infrastructure and business data. We recommend a backup after the initial installation and
configuration of the system landscape. We also recommend a backup after changes (this means
changes to the configuration, software upgrade of individual components, or replacement of
components) are made to the system landscape, depending on the frequency of such changes.
When you decide which infrastructure components to back up, consider the following factors:
n Time required for a complete reinstallation
n Time required for additional configuration
36/66 PUBLIC 11/21/2008

n Effects of the expected downtime of one or more infrastructure components with regard to the
overall availability of the SAP SRM landscape
Note
We recommend that you back up the runtime infrastructure of all the components of an SAP SRM
landscape.
You must test your B&R concept regularly. A single B&R test is insufficient, since the SAP SRM
landscape is likely to change, and render a given concept redundant. System administrators need an
up-to-date B&R concept to be able to quickly restore failed systems.
For more Information, For more information, see the SAP NetWeaver 7.01 Technical Operations
Manual at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 Including Enhancement Package
1 System Administration Technical Operations Manual .
4.4.2 Backup of Individual Components in an SAP SRM

Landscape
When you plan a B&R strategy for application, software, and configuration files, you must consider
the following elements:
n Operating system
n RDBMS data files
n RDBMS software
n SAP software and file systems
n Log files (SAP and other)
n Software of other system components (file systems and configuration files)
Note
A component that has application data (database, for example) is usually also comprised of
application software and configuration files (runtime infrastructure) that need to be backed up.
A component that contains no application data may still be comprised of configuration files and
software that do require a backup.
4.4.2.1 B&R for Operating System, Software, and

Configuration Data
Apart from business-critical application data (generally held in databases), it may also be worthwhile
to back up the system and application software (including configuration files). If you do this, you do
not have to reinstall the system and application software if the software becomes damaged.
11/21/2008 PUBLIC 37/66

While it is always possible to reinstall the operating system, software, and configuration data,
reinstallation and configuration take a long time. Therefore, if a backup of the software and
configuration is available, you can reduce the time needed to restore your system after a system failure.
While data that is contained in the RDBMS can be backed up online, it is not possible to do the
same for the runtime infrastructure. If you perform a backup while the server is running, open
files may not be backed up.
Online Backup
The data contained in the database can be backed up online; however, it is not possible to do the
same for the runtime infrastructure.
An online backup refers to the system landscape and not the databases that contain the
business-critical application, or the infrastructure components.
Note
If you perform a backup while the server is running, open files may not be backed up.
File System Backup Versus Full System Backup

A file system backup only applies to specific files or file systems, whereas a full system backup applies
to all files and file systems, the operating system.
Recommendation
We recommend that you perform a full system backup after installation, that you back up the file
systems of both the installed software and the operating system on a regular basis.
For more information on possible backup scenarios, see SAP Service Marketplace at
http://service.sap.com/atg Advanced Technology Group Backup & Restore .
4.4.2.2 Database B&R
Note
We recommend that you run the database in archive mode. This means all actions on the database
that modify data are recorded by the database and written to a transaction log.
With regular full backups of your database (either offline or online), as well as a complete set of
transaction logs since the last backup, it is possible to restore a crashed database to any point in time
before the database crashed.
Note
We recommend that you back up your database every day, with several backups of the log files
during the day as the log files fill up.
38/66 PUBLIC 11/21/2008

4.4.2.3 B & R for SAP Web Application Server (WebAS) 7.01
Back up the file system in which the application software is installed.
Note
We recommend regular file system backups (at least after software changes and upgrades, for
example kernel upgrades and service packs). Perform a full system backup after installation and
upgrades of the operating system and the SAP software.
For more information, see the SAP NetWeaver 7.01 Technical Operations Manual at
4.4.3 B&R for Individual System Components
4.4.3.1 SAP Live Auction Cockpit Web Presentation Server

(LACWPS) 7.0
SAP LACWPS 7.0 is technically based on SAP NetWeaver 7.01

Note
LACWPS uses the SRM Server as its persistence layer, therefore detailed problem and performance
analysis must be done in both the LACWPS and in the SRM Server.
4.4.3.2 SAP SRM-MDM Catalog 3.0
11/21/2008 PUBLIC 39/66

4.4.4 B&R for a Complete SAP SRM Landscape
4.4.4.1 Landscape Shutdown
You have to shut down the individual components in the following sequence:
SAP Live Auction
n Shut down the SAP J2EE server that is connected to the SAP SRM Server back-end system.
Integrated Catalog
n Shut down the J2EE Engine on which the integrated catalog is installed.
Catalogs
n Shut down the SAP J2EE Engine on which the catalogs are installed and
shut down the underlying RDBMS.
SAP SRM Server
n Make sure that all outgoing documents have been sent and all incoming documents have been
processed. Shut down the ABAP-based part of SAP SUS and the underlying RDBMS.
Backend System (OLTP)
n Shut down the SAP system and the underlying RDBMS.
SAP NetWeaver PI server
n Shut down the XI server and the underlying RDBMS. (The J2EE Engine shuts down automatically
when back-end is stopped.)
4.4.4.2 Offline Backup of the SAP SRM Landscape
To back up the individual components of the landscape, proceed as described in section in section
4.4.2 Backup of Individual Components in an SAP SRM Landscape [external document].
Note
When you back up the SAP NetWeaver PI server, make sure that you also back up the file
system. This is required, because the file system contains the SAP J2EE Engine together with the
necessary configuration files for the system landscape directory and the document transformation
(/usr/sap/<SID>SYS/global/xi...).
40/66 PUBLIC 11/21/2008

4.5 System Copy
4.4.4.3 Landscape Startup
For the startup sequence of the individual components, see section 4.3Starting and Stopping [page 34].
4.4.5 B&R for an SAP SRM Business Scenario

To back up an SAP SRM business scenario, you have to apply the B&R steps of the components that
comprise a business scenario. For these steps, see:
n section 4.4.2Backup of Individual Components in an SAP SRM Landscape [page 37]
n section 4.4.3B&R for Individual System Components [page 39]
To see which components are required for a specific business scenario, see section 2.2Software Component
Matrix [external document].
4.5 System Copy

For more information on prerequisites, procedures, and limitations for copying components of SAP
SRM, see the SAP NetWeaver 7.01 system copy guides at http://help.sap.com/ SAP NetWeaver
SAP NetWeaver 7.0 Including Enhancement Package 1 Installation, Configuration, Upgrade Installation &
Implementation Documentation Center Installation 2 - Installation - SAP NetWeaver Systems .
4.6 Scheduled and Manual Periodical Tasks
4.6.1 Periodical Tasks for SAP NetWeaver 7.01
For more information on standard background jobs and periodical tasks for SAP NetWeaver
components, see the SAP NetWeaver 7.01 Technical Operations Manual at http://help.sap.com
SAP NetWeaver SAP NetWeaver 7.0 Including Enhancement Package 1 System Administration Technical
Operations Manual .
11/21/2008 PUBLIC 41/66

4.6 Scheduled and Manual Periodical Tasks
4.6.2 Periodical Tasks for SAP SRM 7.0
Standard Background Jobs

Program Name / Task Required or Recommended Detailed Description
Optional Frequency
CLEAN_REQREQ_UP Required 5 to 10 minutes For more information, see the Solution
(and START_CLEANER) Manager content on each SAP SRM
scenario you have implemented.
BBP_GET_STATUS_2 Required*
RSPPFPROCESS Optional
BBPERS Optional
BBP_DELETE_LO- Optional
CAL_ACCOUNT
BBP_SC_TRANS- Optional
FER_GROUPED
SRM_CALL_HAN- Required**
DLER_REPORT
* The configuration of this job depends on the number of shopping cart items created per week (it is
recommended to run the job twice a day to collect shopping cart items created during the past seven
days, and to run it in its entirety during the weekend). The job should be monitored regularly to
avoid system resources being utilized completely.
** Only if Records Management is used.
4.6.3 Periodical Tasks for SAP SRM-MDM Catalog 3.0
Standard Background Jobs

Program Name / Task Required or Recommended Detailed Description
Optional Frequency
SRM- Optional Daily This report is only required if contracts are
MDM_CTR_TRANSFER not distributed automatically. It initiates
the transfer of all contracts that are flagged
for distribution.
For more information, see the MDM 5.5 Solution Operation Guide on SAP Service Marketplace
Installation, Configuration, Upgrade Installation & Implementation Documentation Center Operations SAP
NetWeaver MDM SAP NetWeaver MDM Documentation .
42/66 PUBLIC 11/21/2008

4.7 Log on and Load Balancing
4.6.4 Manual Periodical Tasks for SAP SRM 7.0
For more information on the required manual periodical tasks for the SRM Server, see the section
Reports on http://help.sap.com SAP Business Suite SAP Supplier Relationship Mgmt. SAP SRM
7.0 (under Overview).
Note
There are no periodical tasks for the Live Auction Cockpit.
4.7 Log on and Load Balancing

As a web-based application, the basis for logon and load balancing in SAP SRM is a high availability
landscape setup together with a load balanced network setup.
n For more information on network load balancing, see the Technical Infrastructure Guide at
http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 Including Enhancement Package 1
Installation, Configuration, Upgrade Installation & Implementation Documentation Center Installation .
n For information on load balancing between many Java instances and on the SAP Web Dispatcher,
see the SAP NetWeaver 7.01 Technical Operations Manual at http://help.sap.com SAP
NetWeaver SAP NetWeaver 7.0 Including Enhancement Package 1 System Administration Technical
Operations Manual .
A load-balanced network using SAP Web Dispatcher together with Logon Groups in the SAP SRM
Server can be used to redirect certain users to specific application servers.
4.8 User Management

All scenarios and components in SAP SRM use the user management functions provided by SAP
NetWeaver 7.01.
For more information about user administration and authentication, see the SAP SRM Security
Guide at http://service.sap.com/instguides Installation & Upgrade Guides SAP Business Suite
Because of special requirements of the SAP SRM Server, the following SAP SRM-specific user
management tools are also available:
User Management Tools (SAP SRM Server)
11/21/2008 PUBLIC 43/66

4.8 User Management
Tool Detailed Description Comments

Self Registration ‒ SRM Server http://help.sap.com SAP See the section in the
Business Suite SAP Supplier documentation on User
Relationship Management SAP SRM Self-Registration (under
7.0 Overview Getting Started ).
Manage User Data http://help.sap.com See the section in the
(BBPUSERMAINT) ‒ SRM SAP Business Suite SAP Supplier documentation on User and
Server Relationship Management SAP SRM Employee Date (under Master Data).
7.0
User management for supplier http://help.sap.com See the section in the
self-services - SRM Server (SUS) SAP Business Suite SAP Supplier documentation on External
Relationship Management SAP SRM Business Partners (under Functions
7.0 Global Functions ).
External suppliers can also act as bidders in SAP SRM Server SUS scenarios. The users of these
suppliers need to be created in SAP SRM Server with the same user ID (this can be done via replication
from SUS).
For more information, see the SAP SRM 7.0 Solution Manager Content under SAP Solution Manager
under <project name> Configuration SAP SRM <release> Basic Settings for Service Procurement Classic .
4.8.1 Portal User Management

For user management of SAP Enterprise Portal, see the Portal Security Guide at
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guides
for Usage Types EPC and EP .
4.8.1.1 Activating the TPD for User Integration Between SAP

SRM Server (SUS) and SAP Enterprise Portal
You must configure SAP User Management Engine (UME) to activate the Trading Partner Directory
(TPD) of the SAP Enterprise Portal (EP).
Prerequisites
You are logged on to the Administrator of the J2EE Engine in the Visual Administrator console of SAP J2EE Engine.
You have deployed the TPD Software Deployment Archive (SDA) and the Business Package for
Supplier Collaboration 4.0 using the Software Deployment Manager (SDM) at the same time.
44/66 PUBLIC 11/21/2008

4.8 User Management
Procedure
1. Check that TPD SDA has been deployed by performing the following steps:
a) Start SDM by running <portal installation directory>:\usr\sap\<db
instance>\JC00\SDM\program\Remotegui.bat.
b) Log on by choosing the icon with the quick info text Connect.
c) Choose SAPJ2EEEngine SUP-PORTAL .
d) Check that the list includes the srm/suptpdimpl SDA.
e) If you cannot find TPD SDA, you must deploy it manually.
2. On the Visual Administrator screen, in the left screen area, choose Server 0 xxxxx Services
Configuration Adapter .
3. In the right screen area, choose cluster_data server cfg services .
4. Switch to edit mode by choosing the icon with the quick info text Switch between view and edit mode.
5. Open Propertysheet.com.sap.security.core.ume.service.
6. Select the properties shown in the following table and enter the corresponding values in the
Custom field:
Property Value
ume.tpd.classloader library:srm~suptpdimpl
ume.tpd.imp.class com.sap.cc.sup.common.tpd.SPPartnerDirectoryImpl
7. Each time you add a value, choose Apply Custom.

8. Restart SAP J2EE Engine to activate the TPD.
If SAP J2EE Engine does not restart, there may be a typing error in one of the properties you edited.
Check the properties and make any necessary corrections, then restart SAP J2EE Engine again.
For more information about the SAP User Management Engine, see the Portal Security Guide
at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 Including Enhancement Package 1 System
Administration Security Guide Security Guides for SAP NetWeaver According to Usage Types Security Guides
for Usage Types EPC and EP .
4.8.1.2 SRM Server (SUS) and Portal User Integration
In those cases when user data is read directly from an SAP Supplier Self-Service (SUS) persistence store
and they have not been created in SAP Enterprise Portal, you must assign business partners to the
users. Users must have a business partner relationship that is reflected in SAP Enterprise Portal.
11/21/2008 PUBLIC 45/66

4.8 User Management
Prerequisites
You are logged on to SAP Enterprise Portal as a portal administrator and you have activated the
Trading Partner Directory (TPD) for SAP Enterprise Portal, see section 4.8.1.1Activating the TPD for User
Integration Between SAP SRM Server (SUS) and SAP Enterprise Portal [page 44].
Procedure
1. In the User Administration workset, choose User Administration Users Search .
2. In the Search field, enter the name of a user or enter * to search for all users, and then choose Enter.
3. Choose Modify next to the user that you want to modify.
4. Select a company for the user.
5. Save your changes.
Note
We recommend that you assign a business partner to a user immediately after you create the user.
46/66 PUBLIC 11/21/2008

5 High Availability
5 High Availability
The following table describes the business impact for each component of SAP SRM, if that component
should become unavailable.
Component Business Impact if Unavailable
SAP SRM 7.0 Business critical: single point of failure for all
scenarios.
SAP LACWPS 7.0 Live auctions will not be available in the Strategic
Sourcing scenario.
Business critical impact if the component becomes
unavailable while one or more live auctions are active.
The auction outcome may differ significantly from
what it would have been if the component had not
become unavailable.
Live auctions do not need to be available 24 x 7.
SAP NetWeaver Process Integration All scenarios utilizing SAP NW PI will only have
asynchronous messaging available.
Document delivery is delayed but not cancelled.
SAP NetWeaver Enterprise Portal 7.0 As all scenarios are only available via the Portal, a
failure would be critical.
For more information about high availability and switchover, see the SAP NetWeaver 7.01 Technical
Operations Manual at http://help.sap.com SAP NetWeaver SAP NetWeaver Including Enhancement
Package 1 System Administration Technical Operations Manual . See the section on high availability in the
Manual under General Administration Tasks.
11/21/2008 PUBLIC 47/66

6 Software Change Management
Software Change Management standardizes and automates software distribution, maintenance, and
testing procedures for complex software landscapes and multiple software development platforms.
The goal of Software Change Management is to establish consistent, solution-wide change
management that allows for specific maintenance procedures, global rollouts, including localizations,
and open integration with third-party products.
This section provides additional information about the most important software components.
The following topics are covered:
n Transport and Change Management
Enables and secures the distribution of software changes from the development environment to
the quality assurance and productive environment.
n Development Request and Development Release Management
n Template Management
Enables and secures the rollout of global templates, including localizations
n Quality and Test Management
Reduces the time, costs, and risks associated with software changes.
n Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance procedures.
n Release and Upgrade Management
Reduces the time, costs, and risks associated with upgrades.
6.1 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS), which is a tool that helps you to
organize development projects in the ABAP Workbench and in Customizing, and then transport the
changes between the SAP Systems in your system landscape.
SAP SRM 7.0 can be used with more than one portal tenant, and in several different ways.
n One option is for one portal tenant to be used for SAP SRM Server, another one for SAP SRM
Server (SUS), and a third one for SAP NetWeaver BI.
11/21/2008 PUBLIC 49/66

6.2 Development Requests and Development Release Management
n Another option of utilizing more than one portal tenant within the SRM Server is to assign
different purchasing organizations to different portal tenants ‒ each purchasing organization has
a separate portal tenant. This is useful for example, if the SRM Server is provided to different
companies by an application service provider.
n Other SAP SRM components could be shared with other SAP or non-SRM applications like SAP
NetWeaver Process Integration and SAP NetWeaver Enterprise Portal.
6.2 Development Requests and Development Release

Management
The transport workflow provides a framework for transporting enhancements or new developments
of existing business functions in a system landscape.
It is an efficient method of transporting a selected number of requests into a group of transport
targets, and uses clearly defined approval steps to ensure the quality of your target systems.
6.3 Support Packages and SAP Notes Implementation
Information on the support packages (SPs) available for SAP SRM 7.0 can be found in the Release
Information Notes (RIN) for each SP
Support packages for components based on the SAP NetWeaver Application Server (ABAP) (such as
SAP SRM Server) are applied using the Support Package Manager.
Support packages and patches for components based on the SAP NetWeaver Application Server (Java),
for example SAP LACWPS, are deployed using the Software Deployment Manager.
Detailed instructions on applying a support package stack to SAP NetWeaver are given in the SAP
NetWeaver Support Package Stack guides at http://help.sap.com SAP NetWeaver SAP
NetWeaver Including Enhancement Package 1 Installation, Configuration, Upgrade Installation & Implementation
Documentation Center Maintenance .
SAP Notes that require code changes for components based on the SAP NetWeaver Application
Server (ABAP) can be applied using the SAP Note Assistant. For more information, see
http://service.sap.com/note-assistant.
50/66 PUBLIC 11/21/2008

6.4 Release and Upgrade Management
6.4 Release and Upgrade Management
Component Release
Software Component Release Tool
SAP SRM 7.0 System Status
LAC WPS 7.0 System Info
http://<server>:<port>/sap/monitoring/ComponentInfo
n The versions of all components can be displayed centrally in the Solution Manager.
For more information, see the information available on SAP Service Marketplace at
http://service.sap.com/solutionmanager.
n For SAP SRM release and upgrade plans, see the information available on SAP Service Marketplace
at http://service.sap.com/srm.
6.5 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets).
For more information, see http://help.sap.com SAP NetWeaver SAP NetWeaver Including
Enhancement Package 1 Functional View SAP NetWeaver by Key Capability Customizing Business
Configuration Sets .
6.6 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP).
For more information, see http://help.sap.com SAP NetWeaver SAP NetWeaver Including
Enhancement Package 1 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Management
by Key Capability Testing .
For more information on testing software changes based on SAP NetWeaver Appication Server (Java),
see http://help.sap.com SAP NetWeaver SAP NetWeaver Including Enhancement Package 1 Functional
View SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Java
Development Manual .
11/21/2008 PUBLIC 51/66

7 Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP SRM 7.0.
For more information about these services, see SAP Safeguarding on SAP Service Marketplace at
http://service.sap.com/safeguarding .
Note
Information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types is
available in the SAP NetWeaver Problem Analysis Guide (PAG) at http://help.sap.com SAP
NetWeaver SAP NetWeaver Including Enhancement Package 1 Functional View SAP NetWeaver by Key
Capability Solution Life Cycle Management by Key Capability .
Possible problem situations using SAP SRM 7.0

Problem Application components Information
No monitoring information is All SAP SRM application See the CCMS Monitoring
displayed in the CCMS Alert components Infrastructure Problem
Monitor (transaction RZ20) of Analysis Guide in the PAG at
the central monitoring SAP Web http://help.sap.com SAP
AS ABAP system. However, NetWeaver SAP NetWeaver Including
monitoring information is available Enhancement Package 1 Functional View
in the Visual Administrator of the SAP NetWeaver by Key Capability
J2EE server, for example status Solution Life Cycle Management by Key
information in the J2EE status Capability SAP NetWeaver PAG
monitors Usage Type Application Server ABAP
Portal restriction for SAP SAP SRM-MDM Catalog 2.0 Refer SAP Note 1147103
SRM-MDM Catalog
Error “Page not found or not Business Packages for SAP SRM Refer SAP Note 1260119
available” while accessing a catalog
configured in the SRM Server
For troubleshooting SAP NetWeaver MDM, see http://service.sap.com/installMDM

Operations MDM 5.5 SP06 - Solution Operation Guide .
11/21/2008 PUBLIC 53/66

8 Appendix
8 Appendix
8.1 Categories of System Components for Backup and

Restore
Categories of System Suggested Backup and

Components Category Properties Recovery Methods Example
I Only software, no n No backup, new BDOC-modeler
configuration or installation in case
application data of a restore or
n Initial software backup
after installation and
upgrade
n Backup of log files
II Only software n Backup after changes SAP Gateway Comm.
and configuration have been applied or Station
information, no n No backup, new SAP Business Connector
application data installation and
configuration in case
of a restore
n Backup of log files
III Only replicated Data: SAP IMS / Search engine
application data, n No data backup Webserver
replication time is needed
sufficiently small for a Backup of software,
restore configuration, log files
IV Only replicated Data: SAP IMS / Search engine
application data, backup n Application-specific Webserver
recommended because file system backup or
replication time is too n Multiple instances
long, data managed by a Backup of software,
DBMS configuration, log files
V Only replicated Data: Catalog Server
application data, backup n Database and log
recommended because backup or
replication time is too n Multiple instances
long, data managed by a Backup of software,
DBMS configuration, log files
11/21/2008 PUBLIC 55/66

8 Appendix
8.1 Categories of System Components for Backup and Restore
Categories of System Suggested Backup and

Components Category Properties Recovery Methods Example
VI Original application data, Data: Webserver
standalone system, data n Application-specific
not managed by a DBMS file system backup
Backup of software,
configuration, log files
VII Original application data, Data:
standalone system, data n Database and log
managed by a DBMS, not backup
based on SAP NW AS Backup of software,
VIII Original application data, Data: Standalone SAP system
standalone system, based n Database and log
on SAP NW AS backup, application
log backup
Backup of software,
IX Original application Data:
data, data exchange with n Application-specific
other systems, data not file system backup,
managed by a DBMS data consistency with
other systems must be
regarded
Backup of software,
X Original application data, Data: SAP liveCache
data exchange with other n Database and SAP Mobile
systems, data managed log backup, data Workbench
by a DBMS, not based on consistency with
SAP NW AS other systems must be
regarded.
Backup of software,
XI Original application data, Data: SAP system
data exchange with other n Database and log SAP CRM
systems, based on SAP backup, application SAP NW BI
NW AS log backup, data
consistency with
other systems must be
regarded
Backup of software,
56/66 PUBLIC 11/21/2008

8 Appendix
8.2 Related Information
8.2 Related Information
The following table contains links to information relating to the Application Operations Guide.
Content SAP Service Marketplace:
SAP SRM Master Guide, Installation and Upgrade http://service.sap.com/instguides Installation
Guides and Upgrade Guides SAP Business Suite Applications SAP
SRM SAP SRM Server 7.0
SAP Notes http://service.sap.com/notes
Released Platforms http://service.sap.com/platforms
Network Security http://service.sap.com/securityguide
SAP NetWeaver Technical Operations Manual http://help.sap.com SAP NetWeaver SAP

Administration Technical Operations Manual
SAP Solution Manager http://service.sap.com/solutionmanager
11/21/2008 PUBLIC 57/66

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

The following is an overview of the most important documentation types that you need in the
various phases in the life cycle of SAP software.
Figure 6: Documentation Types in the Software Life Cycle
Cross-Phase Documentation
SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages, as
well as many glossary entries in English and German.
n Target group:
l Relevant for all target groups
n Current version:
l On SAP Help Portal at http://help.sap.com Additional Information Glossary (direct
access) or Terminology (as terminology CD)
l In the SAP system in transaction STERM
11/21/2008 PUBLIC 59/66

A Reference
SAP Library is a collection of documentation for SAP software covering functions and processes.
n Target group:
l Consultants
l System administrators
l Project teams for implementations or upgrades
n Current version:
l On SAP Help Portal at http://help.sap.com (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for
raising security levels. A collective security guide is available for SAP NetWeaver. This document
contains general guidelines and suggestions. SAP applications have a security guide of their own.
n Target group:
l Technology consultants
l Solution consultants
n Current version:
l On SAP Service Marketplace at http://service.sap.com/securityguide
Implementation
The master guide is the starting point for implementing an SAP solution. It lists the required
installable units for each business or IT scenario. It provides scenario-specific descriptions of
preparation, execution, and follow-up of an implementation. It also provides references to other
documents, such as installation guides, the technical infrastructure guide and SAP Notes.
n Target group:
l Project teams for implementations
n Current version:
l On SAP Service Marketplace at http://service.sap.com/instguides
The installation guide describes the technical implementation of an installable unit, taking
into account the combinations of operating systems and databases. It does not describe any
business-related configuration.
n Target group:
n Current version:
Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycle
platform. One of its main functions is the configuration of business and IT scenarios. It contains
Customizing activities, transactions, and so on, as well as documentation.
60/66 PUBLIC 11/21/2008

A Reference
n Target group:
n Current version:
l In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system.
The Customizing activities and their documentation are structured from a functional perspective.
(In order to configure a whole system landscape from a process-oriented perspective, SAP Solution
Manager, which refers to the relevant Customizing activities in the individual SAP systems, is used.)
n Target group:
l Project teams for implementations or upgrades
n Current version:
l In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver, and precedes the solution operations guide. The manual 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.
n Target group:
n Current version:
The solution operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed. It refers users to the tools and documentation
that are needed to carry out the various operations-related tasks.
n Target group:
n Current version:
Upgrade
The upgrade master guide is the starting point for upgrading the business and IT scenarios of an
SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an
upgrade. It also refers to other documents, such as the upgrade guides and SAP Notes.
11/21/2008 PUBLIC 61/66

A Reference
n Target group:
l Project teams for upgrades
n Current version:
The upgrade guide describes the technical upgrade of an installable unit, taking into account
the combinations of operating systems and databases. It does not describe any business-related
configuration.
n Target group:
n Current version:
Release notes are documents that contain short descriptions of new features in a particular release
or changes to existing features since the previous release. Release notes about ABAP developments
are the technical prerequisite for generating delta and upgrade Customizing in the Implementation
Guide (IMG).
n Target group:
l Consultants
n Current version:
l On SAP Service Marketplace at http://service.sap.com/releasenotes
l In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
62/66 PUBLIC 11/21/2008

Typographic Conventions
Example Description
<Example> Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, “Enter your <User Name>”.
Example Arrows separating the parts of a navigation path, for example, menu options
Example
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the
documentation
http://www.sap.com Textual cross-references to an internet address
/example Quicklinks added to the internet address of a homepage to enable quick access to
specific content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example n Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
n Cross-references to other documentation or published works
Example n Output on the screen following a user action, for example, messages
n Source code or syntax quoted directly from a program
n File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE Keys on the keyboard
11/21/2008 PUBLIC 63/66

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
© Copyright 2009 SAP AG. All rights reserved.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,
z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented
by Netscape.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products
and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in
Germany and in several other countries all over the world. All other product and service names mentioned are the
trademarks of their respective companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies
(“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not
be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are
those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2
from Michael Kay (http://saxon.sf.net/), XSLT version 1.
64/66 PUBLIC 11/21/2008

Disclaimer
Some components of this product are based on Java™. Any code change in these components may cause unpredictable and
severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.
Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or
altered in any way.
Documentation in the SAP Service Marketplace

You can find this document at the following address: https://service.sap.com/instguides
11/21/2008 PUBLIC 65/66

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be
changed without prior notice.

Application Operations Guide Sap Supplier Relationship Management Powered by Sap Netweaver®

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Application Operations Guide Sap Supplier Relationship Management Powered by Sap Netweaver®

Uploaded by

Copyright:

Available Formats

Application Operations Guide

SAP Supplier Relationship Management powered by SAP

1.0 11/21/2008 Final Version

2/66 PUBLIC 11/21/2008

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 Overview of SAP Supplier Relationship Management 7.0 . . . . . . 9

Chapter 3 Monitoring of SAP SRM . . . . . . . . . . . . . . . . . . . 15

11/21/2008 PUBLIC 3/66

Chapter 4 Management of SAP SRM . . . . . . . . . . . . . . . . . . 33

Chapter 5 High Availability . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 6 Software Change Management . . . . . . . . . . . . . . . . 49

4/66 PUBLIC 11/21/2008

11/21/2008 PUBLIC 5/66

1.1 About this Guide

11/21/2008 PUBLIC 7/66

1.2 Important SAP Notes

SAP Note Number Title

8/66 PUBLIC 11/21/2008

2 Overview of SAP Supplier Relationship

2.1 Technical System Landscape

2.1.1 ABAP Components

11/21/2008 PUBLIC 9/66

l SRM Extension Plus 7.0

2.1.2 Java Components

10/66 PUBLIC 11/21/2008

2.1.3 Additional Components

11/21/2008 PUBLIC 11/66

2.2 Software Component Matrix

You require SAP NetWeaver 7.0® TREX in the following cases:

2.3 Related Documentation

12/66 PUBLIC 11/21/2008

Topic Guide/Tool Location on SAP Service Marketplace/SAP Help Portal

11/21/2008 PUBLIC 13/66

3 Monitoring of SAP SRM

3.1 Alert Monitoring with CCMS

11/21/2008 PUBLIC 15/66

3.1.1 CCMS Monitoring Installation and Setup

3.1.2 Alert Monitoring of Components

3.1.2.1 SAP NetWeaver 7.01 Monitoring

16/66 PUBLIC 11/21/2008

3.1.2.2 Monitoring SAP SRM Server 7.0

11/21/2008 PUBLIC 17/66

Node Type Parameter Value

3.1.2.3 Monitoring of SAP LACWPS 7.0

3.1.2.3.1 GRMG Availability Monitoring for SAP LACWPS 7.0

18/66 PUBLIC 11/21/2008

3.1.2.3.2 Activating GRMG Monitoring

3. Upload the customizing file into the central monitoring system.

11/21/2008 PUBLIC 19/66

a) Log on to the monitoring system as a user with administrator rights.

Adding Scenarios to the XML Customizing File

20/66 PUBLIC 11/21/2008

3.1.2.3.3 Verifying the GRMG Availability Monitoring

Displaying Scenario Execution Status

11/21/2008 PUBLIC 21/66

3.1.2.3.4 Troubleshooting GRMG Availability Monitoring

No GRMG_SelfMonitoring Subtree Found

22/66 PUBLIC 11/21/2008

GRMG_SelfMonitoring Subtree Found with Errors

11/21/2008 PUBLIC 23/66

GRMG Scenario Error Message Cause

24/66 PUBLIC 11/21/2008

GRMG Scenario Error Message Cause