8432123130593405

7/19/2019
SAP Supplier Relationship Management

Powered by SAP NetWeaver Using SAP
SRM Server 7.14
Generated on: 2019-07-19
SAP Supplier Relationship Management | 7.04 SP12
PUBLIC
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the SAP Help Portal.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=21795174&topics=c91a5276b0ee49a29f561ddd4d9… 1/46
7/19/2019
Document History
Caution
Before you start the implementation, make sure you have the latest version of this document. You can nd the latest version at
the following location: http://service.sap.com/instguides Installation and Upgrade Guides SAP Buisness Suite
Applications SAP SRM SAP SRM Server 7.14 .
Table 1
Version Date Description
1.0 2016-01-20 Final Version
Getting Started
Caution
This guide does not replace the daily operations section that we recommend customers create for their speci c production
operations.
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
speci c 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-speci c
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
7/19/2019
Important SAP Notes

Caution
Check regularly to see which SAP Notes are available for the Application Operations Guide.
SAP Note Number Title
19227 Open newest SAPOSCOL
209834 CCMS agent technology
797147 Wily Introscope Installation for SAP Customers
1126859 End-to-End Diagnostics SP15 − SP17
1515223 SAP NetWeaver Process Integration: Release Recommendation
SAP Service Marketplace Links

The following documentation is published on SAP Service Marketplace .
Type of Information Description
SAP 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
SAP SRM - Installation And Upgrade Information Comprehensive information about the installation and upgrade of
SAP SRM
Master Guide – SAP SRM 7.04 Detailed information about the technical system landscape of SAP
SRM 7.04
Solution Operation Guide – SAP SRM 7.04 Detailed information about how to operate your SAP SRM 7.04
system landscape
SAP NetWeaver Information about the application and integration platform SAP
NetWeaver
SAP NetWeaver 7.40 Details on SAP NetWeaver Release 7.40
SAP NetWeaver 7.40 Installation Information Installation information including the Master Guide, Technical
Infrastructure Guide, and Installation Guide
SAP NetWeaver 7.40 Upgrade Information Upgrade information, including the Upgrade Master Guide and
Upgrade Guide
SAP NetWeaver 7.40 Maintenance Information Maintenance information, including the Support Package Guides
SAP NetWeaver 7.4 0Central SAP Notes SAP Notes, including SAP Notes speci c to SAP NetWeaver 7.40
installation, upgrade, and implementation
SAP’s 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 Matrix (PAM) Quick reference to technical and release planning information about
SAP components, featuring SAP component releases and
7/19/2019
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 Technology Information Center Overview of platform and technology-related topics
Unicode at SAP Information about support for multiple local-language characters
SAP Solution Manager Information about SAP Solution Manager
SAP System Administration Comprehensive information about technical infrastructure issues

and network integration
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
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
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 the SAP Information about Business Intelligence http://www.sdn.sap.com/irj/sdn//edw
NetWeaver Business Warehouse (BW)
SAP GUI Family Information about the various members of http://www.sdn.sap.com/irj/sdn/sap-gui

the SAP GUI family
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 http://www.sdn.sap.com/irj/sdn/ha

solutions
SAP Help Portal Links

The following documentation is published on SAP Help Portal at help.sap.com.
7/19/2019
Type of Information Description Location
SAP NetWeaver Library SAP NetWeaver documentation SAP Library for SAP NetWeaver on SAP
Help Portal at
Technical Operations Manual for SAP Instructions for operating your SAP Technical Operations for SAP NetWeaver at
NetWeaver NetWeaver or SAP SRM system SAP Library for SAP NetWeaver on SAP
Help Portal at
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 Library for Supplier Relationship
SAP SRM Management onSAP Help Portal at
SOA SOA documentation SOA content for SRM at SAP Library for
Supplier Relationship Management on SAP
Help Portal at http://help.sap.com/srm
Overview of SAP Enhancement Package 4

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

SAP enhancement package 4 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 speci c 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.14 .
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 4 for SAP Supplier Relationship Management 7.0 (SAP
enhancement package 4 for SAP SRM 7.0) on SAP Service Marketplace.SAP SRM SAP SRM Server 7.14 .
Note
The Scenario and Process Component List (SCL) is a tool that allows you to nd 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 in the master
7/19/2019
guide. You can nd the SCL on SAP Service Marketplace. Also, you can see the following information at the SAP Service
Marketplace:
Latest component version and patch level requirements, as well as the Release Information Note (RIN) available for
each support package stack.
The exact locations of the required software components on the corresponding DVDs and CDs that are shipped with the
SAP enhancement package 4 for SAP Supplier Relationship Management (SAP SRM) 7.0 package.
Note
For each component listed in the software component matrix, there are software requirements that are not explicitly
mentioned in this documentation. Component-speci c 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 Classi cation 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.
Related Documentation
The following table lists where you can nd more information about the technical system landscape.
Topic Guide/Tool Location on SAP Service Marketplace/SAP Help Portal
Enhancement package 4 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.14
Sizing Quick Sizer Tool http://service.sap.com/sizing SAP NetWeaver SAP NetWeaver

in Detail Solution Life-Cycle Management Hardware
Sizing Quick Sizer Tool
Technical Con guration SAP NetWeaver SAP NetWeaver Library: Function Oriented View Solution
Library Lifecycle Management SAP NetWeaver Con guration
Scalability SAP NetWeaver SAP NetWeaver Portal Managing the Portal

Library
High Availability SAP NetWeaver SAP NetWeaver Library: Function Oriented View Solution
Library Lifecycle Management High Availability
Security SAP NetWeaver SAP NetWeaver Security Guide SAP NetWeaver Library:
Library Function Oriented View Security
Monitoring of SAP Supplier Relationship

Management (SAP SRM)
7/19/2019
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 con gure the Computing Center Management System (CCMS) and create a user-de ned SAP SRM
monitor set re ecting a customer-speci c 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 4 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 4 for SAP Supplier Relationship Management
(SAP SRM) 7.0. Pro cient knowledge of system monitoring and basic knowledge of SAP NetWeaver is required to set up and
manage the user-de ned SAP SRM monitors recommended in this guide.
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 con gure alert monitoring with CCMS for SAP enhancement package 4 for SAP Supplier Relationship Management (SAP SRM)
7.0, you must set up a Central Monitoring System (CEN) and connect all SAP SRM 7.14 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.).
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.14 .
Since SAP enhancement package 4 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 rst. In addition to this,
you can de ne special SAP SRM monitors in the CEN system’s CCMS.
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.
Alert Monitoring of Components

7/19/2019
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 4 for SAP Supplier Relationship Management (SAP SRM) 7.0 includes
component-related monitors such as for SAP enhancement package 4 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 .
SAP NetWeaver 7.4 Monitoring

SAP NetWeaver 7.40 is the integration and application platform for SAP enhancement package 4 for SAP Supplier Relationship
Management (SAP SRM) 7.0.
The following SAP NetWeaver components must be integrated into the monitoring infrastructure:
SAP NetWeaver Application Server (ABAP) 7.40 (for SAP enhancement package 4 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 .
SAP SRM Server 7.14 Monitoring

Use
The main component in your SAP Supplier Relationship Management (SAP SRM) solution is SAP SRM Server 7.04. 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
7/19/2019
Your SAP SRM Server 7.14 is connected to the CEN and registered as a remote system.
The SAPCCM4X agent is registered and running for each SAP SRM Server 7.14 instance.
What to Monitor
Your SAP SRM Server 7.14 is running on SAP NetWeaver Application Server (ABAP) 7.40 – which means the primary points of
failure are within the technical infrastructure.
Procedure
1. Go to transaction RZ20 and create a new monitor: SRM Server 7.14 monitor.
2. On the top level, create a virtual node for following:
Back-end monitoring
Database
Operating system
System con guration
Log le monitoring
3. On the second level, create rule-based monitors for each area as described in the following table:
Node Type Parameter Value
Back-End Monitoring Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System <SRMServer_Systems>
Dialogue Response Time Virtual
Rule R3System <SRMServer_Systems>
MTEClass R3DialogResponseTime
Network Time Virtual
CCMS_GET_MTE_BY_CLASS Rule R3System <SRMServer_Systems>
MTEClass R3DialogFrontEndNetTime
Users Logged On Virtual
MTEClass R3UsersLoggedIn
Database Virtual
MTEClass OperatingSystem
Operating System Virtual
MTEClass OperatingSystem
System Con guration Virtual
7/19/2019
CCMS_DEFINE_R3_SYSTEMS Rule R3System <SRMSERVER_SYSTEMS>
Dialog Response Time Virtual
CCMS_GET_MONITORING_CONTEXT_NAMES Rule R3System <SRMSERVER_SYSTEMS>
MoniSegment <ANY>
MoniContext System Con guration
Log File Monitoring Virtual
CCMS_GET_MTE_BY_CLASS Rule R3System <SRMSERVER_SYSTEMS>
MTEClass CcmsFileMonitoring no such MTE class exists,

needs to be changed to lesystemMO
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 con gured your SAP SRM server to run Live Auction Cockpit on the ABAP
server, section 3.1.2.3 is no longer applicable.
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-speci c 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.
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 .
Activating GRMG Monitoring

1. Obtain the XML format customizing les for the GRMG monitoring scenarios of Live Auction Cockpit based on Java server.
A GRMG customizing le 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 le is named la_grmg.xml for Live Auction Cockpit based on Java server. It can be found in
<INSTDIR>:\usr\sap\<systemname>\SYS\global\srmla\monitoring.
2. To adjust the customizing les, you need to edit the la_grmg.xml le using an XML editor or any plain text editor. Change
the URL speci ed in the <scenstarturl> element of the customizing le to the correct hostname and port of your
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=21795174&topics=c91a5276b0ee49a29f561ddd4d… 10/46
7/19/2019
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
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 le. For more information, see section Adding Scenarios to the XML Customizing File
(below).
3. Upload the customizing le into the central monitoring system.
a. 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.
b. Start transaction GRMG by entering GRMG in the OK eld in the SAPGUI toolbar.
c. Click Upload a GRMG Scenario.
A le selection dialog box is displayed.
d. Navigate to the directory in which the customizing le is located and select the le.
e. Click Open to upload the le.
In the rst production release of this transaction, no con rmation 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 les, 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
7/19/2019
1. Copy everything in between the tags (including the tags themselves): <scenario> and </scenario>.
2. Paste them below the last <scenario> tag.
3. Repeat this step for each additional instance you wish to monitor.
4. Modify the values in between <scenversion> and</scenversion>, and <sceninst> and </sceninst>, so that
they are unique for each instance.
Recommendation
We recommend that you use a value of 001 for the rst instance and then increment the value by one for each additional
instance (002, 003, and so on).
5. Change the URL speci ed between the <scenstarturl> and </scenstarturl> tags to the correct and fully quali ed hostname
and port for this particular scenario.
Verifying GRMG Availability Monitoring for

Live Auction based on Java Server
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 speci ed for the element
<scendesc> in the XML customizing le.)
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
7/19/2019
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.
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:
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.
None of the GRMG customizing les that you uploaded could be correctly processed.
1. Check the customizing by using transaction SE16 to display the entries in the following GRMG customizing tables:
Customizing Table Required Contents
GRMG_SCENARIOS
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 le did not contain complete or valid XML
customizing data for GRMG.
2. Download the newest customizing les from the SAP Community Network at the Internet address
http://www.sdn.sap.com/irj/sdn/nw-products .
Caution
7/19/2019
Do not attempt to correct customizing directly in the customizing tables. Instead, correct the problems by
editing the customizing XML le and uploading the le again.
GRMG_SelfMonitoring Subtree Found with Errors

If you were able to nd 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 speci ed 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.
GRMG continues attempting to run each scenario every ten minutes (or whatever interval you have de ned), 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:

1. The URL speci ed in the scenario customizing points to a
HTTP communication failure non-existent host or port.
Connect failed Check that the URL is valid.
Time-out occurred 2. The HTTP server speci ed in the URL is not running.
Start the HTTP server if it is not running. If the GRMG

application runs on the same server as the monitored
components, then this error message also means that the
tested components are not available.
Reason for HTTP POST failure: Your installation is having problems with the network con guration
or with network operation.
TCP/IP error occurred
Data error occurred
Reason for HTTP POST failure: 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
Internal error occurred
transaction SMICM.
Reason for HTTP POST failure: There is a problem with the HTTP server speci ed in the scenario
URL.
System failure occurred
7/19/2019
GRMG Scenario Error Message Cause
Reason for HTTP POST failure: 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
Argument not found
operations with transaction SMICM.
Plug-in not active
Internal error
HTTP invalid state
Reason for HTTP POST failure: You are using an RFC destination of type HTTP instead of specifying
a URL directly in scenario customizing.
Destination not found
The destination has not been de ned or there is a destination use
Not authorized to use HTTP destination
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 speci ed
<no error message>
in the scenario URL. In this case, the XML parse engine may not
return speci c 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: This error message may occur if a GRMG application responds
without reporting the status of any of the components speci ed in
No response for any component in request
the GRMG monitoring request.
<no error message>
Check that the components speci ed in the GRMG customizing le
match those checked by the GRMG application.
You can also compare the GRMG request and response directly by
switching on HTTP tracing brie y (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.
<Any message relating to invalid XML format>
You can view the response directly by switching on HTTP tracing
<no error message>
brie y (level 3) in transaction SMICM on the central server of your
monitoring system.
Reason for scenario failure: There is a problem in the CCMS monitoring architecture.
Any message having to do with the CCMS monitoring Check the alerts elsewhere in the CCMS Selfmonitoring monitor for
architecture, such as possible causes. Be sure, as well, that you have started GRMG
monitoring only on the central server of the SAP system that you
- Invalid TID
are using for monitoring.
- Wrong segment
SAP SRM Monitor

7/19/2019
Use
Note
In earlier releases, SAP Supplier Relationship Management (SAP SRM) used to be known as SAP Enterprise Buyer. This is still
re ected in the name of the monitor tool, which is called SAP EnterpriseBuyer Monitors.
To reduce administrative tasks for system administration and monitoring, we recommend that you create a separate monitor set
with the SRM monitoring area, SAP (CEN) EnterpriseBuyer Monitors, which includes multiple isolated monitors summarized into
one single monitor. This provides you with a simple separation between the middleware and SAP SRM Server.
Procedure
1. Go to transaction RZ20 and create a new monitor under the SRM monitor set created earlier: SAP (CEN ) EnterpriseBuyer
Monitors.
2. On the top level, create a virtual node for each of the following areas:
Approval
Auction
Bid Invitation
Component Planning
Con rmation
Contract Management
Invoice
Others
Procurement Card
Purchase Order
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:
Approval Virtual
CCMS_GET_MTE_BY_ Rule R3System <SRMSERVER_SYSTEMS>
CLASS_AND_CLIENT R3Client <EBP Client>
MTEClass BBP_Approval
Auction Virtual
CLASS_AND_CLIENT
7/19/2019
R3Client <EBP Client>
MTEClass BBP_AUC
Bid Invitation Virtual
MTEClass BBP_BID
Component Planning Virtual
MTEClass BBP_PM
Con rmation Virtual
MTEClass BBP_Con rmation
Contract Management Virtual
MTEClass BBP_Contract
Invoice Virtual
MTEClass BBP_INV
Others Virtual
MTEClass BBP_OT
Procurement Card Virtual
7/19/2019
MTEClass BBP_PC
Purchase Orders Virtual
MTEClass BBP_PO
Shopping Cart Virtual
MTEClass BBP_ShoppingBasket
User Administration Virtual
MTEClass BBP_US
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.
Note
For more information about MDM Core CCMS monitoring functions, see SAP Note 956783 .
GRMG Availability Monitoring for SRM-MDM

Catalog 7.02
Use
SRM-MDM Catalog runs on the SAP NetWeaver Application Server (Java) 7.4. The main focus of monitoring this component is the
monitoring of the SAP J2EE Engine.
7/19/2019
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
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.
Procedure
1. Go to transaction RZ20 and create a new monitor: SRM-MDM Catalog UI
2. On the top level, create a virtual node for each of the following areas:
J2EE Engine 7.03 on <Hostname>
GRMG Availability Monitor
3. On the second level, create rule-based monitors for each area as described in the following table:
J2EE Engine 7.02 on <Hostname> Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System J2EE_Systems
CCMS_GET_MTE_BY_CLASS Rule R3System J2EE_Systems
MTEClass J2EE_PROC
GRMG Availability Monitor Virtual
CCMS_DEFINE_R3_SYSTEMS Rule R3System <CURRENT>
CCMS_GET_MTE_BY_CLASS Rule R3System <CURRENT>
MTEClass GRMG_WDADM630
SAP Enhancement Package 4 for SAP

Supplier Relationship Management (SAP
SRM) 7.0
SAP enhancement package 4 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 speci c to the SAP SRM solution.
7/19/2019
SAP SRM 7.14 application-speci c logging information is written to the application log.
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.
.
The SAP SRM Application Operations Guide covers only differences and additional information speci c to the SAP SRM solution.
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.
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 speci c to the SAP SRM solution.
Scenario Problem Analysis Tools

This section is applicable to all the SAP SRM 7.0 business scenarios.
Interfaces
Interface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and HTTP.
Administration and Maintenance Information Operations Information SAP Help Portal at 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.
Data Archiving Monitors

Administration and Maintenance Information Operations Information on SAP Help Portal at help.sap.com/netweaver and
Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP Help Portal at help.sap.com/netweaver .
7/19/2019
Distributed Statistical Records

For more information about the motivation behind distributed statistical records and how to de ne 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 .
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 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 .
Logs and Trace (Component–Speci c or

Scenario-Speci c)
For Live Auction Cockpit Web Presentation Server based on Java (LACWPS) 6.0: Component-Speci c Monitoring
Logging Categories /Applications/SRMLA
Tracing Locations com.sap.srm.la
For SRM-MDM Catalog 7.01 Component-Speci c Monitoring
Logging Categories /Applications/MDMSRMCAT
Tracing 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.
For SRM Server 7.01 component speci c monitoring having software component SAP SRM SERVER, you can nd the following
object and sub-objects:
Object Sub-Object
/SAPSRM/* (namespace used as of SAP SRM 6.0) All Sub-objects

under
/SAPSRM/ECATT All Sub-objects

under
/SAPSRM/UM_IDM All Sub-objects

under
/SAPPSSRM/* (namespace used for Procurement for Public Sector developments, some of which were retro tted to All Sub-objects
SAP SRM) under
/SAPPSSRM/CLOSEOUT All Sub-objects

under
7/19/2019
Object Sub-Object
/SAPPSSRM/FPDS All Sub-objects

under
/SAPPSSRM/FUT_DATE All Sub-objects

under
/SAPPSSRM/OPTIONS All Sub-objects

under
/SAPPSSRM/PA_LOG All Sub-objects

under
/SAPPSSRM/RM_SRM_INT All Sub-objects

under
/SAPPSSRM/SYNOPSIS All Sub-objects

under
BBP* (namespace used prior to SAP SRM 6.0) All Sub-objects

under
BBP_ARCHIVING All Sub-objects

under
BBP_ATTR All Sub-objects

under
BBP_CM All Sub-objects

under
BBP_CTR_INIT_UPLOAD All Sub-objects

under
BBP_EXTREQ All Sub-objects

under
BBP_LOCATIONS_GET All Sub-objects

under
BBP_MS_TP All Sub-objects

under
BBP_MS_USER All Sub-objects

under
BBP_NONR3_ADDRESS All Sub-objects

under
BBP_NONR3_PARTNER All Sub-objects

under
BBP_OCI All Sub-objects

under
BBP_OPI All Sub-objects

under
BBP_PAYMENTTERMS_GET All Sub-objects

under
BBP_PCH_INDEX All Sub-objects

under
7/19/2019
Object Sub-Object
BBP_PD_REASSIGNMENT All Sub-objects

under
BBP_SECURITY All Sub-objects

under
SAPPSSRM/PA_LOG All Sub-objects

under
BBP_SUS_BUPA All Sub-objects

under
/BBP_SUS_USER All Sub-objects

under
Data Growth and Data Archiving Monitors

SAP enhancement package 4 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-speci c tool.
For more information about Data Archiving see SAP Library for SAP NetWeaver on SAP Help Portal at
http://help.sap.com/netweaver.
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
Administration Tools of Software

Components
All SAP SRM 7.04 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
Software Con guration

All components for SAP enhancement package 4 for SAP Supplier Relationship Management (SAP SRM) 7.0 are technically based
on SAP NetWeaver 7.40. For information about the relevant con guration 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 con guration parameters in the Con guration Manager (CM) repository. For more
information about the Con g Tool, see Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP Help
Portal at http://help.sap.com/netweaver .
7/19/2019
SAP SRM SERVER Con guration 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
con guration.
For more information, see SAP Note

1580107 .
Starting and Stopping

The following information is scenario-independent.
Start and Stop Sequence and Tools
Software Start and Stop Sequence and Tools

Component
Sequence Tool Documentation
SAP NetWeaver 1 Technical Operations for SAP

STARTSAP (UNIX)
Process NetWeaver at SAP Library for SAP
Integration SAP Management Console (Windows) NetWeaver on SAP Help Portal at
Server http://help.sap.com/netweaver .
SAP NetWeaver 2
STARTSAP (UNIX)
Portal
SAP Management Console (Windows)
Back-End System 3
STARTSAP (UNIX)
(OLTP)
SRM Server 4
STARTSAP (UNIX)
Search and 5
Start Services (Windows)
Classi cation
(TREX) Start Daemons (UNIX)
SAP Live Auction 6

Cockpit Web
Presentation
Server based on
Java 6.0 (started
together with
SRM Server)
7/19/2019
Software Start and Stop Sequence and Tools

Component
Sequence Tool Documentation
SRM-MDM 7 Application Server: SAP NetWeaver MDM Solution

Catalog 7.02 Operations Guide at SAP Library for
STARTSAP (UNIX)
SAP NetWeaver MDM on SAP Help
SAP Management Console (Windows) Portal at http://help.sap.com/nwmdm
.
MDM Server:
SAP Management Console (Windows and other

platforms)
Repositories:
MDM Console (Windows)
MDM CLIX (other platforms)
Adobe Document 8 Visual Administrator Con guration Guide for SAP Interactive
Services (ADS) Forms by Adobe at
You can access the Visual Administrator at the operating
http://www.sdn.sap.com/irj/sdn/adobe
system level
.
(D:/USR/SAP/<SID>/JC<INSTNO>/J2EE/ADMIN/GO.BAT)
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:
Backup and restore for each component
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 ow of your company.
In addition, the backup concept must cover disaster recovery processes, for example, loss of your data center due to re. 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 Category Application 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)
7/19/2019
Component Category Application Data Type Backup Method for Application

Data
SAP NetWeaver Portal XI Original

Database and log
backup

and/or incremental)
SAP Live Auction Cockpit Web XI Original and Replicated

Included in SRM Server
Presentation Server
SAP Live Auction Cockpit Web VIII Original

Data is stored on SRM
Presentation Server using
Server
standalone SAP NetWeaver
Application Server Java
Database and log
backup

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 XI Original and Replicated

Database and log
Integration
backup

and/or incremental)
Search and Classi cation III / IV

File system backup
(TREX)
Adobe Document Services

File system backup
(ADS)
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 le 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.
7/19/2019
Due to the non-transactional character of the document work ow between the different landscape components involved within
one SAP Supplier Relationship Management (SAP SRM) business scenario, it is impossible to nd 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 work ow 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 Consistency
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 work ows
and outdated documents appearing after the restoration.
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 con guration of the system landscape. We also recommend a backup after changes (this means changes to
the con guration, 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 con guration
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 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
Backup of Individual Components in an SAP

Supplier Relationship Management (SAP
7/19/2019
SRM) Landscape
When you plan a backup-and-restore strategy for application, software, and con guration les, you must consider the following
elements:
Operating system
RDBMS data les
RDBMS software
SAP software and le systems
Log les (SAP and other)
Software of other system components ( le systems and con guration les)
Note
A component that has application data (database, for example) also contains application software and con guration
les (runtime infrastructure) that need to be backed up.
A component that contains no application data may still contain con guration les and software that do require a
backup.
Backup and Restore for Operating System,

Software, and Con guration 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 con guration les). 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 con guration data, reinstallation and con guration take
a long time. Therefore, if a backup of the software and con guration 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 les 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 les may not be backed up.
File System Backup Versus Full System Backup

7/19/2019
A le system backup only applies to speci c les or le systems, whereas a full system backup applies to all les and le systems,
and to the operating system.
Recommendation
We recommend that you perform a full system backup after installation and that you back up the le 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 .
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.
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 les during the day as the log les ll
up.
Backup and Restore for SAP NetWeaver

Application Server (SAP NetWeaver AS) 7.40
Back up the le system in which the application software is installed.
Note
We recommend regular le 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.
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.
Technical Operations for SAP NetWeaver at SAP Library for SAP NetWeaver on SAP Help Portal at
7/19/2019
The SAP SRM Application Operations Guide covers only differences and additional information speci c to the SAP SRM solution.
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.
Enhancement Package 4 for SRM-MDM

Catalog 7.0
Landscape Shutdown
You 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 Classi cation
Shut down the SAP system and the underlying Relational Database Management System (RDBMS).
SAP NetWeaver Process Integration Server
7/19/2019
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.
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.
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 le system. This is required because the le system contains the SAP J2EE Engine together with the necessary
con guration les for the system landscape directory and the document transformation (
/usr/sap/<SID>SYS/global/xi...).
Landscape Startup
For the startup sequence of the individual components, see Start and Stopping.
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 speci c business scenario, see Software Component Matrix.
Homogeneous System Copy

For a homogeneous system copy of SAP enhancement package 4 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 .
Heterogeneous System Copy

Heterogeneous system copies for SAP enhancement package 4 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 4 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.
7/19/2019
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 .
Periodical Tasks for SAP Enhancement

Package 4 for SAP SRM 7.0
Standard Background Jobs
Program Name / Task Required or Recommended Detailed Description

Optional Frequency
CLEAN_REQREQ_UP (and Required 5 to 10 minutes For more information, see the Solution Manager
START_CLEANER) content on each SAP SRM scenario you have
implemented.
BBP_GET_STATUS_2 Required*
RSPPFPROCESS Optional
BBPERS Optional
BBP_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 con guration 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
For more information about Components of SAP Communication Technology, see Function-Oriented View for SAP NetWeaver on
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
Periodical Tasks for SAP Enhancement

Package 4 for SRM-MDM Catalog 7.0
7/19/2019
Standard Background Jobs
Program Name / Task Required or Recommended Detailed Description

Optional Frequency
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 agged 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 .
Manual Periodical Tasks for Enhancement

Package 4 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
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.
Logon and Load Balancing

7/19/2019
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.
For more information on network load balancing, see Technical Operations for SAP NetWeaver at SAP Library for SAP
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 speci c application servers.
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
Because of special requirements of the SRM Server, the following SRM-speci c user management tools are also available:
User Management Tools (SRM Server)
Tool Detailed Description Prerequisites
Self Registration – SRM Server SAP Library for SAP Supplier Relationship Refer to the documentation.
Management on SAP Help Portal at
Manage User Data (BBPUSERMAINT) – SRM Employee Data under SAP Library for Refer to the documentation.
Server Supplier Relationship Management on SAP
Help Portal at http://help.sap.com/srm
User Management in Supplier Self-Services SAP Library for Supplier Relationship To create users in the SUS system, you must
– SRM Server (SUS) Management on SAP Help Portal at 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 Con guration Structures SAP SRM 7.0 EHP1 Basic Settings for Service Procurement Classic Settings for Supplier
Collaboration Settings for Supplier Self-Services .
Printing
SAP enhancement package 4 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 .
7/19/2019
Perodical Tasks for SAP SRM User Interface

Add-On
Standard Background Enterprise Search Required or Optional Recommended Detailed Description
Jobs Transaction Models Frequency
Catalog and Product Required Once a Week Frequency depends on

master Extraction (/ the changes done in the
SRMNXP/CAT01) catalog. Extraction is
required to get the latest
data.
Indexing Catalog and Required Once a Week Frequency depends on

Search Result
Product Master the frequency of catalog
Model
Extraction and product master
(ESH_COCKPIT) Search Terms extraction.
Price Sales
Customer Fields
Attributed Model
Attachments
Model
Periodic update of item Price Conversion Table Required Once a Week Frequency depends on
price in Catalog to the frequency change of
Common Currency (to currency exchange rate.
update the transaction)
Report /SRMNXP/
CTLG_COM_CUR_UPD
Deletion Report Optional Once a Week Deletes data from

staging tables and
This report allows you to
images from content
delete data of a particular
management server. You
catalog from the staging
need to run a full
tables.
indexing of TREX after
Report running the deletion
report to ensure data
/SRMNXP/ consistency.
CATALOG_ERR_EX_DA
T_DEL
7/19/2019
Standard Background Enterprise Search Required or Optional Recommended Detailed Description

Jobs Transaction Models Frequency
Handling extraction of Optional When extracting large Steps for extraction:

large JSON les (more JSON Files
1. Place les in
than 1GB)
application
server
Note
2. Check for the le
This extraction is
in AL11
provided only in
transaction
background mode. For
more information, 3. In the extraction
refer1875318 cockpit, select
SAP Directories
cockpit.
4. Provide complete
le name
including
directory as
shown in AL11.
5. Check Schedule
Job button.
6. Click and
execute.
The jobs should be monitored regularly to avoid system resources being utilized completely. The role /SRMNXP/
CONTENT_MGMT must be assigned to the user performing the catalog. product master, and master data extraction. Additionally,
the user requires the role SAP_ESH_CR_ADMIN to perform the indexing operations in TREX and Enterprise Search cockpit.
Archiving in SRM UI Add-On

Based on the type of data, archiving in SRM UI Add-On can be broadly categorized into:
Archiving of shopping cart data - transactional data that is in SRM UI Add-On is archived using standard archiving object,
BBP_SC
Archiving of Catalog data - new archiving object SRMNXP_CAT is introduced
Archiving of Shopping Cart and Catalog Data

Tables for Archiving of Shopping Cart Data
The database table that stores the transactional data for the SRM UI Add-On application is /SRMNXP/D_ITMREF. The data from
this table is archived when shopping cart is archived using the archiving object, BBP_SC.
Tables for Archiving of Catalog Data
The database tables that store the catalog data and the related data for the SRM UI Add-On application are:
/SRMNXP/CAT_ITM - main table for catalog
/SRMNXP/ATTCHMNT
7/19/2019
/SRMNXP/ATT_MAIN
/SRMNXP/ATT_THMB
/SRMNXP/ATT_TXT
/SRMNXP/DESC_TXT
/SRMNXP/LNG_TXT
/SRMNXP/MATGRTXT
/SRMNXP/ITM_SRCH
/SRMNXP/ITM_ATTR
/SRMNXP/PRCSCALE
A new archiving object SRMNXP_CAThas been introduced to archive data. You can use transaction SARA to archive catalog items,
which are indexed.
Following is the list of reports introduced that are used from transaction SARA:
S.no Report Program Type Description
1 /SRMNXP/ Preprocessing This is called when system

ARCH_CATALOG_DATA_PRE administrator triggers archiving
of the catalog data. This
program carries out the
achievability check, sets
deletion indicator for the record
to true, and change indicator for
the record in enterprise search
to deleted.
2 /SRMNXP/ Write This program writes all the data

ARCH_CATALOG_DATA_WRI in the /SRMNXP/ CAT_ITM
table that has deletion ag set
to true and the related data from
the other tables to the archive
le. A record in/SRMNXP/
CAT_ITM table has been taken
as an object.
3 /SRMNXP/ Delete This program reads the archived

ARCH_CATALOG_DATA_DEL data from the archive le and
deletes them from the database
tables.
Troubleshooting
Note
If an error 'RFC Communication failure' arises when searching data on the UI, then the problem can be that the TREX server is
down or connection to TREX server could be broken. Check the RFC connection to TREX system.
High Availability
7/19/2019
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.14 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 signi cantly 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.4 As all scenarios are only available via the Portal, a failure would be
critical.
SAP enhancement package 4 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 Technology SAP NetWeaver Platform SAP NetWeaver
7.40 Application Help SAP Library Function-Oriented View Solution Life Cycle Management SAP High Availability .
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 speci c
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.
7/19/2019
Release and Upgrade Management
Reduces the time, costs, and risks associated with upgrades.
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 4for 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
SAP enhancement package 4 for SAP Supplier Relationship Management (SAP SRM) 7.0 can be used with more than one portal
tenant, and in several different ways.
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 provided to different companies by an application service provider.
Other SAP SRM components could be shared with other SAP or non-SRM applications like SAP NetWeaver Process
Integration and SAP NetWeaver Portal.
Development Requests and Development

Release Management
The transport work ow 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 de ned
approval steps to ensure the quality of your target systems.
Support Packages and SAP Notes

Implementation
Information on the support packages (SPs) available for enhancement package 4 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.
7/19/2019
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 Help Portal at
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 .
Release and Upgrade Management

Component Release
Software Component Release Tool
SAP SRM 7.0 System Status
LAC WPS 6.0 System Info http://<server>:

<port>/sap/monitoring/ComponentInfo
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
https://support.sap.com/solutionmanager .
For SAP SRM release and upgrade plans, see the information available on SAP Service Marketplace at
http://service.sap.com/srm .
Template Management
You can deploy Customizing settings by using Business Con guration Sets (BC Sets).
For more information, For more information about BC Con guration Sets, see Function-Oriented View for SAP NetWeaver on
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 Function-Oriented View for SAP
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://help.sap.com/netweaver .
7/19/2019
Troubleshooting
All services offered by SAP Active Global Support are available for SAP enhancement package 4 for SAP Supplier Relationship
Management (SAP SRM) 7.0.
For more information about these services, see SAP Safeguarding on SAP Service Marketplace at http://help.sap.com
Technology Platform SAP Composition Environment SAP NetWeaver CE 7.2 Application Help SAP Library Administrator's
Guide Administration of SAP NetWeaver CE SAP High Availability Tools and Services for High Availability SAP 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
Possible problem situations using SAP enhancement package 4 for SAP Supplier Relationship Management (SAP SRM) 7.0
Problem Application Components Information
No monitoring information is displayed in All SAP Supplier Relationship Management See the (CCMS) CCMS Monitoring
the CCMS Alert Monitor (transaction RZ20) (SAP SRM) application components Infrastructure guide at SAP Community
of the central monitoring SAP Web AS ABAP Network http://wiki.sdn.sap.com Wiki My
system. However, monitoring information is Home Technology Troubleshooting
available in the Visual Administrator of the Guide (JSTTSG)Main Page Application
J2EE server, for example status information Server ABAP (CCMS) CCMS Monitoring
in the J2EE status monitors. Infrastructure
Error “Page not found or not available” while Business Packages for SAP SRM See SAP Note 1260119 .
accessing a catalog con gured in the SRM
Server.
Display of System messages in Portal and srm-ebp-ca-ui See SAP note 1676725 for other
NWBC : Transaction SM02 in SAPGUI allows con guration steps on this feature.
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 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 Classi cation may lead to diminished system performance.
Note
The search function is not supported for the following:
Shopping cart
Purchase order
7/19/2019
Contract
Con rmation
Supplier
Product category
Product
Restarting Embedded Search may lead to diminished system performance.
For troubleshooting SAP NetWeaver MDM, see http://help.sap.com//installmdm71 Solution Operation Guide Troubleshooting
and Supportability Troubleshooting .
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:
Remote Support
Component hierarchy relevant for this application
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.
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 Master Data Governance
Infrastructure
CA-MDG-DRF Data Replication Framework
CA-MDG-RIF Replication Interface Framework
CA-MDG-KM Key Mapping
CA-MDG-ML Mass Load
7/19/2019
CA-MDG-AF Application Framework
CA-MDG-TRR Transport Registry
CA-MDG-VM Value Mapping
CA-MDG-ANR Analytics and Reporting
CA-MDG-DQ Data Quality
Applications
CA-MDG-APP Applications
CA-MDG-APP-CLF MDG Classi cation
CA-MDG-APP-MM MDG Material
CA-MDG-APP-BP MDG Business Partner (central parts)
CA-MDG-APP-SUP MDG Supplier (central parts)
CA-MDG-APP-SUP-FI MDG Supplier ( nancial parts)
CA-MDG-APP-SUP-LO MDG Supplier (logistics parts)
CA-MDG MDG Supplier (SRM parts)
-APP-SUP-SRM
CA-MDG-APP-FIN MDG Financials
BI Content
BW-BCT-MDG Master Data Governance
Note
SAP Supplier Relationship Management (SAP SRM) does not ship speci c 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 Portal at
CA Wily Introscope Integration

Use
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-speci c interaction within Introscope
using the Transaction Trace.
Metrics, which are collected and reported through traces de ned in Probe Builder Directive (PBD) les, de ne 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.
7/19/2019
To enable Introscope for SAP SRM, install and con gure the Introscope Agent on the SAP SRM application server hosts. For more
information about setting up and con guring 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, con guration, and use of diagnostics in SAP Solution Manager, see SAP Service
Marketplace under http://service.sap.com/diagnostics .
Categories of System Components for

Backup and Restore
Categories of System Category Properties Suggested Backup and Example
Components Recovery Methods
I Only software, no con guration BDOC-modeler

No backup, new
or application data
installation in case of a
restore or
Initial software backup

after installation and
upgrade
Backup of log les
II Only software and con guration SAP Gateway Comm. Station

Backup after changes
information, no application data
have been applied or SAP Business Connector
No backup, new
installation and
con guration in case of
a restore
Backup of log les
7/19/2019

III Only replicated application data, Data: SAP IMS / Search engine
replication time is sufficiently
No data backup needed Webserver
small for a restore
Backup of software,
con guration, log les
IV Only replicated application data, Data: SAP IMS / Search engine

backup recommended because
Application-speci c le Webserver
replication time is too long, data
system backup or
managed by a DBMS
Multiple instances
Backup of software,
V Only replicated application data, Data: Catalog Server

backup recommended because
Database and log
replication time is too long, data
backup or
managed by a DBMS
Multiple instances
Backup of software,
VI Original application data, Data: Webserver

standalone system, data not
Application-speci c le
managed by a DBMS
system backup
Backup of software,
VII Original application data, Data:

standalone system, data
Database and log
managed by a DBMS, not based
backup
on SAP NW AS
Backup of software,
VIII Original application data, Data: Standalone SAP system

standalone system, based on
Database and log
SAP NW AS
backup, application log
backup
Backup of software,
IX Original application data, data Data:

exchange with other systems,
Application-speci c le
data not managed by a DBMS
system backup, data
consistency with other
systems must be
regarded
Backup of software,
7/19/2019

X Original application data, data Data: SAP liveCache

Database and log SAP Mobile
data managed by a DBMS, not
backup, data
based on SAP NW AS Workbench
systems must be
regarded.
Backup of software,
XI Original application data, data Data: SAP system

Database and log SAP CRM
based on SAP NW AS
backup, application log
SAP NW BI
backup, data
systems must be
regarded
Backup of software,
Related Information
The following table contains links to information relating to the Application Operations Guide.
Content SAP Service Marketplace:
SAP SRM Master Guide, Installation and Upgrade Guides http://service.sap.com/instguides Installation and Upgrade
Guides SAP Business Suite Applications SAP SRM SAP SRM
Server 7.13
SAP Notes http://support.sap.com/notes
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
SAP NetWeaver (JAVA) Technical Operations Manual Technical Operations for SAP NetWeaver at SAP Library for SAP
SAP Solution Manager http://support.sap.com/solutionmanager

8432123130593405

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

8432123130593405

Загружено:

Авторское право:

Доступные форматы

7/19/2019

SAP Supplier Relationship Management

SAP Supplier Relationship Management | 7.04 SP12

For more information, please visit the SAP Help Portal.

Version Date Description

1.0 2016-01-20 Final Version

About this Guide

Document Found At:

Important SAP Notes

SAP Note Number Title

19227 Open newest SAPOSCOL

209834 CCMS agent technology

797147 Wily Introscope Installation for SAP Customers

1126859 End-to-End Diagnostics SP15 − SP17

1515223 SAP NetWeaver Process Integration: Release Recommendation

SAP Service Marketplace Links

Type of Information Description

SAP NetWeaver 7.40 Details on SAP NetWeaver Release 7.40

SAP’s Release Strategy Release and maintenance strategy of SAP

Hardware Sizing Detailed information about the calculation of hardware, including

Security Information about the security infrastructure of SAP NetWeaver

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

SAP Solution Manager Information about SAP Solution Manager

SAP System Administration Comprehensive information about technical infrastructure issues

SAP Developer Network Links

Type of Information Description Location

SAP GUI Family Information about the various members of 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-

SAP Installation Installation and upgrade information http://www.sdn.sap.com/irj/sdn/nw-

High Availability Overview of high-availability aspects for SAP http://www.sdn.sap.com/irj/sdn/ha

SAP Help Portal Links

Overview of SAP Enhancement Package 4

Technical System Landscape

Software Component Matrix

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

Sizing Quick Sizer Tool http://service.sap.com/sizing SAP NetWeaver SAP NetWeaver

Scalability SAP NetWeaver SAP NetWeaver Portal Managing the Portal

Monitoring of SAP Supplier Relationship

Alert Monitoring with CCMS

CCMS Monitoring Installation and Setup

Alert Monitoring of Components

SAP NetWeaver 7.4 Monitoring

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)

SAP SRM Server 7.14 Monitoring

2. On the top level, create a virtual node for following:

System con guration

Node Type Parameter Value

Back-End Monitoring Virtual

CCMS_DEFINE_R3_SYSTEMS Rule R3System <SRMServer_Systems>

Dialogue Response Time Virtual

Rule R3System <SRMServer_Systems>

Network Time Virtual

CCMS_GET_MTE_BY_CLASS Rule R3System <SRMServer_Systems>

Users Logged On Virtual

CCMS_GET_MTE_BY_CLASS Rule R3System <SRMServer_Systems>

CCMS_GET_MTE_BY_CLASS Rule R3System <SRMServer_Systems>

Operating System Virtual

CCMS_GET_MTE_BY_CLASS Rule R3System <SRMServer_Systems>

System Con guration Virtual

Node Type Parameter Value