operations

Application Operations GuideSAP Supplier Relationship Management Powered by SAP NetWeaver Using SAP SRM Server 7.13

Target Audience System Administrators Technology Consultants

PUBLICDocument version: 1.0 2013-08-13

Document History

CAUTIONBefore 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 Description1.0 2013-08-13 Final Version

[Description]

2/68 PUBLIC 2013-08-13

Table of Contents

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3 SAP Service Marketplace Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.4 SAP Developer Network Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.5 SAP Help Portal Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2 Overview of SAP Enhancement Package 3 for SAP SRM 7.0 . . . . . . . . . . . 132.1 Technical System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.2 Software Component Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 3 Monitoring of SAP Supplier Relationship Management (SAP SRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.1 Alert Monitoring with CCMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1.1 CCMS Monitoring Installation and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1.2 Alert Monitoring of Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1.2.1 SAP NetWeaver 7.4 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1.2.2 SAP SRM Server 7.13 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.1.2.3 Monitoring of SAP Live Auction Cockpit Web Presentation Server based on

Java Server 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.1.2.3.1 GRMG Availability Monitoring for SAP Live Auction Cockpit Web

Presentation Server based on Java Server 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.1.2.3.2 Activating GRMG Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.1.2.3.3 Verifying GRMG Availability Monitoring for Live Auction based on Java

Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.1.2.3.4 Troubleshooting GRMG Availability Monitoring . . . . . . . . . . . . . . . . . . . . . . 213.1.2.4 SAP SRM Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1.2.5 Monitoring SRM-MDM Catalog 7.02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1.2.5.1 SRM-MDM Catalog 7.02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1.2.5.2 GRMG Availability Monitoring for SRM-MDM Catalog 7.02 . . . . . . . . . . . . . . 27

2013-08-13 PUBLIC 3/68

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

3.2.1 Component-Specific Analysis Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.1.1 SAP Enhancement Package 3 for SAP Supplier Relationship Management

(SAP SRM) 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.1.2 SAP Live Auction Cockpit Web Presentation Server based on Java (LACWPS)

6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.1.3 SRM-MDM Catalog 7.02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.2 Scenario Problem Analysis Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.2.2.1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.2.2.2 Data Archiving Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.2.2.3 Distributed Statistical Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.2.2.4 Business Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.2.3 Logs and Trace (ComponentSpecific or Scenario-Specific) . . . . . . . . . . . . . . . 303.2.4 Data Growth and Data Archiving Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 4 Management of SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.1 Administration Tools of Software Components . . . . . . . . . . . . . . . . . . . . . . . . 314.2 Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.3 Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.4 Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.4.1 General Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.4.2 Backup of Individual Components in an SAP Supplier Relationship

Management (SAP SRM) Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.4.2.1 Backup and Restore for Operating System, Software, and Configuration

Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.4.2.2 Database Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.4.2.3 Backup and Restore for SAP NetWeaver Application Server (SAP NetWeaver

AS) 7.40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.4.3 Backup and Restore for Individual System Components . . . . . . . . . . . . . . . . . 374.4.3.1 SAP Live Auction Cockpit Web Presentation Server based on Java (LACWPS)

6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.4.3.2 Enhancement Package 2 for SRM-MDM Catalog 7.0 . . . . . . . . . . . . . . . . . . . . 384.4.4 Backup and Restore for a Complete SAP SRM Landscape . . . . . . . . . . . . . . . . 384.4.4.1 Landscape Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.4.4.2 Offline Backup of the SAP SRM Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.4.4.3 Landscape Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.4.5 Backup and Restore for an SAP SRM Business Scenario . . . . . . . . . . . . . . . . . . 39

4/68 PUBLIC 2013-08-13

4.5 Application Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.5.1 Homogeneous System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.5.2 Heterogeneous System Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.6 Scheduled and Manual Periodical Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404.6.1 Periodical Tasks for SAP NetWeaver 7.40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404.6.2 Periodical Tasks for SAP Enhancement Package 2 for SAP SRM 7.0 . . . . . . . . . 404.6.3 Periodical Tasks for SAP Enhancement Package 3 for SRM-MDM Catalog

7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.6.4 Manual Periodical Tasks for Enhancement Package 3 for SAP Supplier

Relationship Management (SAP SRM) 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.6.5 Manual Periodical Tasks for Live Auction Cockpit based on Java Server

(LACWPS 6.0) and Live Auction Cockpit based on ABAP Server . . . . . . . . . . . 414.7 Logon and Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.8 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.9 Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 5 High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 6 Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476.1 Transport and Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476.2 Development Requests and Development Release Management . . . . . . . . . . . 486.3 Support Packages and SAP Notes Implementation . . . . . . . . . . . . . . . . . . . . . . 486.4 Release and Upgrade Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496.5 Template Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496.6 Quality Management and Test Management . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 8 Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538.1 Remote Support Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538.2 Problem Message Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538.3 CA Wily Introscope Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 9 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579.1 Categories of System Components for Backup and Restore . . . . . . . . . . . . . . . 579.2 Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

2013-08-13 PUBLIC 5/68

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

6/68 PUBLIC 2013-08-13

1 Getting Started

CAUTIONThis guide does not replace the daily operations section that we recommend customers create for their specific production operations.

1.1 About this GuideDesigning, 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 Found At:Technical Operations Manual for SAP NetWeaver

Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver

Operations Guide for SAP NetWeaver

Operations Information under System Administration and Maintenance Information on SAP Help Portal at http://help.sap.com/netweaver

SAP NetWeaver Security Guide

SAP NetWeaver Security Guide under Security Information on SAP Help Portal at http://help.sap.com/netweaver

Solution Life Cycle Management

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 NotesCAUTIONCheck regularly to see which SAP Notes are available for the Application Operations Guide.

SAP Note Number Title19227 Open newest SAPOSCOL209834 CCMS agent technology

1 Getting Started1.1 About this Guide

2013-08-13 PUBLIC 7/68

797147 Wily Introscope Installation for SAP Customers1126859 End-to-End Diagnostics SP15 SP171515223 SAP NetWeaver Process Integration: Release Recommendation

1.3 SAP Service Marketplace LinksThe following documentation is published on SAP Service Marketplace at service.sap.com.Type of Information Description LocationSAP Supplier Relationship Management (SAP SRM) in Detail

Information about business and technical aspects of SAP Supplier Relationship Management (SAP SRM) including news, services, events, demos, education, and workshops

http://service.sap.com/srm

SAP SRM - Installation And Upgrade Information

Comprehensive information about the installation and upgrade of SAP SRM

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

Master Guide SAP SRM 7.03

Detailed information about the technical system landscape of SAP SRM 7.03

http://service.sap.com /instguides SAP Business Suite Applications SAP SRM SAP SRM Server 7.13

Solution Operation Guide SAP SRM 7.03

Detailed information about how to operate your SAP SRM 7.03 system landscape

http://service.sap.com /instguides SAP Business Suite Applications SAP SRM SAP SRM Server 7.13

SAP NetWeaver Information about the application and integration platform SAP NetWeaver

http://service.sap.com/netweaver

SAP NetWeaver 7.40 Details on SAP NetWeaver Release 7.40

service.sap.com/instguidesNW74

SAP NetWeaver 7.40 Installation Information

Installation information including the Master Guide, Technical Infrastructure Guide, and Installation Guide

service.sap.com/installNW74

SAP NetWeaver 7.40 Upgrade Information

Upgrade information, including the Upgrade Master Guide and Upgrade Guide

http://service.sap.com /upgradeNW74

SAP NetWeaver 7.40 Maintenance Information

Maintenance information, including the Support Package Guides

http://service.sap.com /maintenanceNW74

SAP NetWeaver 7.4 0Central SAP Notes

SAP Notes, including SAP Notes specific to SAP NetWeaver 7.40 installation,

http://service.sap.com /SAPNotesNW70

1 Getting Started1.3 SAP Service Marketplace Links

8/68 PUBLIC 2013-08-13

upgrade, and implementation

SAPs Release Strategy Release and maintenance strategy of SAP

http://service.sap.com /releasestrategy

SAP Best Practices Comprehensive information about SAP Business Suite solutions that are affordable, simple to understand, and quick to implement

http://service.sap.com /bestpractices

Product Availability Matrix (PAM)

Quick reference to technical 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

http://service.sap.com/pam

Hardware Sizing Detailed information about the calculation of hardware, including access to the SAP Quick Sizer

http://service.sap.com/sizing

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.

http://service.sap.com/security

SAP Security Guides Guidelines and recommendations relating to system and network security

http://service.sap.com /securityguide

Platform and Technology Information Center

Overview of platform and technology-related topics

http://service.sap.com /platforms

1 Getting Started1.3 SAP Service Marketplace Links

2013-08-13 PUBLIC 9/68

Unicode at SAP Information about support for multiple local-language characters

http://service.sap.com/unicode

SAP Solution Manager Information about SAP Solution Manager

http://service.sap.com /solutionmanager

SAP System Administration

Comprehensive information about technical infrastructure issues and network integration

http://service.sap.com/system-data

SAP Support Package Stacks

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

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

SAP Software Distribution Center

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/swdc

1.4 SAP Developer Network LinksThe following documentation is published on SAP Developer Network (SDN) at http://www.sdn.sap.com/irj/sdn.Type of Information Description LocationEnterprise Data Warehousing - with the SAP NetWeaver Business Warehouse (BW)

Information about Business Intelligence

http://www.sdn.sap.com/irj/sdn/ edw

SAP GUI Family Information about the various members of the SAP GUI family

http://www.sdn.sap.com/irj/sdn/ sap-gui

SAP NetWeaver Portal Information about SAP NetWeaver Portal

http://www.sdn.sap.com/irj/sdn/ nw-products

SAP Installation Installation and upgrade information

http://www.sdn.sap.com/irj/sdn/ nw-products

High Availability Overview of high-availability aspects for SAP solutions

http://www.sdn.sap.com/irj/sdn/ ha

1.5 SAP Help Portal LinksThe following documentation is published on SAP Help Portal at help.sap.com.

1 Getting Started1.4 SAP Developer Network Links

10/68 PUBLIC 2013-08-13

Type of Information

Description Location

SAP NetWeaver Library

SAP NetWeaver documentation

SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver

Technical Operations Manual for SAP NetWeaver

Instructions for operating your SAP NetWeaver or SAP SRM system

Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver

SAP Solution Manager

Solution Manager documentation

SAP Library for Application Lifecycle Management under SAP Solution Manager on SAP Help Portal at http://help.sap.com/alm

SAP Library SAP SRM documentation

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

SAP SRM Business Functions

Information about Business Functions in SAP SRM

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

SOA SOA documentation SOA content for SRM at SAP Library for Supplier Relationship Management on SAP Help Portal at http://help.sap.com/srm

1 Getting Started1.5 SAP Help Portal Links

2013-08-13 PUBLIC 11/68

This page is left blank for documents that are printed on both sides.

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 LandscapeSAP 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 MatrixFor 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 .

NOTEThe 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.

2 Overview of SAP Enhancement Package 3 for SAP SRM 7.02.1 Technical System Landscape

2013-08-13 PUBLIC 13/68

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 .

NOTEFor 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: When you use the contract management application to search for information such as supplier

texts, internal notes, and attachments. When you want to use the metadata search functionality or use SAP NetWeaver Business

Intelligence (SAP NetWeaver BI) Accelerator in Analytics.

2.3 Related DocumentationThe following table lists where you can find more information about the technical system landscape.Topic Guide/Tool Location on SAP Service Marketplace/SAP Help PortalEnhancement package 3 for SAP SRM 7.0

Master Guide http://service.sap.com/instguides Installation and Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM Server 7.13

Sizing Quick Sizer Tool http://service.sap.com/sizing SAP NetWeaver SAP NetWeaver in Detail Solution Life-Cycle ManagementHardware Sizing Quick Sizer Tool

Technical Configuration SAP NetWeaver Library

SAP NetWeaver Library: Function Oriented View Solution Lifecycle Management SAP NetWeaver Configuration

Scalability SAP NetWeaver Library

SAP NetWeaver Portal Managing the Portal

High Availability SAP NetWeaver Library

SAP NetWeaver Library: Function Oriented View Solution Lifecycle Management High Availability

Security SAP NetWeaver Library

SAP NetWeaver Security Guide SAP NetWeaver Library: Function Oriented View Security

2 Overview of SAP Enhancement Package 3 for SAP SRM 7.02.3 Related Documentation

14/68 PUBLIC 2013-08-13

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 CCMSProactive, 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.).

3 Monitoring of SAP Supplier Relationship Management (SAP SRM)3.1 Alert Monitoring with CCMS

2013-08-13 PUBLIC 15/68

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 SetupTo enable the auto-alert mechanism of CCMS, see SAP Note 617547.

RECOMMENDATIONSAP recommends the use of SAP NetWeaver 7.40 for Central Monitoring.

3.1.2 Alert Monitoring of ComponentsOne 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.

NOTEThis 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 MonitoringSAP 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

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 MonitoringThe 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

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 Your SAP SRM Server 7.13 is connected to the CEN and registered as a remote system. The SAPCCM4X agent is registered and running for each SAP SRM Server 7.13 instance.What to MonitorYour 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.

Procedure1. Go to transaction RZ20 and create a new monitor: SRM Server 7.13 monitor.2. On the top level, create a virtual node for following:

Back-end monitoring Database Operating system System configuration Log file monitoring

3. On the second level, create rule-based monitors for each area as described in the following table:Node Type Parameter ValueBack-End Monitoring VirtualCCMS_DEFINE_R3_SYSTEMS Rule R3System


2013-08-13 PUBLIC 17/68

Node Type Parameter ValueDialogue Response Time Virtual

Rule R3System MTEClass R3DialogResponseTime

Network Time VirtualCCMS_GET_MTE_BY_CLASS Rule R3System

MTEClass R3DialogFrontEndNetTimeUsers Logged On VirtualCCMS_GET_MTE_BY_CLASS Rule R3System

MTEClass R3UsersLoggedInDatabase VirtualCCMS_GET_MTE_BY_CLASS Rule R3System

MTEClass OperatingSystemOperating System VirtualCCMS_GET_MTE_BY_CLASS Rule R3System

MTEClass OperatingSystemSystem Configuration VirtualCCMS_DEFINE_R3_SYSTEMS Rule R3System Dialog Response Time VirtualCCMS_GET_MONITORING_CONTEXT_NAMES

Rule R3System MoniSegment MoniContext System Configuration

Log File Monitoring VirtualCCMS_GET_MTE_BY_CLASS Rule R3System

MTEClass 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

NOTEAs 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

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 application-specific 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.For more information, see the Monitoring Setup Guide for SAP NetWeaver (MSG) under SAP NetWeaver 7.0


3.1.2.3.2 Activating GRMG MonitoringProcedure1. 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 :\usr\sap\\SYS\global\srmla\monitoring.

2. To adjust the customizing files, you need to edit the la_grmg.xml file using an XML editor or any plain text editor. Change the URL specified in the element of the customizing file to the correct hostname and port of your installation.

EXAMPLEIf your installation uses hostname yourhostname on port 8080 then the value in between the and tags must be:http://yourhostname:8080/srm/heartBeatNOTEEach 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).

3. 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

2. Start transaction GRMG by entering GRMG in the OK field in the SAPGUI toolbar.3. 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).

4. After you have uploaded all of the customizing files, start the availability monitoring.CAUTIONEnsure 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.

ResultNo 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 File1. Copy everything in between the tags (including the tags themselves): and .2. Paste them below the last tag.3. Repeat this step for each additional instance you wish to monitor.4. Modify the values in between and , and and , so that they are unique for each instance.RECOMMENDATIONWe 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).

5. Change the URL specified between the and tags to the correct and fully qualified hostname and port for this particular scenario.


20/68 PUBLIC 2013-08-13

3.1.2.3.3 Verifying GRMG Availability Monitoring for Live Auction based on Java Server

ProcedureDisplaying Scenario Execution Status

NOTEIf 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 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.

ResultIf 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 MonitoringNo GRMG_SelfMonitoring Subtree FoundIf 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

The GRMG availability monitoring was not started on the central application server of your SAP system.1. Check for other MoniInfra_ subtrees in the CCMS Selfmonitoring monitor.2. Delete any such trees.3. Start GRMG monitoring on the central application server.

None of the GRMG customizing files that you uploaded could be correctly processed.1. Check the customizing by using transaction SE16 to display the entries in the following GRMG

customizing tables:Customizing Table Required ContentsGRMG_SCENARIOS The technical name [SCEN_NAME] of each monitoring scenario

that you uploaded The URL used by the scenario to test availability

GRMG_SCENARIO_T A descriptive name for each technical name [SCEN_NAME] in GRMG_SCENARIOS

GRMG_PROPERTIES At least one entry for each technical name [SCEN_NAME] in GRMG_SCENARIOS

GRMG_COMPONENTS An entry for each component name [COMP_NAME] in GRMG_PROPERTIES

GRMG_COMPONENT_T A descriptive name for each component name [COMP_NAME] in GRMG_COMPONENTS

If any of the required table content is missing, then the customizing file did not contain complete or valid XML customizing data for GRMG.

2. Download the newest customizing files from the SAP Community Network at the Internet address http://www.sdn.sap.com/irj/sdn/nw-products .

CAUTIONDo 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 ErrorsIf 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: The host specified in the scenario URL may have been unreachable. No answer was received. 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

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 CauseReason for HTTP POST failure: HTTP communication failure Connect failed Time-out occurred

1. The URL specified in the scenario customizing points to a non-existent 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.

Reason for HTTP POST failure: TCP/IP error occurred Data error occurred

Your installation is having problems with the network configuration or with network operation.

Reason for HTTP POST failure: Internal error occurred

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.

Reason for HTTP POST failure: System failure occurred

There is a problem with the HTTP server specified in the scenario URL.

Reason for HTTP POST failure: Argument not found Plug-in not active

Internal error HTTP invalid state

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.

Reason for HTTP POST failure: Destination not found Not authorized to use HTTP

destination

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.

Reason for scenario failure:

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.

Reason for scenario failure: No response for any component in

request

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.


2013-08-13 PUBLIC 23/68

GRMG Scenario Error Message CauseYou can also compare the GRMG request and response directly by switching on HTTP tracing briefly (level 3) in transaction SMICM on the central server of your monitoring system.

Reason for scenario failure:

A formal DTD error, such as unbalanced tags, 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.

Reason for scenario failure: Any message having to do with the

CCMS monitoring architecture, such as- Invalid TID- Wrong segment

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 MonitorNOTEIn 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.

Procedure1. Go to transaction RZ20 and create a new monitor under the SRM monitor set created earlier: SAP

(CEN ) EnterpriseBuyer Monitors.2. On the top level, create a virtual node for each of the following areas:

Approval Auction Bid Invitation Component Planning Confirmation Contract Management Invoice Others Procurement Card Purchase Order


24/68 PUBLIC 2013-08-13

Shopping Cart User Administration

3. On the second level, enter all MTE classes as rule-based monitors for each area as described in the table below:

Node Type Parameter ValueApproval VirtualCCMS_DEFINE_R3_SYSTEMS

Rule R3System

CCMS_GET_MTE_BY_CLASS_AND_CLIENT

Rule R3System R3Client MTEClass BBP_Approval

Auction VirtualCCMS_DEFINE_R3_SYSTEMS

Rule R3System


Rule R3System R3Client MTEClass BBP_AUC

Bid Invitation VirtualCCMS_DEFINE_R3_SYSTEMS

Rule R3System


Rule R3System R3Client MTEClass BBP_BID

Component Planning VirtualCCMS_DEFINE_R3_SYSTEMS

Rule R3System


Rule R3System R3Client MTEClass BBP_PM

Confirmation VirtualCCMS_DEFINE_R3_SYSTEMS

Rule R3System


Rule R3System R3Client MTEClass BBP_Confirmation

Contract Management VirtualCCMS_DEFINE_R3_SYSTEMS

Rule R3System


Rule R3System R3Client MTEClass BBP_Contract

Invoice Virtual


2013-08-13 PUBLIC 25/68

Node Type Parameter ValueCCMS_DEFINE_R3_SYSTEMS

Rule R3System


Rule R3System R3Client MTEClass BBP_INV

Others VirtualCCMS_DEFINE_R3_SYSTEMS

Rule R3System


Rule R3System R3Client MTEClass BBP_OT

Procurement Card VirtualCCMS_DEFINE_R3_SYSTEMS

Rule R3System


Rule R3System R3Client MTEClass BBP_PC

Purchase Orders VirtualCCMS_DEFINE_R3_SYSTEMS

Rule R3System


Rule R3System R3Client MTEClass BBP_PO

Shopping Cart VirtualCCMS_DEFINE_R3_SYSTEMS

Rule R3System


Rule R3System R3Client MTEClass BBP_ShoppingBasket

User Administration VirtualCCMS_DEFINE_R3_SYSTEMS

Rule R3System


Rule R3System R3Client MTEClass BBP_US

3.1.2.5 Monitoring SRM-MDM Catalog 7.023.1.2.5.1 SRM-MDM Catalog 7.02SRM-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

NOTEFor 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 Your SRM-MDM Catalog is connected to the Central Monitoring System (CEN) and registered as

a remote system. 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.

Procedure1. Go to transaction RZ20 and create a new monitor: SRM-MDM Catalog UI2. On the top level, create a virtual node for each of the following areas:

J2EE Engine 7.03 on GRMG Availability Monitor

3. On the second level, create rule-based monitors for each area as described in the following table:Node Type Parameter ValueJ2EE Engine 7.02 on VirtualCCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_SystemsCCMS_GET_MTE_BY_CLASS Rule R3System J2EE_Systems

MTEClass J2EE_PROCGRMG Availability Monitor VirtualCCMS_DEFINE_R3_SYSTEMS Rule R3System CCMS_GET_MTE_BY_CLASS Rule R3System

MTEClass GRMG_WDADM630

NOTEThe 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.1 Component-Specific Analysis Tools3.2.1.1 SAP Enhancement Package 3 for SAP Supplier

Relationship Management (SAP SRM) 7.0SAP 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.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.

NOTESAP 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.02SRM-MDM Catalog 7.02 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 Applications Operations Guide covers only differences and additional information specific to the SAP SRM solution.

3 Monitoring of SAP Supplier Relationship Management (SAP SRM)3.2 Detailed Monitoring and Tools for Problem and Performance Analysis

28/68 PUBLIC 2013-08-13

3.2.2 Scenario Problem Analysis ToolsThe following information applies to all SAP SRM 7.0 business scenarios.

3.2.2.1 InterfacesInterface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and HTTP.For more information, see the Monitoring Setup Guide for SAP NetWeaver (MSG) under SAP NetWeaver 7.40

System Administration and Maintenance Information Operations Information 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.2.2.2 Data Archiving MonitorsFor more information, see the Monitoring Setup Guide for SAP NetWeaver (MSG) under SAP NetWeaver 7.40


3.2.2.3 Distributed Statistical RecordsFor 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://help.sap.com/netweaver.

3.2.2.4 Business PackagesFor 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://help.sap.com/netweaver.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 Logs and Trace (ComponentSpecific or Scenario-Specific)

For Live Auction Cockpit Web Presentation Server based on Java (LACWPS) 6.0: Component-Specific MonitoringLogging Categories /Applications/SRMLATracing Locations com.sap.srm.la

For SRM-MDM Catalog 7.01: Component-Specific MonitoringLogging Categories /Applications/MDMSRMCATTracing Locations 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 MonitoringSoftware Component Object Sub-Object Object TextSAP SRM SERVER /SAPSRM/* (namespace used as of SAP SRM

6.0)All Sub-objects under

3.2.4 Data Growth and Data Archiving MonitorsSAP 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

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 Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver.

4.1 Administration Tools of Software ComponentsAll 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 ConfigurationAll 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

Configuration Tool(s)

Detailed Description

SAP SRM SERVER

Implementation Guide (IMG)

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 SRM SERVER

SAP Solution Manager

SAP Solution Manager is the standard SAP tool for process- and scenario-based configuration.For more information, see SAP Note 1580107.

4.3 Starting and StoppingThe following information is scenario-independent.

4 Management of SAP SRM4.1 Administration Tools of Software Components

2013-08-13 PUBLIC 31/68

Start and Stop Sequence and Tools

Software ComponentStart and Stop Sequence and ToolsSequence Tool Documentation

SAP NetWeaver Process Integration Server

1 STARTSAP (UNIX) SAP Management

Console (Windows)

Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver.SAP NetWeaver Portal 2 STARTSAP (UNIX)

SAP Management Console (Windows)

Back-End System (OLTP) 3 STARTSAP (UNIX) SAP Management

Console (Windows)SRM Server 4 STARTSAP (UNIX)

SAP Management Console (Windows)

Search and Classification (TREX)

5 Start Services (Windows)

Start Daemons (UNIX)SAP Live Auction Cockpit Web Presentation Server based on Java 6.0 (started together with SRM Server)

6

SRM-MDM Catalog 7.02 7 Application Server: STARTSAP (UNIX) SAP Management

Console (Windows)MDM Server: SAP Management

Console (Windows and other platforms)

Repositories: MDM Console

(Windows) MDM CLIX (other

platforms)

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

Adobe Document Services (ADS)

8 Visual AdministratorYou can access the Visual Administrator at the operating system level (D:/USR/SAP//JC/J2EE/ADMIN/GO.BAT)

Configuration Guide for SAP Interactive Forms by Adobe at http://www.sdn.sap.com/irj/sdn/adobe.

4 Management of SAP SRM4.3 Starting and Stopping

32/68 PUBLIC 2013-08-13

4.4 Backup and RestoreTo 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: Backup and restore for each component Cross-system data dependencies and handlingThe 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 CategoryApplication Data Type Backup Method for Application Data

SAP SRM Server XI Original and Replicated

Database and log backup File system backup (full and/or incremental)

SAP NetWeaver Portal

XI Original Database and log backup File system backup (full and/or incremental)

SAP Live Auction Cockpit Web Presentation Server

XI Original and Replicated

Included in SRM Server

SAP Live Auction Cockpit Web Presentation Server using standalone SAP NetWeaver Application Server Java

VIII Original Data is stored on SRM Server Database and log backup File system backup (full and/or incremental) New installation

SRM-MDM Catalog

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

SAP NetWeaver Process Integration

XI Original and Replicated

Database and log backup File system backup (full and/or incremental)

4 Management of SAP SRM4.4 Backup and Restore

2013-08-13 PUBLIC 33/68

Component CategoryApplication Data Type Backup Method for Application Data

Search and Classification (TREX)

III / IV File system backup

Adobe Document Services (ADS)

File system backup

4.4.1 General RemarksCAUTIONThis 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. 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).

Physical cConsistencyRestores 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

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: Time required for a complete reinstallation Time required for additional configuration 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

RECOMMENDATIONWe 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 backup-and-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: Operating system RDBMS data files RDBMS software SAP software and file systems Log files (SAP and other) Software of other system components (file systems and configuration files)

NOTEA 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

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 BackupThe 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.

NOTEIf you perform a backup while the server is running, open files may not be backed up.

File System Backup Versus Full System BackupA 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.

RECOMMENDATIONWe 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 RestoreNOTEWe 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

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.

NOTEWe 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.

NOTEWe recommend regular file system backups (at least after software changes and upgrades, for example, kernel upgrades and service packs). Perform a full system backup after installation and upgrades of the operating system and the SAP software.

For more information, see Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver.

4.4.3 Backup and Restore for Individual System Components4.4.3.1 SAP Live Auction Cockpit Web Presentation Server

based on Java (LACWPS) 6.0SAP Live Auction Cockpit Web Presentation Server based on Java (LACWPS) 6.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.

NOTESAP 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.3.2 Enhancement Package 2 for SRM-MDM Catalog 7.0For 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.4 Backup and Restore for a Complete SAP SRM Landscape4.4.4.1 Landscape ShutdownYou have to shut down the individual components in the following sequence:SAP NetWeaver Portal 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 LandscapeTo 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

NOTEWhen 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/SYS/global/xi...).

4.4.4.3 Landscape StartupFor the startup sequence of the individual components, see Start and Stopping.

4.4.5 Backup and Restore for an SAP SRM Business ScenarioTo 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 Copy4.5.1 Homogeneous System CopyFor 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 CopyHeterogeneous 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.

NOTEA 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.

4 Management of SAP SRM4.5 Application Copy

2013-08-13 PUBLIC 39/68

4.6 Scheduled and Manual Periodical Tasks4.6.1 Periodical Tasks for SAP NetWeaver 7.40For 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 / TaskRequired or Optional

Recommended Frequency Detailed Description

CLEAN_REQREQ_UP (and START_CLEANER)

Required 5 to 10 minutes For more information, see the Solution Manager content on each SAP SRM scenario you have implemented.BBP_GET_STATUS_2 Required*

RSPPFPROCESS OptionalBBPERS OptionalBBP_DELETE_LOCAL_ACCOUNT

Optional

BBP_SC_TRANSFER_GROUPED

Optional

SRM_CALL_HANDLER_REPORT

Required**

RSCONN01 Required/SAPSRM/OFFLINE_APPROVAL_SEND

Optional 5 minutes Send job

* 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 Portal at http://help.sap.com/netweaver.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.

4 Management of SAP SRM4.6 Scheduled and Manual Periodical Tasks

40/68 PUBLIC 2013-08-13

4.6.3 Periodical Tasks for SAP Enhancement Package 3 for SRM-MDM Catalog 7.0

Standard Background Jobs

Program Name / TaskRequired or Optional

Recommended Frequency Detailed Description

SRMMDM_CTR_TRANSFER

Optional 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.

CAUTIONWhen 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.

CAUTIONWhen you choose this option, you lose all auction runtime data that can be seen in the Live Auction Cockpit.

4 Management of SAP SRM4.6 Scheduled and Manual Periodical Tasks

2013-08-13 PUBLIC 41/68

4.7 Logon and Load BalancingAs 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. For more information on network load balancing, see Technical Operations for SAP NetWeaver at SAP

Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver. 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://help.sap.com/netweaver.

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 ManagementAll 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 Detailed Description PrerequisitesSelf Registration SRM Server

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

Refer to the documentation.

Manage User Data (BBPUSERMAINT) SRM Server

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

Refer to the documentation.

User Management in Supplier Self-Services SRM Server (SUS)

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 .

4 Management of SAP SRM4.7 Logon and Load Balancing

42/68 PUBLIC 2013-08-13

4.9 PrintingSAP 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.

4 Management of SAP SRM4.9 Printing

2013-08-13 PUBLIC 43/68

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 UnavailableSAP 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 Process Integration

All scenarios using SAP NetWeaver Process Integration will only have asynchronous messaging available.Document delivery is delayed but not cancelled.

SAP NetWeaver Portal 7.3

As all scenarios are only available via the Portal, a failure would be critical.

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 .

5 High Availability

2013-08-13 PUBLIC 45/68

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: Transport and Change Management

Enables and secures the distribution of software changes from the development environment to the quality assurance and productive environment.

Development Request and Development Release Management Template Management

Enables and secures the rollout of global templates, including localizations Quality and Test Management

Reduces the time, costs, and risks associated with software changes. Support Packages and SAP Notes Implementation

Provides standardized software distribution and maintenance procedures. Release and Upgrade Management

Reduces the time, costs, and risks associated with upgrades.

6.1 Transport and Change ManagementSAP 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 Help Portal at http://help.sap.com/netweaver.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.

6 Software Change Management6.1 Transport and Change Management

2013-08-13 PUBLIC 47/68

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).

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 provide

operations

Documents

management of sap srm

sap srm monitor243

important sap notes

monitoring srmmdm catalog

java server

sap developer network

sap help portal links

detailed monitoring