Operations

Application Operations Guide
SAP Supplier Relationship Management Powered by SAP

NetWeaver
Using SAP SRM Server 7.13
Target Audience
w> System Administrators
w> Technology Consultants
PUBLIC
wv@jht'v[OkkP$|'\S4uh(Mp7syN64u2_$0 7
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.03 .
The following table provides an overview of the most important document changes.
Version
Date
Description
1.0
2013-08-13
Final Version
[Description]
2/68
PUBLIC
2013-08-13
Table of Contents
Chapter 1
1.1
1.2
1.3
1.4
1.5
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
SAP Service Marketplace Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
SAP Developer Network Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
SAP Help Portal Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 2
2.1
2.2
2.3
Overview of SAP Enhancement Package 3 for SAP SRM 7.0 . . . . . . . . . . .

Technical System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Component Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 3
Monitoring of SAP Supplier Relationship Management (SAP

SRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alert Monitoring with CCMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CCMS Monitoring Installation and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alert Monitoring of Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAP NetWeaver 7.4 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAP SRM Server 7.13 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Monitoring of SAP Live Auction Cockpit Web Presentation Server based on
Java Server 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GRMG Availability Monitoring for SAP Live Auction Cockpit Web
Presentation Server based on Java Server 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activating GRMG Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying GRMG Availability Monitoring for Live Auction based on Java
Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting GRMG Availability Monitoring . . . . . . . . . . . . . . . . . . . . . .
SAP SRM Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Monitoring SRM-MDM Catalog 7.02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SRM-MDM Catalog 7.02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GRMG Availability Monitoring for SRM-MDM Catalog 7.02 . . . . . . . . . . . . . .
3.1
3.1.1
3.1.2
3.1.2.1
3.1.2.2
3.1.2.3
3.1.2.3.1
3.1.2.3.2
3.1.2.3.3
3.1.2.3.4
3.1.2.4
3.1.2.5
3.1.2.5.1
3.1.2.5.2
2013-08-13
PUBLIC
13
13
13
14
15
15
16
16
16
17
18
18
19
21
21
24
26
26
27
3/68
3.2
3.2.1
3.2.1.1
3.2.1.2
3.2.1.3
3.2.2
3.2.2.1
3.2.2.2
3.2.2.3
3.2.2.4
3.2.3
3.2.4
Chapter 4
4.1
4.2
4.3
4.4
4.4.1
4.4.2
4.4.2.1
4.4.2.2
4.4.2.3
4.4.3
4.4.3.1
4.4.3.2
4.4.4
4.4.4.1
4.4.4.2
4.4.4.3
4.4.5
4/68
Detailed Monitoring and Tools for Problem and Performance

Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Component-Specific Analysis Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAP Enhancement Package 3 for SAP Supplier Relationship Management
(SAP SRM) 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAP Live Auction Cockpit Web Presentation Server based on Java (LACWPS)
6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SRM-MDM Catalog 7.02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scenario Problem Analysis Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Archiving Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distributed Statistical Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Business Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logs and Trace (ComponentSpecific or Scenario-Specific) . . . . . . . . . . . . . . .
Data Growth and Data Archiving Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . .
Management of SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administration Tools of Software Components . . . . . . . . . . . . . . . . . . . . . . . .
Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backup of Individual Components in an SAP Supplier Relationship
Management (SAP SRM) Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backup and Restore for Operating System, Software, and Configuration
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backup and Restore for SAP NetWeaver Application Server (SAP NetWeaver
AS) 7.40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backup and Restore for Individual System Components . . . . . . . . . . . . . . . . .
SAP Live Auction Cockpit Web Presentation Server based on Java (LACWPS)
6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhancement Package 2 for SRM-MDM Catalog 7.0 . . . . . . . . . . . . . . . . . . . .
Backup and Restore for a Complete SAP SRM Landscape . . . . . . . . . . . . . . . .
Landscape Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Offline Backup of the SAP SRM Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Landscape Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backup and Restore for an SAP SRM Business Scenario . . . . . . . . . . . . . . . . . .
PUBLIC
28
28
28
28
28
29
29
29
29
29
30
30
31
31
31
31
33
34
35
36
36
37
37
28
38
38
38
38
39
39
2013-08-13
4.5
4.5.1
4.5.2
4.6
4.6.1
4.6.2
4.6.3
4.7
4.8
4.9
Application Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Homogeneous System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Heterogeneous System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduled and Manual Periodical Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Periodical Tasks for SAP NetWeaver 7.40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Periodical Tasks for SAP Enhancement Package 2 for SAP SRM 7.0 . . . . . . . . .
Periodical Tasks for SAP Enhancement Package 3 for SRM-MDM Catalog
7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual Periodical Tasks for Enhancement Package 3 for SAP Supplier
Relationship Management (SAP SRM) 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual Periodical Tasks for Live Auction Cockpit based on Java Server
(LACWPS 6.0) and Live Auction Cockpit based on ABAP Server . . . . . . . . . . .
Logon and Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5
High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Chapter 6
6.1
6.2
6.3
6.4
6.5
6.6
Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transport and Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Development Requests and Development Release Management . . . . . . . . . . .
Support Packages and SAP Notes Implementation . . . . . . . . . . . . . . . . . . . . . .
Release and Upgrade Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Template Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quality Management and Test Management . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Chapter 8
8.1
8.2
8.3
Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Remote Support Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problem Message Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CA Wily Introscope Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 9
9.1
9.2
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Categories of System Components for Backup and Restore . . . . . . . . . . . . . . . 57
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.6.4
4.6.5
2013-08-13
PUBLIC
39
39
39
40
40
40
41
41
41
42
42
43
47
47
48
48
49
49
49
53
53
53
54
5/68
Chapter A
A.1
6/68
Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
PUBLIC
2013-08-13
Getting Started
1.1
About this Guide
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 SAP NetWeaver documentation is especially important and must be used in conjunction
with this SAP SRM Application Operations Guide as the SAP Supplier Relationship Management (SAP SRM)
guide covers only SAP SRM-specific topics, not general SAP NetWeaver topics:
Document
Technical Operations
Manual for SAP
NetWeaver
Operations Guide for
SAP NetWeaver
SAP NetWeaver
Security Guide
Solution Life Cycle
Management
Found At:
Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP Help Portal at
http://help.sap.com/netweaver
Operations Information under System Administration and Maintenance Information on SAP Help Portal at
http://help.sap.com/netweaver
SAP NetWeaver Security Guide under Security Information on SAP Help Portal at http://
help.sap.com/netweaver
Solution Life Cycle Management for SAP NetWeaver at Solution Oriented View for SAP NetWeaver on SAP
Help Portal at http://help.sap.com/netweaver
1.2 Important SAP Notes

CAUTION
Check regularly to see which SAP Notes are available for the Application Operations Guide.
SAP Note Number
19227
209834
2013-08-13
Title
Open newest SAPOSCOL
CCMS agent technology
PUBLIC
7/68
Getting Started
1.3
SAP Service Marketplace Links
797147
1126859
1515223
Wily Introscope Installation for SAP Customers

End-to-End Diagnostics SP15 SP17
SAP NetWeaver Process Integration: Release Recommendation
1.3 SAP Service Marketplace Links

The following documentation is published on SAP Service Marketplace at service.sap.com.
Type of Information
SAP Supplier
Relationship
Management (SAP SRM)
in Detail
Description
Location
Information about business http://service.sap.com/srm
and technical aspects of SAP
Supplier Relationship
Management (SAP SRM)
including news, services,
events, demos, education,
and workshops
SAP SRM - Installation Comprehensive
http://service.sap.com/srm-inst
And Upgrade
information about the
Information
installation and upgrade of
SAP SRM
Master Guide SAP SRM Detailed information about http://service.sap.com/instguides SAP Business
7.03
the technical system
Suite Applications SAP SRM SAP SRM Server 7.13
landscape of SAP SRM 7.03
Solution Operation
Detailed information about http://service.sap.com/instguides SAP Business
Guide SAP SRM 7.03
how to operate your SAP
Suite Applications SAP SRM SAP SRM Server 7.13
SRM 7.03 system landscape
SAP NetWeaver
Information about the
http://service.sap.com/netweaver
application and integration
platform SAP NetWeaver
SAP NetWeaver 7.40
Details on SAP NetWeaver service.sap.com/instguidesNW74
Release 7.40
SAP NetWeaver 7.40
Installation information
service.sap.com/installNW74
Installation Information including the Master Guide,
Technical Infrastructure
Guide, and Installation
Guide
SAP NetWeaver 7.40
Upgrade information,
http://service.sap.com/upgradeNW74
Upgrade Information
including the Upgrade
Master Guide and Upgrade
Guide
SAP NetWeaver 7.40
Maintenance information, http://service.sap.com/maintenanceNW74
Maintenance
including the Support
Information
Package Guides
SAP NetWeaver 7.4
SAP Notes, including SAP http://service.sap.com/SAPNotesNW70
0Central SAP Notes
Notes specific to SAP
NetWeaver 7.40 installation,
8/68
PUBLIC
2013-08-13
Getting Started
1.3
SAP Service Marketplace Links
upgrade, and
implementation
SAPs Release Strategy
Release and maintenance
strategy of SAP
SAP Best Practices
Comprehensive
information about SAP
Business Suite solutions that
are affordable, simple to
understand, and quick to
implement
Product Availability
Quick reference to technical
Matrix (PAM)
and release planning
information about SAP
components, featuring SAP
component releases and
maintenance end dates, plus
release information based
on languages, country
versions, DB platforms, JSE
platforms, and so on
Hardware Sizing
Detailed information about
the calculation of hardware,
including access to the SAP
Quick Sizer
Security
Information about the
security infrastructure of
SAP NetWeaver SAP delivers
comprehensive security
technologies to protect the
heterogeneous
environments of the SAP
Business Suite. Combined
with specialized partner
solutions, it makes the SAP
Business Suite a secure place
to do business.
Documentation, guides,
best practices, and tools for
SAP NetWeaver Security is
provided here.
SAP Security Guides
Guidelines and
recommendations relating
to system and network
security
Platform and
Overview of platform and
Technology Information technology-related topics
Center
2013-08-13
http://service.sap.com/releasestrategy
http://service.sap.com/bestpractices
http://service.sap.com/pam
http://service.sap.com/sizing
http://service.sap.com/security
http://service.sap.com/securityguide
http://service.sap.com/platforms
PUBLIC
9/68
Getting Started
1.4
SAP Developer Network Links
Unicode at SAP
SAP Solution Manager

SAP System
Administration
SAP Support Package

Stacks
SAP Software
Distribution Center
Information about support

for multiple local-language
characters
Information about SAP
Solution Manager
Comprehensive
information about technical
infrastructure issues and
network integration
Information about SP stacks,
that is, sets of support
packages and patches for the
product version in question,
which must be used in the
given combination
A software center that
allows you to obtain SAP
software electronically by
downloading packages, or
by ordering CDs and DVDs,
with access, based on your
licenses, to the entire SAP
software portfolio
http://service.sap.com/unicode
http://service.sap.com/solutionmanager
http://service.sap.com/system-data
http://service.sap.com/sp-stacks
http://service.sap.com/swdc
1.4 SAP Developer Network Links

The following documentation is published on SAP Developer Network (SDN) at http://
www.sdn.sap.com/irj/sdn.
Type of Information
Description
Location
Enterprise Data Warehousing - with Information about Business

the SAP NetWeaver Business
Intelligence
Warehouse (BW)
SAP GUI Family
Information about the various
members of the SAP GUI family
SAP NetWeaver Portal
Information about SAP NetWeaver
Portal
SAP Installation
Installation and upgrade
information
High Availability
Overview of high-availability aspects
for SAP solutions
http://www.sdn.sap.com/irj/sdn/
edw
sap-gui
nw-products
nw-products
ha
1.5 SAP Help Portal Links

The following documentation is published on SAP Help Portal at help.sap.com.
10/68
PUBLIC
2013-08-13
Getting Started
1.5
SAP Help Portal Links
Type of
Information
SAP NetWeaver
Library
Technical
Operations
Manual for SAP
NetWeaver
SAP Solution
Manager
SAP Library
Description
SAP NetWeaver
documentation
Instructions for
operating your SAP
NetWeaver or SAP
SRM system
Solution Manager
documentation
SAP SRM
documentation
SAP SRM Business Information about
Functions
Business Functions
in SAP SRM
SOA
SOA documentation
2013-08-13
Location
SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/netweaver
Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on
SAP Help Portal at http://help.sap.com/netweaver
SAP Library for Application Lifecycle Management under SAP Solution

Manager on SAP Help Portal at http://help.sap.com/alm
SAP Library for Supplier Relationship Management on SAP Help Portal at
http://help.sap.com/srm
SAP Library for Supplier Relationship Management onSAP Help Portal at

http://help.sap.com/srm
SOA content for SRM at SAP Library for Supplier Relationship Management on
SAP Help Portal at http://help.sap.com/srm
PUBLIC
11/68
This page is left blank for documents

that are printed on both sides.
Overview of SAP Enhancement Package 3 for SAP SRM 7.0
2.1
Technical System Landscape
2 Overview of SAP Enhancement

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

SAP enhancement package 3 for SAP Supplier Relationship Management (SAP SRM) 7.0 is based on
SAP NetWeaver 7.40 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, see the Master Guide at http://
service.sap.com/instguides Installation and Upgrade Guides SAP Business Suite Applications SAP SRM
SAP SRM Server 7.13 .
2.2 Software Component Matrix

For an overview of SAP Supplier Relationship Management (SAP SRM) business scenarios and their
associated software units, see the Software Component Matrix for SAP enhancement package 3 for SAP
Supplier Relationship Management 7.0 (SAP enhancement package 3 for SAP SRM 7.0) on SAP Service
Marketplace at http://service.sap.com/srm-inst SAP SRM SAP SRM Server 7.13 .
NOTE
The Scenario and Process Component List (SCL) is a tool that allows you to find implementation
alternatives for SAP solutions, business scenarios, and processes for your SAP enhancement
package installation. It shows you which application components are needed to implement a
business scenario or process. For more information, see the Appendix [external document] in this
master guide. You can find the SCL on SAP Service Marketplace at http://service.sap.com/
scl .
For the latest component version and patch level requirements, as well as the Release Information
Note (RIN) available for each support package stack, see SAP Service Marketplace at http://
service.sap.com/sp-stacks
SAP enhancement package 3 for SAP SRM 7.0 . On the following screen,
select a support package and choose Show Stack Information to view the corresponding SAP Note for that
support package. For SAP enhancement package 3 for SAP SRM 7.0 SP01, see SAP Note 1818517.
2013-08-13
PUBLIC
13/68
Overview of SAP Enhancement Package 3 for SAP SRM 7.0
2.3
Related Documentation
The exact locations of the required software components on the corresponding DVDs and CDs that
are shipped with the SAP enhancement package 3 for SAP Supplier Relationship Management (SAP
SRM) 7.0 package can be found at SAP Service Marketplace at http://service.sap.com/srm-inst
SAP Business Suite Applications SAP SRM SAP SRM Server 7.13 .
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 section 7, References.
You require Search and Classification 7.1 (TREX 7.1) in the following cases:
Dg52 When you use the contract management application to search for information such as supplier
texts, internal notes, and attachments.
Dg52 When you want to use the metadata search functionality or use SAP NetWeaver Business
Intelligence (SAP NetWeaver BI) Accelerator in Analytics.
2.3 Related Documentation

The following table lists where you can find more information about the technical system landscape.
Topic
Guide/Tool
Location on SAP Service Marketplace/SAP Help Portal
Enhancement package 3 for SAP

SRM 7.0
Master Guide
Sizing
Quick Sizer Tool
Technical Configuration
SAP NetWeaver
Library
SAP NetWeaver
Library
SAP NetWeaver
Library
SAP NetWeaver
Library
Installation
and Upgrade Guides SAP Business Suite Applications SAP
SRM SAP SRM Server 7.13
http://service.sap.com/sizing SAP NetWeaver
SAP NetWeaver in Detail Solution Life-Cycle Management
Hardware Sizing Quick Sizer Tool
SAP NetWeaver Library: Function Oriented View Solution
Lifecycle Management SAP NetWeaver Configuration
SAP NetWeaver Portal Managing the Portal
Scalability
High Availability
Security
14/68
http://service.sap.com/instguides
SAP NetWeaver Library: Function Oriented View Solution

Lifecycle Management High Availability
SAP NetWeaver Security Guide SAP NetWeaver Library:
Function Oriented View Security
PUBLIC
2013-08-13
Monitoring of SAP Supplier Relationship Management (SAP SRM)
3.1
Alert Monitoring with CCMS
3 Monitoring of SAP Supplier

Relationship Management (SAP SRM)
SAP NetWeaver monitoring is an essential task when you run 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
Supplier Relationship Management (SAP SRM) system landscape.
For more information about the underlying technology, see Technical Operations for SAP NetWeaver at SAP
Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver.
As SAP enhancement package 3 for SAP Supplier Relationship Management (SAP SRM) 7.0 is powered
by SAP NetWeaver 7.40, we recommend that you set up the monitoring infrastructure as described in
the Monitoring Setup Guide for SAP NetWeaver (MSG) under SAP NetWeaver 7.40 System Administration and
Maintenance Information Operations Information on SAP Help Portal at http://help.sap.com/netweaver.
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 enhancement
package 3 for SAP Supplier Relationship Management (SAP SRM) 7.0. Proficient knowledge of system
monitoring and basic knowledge of SAP NetWeaver is required to set up and manage the user-defined
SAP SRM monitors recommended in this guide.
3.1 Alert Monitoring with CCMS

Proactive, automatic monitoring is the basis for ensuring reliable operations for your SAP system
environment. SAP Supplier Relationship Management (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 Supplier Relationship Management (SAP SRM) as quickly as possible.
For more information, see the Monitoring Setup Guide for SAP NetWeaver (MSG) under SAP NetWeaver 7.0
System Administration and Maintenance Information Operations Information on SAP Help Portal at http://
help.sap.com/netweaver.
To configure alert monitoring with CCMS for SAP enhancement package 3 for SAP Supplier
Relationship Management (SAP SRM) 7.0, you must set up a Central Monitoring System (CEN) and
connect all SAP SRM 7.13 components to this CEN system. For a list of these components and the
business scenarios for which they are relevant, see Scenario/Component Matrix.
You can access the SRM Server Monitoring templates, called SAP (CEN) EnterpriseBuyer Monitors,
using transaction RZ20 (For more information, see SAP SRM Monitor.).
2013-08-13
PUBLIC
15/68
3.1
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 Applications
SAP SRM
SAP SRM Server 7.13 .
Since SAP enhancement package 3 for SAP Supplier Relationship Management (SAP SRM) 7.0 uses the
complete SAP NetWeaver 7.40 , 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 systems 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 use of SAP NetWeaver 7.40 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 Scenario/Component Matrix.
NOTE
This monitoring set for SAP enhancement package 3 for SAP Supplier Relationship Management
(SAP SRM) 7.0 includes component-related monitors such as for SAP enhancement package 3 for
SAP Supplier Relationship Management (SAP SRM) 7.0 and Live Auction Cockpit 6.0 based on
Java (LACWPS 6.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 about editing or creating monitors and monitor sets, see the Monitoring Setup Guide
for SAP NetWeaver (MSG) under SAP NetWeaver 7.0 System Administration and Maintenance Information
Operations Information on SAP Help Portal at http://help.sap.com/netweaver.
3.1.2.1 SAP NetWeaver 7.4 Monitoring

SAP NetWeaver 7.40 is the integration and application platform for SAP enhancement package 3 for
SAP Supplier Relationship Management (SAP SRM) 7.0.
The following SAP NetWeaver components must be integrated into the monitoring infrastructure:
16/68
PUBLIC
2013-08-13
3.1
2wV
2wV
2wV
2wV
2wV
2wV
2wV
SAP NetWeaver Application Server (ABAP) 7.40 (for SAP enhancement package 3 for SAP SRM 7.0)
SAP NetWeaver Application Server (Java) 7.40 (for SAP Live Auction Cockpit 6.0)
SAP NetWeaver Usage Type Process Integration (PI)
SAP NetWeaver Portal 7.40
SAP NetWeaver Master Data Management (for SRM-MDM Catalog 7.02)
SAP NetWeaver Business Intelligence 7.40 (SAP NetWeaver BI)
For more information and detailed procedures, see the Monitoring Setup Guide for SAP NetWeaver
(MSG) under SAP NetWeaver 7.40 System Administration and Maintenance Information Operations
Information on SAP Help Portal at http://help.sap.com/netweaver and Technical Operations for SAP
NetWeaver at SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver.
3.1.2.2 SAP SRM Server 7.13 Monitoring

The main component in your SAP Supplier Relationship Management (SAP SRM) solution is SAP SRM
Server 7.03. It is based on SAP NetWeaver Application Server (SAP NetWeaver AS) (ABAP) 7.40. For
more information, see the Monitoring Setup Guide for SAP NetWeaver (MSG) under SAP NetWeaver 7.40
help.sap.com/netweaver and Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on
SAP Help Portal at http://help.sap.com/netweaver.
Prerequisites
2wV Your SAP SRM Server 7.13 is connected to the CEN and registered as a remote system.
2wV The SAPCCM4X agent is registered and running for each SAP SRM Server 7.13 instance.
What to Monitor
Your SAP SRM Server 7.13 is running on SAP NetWeaver Application Server (ABAP) 7.40 which means
the primary points of failure are within the technical infrastructure.
Procedure
1.
2.
3.
Go to transaction RZ20 and create a new monitor: SRM Server 7.13 monitor.
On the top level, create a virtual node for following:
2wV Back-end monitoring
2wV Database
2wV Operating system
2wV System configuration
2wV Log file monitoring
On the second level, create rule-based monitors for each area as described in the following table:
Node
Type
Parameter
Value
Back-End Monitoring
CCMS_DEFINE_R3_SYSTEMS
Virtual
Rule
R3System
<SRMServer_Systems>
2013-08-13
PUBLIC
17/68
3.1
Node
Type
Dialogue Response Time
Virtual
Rule
Network Time
CCMS_GET_MTE_BY_CLASS
Virtual
Rule
Users Logged On
Virtual
Rule
Database
Virtual
Rule
Operating System
Virtual
Rule
System Configuration
Dialog Response Time
CCMS_GET_MONITORING_CONTE
XT_NAMES
Virtual
Rule
Virtual
Rule
Log File Monitoring

Virtual
Rule
Parameter
Value
R3System
MTEClass
<SRMServer_Systems>
R3DialogResponseTime
R3System
MTEClass
<SRMServer_Systems>
R3DialogFrontEndNetTime
R3System
MTEClass
<SRMServer_Systems>
R3UsersLoggedIn
R3System
MTEClass
<SRMServer_Systems>
OperatingSystem
R3System
MTEClass
<SRMServer_Systems>
OperatingSystem
R3System
<SRMSERVER_SYSTEMS>
R3System
MoniSegment
MoniContext
<SRMSERVER_SYSTEMS>
<ANY>
System Configuration
R3System
MTEClass
<SRMSERVER_SYSTEMS>
CcmsFileMonitoring no such MTE
class exists, needs to be changed to
filesystemMO
3.1.2.3 Monitoring of SAP Live Auction Cockpit Web

Presentation Server based on Java Server 6.0
3.1.2.3.1
GRMG Availability Monitoring for SAP Live

Auction Cockpit Web Presentation Server based
on Java Server 6.0
NOTE
As of SAP enhancement package 1 for SAP Supplier Relationship Management (SAP SRM) 7.0, it
has been possible to run Live Auction Cockpit on the ABAP server. If you have configured your
SAP SRM server to run Live Auction Cockpit on the ABAP server, section 3.1.2.3 is no longer
applicable.
18/68
PUBLIC
2013-08-13
3.1
SAP Live Auction Cockpit Web Presentation Server based on Java (LACWPS) 6.0 uses SAP SRM Server
for data persistence and business logic, the monitoring tree element (MTE) Auction for applicationspecific monitoring of SAP Live Auction Cockpit Web Presentation Server based on JAVA server
(LACWPS) 6.0. For more information, see SRM Monitor.
The Live Auction Cockpit based on the Java server runs on SAP NetWeaver Application Server (Java)
7.02. The main focus of this component is the monitoring of the SAP J2EE Engine.
3.1.2.3.2
Activating GRMG Monitoring
Procedure
1.
2.
Obtain the XML format customizing files for the GRMG monitoring scenarios of Live Auction
Cockpit based on Java server.
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 based on Java server.
It can be found in <INSTDIR>:\usr\sap\<system name>\SYS\global\srmla\monitoring.
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 must be:
<scenstarturl>http://yourhostname:8080/srm/heartBeat</scenstarturl>
NOTE
3.
Each instance of Live Auction Cockpit based on Java server 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 based on Java server, 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).
Upload the customizing file into the central monitoring system.
1. Log on to the monitoring system as a user with administrator rights.
Ensure that you log on to the central application server. This is the server that offers the
enqueue service. You can determine which server is your central server with transaction
SM51 or with transaction RZ03.
2013-08-13
PUBLIC
19/68
3.1
2.
3.
4.
Start transaction GRMG by entering GRMG in the OK field in the SAPGUI toolbar.
Click Upload a GRMG Scenario.
A file selection dialog box is displayed.
4. Navigate to the directory in which the customizing file is located and select the file.
5. 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).
After you have uploaded all of the customizing files, start the availability monitoring.
CAUTION
Ensure 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
No messages regarding the start of availability monitoring are displayed. For more information, see
Verifying the GRMG Availability Monitoring.
Once you start GRMG monitoring, the monitoring scenarios that you installed run automatically. By
default, the CCMS monitoring architecture repeats each GRMG availability monitoring scenario
automatically every ten minutes.
Adding Scenarios to the XML Customizing File
1.
2.
3.
4.
Copy everything in between the tags (including the tags themselves): <scenario> and </
scenario>.
Paste them below the last <scenario> tag.
Repeat this step for each additional instance you wish to monitor.
Modify the values in between <scenversion> and </scenversion>, and <sceninst> and </
sceninst>, so that they are unique for each instance.
RECOMMENDATION
5.
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 on).
Change the URL specified between the <scenstarturl> and </scenstarturl> tags to the correct
and fully qualified hostname and port for this particular scenario.
20/68
PUBLIC
2013-08-13
3.1
3.1.2.3.3
Verifying GRMG Availability Monitoring for Live

Auction based on Java Server
Procedure
Displaying Scenario Execution Status
NOTE
If you are running live auction on the ABAP Server, this section is no longer relevant for you.
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 subtree 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.
Result
If the Java 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 Java 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
Troubleshooting GRMG Availability Monitoring.
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 Verifying the GRMG
Availability Monitoring, one of the following can be the cause:
2013-08-13
PUBLIC
21/68
3.1
w 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.
w 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
GRMG_SCENARIOS
GRMG_SCENARIO_T
Required Contents
w The technical name [SCEN_NAME] of each monitoring scenario
that you uploaded
w The URL used by the scenario to test availability
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
2.
If any of the required table content is missing, then the customizing file did not contain
complete or valid XML customizing data for GRMG.
Download the newest customizing files from the SAP Community Network at the Internet
address http://www.sdn.sap.com/irj/sdn/nw-products .
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:
w The host specified in the scenario URL may have been unreachable.
w No answer was received.
w An invalid answer was received.
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.
22/68
PUBLIC
2013-08-13
3.1
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 causes:
GRMG Scenario Error Message
Cause
Reason for HTTP POST failure:

> HTTP communication failure
> Connect failed
> Time-out occurred
1.

> TCP/IP error occurred
> Data error occurred
> Internal error occurred
> System failure occurred
> Argument not found
> Plug-in not active
> Internal error
> HTTP invalid state
> Destination not found
> Not authorized to use HTTP
destination
Reason for scenario failure:
> <no error message>

> No response for any component in
request
> <no error message>
2013-08-13
The URL specified in the scenario customizing points to a nonexistent host or port.
Check that the URL is valid.
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.
Your installation is having problems with the network
configuration or with network operation.
There is a problem with the HTTP service in the SAP system you are
using for monitoring. Check on the status of this service with
transaction SMICM.
There is a problem with the HTTP server specified in the scenario
URL.
There is a problem with the HTTP client function in the SAP system
you are using for monitoring. Check on the status of your HTTP
operations with transaction SMICM.
You are using an RFC destination of type HTTP instead of specifying

a URL directly in scenario customizing.
The destination has not been defined or there is a destination use
authorization problem.
This scenario error often occurs when an HTML 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.
Check that the GRMG application is installed and runs correctly at
the target host.
This error message may occur if a GRMG application responds
without reporting the status of any of the components specified in
the GRMG monitoring request.
Check that the components specified in the GRMG customizing file
match those checked by the GRMG application.
PUBLIC
23/68
3.1
GRMG Scenario Error Message

~v <Any message relating to invalid
XML format>
~v <no error message>
~v Any message having to do with the
CCMS monitoring architecture,
such as
- Invalid TID
- Wrong segment
Cause
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.
A formal DTD error, such as unbalanced tags, occurred in the
response.
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.
There is a problem in the CCMS monitoring architecture.
Check the alerts elsewhere in the CCMS Selfmonitoring monitor
for possible causes. Be sure, 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 Supplier Relationship Management (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.
2.
Go to transaction RZ20 and create a new monitor under the SRM monitor set created earlier: SAP
(CEN ) EnterpriseBuyer Monitors.
On the top level, create a virtual node for each of the following areas:
~v Approval
~v Auction
~v Bid Invitation
~v Component Planning
~v Confirmation
~v Contract Management
~v Invoice
~v Others
~v Procurement Card
~v Purchase Order
24/68
PUBLIC
2013-08-13
3.1
3.
3. Shopping Cart

3. User Administration
On the second level, enter all MTE classes as rule-based monitors for each area as described in the
table below:
Node
Type
Approval
Virtual
CCMS_DEFINE_R3_SYS Rule
TEMS
CCMS_GET_MTE_BY_ Rule
CLASS_AND_CLIENT
Auction
Virtual
TEMS
CLASS_AND_CLIENT
Bid Invitation
Virtual
TEMS
CLASS_AND_CLIENT
Component Planning
Virtual
TEMS
CLASS_AND_CLIENT
Confirmation
Virtual
TEMS
CLASS_AND_CLIENT
Contract Management
Virtual
TEMS
CLASS_AND_CLIENT
Invoice
2013-08-13
Parameter
Value
R3System
<SRMSERVER_SYSTEMS>
R3System
R3Client
MTEClass
<SRMSERVER_SYSTEMS>
<EBP Client>
BBP_Approval
R3System
<SRMSERVER_SYSTEMS>
R3System
R3Client
MTEClass
<SRMSERVER_SYSTEMS>
<EBP Client>
BBP_AUC
R3System
<SRMSERVER_SYSTEMS>
R3System
R3Client
MTEClass
<SRMSERVER_SYSTEMS>
<EBP Client>
BBP_BID
R3System
<SRMSERVER_SYSTEMS>
R3System
R3Client
MTEClass
<SRMSERVER_SYSTEMS>
<EBP Client>
BBP_PM
R3System
<SRMSERVER_SYSTEMS>
R3System
R3Client
MTEClass
<SRMSERVER_SYSTEMS>
<EBP Client>
BBP_Confirmation
R3System
<SRMSERVER_SYSTEMS>
R3System
R3Client
MTEClass
<SRMSERVER_SYSTEMS>
<EBP Client>
BBP_Contract
Virtual
PUBLIC
25/68
3.1
Node
Type
TEMS
CLASS_AND_CLIENT
Others
Virtual
TEMS
CLASS_AND_CLIENT
Procurement Card
Virtual
TEMS
CLASS_AND_CLIENT
Purchase Orders
Virtual
TEMS
CLASS_AND_CLIENT
Shopping Cart
Virtual
TEMS
CLASS_AND_CLIENT
User Administration
Virtual
TEMS
CLASS_AND_CLIENT
Parameter
Value
R3System
<SRMSERVER_SYSTEMS>
R3System
R3Client
MTEClass
<SRMSERVER_SYSTEMS>
<EBP Client>
BBP_INV
R3System
<SRMSERVER_SYSTEMS>
R3System
R3Client
MTEClass
<SRMSERVER_SYSTEMS>
<EBP Client>
BBP_OT
R3System
<SRMSERVER_SYSTEMS>
R3System
R3Client
MTEClass
<SRMSERVER_SYSTEMS>
<EBP Client>
BBP_PC
R3System
<SRMSERVER_SYSTEMS>
R3System
R3Client
MTEClass
<SRMSERVER_SYSTEMS>
<EBP Client>
BBP_PO
R3System
<SRMSERVER_SYSTEMS>
R3System
R3Client
MTEClass
<SRMSERVER_SYSTEMS>
<EBP Client>
BBP_ShoppingBasket
R3System
<SRMSERVER_SYSTEMS>
R3System
R3Client
MTEClass
<SRMSERVER_SYSTEMS>
<EBP Client>
BBP_US
3.1.2.5 Monitoring SRM-MDM Catalog 7.02

3.1.2.5.1
SRM-MDM Catalog 7.02
SRM-MDM Catalog is a Java Web Dynpro component for users with a database repository on the MDM
Server. SRM Server transactions are connected to the catalog using the Open Catalog Interface.
26/68
PUBLIC
2013-08-13
3.1

NOTE
For more information about MDM Core CCMS monitoring functions, see SAP Note 956783.
3.1.2.5.2
GRMG Availability Monitoring for SRM-MDM

Catalog 7.02
SRM-MDM Catalog runs on the SAP NetWeaver Application Server (Java) 7.3. The main focus of
monitoring this component is the monitoring of the SAP J2EE Engine.
For more information about monitoring the SAP NetWeaver Application Server (Java), see the Monitoring
Setup Guide for SAP NetWeaver (MSG) under SAP NetWeaver 7.0 System Administration and Maintenance
Information Operations Information on SAP Help Portal at http://help.sap.com/netweaver and Technical
Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/
netweaver.
Prerequisites
2r Your SRM-MDM Catalog is connected to the Central Monitoring System (CEN) and registered as
a remote system.
2r 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.
2.
3.
Go to transaction RZ20 and create a new monitor: SRM-MDM Catalog UI

On the top level, create a virtual node for each of the following areas:
2r J2EE Engine 7.03 on <Hostname>
2r GRMG Availability Monitor
On the second level, create rule-based monitors for each area as described in the following table:
Node
Type
J2EE Engine 7.02 on <Hostname>

Virtual
Rule
Rule
GRMG Availability Monitor

Virtual
Rule
Rule
Parameter
Value
R3System
R3System
MTEClass
J2EE_Systems
J2EE_Systems
J2EE_PROC
R3System
R3System
MTEClass
<CURRENT>
<CURRENT>
GRMG_WDADM630
NOTE
The GRMG customizing file for the MDM catalog, named grmg-customizing, can be found at
the following location:${SDM_ROOT};origin\sap.com\tc\mdm\srmcat\uisearch\
MAIN_SMDM72SP_D\2\10486684\tc~mdm~srmcat~uisearch.sda\META-INF
2013-08-13
PUBLIC
27/68
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 Enhancement Package 3 for SAP Supplier
Relationship Management (SAP SRM) 7.0
SAP enhancement package 3 for SAP Supplier Relationship Management (SAP SRM) 7.0 is technically
based on SAP NetWeaver 7.40.
For information about technical problem analysis (for example, for database, operating system,
workload analysis, and so on), see Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver
on SAP Help Portal at http://help.sap.com/netweaver.
The SAP SRM Application Operations Guide covers only differences and additional information specific
to the SAP SRM solution.
SAP SRM 7.13 application-specific logging information is written to the application log.
3.2.1.2 SAP Live Auction Cockpit Web Presentation Server

based on Java (LACWPS) 6.0
SAP Live Auction Cockpit Web Presentation Server based on Java (LACWPS) 6.0 is technically based on
SAP NetWeaver 7.40.
NOTE
SAP Live Auction Cockpit Web Presentation Server uses the SRM Server as its persistence layer.
Detailed problem and performance analysis must be done in both the SAP Live Auction Cockpit
Web Presentation Server and in the SRM Server.
3.2.1.3 SRM-MDM Catalog 7.02

SRM-MDM Catalog 7.02 is technically based on SAP NetWeaver 7.40.
The SAP SRM Applications Operations Guide covers only differences and additional information
specific to the SAP SRM solution.
28/68
PUBLIC
2013-08-13
3.2
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.
System Administration and Maintenance Information Operations Information SAP Help Portal at http://
3.2.2.2 Data Archiving Monitors

3.2.2.3 Distributed Statistical Records

For more information about the motivation behind distributed statistical records and how to define
and use them, see the Monitoring Setup Guide for SAP NetWeaver (MSG) under SAP NetWeaver 7.40 System
Administration and Maintenance Information Operations Information on SAP Help Portal at http://
3.2.2.4 Business Packages

For more information about the analysis and monitoring of Business Packages and SAP NetWeaver
Portal, see Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP Help Portal at http://
For information about how to monitor the cache upload of the Business Package for Supplier
Collaboration 4.0, see SAP Note 749231.
2013-08-13
PUBLIC
29/68
3.2
3.2.3 Logs and Trace (ComponentSpecific or ScenarioSpecific)

For Live Auction Cockpit Web Presentation Server based on Java (LACWPS) 6.0: Component-Specific Monitoring
Logging Categories
Tracing Locations
/Applications/SRMLA
com.sap.srm.la
For SRM-MDM Catalog 7.01: Component-Specific Monitoring
Logging Categories
Tracing Locations
/Applications/MDMSRMCAT
com.sap.mdm.srmcat
Logging and tracing for ABAP components are done using transaction SLG1. Each log in the database
also has the attributes Object and Sub-object. These attributes describe the application that wrote the log,
and classify this application. You can find the object and sub-objects of SAP SRM applications in the
following list:
For SRM Server 7.01: Component-Specific Monitoring
Software Component Object
Sub-Object
Object Text
SAP SRM SERVER
/SAPSRM/* (namespace used as of SAP SRM All Sub-objects under
6.0)
3.2.4 Data Growth and Data Archiving Monitors

SAP enhancement package 3 for SAP Supplier Relationship Management (SAP SRM) 7.0 uses the
standard tools for archiving and monitoring data archiving available in SAP NetWeaver, and does not
require an application-specific tool.
For more information about Data Archiving see SAP Library for SAP NetWeaver on SAP Help Portal at
http://help.sap.com/netweaver.
30/68
PUBLIC
2013-08-13
Management of SAP SRM
4.1
Administration Tools of Software Components
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.
For more information about the underlying technology, see Technical Operations for SAP NetWeaver at SAP
4.1 Administration Tools of Software Components

All SAP SRM 7.03 components are technically based on SAP NetWeaver 7.40. For information about
the relevant administration tools, see Technical Operations for SAP NetWeaver at SAP Library for SAP
NetWeaver on SAP Help Portal at http://help.sap.com/netweaver.
4.2 Software Configuration

All components for SAP enhancement package 3 for SAP Supplier Relationship Management (SAP
SRM) 7.0 are technically based on SAP NetWeaver 7.40. For information about the relevant
configuration tools, see Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP Help
Portal at http://help.sap.com/netweaver.
J2EE based components store their technical configuration parameters in the Configuration Manager
(CM) repository. For more information about the Config Tool, see Technical Operations for SAP
NetWeaver at SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver.
SAP SRM
SERVER
SAP SRM
SERVER
Configuration
Tool(s)
Implementation
Guide (IMG)
SAP SRM
SERVER
SAP Solution
Manager
Detailed Description
The Implementation Guide is the standard SAP tool for ABAP-based
system used for component Customizing.
Run transaction SPRO to access the Implementation Guide.
SAP Solution Manager is the standard SAP tool for process- and scenariobased configuration.
For more information, see SAP Note 1580107.
4.3 Starting and Stopping

The following information is scenario-independent.
2013-08-13
PUBLIC
31/68
4.3
Starting and Stopping
Start and Stop Sequence and Tools

Software Component
Start and Stop Sequence and Tools

Sequence
Tool
SAP NetWeaver Process

Integration Server
FG"@
FG"@
FG"@
FG"@
Back-End System (OLTP) 3
FG"@
FG"@
SRM Server
FG"@
FG"@
Search and Classification

(TREX)
FG"@
SAP Live Auction Cockpit 6

Web Presentation Server
based on Java 6.0 (started
together with SRM
Server)
SRM-MDM Catalog 7.02 7
Adobe Document Services 8

(ADS)
32/68
FG"@
Documentation
Technical Operations for SAP NetWeaver

STARTSAP (UNIX)
SAP Management
at SAP Library for SAP NetWeaver on
Console (Windows)
SAP Help Portal at http://
STARTSAP (UNIX)
SAP Management
Console (Windows)
STARTSAP (UNIX)
SAP Management
Console (Windows)
STARTSAP (UNIX)
SAP Management
Console (Windows)
Start Services
(Windows)
Start Daemons (UNIX)
Application Server:
FG"@ STARTSAP (UNIX)
FG"@ SAP Management
Console (Windows)
MDM Server:
FG"@ SAP Management
Console (Windows and
other platforms)
Repositories:
FG"@ MDM Console
(Windows)
FG"@ MDM CLIX (other
platforms)
Visual Administrator
You can access the Visual
Administrator at the
operating system level (D:/
USR/SAP/<SID>/
JC<INSTNO>/J2EE/
ADMIN/GO.BAT)
PUBLIC
SAP NetWeaver MDM Solution Operations

Guide at SAP Library for SAP NetWeaver
MDM on SAP Help Portal at http://
help.sap.com/nwmdm.
Configuration Guide for SAP Interactive

Forms by Adobe at http://
www.sdn.sap.com/irj/sdn/adobe.
2013-08-13
4.4
Backup and Restore
4.4 Backup and Restore

To ensure that you can restore and recover your system in case of failure, you must back up your
system landscape regularly.
The backup-and-restore procedure for SAP SRM consists of two parts:
Sc Backup and restore for each component
Sc 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 Categories of System Components for Backup and Restore.
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
Application
Category Data Type
SAP SRM Server XI

SAP NetWeaver XI
Portal
SAP Live Auction XI
Cockpit Web
Presentation
Server
SAP Live Auction VIII
Cockpit Web
Presentation
Server using
standalone SAP
NetWeaver
Application
Server Java
SRM-MDM
Catalog
SAP NetWeaver
Process
Integration
2013-08-13
XI
Backup Method for Application Data
Sc
Sc
Sc
Sc
Sc
Database and log backup

File system backup (full and/or incremental)
Included in SRM Server
Original
Sc
Sc
Sc
Sc
Data is stored on SRM Server

New installation
Original and
Replicated
Data is stored in the MDM repositories.

For more information, see the MDM 7.1 Solution Operations Guide for
SAP NetWeaver MDM at SAP Library for SAP NetWeaver MDM on SAP
Help Portal at http://help.sap.com/nwmdm
Sc Database and log backup
Sc File system backup (full and/or incremental)
Original and
Replicated
Original
Original and
Replicated
Original and
Replicated
PUBLIC
33/68
4.4
Backup and Restore
Component
Search and
Classification
(TREX)
Adobe
Document
Services (ADS)
Application
Category Data Type
Backup Method for Application Data
III / IV
QM#S File system backup
QM#S File system backup
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 Supplier Relationship Management (SAP SRM) business
scenario, it is impossible to find a common point of consistency across the whole SAP Supplier
Relationship Management (SAP SRM) landscape.
The only backup type that can guarantee full physical and logical consistency (these terms are explained
below) of an SAP Supplier Relationship Management (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.
QM#S Logical consistency
Restores the SAP Supplier Relationship Management (SAP SRM) 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).
QM#S Physical cConsistency
Restores individual SAP Supplier Relationship Management (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 Supplier
Relationship Management (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.
34/68
PUBLIC
2013-08-13
4.4
Backup and Restore
A distributed, business system landscape requires a detailed backup-and-restore 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:
Je Time required for a complete reinstallation
Je Time required for additional configuration
Je Effects of the expected downtime of one or more infrastructure components with regard to the
overall availability of the SAP Supplier Relationship Management (SAP SRM) landscape
RECOMMENDATION
We recommend that you back up the runtime infrastructure of all the components of an SAP
SRM landscape.
You must test your backup-and-restore concept regularly. A single backup-and-restore test is
insufficient, since the SAP Supplier Relationship Management (SAP SRM) landscape is likely to
change, and render a given concept redundant. System administrators need an up-to-date backupand-restore concept to be able to quickly restore failed systems.
For more information, see Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP
Help Portal at http://help.sap.com/netweaver.
4.4.2 Backup of Individual Components in an SAP Supplier

Relationship Management (SAP SRM) Landscape
When you plan a backup-and-restore strategy for application, software, and configuration files, you
must consider the following elements:
Je Operating system
Je RDBMS data files
Je RDBMS software
Je SAP software and file systems
Je Log files (SAP and other)
Je Software of other system components (file systems and configuration files)
NOTE
A component that has application data (database, for example) also contains application
software and configuration files (runtime infrastructure) that need to be backed up.
2013-08-13
PUBLIC
35/68
4.4
Backup and Restore
A component that contains no application data may still contain configuration files and
software that do require a backup.
4.4.2.1 Backup and Restore 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.
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, and to the operating system.
RECOMMENDATION
We recommend that you perform a full system backup after installation and that you back up
the file systems of both the installed software and the operating system on a regular basis.
For more information about possible backup scenarios, see SAP Service Marketplace at http://
service.sap.com/atg Advanced Technology Group Backup & Restore .
4.4.2.2 Database Backup and Restore

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.
36/68
PUBLIC
2013-08-13
4.4
Backup and Restore
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.
4.4.2.3 Backup and Restore for SAP NetWeaver Application

Server (SAP NetWeaver AS) 7.40
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.
4.4.3 Backup and Restore for Individual System Components

4.4.3.1 SAP Live Auction Cockpit Web Presentation Server
based on Java (LACWPS) 6.0
SAP Live Auction Cockpit Web Presentation Server based on Java (LACWPS) 6.0 is technically based on
SAP NetWeaver 7.40.
NOTE
SAP Live Auction Cockpit Web Presentation Server uses the SRM Server as its persistence layer.
Detailed problem and performance analysis must be done in both the SAP Live Auction Cockpit
Web Presentation Server and in the SRM Server.
2013-08-13
PUBLIC
37/68
4.4
Backup and Restore
4.4.3.2 Enhancement Package 2 for SRM-MDM Catalog 7.0

4.4.4 Backup and Restore for a Complete SAP SRM Landscape

4.4.4.1 Landscape Shutdown
You have to shut down the individual components in the following sequence:
, Shut down the SAP J2EE server that is connected to the SAP SRM server back-end system.
Adobe Document Services
, Shut down the SAP J2EE server that is connected to the SAP SRM server back-end system.
SAP Live Auction Cockpit
, Shut down the SAP J2EE server that is connected to the SAP SRM server back-end system. This
only applies when you run SAP Live Auction Cockpit on a separate server.
SRM-MDM Catalog
, Shut down the SAP J2EE Engine on which the catalogs are installed and
shut down the underlying Relational Database Management System (RDBMS).
SAP SRM Server
, Make sure that all outgoing documents have been sent and all incoming documents have been
processed. Shut down the ABAP-based part of supplier-self-services (SUS) and the underlying
Relational Database Management System (RDBMS).
Back-End System (OLTP)
, Shut down the SAP system and the underlying Relational Database Management System
(RDBMS).
Search and Classification
, Shut down the SAP system and the underlying Relational Database Management System
(RDBMS).
SAP NetWeaver Process Integration Server
, Shut down the SAP NetWeaver Process Integration Server and the underlying Relational Database
Management System (RDBMS). The J2EE Engine shuts down automatically when the back end is
stopped.
4.4.4.2 Offline Backup of the SAP SRM Landscape

To make a backup of the individual components of the landscape, proceed as described in Backup of
Individual Components in an SAP SRM Landscape.
38/68
PUBLIC
2013-08-13
4.5
Application Copy
NOTE
When you make a backup of the SAP NetWeaver Process Integration (SAP NetWeaver PI) Server,
ensure that you also make a backup of 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...).
4.4.4.3 Landscape Startup

For the startup sequence of the individual components, see Start and Stopping.
4.4.5 Backup and Restore for an SAP SRM Business Scenario

To make a backup of an SAP Supplier Relationship Management (SAP SRM) business scenario, you
have to apply the backup-and-restore steps of the components that comprise a business scenario. For
these steps, see Backup and Restore for Individual System Components.
To see which components are required for a specific business scenario, see Software Component Matrix.
4.5 Application Copy

4.5.1 Homogeneous System Copy
For a homogeneous system copy of SAP enhancement package 3 for SAP Supplier Relationship
Management (SAP SRM) 7.0, the standard procedures of SAP NetWeaver apply. For more information,
see the SAP Community Network at http://www.sdn.sap.com Home Application Lifecycle Management
Technical Enablement Initial Setup System Copy .
4.5.2 Heterogeneous System Copy

Heterogeneous system copies for SAP enhancement package 3 for SAP Supplier Relationship
Management (SAP SRM) 7.0 are currently supported on request and on a project basis. For more
information, see http://service.sap.com/osdbmigration.
NOTE
A client copy from one system to another system with different operating system or database is
not an alternative to a complete heterogeneous migration. For example, client copies do not
ensure that all repository changes are taken over into the new sytem. Therefore, if you want to
change your SAP enhancement package 3 for SAP Supplier Relationship Management (SAP SRM)
7.0 database or application server platform, a heterogeneous system copy is the only procedure
that ensures full data replication into the new system.
2013-08-13
PUBLIC
39/68
4.6
Scheduled and Manual Periodical Tasks
4.6 Scheduled and Manual Periodical Tasks

4.6.1 Periodical Tasks for SAP NetWeaver 7.40
For more information about standard background jobs and periodical tasks for SAP NetWeaver
components, see Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP Help Portal
at http://help.sap.com/netweaver.
4.6.2 Periodical Tasks for SAP Enhancement Package 2 for

SAP SRM 7.0
Standard Background Jobs
Program Name / Task
CLEAN_REQREQ_UP
(and START_CLEANER)
BBP_GET_STATUS_2
RSPPFPROCESS
BBPERS
BBP_DELETE_LOCAL_A
CCOUNT
BBP_SC_TRANSFER_G
ROUPED
SRM_CALL_HANDLER_
REPORT
RSCONN01
/SAPSRM/
OFFLINE_APPROVAL_SE
ND
Required or
Optional
Recommended
Frequency
Required
5 to 10 minutes
For more information, see the Solution

Manager content on each SAP SRM
scenario you have implemented.
5 minutes
Send job
Required*
Optional
Optional
Optional
Optional
Required**
Required
Optional
* The configuration of this job depends on the number of shopping cart items created per week. It is
recommended that you 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 must be monitored regularly to
avoid system resources being utilized completely.
** Only if Records Management is used.
For more information about Required Background Jobs, see SAP Library for SAP NetWeaver on SAP Help
For more information about Components of SAP Communication Technology, see Function-Oriented
View for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver.
For more information about Reports, see SAP Library for Supplier Relationship Management on SAP Help
Portal at http://help.sap.com/srm.
For more information about Offline Approval, see SAP Library for Supplier Relationship Management on SAP
Help Portal at http://help.sap.com/srm.
40/68
PUBLIC
2013-08-13
4.6
Scheduled and Manual Periodical Tasks
4.6.3 Periodical Tasks for SAP Enhancement Package 3 for

SRM-MDM Catalog 7.0
Standard Background Jobs
Program Name / Task
Required or
Optional
SRMMDM_CTR_TRAN Optional
SFER
Recommended
Frequency
Daily
This report is only required if contracts are

not distributed automatically. It initiates the
transfer of all contracts that are flagged for
distribution.
For more information about using MDM, see the SAP NetWeaver MDM Solution Operation Guide at SAP
Library for SAP NetWeaver MDM on SAP Help Portal at http://help.sap.com/nwmdm.
4.6.4 Manual Periodical Tasks for Enhancement Package 3

for SAP Supplier Relationship Management (SAP SRM)
7.0
For more information about the required manual periodical tasks for the SRM Server components,
see Reports under SAP Supplier Relationship Management at SAP Library for Supplier Relationship Management on SAP
Help Portal at http://help.sap.com/srm.
4.6.5 Manual Periodical Tasks for Live Auction Cockpit based

on Java Server (LACWPS 6.0) and Live Auction Cockpit
based on ABAP Server
You can periodically clear activity logs and message data from the live auction component to ensure
that the system response time for your live auction scenario is always optimal. This is valid for live
auctions based on both the JAVA server and the ABAP server, which are available from SAP
enhancement package 1 of SAP Supplier Relationship Management 7.0 onwards.
To perform this task, run the report BBP_LA_MAINTAIN periodically. Choose Cleanup Activity Log to delete
the activity logs for all live auctions in your system.
CAUTION
When you choose Cleanup Activity Log , you lose all records of auction actions performed during a
live auction event.
Choose the appropriate option under section Clean Up messages and Login Data.
CAUTION
When you choose this option, you lose all auction runtime data that can be seen in the Live
Auction Cockpit.
2013-08-13
PUBLIC
41/68
4.7
Logon and Load Balancing
4.7 Logon 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.
SoH7 For more information on network load balancing, see Technical Operations for SAP NetWeaver at SAP
SoH7 For information about load balancing between many Java instances and on the SAP Web Dispatcher,
see Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP Help Portal at http://
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 Engine (UME) of SAP NetWeaver.
For more information, see the SAP NetWeaver Security Guide under Security Information on SAP Help Portal at
http://help.sap.com/netweaver.
Because of special requirements of the SRM Server, the following SRM-specific user management tools
are also available:
User Management Tools (SRM Server)
Tool
Prerequisites
Self Registration SRM

Server
Manage User Data
(BBPUSERMAINT) SRM
Server
User Management in
Supplier Self-Services
SRM Server (SUS)
SAP Library for SAP Supplier Relationship Management on SAP Help

Portal at http://help.sap.com/srm
Employee Data under SAP Library for Supplier Relationship
Management on SAP Help Portal at http://help.sap.com/srm
Refer to the
documentation.
Refer to the
documentation.
SAP Library for Supplier Relationship Management on SAP Help

Portal at http://help.sap.com/srm
To create users in the

SUS system, you
must be assigned as an
administrator.
Users in supplier self-services act as bidders in the SRM Server as well. These users need to be created
in SAP Supplier Relationship Management (SAP SRM) with the same user ID. This can be done via
replication from SUS.
For more information, see the document Settings for SUS in SAP Solution Manager (transaction
SOLAR_LIBRARY) at SAP SRM Configuration Structures
SAP SRM 7.0 EHP1 Basic Settings for Service
Procurement Classic Settings for Supplier Collaboration Settings for Supplier Self-Services .
42/68
PUBLIC
2013-08-13
4.9
Printing
4.9 Printing
SAP enhancement package 3 for SAP Supplier Relationship Management (SAP SRM) 7.0 uses the
standard functionality of SAP NetWeaver for printing. For more information, see the SAP Printing
Guide at SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver.
2013-08-13
PUBLIC
43/68

High Availability
5 High Availability
The following table describes the business impact for each component of SAP Supplier Relationship
Management (SAP SRM), if that component should become unavailable.
Component
Business Impact if Unavailable
SAP SRM 7.13

Business critical: single point of failure for all scenarios.
SAP LACWPS 6.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 All scenarios using SAP NetWeaver Process Integration will only have asynchronous
Process
messaging available.
Integration
Document delivery is delayed but not cancelled.
SAP NetWeaver As all scenarios are only available via the Portal, a failure would be critical.
Portal 7.3
SAP enhancement package 3 for SAP Supplier Relationship Management (SAP SRM) 7.0 follows the
general high availability concept for all SAP NetWeaver-based systems. For more information about
high availability and switch-over, see the documentation on SAP Help Portal at http://
help.sap.com
SAP NetWeaver SAP NetWeaver 7.40 SAP NetWeaver 7.40 Library English SAP
NetWeaver Library: Function-Oriented View Solution Life Cycle Management SAP High Availability .
2013-08-13
PUBLIC
45/68

Software Change Management
6.1
Transport and Change Management
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:
C/ Transport and Change Management
Enables and secures the distribution of software changes from the development environment to
the quality assurance and productive environment.
C/ Development Request and Development Release Management
C/ Template Management
Enables and secures the rollout of global templates, including localizations
C/ Quality and Test Management
Reduces the time, costs, and risks associated with software changes.
C/ Support Packages and SAP Notes Implementation
Provides standardized software distribution and maintenance procedures.
C/ 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.
For transport and change management issues, the procedures of SAP NetWeaver apply for SAP
enhancement package 3 for SAP Supplier Relationship Management (SAP SRM) 7.0.
For more information about Change and Transport System (CTS), see SAP Library for SAP NetWeaver on SAP
SAP enhancement package 3 for SAP Supplier Relationship Management (SAP SRM) 7.0 can be used
with more than one portal tenant, and in several different ways.
2013-08-13
PUBLIC
47/68
6.2
Development Requests and Development Release Management
-h.^ 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 Business Intelligence (SAP NetWeaver BI).
-h.^ 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.
-h.^ Other SAP SRM components could be shared with other SAP or non-SRM applications like SAP
NetWeaver Process Integration and SAP NetWeaver 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 enhancement package 3 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 (based on Java), are deployed using the Software Deployment Manager.
Detailed instructions on applying a support package stack to SAP NetWeaver are given in Support Package
Stack Information under System Administration and Maintenance Information Maintenance Information on SAP
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.
48/68
PUBLIC
2013-08-13
6.4
Release and Upgrade Management
6.4 Release and Upgrade Management

Component Release
Software Component
SAP SRM
LAC WPS
Release
7.0
6.0
Tool
System Status
System Info http://<server>:<port>/sap/monitoring/
ComponentInfo
1Y 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.
1Y 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, For more information about BC Configuration Sets, see Function-Oriented View for
SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver.
6.6 Quality Management and Test Management

You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP).
For more information about test workbench for SAP NetWeaver Application Server (ABAP), see FunctionOriented View for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver.
For more information on testing software changes based on SAP NetWeaver Application Server (Java),
see Application Server Java at Function-Oriented View for SAP NetWeaver on SAP Help Portal at http://
2013-08-13
PUBLIC
49/68

Troubleshooting
7 Troubleshooting
All services offered by SAP Active Global Support are available for SAP enhancement package 3 for SAP
Supplier Relationship Management (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 SAP NetWeaver Problem Analysis Guide (PAG) at Solution Life Cycle Management for SAP
NetWeaver under Solution Oriented View for SAP NetWeaver on SAP Help Portal at http://help.sap.com/
netweaver.
Possible problem situations using SAP enhancement package 3 for SAP Supplier Relationship
Management (SAP SRM) 7.0
Problem
Application
Components
No monitoring information is All SAP Supplier
displayed in the CCMS Alert
Relationship
Monitor (transaction RZ20) of
Management
the central monitoring SAP Web (SAP SRM)
AS ABAP system. However,
application
monitoring information is
components
available in the Visual
Administrator of the J2EE server,
for example status information
in the J2EE status monitors.
Error Page not found or not
Business Packages
available while accessing a
for SAP SRM
catalog configured in the SRM
Server.
Display of System messages in
srm-ebp-ca-ui
Portal and NWBC : Transaction
SM02 in SAPGUI allows a user to
add three messages
simultaneously. When these
messages are displayed in a popup
on SAP GUI, the author name
appears only once followed by all
three messages. However, When
these messages are displayed in
2013-08-13
Information
See the (CCMS) CCMS Monitoring Infrastructure guide
at SAP Community Network http://wiki.sdn.sap.
com Wiki My Home Technology Troubleshooting Guide
(JSTTSG)Main Page Application Server ABAP (CCMS)
CCMS Monitoring Infrastructure
See SAP Note 1260119.
See SAP note 1676725 for other configuration steps on

this feature.
PUBLIC
51/68
Troubleshooting
portal and NWBC, the author

name is displayed separately for
all three messages.
NOTE
The search function in attachments is not supported. Indexing, however, is supported.

Restarting Search and Classification may lead to diminished system performance.
NOTE
The search function is not supported for the following:

Z Shopping cart
Z Purchase order
Z Contract
Z Confirmation
Z Supplier
Z Product category
Z Product
Restarting Embedded Search may lead to diminished system performance.
For troubleshooting SAP NetWeaver MDM, see http://service.sap.com//installmdm71
Operation Guide Troubleshooting and Supportability Troubleshooting .
52/68
PUBLIC
Solution
2013-08-13
Support Desk Management
8.1
Remote Support Setup
8 Support Desk Management
Support Desk Management enables you to set up an efficient internal support desk for your support
organization that seamlessly integrates your end users, internal support employees, partners, and SAP
Active Global Support specialists with an efficient problem resolution procedure.
For support desk management, you need the methodology, management procedures, and tools
infrastructure to run your internal support organization efficiently. The following topics are covered:
T Remote Support
T Component hierarchy relevant for this application
8.1 Remote Support Setup

SAP support needs to be able to work remotely for highest efficiency and availability. Therefore all
required support tools must be remotely accessible for SAP support. For SAP SNC, the standard SAP
procedures for setting up remote support setup apply.
For information about Remote Support Setup, see SAP Service Marketplace at http://
service.sap.com/access-support.
8.2 Problem Message Handover

For information about processing of internal support messages and forwarding them to SAP, see Solution
Manager under SAP Library for Application Lifecycle Management on SAP Help Portal at http://help.sap.com/
alm. To send problem messages to SAP, use the referent SRM application component in the SAP
application component hierarchy.
The following table includes all components of SAP Master Data Governance in the application
component hierarchy (ACH):
CA-MDG
Infrastructure
CA-MDG-DRF
CA-MDG-RIF
CA-MDG-KM
CA-MDG-ML
CA-MDG-AF
CA-MDG-TRR
2013-08-13
Master Data Governance

Data Replication Framework
Replication Interface Framework
Key Mapping
Mass Load
Application Framework
Transport Registry
PUBLIC
53/68
8.3
CA Wily Introscope Integration
CA-MDG-VM
CA-MDG-ANR
CA-MDG-DQ
Applications
CA-MDG-APP
CA-MDG-APP-CLF
CA-MDG-APP-MM
CA-MDG-APP-BP
CA-MDG-APP-SUP
CA-MDG-APP-SUP-FI
CA-MDG-APP-SUP-LO
CA-MDG
-APP-SUP-SRM
CA-MDG-APP-FIN
BI Content
BW-BCT-MDG
Value Mapping
Analytics and Reporting
Data Quality
Applications
MDG Classification
MDG Material
MDG Business Partner (central parts)
MDG Supplier (central parts)
MDG Supplier (financial parts)
MDG Supplier (logistics parts)
MDG Supplier (SRM parts)
MDG Financials
Master Data Governance
NOTE
SAP Supplier Relationship Management (SAP SRM) does not ship specific roles for read-only
access for remote support. For this purpose, you can use the standard SAP NetWeaver roles
SAP_RCA_SAT_DISP for ABAP and SAP_JAVA_SUPPORT for Java.
For more information, see Remote Support Setup at Function-Oriented View for SAP NetWeaver on SAP Help
8.3 CA Wily Introscope Integration

To enable application analysis, including performance monitoring, CA Wily Introscope is integrated
into diagnostics in SAP Solution Manager. SAP provides Introscope instrumentation for SAP Supplier
Relationship Management (SRM).
Introscope incorporates dashboards for performance and stability analysis. In addition, the Introscope
Investigator provides a detailed view of all applications and environment metrics reported by an
Introscope agent to the Wily Enterprise Manager (EM). The EM is the Introscope server and is part of
SAP Solution Manager. You can trace user-specific interaction within Introscope using the Transaction
Trace.
Metrics, which are collected and reported through traces defined in Probe Builder Directive (PBD) files,
define the information that is collected at runtime. An Introscope agent collects this information and
reports it to the EM. The metrics are stored in the EM's database. You can view performance metrics
using either the Introscope Workstation or the Introscope Webview applications.
54/68
PUBLIC
2013-08-13
8.3
CA Wily Introscope Integration
To enable Introscope for SAP SRM, install and configure the Introscope Agent on the SAP SRM
application server hosts. For more information about setting up and configuring Introscope, see SAP
Note 797147 and its attached Frequently Asked Questions document.
The set of metrics on the EM for the SRM-MDM Catalog & LACWPS components are as follows:
1. Average CPU Time (s)
2. Average Response Time (ms)
3. Concurrent Invocations
4. Errors Per Interval
5. Responses Per Interval
6. Stall Count
NOTE
Starting the MDM Catalog and LACWPS applications through the SAP SRM portal triggers the
presence of metrics on the EM.
More Information
For more information about the installation, configuration, and use of diagnostics in SAP Solution
Manager, see SAP Service Marketplace under http://service.sap.com/diagnostics.
2013-08-13
PUBLIC
55/68

Appendix
9.1
Categories of System Components for Backup and Restore
9 Appendix
9.1 Categories of System Components for Backup and

Restore
Categories of System
Components
II
III
IV
VI
2013-08-13
Category Properties
Suggested Backup and

Recovery Methods
Pe No backup, new

installation in case of
a restore or
Pe Initial software
backup after
installation and
upgrade
Pe Backup of log files
Only software and
Pe Backup after changes
configuration
have been applied or
information, no
Pe No backup, new
application data
installation and
configuration in case
of a restore
Pe Backup of log files
Only replicated
Data:
application data,
Pe No data backup
replication time is
needed
sufficiently small for a
Backup of software,
restore
configuration, log files
Only replicated
Data:
application data, backup Pe Application-specific
recommended because
file system backup or
replication time is too
Pe Multiple instances
long, data managed by a Backup of software,
DBMS
Only replicated
Data:
application data, backup Pe Database and log
recommended because
backup or
replication time is too
Pe Multiple instances
long, data managed by a Backup of software,
DBMS
Original application data, Data:
standalone system, data Pe Application-specific
not managed by a DBMS
file system backup
Backup of software,
Only software, no
configuration or
application data
PUBLIC
Example
BDOC-modeler
SAP Gateway Comm.

Station
SAP Business Connector
SAP IMS / Search engine

Webserver
SAP IMS / Search engine

Webserver
Catalog Server
Webserver
57/68
Appendix
9.2
Related Information
Categories of System
Components
VII
VIII
IX
XI
Category Properties
Suggested Backup and

Recovery Methods

standalone system, data '" Database and log
managed by a DBMS, not
backup
Backup of software,
based on SAP NW AS
standalone system, based '" Database and log
on SAP NW AS
backup, application
log backup
Backup of software,
data exchange with other '" Application-specific
systems, data not managed
file system backup,
by a DBMS
data consistency with
other systems must
be regarded
Backup of software,
data exchange with other '" Database and log
systems, data managed by
backup, data
a DBMS, not based on SAP
consistency with
NW AS
other systems must
be regarded.
Backup of software,
data exchange with other '" Database and log
systems, based on SAP NW
backup, application
AS
log backup, data
consistency with
other systems must
be regarded
Backup of software,
Example
Standalone SAP system
SAP liveCache
SAP Mobile
Workbench
SAP system
SAP CRM
SAP NW BI
9.2 Related Information

The following table contains links to information relating to the Application Operations Guide.
Content
SAP SRM Master Guide, Installation and Upgrade
Guides
SAP Service Marketplace:
SAP Notes
http://service.sap.com/notes
58/68
http://service.sap.com/instguides Installation
and Upgrade Guides SAP Business Suite Applications SAP
SRM SAP SRM Server 7.13
PUBLIC
2013-08-13
Appendix
9.2
Related Information
Released Platforms
http://service.sap.com/platforms
Network Security
http://service.sap.com/securityguide
SAP NetWeaver (ABAP) Technical Operations Manual Technical Operations for SAP NetWeaver at SAP Library for SAP
NetWeaver on SAP Help Portal at http://help.sap.com/
netweaver
SAP NetWeaver (JAVA) Technical Operations Manual Technical Operations for SAP NetWeaver at SAP Library for SAP
NetWeaver on SAP Help Portal at http://help.sap.com/
netweaver
SAP Solution Manager
2013-08-13
http://service.sap.com/solutionmanager
PUBLIC
59/68

Reference
A.1
The Main SAP Documentation Types
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.
Cross-Phase Documentation
SAPterm is SAPs terminology database. It contains SAP-specific vocabulary in over 30 languages, as

well as many glossary entries in English and German.
X Target group:
X Relevant for all target groups
X Current version:
X On SAP Help Portal at http://help.sap.com Glossary
X In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes.
X Target group:
X Consultants
X System administrators
X Project teams for implementations or upgrades
X Current version:
X 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.
X Target group:
X System administrators
X Technology consultants
X Solution consultants
X Current version:
X 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,
2013-08-13
PUBLIC
61/68
Reference
A.1
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.
nFC Target group:
nF, Technology consultants
nF, Project teams for implementations
nFC Current version:
nF, 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.
nFC Target group:
nF, On SAP Service Marketplace at http://service.sap.com/instguides
Configuration Documentation in SAP Solution Manager SAP Solution Manager is a life-cycle
platform. One of its main functions is the configuration of business scenarios, business processes, and
implementable steps. It contains Customizing activities, transactions, and so on, as well as
documentation.
nFC Target group:
nF, Solution consultants
nF, 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.)
nFC Target group:
nF, Solution consultants
nF, Project teams for implementations or upgrades
nF, 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 application operations guides of SAP Business Suite. The manual refers
62/68
PUBLIC
2013-08-13
Reference
A.1
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.
}4 Target group:
}4 System administrators
}4 Current version:
}4 On SAP Service Marketplace at http://service.sap.com/instguides
The application 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.
}4 Target group:
}4 System administrators
}4 Technology consultants
}4 Solution consultants
}4 Current version:
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes 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 upgrade guides and SAP Notes.
}4 Target group:
}4 Project teams for upgrades
}4 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.
}4 Target group:
}4 Project teams for upgrades
}4 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).
}4 Target group:
2013-08-13
PUBLIC
63/68
Reference
A.1
[ Consultants
[ Project teams for upgrades
[v Current version:
[ On SAP Service Marketplace at http://service.sap.com/releasenotes
[ In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
64/68
PUBLIC
2013-08-13
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>.
Arrows separating the parts of a navigation path, for example, menu options
Example
Example
Example
Example
http://www.sap.com
/example
123456
Example
Example
EXAMPLE
EXAMPLE
2013-08-13
Emphasized words or expressions

Words or characters that you enter in the system exactly as they appear in the
documentation
Textual cross-references to an internet address
Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web
Hyperlink to an SAP Note, for example, SAP Note 123456
bL Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
bL Cross-references to other documentation or published works
bL Output on the screen following a user action, for example, messages
bL Source code or syntax quoted directly from a program
bL File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
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
Keys on the keyboard
PUBLIC
65/68
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 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
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. National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP Group products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP 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 other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark
information and notices.
Disclaimer
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.

Documentation in the SAP Service Marketplace
You can find this document at the following address: http://service.sap.com/instguides
66/68
PUBLIC
2013-08-13
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 2013 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.

Operations

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Operations

Diunggah oleh

Hak Cipta:

Format Tersedia

Application Operations Guide

SAP Supplier Relationship Management Powered by SAP

Overview of SAP Enhancement Package 3 for SAP SRM 7.0 . . . . . . . . . . .

Monitoring of SAP Supplier Relationship Management (SAP

Detailed Monitoring and Tools for Problem and Performance

Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About this Guide

1.1 About this Guide

1.2 Important SAP Notes

SAP Service Marketplace Links

Wily Introscope Installation for SAP Customers

1.3 SAP Service Marketplace Links

SAP Service Marketplace Links

SAP Developer Network Links

SAP Solution Manager

SAP Support Package

Information about support

1.4 SAP Developer Network Links

Enterprise Data Warehousing - with Information about Business

1.5 SAP Help Portal Links

SAP Help Portal Links

SAP Library for Application Lifecycle Management under SAP Solution

SAP Library for Supplier Relationship Management onSAP Help Portal at

This page is left blank for documents

Overview of SAP Enhancement Package 3 for SAP SRM 7.0

Technical System Landscape

2 Overview of SAP Enhancement

2.1 Technical System Landscape

2.2 Software Component Matrix

Overview of SAP Enhancement Package 3 for SAP SRM 7.0

2.3 Related Documentation

Location on SAP Service Marketplace/SAP Help Portal

Enhancement package 3 for SAP

Quick Sizer Tool

SAP NetWeaver Library: Function Oriented View Solution

Monitoring of SAP Supplier Relationship Management (SAP SRM)

Alert Monitoring with CCMS

3 Monitoring of SAP Supplier

3.1 Alert Monitoring with CCMS

Monitoring of SAP Supplier Relationship Management (SAP SRM)

Alert Monitoring with CCMS

3.1.1 CCMS Monitoring Installation and Setup

3.1.2 Alert Monitoring of Components

3.1.2.1 SAP NetWeaver 7.4 Monitoring

Monitoring of SAP Supplier Relationship Management (SAP SRM)

Alert Monitoring with CCMS

3.1.2.2 SAP SRM Server 7.13 Monitoring

Monitoring of SAP Supplier Relationship Management (SAP SRM)

Alert Monitoring with CCMS

Dialogue Response Time

Log File Monitoring

3.1.2.3 Monitoring of SAP Live Auction Cockpit Web

GRMG Availability Monitoring for SAP Live

Monitoring of SAP Supplier Relationship Management (SAP SRM)

Alert Monitoring with CCMS

Activating GRMG Monitoring

Monitoring of SAP Supplier Relationship Management (SAP SRM)

Alert Monitoring with CCMS

Monitoring of SAP Supplier Relationship Management (SAP SRM)

Alert Monitoring with CCMS

Verifying GRMG Availability Monitoring for Live

Troubleshooting GRMG Availability Monitoring

No GRMG_SelfMonitoring Subtree Found

3. Shopping Cart